<?xml version="1.0" encoding="UTF-8"?>
<FEDREG xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FRMergedXML.xsd">
    <VOL>76</VOL>
    <NO>207</NO>
    <DATE>Wednesday, October 26, 2011</DATE>
    <UNITNAME>Contents</UNITNAME>
    <CNTNTS>
        <AGCY>
            <EAR/>
            <PRTPAGE P="iii"/>
            <HD>Advisory Council on Historic Preservation</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Historic Preservation, Advisory Council</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Agency Health</EAR>
            <HD>Agency for Healthcare Research and Quality</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Scientific Information Requests:</SJ>
                <SJDENT>
                    <SJDOC>Phototherapy for Treatment of Chronic Plaque Psoriasis, </SJDOC>
                    <PGS>66307-66308</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27563</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Agriculture</EAR>
            <HD>Agriculture Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Office of Advocacy and Outreach</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Rural Utilities Service</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>66269-66270</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27638</FRDOCBP>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27639</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Antitrust Division</EAR>
            <HD>Antitrust Division</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>National Cooperative Research and Production Act of 1993:</SJ>
                <SJDENT>
                    <SJDOC>Advanced Media Workflow Association, Inc., </SJDOC>
                    <PGS>66324</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27399</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Cooperative Research Group on Development of a Predictive Model for Corrosion-Fatigue of Materials in Sour Environment, </SJDOC>
                    <PGS>66325</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27398</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Cooperative Research Group on NASGRO Development and Support, </SJDOC>
                    <PGS>66324-66325</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27400</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Army</EAR>
            <HD>Army Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Stationing and Operation of Joint High Speed Vessels; Withdrawal, </SJDOC>
                    <PGS>66281-66282</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27693</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Army Education Advisory Committee, </SJDOC>
                    <PGS>66282</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27695</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Centers Disease</EAR>
            <HD>Centers for Disease Control and Prevention</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Statement of Organization, Functions, and Delegations of Authority, </DOC>
                    <PGS>66308-66309</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27497</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Centers Medicare</EAR>
            <HD>Centers for Medicare &amp; Medicaid Services</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Pilot Program for Parallel Review of Medical Products:</SJ>
                <SJDENT>
                    <SJDOC>Correction, </SJDOC>
                    <PGS>66309</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27694</FRDOCBP>
                </SJDENT>
            </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>66309-66310</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27602</FRDOCBP>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27611</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Coast Guard</EAR>
            <HD>Coast Guard</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Drawbridge Operations:</SJ>
                <SJDENT>
                    <SJDOC>Nanticoke, Seaford, DE, </SJDOC>
                    <PGS>66184</PGS>
                    <FRDOCBP T="26OCR1.sgm" D="0">2011-27722</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Trent River, New Bern, NC, </SJDOC>
                    <PGS>66183-66184</PGS>
                    <FRDOCBP T="26OCR1.sgm" D="1">2011-27721</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Safety Zones:</SJ>
                <SJDENT>
                    <SJDOC>Fireworks Displays within the Fifth Coast Guard District, </SJDOC>
                    <PGS>66239-66248</PGS>
                    <FRDOCBP T="26OCP1.sgm" D="9">2011-27645</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Lower Mississippi River Waterway Safety Advisory Committee, </SJDOC>
                    <PGS>66314</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27643</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Maritime Security Advisory Committee, </SJDOC>
                    <PGS>66313-66314</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27724</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Commerce</EAR>
            <HD>Commerce Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Industry and Security Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>International Trade Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Oceanic and Atmospheric Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Defense Acquisition</EAR>
            <HD>Defense Acquisition Regulations System</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>66282-66283</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27674</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Defense Department</EAR>
            <HD>Defense Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Army Department</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Defense Acquisition Regulations System</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Navy Department</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Defense Transportation Regulation, Part IV, </DOC>
                    <PGS>66281</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27654</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Education</EAR>
            <HD>Education Department</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Teacher Preparation and TEACH Grant Programs:</SJ>
                <SJDENT>
                    <SJDOC>Negotiated Rulemaking Committee, Negotiator Nominations and Schedule of Committee Meetings, </SJDOC>
                    <PGS>66248-66249</PGS>
                    <FRDOCBP T="26OCP1.sgm" D="1">2011-27719</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Committee on Measures of Student Success, </SJDOC>
                    <PGS>66283</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27655</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Employment and Training</EAR>
            <HD>Employment and Training Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Amended Certifications Regarding Eligibility  To Apply for Worker and Alternative Trade Adjustment Assistance:</SJ>
                <SJDENT>
                    <SJDOC>Callaway Golf Ball Operations, Inc., et al., Chicopee, MA, </SJDOC>
                    <PGS>66328</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27702</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Iron Mountain Information Management, Inc., Corporate Service Group, et al., Boston, MA, </SJDOC>
                    <PGS>66327-66328</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27703</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Determinations Regarding Eligibility to Apply for Worker and Alternative Trade Adjustment Assistance, </DOC>
                    <PGS>66328-66330</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27701</FRDOCBP>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27705</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Investigations Regarding Certifications of Eligibility to Apply for Worker and Alternative Trade Ajustment Assistance, </DOC>
                    <PGS>66331-66332</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27700</FRDOCBP>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27704</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>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Wind and Water Power Program, </SJDOC>
                    <PGS>66284</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27682</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Environmental Protection</EAR>
            <HD>Environmental Protection Agency</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Exemptions from the Requirement of a Tolerance:</SJ>
                <SJDENT>
                    <SJDOC>Bacteriophage of Clavibacter Michiganensis Subspecies Michiganensis, </SJDOC>
                    <PGS>66187-66192</PGS>
                    <FRDOCBP T="26OCR1.sgm" D="5">2011-27042</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <PRTPAGE P="iv"/>
                <HD>NOTICES</HD>
                <SJ>Clean Air Act Operating Permit Program:</SJ>
                <SJDENT>
                    <SJDOC>Petition for Objection to State Operating Permit for Public Service Co. of Colorado dba Xcel Energy - Cherokee Power Station, </SJDOC>
                    <PGS>66286</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27734</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Petition for Objection to State Operating Permit for Public Service Co. of Colorado dba Xcel Energy - Valmont Power Station, </SJDOC>
                    <PGS>66285-66286</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27725</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Final 2010 Effluent Guidelines Program Plan, </DOC>
                    <PGS>66286-66304</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="18">2011-27742</FRDOCBP>
                </DOCENT>
            </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>Federal Aviation</EAR>
            <HD>Federal Aviation Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Revision of Class E Airspace:</SJ>
                <SJDENT>
                    <SJDOC>Umiat, AK, </SJDOC>
                    <PGS>66178-66179</PGS>
                    <FRDOCBP T="26OCR1.sgm" D="1">2011-27366</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures, </DOC>
                    <PGS>66179-66181</PGS>
                    <FRDOCBP T="26OCR1.sgm" D="2">2011-27371</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Airworthiness Directives:</SJ>
                <SJDENT>
                    <SJDOC>Boeing Co. Airplanes, </SJDOC>
                    <PGS>66200-66203</PGS>
                    <FRDOCBP T="26OCP1.sgm" D="3">2011-27652</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Bombardier, Inc. Model BD 700 1A10 and BD 700 1A11 Airplanes, </SJDOC>
                    <PGS>66198-66200</PGS>
                    <FRDOCBP T="26OCP1.sgm" D="2">2011-27650</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Bombardier, Inc. Model CL 600 2B16 (CL 601 3A, CL 601 3R, and CL 604 Variants) Airplanes, </SJDOC>
                    <PGS>66203-66205</PGS>
                    <FRDOCBP T="26OCP1.sgm" D="2">2011-27653</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Sikorsky Aircraft Corp. Model S-76A Helicopters, </SJDOC>
                    <PGS>66205-66207</PGS>
                    <FRDOCBP T="26OCP1.sgm" D="2">2011-27659</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Sikorsky Aircraft Corp. Model S-92A Helicopters, </SJDOC>
                    <PGS>66207-66211</PGS>
                    <FRDOCBP T="26OCP1.sgm" D="2">2011-27669</FRDOCBP>
                    <FRDOCBP T="26OCP1.sgm" D="2">2011-27670</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Aviation Insurance, </SJDOC>
                    <PGS>66348</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27710</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>FAA Airport Master Record, </SJDOC>
                    <PGS>66348-66349</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27709</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Financial Responsibility for Licensed Launch Activities, </SJDOC>
                    <PGS>66349-66350</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27711</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>General Aviation and Air Taxi Activity and Avionics Survey, </SJDOC>
                    <PGS>66346-66347</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27628</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Hazardous Materials Training Requirements, </SJDOC>
                    <PGS>66347-66348</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27713</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Organization Designation Authorization, </SJDOC>
                    <PGS>66346</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27712</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Training and Qualification Requirements for Check Airmen and Flight Instructors, </SJDOC>
                    <PGS>66349</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27632</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Type Certification Procedures for Changed Products, </SJDOC>
                    <PGS>66347</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27635</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>RTCA Special Committee 205-EUROCAE WG-71; Software Considerations in Aeronautical Systems, </SJDOC>
                    <PGS>66350</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27708</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>RTCA Special Committee 222 Inmarsat Aeronautical Mobile Satellite (Route) Services, </SJDOC>
                    <PGS>66350-66351</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27707</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Petitions for Exemptions; Summaries of Petitions Received, </DOC>
                    <PGS>66351-66352</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27735</FRDOCBP>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27738</FRDOCBP>
                </DOCENT>
                <SJ>Requests to Release Airport Property:</SJ>
                <SJDENT>
                    <SJDOC>Halifax County Airport (RZZ), Roanoke Rapids, NC, </SJDOC>
                    <PGS>66352</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27634</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Bureau</EAR>
            <HD>Federal Bureau of Investigation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>66325-66326</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27605</FRDOCBP>
                </DOCENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Council for the National Crime Prevention and Privacy Compact, </SJDOC>
                    <PGS>66326</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27546</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Communications</EAR>
            <HD>Federal Communications Commission</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Television Broadcasting Services:</SJ>
                <SJDENT>
                    <SJDOC>Cleveland, OH, </SJDOC>
                    <PGS>66250</PGS>
                    <FRDOCBP T="26OCP1.sgm" D="0">2011-27592</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Energy</EAR>
            <HD>Federal Energy Regulatory Commission</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Automatic Underfrequency Load Shedding and Load Shedding Plans Reliability Standards, </DOC>
                    <PGS>66220-66229</PGS>
                    <FRDOCBP T="26OCP1.sgm" D="9">2011-27625</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Enhancement of Electricity Market Surveillance and Analysis, etc., </DOC>
                    <PGS>66211-66220</PGS>
                    <FRDOCBP T="26OCP1.sgm" D="9">2011-27626</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Transmission Planning Reliability Standards, </DOC>
                    <PGS>66229-66235</PGS>
                    <FRDOCBP T="26OCP1.sgm" D="6">2011-27624</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Combined Filings, </DOC>
                    <PGS>66284-66285</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27623</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Maritime</EAR>
            <HD>Federal Maritime Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agreements Filed, </DOC>
                    <PGS>66304</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27706</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Motor</EAR>
            <HD>Federal Motor Carrier Safety Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Unified Registration System, </DOC>
                    <PGS>66506-66595</PGS>
                    <FRDOCBP T="26OCP3.sgm" D="89">2011-26958</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>66304</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27675</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Retirement</EAR>
            <HD>Federal Retirement Thrift Investment Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>66304-66305</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27886</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Fiscal</EAR>
            <HD>Fiscal Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Surety Companies Acceptable on Federal Bonds:</SJ>
                <SJDENT>
                    <SJDOC>Western National Mutual Insurance Co., </SJDOC>
                    <PGS>66361</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27539</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Fish</EAR>
            <HD>Fish and Wildlife Service</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Endangered and Threatened Wildlife and Plants:</SJ>
                <SJDENT>
                    <SJDOC>90-Day Finding on Petition to Delist the Coastal California Gnatcatcher, </SJDOC>
                    <PGS>66255-66260</PGS>
                    <FRDOCBP T="26OCP1.sgm" D="5">2011-27644</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Designation of Critical Habitat for Lepidium papilliferum (Slickspot Peppergrass), </SJDOC>
                    <PGS>66250-66255</PGS>
                    <FRDOCBP T="26OCP1.sgm" D="5">2011-27727</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Review of Native Species That Are Candidates for Listing; Annual Notice of Findings on Resubmitted Petitions, etc., </SJDOC>
                    <PGS>66370-66439</PGS>
                    <FRDOCBP T="26OCP2.sgm" D="69">2011-27122</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental Assessments; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Proposed Establishment of Everglades Headwaters National Wildlife Refuge and Conservation Area, </SJDOC>
                    <PGS>66321</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27748</FRDOCBP>
                </SJDENT>
                <SJ>Long Range Transportation Plans for Fish and Wildlife Service Lands:</SJ>
                <SJDENT>
                    <SJDOC>HI, IA, Northern NV, OR, WA, and Pacific Island Territories; Correction, </SJDOC>
                    <PGS>66321</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27666</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Food and Drug</EAR>
            <HD>Food and Drug Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Bar Code Technologies for Drugs and Biological Products:</SJ>
                <SJDENT>
                    <SJDOC>Retrospective Review Under Executive Order 13563, </SJDOC>
                    <PGS>66235-66238</PGS>
                    <FRDOCBP T="26OCP1.sgm" D="3">2011-27657</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Draft Documents to Support Submission of an Electronic Common Technical Document; Availability, </DOC>
                    <PGS>66311</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27658</FRDOCBP>
                </DOCENT>
                <SJ>Pilot Program for Parallel Review of Medical Products:</SJ>
                <SJDENT>
                    <SJDOC>Correction, </SJDOC>
                    <PGS>66309</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27694</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Health and Human</EAR>
            <PRTPAGE P="v"/>
            <HD>Health and Human Services Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Agency for Healthcare Research and Quality</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Centers for Disease Control and Prevention</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Centers for Medicare &amp; Medicaid Services</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Children and Families Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Food and Drug Administration</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>66305-66306</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27730</FRDOCBP>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27733</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Requirements and Registration for Leading Health Indicators App Challenge, </DOC>
                    <PGS>66306-66307</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27681</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Historic</EAR>
            <HD>Historic Preservation, Advisory Council</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Quarterly Business, </SJDOC>
                    <PGS>66311-66312</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27533</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Homeland</EAR>
            <HD>Homeland Security Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Coast Guard</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>66312-66313</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27636</FRDOCBP>
                </DOCENT>
            </CAT>
        </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>Energy Efficient Mortgages, </SJDOC>
                    <PGS>66317</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27664</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Family Unification Program, </SJDOC>
                    <PGS>66315-66316</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27683</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Management Reviews of Multifamily Housing Programs, </SJDOC>
                    <PGS>66317-66318</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27660</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Multifamily Insurance Benefits Claims Package, </SJDOC>
                    <PGS>66316-66317</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27662</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Single Family Mortgage Instruments, </SJDOC>
                    <PGS>66314-66315</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27667</FRDOCBP>
                </SJDENT>
                <SJ>Funding Awards, Fiscal Year 2010/2011:</SJ>
                <SJDENT>
                    <SJDOC>Limited English Proficiency Initiative Program, </SJDOC>
                    <PGS>66318-66319</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27668</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Operating Cost Adjustment Factors for 2012, </DOC>
                    <PGS>66319-66320</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27816</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Industry</EAR>
            <HD>Industry and Security Bureau</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Commerce Control List:</SJ>
                <SJDENT>
                    <SJDOC>CFR Correction, </SJDOC>
                    <PGS>66181</PGS>
                    <FRDOCBP T="26OCR1.sgm" D="0">2011-27751</FRDOCBP>
                    <FRDOCBP T="26OCR1.sgm" D="0">2011-27753</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>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Park Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Surface Mining Reclamation and Enforcement Office</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Internal Revenue</EAR>
            <HD>Internal Revenue Service</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Disregarded Entities; Excise Taxes and Employment Taxes, </DOC>
                    <PGS>66181-66183</PGS>
                    <FRDOCBP T="26OCR1.sgm" D="2">2011-27720</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Quarterly Publication of Individuals Who have Chosen to Expatriate, </DOC>
                    <PGS>66361-66367</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="6">2011-27570</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International Trade Adm</EAR>
            <HD>International Trade Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Antidumping Duty Administrative Reviews; Results, Amendments, Extensions, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Stainless Steel Plate in Coils from Belgium, </SJDOC>
                    <PGS>66271-66273</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="2">2011-27749</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Justice Department</EAR>
            <HD>Justice Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Antitrust Division</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Bureau of Investigation</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Labor Department</EAR>
            <HD>Labor Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Employment and Training Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Labor-Management Standards Office</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Well-Being Supplement to the American Time Use Survey, </SJDOC>
                    <PGS>66326-66327</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27699</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Labor Management Standards</EAR>
            <HD>Labor-Management Standards Office</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Labor Organization Officer and Employee Reports, </DOC>
                      
                    <PGS>66442-66504</PGS>
                      
                    <FRDOCBP T="26OCR2.sgm" D="62">2011-26816</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Land</EAR>
            <HD>Land Management Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Filing of Plats of Survey:</SJ>
                <SJDENT>
                    <SJDOC>Idaho, </SJDOC>
                    <PGS>66322</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27665</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Oregon/Washington, </SJDOC>
                    <PGS>66322-66323</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27649</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>66352-66353</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27656</FRDOCBP>
                </DOCENT>
                <SJ>Grant of Petitions for Decision of Inconsequential Noncompliance:</SJ>
                <SJDENT>
                    <SJDOC>Tireco, Inc., </SJDOC>
                    <PGS>66353-66354</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27651</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Oceanic</EAR>
            <HD>National Oceanic and Atmospheric Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Fisheries of the Exclusive Economic Zone Off Alaska:</SJ>
                <SJDENT>
                    <SJDOC>Pacific Cod by Catcher/Processors Using Pot Gear in the Bering Sea and Aleutian Islands Management Area, </SJDOC>
                    <PGS>66195-66196</PGS>
                    <FRDOCBP T="26OCR1.sgm" D="1">2011-27714</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Pacific Cod by Vessels Harvesting Pacific Cod for Processing by the Inshore Component in the Western Regulatory Area of the Gulf of Alaska, </SJDOC>
                    <PGS>66196-66197</PGS>
                    <FRDOCBP T="26OCR1.sgm" D="1">2011-27715</FRDOCBP>
                </SJDENT>
                <SJ>Fisheries of the Northeastern United States:</SJ>
                <SJDENT>
                    <SJDOC>Monkfish; Framework Adjustment 7, </SJDOC>
                    <PGS>66192-66195</PGS>
                    <FRDOCBP T="26OCR1.sgm" D="3">2011-27723</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Fisheries of the Northeastern United States:</SJ>
                <SJDENT>
                    <SJDOC>Atlantic Mackerel, Squid, and Butterfish Fisheries; Specifications and Management Measures, </SJDOC>
                    <PGS>66260-66268</PGS>
                    <FRDOCBP T="26OCP1.sgm" D="8">2011-27726</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ> Applications for Exempted Fishing Permits:</SJ>
                <SJDENT>
                    <SJDOC>Snapper-Grouper Fishery off the Southern Atlantic States and Coral and Coral Reefs Fishery in the South Atlantic, </SJDOC>
                    <PGS>66273-66274</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27745</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>North Pacific Fishery Management Council, </SJDOC>
                    <PGS>66274</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27630</FRDOCBP>
                </SJDENT>
                <SJ>Requests for Applications:</SJ>
                <SJDENT>
                    <SJDOC>Cordell Bank National Marine Sanctuary Advisory Council, </SJDOC>
                    <PGS>66274</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27584</FRDOCBP>
                </SJDENT>
                <SJ>Small Takes of Marine Mammals Incidental to Specified Activities:</SJ>
                <SJDENT>
                    <SJDOC>Pier 36/Brannan Street Wharf Project, San Francisco Bay, CA, </SJDOC>
                    <PGS>66274-66281</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="7">2011-27739</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Park</EAR>
            <HD>National Park Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>National Register of Historic Places:</SJ>
                <SJDENT>
                    <SJDOC>Pending Nominations and Related Actions, </SJDOC>
                    <PGS>66323</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27640</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Navy</EAR>
            <HD>Navy Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Intent to Grant Partially Exclusive Patent Licenses:</SJ>
                <SJDENT>
                    <SJDOC>BOLD Industries, Inc., </SJDOC>
                    <PGS>66283</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27661</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Nuclear Regulatory</EAR>
            <PRTPAGE P="vi"/>
            <HD>Nuclear Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Applications for Amendments to Facility Operating Licenses; Withdrawals:</SJ>
                <SJDENT>
                    <SJDOC>Florida Power Corp., </SJDOC>
                    <PGS>66332</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27689</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Appointments to Performance Review Boards for Senior Executive Service, </DOC>
                    <PGS>66332-66333</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27688</FRDOCBP>
                </DOCENT>
                <SJ>Environmental Assessments; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>H. B. Robinson Steam Electric Plant, Unit No. 2, </SJDOC>
                    <PGS>66333-66334</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27691</FRDOCBP>
                </SJDENT>
                <SJ>Environmental Assessments; Availibity, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Proposed License Renewal for Nuclear Fuel Services, Inc. in Erwin, TN, </SJDOC>
                    <PGS>66334-66336</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="2">2011-27685</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR/>
            <HD>Office of Advocacy and Outreach</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Office of Advocacy and Outreach Federal Financial Assistance Programs, </DOC>
                    <PGS>66169-66178</PGS>
                    <FRDOCBP T="26OCR1.sgm" D="9">2011-27108</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Postal Regulatory</EAR>
            <HD>Postal Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Post Office Closings, </DOC>
                    <PGS>66336-66339</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27646</FRDOCBP>
                    <FRDOCBP T="26OCN1.sgm" D="2">2011-27648</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Postal Service</EAR>
            <HD>Postal Service</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Organization and Administration; Establishment, Classification, and Discontinuance, </DOC>
                    <PGS>66184-66187</PGS>
                    <FRDOCBP T="26OCR1.sgm" D="3">2011-27641</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Presidential Documents</EAR>
            <HD>Presidential Documents</HD>
            <CAT>
                <HD>ADMINISTRATIVE ORDERS</HD>
                <DOCENT>
                    <DOC>Congo, Democratic Republic of the; Continuation of National Emergency (Notice of October 25, 2011), </DOC>
                    <PGS>66597-66599</PGS>
                    <FRDOCBP T="26OCO0.sgm" D="2">2011-27922</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Public Debt</EAR>
            <HD>Public Debt Bureau</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Fiscal Service</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Rural Utilities</EAR>
            <HD>Rural Utilities Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>66270-66271</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27642</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Securities</EAR>
            <HD>Securities and Exchange Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Inaugural Roundtable of the Financial Reporting Series:</SJ>
                <SJDENT>
                    <SJDOC>Uncertainty in Financial Statements; How Much to Recognize and How Best to Communicate It, </SJDOC>
                    <PGS>66339</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27696</FRDOCBP>
                </SJDENT>
                <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
                <SJDENT>
                    <SJDOC>Financial Industry Regulatory Authority, Inc., </SJDOC>
                    <PGS>66344-66345</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27697</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>NYSE Arca, Inc, </SJDOC>
                    <PGS>66339-66344</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="5">2011-27698</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>State Department</EAR>
            <HD>State Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>U.S. Advisory Commission on Public Diplomacy, </SJDOC>
                    <PGS>66345-66346</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27732</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Surface Mining</EAR>
            <HD>Surface Mining Reclamation and Enforcement Office</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>66323-66324</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27401</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Surface Transportation</EAR>
            <HD>Surface Transportation Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Construction and Operation Exemptions:</SJ>
                <SJDENT>
                    <SJDOC>DesertXpress Enterprises, LLC and DesertXpress HSR Corp., Victorville, CA, and Las Vegas, NV, </SJDOC>
                    <PGS>66354-66355</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="1">2011-27679</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 Motor Carrier Safety Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Highway Traffic Safety Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Surface Transportation Board</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Treasury</EAR>
            <HD>Treasury Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Fiscal Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Internal Revenue Service</P>
            </SEE>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Effect of Election on Corporation:</SJ>
                <SJDENT>
                    <SJDOC>Withdrawal, </SJDOC>
                    <PGS>66239</PGS>
                    <FRDOCBP T="26OCP1.sgm" D="0">2011-27631</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>66355-66361</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="6">2011-27671</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Veteran Affairs</EAR>
            <HD>Veterans Affairs Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Joint Biomedical Laboratory Research and Development and Clinical Science Research and Development Services Scientific Merit Review Board, </SJDOC>
                    <PGS>66367</PGS>
                    <FRDOCBP T="26OCN1.sgm" D="0">2011-27717</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <PTS>
            <HD SOURCE="HED">Separate Parts In This Issue</HD>
            <HD>Part II</HD>
            <DOCENT>
                <DOC>Interior Department, Fish and Wildlife Service, </DOC>
                <PGS>66370-66439</PGS>
                <FRDOCBP T="26OCP2.sgm" D="69">2011-27122</FRDOCBP>
            </DOCENT>
            <HD>Part III</HD>
            <DOCENT>
                <DOC>Labor Department, Labor-Management Standards Office, </DOC>
                  
                <PGS>66442-66504</PGS>
                  
                <FRDOCBP T="26OCR2.sgm" D="62">2011-26816</FRDOCBP>
            </DOCENT>
            <HD>Part IV</HD>
            <DOCENT>
                <DOC>Transportation Department, Federal Motor Carrier Safety Administration, </DOC>
                <PGS>66506-66595</PGS>
                <FRDOCBP T="26OCP3.sgm" D="89">2011-26958</FRDOCBP>
            </DOCENT>
            <HD>Part V</HD>
            <DOCENT>
                <DOC>Presidential Documents, </DOC>
                <PGS>66597-66599</PGS>
                <FRDOCBP T="26OCO0.sgm" D="2">2011-27922</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>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>207</NO>
    <DATE>Wednesday, October 26, 2011</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <RULES>
        <RULE>
            <PREAMB>
                <PRTPAGE P="66169"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Office of Advocacy and Outreach </SUBAGY>
                <CFR>7 CFR Chapter XXV </CFR>
                <RIN>RIN 0503-ZA01 </RIN>
                <SUBJECT>Office of Advocacy and Outreach Federal Financial Assistance Programs </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Advocacy and Outreach, USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Interim rule with request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This interim rule establishes the regulations for the administrative provisions of all grants or cooperative agreements to be administered by the Office of Advocacy and Outreach (OAO), established by the Food, Conservation, and Energy Act of 2008, (FCEA). Additionally, this interim rule establishes substantive regulations for the Outreach and Assistance for Socially Disadvantaged Farmers and Ranchers Program (OASDFR Program), established by the Food, Agriculture, Conservation and Trade Act of 1990 (FACT Act). It sets forth the criteria to deliver outreach and technical assistance in a linguistically appropriate manner to socially disadvantaged farmers, ranchers and forest landowners to acquire, own, operate, and retain farms, ranches and non-industrial forest land. In addition, it assures farmers and ranchers who are members of socially disadvantaged groups equitable participation in the full range of agriculture programs offered by the Department. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This interim rule becomes effective on: October 26, 2011. OAO requests to receive comments on or before: December 27, 2011. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by RIN 0503-ZA01, 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">E—Mail: Asher.Weinberg@osec.usda.gov.</E>
                         Include RIN 0503-ZA01 in the subject line of the message. 
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         202-720-7136. Include RIN 0503-ZA01 in the subject line of the message. 
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         paper, disk, or CD-ROM submissions should be submitted to: Office of Advocacy and Outreach, U.S. Department of Agriculture, Attn: Asher Weinberg RIN 0503-ZA01, 1400 Independence Avenue, Room 520-A, Stop 9801, Washington, DC 20250-9821 
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery/Courier:</E>
                         Office of Advocacy and Outreach, U.S. Department of Agriculture, Attn: Asher Weinberg RIN 0503-ZA01, 1400 Independence Avenue, Room 520-A, Washington, DC 20250-9821 
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and RIN for this rulemaking. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Asher Weinberg, Grants Program Manager, OASDFR Program, at (202) 720-3112. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION: </HD>
                <HD SOURCE="HD1">I. Introduction </HD>
                <P>The FCEA amended the Department of Agriculture Reorganization Act of 1994, to establish OAO. In addition, the FCEA amended Section 2501(a) of the FACT Act, to transfer the OASDFR Program to OAO and to authorize mandatory funding for this program for Fiscal Year (FY) 2009 through FY 2012. The purpose of this rulemaking is to establish general regulations governing awards management procedures for all OAO award programs. This rulemaking will also establish specific regulations governing the OASDFR Program awards management procedures. </P>
                <HD SOURCE="HD1">II. Administration Requirements </HD>
                <HD SOURCE="HD2">Executive Orders 12866 &amp; 13563 </HD>
                <P>This action has been determined not significant for the purposes of Executive Orders 12866 and 13563, and therefore, has not been reviewed by the Office of Management and Budget. This interim rule will not create a serious inconsistency or otherwise interfere with an action taken or planned by another agency. It will not materially alter the budgetary impact of entitlements, grants, user fees, or loan programs. It will not have an annual effect on the economy of $100 million or more, nor will it adversely affect the economy, a sector of the economy, productivity, competition, jobs, the environment, public health or safety, or State, local, or tribal governments or communities in a material way. Furthermore, it does not raise a novel legal or policy issue arising out of legal mandates, the President's priorities or principles set forth in the Executive Order. </P>
                <HD SOURCE="HD2">Regulatory Flexibility Act of 1980</HD>
                <P>This interim rule has been reviewed in accordance with the Regulatory Flexibility Act of 1980, as amended by the Small Business Regulatory Enforcement Fairness Act of 1996, 5 U.S.C. 601-612. The Department concluded that the rule will not have a significant economic impact on a substantial number of small entities. The rule does not involve regulatory and informational requirements regarding businesses, organizations, and governmental jurisdictions subject to regulation. </P>
                <HD SOURCE="HD2">Paperwork Reduction Act (PRA) </HD>
                <P>
                    The Department certifies that this interim rule has been assessed in accordance with the requirements of the Paperwork Reduction Act, 44 U.S.C. 2501 
                    <E T="03">et seq.,</E>
                     (PRA). The Department concludes that this interim rule does not impose any new information requirements. 
                </P>
                <HD SOURCE="HD2">Catalog of Federal Domestic Assistance </HD>
                <P>This interim regulation applies to Federal assistance programs administered by OAO, including 10.443, Outreach and Assistance for Socially Disadvantaged Farmers and Ranchers and 10.465, Farmworker Training Grants. </P>
                <HD SOURCE="HD2">Unfunded Mandates Reform Act of 1995 and Executive Order 13132 </HD>
                <P>
                    The Department has reviewed this interim rule in accordance with the requirements of Executive Order No. 13132 and the Unfunded Mandates Reform Act of 1995, 2 U.S.C. 1501 
                    <E T="03">et seq.,</E>
                     and has found no potential or substantial direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. As there is no 
                    <PRTPAGE P="66170"/>
                    Federal mandate contained herein that could result in increased expenditures by State, local, or tribal governments or by the private sector, the Department has not prepared a budgetary impact statement. 
                </P>
                <HD SOURCE="HD2">Executive Order 13175: Consultation and Coordination With Indian Tribal Governments </HD>
                <P>The Department has reviewed this interim rule in accordance with Executive Order 13175 and has determined that it does not have “tribal implications.” The interim rule does not “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 responsibility between the Federal government and Indian tribes.” </P>
                <HD SOURCE="HD1">III. Statutory Authority </HD>
                <P>Section 14013 of the FCEA establishes OAO. This section specifies the establishment and transfer of programs to OAO, including the Socially Disadvantaged Farmers Group, the Small Farms and Beginning Farmers and Ranchers Group, the Farmworker Coordinator, and other programs as determined by the Secretary. In addition, Section 14004 amended Section 2501(a) of the FACT Act to clarify the Secretary's authority to engage in grants and other agreements to provide outreach and assistance for socially disadvantaged farmers and ranchers. Previously, the OASDFR Program (also known as 2501 Program) was administered by the National Institute of Food and Agriculture (NIFA). Section 14013 of the FCEA added Section 226B to the Department of Agriculture Reorganization Act of 1994 to transfer the OASDFR Program to OAO. The OASDFR Program provides outreach and technical assistance in a linguistically appropriate manner to encourage and assist current and prospective socially disadvantaged farmers, ranchers, and forest landowners in (1) owning and operating farms, ranches, and non-industrial forest lands; and (2) in participating equitably in the full range of agricultural programs offered by the Department. </P>
                <HD SOURCE="HD1">IV. Section-by-Section Analysis </HD>
                <P>This interim rule will identify OAO awards management procedures for all competitive and noncompetitive award programs administered within OAO. General OAO awards management procedures are discussed in part 2500 subparts A, B, C, D and E. Part 2500 subpart F of this regulation provides program-specific procedures for the OASDFR Program. </P>
                <HD SOURCE="HD2">Part 2500—OAO Federal Financial Assistance Programs—General Award Administrative Procedures </HD>
                <HD SOURCE="HD2">A. Subpart A—General Information </HD>
                <P>The purpose of this subpart is to establish the definitions and statutes and regulations applicable to this part </P>
                <HD SOURCE="HD2">B. Subpart B—Pre-Award: Solicitation and Proposal </HD>
                <P>The purpose of this subpart is to establish the solicitation criteria through a Request for Proposals (RFP). This subpart also identifies the type of proposals to be submitted and OAO eligibility requirements. </P>
                <HD SOURCE="HD2">C. Subpart C—Pre-Award: Proposal Review and Evaluation </HD>
                <P>The purpose of this subpart is to establish the requirements for reviewing, evaluating and selecting proposals. This subpart also establishes the OAO “Applicant Feedback” process. </P>
                <HD SOURCE="HD2">D. Subpart D—Award </HD>
                <P>The purpose of this subpart is to identify the OAO administrative processes for spending program funds. This subpart also establishes the OAO award agreement which defines the terms and conditions of the award. </P>
                <HD SOURCE="HD2">E. Subpart E—Post-Award and Closeout </HD>
                <P>The purpose of this subpart is to establish the OAO post-award and closeout requirements. Subsequently, this subpart also establishes the OAO regulations in regard to cost-sharing and matching, indirect cost, program income, and financial and technical reporting. </P>
                <HD SOURCE="HD2">F. Subpart F—Outreach and Assistance for Socially Disadvantaged Farmers and Ranchers Program </HD>
                <P>The purpose of this subpart is to establish the program-specific grants and cooperative agreements management procedures for the OASDFR Program. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 7 CFR Part 2500 </HD>
                    <P>Farmers, Federal aid programs, Grants administration, Grant programs—agriculture, Ranchers, Socially disadvantaged groups.</P>
                </LSTSUB>
                <P>For the reasons discussed in the preamble, the Office of Advocacy and Outreach, Departmental Management adds chapter XXV, consisting of part 2500, to Title 7 of the Code of Federal Regulations to read as follows: </P>
                <REGTEXT TITLE="7" PART="2500">
                    <CHAPTER>
                        <HD SOURCE="HED">Chapter XXV—Office of Advocacy and Outreach </HD>
                        <PART>
                            <HD SOURCE="HED">PART 2500—OAO FEDERAL FINANCIAL ASSISTANCE PROGRAMS—GENERAL AWARD ADMINISTRATIVE PROCEDURES </HD>
                            <CONTENTS>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart A—General Information </HD>
                                    <SECHD>Sec. </SECHD>
                                    <SECTNO>2500.001</SECTNO>
                                    <SUBJECT>Applicability of regulations. </SUBJECT>
                                    <SECTNO>2500.002</SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <SECTNO>2500.003</SECTNO>
                                    <SUBJECT>Other applicable statutes and regulations. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart B—Pre-Award: Solicitation and Proposals </HD>
                                    <SECTNO>2500.011</SECTNO>
                                    <SUBJECT>Competition. </SUBJECT>
                                    <SECTNO>2500.012</SECTNO>
                                    <SUBJECT>Requests for proposals. </SUBJECT>
                                    <SECTNO>2500.013</SECTNO>
                                    <SUBJECT>Types of proposals. </SUBJECT>
                                    <SECTNO>2500.014</SECTNO>
                                    <SUBJECT>Eligibility requirements. </SUBJECT>
                                    <SECTNO>2500.015</SECTNO>
                                    <SUBJECT>Content of a proposal. </SUBJECT>
                                    <SECTNO>2500.016</SECTNO>
                                    <SUBJECT>Submission of a proposal. </SUBJECT>
                                    <SECTNO>2500.017</SECTNO>
                                    <SUBJECT>Confidentiality of proposals and awards. </SUBJECT>
                                    <SECTNO>2500.018</SECTNO>
                                    <SUBJECT>Electronic submission. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart C—Pre-Award: Proposal Review and Evaluation </HD>
                                    <SECTNO>2500.021</SECTNO>
                                    <SUBJECT>Guiding principles. </SUBJECT>
                                    <SECTNO>2500.022</SECTNO>
                                    <SUBJECT>Preliminary proposal review. </SUBJECT>
                                    <SECTNO>2500.023</SECTNO>
                                    <SUBJECT>Selection of reviewers. </SUBJECT>
                                    <SECTNO>2500.024</SECTNO>
                                    <SUBJECT>Evaluation criteria. </SUBJECT>
                                    <SECTNO>2500.025</SECTNO>
                                    <SUBJECT>Procedures to minimize or eliminate duplication of effort. </SUBJECT>
                                    <SECTNO>2500.026</SECTNO>
                                    <SUBJECT>Applicant feedback. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart D—Award </HD>
                                    <SECTNO>2500.031</SECTNO>
                                    <SUBJECT>Administration. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart E—Post-Award and Closeout </HD>
                                    <SECTNO>2500.041</SECTNO>
                                    <SUBJECT>Payment. </SUBJECT>
                                    <SECTNO>2500.042</SECTNO>
                                    <SUBJECT>Cost sharing and matching. </SUBJECT>
                                    <SECTNO>2500.043</SECTNO>
                                    <SUBJECT>Program income. </SUBJECT>
                                    <SECTNO>2500.044</SECTNO>
                                    <SUBJECT>Indirect costs. </SUBJECT>
                                    <SECTNO>2500.045</SECTNO>
                                    <SUBJECT>Technical reporting. </SUBJECT>
                                    <SECTNO>2500.046</SECTNO>
                                    <SUBJECT>Financial reporting. </SUBJECT>
                                    <SECTNO>2500.047</SECTNO>
                                    <SUBJECT>Project meetings. </SUBJECT>
                                    <SECTNO>2500.048</SECTNO>
                                    <SUBJECT>Review of disallowed costs. </SUBJECT>
                                    <SECTNO>2500.049</SECTNO>
                                    <SUBJECT>Prior approvals. </SUBJECT>
                                    <SECTNO>2500.050</SECTNO>
                                    <SUBJECT>Suspension, termination, and withholding of support. </SUBJECT>
                                    <SECTNO>2500.051</SECTNO>
                                    <SUBJECT>Debt collection. </SUBJECT>
                                    <SECTNO>2500.052</SECTNO>
                                    <SUBJECT>Award appeals procedures. </SUBJECT>
                                    <SECTNO>2500.053</SECTNO>
                                    <SUBJECT>Expiring appropriations. </SUBJECT>
                                    <SECTNO>2500.054</SECTNO>
                                    <SUBJECT>Monitoring scope, purpose, and awardee responsibility. </SUBJECT>
                                    <SECTNO>2500.055</SECTNO>
                                    <SUBJECT>Audit. </SUBJECT>
                                    <SECTNO>2500.056</SECTNO>
                                    <SUBJECT>Civil rights. </SUBJECT>
                                </SUBPART>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart F—Outreach and Assistance for Socially Disadvantaged Farmers and Ranchers Program </HD>
                                    <SECTNO>2500.101</SECTNO>
                                    <SUBJECT>Applicability of regulations. </SUBJECT>
                                    <SECTNO>2500.102</SECTNO>
                                    <SUBJECT>Purpose. </SUBJECT>
                                    <SECTNO>2500.103</SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <SECTNO>2500.104</SECTNO>
                                    <SUBJECT>Eligibility requirements. </SUBJECT>
                                    <SECTNO>2500.105</SECTNO>
                                    <SUBJECT>Project types and priorities. </SUBJECT>
                                    <SECTNO>2500.106</SECTNO>
                                    <SUBJECT>Funding restrictions. </SUBJECT>
                                    <SECTNO>2500.107</SECTNO>
                                    <SUBJECT>Matching. </SUBJECT>
                                    <SECTNO>2500.108</SECTNO>
                                    <SUBJECT>Term of award. </SUBJECT>
                                    <SECTNO>2500.109</SECTNO>
                                    <SUBJECT>Program requirements.</SUBJECT>
                                </SUBPART>
                            </CONTENTS>
                            <AUTH>
                                <HD SOURCE="HED">Authority:</HD>
                                <P> 7 U.S.C. 6934, 7 U.S.C. 2279. </P>
                            </AUTH>
                            <SUBPART>
                                <PRTPAGE P="66171"/>
                                <HD SOURCE="HED">Subpart A—General Information </HD>
                                <SECTION>
                                    <SECTNO>§ 2500.001</SECTNO>
                                    <SUBJECT>Applicability of regulations. </SUBJECT>
                                    <P>The regulations in subparts A through E of this part apply to the programs authorized under section 14013 of the FCEA to be administered within the Office of Advocacy and Outreach (OAO). The purpose of this part is to set forth regulations for competitive and noncompetitive grants, cooperative agreements, and other assistance agreements awarded through OAO. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.002</SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <P>
                                        <E T="03">Applicant</E>
                                         means the entity that has submitted a proposal in response to an OAO Request For Proposal (RFP). 
                                    </P>
                                    <P>
                                        <E T="03">Authorized Departmental Officer (ADO)</E>
                                         means the Secretary or any employee of the Department with delegated authority to issue or modify award instruments on behalf of the Secretary. 
                                    </P>
                                    <P>
                                        <E T="03">Authorized Organizational Representative (AOR)</E>
                                         means the President or Chief Executive Officer of the applicant organization or the official, designated by the President or Chief Executive Officer of the applicant organization, who has the authority to commit the resources of the organization to the project. 
                                    </P>
                                    <P>
                                        <E T="03">Award</E>
                                         means financial assistance that provides support to accomplish a public purpose. Awards may be grants, cooperative agreements, or other assistance agreements. 
                                    </P>
                                    <P>
                                        <E T="03">Award agreement</E>
                                         means the agreement between OAO and the awardee which sets forth the terms and conditions under which the OAO funds will be made available. Award agreement is used as a general term to describe grant agreements, cooperative agreements, and other assistance agreements. 
                                    </P>
                                    <P>
                                        <E T="03">Award closeout</E>
                                         means the process by which the award operation is concluded at the expiration of the award period or following a decision to terminate the award. 
                                    </P>
                                    <P>
                                        <E T="03">Award period</E>
                                         means the timeframe of the award from the beginning date to the ending date as defined in the award agreement. 
                                    </P>
                                    <P>
                                        <E T="03">Awardee</E>
                                         means the entity designated in the grant agreement, cooperative agreement, or other assistance agreement as the legal entity to which the award is given. 
                                    </P>
                                    <P>
                                        <E T="03">Baseline monitoring</E>
                                         is the minimum, basic monitoring that will take place on an ongoing basis throughout the lifetime of every award. 
                                    </P>
                                    <P>
                                        <E T="03">Beginning date</E>
                                         means the date the award agreement is executed by the awardee and OAO and from which costs can be incurred. 
                                    </P>
                                    <P>
                                        <E T="03">Community-based organization</E>
                                         means a nongovernmental organization with a well-defined constituency that includes all or part of a particular community. 
                                    </P>
                                    <P>
                                        <E T="03">Cooperative agreement</E>
                                         means the award of funds to an eligible awardee to assist in meeting the costs of conducting a project which is intended and designed to accomplish the purpose of the program as identified in the RFP, and where substantial involvement is expected between OAO and the awardee when carrying out the activities included in the agreement. This agreement may also be referred to more generally as an award. 
                                    </P>
                                    <P>
                                        <E T="03">Department</E>
                                         means the U.S. Department of Agriculture. 
                                    </P>
                                    <P>
                                        <E T="03">Disallowed costs</E>
                                         means the use of Federal financial assistance funds for unauthorized activities or items as stipulated in the applicable Federal cost principles (2 CFR part 220, 2 CFR part 225, and 2 CFR part 230). 
                                    </P>
                                    <P>
                                        <E T="03">Ending date</E>
                                         means the date the award agreement is scheduled to be completed. It is also the latest date award funds will be provided under the award agreement, without an approved time extension. 
                                    </P>
                                    <P>
                                        <E T="03">Participant</E>
                                         means an individual or entity that participates in awardee-led activities funded under the award agreement. Furthermore, a participant is any individual or entity who has applied for, otherwise participated in, or received a payment, or other benefit as a result of participating in an activity funded by an OAO award. 
                                    </P>
                                    <P>
                                        <E T="03">Partnering</E>
                                         means a joint effort among two or more eligible entities with the capacity to conduct projects intended and designed to accomplish the purpose of the program. 
                                    </P>
                                    <P>
                                        <E T="03">Program leader</E>
                                         means the program supervisor within OAO. 
                                    </P>
                                    <P>
                                        <E T="03">Project</E>
                                         means activities supported under an OAO award. 
                                    </P>
                                    <P>
                                        <E T="03">Project Director (PD)</E>
                                         means the individual designated by the awardee in the proposal and award documentation, and approved by the ADO who is responsible for the direction and management of the award. 
                                    </P>
                                    <P>
                                        <E T="03">Project Officer (PO)</E>
                                         means an individual within OAO who is responsible for the programmatic oversight of the award on behalf of the Department. 
                                    </P>
                                    <P>
                                        <E T="03">Request for Proposals (RFP)</E>
                                         means an official USDA funding opportunity. At OAO discretion, funding opportunities may be referred to as request for proposals, request for applications, notice of funding availability, or funding opportunity. 
                                    </P>
                                    <P>
                                        <E T="03">Review panel</E>
                                         means an evaluation process involving qualified individuals within the relevant field to give advice on the merit of proposals submitted to OAO. 
                                    </P>
                                    <P>
                                        <E T="03">Secretary</E>
                                         means the Secretary of Agriculture and any other officer or employee of the Department of Agriculture to whom authority may be delegated. 
                                    </P>
                                    <P>
                                        <E T="03">Terminate funding</E>
                                         means the cancellation of Federal assistance, in whole or in part, at any time before the ending date. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.003</SECTNO>
                                    <SUBJECT>Other applicable statutes and regulations. </SUBJECT>
                                    <P>Several Federal statutes and regulations apply to proposals for Federal assistance considered for review and to grants and cooperative agreements awarded by OAO. These include, but are not limited to: </P>
                                    <P>(a) 7 CFR Part 1, Subpart A—USDA implementation of the Freedom of Information Act;</P>
                                    <P>(b) 7 CFR Part 3—USDA implementation of OMB Circular No. A-129, regarding debt management;</P>
                                    <P>(c) Title VI of the Civil Rights Act of 1964 (Pub. L. 88-352), as amended, which prohibits discrimination on the basis of race, color, or national origin, and 7 CFR part 15, subpart A (USDA implementation);</P>
                                    <P>(d) 7 CFR Part 3015—USDA Uniform Federal Assistance Regulations, implementing OMB directives and incorporating provisions of the Federal Grant and Cooperative Agreement Act of 1977, Public Law 95-224, 31 U.S.C. § 6301-6308, as well as general policy requirements applicable to awardees of Departmental financial assistance.</P>
                                    <P>(e) 7 CFR Part 3016—USDA implementation of Administrative Requirements for Grants and Cooperative Agreements to State and Local Governments.</P>
                                    <P>(f) 7 CFR Part 3017—USDA implementation of Governmentwide Debarment and Suspension (Nonprocurement).</P>
                                    <P>(g) 7 CFR Part 3018—USDA implementation of Restrictions on Lobbying. Imposes prohibitions and requirements for disclosure and certification related to lobbying on awardees of Federal contracts, grants, cooperative agreements, and loans.</P>
                                    <P>(h) 7 CFR Part 3019—USDA implementation of OMB Circular No. A-110, Uniform Administrative Requirements for Grants and Agreements with Institutions of Higher Education, Hospitals and Other Non-Profit Organizations (now relocated at 2 CFR part 215).</P>
                                    <P>
                                        (i) 7 CFR Part 3021—USDA implementation of Governmentwide Requirements for Drug-Free Workplace (Financial Assistance).
                                        <PRTPAGE P="66172"/>
                                    </P>
                                    <P>(j) 7 CFR Part 3052—USDA implementation of OMB Circular No. A-133, Audits of States, Local Governments, and Non-Profit Organizations.</P>
                                    <P>(k) 7 U.S.C. 3318—conferring upon the Secretary general authority to enter into contracts, grants, and cooperative agreements to further the research, extension, or teaching programs in the food and agricultural sciences of the Department of Agriculture.</P>
                                    <P>(l) 29 U.S.C. 794 (Section 504, Rehabilitation Act of 1973) and 7 CFR part 15b (USDA implementation of statute)—prohibiting discrimination based upon physical or mental handicap in Federally assisted programs.</P>
                                    <P>
                                        (m) 35 U.S.C. 200 
                                        <E T="03">et seq.</E>
                                        —Bayh-Dole Act, promoting the utilization of inventions arising from federally supported research or development; encouraging maximum participation of small business firms in federally supported research and development efforts; and promoting collaboration between commercial concerns and nonprofit organizations, including universities, while ensuring that the Government obtains sufficient rights in federally supported inventions to meet the needs of the Government and protect the public against nonuse or unreasonable use of inventions (implementing regulations are contained in 37 CFR part 401)
                                    </P>
                                    <P>(n) Title IX of the Education Amendment of 1972 (20 U.S.C. 1681-1683 and 1685-1686), as amended, which prohibits discrimination on the basis of sex;</P>
                                    <P>(o) Age Discrimination Act of 1975 (42 U.S.C. 6101-6107), as amended, which prohibits discrimination on the basis of age;</P>
                                    <P>(p) Drug Abuse Office and Treatment Act of 1972 (Pub. L. 92-255), as amended, relating to nondiscrimination on the basis of drug abuse;</P>
                                    <P>(q) Comprehensive Alcohol Abuse and Alcoholism Prevention, Treatment and Rehabilitation Act of 1970 (Pub. L. 91-616), as amended, relating to nondiscrimination on the basis of alcohol abuse or alcoholism;</P>
                                    <P>(r) Sections 523 and 527 of the Public Health Service Act of 1912 (42 U.S.C. 290dd-3 and 290ee-3), as amended, relating to confidentiality of alcohol and drug abuse patient records;</P>
                                    <P>
                                        (s) Title VIII of the Civil Rights Act of 1968 (42 U.S.C. 3601 
                                        <E T="03">et seq.</E>
                                        ), as amended, relating to nondiscrimination in the sale, rental or financing of housing;
                                    </P>
                                    <P>(t) Any other nondiscrimination provisions in the specific statute(s) under which proposals for Federal assistance are made, and the requirements of any other nondiscrimination statute(s) which may apply to the proposal.</P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart B—Pre-Award: Solicitation and Proposals</HD>
                                <SECTION>
                                    <SECTNO>§ 2500.011 </SECTNO>
                                    <SUBJECT>Competition.</SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Standards for competition.</E>
                                         Except as provided in paragraph (b) of this section, OAO will enter into discretionary grants or cooperative agreement only after competition, unless restricted by statute.
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Exception.</E>
                                         The OAO ADO may make a determination in writing that competition is not deemed appropriate for a particular transaction. Such determination shall be limited to transactions where it can be adequately justified that a noncompetitive award is in the best interest of the Federal Government and necessary to the goals of the program. Non-competitive determinations will comply with regulations established in 7 CFR 3015.158(d).
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.012 </SECTNO>
                                    <SUBJECT>Requests for proposals.</SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General.</E>
                                         For each competitive grant or cooperative agreement, OAO will prepare a program solicitation (also called a request for proposals (RFP)). The RFP may include all or a portion of the following items:
                                    </P>
                                    <P>(1) Contact information.</P>
                                    <P>(2) Catalog of Federal Domestic Assistance (CFDA) number.</P>
                                    <P>(3) Legislative authority and background information.</P>
                                    <P>(4) Purpose, priorities, and fund availability.</P>
                                    <P>(5) Program-specific eligibility requirements.</P>
                                    <P>(6) Program-specific restrictions on the use of funds, if applicable.</P>
                                    <P>(7) Matching requirements, if applicable.</P>
                                    <P>(8) Acceptable types of proposals.</P>
                                    <P>(9) Types of projects to be given priority consideration, including maximum anticipated awards and maximum project lengths, if applicable.</P>
                                    <P>(10) Program areas, if applicable.</P>
                                    <P>(11) Funding restrictions, if applicable.</P>
                                    <P>(12) Directions for obtaining additional requests for proposals and proposal forms.</P>
                                    <P>(13) Information about how to obtain proposal forms and the instructions for completing such forms.</P>
                                    <P>(14) Instructions and requirements for submitting proposals, including submission deadline(s).</P>
                                    <P>(15) Explanation of the proposal evaluation process.</P>
                                    <P>(16) Specific evaluation criteria used in the review process.</P>
                                    <P>(17) Type of Federal assistance awards (i.e., grants or cooperative agreements).</P>
                                    <P>
                                        (b) 
                                        <E T="03">RFP variations.</E>
                                         Where program-specific requirements differ from the requirements established in this part, program solicitations will also address any such variation(s). Variations may occur in the following:
                                    </P>
                                    <P>(1) Award management guidelines.</P>
                                    <P>(2) Restrictions on the delegation of fiscal responsibility.</P>
                                    <P>(3) Required approval for changes to project plans.</P>
                                    <P>(4) Expected program outputs and reporting requirements, if applicable.</P>
                                    <P>(5) Applicable Federal statutes and regulations.</P>
                                    <P>(6) Confidential aspects of proposals and awards, if applicable.</P>
                                    <P>(7) Regulatory information.</P>
                                    <P>(8) Definitions.</P>
                                    <P>(9) Minimum and maximum budget requests and whether proposals outside of these limits will be returned without further review.</P>
                                    <P>
                                        (c) 
                                        <E T="03">Program announcements.</E>
                                         Occasionally, OAO will issue a program announcement (PA) to alert potential applicants and the public about new and ongoing funding opportunities. These PAs may provide tentative due dates and are released without associated proposal packages. No proposals are solicited under a PA. PAs will be announced in the 
                                        <E T="04">Federal Register</E>
                                         or on the OAO Web site.
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.013 </SECTNO>
                                    <SUBJECT>Types of proposals.</SUBJECT>
                                    <P>The type of proposal acceptable may vary by funding opportunity. The RFP will stipulate what will be required for submission to OAO in response to the funding opportunity.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.014 </SECTNO>
                                    <SUBJECT>Eligibility requirements.</SUBJECT>
                                    <P>Program-specific eligibility requirements appear in the subpart applicable to each program and in the corresponding RFPs.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.015 </SECTNO>
                                    <SUBJECT>Content of a proposal.</SUBJECT>
                                    <P>
                                        The RFP provides instructions on how to access a funding opportunity. The funding opportunity contains the proposal package, which includes the forms necessary for completion of a proposal in response to the RFP. The RFP will be posted on 
                                        <E T="03">http://www.Grants.gov.</E>
                                         OAO may also publish the RFP in the 
                                        <E T="04">Federal Register</E>
                                        .
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.016 </SECTNO>
                                    <SUBJECT>Submission of a proposal.</SUBJECT>
                                    <P>
                                        The RFP will provide deadlines for the submission of proposals. OAO may issue separate RFPs and/or establish separate deadlines for different types of proposals, different award instruments, or different topics or phases of the 
                                        <PRTPAGE P="66173"/>
                                        assistance programs. If proposals are not received by applicable deadlines, they will not be considered for funding. Exceptions will be considered only when extenuating circumstances exist, as determined by OAO, and justification and supporting documentation are provided by the applicant. Conformance with preparation and submission instructions is required and will be strictly enforced unless a deviation has been approved. OAO may establish additional requirements. OAO may return without review proposals that are not consistent with the RFP instructions.
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.017 </SECTNO>
                                    <SUBJECT>Confidentiality of proposals and awards.</SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General.</E>
                                         Names of entities submitting proposals, as well as proposal contents and evaluations, except to those involved in the review process, will be kept confidential to the extent permissible by law.
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Identifying confidential and proprietary information in a proposal.</E>
                                         If a proposal contains proprietary information that constitutes a trade secret, proprietary commercial or financial information, confidential personal information, or data affecting the national security, it will be treated in confidence to the extent permitted by law, provided that the information is clearly marked by the applicant with the term “confidential and proprietary information.” In addition, the following statement must be included at the bottom of the project narrative or any other attachment included in the proposal that contains such information: “The following pages (specify) contain proprietary information which (name of proposing organization) requests not to be released to persons outside the Government, except for purposes of evaluation.”
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Disposition of proposals.</E>
                                         By law, OAO is required to make the final decisions as to whether the information is required to be kept in confidence. Information contained in unsuccessful proposals will remain the property of the applicant. However, the Department will retain for three years one file copy of each proposal received; extra copies will be destroyed. Public release of information from any proposal submitted will be subject to existing legal requirements. Any proposal that is funded will be considered an integral part of the award and normally will be made available to the public upon request, except for information designated proprietary by OAO.
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Submission of proprietary information.</E>
                                         The inclusion of proprietary information is discouraged unless it is necessary for the proper evaluation of the proposal. If proprietary information is to be included, it should be limited, set apart from other text on a separate page, and keyed to the text by numbers. It should be confined to a few critical technical items that, if disclosed, could jeopardize the obtaining of foreign or domestic patents. Trade secrets, salaries, or other information that could jeopardize commercial competitiveness should be similarly keyed and presented on a separate page. Proposals or reports that attempt to restrict dissemination of large amounts of information may be found unacceptable by OAO and constitute grounds for return of the proposal without further consideration. Without assuming any liability for inadvertent disclosure, OAO will limit dissemination of such information to its employees and, where necessary for the evaluation of the proposal, to outside reviewers on a confidential basis.
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.018 </SECTNO>
                                    <SUBJECT>Electronic submission.</SUBJECT>
                                    <P>Applicants and awardees are encouraged, but not required, to submit proposals and reports in electronic form as prescribed in the RFP issued by OAO and in the applicable award agreement.</P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart C—Pre-Award: Proposal Review and Evaluation</HD>
                                <SECTION>
                                    <SECTNO>§ 2500.021 </SECTNO>
                                    <SUBJECT>Guiding principles.</SUBJECT>
                                    <P>The guiding principle for Federal assistance proposal review and evaluation is to ensure that each proposal is treated in a consistent and fair manner. After the evaluation process by the review panel, OAO will provide an opportunity for applicant feedback in as timely a manner as possible.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.022 </SECTNO>
                                    <SUBJECT>Preliminary proposal review.</SUBJECT>
                                    <P>Prior to technical examination, a preliminary review will be made of all proposals for responsiveness to the administrative requirements set forth in the RFP. Proposals that do not meet the administrative requirements may be eliminated from program competition. However, OAO retains the right to conduct discussions with applicants to resolve technical and/or budget issues, as deemed necessary by OAO.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.023 </SECTNO>
                                    <SUBJECT>Selection of reviewers.</SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Requirement.</E>
                                         OAO is responsible for performing a review of proposals submitted to OAO competitive award programs. The RFP will identify the criteria that OAO will use for the selection of the proposal review panel.
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Confidentiality.</E>
                                         The identities of reviewers will remain confidential to the maximum extent possible. Therefore, the names of reviewers will not be released to applicants. Names of applicants, as well as proposal content and evaluation comments will be kept confidential to the extent permitted by law, except to those involved in the review process. Reviewers will comply with the above-mentioned confidentiality guidelines.
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Conflicts of interest.</E>
                                         During the evaluation process, extreme care will be taken to prevent any actual or perceived conflicts of interest that may impact review or evaluation. Reviewers are expected to be in compliance with the Conflict-of-Interest process made a part of the RFP.
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.024 </SECTNO>
                                    <SUBJECT>Evaluation criteria.</SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General.</E>
                                         To ensure any project receiving funds from OAO is consistent with the broad goals of the funding program, the content of each proposal submitted to OAO will be evaluated based on a pre-determined set of review criteria as indicated in the RFP.
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Guidance for reviewers.</E>
                                         In order that all potential applicants for a program have similar opportunities to compete for funds, all reviewers will receive an orientation from the Program Leader of the review criteria. Reviewers are instructed to use those same evaluation criteria, and only those criteria, to judge the merit of the proposals they review.
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.025 </SECTNO>
                                    <SUBJECT>Procedures to minimize or eliminate duplication of effort.</SUBJECT>
                                    <P>OAO may implement appropriate business processes to minimize or eliminate the awarding of Federal assistance to projects that unnecessarily duplicate activities already being sponsored under other awards, including awards made by other Federal agencies.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.026 </SECTNO>
                                    <SUBJECT>Applicant feedback.</SUBJECT>
                                    <P>Unsuccessful applicants may submit a request for applicant feedback in writing to OAO within 10 days after receiving written notice of not being selected for further processing. Applicant feedback requests are to be mailed to the Program Leader at the address below, unless otherwise stated in the “Notice of Non-Selection” or in the RFP. At OAO's discretion, either written or oral feedback will be provided to unsuccessful applicants.</P>
                                    <P>
                                        U.S. Department of Agriculture, Departmental Management, Office of Advocacy and Outreach, 
                                        <E T="03">Attn:</E>
                                         Program Leader (Applicant Feedback), Whitten Building, Rm. 520-A, stop 9821, 1400 Independence Avenue, SW., Washington, DC 20250-9821.
                                    </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <PRTPAGE P="66174"/>
                                <HD SOURCE="HED">Subpart D—Award</HD>
                                <SECTION>
                                    <SECTNO>§ 2500.031 </SECTNO>
                                    <SUBJECT>Administration.</SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General.</E>
                                         Within the limit of funds available for such purpose, the OAO ADO shall make Federal assistance awards to those responsible, eligible applicants whose proposals are judged most meritorious under the procedures set forth in the RFP. The date specified by the OAO ADO as the effective date of the award shall be no later than September 30th of the Federal fiscal year in which the project is approved for support and funds are appropriated for such purpose, unless otherwise permitted by law. It should be noted that the project need not be initiated on the award effective date, but as soon thereafter as practical so that project goals may be attained within the funded project period. All funds awarded by OAO shall be expended solely for the purpose for which the funds are awarded in accordance with the approved statement of work and budget, the regulations, the terms and conditions of the OAO award agreement, the applicable Federal cost principles, and the Department's assistance regulations (e.g., 7 CFR parts 3015, 3016, and 3019).
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Award agreement.</E>
                                         The award agreement and accompanying terms and conditions will provide pertinent instructions and information including, at a minimum, the following:
                                    </P>
                                    <P>(1) Legal name and address of performing organization or institution to which OAO has awarded a grant or cooperative agreement.</P>
                                    <P>(2) Title of project.</P>
                                    <P>(3) Name(s) of Project Director(s).</P>
                                    <P>(4) Identifying award number assigned by OAO.</P>
                                    <P>(5) Project period.</P>
                                    <P>(6) Total amount of OAO financial assistance approved.</P>
                                    <P>(7) Legal authority under which the grant or cooperative agreement is awarded.</P>
                                    <P>(8) Appropriate CFDA number.</P>
                                    <P>(9) Approved budget plan (that may be referenced).</P>
                                    <P>(10) Terms and Conditions</P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart E—Post-Award and Closeout</HD>
                                <SECTION>
                                    <SECTNO>§ 2500.041 </SECTNO>
                                    <SUBJECT>Payment.</SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General.</E>
                                         All payments will be made in advance unless a deviation is accepted or as specified in paragraph (b) of this section. All payments to the awardee shall be made via the approved electronic funds transfer (EFT) method. Awardees are expected to request funds via the federally-approved electronic payment system for reimbursement in a timely manner. Exact payment method will be described in the terms and conditions of the award agreement.
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Reimbursement method.</E>
                                         OAO shall use the reimbursement method if it determines that advance payment is not feasible or that the awardee does not maintain or demonstrate the willingness to maintain written procedures that minimize the elapse of time between the transfer of funds and disbursement by the awardee, and financial management systems that meet the standards for fund control and accountability.
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.042 </SECTNO>
                                    <SUBJECT>Cost sharing and matching.</SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General.</E>
                                         Awardees may be required to match the Federal funds received under an OAO award. The required percentage of matching, type of matching (e.g., cash and/or in-kind contributions), sources of match (e.g., non-Federal), and whether OAO has any authority to waive the match will be specified in the subpart applicable to the specific Federal assistance program, as well as in the RFP.
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Indirect costs as in-kind matching contributions.</E>
                                         Indirect costs may be claimed under the Federal portion of the award budget. However, unless explicitly authorized in the RFP, indirect costs may not be claimed on both the Federal and nonfederal portion of the award budget.
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.043 </SECTNO>
                                    <SUBJECT>Program income.</SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General.</E>
                                         OAO shall apply the standards set forth in this subpart in requiring awardee organizations to account for program income related to projects financed in whole or in part with Federal funds.
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Addition method.</E>
                                         Unless otherwise provided in the authorizing statute, in accordance with the terms and conditions of the award, program income earned during the project period shall be retained by the awardee and shall be added to funds committed to the project by OAO and the awardee and used to further eligible project or program objectives. Any specific program deviations will be identified in the individual subparts.
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Award terms and conditions.</E>
                                         Unless the program regulations identified in the individual subpart provide otherwise, awardees shall follow the terms and conditions of the OAO award. Such terms and conditions will be made a part of the OAO award agreement.
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.044 </SECTNO>
                                    <SUBJECT>Indirect costs.</SUBJECT>
                                    <P>Indirect cost rates for grants and cooperative agreements shall be determined in accordance with the applicable assistance regulations and cost principles, unless superseded by another authority.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.045 </SECTNO>
                                    <SUBJECT>Technical reporting.</SUBJECT>
                                    <P>All projects supported with Federal funds under this part must be documented according to the terms and conditions of the OAO award agreement.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.046 </SECTNO>
                                    <SUBJECT>Financial reporting.</SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">SF-425, Federal Financial Report.</E>
                                         As stated in the award terms and conditions of the OAO award agreement, a final SF-425, Federal Financial Report, is due 90 days after the expiration of the award and should be submitted to OAO electronically. The awardee shall report program outlays and program income on the same accounting basis (i.e., cash or accrual) that it uses in its normal accounting system. When submitting a final SF-425, Federal Financial Report, the total matching contribution, if required, should be shown in the report. The final SF-425 must not show any unliquidated obligations. If the awardee still has valid obligations that remain unpaid when the report is due, it shall request an extension of time for submitting the report pursuant to paragraph (c) of this section; submit a provisional report (showing the unliquidated obligations) by the due date; and submit a final report when all obligations have been liquidated, but no later than the approved extension date. SF-425, Federal Financial Reports, must be submitted by all awardees, including Federal agencies and national laboratories.
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Awards with required matching.</E>
                                         For awards requiring a matching contribution, an annual SF-425, Federal Financial Report, is required and this requirement will be indicated in the terms and conditions of the OAO award agreement, in which case it must be submitted no later than 45 days following the end of the budget or reporting period.
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">After the due date.</E>
                                         Requests are considered late when they are submitted after the 90-day period following the award expiration date. Requests to submit a late final SF-425, Federal Financial Report, will only be considered, up to 30 days after the due date, in extenuating circumstances. This request should include a provisional report pursuant to paragraph (a) of this section, as well as an anticipated submission date, a justification for the late submission, and a justification for the extenuating circumstances. If an awardee needs to request additional funds, procedures in paragraph (d) of this section apply.
                                        <PRTPAGE P="66175"/>
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Overdue SF-425, Federal Financial Reports.</E>
                                         Awardees with overdue SF-425, Federal Financial Reports, or other required financial reports (as identified in the award terms and conditions), will have their applicable balances in the approved federal electronic funds transfer system restricted or placed on “manual review,” which restricts the awardee's ability to draw funds, thus requiring prior approval from OAO. If any remaining available balances are needed by the awardee (beyond the 90-day period following the award expiration date) and the awardee has not requested an extension to submit a final SF-425, Financial Status Report, the awardee will be required to contact OAO to request permission to draw any additional funds and will be required to provide justification and documentation to support the draw. Awardees also will need to comply with procedures in paragraph (c) of this section. OAO will approve these draw requests only in extenuating circumstances.
                                    </P>
                                    <P>
                                        (e) 
                                        <E T="03">Additional reporting requirements.</E>
                                         OAO may require forecasts of Federal cash requirements in the “Remarks” section of the report; and when practical and deemed necessary, OAO may require awardees to report in the “Remarks” section the amount of cash advances received in excess of three days (i.e., short narrative with explanations of actions taken to reduce the excess balances). When OAO needs additional information or more frequent reports, a special provision will be added to the award terms and conditions and identified in the OAO award agreement. Should OAO determine that an awardee's accounting system is inadequate, additional pertinent information to further monitor awards may be requested from the awardee until such time as the system is brought up to standard, as determined by OAO. This additional reporting requirement will be required via a special provision to the award terms and conditions of the OAO award agreement.
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.047 </SECTNO>
                                    <SUBJECT>Project meetings.</SUBJECT>
                                    <P>In addition to reviewing and monitoring the status of progress and final technical reports and financial reports, OAO Project Officers may use regular and periodic conference calls to monitor the awardee's performance as well as conferences, workshops, meetings, and symposia to not only monitor the awards, but to facilitate communication and the sharing of project results. These opportunities also serve to eliminate or minimize OAO funding of unneeded duplicative project activities. Required attendance at these conference calls, conferences, workshops, meetings, and symposia will be identified in the RFP or award document.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.048 </SECTNO>
                                    <SUBJECT>Review of disallowed costs.</SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Notice.</E>
                                         If the OAO Project Officer (PO) determines that there is a basis for disallowing a cost, OAO shall provide the awardee written notice of its intent to disallow the cost. The written notice shall state the amount of the cost and the factual and legal basis for disallowing it.
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Awardee response.</E>
                                         Within 60 days of receiving written notice of the PO's intent to disallow the cost, the awardee may respond with written evidence and arguments to show the cost is allowable, or that, for equitable, practical, or other reasons, shall not recover all or part of the amount, or that the recovery should be made in installments. An extension of time will be granted only in extenuating circumstances.
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Decision.</E>
                                         Within 60 days of receiving the awardee's written response to the notice of intent to disallow the cost, the PO shall issue a management decision stating whether or not the cost has been disallowed, the reasons for the decision, and the method of appeal that has been provided under this section. If the awardee does not respond to the written notice under paragraph (a) of this section within the time frame specified in paragraph (b) of this section, the PO shall issue a management decision on the basis of the information available to it. The management decision shall constitute the final action with respect to whether the cost is allowed or disallowed. In the case of a questioned cost identified in the context of an audit subject to 7 CFR part 3052, the management decision will constitute the management decision under 7 CFR 3052.405(a).
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Demand for payment.</E>
                                         If the management decision under paragraph (c) of this section constitutes a finding that the cost is disallowed and, therefore, that a debt is owed to the Government, the PO shall provide the required demand and notice pursuant to 7 CFR 3.11.
                                    </P>
                                    <P>
                                        (e) 
                                        <E T="03">Review process.</E>
                                         Within 60 days of receiving the demand and notice referred to in paragraph (d) of this section, the awardee may submit a written request to the OAO Director for a review of the final management decision that the debt exists and the amount of the debt. Within 60 days of receiving the written request for a review, the OAO Director will issue a final decision regarding the debt. A review by the OAO Director or designee constitutes an administrative review for debts under 7 CFR part 3, subpart F.
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.049 </SECTNO>
                                    <SUBJECT>Prior approvals.</SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Subcontracts.</E>
                                         No more than 50 percent of the award may be subcontracted to other parties without prior written approval of the ADO. Any subcontract awarded to a Federal agency under an award must have prior written approval of the ADO. To request approval, a justification for the proposed subcontractual arrangements, a performance statement, and a detailed budget for the subcontract must be submitted to the ADO.
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">No-cost extensions of time—</E>
                                        (1) 
                                        <E T="03">General.</E>
                                         Awardees may initiate a one-time no-cost extension of the expiration date of the award of up to 12 months unless one or more of the following conditions apply: the terms and conditions of the award prohibit the extension; the extension requires additional Federal funds; and the extension involves any change in the approved objectives or scope of the project. For the first no-cost extension, the awardee must notify OAO in writing with the supporting reasons and revised expiration date at least 10 days before the expiration date specified in the award.
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Additional requests for no-cost extensions of time before expiration date.</E>
                                         When more than one no-cost extension of time or an extension of more than 12 months is required, the extension(s) must be approved in writing by the PO. The awardee must submit a written request, which must be received no later than 10 days prior to the expiration date of the award, to the PO. The request must contain, at a minimum, the following information: The length of the additional time required to complete the project objectives and a justification for the extension; a summary of the progress to date; an estimate of the funds expected to remain unobligated on the scheduled expiration date; a projected timetable to complete the portion(s) of the project for which the extension is being requested; and signature of the AOR and the PD.
                                    </P>
                                    <P>
                                        (3) 
                                        <E T="03">Requests for no-cost extensions of time after expiration date.</E>
                                         OAO may consider and approve requests for no-cost extensions of time up to 120 days following the expiration of the award. These will be approved only for extenuating circumstances, as determined by OAO. The awardee's AOR must submit the requirements identified under paragraph (b)(2) of this section as well as an “extenuating circumstance” justification and a description of the actions taken by the 
                                        <PRTPAGE P="66176"/>
                                        awardee to minimize these requests in the future.
                                    </P>
                                    <P>
                                        (4) 
                                        <E T="03">Other requirements.</E>
                                         No-cost extensions of time may not be exercised merely for the purpose of using unobligated balances.
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.050 </SECTNO>
                                    <SUBJECT>Suspension, termination, and withholding of support.</SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General.</E>
                                         If an awardee has failed to materially comply with the terms and conditions of the award, OAO may take certain enforcement actions, including, but not limited to, suspending the award pending corrective action and terminating the award for cause.
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Suspension.</E>
                                         OAO generally will suspend (rather than immediately terminate) an award to allow the awardee an opportunity to take appropriate corrective action before OAO makes a termination decision. OAO may decide to terminate the award if the awardee does not take appropriate corrective action during the period of suspension. OAO may terminate, without first suspending, the award if the deficiency is so serious as to warrant immediate termination. Termination for cause may be appealed under the terms and conditions identified in the OAO award agreement.
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Termination.</E>
                                         An award also may be terminated, partially or wholly, by the awardee or by OAO with the consent of the awardee. If the awardee decides to terminate a portion of the award, OAO may determine that the remaining portion of the award will not accomplish the purposes for which the award was originally made. In any such case, OAO will advise the awardee of the possibility of termination of the entire award and allow the awardee to withdraw its termination request. If the awardee does not withdraw its request for partial termination, OAO may initiate procedures to terminate the entire award for cause.
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.051 </SECTNO>
                                    <SUBJECT>Debt collection.</SUBJECT>
                                    <P>The collection of debts owed to OAO by awardees, including those resulting from cost disallowances, recovery of funds, unobligated balances, or other circumstances, are subject to the Department's debt collection procedures as set forth in 7 CFR part 3, and, with respect to cost disallowances, § 2500.048.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.052 </SECTNO>
                                    <SUBJECT>Award appeals procedures.</SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General.</E>
                                         OAO permits awardees to appeal certain adverse post-award administrative decisions made by OAO. Such adverse decisions include: Termination, in whole or in part, and determination that an award is void. An award may be terminated for failure of the awardee to carry out its approved project in accordance with the applicable law and the terms and conditions of award; or for failure of the awardee otherwise to comply with any law, regulation, assurance, term, or condition applicable to the award. Additionally, an award may be determined to be void if, for example, it was not authorized by statute or regulation or because it was fraudulently obtained. Appeals of determinations regarding the allowability of costs are subject to the procedures in § 2500.048.
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Appeal Procedures.</E>
                                         The formal notification of an adverse determination will contain a statement of the awardee's appeal rights. To appeal an adverse determination, the awardee must submit a request for review to the OAO official specified in the notification, detailing the nature of the disagreement with the adverse determination and providing supporting documents in accordance with the procedures contained in the notification. The awardee's request to OAO for review must be received within 60 days after receipt of the written notification of the adverse determination; however, an extension may be granted if the awardee can show good cause why an extension is warranted. OAO will carefully consider the merits of all requests for appeals and further reviews. However, at the conclusion of the OAO appeal review process, the OAO decision rendered on the appeal is considered final. The awardee will be notified in writing by OAO of final appeal review determinations.
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.053 </SECTNO>
                                    <SUBJECT>Expiring appropriations.</SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">OAO awards supported with office appropriations.</E>
                                         Most OAO awards are supported with annual appropriations. On September 30th of the 5th fiscal year after the period of availability for obligation ends, the funds for these appropriations accounts expire per 31 U.S.C. 1552 and the account is closed, unless otherwise specified by law. Funds that have not been drawn through the approved electronic funds transfer system, by the awardee or disbursed through any other system or method by August 31st of that fiscal year are subject to be returned to the U.S. Department of the Treasury after that date. The August 31st requirement also applies to awards with a 90-day period concluding on a date after August 31st of that fifth year. Appropriations cannot be restored after expiration of the accounts. More specific instructions are provided in the OAO award terms and conditions.
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">OAO awards supported with funds from other Federal agencies (reimbursable funds).</E>
                                         OAO may require that all draws and reimbursements for awards supported with reimbursable funds (from other Federal agencies) be completed prior to June 30th of the 5th fiscal year after the period of availability for obligation ends to allow for the proper billing, collection, and close-out of the associated interagency agreement before the appropriations expire. The June 30th requirement also applies to awards with a 90-day period concluding on a date after June 30th of that fifth year. Appropriations cannot be restored after expiration of the accounts. More specific instructions are provided in the terms and conditions of the OAO award agreement.
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.055 </SECTNO>
                                    <SUBJECT>Audit.</SUBJECT>
                                    <P>Awardees must comply with the audit requirements of 7 CFR part 3052. The audit requirements apply to the years in which Federal financial assistance funds are received and years in which work is accomplished using these funds.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.056 </SECTNO>
                                    <SUBJECT>Civil rights.</SUBJECT>
                                    <P>Awardees must comply with the civil rights requirements of 7 CFR part 15, subpart A—USDA implementation of Title VI of the Civil Rights Act of 1964, as amended. In accordance, no person in the United States shall, on the ground of race, color, or national origin, be excluded from participation in, be denied the benefits of, or be otherwise subjected to discrimination under any program or activity for which the recipient receives Federal financial assistance and will immediately take any measures necessary to effectuate this agreement.</P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart F—Outreach and Assistance For Socially Disadvantaged Farmers and Ranchers Program</HD>
                                <SECTION>
                                    <SECTNO>§ 2500.101 </SECTNO>
                                    <SUBJECT>Applicability of regulations.</SUBJECT>
                                    <P>The regulations in this subpart apply to the Outreach and Assistance for Socially Disadvantaged Farmers and Ranchers (OASDFR) Program authorized under section 2501 of the Food, Agriculture, Conservation and Trade Act of 1990 (7 U.S.C. 2279), as amended. Unless otherwise specified in this subpart, the requirements of 7 CFR part 2500 subparts A through E will apply in addition to the requirements discussed in this subpart.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.102 </SECTNO>
                                    <SUBJECT>Purpose.</SUBJECT>
                                    <P>
                                        (a) The purpose of the OASDFR Program is to make competitive awards to provide outreach and technical assistance to encourage and assist 
                                        <PRTPAGE P="66177"/>
                                        socially disadvantaged farmers and ranchers in:
                                    </P>
                                    <P>(1) Owning and operating farms, ranches and non-industrial forest lands; and</P>
                                    <P>(2) In participating equitably in the full range of agricultural programs offered by the Department.</P>
                                    <P>(b) The OASDFR Program awards shall be used exclusively to:</P>
                                    <P>(1) Enhance coordination of the outreach, technical assistance, and education efforts authorized under agriculture programs;</P>
                                    <P>(2) Assist in reaching current and prospective socially disadvantaged farmers, ranchers or forest landowners in a linguistically appropriate manner; and</P>
                                    <P>(3) Improve the participation of those farmers and ranchers in agricultural programs.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.103 </SECTNO>
                                    <SUBJECT>Definitions.</SUBJECT>
                                    <P>The definitions provided in subpart A apply to this subpart. In addition, the definitions that apply specifically to the OASDFR Program under this subpart include:</P>
                                    <P>
                                        <E T="03">Agriculture programs</E>
                                         means those programs administered within the Department, by agencies including but not limited to: Forest Service (FS), Natural Resources Conservation Service (NRCS), Farm Service Agency (FSA), Risk Management Agency (RMA), Rural Development (RD), Rural Business Cooperative Service (RBCS), National Institute of Food and Agriculture (NIFA), and Agricultural Marketing Service (AMS), and other such programs as determined by the Department on a case-by-case basis either at the OAO Director's initiative or in response to a written request with supporting explanation for inclusion of a program. (For further details on specific programs included under this subpart see 7 U.S.C. 2279(e)(3) or the RFP).
                                    </P>
                                    <P>
                                        <E T="03">Alaska Native</E>
                                         means a citizen of the United States who is a person of one-fourth or more Alaska Indian, Eskimo, or Aleut blood, or combination thereof. (For further specification, see 43 U.S.C 1602(b) or the RFP).
                                    </P>
                                    <P>
                                        <E T="03">Alaska Native cooperative colleges</E>
                                         means an eligible post-secondary educational institution that has an enrollment of undergraduate full-time equivalent students that is at least 20 percent Alaska Native students at the time of submission of a proposal.
                                    </P>
                                    <P>
                                        <E T="03">Assistance</E>
                                         means providing educational and technical assistance to socially disadvantaged farmers, ranchers, and forest landowners in (1) owning and operating farms, ranches, and non-industrial forest lands; and (2) in participating equitably in the full range of agricultural programs offered by the Department through workshops, site visits and other means of contact in a linguistically appropriate manner.
                                    </P>
                                    <P>
                                        <E T="03">Farmer, rancher, or forest landowner</E>
                                         means the person who primarily cultivates, operates, or manages a farm, ranch, or forest for profit, either as owner or tenant. A farm includes livestock, dairy, poultry, fish, fruit, and truck farms. It also includes plantations, ranches, ranges, and orchards.
                                    </P>
                                    <P>
                                        <E T="03">Hispanic-serving institution</E>
                                         means an eligible institution of higher education that has an enrollment of undergraduate full-time equivalent students that is at least 25 percent Hispanic students at the end of the award year immediately preceding the date of submission of a proposal (see 20 U.S.C. 1101a(5)).
                                    </P>
                                    <P>
                                        <E T="03">Indian tribe</E>
                                         means any Indian tribe, band, nation, or other organized group or community, including any Alaska Native village or regional or village corporation as defined in or established pursuant to the Alaska Native Claims Settlement Act (85 Stat. 688) (43 U.S.C. 1601 
                                        <E T="03">et seq.</E>
                                        ), which is recognized as eligible for the special programs and services provided by the United States to Indians because of their status as Indians. (For further specification, see 25 U.S.C. 450b).
                                    </P>
                                    <P>
                                        <E T="03">Indian tribal community college</E>
                                         means a post-secondary education institution which is formally controlled, or has been officially sanctioned, or chartered, by the governing body of an Indian tribe or tribes. (See 25 U.S.C. 1801(a)(4)).
                                    </P>
                                    <P>
                                        <E T="03">Institution of higher education</E>
                                         means an educational institution in any State that is a public or other nonprofit institution that is legally authorized and accredited by a nationally recognized accrediting agency or association to provide a program of education beyond secondary education for which the institution awards a bachelor's degree. (For further specification, see 20 U.S.C. 1001(a)).
                                    </P>
                                    <P>
                                        <E T="03">Outreach</E>
                                         means the use of formal and informal educational materials and activities in a linguistically appropriate manner that serve to encourage and assist socially disadvantaged farmers and ranchers in:
                                    </P>
                                    <P>(1) Owning and operating farms and ranches; and in</P>
                                    <P>(2) Participating equitably in the full range of agricultural programs offered by the Department.</P>
                                    <P>
                                        <E T="03">Socially disadvantaged farmer, rancher or forest landowner</E>
                                         means a farmer, rancher, or forest landowner who is a member of a socially disadvantaged group. (See 7 U.S.C. 2279(e)(2)).
                                    </P>
                                    <P>
                                        <E T="03">Socially disadvantaged group</E>
                                         means a group whose members have been subjected to racial or ethnic prejudice because of their identity as members of a group without regard to their individual qualities. (See 7 U.S.C. 2279(e)(1)).
                                    </P>
                                    <P>
                                        <E T="03">State</E>
                                         means any of the 50 States of the United States, the District of Columbia, the Commonwealth of Puerto Rico, Guam, the Virgin Islands of the United States, American Samoa, the Commonwealth of the Northern Mariana Islands, and federally recognized Indian tribes.
                                    </P>
                                    <P>
                                        <E T="03">Supplemental funding</E>
                                         means funding to an existing awardee in addition to the amount of the original award contained in the grant or cooperative agreement. Such additional funding is intended to continue or expand work that is within the scope of the original agreement and statement of work.
                                    </P>
                                    <P>
                                        <E T="03">Tribal organization</E>
                                         means the recognized governing body of any Indian tribe. A tribal organization is any legally established organization of Indians which is controlled, sanctioned, or chartered by such governing body or which is democratically elected by the adult members of the Indian community. In any case where an award is made to an organization to perform services benefiting more than one Indian tribe, the approval of each participating Indian tribe shall be a prerequisite to the making of such an award. (See 25 U.S.C. 1603(25).
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.104 </SECTNO>
                                    <SUBJECT>Eligibility requirements.</SUBJECT>
                                    <P>Proposals may be submitted by any of the following:</P>
                                    <P>(a) Any community-based organization, network, or coalition of community-based organizations that:</P>
                                    <P>(1) Has demonstrated experience in providing agricultural education or other agriculturally related services to socially disadvantaged farmers, ranchers, and forest landowners;</P>
                                    <P>(2) Has provided to the Secretary documentary evidence of work with, and on behalf of socially disadvantaged farmers, ranchers, or forest landowners during the three-year period preceding the submission of a proposal for assistance under this program; and</P>
                                    <P>(3) Does not engage in activities prohibited under Section 501(c)(3) of the Internal Revenue Code of 1986.</P>
                                    <P>(b) An 1890 institution or 1994 institution (as defined in 7 U.S.C. 7601), including West Virginia State University.</P>
                                    <P>(c) An Indian tribal community college or an Alaska Native cooperative college.</P>
                                    <P>
                                        (d) A Hispanic-serving institution (as defined in 7 U.S.C. 3103).
                                        <PRTPAGE P="66178"/>
                                    </P>
                                    <P>(e) Any other institution of higher education (as defined in 20 U.S.C. 1001) that has demonstrated experience in providing agriculture education or other agriculturally related services to socially disadvantaged farmers, ranchers, and forest landowners in a region.</P>
                                    <P>(f) An Indian tribe (as defined in 25 U.S.C. 450b) or a national tribal organization that has demonstrated experience in providing agriculture education or other agriculturally-related services to socially disadvantaged farmers, ranchers, and forest landowners in a region.</P>
                                    <P>(g) Other organizations or institutions that received funding under this program before January 1, 1996, but only with respect to projects that the Secretary considers are similar to projects previously carried out by the entity under this program.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.105 </SECTNO>
                                    <SUBJECT>Project types and priorities.</SUBJECT>
                                    <P>For each RFP, OAO may develop and include the appropriate project types and focus areas based on the critical needs of the socially disadvantaged farmer and rancher community. For standard OASDFR projects, competitive grants or cooperative agreements will be awarded to support programs and services, as appropriate, to encourage and assist socially disadvantaged farmers and ranchers in the following focus areas:</P>
                                    <P>(a) Owning and operating farms and ranches;</P>
                                    <P>(b) Participating equitably in the full range of agricultural programs offered by the Department; and</P>
                                    <P>(c) Other areas as specified by the Secretary in the RFP.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.106 </SECTNO>
                                    <SUBJECT>Funding restrictions.</SUBJECT>
                                    <P>Funds made available under this subpart shall not be used for the construction of a new building or facility or the acquisition, expansion, remodeling, or alteration of an existing facility (including site grading and improvement, and architect fees).</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.107 </SECTNO>
                                    <SUBJECT>Matching.</SUBJECT>
                                    <P>Matching funds are not required as a condition of receiving awards under this subpart.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.108 </SECTNO>
                                    <SUBJECT>Term of award.</SUBJECT>
                                    <P>The award term will be defined in the OAO award agreement, and can be later amended upon approval of OAO.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 2500.109 </SECTNO>
                                    <SUBJECT>Program requirements.</SUBJECT>
                                    <P>Grants and cooperative agreements under this subpart shall address the priorities in the Department that involve providing outreach and technical assistance to socially disadvantaged farmers, ranchers, and forest landowners to own and operate farms and participate equitably in agricultural programs; and other priorities as determined by the Secretary. </P>
                                </SECTION>
                            </SUBPART>
                        </PART>
                    </CHAPTER>
                </REGTEXT>
                <SIG>
                    <DATED>Signed in Washington, DC, on October 14, 2011.</DATED>
                    <NAME>Pearlie S. Reed,</NAME>
                    <TITLE>Assistant Secretary for Administration for the Office of the Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27108 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3412-89-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-0750; Airspace Docket No. 11-AAL-08]</DEPDOC>
                <SUBJECT>Revision of Class E Airspace; Umiat, AK</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This action revises Class E airspace at Umiat, AK, due to the cancellation of two special instrument approach procedures at the Umiat Airport. The cancellation of these two special instrument approach procedures has made the transition airspace from 700 feet above the surface no longer necessary for the safety of Instrument Flight Rules (IFR) operations.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective 0901 UTC, December 15, 2011. The Director of the Federal Register approves this incorporation by reference action under title 1, Code of Federal Regulations, part 51, subject to the annual revision of FAA Order 7400.9 and publication of conforming amendments.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Martha Dunn, AAL-538G, Federal Aviation Administration, 222 West 7th Avenue, Box 14, Anchorage, AK 99513-7587; telephone number (907) 271-5898; 
                        <E T="03">fax:</E>
                         (907) 271-2850; 
                        <E T="03">e-mail: Martha.ctr.Dunn@faa.gov. Internet address: http://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/systemops/fs/alaskan/rulemaking/.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">History</HD>
                <P>
                    On Wednesday, August 10, 2011, the FAA published a notice of proposed rulemaking (NPRM) in the 
                    <E T="04">Federal Register</E>
                     to revise Class E airspace at Umiat, AK (76 FR 49387).
                </P>
                <P>Interested parties were invited to participate in this rulemaking proceeding by submitting written comments on the proposal to the FAA. One comment was made regarding a typing error within the final rule. This error has been corrected.</P>
                <P>
                    The Class E airspace areas are published in paragraphs 6002 and 6005, respectively, of FAA Order 7400.9V, 
                    <E T="03">Airspace Designations and Reporting Points,</E>
                     signed September 9, 2011, and effective September 15, 2011, which is incorporated by reference in 14 CFR 71.1. The Class E airspace designations listed in this document will be published subsequently in the Order. With the exception of editorial changes, and the changes described above, this rule is the same as that proposed in the NPRM.
                </P>
                <HD SOURCE="HD1">The Rule</HD>
                <P>This action amends Title 14 Code of Federal Regulations (14 CFR) part 71 by revising Class E airspace at the Umiat Airport, Umiat, AK, due to the cancellation of two special instrument approach procedures. The Class E airspace extending upward from 700 above the surface is no longer necessary for the safety and management of IFR operations at the airport.</P>
                <P>The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore—(1) Is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Because this is a routine matter that will only affect air traffic procedures and air navigation, it is certified that this rule will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <P>The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle 1, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority.</P>
                <P>
                    This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart 1, Section 40103, Sovereignty and use of airspace. Under that section, the FAA is charged with prescribing regulations to ensure the safe and efficient use of the navigable airspace. This regulation is within the scope of that authority because it reflects the changes in use of 
                    <PRTPAGE P="66179"/>
                    the Umiat Airport and is consistent with the FAA's continuing effort to safely and efficiently use the navigable airspace.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">Adoption of the Amendment</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 71 as follows:</P>
                <REGTEXT TITLE="14" PART="71">
                    <PART>
                        <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for 14 CFR part 71 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="14" PART="71">
                    <SECTION>
                        <SECTNO>§ 71.1</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>
                        2. The incorporation by reference in 14 CFR 71.1 of Federal Aviation Administration Order 7400.9V, 
                        <E T="03">Airspace Designations and Reporting Points,</E>
                         signed September 9, 2011, and effective September 15, 2011, is amended as follows:
                    </AMDPAR>
                    <EXTRACT>
                        <HD SOURCE="HD2">Paragraph 6005 Class E arspace extending upward from 700 feet or more above the surface of the earth.</HD>
                        <STARS/>
                        <HD SOURCE="HD1">AAL AK E5 Umiat, AK [Revised]</HD>
                        <FP SOURCE="FP-2">Umiat Airport, AK</FP>
                        <FP SOURCE="FP1-2">(Lat. 69°22′16″ N., long. 152°08′06″ W.)</FP>
                        <P>That airspace extending upward from 1,200 feet above the surface within a 73-mile radius of the Umiat Airport, Alaska.</P>
                    </EXTRACT>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Anchorage, AK, on October 14, 2011.</DATED>
                    <NAME>Marshall G. Severson,</NAME>
                    <TITLE>Acting Manager, Alaska Flight Services.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27366 Filed 10-25-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. 30808; Amdt. No. 3448]</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 October 26, 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 October 26, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Availability of matters 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 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>
                        Richard A. Dunham III, 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 
                    <PRTPAGE P="66180"/>
                    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 October 14, 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 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>
                    <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>
                    <EXTRACT>
                        <HD SOURCE="HD2">Effective 17 NOV 2011</HD>
                        <FP SOURCE="FP-1">Troy, AL, Troy Muni, RADAR-1, Amdt 9</FP>
                        <FP SOURCE="FP-1">Show Low, AZ, Show Low Rgnl, RNAV (GPS) RWY 24, Amdt 2A</FP>
                        <FP SOURCE="FP-1">Salinas, CA, Salinas Muni, Takeoff Minimums and Obstacle DP, Amdt 4</FP>
                        <FP SOURCE="FP-1">Atlanta, GA, Hartsfield-Jackson Atlanta Intl, Takeoff Minimums and Obstacle DP, Amdt 4A</FP>
                        <FP SOURCE="FP-1">Newton, KS, Newton-City-County, Takeoff Minimums and Obstacle DP, Orig</FP>
                        <FP SOURCE="FP-1">Fayetteville, NC, Fayetteville Rgnl/Grannis Field, ILS OR LOC/DME RWY 4, Amdt 16</FP>
                        <FP SOURCE="FP-1">Teterboro, NJ, Teterboro, RNAV (GPS)-C, Orig, CANCELLED</FP>
                        <FP SOURCE="FP-1">Teterboro, NJ, Teterboro, RNAV (GPS) X RWY 6,Orig</FP>
                        <FP SOURCE="FP-1">Watertown, NY, Watertown Intl, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
                        <FP SOURCE="FP-1">Fairview, OK, Fairview Muni, Takeoff Minimums and Obstacle DP, Amdt 3</FP>
                        <FP SOURCE="FP-1">Guymon, OK, Guymon Muni, GPS RWY 36, Orig-A, CANCELLED</FP>
                        <FP SOURCE="FP-1">Guymon, OK, Guymon Muni, RNAV (GPS) RWY 18, Amdt 1</FP>
                        <FP SOURCE="FP-1">Guymon, OK, Guymon Muni, RNAV (GPS) RWY 36, Orig</FP>
                        <FP SOURCE="FP-1">Guymon, OK, Guymon Muni, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
                        <FP SOURCE="FP-1">Norman, OK, University of Oklahoma Westheimer, ILS OR LOC RWY 17, Amdt 1A</FP>
                        <FP SOURCE="FP-1">Jasper, TN, Marion County-Brown Field, Takeoff Minimums and Obstacle DP, Amdt 2</FP>
                        <FP SOURCE="FP-1">Portland, TN, Portland Muni, GPS RWY 19, Orig, CANCELLED</FP>
                        <FP SOURCE="FP-1">Portland, TN, Portland Muni, RNAV (GPS) RWY 1, Orig</FP>
                        <FP SOURCE="FP-1">Portland, TN, Portland Muni, RNAV (GPS) RWY 19, Orig</FP>
                        <FP SOURCE="FP-1">Pulaski, TN, Abernathy Field, RNAV (GPS) RWY 16, Amdt 2</FP>
                        <FP SOURCE="FP-1">Pulaski, TN, Abernathy Field, RNAV (GPS) RWY 34, Amdt 2</FP>
                        <FP SOURCE="FP-1">Pulaski, TN, Abernathy Field, Takeoff Minimums and Obstacle DP, Amdt 4</FP>
                        <FP SOURCE="FP-1">Rogersville, TN, Hawkins County, Takeoff Minimums and Obstacle DP, Amdt 2</FP>
                        <FP SOURCE="FP-1">Amarillo, TX, Tradewind, Takeoff Minimums and Obstacle DP, Amdt 3</FP>
                        <FP SOURCE="FP-1">Lancaster, TX, Lancaster Rgnl, NDB RWY 31, Amdt 3, CANCELLED</FP>
                        <FP SOURCE="FP-1">Yakima, WA, Yakima Air Terminal/Mcallister Field, RNAV (RNP) Y RWY 27, Orig-A</FP>
                        <HD SOURCE="HD2">Effective 15 DEC 2011</HD>
                        <FP SOURCE="FP-1">Savoonga, AK, Savoonga, RNAV (GPS) RWY 5, Amdt 1</FP>
                        <FP SOURCE="FP-1">Savoonga, AK, Savoonga, RNAV (GPS) RWY 23, Amdt 1</FP>
                        <FP SOURCE="FP-1">Shungnak, AK, Shungnak, RNAV (GPS) RWY 9, Amdt 2</FP>
                        <FP SOURCE="FP-1">Shungnak, AK, Shungnak, RNAV (GPS) RWY 27, Amdt 2</FP>
                        <FP SOURCE="FP-1">Hamilton, AL, Marion County-Rankin Fite, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
                        <FP SOURCE="FP-1">Prattville, AL, Prattville-Grouby Field, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
                        <FP SOURCE="FP-1">Reform, AL, North Pickens, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
                        <FP SOURCE="FP-1">McGehee, AR, McGehee Muni, Takeoff Minimums and Obstacle DP, Orig</FP>
                        <FP SOURCE="FP-1">Mesa, AZ, Falcon Fld, RNAV (GPS) RWY 4L, Amdt 1</FP>
                        <FP SOURCE="FP-1">Mesa, AZ, Falcon Fld, RNAV (GPS) RWY 4R, Amdt 1</FP>
                        <FP SOURCE="FP-1">Atwater, CA, Castle, ILS OR LOC/DME RWY 31, Amdt 2C</FP>
                        <FP SOURCE="FP-1">Atwater, CA, Castle, RNAV (GPS) RWY 13, Orig-B</FP>
                        <FP SOURCE="FP-1">Atwater, CA, Castle, RNAV (GPS) RWY 31, Orig-B</FP>
                        <FP SOURCE="FP-1">Atwater, CA, Castle, Takeoff Minimums and Obstacle DP, Amdt 1A</FP>
                        <FP SOURCE="FP-1">Atwater, CA, Castle, VOR/DME RWY 31, Amdt 1B</FP>
                        <FP SOURCE="FP-1">Davis/Woodland/Winters, CA, Yolo County, RNAV (GPS) RWY 34, Amdt 2</FP>
                        <FP SOURCE="FP-1">Denver, CO, Rocky Mountain Metropolitan, ILS OR LOC Y RWY 29R, Amdt 14</FP>
                        <FP SOURCE="FP-1">Denver, CO, Rocky Mountain Metropolitan, ILS OR LOC Z RWY 29R, Orig</FP>
                        <FP SOURCE="FP-1">Denver, CO, Rocky Mountain Metropolitan, RNAV (GPS) RWY 29L, Amdt 1</FP>
                        <FP SOURCE="FP-1">Denver, CO, Rocky Mountain Metropolitan, RNAV (GPS) RWY 29R, Amdt 1</FP>
                        <FP SOURCE="FP-1">Miami, FL, Opa-Locka Executive, GPS RWY 9L, Orig B, CANCELLED</FP>
                        <FP SOURCE="FP-1">Miami, FL, Opa-Locka Executive, GPS RWY 27R, Orig B, CANCELLED</FP>
                        <FP SOURCE="FP-1">Miami, FL, Opa-Locka Executive, ILS OR LOC RWY 9L, Amdt 5</FP>
                        <FP SOURCE="FP-1">Miami, FL, Opa-Locka Executive, ILS OR LOC RWY 12, Amdt 2</FP>
                        <FP SOURCE="FP-1">Miami, FL, Opa-Locka Executive, ILS OR LOC RWY 27R, Amdt 1</FP>
                        <FP SOURCE="FP-1">Miami, FL, Opa-Locka Executive, RNAV (GPS) RWY 9L, Orig</FP>
                        <FP SOURCE="FP-1">Miami, FL, Opa-Locka Executive, RNAV (GPS) RWY 12, Orig</FP>
                        <FP SOURCE="FP-1">Miami, FL, Opa-Locka Executive, RNAV (GPS) RWY 27R, Orig</FP>
                        <FP SOURCE="FP-1">Miami, FL, Opa-Locka Executive, Takeoff Minimums and Obstacle DP, Amdt 9</FP>
                        <FP SOURCE="FP-1">Sebring, FL, Sebring Rgnl, RNAV (GPS) RWY 14, Orig</FP>
                        <FP SOURCE="FP-1">Sebring, FL, Sebring Rgnl, RNAV (GPS) RWY 32, Orig</FP>
                        <FP SOURCE="FP-1">Waynesboro, GA, Burke County, NDB RWY 8, Amdt 2B, CANCELLED</FP>
                        <FP SOURCE="FP-1">Cedar Rapids, IA, The Eastern Iowa, ILS OR LOC RWY 27. Amdt 6B</FP>
                        <FP SOURCE="FP-1">Boise, ID, Boise Air Terminal/Gowen Fld, VOR/DME OR TACAN RWY 10L, Amdt 2</FP>
                        <FP SOURCE="FP-1">Boise, ID, Boise Air Terminal/Gowen Fld, VOR/DME RWY 10R, Amdt 1</FP>
                        <FP SOURCE="FP-1">Abilene, KS, Abilene Muni, Takeoff Minimums and Obstacle DP, Orig</FP>
                        <FP SOURCE="FP-1">Marysville, KS, Marysville, NDB RWY 34, Amdt 5, CANCELLED</FP>
                        <FP SOURCE="FP-1">Moundridge, KS, Moundridge Muni, Takeoff Minimums and Obstacle DP, Orig</FP>
                        <FP SOURCE="FP-1">Paola, KS, Miami County, Takeoff Minimums and Obstacle DP, Orig</FP>
                        <FP SOURCE="FP-1">Indianola, MS, Indianola Muni, NDB RWY 18, Amdt 5A, CANCELLED</FP>
                        <FP SOURCE="FP-1">Indianola, MS, Indianola Muni, NDB RWY 36, Amdt 5A, CANCELLED</FP>
                        <FP SOURCE="FP-1">Lewistown, MT, Lewistown Muni, RNAV (GPS) RWY 8, Amdt 1A</FP>
                        <FP SOURCE="FP-1">Rochester, NY, Greater Rochester Intl, Takeoff Minimums and Obstacle DP, Amdt 7</FP>
                        <FP SOURCE="FP-1">Aurora, OR, Aurora State, Takeoff Minimums and Obstacle DP, Amdt 3</FP>
                        <FP SOURCE="FP-1">
                            North Bend, OR, Southwest Oregon Rgnl, NDB RWY 4, Amdt 5A
                            <PRTPAGE P="66181"/>
                        </FP>
                        <FP SOURCE="FP-1">North Bend, OR, Southwest Oregon Rgnl, RNAV (GPS) Y RWY 4, Orig-A</FP>
                        <FP SOURCE="FP-1">North Bend, OR, Southwest Oregon Rgnl, VOR-A, Amdt 5A</FP>
                        <FP SOURCE="FP-1">North Bend, OR, Southwest Oregon Rgnl, VOR/DME-B, Amdt 4A</FP>
                        <FP SOURCE="FP-1">Scappoose, OR, Scappoose Industrial Airpark, LOC/DME RWY 15, Amdt 2</FP>
                        <FP SOURCE="FP-1">Bay City, TX, Bay City Muni, Takeoff Minimums and Obstacle DP, Orig</FP>
                        <FP SOURCE="FP-1">Denton, TX, Denton Muni, ILS OR LOC RWY 18, Amdt 9</FP>
                        <FP SOURCE="FP-1">Devine, TX, Devine Muni, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
                        <FP SOURCE="FP-1">Kenedy, TX, Karnes County, RNAV (GPS) RWY 16, Orig</FP>
                        <FP SOURCE="FP-1">Kenedy, TX, Karnes County, RNAV (GPS) RWY 34, Orig</FP>
                        <FP SOURCE="FP-1">Kenedy, TX, Karnes County, VOR/DME-A, Amdt 7</FP>
                        <FP SOURCE="FP-1">Paducah, TX, Dan E. Richards Muni, Takeoff Minimums and Obstacle DP, Orig</FP>
                        <FP SOURCE="FP-1">Williamsburg, VA, Williamsburg-Jamestown, Takeoff Minimums and Obstacle DP, Amdt 2</FP>
                        <FP SOURCE="FP-1">Walla Walla, WA, Walla Walla Rgnl, NDB RWY 20, Amdt 6</FP>
                        <FP SOURCE="FP-1">Milwaukee, WI, General Mitchell Intl, ILS OR LOC RWY 19R, Amdt 12</FP>
                        <FP SOURCE="FP-1">Phillips, WI, Price County, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
                        <FP SOURCE="FP-1">Fairmont, WV, Fairmont Muni-Frankman Field, VOR/DME-A, Amdt 1</FP>
                    </EXTRACT>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27371 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Bureau of Industry and Security</SUBAGY>
                <CFR>15 CFR Part 774</CFR>
                <SUBJECT>The Commerce Control List</SUBJECT>
                <HD SOURCE="HD2">CFR Correction</HD>
                <P>In Title 15 of the Code of Federal Regulations, Parts 300-799, revised as of January 1, 2011, in Supplement No. 1 to Part 774, in ECCN 2B008, the “Items” paragraph on page 719 is revised to read as follows:</P>
                <REGTEXT TITLE="15" PART="774">
                    <HD SOURCE="HD1">Supplement No. 1 to PART 774—THE COMMERCE CONTROL LIST</HD>
                    <STARS/>
                    <FP>
                        <E T="03">2B008 Assemblies or Units, Specially Designed for Machine Tools, or Dimensional Inspection or Measuring Systems and Equipment, as Follows (See List of Items Controlled).</E>
                    </FP>
                    <STARS/>
                    <P>
                        <E T="03">Items:</E>
                    </P>
                    <P>
                        a. Linear position feedback units (e.g., inductive type devices, graduated scales, infrared systems or “laser” systems) having an overall “accuracy” less (better) than (800 + (600 × L × 10
                        <E T="51">−3</E>
                        )) nm (L equals the effective length in mm);
                    </P>
                    <P>N.B.: For “laser” systems see also 2B006.b.1.c and d.</P>
                    <P>b. Rotary position feedback units (e.g., inductive type devices, graduated scales, infrared systems or “laser” systems) having an “accuracy” less (better) than 0.00025°;</P>
                    <P>N.B.: For “laser” systems see also 2B006.b.2.</P>
                    <P>c. “Compound rotary tables” and “tilting spindles”, capable of upgrading, according to the manufacturer's specifications, machine tools to or above the levels controlled by 2B001 to 2B009.</P>
                    <STARS/>
                </REGTEXT>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27753 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 1505-01-D</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Bureau of Industry and Security</SUBAGY>
                <CFR>15 CFR Part 774</CFR>
                <SUBJECT>The Commerce Control List</SUBJECT>
                <HD SOURCE="HD2">CFR Correction</HD>
                <P>In Title 15 of the Code of Federal Regulations, Parts 300-799, revised as of January 1, 2011, on page 684, in Supplement No. 1 to Part 774, in ECCN 1C118, the “Items” paragraph is revised to read as follows:</P>
                <REGTEXT TITLE="15" PART="774">
                    <HD SOURCE="HD1">Supplement No. 1 to PART 774—THE COMMERCE CONTROL LIST</HD>
                    <STARS/>
                    <FP>
                        <E T="03">1C118 Titanium-stabilized duplex stainless steel (Ti-DSS), having all of the following characteristics (see List of Items Controlled).</E>
                    </FP>
                    <STARS/>
                    <P>
                        <E T="03">Items:</E>
                    </P>
                    <P>a. Having all of the following characteristics:</P>
                    <P>a.1. Containing 17.0-23.0 weight percent chromium and 4.5-7.0 weight percent nickel;</P>
                    <P>a.2. Having a titanium content of greater than 0.10 weight percent; and </P>
                    <P>a.3. A ferritic-austenitic microstructure (also referred to as a two-phase microstructure) of which at least 10 percent is austenite by volume (according to ASTM E-1181-87 or national equivalents), and</P>
                    <P>b. Having any of the following forms:</P>
                    <P>b.1. Ingots or bars having a size of 100 mm or more in each dimension; </P>
                    <P>b.2. Sheets having a width of 600 mm or more and a thickness of 3 mm or less; or</P>
                    <P>b.3. Tubes having an outer diameter of 600 mm or more and a wall thickness of 3 mm or less.</P>
                    <STARS/>
                </REGTEXT>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27751 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 1505-01-D</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <CFR>26 CFR Part 301</CFR>
                <DEPDOC>[TD 9553]</DEPDOC>
                <RIN>RIN 1545-BH90</RIN>
                <SUBJECT>Disregarded Entities; Excise Taxes and Employment Taxes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final regulations and removal of temporary regulations.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document contains final regulations relating to disregarded entities and excise taxes. These regulations also make conforming changes to the tax liability rule for disregarded entities and the treatment of entity rule for disregarded entities with respect to employment taxes. These regulations affect disregarded entities in general and, in particular, disregarded entities that pay or pay over certain federal excise taxes or that are required to be registered by the IRS.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         These regulations are effective on October 26, 2011.
                    </P>
                    <P>
                        <E T="03">Applicability Date:</E>
                         For dates of applicability, see §§ 301.7701-2(e)(2), 301.7701-2(e)(5), and 301.7701-2(e)(6).
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Michael H. Beker, (202) 622-3070 (not a toll-free number).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>This document contains amendments to the Procedure and Administration Regulations (26 CFR part 301) under section 7701 of the Internal Revenue Code (Code).</P>
                <P>
                    Temporary regulations (TD 9462, 74 FR 46903) and a cross-reference notice of proposed rulemaking (REG-116614-08, 74 FR 46957) were published in the 
                    <E T="04">Federal Register</E>
                     on September 14, 2009 (the 2009 proposed regulations). On October 14, 2009, corrections to the temporary regulations (74 FR 52677) and to the cross-reference notice of proposed rulemaking (74 FR 52708) were published in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>
                    The 2009 proposed regulations clarify that a single-owner eligible entity that is disregarded as an entity separate from its owner for any purpose under § 301.7701-2, but regarded as an entity for certain excise tax purposes under § 301.7701-2(c)(2)(v), is treated as a corporation with respect to those excise taxes. In addition, the 2009 proposed regulations make conforming changes to the tax liability rule for disregarded entities in § 301.7701-2(c)(2)(iii) and the 
                    <PRTPAGE P="66182"/>
                    treatment of entity rule for disregarded entities with respect to employment taxes in § 301.7701-2(c)(2)(iv)(B).
                </P>
                <P>No public hearing was requested or held. One written comment was received. After consideration of the comment, the proposed regulations are adopted by this Treasury decision and the temporary regulations are removed.</P>
                <HD SOURCE="HD1">Summary of the Comment and Explanation of Provisions</HD>
                <HD SOURCE="HD2">A. Air Transportation Excise Tax</HD>
                <P>The commenter asked whether an amount paid to a single-member limited liability company (SMLLC) by its owner for air transportation provided to its owner will be deemed to be paid to a separate corporation and therefore subject to federal transportation excise taxes under section 4261.</P>
                <P>
                    On August 16, 2007, final regulations under § 301.7701-2(c)(2)(v)(A) were published in the 
                    <E T="04">Federal Register</E>
                     (TD 9356, 72 FR 45891) (the 2007 final regulations). The 2007 final regulations provide that a single-owner eligible entity that is disregarded as an entity separate from its owner for Federal tax purposes is treated as a separate entity for certain excise tax purposes, including Federal tax liabilities imposed by Chapter 33 of the Code. Under this rule, amounts paid after December 31, 2007, to an SMLLC by its owner for air transportation are subject to the tax imposed by section 4261. The commenter suggested that the rule in the 2007 final regulations created a tax liability where one did not exist before.
                </P>
                <P>Prior to the adoption of the § 301.7701-2 regulations in 1997, amounts paid from one state law entity to another for air transportation were potentially subject to the section 4261 tax, regardless of the relationship between the entities. See for example, Rev. Ruls. 76-394 (1976-2 CB 355) and 70-325 (1970-1 CB 231), which involve transportation between related corporations and between corporations and their shareholders. Because there are separate and distinct entities in each case, these rulings hold that payments made from one entity to another for taxable air transportation are “amounts paid” for purposes of the section 4261 tax. While section 4282 provides a limited exception in the case of air transportation excise taxes for certain affiliated groups that do not offer air transportation services to non-affiliated members, no exception had been provided prior to 1997 for other situations.</P>
                <P>The adoption of the § 301.7701-2 regulations in 1997 departed from this long-standing precedent by making those previously taxable transactions no longer subject to excise tax when the owner of an eligible entity elected to be a disregarded entity. The 2007 regulations merely restored the long-standing and reasonable pre-1997 rule. Accordingly, the final regulations retain the rule that excise taxes imposed on amounts paid for covered services (such as air transportation) apply to amounts paid between state law entities for such services (unless a statutory exception applies).</P>
                <HD SOURCE="HD2">B. Indoor Tanning Services Excise Tax</HD>
                <P>After the 2009 proposed regulations were published, section 10907 of the Patient Protection and Affordable Care Act, Public Law 111-148 (124 Stat. 119 (2010)) added new Chapter 49 to the Code, which contains an excise tax on amounts paid for indoor tanning services under new section 5000B. The IRS and Treasury Department are aware of issues relating to the treatment of qualified subchapter S subsidiaries and single-owner eligible entities that are disregarded as entities separate from their owners with respect to tax liabilities imposed by Chapter 49 of the Code. The issues are similar to those addressed in § 301.7701-2(c)(2)(v). Accordingly, the IRS and the Treasury Department plan to issue regulations addressing the treatment of those entities with respect to tax liabilities imposed by Chapter 49 of the Code.</P>
                <HD SOURCE="HD2">C. Firearms Excise Tax and Harbor Maintenance Tax</HD>
                <P>The rules in the final regulations do not apply to the firearms excise tax administered by the Alcohol and Tobacco Tax and Trade Bureau (TTB) and the harbor maintenance tax administered by U.S. Customs and Border Protection (Customs). Rules in 26 CFR part 301 generally do not apply for purposes of these taxes and taxpayers should not assume that a single owner entity will be disregarded under applicable TTB or Customs rules.</P>
                <HD SOURCE="HD3">Availability of IRS Documents</HD>
                <P>The IRS revenue rulings cited in this preamble are published in the Internal Revenue Cumulative Bulletin and are available from the Superintendent of Documents, P.O. Box 371954, Pittsburgh, PA 15250-7954.</P>
                <HD SOURCE="HD1">Special Analyses</HD>
                <P>It has been determined that this Treasury decision is not a significant regulatory action as defined in Executive Order 12866. Therefore, a regulatory assessment is not required. It has also been determined that section 553(b) of the Administrative Procedure Act (5 U.S.C. chapter 5) does not apply to these regulations, and, because the regulations do not impose a collection of information on small entities, the Regulatory Flexibility Act (5 U.S.C. chapter 6) does not apply. Pursuant to section 7805(f) of the Code, the proposed regulations preceding these regulations were submitted to the Chief Counsel for Advocacy of the Small Business Administration for comment on its impact on small business.</P>
                <HD SOURCE="HD1">Drafting Information</HD>
                <P>The principal author of these regulations is Michael H. Beker, Office of the Associate Chief Counsel (Passthroughs and Special Industries). However, other personnel from the IRS and the Treasury Department participated in their development.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 26 CFR Part 301</HD>
                    <P>Employment taxes, Estate taxes, Excise taxes, Gift taxes, Income taxes, Penalties, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <HD SOURCE="HD1">Adoption of Amendments to the Regulations</HD>
                <P>Accordingly, 26 CFR part 301 is amended as follows:</P>
                <REGTEXT TITLE="26" PART="301">
                    <PART>
                        <HD SOURCE="HED">PART 301—PROCEDURE AND ADMINISTRATION</HD>
                    </PART>
                    <AMDPAR>
                        <E T="04">Paragraph 1.</E>
                         The authority citation for part 301 continues to read in part as follows:
                    </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>26 U.S.C. 7805. * * *</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="301">
                    <AMDPAR>
                        <E T="04">Par. 2.</E>
                         Section 301.7701-2 is amended by:
                    </AMDPAR>
                    <AMDPAR>
                        1. Revising paragraphs (c)(2)(iii), (c)(2)(iv)(B), (c)(2)(v)(B), (c)(2)(v)(C) 
                        <E T="03">Example</E>
                         (iv), (e)(2), and (e)(6).
                    </AMDPAR>
                    <AMDPAR>2. Adding two sentences at the end of paragraph (e)(5).</AMDPAR>
                    <P>The additions and revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 301.7701-2 </SECTNO>
                        <SUBJECT>Business entities; definitions.</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(2) * * *</P>
                        <P>
                            (iii) 
                            <E T="03">Tax liabilities of certain disregarded entities</E>
                            —(A) 
                            <E T="03">In general.</E>
                             An entity that is disregarded as separate from its owner for any purpose under this section is treated as an entity separate from its owner for purposes of—
                        </P>
                        <P>
                            (
                            <E T="03">1</E>
                            ) Federal tax liabilities of the entity with respect to any taxable period for which the entity was not disregarded;
                        </P>
                        <P>
                            (
                            <E T="03">2</E>
                            ) Federal tax liabilities of any other entity for which the entity is liable; and
                        </P>
                        <P>
                            (
                            <E T="03">3</E>
                            ) Refunds or credits of Federal tax.
                            <PRTPAGE P="66183"/>
                        </P>
                        <P>
                            (B) 
                            <E T="03">Examples.</E>
                             The following examples illustrate the application of paragraph (c)(2)(iii)(A) of this section:
                        </P>
                        <EXAMPLE>
                            <HD SOURCE="HED"> Example 1. </HD>
                            <P>In 2006, X, a domestic corporation that reports its taxes on a calendar year basis, merges into Z, a domestic LLC wholly owned by Y that is disregarded as an entity separate from Y, in a state law merger. X was not a member of a consolidated group at any time during its taxable year ending in December 2005. Under the applicable state law, Z is the successor to X and is liable for all of X's debts. In 2009, the Internal Revenue Service (IRS) seeks to extend the period of limitations on assessment for X's 2005 taxable year. Because Z is the successor to X and is liable for X's 2005 taxes that remain unpaid, Z is the proper party to sign the consent to extend the period of limitations.</P>
                        </EXAMPLE>
                        <EXAMPLE>
                            <HD SOURCE="HED">Example 2. </HD>
                            <P>
                                The facts are the same as in 
                                <E T="03">Example 1,</E>
                                 except that in 2007, the IRS determines that X miscalculated and underreported its income tax liability for 2005. Because Z is the successor to X and is liable for X's 2005 taxes that remain unpaid, the deficiency may be assessed against Z and, in the event that Z fails to pay the liability after notice and demand, a general tax lien will arise against all of Z's property and rights to property.
                            </P>
                        </EXAMPLE>
                        <P>(iv) * * *</P>
                        <P>
                            (B) 
                            <E T="03">Treatment of entity.</E>
                             An entity that is disregarded as an entity separate from its owner for any purpose under this section is treated as a corporation with respect to taxes imposed under Subtitle C—Employment Taxes and Collection of Income Tax (Chapters 21, 22, 23, 23A, 24, and 25 of the Internal Revenue Code).
                        </P>
                        <STARS/>
                        <P>(v) * * *</P>
                        <P>
                            (B) 
                            <E T="03">Treatment of entity.</E>
                             An entity that is disregarded as an entity separate from its owner for any purpose under this section is treated as a corporation with respect to items described in paragraph (c)(2)(v)(A) of this section.
                        </P>
                        <P>(C) * * *</P>
                        <P>
                            <E T="03">Example.</E>
                             * * *
                        </P>
                        <P>
                            (iv) Assume the same facts as in paragraph (c)(2)(v)(C) 
                            <E T="03">Example</E>
                             (i) and (ii) of this section. If LLCB does not pay the tax on its sale of coal under chapter 32 of the Internal Revenue Code, any notice of lien the Internal Revenue Service files will be filed as if LLCB were a corporation.
                        </P>
                        <STARS/>
                        <P>(e) * * *</P>
                        <P>(2) Paragraph (c)(2)(iii) of this section applies on and after September 14, 2009. For rules that apply before September 14, 2009, see 26 CFR part 301, revised as of April 1, 2009.</P>
                        <STARS/>
                        <P>(5) * * * However, paragraph (c)(2)(iv)(B) of this section applies with respect to wages paid on or after September 14, 2009. For rules that apply before September 14, 2009, see 26 CFR part 301 revised as of April 1, 2009.</P>
                        <P>(6)(i) Except as provided in this paragraph (e)(6), paragraph (c)(2)(v) of this section applies to liabilities imposed and actions first required or permitted in periods beginning on or after January 1, 2008.</P>
                        <P>
                            (ii) Paragraphs (c)(2)(v)(B) and (c)(2)(v)(C) 
                            <E T="03">Example</E>
                             (iv) of this section apply on and after September 14, 2009.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="301">
                    <SECTION>
                        <SECTNO>§ 301.7701-2T </SECTNO>
                        <SUBJECT>[Removed]</SUBJECT>
                    </SECTION>
                    <AMDPAR>
                        <E T="04">Par. 3.</E>
                         Section 301.7701-2T is removed.
                    </AMDPAR>
                </REGTEXT>
                <SIG>
                    <NAME> Steven T. Miller,</NAME>
                    <TITLE>Deputy Commissioner for Services and Enforcement.</TITLE>
                    <DATED>Approved: October 18, 2011.</DATED>
                    <NAME> Emily S. McMahon,</NAME>
                    <TITLE>Acting, Assistant Secretary of the Treasury (Tax Policy). </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27720 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 117</CFR>
                <DEPDOC>[Docket No. USCG-2011-0960]</DEPDOC>
                <SUBJECT>Drawbridge Operation Regulations; Trent River, New Bern, NC</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of temporary deviation from regulations.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Commander, Fifth Coast Guard District, has issued a temporary deviation from the regulations governing the operation of the US 70 (Alfred Cunningham) Bridge, at mile 0.0, over the Trent River, at New Bern, NC. The deviation restricts the operation of the draw span to facilitate the general maintenance of the Bridge.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This deviation is effective from 8 p.m. October 26, 2011 through 11:59 p.m. on October 27, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Documents mentioned in this preamble as being available in the docket are part of docket USCG-2011-0960 and are available online by going to 
                        <E T="03">http://www.regulations.gov,</E>
                         inserting USCG-2011-0960 in the “Keywords” box, and then clicking “Search”. This material is 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 rule, call or e-mail Mr. Bill H. Brazier, Bridge Management Specialist, Fifth Coast Guard District, telephone (757) 398-6422, e-mail 
                        <E T="03">Bill.H.Brazier@uscg.mil.</E>
                         If you have questions on reviewing the docket, call Renee V. Wright, Program Manager, Docket Operations, (202) 366-9826.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The North Carolina Department of Transportation (NCDOT), who owns and operates this bascule lift bridge, has requested a temporary deviation from the current operating regulations set out in 33 CFR 117.843(a), to facilitate the general maintenance of the bridge.</P>
                <P>In the closed position to vessels, the US 70 (Alfred Cunningham) Bridge, at mile 0.0, at New Bern, NC has a vertical clearance of 14 feet, above mean high water.</P>
                <P>Under this temporary deviation, the drawbridge will be closed to vessels requiring an opening each day from 8 p.m. until 11:59 p.m. on October 26, 2011 and October 27, 2011. There are no alternate routes for vessels transiting this section of the Trent River.</P>
                <P>The Coast Guard reviewed the 2010 drawbridge logs provided by NCDOT. In the month of October 2010, between the hours of 8 p.m. and 11:59 p.m., there were approximately four recorded vessel openings of the drawbridge. The drawbridge will be able to open for emergencies. Most vessel traffic utilizing this bridge consists of recreational boaters. October is outside of the high recreational boating season therefore, only a small number of boaters may be affected by this temporary closure. There are no alternate routes on this section of Trent River. Vessels that can pass through the bridge in the closed position may do so at any time.</P>
                <P>The Coast Guard will inform all users of the waterway through our Local and Broadcast Notice to Mariners of the closure periods for the bridge so that vessels can arrange their transits to minimize any impacts caused by the temporary deviation.</P>
                <P>In accordance with 33 CFR 117.35(e), the draw must return to its original operating schedule immediately at the end of the designated time period. This deviation from the operating regulations is authorized under 33 CFR 117.35.</P>
                <SIG>
                    <PRTPAGE P="66184"/>
                    <DATED>Dated: October 18, 2011.</DATED>
                    <NAME>Waverly W. Gregory, Jr.,</NAME>
                    <TITLE>Bridge Program Manager, By direction of the Commander, Fifth Coast Guard District.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27721 Filed 10-25-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 117</CFR>
                <DEPDOC>[Docket No. USCG-2011-0972]</DEPDOC>
                <SUBJECT>Drawbridge Operation Regulation; Nanticoke, Seaford, DE</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of temporary deviation from regulations.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Commander, Fifth Coast Guard District, has issued a temporary deviation from the regulation governing the operation of the SR 13 Bridge across the Nanticoke River, mile 39.6, at Seaford, DE. The deviation is necessary to accommodate the cleaning and painting of the bridge. This deviation allows the bridge to remain in the closed position throughout the month of November to facilitate the maintenance work.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This deviation is effective from 12:01 a.m. on November 1, 2011 to 11:59 on November 30, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Documents mentioned in this preamble as being available in the docket are part of docket USCG-2011-0972 and are available online by going to 
                        <E T="03">http://www.regulations.gov,</E>
                         inserting USCG-2011-0972 in 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 rule, call or e-mail Lindsey Middleton, Bridge Management Specialist, Coast Guard; telephone 757-398-6629, e-mail 
                        <E T="03">Lindsey.R.Middleton@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>
                <P>Marinis Bros. Inc., on behalf of Delaware Department of Transportation (DelDOT), has requested a temporary deviation from the current operating regulation of the SR 13 Bridge across the Nanticoke River, mile 39.6, at Seaford, DE. The requested deviation is to accommodate painting and cleaning of the bridge. The vertical clearance of this single-leaf bascule bridge is three feet at mean high water (MHW) in the closed position and unlimited in the open position. During this deviation period, the vertical clearance will be limited to one foot at MHW due to the scaffolding that will be used for the maintenance of the bridge. The bridge will remain in the closed position for the entire month. In critical situations the bridge will be able to open if at least 24 hours of notice is given. There are no alternate routes available to vessels.</P>
                <P>The current operating schedule for the bridge is set out in 33 CFR 117.243(b). According to that schedule, during the month of November the bridge shall open on signal, except that from 6 p.m. to 8 a.m. Monday through Friday and 3:30 p.m. through 7:30 a.m. Saturday and Sunday, if at least four hours notice is given.</P>
                <P>Logs from November 2010 have shown that there were 20 openings for the entire month. Sixteen of those openings were on November 13th and 14th. The openings were due to a Bass Fishing Tournament; however, the tournament is not scheduled for this year minimizing the amount of anticipated openings. The majority of vessel traffic utilizing this waterway is recreational boaters. There is one mariner that requests most of the bridge openings throughout the winter months. Marinis Bros., Inc. has coordinated with this mariner. DelDOT has coordinated with the town concerning the month long bridge closure as well. The Coast Guard will inform all other users of the waterway through our Local and Broadcast Notices to Mariners so that mariners can arrange their transits to minimize any impact caused by the temporary deviation. The Coast Guard will also require the bridge owner to post signs on either side of the bridge notifying mariners of the temporary regulation change.</P>
                <P>In accordance with 33 CFR 117.35(e), the drawbridge must return to its regular operating schedule immediately at the end of the designated time period. This deviation from the operating regulations is authorized under 33 CFR 117.35.</P>
                <SIG>
                    <DATED>Dated: October 12, 2011.</DATED>
                    <NAME>Waverly W. Gregory, Jr.,</NAME>
                    <TITLE>Bridge Program Manager, Fifth Coast Guard District.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27722 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">POSTAL SERVICE</AGENCY>
                <CFR>39 CFR Part 241</CFR>
                <SUBJECT>Post Office Organization and Administration: Establishment, Classification, and Discontinuance</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Postal Service.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Postal Service is amending its regulations to improve the administration of the Post Office closing and consolidation process. This final rule adopts changes to Postal Service regulations pertaining to the definition of “consolidation” and the staffing of Post Offices.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         December 1, 2011.
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jim Boldt, (202) 268-6799.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On March 31, 2011, the Postal Service published a proposed rule in the 
                    <E T="04">Federal Register</E>
                     (76 FR 17794) to improve the process for discontinuing Post Offices and other Postal Service-operated retail facilities. The proposed rule also included various proposals to apply certain discontinuance procedures to all retail facilities operated by Postal Service employees. The Postal Service requested comments on the proposed rule.
                </P>
                <P>
                    On July 13, 2011, the Postal Service published an initial final rule (76 FR 41413), with minor corrections published on July 21, 2011 (76 FR 43898). That final rule responded to comments and made numerous changes from the proposed rule, resulting in revised regulations that took effect on July 14, 2011. In the final rule, the Postal Service noted that certain aspects of the proposed rule were subject to then-ongoing consultations under 39 U.S.C. 1004(b)-(d). As a result, the first final rule implemented only changes to 39 CFR part 241 that were not subject to ongoing consultations. 76 FR 41413. The Postal Service advised that changes subject to consultation—namely, those concerning the definition of “consolidation” and the staffing of Post Offices—were being deferred and could be addressed in a subsequent final rule. 
                    <E T="03">Id.</E>
                     at 41414-15.
                </P>
                <P>
                    At this time, the consultations referenced in the first final rule have run their course, and the Postal Service is prepared to issue the remaining proposed changes, with minor modifications as explained in section III below. Analysis of the pertinent comments received appears below. With the changes described herein, the final rule will take effect upon the publication of corresponding changes in 
                    <PRTPAGE P="66185"/>
                    the 
                    <E T="03">Postal Bulletin,</E>
                     scheduled for December 1, 2011.
                </P>
                <HD SOURCE="HD1">I. Response to Comments Received</HD>
                <P>As recounted in the first final rule (76 FR 41413), the Postal Service received approximately 257 comments in response to the proposed rule. Commenters included 34 Members of Congress, the Postal Regulatory Commission (“Commission” or “PRC”), five state legislators, three postmasters' and postal supervisors' organizations, one postal lessors' organization and various of its members, one mailing industry stakeholder, and numerous other postal customers. Although some comments were favorable about certain aspects of the proposed rule, almost all of the comments expressed concerns about various aspects of the proposed rule. Below we discuss the comments pertinent to this final rule and our response to each.</P>
                <HD SOURCE="HD2">A. Definition of “Consolidation”</HD>
                <P>Several commenters expressed concern about the proposed rule's interpretation of “consolidation,” such that the term would no longer apply to the conversion of a Post Office into a Postal Service-operated station or branch. In particular, these commenters claim that this approach, combined with the fact that 39 U.S.C. 404(d)(5) does not confer appeal rights for closings or consolidations of stations and branches, could result in an effective denial of appeal rights if the Postal Service were to convert a Post Office into a station or branch and then proceed to close or consolidate the facility. Comments about appeal rights were discussed in the first final rule (76 FR 41414-15).</P>
                <P>
                    Overall, this rulemaking expands the circumstances in which full-blown discontinuance studies are used; hence, it increases the overall transparency of discontinuance decisions affecting Postal Service-operated retail facilities. Previously, stations and branches studied for discontinuance were studied in a faster, less intensive process. 
                    <E T="03">See</E>
                     PRC, Advisory Opinion Concerning the Process for Evaluating Closing Stations and Branches (“SBOC Opinion”), Docket No. N2009-1, March 10, 2010, at 48-57, 61-65 (exploring differences between the discontinuance processes for Post Offices and for stations and branches).
                </P>
                <P>
                    Contrary to longstanding arguments by the Postal Service resting on much of the legislative history and case law on which some of the comments rely, the Commission, labor organizations, and others have asserted that customers perceive no functional difference between a Post Office and a classified station or classified branch. 
                    <E T="03">See, e.g.,</E>
                     SBOC Opinion at 52, 64; Comments of American Postal Workers Union, AFL-CIO, Eugene Area Local No. 679, PRC Docket No. A2011-4, January 21, 2011, at 1-3. While the Postal Service continues to disagree with the proponents of this view as to whether that lack of perceived difference has legal relevance, the Postal Service acknowledges the practical vitality of the observation. As a result, it is difficult to understand what concrete purpose would be furthered by continuing to apply discontinuance procedures to the conversion of one Postal Service-operated retail facility type to another, when customers will not see any significant difference in service. In contrast, customers are more likely to experience or perceive an impact from the replacement of a Postal Service-operated retail facility with a contractor-operated retail facility.
                </P>
                <P>“Consolidation,” in its former sense of changing a Post Office into a station or branch of another Post Office, has rarely been applied over the last 20 years. From the perspective of postal customers, a conversion between Postal Service-operated retail facility types has only minimal impact, as few customers are aware of the distinction between different types of retail units.</P>
                <P>Unlike classified stations and branches, contractor-operated retail facilities can be closed without being subject to the discontinuance process. Relationships established through a contract have alternative mechanisms for termination or other changes. The continuation of contractor-operated facilities is much more dependent on the contractor's willingness to furnish services under contract for a reasonable fee. Contractor-operated units may accordingly experience less predictability in their continuation. Hence, it is more important that customers and other stakeholders have an opportunity to provide input when a Postal Service-operated retail facility is converted into a contractor-operated retail facility than when a conversion results in Postal Service-operated classified station or branch. The latter are not subject to the greater unpredictability of a contractor-operator, and so customers are unlikely to perceive a significant difference in service when a Post Office is converted into a Postal Service-operated classified station or branch.</P>
                <P>
                    Two postmaster organizations submitted a legal opinion to the effect that the proposed approach to “consolidation” runs counter to a consistent definition provided by legislative history, courts, and the Postal Service itself. This legal analysis appears to overlook the fact that most of the authorities on which it relies, some of which date back to the 1970s, were premised on Postal Service regulations in effect at the time and did not speak to whether the Postal Service was somehow precluded from changing those regulations. That the Postal Service's previous interpretation of “consolidation” was found to be reasonable does not mean that that interpretation is the only reasonable and valid one. See 
                    <E T="03">Citizens for the Hopkins Post Office</E>
                     v. 
                    <E T="03">United States Postal Serv.,</E>
                     830 F. Supp. 296, 299 (D.S.C. 1993) (“This court finds the definition of `consolidation' advanced by the Postal Service [in its then-current regulations] to be one which is reasonable[.]” (emphasis added)).
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The author of the legal opinion appears to have misquoted this sentence of the 
                        <E T="03">Citizens for the Hopkins Post Office</E>
                         opinion as referring to “the [sic] one which is reasonable.” This error may help to explain why the author reads the opinion as supporting the author's conclusion that the Postal Service's historical interpretation of “consolidation” is the 
                        <E T="03">only</E>
                         permissible one, rather than one of multiple interpretive possibilities. The actual quotation supports the latter view.
                    </P>
                </FTNT>
                <P>
                    The United States Supreme Court has long held that an “initial agency interpretation [of a statute] is not instantly carved in stone” and that any agency “must consider varying interpretations and the wisdom of its policy on a continuing basis.” 
                    <E T="03">Chevron, U.S.A., Inc.</E>
                     v. 
                    <E T="03">Natural Resources Defense Council, Inc.,</E>
                     467 U.S. 837, 863-64 (1984). This is the case even where a revised interpretation “represents a sharp break with prior interpretations.” 
                    <E T="03">Id.</E>
                     at 862. Because the plain language of the statute is silent and ambiguous as to the intended definition of “consolidation,” and because the Postal Service is charged with implementing 39 U.S.C. 404(d), the Postal Service is free to revise its interpretation of the statute so long as its interpretation is reasonable. 
                    <E T="03">See id.</E>
                     at 842-43; 
                    <E T="03">Rust</E>
                     v. 
                    <E T="03">Sullivan,</E>
                     500 U.S. 173, 186-87 (1991); 
                    <E T="03">see also Citizens for the Hopkins Post Office,</E>
                     830 F. Supp. at 298-99 (“The term `consolidation' as used in § 404(b) [now 404(d)] is not defined in the statute. Consequently, this court will begin with the principle that the construction placed on a statute by the agency charged with administering it is entitled to considerable deference and should be upheld if reasonable.”). In the proposed rule and elsewhere in this final rule, the Postal Service has explained why it is reasonable to revise its interpretation of “consolidation” in order to give sensible and feasible effect to larger regulatory 
                    <PRTPAGE P="66186"/>
                    changes that will increase transparency and public participation.
                </P>
                <P>
                    The same legal opinion cited a pleading filed by the Postal Service in an ongoing federal action to support its view that the instant rulemaking somehow undoes an indelible aspect of postal law. The legal opinion fails to note that the subject matter of the litigation and the quoted pleading itself concern Postal Service regulations in effect at the time. They do not prejudice the Postal Service's authority or discretion to revise those regulations at a later time. An agency is entitled to defend its actions based on its legal interpretation and regulations in effect at the applicable time, rather than on prior or subsequent policies and regulations. As the Postal Service noted in its proposed rule and first final rule, and reiterates here, this rulemaking is not retroactive and does not affect any actions taken by the Postal Service under previous regulations. 
                    <E T="03">See generally,</E>
                      
                    <E T="03">Bowen</E>
                     v. 
                    <E T="03">Georgetown Univ. Hosp.,</E>
                     488 U.S. 204, 208 (1988) (holding that agency regulations are not retroactive except as specifically authorized by Congress).
                </P>
                <P>In sum, the proposed reinterpretation of “consolidation” is within the Postal Service's authority to administer the statutory scheme. The Postal Service is adopting a new interpretation of the existing statutory term, while continuing to apply the discontinuance procedures established by Congress to consolidations as distinct from closings. The proposed interpretation is reasonable in its own right and goes a long way toward closing the gap between respective Postal Service and Commission positions. It also fits into the larger framework of changes to orient discontinuance processes more appropriately around customer expectations—as the Commission and others have recommended for years—and to increase public transparency and participation.</P>
                <HD SOURCE="HD1">B. Staffing of Post Offices</HD>
                <P>Many commenters expressed the view that the Postmaster Equity Act, Public Law 108-86 (2003), precludes the proposed change to 39 CFR 241.1 such that a Post Office may be staffed by non-postmaster personnel. As codified in 39 U.S.C. 1004(i)(3), the Postmaster Equity Act defines a “postmaster” as “an individual who is the manager in charge of the operations of a post office, with or without the assistance of subordinate managers or supervisors.”</P>
                <P>
                    The Postmaster Equity Act serves the purpose of requiring consultation by the Postal Service with groups representing middle management tiers regarding, among other things, pay policies and schedules. It was not intended to—and unambiguously did not—modify the Postal Service's authority to determine the staffing and scope of its retail facility network. 
                    <E T="03">See</E>
                     39 U.S.C. 403(b)(1), 403(b)(3), 404(a)(3), 1001(e)(4)-(5). Congress was explicit in framing Section 1004(i)'s definitions as applicable only “for purposes of this section.” 39 U.S.C. 1004(i). Cf. 
                    <E T="03">United States</E>
                     v. 
                    <E T="03">Cons. Life Ins. Co.,</E>
                     430 U.S. 725, 769 (1977) (White, J., dissenting) (finding a definition under section 801(c)(2) and (3) of the Internal Revenue Code of 1954 to be inapplicable to rules for taxing the income of life insurance companies from modified coinsured contracts under section 820 of the Internal Revenue Code of 1954, because the definition was applicable only “for purposes of * * * subsection 801(a)”); 
                    <E T="03">Thomas</E>
                     v. 
                    <E T="03">U.S. Bank Nat'l A</E>
                    ss'n, 575 F.3d 794, 798 (8th Cir. 2009) (construing preemption language “for purposes of this section” in 12 U.S.C. 1831d(a) as meaning that “conflicting state constitutions or statutes are not preempted for every and all purposes, but only for purposes of `this section'”). Congress could have applied Section 1004(i)'s definitions to title 39 more broadly or even to section 404(d) in particular, but it did not do so. Therefore, the limited context of the Postmaster Equity Act is inapposite to this rulemaking.
                </P>
                <P>Even if the Postmaster Equity Act had some import in this context, the proposed rule would not be inconsistent with the definition of a “postmaster” therein. The Postmaster Equity Act does not require that each postmaster manage only one Post Office or that every Post Office be individually staffed by a postmaster. Indeed, in many cities, postmasters are responsible for a main Post Office and several classified stations and branches, which the Commission has repeatedly described as having no functional difference from customers' perspectives from Post Offices. The Postal Service is confident that rural postmasters would be similarly capable of overseeing operations at more than one retail facility.</P>
                <P>Decisions about the staffing of Post Offices are within the Postal Service's general authority to manage Post Offices and staff appointments under the Postal Reorganization Act provisions cited above. The proposed rule is consistent with the definition of a postmaster under the Postmaster Equity Act, exercises appropriate and reasonable rule-making authority under the Postal Reorganization Act, and streamlines postal operations in order to reduce costs and enhance value. Therefore, it is a reasonable exercise of the Postal Service's authority to administer its statutory objectives, and it is not inconsistent with title 39 of the U.S. Code.</P>
                <P>One commenter was concerned that, as a result of the same change, the presence of Post Offices staffed by non-postmaster personnel would make it easier for the Postal Service to close those facilities. It is unclear how such an effect would flow from mere staffing arrangements, however. The same requirements, criteria, and procedures apply to all Post Offices, regardless of how they are staffed. As explained in the proposed rule, those same requirements, criteria, and procedures are now applied, as a matter of policy, to Postal Service-operated stations and branches, which are not staffed by postmasters today. If anything, this change could lead to the continued operation of Post Offices that otherwise would be discontinued, due to the Postal Service's ability to staff them in a more flexible and economical fashion.</P>
                <P>Another commenter viewed the proposed change to 39 CFR 241.1 as inconsistent with Employee and Labor Relations Manual (ELM) 113.3, which the commenter believed to correspond to 39 U.S.C. 1004(i)(3). ELM 113.3(k) reflects the Postal Service's previous practice of requiring a postmaster at all Post Offices. As explained above, 39 U.S.C. 1004(i)(3) defines a “postmaster” in association with a Post Office, but does not require that a Post Office be associated with a postmaster staffing each Post Office in all cases. Hence, the Postal Service is not precluded by statute from taking a different approach. The Postal Service plans to update ELM 113.3(k) to reflect the change to 39 CFR 241.1.</P>
                <P>
                    A postal supervisors' organization raised concerns that the replacement of Executive and Administrative Schedule (EAS) employees with bargaining-unit employees, and/or postmasters with clerks-in-charge, would increase workload, deprive communities of access to knowledgeable management personnel, and not offer significant cost savings in light of current pay ceilings. The Postal Service has not yet determined to take any such specific action in furtherance of these changes to the overarching regulations. Any particular staffing decision would presumably take account of workload, community needs, and cost savings. In this rulemaking, the Postal Service only removes, as a general matter, a self-imposed restriction on its discretion to make such decisions in instances where 
                    <PRTPAGE P="66187"/>
                    more flexible staffing may be the most rational option.
                </P>
                <HD SOURCE="HD1">II. Explanation of Changes From Proposed Rule</HD>
                <P>The final rule includes the following additional changes to the proposed rule.</P>
                <P>Paragraph 241.1(a) has been revised to clarify that the operation or staffing of a Post Office by non-postmaster personnel must be at the direction of the postmaster, and that it may include times when the postmaster is not physically present. While the proposed rule referred to whether a Post Office was “operated or managed” by non-postmaster personnel, the phrase “operated or staffed” better reflects the intended meaning that a postmaster would continue to manage operations at the Post Office, albeit possibly without personally operating or staffing it on a continuous basis.</P>
                <P>A sentence is added to paragraph 241.3(a)(1)(ii) (redesignated as 241.3(a)(1)(iii)) to clarify that these regulations will no longer apply to discontinuance actions pending as of December 1, 2011, that pertain to the conversion of a Post Office to another type of USPS-operated facility.</P>
                <P>The definition of “consolidation” in paragraph 241.3(a)(2)(iv) is revised to restrict the term's definition to instances where a Postal Service-operated retail facility is replaced with a contractor-operated retail facility that reports to a Postal Service-operated retail facility. Consistent with the proposed rule, the term no longer encompasses situations where a Post Office is replaced with a Classified Station or Classified Branch.</P>
                <P>Paragraph 241.3(b)(4) is revised to indicate the possibility that a consolidated facility's name, or a similar name, can be used by the succeeding facility, rather than suggesting an expectation that the former name will be maintained, thereby allowing for the range of contract- and service-specific circumstances that can affect such a determination.</P>
                <P>The Postal Service hereby adopts the following changes to 39 CFR part 241.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 39 CFR Part 241</HD>
                    <P>Organization and functions (government agencies), Postal Service.</P>
                </LSTSUB>
                <P>Accordingly, 39 CFR part 241 is amended as follows:</P>
                <REGTEXT TITLE="39" PART="241">
                    <PART>
                        <HD SOURCE="HED">PART 241—RETAIL ORGANIZATION AND ADMINISTRATION: ESTABLISHMENT, CLASSIFICATION, AND DISCONTINUANCE</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for 39 CFR part 241 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>39 U.S.C. 101, 401, 403, 404, 410, 1001.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="39" PART="241">
                    <AMDPAR>2. In § 241.1, paragraph (a) is revised to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 241.1 </SECTNO>
                        <SUBJECT>Post offices.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Establishment.</E>
                             Post Offices are established and maintained at locations deemed necessary to ensure that regular and effective postal services are available to all customers within specified geographic boundaries. A Post Office may be operated or staffed by a postmaster or by another type of postal employee at the direction of the postmaster, including when the postmaster is not physically present.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="39" PART="241">
                    <AMDPAR>3. In § 241.3:</AMDPAR>
                    <AMDPAR>a. Paragraph (a)(1)(i)(B) is revised;</AMDPAR>
                    <AMDPAR>b. Paragraph (a)(1)(ii) is redesignated as paragraph (a)(1)(iii), and new paragraph (a)(1)(ii) is added;</AMDPAR>
                    <AMDPAR>c. Newly redesignated paragraph (a)(1)(iii) is revised;</AMDPAR>
                    <AMDPAR>d. Paragraph (a)(2)(iv) is revised;</AMDPAR>
                    <AMDPAR>e. Paragraph (b)(2)(i) is revised;</AMDPAR>
                    <AMDPAR>f. Paragraph (b)(4) is revised; and</AMDPAR>
                    <AMDPAR>g. Paragraph (c)(2) is revised.</AMDPAR>
                    <P>The revisions and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 241.3 </SECTNO>
                        <SUBJECT>Discontinuance of USPS-operated retail facilities.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>(1) * * *</P>
                        <P>(i) * * *</P>
                        <P>(B) Combine a USPS-operated Post Office, station, or branch with another USPS-operated retail facility, or </P>
                        <P>(ii) The conversion of a Post Office into, or the replacement of a Post Office with, another type of USPS-operated retail facility is not a discontinuance action subject to this section. A change in the staffing of a Post Office such that it is staffed only part-time by a postmaster, or not staffed at all by a postmaster, but rather by another type of USPS employee, is not a discontinuance action subject to this section.</P>
                        <P>(iii) The regulations in this section are mandatory only with respect to discontinuance actions for which initial feasibility studies have been initiated on or after July 14, 2011. Unless otherwise provided by responsible personnel, the rules under § 241.3 as in effect prior to July 14, 2011 shall apply to discontinuance actions for which initial feasibility studies have been initiated prior to July 14, 2011. Discontinuance actions pending as of December 1, 2011, that pertain to the conversion of a Post Office to another type of USPS-operated facility are no longer subject to these regulations.</P>
                        <P>(2) * * *</P>
                        <P>(iv) “Consolidation” means an action that converts a Postal Service-operated retail facility into a contractor-operated retail facility. The resulting contractor-operated retail facility reports to a Postal Service-operated retail facility.</P>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(2) * * *</P>
                        <P>(i) In a consolidation, the ZIP Code for the replacement contractor-operated retail facility is the ZIP Code originally assigned to the discontinued facility.</P>
                        <STARS/>
                        <P>
                            (4) 
                            <E T="03">Name of facility established by consolidation.</E>
                             If a USPS-operated retail facility is consolidated by establishing in its place a contractor-operated facility, the replacement unit can be given the same name of the facility that is replaced, if appropriate in light of the nature of the contract and level of service provided.
                        </P>
                        <P>(c) * * *</P>
                        <P>
                            (2) 
                            <E T="03">Consolidation.</E>
                             The proposed action may include a consolidation of USPS-operated retail facilities. A consolidation arises when a USPS-operated retail facility is replaced with a contractor-operated retail facility.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <NAME>Stanley F. Mires,</NAME>
                    <TITLE>Attorney, Legal Policy and Legislative Advice.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27641 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-12-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <CFR>40 CFR Part 180</CFR>
                <DEPDOC>[EPA-HQ-OPP-2009-0538; FRL-8891-3]</DEPDOC>
                <SUBJECT>Bacteriophage of Clavibacter Michiganensis Subspecies Michiganensis; Exemption From the Requirement of a Tolerance</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This regulation establishes an exemption from the requirement of a tolerance for residues of lytic bacteriophage of Clavibacter michiganensis subspecies michiganensis produced in Clavibacter michiganensis subspecies michiganensis in or on tomato when applied as a bactericide in accordance with good agricultural practices. On behalf of OmniLytics, Inc., Interregional Research Project Number 4 (IR-4) submitted a petition to EPA under the Federal Food, Drug, and Cosmetic Act (FFDCA) requesting an exemption from 
                        <PRTPAGE P="66188"/>
                        the requirement of a tolerance. This regulation eliminates the need to establish a maximum permissible level for residues of lytic bacteriophage of Clavibacter michiganensis subspecies michiganensis produced in Clavibacter michiganensis subspecies michiganensis under the FFDCA.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        This regulation is effective October 26, 2011. Objections and requests for hearings must be received on or before December 27, 2011, and must be filed in accordance with the instructions provided in 40 CFR part 178 (see also Unit I.C. of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                        ).
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        EPA has established a docket for this action under docket identification (ID) number EPA-HQ-OPP-2009-0538. All documents in the docket are listed in the docket index available at 
                        <E T="03">http://www.regulations.gov.</E>
                         Although listed in the index, some information is not publicly available, 
                        <E T="03">e.g.,</E>
                         Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, is not placed on the Internet and will be publicly available only in hard copy form. Publicly available docket materials are available in the electronic docket at 
                        <E T="03">http://www.regulations.gov,</E>
                         or, if only available in hard copy, at the Office of Pesticide Programs (OPP) Regulatory Public Docket in Rm. S-4400, One Potomac Yard (South Bldg.), 2777 S. Crystal Dr., Arlington, VA. The Docket Facility is open from 8:30 a.m. to 4 p.m., Monday through Friday, excluding legal holidays. The Docket Facility telephone number is (703) 305-5805.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Denise Greenway, Biopesticides and Pollution Prevention Division (7511P), Office of Pesticide Programs, Environmental Protection Agency, 1200 Pennsylvania Ave., NW., Washington, DC 20460-0001; 
                        <E T="03">telephone number:</E>
                         (703) 308-8263; 
                        <E T="03">e-mail address: greenway.denise@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">I. General Information</HD>
                <HD SOURCE="HD2">A. Does this action apply to me?</HD>
                <P>You may be potentially affected by this action if you are an agricultural producer, food manufacturer, or pesticide manufacturer. Potentially affected entities may include, but are not limited to:</P>
                <P>• Crop production (NAICS code 111).</P>
                <P>• Animal production (NAICS code 112).</P>
                <P>• Food manufacturing (NAICS code 311).</P>
                <P>• Pesticide manufacturing (NAICS code 32532).</P>
                <P>
                    This listing is not intended to be exhaustive, but rather provides a guide for readers regarding entities likely to be affected by this action. Other types of entities not listed in this unit could also be affected. The North American Industrial Classification System (NAICS) codes have been provided to assist you and others in determining whether this action might apply to certain entities. If you have any questions regarding the applicability of this action to a particular entity, consult the person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    .
                </P>
                <HD SOURCE="HD2">B. How can I get electronic access to other related information?</HD>
                <P>
                    You may access a frequently updated electronic version of 40 CFR part 180 through the Government Printing Office's e-CFR site at 
                    <E T="03">http://ecfr.gpoaccess.gov/cgi/t/text/text-idx?&amp;c=ecfr&amp;tpl=/ecfrbrowse/Title40/40tab_02.tpl.</E>
                </P>
                <HD SOURCE="HD2">C. How can I file an objection or hearing request?</HD>
                <P>Under FFDCA section 408(g), 21 U.S.C. 346a(g), any person may file an objection to any aspect of this regulation and may also request a hearing on those objections. You must file your objection or request a hearing on this regulation in accordance with the instructions provided in 40 CFR part 178. To ensure proper receipt by EPA, you must identify docket ID number EPA-HQ-OPP-2009-0538 in the subject line on the first page of your submission. All objections and requests for a hearing must be in writing, and must be received by the Hearing Clerk on or before December 27, 2011. Addresses for mail and hand delivery of objections and hearing requests are provided in 40 CFR 178.25(b).</P>
                <P>In addition to filing an objection or hearing request with the Hearing Clerk as described in 40 CFR part 178, please submit a copy of the filing that does not contain any CBI for inclusion in the public docket. Information not marked confidential pursuant to 40 CFR part 2 may be disclosed publicly by EPA without prior notice. Submit a copy of your non-CBI objection or hearing request, identified by docket ID number EPA-HQOPP-2009-0538, by one of the following methods:</P>
                <P>
                    • 
                    <E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>
                     Follow the on-line instructions for submitting comments.
                </P>
                <P>
                    • 
                    <E T="03">Mail:</E>
                     OPP Regulatory Public Docket (7502P), Environmental Protection Agency, 1200 Pennsylvania Ave., NW., Washington, DC 20460-0001.
                </P>
                <P>
                    • 
                    <E T="03">Delivery:</E>
                     OPP Regulatory Public Docket (7502P), Environmental Protection Agency, Rm. S-4400, One Potomac Yard (South Bldg.), 2777 S. Crystal Dr., Arlington, VA. Deliveries are only accepted during the Docket Facility's normal hours of operation (8:30 a.m. to 4 p.m., Monday through Friday, excluding legal holidays). Special arrangements should be made for deliveries of boxed information. The Docket Facility telephone number is (703) 305-5805.
                </P>
                <HD SOURCE="HD1">II. Background and Statutory Findings</HD>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of September 23, 2009 (74 FR 48556) (FRL-8434-7), EPA issued a notice pursuant to section 408(d)(3) of FFDCA, 21 U.S.C. 346a(d)(3), announcing the filing of a pesticide tolerance petition (PP 9E7552) by IR-4, Rutgers University, 500 College Rd. East, Suite 201W, Princeton, NJ 08540 (on behalf of OmniLytics, Inc., 9100 South 500 West, Sandy, UT 84070). The petition requested that 40 CFR part 180 be amended by establishing an exemption from the requirement of a tolerance for residues of bacteriophage of Clavibacter michiganensis subspecies michiganensis. This notice referenced a summary of the petition prepared by the petitioner, IR-4, which is available in the docket via 
                    <E T="03">http://www.regulations.gov.</E>
                     There were no comments received in response to the notice of filing.
                </P>
                <P>
                    Section 408(c)(2)(A)(i) of FFDCA allows EPA to establish an exemption from the requirement for a tolerance (the legal limit for a pesticide chemical residue in or on a food) only if EPA determines that the exemption is “safe.” Section 408(c)(2)(A)(ii) of FFDCA defines “safe” to mean that “there is a reasonable certainty that no harm will result from aggregate exposure to the pesticide chemical residue, including all anticipated dietary exposures and all other exposures for which there is reliable information.” This includes exposure through drinking water and in residential settings but does not include occupational exposure. Pursuant to section 408(c)(2)(B) of FFDCA, in establishing or maintaining in effect an exemption from the requirement of a tolerance, EPA must take into account the factors set forth in section 408(b)(2)(C) of FFDCA, which require EPA to give special consideration to exposure of infants and children to the pesticide chemical residue in establishing a tolerance exemption and to “ensure that there is a reasonable certainty that no harm will result to infants and children from aggregate 
                    <PRTPAGE P="66189"/>
                    exposure to the pesticide chemical residue. * * *”
                </P>
                <P>Additionally, section 408(b)(2)(D) of FFDCA requires that EPA consider “available information concerning the cumulative effects of [a particular pesticide's] * * * residues and other substances that have a common mechanism of toxicity.”</P>
                <P>EPA performs a number of analyses to determine the risks from aggregate exposure to pesticide residues. First, EPA determines the toxicity of pesticides. Second, EPA examines exposure to the pesticide through food, drinking water, and through other exposures that occur as a result of pesticide use in residential settings.</P>
                <HD SOURCE="HD1">III. Toxicological Profile</HD>
                <P>Consistent with section 408(b)(2)(D) of FFDCA, EPA has reviewed the available scientific data and other relevant information in support of this action and considered its validity, completeness, and reliability and the relationship of this information to human risk. EPA has also considered available information concerning the variability of the sensitivities of major identifiable subgroups of consumers, including infants and children.</P>
                <HD SOURCE="HD2">A. Bacteriophage Overview</HD>
                <P>Bacteriophage, the most abundant group of biological entities on the planet, are naturally occurring viruses that are found in soil and water and in association with plants and animals, including humans (Refs. 1 through 8). Bacteriophage are obligate parasites of bacteria, which means they attach to, infect, and reproduce in bacteria, and are host-specific for bacteria, with specific bacteriophage attacking only one bacterial species and most frequently only one strain within a bacterial species (Refs. 9 through 11). As such, bacteriophage do not attack other beneficial bacteria. In addition, there is no evidence for bacteriophage infecting any other life form, including humans, except bacteria (Refs. 7, 12, and 13). Humans and other animals commonly consume bacteriophage as they are abundantly found in water, on plant surfaces, and in foods such as ground beef, pork sausage, chicken, oysters, cheese, mushrooms, and broccoli (Refs. 3, 4, and 14 through 19). In addition, bacteriophage are common commensals of the human gut and likely play an important role in regulating populations of various bacteria in the gastrointestinal tract (Ref. 7). As cited in public literature, bacteriophage have been used for more than 80 years as therapeutic agents with no ill effects and are active against bacteria that cause many infections and human diseases (Refs. 7, 20, and 21).</P>
                <P>
                    Since 2005, bacteriophage have also been used in a pesticide product (Agriphage; EPA Reg. No. 67986-1), without reported incidents, to control particular bacterial diseases (Xanthomonas campestris pv. vesicatoria and Pseduomonas syringae pv. tomato) of tomato and pepper. In conjunction with registration of the aforementioned pesticide product, EPA established an exemption from the requirement of a tolerance for residues of bacteriophage of Xanthomonas campestris pv. vesicatoria and Pseudómonas syringae pv. tomato in or on tomato and pepper (see the 
                    <E T="04">Federal Register</E>
                     of December 28, 2005 (70 FR 76704) (FRL-7753-6)). Much like the previously registered bacteriophage, OmniLytics, Inc. is proposing that bacteriophage of Clavibacter michiganensis subspecies michiganensis be applied as a pesticide for a very limited use-to control bacterial canker disease on tomato.
                </P>
                <HD SOURCE="HD2">B. Microbial Pesticide Toxicology Data Requirements</HD>
                <P>All mammalian toxicology data requirements supporting the request for an exemption from the requirement of a tolerance for residues of bacteriophage of Clavibacter michiganensis subspecies michiganensis in or on tomato have been fulfilled with submission of valid studies from the public literature (Refs. 22 and 23).</P>
                <P>
                    As mentioned in Unit III.A., bacteriophage are viruses that only infect specific bacteria, a basic fact supported by both information presented in public literature and the absence of reported adverse effects to humans even with commonplace exposure to bacteriophage. Literature submitted established that bacteriophage have been used historically and through modern times in lieu of or to assist the action of antibiotics. Clinical uses encompass all manner of administration from injection/intravenous and surgical wound applications to topical and ingestible preparations. There have been no reports of adverse effects from such administrations and in other similar cases using controlled scientific studies. Also submitted were literature citations showing that bacteriophage are common and abundant in soils, are in a wide range of plant materials, and are generally present in high numbers in the environment (
                    <E T="03">e.g.,</E>
                     up to 1010 plaque-forming units (PFU) per liter may be found in non-polluted waters). Yet again, no adverse effects to humans have been reported with these types of potential exposure. Moreover, bacteriophage presence reported in foods and feeds ranges from 101 to 105 PFU/100 grams (g) of meat and up to 107 PFU/100 g of cheese without any known harmful effects after consumption of such materials. Finally, the petitioner noted that, during an extensive history of bacteriophage laboratory and pesticidal usage, adverse reports in the literature have not been documented and episodes of hypersensitivity have not occurred.
                </P>
                <P>Because bacteriophage are obligate bacterial parasites and are not known to infect humans, the only human health risk associated with use of bacteriophage of Clavibacter michiganensis subspecies michiganensis as a bactericide is potential for acquisition and production of microbial toxins. This acquisition occurs through lysogeny, which is when bacteriophage integrate into the genome of toxigenic bacterial host strains and pick up and transmit those genetic traits to other bacteria that otherwise would not produce toxic substances. Therefore, bacteriophage of Clavibacter michiganensis subspecies michiganensis that meet the following two conditions do not present this risk issue:</P>
                <P>1. Bacteriophage produced in Clavibacter michiganensis subspecies michiganensis, which has been sequenced and determined to be an atoxigenic host bacteria, and</P>
                <P>
                    2. Bacteriophage possessing the capability to lyse host bacteria, 
                    <E T="03">i.e.,</E>
                     completely destroy host cells during the viral production process, which precludes genetic transfer of possible toxins to other bacteria (Ref. 22).
                </P>
                <HD SOURCE="HD1">IV. Aggregate Exposure</HD>
                <P>In examining aggregate exposure, section 408 of FFDCA directs EPA to consider available information concerning exposures from the pesticide residue in food and all other non-occupational exposures, including drinking water from ground water or surface water and exposure through pesticide use in gardens, lawns, or buildings (residential and other indoor uses).</P>
                <HD SOURCE="HD2">A. Dietary Exposure</HD>
                <P>
                    <E T="03">1. Food exposure.</E>
                     Published literature submitted by the petitioner, as well as other publicly available literature, indicate that bacteriophage are commonly associated with food and are therefore regularly consumed by humans. According to Ackermann (1997), these viruses have been found in association with “buds, leaves, root nodules (leguminous plants), roots, 
                    <PRTPAGE P="66190"/>
                    rotting fruit, seeds, stems, and straw; crown gall tumors * * * healthy or diseased alfalfa, barley, beans, broccoli, Brussels sprouts, buckwheat, clover, cotton, cucumber, lucerne, mulberry, oats, peas, peach trees, radish, rutabaga, ryegrass, rye, timothy, tobacco, tomatoes, [and] wheat” (Ref. 14). Moreover, bacteriophage have been isolated from a wide range of food products, including ground beef, pork sausage, chicken, farmed freshwater fish, common carp, marine fish, oil sardines, raw skim milk, and cheese (Refs. 15, 16, and 24 through 27). In fact, several studies have suggested that 100% of the ground beef and chicken meat sold at retail stores contain various levels of bacteriophage. For instance, bacteriophage were recovered from 100% of examined fresh chicken and pork sausage samples and from 33% of delicatessen meat samples analyzed; the levels ranged from 3.3 × 1010 to 4.4 × 1010 PFU/100 g of fresh chicken, up to 3.5 × 1010 PFU/100 g of fresh pork, and up to 2.7 × 1010 PFU/100 g of roast turkey breast samples (Ref 16). Other studies similarly showed the widespread occurrence of bacteriophage in certain foods:
                </P>
                <P>a. 38 bacteriophage-host systems were isolated from 22 of 45 refrigerated products (Ref 27);</P>
                <P>b. Bacteriophage infecting fire blight pathogen (Erwinia amylovora) were isolated from apple, pear, and raspberry tissues and from soil samples collected at sites displaying fire blight symptoms (Ref 5); and</P>
                <P>c. Shellfish, which filter large quantities of seawater, concentrated both bacteria and bacteriophage (Ref 6).</P>
                <P>Because lytic bacteriophage of Clavibacter michiganensis subspecies michiganensis produced in Clavibacter michiganensis subspecies michiganensis are intended to be applied to tomatoes, it is likely that dietary exposure will occur; however, no adverse effects are expected to occur. Despite constant and direct food exposure to bacteriophage (examples provided in the preceding paragraph and in Unit III.), no adverse effects to humans have been reported in publicly available literature. Indeed, no such effects are expected given that bacteriophage, including the one at issue in this action, are not capable of infecting eukaryotic cells and are host specific, attacking only bacteria.</P>
                <P>
                    <E T="03">2. Drinking water exposure.</E>
                     Published literature submitted by the petitioner, as well as other publicly available literature, indicate that, much like food, bacteriophage are commonly associated with water and are therefore regularly consumed by humans. According to Demuth 
                    <E T="03">et al.</E>
                     (1993), “Bacteriophage * * * have been isolated from all types of bacteria and from virtually any aquatic or terrestrial habitat where bacteria can exist. However, only in the last few years has it been recognized that viruses (phage) are extremely abundant in ocean and fresh water and may exceed the concentration of bacteria by up to 100-fold” (Ref. 3). Other studies showed that bacteriophage of Erwinia carotovora and Erwinia ananas were isolated from certain freshwater lakes in Florida and Texas (Ref. 4) and that coliphage were present in some samples of drinking water (Ref 28).
                </P>
                <P>
                    When lytic bacteriophage of Clavibacter michiganensis subspecies michiganensis produced in Clavibacter michiganensis subspecies michiganensis are applied to tomato as a bactericide in accordance with good agricultural practices, exposure of humans to residues of these bacteriophage in consumed drinking water may occur. Although lytic bacteriophage of Clavibacter michiganensis subspecies michiganensis produced in Clavibacter michiganensis subspecies michiganensis are not expected to reach surface water because the proposed use patterns do not include direct application to aquatic sites, it is possible that this microbial pest control agent could make it into ground water. Nonetheless, if oral exposure to lytic bacteriophage of Clavibacter michiganensis subspecies michiganensis produced in Clavibacter michiganensis subspecies michiganensis occurs through consumed drinking water (
                    <E T="03">e.g.,</E>
                     due to surface water contamination by microbial pesticide spray drift or runoff or contact with ground water), for the many reasons enumerated in Unit III. and Unit IV.A.1., EPA concludes there is reasonable certainty that this type of drinking water exposure, or any level of drinking water exposure for that matter, will not result in harm to humans.
                </P>
                <HD SOURCE="HD2">B. Other Non-Occupational Exposure</HD>
                <P>
                    Dermal and inhalation non-occupational exposures to lytic bacteriophage of Clavibacter michiganensis subspecies michiganensis produced in Clavibacter michiganensis subspecies michiganensis are not expected as all proposed pesticide applications will take place in distinct agricultural settings. Even if dermal and inhalation non-occupational exposures were to occur inadvertently (
                    <E T="03">e.g.,</E>
                     through spray drift) or due to an eventual expansion of use sites, such exposures would not be of concern given the information presented in Unit III. and Unit IV.A.
                </P>
                <HD SOURCE="HD1">V. Cumulative Effects From Substances With a Common Mechanism of Toxicity</HD>
                <P>Section 408(b)(2)(D)(v) of FFDCA requires that, when considering whether to establish, modify, or revoke a tolerance exemption, EPA consider “available information concerning the cumulative effects of [a particular pesticide's] * * * residues and other substances that have a common mechanism of toxicity.”</P>
                <P>
                    EPA has not found lytic bacteriophage of Clavibacter michiganensis subspecies michiganensis produced in Clavibacter michiganensis subspecies michiganensis to share a common mechanism of toxicity with any other substances, and lytic bacteriophage of Clavibacter michiganensis subspecies michiganensis produced in Clavibacter michiganensis subspecies michiganensis do not appear to produce a toxic metabolite against the target pest. For the purposes of this tolerance action, therefore, EPA has assumed that lytic bacteriophage of Clavibacter michiganensis subspecies michiganensis produced in Clavibacter michiganensis subspecies michiganensis do not have a common mechanism of toxicity with other substances. Therefore, section 408(b)(2)(D)(v) of the FFDCA does not apply. For information regarding EPA's efforts to determine which chemicals have a common mechanism of toxicity and to evaluate the cumulative effects of such chemicals, see EPA's Web site at 
                    <E T="03">http://www.epa.gov/pesticides/cumulative.</E>
                </P>
                <HD SOURCE="HD1">VI. Determination of Safety for United States (U.S.) Population, Infants and Children</HD>
                <P>
                    FFDCA section 408(b)(2)(C) provides that EPA shall assess the available information about consumption patterns among infants and children, special susceptibility of infants and children to pesticide chemical residues, and the cumulative effects on infants and children of the residues and other substances with a common mechanism of toxicity. In addition, FFDCA section 408(b)(2)(C) provides that EPA shall apply an additional tenfold (10×) margin of safety for infants and children in the case of threshold effects to account for prenatal and postnatal toxicity and the completeness of the database on toxicity and exposure unless EPA determines that a different margin of safety will be safe for infants and children. This additional margin of safety is commonly referred to as the Food Quality Protection Act Safety Factor. In 
                    <PRTPAGE P="66191"/>
                    applying this provision, EPA either retains the default value of 10× or uses a different additional safety factor when reliable data available to EPA support the choice of a different factor.
                </P>
                <P>As previously discussed in Unit III. and Unit IV., humans, including infants and children, have been exposed to bacteriophage through food and water, where they are commonly found, and through decades of therapeutic use with no known or reported adverse effects. Based on this, as well as all the other reasons enumerated repeatedly in this unit, EPA concludes that there is a reasonable certainty that no harm will result to the U.S. population, including infants and children, from aggregate exposure to the residues of lytic bacteriophage of Clavibacter michiganensis subspecies michiganensis produced in Clavibacter michiganensis subspecies michiganensis. Such exposure includes all anticipated dietary exposures and all other exposures for which there is reliable information. EPA has arrived at this conclusion because, considered collectively, the public literature available on bacteriophage, including the one at issue in this action, do not demonstrate toxic, pathogenic, and/or infective potential to mammals. Thus, there are no threshold effects of concern and, as a result, an additional margin of safety is not necessary.</P>
                <HD SOURCE="HD1">VII. Other Considerations</HD>
                <HD SOURCE="HD2">A. Analytical Enforcement Methodology</HD>
                <P>An analytical method is not required for enforcement purposes for the reasons stated above and because EPA is establishing an exemption from the requirement of a tolerance without any numerical limitation.</P>
                <HD SOURCE="HD2">B. International Residue Limits</HD>
                <P>In making its tolerance decisions, EPA seeks to harmonize U.S. tolerances with international standards whenever possible, consistent with U.S. food safety standards and agricultural practices. In this context, EPA considers the international maximum residue limits (MRLs) established by the Codex Alimentarius Commission (Codex), as required by FFDCA section 408(b)(4). The Codex Alimentarius is a joint U.N. Food and Agriculture Organization/World Health Organization food standards program, and it is recognized as an international food safety standards-setting organization in trade agreements to which the United States is a party. EPA may establish a tolerance that is different from a Codex MRL; however, FFDCA section 408(b)(4) requires that EPA explain the reasons for departing from the Codex level.</P>
                <P>The Codex has not established a MRL for lytic bacteriophage of Clavibacter michiganensis subspecies michiganensis produced in Clavibacter michiganensis subspecies michiganensis.</P>
                <HD SOURCE="HD2">C. Revisions to Requested Exemption</HD>
                <P>In its petition, the petitioner requested generally that the Agency issue an exemption from the requirement of a tolerance for residues of bacteriophage of Clavibacter michiganensis subspecies michiganensis in or on tomato. The petitioner's supporting materials indicated that the actual pesticide that would be used would be safe because the bacteriophage were lytic and produced in Clavibacter michiganensis subspecies michiganensis. The Agency believes both that these two conditions are necessary to make the safety finding and the petitioner was only requesting a narrow exemption; therefore, the Agency is modifying the tolerance exemption regulatory text to include such criteria.</P>
                <HD SOURCE="HD1">VIII. Conclusions</HD>
                <P>EPA concludes that there is a reasonable certainty that no harm will result to the U.S. population, including infants and children, from aggregate exposure to residues of lytic bacteriophage of Clavibacter michiganensis subspecies michiganensis produced in Clavibacter michiganensis subspecies michiganensis. Therefore, an exemption from the requirement of a tolerance is established for residues of lytic bacteriophage of Clavibacter michiganensis subspecies michiganensis produced in Clavibacter michiganensis subspecies michiganensis in or on tomato when applied as a bactericide in accordance with good agricultural practices.</P>
                <HD SOURCE="HD1">IX. References</HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">
                        1. Keel C, Ucurum Z, Michaux P, Adrian M, Haas D. 2002. Deleterious impact of a virulent bacteriophage on survival and biocontrol activity of Pseudomonas fluorescens strain CHAO in natural soil. 
                        <E T="03">Molecular Plant-Microbe Interactions</E>
                         15:567-576.
                    </FP>
                    <FP SOURCE="FP-2">
                        2. Liew KW, Alvarez AM. 1981. Biological and morphological characterization of Xanthomonas campestris bacteriophages. 
                        <E T="03">Phytopatholoy</E>
                         71:269-273.
                    </FP>
                    <FP SOURCE="FP-2">
                        3. Demuth J, Neve H, Witzel K-P. 1993. Direct electron microscopy study on the morphological diversity of bacteriophage populations in Lake Plussse. 
                        <E T="03">Applied and Environmental Microbiology</E>
                         59:3378-3384.
                    </FP>
                    <FP SOURCE="FP-2">
                        4. Eayre CG, Bartz JA, Concelmo DE. 1995. Bacteriophages of Erwinia carotovora and Erwinia ananas isolated from freshwater lakes. 
                        <E T="03">Plant Disease</E>
                         79:801-804.
                    </FP>
                    <FP SOURCE="FP-2">
                        5. Schnabel EL, Jones AL. 2001. Isolation and characterization of five Erwinia amylovora bacteriophages and assessment of phage resistance in strains of Erwinia amylovora. 
                        <E T="03">Applied and Environmental Microbiology</E>
                         67:59-64.
                    </FP>
                    <FP SOURCE="FP-2">
                        6. Denis FA. 1975. Contamination of shellfish with strains of Pseudomonas aeruginosa and specific bacteriophages. 
                        <E T="03">Canadian Journal of Microbiology</E>
                         21:1055-1057.
                    </FP>
                    <FP SOURCE="FP-2">
                        7. Merril CR, Scholl D, Adhya SL. 2003. The prospect for bacteriophage therapy in Western medicine. 
                        <E T="03">Nature</E>
                         2:489-497.
                    </FP>
                    <FP SOURCE="FP-2">
                        8. Rohwer F. 2003. Global phage diversity. 
                        <E T="03">Cell</E>
                         113:1-2.
                    </FP>
                    <FP SOURCE="FP-2">
                        9. Stocker BAD. 1955. Bacteriophage and bacterial classification. 
                        <E T="03">Journal of General Microbiology</E>
                         12:375-381.
                    </FP>
                    <FP SOURCE="FP-2">
                        10. Duckworth DH, Gulig PA. 2002. Bacteriophage: potential treatment for bacterial infections. 
                        <E T="03">Biodrugs</E>
                         16:57-62.
                    </FP>
                    <FP SOURCE="FP-2">
                        11. Summers WC. 2001. Bacteriophage therapy. 
                        <E T="03">Annual Review of Microbiology</E>
                         55:437-451.
                    </FP>
                    <FP SOURCE="FP-2">
                        12. Lorch A. 1999. Bacteriophage: an alternative to antibiotics? 
                        <E T="03">Biotechnology and Development Monitor</E>
                         39:14-17.
                    </FP>
                    <FP SOURCE="FP-2">
                        13. Petricciani JC, Hsu TC, Stock AD, Turner JH, Wenger SL, Elisberg BL. 1978. Bacteriophages, vaccines, and people: an assessment of risk. 
                        <E T="03">Proceedings of the Society for Experimental Biology and Medicine.</E>
                         58:378-382.
                    </FP>
                    <FP SOURCE="FP-2">
                        14. Ackermann H-W. 1997. Bacteriophage ecology. Pp. 335-339 in: “
                        <E T="03">Progress in Microbial Ecology</E>
                         (Proceedings of Seventh International Symposium on Microbial Ecology)”. Martins MT, Sato MIZ, Tiedje JM, Hagler LCN, Döbereiner J, Sanchez PS, eds. Brazilian Society for Microbiology.
                    </FP>
                    <FP SOURCE="FP-2">
                        15. Kennedy JE Jr, Wei CI, Oblinger JL. 1986. Methodology for enumeration of coliphages in foods. 
                        <E T="03">Applied and Environmental Microbiology</E>
                         51:956-962.
                    </FP>
                    <FP SOURCE="FP-2">
                        16. Kennedy JE Jr, Oblinger JL, Bitton G. 1984. Recovery of coliphages from chicken, pork sausage and delicatessen meats. 
                        <E T="03">Journal of Food Protection</E>
                         47:623-626.
                    </FP>
                    <FP SOURCE="FP-2">
                        17. DePaola A, Motes ML, Chan AM, Suttle CA. 1998. Phages infecting Vibrio vulnificus are abundant and diverse in oysters (Crassostrea virginica) collected from the Gulf of Mexico. 
                        <E T="03">Applied and Environmental Microbiology</E>
                         64:346-351.
                    </FP>
                    <FP SOURCE="FP-2">
                        18. Quiberoni A, Tremblay D, Ackermann H-W, Moineau S, Reinheimer JA. 2006. Diversity of Streptococcus thermophilus phages in a large-production cheese factory in Argentina. 
                        <E T="03">Journal of Dairy Science</E>
                         89:3791-3799.
                    </FP>
                    <FP SOURCE="FP-2">
                        19. Guillaumes J, Houdeau G, Germain R, Olivier JM. 1988. Improvement of the biocontrol of Pseudomonas tolaasii using bacteriophages associated with an antagonistic bacterium. 
                        <E T="03">Bulletin OEPP</E>
                         18:77-82.
                    </FP>
                    <FP SOURCE="FP-2">
                        20. Radetsky P. 1996. The good virus. 
                        <E T="03">Discover</E>
                         17:50-58.
                    </FP>
                    <FP SOURCE="FP-2">
                        21. Chanishvili N, Chanishvili T, Tediashvili M, Barrow PA. 2001. Phages and their 
                        <PRTPAGE P="66192"/>
                        application against drug-resistant bacteria. 
                        <E T="03">Journal of Chemical Technology and Biotechnology</E>
                         76:689-699.
                    </FP>
                    <FP SOURCE="FP-2">22. U.S. EPA. 2011. Bacteriophage of Clavibacter michiganensis subsp. michiganensis—AgriPhage CMM. Memorandum from J.V. Gagliardi, Ph.D. to A. Gross dated June 30, 2011.</FP>
                    <FP SOURCE="FP-2">
                        23. U.S. EPA. 2011. Bacteriophage of Clavibacter michiganensis subspecies michiganensis Biopesticides Registration Action Document dated August 25, 2011 (available as “Supporting &amp; Related Material” with docket ID number EPA-HQ-OPP2009-0539 at 
                        <E T="03">http://www.regulations.gov</E>
                        ).
                    </FP>
                    <FP SOURCE="FP-2">
                        24. Atterbury RJ, Connerton PL, Dodd CER, Rees CED, Connerton IF. 2003. Isolation and characterization of Campylobacter bacteriophages from retail poultry. 
                        <E T="03">Applied and Environmental Microbiology</E>
                         69:4511-4518.
                    </FP>
                    <FP SOURCE="FP-2">
                        25. Gautier M, Rouault A, Sommer P, Briandet R. 1995. Occurrence of Propionibacterium freudenreichii bacteriophages in swiss cheese. 
                        <E T="03">Applied and Environmental Microbiology</E>
                         61:2572-2576.
                    </FP>
                    <FP SOURCE="FP-2">
                        26. Greer GG. 2005. Bacteriophage control of foodborne bacteria. 
                        <E T="03">Journal of Food Protection</E>
                         68:1102-1111.
                    </FP>
                    <FP SOURCE="FP-2">
                        27. Whitman PA, Marshall RT. 1971. Isolation of psychrophilic bacteriophagehost systems from refrigerated food products. 
                        <E T="03">Applied Microbiology</E>
                         22:220-223.
                    </FP>
                    <FP SOURCE="FP-2">
                        28. El-Abagy MM, Dutka BJ, Kamel M. 1988. Incidence of coliphage in potable water supplies. 
                        <E T="03">Applied and Environmental Microbiology</E>
                         54:1632-1633.
                    </FP>
                </EXTRACT>
                <HD SOURCE="HD1">X. Statutory and Executive Order Reviews</HD>
                <P>
                    This final rule establishes a tolerance exemption under section 408(d) of FFDCA in response to a petition submitted to EPA. The Office of Management and Budget (OMB) has exempted these types of actions from review under Executive Order 12866, entitled Regulatory Planning and Review (58 FR 51735, October 4, 1993). Because this final rule has been exempted from review under Executive Order 12866, this final rule is not subject to Executive Order 13211, entitled Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use (66 FR 28355, May 22, 2001), or Executive Order 13045, entitled Protection of Children from Environmental Health Risks and Safety Risks (62 FR 19885, April 23, 1997). This final rule does not contain any information collections subject to OMB approval under the Paperwork Reduction Act (PRA), 44 U.S.C. 3501 
                    <E T="03">et seq.,</E>
                     nor does it require any special considerations under Executive Order 12898, entitled Federal Actions to Address Environmental Justice in Minority Populations and Low-Income Populations (59 FR 7629, February 16, 1994).
                </P>
                <P>
                    Since tolerances and exemptions that are established on the basis of a petition under section 408(d) of FFDCA, such as the tolerance exemption in this final rule, do not require the issuance of a proposed rule, the requirements of the Regulatory Flexibility Act (RFA) (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ) do not apply.
                </P>
                <P>This final rule directly regulates growers, food processors, food handlers, and food retailers, not States or tribes. As a result, this action does not alter the relationships or distribution of power and responsibilities established by Congress in the preemption provisions of section 408(n)(4) of FFDCA. As such, EPA has determined that this action will not have a substantial direct effect on States or tribal governments, on the relationship between the national government and the States or tribal governments, or on the distribution of power and responsibilities among the various levels of government or between the Federal Government and Indian tribes. Thus, EPA has determined that Executive Order 13132, entitled Federalism (64 FR 43255, August 10, 1999), and Executive Order 13175, entitled Consultation and Coordination with Indian Tribal Governments (65 FR 67249, November 9, 2000), do not apply to this final rule. In addition, this final rule does not impose any enforceable duty or contain any unfunded mandate as described under Title II of the Unfunded Mandates Reform Act of 1995 (UMRA) (Pub. L. 104-4).</P>
                <P>This action does not involve any technical standards that would require EPA consideration of voluntary consensus standards pursuant to section 12(d) of the National Technology Transfer and Advancement Act of 1995 (NTTAA), Public Law 104-113, section 12(d) (15 U.S.C. 272 note).</P>
                <HD SOURCE="HD1">XI. Congressional Review Act</HD>
                <P>
                    The Congressional Review Act, 5 U.S.C. 801 
                    <E T="03">et seq.,</E>
                     generally provides that before a rule may take effect, the agency promulgating the rule must submit a rule report to each House of the Congress and to the Comptroller General of the United States. EPA will submit a report containing this rule and other required information to the U.S. Senate, the U.S. House of Representatives, and the Comptroller General of the United States prior to publication of this final rule in the 
                    <E T="04">Federal Register</E>
                    . This final rule is not a “major rule” as defined by 5 U.S.C. 804(2).
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 40 CFR Part 180</HD>
                    <P>Environmental protection, Administrative practice and procedure, Agricultural commodities, Pesticides and pests, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: September 30, 2011.</DATED>
                    <NAME>Steven Bradbury,</NAME>
                    <TITLE>Director, Office of Pesticide Programs.</TITLE>
                </SIG>
                <P>Therefore, 40 CFR chapter I is amended as follows:</P>
                <REGTEXT TITLE="40" PART="180">
                    <PART>
                        <HD SOURCE="HED">PART 180—[AMENDED]</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 180 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>21 U.S.C. 321(q), 346a and 371.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="40" PART="180">
                    <AMDPAR>2. Section 180.1307 is added to subpart D to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 180.1307</SECTNO>
                        <SUBJECT>Bacteriophage of Clavibacter michiganensis subspecies michiganensis; exemption from the requirement of a tolerance.</SUBJECT>
                        <P>An exemption from the requirement of a tolerance is established for residues of lytic bacteriophage of Clavibacter michiganensis subspecies michiganensis produced in Clavibacter michiganensis subspecies michiganensis in or on tomato when applied as a bactericide in accordance with good agricultural practices.</P>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27042 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <CFR>50 CFR Part 648</CFR>
                <DEPDOC>[Docket No. 101119575-1554-02]</DEPDOC>
                <RIN>RIN 0648-BA46</RIN>
                <SUBJECT>Fisheries of the Northeastern United States; Monkfish; Framework Adjustment 7</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This final rule implements measures that were approved in Framework Adjustment 7 to the Monkfish Fishery Management Plan. The New England Fishery Management Council and Mid-Atlantic Fishery Management Council developed Framework Adjustment 7 to adjust the annual catch target for the Northern Fishery Management Area to be consistent with the most recent 
                        <PRTPAGE P="66193"/>
                        scientific advice regarding the acceptable biological catch for monkfish. The New England Council's Scientific and Statistical Committee recommended a revision to the acceptable biological catch based on information from the 50th Northeast Regional Stock Assessment Review Committee. Framework Adjustment 7 specifies a new days-at-sea allocation and trip limits for the Northern Fishery Management Area consistent with the new annual catch target, and establishes revised biomass reference points for the Northern and Southern Fishery Management Areas.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective October 26, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        An environmental assessment (EA) was prepared for Framework Adjustment 7 (Framework 7) that describes the proposed action and other alternatives considered, and provides an analysis of the impacts of the proposed measures and alternatives. Copies of Framework 7, including the EA and the Initial Regulatory Flexibility Analysis (IRFA), are available on request from Paul J. Howard, Executive Director, New England Fishery Management Council (Council), 50 Water Street, Newburyport, MA 01950. These documents are also available online at 
                        <E T="03">http://www.nefmc.org.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jason Berthiaume, Fisheries Management Specialist, (978) 281-9177; 
                        <E T="03">fax:</E>
                         (978) 281-9135.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Background</HD>
                <P>The monkfish fishery is jointly managed by the New England and Mid-Atlantic Fishery Management Councils (Councils), with the New England Council having the administrative lead. The fishery extends from Maine to North Carolina, and is divided into two management units: The Northern Fishery Management Area (NFMA) and the Southern Fishery Management Area (SFMA). Details on the background and need for Amendment 5 and this framework are contained in the amendment and the preambles for the proposed (76 FR 11737; March 3, 2011) and final rules (76 FR 30265; May 25, 2011) for Amendment 5, and are not repeated here.</P>
                <P>Amendment 5, which was partially approved by NMFS on April 28, 2011, was intended to bring the Monkfish Fishery Management Plan (FMP) into compliance with the requirements of the reauthorized Magnuson-Stevens Fishery Conservation and Management Act (Magnuson-Stevens Act). The Magnuson-Stevens Act requires that all FMPs contain annual catch limits (ACL) to prevent overfishing, and measures to ensure accountability. Among other measures, Amendment 5 implemented accountability measures (AMs) and ACLs, established biological and management reference points and control rules, and specified an annual catch target (ACT), days-at-sea (DAS), and trip limits for the SFMA.</P>
                <P>However, NMFS disapproved the proposed ACT for the NFMA in Amendment 5, and specification of DAS and trip limits to achieve that ACT. Amendment 5 proposed an ACT for the NFMA of 10,750 mt, an allocation of 40 DAS, and trip limits of 1,250 lb (567 kg) tail wt. per DAS for Category A and C vessels, and 800 lb (363 kg) tail wt. per DAS for Category B and D vessels based on the 2007 Data Poor Working Group (DPWG) Assessment, which was considered to be the best scientific information available at the time the Amendment 5 document was finalized by the Councils. Subsequent to the Councils taking final action on Amendment 5, a 2010 stock assessment (50th Northeast Regional Stock Assessment Review Committee (SARC 50)) became available, which revealed new scientific information that, when included in the Councils' interim acceptable biological catch (ABC) approach, reduced the monkfish NFMA ABC. In response to the new assessment, the New England Council's Scientific and Statistical Committee (SSC) revisited its previous ABC recommendation at a meeting in August 2010. The SSC, after much discussion concerning the uncertainty with the new assessment and alternate methods for calculating ABC to account for this uncertainty, agreed to maintain the existing interim ABC approach it previously recommended. Using this interim ABC approach, the SSC recalculated the recommended ABC in Amendment 5 to incorporate the results of SARC 50. Based on the recalculation of the ABCs, the SFMA's ACT and associated DAS and trip limit measures were found to still be consistent with the new ABC and ACL, and they were approved by NMFS in Amendment 5. The recalculated ABC for the NFMA, on the other hand, was reduced from 10,750 mt to 7,592 mt, creating an inconsistency with the Amendment 5 recommended ABC, ACT, and associated NFMA DAS and trip limit measures. Based on this inconsistency, NMFS disapproved the Amendment 5 proposed specifications for the NFMA.</P>
                <P>This disapproval left current measures in effect for the NFMA until superseded by a revised ACT and specification of DAS and trip limits which is the purpose of this action. Because it was too late for the Councils to revise the Amendment 5 NFMA measures in a timely fashion for fishing year (FY) 2011, the Councils initiated Framework 7 in September 2010 to revise the ACT for the NFMA to be consistent with the most recent scientific advice. Leaving the current measures in place was considered an acceptable interim measure because they are more conservative than measures being implemented by this framework. This framework reconfirms the SFMA ABC and associated specifications and management measures that were approved and implemented through Amendment 5. This framework also updates the biomass reference points in the Monkfish FMP to be consistent with the results of SARC 50.</P>
                <HD SOURCE="HD1">Approved Measures</HD>
                <HD SOURCE="HD2">1. ACT</HD>
                <P>Framework 7 reduces the ACT for the NFMA to be consistent with the most recent scientific advice regarding the monkfish NFMA ABC. The SSC recommended a reduction of the NFMA ABC, based on SARC 50, to 7,592 mt. The ACT being implemented in this final rule is 86.5 percent of the ABC, or 6,567 mt. The ACT for the NFMA being implemented is slightly higher than the current total allowable landings (TAL) for the NFMA. Any landings that occur between when Amendment 5 was implemented on May 25, 2011, and the effective date of this final rule will be counted against the ACT for the current FY and will be used to determine whether AMs are triggered.</P>
                <HD SOURCE="HD2">2. Specification of DAS and Trip Limits</HD>
                <P>The DAS allocations and trip limits implemented in this action are calculated to achieve, but not go over, the ACT. The trip limits for the NFMA for permit categories A and C will be 1,250 lb (567 kg) tail weight, and 600 lb (272 kg) tail weight for permit categories B and D, with all categories having an initial DAS allocation of 40 DAS. After accounting for the Monkfish Research Set-Aside (RSA) program, the final allocation is 39.3 DAS.</P>
                <HD SOURCE="HD2">3. Revision to Biological Reference Points</HD>
                <P>
                    This action revises the biological reference points in the Monkfish FMP to be consistent with those recommended by the SSC and SARC 50. In the SARC 50 report, the Southern Demersal Working Group recommended an approach that would set biomass target reference points based on the long-term 
                    <PRTPAGE P="66194"/>
                    projected biomass (B) corresponding to the fishing mortality rate (F) at maximum sustainable yield, or its proxy, which for monkfish is F
                    <E T="52">max</E>
                    . This recommendation, along with the recommendation to set B threshold reference points at one-half of the target, is consistent with National Standard 1. The B
                    <E T="52">target</E>
                     under this recommendation is 52,930 mt for the NFMA and 74,490 mt for the SFMA, and B
                    <E T="52">threshold</E>
                     of 26,465 mt for the NFMA and 37,245 mt for the SFMA.
                </P>
                <HD SOURCE="HD3">Comments and Responses</HD>
                <P>The public comment period for the proposed rule ended on September 6, 2011. One comment was received.</P>
                <P>
                    <E T="03">Comment 1:</E>
                     The commenter suggested that all fishery quotas should be cut, based on the notion that coastal hypoxia was not considered when developing Framework 7.
                </P>
                <P>
                    <E T="03">Response:</E>
                     The commenter discussed coastal hypoxia at length, but did not explain how it relates to this rule and there is no known scientific basis for the commenter's suggestion. The reasons presented by the Council and NMFS for recommending the monkfish measures in this Framework are based on the best scientific information available, and are discussed in the preambles to both the proposed and final rule.
                </P>
                <HD SOURCE="HD3">Classification</HD>
                <P>Pursuant to section 304(b)(1)(A) of the Magnuson-Stevens Act, the NMFS Assistant Administrator has made a determination that this final rule is consistent with the Monkfish FMP, Framework 7, other provisions of the Magnuson-Stevens Act, and other applicable laws.</P>
                <P>Pursuant to the APA, 5 U.S.C. 553(d)(1), NMFS finds good cause to waive the 30-day delay in effectiveness of this rule. This final rule implements measures that are less restrictive than current regulations by increasing monkfish DAS allocations and trip limits for permit category B and D vessels in the NFMA. The increase in the DAS allocations and trip limits being implemented by this action are measures that were intended to be implemented with Amendment 5 on May 1, 2011 (start of the 2011 FY). However, while Amendment 5 was being finalized, new scientific information became available which resulted in the disapproval of the measures in Amendment 5 that modify the NFMA DAS and trip limits. Therefore, this action was adopted to implement less restrictive DAS and trip limits that were disapproved in Amendment 5.</P>
                <P>Moreover, the monkfish fishery is a seasonal fishery, with the majority of the fishing activity occurring in the spring and fall. Waiving the 30-day delay in effectiveness of this rule will allow vessels to immediately utilize the additional DAS and trip limits for a greater portion of the fall fishery than if the current and more restrictive regulations were in place for the 30-day delay in effectiveness period. Specifically, some vessels have already exhausted their DAS. Waiving the 30-day delayed effectiveness will provide more opportunities for these vessels to continue fishing in the fall fishery. A delay in effectiveness could result in unnecessary short-term adverse economic impacts to monkfish vessels and associated shoreside facilities and fishing communities. Lastly, in the recent past, the monkfish fishery has not been able to utilize its full ACT. It is expected that, with increased DAS allocation and trip limits being implemented with this action, the monkfish fishery will be able to more effectively utilize the ACT. Thus, a delay in effectiveness would be contrary to achieving optimum yield in the monkfish fishery, thereby undermining the purpose of this rulemaking.</P>
                <P>The Office of Management and Budget has determined that this rule is not significant for purposes of Executive Order 12866.</P>
                <P>
                    The New England Council prepared an EA for Framework 7 to the Monkfish FMP that discusses the impact on the environment as a result of this rule. A copy of the EA is available from the Council (see 
                    <E T="02">ADDRESSES</E>
                    ).
                </P>
                <P>
                    NMFS, pursuant to section 604 of the Regulatory Flexibility Act (RFA), has prepared a Final Regulatory Flexibility Analysis (FRFA) in support of Framework 7. The FRFA incorporates the IRFA, relevant analyses contained in the Framework and its EA, and a summary of the analyses completed to support the action in this rule. A copy of the analyses done in the Framework and EA is available from the Councils (see 
                    <E T="02">ADDRESSES</E>
                    ). A summary of the IRFA was published in the proposed rule for this action and is not repeated here. A description of why this action was considered, the objectives of, and the legal basis for this rule is contained in the preamble to the proposed rule and this final rule and is not repeated here.
                </P>
                <HD SOURCE="HD3">A Summary of the Significant Issues Raised by the Public in Response to the IRFA, a Summary of the Agency's Assessment of Such Issues, and a Statement of Any Changes Made in the Proposed Rule as a Result of Such Comments</HD>
                <P>No significant issues were raised by the public comment in response to the IRFA.</P>
                <P>For purposes of the IRFA, all of the entities (fishing vessels) affected by this action are considered small entities under the Small Business Administration size standards for small fishing businesses (less than $4.0 million in annual gross sales). Although multiple vessels may be owned by a single owner, tracking of ownership is not readily available to reliably ascertain affiliated entities. Therefore, for purposes of this analysis, each permitted vessel is treated as a single small business entity. Consequently, there are no differential impacts between large and small entities. Information on costs in the fishery is not readily available and individual vessel profitability cannot be determined directly; therefore, expected changes in gross revenues were used as a proxy for profitability.</P>
                <P>This action does not introduce any new reporting, recordkeeping, or other compliance requirements. This final rule does not duplicate, overlap, or conflict with other Federal rules.</P>
                <HD SOURCE="HD1">Description and Estimate of Number of Small Entities to Which the Final Rule Will Apply</HD>
                <P>The management measures in Framework 7 have the potential to affect all federally permitted monkfish vessels that are actively participating in the fishery. As of September 2009, there were 758 limited access monkfish permit holders and 2,156 open access permit holders. Of these, 573 limited access permit holders (76 percent) actively participated in the monkfish fishery during FY 2008, while only 504 open access permit holders (23 percent) actively participated in the fishery during that time period. Thus, this action is expected to impact at least 1,077 currently active monkfish permit holders, but have no impact on open access permit holders.</P>
                <P>
                    The majority of the measures in this action are specific to the NFMA, and, thus, will apply to vessels that fish primarily in the NFMA. Of the 546 vessels that participated in the fishery in FY 2009, 232 reported fishing in the NFMA. Of the 232, 115 reported fishing only in the NFMA and 171 in both the NFMA and SFMA. Accordingly, this 
                    <PRTPAGE P="66195"/>
                    action will most likely impact approximately 232 vessels that fish in the NFMA.
                </P>
                <HD SOURCE="HD1">Description of the Steps the Agency Has Taken To Minimize the Significant Economic Impact on Small Entities Consistent With the Stated Objectives of Applicable Statutes</HD>
                <P>All of the management measures contained in Framework 7 and implemented in this final rule either provide for increased fishing opportunities or increased efficiency and profitability. This action increases fishing opportunities by raising the overall annual DAS allocations for all limited access monkfish vessels from 31 DAS to 40 DAS, prior to adjusting the DAS allocation for the Monkfish RSA program. Although the DAS usage cap for the SFMA remains at 28 DAS, the NFMA DAS increase provides additional fishing opportunities for vessels that fish primarily in the NFMA, vessels that fish in both the NFMA and SFMA, and vessels that fish primarily in the SFMA that may also wish to pursue fishing opportunities in the NFMA. Previously, vessels that fished primarily in the SFMA who utilized the maximum 28 SFMA DAS would otherwise have 3 DAS remaining that could only be used in the NFMA. With this action, these vessels will now have 12 DAS available for use in the NFMA prior to adjusting the DAS allocation for the Monkfish RSA program, which may provide opportunities for these vessels to also participate in the NFMA fishery as well as the SFMA fishery.</P>
                <P>In regards to increased efficiency and profitability, this action increases the NFMA ACT. Assuming that prices do not decrease due to higher landings, a higher ACT would result in higher monkfish revenues and thus additional benefits to vessels. However, this is only the case if the higher allocation is actually landed. To achieve the higher ACT, this action also raises the trip limits for permit Category B and D vessels from 470 lb (213 kg) to 600 lb (272 kg) tail weight. This increase allows Category B and D vessels fishing in the NFMA to land more monkfish than previously authorized, which could increase vessel efficiency and profitability, as well as reducing any regulatory discards.</P>
                <HD SOURCE="HD3">Small Entity Compliance Guide</HD>
                <P>
                    Section 212 of the Small Business Regulatory Enforcement Fairness Act of 1996 states that, for each rule or group of related rules for which an agency is required to prepare a FRFA, the agency shall publish one or more guides to assist small entities in complying with the rule, and shall designate such publications as “small entity compliance guides.” The agency shall explain the actions a small entity is required to take to comply with a rule or group of rules. As part of this rulemaking process, a letter to permit holders that also serves as small entity compliance guide (the guide) was prepared. Copies of this final rule are available from the NMFS Northeast Regional Office, and the guide, 
                    <E T="03">i.e.,</E>
                     permit holder letter, will be sent to all holders of permits for the monkfish fishery. The guide and this final rule will be available upon request, and posted on the Northeast Regional Office's Web site at 
                    <E T="03">http://www.nero.noaa.gov.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 50 CFR Part 648</HD>
                    <P>Fisheries, Fishing, Recordkeeping and reporting requirements.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: October 19, 2011.</DATED>
                    <NAME>Samuel D. Rauch III,</NAME>
                    <TITLE>Deputy Assistant Administrator for Regulatory Programs, National Marine Fisheries Service.</TITLE>
                </SIG>
                <P>For the reasons set out in the preamble, 50 CFR part 648 is amended as follows:</P>
                <REGTEXT TITLE="50" PART="648">
                    <PART>
                        <HD SOURCE="HED">PART 648—FISHERIES OF THE NORTHEASTERN UNITED STATES</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 648 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                             16 U.S.C. 1801 
                            <E T="03">et seq.</E>
                        </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="50" PART="648">
                    <AMDPAR>2. In § 648.92, revise paragraph (b)(1)(i) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 648.92 </SECTNO>
                        <SUBJECT>Effort-control program for monkfish limited access vessels.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(1) * * *</P>
                        <P>
                            (i) 
                            <E T="03">General provision.</E>
                             Limited access monkfish permit holders shall be allocated 40 monkfish DAS each fishing year to be used in accordance with the restrictions of this paragraph (b), unless otherwise restricted by paragraph (b)(1)(ii) of this section or modified by § 648.96(b)(3), or unless the vessel is enrolled in the Offshore Fishery Program in the SFMA, as specified in paragraph (b)(1)(iv) of this section. The annual allocation of monkfish DAS shall be reduced by the amount calculated in paragraph (b)(1)(v) of this section for the research DAS set-aside. Limited access NE multispecies and limited access sea scallop permit holders who also possess a limited access monkfish permit must use a NE multispecies or sea scallop DAS concurrently with each monkfish DAS utilized, except as provided in paragraph (b)(2) of this section, unless otherwise specified under this subpart F.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="50" PART="648">
                    <AMDPAR>3. In § 648.94, revise paragraph (b)(1)(ii) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 648.94 </SECTNO>
                        <SUBJECT>Monkfish possession and landing restrictions.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(1) * * *</P>
                        <P>
                            (ii) 
                            <E T="03">Category B and D vessels.</E>
                             Limited access monkfish Category B and D vessels that fish under a monkfish DAS exclusively in the NFMA may land up to 600 lb (272 kg) tail weight or 1,746 lb (792 kg) whole weight of monkfish (gutted) per DAS (or any prorated combination of tail weight and whole weight based on the conversion factor for tail weight to whole weight of 2.91). For every 1 lb (0.45 kg) of tail only weight landed, the vessel may land up to 1.91 lb (0.87 kg) of monkfish heads only, as described in paragraph (a) of this section.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27723 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <CFR>50 CFR Part 679</CFR>
                <DEPDOC>[Docket No. 101126521-0640-02]</DEPDOC>
                <RIN>RIN 0648-XA791</RIN>
                <SUBJECT>Fisheries of the Exclusive Economic Zone Off Alaska; Pacific Cod by Catcher/Processors Using Pot Gear in the Bering Sea and Aleutian Islands Management Area</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary rule; closure.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NMFS is prohibiting directed fishing for Pacific cod by pot catcher/processors in the Bering Sea and Aleutian Islands management area (BSAI). This action is necessary to prevent exceeding the 2011 Pacific cod total allowable catch (TAC) specified for pot catcher/processors in the BSAI.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective 1200 hrs, Alaska local time (A.l.t.), October 23, 2011, through 1200 hrs, A.l.t., December 31, 2011.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Obren Davis, 907-586-7228.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    NMFS manages the groundfish fishery in the 
                    <PRTPAGE P="66196"/>
                    BSAI exclusive economic zone according to the Fishery Management Plan for Groundfish of the Bering Sea and Aleutian Islands Management Area (FMP) prepared by the North Pacific Fishery Management Council under authority of the Magnuson-Stevens Fishery Conservation and Management Act. Regulations governing fishing by U.S. vessels in accordance with the FMP appear at subpart H of 50 CFR part 600 and 50 CFR part 679.
                </P>
                <P>The 2011 Pacific cod TAC allocated as a directed fishing allowance to pot catcher/processors in the BSAI is 3,041 metric tons as established by the final 2011 and 2012 harvest specifications for groundfish in the BSAI (76 FR 11139, March 1, 2011).</P>
                <P>In accordance with § 679.20(d)(1)(iii), the Administrator, Alaska Region, NMFS, has determined that the 2011 Pacific cod TAC allocated as a directed fishing allowance to pot catcher/processors in the BSAI has been reached. Consequently, NMFS is prohibiting directed fishing for Pacific cod by pot catcher/processors in the BSAI.</P>
                <P>After the effective date of this closure the maximum retainable amounts at § 679.20(e) and (f) apply at any time during a trip.</P>
                <HD SOURCE="HD1">Classification</HD>
                <P>This action responds to the best available information recently obtained from the fishery. The Assistant Administrator for Fisheries, NOAA (AA), finds good cause to waive the requirement to provide prior notice and opportunity for public comment pursuant to the authority set forth at 5 U.S.C. 553(b)(B) as such requirement is impracticable and contrary to the public interest. This requirement is impracticable and contrary to the public interest as it would prevent NMFS from responding to the most recent fisheries data in a timely fashion and would delay the closure of Pacific cod by pot catcher/processors in the BSAI. NMFS was unable to publish a notice providing time for public comment because the most recent, relevant data only became available as of October 20, 2011.</P>
                <P>The AA also finds good cause to waive the 30-day delay in the effective date of this action under 5 U.S.C. 553(d)(3). This finding is based upon the reasons provided above for waiver of prior notice and opportunity for public comment.</P>
                <P>This action is required by § 679.20 and is exempt from review under Executive Order 12866.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>
                        16 U.S.C. 1801 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: October 21, 2011.</DATED>
                    <NAME>Alan D. Risenhoover,</NAME>
                    <TITLE>Acting Director, Office of Sustainable Fisheries, National Marine Fisheries Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27714 Filed 10-21-11; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <CFR>50 CFR Part 679</CFR>
                <DEPDOC>[Docket No. 101126522-0640-02]</DEPDOC>
                <RIN>RIN 0648-XA790</RIN>
                <SUBJECT>Fisheries of the Exclusive Economic Zone Off Alaska; Pacific Cod by Vessels Harvesting Pacific Cod for Processing by the Inshore Component in the Western Regulatory Area of the Gulf of Alaska</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary rule; closure.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NMFS is prohibiting directed fishing for Pacific cod by vessels harvesting Pacific cod for processing by the inshore component in the Western Regulatory Area of the Gulf of Alaska (GOA). This action is necessary to prevent exceeding the 2011 Pacific total allowable catch (TAC) apportioned to vessels harvesting Pacific cod for processing by the inshore component of the Western Regulatory Area of the GOA.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective 1200 hrs, Alaska local time (A.l.t.), October 26, 2011, through 2400 hrs, A.l.t., December 31, 2011.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Josh Keaton, 907-586-7228.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>NMFS manages the groundfish fishery in the GOA exclusive economic zone according to the Fishery Management Plan for Groundfish of the Gulf of Alaska (FMP) prepared by the North Pacific Fishery Management Council under authority of the Magnuson-Stevens Fishery Conservation and Management Act. Regulations governing fishing by U.S. vessels in accordance with the FMP appear at subpart H of 50 CFR part 600 and 50 CFR part 679. Regulations governing sideboard protections for GOA groundfish fisheries appear at subpart B of 50 CFR part 680.</P>
                <P>The 2011 Pacific cod TAC apportioned to vessels harvesting Pacific cod for processing by the inshore component of the Western Regulatory Area of the GOA is 20,507 metric tons (mt), as established by the final 2011 and 2012 harvest specifications for groundfish of the GOA (76 FR 11111, March 1, 2011).</P>
                <P>In accordance with § 679.20(d)(1)(i), the Administrator, Alaska Region, NMFS (Regional Administrator) has determined that the 2011 Pacific cod TAC apportioned to vessels harvesting Pacific cod for processing by the inshore component of the Western Regulatory Area of the GOA will soon be reached. Therefore, the Regional Administrator is establishing a directed fishing allowance of 20,257 mt, and is setting aside the remaining 250 mt as bycatch to support other anticipated groundfish fisheries. In accordance with § 679.20(d)(1)(iii), the Regional Administrator finds that this directed fishing allowance has been reached. Consequently, NMFS is prohibiting directed fishing for Pacific cod by vessels harvesting Pacific cod for processing by the inshore component in the Western Regulatory Area of the GOA.</P>
                <P>After the effective date of this closure the maximum retainable amounts at § 679.20(e) and (f) apply at any time during a trip.</P>
                <HD SOURCE="HD1">Classification</HD>
                <P>This action responds to the best available information recently obtained from the fishery. The Assistant Administrator for Fisheries, NOAA (AA), finds good cause to waive the requirement to provide prior notice and opportunity for public comment pursuant to the authority set forth at 5 U.S.C. 553(b)(B) as such requirement is impracticable and contrary to the public interest. This requirement is impracticable and contrary to the public interest as it would prevent NMFS from responding to the most recent fisheries data in a timely fashion and would delay the directed fishing closure of Pacific cod by vessels harvesting Pacific cod for processing by the inshore component in the Western Regulatory Area of the GOA. NMFS was unable to publish a notice providing time for public comment because the most recent, relevant data only became available as of October 20, 2011.</P>
                <PRTPAGE P="66197"/>
                <P>The AA also finds good cause to waive the 30-day delay in the effective date of this action under 5 U.S.C. 553(d)(3). This finding is based upon the reasons provided above for waiver of prior notice and opportunity for public comment.</P>
                <P>This action is required by § 679.20 and is exempt from review under Executive Order 12866.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>
                        16 U.S.C. 1801 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: October 21, 2011.</DATED>
                    <NAME>Alan D. Risenhoover,</NAME>
                    <TITLE>Director, Office of Sustainable Fisheries, National Marine Fisheries Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27715 Filed 10-21-11; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </RULE>
    </RULES>
    <VOL>76</VOL>
    <NO>207</NO>
    <DATE>Wednesday, October 26, 2011</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <PRORULES>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="66198"/>
                <AGENCY TYPE="F">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2011-1092; Directorate Identifier 2011-NM-111-AD]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Bombardier, Inc. Model BD-700-1A10 and BD-700-1A11 Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We propose to adopt a new airworthiness directive (AD) for the products listed above. This proposed AD results from mandatory continuing airworthiness information (MCAI) originated by an aviation authority of another country to identify and correct an unsafe condition on an aviation product. The MCAI describes the unsafe condition as:</P>
                    <EXTRACT>
                        <FP>During a routine inspection, deformation was found at the neck of the pressure regulator body on the oxygen Cylinder and Regulator Assemblies (CRA).</FP>
                        <FP>An investigation by the vendor * * * revealed that the deformation was attributed to two (2) batches of raw material that did not meet the required tensile strength. This may cause elongation of the pressure regulator neck, which could result in rupture of the oxygen cylinder, and in the case of cabin depressurization, oxygen not being available when required.</FP>
                        <STARS/>
                    </EXTRACT>
                </SUM>
                <FP>The proposed AD would require actions that are intended to address the unsafe condition described in the MCAI.</FP>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We must receive comments on this proposed AD by December 12, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments 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 instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (202) 493-2251.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         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>
                        • 
                        <E T="03">Hand Delivery:</E>
                         U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        For service information identified in this proposed AD, contact Bombardier, Inc., 400 Côte-Vertu Road West, Dorval, Québec H4S 1Y9, Canada; telephone 514-855-5000; fax 514-855-7401; e-mail 
                        <E T="03">thd.crj@aero.bombardier.com;</E>
                         Internet 
                        <E T="03">http://www.bombardier.com</E>
                        . You may review copies of the referenced service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington. For information on the availability of this material at the FAA, call 425-227-1221.
                    </P>
                </ADD>
                <HD SOURCE="HD1">Examining the AD Docket</HD>
                <P>
                    You may examine the AD docket on the Internet at 
                    <E T="03">http://www.regulations.gov;</E>
                     or in person at the Docket Operations office between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this proposed AD, the regulatory evaluation, any comments received, and other information. The street address for the Docket Operations office (telephone (800) 647-5527) is in the 
                    <E T="02">ADDRESSES</E>
                     section. Comments will be available in the AD docket shortly after receipt.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Cesar Gomez, Aerospace Engineer, Airframe and Mechanical Systems Branch, ANE-171, FAA, New York Aircraft Certification Office, 1600 Stewart Avenue, Suite 410, Westbury, New York 11590; telephone (516) 228-7318; fax (516) 794-5531.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>
                    We invite you to send any written relevant data, views, or arguments about this proposed AD. Send your comments to an address listed under the 
                    <E T="02">ADDRESSES</E>
                     section. Include “Docket No. FAA-2011-1092; Directorate Identifier 2011-NM-111-AD” at the beginning of your comments. We specifically invite comments on the overall regulatory, economic, environmental, and energy aspects of this proposed AD. We will consider all comments received by the closing date and may amend this proposed AD based on those comments.
                </P>
                <P>
                    We will post all comments we receive, without change, to 
                    <E T="03">http://www.regulations.gov</E>
                    , including any personal information you provide. We will also post a report summarizing each substantive verbal contact we receive about this proposed AD.
                </P>
                <HD SOURCE="HD1">Discussion</HD>
                <P>The Transport Canada Civil Aviation (TCCA), which is the aviation authority for Canada, has issued Canadian Airworthiness Directive CF-2011-10, dated May 13, 2011 (referred to after this as “the MCAI”), to correct an unsafe condition for the specified products. The MCAI states:</P>
                <EXTRACT>
                    <P>During a routine inspection, deformation was found at the neck of the pressure regulator body on the oxygen Cylinder and Regulator Assemblies (CRA).</P>
                    <P>An investigation by the vendor, Avox Systems Inc., revealed that the deformation was attributed to two (2) batches of raw material that did not meet the required tensile strength. This may cause elongation of the pressure regulator neck, which could result in rupture of the oxygen cylinder, and in the case of cabin depressurization, oxygen not being available when required.</P>
                    <P>This [Canadian] directive mandates [an inspection to determine if a certain oxygen CRA is installed and] the replacement of oxygen CRAs containing pressure regulators, part number (P/N) 806370-06, that do not meet the required material properties.</P>
                </EXTRACT>
                <FP>You may obtain further information by examining the MCAI in the AD docket.</FP>
                <HD SOURCE="HD1">Relevant Service Information</HD>
                <P>Bombardier has issued Service Bulletins 700-1A11-35-010 (for Model BD-700-1A11 airplanes) and 700-35-011 (for Model BD-700-1A10 airplanes), both Revision 01, both dated February 1, 2011. The actions described in this service information are intended to correct the unsafe condition identified in the MCAI.</P>
                <HD SOURCE="HD1">FAA's Determination and Requirements of This Proposed AD</HD>
                <P>
                    This product has been approved by the aviation authority of another country, and is approved for operation in the United States. Pursuant to our bilateral agreement with the State of Design Authority, we have been notified 
                    <PRTPAGE P="66199"/>
                    of the unsafe condition described in the MCAI and service information referenced above. We are proposing this AD because we evaluated all pertinent information and determined an unsafe condition exists and is likely to exist or develop on other products of the same type design.
                </P>
                <HD SOURCE="HD1">Differences Between This AD and the MCAI or Service Information</HD>
                <P>We have reviewed the MCAI and related service information and, in general, agree with their substance. But we might have found it necessary to use different words from those in the MCAI to ensure the AD is clear for U.S. operators and is enforceable. In making these changes, we do not intend to differ substantively from the information provided in the MCAI and related service information.</P>
                <P>We might also have proposed different actions in this AD from those in the MCAI in order to follow FAA policies. Any such differences are highlighted in a NOTE within the proposed AD.</P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>Based on the service information, we estimate that this proposed AD would affect about 39 products of U.S. registry. We also estimate that it would take about 10 work-hours per product to comply with the basic requirements of this proposed AD. The average labor rate is $85 per work-hour. Required parts would cost about $0 per product. Where the service information lists required parts costs that are covered under warranty, we have assumed that there will be no charge for these parts. As we do not control warranty coverage for affected parties, some parties may incur costs higher than estimated here. Based on these figures, we estimate the cost of the proposed AD on U.S. operators to be $33,150, or $850 per product.</P>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. “Subtitle VII: Aviation Programs,” describes in more detail the scope of the Agency's authority.</P>
                <P>We are issuing this rulemaking under the authority described in “Subtitle VII, Part A, Subpart III, Section 44701: General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>We determined that this proposed AD would not have federalism implications under Executive Order 13132. This proposed AD would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>
                    <E T="03">For the reasons discussed above, I certify this proposed regulation:</E>
                </P>
                <P>1. Is not a “significant regulatory action” under Executive Order 12866;</P>
                <P>2. Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979); and</P>
                <P>3. Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <P>We prepared a regulatory evaluation of the estimated costs to comply with this proposed AD and placed it in the AD docket.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA proposes to amend 14 CFR part 39 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                    <P>1. The authority citation for part 39 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                        <P>2. The FAA amends § 39.13 by adding the following new AD:</P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">Bombardier, Inc.:</E>
                                 Docket No. FAA-2011-1092; Directorate Identifier 2011-NM-111-AD.
                            </FP>
                            <HD SOURCE="HD1">Comments Due Date</HD>
                            <P>(a) We must receive comments by December 12, 2011.</P>
                            <HD SOURCE="HD1">Affected ADs</HD>
                            <P>(b) None.</P>
                            <HD SOURCE="HD1">Applicability</HD>
                            <P>(c) This AD applies to Bombardier, Inc. Model BD-700-1A10 and BD-700-1A11 airplanes, certificated in any category, serial numbers (S/N) 9002 through 9126 inclusive, 9128 through 9312 inclusive, 9314 through 9322 inclusive, 9324 through 9335 inclusive, 9337, 9338, 9340, 9341, 9343, 9344, 9346, 9347, 9350, 9353, 9355, 9356, 9358, 9361, 9365, 9372, 9374, 9384, 9402, 9403, and subsequent.</P>
                            <HD SOURCE="HD1">Subject</HD>
                            <P>(d) Air Transport Association (ATA) of America Code 35: Oxygen.</P>
                            <HD SOURCE="HD1">Reason</HD>
                            <P>(e) The mandatory continuing airworthiness information (MCAI) states:</P>
                            <P>During a routine inspection, deformation was found at the neck of the pressure regulator body on the oxygen Cylinder and Regulator Assemblies (CRA).</P>
                            <P>An investigation by the vendor * * * revealed that the deformation was attributed to two (2) batches of raw material that did not meet the required tensile strength. This may cause elongation of the pressure regulator neck, which could result in rupture of the oxygen cylinder, and in the case of cabin depressurization, oxygen not being available when required.</P>
                            <STARS/>
                            <HD SOURCE="HD1">Compliance</HD>
                            <P>(f) You are responsible for having the actions required by this AD performed within the compliance times specified, unless the actions have already been done.</P>
                            <HD SOURCE="HD1">Actions</HD>
                            <P>(g) For airplanes having S/N 9002 through 9126 inclusive, 9128 through 9312 inclusive, 9314 through 9322 inclusive, 9324 through 9335 inclusive, 9337, 9338, 9340, 9341, 9343, 9344, 9346, 9347, 9350, 9353, 9355, 9356, 9358, 9361, 9365, 9372, 9374, 9384, 9402, 9403: Within 7 months after the effective date of this AD, do an inspection of oxygen pressure regulators having P/N 806370-06 to determine if the serial number is listed in Table 2 of the Accomplishment Instructions of Bombardier Service Bulletin 700-35-011 (for Model BD-700-1A10 airplanes) or 700-1A11-35-010 (for Model BD-700-1A11 airplanes), both Revision 01, both dated February 1, 2011.</P>
                            <P>(1) If the serial number of the pressure regulator having P/N 806370-06 is listed in Table 2 of the Accomplishment Instructions of Bombardier Service Bulletin 700-35-011 (for Model BD-700-1A10 airplanes) or 700-1A11-35-010 (for Model BD-700-1A11 airplanes), both Revision 01, both dated February 1, 2011, within 7 months after the effective date of this AD, replace the affected oxygen CRA, in accordance with paragraph 2.C. of the Accomplishment Instructions of Bombardier Service Bulletin 700-35-011 (for Model BD-700-1A10 airplanes) or 700-1A11-35-010 (for Model BD-700-1A11 airplanes), both Revision 01, both dated February 1, 2011.</P>
                            <P>
                                (2) If the serial number of the oxygen pressure regulator having P/N 806370-06 is not listed in Table 2 of the Accomplishment Instructions of Bombardier Service Bulletin 700-35-011 (for Model BD-700-1A10 airplanes) or 700-1A11-35-010 (for Model BD-700-1A11 airplanes), both Revision 01, 
                                <PRTPAGE P="66200"/>
                                both dated February 1, 2011, no further action is required by this paragraph.
                            </P>
                            <HD SOURCE="HD1">Parts Installation</HD>
                            <P>(h) For all airplanes: As of the effective date of this AD, no person may install an oxygen pressure regulator (P/N 806370-06) having any serial number listed in Table 2 of the Accomplishment Instructions of Bombardier Service Bulletin 700-35-011 (for Model BD-700-1A10 airplanes) or 700-1A11-35-010 (for Model BD-700-1A11 airplanes), both Revision 01, both dated February 1, 2011, on any airplane, unless a suffix “-A” is beside the serial number.</P>
                            <HD SOURCE="HD1">FAA AD Differences</HD>
                            <NOTE>
                                <HD SOURCE="HED">Note 1:</HD>
                                <P>This AD differs from the MCAI and/or service information as follows:</P>
                                <P>The MCAI applicability specifies only airplanes having certain serial numbers and prohibits installation of the affected part on those airplanes. Because the affected part could be rotated onto any of the Model BD-700-1A10 and BD-700-1A11 airplanes, this AD applies to S/N 9002 through 9126 inclusive, 9128 through 9312 inclusive, 9314 through 9322 inclusive, 9324 through 9335 inclusive, 9337, 9338, 9340, 9341, 9343, 9344, 9346, 9347, 9350, 9353, 9355, 9356, 9358, 9361, 9365, 9372, 9374, 9384, 9402, 9403, and subsequent. This has been coordinated with the Transport Canada Civil Aviation (TCCA).</P>
                            </NOTE>
                            <HD SOURCE="HD1">Other FAA AD Provisions</HD>
                            <P>(i) The following provisions also apply to this AD:</P>
                            <P>
                                (1) 
                                <E T="03">Alternative Methods of Compliance (AMOCs):</E>
                                 The Manager, New York Aircraft Certification Office (ACO), ANE-170, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the ACO, send it to 
                                <E T="03">Attn:</E>
                                 Program Manager, Continuing Operational Safety, FAA, New York ACO, 1600 Stewart Avenue, Suite 410, Westbury, New York 11590; telephone 516-228-7300; fax 516-794-5531. Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office. The AMOC approval letter must specifically reference this AD.
                            </P>
                            <P>
                                (2) 
                                <E T="03">Airworthy Product:</E>
                                 For any requirement in this AD to obtain corrective actions from a manufacturer or other source, use these actions if they are FAA-approved. Corrective actions are considered FAA-approved if they are approved by the State of Design Authority (or their delegated agent). You are required to assure the product is airworthy before it is returned to service.
                            </P>
                            <HD SOURCE="HD1">Related Information</HD>
                            <P>(j) Refer to MCAI Transport Canada Civil Aviation (TCCA) Airworthiness Directive CF-2011-10, dated May 13, 2011; Bombardier Service Bulletin 700-35-011, Revision 01, dated February 1, 2011; and Bombardier Service Bulletin 700-1A11-35-010, Revision 01, dated February 1, 2011; for related information.</P>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Renton, Washington, on October 17, 2011.</DATED>
                        <NAME>Kalene C. Yanamura,</NAME>
                        <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27650 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2011-1094; Directorate Identifier 2011-NM-070-AD]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; The Boeing Company Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We propose to adopt a new airworthiness directive (AD) for certain The Boeing Company Model 757 airplanes. This proposed AD would require inspecting for discrepancies and insufficient coverage of the secondary fuel barrier, determining the thickness of the secondary fuel barrier, and corrective actions if necessary. This proposed AD was prompted by reports that inspections of the wing center section revealed defective, misapplied, or missing secondary fuel vapor barrier on the center fuel tank. We are proposing this AD to detect and correct defective surfaces and insufficient thickness of secondary fuel barrier, which could allow fuel leaks or fumes into the pressurized cabin, and allow fuel or fuel vapors to come in contact with an ignition source, which could result in a fire or an explosion.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We must receive comments on this proposed AD by December 12, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments 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 instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         202-493-2251.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         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>
                        • 
                        <E T="03">Hand Delivery:</E>
                         Deliver to Mail address above between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        For service information identified in this proposed AD, contact Boeing Commercial Airplanes, Attention: Data &amp; Services Management, P.O. Box 3707, MC 2H-65, Seattle, Washington 98124-2207; telephone 206-544-5000, extension 1; fax 206-766-5680; e-mail 
                        <E T="03">me.boecom@boeing.com;</E>
                         Internet 
                        <E T="03">https://www.myboeingfleet.com.</E>
                         You may review copies of the referenced service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, Washington. For information on the availability of this material at the FAA, call 425-227-1221.
                    </P>
                </ADD>
                <HD SOURCE="HD1">Examining the AD Docket</HD>
                <P>
                    You may examine the AD docket on the Internet at 
                    <E T="03">http://www.regulations.gov;</E>
                     or in person at the Docket Management Facility between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this proposed AD, the regulatory evaluation, any comments received, and other information. The street address for the Docket Office (
                    <E T="03">phone:</E>
                     800-647-5527) is in the 
                    <E T="02">ADDRESSES</E>
                     section. Comments will be available in the AD docket shortly after receipt.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kevin Nguyen, Aerospace Engineer, Propulsion Branch, ANM-140S, FAA, Seattle Aircraft Certification Office (ACO), 1601 Lind Avenue, SW., Renton, Washington 98057-3356; 
                        <E T="03">phone:</E>
                         425-917-6501; 
                        <E T="03">fax:</E>
                         425-917-6590; 
                        <E T="03">e-mail: kevin.nguyen@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>
                    We invite you to send any written relevant data, views, or arguments about this proposal. Send your comments to an address listed under the 
                    <E T="02">ADDRESSES</E>
                     section. Include “Docket No. FAA-2011-1094; Directorate Identifier 2011-NM-070-AD” at the beginning of your comments. We specifically invite comments on the overall regulatory, economic, environmental, and energy aspects of this proposed AD. We will consider all comments received by the closing date and may amend this proposed AD because of those comments.
                </P>
                <P>
                    We will post all comments we receive, without change, to 
                    <E T="03">http://www.regulations.gov,</E>
                     including any personal information you provide. We will also post a report summarizing each substantive verbal contact we receive about this proposed AD.
                </P>
                <HD SOURCE="HD1">Discussion</HD>
                <P>
                    We received reports that inspections of the wing center section revealed 
                    <PRTPAGE P="66201"/>
                    defective, misapplied, or missing secondary fuel vapor barrier on the center fuel tank. The secondary fuel barrier is applied external to the fuel tank walls, which are subject to cabin pressure to provide a secondary means to contain fuel and fuel vapors. When the secondary fuel barrier is applied satisfactorily, it protects the pressurized cabin areas from fuel leaks and fumes. If the secondary fuel barrier is defective, fuel or fumes can leak through fastener holes or cracks in the structure and pass into the passenger compartment. There have been no reports from operators of fuel leaks or fumes in the passenger compartment. We are proposing this AD to detect and correct defective surfaces and insufficient thickness of secondary fuel barrier, which could allow fuel leaks or fumes into the pressurized cabin, and allow fuel or fuel vapors to come in contact with an ignition source, which could result in a fire or an explosion.
                </P>
                <HD SOURCE="HD1">Related Rulemaking</HD>
                <P>On June 10, 2005, the FAA issued AD 2005-13-15, Amendment 39-14152 (70 FR 36486, June 24, 2005), applicable to certain Boeing Model 737-200, -200C, -300, -400, -500, -600, -700, -700C, -800, and -900 series airplanes, which requires a one-time detailed inspection for discrepancies of the secondary fuel vapor barrier of the wing center section, and related investigative and corrective actions if necessary. That AD was prompted by reports that the secondary fuel vapor barrier was not applied correctly to, or was missing from, certain areas of the wing center section. The actions required by that AD are intended to prevent fuel or fuel vapors from leaking into the cargo or passenger compartments and coming into contact with a possible ignition source, which could result in fire or explosion.</P>
                <HD SOURCE="HD1">Relevant Service Information</HD>
                <P>We reviewed Boeing Service Bulletins 757-57-0060, Revision 2, dated May 24, 2007 (for Model 757-200, 757-200PF, and 757-200CB series airplanes); and 757-57-0061, Revision 1, dated May 24, 2007 (for Model 757-300 series airplanes). These service bulletins describe procedures for, depending on airplane configuration, inspecting for discrepancies and insufficient coverage of the secondary fuel barrier, determining the thickness of the secondary fuel barrier, and corrective actions if necessary. Discrepancies include missing, peeled, non-continuous, or non-transparent secondary fuel barrier; small air bubbles, air pockets, blister-like areas, or solid particles in the secondary fuel barrier; fillet sealant, primer, corrosion-inhibiting compound or other finishes applied to the top of the secondary fuel barrier; missing fillet (cap) seals; or areas of secondary fuel barrier whose thickness is less than or greater than specified limits; or areas not having a transparent quality that makes it possible to see a crack in the structure; or areas not having a minimum application coverage area. Corrective actions include repairing the secondary fuel barrier, including removal and reapplication, if needed; or applying more secondary fuel barrier, as needed.</P>
                <HD SOURCE="HD1">FAA's Determination</HD>
                <P>We are proposing this AD because we evaluated all the relevant information and determined the unsafe condition described previously is likely to exist or develop in other products of these same type designs.</P>
                <HD SOURCE="HD1">Proposed AD Requirements</HD>
                <P>This proposed AD would require accomplishing the actions specified in the service information described previously, except as discussed under “Differences Between the Proposed AD and the Service Information.”</P>
                <HD SOURCE="HD1">Differences Between the Proposed AD and the Service Information</HD>
                <P>Although Boeing Service Bulletin 757-57-0060, Revision 2, and Boeing Service Bulletin 757-57-0061, Revision 1, both dated May 24, 2007, specify to send the inspection results to the manufacturer, this proposed AD would not require any report. Boeing Service Bulletin 757-57-0060, Revision 2, and Boeing Service Bulletin 757-57-0061, Revision 1, both dated May 24, 2007, refer to a “detailed visual inspection” for discrepancies and insufficient coverage of the secondary fuel barrier. We have determined that the procedures in the service bulletin should be described as a “detailed inspection.” Note 1 has been included in this AD to define this type of inspection.</P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>We estimate that this proposed AD affects 619 airplanes of U.S. registry. We estimate the following costs to comply with this proposed AD:</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,r100,12C,12C,12C,12C">
                    <TTITLE>Estimated Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Action</CHED>
                        <CHED H="1">Labor cost</CHED>
                        <CHED H="1">Parts cost</CHED>
                        <CHED H="1">Cost per product</CHED>
                        <CHED H="1">Cost on U.S. operators</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Access and inspect secondary fuel barrier</ENT>
                        <ENT>42 work-hours × $85 per hour = $3,570 per inspection</ENT>
                        <ENT>$0</ENT>
                        <ENT>$3,570</ENT>
                        <ENT>$2,209,830</ENT>
                    </ROW>
                </GPOTABLE>
                <P>We estimate the following costs to do any necessary repairs that would be required based on the results of the proposed inspection. We have no way of determining the number of aircraft that might need these repairs:</P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,r100,12C,12C">
                    <TTITLE>On-Condition Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Action</CHED>
                        <CHED H="1">Labor cost</CHED>
                        <CHED H="1">Parts cost</CHED>
                        <CHED H="1">Cost per product</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Apply secondary fuel barrier</ENT>
                        <ENT>7 work-hours × $85 per hour = $595 per secondary fuel barrier application</ENT>
                        <ENT>$0</ENT>
                        <ENT>$595</ENT>
                    </ROW>
                </GPOTABLE>
                <P>According to the manufacturer, some of the costs of this proposed AD may be covered under warranty, thereby reducing the cost impact on affected individuals. We do not control warranty coverage for affected individuals. As a result, we have included all costs in our cost estimate.</P>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>
                    Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, 
                    <PRTPAGE P="66202"/>
                    section 106, describes the authority of the FAA Administrator. Subtitle VII: Aviation Programs, describes in more detail the scope of the Agency's authority.
                </P>
                <P>We are issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701: “General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>We determined that this proposed AD would not have federalism implications under Executive Order 13132. This proposed AD would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>
                    <E T="03">For the reasons discussed above, I certify this proposed regulation:</E>
                </P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
                <P>(2) Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979),</P>
                <P>(3) Will not affect intrastate aviation in Alaska, and</P>
                <P>(4) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA proposes to amend 14 CFR part 39 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                    <P>1. The authority citation for part 39 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13</SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                        <P>2. The FAA amends § 39.13 by adding the following new airworthiness directive (AD):</P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">The Boeing Company:</E>
                                 Docket No. FAA-2011-1094; Directorate Identifier 2011-NM-070-AD.
                            </FP>
                            <HD SOURCE="HD1">Comments Due Date</HD>
                            <P>(a) We must receive comments by December 12, 2011.</P>
                            <HD SOURCE="HD1">Affected ADs</HD>
                            <P>(b) None.</P>
                            <HD SOURCE="HD1">Applicability</HD>
                            <P>(c) This AD applies to The Boeing Company Model 757-200, 757-200PF, and 757-200CB series airplanes, certificated in any category, as identified in Boeing Service Bulletin 757-57-0060, Revision 2, dated May 24, 2007; and Model 757-300 series airplanes, certificated in any category, as identified in Boeing Service Bulletin 757-57-0061, Revision 1, dated May 24, 2007.</P>
                            <HD SOURCE="HD1">Subject</HD>
                            <P>(d) Joint Aircraft System Component (JASC)/Air Transport Association (ATA) of America Code 57: Wings.</P>
                            <HD SOURCE="HD1">Unsafe Condition</HD>
                            <P>(e) This proposed AD was prompted by reports that inspections of the wing center section revealed defective, misapplied, or missing secondary fuel vapor barrier on the center fuel tank. We are issuing this AD to detect and correct defective surfaces and insufficient thickness of secondary fuel barrier, which could allow fuel leaks or fumes into the pressurized cabin, and allow fuel or fuel vapors to come in contact with an ignition source, which could result in a fire or an explosion.</P>
                            <HD SOURCE="HD1">Compliance</HD>
                            <P>(f) Comply with this AD within the compliance times specified, unless already done.</P>
                            <HD SOURCE="HD1">Detailed Inspection</HD>
                            <P>(g) For airplanes identified in Boeing Service Bulletin 757-57-0060, Revision 2, dated May 24, 2007, as Group 1, Group 2, and Group 4 Configuration 1; and airplanes identified in Boeing Service Bulletin 757-57-0061, Revision 1, dated May 24, 2007, as Group 1, Group 2, and Group 3 Configuration 1: Within 60 months after the effective date of this AD, do a detailed inspection to detect discrepancies of the secondary fuel barrier at the front spar and the upper panel of the wing center section, and if discrepancies exist, repair before further flight, in accordance with the Accomplishment Instructions of Boeing Service Bulletin 757-57-0060, Revision 2, dated May 24, 2007; or Boeing Service Bulletin 757-57-0061, Revision 1, dated May 24, 2007; as applicable.</P>
                            <NOTE>
                                <HD SOURCE="HED">Note 1:</HD>
                                <P>For the purposes of this AD, a detailed inspection is: “An intensive examination of a specific item, installation, or assembly to detect damage, failure, or irregularity. Available lighting is normally supplemented with a direct source of good lighting at intensity deemed appropriate. Inspection aids such as mirror, magnifying lenses, etc., may be necessary. Surface cleaning and elaborate access procedures may be required.”</P>
                            </NOTE>
                            <HD SOURCE="HD1">Inspection of Minimum Application Coverage Area</HD>
                            <P>(h) For Group 3 airplanes identified in Boeing Service Bulletin 757-57-0060, Revision 2, dated May 24, 2007; and Group 2 airplanes identified in Boeing Service Bulletin 757-57-0061, Revision 1, dated May 24, 2007: Within 60 months after the effective date of this AD, do a detailed inspection of the front spar and the upper panel to ensure the secondary fuel barrier application covers the minimum area specified in Boeing Service Bulletin 757-57-0060, Revision 2, dated May 24, 2007; or Boeing Service Bulletin 757-57-0061, Revision 1, dated May 24, 2007; as applicable. If the secondary fuel barrier does not cover the minimum specified area, apply more secondary fuel barrier before further flight, in accordance with the Accomplishment Instructions of Boeing Service Bulletin 757-57-0060, Revision 2, dated May 24, 2007; or Boeing Service Bulletin 757-57-0061, Revision 1, dated May 24, 2007; as applicable.</P>
                            <HD SOURCE="HD1">Measurement of Thickness of Secondary Fuel Barrier</HD>
                            <P>(i) For Group 1, Group 2, and Group 4 Configuration 1 airplanes identified in Boeing Service Bulletin 757-57-0060, Revision 2, dated May 24, 2007; and for Group 1, Group 2, and Group 3 Configuration 1 airplanes identified in Boeing Service Bulletin 757-57-0061, Revision 1, dated May 24, 2007: Within 60 months after the effective date of this AD, measure the thickness of the secondary fuel barrier. If the thickness is less than or over the acceptable limits defined in Boeing Service Bulletin 757-57-0060, Revision 2, dated May 24, 2007; or Boeing Service Bulletin 757-57-0061, Revision 1, dated May 24, 2007; as applicable, apply more secondary fuel barrier or repair before further flight, in accordance with the Accomplishment Instructions of Boeing Service Bulletin 757-57-0060, Revision 2, dated May 24, 2007; or Boeing Service Bulletin 757-57-0061, Revision 1, dated May 24, 2007; as applicable.</P>
                            <P>
                                (j) For Group 4, Configuration 2 airplanes identified in Boeing Service Bulletin 757-57-0060, Revision 2, dated May 24, 2007; and Group 3, Configuration 2 airplanes identified in Boeing Service Bulletin 757-57-0061, Revision 1, dated May 24, 2007: Within 60 months, review the maintenance records to determine if there was a minimum of 0.005 inch of new secondary fuel barrier applied, or if the thickness of the secondary fuel barrier cannot be determined from the maintenance records, measure the thickness of the secondary fuel barrier. If the thickness is less than or over the acceptable limits specified in Boeing Service Bulletin 757-57-0060, Revision 2, dated May 24, 2007; or Boeing Service Bulletin 757-57-0061, Revision 1, dated May 24, 2007; as applicable, apply more secondary fuel barrier or repair before further flight, in accordance with the Accomplishment Instructions of Boeing Service Bulletin 757-57-0060, Revision 2, dated May 24, 2007; or Boeing Service Bulletin 757-57-0061, Revision 1, dated May 24, 2007; as applicable.
                                <PRTPAGE P="66203"/>
                            </P>
                            <HD SOURCE="HD1">No Reporting Requirement</HD>
                            <P>(k) Although Boeing Service Bulletin 757-57-0060, Revision 2, dated May 24, 2007; and Boeing Service Bulletin 757-57-0061, Revision 1, dated May 24, 2007; specify to submit certain information to the manufacturer, this AD does not include that requirement.</P>
                            <HD SOURCE="HD1">Alternative Methods of Compliance (AMOCs)</HD>
                            <P>
                                (l)(1) The Manager, Seattle Aircraft Certification Office, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the manager of the ACO, send it to the attention of the person identified in the Related Information section of this AD. Information may be e-mailed to: 
                                <E T="03">9-NM-Seattle-ACO-AMOC-REQUESTS@faa.gov.</E>
                            </P>
                            <P>(2) Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office.</P>
                            <HD SOURCE="HD1">Related Information</HD>
                            <P>
                                (m)(1) For more information about this AD, contact Kevin Nguyen, Aerospace Engineer, Propulsion Branch, ANM-140S, FAA, Seattle Aircraft Certification Office (ACO), 1601 Lind Avenue, SW., Renton, Washington 98057-3356; phone: 425-917-6501; fax: 425-917-6590; e-mail: 
                                <E T="03">kevin.nguyen@faa.gov.</E>
                            </P>
                            <P>
                                (2) For service information identified in this AD, contact Boeing Commercial Airplanes, Attention: Data &amp; Services Management, P.O. Box 3707, MC 2H-65, Seattle, Washington 98124-2207; telephone 206-544-5000, extension 1; fax 206-766-5680; e-mail 
                                <E T="03">me.boecom@boeing.com;</E>
                                 Internet 
                                <E T="03">https://www.boeingfleet.com.</E>
                                 You may review copies of the referenced service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue,  SW., Renton, Washington. For information on the availability of this material at the FAA, call 425-227-1221.
                            </P>
                        </EXTRACT>
                        <STARS/>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Renton, Washington, on October 17, 2011.</DATED>
                        <NAME>Kalene C. Yanamura,</NAME>
                        <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27652 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2011-1095; Directorate Identifier 2010-NM-241-AD]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Bombardier, Inc. Model CL-600-2B16 (CL-601-3A, CL-601-3R, and CL-604 Variants) Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We propose to adopt a new airworthiness directive (AD) for the products listed above. This proposed AD results from mandatory continuing airworthiness information (MCAI) originated by an aviation authority of another country to identify and correct an unsafe condition on an aviation product. The MCAI describes the unsafe condition as:</P>
                    <EXTRACT>
                        <P>During pre-delivery inspections and test flights, several short circuit events were reported, one of which resulted in smoke in the cockpit. There were no in-service incidents.</P>
                        <FP>Investigations have identified three conditions affecting the wiring of Circuit Breaker Panels * * * and Junction Boxes * * *, which would lead to short circuiting:</FP>
                        <STARS/>
                        <FP>If not corrected, these conditions could result in arcing, damage to adjacent structure, smoke in the cockpit, or loss of system redundancies.</FP>
                        <STARS/>
                    </EXTRACT>
                </SUM>
                <FP>The proposed AD would require actions that are intended to address the unsafe condition described in the MCAI.</FP>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We must receive comments on this proposed AD by December 12, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments 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 instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (202) 493-2251.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         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>
                        • 
                        <E T="03">Hand Delivery:</E>
                         U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-40, 1200 New Jersey Avenue, SE., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        For service information identified in this proposed AD, contact Bombardier, Inc., 400 Côte-Vertu Road West, Dorval, Québec H4S 1Y9, Canada; 
                        <E T="03">phone:</E>
                         514-855-5000; 
                        <E T="03">fax:</E>
                         514-855-7401; 
                        <E T="03">e-mail:</E>
                          
                        <E T="03">thd.crj@aero.bombardier.com;</E>
                          
                        <E T="03">Internet: http://www.bombardier.com</E>
                        . You may review copies of the referenced service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington. For information on the availability of this material at the FAA, call 425-227-1221.
                    </P>
                </ADD>
                <HD SOURCE="HD1">Examining the AD Docket</HD>
                <P>
                    You may examine the AD docket on the Internet at 
                    <E T="03">http://www.regulations.gov;</E>
                     or in person at the Docket Operations office between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this proposed AD, the regulatory evaluation, any comments received, and other information. The street address for the Docket Operations office (
                    <E T="03">phone:</E>
                     800-647-5527) is in the 
                    <E T="02">ADDRESSES</E>
                     section. Comments will be available in the AD docket shortly after receipt.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Assata Dessaline, Aerospace Engineer, Avionics and Flight Test Branch, ANE-172, New York Aircraft Certification Office (ACO), FAA, 1600 Stewart Ave. Suite 410, Westbury, NY 11590; telephone (516) 228-7301; fax (516) 794-5531.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>
                    We invite you to send any written relevant data, views, or arguments about this proposed AD. Send your comments to an address listed under the 
                    <E T="02">ADDRESSES</E>
                     section. Include “Docket No. FAA-2011-1095; Directorate Identifier 2010-NM-241-AD” at the beginning of your comments. We specifically invite comments on the overall regulatory, economic, environmental, and energy aspects of this proposed AD. We will consider all comments received by the closing date and may amend this proposed AD based on those comments.
                </P>
                <P>
                    We will post all comments we receive, without change, to 
                    <E T="03">http://www.regulations.gov</E>
                    , including any personal information you provide. We will also post a report summarizing each substantive verbal contact we receive about this proposed AD.
                </P>
                <HD SOURCE="HD1">Discussion</HD>
                <P>
                    Transport Canada Civil Aviation (TCCA), which is the airworthiness authority for Canada, has issued Canadian Airworthiness Directive CF-2010-25, dated August 3, 2010 (referred to after this as “the MCAI”), to correct 
                    <PRTPAGE P="66204"/>
                    an unsafe condition for the specified products. The MCAI states:
                </P>
                <EXTRACT>
                    <P>During pre-delivery inspections and test flights, several short circuit events were reported, one of which resulted in smoke in the cockpit. There were no in-service incidents.</P>
                    <P>Investigations have identified three conditions affecting the wiring of Circuit Breaker Panels 1, 2, 3 and 4 (CBP-1, CBP-2, CBP-3, and CBP-4) and Junction Boxes 17 and 18 (JB17 and JB18), which would lead to short circuiting:</P>
                    <P>1. In CBP-1, there may be low clearance between specific bus bars and the circuit breaker panel structure.</P>
                    <P>2. Some nickel-plated terminal lugs, size number 22-20 with a green insulating sleeve, may not have been manufactured to applicable standards. These terminal lugs may have been installed in CBP-1, CBP-2, CBP-3, CBP-4, JB17 and JB18. This manufacturing defect affects the mechanical hold of the wire in the crimped lug barrel.</P>
                    <P>3. In JB17, JB18 and the above-mentioned CBPs, foreign object debris (FOD) may be found.</P>
                    <P>If not corrected, these conditions could result in arcing, damage to adjacent structure, smoke in the cockpit, or loss of system redundancies.</P>
                    <P>This TCCA directive is issued to mandate the replacement or relocation of the specific CBP-1 bus bars, the [detailed] inspection, and rework if necessary, of any loose or improperly crimped lugs in CBP-1, CBP-2, CBP-3, CBP-4, JB17 and JB18, and to ensure there is no FOD in the affected areas [via a general visual inspection for FOD, and removal if necessary].</P>
                </EXTRACT>
                <FP>You may obtain further information by examining the MCAI in the AD docket.</FP>
                <HD SOURCE="HD1">Relevant Service Information</HD>
                <P>Bombardier has issued Service Bulletin 605-24-002, dated December 07, 2009, and Service Bulletin 605-24-004, dated January 18, 2010. The actions described in this service information are intended to correct the unsafe condition identified in the MCAI.</P>
                <HD SOURCE="HD1">FAA's Determination and Requirements of This Proposed AD</HD>
                <P>This product has been approved by the aviation authority of another country, and is approved for operation in the United States. Pursuant to our bilateral agreement with the State of Design Authority, we have been notified of the unsafe condition described in the MCAI and service information referenced above. We are proposing this AD because we evaluated all pertinent information and determined an unsafe condition exists and is likely to exist or develop on other products of the same type design.</P>
                <HD SOURCE="HD1">Differences Between This AD and the MCAI or Service Information</HD>
                <P>We have reviewed the MCAI and related service information and, in general, agree with their substance. But we might have found it necessary to use different words from those in the MCAI to ensure the AD is clear for U.S. operators and is enforceable. In making these changes, we do not intend to differ substantively from the information provided in the MCAI and related service information.</P>
                <P>We might also have proposed different actions in this AD from those in the MCAI in order to follow FAA policies. Any such differences are highlighted in a NOTE within the proposed AD.</P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>Based on the service information, we estimate that this proposed AD would affect about 69 products of U.S. registry. We also estimate that it would take about 6 work-hours per product to comply with the basic requirements of this proposed AD. The average labor rate is $85 per work-hour. Required parts would cost about $347 per product. Where the service information lists required parts costs that are covered under warranty, we have assumed that there will be no charge for these costs. As we do not control warranty coverage for affected parties, some parties may incur costs higher than estimated here. Based on these figures, we estimate the cost of the proposed AD on U.S. operators to be $59,133, or $857 per product.</P>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. “Subtitle VII: Aviation Programs,” describes in more detail the scope of the Agency's authority.</P>
                <P>We are issuing this rulemaking under the authority described in “Subtitle VII, Part A, Subpart III, Section 44701: General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>We determined that this proposed AD would not have federalism implications under Executive Order 13132. This proposed AD would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>
                    <E T="03">For the reasons discussed above, I certify this proposed regulation:</E>
                </P>
                <P>1. Is not a “significant regulatory action” under Executive Order 12866;</P>
                <P>2. Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979); and</P>
                <P>3. Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <P>We prepared a regulatory evaluation of the estimated costs to comply with this proposed AD and placed it in the AD docket.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA proposes to amend 14 CFR part 39 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                    <P>1. The authority citation for part 39 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                        <P>2. The FAA amends § 39.13 by adding the following new AD:</P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">Bombardier, Inc.:</E>
                                 Docket No. FAA-2011-1095; Directorate Identifier  2010-NM-241-AD.
                            </FP>
                            <HD SOURCE="HD1">Comments Due Date</HD>
                            <P>(a) We must receive comments by December 12, 2011.</P>
                            <HD SOURCE="HD1">Affected ADs</HD>
                            <P>(b) None.</P>
                            <HD SOURCE="HD1">Applicability</HD>
                            <P>
                                (c) This AD applies to Bombardier, Inc. Model CL-600-2B16 (CL-601-3A, CL-601-3R, and CL-604 Variants) airplanes, certificated in any category, serial numbers 5701 through 5752 inclusive, 5754 through 5775 inclusive, 5777, 5779 through 5781 inclusive, 5783 through 5790 inclusive, 5792, 5794 through 5796 inclusive, 5798, 5801, and 5804.
                                <PRTPAGE P="66205"/>
                            </P>
                            <HD SOURCE="HD1">Subject</HD>
                            <P>(d) Air Transport Association (ATA) of America Code 24: Electrical Power.</P>
                            <HD SOURCE="HD1">Reason</HD>
                            <P>(e) The mandatory continuing airworthiness information (MCAI) states:</P>
                            <FP>During pre-delivery inspections and test flights, several short circuit events were reported, one of which resulted in smoke in the cockpit. There were no in-service incidents.</FP>
                            <FP>Investigations have identified three conditions affecting the wiring of Circuit Breaker Panels * * * and Junction Boxes * * *, which would lead to short circuiting:</FP>
                            <FP>If not corrected, these conditions could result in arcing, damage to adjacent structure, smoke in the cockpit, or loss of system redundancies.</FP>
                            <HD SOURCE="HD1">Compliance</HD>
                            <P>(f) You are responsible for having the actions required by this AD performed within the compliance times specified, unless the actions have already been done.</P>
                            <HD SOURCE="HD1">Inspections, Bus Bar Actions, and Corrective Actions</HD>
                            <P>(g) For airplanes having serial numbers 5701 through 5752, 5754 through 5775, 5777, 5780 through 5781, 5783 through 5790, 5792, 5794 through 5796, 5798, 5801, and 5804: Within 800 flight hours after the effective date of this AD, do the actions in paragraph (g)(1), (g)(2), and (g)(3) of this AD, in accordance with the Accomplishment Instructions of the Bombardier Service Bulletin 605-24-004, dated January 18, 2010.</P>
                            <P>(1) Do a detailed inspection in CBP-1 for loose lugs and for crimped lugs that have any of the conditions specified in step 2.B.(9)(d) of Bombardier Service Bulletin 605-24-004, dated January 18, 2010. Before further flight, replace all loose lugs and all crimped lugs in CBP-1 that have any of the conditions specified in step 2.B.(9)(d) of Bombardier Service Bulletin 605-24-004, dated January 18, 2010.</P>
                            <P>(2) Relocate or replace the CBP-1 bus bars as applicable.</P>
                            <P>(3) Do a general visual inspection for foreign object damage (FOD). If any FOD is found: Before further flight, remove the FOD.</P>
                            <P>(h) For airplanes having serial numbers 5701 through 5752, 5754 through 5756, 5758 through 5775, 5779, 5781, 5788, 5789, 5792, 5795, 5798, 5801, and 5804: Within 800 flight hours after the effective date of this AD, do the actions in paragraph (h)(1) and (h)(2) of this AD, in accordance with the Accomplishment Instructions of the Bombardier Service Bulletin 605-24-002, dated December 7, 2009.</P>
                            <P>(1) Do a detailed inspection for loose lugs and for crimped lugs that have any of the conditions specified in step 2.B.(2)(d) of Bombardier Service Bulletin 605-24-002, dated December 7, 2009, in CBP-2, CBP-3, CBP-4, JB17, and JB18. Before further flight, replace all loose lugs and all crimped lugs that have any of the conditions specified in step 2.B.(2)(d) of Bombardier Service Bulletin 605-24-002, dated  December 7, 2009, in CBP-2, CBP-3, CBP-4, JB17, and JB18.</P>
                            <P>(2) Do a general visual inspection for FOD. If any FOD is found: Before further flight, remove the FOD.</P>
                            <HD SOURCE="HD1">FAA AD Differences</HD>
                            <NOTE>
                                <HD SOURCE="HED">Note 1:</HD>
                                <P> This AD differs from the MCAI and/or service information as follows: The Accomplishment Instructions of Bombardier Service Bulletin 605-24-002, dated  December 7, 2009, does not specify corrective action for the general visual inspection for FOD. This AD requires removing any FOD discovered during the general visual inspection.</P>
                            </NOTE>
                            <HD SOURCE="HD1">Other FAA AD Provisions</HD>
                            <P>(i) The following provisions also apply to this AD:</P>
                            <P>
                                (1) 
                                <E T="03">Alternative Methods of Compliance (AMOCs):</E>
                                 The Manager, New York Aircraft Certification Office, ANE-170, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with  14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the manager of the ACO, send it to ATTN: Program Manager, Continuing Operational Safety, FAA, New York ACO, 1600 Stewart Avenue, Suite 410, Westbury, New York 11590; telephone (516) 228-7300; fax (516) 794-5531. Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office. The AMOC approval letter must specifically reference this AD.
                            </P>
                            <P>
                                (2) 
                                <E T="03">Airworthy Product:</E>
                                 For any requirement in this AD to obtain corrective actions from a manufacturer or other source, use these actions if they are FAA-approved. Corrective actions are considered FAA-approved if they are approved by the State of Design Authority (or their delegated agent). You are required to assure the product is airworthy before it is returned to service.
                            </P>
                            <HD SOURCE="HD1">Related Information</HD>
                            <P>(j) Refer to MCAI Canadian Airworthiness Directive CF-2010-25, dated August 3, 2010; and Bombardier Service Bulletin 605-24-002, dated December 07, 2009; and Bombardier Service Bulletin 605-24-004, dated January 18, 2010; for related information.</P>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Renton, Washington, on October 17, 2011.</DATED>
                        <NAME>Kalene C. Yanamura,</NAME>
                        <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27653 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2010-0517; Directorate Identifier 2009-SW-73-AD]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Sikorsky Aircraft Corporation Model S-76A Helicopters</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration, DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document proposes adopting a new airworthiness directive (AD) for the Sikorsky Aircraft Corporation (Sikorsky) Model S-76A helicopters. This proposal would require modifying the electric rotor brake (ERB). Thereafter, the AD would also require inserting changes to the “Normal Procedures” and “Emergency Procedures” sections of the Rotorcraft Flight Manual (RFM), which revises the information of the basic RFM when the ERB is installed. This proposal is prompted by a reported incident of a fire occurring in an ERB installed on a Model S-76A helicopter. The actions specified by this proposed AD are intended to prevent overheating of the ERB assembly, ignition of the ERB hydraulic fluid, a fire in the main gearbox area, and subsequent loss of control of the helicopter.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before December 27, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Use one of the following addresses to submit comments on this proposed AD:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         202-493-2251.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         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>
                        • 
                        <E T="03">Hand Delivery:</E>
                         U.S. Department of Transportation, Docket Operations, M-30, 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>
                    <P>
                        You may get the service information identified in this proposed AD from Sikorsky Aircraft Corporation, Attn: Manager, Commercial Technical Support, mailstop s581a, 6900 Main Street, Stratford, CT, telephone (203) 383-4866, e-mail address: 
                        <PRTPAGE P="66206"/>
                        <E T="03">tsslibrary@sikorsky.com,</E>
                         or at 
                        <E T="03">http://www.sikorsky.com.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Caspar Wang, Aviation Safety Engineer, Boston Aircraft Certification Office, 12 New England Executive Park, Burlington, MA 01803, telephone (781) 238-7799, fax (781) 238-7170.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>
                    We invite you to submit any written data, views, or arguments regarding this proposed AD. Send your comments to the address listed under the caption 
                    <E T="02">ADDRESSES</E>
                    . Include the docket number “FAA-2010-0517, Directorate Identifier 2009-SW-73-AD” at the beginning of your comments. We specifically invite comments on the overall regulatory, economic, environmental, and energy aspects of the proposed AD. We will consider all comments received by the closing date and may amend the proposed AD in light of those comments.
                </P>
                <P>
                    We will post all comments we receive, without change, to 
                    <E T="03">http://www.regulations.gov,</E>
                     including any personal information you provide. We will also post a report summarizing each substantive verbal contact with FAA personnel concerning this proposed rulemaking. Using the search function of our docket Web site, you can find and read the comments to any of our dockets, including the name of the individual who sent or signed the comment. You may review the DOT's complete Privacy Act Statement in the 
                    <E T="04">Federal Register</E>
                     published on April 11, 2000 (65 FR 19477-78).
                </P>
                <HD SOURCE="HD1">Examining the Docket</HD>
                <P>
                    You may examine the docket that contains the proposed AD, any comments, and other information on the Internet at 
                    <E T="03">http://www.regulations.gov</E>
                     or in person at the Docket Operations office between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The Docket Operations office (telephone (800) 647-5527) is located in Room W12-140 on the ground floor of the West Building at the street address stated in the 
                    <E T="02">ADDRESSES</E>
                     section. Comments will be available in the AD docket shortly after receipt.
                </P>
                <HD SOURCE="HD1">Discussion</HD>
                <P>A number of service documents and ADs have been issued relating to the ERB on these and similar model helicopters. AD 82-17-03, issued July 30, 1982 (47 FR 35469, August 16, 1982), requires a puck-to-disc inspection of rotor brake, part number (P/N) 76363-09101-101, and modification of the ERB system including, among other modifications, installation of a warning relay by following Sikorsky Customer Service Bulletin No. 76-66-10B, dated November 25, 1981. AD 2003-04-15, issued February 14, 2003 (68 FR 8994, February 27, 2003), requires inspecting certain rotor brake discs for cracks that resulted from improper heat treating of the disc. This document proposes adopting a new AD for the Sikorsky Model S-76A helicopters with a different part-numbered ERB. This proposal would require, within 120 days, modifying the ERB by installing and operationally testing the parts contained in an ERB warning relay kit (P/N 76070-55023-011), an ERB circuit modification kit (P/N 76070-55033-012), and an ERB modification kit (P/N 76070-55207-011) for helicopters with ERB, P/N 76363-09100-012. This proposal is prompted by a reported incident of a fire occurring in an ERB installed on a Model S-76A helicopter in Brazil. The actions specified by this proposed AD are intended to prevent overheating of the ERB assembly, ignition of the ERB hydraulic fluid, a fire in the main gearbox area, and subsequent loss of control of the helicopter.</P>
                <P>We have reviewed the following documents from Sikorsky:</P>
                <P>• Customer Service Bulletin No. 76-66-10B, Revision 1, pages 2-8, dated July 30, 1981, and Revision 2, pages 1 and 9-13 dated November 25, 1981 (CSB), specifies installing an ERB warning relay kit;</P>
                <P>• Customer Service Notice 76-113, dated June 1, 1983 (CSN), which specifies installing an ERB circuit breaker and modification kit; and</P>
                <P>• ASB No. 76-66-48B, Revision B, dated July 8, 2009, which specifies a one-time installation of an ERB modification kit containing two other kits and several modifications.</P>
                <P>• RFM Supplement No. 41, dated September 6, 2005, which revises the information in the basic RFM normal and emergency procedures sections when the ERB system is modified.</P>
                <P>This unsafe condition is likely to exist or develop on other helicopters of the same type design. Therefore, the proposed AD would require modifying the ERB by installing the parts contained in a warning relay system modification kit, part number (P/N) 76070-55023-011; a circuit modification kit, P/N 76070-55033-012; and a manifold, relay box, junction box, right-hand relay panel, and wiring harness modification kit, P/N 76070-55207-011. The proposed AD would also require operationally testing the ERB system after each modification. The proposed AD would also require inserting changes contained in a supplement into the RFM.</P>
                <P>These actions would be required to be accomplished in accordance with specified portions of the service information described previously.</P>
                <P>We estimate that this proposed AD would affect 180 helicopters of U.S. registry. It would take about 38 work hours per helicopter to perform the modifications and operational tests at an average labor rate of $85 per work hour. Required parts would cost $13,300 per helicopter. Based on these figures, we estimate the total cost impact of the proposed AD on U.S. operators would be $2,975,400 for the fleet.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>We have determined that this proposed AD would not have federalism implications under Executive Order 13132. Additionally, this proposed AD would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>For the reasons discussed above, I certify that the proposed regulation:</P>
                <P>1. Is not a “significant regulatory action” under Executive Order 12866;</P>
                <P>2. Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979); and</P>
                <P>3. Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <P>We prepared a draft economic evaluation of the estimated costs to comply with this proposed AD. See the AD docket to examine the draft economic evaluation.</P>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, Section 106, describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
                <P>
                    We are issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701, “General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority 
                    <PRTPAGE P="66207"/>
                    because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, pursuant to the authority delegated to me by the Administrator, the Federal Aviation Administration proposes to amend part 39 of the Federal Aviation Regulations (14 CFR part 39) as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                    <P>1. The authority citation for part 39 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                        <P>2. Section 39.13 is amended by adding a new airworthiness directive (AD) to read as follows:</P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">Sikorsky Aircraft Corporation:</E>
                                 Docket No. FAA-2010-0517; Directorate Identifier 2009-SW-73-AD.
                            </FP>
                            <P>
                                <E T="03">Applicability:</E>
                                 Model S-76A helicopters, with an electric rotor brake (ERB), part number (P/N) 76363-09100-012, installed, certificated in any category.
                            </P>
                            <P>
                                <E T="03">Compliance:</E>
                                 Required as indicated, unless accomplished previously.
                            </P>
                            <P>To prevent overheating of the ERB assembly, ignition of the ERB hydraulic fluid, fire in the main gearbox area, and subsequent loss of control of the helicopter, do the following:</P>
                            <P>(a) Within 120 days, modify the ERB by installing:</P>
                            <P>(1) Warning relay system parts contained in modification kit, part number (P/N) 76070-55023-011, and operationally testing the ERB system in accordance with paragraphs 2.A. through 2.F., of Sikorsky Customer Service Bulletin No. 76-66-10B, Revision 1 (pages 2 through 8), dated July 30, 1981, and Revision 2, (pages 1 and 9 through 13) dated November 25, 1981;</P>
                            <P>(2) Circuit breaker and diodes contained in ERB circuit modification kit, P/N 76070-55033-012, and operationally testing the ERB system in accordance with paragraph B. through F. of Sikorsky Customer Service Notice 76-113, dated June 1, 1983; and</P>
                            <P>(3) Manifold, relay box, junction box, right-hand relay panel, and wiring harness parts contained in ERB modification kit, P/N 76070-55207-011, and operationally testing the ERB system in accordance with paragraphs 3.B. through 3.I. of the Accomplishment Instructions of Sikorsky Alert Service Bulletin No. 76-66-48B, Revision B, dated July 8, 2009.</P>
                            <P>(b) After accomplishing paragraph (a) of this AD, insert into the Sikorsky Rotorcraft Flight Manual (RFM) the changes to the “Normal Procedures (Part I, Section II)” and “Emergency Procedures (Part 1, Section III)” contained in Sikorsky RFM, Supplement No. 41, dated September 6, 2005.</P>
                            <P>
                                (c) To request a different method of compliance or a different compliance time for this AD, follow the procedures in 14 CFR 39.19. Contact the Manager, Boston Aircraft Certification Office, FAA, 
                                <E T="04">ATTN:</E>
                                 Caspar Wang, Aviation Safety Engineer, 12 New England Executive Park, Burlington, MA 01803, telephone (781) 238-7799, fax (781) 238-7170, for information about previously approved alternative methods of compliance.
                            </P>
                            <P>(d) The Joint Aircraft System/Component (JASC) Code is 6321: Main Rotor Brake.</P>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Fort Worth, Texas, on October 7, 2011.</DATED>
                        <NAME>Lance T. Gant,</NAME>
                        <TITLE>Acting Manager, Rotorcraft Directorate, Aircraft Certification Service.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27659 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2011-1115; Directorate Identifier 2010-SW-011-AD]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Sikorsky Aircraft Corporation (Sikorsky) Model S-92A Helicopters</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration, DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document proposes adopting a new airworthiness directive (AD) for the Sikorsky Model S-92A helicopters. This proposal would require revising the Operating Limitations section of the Sikorsky Model S-92A Rotorcraft Flight Manual (RFM). This proposal is prompted by the manufacturer's analysis of engine data that revealed the data was inaccurate in dealing with available above specification engine power margin. The actions specified by this proposed AD are intended to prevent the use of inaccurate engine performance data in calculating maximum gross weight by revising the Operating Limitations section of the RFM.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before December 27, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Use one of the following addresses to submit comments on this proposed AD:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov</E>
                        . Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         202-493-2251.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         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>
                        • 
                        <E T="03">Hand Delivery:</E>
                         U.S. Department of Transportation, Docket Operations, M-30, 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>John Coffey, Aviation Safety Engineer, Boston Aircraft Certification Office, 12 New England Executive Park, Burlington, MA 01803, telephone (781) 238-7173, fax (781) 238-7170.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>
                    We invite you to submit any written data, views, or arguments regarding this proposed AD. Send your comments to the address listed under the caption 
                    <E T="02">ADDRESSES</E>
                    . Include the docket number “FAA-2011-1115, Directorate Identifier 2010-SW-011-AD” at the beginning of your comments. We specifically invite comments on the overall regulatory, economic, environmental, and energy aspects of the proposed AD. We will consider all comments received by the closing date and may amend the proposed AD in light of those comments.
                </P>
                <P>
                    We will post all comments we receive, without change, to 
                    <E T="03">http://www.regulations.gov,</E>
                     including any personal information you provide. We will also post a report summarizing each substantive verbal contact with FAA personnel concerning this proposed rulemaking. Using the search function of our docket web site, you can find and read the comments to any of our dockets, including the name of the individual who sent or signed the comment. You may review the DOT's complete Privacy Act Statement in the 
                    <E T="04">Federal Register</E>
                     published on April 11, 2000 (65 FR 19477-78).
                </P>
                <HD SOURCE="HD1">Examining the Docket</HD>
                <P>
                    You may examine the docket that contains the proposed AD, any comments, and other information on the Internet at 
                    <E T="03">http://www.regulations.gov</E>
                     or in person at the Docket Operations office between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The Docket Operations office (telephone (800) 647-5527) is located in Room W12-140 on the ground floor of the West Building at the street address stated in the 
                    <E T="02">ADDRESSES</E>
                     section. Comments will be available in the AD docket shortly after receipt.
                    <PRTPAGE P="66208"/>
                </P>
                <HD SOURCE="HD1">Discussion</HD>
                <P>
                    This document proposes adopting a new AD for the Sikorsky Model S-92A helicopters. This proposal would require revising the Operating Limitations section, Part 1, Section 1, 
                    <E T="03">Weight Limits,</E>
                     of the Sikorsky Model S-92A RFM with the following statement “Performance credit for above specification engine power margin is prohibited.” Engine power margin is determined through power assurance checks. Previous flight manual revisions allowed for the use of above specification engine power margin as shown in the circled area of Figure 1 of this AD. The use of above-specification engine power margin is now being prohibited. Sikorsky has published various RFM revisions correcting the charts in Parts I and IV of the RFM. If those revisions have previously been incorporated into the RFM, the RFM revision specified by this proposed AD would not be required. The RFM revisions, all dated April 9, 2008, are as follows:
                </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s25,xs60">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Affected RFM</CHED>
                        <CHED H="1">
                            Revision with 
                            <LI>correct charts</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">S92A-RFM-002</ENT>
                        <ENT>Revision 8.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">S92A-RFM-003</ENT>
                        <ENT>Revision 7.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">S92A-RFM-004</ENT>
                        <ENT>Revision 6.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">S92A-RFM-005</ENT>
                        <ENT>Revision 5.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">S92A-RFM-006</ENT>
                        <ENT>Revision 6.</ENT>
                    </ROW>
                </GPOTABLE>
                <P> This proposal is prompted by the manufacturer's analysis of engine data that revealed the data was inaccurate in dealing with available engine power margin. The actions specified by this proposed AD are intended to prevent the use of inaccurate performance data in calculating maximum gross weight by revising the Operating Limitations section of the RFM.</P>
                <P>This unsafe condition is likely to exist or develop on other helicopters of the same type design. Therefore, the proposed AD would require inserting a limitation into the Operating Limitation section of the RFM prohibiting the use of power margin percentage credit in calculating gross weight and inserting the revisions into the Operating Limitations, Part 1, Section 1, of Sikorsky RFM SA S92A-RFM-002, -003, -004, -005, and -006.</P>
                <P>We estimate that this proposed AD would affect 37 helicopters of U.S. registry, and the proposed actions would take about 1 work hour per helicopter to insert the revisions into the RFM at an average labor rate of $85 per work hour. Parts costs are not associated with this AD. Based on these figures, we estimate the total cost impact of the proposed AD on U.S. operators would be $3,145.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>We have determined that this proposed AD would not have federalism implications under Executive Order 13132. Additionally, this proposed AD would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>
                    <E T="03">For the reasons discussed above, I certify that the proposed regulation:</E>
                </P>
                <P>1. Is not a “significant regulatory action” under Executive Order 12866;</P>
                <P>2. Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979);</P>
                <P>3. Will not affect intrastate aviation in Alaska to the extent that it justifies making a regulatory distinction; and</P>
                <P>4. Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <P>We prepared an economic evaluation of the estimated costs to comply with this proposed AD. See the AD docket to examine the draft economic evaluation.</P>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, Section 106, describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
                <P>We are issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701, “General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, pursuant to the authority delegated to me by the Administrator, the Federal Aviation Administration proposes to amend part 39 of the Federal Aviation Regulations (14 CFR part 39) as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                    <P>1. The authority citation for part 39 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                        <P>2. Section 39.13 is amended by adding a new airworthiness directive to read as follows:</P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">Sikorsky Aircraft Corporation:</E>
                                 Docket No. FAA-2011-1115; Directorate Identifier 2010-SW-011-AD.
                            </FP>
                            <P>
                                <E T="03">Applicability:</E>
                                 Model S-92A helicopters, certificated in any category.
                            </P>
                            <P>
                                <E T="03">Compliance:</E>
                                 Within 90 days, unless accomplished previously.
                            </P>
                            <P>To prevent the use of inaccurate performance data in calculating the maximum gross weight, revise the Operating Limitations section of the Rotorcraft Flight Manual (RFM) as follows:</P>
                            <P>
                                (a) By making pen and ink changes, insert into the Operating Limitations section, Part 1, Section 1, 
                                <E T="03">Weight Limits,</E>
                                 of RFM SA S92A-RFM-002, -003, -004, -005, and  -006 the following limitation “Performance credit for above specification engine power margin is prohibited.”
                            </P>
                            <P>(b) If the RFM already contains the revisions appropriate for your helicopter as listed in the following Table 1, all dated April 9, 2008, with the correct performance charts, without the performance credit as depicted in the circled area of Figure 1 of this AD, the operating limitation required by paragraph (a) of this AD does not need to be inserted into the RFM.</P>
                            <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s50,xs60">
                                <TTITLE>Table 1</TTITLE>
                                <BOXHD>
                                    <CHED H="1">Affected RFM</CHED>
                                    <CHED H="1">
                                        Revision with 
                                        <LI>correct charts</LI>
                                    </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="01">S92A-RFM-002</ENT>
                                    <ENT>Revision 8.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">S92A-RFM-003</ENT>
                                    <ENT>Revision 7.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">S92A-RFM-004</ENT>
                                    <ENT>Revision 6.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">S92A-RFM-005</ENT>
                                    <ENT>Revision 5.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">S92A-RFM-006</ENT>
                                    <ENT>Revision 6.</ENT>
                                </ROW>
                            </GPOTABLE>
                            <NOTE>
                                <HD SOURCE="HED">Note 1:</HD>
                                <P>Previous RFM revisions allowed for the use of above-specification engine power margin as depicted in the circled area of Figure 1 of this AD.</P>
                            </NOTE>
                            <GPH SPAN="3" DEEP="469">
                                <PRTPAGE P="66209"/>
                                <GID>EP26OC11.066</GID>
                            </GPH>
                            <P>
                                (c) To request a different method of compliance or a different compliance time for this AD, follow the procedures in 14 CFR 39.19. Contact the Manager, Boston Aircraft Certification Office, FAA, 
                                <E T="03">Attn:</E>
                                 John Coffey Aviation Safety Engineer, 12 New England Executive Park, Burlington, MA 01803, telephone (781) 238-7173, fax (781) 238-7170, for information about previously approved alternative methods of compliance.
                            </P>
                            <P>(d) The Joint Aircraft System/Component (JASC) Code is 7200: Engine (Turbine/Turboprop).</P>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Fort Worth, Texas, on October 7, 2011.</DATED>
                        <NAME>Lance T. Gant,</NAME>
                        <TITLE>Acting Manager, Rotorcraft Directorate, Aircraft Certification Service.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27670 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2011-1113; Directorate Identifier 2009-SW-53-AD]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Sikorsky Aircraft Corporation (Sikorsky) Model S-92A Helicopters</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration, DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This document proposes adopting a new airworthiness directive (AD) for the Sikorsky Model S-92A helicopters. This proposal would require inspecting each tail rotor blade (blade) for mislocated aluminum wire mesh in the blade skin. This proposal is prompted by the discovery that blades were manufactured with aluminum wire mesh mislocated, leaving portions of the graphite torque tube (spar) region unprotected from a lightning strike. This condition can exist in both the upper and lower blade skin airfoils. The actions specified by this proposed AD are intended to detect mislocated blade wire mesh and to prevent spar delamination, loss of the blade tip cap during a lightning strike, blade 
                        <PRTPAGE P="66210"/>
                        imbalance, loss of a blade, and subsequent loss of control of the helicopter.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before December 27, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Use one of the following addresses to submit comments on this proposed AD:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         202-493-2251.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         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>
                        • 
                        <E T="03">Hand Delivery:</E>
                         U.S. Department of Transportation, Docket Operations, M-30, 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>
                    <P>
                        You may get the service information identified in this proposed AD from Sikorsky Aircraft Corporation, Attn: Manager, Commercial Technical Support, mailstop s581a, 6900 Main Street, Stratford, CT, telephone (203) 383-4866, e-mail address 
                        <E T="03">tsslibrary@sikorsky.com,</E>
                         or at 
                        <E T="03">http://www.sikorsky.com.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Nicholas Faust, Aviation Safety Engineer, Boston Aircraft Certification Office, 12 New England Executive Park, Burlington, MA 01803, telephone (781) 238-7763, fax (781) 238-7170.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>
                    We invite you to submit any written data, views, or arguments regarding this proposed AD. Send your comments to the address listed under the caption 
                    <E T="02">ADDRESSES</E>
                    . Include the docket number “FAA-2011-1113, Directorate Identifier 2009-SW-53-AD” at the beginning of your comments. We specifically invite comments on the overall regulatory, economic, environmental, and energy aspects of the proposed AD. We will consider all comments received by the closing date and may amend the proposed AD in light of those comments.
                </P>
                <P>
                    We will post all comments we receive, without change, to 
                    <E T="03">http://www.regulations.gov,</E>
                     including any personal information you provide. We will also post a report summarizing each substantive verbal contact with FAA personnel concerning this proposed rulemaking. Using the search function of our docket Web site, you can find and read the comments to any of our dockets, including the name of the individual who sent or signed the comment. You may review the DOT's complete Privacy Act Statement in the 
                    <E T="04">Federal Register</E>
                     published on April 11, 2000 (65 FR 19477-78).
                </P>
                <HD SOURCE="HD1">Examining the Docket</HD>
                <P>
                    You may examine the docket that contains the proposed AD, any comments, and other information on the Internet at 
                    <E T="03">http://www.regulations.gov</E>
                     or in person at the Docket Operations office between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The Docket Operations office (telephone (800) 647-5527) is located in Room W12-140 on the ground floor of the West Building at the street address stated in the 
                    <E T="02">ADDRESSES</E>
                     section. Comments will be available in the AD docket shortly after receipt.
                </P>
                <HD SOURCE="HD1">Discussion</HD>
                <P>This document proposes adopting a new AD for the Sikorsky Model S-92A helicopters. This proposal would require inspecting each blade for mislocated aluminum wire mesh in the blade skin. This proposal is prompted by the discovery that blades were manufactured with aluminum wire mesh mislocated, leaving portions of the graphite torque tube (spar) region unprotected from a lightning strike. This condition can exist on both the upper and lower blade skin airfoils. The actions specified by this proposed AD are intended to detect mislocated blade wire mesh to prevent spar delamination and loss of the blade tip cap during a lightning strike leading to blade imbalance, loss of a blade, and subsequent loss of control of the helicopter.</P>
                <P>We have reviewed Sikorsky Special Service Instructions SSI No. 92-021A, dated October 21, 2009 (SSI), which specifies inspecting the blade for mislocated blade wire mesh. Two options are identified in the SSI. One option is to conduct an eddy current inspection and the other option is to conduct a visual inspection after sanding to determine if there is mislocated wire mesh.</P>
                <P>This unsafe condition is likely to exist or develop on other helicopters of the same type design. Therefore, the proposed AD would require inspecting each blade to determine if the wire mesh is mislocated and replacing the blade with an airworthy blade if the wire mesh is mislocated. The actions would be required to be done by following the service information described previously.</P>
                <P>We estimate that this proposed AD would affect 44 helicopters of U.S. registry. There are 486 suspect blades worldwide, and we assume 29 percent (141) of those blades may be on helicopters of U.S. registry. We estimate that inspecting a blade for mislocated wire mesh would take about 4 work hours per blade, assuming all operators opt to do the blade sanding inspection rather than the eddy current inspection, at an average labor rate of $85 per work hour. Required parts would cost about $13,000 for each blade repaired by the manufacturer or $180,000 for each new blade. The total cost of the proposed AD for U.S. operators would be $3,215,940, assuming 51 blades are found with mislocated wire mesh, and assuming 36 of those blades are replaced with blades repaired by the manufacturer and 15 blades are replaced with new blades.</P>
                <HD SOURCE="HD1">Regulatory Findings</HD>
                <P>We have determined that this proposed AD would not have federalism implications under Executive Order 13132. Additionally, this proposed AD would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>
                    <E T="03">For the reasons discussed above, I certify that the proposed regulation:</E>
                </P>
                <P>1. Is not a “significant regulatory action” under Executive Order 12866;</P>
                <P>2. Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979);</P>
                <P>3. Will not affect intrastate aviation in Alaska to the extent that it justifies making a regulatory distinction; and</P>
                <P>4. Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <P>We prepared a draft economic evaluation of the estimated costs to comply with this proposed AD. See the AD docket to examine the draft economic evaluation.</P>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, Section 106, describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
                <P>
                    We are issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701, “General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures 
                    <PRTPAGE P="66211"/>
                    the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, pursuant to the authority delegated to me by the Administrator, the Federal Aviation Administration proposes to amend part 39 of the Federal Aviation Regulations (14 CFR part 39) as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                    <P>1. The authority citation for part 39 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                        <P>2. Section 39.13 is amended by adding a new airworthiness directive to read as follows:</P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">Sikorsky Aircraft Corporation:</E>
                                 Docket No. FAA-2011-1113; Directorate Identifier 2009-SW-53-AD.
                            </FP>
                            <P>
                                <E T="03">Applicability:</E>
                                 Model S-92A helicopters, tail rotor blade assembly (blade), part numbers (P/N) 92170-11000-044, -045, and -046, with a serial number with a prefix of “A111” and a number equal to or less than “-00585,” installed, certificated in any category.
                            </P>
                            <P>
                                <E T="03">Compliance:</E>
                                 Required as indicated, unless accomplished previously.
                            </P>
                            <P>To detect mislocated blade wire mesh and to prevent spar delamination, loss of the blade tip cap during a lightning strike, blade imbalance, loss of a blade, and subsequent loss of control of the helicopter, do the following:</P>
                            <P>(a) Within 60 days, inspect the upper and lower airfoils of each tail rotor blade to determine if the wire mesh is mislocated.</P>
                            <P>(1) Inspect by using either an eddy current inspection in accordance with paragraphs B.(1)(a) through B.(1)(o) or using the hand-sanding method and visually inspecting in accordance with paragraphs B.(2)(a) through B.(2)(d) of Sikorsky Special Service Instructions SSI No. 92-021A, Revision A, dated October 21, 2009, except you are not required to contact or report nonconforming blades to the manufacturer. If you sand and visually inspect and confirm the correct location of the wire mesh, touch-up and repaint the sanded area.</P>
                            <P>(2) If there is a blade with a mislocated wire mesh, before further flight, replace the blade with an airworthy blade.</P>
                            <P>
                                (b) To request a different method of compliance or a different compliance time for this AD, follow the procedures in 14 CFR 39.19. Contact the Manager, Boston Aircraft Certification Office, FAA, 
                                <E T="03">Attn:</E>
                                 Nicholas Faust, Aviation Safety Engineer, Boston Aircraft Certification Office, 12 New England Executive Park, Burlington, MA 01803, telephone (781) 238-7763, fax (781) 238-7170, for information about previously approved alternative methods of compliance.
                            </P>
                            <P>(c) The Joint Aircraft System/Component (JASC) Code is 6410, Tail Rotor Blades.</P>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Fort Worth, Texas, on October 7, 2011.</DATED>
                        <NAME>Lance T. Gant,</NAME>
                        <TITLE>Acting Manager, Rotorcraft Directorate, Aircraft Certification Service.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27669 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <CFR>18 CFR Part 35</CFR>
                <DEPDOC>[Docket No. RM11-17-000]</DEPDOC>
                <SUBJECT>Enhancement of Electricity Market Surveillance and Analysis Through Ongoing Electronic Delivery of Data From Regional Transmission Organizations and Independent System Operators</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Energy Regulatory Commission, DOE.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P/>
                </ACT>
                Notice of proposed rulemaking.
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Energy Regulatory Commission (Commission) proposes to revise its regulations to require each regional transmission organization (RTO) and independent system operator (ISO) to electronically deliver to the Commission, on an ongoing basis, data related to the markets that it administers. Ongoing electronic delivery of data relating to physical and virtual offers and bids, market awards, resource outputs, marginal cost estimates, shift factors, financial transmission rights, internal bilateral contracts, and interchange pricing will facilitate the Commission's development and evaluation of its policies and regulations and will enhance Commission efforts to detect anti-competitive or manipulative behavior, or ineffective market rules, thereby helping to ensure just and reasonable rates.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on the proposed rule are due December 27, 2011.</P>
                    <P>Comments, identified by docket number, may be filed in the following ways:</P>
                    <P>
                        • 
                        <E T="03">Electronic Filing</E>
                         through 
                        <E T="03">http://www.ferc.gov.</E>
                         Documents created electronically using word processing software should be filed in native applications or print-to-PDF format and not in a scanned format.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail/Hand Delivery:</E>
                         Those unable to file electronically may mail or hand-deliver comments to: Federal Energy Regulatory Commission, Secretary of the Commission, 888 First Street, NE., Washington, DC 20426.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         For detailed instructions on submitting comments and additional information on the rulemaking process, see the Comment Procedures Section of this document.
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <FP SOURCE="FP-1">
                        William Sauer (Technical Information), Office of Enforcement, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, (202) 502-6639, 
                        <E T="03">william.sauer@ferc.gov.</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        Christopher Daignault (Legal Information), Office of the General Counsel, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, (202) 502-8286, 
                        <E T="03">christopher.daignault@ferc.gov.</E>
                    </FP>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Notice of Proposed Rulemaking</HD>
                <DATE>October 20, 2011.</DATE>
                <P>
                    1. In this Notice of Proposed Rulemaking (NOPR), the Federal Energy Regulatory Commission (Commission) proposes, pursuant to sections 301(b) and 307(a) of the Federal Power Act (FPA),
                    <SU>1</SU>
                    <FTREF/>
                     to amend its regulations to require each regional transmission organization (RTO) and independent system operator (ISO) to electronically deliver to the Commission, on an ongoing basis, data related to the markets that it administers. Ongoing electronic delivery of data relating to physical and virtual offers and bids, market awards, resource outputs, marginal cost estimates, shift factors, financial transmission rights (FTR), internal bilateral contracts, and interchange pricing will facilitate the Commission's development and evaluation of its policies and regulations and will enhance Commission efforts to detect anti-competitive or manipulative behavior, or ineffective market rules, thereby helping to ensure just and reasonable rates.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         16 U.S.C. 825(b), 825f(a).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    2. Wholesale electricity markets have witnessed tremendous change in recent years. In the decades after the 1935 enactment of the FPA, the industry was characterized by self-sufficient, vertically integrated utilities. Most utilities built their own generation, transmission, and distribution facilities 
                    <PRTPAGE P="66212"/>
                    and sold electricity to their own wholesale and retail customers. During this time, the Commission regulated jurisdictional entities' rates through traditional cost-based ratemaking. Cost-based rate regulation ensures that rates are just and reasonable by administratively determining an entity's cost of providing service. Changes in national policy and other forces led to increased coordination and competition in the late 1960s and 1970s,
                    <SU>2</SU>
                    <FTREF/>
                     and the enactment of the Public Utility Regulatory Policies Act (PURPA).
                    <SU>3</SU>
                    <FTREF/>
                     The 1980s and early 1990s experienced an increased adoption of market-based ratemaking and wholesale power sales competition to promote efficiency and to lower wholesale power prices.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Counted among such forces are the Northeast blackout of 1965 and the responses to perceived transmission system insufficiencies, as well as the subsequent oil crisis of 1973. For a discussion of developments following the 1965 blackout, 
                        <E T="03">see</E>
                         William F. Fox, Jr., 
                        <E T="03">Federal Regulation of Energy</E>
                         749, 755 (1983 &amp; Supp. 1993), and Stephen Breyer and Paul W. MacAvoy, 
                        <E T="03">The Federal Power Commission and the Coordination Problem in the Electrical Power Industry,</E>
                         46 S. Cal. L. Rev. 661, 661 (1973).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Public Utility Regulatory Policies Act of 1978, Pub. L. No. 95-617, 92 Stat. 3117 (1978) (codified as amended in scattered sections of 16 U.S.C.); 
                        <E T="03">see, e.g.,</E>
                         16 U.S.C. 824a-3, 824i, 824j.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See, e.g., Louisville Gas &amp; Elec. Co.,</E>
                         62 FERC ¶ 61,016, at 61,143 &amp; n.16, 61,149 (1993) (accepting non-traditional, market-based rates as consistent with primary regulatory goal of ensuring lowest reasonable cost energy to consumers, provided service is reliable and the seller demonstrates a lack of market power); 
                        <E T="03">Pac. Gas &amp; Elec. Co.,</E>
                         38 FERC ¶ 61,242, at 61,790 (1987) (accepting proposed competitive rates because “competition * * * encourages utilities to make efficient decisions with a minimum of regulatory intervention [and, u]ltimately, consumers should benefit from lower prices as competition improves efficiency.”), 
                        <E T="03">modifying on other ground,</E>
                         47 FERC ¶ 61,121 (1989), 
                        <E T="03">modified,</E>
                         50 FERC ¶ 61,339 (1990), 
                        <E T="03">modified sub nom. W. Sys. Power Pool,</E>
                         55 FERC ¶ 61,099, at 61,319 (addressing applicant's failure to eliminate anticompetitive effects by mitigating market power), 
                        <E T="03">granting stay,</E>
                         55 FERC ¶ 61,154, 
                        <E T="03">reh'g granted in part,</E>
                         55 FERC ¶ 61,495 (1991), 
                        <E T="03">modified,</E>
                         59 FERC ¶ 61,249 (1992); 
                        <E T="03">Pub. Serv. Co. of New Mexico,</E>
                         25 FERC ¶ 61,469, at 62,038 (1983) (averring that “competition penalizes a seller that is inefficient or has an unreasonable pricing strategy[; consequently,] consumers * * * benefit because the improvements in efficiency lead to lower prices.”); 
                        <E T="03">see also Heartland Energy Servs., Inc.,</E>
                         68 FERC ¶ 61,223 (1994) (reviewing early Commission decisions granting market-based rate authority).
                    </P>
                </FTNT>
                <P>
                    3. National policy fostered further market evolution by encouraging increased competition among generators through the Energy Policy Act of 1992 (EPAct 1992).
                    <SU>5</SU>
                    <FTREF/>
                     Specifically, EPAct 1992 eased regulatory restrictions so that independent and affiliate generators could more easily enter, and compete in, wholesale electricity markets. EPAct 1992 also expanded the Commission's authority to address undue discrimination in transmission access in order to promote wholesale competition. In subsequent orders, the Commission found that the availability of transmission service enhances competition in power markets, by increasing power supply options of buyers and power sales options of sellers, and leads to lower rates for consumers.
                    <SU>6</SU>
                    <FTREF/>
                     By the mid-1990s, the Commission had determined that additional measures were needed to address undue discrimination in transmission access and issued Order Nos. 888
                    <SU>7</SU>
                    <FTREF/>
                     and 889,
                    <SU>8</SU>
                    <FTREF/>
                     which required “open access” transmission service. In doing so, the Commission explained that its action “remove[s] impediments to competition in the wholesale power marketplace and * * * bring[s] more efficient, lower cost power to the Nation's electricity customers.” 
                    <SU>9</SU>
                    <FTREF/>
                     The Commission subsequently issued Order No. 890,
                    <SU>10</SU>
                    <FTREF/>
                     to further remedy undue discrimination and thereby remove barriers to competition.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Pub. L. No. 102-486, 106 Stat. 2776 (1992).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">Fla. Mun. Power Agency v. Fla. Power &amp; Light Co.,</E>
                         65 FERC ¶ 61,125, at 61,615, 
                        <E T="03">reh'g dismissed,</E>
                         65 FERC ¶ 61,372 (1993), 
                        <E T="03">final order,</E>
                         67 FERC ¶ 61,167 (1994), 
                        <E T="03">order on reh'g,</E>
                         74 FERC ¶ 61,006 (1996).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">Promoting Wholesale Competition Through Open Access Non-Discriminatory Transmission Services by Public Utilities; Recovery of Stranded Costs by Public Utilities and Transmitting Utilities,</E>
                         Order No. 888, FERC Stats. &amp; Regs. ¶ 31,036 (1996), 
                        <E T="03">order on reh'g,</E>
                         Order No. 888-A, FERC Stats. &amp; Regs. ¶ 31,048, 
                        <E T="03">order on reh'g,</E>
                         Order No. 888-B, 81 FERC ¶ 61,248 (1997), 
                        <E T="03">order on reh'g,</E>
                         Order No. 888-C, 82 FERC ¶ 61,046 (1998), 
                        <E T="03">aff'd in relevant part sub nom. Transmission Access Policy Study Group</E>
                         v.
                        <E T="03"> FERC,</E>
                         225 F.3d 667 (D.C. Cir. 2000), 
                        <E T="03">aff'd sub nom. New York</E>
                         v.
                        <E T="03"> FERC,</E>
                         535 U.S. 1 (2002).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">Open Access Same-Time Information System and Standards of Conduct,</E>
                         Order No. 889, FERC Stats. &amp; Regs. ¶ 31,035 (1996), 
                        <E T="03">order on reh'g,</E>
                         Order No. 889-A, FERC Stats. &amp; Regs. ¶ 31,049, 
                        <E T="03">reh'g denied,</E>
                         Order No. 889-B, 81 FERC ¶ 61,253 (1997).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Order No. 888, FERC Stats. &amp; Regs. ¶ 31,036 at 31,634.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">Preventing Undue Discrimination and Preference in Transmission Service,</E>
                         Order No. 890, FERC Stats. &amp; Regs. ¶ 31,241, 
                        <E T="03">order on reh'g,</E>
                         Order No. 890-A, FERC Stats. &amp; Regs. ¶ 31,261 (2007), 
                        <E T="03">order on reh'g,</E>
                         Order No. 890-B, 123 FERC ¶ 61,299 (2008),
                        <E T="03"> order on reh'g,</E>
                         Order No. 890-C, 126 FERC ¶ 61,228 (2009), 
                        <E T="03">order on clarification,</E>
                         Order No. 890-D, 129 FERC ¶ 61,126 (2009).
                    </P>
                </FTNT>
                <P>
                    4. In addition to addressing undue discrimination in transmission access, Order No. 888 encouraged the formation of ISOs. The Commission posited that “ISOs have great potential to assist us and the industry to help provide regional efficiencies, to facilitate economically efficient pricing, and, especially in the context of power pools, to remedy undue discrimination and mitigate market power.” 
                    <SU>11</SU>
                    <FTREF/>
                     To facilitate ISO formation and foster independent operation of the transmission grid, the Commission suggested that utilities should voluntarily transfer operating control of their transmission facilities to an ISO. Four years later, in Order No. 2000,
                    <SU>12</SU>
                    <FTREF/>
                     the Commission encouraged the voluntary formation of RTOs to administer the transmission grid on a regional basis. To date, the Commission has approved six RTOs and ISOs: PJM Interconnection, L.L.C. (PJM); New York Independent System Operator, Inc. (NYISO); Midwest Independent Transmission System Operator, Inc. (Midwest ISO); ISO New England Inc. (ISO-NE); California Independent System Operator Corporation (CAISO); and Southwest Power Pool, Inc. (SPP). Together, these six RTOs and ISOs serve more than half of the United States' wholesale electricity demand.
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Order No. 888, FERC Stats. &amp; Regs. ¶ 31,036 at 31,652; 
                        <E T="03">see also id.</E>
                         at 31,730-32.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">Regional Transmission Organizations,</E>
                         Order No. 2000, 65 FR 809 (Jan. 6, 2000), FERC Stats. &amp; Regs. ¶ 31,089 (1999), 
                        <E T="03">order on reh'g,</E>
                         Order No. 2000-A, FERC Stats. &amp; Regs. ¶ 31,092 (2000), 
                        <E T="03">aff'd sub nom. Pub. Util. Dist. No. 1 of Snohomish County, Washington</E>
                         v.
                        <E T="03"> FERC,</E>
                         272 F.3d 607 (D.C. Cir. 2001).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See</E>
                         ISO/RTO Council, 
                        <E T="03">Progress of Organized Wholesale Electriciy Markets in North America</E>
                         1 (2007), 
                        <E T="03">http://www.isorto.org/atf/cf/%7B5B4E85C6-7EAC-40A0-8DC3-003829518EBD%7D/IRC_State_of_the_Markets_Report_103007.pdf.</E>
                    </P>
                </FTNT>
                <P>5. The wholesale electricity markets operated by Commission-approved RTOs/ISOs have evolved since their inception and will likely continue to do so as advances in technology usher in additional competing resources, computational efficiencies, new products, and new types of market participants. Today, for example, market participants include independent generating resources, storage devices, demand response and energy efficiency providers, marketers and traders, vertically integrated utilities, power marketing administrations, municipalities and cooperatives, among others.</P>
                <P>
                    6. Substantial changes also have occurred with respect to the manner in which electricity is bought and sold. For example, when the IntercontinentalExchange (ICE) was established in 2000, the vast majority of electricity sales transacted on ICE contained requirements for physical delivery. Electricity bought or sold without requirements for physical delivery is commonly referred to as a financial electricity product. Beginning in 2004, the volume of financial electricity products bought and sold on ICE eclipsed that of electricity bought and sold on ICE with physical delivery requirements. The financial electricity product volumes on ICE also surpassed electricity volumes reported to the Commission through Electric Quarterly 
                    <PRTPAGE P="66213"/>
                    Reports (EQR) in several markets.
                    <SU>14</SU>
                    <FTREF/>
                     Given that financial electricity products commonly settle using published prices from Commission-jurisdictional markets, changes in the prices of physical electricity products impact the values of both physical and financial electricity products.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See</E>
                         Federal Energy Regulatory Commission, 
                        <E T="03">2008 State of the Markets Report</E>
                         (2009), 
                        <E T="03">available at http://www.ferc.gov/market-oversight/st-mkt-ovr/2008-som-final.pdf.</E>
                         We also note that financial electricity products may be transacted (1) Through exchanges besides ICE (
                        <E T="03">e.g.,</E>
                         NYMEX and Nodal Exchange), (2) by voice brokers, (3) bilaterally, or (4) by using other means.
                    </P>
                </FTNT>
                <P>
                    7. Recognizing the importance of information relating to market trading and market oversight, the Commission issued Order No. 2001 
                    <SU>15</SU>
                    <FTREF/>
                     and Order No. 697,
                    <SU>16</SU>
                    <FTREF/>
                     establishing reporting requirements for entities selling under market-based rates. As one keen observer stated, in this regard, “[i]nformation is the key to a viable electricity market and to preventing market manipulation.” 
                    <SU>17</SU>
                    <FTREF/>
                     In addition, the Energy Policy Act of 2005 (EPAct 2005) 
                    <SU>18</SU>
                    <FTREF/>
                     gave the Commission expanded authority to address market manipulation,
                    <SU>19</SU>
                    <FTREF/>
                     including the ability to assess civil fines and seek criminal penalties.
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">Revised Public Utility Filing Requirements,</E>
                         Order No. 2001, FERC Stats. &amp; Regs. ¶ 31,127, 
                        <E T="03">reh'g denied,</E>
                         Order No. 2001-A, 100 FERC ¶ 61,074, 
                        <E T="03">reh'g denied,</E>
                         Order No. 2001-B, 100 FERC ¶ 61,342, 
                        <E T="03">order directing filing,</E>
                         Order No. 2001-C, 101 FERC ¶ 61,314 (2002), 
                        <E T="03">order directing filing,</E>
                         Order No. 2001-D, 102 FERC ¶ 61,334, 
                        <E T="03">order refining filing requirements,</E>
                         Order No. 2001-E, 105 FERC ¶ 61,352 (2003), 
                        <E T="03">order on clarification,</E>
                         Order No. 2001-F, 106 FERC ¶ 61,060 (2004), 
                        <E T="03">order revising filing requirements,</E>
                         Order No. 2001-G, 120 FERC ¶ 61,270, 
                        <E T="03">order on reh'g and clarification,</E>
                         Order No. 2001-H, 121 FERC ¶ 61,289 (2007), 
                        <E T="03">order revising filing requirements,</E>
                         Order No. 2001-I, FERC Stats. &amp; Regs. ¶ 31,282 (2008).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">Market-Based Rates for Wholesale Sales of Electric Energy, Capacity and Ancillary Services by Public Utilities,</E>
                         Order No. 697, FERC Stats. &amp; Regs. ¶ 31,252, 
                        <E T="03">clarified,</E>
                         121 FERC ¶ 61,260 (2007), 
                        <E T="03">order on reh'g,</E>
                         Order No. 697-A, FERC Stats. &amp; Regs. ¶ 31,268, 
                        <E T="03">clarified,</E>
                         124 FERC ¶ 61,055, 
                        <E T="03">order on reh'g,</E>
                         Order No. 697-B, FERC Stats. &amp; Regs. ¶ 31,285 (2008), 
                        <E T="03">order on reh'g,</E>
                         Order No. 697-C, FERC Stats. &amp; Regs. ¶ 31,291 (2009), 
                        <E T="03">order on reh'g,</E>
                         Order No. 697-D, FERC Stats. &amp; Regs. ¶ 31,305 (2010), 
                        <E T="03">aff'd sub nom. Montana Consumer Counsel</E>
                         v.
                        <E T="03"> FERC,</E>
                         No. 08-71827, 2011 U.S. App. LEXIS 20724 (9th Cir. Oct. 13, 2011). In its decision upholding Order No. 697, the Ninth Circuit Court of Appeals noted that monitoring must be accompanied by enforcement because “[w]ithout enforcement, there is little reason to believe that sellers will police themselves.” 
                        <E T="03">Montana Consumer Counsel,</E>
                         2011 U.S. App. LEXIS 20724 at *19 n.5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         Charles H. Koch, Jr., 
                        <E T="03">Collaborative Governance: Lessons for Europe from U.S. Electricity Restructuring,</E>
                         61 Admin. L. Rev. 71, 97 (2009).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         Public Law No. 109-58, 119 Stat. 594 (2005).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See, e.g.,</E>
                         16 U.S.C. 824v.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See</E>
                         16 U.S.C. 825o (criminal penalties); 16 U.S.C. 825o-1 (civil fines).
                    </P>
                </FTNT>
                <P>
                    8. Independent market monitoring by RTO/ISO market monitoring units (MMU) is an important means to evaluate market developments and to identify and deter market abuses and manipulation. In Order No. 2000, the Commission identified market monitoring as a basic function of an RTO.
                    <SU>21</SU>
                    <FTREF/>
                     The Commission refined its approach to MMUs in a 2005 policy statement and in Order No. 719.
                    <SU>22</SU>
                    <FTREF/>
                     In the 2005 Policy Statement, the Commission outlined tasks for MMUs to perform in order to enhance the competitive structure of RTO/ISO markets.
                    <SU>23</SU>
                    <FTREF/>
                     Subsequently, in Order No. 719, the Commission further clarified requirements for MMU functions, independence, and information sharing.
                    <SU>24</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         Prior to this first generic consideration of MMUs in Order No. 2000, the Commission addressed market monitoring in connection with individual RTO/ISO proposals
                        <E T="03">. See Pac. Gas &amp; Elec. Co.,</E>
                         77 FERC ¶ 61,265 (1996), 
                        <E T="03">order on reh'g,</E>
                         81 FERC ¶ 61,122 (1997), 
                        <E T="03">order on clarification,</E>
                         83 FERC ¶ 61,033 (1998) (requiring the ISO to file a detailed monitoring plan and listing minimum elements for such a plan); 
                        <E T="03">Pennsylvania-New Jersey-Maryland Interconnection,</E>
                         81 FERC ¶ 61,257 (1997) (requiring PJM Interconnection, L.L.C. to develop a market monitoring program to evaluate market power and market design flaws).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">Market Monitoring Units in Regional Transmission Organizations and Independent System Operators,</E>
                         111 FERC ¶ 61,267 (2005) (2005 Policy Statement); 
                        <E T="03">Wholesale Competition in Regions with Organized Electric Markets,</E>
                         Order No. 719, FERC Stats. &amp; Regs. ¶ 31,281 (2008), 
                        <E T="03">order on reh'g,</E>
                         Order No. 719-A, FERC Stats. &amp; Regs. ¶ 31,292 (2009), 
                        <E T="03">order on reh'g,</E>
                         Order No. 719-B, 129 FERC ¶ 61,252 (2009).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         2005 Policy Statement, 111 FERC ¶ 61,267 at P 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         Specifically, MMU functions consist of evaluating existing and proposed market rules, tariff provisions, and market design elements and recommending changes, if applicable; reviewing and reporting on the performance of wholesale markets; and identifying and notifying the Commission of behavior that may require investigation. 
                        <E T="03">See</E>
                         Order No. 719, FERC Stats. &amp; Regs. ¶ 31,281 at P 354.
                    </P>
                </FTNT>
                <P>
                    9. The Commission has acknowledged that MMUs perform a vital and necessary function in market oversight 
                    <SU>25</SU>
                    <FTREF/>
                     but that they do not supplant the Commission's authority.
                    <SU>26</SU>
                    <FTREF/>
                     Rather, MMUs are designed to provide the Commission with an 
                    <E T="03">additional</E>
                     means of detecting market power abuses, market design flaws, and opportunities for improvements in market efficiency.
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See, e.g.,</E>
                         Order No. 719, FERC Stats. &amp; Regs. ¶ 31,281 at P 314.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         Order No. 2000, FERC Stats. &amp; Regs. ¶ 31,089 at 31,156-57.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Discussion</HD>
                <P>10. In this NOPR, the Commission proposes to revise its regulations to require each RTO and ISO to electronically deliver to the Commission, on an ongoing, non-public basis, data related to the markets that it administers; namely, data relating to physical and virtual offers and bids, market awards, resource outputs, marginal cost estimates, shift factors, FTRs, internal bilateral contracts, and interchange pricing. To facilitate such ongoing, electronic delivery, the Commission proposes that each RTO and ISO use automated electronic procedures to provide this data.</P>
                <P>
                    11. The Commission is statutorily obligated to ensure that sales of electricity in wholesale markets are made at just and reasonable rates,
                    <SU>28</SU>
                    <FTREF/>
                     and to address market manipulation in connection with the purchase or sale of electricity subject to the Commission's jurisdiction.
                    <SU>29</SU>
                    <FTREF/>
                     Toward that end, section 301(b) of the FPA provides that the Commission shall at all times have access to and the right to inspect and examine all accounts and records of public utilities.
                    <SU>30</SU>
                    <FTREF/>
                     In this NOPR, and pursuant to its authority under section 301(b), the Commission proposes to seek ongoing electronic delivery of data including accounts and records of the RTOs/ISOs, which are public utilities.
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">See</E>
                         16 U.S.C. 824d, 824e.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See</E>
                         16 U.S.C. 824v.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         16 U.S.C. 825(b).
                    </P>
                </FTNT>
                <P>
                    12. Moreover, the Commission also has authority pursuant to section 307(a) of the FPA to investigate any facts, conditions, practices, or matters it may deem necessary or proper to determine whether any person, electric utility, transmitting utility, or other entity may have violated or might violate the FPA or the Commission's regulations, or to aid in the enforcement of the FPA or the Commission regulations, or to obtain information about wholesale power sales or the transmission of power in interstate commerce.
                    <SU>31</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         16 U.S.C. 825f(a).
                    </P>
                </FTNT>
                <P>13. As markets continue to evolve with increased levels of sophistication, the Commission must continue to evaluate the type of data necessary to ensure just and reasonable rates. The Commission's market monitoring and surveillance capabilities and associated data requirements must keep pace with market developments and evolve along with the markets. Further, the Commission's evaluation of the market rules, regulations, and policies should be informed by the data collection proposed herein. Electronic delivery of the types of data proposed herein will help to bring the Commission's access to RTO/ISO data in sync with the types and levels of activity in those markets and help to ensure that rates are just and reasonable.</P>
                <P>
                    14. Most of the data discussed in this NOPR are already collected and stored by the RTOs/ISOs in order to administer 
                    <PRTPAGE P="66214"/>
                    their markets. To the extent that an RTO/ISO does not already collect specific data, the Commission is not proposing to require either the collection of such data from market participants or its electronic delivery to the Commission. The Commission also proposes that key identifiers and other descriptive details necessary to understand the data be included in the data electronically delivered to the Commission. Finally, the Commission proposes that each RTO/ISO electronically deliver the data to the Commission using a common transfer method and format (
                    <E T="03">i.e.,</E>
                     Secure File Transfer Protocol and XML), which are described below. The Commission is not proposing that each RTO/ISO aggregate or materially modify the data prior to electronic delivery to the Commission.
                    <SU>32</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         The Commission is currently considering providing an XML Schema Definition (XSD) that describes the structure of the XML document to be electronically delivered to the Commission. XSD defines those elements, attributes, data types, and any default or fixed values in the XML. Depending on how the requested data is stored by each RTO/ISO, some data transformation may be required to prepare XML that is consistent with the XSD. For example, one RTO/ISO might store dates in MM-DD-YYYY format while the rest use YYYY-MM-DD format. As such, an XSD might specify that dates in the XML be electronically delivered to the Commission in YYYY-MM-DD format.
                    </P>
                </FTNT>
                <P>15. This NOPR proposes to require an automated data delivery process, in part, to minimize any burden on RTOs/ISOs. The Commission currently can request this data from individual RTOs and ISOs on an ad hoc basis. Such recurrent, periodic data requests may require more Commission and RTO/ISO resources than the proposed electronic delivery of this data using an automated process.</P>
                <P>
                    16. Although the six RTOs/ISOs have developed different wholesale electricity market designs, there are many similarities in the data that they use to administer these markets. Generally speaking, market participants with their own supply resources or with supply resources under contract submit energy supply offers indicating the price at which they are willing to supply various quantities of energy. Load-serving entities submit demand bids indicating the price at which they are willing to buy various quantities of energy. The supply offers pass through market power screens. These screens are used to determine whether the resources can affect the market price and whether the offers should be mitigated. If an energy supply offer triggers the application of mitigation, it is replaced with a mitigated energy supply offer. Generally, mitigated energy supply offers are calculated using estimated marginal cost data, which approximate generators' costs under different conditions.
                    <SU>33</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         The estimated marginal cost data the Commission proposes to receive through this NOPR do not include individual generators' actual costs, revenues, or profits.
                    </P>
                </FTNT>
                <P>
                    17. Similar to the process for submitting energy offers and bids, market participants with their own supply resources or with supply resources under contract also submit offers to provide ancillary services and capacity services.
                    <SU>34</SU>
                    <FTREF/>
                     These offers typically indicate a price at which a market participant is willing to provide the service and, like the energy supply offers discussed above, are subject to mitigation when appropriate.
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         We note that currently CAISO and SPP do not administer a centralized capacity market.
                    </P>
                </FTNT>
                <P>18. Entities with or without physical assets or load obligations may also submit “virtual” supply offers and demand bids in the RTO/ISO day-ahead markets. These virtual offers and bids contribute to price formation in RTO/ISO markets. Further, entities located outside of the RTO/ISO footprint may submit supply offers and demand bids in the form of interchange offers and bids.</P>
                <P>
                    19. The RTOs/ISOs match the above-described inputs through an intricate process designed to use the lowest-cost resources to meet demand.
                    <SU>35</SU>
                    <FTREF/>
                     This process yields pricing signals through locational marginal pricing (LMP) that determine which supply offers and demand bids are selected (and which would also inform long-term planning, 
                    <E T="03">e.g.,</E>
                     decisions on whether to enter and exit markets). Supply offers that are selected are required to provide a specific amount of service. For example, resources that are selected in the day-ahead energy market will be given an energy market award that specifies the amount of energy a particular resource is financially obligated to supply. These market awards are determined by each resource's supply offer and the corresponding day-ahead LMP. Finally, the RTO/ISO provides dispatch instructions for resources in real time. Real-time compensation is determined by the dispatch instructions, metered output, and the corresponding LMP.
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         We note that other inputs, including generation capabilities and other system costs, 
                        <E T="03">inter alia,</E>
                         are used by RTOs/ISOs to arrive at the lowest-cost solution.
                    </P>
                </FTNT>
                <P>20. LMP is comprised of three components: The system-wide price of energy, transmission line losses, and the congestion charge. The congestion charge component of LMP is calculated using shift factors when modeled flows are above the intended physical capability of given transmission facilities. A shift factor reflects the positive or negative percentage effect that a one-megawatt change in generation output or demand will have on an identified constraint. These shift factors are used to create a dispatch strategy that is consistent with physical and other reliability constraints. In other words, shift factors allow RTOs/ISOs to manage transmission constraints through congestion charge price signals that relate to a generator's or load's influence on a specific constraint.</P>
                <P>21. Prices in the RTO/ISO day-ahead markets and real-time balancing markets can be volatile depending on market conditions. Products designed to hedge RTO/ISO price volatility have provided valuable tools for RTO/ISO market participants to secure predictable revenue streams or reduce price risk associated with generation costs. These price hedging tools have evolved concurrently with changes in wholesale electricity markets.</P>
                <P>
                    22. In the RTO/ISO markets, market participants can limit price risk using several tools, notably, virtual offers and bids, FTRs, and internal bilateral contracts. Virtual offers and bids (collectively, virtuals) allow market participants the opportunity, among other things, to transfer price risk between day-ahead and real-time markets within an RTO/ISO. When virtuals are scheduled in the day-ahead market, the financial commitment is established at published day-ahead prices, and virtuals are automatically liquidated with the opposite buy/sell position, in most cases at real-time prices. Virtuals are not backed by physical assets. If a load-serving entity determines that it might need to purchase supply from real-time markets,
                    <SU>36</SU>
                    <FTREF/>
                     the load-serving entity could use virtuals to “lock-in” a day-ahead price.
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         A load-serving entity might determine such a need to purchase supply, for example, because of potential weather-related events or generator malfunction.
                    </P>
                </FTNT>
                <P>
                    23. FTRs provide market participants with a mechanism to hedge transmission costs under LMP-based market designs. In general, load-serving entities in RTOs/ISOs are allocated either FTRs or transmission rights convertible into FTRs. This allocation is often based on usage during an historical period. Allocated FTRs are limited to load-serving entities and to those who funded construction of specific transmission facilities. Other FTRs are auctioned, and such FTRs generally can be purchased by creditworthy entities. Moreover, FTRs 
                    <PRTPAGE P="66215"/>
                    can be resold outside of the RTO/ISO auction and allocation procedures. Transactions occurring outside of the RTO/ISO allocation and auction procedures are commonly referred to as secondary market transactions.
                </P>
                <P>24. Finally, internal bilateral contracts allow market participants to hedge energy costs under LMP-based market designs. In RTOs/ISOs, market participants can enter into bilateral agreements and use the RTO/ISO to perform settlement functions. These internal bilateral contracts typically rely on a bilaterally negotiated price rather than the potentially more volatile RTO/ISO LMP-based energy price, and they allow market participants the opportunity to transfer risks relating to energy costs among market participants. Thus, a load-serving entity may enter into an internal bilateral contract with a supplier to settle its energy costs at a predetermined rate rather than at the applicable LMP. If the market participant reports this internal bilateral contract to the RTO/ISO, the RTO/ISO would then account for this agreement in its settlement process.</P>
                <P>
                    25. RTO/ISO price-hedging products have been created outside of the RTO/ISO markets as well. Electricity futures were first traded on NYMEX in March 1996.
                    <SU>37</SU>
                    <FTREF/>
                     Electricity futures, which are traded on organized exchanges, and electricity forwards, which are traded outside of organized exchanges, are transactions that typically specify a quantity of physical electricity to be delivered at a specific time and place in the future at an agreed-upon price.
                    <SU>38</SU>
                    <FTREF/>
                     A generation owner can sell output from its facility at a pre-determined price by entering into futures or forward transactions even as the RTO/ISO price varies.
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         S.J. Deng and S.S. Oren, 
                        <E T="03">Electricity derivatives and risk management,</E>
                         31 Energy 940, 943 (2006), 
                        <E T="03">available at http://www.sciencedirect.com.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         
                        <E T="03">See id.</E>
                         at 942-43.
                    </P>
                </FTNT>
                <P>
                    26. In recent years, other products for hedging RTO/ISO prices have developed, such as electricity swaps. Swaps are similar to electricity futures and forwards, but swaps are financial transactions that do not require physical delivery. Electricity swaps can be bought or sold at a given “fixed” price and subsequently settle at a “floating” published daily electricity price; this is typically referred to as a “fixed-for-floating” swap. Swaps can act as a hedge when used alongside physical electricity sales, by guaranteeing the generation owner an agreed upon price, notwithstanding fluctuation in the published electricity price. Specifically, if the published daily electricity price is higher than the agreed upon price, the generation owner pays the difference to the counter-party to the swap but still receives the agreed upon price.
                    <SU>39</SU>
                    <FTREF/>
                     This effectively guarantees a predictable revenue stream to the generation owner. RTO/ISO posted prices are one of the commonly referenced settlement values used in electricity swaps.
                </P>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         For example, Generator sells to the RTO/ISO at a market-based rate, which varies according to the market. As a hedge, Generator sells a financial swap to Counter-party at $30/MWh. If the published electricity price that Generator receives on day one is $20/MWh, Counter-party pays Generator the difference, i.e., $10 ($30 minus $20). Thus, Generator receives the agreed upon price of $30/MWh. Conversely, if the published electricity price that Generator receives on day two is $45/MWh, Generator owes Counter-party the difference, 
                        <E T="03">i.e.,</E>
                         $15 ($45 minus $30). Thus, Generator again receives the agreed upon price of $30/MWh.
                    </P>
                </FTNT>
                <P>27. To the extent that any market participant is willing to manipulate the market, that market participant would have an incentive to manipulate RTO/ISO prices that are used to settle values for electricity products, including financial products such as electricity swaps. The likelihood of an attempt at market manipulation can be reduced if the perceived cost of manipulation exceeds the perceived benefit. For example, a market participant may wish to drive up an RTO/ISO price because that market participant also holds an electricity swap that benefits from a higher RTO/ISO price. In that vein, the market participant may offer supply into the RTO/ISO market at levels above its own marginal costs, driving up an RTO/ISO price by requiring a higher-priced unit to be selected. That market participant would receive less revenue from the RTO/ISO due to the lost sales opportunity from its own higher-priced offer not being selected. However, in this example, the market participant may be able to more than offset the reduction in revenue through the benefit of its electricity swap associated with the higher RTO/ISO price.</P>
                <P>28. Given the history of electricity markets it regulates, the Commission expects that such markets will continue to evolve, that new physical and financial products will be formed, and that increasingly complex manipulative or other anti-competitive strategies may be created.</P>
                <HD SOURCE="HD2">A. Market Monitoring and Surveillance</HD>
                <P>29. To keep pace with market developments, the Commission is proposing to establish ongoing, electronic delivery of data from each RTO and ISO to enhance its market monitoring and surveillance efforts. By seeking electronic delivery of the data outlined in this NOPR, the Commission does not seek to displace or modify any of the existing market monitoring functions performed by MMUs. Nor do we intend our proposal to be perceived as an implicit criticism of the MMUs' performance. Instead, this data will help the Commission detect anti-competitive or manipulative behavior, or ineffective market rules, and thus help ensure just and reasonable rates.</P>
                <P>30. Among other objectives, the Commission will use the data it proposes to receive as part of automated screens and other analyses designed to detect attempts to manipulate RTO/ISO pricing for the purpose of benefiting products that settle using RTO/ISO pricing and to detect abuses involving interchange transactions. Supply offer, demand bid, virtual, and FTR data will assist the Commission in understanding how market participants are positioning themselves in RTO/ISO markets. For example, market participants attempting to move RTO/ISO settlement pricing might offer supply into the RTO/ISO market at uncompetitive prices. Likewise, market participants could target specific LMP prices using virtual offers and bids. Because congestion impacts are often spread across many price nodes (and result in many different LMPs) through shift factors, these virtual offers and bids need not be placed at the specific price node for which a market participant might be attempting to move the LMP. Estimated marginal cost and shift factor data will enhance the Commission's ability to identify such behavior that may be designed to impact RTO/ISO pricing. Moreover, interchange pricing data will assist the Commission's efforts to identify anomalous or uneconomic electricity interchange schedules; electricity schedules between markets that are not consistent with pricing signals could be a source of market inefficiency or raise other anti-competitive concerns.</P>
                <P>
                    31. Securing data concerning the markets that the RTOs/ISOs administer is part of the Commission's broader effort to enhance its market monitoring and surveillance capabilities. Specifically, in a recently issued NOPR on Commission access to electronic tag (e-Tag) data,
                    <SU>40</SU>
                    <FTREF/>
                     the Commission proposed to make e-Tag data available to the Commission to assist in monitoring the market and preventing manipulation, among other things. In yet another NOPR, the Commission proposed to require additional contract and transaction data from those who file 
                    <PRTPAGE P="66216"/>
                    EQRs and to extend the EQR filing requirements to wholesale market participants which fall outside the Commission's FPA section 205 jurisdiction.
                    <SU>41</SU>
                    <FTREF/>
                     The Commission stated that these proposals would strengthen the Commission's ability to identify potential exercises of market power or manipulation. We believe that the same is true here.
                </P>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         
                        <E T="03">Availability of E-Tag Information to Commission Staff,</E>
                         Notice of Proposed Rulemaking, FERC Stats. &amp; Regs. ¶ 32,675 (2011).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         
                        <E T="03">Electricity Market Transparency Provisions of Section 220 of The Federal Power Act,</E>
                         Notice of Proposed Rulemaking, FERC Stats. &amp; Regs. ¶ 32,676 (2011).
                    </P>
                </FTNT>
                <P>32. Utilizing the data the Commission proposes to receive in this NOPR and the two NOPRs addressed above could greatly enhance the Commission's market monitoring and surveillance capabilities. The data will permit the Commission to improve its screening of market participants for illicit behavior, making such conduct more difficult to mask. In addition, the data the Commission proposes to collect in these NOPRs could provide a better picture of legitimate market activity and lessen the possibility that market monitoring and surveillance screens will result in error.</P>
                <HD SOURCE="HD2">B. Commission Policies and Regulations</HD>
                <P>33. In overseeing wholesale electricity markets, the Commission evaluates, in response to submissions or on its own motion, existing market designs and the effectiveness of market rules. The Commission proposes to use RTO/ISO market data to more effectively carry out these functions. Electronic delivery of this data will enable the Commission to better identify ineffective market rules and better inform Commission policies and decision-making, and thus help prevent anti-competitive behavior and ensure just and reasonable rates.</P>
                <P>34. We believe that electronic delivery of RTO/ISO market data will provide the Commission with empirical information that will augment ongoing industry outreach in determining the effectiveness of the Commission-approved market rules and the efficiency of existing market designs in producing just and reasonable rates. Electronic delivery of the market data sought would allow the Commission to perform better ongoing analysis as markets evolve and new resources begin participating in these markets. For example, the market data sought should enable the Commission to assess both the scheduling practices of renewable resources and how renewable energy schedules compare with actual real-time performance. Because of its unique position, the Commission will be able to perform such analysis across the RTO/ISO markets. This cross-market analysis will enhance the Commission's ongoing efforts to assess the performance of different market designs and rules.</P>
                <P>35. In seeking electronic delivery of this data, the Commission emphasizes that it does not seek to displace existing MMU efforts to evaluate market rules and market designs nor is it proposing to modify any of the market monitoring functions performed by MMUs. Rather, the Commission is seeking to augment the assessments currently being performed by MMUs, thus strengthening the Commission's regulatory capabilities through the ongoing electronic delivery of RTO/ISO market data.</P>
                <HD SOURCE="HD2">C. Requested Data</HD>
                <P>
                    36. As part of this rulemaking, the Commission proposes to require ongoing electronic delivery of, the data (
                    <E T="03">e.g.,</E>
                     the information to be included in the datasets) described below. The Commission invites comment on these data requirements:
                </P>
                <P>
                    1. 
                    <E T="03">Supply offers and demand bids for energy and ancillary services</E>
                    —The Commission is proposing that RTOs/ISOs provide their data on supply offers and demand bids submitted to RTO/ISO markets. This dataset would include all offers and bids for energy and ancillary services. This dataset would also include offers and bids submitted for interchange transactions, as well as those submitted without economic consideration, 
                    <E T="03">i.e.,</E>
                     self schedules.
                </P>
                <P>
                    2. 
                    <E T="03">Virtual offers and bids</E>
                    —The Commission is proposing that RTOs/ISOs provide their data on virtual supply offers and virtual demand bids submitted to RTO/ISO markets.
                </P>
                <P>
                    3. 
                    <E T="03">Energy/ancillary service awards</E>
                    —The Commission is proposing that RTOs/ISOs provide their data on market awards for energy and ancillary services. This dataset would include the quantity and price of all market awards for energy and ancillary services. The dataset would also identify resources that are self-scheduled.
                </P>
                <P>
                    4. 
                    <E T="03">Capacity market offers, designations, and prices</E>
                    —For RTOs/ISOs with centralized capacity markets, the Commission is proposing to require RTOs/ISOs to provide their data on capacity offers as well as capacity market outcomes or designations. This dataset would identify capacity resources, the amount of procured capacity, and the applicable capacity market price.
                </P>
                <P>
                    5. 
                    <E T="03">Resource output</E>
                    —The Commission is proposing that RTOs/ISOs provide their data on resource output data used in market settlements. This dataset would include details used in market settlements, including RTO/ISO dispatch instructions (
                    <E T="03">i.e.,</E>
                     the output that a dispatched resource is expected to produce in real-time) for energy or ancillary services, or whether resources are operating at self-scheduled output levels, and measured output levels.
                </P>
                <P>
                    6. 
                    <E T="03">Marginal cost estimates</E>
                    —The Commission is proposing that RTOs/ISOs provide their data on marginal cost estimates; such estimates are typically generated for the potential replacement of supply offers in market power mitigation procedures. This dataset would include all marginal cost estimates that have been developed, and not just those estimates that were used to generate mitigated supply offers. The Commission is seeking just the resulting marginal cost estimates themselves, however, and is not proposing that RTOs/ISOs provide the inputs that allow for calculation of those estimates. Further, the Commission is not seeking other operating information regarding individual generators' actual costs, revenues, or profits.
                </P>
                <P>
                    7. 
                    <E T="03">Day-ahead shift factors</E>
                    —The Commission is proposing that RTOs/ISOs provide their data on shift factors calculated for use in the day-ahead market. This would include generation shift factors, which are factors to be applied to a generator's expected change in output to determine the amount of flow contribution that that change in output will impose on an identified transmission facility or flowgate, and load shift factors, which are factors to be applied to a load's expected change in demand to determine the amount of flow contribution that that change in demand will impose on an identified transmission facility or flowgate. This dataset would not be limited to binding constraints, but should also include all shift factors calculated to address non-binding constraints.
                </P>
                <P>
                    8. 
                    <E T="03">FTR data</E>
                    —The Commission is proposing that RTOs/ISOs provide their data on FTR transactions that may not be publicly posted in all RTO/ISO markets. Specifically, the Commission is proposing that RTOs/ISOs provide data detailing how all FTRs and allocated rights were acquired, either through RTO/ISO allocation or auction procedures; data detailing whether the acquired allocation positions were converted from positions that collect auction revenue into positions that collect congestion revenue; and data detailing secondary market transactions to the extent that they are available to the RTO/ISO.
                </P>
                <P>
                    9. 
                    <E T="03">Internal Bilateral Contracts</E>
                    —The Commission is proposing that RTOs/ISOs provide their data on the settlement of internal bilateral contracts for energy.
                    <PRTPAGE P="66217"/>
                </P>
                <P>
                    10. 
                    <E T="03">Pricing data for interchange transactions</E>
                    —The Commission is proposing that RTOs/ISOs provide their data on pricing information for scheduled interchanges. Scheduled interchanges include any transaction between two or more Balancing Authority Areas. To enhance the Commission's market monitoring and surveillance efforts, the Commission is proposing that eTag IDs be included, when applicable, in addition to other interchange pricing details and transaction identification.
                </P>
                <P>37. The data that the Commission is proposing to receive electronically in this NOPR are limited to physical and virtual offers and bids, market awards, resource outputs, marginal cost estimates, shift factors, FTRs, internal bilateral contracts, and interchange pricing. These datasets would include descriptive information such as market participant names, unique identifiers, pricing points, and other information that the Commission considers necessary and appropriate to understand and analyze the data described in this NOPR. Markets are not static, however, and, as markets continue to evolve, the Commission may initiate a new rulemaking process in the future to reassess the data necessary for its market monitoring and surveillance efforts and for its policy and decision-making needs.</P>
                <P>38. The Commission proposes that RTOs/ISOs be required to electronically deliver the data discussed in this NOPR to the Commission within seven days after each RTO/ISO creates the datasets in a market run or otherwise. For example, day-ahead offers and bids, market awards, resource outputs, day-ahead shift factors, internal bilateral contracts, and day-ahead interchange pricing data would be required to be electronically delivered within seven days after the completion of each day-ahead market run. Real-time offers and bids and real-time interchange pricing data would be required to be electronically delivered within seven days after the completion of each real-time market run. For data that are updated less frequently, including capacity market results, estimated marginal costs, and FTR data, each RTO/ISO would be expected to electronically deliver that data within seven days after it is created or updated by the RTO/ISO. For the initial delivery of data under this proposal, however, the Commission proposes that each RTO/ISO would be required to electronically deliver all such data forty-five days after the effective date of any final rule in this proceeding. Finally, if the RTO/ISO makes later corrections to the data (after they have been delivered to the Commission), the RTO/ISO would be expected to electronically deliver the corrected data to the Commission within seven days after the correction has been made. The Commission invites comments with respect to the timeframe in which the data described in this NOPR should be electronically delivered to the Commission.</P>
                <P>39. The Commission proposes to locate the requirement to electronically deliver this data on an ongoing basis within section 35.28(g) of our regulations. Further, the Commission proposes to direct each RTO/ISO to submit a compliance filing amending its open access transmission tariff to reflect this requirement within forty-five days after the effective date of any final rule in this proceeding.</P>
                <HD SOURCE="HD2">D. Data Formatting and Web-Based Delivery</HD>
                <P>40. In order to facilitate the Commission's efforts described above, the Commission is proposing to require each RTO and ISO to use consistent formatting and delivery methods to electronically deliver the data described in this NOPR to the Commission. Consistent formatting and delivery methods will enable the Commission to develop routine data procedures to link RTO/ISO and other market data, thus enabling automated analytic techniques.</P>
                <P>
                    41. In regard to data formatting, the Commission is proposing to require that any data outlined in this NOPR be in an XML format that is consistent for all RTOs/ISOs when electronically delivered to the Commission. As stated above, the Commission is not proposing that each RTO/ISO materially modify the data prior to electronic delivery to the Commission.
                    <SU>42</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         
                        <E T="03">See supra</E>
                         P 14.
                    </P>
                </FTNT>
                <P>
                    42. In Order No. 714,
                    <SU>43</SU>
                    <FTREF/>
                     the Commission adopted XML format for entities to use when making tariff related filings, based upon industry agreement.
                    <SU>44</SU>
                    <FTREF/>
                     XML is also commonly used by RTOs/ISOs to deliver data to market participants through Open Access Same-Time Information Systems (OASIS) and other purposes. Data not formatted in XML may also be extracted directly from a database into an XML-formatted file using automated procedures. However, the Commission also recognizes that XML, which was adopted by the industry as the most effective format to use when electronically filing tariffs, may not be the preferred format to use when electronically delivering RTO/ISO data. Accordingly, we seek comment on this issue.
                </P>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         
                        <E T="03">Electronic Tariff Filings,</E>
                         Order No. 714, 73 FR 57515, FERC Stats. &amp; Regs. ¶ 31,276 (2008).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         Order No. 714, FERC Stats. &amp; Regs. ¶ 31,276 at P 30.
                    </P>
                </FTNT>
                <P>43. In regard to the data delivery method, the Commission is proposing that each RTO and ISO use a secure data delivery method to provide data to the Commission due to the commercially-sensitive nature of the market data described in this NOPR. Specifically, the Commission is proposing that any RTO/ISO market data be electronically delivered using the Secure File Transfer Protocol (SFTP). Delivery by SFTP is similar to delivery by File Transfer Protocol or “FTP,” a widely-used file-sharing protocol; except that all communications transmitted using SFTP are encrypted. Access to the server where the data is electronically delivered will only be granted to each applicable RTO and ISO and to the Commission.</P>
                <P>44. Accordingly, and as part of our consideration of the range of possible formats and delivery methods that RTOs/ISOs may use to electronically deliver data to the Commission, the Commission invites comments with respect to efficient and secure ways to provide the Commission with RTO/ISO data. The Commission also invites comment on the time and resources that may be needed by RTOs/ISOs for the initial implementation and ongoing compliance with the proposed requirements of this rule. Finally, the Commission invites comment on whether a phased implementation approach should be undertaken, and, if so, what a potential phased approach should entail.</P>
                <HD SOURCE="HD2">E. Non-Public Data</HD>
                <P>
                    45. Much of the information that the Commission expects to receive in this proposal is, by its nature, commercially-sensitive.
                    <SU>45</SU>
                    <FTREF/>
                     Disclosure of such information could result in competitive harm to market participants and the market as a whole.
                    <SU>46</SU>
                    <FTREF/>
                     Accordingly, the 
                    <PRTPAGE P="66218"/>
                    Commission proposes that the data sought in this proceeding is to be kept non-public and not be made publicly available,
                    <SU>47</SU>
                    <FTREF/>
                     except as may be directed by the Commission, or a court with appropriate jurisdiction.
                    <SU>48</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         In the past, the Commission has granted requests for privileged or confidential treatment of similar non-public data. 
                        <E T="03">See, e.g., N.Y. Indep. Sys. Operator, Inc.,</E>
                         131 FERC ¶ 61,169, at P 15 (2010) (granting such treatment for data relating to specific generator or other equipment details, transmission system information, bidding strategies, generator reference levels, generator costs, guarantee payments, and the associated relevant time periods); 
                        <E T="03">see also So. Cal. Edison Co.,</E>
                         135 FERC ¶ 61,201, at P 20; 
                        <E T="03">Hydrogen Energy Cal. LLC,</E>
                         135 FERC ¶ 61,068, at P 25 (2011); 
                        <E T="03">N.Y. Indep. Sys. Operator, Inc.,</E>
                         130 FERC ¶ 61,029, at P 3 (2010).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         Section 301(b) of the FPA, 16 U.S.C. 825(b), provides that no member, officer, or employee of the Commission may divulge any fact or information that may come to his knowledge during the course of examination of books or other 
                        <PRTPAGE/>
                        accounts, except as may be directed by the Commission or by a court.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         We note that, notwithstanding that the Commission may have data available to it, complainants still must bear the burden of making a prima facie case; complainants must do more than make unsubstantiated allegations. 
                        <E T="03">Interstate Power &amp; Light Co.</E>
                         v.
                        <E T="03"> ITC Midwest, LLC,</E>
                         135 FERC ¶ 61,162, at P 18 (2011); 
                        <E T="03">see also UNITIL Power Corp.</E>
                         v.
                        <E T="03"> Pub. Serv. Co. of N.H.,</E>
                         62 FERC P 61,055, at 61,287 (1993) (“The question we must answer at this stage of the proceeding is whether UNITIL has presented sufficient evidence of PSNH's costs so that we may assess whether a trial-type, evidentiary hearing is warranted.”); Houlton Water Co. v. Me. Pub. Serv. Co., 55 FERC P 61,037, at 61,110 (1991) (“Maine Public correctly states that a customer seeking a section 206 investigation of existing rates must provide some basis to question the reasonableness of the overall rate level, taking into account changes in all cost components and not just [the item being challenged].”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         We note that the Freedom of Information Act (FOIA) allows persons to file requests to obtain data from the Commission. However, commercially-sensitive data, like that described in this NOPR, is covered by exemption 4 of FOIA, which protects “trade secrets and commercial or financial information obtained from a person [that is] privileged or confidential.” 5 U.S.C. 552(b)(4) (2006), 
                        <E T="03">amended by</E>
                         OPEN Government Act of 2007, Pub. L. No. 110-175, 121 Stat. 2524 (2007); 
                        <E T="03">accord</E>
                         18 CFR 388.107(d).
                    </P>
                </FTNT>
                <P>46. To the extent the data collected pursuant to this rulemaking are used, for example, to support proposed market rule changes, the analysis relied upon by the Commission will be publicly available except that confidential market information and other protected or confidential information will remain non-public. Also, the Commission may direct its staff to publicly issue a staff report outside of a rulemaking proceeding with similar protections for confidential or otherwise protected information.</P>
                <HD SOURCE="HD1">III. Information Collection Statement</HD>
                <P>47. The collections of information contained in this proposed rule have been submitted to the Office of Management and Budget (OMB) for review under section 3507(d) of the Paperwork Reduction Act of 1995, 44 U.S.C. 3507(d). The Commission solicits comments on the Commission's need for this information, whether the information will have practical utility, the accuracy of the provided burden estimates, ways to enhance the quality, utility, and clarity of the information to be collected, and any suggested methods for minimizing respondents' burden, including the use of automated information techniques. Respondents subject to the filing requirements of this rule will not be penalized for failing to respond to these collections of information unless the collections of information display a valid OMB Control number.</P>
                <P>48. The proposed rule does not require market participants other than the RTOs/ISOs to report information to the Commission.</P>
                <P>49. The Commission's estimated reporting burden related to the proposed rule in Docket RM11-17-000 follow.</P>
                <GPOTABLE COLS="8" OPTS="L2,tp0,i1" CDEF="s50,12,12,12,12,12,12,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Data collection, proposed FERC-921</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">Implementing burden</CHED>
                        <CHED H="2">
                            Burden hrs. per
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="2">
                            Cost per
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Annual recurring operating 
                            <LI>burden</LI>
                        </CHED>
                        <CHED H="2">
                            Burden hrs. per
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="2">
                            Cost per
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Average annual burden
                            <LI>(implementation cost </LI>
                            <LI>averaged over 3 yrs.)</LI>
                        </CHED>
                        <CHED H="2">
                            Burden hrs.
                            <LI>for all</LI>
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="2">
                            Cost for all
                            <LI>respondents</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Compliance filing</ENT>
                        <ENT>6</ENT>
                        <ENT>7</ENT>
                        <ENT>$1,750</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>14</ENT>
                        <ENT>$3,500</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Web-Based Delivery</ENT>
                        <ENT>6</ENT>
                        <ENT>1,040</ENT>
                        <ENT>100,864</ENT>
                        <ENT>40</ENT>
                        <ENT>$3,879</ENT>
                        <ENT>2,320</ENT>
                        <ENT>225,003</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Grand Total, Average Annual Estimates</ENT>
                        <ENT>6</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>2,334</ENT>
                        <ENT>228,503</ENT>
                    </ROW>
                </GPOTABLE>
                <P>50. The Commission recognizes that there will be an initial implementation burden associated with providing the Commission with RTO/ISO data. This includes submitting a compliance filing to the Commission, which the Commission estimates as a burden of 7 hours per RTO/ISO, and implementing a process to automatically upload data to an SFTP site for Commission use (including development, testing and production). The Commission estimates a burden of 1040 hours per RTO/ISO for the development, testing and production of an automated process to provide the Commission with the data described in this NOPR. In this regard, though, RTO/ISO markets have already developed capabilities necessary to handle RTO/ISO data in an automated manner. For instance, through their Open Access Same-time Information Systems (OASIS), RTOs/ISOs already make certain market data publically available in XML format using automated procedures. Likewise, some RTOs/ISOs have developed procedures similar to those proposed in this NOPR to deliver data to their MMUs.</P>
                <P>51. For the recurring effort involved in electronically delivering RTO/ISO data to the Commission, the Commission anticipates that the additional burden associated with this rule will be minimal. Any recurring burden would be associated with addressing updates to RTO/ISO data as the data that they process changes and due to occasional errors in the data handling or data upload process.</P>
                <PRTPAGE P="66219"/>
                <P>
                    <E T="03">Information Collection Costs:</E>
                     The Commission has estimated the cost of compliance per RTO/ISO to be $102,614 in the initial year of implementation and $3,879 in subsequent years. The Commission expects that the compliance filing will be completed by RTO/ISO legal staff and has estimated an hourly rate at $250/hour. The Commission estimates that a variety of staff, including legal, database administrators and IT and information security specialists, will be required to electronically deliver to the Commission the RTO/ISO data described in this NOPR. The Commission estimated the average hourly cost for this task to be $96.98/hour (including legal staff at $250/hour, information systems manager at $105.35/hour, database administrator at $55.61/hour, and information security analyst at $57.67/hour).
                    <SU>49</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         Hourly average wage is an average and was calculated using Bureau of Labor Statistics (BLS), Occupational Employment Statistics data for May 2010 (at 
                        <E T="03">http://www.bls.gov/oes/</E>
                        ) for the database administrator and information security analysts. The average hourly figure for legal staff and information systems manager is a composite from BLS and other resources. The following weightings were applied to estimate the average hourly cost: Legal staff (
                        <FR>1/6</FR>
                        ), information systems manager (
                        <FR>1/6</FR>
                        ), database administrator (
                        <FR>1/3</FR>
                        ), and information security analyst (
                        <FR>1/3</FR>
                        ).
                    </P>
                </FTNT>
                <P>
                    <E T="03">Title:</E>
                     Proposed FERC-921.
                    <SU>50</SU>
                    <FTREF/>
                    .
                </P>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         OATT compliance filings (like the one-time compliance filing here) are normally included under FERC-516 (OMB Control No. 1902-0096). However, the reporting requirements (including the compliance filing) contained in this proposed rule in Docket No. RM11-17 will be covered by a proposed FERC-921.
                    </P>
                </FTNT>
                <P>
                    <E T="03">Action:</E>
                     Proposed collection.
                </P>
                <P>
                    <E T="03">OMB Control No.: To be determined.</E>
                </P>
                <P>
                    <E T="03">Respondents for this Rulemaking:</E>
                     RTOs and ISOs.
                </P>
                <P>
                    <E T="03">Frequency of Information:</E>
                     Initial implementation, compliance filing, and automated daily updates.
                </P>
                <P>
                    52. 
                    <E T="03">Necessity of Information:</E>
                     As wholesale electricity markets continue to develop and evolve, new opportunities arise for anti-competitive or manipulative behavior. The Commission's market monitoring and surveillance capabilities and associated data requirements must keep pace with market developments and evolve along with the markets. The data discussed in this NOPR will allow the Commission to more effectively identify and address such behavior; to identify ineffective market rules; to better inform Commission policies and regulations; and thus to help ensure just and reasonable rates.
                </P>
                <P>
                    53. 
                    <E T="03">Internal Review:</E>
                     The Commission has made a preliminary determination that the proposed revisions are necessary to keep pace with ever-changing possibilities for anti-competitive or manipulative behavior and to better inform Commission policies and regulations, and thus to ensure that rates are just and reasonable. The Commission has assured itself, by means of its internal review, that there is specific, objective support for the burden estimate associated with the information requirements.
                </P>
                <P>
                    54. Interested persons may obtain information on the reporting requirements by contacting the Federal Energy Regulatory Commission, Office of the Executive Director, 888 First Street, NE., Washington, DC 20426 [
                    <E T="03">Attention:</E>
                     Ellen Brown, 
                    <E T="03">e-mail: DataClearance@ferc.gov, phone:</E>
                     (202) 502-8663, 
                    <E T="03">fax:</E>
                     (202) 273-0873].
                </P>
                <P>
                    55. Comments concerning the information collections proposed in this NOPR and the associated burden estimates, should be sent to the Commission in this docket and may also be sent to the Office of Management and Budget, Office of Information and Regulatory Affairs, Washington, DC 20503 [
                    <E T="03">Attention:</E>
                     Desk Officer for the Federal Energy Regulatory Commission]. For security reasons, comments should be sent by e-mail to OMB at the following 
                    <E T="03">e-mail address: oira_submission@omb.eop.gov.</E>
                     Please reference FERC-921 and the docket number of this proposed rulemaking (Docket No. RM11-17-000) in your submission.
                </P>
                <HD SOURCE="HD1">IV. Environmental Analysis</HD>
                <P>
                    56. The Commission is required to prepare an Environmental Assessment or an Environmental Impact Statement for any action that may have a significant adverse effect on the human environment.
                    <SU>51</SU>
                    <FTREF/>
                     The Commission has categorically excluded certain actions from these requirements as not having a significant effect on the human environment.
                    <SU>52</SU>
                    <FTREF/>
                     The actions proposed here fall within a categorical exclusion in the Commission's regulations, 
                    <E T="03">i.e.,</E>
                     they involve information gathering, analysis, and dissemination.
                    <SU>53</SU>
                    <FTREF/>
                     Therefore, environmental analysis is unnecessary and has not been performed.
                </P>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         
                        <E T="03">Regulations Implementing the National Environmental Policy Act,</E>
                         Order No. 486, 52 FR 47,897 (Dec. 17, 1987), FERC Stats. &amp; Regs. ¶ 30,783 (1987).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         18 CFR 380.4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         
                        <E T="03">See</E>
                         18 CFR 380.4(a)(5).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">V. Regulatory Flexibility Act Certification</HD>
                <P>
                    57. The Regulatory Flexibility Act of 1980 (RFA) 
                    <SU>54</SU>
                    <FTREF/>
                     generally requires a description and analysis of final rules that will have significant economic impact on a substantial number of small entities. The RFA mandates consideration of regulatory alternatives that accomplish the stated objectives of a rule and that minimize any significant economic impact on a substantial number of small entities. The Small Business Administration's (SBA) Office of Size Standards is responsible for the definition of a small business.
                    <SU>55</SU>
                    <FTREF/>
                     The SBA has established a size standard for utilities, stating that a firm is small if, including its affiliates, it is primarily engaged in the transmission, generation and/or distribution of electric energy for sale and its total electric output for the preceding twelve months did not exceed four million megawatt hours.
                    <SU>56</SU>
                    <FTREF/>
                     RTOs and ISOs are not small entities, and they are the only entities impacted directly by this proposed rule.
                </P>
                <FTNT>
                    <P>
                        <SU>54</SU>
                         5 U.S.C. 601-612.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>55</SU>
                         13 CFR 121.101.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>56</SU>
                         13 CFR 121.201 (Sector 22, Utilities).
                    </P>
                </FTNT>
                <P>58. CAISO is a nonprofit organization with over 54,000 megawatts of capacity and over 25,000 circuit miles of transmission lines.</P>
                <P>59. NYISO is a nonprofit organization that oversees wholesale electricity markets serving 19.2 million customers. NYISO manages a nearly 11,000-mile network of high-voltage transmission lines.</P>
                <P>60. PJM is comprised of more than 700 members including power generators, transmission owners, electricity distributers, power marketers, and large industrial customers and serves 13 states and the District of Columbia.</P>
                <P>61. SPP is comprised of 63 members serving 6.2 million households in nine states and has 48,930 miles of transmission lines.</P>
                <P>62. Midwest ISO is a nonprofit organization with over 145,000 megawatts of installed generation. Midwest ISO has over 57,600 miles of transmission lines and serves 13 states and one Canadian province.</P>
                <P>63. ISO-NE is a regional transmission organization serving six states in New England. The system is comprised of more than 8,000 miles of high-voltage transmission lines and over 300 generators.</P>
                <P>64. The Commission believes this proposed rule will not have a significant economic impact on a substantial number of small entities, and therefore no regulatory flexibility analysis is required.</P>
                <HD SOURCE="HD1">VI. Comment Procedures</HD>
                <P>
                    65. The Commission invites interested persons to submit comments on the matters and issues proposed in this 
                    <PRTPAGE P="66220"/>
                    notice to be adopted, including any related matters or alternative proposals that commenters may wish to discuss. Comments are due December 27, 2011. Comments must refer to Docket No. RM11-17-000, and must include the commenter's name, the organization they represent, if applicable, and their address.
                </P>
                <P>
                    66. The Commission encourages comments to be filed electronically via the eFiling link on the Commission's Web site at 
                    <E T="03">http://www.ferc.gov.</E>
                     The Commission accepts most standard word processing formats. Documents created electronically using word processing software should be filed in native applications or print-to-PDF format and not in a scanned format. Commenters filing electronically do not need to make a paper filing.
                </P>
                <P>67. Commenters that are not able to file comments electronically must send an original copy of their comments to: Federal Energy Regulatory Commission, Secretary of the Commission, 888 First Street, NE., Washington, DC 20426.</P>
                <P>68. All comments will be placed in the Commission's public files and may be viewed, printed, or downloaded remotely as described in the Document Availability section below. Commenters on this proposal are not required to serve copies of their comments on other commenters.</P>
                <HD SOURCE="HD1">VII. Document Availability</HD>
                <P>
                    69. In addition to publishing the full text of this document in the 
                    <E T="04">Federal Register</E>
                    , the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the Internet through the Commission's Home Page (
                    <E T="03">http://www.ferc.gov</E>
                    ) and in the Commission's Public Reference Room during normal business hours (8:30 a.m. to 5 p.m. Eastern time) at 888 First Street, NE., Room 2A, Washington, DC 20426.
                </P>
                <P>70. From the Commission's Home Page on the Internet, this information is available on eLibrary. The full text of this document is available on eLibrary both in PDF and Microsoft Word format for viewing, printing, and/or downloading. To access this document in eLibrary, type the docket number excluding the last three digits of this document in the docket number field.</P>
                <P>
                    71. User assistance is available for eLibrary and the Commission's Web site during normal business hours from the Commission's Online Support at 202-502-6652 (toll free at 1-866-208-3676) or e-mail at 
                    <E T="03">ferconlinesupport@ferc.gov,</E>
                     or the Public Reference Room at 202-502-8371, TTY 202-502-8659. E-mail the Public Reference Room at 
                    <E T="03">public.referenceroom@ferc.gov.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 18 CFR Part 35</HD>
                    <P>Electric power rates, Electric utilities, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <SIG>
                    <P>By direction of the Commission. Commissioner Spitzer is not participating.</P>
                    <NAME>Nathaniel J. Davis, Sr.,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
                <P>
                    In consideration of the foregoing, the Commission proposes to revise Chapter I, Title 18 of the 
                    <E T="03">Code of Federal Regulations</E>
                     to read as follows:
                </P>
                <PART>
                    <HD SOURCE="HED">PART 35—FILING OF RATE SCHEDULES AND TARIFFS</HD>
                    <P>1. The authority for part 35 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>16 U.S.C. 791a-825r, 2601-2645; 31 U.S.C. 9701; 42 U.S.C. 7101-7352.</P>
                    </AUTH>
                    <P>2. In § 35.28, paragraphs (g)(4) through (g)(6) are redesignated as paragraphs (g)(5) through (g)(7) and a new paragraph (g)(4) is added to read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 35.28. </SECTNO>
                        <SUBJECT>Non-discriminatory open access transmission tariff.</SUBJECT>
                        <STARS/>
                        <P>
                            (g) 
                            <E T="03">Tariffs and operations of Commission-approved independent system operators and regional transmission organizations.</E>
                        </P>
                        <STARS/>
                        <P>
                            (4) 
                            <E T="03">Electronic delivery of data.</E>
                             Each Commission-approved regional transmission organization and independent system operator must electronically deliver to the Commission, on an ongoing basis and in a form and manner acceptable to the Commission, data related to the markets that the regional transmission organization or independent system operator administers.
                        </P>
                        <STARS/>
                    </SECTION>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27626 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <CFR>18 CFR Part 40</CFR>
                <DEPDOC>[Docket No. RM11-20-000]</DEPDOC>
                <SUBJECT>Automatic Underfrequency Load Shedding and Load Shedding Plans Reliability Standards</SUBJECT>
                <DATE>October 20, 2011.</DATE>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Energy Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Proposed Rulemaking.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Under section 215 of the Federal Power Act, the Federal Energy Regulatory Commission (Commission) proposes to approve Reliability Standards PRC-006-1 (Automatic Underfrequency Load Shedding) and EOP-003-2 (Load Shedding Plans), developed and submitted to the Commission for approval by the North American Electric Reliability Corporation (NERC), the Electric Reliability Organization certified by the Commission. The proposed Reliability Standards establish design and documentation requirements for automatic underfrequency load shedding programs that arrest declining frequency and assist recovery of frequency following system events leading to frequency degradation. The Commission also proposes to approve the related Violation Risk Factors and Violation Severity Levels, implementation plan, and effective date proposed by NERC.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments are due December 27, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments, identified by docket number, may be filed in the following ways:</P>
                    <P>
                        • Electronic Filing through 
                        <E T="03">http://www.ferc.gov.</E>
                         Documents created electronically using word processing software should be filed in native applications or print-to-PDF format and not in a scanned format.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail/Hand Delivery:</E>
                         Those unable to file electronically may mail or hand-deliver comments to: Federal Energy Regulatory Commission, Secretary of the Commission, 888 First Street, NE., Washington, DC 20426.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         For detailed instructions on submitting comments and additional information on the rulemaking process, see the Comment Procedures Section of this document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P/>
                    <P>
                        Stephanie Schmidt (Technical Information), Office of Electric Reliability, Division of Reliability Standards, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, (202) 502-6568,  
                        <E T="03">Stephanie.Schmidt@ferc.gov</E>
                        .
                    </P>
                    <P>
                        Matthew Vlissides (Legal Information), Office of the General Counsel, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, (202) 502-8408,  
                        <E T="03">Matthew.Vlissides@ferc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P SOURCE="NPAR">
                    1. Under section 215 of the Federal Power Act (FPA),
                    <SU>1</SU>
                    <FTREF/>
                     the Commission proposes to approve proposed Reliability Standards PRC-006-1 
                    <PRTPAGE P="66221"/>
                    (Automatic Underfrequency Load Shedding) and EOP-003-2 (Load Shedding Plans). The proposed Reliability Standards were developed and submitted for approval to the Commission by the North American Electric Reliability Corporation (NERC), which the Commission certified as the Electric Reliability Organization (ERO) responsible for developing and enforcing mandatory Reliability Standards.
                    <SU>2</SU>
                    <FTREF/>
                     The proposed Reliability Standards establish design and documentation requirements for automatic underfrequency load shedding (UFLS) programs, which are meant to arrest declining frequency and assist recovery of frequency following underfrequency events and provide last resort system preservation measures.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         16 U.S.C. 824o (2006).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">North American Electric Reliability Corp.,</E>
                         116 FERC ¶ 61,062, 
                        <E T="03">order on reh'g &amp; compliance,</E>
                         117 FERC ¶ 61,126 (2006), 
                        <E T="03">aff'd sub nom. Alcoa, Inc.</E>
                         v.
                        <E T="03"> FERC,</E>
                         564 F.3d 1342 (DC Cir. 2009).
                    </P>
                </FTNT>
                <P>2. The Commission proposes to approve the related Violation Risk Factors (VRFs) and Violation Severity Levels (VSLs), implementation plan, and effective date proposed by NERC. The Commission also proposes to approve the retirement of the currently effective Reliability Standards PRC-007-0, PRC-009-0, and EOP-003-1, and the NERC-approved Reliability Standard PRC-006-0.</P>
                <P>3. The Commission seeks comments from NERC and other interested persons on specific issues concerning the proposed Reliability Standards.</P>
                <HD SOURCE="HD1">I. Background</HD>
                <HD SOURCE="HD2">A. Underfrequency Load Shedding</HD>
                <P>
                    4. An interconnected electric power system must balance load and generation in order to maintain frequency within a reliable range.
                    <SU>3</SU>
                    <FTREF/>
                     The balance between generation and load within an interconnected electric power system is shown in the frequency of the system.
                    <SU>4</SU>
                    <FTREF/>
                     Underfrequency protection schemes are drastic measures employed if the system frequency falls below a specified value.
                    <SU>5</SU>
                    <FTREF/>
                     The Blackout Report provides the following explanation:
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Electric Power Research Institute, 
                        <E T="03">EPRI Power Systems Dynamics Tutorial,</E>
                         Chapter 4 at page 4-78 (2009), 
                        <E T="03">available at http://www.epri.com</E>
                         (EPRI Tutorial).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <EXTRACT>
                    <P>
                        [A]utomatic under-frequency load-shedding (UFLS) is designed for use in extreme conditions to stabilize the balance between generation and load after an electrical island has been formed, dropping enough load to allow frequency to stabilize within the island. All synchronous generators in North America are designed to operate at 60 cycles per second (Hertz) and frequency reflects how well load and generation are balanced—if there is more load than generation at any moment, frequency drops below 60 Hz, and it rises above that level if there is more generation than load. By dropping load to match available generation within the island, UFLS is a safety net that helps to prevent the complete blackout of the island, which allows faster system restoration afterward. UFLS is not effective if there is electrical instability or voltage collapse within the island.
                        <SU>6</SU>
                        <FTREF/>
                    </P>
                </EXTRACT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">U.S.-Canada Power System Outage Task Force, Final Report on the August 14, 2003 Blackout in the United States and Canada: Causes and Recommendations</E>
                         at 92-93 (2004) (Blackout Report).
                    </P>
                </FTNT>
                <P>
                    5. UFLS programs are designed for each defined area or system, and they are commonly implemented with devices installed on the distribution side of the power system.
                    <SU>7</SU>
                    <FTREF/>
                     Factors considered in developing a UFLS program include: (1) Underfrequency set point, (2) minimum amount of load to shed, and (3) what load and at what locations to shed.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         UFLS programs are designed to maintain a balance between resources and demand in a defined area (e.g., Interconnection, Regional Entity area, or planning coordinator area).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">1. Underfrequency Set Point</HD>
                <P>
                    6. The underfrequency set point is the frequency at which a specified load will disconnect from the system in a UFLS program.
                    <SU>8</SU>
                    <FTREF/>
                     Separately, generators have their own underfrequency set points, which will disconnect them from the system if the frequency drops to a certain value, thus protecting them from damage.
                    <SU>9</SU>
                    <FTREF/>
                     Underfrequency set points for load shedding are set above the frequencies at which generators disconnect.
                    <SU>10</SU>
                    <FTREF/>
                     This is done to prevent losing additional resources that would exacerbate the imbalance between resources and demand, resulting in further frequency declines. UFLS programs initiate at a specified point to shed the first load block, and if necessary additional load blocks at other lower set points, to arrest system frequency decline prior to the loss of additional resources.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         In Order No. 693-A, the Commission directed NERC to collect the frequency and magnitude of load in UFLS systems. 
                        <E T="03">Mandatory Reliability Standards for the Bulk-Power System,</E>
                         Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242, 
                        <E T="03">order on reh'g,</E>
                         Order No. 693-A, 120 FERC ¶ 61,053, at P 145 (2007). NERC submitted a response to this request on February 1, 2008 that included the underfrequency set points and magnitude of load shed in each Regional Entity. NERC, 
                        <E T="03">Response to FERC Supplemental Request for Information on the Status of Underfrequency Load Shedding,</E>
                         Docket No. RM06-16-000 (filed Feb. 1, 2008).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         EPRI Tutorial at page 4-81.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">Id.</E>
                         at P 4-78, 4-79.
                    </P>
                </FTNT>
                <P>
                    7. Once a frequency threshold 
                    <SU>12</SU>
                    <FTREF/>
                     is identified, the balance of resources and demand to be maintained to prevent the system from reaching that frequency threshold is determined. UFLS programs use validated models of the power system, which consist of mathematical representations of static (e.g., transformers and transmission lines) and dynamic (e.g., generators and motor loads) components of the power system aggregated to simulate how the system performs during system operations.
                    <SU>13</SU>
                    <FTREF/>
                     Models are validated, typically, by comparing actual system operations against simulated system operations to ensure the simulated system operations are within a defined and acceptable margin of tolerance relative to actual system operations. Inaccurate power system models may result in a UFLS program that does not perform as desired, thus undermining the reliability objective of UFLS.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         A frequency threshold is a pre-determined frequency that UFLS programs are designed to avoid reaching, as the system may become unstable at this frequency.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See, e.g.,</E>
                         PowerTech Labs Inc., 
                        <E T="03">2010 Evaluation and Assessment of Southwest Power Pool (SPP) Under-Frequency Load Shedding Scheme, available at</E>
                          
                        <E T="03">http://www.spp.org/publications/SPP-2010-UFLS-Final.pdf.</E>
                    </P>
                </FTNT>
                <P>
                    8. A UFLS program is designed to shed sufficient load to arrest system frequency decline without shedding too much load such that frequency increases above 60 Hz. If a UFLS program is not effective, either because of invalid power system models or miscoordination of the UFLS program with entities inside and outside of the intended island, it may not achieve the reliability objective of preventing cascading outages. This, in turn, could further undermine reliability and recovery of the Bulk-Power System during a system emergency.
                    <SU>14</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         For example, if not enough load is shed to arrest frequency decline, additional resources may disconnect from the Interconnection to prevent damage to generators, and thus system frequency will continue to collapse. Conversely, if too much load is shed, the system frequency could exceed 60 Hz also causing resources to disconnect from the Interconnection to prevent damage to generators. EPRI Tutorial at page 4-78.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Minimum Amount of Load to Shed</HD>
                <P>
                    9. The amount of load to disconnect is the amount of load shed at each underfrequency set point, typically expressed in megawatts or percent of system peak load or both.
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         EPRI Tutorial at page 4-78.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">3. What Load to Shed</HD>
                <P>
                    10. In addition to determining the amount of load to disconnect based on validated power system models, a UFLS program identifies what loads to shed 
                    <PRTPAGE P="66222"/>
                    and their locations. Therefore, in deciding what specific loads to shed, consideration is given to whether the load is critical (e.g., hospitals, police stations, or fire stations). These loads would typically not be included in a UFLS program.
                </P>
                <HD SOURCE="HD2">B. Mandatory Reliability Standards</HD>
                <P>
                    11. Section 215 of the FPA requires a Commission-certified ERO to develop mandatory and enforceable Reliability Standards, which are subject to Commission review and approval. Once approved, the Reliability Standards may be enforced by the ERO, subject to Commission oversight, or by the Commission independently.
                    <SU>16</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See</E>
                         16 U.S.C. 824o(e).
                    </P>
                </FTNT>
                <P>
                    12. Pursuant to section 215 of the FPA, the Commission established a process to select and certify an ERO 
                    <SU>17</SU>
                    <FTREF/>
                     and, subsequently, certified NERC as the ERO.
                    <SU>18</SU>
                    <FTREF/>
                     On March 16, 2007, the Commission issued Order No. 693, approving 83 of the 107 Reliability Standards filed by NERC, including Reliability Standards PRC-007-0, PRC-009-0, and EOP-003-1.
                    <SU>19</SU>
                    <FTREF/>
                     The Commission neither approved nor remanded NERC-approved Reliability Standard PRC-006-0 in Order No. 693.
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">Rules Concerning Certification of the Electric Reliability Organization; and Procedures for the Establishment, Approval and Enforcement of Electric Reliability Standards,</E>
                         Order No. 672, FERC Stats. &amp; Regs. ¶ 31,204, 
                        <E T="03">order on reh'g,</E>
                         Order No. 672-A, FERC Stats. &amp; Regs. ¶ 31,212 (2006).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">North American Electric Reliability Corp.,</E>
                         116 FERC ¶ 61,062, 
                        <E T="03">order on reh'g &amp; compliance,</E>
                         117 FERC ¶ 61,126 (2006), 
                        <E T="03">aff'd sub nom., Alcoa, Inc.</E>
                         v.
                        <E T="03"> FERC,</E>
                         564 F.3d 1342 (D.C. Cir. 2009).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at P 603.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">Id.</E>
                         P 1479.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. NERC-Approved Reliability Standard</HD>
                <HD SOURCE="HD3">1. PRC-006-0</HD>
                <P>
                    13. NERC-approved Reliability Standard PRC-006-0 addresses the development of a regional UFLS program that is used as a last resort to preserve islanding operation following a major system event on the Bulk-Power System that could otherwise cause the island system frequency to collapse. PRC-006-0 requires regional reliability organizations to develop, coordinate, document and assess UFLS program design and effectiveness at least every five years. In Order No. 693, the Commission determined neither to approve nor remand this “fill-in-the-blank” Reliability Standard because the regional procedures had not been submitted, and the Commission held that it would not propose to approve or remand PRC-006-0 until the ERO submitted the additional information.
                    <SU>21</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">Id.</E>
                         P 1477, 1479.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">D. Currently Effective Reliability Standards</HD>
                <HD SOURCE="HD3">1. PRC-007-0</HD>
                <P>14. Reliability Standard PRC-007-0 requires transmission owners, transmission operators, load serving entities (LSEs) and distribution providers to provide, and annually update, their underfrequency data to facilitate the regional reliability organization's maintenance of the UFLS program database.</P>
                <HD SOURCE="HD3">2. PRC-009-0</HD>
                <P>15. Reliability Standard PRC-009-0 requires that the performance of a UFLS system be analyzed and documented following an underfrequency event by requiring the transmission owner, transmission operator, LSE and distribution provider to document the deployment of their UFLS systems in accordance with the regional reliability organization's program.</P>
                <HD SOURCE="HD3">3. EOP-003-1</HD>
                <P>16. Reliability Standard EOP-003-1 addresses load shedding plans and requires that balancing authorities and transmission operators operating with insufficient transmission and/or generation capacity have the capability and authority to shed load rather than risk a failure of the system. It includes requirements to establish plans for automatic load shedding for underfrequency or undervoltage, manual load shedding to respond to real-time emergencies, and communication with other balancing authorities and transmission operators.</P>
                <HD SOURCE="HD1">II. Proposed Reliability Standards</HD>
                <P>
                    17. On March 31, 2011, NERC filed a petition seeking Commission approval of proposed Reliability Standards PRC-006-1 and EOP-003-2 and requesting the concurrent retirement of the currently effective Reliability Standards PRC-007-0, PRC-009-0, and EOP-003-1 and NERC-approved Reliability Standard PRC-006-0.
                    <SU>22</SU>
                    <FTREF/>
                     NERC requests an effective date for PRC-006-1 and EOP-003-2 of one year following the first day of the first calendar quarter after applicable regulatory approvals with respect to all Requirements of the proposed Reliability Standards 
                    <E T="03">except</E>
                     Parts 4.1 through 4.6 of Requirement R4 of PRC-006-1. With respect to Parts 4.1 through 4.6 of Requirement R4 of PRC-006-1, NERC requests an effective date of one year following the receipt of generation data as would be required in draft Reliability Standard PRC-024-1 
                    <SU>23</SU>
                    <FTREF/>
                     but no sooner than one year following the first day of the first calendar quarter after applicable regulatory approvals of PRC-006-1.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         NERC Petition at 1. The proposed new Reliability Standards are not attached to the NOPR. They are, however, available on the Commission's eLibrary document retrieval system in Docket No. RM11-20-000 and are available on the ERO's Web site, 
                        <E T="03">http://www.nerc.com.</E>
                         Reliability Standards approved by the Commission are not codified in the CFR.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         PRC-024-1 addresses “Generator Performance During Frequency and Voltage Excursions” and is currently being developed in the NERC standard drafting process.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">A. PRC-006-1</HD>
                <P>
                    18. Proposed Reliability Standard PRC-006-1 would apply to planning coordinators, “UFLS entities,” 
                    <SU>24</SU>
                    <FTREF/>
                     and transmission owners that “own Elements identified in the UFLS program established by the Planning Coordinators.” NERC states that the primary purpose of the proposed Reliability Standard is the establishment of design and document requirements for UFLS programs that arrest declining frequency and assist recovery of frequency following system events leading to frequency degradation.
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         PRC-006-1 defines “UFLS entities” as: “All entities that are responsible for the ownership, operation, or control of UFLS equipment as required by the UFLS program established by the Planning Coordinators.”
                    </P>
                </FTNT>
                <P>
                    19. NERC states that PRC-006-1 satisfies the Commission's criteria, set forth in Order No. 672, for determining whether a proposed Reliability Standard is just, reasonable, not unduly discriminatory or preferential and in the public interest.
                    <SU>25</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         Order No. 672, FERC Stats. &amp; Regs. ¶ 31,204 at P 323-37.
                    </P>
                </FTNT>
                <P>20. According to NERC, PRC-006-1 is designed to achieve a specific reliability goal by establishing design and documentation requirements for automatic UFLS programs to arrest declining frequency, assist recovery of frequency following underfrequency events and provide last resort system preservation measures. NERC contends that PRC-006-1 contains a technically sound method to achieve its reliability goal by establishing a framework for developing, designing, assessing and coordinating UFLS programs, and that PRC-006-1 is clear and unambiguous regarding what is required and who is required to comply with the Reliability Standard.</P>
                <P>
                    21. NERC states that PRC-006-1 does not reflect “best practices” without regard to implementation cost.
                    <SU>26</SU>
                    <FTREF/>
                     NERC contends that it achieves a specific reliability goal of establishing design 
                    <PRTPAGE P="66223"/>
                    and documentation requirements for automatic UFLS programs to arrest declining frequency and assist recovery following underfrequency events, and that UFLS programs provide last resort system preservation measures by shedding load during system disturbances that result in substantial imbalance between load and generation. NERC also maintains that PRC-006-1 does not aim at a “lowest common denominator” but instead establishes common performance characteristics that all UFLS programs must meet to effectively protect Bulk-Power System reliability.
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         NERC Petition at 24.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">Id.</E>
                         at 26.
                    </P>
                </FTNT>
                <P>22. NERC states that PRC-006-1 does not include any differentiation in requirements based on entity size, though it provides the opportunity for planning coordinators to consider input from smaller entities when developing the UFLS program. NERC further explains that PRC-006-1 would apply throughout North America, with variances for entities within the Western Electricity Coordinating Council (WECC) and the Quebec Interconnections.</P>
                <P>23. As proposed by NERC, PRC-006-1 has 14 requirements and 19 sub-requirements, summarized as follows:</P>
                <P>
                    <E T="03">Requirement R1:</E>
                     Requires each planning coordinator to develop and document criteria to identify portions of the bulk electric system that may form islands.
                </P>
                <P>
                    <E T="03">Requirement R2:</E>
                     Requires each planning coordinator to identify the islands to serve as a basis for designing its UFLS program. Sub-Requirements 2.1, 2.2, and 2.3 serve as a checklist of items that the entity must consider when identifying islands.
                </P>
                <P>
                    <E T="03">Requirement R3:</E>
                     Requires each planning coordinator to develop a UFLS program, including notification of and a schedule for implementation by the UFLS entities within its area, that meets the specific performance characteristics set forth in sub-Requirements 3.1 through 3.3 in simulations of underfrequency conditions resulting from an imbalance of up to 25 percent within the identified island.
                </P>
                <P>
                    <E T="03">Requirement R4:</E>
                     Requires each planning coordinator to conduct and document a UFLS design assessment at least once every five years that determines through dynamic simulation whether the UFLS program design meets the performance characteristics in Requirement R3 for each island identified in Requirement R2, with sub-Requirements 4.1 through 4.7 specifying items that the simulation must model.
                </P>
                <P>
                    <E T="03">Requirement R5:</E>
                     Requires each planning coordinator to coordinate its UFLS design with all other planning coordinators whose areas or portions of whose areas are also part of the same identified island through specific actions identified in Requirement R5.
                </P>
                <P>
                    <E T="03">Requirement R6:</E>
                     Requires each planning coordinator to maintain a UFLS database containing data necessary to model its UFLS program for use in event analyses and assessments of the UFLS program at least once each calendar year, with no more than 15 months between maintenance activities.
                </P>
                <P>
                    <E T="03">Requirement R7:</E>
                     Requires each planning coordinator to provide its UFLS database to other planning coordinators within its Interconnection within 30 calendar days of request.
                </P>
                <P>
                    <E T="03">Requirement R8:</E>
                     Requires each UFLS entity to provide data to its planning coordinator(s) according to the format and schedule specified by the planning coordinator(s) to support maintenance of the UFLS database.
                </P>
                <P>
                    <E T="03">Requirement R9:</E>
                     Requires each UFLS entity to provide automatic tripping of load in accordance with the UFLS program design and schedule for application determined by its planning coordinator(s) in each planning coordinator area in which it owns assets.
                </P>
                <P>
                    <E T="03">Requirement R10:</E>
                     Requires each transmission owner to provide automatic switching of its existing capacitor banks, transmission lines, and reactors to control overvoltage as a result of underfrequency load shedding if required by the UFLS program and schedule for application determined by the planning coordinator(s) in each planning coordinator area in which the transmission owner owns transmission.
                </P>
                <P>
                    <E T="03">Requirement R11:</E>
                     Requires each planning coordinator, in whose area a bulk electric system islanding event results in system frequency excursions below the initializing set points of the UFLS program, to conduct and document an assessment of the event within one year of event actuation that evaluates the performance of the UFLS equipment (sub-Requirement 11.1), and the effectiveness of the UFLS program (sub-Requirement 11.2).
                </P>
                <P>
                    <E T="03">Requirement R12:</E>
                     Requires each planning coordinator, in whose islanding event assessment (Requirement R11) UFLS program deficiencies are identified, to conduct and document a UFLS design assessment to consider the identified deficiencies within two years of event actuation.
                </P>
                <P>
                    <E T="03">Requirement R13:</E>
                     Requires each planning coordinator, in whose area a bulk electric system islanding event occurred that also included the area(s) or portions of area(s) of other planning coordinator(s) in the same islanding event and that resulted in system frequency excursions below the initializing set points of the UFLS program, to coordinate its event assessment (in accordance with Requirement R11) with all other planning coordinators whose areas or portions of whose areas were also included in the same islanding event by either: (i) Conducting a joint event assessment per Requirement R11 among the planning coordinators whose areas or portions of whose areas were included in the same islanding event; or (ii) conducting an independent event assessment per Requirement R11 that reaches conclusions and recommendations consistent with those of the event assessments of the other planning coordinators whose areas or portions of whose areas were included in the same islanding event; or (iii) conducting an independent event assessment per Requirement R11 and where the assessment fails to reach conclusions and recommendations consistent with those of the event assessments of the other planning coordinators whose areas or portions of whose areas were included in the same islanding event, identifying differences in the assessments that likely resulted in the differences in the conclusions and recommendations and report these differences to the other planning coordinators whose areas or portions of whose areas were included in the same islanding event and to the ERO.
                </P>
                <P>
                    <E T="03">Requirement R14:</E>
                     Requires the planning coordinator to respond to written comments submitted by UFLS entities and transmission owners within its planning coordinator area following a comment period and before finalizing its UFLS program, indicating in the written response to comments whether changes will be made or reasons why changes will not be made to the UFLS program, including a schedule for implementation (sub-Requirement 14.1) and the UFLS design assessment (sub-Requirement 14.2).
                </P>
                <HD SOURCE="HD2">B. EOP-003-2</HD>
                <P>
                    24. Proposed Reliability Standard EOP-003-2 would apply to balancing authorities and transmission operators. NERC states that EOP-003-2 makes minimal changes to EOP-003-1 by removing references to UFLS, which NERC describes as redundant in light of proposed Reliability Standard PRC-006-1, and instead focuses proposed Reliability Standard EOP-003-2 on undervoltage conditions.
                    <PRTPAGE P="66224"/>
                </P>
                <HD SOURCE="HD1">III. Discussion</HD>
                <P>25. Pursuant to section 215(d)(2) of the FPA, the Commission proposes to approve Reliability Standard PRC-006-1 and EOP-003-1 as just, reasonable, not unduly discriminatory or preferential, and in the public interest. The Commission believes that the UFLS program addressed in the proposed Reliability Standards is important to arresting declining frequency and assisting recovery of frequency following system events that lead to system instability, which can result in a blackout. The Commission finds that the proposed Reliability Standards are necessary for reliability because UFLS is used in extreme conditions to stabilize the balance between generation and load after an electrical island has been formed, dropping enough load to allow frequency to stabilize within the island. Reliability Standard PRC-006-1, in conjunction with the conforming changes to EOP-003-2, provides last resort Bulk-Power System preservation measures by establishing the first national Reliability Standard of common performance characteristics that all UFLS programs must meet. In addition, the Commission proposes to approve the related VRFs and VSLs, implementation plan, and effective date proposed by NERC. Finally, the Commission proposes to approve the retirement of the currently effective Reliability Standards PRC-007-0, PRC-009-0, and EOP-003-1, and the NERC-approved Reliability Standard PRC-006-0.</P>
                <P>26. The Commission addresses or seeks comments from the ERO and other interested persons on aspects of the proposed Reliability Standards. Specifically, we address or seek comments on the following issues: (A) Impact of resources not connected to the bulk electric system; (B) validation of power system models used to simulate ULFS programs; (C) scope of UFLS events assessments; (D) impact of generator owner trip settings outside of the UFLS program; (E) UFLS program coordination with other protection systems; (F) identification of island boundaries in UFLS programs; (G) automatic load shedding in PRC-006-1 and manual load shedding in EOP-003-2; (H) elimination of balancing authority responsibilities in EOP-003-2; and (I) the “Lower VSL” for Requirement R8 and the “Medium” VRF for Requirement R5 of PRC-006-1. These issues also apply to the corresponding Requirements in the requested regional variance for WECC in PRC-006-1.</P>
                <HD SOURCE="HD2">A. Impact of Resources Not Connected to Bulk Electric System Facilities</HD>
                <P>27. As described above, UFLS programs are designed to maintain balance between resources and load in a defined area (e.g., an Interconnection, Regional Entity area, or planning coordinator area). When a resource is lost, load exceeds supply causing frequency to decrease below its scheduled value (e.g., 60 Hz in the United States). Conversely, a loss of load or excess supply can result in higher frequencies than scheduled, resulting in an overfrequency condition. As a last resort, UFLS programs are initiated during extreme underfrequency conditions to reestablish balance by shedding load at predetermined frequencies and times to prevent system-wide blackouts.</P>
                <P>28. Requirement R2 of PRC-006-1 requires planning coordinators to identify islands to serve as a basis for designing UFLS programs. Requirement R3 addresses performance characteristics for UFLS programs. Requirement R4 requires each planning coordinator to conduct and document the assessment of its UFLS design and determine if the UFLS program meets the performance characteristics in Requirement R3 for each island identified in Requirement R2.</P>
                <P>29. The simulations outlined in Requirement R4 all concern individual generating units greater than 20 MVA gross nameplate rating or generating plants/facilities greater then 75 MVA “connected to the bulk electric system.” However, some generation that meets the 20 MVA and 75 MVA criteria is not connected to bulk electric system facilities. Accordingly, those resources not connected to bulk electric system facilities would not be modeled pursuant to Requirement R4. However, a resource not connected to the bulk electric system may serve load designed to be shed in a UFLS program. The Commission is concerned that failure to account for resources not connected to the bulk electric system in a planning coordinator's UFLS program could result in the planning coordinator being unaware of how such resources respond to underfrequency conditions. If the planning coordinator is unaware of how these facilities have responded, it may plan to shed more load than is required for an area's frequency to return to normal. This could lead to an unintended overfrequency condition if the plan is carried out in the operating timeframe. These conditions, in turn, could lead the plan to violate the performance characteristics specified in Requirement R3.</P>
                <P>30. The performance characteristics identified in Requirement R3 provide acceptable parameters for developing UFLS programs that are designed to restore balance between resources and load. However, the Commission is concerned that generation resources or facilities that are not connected to the bulk electric system may not be considered during the development of UFLS programs.</P>
                <P>31. The Commission seeks comments from the ERO and other interested persons as to whether and how all resources required for the reliable operation of the bulk electric system, including resources not connected to bulk electric system facilities, are considered in the development of UFLS programs under Requirements R3 and R4.</P>
                <HD SOURCE="HD2">B. Validation of Power System Models</HD>
                <P>
                    32. Power systems consist of static components (e.g., transformers and transmission lines) and dynamic components (e.g., generators and motor loads). Mathematical representations of these components are aggregated to create an area's power system model. Power system planners 
                    <SU>28</SU>
                    <FTREF/>
                     and system operators base decisions on simulations, both static and dynamic, using area power system models to meet requirements in both Commission-approved planning and operational Reliability Standards.
                    <SU>29</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         Power system planners may include functional entities such as transmission planners and planning coordinators.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See, e.g.,</E>
                         Reliability Standards MOD-010-0, MOD-012-0 and TOP-002-2a, Requirement R19.
                    </P>
                </FTNT>
                <P>33. Requirements R4 and R11 of PRC-006-1 require applicable entities to use dynamic simulations to design and assess the effectiveness of UFLS programs. As previously discussed, UFLS programs are designed to provide last resort system preservation measures by: (1) Arresting declining frequency; and (2) assisting recovery of frequency following underfrequency events. Dynamic simulations that do not accurately represent the power system can result in an UFLS program that is ineffective.</P>
                <P>
                    34. The Commission believes that the UFLS program design requirements established in Requirement R2 and the required assessments established in Requirements R4 and R11 of PRC-006-1 are generally acceptable and include improvements above the current Reliability Standards. Accordingly, the Commission believes that the language in the proposed Requirements is appropriate.
                    <PRTPAGE P="66225"/>
                </P>
                <HD SOURCE="HD2">C. UFLS Event Assessments</HD>
                <HD SOURCE="HD3">1. Assessments in the Absence of Island Formation</HD>
                <P>35. Requirement R11 of PRC-006-1 requires planning coordinators to conduct assessments after a “BES islanding event results in system frequency excursion below the initializing set points of the UFLS program.” The Commission is concerned whether the phrase “BES islanding event” could be interpreted to mean that a planning coordinator only has to assess an event if it meets both of the following requirements: (1) System frequency excursions fall below the initializing set point for UFLS; and (2) bulk electric system islands form within the Interconnection. If the frequency falls below the initializing UFLS set point but islands do not form (e.g., because the event was not severe enough to isolate portions of the Interconnection, or UFLS or other protection systems failed to operate properly to form islands), an assessment of the performance of the UFLS program for this event is still useful because it can determine if the UFLS program operated as expected.</P>
                <P>36. The Commission seeks clarification from the ERO regarding what actions must planning coordinators take under Requirement R11 if an event results in system frequency excursions falling below this initializing set point for UFLS but without the formation of a bulk electric system island.</P>
                <HD SOURCE="HD3">2. Coordination of Assessments and Results</HD>
                <P>37. Requirements R5 and R13 of PRC-006-1 require planning coordinators that share identified islands to coordinate UFLS program design and event assessment. The options for coordinating designs of UFLS programs in Requirement R5 include: (1) Developing a common program; (2) conducting a joint UFLS design assessment among the planning coordinators whose area or portions of whose areas are part of the same identified island; or (3) conducting an independent design assessment and, in the event the UFLS design assessment fails to meet Requirement R3, identify modifications to the UFLS program(s) to meet Requirement R3 and report these modifications as recommendations to the other planning coordinators.</P>
                <P>38. The options for coordinating event assessments in Requirement R13 include: (1) Conducting a joint event assessment per Requirement R11 among planning coordinators whose areas were affected; (2) conducting an independent event assessment per Requirement R11 that reaches conclusions and recommendations consistent with other planning coordinators whose areas were affected; or (3) conducting an independent event assessment per Requirement R11 and where the assessment fails to reach conclusions and recommendations consistent with those of the other planning coordinators whose areas were affected by the same islanding event, identify differences in the assessments and report these differences to the other affected planning coordinators. The Commission seeks comments from the ERO and other interested persons as to whether the differences should be subsequently reported to the reliability coordinator for resolution in the event that the process does not resolve differences in the assessments.</P>
                <P>39. The Commission believes that Requirements R5 and R13 provide flexibility in coordinating UFLS design programs and event assessments among planning coordinators whose areas fall within the same island or whose areas are affected by the same event. Accordingly, the Commission believes that the language in the proposed Requirements is appropriate.</P>
                <HD SOURCE="HD3">3. Assessment Timeline for Completion</HD>
                <P>40. Requirement R11 of Reliability Standard PRC-006-1 requires a planning coordinator to perform an island event assessment within one year of an event. If the planning coordinator identifies program deficiencies, Requirement R12 requires the planning coordinator to conduct and document UFLS design assessments, which are meant to consider the deficiencies, within two years of an event. The Commission is concerned that this time frame may be too long since it appears that island event assessments and consideration of deficiencies could reasonably be conducted in a much shorter time frame. Under NERC's proposal, deficiencies could remain within a UFLS program for two years from an event exposing the Bulk-Power System to instability, uncontrolled separation and cascading outages should a frequency event occur that the UFLS program mishandles. NERC provided no explanation of its basis for the proposed two-year time frame.</P>
                <P>41. The Commission asks the ERO and other interested persons what the basis is for proposing a two-year time frame. In addition, the Commission seeks clarification from the ERO as to how soon after event actuation would an entity need to implement corrections in response to any deficiencies identified in the event assessment under Requirement R11.</P>
                <HD SOURCE="HD2">D. Generator Owner Trip Settings Outside of the UFLS Program</HD>
                <P>42. Requirements 4.1 through 4.7 of Reliability Standard PRC-006-1 are intended to capture the effects of generators that trip prior to UFLS initiation. As previously discussed, a generator trip normally creates an imbalance between resources and load causing system frequency to decline. Some generators may need to disconnect from the system prior to reaching underfrequency set points to protect their components from permanent damage. If this loss occurs during a system event, the generator can no longer provide a response to assist in arresting frequency decline. This resource loss also counteracts the response provided by other resources to arrest frequency decline, increasing the likelihood of instability, uncontrolled separation, and cascading outages.</P>
                <P>43. We agree that planning coordinators should consider generators that trip prior to underfrequency set points when developing their UFLS programs. The Commission seeks comments from the ERO and other interested persons on how generation losses outside of the UFLS set points (i.e., generators having trip settings prior to the UFLS underfrequency set points) should be accounted for in UFLS programs (e.g., generator owners who trip outside of the UFLS set points could procure load to shed to account for the loss in generation).</P>
                <HD SOURCE="HD2">E. UFLS Program Coordination With Other Protection Systems</HD>
                <P>
                    44. Recommendation 21C of the Blackout Report addresses the coordination of protection systems.
                    <SU>30</SU>
                    <FTREF/>
                     The recommendation states that NERC shall “determine the goals and principles needed to establish an integrated approach to relay protection for generators and transmission lines and the use of underfrequency and undervoltage load shedding (UFLS and UVLS) programs. An integrated approach is needed to ensure that at the local and regional levels, these interactive components provide an appropriate balance of risks and benefits in terms of protecting specific assets and facilitating overall grid survival.” 
                    <SU>31</SU>
                    <FTREF/>
                     Accordingly, an integrated approach requires coordination of all types of protection systems (e.g., UFLS, UVLS), internally and externally to an entity's 
                    <PRTPAGE P="66226"/>
                    area, to be responsive to the Blackout Report.
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         Blackout Report at 159.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    45. While PRC-006-1 requires coordination of UFLS programs among planning coordinators in Requirements R5, R7, and R13, it does not appear to capture the same level of coordination with other protection systems as in Requirement R1.2.8 of PRC-006-0.
                    <SU>32</SU>
                    <FTREF/>
                     The Commission seeks comments from NERC and other interested persons on whether and how coordination with other protection systems is or is not achieved under the new requirements.
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         Requirement 1.2.8 of PRC-006-0 encompasses “[a]ny other schemes that are part of or impact the UFLS program.”
                    </P>
                </FTNT>
                <HD SOURCE="HD2">F. Identification of Island Boundaries</HD>
                <P>46. Requirement R1 of PRC-006-1 directs planning coordinators to develop criteria to select areas that may form islands based on historical events and system studies. Historical events and system studies provide planning coordinators with the data necessary to determine where islands will occur based on the physics of the system. Requirement R2.3 clarifies that islands identified in Requirement R1, which span two or more Regional Entity areas, should be broken up such that each Regional Entity area forms an island. Requirement R2.3 allows planning coordinators to “adjust the island boundaries to differ from the Regional Entity area boundaries by mutual consent where necessary” to preserve contiguous island boundaries that better reflect simulations. The Commission agrees that identifying island boundaries based on where they are likely to occur due to system characteristics, as opposed to maintaining rigid Regional Entity area boundaries, should result in more effective UFLS programs. Accordingly, the Commission encourages cooperation among entities to create UFLS programs that set island boundaries based on where separations are expected to occur during an underfrequency event.</P>
                <P>
                    47. In its petition, NERC states that the Requirements allow planning coordinators to “select islands including interconnected portions of the bulk electric system in adjacent Planning Coordinator areas and Regional Entity areas, without the need for coordinating this selection with Planning Coordinators in neighboring regions.” 
                    <SU>33</SU>
                    <FTREF/>
                     Requirement R2.3 of PRC-006-1, however, requires “mutual consent” to adjust island boundaries from Regional Entity boundaries. The Commission seeks clarification from the ERO concerning the required degree of cooperation and/or “mutual consent” between planning coordinators under the proposed Reliability Standard in order for island boundaries to be set so that, while deviating from Regional Entity boundaries, they better approximate actual island separation boundaries.
                </P>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         NERC Petition at 75-76.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">G. Automatic Load Shedding and Manual Load Shedding</HD>
                <P>48. Proposed Reliability Standard PRC-006-1 requires automatically shedding predetermined amounts of load if frequency declines to the UFLS set point in order to rebalance resources and demand and prevent frequency decline that might cause instability, uncontrolled separation, or cascading outages. Proposed Reliability Standard EOP-003-2 requires manual load shedding plans, which may be employed in addition to the automatic load shedding in the UFLS program, or to mitigate other reliability issues. If load allocated to be shed automatically is also planned for manual load shedding, then that load resource would be double-counted. Once load is disconnected from the system, either automatically or manually, it cannot be used again to arrest frequency decline. In the event that a load resource is double-counted and removed during automatic UFLS, the manual load shedding cannot be completed if called upon. Even if additional load is located and shed to compensate for this missing load, the system would be put into an un-studied state and could have unpredicted, negative responses. Accordingly, resources allocated to each type of load shedding (i.e., automatic and manual) should not overlap.</P>
                <P>49. There are no requirements in PRC-006-1 to coordinate automatic load shedding by UFLS and manual load shedding under EOP-003-2. The Commission seeks comments from the ERO and other interested persons on how the coordination of automatic and manual load shedding is considered in light of the fact that the proposed Reliability Standards do not explicitly require coordination.</P>
                <HD SOURCE="HD2">H. Elimination of Requirements for Balancing Authorities in EOP-003-2</HD>
                <P>50. Requirements R2, R4, and R7 of the currently-effective Reliability Standard EOP-003-1 apply to transmission operators and balancing authorities. Proposed Reliability Standard EOP-003-2 proposes to eliminate balancing authorities from Requirements R2, R4, and R7.</P>
                <P>
                    51. Under the proposed modification, balancing authorities would no longer: (i) Establish plans for automatic load shedding for underfrequency or undervoltage conditions (Requirement R2); (ii) consider factors (including frequency, rate of frequency decay, voltage level, rate of voltage decay, or power flow levels) in designing an automatic undervoltage load shedding scheme (Requirement R4); and (iii) coordinate automatic load shedding throughout its area with underfrequency isolation of generating units, tripping of shunt capacitors, and other automatic actions that will occur under abnormal frequency, voltage, or power flow conditions (Requirement R7). In its petition, NERC explains that balancing authorities were deleted from Requirements R2 and R4 “because the frequency related aspects of these requirements were removed, leaving only consideration of automatic undervoltage load shedding in these two requirements.” 
                    <SU>34</SU>
                    <FTREF/>
                     NERC's petition, however, does not explain why balancing authorities were removed from Requirement R7. Moreover, given that balancing authorities would no longer be subject to Requirements R2, R4, and R7 of EOP-003-2 and are not listed as applicable entities in PRC-006-1, the proposed Reliability Standards do not preserve these existing balancing authority responsibilities.
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         NERC Petition at 42.
                    </P>
                </FTNT>
                <P>52. The Commission seeks clarification from the ERO as to why these existing balancing authority responsibilities were not incorporated into Reliability Standards PRC-006-1 or EOP-003-2. The Commission also seeks comments from the ERO and other interested persons as to why balancing authorities should not be informed of UFLS program plans that directly impact balancing authority functions.</P>
                <HD SOURCE="HD2">I. Violation Risk Factors and Violation Severity Levels</HD>
                <P>53. NERC states that each primary requirement in PRC-006-1 and EOP-003-2 is assigned a Violation Risk Factor (VRF) and Violation Severity Level (VSL) and that these elements support the determination of an initial value range for the Base Penalty Amount regarding violations of requirements in Commission-approved Reliability Standards, as defined in the ERO Sanction Guidelines.</P>
                <P>54. The Commission proposes to approve the VRFs and VSLs in PRC-006-1 and EOP-003-2. However, the Commission seeks comments from the ERO and other interested persons regarding one proposed VSL and one proposed VRF for PRC-006-1.</P>
                <P>
                    55. The “Lower VSL” assignment for Requirement R8 in PRC-006-1 applies 
                    <PRTPAGE P="66227"/>
                    when a UFLS entity fails to provide data to its planning coordinator for 5 to 10 calendar days following the schedule specified by the planning coordinator. Requirement R8 of PRC-006-1 does not include a 5-day grace period for providing data to planning coordinators. Accordingly, the subject VSL assignment may be inconsistent with the Commission's VSL Guideline 3. The guideline states that a VSL “should not appear to redefine or undermine the requirement.” 
                    <SU>35</SU>
                    <FTREF/>
                     The five-day grace period implicit in the proposed VSL appears to be inconsistent with this guideline. In addition, the proposed VSL creates a compliance issue. Specifically, it is unclear where a UFLS entity falls in the VRF and VSL matrices if it fails to provide data to its planning coordinator within 1 to 5 days of its scheduled date.
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         
                        <E T="03">North American Electric Reliability Corp.,</E>
                         123 FERC ¶ 61,284, at P 32 (2008).
                    </P>
                </FTNT>
                <P>
                    56. The VRF for Requirement R5, which requires planning coordinators to coordinate their UFLS program design with other planning coordinators whose area is in part of the same identified island, is proposed as “Medium.” NERC states that Requirement R5 is “not related to similar reliability goals in other standards.” 
                    <SU>36</SU>
                    <FTREF/>
                     However, coordination of load shedding plans is required in a similar manner in Requirement R3 of currently effective Reliability Standard EOP-003-1,
                    <SU>37</SU>
                    <FTREF/>
                     which includes a VRF of “High.” The lack of coordination of UFLS programs among planning coordinators within the same identified island could lead to ineffective UFLS operations and further cascading outages within the island when UFLS is activated.
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         NERC Petition at 46.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         Proposed Reliability Standard EOP-003-2 includes the same VRF assignment of “High” for Requirement R3.
                    </P>
                </FTNT>
                <P>
                    57. Guideline 3 of the Commission's VRF Guidelines states that “[a]bsent justification to the contrary, the Commission expects the assignment of Violation Risk Factors corresponding to Requirements that address similar reliability goals in different Reliability Standards would be treated comparably.” 
                    <SU>38</SU>
                    <FTREF/>
                     The Commission seeks clarification from the ERO why coordination of load shedding plans is a “High” VRF for transmission operators and balancing authorities in EOP-003-2 but NERC proposes a “Medium” VRF for planning coordinators in, PRC-006-1.
                </P>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         
                        <E T="03">North American Electric Reliability Corp.,</E>
                         119 FERC ¶ 61,145, at P 25 (2007).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">J. Implementation Plan and Effective Date</HD>
                <P>
                    58. NERC requests an effective date for PRC-006-1 and EOP-003-2 of one year following the first day of the first calendar quarter after applicable regulatory approvals with respect to all Requirements of the proposed Reliability Standards except Parts 4.1 through 4.6 of Requirement R4 of PRC-006-1. With respect to Parts 4.1 through 4.6 of Requirement R4 of PRC-006-1, NERC requests an effective date of one year following the receipt of generation data as required in Reliability Standard PRC-024-1,
                    <SU>39</SU>
                    <FTREF/>
                     but no sooner than one year following the first day of the first calendar quarter after applicable regulatory approvals of PRC-006-1.
                </P>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         PRC-024-1 addresses “Generator Performance During Frequency and Voltage Excursions” and is currently being developed in the NERC standard drafting process under Project 2007-09 (Generator Verification), which is one of NERC's priority projects.
                    </P>
                </FTNT>
                <P>59. NERC contends that the proposed implementation plan is not excessively long and allows sufficient time for entities to transition and install the necessary processes to become compliant. NERC maintains that the one year phase-in for compliance provides planning coordinators sufficient time: (1) To develop, modify, or validate (to determine that an existing program meets required performance characteristics) existing UFLS programs; and (2) to establish a schedule for implementation, or validate a schedule for completion of program revisions already in progress. Moreover, NERC states that transmission owners and distribution providers will comply with the schedule determined by planning coordinators but no sooner than the effective date of the standard.</P>
                <P>60. The Commission proposes to accept the implementation plan and effective date proposed by the ERO for PRC-006-1 and EOP-003-2. However, the Commission seeks comments from the ERO and other interested persons about any potential reliability gaps that may occur during the development and implementation of PRC-024-1, such as how the planning coordinators will adequately determine and apply UFLS simulations and plans in the absence of generator trip settings.</P>
                <HD SOURCE="HD1">IV. Information Collection Statement</HD>
                <P>
                    61. The Office of Management and Budget (OMB) regulations require that OMB approve certain reporting and recordkeeping (collections of information) imposed by an agency.
                    <SU>40</SU>
                    <FTREF/>
                     Upon approval of a collection(s) of information, OMB will assign an OMB control number and expiration date. Respondents subject to the filing requirements of this rule will not be penalized for failing to respond to these collections of information unless the collections of information display a valid OMB control number.
                </P>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         5 CFR 1320.11.
                    </P>
                </FTNT>
                <P>62. The Commission is submitting these reporting and recordkeeping requirements to OMB for its review and approval under section 3507(d) of PRA. Comments are solicited on the Commission's need for this information, whether the information will have practical utility, the accuracy of provided burden estimate, ways to enhance the quality, utility, and clarity of the information to be collected, and any suggested methods for minimizing the respondent's burden, including the use of automated information techniques.</P>
                <P>
                    63. This Notice of Proposed Rulemaking proposes to approve Reliability Standards PRC-006-1 and EOP-003-2, which would replace currently effective Reliability Standards PRC-007-0, PRC-009-0, EOP-003-1 and NERC-approved Reliability Standard PRC-006-0.
                    <SU>41</SU>
                    <FTREF/>
                     As noted previously, Reliability Standard PRC-006-0 was never approved by the Commission, and therefore has never been mandatory and enforceable. On the other hand, Reliability Standards PRC-007-0 and PRC-009-0 were approved by the Commission and are currently mandatory and enforceable. Because Proposed Reliability Standard PRC-006-1 incorporates the requirements from Reliability Standards PRC-006-0, PRC-007-0, and PRC-009-0 some of the existing requirements will become mandatory and enforceable (where previously they were voluntary), while others continue to be so. To properly account for the burden on respondents, the Commission will treat the burden resulting from NERC-approved Reliability Standard PRC-006-0 as essentially new to the industry, even though it is likely that most applicable entities have already been complying.
                    <SU>42</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         PRC-006-0 was not approved by the Commission but remained effective as a NERC-approved standard (but not mandatory or enforceable). The other three standards were approved by the Commission. 
                        <E T="03">Mandatory Reliability Standards for the Bulk-Power System,</E>
                         Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242, 
                        <E T="03">order on reh'g,</E>
                         Order No. 693-A, 120 FERC ¶ 61,053 (2007).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         This statement is made because currently effective Reliability Standards PRC-007-0 and PRC-009-0 required UFLS entities to follow the UFLS program implemented by Reliability Standard PRC-006-0. Therefore, it is likely that entities have already been following the requirements contained in Reliability Standard PRC-006-0.
                    </P>
                </FTNT>
                <P>
                    64. The reporting requirements in proposed Reliability Standard EOP-
                    <PRTPAGE P="66228"/>
                    003-2 are virtually the same as those in currently effective Reliability Standard EOP-003-1. The difference is that proposed Reliability Standard EOP-003-2 proposes to eliminate balancing authorities from Requirements R2 and from Measure M1.
                    <SU>43</SU>
                    <FTREF/>
                     This requirement and measure deal with establishing and documenting automatic load shedding plans.
                </P>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         Balancing authorities are also removed from Requirements R4 and R7, but these do not have reporting requirements associated with them.
                    </P>
                </FTNT>
                <P>
                    65. 
                    <E T="03">Public Reporting Burden:</E>
                     Our estimate below regarding the number of respondents is based on the NERC compliance registry as of 7/29/11. According to the NERC compliance registry, there are 72 planning coordinators and 126 balancing authorities. The individual burden estimates are based on the time needed to gather data, run studies, and analyze study results to design or update the UFLS programs. Additionally, documentation and the review of UFLS program results by supervisors and management is included in the administrative estimations. These are consistent with estimates for similar tasks in other Commission approved standards.
                </P>
                <GPOTABLE COLS="5" OPTS="L2(,0,),tp0,i1" CDEF="s50,12,12,14,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            PRC-006-1 (Automatic underfrequency load shedding) 
                            <SU>44</SU>
                        </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents </LI>
                            <LI>annually </LI>
                        </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>responses per </LI>
                            <LI>respondent </LI>
                        </CHED>
                        <CHED H="1">
                            Average burden hours per 
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">Total annual burden hours </CHED>
                    </BOXHD>
                    <ROW RUL="s">
                        <ENT I="25"> </ENT>
                        <ENT>(1) </ENT>
                        <ENT>(2) </ENT>
                        <ENT>(3) </ENT>
                        <ENT>(1)x(2)x(3)</ENT>
                    </ROW>
                    <ROW RUL="s,n,n,s">
                        <ENT I="01">PCs *: Design and document Automatic UFLS Program</ENT>
                        <ENT O="xl"/>
                        <ENT O="xl"/>
                        <ENT>120</ENT>
                        <ENT>8,640</ENT>
                    </ROW>
                    <ROW RUL="s,n,n,s">
                        <ENT I="01">PCs: Management Review of Documentation</ENT>
                        <ENT>72</ENT>
                        <ENT>1</ENT>
                        <ENT>40</ENT>
                        <ENT>2,880</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">PCs: Record Retention</ENT>
                        <ENT O="xl"/>
                        <ENT O="xl"/>
                        <ENT>16</ENT>
                        <ENT>1,152</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>12,672</ENT>
                    </ROW>
                </GPOTABLE>
                <GPOTABLE COLS="6" OPTS="L2(0,,),ns,tp0,p0,8/9,i1" CDEF="s50,12,12,8,4,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW RUL="s">
                        <ENT I="22">
                            EOP-003-2 (Load Shedding Plans) 
                            <SU>45</SU>
                        </ENT>
                        <ENT A="04"/>
                    </ROW>
                    <ROW RUL="n,n,n,s">
                        <ENT I="01">Removal of BAs * from Reporting Requirements in R2 and M1 (Burden Reduction)</ENT>
                        <ENT>126</ENT>
                        <ENT>1</ENT>
                        <ENT>Reporting</ENT>
                        <ENT>−10</ENT>
                        <ENT>−1260</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="11"> </ENT>
                        <ENT> </ENT>
                        <ENT> </ENT>
                        <ENT>Record Retention</ENT>
                        <ENT>−1</ENT>
                        <ENT>−126</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>−1,386</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Net Change in Burden</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>11,286</ENT>
                    </ROW>
                    <TNOTE>* PC = Planning Coordinator; BA = Balancing Authority.</TNOTE>
                </GPOTABLE>
                <P>
                    <E T="03">Total Annual Hours for Collection:</E>
                     (Compliance/Documentation) = 11,286 hours.
                </P>
                <P>
                    <E T="03">Total Reporting Cost for Planning Coordinators:</E>
                     = 11,520 hours @ $120/hour = $1,382,400.
                </P>
                <P>
                    <E T="03">Total Record Retention Cost for Planning Coordinators:</E>
                     1,152 hours @ $28/hour = $32,256.
                </P>
                <P>
                    Total Reporting and Record Retention Cost Savings for Balancing Authorities: = (1,260 hours @ $120/hour) + (126 hours @ $28/hour) = $154,728.
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         Proposed Reliability Standard PRC-006-1 applies to both planning coordinators and to UFLS entities. However, the burden associated with the UFLS entities is not new because it was accounted for under Commission approved Reliability Standards PRC-007-0 and PRC-009-0.
                    </P>
                    <P>
                        <SU>45</SU>
                         Transmission operators also have to comply with Reliability Standard EOP-003-2 but since the applicable reporting requirements (and associated burden) have not changed from the existing standard to the proposed standard these entities are not included here.
                    </P>
                </FTNT>
                <P>
                    <E T="03">Total Annual Cost (Reporting + Record Retention)</E>
                     
                    <SU>46</SU>
                    <FTREF/>
                    : = $1,414,656−$154,728 = $1,259,928.
                </P>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         The hourly reporting cost is based on the cost of an engineer to implement the requirements of the rule. The record retention cost comes from Commission staff research on record retention requirements.
                    </P>
                </FTNT>
                <P>
                    <E T="03">Title:</E>
                     Mandatory Reliability Standards for the Bulk-Power System.
                </P>
                <P>
                    <E T="03">Action:</E>
                     Proposed Collection FERC-725A.
                </P>
                <P>
                    <E T="03">OMB Control No.:</E>
                     1902-0244.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Businesses or other for-profit institutions; not-for-profit institutions.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Necessity of the Information:</E>
                     This proposed rule proposes to approve the requested modifications to Reliability Standards pertaining to automatic underfrequency load shedding. The proposed Reliability Standards help ensure the reliable operation of the bulk electric system by arresting declining frequency and assisting recovery of frequency following system events leading to frequency degradation.
                </P>
                <P>
                    <E T="03">Internal Review:</E>
                     The Commission has reviewed the proposed Reliability Standards and made a determination that its action is necessary to implement section 215 of the FPA. These requirements, if accepted, should conform to the Commission's expectation for UFLS programs as well as procedures within the energy industry.
                </P>
                <P>
                    66. Interested persons may obtain information on the reporting requirements by contacting the following: Federal Energy Regulatory Commission, 888 First Street, NE. Washington, DC 20426 [
                    <E T="03">Attention:</E>
                     Ellen Brown, Office of the Executive Director, 
                    <E T="03">e-mail: DataClearance@ferc.gov,</E>
                      
                    <E T="03">phone:</E>
                     (202) 502-8663, 
                    <E T="03">fax:</E>
                     (202) 273-0873].
                </P>
                <P>
                    67. For submitting comments concerning the collection(s) of information and the associated burden estimate(s), please send your comments to the Commission and to the Office of Management and Budget, Office of Information and Regulatory Affairs, Washington, DC 20503 [
                    <E T="03">Attention:</E>
                     Desk Officer for the Federal Energy Regulatory Commission, 
                    <E T="03">phone:</E>
                     (202) 395-4638, 
                    <E T="03">fax:</E>
                     (202) 395-7285]. For security reasons, comments to OMB should be submitted by e-mail to: 
                    <E T="03">oira_submission@omb.eop.gov.</E>
                     Comments submitted to OMB should include Docket Number RM11-20 and OMB Control Number 1902-0244.
                </P>
                <HD SOURCE="HD1">V. Environmental Analysis</HD>
                <P>
                    68. The Commission is required to prepare an Environmental Assessment or an Environmental Impact Statement 
                    <PRTPAGE P="66229"/>
                    for any action that may have a significant adverse effect on the human environment.
                    <SU>47</SU>
                    <FTREF/>
                     The Commission has categorically excluded certain actions from this requirement as not having a significant effect on the human environment. Included in the exclusion are rules that are clarifying, corrective, or procedural or that do not substantially change the effect of the regulations being amended.
                    <SU>48</SU>
                    <FTREF/>
                     The actions proposed here fall within this categorical exclusion in the Commission's regulations.
                </P>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         Order No. 486, 
                        <E T="03">Regulations Implementing the National Environmental Policy Act of 1969,</E>
                         FERC Stats. &amp; Regs., Regulations Preambles 1986-1990¶ 30,783 (1987).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         18 CFR 380.4(a)(2)(ii).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">VI. Regulatory Flexibility Act Certification</HD>
                <P>
                    69. The Regulatory Flexibility Act of 1980 (RFA) 
                    <SU>49</SU>
                    <FTREF/>
                     generally requires a description and analysis of final rules that will have significant economic impact on a substantial number of small entities. The RFA mandates consideration of regulatory alternatives that accomplish the stated objectives of a proposed rule and that minimize any significant economic impact on a substantial number of small entities. The Small Business Administration's (SBA) Office of Size Standards develops the numerical definition of a small business.
                    <SU>50</SU>
                    <FTREF/>
                     The SBA has established a size standard for electric utilities, stating that a firm is small if, including its affiliates, it is primarily engaged in the transmission, generation and/or distribution of electric energy for sale and its total electric output for the preceding twelve months did not exceed four million megawatt hours.
                    <SU>51</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         5 U.S.C. 601-612.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         13 CFR 121.101.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         13 CFR 121.201, Sector 22, Utilities &amp; n.1.
                    </P>
                </FTNT>
                <P>70. Proposed Reliability Standard PRC-006-1 proposes to establish design, assessment, and documentation requirements for automatic UFLS program. It will be applicable to planning coordinators and entities that are responsible for the ownership, operation, or control of UFLS equipment. Proposed Standard EOP-003-2 proposes to remove balancing authorities from having to comply with R2 and M1 of the standard. Comparison of the NERC compliance registry with data submitted to the Energy Information Administration on Form EIA-861 indicates that perhaps as many as 8 small entities are registered as planning coordinators and 18 small entities are registered as balancing authorities. The Commission estimates that the small planning coordinators to whom the proposed Reliability Standard will apply will incur compliance and recordkeeping costs of $157,184 ($19,648 per planning coordinator) associated with the Standard's requirements. The small balancing authorities will receive a savings of $154,728 ($8,596 per balancing authority). Accordingly, proposed Reliability Standards PRC-006-1 and EOP-003-2 should not impose a significant operating cost increase or decrease on the affected small entities.</P>
                <P>71. Based on this understanding, the Commission certifies that these Reliability Standards will not have a significant economic impact on a substantial number of small entities. Accordingly, no regulatory flexibility analysis is required.</P>
                <HD SOURCE="HD1">VII. Comment Procedures</HD>
                <P>72. The Commission invites interested persons to submit comments on the matters and issues proposed in this notice to be adopted, including any related matters or alternative proposals that commenters may wish to discuss. Comments are due December 27, 2011. Comments must refer to Docket No. RM11-20-000, and must include the commenter's name, the organization they represent, if applicable, and their address in their comments.</P>
                <P>
                    73. The Commission encourages comments to be filed electronically via the eFiling link on the Commission's Web site at 
                    <E T="03">http://www.ferc.gov.</E>
                     The Commission accepts most standard word processing formats. Documents created electronically using word processing software should be filed in native applications or print-to-PDF format and not in a scanned format. Commenters filing electronically do not need to make a paper filing.
                </P>
                <P>74. Commenters that are not able to file comments electronically must send an original of their comments to: Federal Energy Regulatory Commission, Secretary of the Commission, 888 First Street, NE., Washington, DC 20426.</P>
                <P>75. All comments will be placed in the Commission's public files and may be viewed, printed, or downloaded remotely as described in the Document Availability section below. Commenters on this proposal are not required to serve copies of their comments on other commenters.</P>
                <HD SOURCE="HD1">VIII. Document Availability</HD>
                <P>
                    76. In addition to publishing the full text of this document in the 
                    <E T="04">Federal Register</E>
                    , the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the Internet through the Commission's Home Page (
                    <E T="03">http://www.ferc.gov</E>
                    ) and in the Commission's Public Reference Room during normal business hours (8:30 a.m. to 5 p.m. Eastern time) at 888 First Street, NE., Room 2A, Washington, DC 20426.
                </P>
                <P>77. From the Commission's Home Page on the Internet, this information is available on eLibrary. The full text of this document is available on eLibrary in PDF and Microsoft Word format for viewing, printing, and/or downloading. To access this document in eLibrary, type the docket number excluding the last three digits of this document in the docket number field.</P>
                <P>
                    78. User assistance is available for eLibrary and the Commission's Web site during normal business hours from the Commission's Online Support at 202-502-6652 (toll free at 1-866-208-3676) or e-mail at 
                    <E T="03">ferconlinesupport@ferc.gov,</E>
                     or the Public Reference Room at (202) 502-8371, TTY (202) 502-8659. E-mail the Public Reference Room at 
                    <E T="03">public.referenceroom@ferc.gov.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 18 CFR Part 40</HD>
                    <P>Electric power; Electric utilities; Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <SIG>
                    <P>By direction of the Commission. Commissioner Spitzer is not participating.</P>
                    <NAME>Nathaniel J. Davis, Sr.,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27625 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <CFR>18 CFR Part 40</CFR>
                <DEPDOC>[Docket No. RM11-18-000]</DEPDOC>
                <SUBJECT>Transmission Planning Reliability Standards</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Energy Regulatory Commission, DOE.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Transmission Planning (TPL) Reliability Standards are intended to ensure that the transmission system is planned and designed to meet an appropriate and specific set of reliability criteria. Reliability Standard TPL-002-0a references a table which identifies different categories of contingencies and allowable system impacts in the planning process. The table includes a footnote regarding planned or controlled interruption of electric supply where a single contingency occurs on a transmission system. North American Electric Reliability Corporation (NERC), the Commission-certified Electric 
                        <PRTPAGE P="66230"/>
                        Reliability Organization, requests approval of a revision to the footnote. In this notice, the Commission proposes to remand NERC's proposed revision to the footnote.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments are due December 27, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by docket number by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Agency Web Site: http://www.ferc.gov.</E>
                         Documents created electronically using word processing software should be filed in native applications or print-to-PDF format and not in a scanned format.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail/Hand Delivery:</E>
                         Commenters unable to file comments electronically must mail or hand deliver comments to: Federal Energy Regulatory Commission, Secretary of the Commission, 888 First Street, NE., Washington, DC 20426.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <FP SOURCE="FP-1">
                        Robert T. Stroh (Legal Information), Office of the General Counsel, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, 
                        <E T="03">Telephone:</E>
                         (202) 502-8473.
                    </FP>
                    <FP SOURCE="FP-1">
                        Eugene Blick (Technical Information), Office of Electric Reliability, Federal Energy Regulatory Commission, 888 First Street, NE., Washington, DC 20426, 
                        <E T="03">Telephone:</E>
                         (202) 502-8066.
                    </FP>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Notice of Proposed Rulemaking</HD>
                <DATE>October 20, 2011.</DATE>
                <P>
                    1. On March 31, 2011, the North American Electric Reliability Corporation (NERC) filed a petition seeking approval of Table 1, footnote `b' of four Reliability Standards: Transmission Planning: TPL-001-1—System Performance Under Normal (No Contingency) Conditions (Category A), TPL-002-1b—System Performance Following Loss of a Single Bulk Electric System Element (Category B), TPL-003-1a—System Performance Following Loss of Two or More Bulk Electric System Elements (Category C), and TPL-004-1- System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Elements (Category D).
                    <SU>1</SU>
                    <FTREF/>
                     Pursuant to section 215(d)(4) of the Federal Power Act (FPA) 
                    <SU>2</SU>
                    <FTREF/>
                    , the Commission proposes to remand the proposed Table 1, footnote b. As discussed below, the Commission believes that the proposed Reliability Standard does not meet the statutory criteria for approval that it be just, reasonable, not unduly discriminatory or preferential, and in the public interest.
                    <SU>3</SU>
                    <FTREF/>
                     The Commission seeks comments on its proposal.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         While footnote ‘b’ appears in all four of the above referenced TPL Reliability Standards, its relevance and practical applicability is limited to TPL-002-0a.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         18 U.S.C. 824o(d)(4) (2006).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         16 U.S.C. 824o(d)(2) (2006).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Background</HD>
                <P>2. Section 215 of the FPA requires a Commission-certified Electric Reliability Organization (ERO) to develop mandatory and enforceable Reliability Standards, which are subject to Commission review and approval. Approved Reliability Standards are enforced by the ERO, subject to Commission oversight, or by the Commission independently.</P>
                <P>
                    3. Pursuant to section 215 of the FPA, the Commission established a process to select and certify an ERO 
                    <SU>4</SU>
                    <FTREF/>
                     and, subsequently, certified NERC as the ERO.
                    <SU>5</SU>
                    <FTREF/>
                     On March 16, 2007, the Commission issued Order No. 693, approving 83 of the 107 Reliability Standards filed by NERC, including Reliability Standard TPL-002-0, Table 1, footnote ‘b.’ 
                    <SU>6</SU>
                    <FTREF/>
                     In addition, pursuant to section 215(d)(5) of the FPA,
                    <SU>7</SU>
                    <FTREF/>
                     the Commission directed NERC to develop modifications to 56 of the 83 approved Reliability Standards, including footnote ‘b’ of Reliability Standard TPL-002-0.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">Rules Concerning Certification of the Electric Reliability Organization; and Procedures for the Establishment, Approval and Enforcement of Electric Reliability Standards,</E>
                         Order No. 672, FERC Stats. &amp; Regs. ¶ 31,204, 
                        <E T="03">order on reh'g,</E>
                         Order No. 672-A, FERC Stats. &amp; Regs. ¶ 31,212 (2006).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">North American Electric Reliability Corp.,</E>
                         116 FERC ¶ 61,062, 
                        <E T="03">order on reh'g &amp; compliance,</E>
                         117 FERC ¶ 61,126 (2006), 
                        <E T="03">aff'd sub nom., Alcoa, Inc.</E>
                         v.
                        <E T="03"> FERC,</E>
                         564 F.3d 1342 (D.C. Cir. 2009).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">Mandatory Reliability Standards for the Bulk-Power System,</E>
                         Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242, 
                        <E T="03">order on reh'g,</E>
                         Order No. 693-A, 120 FERC ¶ 61,053 (2007).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         16 U.S.C. 824o(d)(5)(2006).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         Order No. 693, FERC Stats &amp; Regs. ¶ 31,242 at P 1797.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">A. Transmission Planning (TPL) Reliability Standards</HD>
                <P>
                    4. Currently-effective Reliability Standard TPL-002-0a addresses Bulk-Power System planning and related system performance for single element contingency conditions. Requirement R1 of TPL-002-0a requires that each Planning Authority and Transmission Planner “demonstrate through a valid assessment that its portion of the interconnected transmission system is planned such that the Network can be operated to supply projected customer demands and projected Firm Transmission Services, at all demand levels over the range of forecast system demands, under the contingency conditions as defined in Category B of Table I.” 
                    <SU>9</SU>
                    <FTREF/>
                     Table I identifies different categories of contingencies and allowable system impacts in the planning process. With regard to system impacts, Table I further provides that a Category B (single) contingency must not result in cascading outages, loss of demand or curtailed firm transfers, system instability or exceeded voltage or thermal limits. With regard to the clause regarding loss of demand, current footnote ‘b’ of Table 1 states:
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Reliability Standard TPL-002-0a, Requirement R1.
                    </P>
                </FTNT>
                <EXTRACT>
                    <P>Planned or controlled interruption of electric supply to radial customers or some local Network customers, connected to or supplied by the Faulted element or by the affected area, may occur in certain areas without impacting the overall reliability of the interconnected transmission systems. To prepare for the next contingency, system adjustments are permitted, including curtailments of contracted Firm (non-recallable reserved) electric power Transfers.</P>
                </EXTRACT>
                <HD SOURCE="HD2">B. Order No. 693 Directive</HD>
                <P>
                    5. In Order No. 693, the Commission stated that it believes that the transmission planning Reliability Standard should not allow an entity to plan for the loss of non-consequential firm load in the event of a single contingency.
                    <SU>10</SU>
                    <FTREF/>
                     The Commission directed the ERO to develop certain modifications, including a clarification of Table 1, footnote ‘b’. The Commission stated that:
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See</E>
                         Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at P 1794. Non-consequential load loss includes the removal, by any means, of any planned firm load that is not directly served by the elements that are removed from service as a result of the contingency. Currently-effective footnote ‘b’ deals with both consequential load loss and non-consequential load loss. NERC's proposed footnote ‘b’ characterizes both types of load loss as “Firm Demand.” The focus of this NOPR is NERC's proposed treatment of non-consequential load loss or planned interruption of “Firm Demand.”
                    </P>
                </FTNT>
                <EXTRACT>
                    <P>
                        Based on the record before us, we believe that the transmission planning Reliability Standard should not allow an entity to plan for the loss of non-consequential load in the event of a single contingency. The Commission directs the ERO to clarify the Reliability Standard. Regarding the comments of Entergy and Northern Indiana that the Reliability Standard should allow entities to plan for the loss of firm service for a single contingency, the Commission finds that their comments may be considered through the Reliability Standards development process. However, we strongly discourage an approach that reflects the lowest common denominator. The Commission also clarifies that an entity may seek a regional difference to the Reliability Standard from the ERO for case-specific circumstances.
                        <SU>11</SU>
                        <FTREF/>
                    </P>
                </EXTRACT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Order No. 693, FERC Stats. &amp; Regs. ¶ 31,242 at P 1794 (footnotes omitted).
                    </P>
                </FTNT>
                <PRTPAGE P="66231"/>
                <P>
                    6. In a subsequent clarifying order, the Commission stated that it believed that a regional difference, or a case-specific exception process that can be technically justified, to plan for the loss of firm service “at the fringes of various systems” would be an acceptable approach in limited circumstances.
                    <SU>12</SU>
                    <FTREF/>
                     Specifically, the Commission clarified that:
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">Mandatory Reliability Standards for the Bulk Power System,</E>
                         131 FERC ¶ 61,231, at P 21 (2010) (June 2010 Order).
                    </P>
                </FTNT>
                <EXTRACT>
                    <P>
                        Moreover, the Commission, in * * * Order No. 693, then provided a clarification that an entity may seek a regional difference to the Reliability Standard from the ERO for case-specific circumstances. We believe that a regional difference, or a case-specific exception process that can be technically justified, to plan for the loss of firm service “at the fringes of various systems” would be an acceptable approach. Thus, the Commission did not dictate a single solution as NERC and others now claim. In any event, NERC must provide a strong technical justification for its proposal.
                        <SU>13</SU>
                        <FTREF/>
                    </P>
                </EXTRACT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. NERC's Petition for Approval of TPL-002-0a, Footnote b</HD>
                <P>
                    7. On March 31, 2011, NERC filed a petition seeking approval of its proposal to revise and clarify footnote ‘b’ “in regard to load loss following a single contingency.” 
                    <SU>14</SU>
                    <FTREF/>
                     NERC stated that it did not eliminate the ability of an entity to plan for the loss of non-consequential load in the event of a single contingency but drafted a footnote that, according to NERC, “meets the Commission's directive while simultaneously meeting the needs of industry and respecting jurisdictional bounds.” 
                    <SU>15</SU>
                    <FTREF/>
                     NERC states that its proposed footnote ‘b’ establishes the requirements for the limited circumstances when and how an entity can plan to interrupt Firm Demand for Category B contingencies. It allows for planned interruption of Firm Demand when “subject to review in an open and transparent stakeholder process.” 
                    <SU>16</SU>
                    <FTREF/>
                     NERC's proposed footnote ‘b’ states:
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         NERC Petition at 10.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <EXTRACT>
                    <P>An objective of the planning process should be to minimize the likelihood and magnitude of interruption of firm transfers or Firm Demand following Contingency events. Curtailment of firm transfers is allowed when achieved through the appropriate redispatch of resources obligated to re-dispatch, where it can be demonstrated that Facilities, internal and external to the Transmission Planner's planning region, remain within applicable Facility Ratings and the re-dispatch does not result in the shedding of any Firm Demand. It is recognized that Firm Demand will be interrupted if it is: (1) Directly served by the Elements removed from service as a result of the Contingency, or (2) Interruptible Demand or Demand-Side Management Load. Furthermore, in limited circumstances Firm Demand may need to be interrupted to address BES performance requirements. When interruption of Firm Demand is utilized within the planning process to address [Bulk Electric System] performance requirements, such interruption is limited to circumstances where the use of Demand interruption are documented, including alternatives evaluated; and where the Demand interruption is subject to review in an open and transparent stakeholder process that includes addressing stakeholder comments.</P>
                </EXTRACT>
                <HD SOURCE="HD2">D. Supplemental Information</HD>
                <P>
                    8. On June 7, 2011, in response to a Commission deficiency letter, NERC explained that “the approach proposed in footnote ‘b’ is equally efficient because many of the stakeholder processes that will be used in footnote ‘b’ planning decisions are already in place, as implemented by FERC in Order No. 890 and in state regulatory jurisdictions.” 
                    <SU>17</SU>
                    <FTREF/>
                     NERC also pointed to state public utility commission processes or processes existing in local jurisdictions that address transmission planning issues that could serve to provide a case-specific review of the planned interruption of Firm Demand. NERC added that an ERO-sponsored planning process is not likely to be efficient or effective because of extensive jurisdictional issues between NERC, the Commission, and the many authorities having jurisdiction that would have to be resolved before implementation could occur. NERC added that an ERO-specific process would lead to conflicts among federal, provincial, state and local governing bodies that have jurisdiction over various parts of the planning, siting and construction process. NERC also believes that a NERC-centered process would duplicate planning actions occurring elsewhere (
                    <E T="03">e.g.,</E>
                     where resource allocation decisions are actually being made), and such a process could lead to inconsistent results. NERC concluded that a more reasonable and expeditious path would be to rely on existing stakeholder processes. According to NERC, such processes would more likely engage the appropriate local-level decision-makers and policy-makers.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         NERC Data Response at 4.
                    </P>
                </FTNT>
                <P>9. With respect to review and oversight by NERC and the Regional Entities, NERC submitted that an ERO-specific process would place the ERO in the position of managing and actively participating in a planning process, which conflicts with its role as the compliance monitor and enforcement authority. NERC also stated that neither the ERO nor the Regional Entities will review decisions regarding planned interruptions. Their role will be limited to reviewing whether the registered entity participated in a stakeholder process when planning to interrupt Firm Demand. NERC explained that Regional Entities will have oversight after-the-fact by auditing the entity's implementation of footnote ‘b’ to determine if the entity planned on interrupting Firm Demand and whether the decision by the entity to rely on planned interruption of Firm Demand was vetted through the stakeholder process and qualified as one of the situations identified in footnote b.</P>
                <P>10. Furthermore, NERC stated that an objective of the planning process should be to minimize the likelihood and magnitude of planned Firm Demand interruptions. NERC recognizes that there may be topological or system configurations where allowing planned interruptions of Firm Demand may provide more reliable service. NERC contends that due to the wide variety of system configurations and regulatory compacts, it is not feasible for the ERO to develop a one-size-fits-all criterion for limiting the planned firm load interruptions for Category B events. According to NERC, the standards drafting team evaluated setting a certain magnitude of planned interruption of Firm Demand, but there was no analytical data to support a single value, and it would be viewed as arbitrary.</P>
                <HD SOURCE="HD1">II. Discussion</HD>
                <P>
                    11. The Commission proposes to remand NERC's proposal to modify Reliability Standard TPL-002-0a, Table 1, footnote ‘b.’ The Commission believes that NERC's proposal does not meet the directives in Order No. 693 and the June 2010 Order and does not clarify or define the circumstances in which an entity can plan to interrupt Firm Demand for a single contingency. Specifically, the Commission is concerned that the procedural and substantive parameters of NERC's proposed stakeholder process are too undefined to provide assurances that the process will be effective in determining when it is appropriate to plan for interrupting Firm Demand, does not contain NERC-defined criteria on circumstances to determine when an exception for planned interruption of Firm Demand is permissible, and could result in inconsistent results in implementation. In proposing a stakeholder process without specification of any technical means by which exceptions are to be evaluated, 
                    <PRTPAGE P="66232"/>
                    the proposed footnote effectively turns the processes into a reliability standards development process outside of NERC's existing procedures. Furthermore, the Commission believes that regardless of the process used, the result could lead to inconsistent reliability requirements within and across reliability regions. While the Commission recognizes that some variation among regions or entities is reasonable given varying grid topography and other legitimate considerations, there are no technical or other criteria to determine whether varied results are arbitrary or based on meaningful distinctions. While the Commission acknowledges that NERC has flexibility in developing alternative approaches, we believe that the proposed approach is not equally efficient or effective as the Commission's directives and that NERC has failed to provide a strong technical justification for its proposal.
                </P>
                <P>
                    12. As an initial matter, the Commission is concerned that the process lacks parameters. The standard requires that, when planning to interrupt Firm Demand, the Firm Demand interruption must be “subject to review in an open and transparent stakeholder process that includes addressing stakeholder comments.” 
                    <SU>18</SU>
                    <FTREF/>
                     However, without any substantive parameters governing the stakeholder process, the enforceability of this obligation by NERC and the Regional Entities' would be limited to a review to ensure only that a stakeholder process occurred. Indeed, NERC's explanation appears to confirm this concern, as NERC explained that Regional Entities' involvement is limited to oversight after-the-fact by auditing the entity's implementation of footnote ‘b’ to determine if the entity planned on interrupting Firm Demand and whether the decision by the entity to rely on planned interruption of Firm Demand was vetted through the stakeholder process and qualified as one of the situations identified in footnote ‘b’.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         NERC Petition at 10.
                    </P>
                </FTNT>
                <P>
                    13. Further, the Commission is concerned that the NERC proposal leaves undefined the circumstances in which it is allowable to plan for Firm Demand to be interrupted in response to a Category B contingency. The TPL-002-0a Reliability Standard requires Planning Authorities and Transmission Planners to demonstrate through a valid assessment that the transmission system is planned and can be operated to supply projected Firm Demand at all demand levels over a range of forecasted system demands.
                    <SU>19</SU>
                    <FTREF/>
                     Moreover, the planner must consider all single contingencies applicable to Table I, Category B and demonstrate that system performance is met. For those instances where system performance is not met, the planner must provide a written summary of its plans to achieve system performance including implementation schedules, in service dates of facilities and implementation lead times.
                    <SU>20</SU>
                    <FTREF/>
                     In regard to NERC's proposal, the Commission is concerned that footnote ‘b’ would function as a means to override the reliability objective and system performance requirements of the TPL Reliability Standard without any technical or other criteria specified to determine when planning to interrupt Firm Demand would be allowable. In this case NERC has provided no technically sound means of determining situations in which planning to interrupt Firm Demand would be allowable, and instead has removed such decision-making to an unspecified stakeholder process without any assurance that such processes will deploy technically sound means of approving or denying exceptions. Without any technical or other criteria specified to determine when planning to interrupt Firm Demand would be allowable, the Commission is concerned that multiple stakeholder processes across the country engaging in such determinations could lead to inconsistent and arbitrary exceptions including, potentially, allowing entities to plan to interrupt any amount of Firm Demand in any location and at any voltage level. While the Commission recognizes that some variation among regions or entities is reasonable given varying grid topography and other legitimate considerations, there are no technical or other criteria to determine whether varied results are arbitrary or based on meaningful distinctions. The Commission is thus concerned that there may be a lack of consistency in determinations to allow the planned interruption of Firm Demand. The proposed stakeholder process does not have any parameters except for openness and transparency. As a result, multiple processes that could be adopted across the country would likely lead to inconsistent determinations to allow for the planned interruption of Firm Demand.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         Reliability Standard TPL-002-0a, Requirement R1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         Reliability Standard TPL-002-0a, Requirements R1.5 and R2.
                    </P>
                </FTNT>
                <P>14. The Commission believes that a remand would give NERC and industry flexibility to develop an approach that would address the issues identified by the Commission with the proposed footnote `b' stakeholder process including, as discussed below, definition of the process and criteria or guidelines for the process.</P>
                <HD SOURCE="HD2">A. Lack of Technical or Other Criteria</HD>
                <P>
                    15. NERC's proposal does not prescribe the criteria that would define the parameters of permissible interruption of Firm Demand. In Order No. 693 the Commission expressed concern that, as a general rule, footnote `b' should not allow an entity to plan for the loss of non-consequential load in the event of a single contingency and directed NERC to clarify the standard. The Commission stated in the June 2010 Order that a regional difference or a case-specific exception process that could be technically justified would be acceptable. While the Commission allows NERC to propose an equally effective and efficient solution to a Commission's proposed solution, the Commission does not believe that the proposal is equally effective and efficient. First, NERC's proposed footnote `b' contains no constraints and could allow an entity to plan to interrupt any amount of Firm Demand, in any location or at any voltage level as needed for any single contingency, provided that it is documented and subjected to a stakeholder process. This result is contrary to the underlying standard and our prior orders.
                    <SU>21</SU>
                    <FTREF/>
                     Further, NERC did not technically justify its proposal, instead relying on the benefit of having transparency in the process. The Commission does not believe transparency in this instance can substitute for a technical justification.
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See</E>
                         Order No. 693, 
                        <E T="03">see also</E>
                         June 2010 Order.
                    </P>
                </FTNT>
                <P>
                    16. In its supplemental filing, NERC states that it is not feasible for the ERO to develop a one-size-fits-all criterion for limiting the planned interruption of Firm Demand due to the wide variety of system configurations and regulatory compacts.
                    <SU>22</SU>
                    <FTREF/>
                     NERC states that the standards drafting team believes there is no analytical data to support a single level and therefore any single value was viewed as arbitrary.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         NERC Data Response at 6.
                    </P>
                </FTNT>
                <P>
                    17. We are not persuaded by NERC's reasoning. First, both NERC and the Commission have developed thresholds in other reliability contexts that have overcome similar claims of arbitrariness. For example, the threshold for conducting vegetation management pursuant to Reliability Standard FAC-003-1 applies to all transmission lines operated at 200 kV and above.
                    <SU>23</SU>
                    <FTREF/>
                     In the 
                    <PRTPAGE P="66233"/>
                    same vein, NERC's Statement of Compliance Registry Criteria has numerous thresholds for determining eligibility for registration.
                    <SU>24</SU>
                    <FTREF/>
                     The Commission did not suggest a one size fits all exceptions process. If the ERO were to perform an exception process, it might include flexibility in decisions based on disparate topology or on other matters since it could utilize its technical expertise to determine the reliability impact from one region to another. Moreover, the Commission's proposal to remand revised footnote `b' due to a lack of criteria does not preclude NERC from developing another alternative, provided that it is equally “efficient and effective.”
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         Reliability Standard FAC-003-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">See, e.g.,</E>
                         NERC Statement of Registry Criteria, Section III. The Commission approved Statement of Registry Criteria in Order No. 693.
                    </P>
                </FTNT>
                <P>
                    18. Finally, the Commission understands that there are a wide variety of system configurations and regulatory compacts. NERC indicates that the standards drafting team considered a variety of limits; however, it is not clear whether NERC considered a blend of quantitative and qualitative thresholds. For example, a standard could require a process with a quantitative limitation on how much Firm Demand could be planned for interruption and that standard could provide an exception process where a registered entity would submit documents and explanation to the ERO or a Regional Entity for approval based upon certain considerations.
                    <SU>25</SU>
                    <FTREF/>
                     In short, we believe that a more defined process would be needed but, by itself, would not be adequate without NERC-defined technical or other criteria to determine planned interruption of Firm Demand. The Commission seeks comment on these proposals.
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         While we encourage NERC to exercise flexibility in designing an appropriate standard, under this example, the exception process could consist of a stakeholder process that has some level of due process as long as that process does not allow the entity that proposes its exception to make the decision on whether to grant the exception.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Stakeholder Process</HD>
                <P>19. The Commission believes that NERC's proposed footnote `b' stakeholder process does not meet Order No. 693 and the June 2010 Order directive. According to NERC, the type of stakeholder process used under its proposed footnote `b' can vary from one planning entity to the next. NERC offers several stakeholder processes as examples, such as the Order 890-type process, a state public utility commission or local jurisdiction process, or a Regional Transmission Organization/Independent System Operator (RTO/ISO) stakeholder process.</P>
                <P>20. First, because NERC's proposed footnote `b' does not define the stakeholder process, the express terms of the standard would allow an applicable entity to form or participate in any stakeholder process and be compliant with the proposed standard. Second, as we have mentioned, NERC has offered no technical justification for exceptions to be granted through the stakeholder process and therefore no means for the Commission to judge whether the process will protect the reliability of the Bulk-Power System. Nothing in the proposed footnote `b' restricts the stakeholder process, other than that it must be an open and transparent stakeholder process that includes addressing stakeholder comments. The Commission is concerned that any meeting that is open to stakeholders could meet this standard. Further, because the stakeholder process is not defined, the proposal could allow a transmission planner to develop a process that provides insufficient process and transparency and still comply with the standard. The Commission believes that such process would be insufficient because it allows any stakeholder process to essentially become a reliability standards development processes outside of NERC's existing procedures. Furthermore, the Commission believes that regardless of the stakeholder process used, the outcome could lead to inconsistent results, with no technical or other criteria to determine whether varied results are arbitrary or based on meaningful distinctions. The Commission seeks comment on whether a stakeholder process is the appropriate vehicle to approve or deny exceptions to allow entities to plan to interrupt Firm Demand for a single contingency and if so, whether the proposed footnote `b' would require any stakeholder due process.</P>
                <P>21. Nor does the standard describe what would be entailed in addressing the stakeholder comments. As described above, the process under the standard does not provide for any technical rigor to address stakeholder concerns. While the standard requires transparency and an opportunity for stakeholder comments on the transmission planner's proposed plan to interrupt Firm Demand, it does not mandate any particular stakeholder involvement, nor does it mandate that interested governmental authorities be afforded notice and an opportunity to comment. As we read the proposed standard, a responsible entity could define when it would plan to interrupt Firm Demand on its own, then ask for stakeholder input on that plan. While the standard requires the responsible entity to “address” stakeholder comments, the responsible entity is not required to specify or support the technical basis upon which it rendered a decision. The Commission believes that the stakeholder process in proposed footnote `b' would allow the transmission planner to define the circumstances when it would rely on planned interruption of Firm Demand, provide that definition for review by regulators and other stakeholders, receive comments from regulators and stakeholders requesting a more narrow definition, and explain to the regulators and stakeholders why it is declining the request and maintaining the broader definition, even if every other transmission planner facing similar circumstances would reach the opposite conclusion.</P>
                <P>
                    22. In Order No. 693 and the June 2010 Order, the Commission stated that a regional difference or a case-specific exception process, among other things, would be an acceptable approach. With regard to a case-specific process, NERC replied it would “create undesirable delays and uncertainty in the transmission planning process.” 
                    <SU>26</SU>
                    <FTREF/>
                     However, the proposed footnote `b' does not provide a time limitation by which planning decisions to interrupt Firm Demand must be made. The Commission is not persuaded that NERC's proposed approach ameliorates this concern. The Commission seeks comment on whether an exceptions process that provides defined criteria, with some allowance or consideration for unique circumstances, could be crafted that would resolve NERC's concerns of “undesirable delays” and “uncertainty.”
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         NERC Data Response at 2.
                    </P>
                </FTNT>
                <P>
                    23. In sum, the Commission is concerned that the stakeholder process set forth in the NERC proposal is not sufficiently defined, rendering it potentially unenforceable. As mentioned above, the proposed stakeholder process includes no parameters other than openness and transparency. NERC states that it and the Regional Entities will review a responsible entity's decision to plan to interrupt Firm Demand using an after-the-fact audit, to determine if the entity's implementation of footnote `b' to plan Firm Demand interruption and whether the decision by the entity was vetted through the stakeholder process and qualified as one of the situations 
                    <PRTPAGE P="66234"/>
                    identified in footnote `b.' 
                    <SU>27</SU>
                    <FTREF/>
                     The Commission believes that this could result in a transmission planner invoking a process that provides for minimal stakeholder involvement, providing scant reasons to reject any stakeholder input and then defending its decision by claiming that it has satisfied the provision. While the Compliance Enforcement Authority would verify that the process fulfilled the letter of NERC's proposed footnote `b'—that some open, transparent stakeholder process was involved and that the responsible entity in some way addressed stakeholder concerns—there is no mechanism for the ERO or a Regional Entity to enforce a finding that the evidence does not support an acceptable instance of planned interruption of Firm Demand. The Commission seeks comment on the concerns raised above.
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         NERC Data Response at 7-8.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Commission Proposal</HD>
                <P>24. The Commission believes that NERC's proposed footnote `b' does not meet the Commission's Order No. 693 directives, nor is it an equally effective and efficient alternative. On this basis, the Commission proposes to remand the proposal to NERC.</P>
                <P>
                    25. The Commission also proposes to provide further guidance on acceptable approaches to footnote `b'. We seek comment on all of the options below. In addition, while the Commission is proposing certain options for revising footnote `b', we also seek comment on other potential options to solve the concerns outlined in this NOPR. As noted above, the Commission understands that there are a wide variety of system configurations and regulatory compacts. We believe that a more defined process than that provided in the proposed footnote `b' would be needed but, by itself, would not be adequate without NERC-defined technical or other criteria to determine an acceptable planned interruption of Firm Demand at the fringes of the system.
                    <SU>28</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         Any exceptions process to determine specific requests for planned interruption of Firm Demand may not necessarily be limited to the fringes of the system.
                    </P>
                </FTNT>
                <P>26. We acknowledge that the standards drafting team considered a variety of limits; however, setting some form of criteria within the standard itself for planning to interrupt Firm Demand may be an acceptable approach to setting criteria for footnote `b' and would be an option for NERC to consider. We also seek comment on whether existing protocols could provide guidance to NERC in devising criteria. For example, the Department of Energy's Electric Emergency Incident and Disturbance Report (Form OE-417) requires, among other things, an entity to report the uncontrolled loss of 300 Megawatts or more of firm system loads for more than 15 minutes from a single incident, load shedding of 100 Megawatts or more implemented under emergency operational policy, and the loss of service for more than 1 hour to 50,000 customers. While these are reporting requirements for the operational timeframe, and may include distribution level load shedding, the Commission requests comments on whether they could also serve as a basis for setting limits on when an entity can plan to interrupt Firm Demand on the Bulk-Power System. Another existing document that could provide guidance on how to set a limit on the planned interruption of Firm Demand is NERC's Statement of Compliance Registry Criteria, which uses, for example, 25 MW as a threshold in determining when a load-serving entity or distribution provider should register with NERC. We seek comments on this proposed option, and any other external documents that could be used to guide a revision to footnote `b.'</P>
                <P>27. Second, as stated above, it is not clear whether NERC considered a blend of quantitative and qualitative thresholds. The Commission seeks comments on whether this would be an option for providing criteria that would be generally applicable, but also for allowing for certain cases that may exceed the criteria. For example, a standard could require a process with a quantitative limitation on how much Firm Demand could be planned for interruption and that standard could provide an exception process where a registered entity would submit documents and explanation to the ERO or a Regional Entity for approval based upon certain considerations. NERC has raised concerns about conflicts among federal, provincial, state and local governing bodies that have jurisdiction over various parts of the planning, siting and construction process. The Commission believes that this approach may satisfy the need for technical criteria that we have described, while accounting for NERC's concerns about the difficulty of developing a one-size-fits-all criterion for limiting planned Firm Demand interruptions and the appropriateness and feasibility of managing and actively participating in each planning process. As NERC states, the objective of footnote `b' should be to minimize the likelihood and magnitude of planned Firm Demand interruptions. The Commission believes that setting generally applicable criteria for when an applicable entity can plan to shed Firm Demand, coupled with an exceptions process overseen by NERC and the Regional Entities, could mean that few exception requests must be processed by NERC and the Regional Entities. We seek comment on this option, and which entities should be involved in the review and subsequent determination as to whether an exception should be allowed.</P>
                <P>28. NERC has raised concerns about conflicts among federal, provincial, state and local governing bodies that have jurisdiction over various parts of the planning, siting and construction process. There also may be concerns about the costs of planning to avoid Firm Demand shedding. The Commission seeks comment on whether a feasible option would be to revise footnote `b' to allow for the planned interruption of Firm Demand in circumstances where the transmission planner can show that it has customer or community consent and there is no adverse impact to the Bulk-Power System. This presumably would not require affirmative consent by every individual retail customer, but we recognize that either term, customer or community, would need to be adequately defined. The Commission therefore seeks comments on who might be able to represent the customer or community in this option and how customer or community consent might be demonstrated. Additionally, we seek comment on how it would be determined that firm demand shedding with customer consent would not adversely impact the Bulk-Power System. However, we also seek comment on whether a customer who would otherwise consent to having its planning authority or transmission planner plan to interrupt Firm Demand pursuant to this option could instead select interruptible or conditional firm service under the tariff to address cost concerns.</P>
                <P>
                    29. Finally, regardless of how NERC revises footnote `b' to resolve the concerns outlined in this NOPR and in previous orders, the Commission notes that NERC will need to support the revision to footnote `b.' If there is a threshold component to the revised footnote, the Commission believes that NERC would need to support the threshold and show that instability, uncontrolled separation, or cascading failures of the system will not occur as a result of planning to shed Firm Demand up to the threshold. In addition, if there is an individual exception option, the Commission 
                    <PRTPAGE P="66235"/>
                    believes that the applicable entities should be required to find that there is no adverse impact to the Bulk-Power System from the exception and that it is considered in wide-area coordination and operations. Further, we believe that any exception should be subject to further review by the Regional Entity, NERC, and the Commission. This does not necessarily mean that the Regional Entity, NERC, or the Commission should have to approve the exception, but that any of the three could later audit its implementation.
                </P>
                <P>30. In conclusion, while the Commission provides three options for revising footnote `b' in this Notice of Proposed Rulemaking, we seek comments on the feasibility of the options and on ways in which the options might be improved. In addition, we seek comment on whether there are other ways for NERC to solve the concerns outlined above in an equally effective and efficient manner.</P>
                <HD SOURCE="HD1">III. Information Collection Statement</HD>
                <P>
                    31. The Office of Management and Budget (OMB) regulations require that OMB approve certain reporting and recordkeeping (collections of information) imposed by an agency.
                    <SU>29</SU>
                    <FTREF/>
                     The information contained here is also subject to review under section 3507(d) of the Paperwork Reduction Act of 1995.
                    <SU>30</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         5 CFR 1320.11.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         44 U.S.C. 3507(d).
                    </P>
                </FTNT>
                <P>32. As stated above, the subject of this NOPR is NERC's proposed modification to Table 1, footnote `b' applicable in four TPL Reliability Standards. This NOPR proposes to remand the footnote `b' modification to NERC. By remanding footnote `b' the applicable Reliability Standards and any information collection requirements are unchanged. Therefore, the Commission will submit this NOPR to OMB for informational purposes only.</P>
                <P>
                    33. Interested persons may obtain information on the reporting requirements by contacting the following: Federal Energy Regulatory Commission, 888 First Street, NE. Washington, DC 20426 [
                    <E T="03">Attention:</E>
                     Ellen Brown, Office of the Executive Director, 
                    <E T="03">e-mail: data.clearance@ferc.gov, phone:</E>
                     (202) 502-8663, or 
                    <E T="03">fax:</E>
                     (202) 273-0873].
                </P>
                <HD SOURCE="HD1">IV. Regulatory Flexibility Act</HD>
                <P>
                    34. The Regulatory Flexibility Act of 1980 (RFA) 
                    <SU>31</SU>
                    <FTREF/>
                     generally requires a description and analysis of final rules that will have significant economic impact on a substantial number of small entities. The RFA mandates consideration of regulatory alternatives that accomplish the stated objectives of a proposed rule and that minimize any significant economic impact on a substantial number of small entities. The Small Business Administration's (SBA) Office of Size Standards develops the numerical definition of a small business.
                    <SU>32</SU>
                    <FTREF/>
                     The SBA has established a size standard for electric utilities, stating that a firm is small if, including its affiliates, it is primarily engaged in the transmission, generation and/or distribution of electric energy for sale and its total electric output for the preceding twelve months did not exceed four million megawatt hours.
                    <SU>33</SU>
                    <FTREF/>
                     The RFA is not implicated by this NOPR because the Commission is remanding footnote' b' and not proposing any modifications to the existing burden or reporting requirements. With no changes to the Reliability Standards as approved, the Commission certifies that this NOPR will not have a significant economic impact on a substantial number of small entities.
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         5 U.S.C. 601-612.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         13 CFR 121.201.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         
                        <E T="03">Id.</E>
                         n.22.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">V. Comment Procedures</HD>
                <P>
                    35. The Commission invites interested persons to submit comments on the matters and issues proposed in this notice to be adopted, including any related matters or alternative proposals that commenters may wish to discuss. Comments are due 60 days from publication in the 
                    <E T="04">Federal Register</E>
                    . Comments must refer to Docket No. RM11-18-000, and must include the commenter's name, the organization they represent, if applicable, and their address in their comments.
                </P>
                <P>
                    36. The Commission encourages comments to be filed electronically via the eFiling link on the Commission's Web site at 
                    <E T="03">http://www.ferc.gov.</E>
                     The Commission accepts most standard word processing formats. Documents created electronically using word processing software should be filed in native applications or print-to-PDF format and not in a scanned format. Commenters filing electronically do not need to make a paper filing.
                </P>
                <P>37. Commenters that are not able to file comments electronically must send an original of their comments to: Federal Energy Regulatory Commission, Secretary of the Commission, 888 First Street, NE., Washington, DC 20426.</P>
                <P>38. All comments will be placed in the Commission's public files and may be viewed, printed, or downloaded remotely as described in the Document Availability section below. Commenters on this proposal are not required to serve copies of their comments on other commenters.</P>
                <HD SOURCE="HD1">VI. Document Availability</HD>
                <P>
                    39. In addition to publishing the full text of this document in the 
                    <E T="04">Federal Register</E>
                    , the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the Internet through FERC's Home Page (
                    <E T="03">http://www.ferc.gov</E>
                    ) and in FERC's Public Reference Room during normal business hours (8:30 a.m. to 5 p.m. Eastern time) at 888 First Street, NE., Room 2A, Washington, DC 20426.
                </P>
                <P>40. From FERC's Home Page on the Internet, this information is available on eLibrary. The full text of this document is available on eLibrary in PDF and Microsoft Word format for viewing, printing, and/or downloading. To access this document in eLibrary, type the docket number excluding the last three digits of this document in the docket number field.</P>
                <P>
                    41. User assistance is available for eLibrary and the FERC's Web site during normal business hours from FERC Online Support at (202) 502-6652 (toll free at 1-866-208-3676) or e-mail at 
                    <E T="03">ferconlinesupport@ferc.gov,</E>
                     or the Public Reference Room at (202) 502-8371, TTY (202) 502-8659. E-mail the Public Reference Room at 
                    <E T="03">public.referenceroom@ferc.gov.</E>
                </P>
                <SIG>
                    <P>By direction of the Commission. Commissioner Spitzer is not participating.</P>
                    <NAME>Nathaniel J. Davis, Sr.,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27624 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <CFR>21 CFR Parts 201 and 610</CFR>
                <DEPDOC>[Docket No. FDA-2011-N-0719]</DEPDOC>
                <SUBJECT>Bar Code Technologies for Drugs and Biological Products; Retrospective Review Under Executive Order 13563; Request for Comments</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Food and Drug Administration (FDA) is announcing a review of the “Bar Code Final Rule,” under Executive Order 13563, “Improving Regulation and Regulatory Review.” The Bar Code Final Rule, which was published in 2004, requires 
                        <PRTPAGE P="66236"/>
                        certain human drug products and biological products to have a bar code. Information submitted can help FDA to reassess the costs and benefits of the rule and to identify any relevant changes in technology that have occurred since it went into effect. FDA is establishing a public docket to receive information relevant to reassessing the Bar Code Rule. This is an opportunity for interested persons to share information, research, and ideas on the need, maturity, and acceptability of alternative identification technologies for the identification, including the unique identification, of drugs and biological products. FDA will use the information received to assess whether the Bar Code Final Rule is achieving its intended benefits as effectively as possible or should be modified.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>FDA will accept both initial comments and reply comments in response to this notice. Initial comments must be received on or before January 9, 2012 and reply comments on or before February 23, 2012. (See the “Comments” section of this document for more information.)</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit electronic comments to 
                        <E T="03">http://www.regulations.gov.</E>
                         Submit written comments to the Division of Dockets Management (HFA-305), Food and Drug Administration, 5630 Fishers Lane, rm. 1061, Rockville, MD 20852. All comments should be identified with the docket number found in brackets in the heading of this document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Benjamin A. Chacko, Center for Biologics Evaluation and Research (HFM-17), Food and Drug Administration, 1401 Rockville Pike, suite 200N, Rockville, MD 20852-1448, 301-827-6210.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On February 2, 2011, President Barack Obama issued Executive Order (E.O.) 13563, “Improving Regulation and Regulatory Review” (76 FR 3821). One of the provisions in the new Executive order is the affirmation of retrospective reviews of existing significant regulations. As one step in implementing the new Executive order, FDA published a notice in the 
                    <E T="04">Federal Register</E>
                     on April 27, 2011 (76 FR 23520), entitled “Periodic Review of Existing Regulations; Retrospective Review Under E.O. 13563.” In that document, FDA announced that it is conducting a review of its existing regulations to determine, in part, whether they can be made more effective in light of current public health needs and to take advantage of and support advances in innovation that have occurred since those regulations took effect. Under E.O. 13563, and under the Department of Health and Human Services' 
                    <E T="03">Plan for Retrospective Review of Existing Rules,</E>
                     FDA will consider strengthening, complementing, or modernizing rules where necessary or appropriate.
                </P>
                <P>
                    As FDA conducts its retrospective review of regulations, the Agency will take into account the following factors: 
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Department of Health and Human Services, “
                        <E T="03">Plan for Retrospective Review of Existing Rules,</E>
                        ” pp. 21-22 (August 22, 2011).
                    </P>
                </FTNT>
                <P>• Whether an action will have a positive impact on innovation in an area of public health, safety, or delivery of or access to care;</P>
                <P>• Whether the public health benefits of an action have been realized;</P>
                <P>• Whether the public or regulated community view modification or revocation of a regulation as important and have offered useful comments and suggestions for change;</P>
                <P>• Whether the impact and effectiveness of a regulation has changed or been superseded by changes in conditions or advances in scientific or technological information;</P>
                <P>• Whether there are significant, unresolved issues with implementation or enforcement; and</P>
                <P>• How long the regulation has been in effect and whether it has been subject to prior reviews.</P>
                <P>The first rule FDA is reviewing under E.O. 13563 is the Bar Code Final Rule. The Agency plans to reassess its costs and benefits and to determine if the Bar Code Final Rule should be modified to take into account changes in technology that have occurred since the rule went into effect in 2004.</P>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of March 14, 2003 (68 FR 12500), FDA published a proposed rule (Bar Code Proposed Rule) that would require certain human drug product labels and biological product labels to have a linear bar code that would contain, at a minimum, the drug's National Drug Code (NDC) number. In the 
                    <E T="04">Federal Register</E>
                     of February 26, 2004 (69 FR 9120), the Agency finalized the proposed rule (§§ 201.25 and 610.67 (21 CFR 201.25 and 610.67)). As discussed in the preamble to the Bar Code Proposed Rule, the rule was intended to help reduce the number of medication errors that occur in hospitals and other health care settings (68 FR 12500 at 12501 through 12502). FDA envisioned that bar codes would be part of a system, along with bar code scanners and computerized databases, that would enable health care professionals to check whether they are giving the right drug (in the right dose and via the right route of administration) to the right patient at the right time (
                    <E T="03">Id.</E>
                     at 12501).
                </P>
                <P>The events that led FDA to propose requiring bar codes are described in the preamble to the Bar Code Proposed Rule. In brief, medication errors are known to be a serious public health problem and can occur at several points from the time a health care provider prescribes the drug to a patient to the time when the patient receives the drug. The use of bar codes on drug products was expected to significantly reduce medication errors. Bar codes also can complement other efforts to reduce medication errors, such as computer physician order entry (CPOE) systems (where a physician enters orders electronically into a computer instead of writing the order on paper, and subsequently the order can be checked against the patient's electronic records for possible drug interactions, overdoses, and patient allergies) and retail pharmacy-based computer systems that use a bar-coded NDC number to verify that a consumer's prescription is being dispensed with the correct drug. FDA refers readers to the preamble to the Bar Code Proposed Rule should they wish to obtain details on the events, recommendations, meetings, and literature that shaped the proposed rule.</P>
                <P>
                    In the preamble to the Bar Code Proposed Rule, the Agency discussed in detail the challenge of requiring the use of linear bar codes, which, while enabling hospitals to buy scanning equipment with the confidence that their purchased equipment would not be rendered obsolete by new technology, could affect future technological innovation (68 FR 12500 at 12508 through 12510). Comments received related to a public meeting on bar coding, presented an array of differing opinions on the issue of whether to require a specific technology (68 FR 12500 at 12508). Given the complexity of the issues, FDA requested in the Bar Code Proposed Rule comment concerning alternatives that could replace or be used in conjunction with the linear bar code such as another symbol, standard, or technology (
                    <E T="03">Id.</E>
                     at 12510 and 12529).
                </P>
                <P>
                    In response to the Bar Code Proposed Rule, FDA received comments including those opposing the use of linear bar codes or asking the Agency to consider other technologies or to eliminate any reference to linear bar codes in the final rule. Such comments primarily argued that selecting a symbology or standard would inhibit technological innovation. 
                    <PRTPAGE P="66237"/>
                    Comments opposed to a linear bar code requirement generally advocated the following alternatives: (1) Two-dimensional symbologies, (2) the European Article Number/Uniform Code Council (EAN/UCC) system generally, (3) radio frequency identification (RFID) chips, or (4) no standard or symbology at all (69 FR 9120 at 9136).
                </P>
                <P>Ultimately, FDA determined that, based on data and public comment, a linear bar code requirement was appropriate (Id. at 9137 through 9138). In the preamble to the Bar Code Final Rule, the Agency addressed comments concerning alternatives to the linear bar code and stated that, while it believed that linear bar codes were an established, cost-effective, widely used and easily recognized technology, it also acknowledged that linear bar codes have several disadvantages. For example, linear bar codes may take up more label space than alternative technologies and may encode less data compared to other technologies. Thus, if more data need to be encoded on the packaging or labeling for any other reason (such as to allow tracking and tracing of drug products through the drug distribution system), a linear bar code might prove too limiting (Id. at 9137). FDA also stated that, although it had decided to preserve the linear bar code requirement, it would consider revising the rule to accommodate newer technologies as they become more mature and established (Id. at 9137 through 9138).</P>
                <P>
                    Since FDA issued the Bar Code Final Rule, advances in alternative technologies have occurred. In addition, it has become increasingly clear from industry, health care providers, and other FDA initiatives, that certain FDA-regulated products present unique bar coding concerns. For example, the Agency has since learned that certain vaccines present unique challenges in the bar coding context, particularly with respect to compliance with recordkeeping and mandatory adverse event reporting requirements that are specific to the administration of childhood vaccines.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The National Childhood Vaccine Injury Act of 1986 (Pub. L. 99-660) (42 U.S.C. 300aa-25(a)) requires health care providers to report certain adverse events related to identified childhood vaccines to the Vaccine Adverse Event Reporting System (42 U.S.C. 300aa-25(b)). Although health care providers are encouraged to report adverse events related to other drugs and biological products to FDA, they are not required to do so.
                    </P>
                </FTNT>
                <P>
                    In recognition of these challenges, in the 
                    <E T="04">Federal Register</E>
                     of August 11, 2011 (76 FR 49772), FDA announced the availability of a final guidance document entitled “Guidance for Industry: Bar Code Label Requirements—Questions and Answers” 
                    <SU>3</SU>
                    <FTREF/>
                    . This guidance amended and superseded the final guidance of the same title dated October 2006, by incorporating a revised response to question 12 (Q12), which pertains to the use of alternate coding technologies for vaccines. The Agency explained in the 
                    <E T="04">Federal Register</E>
                     notice announcing the final guidance that it believes alternative technology such as two-dimensional symbology has advanced, allowing the Agency to reconsider the use of such technology. Accordingly, it will now consider requests from vaccine manufacturers who request to use alternate coding technologies, such as two-dimensional symbology, that encode lot number and expiration date information, for an exemption under § 201.25(d)(1)(ii) to the linear bar code requirement. FDA limited the scope of its revised response to Q12 to vaccines because of the mandatory reporting concerns specific to these products as described in the guidance.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         “Guidance for Industry: Bar Code Label Requirements—Questions and Answers” dated August 2011 (
                        <E T="03">http://www.fda.gov/downloads/BiologicsBloodVaccines/GuidanceComplianceRegulatoryInformation/Guidances/UCM267392.pdf</E>
                        ).
                    </P>
                </FTNT>
                <P>
                    FDA recognizes, however, that since alternative technologies continue to advance, it may now be feasible for these technologies to address other stakeholder coding needs in other contexts and for other products. For example, under section 505D of the Federal Food, Drug, and Cosmetic Act (the FD&amp;C Act) (21 U.S.C. 355e), FDA is developing standards for identification, validation, authentication, and tracking and tracing of prescription drugs. The goal of this initiative is to implement a system to further ensure patient safety and to improve the security of the drug supply chain against counterfeit, diverted, subpotent, substandard, adulterated, misbranded, or expired drugs. In March 2010, FDA issued a guidance that discusses a standard for uniquely identifying prescription drug packages using a Standardized Numerical Identifier (SNI).
                    <SU>4</SU>
                    <FTREF/>
                     In the guidance, the Agency did not specify the means of incorporating the SNI onto the package. However, the guidance recognizes that the SNI is a flexible standard that can be encoded into a variety of machine-readable forms of data carriers, such as two-dimensional bar codes, alternate coding systems, and RFID. Thus, the guidance leaves options open while technologies for securing the supply chain continue to be identified, and standards making use of SNI are developed. Similarly, while FDA recognizes that the underlying primary goals of the Bar Code Final Rule and section 505D of the FD&amp;C Act are different, the Agency wants to leave options open with respect to how the same technology may be used for both purposes.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         “Guidance for Industry: Standards for Securing the Drug Supply Chain—Standardized Numerical Identification for Prescription Drug Packages” dated March 2010 (
                        <E T="03">http://www.fda.gov/downloads/RegulatoryInformation/Guidance/UCM206075.pdf</E>
                        ).
                    </P>
                </FTNT>
                <P>FDA is announcing the establishment of a public docket to provide an opportunity for interested persons to share information, research, and ideas on the effectiveness of the current regulation and the need, maturity, and acceptability of alternative technologies for the identification, including the unique identification, of drugs and biological products. FDA will use the information received to assess coding technologies in relation to current bar code requirements and other initiatives.</P>
                <HD SOURCE="HD1">II. Request for Comments and Information</HD>
                <P>FDA is requesting comments and supporting information on (1) bar code labeling standards for drugs and biological products and (2) the identification of current alternative technologies for use by industry and others.</P>
                <P>To facilitate this discussion, FDA sets forth some questions in the following paragraphs. These questions, which are not meant to be exhaustive, are provided to stimulate public comments that will help FDA evaluate the Bar Code Final Rule and the accommodation of alternative technologies to the linear bar code requirement (§ 201.25). The public is encouraged to address these and/or other related questions.</P>
                <P>The Agency encourages responses to the following questions about the costs and benefits of any alternative to the linear bar code. FDA also encourages you to provide as much detail and context as possible in your responses. Furthermore, the Agency specifically invites small businesses to provide information about the potential impact of alternatives to the linear bar code.</P>
                <P>1. Is there a need for alternative technologies to the linear bar code? Does the current linear bar code requirement meet the current needs of the health care industry and health care providers?</P>
                <P>
                    2. How has product coding technology changed since FDA issued the Bar Code Final Rule on February 26, 2004? Please provide information about the maturity, degree of adoption, cost, and ease of use of coding technologies 
                    <PRTPAGE P="66238"/>
                    that may be considered as alternatives or in addition to the linear bar code.
                </P>
                <P>3. What factors other than those listed in question 2 should FDA take into account in considering technologies alternative to or in addition to the linear bar code?</P>
                <P>4. What technologies or coding systems warrant FDA's consideration as alternatives to the linear bar code? In your response, the Agency particularly invites comments on the following issues for each technology identified:</P>
                <P>A. What is the current state of development and availability of the alternative technology?</P>
                <P>B. Would adoption of this technology as an alternative to the linear bar code further reduce medication errors in hospitals and health care settings? Please provide supporting data, if available.</P>
                <P>C. Would adoption of this alternative technology advance public health protections? If so, how? If supporting data exist, please provide this information.</P>
                <P>
                    5. Does the adoption of this alternative technology have implications for other FDA or Department of Health and Human Services initiatives (
                    <E T="03">e.g.,</E>
                     SNI)?
                </P>
                <P>6. Have you used the linear bar code for authentication or tracking and tracing of prescription drugs?</P>
                <P>A. If so, how?</P>
                <P>B. Please describe any successes or challenges that you have encountered in adopting linear bar code technology for this purpose.</P>
                <P>C. If not, which if any alternative technologies could reduce medication errors while also serving other functions?</P>
                <P>7. For hospitals and other health-care facilities that have adopted bar code technologies using linear bar codes:</P>
                <P>A. What difficulties did you encounter in adopting the technology?</P>
                <P>B. How have productivity and operating costs changed?</P>
                <P>C. What differences have you seen in medical outcomes?</P>
                <P>D. What problems have you experienced with the technology?</P>
                <P>8. For hospitals and other health-care facilities that have adopted alternative technologies or non-linear coding:</P>
                <P>A. What difficulties did you encounter in adopting the technology?</P>
                <P>B. How have productivity and operating costs changed?</P>
                <P>C. What differences have you seen in medical outcomes?</P>
                <P>D. What problems have you experienced with the technology?</P>
                <P>9. For hospitals and other health-care facilities that have not adopted bar code technologies using linear bar codes:</P>
                <P>A. Do you plan to adopt the technology within the next 12 months?</P>
                <P>B. If you do not plan to adopt the technology, please explain what factor(s) most influenced the decision not to adopt it.</P>
                <P>10. How would technology adoption have proceeded since 2004 had the Bar Code Final Rule not gone into effect?</P>
                <P>11. What are hospitals' and other health-care facilities' forecasts for technology adoption once incentives in the Economic Stimulus Act of 2008 (Pub. L. 110-185) are no longer in effect?</P>
                <P>
                    12. Would there be an economic impact on those parties who may not be subject to the bar code requirement but who nonetheless may use or adopt or have adopted bar code technology (
                    <E T="03">e.g.,</E>
                     hospitals, clinics, public health agencies, and health care providers)? Please use the following questions to guide your responses.
                </P>
                <P>
                    A. 
                    <E T="03">Current practices.</E>
                     Describe your current practice(s) at your institution with respect to those products that are required to be labeled with a bar code under §§ 201.25 and 610.67. Have you encountered any barriers to your ability to use technology at your institution?
                </P>
                <P>
                    B. 
                    <E T="03">Using an alternative to the linear bar code.</E>
                     If an alternative to the linear bar code could be placed on the label of at least some of your products, what impact, if any, would that have on your current practice(s)? How would you change your practices, if at all?
                </P>
                <P>
                    C. 
                    <E T="03">Expenses.</E>
                     What unplanned expenses, if any, would you incur, if an alternative to the linear bar code could be placed on the label of at least some of your products? If you could foresee using an alternative to the linear bar code, would you modify operations in your facility, and if so, how?
                </P>
                <P>
                    D. 
                    <E T="03">Adverse event reporting and recalls.</E>
                     Have you encountered challenges/successes in drug identification or reporting with respect to products that contain a bar code on their labels? If so, please describe them. Would an alternative to the linear bar code have an impact on your recall management or adverse event reporting, and if so, how?
                </P>
                <P>13. Are there other parties whose economic interests we should consider?</P>
                <HD SOURCE="HD1">III. Comments</HD>
                <P>
                    Interested persons may submit to the Division of Dockets Management (see 
                    <E T="02">ADDRESSES</E>
                    ) either electronic or written comments regarding this document. It is only necessary to send one set of comments. It is no longer necessary to send two copies of mailed comments. Identify comments with the docket number found in brackets in the heading of this document. Received comments may be seen in the Division of Dockets Management between 9 a.m. and 4 p.m., Monday through Friday.
                </P>
                <P>
                    Please allow sufficient time for mailed comments to be timely received by the due dates in the event of delivery delay. Comments must be received by these dates to be considered. We request that comments be identified clearly as an “initial” comment or a “reply” comment. Initial comments may address any issue raised in this notice. Initial comments will be made available electronically, online at 
                    <E T="03">http://www.regulations.gov,</E>
                     or for public inspection in the Division of Dockets Management (see 
                    <E T="02">ADDRESSES</E>
                    ). To allow sufficient opportunity for interested persons to prepare and submit any reply comments, late-filed initial comments will not be considered. Reply comments must address only matters raised in initial comments and must not be used to present new arguments, contentions, or factual material that is not responsive to the initial comments. To be considered, reply comments must identify which initial comments they are replying to, and which specific issues(s) are being addressed. We will not consider comments received during the reply comment period that do not identify the specific issue(s) raised during the initial comment period on which the reply comment is based. It is the Agency's intent to comply with Executive Order 13563 as quickly as possible, so we will not look favorably on requests for extensions of the comment period.
                </P>
                <P>Comments previously submitted to the Division of Dockets Management for the following docket will also be considered by FDA and do not need to be resubmitted: “Draft Guidance for Industry: Bar Code Label Requirements (Question 12 Update)” (75 FR 54347 September 2010; Docket No. FDA-2010-D-0426).</P>
                <SIG>
                    <DATED>Dated: October 21, 2011.</DATED>
                    <NAME>Leslie Kux,</NAME>
                    <TITLE>Acting Assistant Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27657 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="66239"/>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <CFR>26 CFR Parts 1</CFR>
                <DEPDOC>[REG-158677-05]</DEPDOC>
                <RIN>RIN 1545-BF24</RIN>
                <SUBJECT>Effect of Election on Corporation</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Withdrawal of notice of proposed rulemaking.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document withdraws the proposed regulation seeking to clarify that if a bank is an S corporation within the meaning of section 1361(a)(1), its status as an S corporation does not affect the applicability of the special rules for banks under the Internal Revenue Code.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Laura Fields at (202) 622-3050 (not a toll-free number).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On August 24, 2006, the Treasury Department and the IRS published in the 
                    <E T="04">Federal Register</E>
                     (71 FR 50007) a notice of proposed rulemaking under section 1363 (REG-158677-05), relating to the applicability of the special banking rules to banks that are S corporations within the meaning of section 1361(a)(1) of the Internal Revenue Code.
                </P>
                <P>The Treasury Department and the IRS received written comments on the proposed regulation from various interested parties. The Treasury Department and the IRS have decided to withdraw the proposed regulation.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 26 CFR Part 1</HD>
                    <P>Income taxes, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <HD SOURCE="HD1">Withdrawal of Notice of Proposed Rulemaking</HD>
                <P>
                    Accordingly, under the authority of 26 U.S.C. 7805, the notice of proposed rulemaking (REG-158677-05) that was published in the 
                    <E T="04">Federal Register</E>
                     on August 24, 2006 (71 FR 50007) is withdrawn.
                </P>
                <SIG>
                    <NAME>Steven T. Miller,</NAME>
                    <TITLE>Deputy Commissioner for Services and Enforcement.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27631 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 165</CFR>
                <DEPDOC>[Docket No. USCG-2011-0118]</DEPDOC>
                <RIN>RIN 1625-AA00</RIN>
                <SUBJECT>Safety Zones; Fireworks Displays Within the Fifth Coast Guard District</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard proposes to revise the list of permanent safety zones established for fireworks displays at various locations within the geographic boundary of the Fifth Coast Guard District. This action is necessary to protect the life and property of the maritime public from the hazards posed by fireworks displays. Entry into or movement within these proposed zones during the enforcement periods is prohibited without approval of the appropriate Captain of the Port.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments and related material must be received by the Coast Guard on or before November 25, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments identified by docket number USCG-2011-0118 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.
                    </P>
                    <P>
                        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 Dennis Sens, Prevention Division, Fifth Coast Guard District; telephone 757-398-6204, e-mail 
                        <E T="03">Dennis.M.Sens@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">Public Participation and Request for Comments</HD>
                <P>
                    We encourage you to participate in this rulemaking by submitting comments and related materials. All comments received will be posted without change to 
                    <E T="03">http://www.regulations.gov</E>
                     and will include any personal information you have provided.
                </P>
                <HD SOURCE="HD1">Submitting Comments</HD>
                <P>
                    If you submit a comment, please include the docket number for this rulemaking (USCG-2011-0118), 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 telephone 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 “Document Type” drop down menu select “Proposed Rule” and insert “USCG-2011-0118” in the “Keyword” 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. We will consider all comments and material received during the comment period and may change the rule based on your comments.
                </P>
                <HD SOURCE="HD1">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 
                    <PRTPAGE P="66240"/>
                    become highlighted in blue. In the “Keyword” box insert “USCG-2011-0118” 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="HD1">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="HD1">Public Meeting</HD>
                <P>
                    We do not now plan to hold a public meeting. But you may submit a request for one 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>
                <HD SOURCE="HD1">Basis and Purpose</HD>
                <P>In this rule the Coast Guard proposes to revise the list of permanent safety zones at 33 CFR 165.506, established for fireworks displays at various locations within the geographic boundary of the Fifth Coast Guard District. For a description of the geographical area of the Fifth District and subordinate Coast Guard Sectors—Captain of the Port Zones, please see 33 CFR 3.25. Currently there are 73 permanent safety zones that are established for annually recurring fireworks displays within the geographic boundaries of the Fifth Coast Guard District.</P>
                <P>The Coast Guard proposes to revise the list of permanent safety zones at 33 CFR 165.506, established for fireworks displays, by adding 3 new locations, deleting 2 previously established locations and modifying 19 previously established locations within the geographic boundary of the Fifth Coast Guard District. This rule will increase the total number of permanent safety zones to 74 locations for fireworks displays within the boundary of the Fifth Coast Guard District.</P>
                <P>This rule proposes to add 3 new safety zone locations to the permanent safety zones listed in 33 CFR 165.506. The new safety zones include locations at: North Atlantic Ocean, Atlantic City, NJ; Great Wicomico River, Mila, VA; and Cockrell's Creek, Reedville, VA.</P>
                <P>The 19 previously established safety zone locations proposed for modification by this rule are: Severn River and Spa Creek, Annapolis, MD; Baltimore Inner Harbor, Patapsco River, MD, (2 locations); Patuxent River, Calvert County, MD; Chesapeake Bay, Chesapeake Beach, MD; Potomac River, Charles County, MD; Potomac River, Charles County, MD near Mount Vernon; Potomac River, National Harbor, MD; Miles River, St. Michaels, MD; Tred Avon River, Oxford, MD; Upper Potomac River, Alexandria, VA; Anacostia River, Washington, DC; Potomac River, Prince William County, VA; North Atlantic Ocean, Ocean City, NJ; Chesapeake Bay, Norfolk, VA; North Atlantic Ocean, Virginia Beach, VA (2 locations); Pamlico River, Washington, NC; and Motts Channel, Banks Channel, Wrightsville Beach, NC. Safety zone modifications include revision to dates and minor changes to coordinates that define safety zone boundaries.</P>
                <P>The Coast Guard typically receives numerous applications for fireworks displays in these general areas. Previously, a temporary safety zone was established on an emergency basis for each display. This limited the opportunity for public comment. Establishing permanent safety zones through notice and comment rulemaking provides the public the opportunity to comment on the safety zone locations, size, and length of time the zones will be enforced.</P>
                <P>Each year organizations in the Fifth Coast Guard District sponsor fireworks displays in the same general location and time period. Each event uses a barge or an on-shore site near the shoreline as the fireworks launch platform. A safety zone is used to control vessel movement within a specified distance surrounding the launch platforms to ensure the safety of persons and property. Coast Guard personnel on scene may allow boaters within the safety zone if conditions permit.</P>
                <P>
                    The Coast Guard would publish notices in the 
                    <E T="04">Federal Register</E>
                     if an event sponsor reported a change to the listed event venue or date. In the case of inclement weather the event usually will be conducted on the day following the date listed in the Table to § 165.506. Coast Guard Captains of the Port would give notice of the enforcement of each safety zone by all appropriate means to provide the widest dissemination of notice among the affected segments of the public. This would include publication in the Local Notice to Mariners and Marine Information Broadcasts. Marine information and facsimile broadcasts may also be made for these events, beginning 24 to 48 hours before the event. Fireworks barges or launch sites on land used in the locations stated in this rulemaking would also display a sign labeled “FIREWORKS—DANGER—STAY AWAY”* * * The sign would be affixed to the port and starboard side of the barge or mounted on a post 3 feet above ground level when on land and in close proximity to the shoreline facing the water. This sign provides on scene notice that the safety zone is or will be enforced on that day. The sign will be diamond shaped, 4 feet by 4 feet with a 3-inch orange retro-reflective border. The word “DANGER” shall be 10-inch black block letters centered on the sign with the words “FIREWORKS” and “STAY AWAY” in 6 inch black block letters placed above and below the word “DANGER” respectively on a white background. There would also be a Coast Guard patrol vessel on scene 30 minutes before the display is scheduled to start until 30 minutes after its completion to enforce the safety zone.
                </P>
                <P>The enforcement period for these proposed safety zones is from 5:30 p.m. to 1 a.m. local time. However, vessels may enter, remain in, or transit through these safety zones during this timeframe if authorized by the Captain of the Port or designated Coast Guard patrol personnel on scene, as provided for in 33 CFR 165.23.</P>
                <P>This rule is being proposed to provide for the safety of life on navigable waters during the events and to give the marine community the opportunity to comment on the proposed zone locations, size, and length of time the zones will be active.</P>
                <HD SOURCE="HD1">Discussion of Proposed Rule</HD>
                <P>The Coast Guard proposes to revise the regulations at 33 CFR 165.506 by adding the following 3 permanent safety zone locations.</P>
                <HD SOURCE="HD1">North Atlantic Ocean, Atlantic City, NJ, Safety Zone</HD>
                <P>The waters of the North Atlantic Ocean within a 500 yard radius of the fireworks barge located at latitude 39°20′58″ N, longitude 074°25′58″ W, near the shoreline at Atlantic City, NJ.</P>
                <HD SOURCE="HD1">Great Wicomico River, Mila, VA, Safety Zone</HD>
                <P>
                    All waters of the Great Wicomico River located within a 420 foot radius of the fireworks display at approximate 
                    <PRTPAGE P="66241"/>
                    position latitude 37°50′31″ N, longitude 076°19′42″ W near Mila, Virginia.
                </P>
                <HD SOURCE="HD1">Cockrell's Creek, Reedville, VA, Safety Zone</HD>
                <P>All waters of Cockrell's Creek located within a 420 foot radius of the fireworks display at approximate position latitude 37°49′54″ N, longitude 076°16′44″ W near Reedville, Virginia.</P>
                <P>The Coast Guard proposes to revise regulations at 33 CFR 165.506 by modifying 19 existing permanent safety zone locations. The following table shows where these 19 existing permanent safety zones are listed within the Table to 33 CFR 165.506 and describes the revisions that are being made to these safety zones.</P>
                <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="xs40,r100,r150,r50">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Number</CHED>
                        <CHED H="1">
                            Table to § 165.506
                            <LI>section</LI>
                        </CHED>
                        <CHED H="1">Location</CHED>
                        <CHED H="1">Revision</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">1</ENT>
                        <ENT>a.11</ENT>
                        <ENT>N. Atlantic Ocean, Ocean City, NJ</ENT>
                        <ENT>Event date.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2</ENT>
                        <ENT>b.2</ENT>
                        <ENT>Severn River &amp; Spa Creek, Annapolis, MD</ENT>
                        <ENT>Coordinates.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3</ENT>
                        <ENT>b.6</ENT>
                        <ENT>Baltimore Inner Harbor, Patapsco River, MD</ENT>
                        <ENT>Event date &amp; coordinates.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4</ENT>
                        <ENT>b.7</ENT>
                        <ENT>Baltimore Inner Harbor, Patapsco River, MD</ENT>
                        <ENT>Event date &amp; coordinates.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">5</ENT>
                        <ENT>b.9</ENT>
                        <ENT>Patuxent River, Calvert County, MD</ENT>
                        <ENT>Coordinates.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">6</ENT>
                        <ENT>b.11</ENT>
                        <ENT>Chesapeake Bay, Chesapeake Beach, MD</ENT>
                        <ENT>Coordinates.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7</ENT>
                        <ENT>b.13</ENT>
                        <ENT>Potomac River, Charles County, MD</ENT>
                        <ENT>Event date &amp; coordinates</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">8</ENT>
                        <ENT>b.14</ENT>
                        <ENT>Potomac River, Charles County, MD, Mount Vernon</ENT>
                        <ENT>Coordinates.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">9</ENT>
                        <ENT>b.16</ENT>
                        <ENT>Potomac River, National Harbor, MD</ENT>
                        <ENT>Event date &amp; coordinates.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10</ENT>
                        <ENT>b.18</ENT>
                        <ENT>Miles River, St. Michaels, MD</ENT>
                        <ENT>Coordinates.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">11</ENT>
                        <ENT>b.19</ENT>
                        <ENT>Tred Avon River, Oxford, MD</ENT>
                        <ENT>Coordinates.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12</ENT>
                        <ENT>b.21</ENT>
                        <ENT>Upper Potomac River, Alexandria, VA</ENT>
                        <ENT>Event date.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">13</ENT>
                        <ENT>b.22</ENT>
                        <ENT>Anacostia River, Washington, DC</ENT>
                        <ENT>Coordinates.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">14</ENT>
                        <ENT>b.23</ENT>
                        <ENT>Potomac River, Prince William County, VA</ENT>
                        <ENT>Event date &amp; coordinates.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15</ENT>
                        <ENT>c.10</ENT>
                        <ENT>Chesapeake Bay, Norfolk, VA</ENT>
                        <ENT>Event date.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">16</ENT>
                        <ENT>c.16</ENT>
                        <ENT>N. Atlantic Ocean, Virginia Beach, VA</ENT>
                        <ENT>Event date.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">17</ENT>
                        <ENT>c.17</ENT>
                        <ENT>N. Atlantic Ocean, Virginia Beach, VA</ENT>
                        <ENT>Event date.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">18</ENT>
                        <ENT>d.7</ENT>
                        <ENT>Pamlico River, Washington, NC</ENT>
                        <ENT>Coordinates.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">19</ENT>
                        <ENT>d.10</ENT>
                        <ENT>Motts Channel, Banks Channel, Wrightsville Beach, NC</ENT>
                        <ENT>Event date.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The Coast Guard proposes to amend regulations at 33 CFR 165.506 by disestablishing the following 2 permanent safety zones. All coordinates listed for the following safety zones reference Datum NAD 1983.</P>
                <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="xs40,r100,r100,r250">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Number</CHED>
                        <CHED H="1">Date</CHED>
                        <CHED H="1">Location</CHED>
                        <CHED H="1">Regulated area</CHED>
                    </BOXHD>
                    <ROW EXPSTB="03" RUL="s">
                        <ENT I="21">
                            <E T="02">(b) Coast Guard Sector Baltimore—COTP Zone</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">10</ENT>
                        <ENT>July 4th</ENT>
                        <ENT>Patuxent River, Solomons Island, Calvert County, MD, Safety Zone</ENT>
                        <ENT>All waters of the Patuxent River within a 400 yard radius of the fireworks barge located at latitude 38°19′03″ N, longitude 076°26′07.6″ W.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">11</ENT>
                        <ENT>July 4th</ENT>
                        <ENT>Patuxent River, Solomons Island, MD, Safety Zone</ENT>
                        <ENT>All waters of Patuxent River within a 300 yard radius of the fireworks barge in an area bound by the following points: latitude 38°19′42″ N, longitude 076°28′02″ W; thence to latitude 38°19′26″ N, longitude 076°28′18″ W; thence to latitude 38°18′48″ N, longitude 076°27′42″ W; thence to latitude 38°19′06″ N, longitude 076°27'25” W; thence to the point of origin, located near Solomons Island, MD.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Regulatory Analyses</HD>
                <P>We developed this proposed rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on 13 of these statutes and executive orders.</P>
                <HD SOURCE="HD1">Regulatory Planning and Review</HD>
                <P>This NPRM has not been designated a significant regulatory action under section 3(f) of Executive Order 12866, Regulatory Planning and Review, as supplemented by Executive Order 13563, Improving Regulation and Regulatory Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of Executive Order 12866 or under section 1 of Executive Order 13563. The Office of Management and Budget has not reviewed it under those Orders.</P>
                <P>We expect the economic impact of this proposed rule to be so minimal that a full Regulatory Evaluation is unnecessary. This finding is based on the short amount of time that vessels would be restricted from the zones, and the small zone sizes positioned in low vessel traffic areas. Vessels would not be precluded from getting underway, or mooring at any piers or marinas currently located in the vicinity of the proposed safety zones. Advance notifications would also be made to the local maritime community by issuing Local Notice to Mariners, Marine information and facsimile broadcasts so mariners can adjust their plans accordingly. Notifications to the public for most events will usually be made by local newspapers, radio and TV stations. The Coast Guard anticipates that these safety zones will only be enforced 2 to 3 times per year.</P>
                <HD SOURCE="HD1">Small Entities</HD>
                <P>
                    Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this proposed rule would have a significant economic impact on a 
                    <PRTPAGE P="66242"/>
                    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 proposed rule, if promulgated, 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 and operators of vessels intending to transit or anchor in the proposed safety zones during the times these zones are enforced.</P>
                <P>These proposed safety zones will not have a significant economic impact on a substantial number of small entities for the following reasons: The enforcement period will be short in duration and, in many of the zones, vessels can transit safely around the safety zones. Generally, blanket permission to enter, remain in, or transit through these safety zones will be given except during the period that the Coast Guard patrol vessel is present. Before the enforcement period, we will issue maritime advisories widely.</P>
                <P>
                    If you think that your business, organization, or governmental jurisdiction qualifies as a small entity and that this rule would have a significant economic impact on it, please submit a comment (see 
                    <E T="02">ADDRESSES</E>
                    ) explaining why you think it qualifies and how and to what degree this rule would economically affect it.
                </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 proposed rule so that they can better evaluate its effects on them and participate in the rulemaking. If the rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact the person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    . The Coast Guard will not retaliate against small entities that question or complain about this proposed rule or any policy or action of the Coast Guard.
                </P>
                <HD SOURCE="HD1">Collection of Information</HD>
                <P>This proposed rule would call 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 proposed 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 (adjusted for inflation) or more in any one year. Though this proposed rule would 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 proposed rule would 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>
                <HD SOURCE="HD1">Civil Justice Reform</HD>
                <P>This proposed 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 proposed rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and would not create an environmental risk to health or risk to safety that might disproportionately affect children.</P>
                <HD SOURCE="HD1">Indian Tribal Governments</HD>
                <P>This proposed rule does not have Tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it would 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 proposed rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. The Administrator of the Office of Information and Regulatory Affairs has not designated it as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211.</P>
                <HD SOURCE="HD1">Technical Standards</HD>
                <P>
                    The National Technology Transfer and Advancement Act (NTTAA) (15 U.S.C. 272 note) directs agencies to use voluntary consensus standards in their regulatory activities unless the agency provides Congress, through the Office of Management and Budget, with an explanation of why using these standards would be inconsistent with applicable law or otherwise impractical. Voluntary consensus standards are technical standards (
                    <E 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 proposed 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 proposed 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 made a preliminary determination that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment. A preliminary environmental analysis checklist supporting this preliminary determination is available in the docket where indicated under 
                    <E T="02">ADDRESSES</E>
                    . This proposed rule involves implementation of regulations within 33 CFR Part 165 that establish safety zones on navigable waters of the United States, and, therefore paragraph (34)(g) of figure 2-1 applies. These safety zones are enforced for the duration of the 
                    <PRTPAGE P="66243"/>
                    fireworks displays, which are launched from or adjacent to navigable waters of the United States and may have potential for negative impact on the safety or other interest of waterway users and shore side activities in the event area. The category of activities includes fireworks launched from barges at or near the shoreline that generally rely on the use of navigable waters as a safety buffer. We seek any comments or information that may lead to the discovery of a significant environmental impact from this proposed rule.
                </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, and Waterways.</P>
                </LSTSUB>
                <P>For the reasons discussed in the preamble, the Coast Guard proposes to amend 33 CFR part 165 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
                    <P>1. The authority citation for part 165 continues to read as follows:</P>
                    <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, 160.5; Pub. L. 107-295, 116 Stat. 2064; Department of Homeland Security Delegation No. 0170.1.</P>
                    </AUTH>
                    <P>2. Revise § 165.506 to read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 165.506 </SECTNO>
                        <SUBJECT>Safety Zones; Fifth Coast Guard District Fireworks Displays.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Regulations.</E>
                             (1) The general regulations contained in 33 CFR 165.23 apply.
                        </P>
                        <P>(2) The following regulations apply to the fireworks safety zones listed in the Table to § 165.506. These regulations will be enforced annually, for the duration of each fireworks event listed in the Table to § 165.506. In the case of inclement weather, the event may be conducted on the day following the date listed in the Table to § 165.506. Annual notice of the exact dates and times of the enforcement period of the regulation with respect to each safety zone, the geographical area, and other details concerning the nature of the fireworks event will be published in Local Notices to Mariners and via Broadcast Notice to Mariners over VHF-FM marine band radio.</P>
                        <P>(3) All persons and vessels shall comply with the instructions of the Coast Guard Captain of the Port or the designated on-scene-patrol personnel. Those personnel are comprised of commissioned, warrant, and petty officers of the U.S. Coast Guard. Other Federal, State and local agencies may assist these personnel in the enforcement of the safety zone. Upon being hailed by a U.S. Coast Guard vessel by siren, radio, flashing light or other means, the operator of a vessel shall proceed as directed.</P>
                        <P>(b) Notification. (1) Fireworks barges and launch sites on land that operate within the regulated areas contained in the Table to § 165.506 will have a sign affixed to the port and starboard side of the barge or mounted on a post 3 feet above ground level when on land immediately adjacent to the shoreline and facing the water labeled “FIREWORKS—DANGER—STAY AWAY.” This will provide on scene notice that the safety zone will be enforced on that day. This notice will consist of a diamond shaped sign 4 feet by 4 feet with a 3-inch orange retro reflective border. The word “DANGER” shall be 10 inch black block letters centered on the sign with the words “FIREWORKS” and “STAY AWAY” in 6 inch black block letters placed above and below the word “DANGER” respectively on a white background.</P>
                        <P>(2) Coast Guard Captains of the Port in the Fifth Coast Guard District will notify the public of the enforcement of these safety zones by all appropriate means to effect the widest publicity among the affected segments of the public. Publication in the Local Notice to Mariners, marine information broadcasts, and facsimile broadcasts may be made for these events, beginning 24 to 48 hours before the event is scheduled to begin, to notify the public.</P>
                        <P>
                            (c) 
                            <E T="03">Contact Information.</E>
                             Questions about safety zones and related events should be addressed to the local Coast Guard Captain of the Port for the area in which the event is occurring. Contact information is listed below. For a description of the geographical area of each Coast Guard Sector—Captain of the Port zone, please see 33 CFR 3.25.
                        </P>
                        <P>(1) Coast Guard Sector Delaware Bay—Captain of the Port Zone, Philadelphia, Pennsylvania: (215) 271-4944.</P>
                        <P>(2) Coast Guard Sector Baltimore—Captain of the Port Zone, Baltimore, Maryland: (410) 576-2525.</P>
                        <P>(3) Coast Guard Sector Hampton Roads—Captain of the Port Zone, Norfolk, Virginia: (757) 483-8567.</P>
                        <P>(4) Coast Guard Sector North Carolina—Captain of the Port Zone, Wilmington, North Carolina: (877) 229-0770 or (910) 772-2200.</P>
                        <P>
                            (d) 
                            <E T="03">Enforcement Period.</E>
                             The safety zones in the Table to § 165.506 will be enforced from 5:30 p.m. to 1 a.m. each day a barge with a “FIREWORKS—DANGER—STAY AWAY” sign on the port and starboard side is on-scene or a “FIREWORKS—DANGER—STAY AWAY” sign is posted on land adjacent to the shoreline, in a location listed in the Table to § 165.506. Vessels may not enter, remain in, or transit through the safety zones during these enforcement periods unless authorized by the Captain of the Port or designated Coast Guard patrol personnel on scene.
                        </P>
                        <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="xs25,r50,r50,r150">
                            <TTITLE>Table to § 165.506</TTITLE>
                            <TDESC>[All coordinates listed in the Table to § 165.506 reference Datum NAD 1983.]</TDESC>
                            <BOXHD>
                                <CHED H="1">Number</CHED>
                                <CHED H="1">Date</CHED>
                                <CHED H="1">Location</CHED>
                                <CHED H="1">Regulated area</CHED>
                            </BOXHD>
                            <ROW EXPSTB="03" RUL="s">
                                <ENT I="21">
                                    <E T="02">(a.) Coast Guard Sector Delaware Bay—COTP Zone</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">1</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>North Atlantic Ocean, Bethany Beach, DE, Safety Zone</ENT>
                                <ENT>The waters of the North Atlantic Ocean within a 500 yard radius of the fireworks barge in approximate position latitude 38°32′08″  N, longitude 075°03′15″ W, adjacent to shoreline of Bethany Beach, DE.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">2</ENT>
                                <ENT>Labor Day</ENT>
                                <ENT>Indian River Bay, DE, Safety Zone</ENT>
                                <ENT>All waters of the Indian River Bay within a 360 yard radius of the fireworks launch location on the pier in approximate position latitude 38°36′42″ N, longitude 075°08′18″  W, about 700 yards east of Pots Net Point, DE.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">3</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>North Atlantic Ocean, Rehoboth Beach, DE, Safety Zone</ENT>
                                <ENT>All waters of the Atlantic Ocean within a 360 yard radius of the fireworks barge in approximate position latitude 38°43′01.2″ N, longitude 075°04′21″ W, approximately 400 yards east of Rehoboth Beach, DE.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">4</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>North Atlantic Ocean, Avalon, NJ, Safety Zone</ENT>
                                <ENT>The waters of the North Atlantic Ocean within a 500 yard radius of the fireworks barge in approximate location latitude 39°05′31″ N, longitude 074°43′00″ W, in the vicinity of the shoreline at Avalon, NJ.</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="66244"/>
                                <ENT I="01">5</ENT>
                                <ENT>July 4th, September—2nd Saturday</ENT>
                                <ENT>Barnegat Bay, Barnegat Township, NJ, Safety Zone</ENT>
                                <ENT>The waters of Barnegat Bay within a 500 yard radius of the fireworks barge in approximate position latitude 39°44′50″ N, longitude 074°11′21″ W, approximately 500 yards north of Conklin Island, NJ.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">6</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>North Atlantic Ocean, Cape May, NJ, Safety Zone</ENT>
                                <ENT>The waters of the North Atlantic Ocean within a 500 yard radius of the fireworks barge in approximate location latitude 38°55′36″ N, longitude 074°55′26″ W, immediately adjacent to the shoreline at Cape May, NJ.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">7</ENT>
                                <ENT>July 3rd</ENT>
                                <ENT>Delaware Bay, North Cape May, NJ, Safety Zone</ENT>
                                <ENT>All waters of the Delaware Bay within a 500 yard radius of the fireworks barge in approximate position latitude 38°58′00″ N, longitude 074°58′30″ W.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">8</ENT>
                                <ENT>August—3rd Sunday</ENT>
                                <ENT>Great Egg Harbor Inlet, Margate City, NJ, Safety Zone</ENT>
                                <ENT>All waters within a 500 yard radius of the fireworks barge in approximate location latitude 39°19′33″ N, longitude 074°31′28″ W, on the Intracoastal Waterway near Margate City, NJ.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">9</ENT>
                                <ENT>
                                    July 4th, August every Thursday
                                    <LI>September 1st Thursday</LI>
                                </ENT>
                                <ENT>Metedeconk River, Brick Township, NJ, Safety Zone</ENT>
                                <ENT>The waters of the Metedeconk River within a 300 yard radius of the fireworks launch platform in approximate position latitude 40°03′24″ N, longitude 074°06′42″ W, near the shoreline at Brick Township, NJ.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">10</ENT>
                                <ENT>July—1st Friday</ENT>
                                <ENT>North Atlantic Ocean, Atlantic City, NJ, Safety Zone</ENT>
                                <ENT>The waters of the North Atlantic Ocean within a 500 yard radius of the fireworks barge located at latitude 39°20′58″ N, longitude 074°25′58″ W, near the shoreline at Atlantic City, NJ.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">11</ENT>
                                <ENT>July 4th, October—1st Saturday</ENT>
                                <ENT>North Atlantic Ocean, Ocean City, NJ, Safety Zone</ENT>
                                <ENT>The waters of the North Atlantic Ocean within a 500 yard radius of the fireworks barge in approximate location latitude 39°16′22″ N, longitude 074°33′54″ W, in the vicinity of the shoreline at Ocean City, NJ.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">12</ENT>
                                <ENT>May—4th Saturday</ENT>
                                <ENT>Barnegat Bay, Ocean Township, NJ, Safety Zone</ENT>
                                <ENT>All waters of Barnegat Bay within a 500 yard radius of the fireworks barge in approximate position latitude 39°47′33″ N, longitude 074°10′46″ W.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">13</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>Little Egg Harbor, Parker Island, NJ, Safety Zone</ENT>
                                <ENT>All waters of Little Egg Harbor within a 500 yard radius of the fireworks barge in approximate position latitude 39°34′18″ N, longitude 074°14′43″ W, approximately 100 yards north of Parkers Island.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">14</ENT>
                                <ENT>September—3rd Saturday</ENT>
                                <ENT>Delaware River, Chester, PA, Safety Zone</ENT>
                                <ENT>All waters of the Delaware River near Chester, PA just south of the Commodore Barry Bridge within a 250 yard radius of the fireworks barge located in approximate position latitude 39°49′43.2″ N, longitude 075°22′42″ W.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">15</ENT>
                                <ENT>September—3rd Saturday</ENT>
                                <ENT>Delaware River, Essington, PA, Safety Zone</ENT>
                                <ENT>All waters of the Delaware River near Essington, PA, west of Little Tinicum Island within a 250 yard radius of the fireworks barge located in the approximate position latitude 39°51′18″ N, longitude 075°18′57″ W.</ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="01">16</ENT>
                                <ENT>July 4th, Columbus Day, December 31st, January 1st</ENT>
                                <ENT>Delaware River, Philadelphia, PA, Safety Zone</ENT>
                                <ENT>All waters of Delaware River, adjacent to Penns Landing, Philadelphia, PA, bounded from shoreline to shoreline, bounded on the south by a line running east to west from points along the shoreline at latitude 39°56′31.2″ N, longitude 075°08′28.1″ W; thence to latitude 39°56′29.1″ N, longitude 075°07′56.5″ W, and bounded on the north by the Benjamin Franklin Bridge.</ENT>
                            </ROW>
                            <ROW EXPSTB="03" RUL="s">
                                <ENT I="21">
                                    <E T="02">(b.) Coast Guard Sector Baltimore—COTP Zone</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">1</ENT>
                                <ENT>April—1st or 2nd Saturday</ENT>
                                <ENT>Washington Channel, Upper Potomac River, Washington, DC, Safety Zone</ENT>
                                <ENT>All waters of the Upper Potomac River within a 150 yard radius of the fireworks barge in approximate position latitude 38°52′09″ N, longitude 077°01′13″ W, located within the Washington Channel in Washington Harbor, DC.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">2</ENT>
                                <ENT>July 4th, December—1st and 2nd, Saturday, December 31st</ENT>
                                <ENT>Severn River and Spa Creek, Annapolis, MD, Safety Zone</ENT>
                                <ENT>All waters of the Severn River and Spa Creek within an area bounded by a line drawn from latitude 38°58′40″ N, longitude 076°28′49″ W; thence to latitude 38°58′26″ N, longitude 076°28′28″ W; thence to latitude 38°58′45″ N, longitude 076°28′07″ W; thence to latitude 38°59′01″ N, longitude 076°28′37″ W, thence to latitude 38°58′57″ N, longitude 076°28′40″ W, located near the entrance to Spa Creek in Annapolis, Maryland.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">3</ENT>
                                <ENT>Saturday before Independence Day holiday</ENT>
                                <ENT>Middle River, Baltimore County, MD, Safety Zone</ENT>
                                <ENT>All waters of the Middle River within a 300 yard radius of the fireworks barge in approximate position latitude 39°17′45″ N, longitude 076°23′49″ W, approximately 300 yards east of Rockaway Beach, near Turkey Point.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">4</ENT>
                                <ENT>July 4th, December 31st</ENT>
                                <ENT>Patapsco River (Middle Branch), Baltimore, MD, Safety Zone</ENT>
                                <ENT>All waters of the Patapsco River, Middle Branch, within an area bound by a line drawn from the following points: latitude 39°15′22″ N, longitude 076°36′36″ W; thence to latitude 39°15′10″ N, longitude 076°36′00″ W; thence to latitude 39°15′40″ N, longitude 076°35′23″ W; thence to latitude 39°15′49″ N, longitude 076°35′47″ W; thence to the point of origin, located approximately 600 yards east of Hanover Street (SR-2) Bridge.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">5</ENT>
                                <ENT>June 14th, July 4th, September—2nd Saturday, December 31st</ENT>
                                <ENT>Northwest Harbor (East Channel), Patapsco River, MD, Safety Zone</ENT>
                                <ENT>All waters of the Patapsco River within a 300 yard radius of the fireworks barge in approximate position 39°15′55″ N, 076°34′35″ W, located adjacent to the East Channel of Northwest Harbor.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">6</ENT>
                                <ENT>May—2nd or 3rd Thursday or Friday, July 4th, December 31st</ENT>
                                <ENT>Baltimore Inner Harbor, Patapsco River, MD, Safety Zone</ENT>
                                <ENT>All waters of the Patapsco River within a 100 yard radius of the fireworks barge in approximate position latitude 39°17′01″ N, longitude 076°36′31″ W, located at the entrance to Baltimore Inner Harbor, approximately 125 yards southwest of pier 3.</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="66245"/>
                                <ENT I="01">7</ENT>
                                <ENT>May—2nd or 3rd Thursday or Friday, July 4th, December 31st</ENT>
                                <ENT>Baltimore Inner Harbor, Patapsco River, MD, Safety Zone</ENT>
                                <ENT>The waters of the Patapsco River within a 100 yard radius of approximate position latitude 39°17′04″ N, longitude 076°36′36″ W, located in Baltimore Inner Harbor, approximately 125 yards southeast of pier 1.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">8</ENT>
                                <ENT>July 4th, December 31st</ENT>
                                <ENT>Northwest Harbor (West Channel) Patapsco River, MD, Safety Zone</ENT>
                                <ENT>All waters of the Patapsco River within a 300 yard radius of the fireworks barge in approximate position latitude 39°16′21″ N, longitude 076°34′38″ W, located adjacent to the West Channel of Northwest Harbor.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">9</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>Patuxent River, Calvert County, MD, Safety Zone</ENT>
                                <ENT>All waters of the Patuxent River within a 200 yard radius of the fireworks barge located at latitude 38°19′17″ N, longitude 076°27′45″ W, approximately 800 feet from shore at Solomons Island, MD.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">10</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>Chester River, Kent Island Narrows, MD, Safety Zone</ENT>
                                <ENT>All waters of the Chester River, within an area bound by a line drawn from the following points: latitude 38°58′50″ N, longitude 076°15′00″ W; thence north to latitude 38°59′00″ N, longitude 076°15′00″ W; thence east to latitude 38°59′00″ N, longitude 076°14′46″ W; thence southeast to latitude 38°58′50″ N, longitude 076°14′28″ W; thence southwest to latitude 38°58′37″ N, longitude 076°14′36″ W, thence northwest to latitude 38°58′42″ N, longitude 076°14′55″ W, thence to the point of origin, located approximately 900 yards north of Kent Island Narrows (US-50/301) Bridge.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">11</ENT>
                                <ENT>July 3rd</ENT>
                                <ENT>Chesapeake Bay, Chesapeake Beach, MD, Safety Zone</ENT>
                                <ENT>All waters of the Chesapeake Bay within a 150 yard radius of the fireworks barge in approximate position latitude 38°41′36″ N, longitude 076°31′30″ W, and within a 150 yard radius of the fireworks barge in approximate position latitude 38°41′28″ N, longitude 076°31′29″ W, located near Chesapeake Beach, Maryland.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">12</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>Choptank River, Cambridge, MD, Safety Zone</ENT>
                                <ENT>All waters of the Choptank River within a 300 yard radius of the fireworks launch site at Great Marsh Point, located at latitude 38°35′06″ N, longitude 076°04′46″ W.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">13</ENT>
                                <ENT>July—2nd or 3rd Saturday and last Saturday</ENT>
                                <ENT>Potomac River, Charles County, MD, Safety Zone</ENT>
                                <ENT>All waters of the Potomac River within a 300 yard radius of the fireworks barge in approximate position latitude 38°20′05″ N, longitude 077°15′00″ W, approximately 500 yards north of the shoreline at Fairview Beach, Virginia.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">14</ENT>
                                <ENT>May—last Saturday, July 4th</ENT>
                                <ENT>Potomac River, Charles County, MD—Mount Vernon, Safety Zone</ENT>
                                <ENT>All waters of the Potomac River within an area bound by a line drawn from the following points: latitude 38°42′30″ N, longitude 077°04′47″ W; thence to latitude 38°42′18″ N, longitude 077°04′42″ W; thence to latitude 38°42′11″ N, longitude 077°05′10″ W; thence to latitude 38°42′22″ N, longitude 077°05′12″ W; located at the Mount Vernon Estate, in Fairfax County, Virginia.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">15</ENT>
                                <ENT>October—1st Saturday</ENT>
                                <ENT>Dukeharts Channel, Potomac River, MD, Safety Zone</ENT>
                                <ENT>All waters of the Potomac River within a 300 yard radius of the fireworks barge in approximate position latitude 38°13′27″ N, longitude 076°44′48″ W, located adjacent to Dukeharts Channel near Coltons Point, Maryland.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">16</ENT>
                                <ENT>July—Day before Independence Day holiday, November—3rd Thursday and last Friday, December—1st, 2nd and 3rd Friday</ENT>
                                <ENT>Potomac River, National Harbor, MD, Safety Zone</ENT>
                                <ENT>All waters of the Potomac River within an area bound by a line drawn from the following points: latitude 38°47′13″ N, longitude 077°00′58″ W; thence to latitude 38°46′51″ N, longitude 077°01′15″ W; thence to latitude 38°47′25″ N, longitude 077°01′33″ W; thence to latitude 38°47′32″ N, longitude 077°01′08″ W; thence to the point of origin, located at National Harbor, Maryland.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">17</ENT>
                                <ENT>July 4th, September—last Saturday</ENT>
                                <ENT>Susquehanna River, Havre de Grace, MD, Safety Zone</ENT>
                                <ENT>All waters of the Susquehanna River within a 150 yard radius of the fireworks barge in approximate position latitude 39°32′42″ N, longitude 076°04′30″ W, approximately 800 yards east of the waterfront at Havre de Grace, MD.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">18</ENT>
                                <ENT>June and July—Saturday before Independence Day holiday</ENT>
                                <ENT>Miles River, St. Michaels, MD, Safety Zone</ENT>
                                <ENT>All waters of the Miles River within a 200 yard radius of approximate position latitude 38°47′42″ N, longitude 076°12′51″ W, located at the entrance to Long Haul Creek.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">19</ENT>
                                <ENT>June and July—Saturday or Sunday before Independence Day holiday</ENT>
                                <ENT>Tred Avon River, Oxford, MD, Safety Zone</ENT>
                                <ENT>All waters of the Tred Avon River within a 150 yard radius of the fireworks barge in approximate position latitude 38°41′24″ N, longitude 076°10′37″ W, approximately 500 yards northwest of the waterfront at Oxford, MD.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">20</ENT>
                                <ENT>July 3rd</ENT>
                                <ENT>Northeast River, North East, MD, Safety Zone</ENT>
                                <ENT>All waters of the Northeast River within a 300 yard radius of the fireworks barge in approximate position latitude 39°35′26″ N, longitude 075°57′00″ W, approximately 400 yards south of North East Community Park.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">21</ENT>
                                <ENT>June—2nd or 3rd Saturday, July—1st, 2nd or 3rd Saturday, September—1st or 2nd Saturday</ENT>
                                <ENT>Upper Potomac River, Alexandria, VA, Safety Zone</ENT>
                                <ENT>All waters of the Upper Potomac River within a 300 yard radius of the fireworks barge in approximate position 38°48′37″ N, 077°02′02″ W, located near the waterfront of Alexandria, Virginia.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">22</ENT>
                                <ENT>March through October, at the conclusion of evening MLB games at Washington Nationals Ball Park</ENT>
                                <ENT>Anacostia River, Washington, DC, Safety Zone</ENT>
                                <ENT>All waters of the Anacostia River within a 150 yard radius of the fireworks barge in approximate position latitude 38°52′13″ N, longitude 077°00′16″ W, located near the Washington Nationals Ball Park.</ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="01">23</ENT>
                                <ENT>June—last Saturday, July—3rd, 4th or last Saturday or Sunday</ENT>
                                <ENT>Potomac River, Prince William County, VA, Safety Zone</ENT>
                                <ENT>All waters of the Potomac River within a 200 yard radius of the fireworks barge in approximate position latitude 38°34′07″ N, longitude 077°15′32″ W, located near Cherry Hill, Virginia.</ENT>
                            </ROW>
                            <ROW EXPSTB="03" RUL="s">
                                <PRTPAGE P="66246"/>
                                <ENT I="21">
                                    <E T="02">(c.) Coast Guard Sector Hampton Roads—COTP Zone</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">1</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>North Atlantic Ocean, Ocean City, MD, Safety Zone</ENT>
                                <ENT>All waters of the Atlantic Ocean in an area bound by the following points: latitude 38°19′39.9″ N, longitude 075°05′03.2″ W; thence to latitude 38°19′36.7″ N, longitude 075°04′53.5″ W; thence to latitude 38°19′45.6″ N, longitude 075°04′49.3″ W; thence to latitude 38°19′49.1″ N, longitude 075°05′00.5″ W; thence to point of origin. The size of the safety zone extends approximately 300 yards offshore from the fireworks launch area located at the high water mark on the beach.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">2</ENT>
                                <ENT>May—4th Sunday, June—3rd Monday, and June 29th, July 4th, August—1st and 4th Sunday, September—1st and 4th Sunday</ENT>
                                <ENT>Isle of Wight Bay, Ocean City, MD, Safety Zone</ENT>
                                <ENT>All waters of Isle of Wight Bay within a 350 yard radius of the fireworks barge in approximate position latitude 38°22′32″ N, longitude 075°04′30″ W.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">3</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>Assawoman Bay, Fenwick Island—Ocean City, MD, Safety Zone</ENT>
                                <ENT>All waters of Assawoman Bay within a 360 yard radius of the fireworks launch location on the pier at the West end of Northside Park, in approximate position latitude 38°25′57.6″ N, longitude 075°03′55.8″ W.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">4</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>Broad Bay, Virginia Beach, VA, Safety Zone</ENT>
                                <ENT>All waters of the Broad Bay within a 400 yard radius of the fireworks display in approximate position latitude 36°52′08″ N, longitude 076°00′46″ W, located on the shoreline near the Cavalier Golf and Yacht Club, Virginia Beach, Virginia.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">5</ENT>
                                <ENT>October—1st Friday</ENT>
                                <ENT>York River, West Point, VA, Safety Zone</ENT>
                                <ENT>All waters of the York River near West Point, VA within a 400 yard radius of the fireworks display located in approximate position latitude 37°31′25″ N, longitude 076°47′19″ W.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">6</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>York River, Yorktown, VA, Safety Zone</ENT>
                                <ENT>All waters of the York River within a 400 yard radius of the fireworks display in approximate position latitude 37°14′14″ N, longitude 076°30′02″ W, located near Yorktown, Virginia.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">7</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>Chincoteague Channel, Chincoteague, VA, Safety Zone</ENT>
                                <ENT>All waters of the Chincoteague Channel within a 360 yard radius of the fireworks launch location at the Chincoteague carnival waterfront in approximate position latitude 37°55′40.3″ N, longitude 075°23′10.7″ W, approximately 900 yards southwest of Chincoteague Swing Bridge.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">8</ENT>
                                <ENT>May—1st Friday, July 4th</ENT>
                                <ENT>James River, Newport News, VA, Safety Zone</ENT>
                                <ENT>All waters of the James River within a 325 yard radius of the fireworks barge in approximate position latitude 36°58′30″ N, longitude 076°26′19″ W, located in the vicinity of the Newport News Shipyard, Newport News, Virginia.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">9</ENT>
                                <ENT>July 9th</ENT>
                                <ENT>Chesapeake Bay, Hampton, VA, Safety Zone</ENT>
                                <ENT>All waters of the Chesapeake Bay within a 350 yard radius of approximate position latitude 37°02′23″ N, longitude 076°17′22″ W, located near Buckroe Beach.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">10</ENT>
                                <ENT>June—4th Friday, July—1st Friday, July 4th</ENT>
                                <ENT>Chesapeake Bay, Norfolk, VA, Safety Zone</ENT>
                                <ENT>All waters of the Chesapeake Bay within a 400 yard radius of the fireworks display located in position latitude 36°57′21″ N, longitude 076°15′00″ W, located near Ocean View Fishing Pier.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">11</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>Chesapeake Bay, Virginia Beach, VA, Safety Zone</ENT>
                                <ENT>All waters of the Chesapeake Bay 400 yard radius of the fireworks display in approximate position latitude 36°55′02″ N, longitude 076°03′27″ W, located at the First Landing State Park at Virginia Beach, Virginia.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">12</ENT>
                                <ENT>Memorial Day, June—1st and 2nd Friday, Saturday and Sunday, July 4th, November—4th Saturday, December—1st Saturday and December 31st, January—1st</ENT>
                                <ENT>Elizabeth River, Southern Branch, Norfolk, VA, Safety Zone</ENT>
                                <ENT>All waters of the Elizabeth River Southern Branch in an area bound by the following points: latitude 36°50′54.8″ N, longitude 076°18′10.7″ W; thence to latitude 36°51′7.9″ N, longitude 076°18′01″ W; thence to latitude 36°50′45.6″ N, longitude 076°17′44.2″ W; thence to latitude 36°50′29.6″ N, longitude 076°17′23.2″ W; thence to latitude 36°50′7.7″ N, longitude 076°17′32.3″ W; thence to latitude 36°49′58″ N, longitude 076°17′28.6″ W; thence to latitude 36°49′52.6″ N, longitude 076°17′43.8″ W; thence to latitude 36°50′27.2″ N, longitude 076°17′45.3″ W thence to the point of origin.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">13</ENT>
                                <ENT>May—2nd Saturday, September—1st Saturday and Sunday, December—1st Saturday</ENT>
                                <ENT>Appomattox River, Hopewell, VA, Safety Zone</ENT>
                                <ENT>All waters of the Appomattox River within a 400 yard radius of the fireworks barge in approximate position latitude 37°19′11″ N, longitude 077°16′55″ W.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">14</ENT>
                                <ENT>July—3rd Saturday</ENT>
                                <ENT>John H. Kerr Reservoir, Clarksville, VA, Safety Zone</ENT>
                                <ENT>All waters of John H. Kerr Reservoir within a 400 yard radius of approximate position latitude 36°37′51″ N, longitude 078°32′50″ W, located near the center span of the State Route 15 Highway Bridge.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">15</ENT>
                                <ENT>May, June, July, August, September, October—every Wednesday, Friday, Saturday and Sunday, July 4th</ENT>
                                <ENT>North Atlantic Ocean, Virginia Beach, VA, Safety Zone A</ENT>
                                <ENT>All waters of the Atlantic Ocean within a 1000 yard radius of the center located near the shoreline at approximate position latitude 36°51′12″ N, longitude 075°58′06″ W, located off the beach between 17th and 31st streets.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">16</ENT>
                                <ENT>September—4th Saturday or October—1st Saturday</ENT>
                                <ENT>North Atlantic Ocean, VA Beach, VA, Safety Zone B</ENT>
                                <ENT>All waters of the Atlantic Ocean within a 350 yard radius of approximate position latitude 36°50′35″ N, longitude 075°58′09″ W, located on the 14th Street Fishing Pier.</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="66247"/>
                                <ENT I="01">17</ENT>
                                <ENT>Friday, Saturday, Sunday and Monday—Labor Day Weekend </ENT>
                                <ENT>North Atlantic Ocean, VA Beach, VA, Safety Zone C</ENT>
                                <ENT>All waters of the Atlantic Ocean within a 350 yard radius of approximate position latitude 36°49′55″ N, longitude 075°58′00″ W, located off the beach between 2nd and 6th streets.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">18</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>Nansemond River, Suffolk, VA, Safety Zone</ENT>
                                <ENT>All waters of the Nansemond River within a 350 yard radius of approximate position latitude 36°44′27″ N, longitude 076°34′42″ W, located near Constant's Wharf in Suffolk, VA.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">19</ENT>
                                <ENT>February—4th Saturday, July 4th</ENT>
                                <ENT>Chickahominy River, Williamsburg, VA, Safety Zone</ENT>
                                <ENT>All waters of the Chickahominy River within a 400 yard radius of the fireworks display in approximate position latitude 37°14′50″ N, longitude 076°52′17″ W, near Barrets Point, Virginia.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">20</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>James River, Williamsburg, VA, Safety Zone</ENT>
                                <ENT>All waters of the James River within a 350 yard radius of approximate position latitude 37°13′23.3″ N, longitude 076°40′11.8″ W, located near Kingsmill Resort.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">21</ENT>
                                <ENT>July—3rd, 4th and 5th</ENT>
                                <ENT>Great Wicomico River, Mila, VA, Safety Zone</ENT>
                                <ENT>All waters of the Great Wicomico River located within a 420 foot radius of the fireworks display at approximate position latitude 37°50′31″ N, longitude 076°19′42″ W near Mila, Virginia.</ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="01">22</ENT>
                                <ENT>July—1st Friday, Saturday and Sunday</ENT>
                                <ENT>Cockrell's Creek, Reedville, VA, Safety Zone</ENT>
                                <ENT>All waters of Cockrell's Creek located within a 420 foot radius of the fireworks display at approximate position latitude 37°49′54″ N, longitude 076°16′44″ W near Reedville, Virginia.</ENT>
                            </ROW>
                            <ROW EXPSTB="03" RUL="s">
                                <ENT I="21">
                                    <E T="02">(d.) Coast Guard Sector North Carolina—COTP Zone</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="01">1</ENT>
                                <ENT>July 4th, October—1st Friday</ENT>
                                <ENT>Morehead City Harbor Channel, NC, Safety Zone</ENT>
                                <ENT>All waters of the Morehead City Harbor Channel that fall within a 360 yard radius of latitude 34°43′01″ N, longitude 076°42′59.6″ W, a position located at the west end of Sugar Loaf Island, NC.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">2</ENT>
                                <ENT>April—2nd Saturday, July 4th, August—3rd Monday, October—1st Friday</ENT>
                                <ENT>Cape Fear River, Wilmington, NC, Safety Zone</ENT>
                                <ENT>All waters of the Cape Fear River within an area bound by a line drawn from the following points: latitude 34°13′54″ N, longitude 077°57′06″ W; thence northeast to latitude 34°13′57″ N, longitude 077°57′05″ W; thence north to latitude 34°14′11″ N, longitude 077°57′07″ W; thence northwest to latitude 34°14′22″ N, longitude 077°57′19″ W; thence east to latitude 34°14'22″ N, longitude 077°57′06″ W; thence southeast to latitude 34°14′07″ N, longitude 077°57′00″ W; thence south to latitude 34°13′54″ N, longitude 077°56′58″ W; thence to the point of origin, located approximately 500 yards north of Cape Fear Memorial Bridge.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">3</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>Green Creek and Smith Creek, Oriental, NC, Safety Zone</ENT>
                                <ENT>All waters of Green Creek and Smith Creek that fall within a 300 yard radius of the fireworks launch site at latitude 35°01′29.6″ N, longitude 076°42′10.4″ W, located near the entrance to the Neuse River in the vicinity of Oriental, NC.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">4</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>Pasquotank River, Elizabeth City, NC, Safety Zone</ENT>
                                <ENT>All waters of the Pasquotank River within a 300 yard radius of the fireworks launch site in approximate position latitude 36°18′00″ N, longitude 076°13′00″ W, approximately 200 yards south of the east end of the Elizabeth City Bascule Bridges.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">5</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>Currituck Sound, Corolla, NC, Safety Zone</ENT>
                                <ENT>All waters of the Currituck Sound within a 300 yard radius of the fireworks barge in approximate position latitude 36°22′48″ N, longitude 075°51′15″ W.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">6</ENT>
                                <ENT>July 4th, November—3rd Saturday</ENT>
                                <ENT>Middle Sound, Figure Eight Island, NC, Safety Zone</ENT>
                                <ENT>All waters of the Figure Eight Island Causeway Channel from latitude 34°16′32″ N, longitude 077°45′32″ W, thence east along the marsh to a position located at latitude 34°16′19″ N, longitude 077°44′55″ W, thence south to the causeway at position latitude 34°16′16″ N, longitude 077°44′58″ W, thence west along the shoreline to position latitude 34°16′29″ N, longitude 077°45′34″ W, thence back to the point of origin.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">7</ENT>
                                <ENT>June—2nd Saturday, July—1st Saturday after July 4th</ENT>
                                <ENT>Pamlico River, Washington, NC, Safety Zone</ENT>
                                <ENT>All waters of the Pamlico River that fall within a 300 yard radius of the fireworks launch site at latitude 35°32′27″ N, longitude 077°03′40.5″ W, located 500 yards north of Washington railroad trestle bridge.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">8</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>Neuse River, New Bern, NC, Safety Zone</ENT>
                                <ENT>All waters of the Neuse River within a 360 yard radius of the fireworks barge in approximate position latitude 35°06′07.1″ N, longitude 077°01′35.8″ W, located 420 yards north of the New Bern, Twin Span, high rise bridge.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">9</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>Edenton Bay, Edenton, NC, Safety Zone</ENT>
                                <ENT>All waters within a 300 yard radius of position latitude 36°03′04″ N, longitude 076°36′18″ W, approximately 150 yards south of the entrance to Queen Anne Creek, Edenton, NC.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">10</ENT>
                                <ENT>July 4th, November—Saturday following Thanksgiving</ENT>
                                <ENT>Motts Channel, Banks Channel, Wrightsville Beach, NC, Safety Zone</ENT>
                                <ENT>All waters of Motts Channel within a 500 yard radius of the fireworks launch site in approximate position latitude 34°12′29″ N, longitude 077°48′27″ W, approximately 560 yards south of Sea Path Marina, Wrightsville Beach, NC.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">11</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>Cape Fear River, Southport, NC, Safety Zone</ENT>
                                <ENT>All waters of the Cape Fear River within a 600 yard radius of the fireworks barge in approximate position latitude 33°54′40″ N, longitude 078°01′18″ W, approximately 700 yards south of the waterfront at Southport, NC.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">12</ENT>
                                <ENT>July 4th</ENT>
                                <ENT>Big Foot Slough, Ocracoke, NC, Safety Zone</ENT>
                                <ENT>All waters of Big Foot Slough within a 300 yard radius of the fireworks launch site in approximate position latitude 35°06′54″ N, longitude 075°59′24″ W, approximately 100 yards west of the Silver Lake Entrance Channel at Ocracoke, NC.</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="66248"/>
                                <ENT I="01">13</ENT>
                                <ENT>August—1st Tuesday</ENT>
                                <ENT>New River, Jacksonville, NC, Safety Zone</ENT>
                                <ENT>All waters of the New River within a 300 yard radius of the fireworks launch site in approximate position latitude 34°44′45″ N, longitude 077°26′18″ W, approximately one half mile south of the Hwy 17 Bridge, Jacksonville, North Carolina.</ENT>
                            </ROW>
                        </GPOTABLE>
                    </SECTION>
                    <SIG>
                        <DATED>Dated: September 12, 2011.</DATED>
                        <NAME>William D. Lee,</NAME>
                        <TITLE>Rear Admiral, U.S. Coast Guard, Commander, Fifth Coast Guard District.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27645 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF EDUCATION</AGENCY>
                <CFR>34 CFR Chapter VI</CFR>
                <SUBJECT>Negotiated Rulemaking Committee, Negotiator Nominations and Schedule of Committee Meetings—Teacher Preparation and TEACH Grant Programs</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Postsecondary Education, Department of Education.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Intent to establish negotiated rulemaking committees.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We announce our intention to establish a negotiated rulemaking committee to prepare proposed regulations under Title II and Title IV of the Higher Education Act of 1965, as amended (HEA). The committee will include representatives of organizations or groups with interests that are significantly affected by the topics proposed for negotiation. We request nominations for individual negotiators who represent key stakeholder constituencies for the issues to be negotiated to serve on the committee and we set a schedule for committee meetings.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        We must receive your nominations for negotiators to serve on the committee on or before November 25, 2011. The dates, times, and locations of the committee meetings are set out in the 
                        <E T="03">Schedule for Negotiations</E>
                         section under 
                        <E T="02">SUPPLEMENTARY INFORMATION,</E>
                         below.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Please send your nominations for negotiators to Wendy Macias, U.S. Department of Education, 1990 K Street, NW., room 8017, Washington, DC 20006, or by fax at (202) 502-7874. You may also e-mail your nominations to 
                        <E T="03">Wendy.Macias@ed.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For information about the content of this notice, including information about the negotiated rulemaking process or the nomination submission process, contact: Wendy Macias, U.S. Department of Education, 1990 K Street, NW., room 8017, Washington, DC 20006. 
                        <E T="03">Telephone:</E>
                         (202) 502-7526. You may also e-mail your questions about the nomination submission process to: 
                        <E T="03">Wendy.Macias@ed.gov.</E>
                    </P>
                    <NOTE>
                        <HD SOURCE="HED">Note:</HD>
                        <P>
                             For general information about the negotiated rulemaking process, see 
                            <E T="03">The Negotiated Rulemaking Process for Title IV Regulations, Frequently Asked Questions</E>
                             at 
                            <E T="03">http://www.ed.gov/policy/highered/reg/hearulemaking/hea08/neg-reg-faq.html.</E>
                        </P>
                    </NOTE>
                    <P>If you use a telecommunications device for the deaf (TDD), call the Federal Relay Service (FRS), toll free at 1-800-877-8339.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On May 5, 2011, we published a notice in the 
                    <E T="04">Federal Register</E>
                     (76 FR 25650) announcing our intent to establish one or more negotiated rulemaking committees to develop proposed regulations under the HEA. In addition, we announced our intent to develop these proposed regulations by following the negotiated rulemaking procedures in Section 492 of the HEA.
                </P>
                <P>
                    The notice also announced a series of three regional hearings at which interested parties could comment on the topics suggested by the Department and suggest additional topics for consideration for action by the negotiating committees. We also held four public roundtable discussions to complement the regional hearings. The hearings and roundtables were held in: Nashville, Tennessee (roundtable only); Tacoma, Washington; Chicago, Illinois; and Charleston, South Carolina. We invited parties to comment and submit topics for consideration in writing as well. (Transcripts from the regional hearings can be found at 
                    <E T="03">http://www2.ed.gov/policy/highered/reg/hearulemaking/2011/hearings.html.</E>
                     Written comments may be viewed through the Federal eRulemaking Portal at 
                    <E T="03">http://www.regulations.gov.</E>
                     Instructions for finding comments are available on the site under “How to Use 
                    <E T="03">Regulations.gov”</E>
                     in the Help section. Individuals can enter docket ID ED-2011-OPE-0003 in the “Enter Keyword or ID” search box to locate the appropriate docket.) 
                    <E T="03">Regulatory Issues:</E>
                     After consideration of the information received at the regional hearings, in the roundtable discussions, and in writing, we have decided to establish a negotiating committee to address teacher preparation program issues in Title II of the HEA and in the Teacher Education Assistance for College and Higher Education (TEACH) Grant Program authorized by Title IV of the HEA.
                </P>
                <P>
                    We list the topics the committee is likely to address in the 
                    <E T="03">Committee Topics</E>
                     section, below.
                </P>
                <P>We intend to select negotiators for the committee who represent the interests significantly affected by the topics proposed for negotiations. In so doing, we will follow the requirement in Section 492(b)(1) of the HEA that the individuals selected must have demonstrated expertise or experience in the relevant subjects under negotiation. We will also select individual negotiators who reflect the diversity among program participants, in accordance with Section 492(b)(1) of the HEA. Our goal is to establish a committee that will allow significantly affected parties to be represented while keeping the committee size manageable.</P>
                <P>The committee may create subgroups on particular topics that may involve additional individuals who are not members of the committee. Individuals who are not selected as members of the committee will be able to attend the meetings, have access to the individuals representing their constituencies, and participate in informal working groups on various issues between the meetings. The committee meetings will be open to the public.</P>
                <P>The Department has identified the following constituencies as having interests that are significantly affected by the topics proposed for negotiations. The Department plans to seat as negotiators individuals from organizations or groups representing these constituencies:</P>
                <P>• Postsecondary students, including legal assistance organizations that represent students.</P>
                <P>
                    • Teachers.
                    <PRTPAGE P="66249"/>
                </P>
                <P>• Financial aid administrators at postsecondary institutions.</P>
                <P>• Business officers and bursars at postsecondary institutions.</P>
                <P>• Admissions officers at postsecondary institutions.</P>
                <P>• State officials, including officials with teacher preparation program approval agencies, State teacher licensing boards, higher education executive officers, chief State school officers, State attorneys general, and State data system administrators.</P>
                <P>• Institutions that offer teacher preparation programs, including schools of education.</P>
                <P>○ Institutions of higher education eligible to receive Federal assistance under Title III, Parts A, B, and F, and Title V of the HEA, which include Historically Black Colleges and Universities, Hispanic-Serving Institutions, American Indian Tribally Controlled Colleges and Universities, Alaska Native and Native Hawaiian-Serving Institutions, Predominantly Black Institutions, and other institutions with a substantial enrollment of needy students as defined in Title III of the HEA.</P>
                <P>○ Two-year public institutions of higher education.</P>
                <P>○ Four-year public institutions of higher education.</P>
                <P>○ Private, non-profit institutions of higher education.</P>
                <P>○ Private, for-profit institutions of higher education.</P>
                <P>• Operators of programs for alternative routes to teacher certification.</P>
                <P>• Accrediting agencies.</P>
                <P>• Students enrolled in elementary and secondary education, including parents of students enrolled in elementary and secondary education.</P>
                <P>• School and local educational agency officials, including those responsible for hiring teachers and evaluating teacher performance.</P>
                <P>The goal of the committee is to develop high-quality proposed regulations that reflect a final consensus of the committee. Consensus means that there is no dissent by any member of the negotiating committee, including the committee member representing the Department. An individual selected as a negotiator will be expected to represent the interests of their organization or group. If consensus is reached, all members of the organization or group represented by a negotiator are bound by the consensus and are prohibited from commenting negatively on the resulting proposed regulations. The Department will not consider any such negative comments that are submitted by members of such an organization or group.</P>
                <HD SOURCE="HD1">Nominations</HD>
                <P>Nominations should include:</P>
                <P>• The name of the nominee, the organization or group the nominee represents, and a description of the interests that the nominee represents.</P>
                <P>• Evidence of the nominee's expertise or experience in the subject, or subjects, to be negotiated.</P>
                <P>• Evidence of support from individuals or groups of the constituency that the nominee will represent.</P>
                <P>• The nominee's commitment that he or she will actively participate in good faith in the development of the proposed regulations.</P>
                <P>• The nominee's contact information, including address, phone number, fax number, and e-mail address.</P>
                <P>
                    For a better understanding of the negotiated rulemaking process, nominees should review 
                    <E T="03">The Negotiated Rulemaking Process for Title IV Regulations, Frequently Asked Questions</E>
                     at 
                    <E T="03">http://www.ed.gov/policy/highered/reg/hearulemaking/hea08/neg-reg-faq.html</E>
                     prior to committing to serve as a negotiator.
                </P>
                <P>Nominees will be notified whether or not they have been selected as negotiators as soon as the Department's review process is completed.</P>
                <HD SOURCE="HD1">Committee Topics</HD>
                <P>The topics the committee is likely to address are as follows:</P>
                <P>• The requirements for institutional and program report cards on the quality of teacher preparation (Section 205(a) of the HEA);</P>
                <P>• The requirements for State report cards on the quality of teacher preparation (Section 205(b) of the HEA);</P>
                <P>• The standards to ensure reliability, validity, and accuracy of the data submitted in report cards on the quality of teacher preparation (Section 205(c) of the HEA);</P>
                <P>• The criteria used by States to assess the performance of teacher preparation programs at higher education institutions in the State, the identification of low-performing programs (Section 207(a) of the HEA), and the consequences of a State's termination of eligibility of a program (Section 207(b) of the HEA);</P>
                <P>• The definition of the term “high quality teacher preparation program” for the purpose of establishing the eligibility of an institution to participate in the TEACH Grant program (Section 420L(1) of the HEA);</P>
                <P>• The definition of the term “high quality professional development services” for the purpose of establishing the eligibility of an institution to participate in the TEACH Grant program (Section 420L(1) of the HEA); and</P>
                <P>• The service and repayment obligations for the TEACH Grant Program (Subpart E of 34 CFR 686).</P>
                <P>These topics are tentative. Topics may be added or removed as the process continues.</P>
                <HD SOURCE="HD1">Schedule for Negotiations</HD>
                <P>The committee will meet for three sessions on the following dates:</P>
                <P>
                    <E T="03">Session 1:</E>
                     January 18-20, 2012.
                </P>
                <P>
                    <E T="03">Session 2:</E>
                     February 27-29, 2012.
                </P>
                <P>
                    <E T="03">Session 3:</E>
                     April 3-5, 2012.
                </P>
                <P>The first and second day of each session will begin at 9 a.m. and end around 5 p.m. The final day of each session will begin at 9 a.m. and end at 12 p.m. </P>
                <P>The meetings will be held at the U.S. Department of Education at: 1990 K Street, NW., Eighth Floor Conference Center, Washington, DC 20006.</P>
                <P>
                    <E T="03">Accessible Format:</E>
                     Individuals with disabilities can obtain this document in an accessible format (
                    <E T="03">e.g.,</E>
                     braille, large print, audiotape, or compact disc) by contacting the contact person under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT.</E>
                </P>
                <P>
                    <E T="03">Electronic Access to This Document:</E>
                     The official version of this document is the document published in the 
                    <E T="04">Federal Register.</E>
                     Free internet access to the official edition of the 
                    <E T="04">Federal Register</E>
                     and the Code of Federal Regulations is available via the 
                    <E T="03">Federal Digital System</E>
                     at: 
                    <E T="03">http://www.gpo.gov/fdsys.</E>
                     At this site you can view this document, as well as all other documents of this Department published in the 
                    <E T="04">Federal Register,</E>
                     in text or Adobe Portable Document Format (PDF). To use PDF, you must have Adobe Acrobat Reader, which is available free at this site.
                </P>
                <P>
                    You may also access documents of the Department published in the 
                    <E T="04">Federal Register</E>
                     by using the article search feature at 
                    <E T="03">http://www.federalregister.gov.</E>
                     Specifically, through the advanced search feature at this site, you can limit your search to documents published by the Department.
                </P>
                <AUTH>
                    <HD SOURCE="HED">Program Authority:</HD>
                    <P>
                        20 U.S.C. 1021 
                        <E T="03">et seq.,</E>
                         1070g 
                        <E T="03">et seq.,</E>
                         1098a.
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: October 21, 2011.</DATED>
                    <NAME>Eduardo M. Ochoa,</NAME>
                    <TITLE>Assistant Secretary for Postsecondary Education.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27719 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4000-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="66250"/>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <CFR>47 CFR Part 73</CFR>
                <DEPDOC>[MB Docket No. 11-159, RM-11644; DA 11-1690]</DEPDOC>
                <SUBJECT>Television Broadcasting Services; Cleveland, OH</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>The Commission has before it a petition for rulemaking filed by Community Television of Ohio License, LLC (“Community Television”), the licensee of station WJW (TV), channel 8, Cleveland, Ohio, requesting the substitution of channel 31 for channel 8 at Cleveland. Community Television is seeking the channel substitution because a sizeable number of the station's viewers in areas southwest of the station's transmitter were not able to receive the station's over-the-air signal after it terminated analog service on June 12, 2009, and commenced post-transition digital service on its VHF channel. Many viewers reporting difficulty receiving WJW (TV)'s signal report they have no difficulty receiving the UHF stations in the area. Channel 31 was selected because this was Community Television's pre-transition digital channel and it has retained much of the channel 31 transmission equipment.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be filed on or before November 25, 2011, and reply comments on or before December 12, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Federal Communications Commission, Office of the Secretary, 445 12th Street, SW., Washington, DC 20554. In addition to filing comments with the FCC, interested parties should serve counsel for petitioner as follows: Scott S. Patrick, Esq., Dow Lohnes PLLC, 1200 New Hampshire Avenue, NW., Suite 800, Washington, DC 20036-6802.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Joyce L. Bernstein, 
                        <E T="03">joyce.bernstein@fcc.gov,</E>
                         Media Bureau, (202) 418-1647.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This is a synopsis of the Commission's Notice of Proposed Rule Making, MB Docket No. 11-159, adopted October 7, 2011, and released October 11, 2011. The full text of this document is available for public inspection and copying during normal business hours in the FCC's Reference Information Center at Portals II, CY-A257, 445 12th Street, SW., Washington, DC 20554. This document will also be available via ECFS (
                    <E T="03">http://www.fcc.gov/cgb/ecfs/</E>
                    ). (Documents will be available electronically in ASCII, Word 97, and/or Adobe Acrobat.) This document may be purchased from the Commission's duplicating contractor, Best Copy and Printing, Inc., 445 12th Street, SW., Room CY-B402, Washington, DC 20554, telephone 1-800-478-3160 or via e-mail 
                    <E T="03">www.BCPIWEB.com.</E>
                     To request this document in accessible formats (computer diskettes, large print, audio recording, and Braille), send an e-mail to 
                    <E T="03">fcc504@fcc.gov</E>
                     or call the Commission's Consumer and Governmental Affairs Bureau at (202) 418-0530 (voice), (202) 418-0432 (TTY). This document does not contain proposed information collection requirements subject to the Paperwork Reduction Act of 1995, Public Law 104-13. In addition, therefore, it does not contain any proposed information collection burden “for small business concerns with fewer than 25 employees,” pursuant to the Small Business Paperwork Relief Act of 2002, Public Law 107-198, 
                    <E T="03">see</E>
                     44 U.S.C. 3506(c)(4).
                </P>
                <P>
                    Provisions of the Regulatory Flexibility Act of 1980 do not apply to this proceeding. Members of the public should note that from the time a Notice of Proposed Rule Making is issued until the matter is no longer subject to Commission consideration or court review, all 
                    <E T="03">ex parte</E>
                     contacts (other than 
                    <E T="03">ex parte</E>
                     presentations exempt under 47 CFR 1.1204(a)) are prohibited in Commission proceedings, such as this one, which involve channel allotments. See 47 CFR 1.1208 for rules governing restricted proceedings.
                </P>
                <P>For information regarding proper filing procedures for comments, see 47 CFR 1.415 and 1.420.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 47 CFR Part 73</HD>
                    <P>Television, Television broadcasting.</P>
                </LSTSUB>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Barbara A. Kreisman,</NAME>
                    <TITLE>Chief, Video Division, Media Bureau.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Proposed Rules</HD>
                <P>For the reasons discussed in the preamble, the Federal Communications Commission proposes to amend 47 CFR part 73 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 73—RADIO BROADCAST SERVICES</HD>
                    <P>1. The authority citation for part 73 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED"> Authority: </HD>
                        <P>47 U.S.C. 154, 303, 334, 336, and 339.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 73.622 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                        <P>2. Section 73.622(i), the Post-Transition Table of DTV Allotments under Ohio is amended by removing channel 8 and adding channel 31 at Cleveland.</P>
                    </SECTION>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27592 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Fish and Wildlife Service</SUBAGY>
                <CFR>50 CFR Part 17</CFR>
                <DEPDOC>[FWS-R1-ES-2010-0071; MO 92210-0-0009]</DEPDOC>
                <RIN>RIN 1018-AX16</RIN>
                <SUBJECT>Endangered and Threatened Wildlife and Plants; Designation of Critical Habitat for Lepidium papilliferum (Slickspot Peppergrass)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Fish and Wildlife Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule; reopening of comment period.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        We, the U.S. Fish and Wildlife Service (Service), announce the reopening of the comment period on our May 10, 2011, proposal to designate critical habitat for 
                        <E T="03">Lepidium papilliferum</E>
                         (slickspot peppergrass) under the Endangered Species Act of 1973, as amended (Act). We also announce the availability of a draft economic analysis (DEA) of the proposed designation and an amended required determinations section of the proposal. We are reopening the comment period to allow all interested parties an opportunity to comment simultaneously on the proposed rule, the associated DEA, and the amended required determinations section. Comments previously submitted on this rulemaking do not need to be resubmitted, as they will be fully considered in preparation of the final rule.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We will consider comments received on or before December 12, 2011. Comments must be received by 11:59 p.m. Eastern Time on the closing date. Any comments that we receive after the closing date may not be considered in the final decision on this action.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        <E T="03">Document availability:</E>
                         You may obtain a copy of the DEA via 
                        <E T="03">http://www.regulations.gov</E>
                         at Docket No. FWS-R1-ES-2010-0071 or by contacting the office listed under 
                        <E T="02">FOR FURTHER INFORMATION CONTACT.</E>
                        <PRTPAGE P="66251"/>
                    </P>
                    <P>
                        <E T="03">Comment submission:</E>
                         You may submit comments by one of the following methods:
                    </P>
                    <P>
                        (1) 
                        <E T="03">Electronically:</E>
                         Go to the Federal eRulemaking Portal at 
                        <E T="03">http://www.regulations.gov.</E>
                         In the box that reads “Enter Keyword or ID,” enter the docket number for this proposed rule, which is FWS-R1-ES-2010-0071, and then click the Search button. You should then see an icon that reads “Submit a Comment.” Please ensure that you have found the correct rulemaking before submitting your comment.
                    </P>
                    <P>
                        (2) 
                        <E T="03">By hard copy:</E>
                         Submit by U.S. mail or hand-delivery to: Public Comments Processing, Attn: FWS-R1-ES-2010-0071; Division of Policy and Directives Management; U.S. Fish and Wildlife Service; 4401 N. Fairfax Drive, MS 2042-PDM; Arlington, VA 22203.
                    </P>
                    <P>
                        We will post all comments on 
                        <E T="03">http://www.regulations.gov.</E>
                         This generally means that we will post any personal information you provide us (see the Public Comments section below for more information).
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Brian T. Kelly, State Supervisor, Idaho Fish and Wildlife Office, 1387 S. Vinnell Way, Room 368, Boise, ID 83709, by telephone (208-378-5243), or by facsimile (208-378-5262). Persons who use a telecommunications device for the deaf (TDD) may call the Federal Information Relay Service (FIRS) at 800-877-8339.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Public Comments</HD>
                <P>
                    We will accept written comments and information during this reopened comment period on our proposed critical habitat for 
                    <E T="03">Lepidium papilliferum</E>
                     that was published in the 
                    <E T="04">Federal Register</E>
                     on May 10, 2011 (76 FR 27184), our DEA of the proposed designation, and the amended required determinations provided in this document. We will consider information and recommendations from all interested parties. We are particularly interested in comments concerning:
                </P>
                <P>(1) The reasons why we should or should not designate habitat as “critical habitat” under section 4 of the Act, including whether there are threats to the species from human activity, the degree to which threats from human activity can be expected to increase due to the designation, and whether that increase in threats outweighs the benefit of designation such that the designation of critical habitat may not be prudent.</P>
                <P>(2) Specific information on:</P>
                <P>
                    (a) The amount and distribution of 
                    <E T="03">Lepidium papilliferum</E>
                     habitat;
                </P>
                <P>
                    (b) What areas occupied at the time of listing and that contain features essential to the conservation of 
                    <E T="03">Lepidium papilliferum</E>
                     should be included in the designation and why;
                </P>
                <P>(c) The habitat components (primary constituent elements) essential to the conservation of the species, such as specific soil characteristics, plant associations, or pollinators, and the quantity and spatial arrangement of these features on the landscape needed to provide for the conservation of the species;</P>
                <P>(d) What areas not occupied at the time of listing are essential for the conservation of the species, if any, and why; and</P>
                <P>
                    (e) Special management considerations or protections that the features essential to the conservation of 
                    <E T="03">Lepidium papilliferum</E>
                     may require, including managing for the potential effects of climate change.
                </P>
                <P>(3) Land use designations and current or planned activities in the proposed critical habitat areas and their possible impacts on proposed critical habitat.</P>
                <P>(4) Any reasonably foreseeable economic, national security, or other relevant impacts that may result from designating any area that may be included in the final designation. We are particularly interested in any impacts on small entities, and the benefits of including or excluding areas from the proposed designation that are subject to these impacts.</P>
                <P>(5) Information on whether the benefits of an exclusion of any particular area outweigh the benefits of inclusion under section 4(b)(2) of the Act, after considering both the potential impacts and benefits of the proposed critical habitat designation. Under section 4(b)(2) of the Act, we may exclude an area from critical habitat if we determine that the benefits of such exclusion outweigh the benefits of including that particular area as critical habitat, unless failure to designate that specific area as critical habitat will result in the extinction of the species. We are considering the possible exclusion of areas under private ownership, in particular, as we anticipate the benefits of exclusion may outweigh the benefits of inclusion in those areas. We therefore request specific information on:</P>
                <P>(a) The benefits of including any specific areas in the final designation and supporting rationale,</P>
                <P>(b) The benefits of excluding any specific areas from the final designation and supporting rationale, and</P>
                <P>(c) Whether any specific exclusions may result in the extinction of the species and why (see “Consideration of Impacts Under Section 4(b)(2) of the Act,” below).</P>
                <P>
                    (6) The use of Public Land Survey System quarter-quarter sections to delineate the proposed critical habitat designation. We used quarter-quarter sections in this proposed rule because they are the most-commonly-used minimum size and method for delineating land ownership boundaries within the range of 
                    <E T="03">Lepidium papilliferum.</E>
                </P>
                <P>
                    (7) The projected and reasonably likely impacts of climate change on 
                    <E T="03">Lepidium papilliferum</E>
                     and on the critical habitat areas we are proposing.
                </P>
                <P>(8) Whether we could improve or modify our approach to designating critical habitat in any way to provide for greater public participation and understanding, or to better accommodate public concerns and comment.</P>
                <P>(9) Information on the extent to which the description of economic impacts in the DEA is reasonable and accurate.</P>
                <P>(10) The likelihood of adverse social reactions to the designation of critical habitat, as discussed in the DEA, and how the consequences of such reactions, if likely to occur, would relate to the conservation and regulatory benefits of the proposed critical habitat designation.</P>
                <P>If you submitted comments or information on the proposed rule (76 FR 27184) during the initial or extended comment period (76 FR 39807) that was open from May 11 through September 9, 2011, please do not resubmit them. We will incorporate them into the public record as part of this comment period, and we will fully consider them in the preparation of our final determination. Our final determination concerning critical habitat will take into consideration all written comments and any additional information we receive during all comment periods. On the basis of public comments, we may, during the development of our final determination, find that areas proposed are not essential, are appropriate for exclusion under section 4(b)(2) of the Act, or are not appropriate for exclusion.</P>
                <P>
                    You may submit your comments and materials concerning the proposed rule or DEA by one of the methods listed in 
                    <E T="02">ADDRESSES</E>
                    . We request that you send comments only by the methods described in 
                    <E T="02">ADDRESSES</E>
                    .
                </P>
                <P>
                    If you submit a comment via 
                    <E T="03">http://www.regulations.gov,</E>
                     your entire comment—including any personal identifying information—will be posted on the Web site. We will post all hardcopy comments on 
                    <E T="03">http://www.regulations.gov</E>
                     as well. If you 
                    <PRTPAGE P="66252"/>
                    submit a hardcopy comment that includes personal identifying information, you may request at the top of your document that we withhold this information from public review. However, we cannot guarantee that we will be able to do so.
                </P>
                <P>
                    Comments and materials we receive, as well as supporting documentation we used in preparing the proposed rule and DEA, will be available for public inspection on 
                    <E T="03">http://www.regulations.gov</E>
                     at Docket No. FWS-R1-ES-2010-0071, or by appointment, during normal business hours, at the U.S. Fish and Wildlife Service, Idaho Fish and Wildlife Office (see 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    ). You may obtain copies of the proposed rule and the DEA on the Internet at 
                    <E T="03">http://www.regulations.gov</E>
                     at Docket Number FWS-R1-ES-2010-0071, or by mail from the Idaho Fish and Wildlife Office (see 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    ).
                </P>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    It is our intent to discuss only those topics directly relevant to the designation of critical habitat for 
                    <E T="03">Lepidium papilliferum</E>
                     in this document. For more information on previous Federal actions concerning 
                    <E T="03">L. papilliferum,</E>
                     refer to the proposed designation of critical habitat published in the 
                    <E T="04">Federal Register</E>
                     on May 10, 2011 (76 FR 27184). For more information on 
                    <E T="03">L. papilliferum</E>
                     or its habitat, please refer to the final listing rule published in the 
                    <E T="04">Federal Register</E>
                     on October 8, 2009 (74 FR 52014), which is available online at 
                    <E T="03">http://www.regulations.gov</E>
                     at Docket No. FWS-R1-ES-2010-0071 or from the Idaho Fish and Wildlife Office (see 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    ).
                </P>
                <HD SOURCE="HD2">Previous Federal Actions</HD>
                <P>
                    On May 10, 2011, we published a proposed rule to designate critical habitat for 
                    <E T="03">Lepidium papilliferum</E>
                     (76 FR 27184). We proposed to designate as critical habitat approximately 23,374 hectares (57,756 acres) in four units in Ada, Elmore, Payette, and Owyhee Counties in Idaho. We announced a 60-day comment period in that proposed rule, scheduled to close on July 11, 2011. On June 1, 2011, we received a request from the Governor of Idaho seeking a 60-day extension of the comment period so that the State of Idaho may coordinate comments between the State agencies that may be affected by critical habitat, and to allow adequate time for citizens to provide input on the proposed critical habitat designation. In response to this request, on July 7, 2011, we announced in the 
                    <E T="04">Federal Register</E>
                     an extension of the comment period for an additional 60 days, until September 9, 2011 (76 FR 39807).
                </P>
                <HD SOURCE="HD3">Critical Habitat</HD>
                <P>Section 3 of the Act defines critical habitat as the specific areas within the geographical area occupied by a species, at the time it is listed in accordance with the Act, on which are found those physical or biological features essential to the conservation of the species and that may require special management considerations or protection, and specific areas outside the geographical area occupied by a species at the time it is listed, upon a determination that such areas are essential for the conservation of the species. If the proposed rule is made final, section 7 of the Act will prohibit destruction or adverse modification of critical habitat by any activity funded, authorized, or carried out by any Federal agency. Federal agencies proposing actions affecting critical habitat must consult with us on the effects of their proposed actions, under section 7(a)(2) of the Act.</P>
                <HD SOURCE="HD3">Consideration of Impacts Under Section 4(b)(2) of the Act</HD>
                <P>Section 4(b)(2) of the Act requires that we designate or revise critical habitat based upon the best scientific data available, after taking into consideration the economic impact, impact on national security, or any other relevant impact of specifying any particular area as critical habitat. We may exclude an area from critical habitat if we determine that the benefits of excluding the area outweigh the benefits of including the area as critical habitat, provided such exclusion will not result in the extinction of the species.</P>
                <P>When considering the benefits of inclusion for an area, we consider the additional regulatory benefits that area would receive from the protection from adverse modification or destruction as a result of actions with a Federal nexus (activities conducted, funded, permitted, or authorized by Federal agencies), the educational benefits of mapping areas containing essential features that aid in the recovery of the listed species, and any benefits that may result from designation due to State or Federal laws that may apply to critical habitat.</P>
                <P>When considering the benefits of exclusion, we consider, among other things, whether exclusion of a specific area is likely to result in conservation; the continuation, strengthening, or encouragement of partnerships; or implementation of a management plan.</P>
                <P>
                    In the case of 
                    <E T="03">Lepidium papilliferum,</E>
                     the benefits of critical habitat include public awareness of the presence of
                    <E T="03"/>
                     the species and the importance of habitat protection, and, where a Federal nexus exists, increased habitat protection for 
                    <E T="03">L. papilliferum</E>
                     due to protection from adverse modification or destruction of critical habitat. In practice, situations with a Federal nexus exist primarily on Federal lands or for projects undertaken by, or with the authorization or permission of, Federal agencies. We are considering the possible exclusion of areas under private ownership from the designation of critical habitat for 
                    <E T="03">L. papilliferum,</E>
                     as we anticipate the benefits of exclusion may outweigh the benefits of inclusion in those areas.
                </P>
                <P>
                    The final decision on whether to exclude any areas will be based on the best scientific data available at the time of the final designation, including information obtained during the comment period and information about the economic impact of designation. Accordingly, we have prepared a draft economic analysis (DEA) concerning the proposed critical habitat designation, which is available for review and comment (see 
                    <E T="02">ADDRESSES</E>
                     section).
                </P>
                <HD SOURCE="HD3">Draft Economic Analysis</HD>
                <P>
                    The DEA identifies and analyzes the potential economic impacts associated with the proposed critical habitat designation for
                    <E T="03"> Lepidium papilliferum.</E>
                     The DEA describes the economic impacts of all potential conservation efforts for 
                    <E T="03">L. papilliferum;</E>
                     some of these costs will likely be incurred regardless of whether we designate critical habitat. The economic impact of the proposed critical habitat designation is analyzed by comparing scenarios both “with critical habitat” and “without critical habitat.” The “without critical habitat” scenario represents the baseline for the analysis, considering protections already in place for the species (e.g., under the Federal listing and other Federal, State, and local regulations). The baseline, therefore, represents the costs incurred regardless of whether critical habitat is designated. The “with critical habitat” scenario describes the incremental impacts associated specifically with the designation of critical habitat for the species. In other words, these incremental impacts would not occur but for the designation.
                </P>
                <P>
                    These incremental impacts produce the costs that we consider in the final designation of critical habitat when evaluating the benefits of excluding particular areas under section 4(b)(2) of the Act. The analysis looks retrospectively at baseline impacts incurred since the species was listed, and forecasts both baseline and incremental impacts likely to occur if 
                    <PRTPAGE P="66253"/>
                    we finalize the proposed critical habitat designation.
                </P>
                <P>As described above, the DEA separates conservation measures into two distinct categories according to “without critical habitat” and “with critical habitat” scenarios. The “without critical habitat” scenario represents the baseline for the analysis, considering protections otherwise afforded to the species (e.g., under the Federal listing and other Federal, State, and local regulations). The “with critical habitat” scenario describes the incremental impacts specifically due to designation of critical habitat for the species. In other words, these incremental conservation measures and associated economic impacts would not occur but for the designation. Conservation measures implemented under the baseline (without critical habitat) scenario are described qualitatively within the DEA, but economic impacts associated with these measures are not quantified. Economic impacts are only quantified for conservation measures implemented specifically due to the designation of critical habitat (i.e., incremental impacts). For a further description of the methodology of the analysis, see Chapter 2, “Framework for the Analysis,” of the DEA.</P>
                <P>
                    The DEA provides estimated costs of the foreseeable potential economic impacts of the proposed critical habitat designation for 
                    <E T="03">Lepidium papilliferum</E>
                     over the next 20 years, from 2012 through 2031. We determined that this 20-year timeframe was the appropriate period for analysis because the availability of land-use planning information becomes very limited for most activities beyond that timeframe. The DEA identifies potential incremental costs as a result of the proposed critical habitat designation; these are those costs attributed to critical habitat over and above those baseline costs attributed to listing and other regulatory protections. The DEA quantifies economic impacts of 
                    <E T="03">L. papilliferum</E>
                     conservation efforts associated with the following categories of activity: (1) Wildfire and invasive nonnative species management; (2) commercial and residential development; (3) utility and transportation activities; and (4) livestock use. The most visible effect to 
                    <E T="03">L. papilliferum</E>
                     and its habitat from livestock use is through localized trampling impacts; however, as stated in the final listing rule, under current management conditions we do not consider this activity to represent a significant threat to the species. Although the final listing rule evaluated recreation as a possible minor threat to the species, this does not appear to be a major factor impacting either 
                    <E T="03">L. papilliferum</E>
                     or its habitat. We therefore do not anticipate any measurable economic impact of critical habitat designation for this species on recreation, and this activity was not considered in the draft economic analysis.
                </P>
                <P>
                    Approximately 95 percent of the proposed critical habitat area is on public lands (roughly 86 percent is Federal land managed by the Bureau of Land Management (BLM)). Of this, 8 percent is State land, 2 percent is County land (Payette, Ada, Owyhee, and Elmore counties, Idaho), and the remaining 5 percent covers privately owned lands. Commercial and residential develop could result in the loss of 
                    <E T="03">Lepidium papilliferum</E>
                     populations, as well as indirect losses through the development of infrastructure that allows greater access to the habitat (e.g., off-road vehicles, human-ignited wildfires) and habitat fragmentation. Although no development has taken place within the proposed critical habitat areas since publication of the proposed rule, portions of the critical habitat area are adjacent to urban and rural development, or within the Interstate 84 corridor, increasing the probability that the areas may be subject to future development.
                </P>
                <P>
                    The most significant biological threats to the species are related to increased frequency of wildfire, combined with the invasion of nonnative annual grasses. The invasion of nonnative annual grasses provides a continuous source of fuel, which directly contributes to a dramatic increase in natural fire frequency. Conservation measures related to wildfire and nonnative species have been incorporated into a Conservation Agreement being implemented by the BLM, which applies to 86 percent of the proposed critical habitat area. Rights-of-way and pipeline activities, particularly those related to utilities and transportation activities, became subject to section 7 consultation in 2009, when the species was listed under the Act, and actions are already being reviewed to evaluate potential impacts to the species related to equipment operation or construction within areas occupied by the species. A review of our consultation records indicates that no project modifications have been required to date, either because the activities were not within 
                    <E T="03">Lepidium papilliferum</E>
                     habitat, or conservation measures were incorporated into project designs to avoid impacts to the species or its habitat.
                </P>
                <P>The draft economic analysis concludes that critical habitat designation is not likely to affect levels of economic activity or conservation measures being implemented within the proposed critical habitat area. Unless changes occur to existing conservation measures or the management of land use activities, the incremental impacts of critical habitat designation would be limited to the additional administrative costs of section 7 consultations for Federal agencies, associated with considering the potential for adverse modification of critical habitat. These costs are estimated to be $14,200 annually, or $161,000 over a 20-year period, based on the present value discounted at seven percent.</P>
                <P>
                    Because approximately 86 percent of the proposed critical habitat area is Federal land managed by the BLM, the proposed critical habitat designation is unlikely to generate economic impacts beyond administrative costs of section 7 consultation. Additionally, a binding Conservation Agreement has been developed to address the conservation needs of this species on BLM land, and BLM already consults with us under section 7 of the Act to ensure their activities do not jeopardize the continued existence of the species. The BLM intends to continue to manage these lands for conservation of 
                    <E T="03">Lepidium papilliferum,</E>
                     by implementing the specific conservation measures identified in Chapter 3 of the draft economic analysis. In addition, project proponents and land managers are aware of the species' presence throughout its range, and the need to consult with the Service for projects that have a Federal nexus that may affect the species. We believe activities on private lands are unlikely to have a Federal nexus or be subject to section 7 consultation, based on a review of our consultation records to date. However, in the case that private lands may possibly be subject to a Federal permit or funding source in the future (e.g., U.S. Department of Agriculture, Natural Resources Conservation Service programs or Federal permitting of alternative energy projects), the DEA underestimates potential administrative costs due to critical habitat designation in the 5 percent of proposed critical habitat that overlaps the private lands. However, we have no information indicating that any such activity will occur on private lands in the foreseeable future.
                </P>
                <P>
                    In conclusion, the Service does not foresee a circumstance in which critical habitat designation will change the outcome of future section 7 consultations. Any conservation 
                    <PRTPAGE P="66254"/>
                    measures implemented to minimize impacts to the species would very likely be sufficient to also minimize impacts to critical habitat. Therefore, we do not believe any additional conservation measures would be needed solely to minimize impacts to critical habitat. Based on this reasoning, we also do not anticipate critical habitat designation to result in any appreciable incremental economic benefits. Any economic benefits related to conservation activities would flow from the listing of the species, rather than the designation of critical habitat, and would fall within the economic baseline.
                </P>
                <P>As we stated earlier, we are soliciting data and comments from the public on the DEA, as well as all aspects of the proposed rule and our amended required determinations. We may revise the proposed rule or supporting documents to incorporate or address information we receive during the public comment period. In particular, we may exclude an area from critical habitat if we determine that the benefits of excluding the area outweigh the benefits of including the area, provided the exclusion will not result in the extinction of the species.</P>
                <HD SOURCE="HD1">Required Determinations—Amended</HD>
                <P>
                    In our May 10, 2011, proposed rule (76 FR 27184), we indicated that we would defer our determination of compliance with several statutes and executive orders until the information concerning potential economic impacts of the designation and potential effects on landowners and stakeholders became available in the DEA. We have now made use of the DEA data to make these determinations. In this document, we affirm the information in our proposed rule concerning Executive Order (E.O.) 12866 (Regulatory Planning and Review), E.O. 12630 (Takings), E.O. 13132 (Federalism), E.O. 12988 (Civil Justice Reform), E.O. 13211 (Energy, Supply, Distribution, and Use), the Unfunded Mandates Reform Act (2 U.S.C. 1501 
                    <E T="03">et seq.</E>
                    ), the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), the National Environmental Policy Act (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), and the President's memorandum of April 29, 1994, “Government-to-Government Relations with Native American Tribal Governments” (59 FR 22951). However, based on the DEA data, we are amending our required determination concerning the Regulatory Flexibility Act (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <HD SOURCE="HD2">Regulatory Flexibility Act</HD>
                <P>Under the Regulatory Flexibility Act, as amended by the Small Business Regulatory Enforcement Fairness Act (5 U.S.C. 802(2)), whenever an agency is required to publish a notice of rulemaking for any proposed or final rule, it must prepare and make available for public comment a regulatory flexibility analysis that describes the effect of the rule on small entities (i.e., small businesses, small organizations, and small government jurisdictions). However, no regulatory flexibility analysis is required if the head of an agency certifies the rule will not have a significant economic impact on a substantial number of small entities. Based on our DEA of the proposed designation, we provide our analysis for determining whether the proposed rule would result in a significant economic impact on a substantial number of small entities. Based on comments we receive, we may revise this determination as part of our final rulemaking.</P>
                <P>According to the Small Business Administration, small entities include small organizations, such as independent nonprofit organizations; small governmental jurisdictions, including school boards and city and town governments that serve fewer than 50,000 residents; and small businesses (13 CFR 121.201). For example, small businesses include manufacturing and mining concerns with fewer than 500 employees, wholesale trade entities with fewer than 100 employees, retail and service businesses with less than $5 million in annual sales, general and heavy construction businesses with less than $27.5 million in annual business, special trade contractors doing less than $11.5 million in annual business, and agricultural businesses with annual sales less than $750,000. To determine if potential economic impacts to these small entities are significant, we considered the types of activities that might trigger regulatory impacts under this designation as well as types of project modifications that may result. In general, the term “significant economic impact” is meant to apply to a typical small business firm's business operations.</P>
                <P>
                    To determine if the proposed designation of critical habitat for 
                    <E T="03">Lepidium papilliferum</E>
                     would affect a substantial number of small entities, we considered the number of small entities affected within particular types of economic activities, such as commercial and residential development. In order to determine whether it is appropriate for our agency to certify that this rule would not have a significant economic impact on a substantial number of small entities, we considered each industry or category individually. In estimating the numbers of small entities potentially affected, we also considered whether their activities have any Federal involvement. Critical habitat designation will not affect activities that do not have any Federal involvement; designation of critical habitat only affects activities conducted, funded, permitted, or authorized by Federal agencies. In areas where 
                    <E T="03">L. papilliferum</E>
                     is present, Federal agencies already are required to consult with us under section 7 of the Act on activities they fund, permit, or implement that may affect the species. If we finalize this proposed critical habitat designation, consultations to avoid the destruction or adverse modification of critical habitat would be incorporated into the existing consultation process.
                </P>
                <P>
                    In the DEA, we evaluated the potential economic effects on small entities resulting from implementation of conservation actions related to the proposed designation of critical habitat for 
                    <E T="03">Lepidium papilliferum.</E>
                     As estimated in Chapter 4 of the DEA, incremental impacts of the proposed designation are limited to additional incremental costs of time spent by the Service, Federal action agency, and any third parties in section 7 consultation over and above time spent on the jeopardy analysis component of the consultation. Small entities may participate in section 7 consultation as a third party (the primary consulting parties being the Service and the Federal action agency); therefore, it is possible that the small entities may spend additional time considering critical habitat during section 7 consultation for 
                    <E T="03">L. papilliferum.</E>
                     These incremental administrative impacts are the only potential incremental impacts of critical habitat designation that may be borne by small entities. Some of the forecast consultations for
                    <E T="03"> L. papilliferum</E>
                     may involve third parties, such as ranchers, energy companies (for pipeline projects), or developers. The maximum annualized incremental impact to such third parties is anticipated to total $2,810 between 2012 and 2031; such costs are expected to be distributed between multiple third parties. While $2,810 is expected to represent the maximum total cost annually, the potential third party cost for each individual consultation is anticipated to be significantly less, on the order of $260 to $1,750 depending on the consultation type. Small entities are consequently anticipated to bear a relatively low cost impact as a result of the designation of critical habitat for 
                    <E T="03">L. papilliferum.</E>
                     We do not believe this designation will have a significant impact on these small entities or affect a substantial number of them. Please 
                    <PRTPAGE P="66255"/>
                    refer to Appendix A of the DEA of the proposed critical habitat designation for a more detailed discussion of potential economic impacts.
                </P>
                <P>In summary, we have considered whether the proposed designation would result in a significant economic impact on a substantial number of small entities. Information for this analysis was gathered from the Small Business Administration, stakeholders, and the Service. For the above reasons and based on currently available information, we certify that if promulgated, the proposed designation would not have a significant economic impact on a substantial number of small business entities. Therefore, an initial regulatory flexibility analysis is not required.</P>
                <HD SOURCE="HD1">Authors</HD>
                <P>The primary authors of this notice are the staff members of the Idaho Fish and Wildlife Office, Pacific Region, U.S. Fish and Wildlife Service.</P>
                <HD SOURCE="HD1">Authority</HD>
                <P>
                    The authority for this action is the Endangered Species Act of 1973, as amended (16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <SIG>
                    <DATED>Dated: October 17, 2011.</DATED>
                    <NAME>Eileen Sobeck,</NAME>
                    <TITLE>Acting Assistant Secretary for Fish and Wildlife and Parks.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27727 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-55-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Fish and Wildlife Service</SUBAGY>
                <CFR>50 CFR Part 17</CFR>
                <DEPDOC>[Docket No. FWS-R8-ES-2011-0066; 92220-1113-0000; ABC Code: C5]</DEPDOC>
                <SUBJECT>Endangered and Threatened Wildlife and Plants; 90-Day Finding on a Petition to Delist the Coastal California Gnatcatcher as Threatened</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Fish and Wildlife Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of 90-day petition finding.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        We, the U.S. Fish and Wildlife Service (Service), announce a 90-day finding on a petition to remove the coastal California gnatcatcher (
                        <E T="03">Polioptila californica californica</E>
                        ) as a threatened species under the Endangered Species Act of 1973, as amended (Act). Based on our review, we find that the petition does not present substantial scientific or commercial information to indicate that delisting the coastal California gnatcatcher may be warranted. Therefore, we are not initiating a status review in response to this petition. We also conclude that the coastal California gnatcatcher constitutes a valid subspecies and are no longer considering whether to propose its reclassification to a distinct population segment (DPS) under the Act. We ask the public to submit to us any new information that becomes available concerning the status of, or threats to, the coastal California gnatcatcher or its habitat at any time.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The finding announced in this document was made on October 26, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        This finding is available on the Internet at 
                        <E T="03">http://www.regulations.gov</E>
                         at Docket Number FWS-R8-ES-2011-0066. Supporting documentation we used in preparing this finding is available for public inspection, by appointment, during normal business hours at the U.S. Fish and Wildlife Service, Carlsbad Fish and Wildlife Office, 6010 Hidden Valley Road, Suite 101, Carlsbad, CA 92011. Please submit any new information, materials, comments, or questions concerning this finding to the above address.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jim Bartel, Field Supervisor, Carlsbad Fish and Wildlife Office, U.S. Fish and Wildlife Service, 6010 Hidden Valley Road, Suite 101, Carlsbad, CA 92011, by telephone at 760-431-9440, or by facsimile to 760-431-9624. Persons who use a telecommunications device for the deaf (TDD) may call the Federal Information Relay Service (FIRS) at 800-877-8339.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    Section 4(b)(3)(A) of the Act (16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ) requires that we make a finding on whether a petition to list, delist, or reclassify a species presents substantial scientific or commercial information indicating that the petitioned action may be warranted. We are to base this finding on information provided in the petition, supporting information submitted with the petition, and information otherwise available in our files. To the maximum extent practicable, we are to make this finding within 90 days of our receipt of the petition, and publish our notice of the finding promptly in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>Our standard for substantial scientific or commercial information within the Code of Federal Regulations (CFR) with regard to a 90-day petition finding is “that amount of information that would lead a reasonable person to believe that the measure proposed in the petition may be warranted” (50 CFR 424.14(b)(1)). If we find that substantial scientific or commercial information was presented, we are required to promptly conduct a species status review, which we subsequently summarize in our 12-month finding.</P>
                <HD SOURCE="HD2">Petition History</HD>
                <P>We received a petition, dated April 9, 2010, from the Pacific Legal Foundation (PLF), representing the Coalition of Labor Agriculture, and Business (COLAB), Property Owners Association of Riverside County, and M. Lou Marsh, M.D., on April 12, 2010, to remove the coastal California gnatcatcher from the Federal List of Endangered and Threatened Wildlife (List) under the Act (PLF 2010, pp. 1-9). The petition clearly identifies itself as such and included the requisite identification information for the petitioner(s), as required in 50 CFR 424.14(a). This finding addresses the petition.</P>
                <HD SOURCE="HD2">Previous Federal Actions</HD>
                <P>
                    The coastal California gnatcatcher has been the subject of numerous 
                    <E T="04">Federal Register</E>
                     publications since its inclusion as a category two candidate species in 1982 (47 FR 58454, December 30, 1982; Service 2010, p. 3) (see 
                    <E T="03">http://ecos.fws.gov/speciesProfile/profile/speciesProfile.action?spcode=B08X</E>
                    ). On March 22, 1991, the Service published a 90-day finding addressing seven petitions to list five species as threatened or endangered, including three petitions pertaining to the coastal California gnatcatcher (56 FR 12146), and concluded that substantial information was presented to indicate that listing might be warranted. This finding led to the September 17, 1991, publication of a proposed rule to list the coastal California gnatcatcher as endangered; the public comment period for this proposed rule lasted 6 months, until March 16, 1992 (56 FR 47053). The proposed rule also constituted our 12-month finding, which the proposed rule referred to as the “final finding”, on the petition.
                </P>
                <P>
                    On September 22, 1992, the Service reopened the public comment period on the proposed rule to list the coastal California gnatcatcher as endangered for an additional 30 days, from September 22, 1992, until October 22, 1992, and notified the public that we needed extra time to obtain and review the information regarding the taxonomy of the coastal California gnatcatcher (57 FR 43686). On March 30, 1993, the Service published a final rule to list the coastal California gnatcatcher as a threatened species (58 FR 16742). In that rule, we 
                    <PRTPAGE P="66256"/>
                    did not designate critical habitat, because we had determined that designating critical habitat for the gnatcatcher was not prudent.
                </P>
                <P>
                    On March 30, 1993, the same day that the final listing rule published in the 
                    <E T="04">Federal Register</E>
                    , we also published a proposed rule to adopt a special rule under section 4(d) of the Act (16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ) to allow for the take of the coastal California gnatcatcher (58 FR 65088). On December 10, 1993, the Service published in the 
                    <E T="04">Federal Register</E>
                     a final rule adopting the special rule concerning take of the coastal California gnatcatcher (58 FR 65088). The special rule is codified in the Code of Federal Regulations (CFR) at 50 CFR 17.41(b).
                </P>
                <P>
                    In a Memorandum Opinion and Order filed in the U.S. District Court for the District of Columbia on May 2, 1994 (
                    <E T="03">Building Industry Association of Southern California et al.</E>
                     v. 
                    <E T="03">Babbitt</E>
                    ), the Court vacated the listing determination for the coastal California gnatcatcher, stating the Secretary of the Interior should have made available the raw data that formed the basis of Dr. Jonathan Atwood's report (Atwood 1991) that concluded subspecies recognition for the coastal California gnatcatcher. We subsequently made these data available to the public for review and comment on June 2, 1994, for a period of 60 days, until August 1, 1994 (59 FR 28508). On June 16, 1994, the Court reinstated the threatened status for the coastal California gnatcatcher until the public could review and comment on the raw data analyzed by Atwood.
                </P>
                <P>
                    Before the comment period for the June 2, 1994, 
                    <E T="04">Federal Register</E>
                     publication ended, we extended that public comment period (59 FR 38426, July 28, 1994), and we subsequently extended it two more times, on August 26, 1994 (59 FR 44125), and October 25, 1994 (59 FR 53628). Therefore, the public comment period on data pertaining to the subspecific taxonomy of the coastal California gnatcatcher lasted from June 2, 1994, until December 1, 1994. Further, on December 27, 1994, we reopened the public comment period on those data for an additional 30 days, until January 26, 1995 (59 FR 66509).
                </P>
                <P>
                    On March 27, 1995, the Service published in the 
                    <E T="04">Federal Register</E>
                     (60 FR 15693) an extensive review of the Atwood data (including independent scientific analyses of the Atwood data) received during the public comment periods concerning the subspecies classification of the coastal California gnatcatcher. We affirmed our earlier determination that the coastal California gnatcatcher is a valid subspecies (58 FR 16742, March 30, 1993; 58 FR 65088, December 10, 1993) and affirmed the coastal California gnatcatcher's threatened status under the Act.
                </P>
                <P>
                    On February 8, 1999, the Service published in the 
                    <E T="04">Federal Register</E>
                     (64 FR 5957) a notice of determination that it was prudent to designate critical habitat for the coastal California gnatcatcher. We subsequently published a proposed rule to designate critical habitat for the coastal California gnatcatcher (65 FR 5945; February 7, 2000); announced a reopening of comment period and availability of a draft economic analysis for the February 7, 2000, proposed rule (65 FR 40073; June 29, 2000); and published a final rule designating critical habitat for the coastal California gnatcatcher (65 FR 63679; October 24, 2000).
                </P>
                <P>
                    In response to a June 11, 2002, court ruling from the U.S. District Court for the Central District of California (
                    <E T="03">Building Industry Association of Southern California et al.</E>
                     v.
                    <E T="03"> Norton</E>
                    ), the Service published a proposed rule to revise designated critical habitat for the coastal California gnatcatcher on April 24, 2003 (68 FR 20228). In this proposed rule, the Service reconsidered the economic impacts associated with designating any particular area as critical habitat, announced that we were considering whether the listing of the coastal California gnatcatcher should be amended as a DPS in light of a study by Zink 
                    <E T="03">et al.</E>
                     (2000) questioning the genetic distinctiveness of the coastal California gnatcatcher, and opened a 60-day period for public comments (68 FR 20228). On April 8, 2004, the Service published two documents related to the coastal California gnatcatcher: The first reopened the public comment period on the proposed determination of a DPS of the coastal California gnatcatcher (69 FR 18515), and the second was a notice of availability of draft economic analysis and a public hearing on the proposed April 24, 2003, designation of critical habitat (69 FR 18516). The Service published its final rule concerning the revised designation of critical habitat on December 19, 2007 (72 FR 72009), for the coastal California gnatcatcher. In that 
                    <E T="04">Federal Register</E>
                     publication, we announced that we were continuing to evaluate whether the current listing of the coastal California gnatcatcher as a subspecies under the Act should be retained or changed.
                </P>
                <P>
                    In 2010, we completed a 5-year status review of the coastal California gnatcatcher (Service 2010, pp. 1-51). After analyzing all available information, including Zink 
                    <E T="03">et al.</E>
                     (2000), we recommended no change in its threatened status and indicated that we would not pursue delineation of a DPS for the coastal California gnatcatcher (Service 2010, p. 36; 
                    <E T="03">http://ecos.fws.gov/docs/five_year_review/doc3571.pdf</E>
                    ). With a recommendation of no change in threatened status, the coastal California gnatcatcher maintains its recovery priority number of 9C, based on the taxon's status as a subspecies facing a high degree of threat with a low recovery potential.
                </P>
                <HD SOURCE="HD2">Species Information</HD>
                <P>
                    For information on the biology and life history of the coastal California gnatcatcher, 
                    <E T="03">see</E>
                     the 2010 coastal California gnatcatcher 5-year review (Service 2010, pp. 6-11).
                </P>
                <HD SOURCE="HD1">Evaluation of Information for This Finding</HD>
                <P>Under section 3(16) of the Act, we may consider for listing any species, including subspecies, of fish, wildlife, or plants, or any DPS of vertebrate fish or wildlife that interbreeds when mature (16 U.S.C. 1532(16)). Such entities are considered eligible for listing under the Act (and, therefore, are referred to as listable entities), should we determine that they meet the definition of an endangered or threatened species.</P>
                <P>Section 4 of the Act (16 U.S.C. 1533) and its implementing regulations at 50 CFR 424 set forth the procedures for adding a species to, or removing a species from the List. A species may be determined to be an endangered or threatened species due to one or more of the five factors described in section 4(a)(1) of the Act:</P>
                <P>(A) The present or threatened destruction, modification, or curtailment of its habitat or range;</P>
                <P>(B) Overutilization for commercial, recreational, scientific, or educational purposes;</P>
                <P>(C) Disease or predation;</P>
                <P>(D) The inadequacy of existing regulatory mechanisms; or</P>
                <P>(E) Other natural or manmade factors affecting its continued existence.</P>
                <P>We must consider these same five factors in delisting a species. We may delist a species according to 50 CFR 424.11(d) if the best available scientific and commercial data indicate that the species is neither endangered nor threatened for the following reasons:</P>
                <P>(1) The species is extinct;</P>
                <P>(2) The species has recovered and is no longer endangered or threatened; or</P>
                <P>(3) The original scientific data used at the time the species was classified were in error.</P>
                <P>
                    In making this 90-day finding, we evaluated whether information 
                    <PRTPAGE P="66257"/>
                    regarding the coastal California gnatcatcher, as presented in the petition and other information available in our files, is substantial, thereby indicating that the petitioned action may be warranted. The petition did not assert that the coastal California gnatcatcher is extinct, nor do we have information in our files indicating that the coastal California gnatcatcher is extinct. The petition did not assert that the coastal California gnatcatcher has recovered and is no longer endangered or threatened, nor do we have information in our files indicating the coastal California gnatcatcher has recovered. The petition also did not contain any information regarding threats to the coastal California gnatcatcher. We recently completed a 5-year status review in which we determined that the threats found at the time of listing remain, and we recommended that the coastal California gnatcatcher retain its threatened status (Service 2010, pp. 11-35). The petition asserts that the original scientific data used at the time the coastal California gnatcatcher was listed as Threatened under the Act were in error. Our evaluation of the information included with the petition is presented below.
                </P>
                <P>
                    The petitioners claim the coastal California gnatcatcher is not a valid subspecies and request we remove the coastal California gnatcatcher from the List. The petitioners present an unpublished literature review prepared for the Pacific Legal Foundation by Dr. Matthew A. Cronin (2009, 
                    <E T="03">in litt.</E>
                     pp. 1-18), which reviewed “* * * post-listing studies to explain why the subspecies classification for the California gnatcatcher is no longer tenable” (PLF 2010, p. 4). The petition presented two published journal articles, Zink 
                    <E T="03">et al.</E>
                     (2000, pp. 1394-1405) and Skalski 
                    <E T="03">et al.</E>
                     (2008, pp. 199-220), supporting three issues of concern raised by Cronin (2009, 
                    <E T="03">in litt.</E>
                     pp. 1-18). The issues of concern raised by Cronin and stated in the petition are:
                </P>
                <P>
                    (1) “Zink 
                    <E T="03">et al.</E>
                     (2000, pp. 1394-1405) determined that Atwood's observed morphological characteristic changes are not representative of genetic differentiation, which differentiation could support a subspecies classification. The Zink study's conclusion is all the more significant given that Atwood was a co-author. In their paper, Zink and Atwood expressly state that 
                    <E T="03">P. californica</E>
                     should have no subspecies.
                </P>
                <P>
                    (2) Skalski 
                    <E T="03">et al.</E>
                     (2008, pp. 199-220) determined that Atwood's statistical analyses were seriously flawed because Atwood's supposed diagnostic characters support a geographic cline, not a distinct break in character distribution markers, which could support a subspecies classification.
                </P>
                <P>
                    (3) Skalski 
                    <E T="03">et al.</E>
                     (2008, pp. 199-220) determined that Atwood's data sets were confounded: many of Atwood's specimens may not have been representative of wild gnatcatchers.”
                </P>
                <P>
                    The first issue presented by the petitioners refers to Zink 
                    <E T="03">et al.</E>
                     (2000, pp. 1394-1405), which asserts that the morphological differences (
                    <E T="03">i.e.,</E>
                     plumage coloration, body size) identified by Atwood (1988, pp. iii-vii, 1-74; 1991, pp. 118-133) do not represent genetic differentiation that supports subspecies classification. Zink 
                    <E T="03">et al.</E>
                     (2000, p. 1399) examined variation within the mitochondrial (mt) mtDNA control region and three mtDNA genes of the coastal California gnatcatcher and concluded the genetic information does not support recognition of the coastal California gnatcatcher as a subspecies. Zink 
                    <E T="03">et al.</E>
                     (2000) does not state that 
                    <E T="03">Polioptila californica</E>
                     should have no subspecies, but instead suggests that currently recognized subspecies may not be equivalent to ecologically significant units.
                </P>
                <P>
                    As a result of uncertainty in the subspecies status of the coastal California gnatcatcher raised by Zink 
                    <E T="03">et al.</E>
                     (2000, pp. 1394-1405), in 2003 and 2004 the Service solicited public comments on a proposed determination of a DPS for the coastal California gnatcatcher (68 FR 20228; 69 FR 18515). Public comments received in 2004 on this issue were highly polarized, though most expressed concern with the validity or usefulness of redefining the coastal California gnatcatcher as a DPS. Some commenters advocated delisting the coastal California gnatcatcher and asserted that the application of the DPS policy was inappropriate. They argued that the information presented by Zink 
                    <E T="03">et al.</E>
                     (2000, pp. 1394-1405) challenging the subspecies classification for the coastal California gnatcatcher superseded over 100 years of previously published taxonomic treatments recognizing morphological distinctiveness to varying degrees within the greater California gnatcatcher taxon, including (Brewster 1881, p. 103; Brewster 1902, p. 210; Thayer and Bangs 1907, p. 138; Grinnell 1926, p. 496; Grinnell 1928, p. 227; van Rossem 1931, p. 35; Hellmayr 1934, p. 508; AOU 1957, p. 451; Miller 
                    <E T="03">et al.</E>
                     1957, pp. 204-205; Mayr and Paynter 1964, pp. 449-450; Atwood 1988, p. 61; Atwood 1991, p. 127; Phillips 1991, p. 25; Mellink and Rea 1994, p. 53; Howell and Webb 1995, p. 578). However, many public commenters advocated the retention of the coastal California gnatcatcher as a listed subspecies and questioned if information from one scientific publication was sufficient to overrule information from multiple, previously published, scientific papers that acknowledge the distinctiveness of the coastal California gnatcatcher and lend support to its retention as a listed subspecies. The Service also received comments from peer-reviewers, the majority of which cautioned against putting too much weight on Zink 
                    <E T="03">et al.'</E>
                    s (2000) conclusions and questioned whether the analysis by Zink 
                    <E T="03">et al.</E>
                     (2000, pp. 1394-1405) supported a change of the coastal California gnatcatcher's subspecific status (2000, pp. 1394-1405).
                </P>
                <P>In 2004, the Service also convened a panel of seven Federal scientists (five Service biologists not associated with the listing of the coastal California gnatcatcher, one Smithsonian Institute biologist, and one National Park Service biologist) to discuss and evaluate how well scientific evidence supports the following statements:</P>
                <P>
                    (1) The coastal California gnatcatcher (
                    <E T="03">Polioptila californica californica</E>
                    ) is a valid subspecies.
                </P>
                <P>(2) The coastal California gnatcatcher is discrete (substantially divergent in physical, physiological, ecological, genetic, or behavioral characters) from other portions of the species.</P>
                <P>(3) Loss of the coastal California gnatcatcher would represent a significant diminution of the species as a whole (in terms of evolutionary legacy or range of biological characteristics represented within the species).</P>
                <P>(4) The coastal California gnatcatcher is neither a valid subspecies nor a discrete and significant portion of the species.</P>
                <P>
                    (5) The mtDNA evidence presented by Zink 
                    <E T="03">et al.</E>
                     (2000) alone constitutes sufficient information to overturn the existing taxonomy.
                </P>
                <P>Overall, panelists supported retaining the coastal California gnatcatcher as a subspecies under the Act for reasons including (but not limited to):</P>
                <P>
                    (1) “There is evidence showing the coastal California gnatcatcher differs in several morphological characters from gnatcatcher populations farther south (body plumage color, tail length, amount of white in tail, and brownish plumage in females). All authorities have recognized it as a distinct taxon based on its physical appearance since it was first described. While some doubt has been cast on recent analyses of morphological data by Atwood (1991), problems with that analysis do not invalidate previous and subsequent morphological work (Grinnell 1926, van 
                    <PRTPAGE P="66258"/>
                    Rossem 1931, Mellink and Rea 1994).” (VanderWerf, 
                    <E T="03">in litt.</E>
                     2004, p. 1).
                </P>
                <P>
                    (2) Although Zink 
                    <E T="03">et al.</E>
                     (2000) concluded that mitochondrial DNA does not support the existence of a subspecies of
                    <E T="03"> Polioptila californica,</E>
                     “mtDNA represents only a single genetic marker among many potential markers that could provide an indication of population subdivision, subspecies, or local adaptation. Other molecular markers with higher mutation rates may reveal more recent patterns of divergence and would be more likely to show population differentiation, such as nuclear genetic markers, which might be linked to selected traits and would be expected to evolve more rapidly than mtDNA. None of these other markers have been investigated” (VanderWerf, 
                    <E T="03">in litt.</E>
                     2004, pp. 1-2).
                </P>
                <P>
                    (3) “Phylogenetic reconstructions and taxonomic determinations should be, and usually are, based on a variety of morphological, genetic (including nuclear and mtDNA), and behavioral evidence.” (VanderWerf, 
                    <E T="03">in litt.</E>
                     2004, p. 2).
                </P>
                <P>
                    (4) “Patterns in mtDNA variations can be extremely variable and may or may not have anything to do with the patterns seen in nuclear markers, or with morphological, ecological, physiological, or behavioral data, and therefore are often not reflective of important differences between species, subspecies or populations. Patterns of genetic variation can be totally different from, and uninformative about, important adaptive differences between taxa (Crandall 
                    <E T="03">et al.</E>
                     2000). Besides the California gnatcatcher, there are many examples in which mtDNA evidence failed to detect documented differences in morphology, nuclear DNA and ecological adaptation, including the Common raven (Omland 
                    <E T="03">et al.</E>
                     2000), Orchard oriole (Baker 
                    <E T="03">et al.</E>
                     2003), Florida grasshopper sparrow (Bulgin 
                    <E T="03">et al.</E>
                     2003), and Swamp sparrows (Greenberg 
                    <E T="03">et al.</E>
                     1998).” (VanderWerf, 
                    <E T="03">in litt.</E>
                     2004, p. 2).
                </P>
                <P>
                    (5) “The most comprehensive review of available mtDNA data was conducted by Funk and Omland (2003), who found that 23 percent of 2,319 species showed evidence of paraphyly or polyphyly based on mtDNA (sharing of mtDNA haplotypes among species), and they concluded that the causes of this must be understood to avoid erroneous phylogenetic interpretations.” (VanderWerf, 
                    <E T="03">in litt.</E>
                     2004, p. 2).
                </P>
                <P>
                    (6) “Loss of the coastal California gnatcatcher would substantially decrease the species' range and, since it occurs in a somewhat different habitat type from other populations, would diminish the ecological range of characteristics present in the species. Although the adaptive significance of the morphological differences has not been investigated, it is possible they represent important adaptations to the local environment, and that their loss would diminish the species evolutionary legacy.” (VanderWerf, 
                    <E T="03">in litt.</E>
                     2004, pp. 1-2).
                </P>
                <P>
                    (7) “Zink 
                    <E T="03">et al.</E>
                     (2000) provide some interesting information on the evolutionary history of [gnatcatcher] populations, but the argument that the California gnatcatcher is not distinct from other populations is based on a single genetic character, mtDNA, and this is a far too narrow and limited technique for making determinations of taxonomic validity. Most features of an organism are determined by multiple (nuclear) genes, not by mtDNA. Taxonomists and other biologists interested in evolutionary units cannot ignore available data on other aspects of the genome and physical and ecological characters (Crandall 
                    <E T="03">et al.</E>
                     2000). Under the very narrow criterion of Zink 
                    <E T="03">et al.</E>
                     (2000) few subspecies would be valid, and many full species would not be recognized, despite abundant and definitive data that they are no longer capable of interbreeding with other species (Avise 2004).” (VanderWerf, 
                    <E T="03">in litt.</E>
                     2004, pp. 2-3).
                </P>
                <P>
                    The panel concluded that the scientific evidence: (1) Substantially supports that the coastal California gnatcatcher is a valid subspecies; (2) substantially supports that the coastal California gnatcatcher  is discrete from other portions of the species; (3) substantially supports that the loss of the coastal California gnatcatcher would represent a significant diminution of the species as a whole; (4) offers little support for the assertion that the coastal California gnatcatcher is neither a valid subspecies nor a discrete and significant portion of the species; and (5) displays little support that the mtDNA evidence presented by Zink 
                    <E T="03">et al.</E>
                     (2000, pp. 1394-1405) alone constitutes sufficient information to overturn the existing taxonomy. The panel also noted that further decision on the status of the taxon should wait for analyses of a variety of morphological, genetic (including nuclear and mtDNA), and behavioral evidence.
                </P>
                <P>
                    In 2005, Edwards 
                    <E T="03">et al.</E>
                     (p. 6552) asserted that nuclear genes, not mtDNA, should have priority in determining avian species delimitation. Additionally, Haig and Winker (2010, pp. 172, 174) asserted the best approach for subspecies recognition is to include multiple characters (mtDNA, nuclear DNA, morphology) and that reliance on a single locus with unique properties, such as mtDNA, may not accurately reflect the genetic differences among populations due to random genetic effects (Funk 
                    <E T="03">et al.</E>
                     2007, pp. 1287-1288).
                </P>
                <P>
                    We acknowledge that the taxonomic classification of the coastal California gnatcatcher has been the subject of considerable scientific debate. The Service also addresses the information presented by Zink 
                    <E T="03">et al.</E>
                     (2000) in a recent 5-year review for the coastal California gnatcatcher (Service 2010, pp. 4-5). Species experts have recognized the coastal California gnatcatcher as a distinct taxon based on its physical appearance since it was first described, and the taxon is recognized as a distinct subspecies by the American Ornithologists Union (AOU 1957, p. 451). Some doubt has been cast on analyses of morphological data by Atwood (1991, pp. 118-133) (
                    <E T="03">e.g.,</E>
                     Cronin 1997, p. 663), but problems with those analyses do not invalidate previous and subsequent morphological work (Grinnell 1926, pp. 493-500; van Rossem 1931, pp. 36-37; Phillips 1991, pp. 25-26; Mellink and Rea 1994, pp. 50-62). Analysis by Zink 
                    <E T="03">et al.</E>
                     (2000, p. 1402) suggested that the northern population of California gnatcatchers does not appear to be unique, and that not all recognized subspecies equate to evolutionary significant units, although they were unable to expressly state that 
                    <E T="03">P. californica</E>
                     should have no subspecies, as claimed in the petition. We concluded in our 5-year review (Service 2010, pp. 4-5), that Zink 
                    <E T="03">et al.</E>
                     (2000, pp. 1394-1405) was insufficient to disregard the existing taxonomic status of the coastal California gnatcatcher and the information from multiple scientific papers that support subspecies classification of 
                    <E T="03">P.c. cali-fornica.</E>
                     We affirm that conclusion here. We conclude that the information and analysis in Zink 
                    <E T="03">et al.</E>
                     2000 does not present substantial information that the current subspecies taxonomic classification of the coastal California gnatcatcher may be in error.
                </P>
                <P>
                    The second issue presented by the petitioners refers to Skalski 
                    <E T="03">et al.</E>
                     (2008, pp. 199-220) and the assertion that the statistical analyses applied to the morphological data (collected by Atwood in determining the subspecies status of the coastal California gnatcatcher) were not appropriate statistical techniques for determining subspecific species classification. The issue Skalski 
                    <E T="03">et al.</E>
                     (2008, pp. 199-220) raises concerns the use of numerous tests of equality of sample means, cluster analysis, and discriminant analysis (Atwood 1991; Atwood, 
                    <E T="03">in litt.</E>
                     1994; Link and Pendleton, 
                    <E T="03">in litt.</E>
                     1994; 
                    <PRTPAGE P="66259"/>
                    McDonald 
                    <E T="03">et al., in litt.</E>
                     1994; Messer, 
                    <E T="03">in litt.</E>
                     1994, Newton, 
                    <E T="03">in litt.</E>
                     1994), which supported the subspecies classification. Skalski 
                    <E T="03">et al.</E>
                     (2008, pp. 199-220) assert these analyses are subject to high rates of false positives (Type I error) and therefore determination of classification as a subspecies should be based on analyses designed to detect specific alternative hypotheses, such as step and spline regression, while being insensitive to the sample location distributions (Skalski 
                    <E T="03">et al.</E>
                     2008, p. 217).
                </P>
                <P>
                    We examined this paper and determined the statistical analysis conducted by Skalski 
                    <E T="03">et al.</E>
                     (2008, pp. 210-212), a spline regression model using the log-length of the white spot on the sixth rectrix (tail feather) of the California gnatcatcher, was a new interpretation of old data and examined only one character, as an example of the statistical analysis of the 31 that Atwood (1988, pp. iii-vii, 1-74; 1991, 118-133) analyzed in his research. Skalski's analysis of this character, in contrast to Atwood's analysis, did not detect variation in the character consistent with subspecific designations within the California gnatcatcher. However, the Service concludes the results of this restrictive analysis do not present substantial evidence supporting potential revision of the subspecific taxonomic classification of the coastal California gnatcatcher. While the issue of concern raised by Skalski 
                    <E T="03">et al.</E>
                     (2008, pp. 199-220) and the petitioners relates to the validity of the statistical technique used, and we acknowledge that application of different statistical methods may yield different conclusions, the study's application of alternative methods of data analyses is limited. Without further analysis of additional characters, few conclusions can be made as to the appropriate taxonomic classification of the coastal California gnatcatcher. The current information does not provide substantial information that the current subspecies taxonomic classification of the coastal California gnatcatcher may be in error.
                </P>
                <P>
                    We previously analyzed the statistical technique utilized to determine subspecific classification of the coastal California gnatcatcher and addressed this topic in a publication in the 
                    <E T="04">Federal Register</E>
                     that determined that the conclusions reached by Atwood (1991) were reasonable and were largely consistent with five other independent and alternative scientific analyses (Link and Pendleton, 
                    <E T="03">in litt.</E>
                     1994; Atwood, 
                    <E T="03">in litt.</E>
                     1994; McDonald 
                    <E T="03">et al., in litt.</E>
                     1994; Messer, 
                    <E T="03">in litt.</E>
                     1994, Newton, 
                    <E T="03">in litt.</E>
                     1994) that were received at that time and support 30° north latitude as the southern subspecific boundary of 
                    <E T="03">P.c. californica</E>
                     (60 FR 15698; March 27, 1995). We continue to agree that Atwood's conclusions are reasonable because they are based on scientifically sound methodology that represents the best available scientific and commercial data available (60 FR 15699; March 27, 1995), as required in 50 CFR 424.11(d).
                </P>
                <P>
                    The final issue presented by the petitioners also refers to Skalski 
                    <E T="03">et al.</E>
                     (2008, pp. 199-220) and their assertion that “foxing” (the change in feather color associated with time after preparation of the specimen) of museum specimens might have biased Atwood's original and subsequent analysis of phenotypic characters, including plumage brightness (Atwood 1988, pp. iii-vii, 1-74; 1991, 118-133), by confounding the specimen's year of collection with measures of brightness of plumage. Significantly, Skalski 
                    <E T="03">et al.</E>
                     (2008) did not reexamine the specimens evaluated by Atwood, but instead constructed scatterplot diagrams that compared the area of specimen collection (latitude) with time (year) collected.
                </P>
                <P>Mellink and Rea (1994, pp. 50-62), in their analyses of coastal California gnatcatcher taxonomy, collected samples from the field and specimens from museums for comparison of genetic differences. The petition argues that the study skins analyzed by Mellink and Rea (1994) were also subject to foxing. However, Mellink and Rea (1994, pp. 52-53) excluded samples that were worn, damaged, or soiled to eliminate discrepancies among samples and concluded that within this species, foxing is “* * * slight and seems restricted largely to the gray underparts, with little or no apparent change in brown areas.”</P>
                <P>
                    Additionally, as mentioned under the second issue presented by the petitioners, five independent statistical analyses were conducted and submitted to the Service, in response to a request for public comment (59 FR 28508, 59 FR 38426, 59 FR 44125, 59 FR 53628, 59 FR 66509). These analyses (Link and Pendleton, 
                    <E T="03">in litt.</E>
                     1994; Atwood, 
                    <E T="03">in litt.</E>
                     1994; McDonald 
                    <E T="03">et al., in litt.</E>
                     1994; Messer, 
                    <E T="03">in litt.</E>
                     1994; Newton, 
                    <E T="03">in litt.</E>
                     1994) as well as Mellink and Rea (1994) were addressed in the March 27, 1995, 
                    <E T="04">Federal Register</E>
                     publication (60 FR 15693) announcing our determination that the coastal California gnatcatcher is a valid subspecies and affirming the coastal California gnatcatcher's threatened status under the Act (60 FR 15695). In that document, we concluded that there was no justification to support a claim that Atwood's 1991 data were incomplete, censored, or otherwise inadequate. Furthermore, we concluded that the analysts of the five independent reviews of Atwood's 1991 data took adequate care to remove potential effects of confounding of specimen age and collection area (60 FR 15695; March 27, 1995).
                </P>
                <P>
                    We conclude that the petitioner did not present substantial new information regarding the subspecific status of the coastal California gnatcatcher. The genetic information provided in the petition (Zink 
                    <E T="03">et al.</E>
                     2000) and assertions of improper statistical analyses (Skalski 
                    <E T="03">et al.</E>
                     2008) have been the focus of several Service (Service 2010) and independent scientific reviews (Link and Pendleton, 
                    <E T="03">in litt.</E>
                     1994; Atwood, 
                    <E T="03">in litt.</E>
                     1994; McDonald 
                    <E T="03">et al., in litt.</E>
                     1994; Messer, 
                    <E T="03">in litt.</E>
                     1994; Newton, 
                    <E T="03">in litt.</E>
                     1994; Mellink and Rea 1994; VanderWerf, 
                    <E T="03">in litt.</E>
                     2004) and the Service has concluded that the information is insufficient to support reclassification (see Service 2010, pp. 1-51). Issues regarding morphological analyses and specimen quality have also been considered by the Service and by numerous other taxonomic examinations, all of which support the subspecific status of the coastal California gnatcatcher (Grinnell 1926, pp. 493-500; van Rossem 1931, pp. 36-37; Phillips 1991, pp. 25-26; Mellink and Rea 1994, pp. 50-62). We hereby reaffirm our determination and recognition of the coastal California gnatcatcher as a distinct taxon, at the rank of subspecies as 
                    <E T="03">Polioptila californica californica.</E>
                </P>
                <HD SOURCE="HD1">Finding</HD>
                <P>In summary, the petition does not present substantial information to support a finding that the removal of the coastal California gnatcatcher from the List of Endangered and Threatened Wildlife may be warranted on the ground that the coastal California gnatcatcher is not a valid subspecies.</P>
                <P>
                    The petition presents an unpublished review by Cronin (2009, pp. 1-18) contending that subspecies classification for the coastal California gnatcatcher is not reasonable. The review discusses articles by Skalski 
                    <E T="03">et al.</E>
                     (2008, pp. 1394-1405) and Zink 
                    <E T="03">et al.</E>
                     (2000), that provide analyses of Atwood's (1991) data. We previously reviewed Atwood's data (1988 and 1991) and concluded that Atwood's conclusion that the coastal California gnatcatcher is a valid subspecies is adequately supported (60 FR 15693, March 27, 1995). We also convened a panel of experts in 2004 to consider the Zink 
                    <E T="03">et al.</E>
                     (2000) study. The panel concluded that Zink 
                    <E T="03">et al.</E>
                     (2000) offers 
                    <PRTPAGE P="66260"/>
                    little and insufficient support for reconsidering the coastal California gnatcatcher's subspecies classification. Our recent status review also concluded that the coastal California gnatcatcher represents a valid subspecies (Service 2010, pp. 1-51).
                </P>
                <P>
                    The petitioners also assert that the Service should overturn the classification of the coastal California gnatcatcher as a subspecies due to inappropriate techniques used in Atwood's (1991) statistical analysis of morphological data and present a review and interpretation of two journal articles in support of their claim. The Service reviewed the articles and determined that they do not present new information; instead they consist of an incomplete interpretation of old data. Moreover, the concerns raised by petitioners regarding “foxing” and the statistical technique utilized to analyze the data, were previously considered and rejected in our March 27, 1995, 
                    <E T="04">Federal Register</E>
                     publication affirming that the coastal California gnatcatcher meets the definition of a “species” under the Act (60 FR 15693), a Service status review (Service 2010, pp. 1-51), and a peer-reviewed journal (Mellink and Rea 1994, pp. 50-62).
                </P>
                <P>
                    Morphological variation within the California gnatcatcher species has been recognized as an indicator of the distinctiveness of populations and subspecific groups by numerous biologists, publications, and the AOU before and after Atwood's conclusion that the coastal California gnatcatcher is a valid subspecies (Brewster 1881, p. 103; Brewster 1902, p. 210; Thayer and Bangs 1907, p. 138; Grinnell 1926, p. 496; Grinnell 1928, p. 227; van Rossem 1931, p. 35; Hellmayer 1934, p. 508; AOU 1957, p. 451; Miller 
                    <E T="03">et al.</E>
                     1957, pp. 204-205; Paynter 1964, pp. 449-450; Atwood 1988, p. 61; Atwood 1991, p. 127; Phillips 1991, p. 25; Mellink and Rea 1994, p. 53; Howell and Webb 1995, p. 578). Thus, we conclude that the best information available indicates that the coastal California gnatcatcher is a valid subspecies and that the original scientific data evaluated and methods of analysis used at the time of listing were not in error as suggested by the petitioners.
                </P>
                <P>The sole focus of the petition is the contention that the coastal California gnatcatcher is not a valid subspecies and therefore should be delisted. Petitioners do not provide any information related to the other relevant factors that the Service considers when reviewing proposals to list or delist a species, including the factors provided under subsection 4(a)(1) of the Act. The information in Service files, including our recent 5-year review of the species (Service 2010, pp. 1-51), confirms that threats to the coastal California gnatcatcher remain.</P>
                <P>We have reviewed the petition, as well as the literature cited in the petition, and we have evaluated that information and information in our files. Based on this review and evaluation, we find that the petition does not present substantial scientific or commercial information to indicate that removal of the coastal California gnatcatcher from the List may be warranted. Although we will not commence a status review in response to this petition, we will continue to monitor the population status and trends of the coastal California gnatcatcher, potential threats to the coastal California gnatcatcher, and ongoing management actions that might be important with regard to the conservation of the coastal California gnatcatcher across its range.</P>
                <P>
                    Because we conclude that the coastal California gnatcatcher is a valid subspecies under the Act, we are no longer considering whether to propose its reclassification to a DPS under the Act. This document reaffirms our recognition of the coastal California gnatcatcher as a subspecies. We encourage interested parties to continue to gather data that will assist with the conservation of the subspecies. If you wish to provide information regarding the coastal California gnatcatcher, you may submit your information or materials to the Field Supervisor, Carlsbad Fish and Wildlife Office (see 
                    <E T="02">ADDRESSES</E>
                    ), at any time.
                </P>
                <HD SOURCE="HD1">References Cited</HD>
                <P>
                    A complete list of references cited is available on the Internet at 
                    <E T="03">http://www.regulations.gov</E>
                     and upon request from the Carlsbad Fish and Wildlife Office (see 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    ).
                </P>
                <HD SOURCE="HD1">Author</HD>
                <P>The primary authors of this notice are the staff members of the Carlsbad Fish and Wildlife Office.</P>
                <HD SOURCE="HD1">Authority</HD>
                <P>
                    The authority for this action is the Endangered Species Act of 1973, as amended (16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <SIG>
                    <DATED>Dated: October 14, 2011.</DATED>
                    <NAME>Gregory E. Siekaniec,</NAME>
                    <TITLE>Acting Director, U.S. Fish and Wildlife Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27644 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-55-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <CFR>50 CFR Part 648</CFR>
                <DEPDOC>[Docket No. 110707371-1617-01]</DEPDOC>
                <RIN>RIN 0648-BB28</RIN>
                <SUBJECT>Fisheries of the Northeastern United States; Atlantic Mackerel, Squid, and Butterfish Fisheries; Specifications and Management Measures</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule, request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        NMFS proposes 2012 specifications and management measures for Atlantic mackerel and butterfish, and 2012-2014 specifications for 
                        <E T="03">Illex</E>
                         and longfin squid. This is the first year that the specifications are being recommended for Atlantic mackerel and butterfish under the provisions of the Mid-Atlantic Fishery Management Council's (Council) Annual Catch Limit and Accountability Measure Omnibus Amendment (Omnibus Amendment). The two squid species are exempt from these requirements because they have a life cycle of less than 1 year. This action also proposes to adjust the closure threshold for the commercial mackerel fishery to 95 percent (from 90 percent), to allow the use of jigging gear to target longfin squid if the longfin squid fishery is closed due to the butterfish mortality cap, and to require a 3-inch (76-mm) minimum codend mesh size in order to possess more than 2,000 lb (0.9 mt) of butterfish (up from 1,000 lb (0.45mt)). Finally, this rule proposes minor corrections in existing regulatory text intended to clarify the intent of the regulations. These proposed specifications and management measures promote the utilization and conservation of the Atlantic Mackerel, Squid, and Butterfish (MSB) resource.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Public comments must be received no later than 5 p.m., eastern standard time, on November 25, 2011.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Copies of supporting documents used by the Mid-Atlantic Fishery Management Council (Council), including the Environmental Assessment (EA) and Regulatory Impact Review (RIR)/Initial Regulatory Flexibility Analysis (IRFA), are available from: Dr. Christopher M. Moore, Executive Director, Mid-Atlantic Fishery Management Council, Suite 201, 
                        <PRTPAGE P="66261"/>
                        800 N. State Street, Dover, DE 19901. The EA/RIR/IRFA is accessible via the Internet at 
                        <E T="03">http://www.nero.noaa.gov.</E>
                    </P>
                    <P>You may submit comments, identified by NOAA-NMFS-2011-0245, by any one of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Electronic Submission:</E>
                         Submit all electronic public comments via the Federal e-Rulemaking Portal 
                        <E T="03">http://www.regulations.gov.</E>
                         To submit comments via the e-Rulemaking Portal, first click the “submit a comment” icon, then enter NOAA-NMFS-2011-0245 in the keyword search. Locate the document you wish to comment on from the resulting list and click on the “Submit a Comment” icon on the right of that line.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         To NMFS, Northeast Regional Office, 55 Great Republic Dr, Gloucester, MA 01930. Mark the outside of the envelope “Comments on 2012 MSB Specifications.”
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (978) 281-9135, 
                        <E T="03">Attn:</E>
                         Aja Szumylo.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         Comments must be submitted by one of the above methods to ensure that the comments are received, documented, and considered by NMFS. Comments sent by any other method, to any other address or individual, or received after the end of the comment period, may not be considered. All comments received are a part of the public record and will generally be posted for public viewing on 
                        <E T="03">http:www.regulations.gov</E>
                         without change. All personal identifying information (
                        <E T="03">e.g.,</E>
                         name, address, etc.) submitted voluntarily by the sender will be publicly accessible. Do not submit confidential business information, or otherwise sensitive or protected information. NMFS will accept anonymous comments (enter “N/A” in the required fields if you wish to remain anonymous). Attachments to electronic comments will be accepted in Microsoft Word or Excel, WordPerfect, or Adobe PDF file formats only.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Aja Szumylo, Fishery Policy Analyst, 978-281-9195, fax 978-281-9135.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    Specifications, as referred to in this proposed rule, are the combined suite of commercial and recreational catch levels established for one or more fishing years. The specification process also allows for the modification of a select number of management measures, such as closure thresholds, gear restrictions, and possession limits. The Council's process for establishing specifications relies on provisions within the Fishery Management Plan (FMP) and its implementing regulations, as well as requirements established by the Magnuson-Stevens Act. Specifically, section 302(g)(1)(B) of the Magnuson-Stevens Act states that the Scientific and Statistical Committee (SSC) for each Regional Fishery Management Council shall provide its Council ongoing scientific advice for fishery management decisions, including recommendations for acceptable biological catch (ABC), preventing overfishing, maximum sustainable yield, and achieving rebuilding targets. The ABC is a level of catch that accounts for the scientific uncertainty in the estimate of the stock's defined overfishing level (OFL). The Council's SSC met on May 26 and 27, 2011, to recommend ABCs for the 2012 Atlantic mackerel (mackerel) and butterfish specifications, and the 2012-2014 
                    <E T="03">Illex</E>
                     and longfin squid specifications.
                </P>
                <P>
                    The FMP's implementing regulations require the involvement of a monitoring committee in the specification process for each species. Since the Magnuson-Stevens Act requirements for the SSC to recommend ABC became effective, the monitoring committees' role has largely been to recommend any reduction in catch limits from the SSC-recommended ABCs to offset management uncertainty, and to recommend other management measures (
                    <E T="03">e.g.,</E>
                     gear and/or possession restrictions) needed for the efficient management of the fishery. The MSB Monitoring Committee met on May 27, 2011, to discuss specification related recommendations for the 2012 mackerel and butterfish fisheries, and the 2012-2014 
                    <E T="03">Illex</E>
                     and longfin squid fisheries.
                </P>
                <P>Following the meetings described above, the Council considered the recommendations of the SSC, the Monitoring Committee, and public comments at its June 14-16, 2011, meeting in Port Jefferson, NY, and made their specification recommendations. The Council submitted these recommendations, along with the required analyses, for agency review on August 9, 2011, with final submission on September 15, 2011. NMFS must review the Council's recommendations to assure that they comply with the FMP and applicable law, and conduct notice-and-comment rulemaking to propose and implement the final recommendations.</P>
                <P>The structure of specifications for the mackerel and butterfish fisheries was revised by the Council's recently finalized regulations implementing the Omnibus Amendment (76 FR 60606, September 29, 2011), which established annual catch limit (ACL) and accountability measure (AM) provisions for all of the Council's FMPs. Following the specification of ABC, the revised regulations at § 648.22 require the specification of ACLs, which, if exceeded, require payback deductions from the subsequent year's catch limit. In order to avoid ACL overages, and the associated paybacks when ACLs are exceeded, the regulations also require the specification of annual catch targets (ACTs) to provide a buffer for management. Several specifications, including domestic annual harvest (DAH), domestic annual processing (DAP), total allowable level of foreign fishing (TALFF), and joint venture processing for mackerel (JVP), were previously required in the implementing regulations for the FMP, and remain unchanged by the Omnibus Amendment.</P>
                <P>For mackerel, the Omnibus Amendment and Amendment 11 to the MSB FMP (approved on September 30, 2011) created distinct allocations for the commercial and recreational mackerel fisheries. The revised mackerel regulations require the specification of ACTs for both the commercial and recreational mackerel fisheries. For butterfish, the regulations require specification of the mortality cap on the longfin squid fishery.</P>
                <P>
                    The regulations governing specifications for 
                    <E T="03">Illex</E>
                     and longfin squid are largely unchanged; both squid species are exempt from ACL/AM requirements because they have a life cycle of less than 1 year. For both squid species, regulations at § 648.22 require the specification of ABC, initial optimum yield (IOY), DAH, and DAP.
                </P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,xls40,xls40,xls40,xls40">
                    <TTITLE>Table 1—Proposed Specifications, in Metric Tons (mt), for Mackerel and Butterfish for the 2012 Fishing Year, and for Illex and Longfin Squid for the 2012-2014 Fishing Years </TTITLE>
                    <BOXHD>
                        <CHED H="1">Specifications </CHED>
                        <CHED H="1">Mackerel </CHED>
                        <CHED H="1">Butterfish </CHED>
                        <CHED H="1">
                            <E T="03">Illex</E>
                        </CHED>
                        <CHED H="1">Longfin </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">OFL </ENT>
                        <ENT>Unknown </ENT>
                        <ENT>Unknown </ENT>
                        <ENT>Unknown </ENT>
                        <ENT>Unknown </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ABC </ENT>
                        <ENT>43,781 </ENT>
                        <ENT>3,622 </ENT>
                        <ENT>24,000 </ENT>
                        <ENT>23,400 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ACL </ENT>
                        <ENT>43,781 </ENT>
                        <ENT>3,622 </ENT>
                        <ENT>N/A </ENT>
                        <ENT>N/A </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="66262"/>
                        <ENT I="01">Commercial ACT </ENT>
                        <ENT>34,907 </ENT>
                        <ENT>3,260 </ENT>
                        <ENT>N/A </ENT>
                        <ENT>N/A </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Recreational ACT/RHL </ENT>
                        <ENT>2,443 </ENT>
                        <ENT>N/A </ENT>
                        <ENT>N/A </ENT>
                        <ENT>N/A </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">IOY </ENT>
                        <ENT>N/A </ENT>
                        <ENT>N/A </ENT>
                        <ENT>22,915 </ENT>
                        <ENT>22,445 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DAH/DAP </ENT>
                        <ENT>33,821 </ENT>
                        <ENT>1,087 </ENT>
                        <ENT>22,915 </ENT>
                        <ENT>22,445 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JVP </ENT>
                        <ENT>0 </ENT>
                        <ENT>N/A </ENT>
                        <ENT>N/A </ENT>
                        <ENT>N/A </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TALFF </ENT>
                        <ENT>0 </ENT>
                        <ENT>0 </ENT>
                        <ENT>N/A </ENT>
                        <ENT>N/A </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD2">Research Set-Aside</HD>
                <P>
                    The Mid-Atlantic Research Set-Aside (RSA) Program allows research projects to be funded through the sale of fish that has been set aside from the total annual quota. The RSA may vary between 0 and 3 percent of the overall quota for each species. The Council has recommended that up to 3 percent of the total ACL for mackerel and butterfish, and up to 3 percent of the IOY for 
                    <E T="03">Illex</E>
                     and longfin squid, may be set aside to fund projects selected under the 2012 Mid-Atlantic RSA Program. NMFS solicited research proposals under the 2012 Mid-Atlantic RSA Program through a Federal Funding Opportunity announcement that published on January 6, 2011. The project selection and award process for the 2012 Mid-Atlantic RSA Program has not concluded. However, three projects have been preliminarily selected for approval by the Northeast Fisheries Science Center. These projects have collectively requested 250,580 lb (113,681 kg) of longfin squid, 200,000 lb (90,718 kg) of butterfish, 689,932 lb (312,948 kg) of summer flounder, 509,160 lb (230,951 kg) of scup, 184,280 lb (83,588 kg) of black sea bass, and 200,000 lb (90,718 kg) of bluefish. Project awards are pending a review by the NOAA Grants Office. If any portion of the MSB RSA is not awarded, NMFS will return it to the general fishery either through the final 2012 MSB specification rulemaking process or through the publication of a separate notice in the 
                    <E T="04">Federal Register</E>
                     notifying the public of a quota adjustment.
                </P>
                <P>These proposed specifications include a brief description of the preliminarily selected 2012 Mid-Atlantic RSA projects, including a description of applicable MSB exemptions that will likely be required to conduct the proposed research and compensation fishing. The Magnuson-Stevens Act requires that interested parties be provided an opportunity to comment on all proposed exempted fishing permits (EFPs).</P>
                <P>Vessels harvesting RSA quota in support of approved research projects would be issued EFPs authorizing them to exceed Federal possession limits and to fish during Federal quota closures. With respect to the MSB FMP, such regulations include closure regulations at § 648.24 and possession restrictions at § 648.26. These exemptions are necessary to allow project investigators to recover research expenses, as well as adequately compensate fishing industry participants harvesting RSA. Vessels harvesting RSA would operate within all other regulations that govern the commercial fishery, unless otherwise exempted through a separate EFP. Vessels conducting compensation fishing would harvest RSA quota during the fishing year from January 1-December 31, 2012.</P>
                <P>
                    <E T="03">Project #1:</E>
                     The proposed project is the continuation of a scup survey of 10 hard-bottom sites in Southern New England (SNE) that are not sampled by current state and Federal finfish trawl surveys. Unvented fish pots will be fished on each site from June through October in coastal waters of Nantucket Sound, Martha's Vineyard Sound, and Buzzard's Bay, MA, and Rhode Island Sound, RI. The length frequency distribution of the catch will be compared statistically to each of the other collection sites, and to finfish trawl data collected by the NMFS and state agencies to gain greater understanding of the scup stock structure. Vessels conducting research would not require any exemptions from regulations implemented under the MSB FMP. Vessels harvesting RSA quota would require the aforementioned closure and possession limit exemptions to facilitate compensation fishing activities.
                </P>
                <P>
                    <E T="03">Project #2:</E>
                     The proposed project is a black sea bass survey of sites in SNE and Mid‐Atlantic waters. Unvented black sea bass pots will be fished on each site, which will include one in Massachusetts, one south of Rhode Island, one south of New Jersey, and one south of Virginia, for 5 months from June through October in SNE, and April through August in the Mid‐Atlantic. The project is designed to collect black sea bass from sites that are un‐sampled by current state and Federal finfish bottom trawl surveys. The length frequency distribution of the catch will be compared to each of the other collection sites, and to finfish trawl data collected by NMFS and state agencies to gain greater understanding of the black sea bass stock structure. Vessels conducting research would not require any exemptions from regulations implemented under the MSB FMP. Vessels harvesting RSA quota would require the aforementioned closure and possession limit exemptions to facilitate compensation fishing activities.
                </P>
                <P>
                    <E T="03">Project #3:</E>
                     The proposed project would continue a spring and fall trawl survey in shallow waters between Martha's Vineyard, MA, and Cape Hatteras, NC, that are not sampled by the NMFS trawl survey. The project investigators plan to provide stock assessment data for Mid-Atlantic RSA species, including summer flounder, scup, black sea bass, longfin squid, butterfish, and Atlantic bluefish, and assessment-quality data for weakfish, Atlantic croaker, spot, several skate and ray species, smooth dogfish, horseshoe crab, and several unmanaged but important forage species. Vessels conducting this near-shore trawl survey would not require any exemptions from regulations implemented under the MSB FMP. Vessels harvesting RSA quota would require the aforementioned closure and possession limit exemptions to facilitate compensation fishing activities.
                </P>
                <HD SOURCE="HD1">2012 Proposed Specifications and Management Measures for Mackerel and Butterfish</HD>
                <HD SOURCE="HD2">Atlantic Mackerel</HD>
                <P>
                    The status of the mackerel stock was assessed by the Transboundary Resources Assessment Committee (TRAC) in March 2010. The 2010 TRAC Status Report indicated reduced productivity in the stock and a lack of older fish in both the survey and catch data; however, the status of the mackerel stock is unknown because biomass reference points could not be determined. According to the FMP, mackerel ABC must be calculated using 
                    <PRTPAGE P="66263"/>
                    the formula U.S. ABC = Stock-wide ABC − C, where C is the estimated catch of mackerel in Canadian waters for the upcoming fishing year. Due to uncertainty in the assessment, the TRAC recommended that total annual catches not exceed 80,000 mt (average total U.S. and Canadian landings from 2006-2008) until new information is available. The SSC recommended specifying the stock-wide ABC for 2012 at 80,000 mt, consistent with the TRAC recommendation. The Council recommended a U.S. ABC of 43,781 mt (80,000 mt − 36,219 mt (estimated 2012 Canadian catch)).
                </P>
                <P>Consistent with MSB Amendment 11, the Council recommended a recreational allocation of 2,714 mt (6.2 percent of the U.S. ABC). The proposed Recreational ACT of 2,443 mt (90 percent of 2,714 mt) is reduced to account for low precision and time lag of recreational catch estimates, as well as lack of recreational discard estimates. The Recreational ACT is equal to the Recreational Harvest Limit (RHL), which would be the effective cap on recreational catch.</P>
                <P>For the commercial mackerel fishery, the Council recommended a commercial fishery allocation of 41,067 mt (93.8 percent of the U.S. ABC, the portion of the ACL that was not allocated to the recreational fishery). The recommended Commercial ACT of 34,907 mt (85 percent of 41,067) is reduced to address uncertainty in estimated 2012 Canadian landings, uncertainty in discard estimates, and possible misreporting. The Commercial ACT would be further reduced by a discard rate of 3.11 percent (mean plus one standard deviation of discards from 1999-2008), to arrive at the proposed DAH of 33,821 mt. The DAH would be the effective cap on commercial catch, as it has been in past specifications.</P>
                <P>Consistent with the Council's recommendation, NMFS proposes mackerel specifications that would set the U.S. ABC/ACL at 43,781 mt, the Commercial ACT at 34,907 mt, the DAH and DAP at 33,821 mt, and the Recreational ACT at 2,443 mt.</P>
                <P>Additionally, as recommended by the Council, NMFS proposes to maintain JVP at zero (the most recent allocation was 5,000 mt of JVP in 2004). In the past, the Council recommended a JVP greater than zero because it believed U.S. processors lacked the ability to process the total amount of mackerel that U.S. harvesters could land. However, for the past 8 years, the Council has recommended zero JVP because U.S. shoreside processing capacity for mackerel has expanded. The Council concluded that processing capacity was no longer a limiting factor relative to domestic production of mackerel.</P>
                <P>The Magnuson-Stevens Act provides that the specification of TALFF, if any, shall be the portion of the optimum yield (OY) of a fishery that will not be harvested by U.S. vessels. TALFF would allow foreign vessels to harvest U.S. fish and sell their product on the world market, in direct competition with U.S. industry efforts to expand exports. While a surplus existed between ABC and the mackerel fleet's harvesting capacity for many years, that surplus has disappeared due to downward adjustments of the specifications in recent years. Based on analysis and a review of the state of the world mackerel market and possible increases in U.S. production levels, the Council concluded that specifying a DAH/DAP resulting in zero TALFF will yield positive social and economic benefits to both U.S. harvesters and processors, and to the Nation. For these reasons, consistent with the Council's recommendation, NMFS proposes to specify DAH at a level that can be fully harvested by the domestic fleet, thereby precluding the specification of a TALFF, in order to support the U.S. mackerel industry. NMFS concurs that it is reasonable to assume that in 2012 the commercial fishery has the ability to harvest 33,821 mt of mackerel.</P>
                <P>Finally, this rule proposes that the commercial fishery be closed at 95 percent of the DAH, as recommended by the Council. The current closure threshold of 90 percent of the DAH was designed to accommodate misreporting in the commercial fishery, and the lack of a distinct allocation for the recreational fishery. A 95-percent closure threshold should be sufficient to prevent overages, given that a recreational allocation is now required by the FMP.</P>
                <HD SOURCE="HD2">Butterfish</HD>
                <P>The current status of the butterfish stock is unknown because biomass reference points could not be determined in the SAW 49 assessment (February 2010). Though the butterfish population appears to be declining over time, fishing mortality does not seem to be the major cause. Butterfish have a high natural mortality rate, and the current estimated fishing mortality (F = 0.02) is well below all candidate overfishing threshold reference points. The assessment report noted that predation is likely an important component of the butterfish natural mortality rate (currently assumed to be 0.8), but also noted that estimates of consumption of butterfish by predators appear to be very low. In short, the underlying causes for population decline are unknown.</P>
                <P>The SSC recommended an ABC of 3,622 mt (100 percent increase from 2011) because butterfish survey indices appear stable or increasing, there have been anecdotal observations of increased butterfish abundance, and fishing mortality appears low when compared to natural mortality.</P>
                <P>
                    The Council recommended setting the butterfish ACL equal to the ABC, and establishing a 10-percent buffer between ACL and ACT for management uncertainty, which would result in an ACT of 3,260 mt. Since discards have been roughly 
                    <FR>2/3</FR>
                     of catch (1999-2008 average), the Council recommended setting the DAH and DAP at 1,087 mt (3,260 mt−2,173 mt discards). Butterfish TALFF is only specified to address bycatch by foreign fleets targeting mackerel TALFF. Because there is no mackerel TALFF, butterfish TALFF would also be set at zero.
                </P>
                <P>The Council recommended setting the butterfish mortality cap on the longfin squid fishery at 2,445 mt (75 percent of 3,260 mt). If the butterfish mortality cap is harvested during Trimester I (January-April) or Trimester III (September-December), the directed longfin squid fishery will close for the remainder of that trimester.</P>
                <P>NMFS proposes specifications, consistent with the Council's recommendation, that would set the butterfish ABC/ACL at 3,622 mt, the ACT at 3,260 mt, the DAH and DAP at 1,087 mt, and the butterfish mortality cap on the longfin squid fishery at 2,445 mt. Additionally, consistent with MSB regulations, NMFS is proposing zero TALFF for butterfish in 2010 because mackerel TALFF is also specified at zero. Consistent with 2011, NMFS proposes that the 2012 butterfish mortality cap be allocated by Trimester as follows:</P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s50,7.1,8.2">
                    <TTITLE>Table 2—Proposed Trimester Allocation of Butterfish Mortality Cap on the Longfin Squid Fishery for 2012 </TTITLE>
                    <BOXHD>
                        <CHED H="1">Trimester </CHED>
                        <CHED H="1">Percent </CHED>
                        <CHED H="1">
                            Metric 
                            <LI>tons </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">I (Jan-Apr) </ENT>
                        <ENT>65 </ENT>
                        <ENT>1,589.25 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">II (May-Aug) </ENT>
                        <ENT>3.3 </ENT>
                        <ENT>80.69 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">III (Sep-Dec) </ENT>
                        <ENT>31.7 </ENT>
                        <ENT>775.06 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>100 </ENT>
                        <ENT>2,445 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    Finally, the Council recommended, and NMFS proposes, that a 3-inch (76-mm) minimum codend mesh size requirement apply for vessels 
                    <PRTPAGE P="66264"/>
                    possessing 2,000 lb (0.9 mt) or more of butterfish (up from 1,000 lb (0.45 mt) in 2011) in order to allow some portion of butterfish discards to be landed.
                </P>
                <HD SOURCE="HD1">
                    2012-2014 Proposed Specifications and Management Measures for 
                    <E T="7462">Illex</E>
                     Squid and Longfin Squid
                </HD>
                <HD SOURCE="HD2">Illex Squid</HD>
                <P>
                    The 
                    <E T="03">Illex</E>
                     stock was most recently assessed at SARC 42 in late 2005. While it was not possible to evaluate current stock status because there are no reliable current estimates of stock biomass or F, qualitative analyses determined that overfishing had not likely been occurring. The SSC recommended the status quo ABC of 24,000 mt based on observations that catches in this range, and up to 26,000 mt, have not caused any apparent harm to the stock.
                </P>
                <P>The Council recommended that the ABC be reduced by a revised discard rate of 4.52 percent (the mean plus one standard deviation of the most recent 10 years of observed discards), which results in an IOY, DAH, and DAP for recommendation of 22,915 mt for the 2012-2014 fishing years.</P>
                <P>
                    Consistent with the Council's recommendation, NMFS proposes to specify the 
                    <E T="03">Illex</E>
                     ABC as 24,000 mt, and to specify IOY, DAH, and DAP as 22,915 mt for the 2012-2014 fishing years. The FMP does not authorize the specification of JVP and TALFF for the 
                    <E T="03">Illex</E>
                     fishery because of the domestic fishing industry's capacity to harvest and to process the OY from this fishery.
                </P>
                <HD SOURCE="HD2">Longfin Squid</HD>
                <P>The 51st Northeast Regional Stock Assessment Workshop (SAW 51), published in January 2011, found that the longfin squid stock is not overfished, but that the overfishing status is unknown. The SSC used the updated stock assessment information to recommend an ABC of 23,400 mt for the 2012-2014 fishing years, subject to annual review. This recommendation corresponds to catch in the year with the highest observed exploitation fraction (catch divided by estimated biomass) during a period of light exploitation (1976-2009). The SSC interpreted this level of exploitation to be sustainable over the long term.</P>
                <P>The Council recommended that the ABC be reduced by a revised discard rate of 4.08 percent (mean plus one standard deviation of the most recent 10 years of observed discards), which results in an IOY, DAH, and DAP for recommendation of 22,445 mt for the 2012-2014 fishing years.</P>
                <P>NMFS concurs with the Council's recommendation; therefore, this action proposes an ABC of 23,400 mt, and an IOY, DAH, and DAP of 22,445 mt for the 2012-2014 fishing years. The FMP does not authorize the specification of JVP and TALFF for the longfin squid fishery because of the domestic industry's capacity to harvest and process the OY for this fishery.</P>
                <HD SOURCE="HD3">Distribution of the Longfin DAH</HD>
                <P>The proposed 2012-2014 longfin DAH would be allocated into trimesters, according to percentages specified in the FMP, as follows:</P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s50,8,8">
                    <TTITLE>Table 3—Proposed Trimester Allocation of Longfin Quota for 2012-2014 </TTITLE>
                    <BOXHD>
                        <CHED H="1">Trimester </CHED>
                        <CHED H="1">Percent </CHED>
                        <CHED H="1">
                            Metric 
                            <LI>tons </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">I (Jan-Apr) </ENT>
                        <ENT>43 </ENT>
                        <ENT>9,651 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">II (May-Aug) </ENT>
                        <ENT>17 </ENT>
                        <ENT>3,816 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">III (Sep-Dec) </ENT>
                        <ENT>40 </ENT>
                        <ENT>8,978 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>100 </ENT>
                        <ENT>22,445 </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD3">Longfin Squid Jigging Exemption</HD>
                <P>The Council recommended, and NMFS proposes, to allow Longfin Squid/Butterfish moratorium permit holders to possess longfin squid in excess of the 2,500-lb (0.93-mt) possession limit during any closures of the longfin squid fishery resulting from the butterfish mortality cap, provided that all trawl gear is appropriately stowed. The butterfish mortality cap was designed to limit butterfish bycatch in the longfin squid trawl fishery, and jigging for squid is not expected to result in substantial butterfish bycatch.</P>
                <HD SOURCE="HD1">Corrections</HD>
                <P>
                    This proposed rule also contains minor corrections to existing regulations. The corrections would not change the intent of any regulations; they would only clarify the intent of existing regulations by correcting technical errors. The proposed regulatory text restructures § 648.23(a). In addition, the 
                    <E T="03">Illex</E>
                     fishery gear exemption in § 648.23(a) (formerly at § 648.23(a)(3)(ii)) would be revised to clarify the timing of the exemption, and to match the stated gear requirements to those implemented for the longfin squid fishery through Amendment 10 to the MSB FMP. Finally, longfin squid was previously referred to as 
                    <E T="03">Loligo</E>
                     squid. Due to a recent change in the scientific name of longfin squid from 
                    <E T="03">Loligo pealeii</E>
                     to 
                    <E T="03">Doryteuthis (Amerigo)</E>
                      
                    <E T="03">pealeii,</E>
                     the Council will now use the common name “longfin squid” in all official documents to avoid confusion. Accordingly, the regulatory text is amended to replace all references to “
                    <E T="03">Loligo”</E>
                     squid with the term “longfin squid.”
                </P>
                <HD SOURCE="HD1">Classification</HD>
                <P>Pursuant to section 304(b)(1)(A) of the Magnuson-Stevens Act, the NMFS Assistant Administrator has determined that this proposed rule is consistent with the Atlantic Mackerel, Squid, and Butterfish FMP, other provision of the Magnuson-Stevens Act, and other applicable law, subject to further consideration after public comment.</P>
                <P>This proposed rule has been determined to be not significant for purposes of Executive Order 12866.</P>
                <P>
                    The Council prepared an IRFA, as required by section 603 of the Regulatory Flexibility Act (RFA). The IRFA describes the economic impact this proposed rule, if adopted, would have on small entities. A summary of the analysis follows. A copy of this analysis is available from the Council or NMFS (see 
                    <E T="02">ADDRESSES</E>
                    ) or via the Internet at 
                    <E T="03">http://www.nero.noaa.gov.</E>
                </P>
                <HD SOURCE="HD2">Statement of Objective and Need</HD>
                <P>
                    This action proposes 2012 specifications for mackerel and butterfish, and 2012-2014 specifications for 
                    <E T="03">Illex</E>
                     and longfin squid. It also proposes to modify the closure threshold for the commercial mackerel fishery, to adjust the gear requirements for the butterfish fishery, to create an exemption for the use of jigs, should the longfin squid fishery be closed due to reaching the butterfish mortality cap. A complete description of the reasons why this action is being considered, and the objectives of and legal basis for this action, are contained in the preamble to this proposed rule and are not repeated here.
                </P>
                <HD SOURCE="HD2">Description and Estimate of Number of Small Entities To Which the Rule Will Apply</HD>
                <P>
                    Based on permit data for 2011, the numbers of potential fishing vessels in the 2012 fisheries are as follows: 351 Longfin squid/butterfish moratorium permits; 76 
                    <E T="03">Illex</E>
                     moratorium permits; 2,201 mackerel permits; 1,904 incidental squid/butterfish permits; and 831 MSB party/charter permits. Small businesses operating in commercial and recreational (
                    <E T="03">i.e.,</E>
                     party and charter vessel operations) fisheries have been defined by the Small Business Administration as firms with gross revenues of up to $4.0 and $6.5 million, respectively. There are no large entities participating in this fishery, as that term is defined in section 601 of the RFA. Therefore, there are no disproportionate economic impacts on small entities. 
                    <PRTPAGE P="66265"/>
                    Many vessels participate in more than one of these fisheries; therefore, permit numbers are not additive.
                </P>
                <HD SOURCE="HD2">Description of Projected Reporting, Recordkeeping, and Other Compliance Requirements</HD>
                <P>There are no new reporting or record keeping requirements contained in any of the alternatives considered for this action. In addition, there are no Federal rules that duplicate, overlap, or conflict with this proposed rule.</P>
                <HD SOURCE="HD2">Minimizing Significant Economic Impacts on Small Entities</HD>
                <HD SOURCE="HD1">Proposed Actions</HD>
                <P>
                    The recently finalized Omnibus Amendment, which applies to mackerel and butterfish, changes the structure of specifications compared to that used in past years. In order to facilitate comparison of alternatives, the discussions of mackerel and butterfish specifications below will focus on the effective limit on directed harvest, regardless of the terminology used for the specification. The specifications and terminology for 
                    <E T="03">Illex</E>
                     and longfin squid are unchanged from those used in 2011.
                </P>
                <P>The mackerel commercial DAH proposed in this action (33,821 mt) represents a reduction from status quo (2011 DAH = 46,779 mt). Despite the reduction, the proposed DAH is above recent U.S. landings; mackerel landings for 2008-2010 averaged 18,830 mt. Thus, the reduction does not pose a constraint to vessels relative to the landings in recent years. In 2011, there was a soft allocation of 15,000 mt of the mackerel DAH for the recreational mackerel fishery. The Omnibus Amendment and MSB Amendment 11 established an explicit allocation for the recreational fishery, and this action proposes a Recreational ACT/RHL of 2,443 mt. Because recreational harvest from 2008-2010 averaged 738 mt, it does not appear that the new, explicit allocation for the recreational fishery will constrain recreational harvest. Overall, the proposed action is not expected to result in any reductions in revenues for vessels that participate in either the commercial or recreational mackerel fisheries.</P>
                <P>The proposed change to the mackerel closure threshold, which would require the closure of the commercial mackerel fishery at 95 percent of the DAH, is a preventative measure intended to ensure that the commercial catch limit is not exceeded. The economic burden on fishery participants associated with this measure is expected to be minimal.</P>
                <P>The butterfish DAH proposed in this action (1,087 mt) represents a 117-percent increase over the 2011 DAH (500 mt). Due to market conditions, there has not been a directed butterfish fishery in recent years; therefore, recent landings have been low. The proposed increase in the DAH has the potential to increase revenue for permitted vessels.</P>
                <P>The proposed adjustment to the gear requirement for the butterfish fishery, which would require vessels possessing 2,000 lb (0.9 mt) or more of butterfish to fish with a 3-inch (76-mm) minimum codend mesh, is expected to result in a modest increase in revenue for fishery participants. This adjustment would enable additional retention of butterfish by vessels using small-mesh fishing gear. Previously, the mesh size requirement applied to vessels possessing 1,000 lb (0.45 mt) or more of butterfish.</P>
                <P>
                    The 
                    <E T="03">Illex</E>
                     IOY (22,915 mt) proposed in this action represents a slight decrease compared to status quo (23,328 mt). Though annual 
                    <E T="03">Illex</E>
                     landings have totaled over 
                    <FR>2/3</FR>
                     of the IOY in the past 3 years (15,900 mt for 2008, 18,419 mt for 2009, and 15,825 for 2010), the landings were lower than the level being proposed. Thus, implementation of this proposed action should not result in a reduction in revenue or a constraint on expansion of the fishery in 2012.
                </P>
                <P>The longfin squid IOY (22,445 mt) represents an increase from the status quo (20,000 mt). Because longfin squid landings from 2008-2010 averaged 9,182 mt, the proposed IOY provides an opportunity to increase landings, though if recent trends of low landings continue, there may be no increase in landings despite the increase in the allocation. No reductions in revenues for the longfin squid fishery are expected as a result of this proposed action.</P>
                <P>As discussed in the Final Regulatory Flexibility Analysis (FRFA) for MSB Amendment 10, the butterfish mortality cap has a potential for economic impact on fishery participants. The longfin squid fishery will close during Trimesters I and III if the butterfish mortality cap is reached. If the longfin squid fishery is closed in response to butterfish catch before the entire longfin squid quota is harvested, then a loss in revenue is possible. The potential for longfin squid revenue loss is dependent upon the size of the butterfish mortality cap. The proposed 2012 butterfish mortality cap of 2,445 mt represents a 70-percent increase over status quo (1,436 mt). The 2011 butterfish mortality cap did not result in a closure of the longfin squid fishery in Trimester I. At the start of Trimester III, over 55 percent of the butterfish mortality cap (compared to 31.7 percent allocated at the start of the fishing year) was available for the longfin squid fishery for the duration of the fishing year. Though a majority of the cap is still available, it could still result in a closure of the longfin squid fishery late in the fishing year. Nonetheless, given that the lower cap has not yet constrained the longfin squid fishery, it is reasonable to expect that the proposed increase to the cap will also not constrain the longfin squid fishery. For that reason, additional revenue losses are not expected as a result of this proposed action.</P>
                <P>The proposed jigging measure would allow Longfin Squid/Butterfish moratorium permit holders to possess longfin squid in excess of the possession limit during any closures of the longfin squid fishery resulting from the butterfish mortality cap. Jigging for longfin squid has been shown to be commercially infeasible. However, because butterfish bycatch in jig gear is expected to be very minimal, it seems reasonable to allow jig fishing for squid. If attempts to use jig gear for commercial longfin squid fishing are successful, the use of this gear could help mitigate economic impacts on fishery participants if the longfin squid fishery is closed due to the mortality cap.</P>
                <HD SOURCE="HD1">Alternatives to the Proposed Rule</HD>
                <P>
                    The Council analysis evaluated four alternatives to the proposed specifications for mackerel. The first (status quo) and second non-selected alternatives were based on the specifications structure that existed prior to the implementation of the Omnibus Amendment, and were not selected because they are no longer in compliance with the MSB FMP. The other alternatives differ in their specification of the stockwide ABC (80,000 mt in the preferred alternative). The same amount of expected Canadian catch (36,219 mt) was subtracted from the stockwide ABC in each alternative. The third alternative (least restrictive) would set the U.S. ABC and ACL at 63,781 mt (100,000 mt stockwide ABC minus 36,219 mt Canadian catch), the Commercial ACT at 50,853 mt, the DAH and DAP at 49,271 mt, and the Recreational ACT at 3,559 mt. The fourth alternative (most restrictive) would set the U.S. ABC and ACL at 23,781 mt (60,000 mt stockwide ABC minus 36,219 mt Canadian catch), the Commercial ACT at 18,961 mt, the DAH and DAP at 18,371 mt, and the Recreational ACT at 1,327 mt. These two alternatives were not selected because they were all inconsistent with the ABC recommended by the SSC.
                    <PRTPAGE P="66266"/>
                </P>
                <P>The status quo closure threshold for the commercial mackerel fishery (90 percent) was considered overly precautionary when compared to the proposed closure threshold (95 percent). The status quo closure threshold, which was designed in part because there was no distinct allocation for the recreational mackerel fishery, is no longer considered appropriate.</P>
                <P>There were four alternatives to the preferred action for butterfish that were not selected by the Council. The first (status quo) and second non-selected were based on the specifications structure that existed prior to the implementation of the Omnibus Amendment, and were not selected because they are no longer in compliance with the MSB FMP. The third alternative (least restrictive) would have set the ABC and ACL at 4,528 mt, the ACT at 4,075 mt, the DAH and DAP at 1,358 mt, and the butterfish mortality cap at 3,056 mt. The fourth alternative (most restrictive) would have set the ABC and ACL at 2,717 mt, the ACT at 2,445 mt, the DAH and DAP at 815 mt, and the butterfish mortality cap at 1,834 mt. These two alternatives were not selected because they were all inconsistent with the ABC recommended by the SSC.</P>
                <P>There were two alternatives regarding proposed adjustment to the butterfish gear requirement. The status quo alternative requires vessels possessing 1,000 lb (0.45 mt) or more of butterfish to fish with a 3-inch (76-mm) minimum codend mesh. The preferred alternative (3-inch (76-mm) mesh to possess 2,000 lb (0.9 mt)) is expected to create some additional revenue in the form of butterfish landings for vessels using mesh sizes smaller than 3 inches (76 mm).</P>
                <P>
                    Three alternatives to the preferred action were considered for 
                    <E T="03">Illex,</E>
                     but were not selected by the Council. All alternatives would establish specifications for the 2012-2014 fishing years. The first alternative (status quo), shared the same 24,000-mt ABC as the proposed action. However, a discard rate of 2.8 percent was deducted to reach an IOY, DAH, and DAP at 23,328 mt rather than the 22,915 mt specified in this proposed action. The Council did not select the status quo alternative because it found the updated discard rate of 4.52 percent to be a more appropriate representation of discards in the 
                    <E T="03">Illex</E>
                     fishery. The second alternative (least restrictive) would have set ABC at 30,000 mt, and IOY, DAH, and DAP at 28,644 mt (ABC reduced by 4.52 percent for discards). This alternative was not selected because the higher specifications were inconsistent with the results of the most recent stock assessment. The third alternative (most restrictive) would have set ABC at 18,000 mt, and IOY, DAH, and DAP at 17,186 mt (ABC reduced by 4.52 percent for discards). The Council considered this alternative unnecessarily restrictive.
                </P>
                <P>There were three alternatives to the proposed action evaluated for longfin squid. All alternatives would establish specifications for the 2012-2014 fishing years. The first alternative (status quo) would have set the ABC at 24,000 mt, and the IOY, DAH and DAP at 20,000 mt. The second alternative (least restrictive) would have set the ABC at 29,250 mt, and the IOY, DAH, and DAP at 28,057 mt (ABC reduced by 4.08 percent for discards). The third alternative (most restrictive) would have set the ABC at 17,550 mt, and the IOY, DAH and DAP at 16,834 mt (ABC reduced by 4.08 percent for discards). These three alternatives were not selected because they were all inconsistent with the ABC recommended by the SSC.</P>
                <P>The alternatives for longfin squid RSA would allow up to 1.65 percent (status quo) or up to 3 percent (preferred) of the longfin squid IOY to be used to fund research projects for the 2012-2014 fishing years. In 2011, butterfish RSA was only awarded to cover butterfish discards by vessels fishing for longfin squid RSA. The small amount of butterfish RSA available in 2011 (15 mt, or 3 percent of 500 mt butterfish DAH) was only sufficient to cover discards for an amount of longfin squid RSA equal to 1.65 percent of the IOY. The recommended increase in the 2012 butterfish quota will allow for enough butterfish RSA (3 percent of the 1,087 mt butterfish DAH) to accommodate discards for longfin squid RSA equal to 3 percent of the IOY. </P>
                <P>For the jigging exemption, the status quo alternative prevents Longfin squid/Butterfish moratorium permit holders from possessing or landing over 2,500 lb (1.13 mt) of longfin squid if the directed fishery is closed because of the butterfish mortality cap. The preferred alternative would allow such vessel to posses and land over 2,500 lb (1.13 mt) if using jigging gear. If the use of jigs for commercial longfin squid fishery proves successful, the preferred alternative may help reduce the economic impacts of closures of the longfin squid fishery resulting from the butterfish mortality cap.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 50 CFR Part 648</HD>
                    <P>Fisheries, Fishing, Recordkeeping and reporting requirements.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: October 21, 2011.</DATED>
                    <NAME>Samuel D. Rauch III,</NAME>
                    <TITLE>Deputy Assistant Administrator for Regulatory Programs, National Marine Fisheries Service. </TITLE>
                </SIG>
                <P>For the reasons set out in the preamble, 50 CFR part 648, as amended at 76 FR 60649, September 29, 2011, is proposed to be amended as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 648—FISHERIES OF THE NORTHEASTERN UNITED STATES</HD>
                    <P>1. The authority citation for part 648 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>
                             16 U.S.C. 1801 
                            <E T="03">et seq.</E>
                        </P>
                    </AUTH>
                    <P>
                        2. In § 648.2, remove the definition for 
                        <E T="03">Loligo,</E>
                         revise the definition of 
                        <E T="03">Squid,</E>
                         and add the definition for 
                        <E T="03">Longfin squid</E>
                         in alphabetical order, to read as follows:
                    </P>
                    <SECTION>
                        <SECTNO>§ 648.2 </SECTNO>
                        <SUBJECT>Definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Longfin squid</E>
                             means 
                            <E T="03">Doryteuthis (Amerigo)</E>
                              
                            <E T="03">pealeii</E>
                             (formerly referred to as 
                            <E T="03">Loligo pealeii</E>
                            ).
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Squid</E>
                             means longfin squid (
                            <E T="03">Doryteuthis (Amerigo)</E>
                              
                            <E T="03">pealeii,</E>
                             formerly 
                            <E T="03">Loligo pealeii</E>
                            ) or 
                            <E T="03">Illex illecebrosus.</E>
                        </P>
                        <STARS/>
                        <P>3. In § 648.23, paragraph (a) is revised to read as follows:</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 648.23 </SECTNO>
                        <SUBJECT>Mackerel, squid, and butterfish gear restrictions.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Mesh restrictions and exemptions.</E>
                             Vessels subject to the mesh restrictions in this paragraph (a) may not have available for immediate use any net, or any piece of net, with a mesh size smaller than that specified in paragraphs (a)(1) and (a)(2) of this section.
                        </P>
                        <P>
                            (1) 
                            <E T="03">Butterfish fishery.</E>
                             Owners or operators of otter trawl vessels possessing 2,000 lb (0.9 mt) or more of butterfish harvested in or from the EEZ may only fish with nets having a minimum codend mesh of 3 inches (76 mm) diamond mesh, inside stretch measure, applied throughout the codend for at least 100 continuous meshes forward of the terminus of the net, or for codends with less than 100 meshes, the minimum mesh size codend shall be a minimum of one-third of the net, measured from the terminus of the codend to the headrope.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Longfin squid fishery.</E>
                             Owners or operators of otter trawl vessels possessing longfin squid harvested in or from the EEZ may only fish with nets having a minimum mesh size of 2
                            <FR>1/8</FR>
                             inches (54 mm) during Trimesters I (Jan-Apr) and III (Sept-Dec), or 1
                            <FR>7/8</FR>
                             inches (48 mm) during Trimester II (May-Aug), diamond mesh, inside 
                            <PRTPAGE P="66267"/>
                            stretch measure, applied throughout the codend for at least 150 continuous meshes forward of the terminus of the net, or, for codends with less than 150 meshes, the minimum mesh size codend shall be a minimum of one-third of the net measured from the terminus of the codend to the headrope, unless they are fishing consistent with exceptions specified in paragraph (b) of this section.
                        </P>
                        <P>
                            (i) 
                            <E T="03">Net obstruction or constriction.</E>
                             Owners or operators of otter trawl vessels fishing for and/or possessing longfin squid shall not use any device, gear, or material, including, but not limited to, nets, net strengtheners, ropes, lines, or chafing gear, on the top of the regulated portion of a trawl net that results in an effective mesh opening of less than 2
                            <FR>1/8</FR>
                             inches (54 mm) during Trimesters I (Jan-Apr) and III (Sept-Dec), or 1
                            <FR>7/8</FR>
                             inches (48 mm) during Trimester II (May-Aug), diamond mesh, inside stretch measure. “Top of the regulated portion of the net” means the 50 percent of the entire regulated portion of the net that would not be in contact with the ocean bottom if, during a tow, the regulated portion of the net were laid flat on the ocean floor. However, owners or operators of otter trawl vessels fishing for and/or possessing longfin squid may use net strengtheners (covers), splitting straps, and/or bull ropes or wire around the entire circumference of the codend, provided they do not have a mesh opening of less than 5 inches (12.7 cm) diamond mesh, inside stretch measure. For the purposes of this requirement, head ropes are not to be considered part of the top of the regulated portion of a trawl net.
                        </P>
                        <P>
                            (ii) 
                            <E T="03">Jigging exemption.</E>
                             During closures of the longfin squid fishery resulting from the butterfish mortality cap, described in § 648.26(c)(3), vessels fishing for longfin squid using jigging gear are exempt from the closure possession limit specified in § 648.26(b), provided that all otter trawl gear is stowed as specified in paragraph (b) of this section.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Illex fishery.</E>
                             Seaward of the following coordinates, otter trawl vessels possessing longfin squid harvested in or from the EEZ and fishing for 
                            <E T="03">Illex</E>
                             during the months of June, July, August, in Trimester II, and September in Trimester III are exempt from the longfin squid gear requirements specified in paragraph (a)(2) of this section, provided that landward of the specified coordinates they do not have available for immediate use, as defined in paragraph (b) of this section, any net, or any piece of net, with a mesh size less than 1
                            <FR>7/8</FR>
                             inches (48 mm) diamond mesh in Trimester II, and 2
                            <FR>1/8</FR>
                             inches (54 mm) diamond mesh in Trimester III, or any piece of net, with mesh that is rigged in a manner that is prohibited by paragraph (a)(2) of this section.
                        </P>
                        <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s25,xls34,xls34">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1">Point</CHED>
                                <CHED H="1">N. lat.</CHED>
                                <CHED H="1">W. long.</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">M1</ENT>
                                <ENT>43°58.0′</ENT>
                                <ENT>67°22.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M2</ENT>
                                <ENT>43°50.0′</ENT>
                                <ENT>68°35.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M3</ENT>
                                <ENT>43°30.0′</ENT>
                                <ENT>69°40.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M4</ENT>
                                <ENT>43°20.0′</ENT>
                                <ENT>70°00.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M5</ENT>
                                <ENT>42°45.0′</ENT>
                                <ENT>70°10.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M6</ENT>
                                <ENT>42°13.0′</ENT>
                                <ENT>69°55.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M7</ENT>
                                <ENT>41°00.0′</ENT>
                                <ENT>69°00.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M8</ENT>
                                <ENT>41°45.0′</ENT>
                                <ENT>68°15.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M9</ENT>
                                <ENT>42°10.0′</ENT>
                                <ENT>67°10.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M10</ENT>
                                <ENT>41°18.6′</ENT>
                                <ENT>66°24.8′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M11</ENT>
                                <ENT>40°55.5′</ENT>
                                <ENT>66°38.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M12</ENT>
                                <ENT>40°45.5′</ENT>
                                <ENT>68°00.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M13</ENT>
                                <ENT>40°37.0′</ENT>
                                <ENT>68°00.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M14</ENT>
                                <ENT>40°30.0′</ENT>
                                <ENT>69°00.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M15</ENT>
                                <ENT>40°22.7′</ENT>
                                <ENT>69°00.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M16</ENT>
                                <ENT>40°18.7′</ENT>
                                <ENT>69°40.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M17</ENT>
                                <ENT>40°21.0′</ENT>
                                <ENT>71°03.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M18</ENT>
                                <ENT>39°41.0′</ENT>
                                <ENT>72°32.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M19</ENT>
                                <ENT>38°47.0′</ENT>
                                <ENT>73°11.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M20</ENT>
                                <ENT>38°04.0′</ENT>
                                <ENT>74°06.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M21</ENT>
                                <ENT>37°08.0′</ENT>
                                <ENT>74°46.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M22</ENT>
                                <ENT>36°00.0′</ENT>
                                <ENT>74°52.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M23</ENT>
                                <ENT>35°45.0′</ENT>
                                <ENT>74°53.0′</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">M24</ENT>
                                <ENT>35°28.0′</ENT>
                                <ENT>74°52.0′</ENT>
                            </ROW>
                        </GPOTABLE>
                        <STARS/>
                        <P>4. In § 648.24, paragraph (b)(1) is revised to read as follows:</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 648.24 </SECTNO>
                        <SUBJECT>Fishery closures and accountability measures.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>
                            (1) 
                            <E T="03">Mackerel commercial sector EEZ closure.</E>
                             NMFS shall close the commercial mackerel fishery in the EEZ when the Regional Administrator projects that 95 percent of the mackerel DAH is harvested, if such a closure is necessary to prevent the DAH from being exceeded. The closure of the commercial fishery shall be in effect for the remainder of that fishing year, with incidental catches allowed as specified in § 648.26. When the Regional Administrator projects that the DAH for mackerel shall be landed, NMFS shall close the commercial mackerel fishery in the EEZ, and the incidental catches specified for mackerel in § 648.26 will be prohibited.
                        </P>
                        <STARS/>
                        <P>5. In the table below, for each section in the left column, remove the text from whenever it appears throughout the section and add the text indicated in the right column.</P>
                        <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="s50,r50,r50,9">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1">Section </CHED>
                                <CHED H="1">Remove </CHED>
                                <CHED H="1">Add</CHED>
                                <CHED H="1">Frequency</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">§ 648.4(a)(5)(i) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.4(a)(5)(i)(A) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin </ENT>
                                <ENT>2</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.4(a)(5)(i)(L)(ii) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    § 648.4(a)(10)(iv)(C)(
                                    <E T="03">1</E>
                                    )(
                                    <E T="03">i</E>
                                    ) 
                                </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    § 648.4(a)(10)(iv)(C)(
                                    <E T="03">1</E>
                                    )(
                                    <E T="03">ii</E>
                                    ) 
                                </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.13(a) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>2</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.14(g)(1)(ii)(B) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>2</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.14(g)(1)(iii) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.14(g)(2)(ii) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin </ENT>
                                <ENT>2</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.14(g)(2)(iii) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.14(o)(1)(vi) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.22(a)(2) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.22(a)(4) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.22(a)(5) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.22(b)(1) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.22(b)(1)(i)(A) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.22(b)(3)(v) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.22(c)(1)(i) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.22(c)(3) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.22(c)(6) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.22(f) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin </ENT>
                                <ENT>2</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.24(a) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>4</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.24(c)(3) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>2</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="66268"/>
                                <ENT I="01">§ 648.26(b) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>7</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.27 (heading) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.27(a) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.27(b) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>5</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.27(c) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>3</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.27(d) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin squid </ENT>
                                <ENT>2</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.124(a)(2) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin </ENT>
                                <ENT>1</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 648.124(b)(2) </ENT>
                                <ENT>
                                    <E T="03">Loligo</E>
                                </ENT>
                                <ENT>longfin </ENT>
                                <ENT>1</ENT>
                            </ROW>
                        </GPOTABLE>
                    </SECTION>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27726 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </PRORULE>
    </PRORULES>
    <VOL>76</VOL>
    <NO>207</NO>
    <DATE>Wednesday, October 26, 2011</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NOTICES>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="66269"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <DATE>October 20, 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">Animal Plant and Health Inspection Service</HD>
                <P>
                    <E T="03">Title:</E>
                     Self Certification Medical Statement.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0579-0196.
                </P>
                <P>
                    <E T="03">Summary of Collection:</E>
                     The United States Department of Agriculture is responsible for ensuring consumers that food and farm products are moved from producer to consumer in the most efficient, dependable, economical, and equitable system possible. 5 CFR part 339 authorizes an agency to obtain medical information about the applicant's health status to assist management in making employment decisions concerning positions that have specific medical standards or physical requirements in order to determine medical/physical fitness. The Marketing and Regulatory Programs (MRP) of the Animal Plant and Health Inspection Service (APHIS) of the U.S. Department of Agriculture hires individuals each year in commodity grading and inspection positions. These positions involve arduous duties and work under conditions, around moving machinery, slippery surfaces, and high noise level areas. APHIS will collect information using the MRP-5 form (Self-Certification Medical Statement).
                </P>
                <P>
                    <E T="03">Need and Use of the Information:</E>
                     The information collected from the prospective employees assists the MRP officials, administrative personnel, and servicing Human Resources Offices in determining an applicant's physical fitness and suitability for employment in positions with approved medical standards and physical requirements and direct contact with meat, dairy, fresh or processed fruits and vegetables, and poultry intended for human consumption and cotton and tobacco products intended for consumer use. Denial of the information would greatly hamper APHIS recruiting capability and adversely affect management's ability to facilitate hiring, placement, and utilization of qualified individuals into positions that have specific medical standards and physical requirements.
                </P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     Individuals or households.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     524.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     Reporting: On occasion.
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     88.
                </P>
                <SIG>
                    <NAME>Ruth Brown,</NAME>
                    <TITLE>Departmental Information Collection Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27638 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-34-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <DATE>October 20, 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 
                    <PRTPAGE P="66270"/>
                    displays a currently valid OMB control number.
                </P>
                <HD SOURCE="HD1">Food Safety and Inspection Service</HD>
                <P>
                    <E T="03">Title:</E>
                     Salmonella Initiative Program.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0583-New.
                </P>
                <P>
                    <E T="03">Summary of Collection:</E>
                     The Food Safety and Inspection Service (FSIS) has been delegated the authority to exercise the functions of the Secretary as provided in the Federal Meat Inspection Act (FMIA) (21 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ), the Poultry Products Inspection Act (PPIA) (21 U.S.C. 451 
                    <E T="03">et seq.</E>
                    ). These statutes mandate that FSIS protect the public by ensuring that meat and poultry products are safe, wholesome, unadulterated, and properly labeled and packaged. The Salmonella initiative Program (SIP) offers incentives to meat and poultry slaughter establishments to control Salmonella in their operations. SIP benefits public health because it encourages establishments to test for microbial pathogens, which is a key feature of effective process control.
                </P>
                <P>
                    <E T="03">Need and Use of the Information:</E>
                     Under SIP, establishments will share their data with the Food Safety and Inspection Service (FSIS); this will help the Agency in formulating its policy. Establishments that want to enter SIP must send a protocol to FSIS informing the Agency about their plans for implementing SIP in their establishment, including data collection, objectives and methods of evaluating the new technology for which they are receiving the regulator waiver.
                </P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     Individuals or households.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     300.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     Recordkeeping; Reporting: On occasion.
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     206,000.
                </P>
                <SIG>
                    <NAME>Ruth Brown,</NAME>
                    <TITLE>Departmental Information Collection Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27639 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-DM-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Rural Utilities Service</SUBAGY>
                <SUBJECT>Information Collection Activity; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Rural Utilities Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35, as amended), the Rural Utilities Service's (RUS) invites comments on this information collection for which approval from the Office of Management and Budget (OMB) will be requested.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on this notice must be received by December 27, 2011.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Michele L. Brooks, Director, Program Development &amp; Regulatory Analysis, Rural Utilities Service, USDA, 1400 Independence Ave., SW., STOP 1522, Room 5168—South Building, Washington, DC 20250-1522. 
                        <E T="03">Telephone:</E>
                         (202) 690-1078. 
                        <E T="03">Fax:</E>
                         (202) 720-8435.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Office of Management and Budget's (OMB) regulation (5 CFR part 1320) implanting provisions of the Paperwork Reduction Act of 1995 (Pub. L. 104-13) requires that interested members of the public and affected agencies have an opportunity to comment on information collection and recordkeeping activities (see 5 CFR 1320.8(d)). This notice identifies an information collection that RUS is submitting to OMB for extension.</P>
                <P>
                    Comments are invited on (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 assumption used; (c) ways to enhance the quality, utility and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques on other forms of information technology. Comments may be sent to: MaryPat Daskal, Program Development and Regulatory Analysis, Rural Utilities Service, U.S. Department of Agriculture, 1400 Independence Ave., SW., Room 5166-South, STOP 1522, Washington, DC 20250-1522. 
                    <E T="03">Fax:</E>
                     (202) 720-8435. 
                    <E T="03">E-mail: marypat.daskal@wdc.usda.gov.</E>
                </P>
                <P>
                    <E T="03">Title:</E>
                     7 CFR Part 1726, Electric System Construction Policies and Procedures.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0572-0107.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension of a previously approved collection.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     In order to facilitate the programmatic interest of the Rural Electrification Act of 1936, 7 U.S.C. 901 
                    <E T="03">et seq.</E>
                     (RE Act), and, in order to assure that loans made or guaranteed by RUS are adequately secured, RUS, as a secured lender, has established certain standards and specifications for materials, equipment, and construction of electric systems. The use of standard forms, construction contracts, and procurement procedures helps assure RUS that appropriate standards and specification are maintained; RUS' loan security is not adversely affected; and the loan and loan guarantee funds are used effectively and for the intended purposes. The list of forms and corresponding purposes for this information collection are as follows:
                </P>
                <HD SOURCE="HD1">1. RUS Form 168b, Contractor's Bond</HD>
                <P>This form is used to provide a surety bond for contracts on RUS Forms 200, 257, 786, 790, &amp; 830.</P>
                <HD SOURCE="HD1">2. RUS Form 168c, Contractor's Bond (less than $1 million)</HD>
                <P>This form is used to provide a surety bond in lieu of RUS Form 168b, when contractor's surety has accepted a small business administration guarantee.</P>
                <HD SOURCE="HD1">3. RUS Form 187, Certificate of Completion—Contract Construction</HD>
                <P>This form is used for the closeout of RUS Forms 200, 257, 786, and 830.</P>
                <HD SOURCE="HD1">4. RUS Form 198, Equipment Contract</HD>
                <P>This form is used for equipment purchases.</P>
                <HD SOURCE="HD1">5. RUS Form 200, Construction Contract—Generating</HD>
                <P>This form is used for generating plant construction or for the furnishing and installation of major items of equipment.</P>
                <HD SOURCE="HD1">6. RUS Form 213, Certificate (“Buy American”)</HD>
                <P>This form is used to document compliance with the “Buy American” requirement.</P>
                <HD SOURCE="HD1">7. RUS Form 224, Waiver and Release of Lien</HD>
                <P>This form is used by subcontractors to provide a release of lien in connection with the closeout of RUS Forms 198, 200, 257, 786, 790, and 830.</P>
                <HD SOURCE="HD1">8. RUS Form 231, Certificate of Contractor</HD>
                <P>This form is used for the closeout of RUS Forms 198, 200, 257, 786, and 830.</P>
                <HD SOURCE="HD1">9. RUS Form 238, Construction or Equipment Contract Amendment</HD>
                <P>This form is used to amend contracts except for distribution line construction contracts.</P>
                <HD SOURCE="HD1">10. RUS Form 254, Construction Inventory</HD>
                <P>
                    This form is used to document the final construction in connection with the closeout of RUS Form 830.
                    <PRTPAGE P="66271"/>
                </P>
                <HD SOURCE="HD1">11. RUS Form 257, Contract to Construct Buildings</HD>
                <P>This form is used to construct headquarter buildings, generating plant buildings and other structure construction.</P>
                <HD SOURCE="HD1">12. RUS Form 307, Bid Bond</HD>
                <P>This form is used to provide a bid bond in RUS Forms 200, 257, 786, 790 and 830.</P>
                <HD SOURCE="HD1">13. RUS Form 786, Electric System Communications and Control Equipment Contract</HD>
                <P>This form is used for delivery and installation of equipment for system communications.</P>
                <HD SOURCE="HD1">14. RUS Form 790, Electric System Construction Contract Non-Site Specific Construction (Notice and Instructions to Bidders)</HD>
                <P>This form is used for limited distribution construction accounted for under work order procedure.</P>
                <HD SOURCE="HD1">15. RUS Form 792b, Certificate of Contractor and Indemnity Agreement (Line Extensions)</HD>
                <P>This form is used in the closeout of RUS Form 790.</P>
                <HD SOURCE="HD1">16. RUS Form 830, Electric System Construction Contract (Labor &amp; Material)</HD>
                <P>This form is used for distribution and/or transmission project construction.</P>
                <P>
                    <E T="03">Estimate of Burden:</E>
                     Public reporting burden for this collection of information is estimated to average 1.5 minutes per response.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Businesses or other for profits; not-for-profit institutions.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     1,210.
                </P>
                <P>
                    <E T="03">Estimated Number of Responses per Respondent:</E>
                     4.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden on Respondents:</E>
                     104 hours.
                </P>
                <P>Copies of this information collection, and related form and instructions, can be obtained from MaryPat Daskal, Program Development and Regulatory Analysis, at (202) 720-7853.</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>Dated: October 19, 2011.</DATED>
                    <NAME>Jonathan Adelstein,</NAME>
                    <TITLE>Administrator, Rural Utilities Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27642 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-423-808]</DEPDOC>
                <SUBJECT>Stainless Steel Plate in Coils From Belgium: Notice of Preliminary Results of Antidumping Duty Changed Circumstances Review</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In response to a request from the interested party, Aperam Stainless Belgium N.V. (“Aperam”), the Department of Commerce (“the Department”) initiated a changed circumstances review (“CCR”) of the antidumping duty order of stainless steel plate in coils (“SSPC”) from Belgium.
                        <SU>1</SU>
                        <FTREF/>
                         We have preliminarily determined that Aperam is the successor-in-interest to ArcelorMittal Stainless Belgium N.V. (“AMSB”) with respect to the antidumping duty order on SSPC from Belgium.
                        <SU>2</SU>
                        <FTREF/>
                         We invite interested parties to comment on these preliminary results. Parties who submit comments in these reviews are requested to submit with each argument (1) A statement of the issue and (2) a brief summary of the argument.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             
                            <E T="03">See Stainless Steel Plate in Coils From Belgium: Notice of Initiation of Antidumping Duty Changed Circumstances Review,</E>
                             76 FR 45511 (July 29, 2011) (“
                            <E T="03">CCR Initiation Notice”</E>
                            ).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             
                            <E T="03">See Antidumping Duty Orders; Certain Stainless Steel Plate in Coils From Belgium, Canada, Italy, the Republic of Korea, South Africa, and Taiwan,</E>
                             64 FR 27756 (May 21, 1999); 
                            <E T="03">Notice of Amended Antidumping Duty Orders; Certain Stainless Steel Plate in Coils From Belgium, Canada, Italy, the Republic of Korea, South Africa, and Taiwan,</E>
                             68 FR 11520 (March 11, 2003); 
                            <E T="03">Notice of Amended Antidumping Duty Orders; Certain Stainless Steel Plate in Coils From Belgium, Canada, Italy, the Republic of Korea, South Africa, and Taiwan,</E>
                             68 FR 16117 (April 2, 2003); 
                            <E T="03">Notice of Correction to the Amended Antidumping Duty Orders; Certain Stainless Steel Plate in Coils From Belgium, Canada, Italy, the Republic of Korea, South Africa, and Taiwan,</E>
                             68 FR 20114 (April 24, 2003) (collectively, “
                            <E T="03">Antidumping Order”</E>
                            ).
                        </P>
                    </FTNT>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         October 26, 2011.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>George McMahon or Stephanie Moore, AD/CVD Operations, Office 3, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street &amp; Constitution Avenue, NW., Washington, DC 20230; telephone: (202) 482-1167 and (202) 482-3692, respectively.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On May 21, 1999, the Department published in the 
                    <E T="04">Federal Register</E>
                     an antidumping duty order on stainless steel plate in coils from Belgium. 
                    <E T="03">See Antidumping Order.</E>
                     In the Department's initial less-than-fair-value investigation, the respondent company subject to investigation was ALZ N.V. On June 1, 2009, the Department determined that AMSB was the successor-in-interest to Ugine &amp; ALZ Belgium (“U&amp;A Belgium”), which was a successor-in-interest to ALZ N.V.
                    <SU>3</SU>
                    <FTREF/>
                     The Department is currently conducting an administrative review of Aperam covering the period of review of May 1, 2010 through April 30, 2011.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See, e.g.,</E>
                         “Successor-in-Interest Analysis” Memorandum from G. McMahon to J. Terpstra, at page 2 (June 1, 2009), Attached as Appendix 4 to Aperam's request for a CCR; 
                        <E T="03">see also</E>
                          
                        <E T="03">Stainless Steel Plate in Coils From Belgium: Notice of Initiation of Antidumping Duty Changed Circumstances Review,</E>
                         76 FR 45511, 45512 (July 29, 2011).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See Initiation of Antidumping and Countervailing Duty Administrative Reviews and Request for Revocation in Part,</E>
                         76 FR 37781 (June 28, 2011).
                    </P>
                </FTNT>
                <P>
                    On June 14, 2011, Aperam requested that the Department initiate and conduct an expedited changed circumstances review to determine that for purposes of the antidumping law, Aperam is the successor-in-interest to AMSB.
                    <SU>5</SU>
                    <FTREF/>
                     In response to Aperam's request, the Department initiated a changed circumstances review of the antidumping duty order on SSPC from Belgium. 
                    <E T="03">See CCR Initiation Notice.</E>
                     On August 8, 2011, the Department issued a questionnaire to Aperam and based on our analysis of its response, we preliminarily determine that Aperam is the successor-in-interest to AMSB, which was itself a successor-in-interest to the respondent in the less-than-fair-value investigation, and that, as such, Aperam is entitled to receive the same antidumping duty treatment accorded AMSB. We have received no comments from the petitioners 
                    <SU>6</SU>
                    <FTREF/>
                     regarding Aperam's CCR request or questionnaire response.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Aperam's letter to the Secretary of Commerce, dated, June 14, 2011.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Petitioners consist of: Allegheny Ludlum Corporation, North American Stainless, United Auto Workers Local 3303, Zanesville Arco Independent Organization, and the United Steel, Paper and Forestry, Rubber, Manufacturing, Energy, Allied Industrial and Service Workers International Union, AFL-CIO/CLC.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Antidumping Duty Order</HD>
                <P>
                    The product covered by this order is certain stainless steel plate in coils. Stainless steel is an alloy steel containing, by weight, 1.2 percent or less of carbon and 10.5 percent or more of chromium, with or without other elements. The subject plate products are flat-rolled products, 254 mm or over in width and 4.75 mm or more in thickness, in coils, and annealed or otherwise heat treated and pickled or 
                    <PRTPAGE P="66272"/>
                    otherwise descaled. The subject plate may also be further processed (
                    <E T="03">e.g.,</E>
                     cold-rolled, polished, 
                    <E T="03">etc.</E>
                    ) provided that it maintains the specified dimensions of plate following such processing. Excluded from the scope of this order are the following: (1) Plate not in coils; (2) Plate that is not annealed or otherwise heat treated and pickled or otherwise descaled; (3) Sheet and strip; and (4) Flat bars.
                </P>
                <P>The merchandise subject to this order is currently classifiable in the Harmonized Tariff Schedule of the United States (“HTSUS”) at subheadings: 7219.11.00.30, 7219.11.00.60, 7219.12.00.06, 7219.12.00.21, 7219.12.00.26, 7219.12.00.51, 7219.12.00.56, 7219.12.00.66, 7219.12.00.71, 7219.12.00.81, 7219.31.00.10, 7219.90.00.10, 7219.90.00.20, 7219.90.00.25, 7219.90.00.60, 7219.90.00.80, 7220.11.00.00, 7220.20.10.10, 7220.20.10.15, 7220.20.10.60, 7220.20.10.80, 7220.20.60.05, 7220.20.60.10, 7220.20.60.15, 7220.20.60.60, 7220.20.60.80, 7220.90.00.10, 7220.90.00.15, 7220.90.00.60, and 7220.90.00.80. Although the HTSUS subheadings are provided for convenience and customs purposes, the written description of the merchandise subject to these orders is dispositive.</P>
                <HD SOURCE="HD1">Preliminary Results of Changed Circumstances Review</HD>
                <P>
                    In making a successor-in-interest determination, the Department examines several factors including, but not limited to, changes in: (1) Management; (2) production facilities; (3) supplier relationships; and (4) customer base. 
                    <E T="03">See, e.g.,</E>
                      
                    <E T="03">Carbon and Certain Alloy Steel Wire Rod From Trinidad and Tobago: Notice of Initiation and Preliminary Results of Antidumping Duty Changed Circumstances Review,</E>
                     73 FR 17952, 17953 (April 2, 2008), unchanged in 
                    <E T="03">Carbon and Certain Alloy Steel Wire Rod From Trinidad and Tobago: Notice of Final Results of Antidumping Duty Changed Circumstances Review,</E>
                     73 FR 30052 (May 23, 2008); 
                    <E T="03">see also</E>
                      
                    <E T="03">Ball Bearings and Parts Thereof from Japan: Initiation and Preliminary Results of Changed-Circumstances Review,</E>
                     71 FR 14679, 14680 (March 23, 2006), unchanged in 
                    <E T="03">Notice of Final Results of Antidumping Duty Changed-Circumstances Review: Ball Bearings and Parts Thereof from Japan,</E>
                     71 FR 26452 (May 5, 2006) (collectively, “
                    <E T="03">CCR Japan”</E>
                    ). Although no single factor or combination of factors will necessarily provide a dispositive indication of a successor-in-interest relationship, the Department will generally consider the new company to be the successor to the previous company if its resulting operation is similar to that of its predecessor. 
                    <E T="03">See CCR Japan;</E>
                      
                    <E T="03">see also</E>
                      
                    <E T="03">Brass Sheet and Strip From Canada; Final Results of Antidumping Duty Administrative Review,</E>
                     57 FR 20460 (May 13, 1992), and accompanying Issues and Decision Memorandum at Comment 1. Thus, if the evidence demonstrates that, with respect to the production and sale of the subject merchandise, the new company operates as the same business entity as the prior company, the Department will assign the new company the cash-deposit rate of its predecessor. 
                    <E T="03">Id.; see</E>
                      
                    <E T="03">also Circular Welded Non-Alloy Steel Pipe From the Republic of Korea; Preliminary Results of Antidumping Duty Changed Circumstances Review,</E>
                     63 FR 14679 (March 26, 1998), unchanged in 
                    <E T="03">Circular Welded Non-Alloy Steel Pipe From Korea; Final Results of Antidumping Duty Changed Circumstances Review,</E>
                     63 FR 20572 (April 27, 1998), in which the Department found that a company which only changed its name and did not change its operations is a successor-in-interest to the company before it changed its name.
                </P>
                <P>In accordance with 19 CFR 351.216, we preliminarily determine that Aperam is the successor-in-interest to AMSB. In its June 14, 2011, CCR request, Aperam provided evidence supporting its claim to be the successor-in-interest to AMSB. Documentation attached to Aperam's CCR request shows that the shareholders of Aperam's corporate parent, ArcelorMittal S.A., approved a spin-off of AMSB's stainless and specialty steels business into Aperam, and the resulting name change to Aperam Stainless Belgium N.V. resulted in little or no change in management, production facility, supplier relationships, or customer base. This documentation consists of: (1) Official minutes of the extraordinary general meeting of ArcelorMittal shareholders regarding the shareholders' approval of the spin-off of ArcelorMittal's stainless and specialty steels business into Aperam; (2) a letter from Lakshmi N. Mittal, CEO, dated December 13, 2010, regarding the announcement of the spin-off of the stainless steel business from ArcelorMittal to Aperam; (3) name change registration with the Economics Ministry, Government of Belgium; (4) the Department's “Successor-in-Interest Analysis” Memorandum, dated June 1, 2009, regarding a prior successor-in-interest determination and the criteria which served as the basis for this decision; (5) list of the AMSB and Aperam's shareholders which indicates no changes before and after the spin-off; and (6) organization charts which show that the management structure prior to and after the spin-off of the stainless business to Aperam is almost identical.</P>
                <P>
                    In its CCR questionnaire response, dated September 12, 2011, Aperam provided further information to support its claim that it is the successor-in-interest to AMSB. Specifically, Aperam reported that, pursuant to the corporate name change from AMSB to Aperam, there were no changes to the production facilities, production capacity of SSPC, channels of distribution, customer categories, major inputs from affiliated parties or sales to its affiliates. Aperam also indicated that there were no changes in the types of SSPC produced before and after the corporate name change from AMSB to Aperam. With regard to its customers in both the United States and in its home market, Aperam's response shows that there were no significant changes resulting from the corporate name change, and Aperam cited the current market situation as the basis for the changes which occurred. 
                    <E T="03">Id.</E>
                     at pages 2-6. Aperam states, “ {n}o changes have occurred at Aperam Stainless Belgium as a result of the spin-off, nor have there been any changes in the broader organization in terms of corporate strategy, organizational structure, management, ownership, production, or sales.” 
                    <E T="03">Id.</E>
                     at page 7.
                </P>
                <P>In summary, Aperam has presented evidence to support its claim of successorship. The record indicates that the corporate name change to Aperam has not significantly changed the operations of the company. The production facilities, supplier relationships, management, and customer base of Aperam are substantially unchanged from their status prior to the corporate name change. The record evidence demonstrates that Aperam operates essentially in the same manner as the predecessor company, AMSB.</P>
                <P>
                    We find that the evidence provided by Aperam is sufficient to preliminarily determine that the change of its corporate name from AMSB to Aperam did not affect the company's operations in a meaningful way. Therefore, based on the aforementioned reasons, we preliminarily determine that Aperam is the successor-in-interest to AMSB and, thus, should receive the same antidumping duty treatment with respect to stainless steel plate in coils from Belgium as the former AMSB.
                    <PRTPAGE P="66273"/>
                </P>
                <HD SOURCE="HD1">Public Comment</HD>
                <P>Any interested party may request a hearing within 30 days of publication of this notice. Any hearing, if requested, will be held no later than 44 days after the date of publication of this notice, or the first workday thereafter. Case briefs from interested parties may be submitted not later than 30 days after the date of publication of this notice. Rebuttal briefs, limited to the issues raised in the case briefs, may be filed not later than 37 days after the date of publication of this notice. All written comments shall be submitted in accordance with 19 CFR 351.303. Persons interested in attending the hearing, if one is requested, should contact the Department for the date and time of the hearing. The Department intends to issue the final results within 270 days from the date of initiation of this changed circumstances review, in accordance with 19 CFR 351.216(e), including the results of its analysis of issues raised in any written comments.</P>
                <P>The current requirement for a cash deposit of estimated antidumping duties on all subject merchandise will continue unless and until it is modified pursuant to the final results of this changed circumstances review.</P>
                <P>We are issuing and publishing these results and notice in accordance with sections 751(b)(1) and 777(i)(1) and (2) of the Tariff Act of 1930, as amended, and 19 CFR 351.216.</P>
                <SIG>
                    <DATED>Dated: October 20, 2011.</DATED>
                    <NAME>Ronald K. Lorentzen,</NAME>
                    <TITLE>Deputy Assistant Secretary for Import Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27749 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <RIN>RIN 0648-XA643</RIN>
                <SUBJECT>Snapper-Grouper Fishery Off the Southern Atlantic States and Coral and Coral Reefs Fishery in the South Atlantic; Exempted Fishing Permit</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of receipt of an application for an exempted fishing permit; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NMFS announces the receipt of an application for an exempted fishing permit (EFP) from Keith Farmer, on behalf of the North Carolina Department of Environment and Natural Resources Aquariums Division (North Carolina Aquariums). If granted, the EFP would authorize North Carolina Aquariums to collect, with certain conditions, various species of reef fish and live rock in Federal waters off North Carolina. The specimens would be used in educational exhibits displaying North Carolina native species at aquariums located at Pine Knoll Shores, Roanoke Island, Fort Fisher, and Jeanette's Ocean Pier, NC.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received no later than 5 p.m., eastern standard time, on November 25, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments on the application by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">E-mail: Karla.Gore@noaa.gov.</E>
                         Include in the subject line of the e-mail comment the following document identifier: “North Carolina Aquariums”.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Karla Gore, Southeast Regional Office, NMFS, 263 13th Avenue South, St. Petersburg, FL 33701.
                    </P>
                    <P>The application and related documents are available for review upon written request to any of the above addresses.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Karla Gore, 727-824-5305; 
                        <E T="03">e-mail: karla.gore@noaa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The EFP is requested under the authority of the Magnuson-Stevens Fishery Conservation and Management Act (16 U.S.C 1801 
                    <E T="03">et seq.</E>
                    ), and regulations at 50 CFR 600.745(b) concerning exempted fishing.
                </P>
                <P>The proposed species collection involves activities covered by regulations implementing the Fishery Management Plan (FMP) for the Snapper-Grouper Fishery of the South Atlantic Region and the FMP for Coral, Coral Reefs, and Live/Hard Bottom Habitats of the South Atlantic Region. The applicant requires authorization to opportunistically collect 878 live fish in the South Atlantic snapper-grouper complex, and a specified quantity of live rock. The fish, listed by common name (total number of fish), and amount of live rock to be harvested over a 2-year period by North Carolina Aquariums includes: red hind (16), rock hind (16), red grouper (16), gag (16), scamp (16), red porgy (16), yellowfin grouper (9), yellowmouth grouper (16), snowy grouper (12), silk snapper (16), vermilion snapper (78), tomtate (200), smallmouth grunt (100), cottonwick (200), yellowedge grouper (9), graysby (16), coney (16), yellowtail snapper (84), schoolmaster snapper (26), and 300 lb (136 kg) of live rock.</P>
                <P>Specimens would be collected in Federal waters from 3 miles (4.8 km) offshore out to 100 fathoms (182 m), from 33°10′ N lat. to 36°30′ N lat. off North Carolina. The project proposes to use hook-and-line gear, black sea bass pots and minnow traps to collect fish, and SCUBA gear to collect live rock by hand. This EFP would authorize sampling operations to be conducted on three vessels to be named by North Carolina Aquariums and designated in the EFP. The specimens would be opportunistically collected year-round for a period of up to 2 years, commencing on the date of issuance of the EFP. The EFP would not authorize the collection of species with an annual catch limit of zero (Red snapper, Warsaw grouper, and Speckled hind).</P>
                <P>The overall intent of the project is to incorporate North Carolina native species into the educational exhibits at the four aquariums located at Pine Knoll Shores, Roanoke Island, Fort Fisher, and Jeanette's Ocean Pier, North Carolina. The aquariums use these displays of native North Carolina habitats and species to teach the public about conservation of these resources.</P>
                <P>NMFS finds this application warrants further consideration. Based on a preliminary review, NMFS intends to issue an EFP. Possible conditions the agency may impose on this permit, if it is indeed granted, include but are not limited to, a prohibition of conducting research within marine protected areas, marine sanctuaries, special management zones, or artificial reefs without additional authorization. Additionally, NMFS prohibits the possession of Nassau grouper, goliath grouper, red snapper, speckled hind or Warsaw grouper, and requires any sea turtles taken incidentally during the course of fishing or scientific research activities to be handled with due care to prevent injury to live specimens, observed for activity, and returned to the water. The EFP would specify that any harvest of live rock would have to be replaced by an equivalent amount of new rock substrate, or be obtained from a commercial (aquaculture) source. A final decision on the issuance of the EFP will depend on NMFS' review of public comments received on the application, consultations with the affected state, the South Atlantic Fishery Management Council, and the U.S. Coast Guard, and a determination that it is consistent with all applicable laws.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                         16 U.S.C 1801 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <PRTPAGE P="66274"/>
                    <DATED>Dated: October 21, 2011.</DATED>
                    <NAME>Emily H. Menashes,</NAME>
                    <TITLE>Acting Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27745 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <RIN>RIN 0648-XA788</RIN>
                <SUBJECT>North Pacific Fishery Management Council (NPFMC); Public Meetings</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of public meetings.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The North Pacific Fishery Management Council's (Council) Gulf of Alaska (GOA) and Bering Sea/Aleutian Islands (BS/AI) Groundfish Plan Teams will meet in Seattle.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>November 14-18, 2011. The meetings will begin at 9 a.m., Monday, November 14, and continue through Friday, November 18, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meetings will be held at the Alaska Fisheries Science Center, 7600 Sand Point Way, NE., Building 4, Observer Training Room (GOA Plan Team) and Traynor Room (BS/AI Plan Team), Seattle, WA.</P>
                    <P>
                        <E T="03">Council address:</E>
                         North Pacific Fishery Management Council, 605 W. 4th Ave., Suite 306, Anchorage, AK 99501-2252.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jane DiCosimo or Diana Stram, NPFMC; 
                        <E T="03">telephone:</E>
                         (907) 271-2809.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Plan Teams will compile and review the annual Groundfish Stock Assessment and Fishery Evaluation Report (SAFE), including the Economic Report, the Ecosystems Consideration Chapter, the stock assessments for BSAI and GOA groundfish, and recommend final groundfish catch specifications for 2012/13.</P>
                <P>
                    The Agenda is subject to change, and the latest version will be posted at 
                    <E T="03">http://www.alaskafisheries.noaa.gov/npfmc/.</E>
                </P>
                <HD SOURCE="HD1">Special Accommodations</HD>
                <P>These meetings are physically accessible to people with disabilities. Requests for sign language interpretation or other auxiliary aids should be directed to Gail Bendixen, (907) 271-2809, at least 5 working days prior to the meeting date.</P>
                <SIG>
                    <DATED>Dated: October 20, 2011.</DATED>
                    <NAME>Tracey L. Thompson,</NAME>
                    <TITLE>Acting Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27630 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <SUBJECT>Availability of Seats for the Cordell Bank National Marine Sanctuary Advisory Council</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of National Marine Sanctuaries (ONMS), National Ocean Service (NOS), National Oceanic and Atmospheric Administration (NOAA), Department of Commerce (DOC).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for applications.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The ONMS is seeking applications for the following vacant seats on the Cordell Bank National Marine Sanctuary Advisory Council: Education, Primary and Alternate seats; Fishing, Primary and Alternate seats; Research, Alternate seat; Community-at-Large Mann County, Alternate seat; Community-at-Large Sonoma County, Alternate seat. Applicants are chosen based upon their particular expertise and experience in relation to the seat for which they are applying; community and professional affiliations; philosophy regarding the protection and management of marine resources; and possibly the length of residence in the area affected by the sanctuary. Applicants who are chosen as members should expect to serve three-year terms, pursuant to the council's Charter.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applications are due by December 1, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Application kits may be obtained from 
                        <E T="03">http://cordellbank.noaa.gov/</E>
                         or Kaitlin Graiff, 
                        <E T="03">kaitlin.graiff@noaa.gov,</E>
                         P.O. Box 159, Olema, CA 94950. Completed applications should be sent to the above postal or e-mail address, or faxed to 415-663-0315 attn. Kaitlin Graiff.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kaitlin Graiff, Advisory Council Coordinator, 415-663-0314 x105, 
                        <E T="03">kaitlin.graiff@noaa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Cordell Bank National Marine Sanctuary Advisory Council was established in 2001 to ensure continued public participation in the management of the sanctuary. Council seats are occupied by members representing research, conservation, maritime activity, fishing, education, Mann and Sonoma County community-at-large, as well as Federal agency partners. Individual council members act as liaisons between the Sanctuary and their constituent groups. The council holds a minimum of four regular meetings per year, and an annual retreat in the summer.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>
                        16 U.S.C. 1431, 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <EXTRACT>
                    <FP>(Federal Domestic Assistance Catalog Number 11.429 Marine Sanctuary Program)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: October 18, 2011.</DATED>
                    <NAME>Daniel J. Basta,</NAME>
                    <TITLE>Director, Office of National Marine Sanctuaries, National Ocean Service, National Oceanic and Atmospheric Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27584 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-NK-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <RIN>RIN 0648-XA650</RIN>
                <SUBJECT>Small Takes of Marine Mammals Incidental to Specified Activities; Pier 36/Brannan Street Wharf Project in the San Francisco Bay, CA</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; proposed incidental harassment authorization; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NMFS has received a complete and adequate application from the United States Army Corps of Engineers, San Francisco District (USACE), on behalf of the Port of San Francisco (Port), for an Incidental Harassment Authorization (IHA) to take marine mammals, by harassment, incidental to pile driving during construction of the Brannan Street Wharf. Pursuant to the Marine Mammal Protection Act (MMPA), NMFS is proposing to issue an IHA to incidentally harass, by Level B harassment, four species of marine mammals during the specified activity within a specific geographic region and is requesting comments on its proposal.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments and information must be received no later than November 25, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments on the application and this proposal should be addressed to Michael Payne, Chief, Permits, Conservation and Education Division, Office of Protected Resources, National Marine Fisheries Service, 1315 East-West Highway, Silver Spring, MD 20910-3225. The mailbox address for 
                        <PRTPAGE P="66275"/>
                        providing e-mail comments is 
                        <E T="03">ITP.Magliocca@noaa.gov.</E>
                         NMFS is not responsible for e-mail comments sent to addresses other than the one provided here. Comments sent via e-mail, including all attachments, must not exceed a 10-megabyte file size.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All comments received are a part of the public record and will generally be posted to 
                        <E T="03">http://www.nmfs.noaa.gov/pr/permits/incidental.htm</E>
                         without change. All Personal Identifying Information (for example, name, address, etc.) voluntarily submitted by the commenter may be publicly accessible. Do not submit Confidential Business Information or otherwise sensitive or protected information.
                    </P>
                    <P>
                        A copy of the application containing a list of the references used in this document may be obtained by writing to the address specified above, telephoning the contact listed below (see 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        ), or visiting the internet at: 
                        <E T="03">http://www.nmfs.noaa.gov/pr/permits/incidental.htm.</E>
                         Documents cited in this notice may also be viewed, by appointment, during regular business hours, at the aforementioned address.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Michelle Magliocca, Office of Protected Resources, NMFS, (301) 427-8401.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    Sections 101(a)(5)(A) and (D) of the MMPA (16 U.S.C. 1361 
                    <E T="03">et seq.</E>
                    ) direct the Secretary of Commerce to allow, upon request, the incidental, but not intentional, taking of small numbers of marine mammals by United States citizens who engage in a specified activity (other than commercial fishing) within a specific geographical region if certain findings are made and either regulations are issued or, if the taking is limited to harassment, a notice of a proposed authorization is provided to the public for review.
                </P>
                <P>Authorization for incidental takings shall be granted if NMFS finds that the taking will have a negligible impact on the species or stock(s), will not have an unmitigable adverse impact on the availability of the species or stock(s) for subsistence uses (where relevant), and if the permissible methods of taking and requirements pertaining to the mitigation, monitoring and reporting of such takings are set forth. NMFS has defined “negligible impact” in 50 CFR 216.103 as “ * * * an impact resulting from the specified activity that cannot be reasonably expected to, and is not reasonably likely to, adversely affect the species or stock through effects on annual rates of recruitment or survival.”</P>
                <P>Section 101(a)(5)(D) of the MMPA established an expedited process by which citizens of the United States can apply for an authorization to incidentally take small numbers of marine mammals by harassment. Section 101(a)(5)(D) further established a 45-day time limit for NMFS' review of an application, followed by a 30-day public notice and comment period on any proposed authorizations for the incidental harassment of marine mammals. Within 45 days of the close of the comment period, NMFS must either issue or deny the authorization.</P>
                <P>Except with respect to certain activities not pertinent here, the MMPA defines “harassment” as:</P>
                <EXTRACT>
                    <FP>any act of pursuit, torment, or annoyance which (i) has the potential to injure a marine mammal or marine mammal stock in the wild [Level A harassment]; or (ii) has the potential to disturb a marine mammal or marine mammal stock in the wild by causing disruption of behavioral patterns, including, but not limited to, migration, breathing, nursing, breeding, feeding, or sheltering [Level B harassment].</FP>
                </EXTRACT>
                <HD SOURCE="HD1">Summary of Request</HD>
                <P>
                    On May 6, 2011, NMFS received an application from the USACE, on behalf of the Port, requesting an IHA for the take, by Level B harassment, of small numbers of Pacific harbor seals (
                    <E T="03">Phoca vitulina</E>
                    ), California sea lions (
                    <E T="03">Zalophus californianus</E>
                    ), gray whales (
                    <E T="03">Eschrichtius robustus</E>
                    ), and Pacific harbor porpoises (
                    <E T="03">Phocoena phocoena</E>
                    ) incidental to pile driving activities during construction of the Brannan Street Wharf in San Francisco, California. Upon receipt of additional information and a revised application, NMFS determined the application complete and adequate on August 7, 2011.
                </P>
                <P>
                    The Port proposes to construct a pile-supported park that would be known as the “Brannan Street Wharf” and would replace the existing Pier 36 and provide recreational space for the public. The proposed project would require installation of 261 steel and concrete piles and 57,000 square feet (ft
                    <SU>2</SU>
                    ) of new decking. Because elevated sound levels from pile driving have the potential to result in marine mammal harassment, NMFS is proposing to issue an IHA for take incidental to the specified activity.
                </P>
                <HD SOURCE="HD1">Description of the Specified Activity</HD>
                <P>
                    The Port proposes to replace the existing Pier 36 with a pile-supported park along the San Francisco waterfront. The proposed park would provide a new open space for the purpose of public recreation and include the following: a 26,000 ft
                    <SU>2</SU>
                     raised lawn area; a waterside walkway with seating, shelters, and picnic tables; and a 2,000 ft
                    <SU>2</SU>
                     small craft float and accessible gangway for launching non-motorized recreational vessels.
                </P>
                <P>
                    To construct the 57,000 ft
                    <SU>2</SU>
                     open space, the existing overwater Pier 36 structures would be demolished, the existing supporting caissons would be removed, and 261 steel and concrete piles would be installed at the site using vibratory and impact pile driving. Demolition and removal of the caissons is not expected to harass marine mammals because these activities would occur above water and the height of the existing Pier 36 decking prevents marine mammals from hauling out. (The nearest haul-out site is over 3.2 kilometers (km) (2 miles [mi]) away at Yerba Buena Island.) The caissons would be removed using a barge mounted excavator and this method is not expected to generate sound at pressures outside of the ambient noise conditions. Installation of the new cast-in-place concrete decking would also occur above water. Installation of the 261 steel and concrete piles, however, would require in-water pile driving that could produce high-intensity sound and has the potential to harass marine mammals. A breakdown of proposed pile size and type is shown in Table 1.
                </P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,14,r50,14">
                    <TTITLE>Table 1—Summary of Pile Types and Pile Driving Activity</TTITLE>
                    <BOXHD>
                        <CHED H="1">Pile type</CHED>
                        <CHED H="1">Total piles</CHED>
                        <CHED H="1">Pile driver</CHED>
                        <CHED H="1">Max piles per day</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">24-inch octagonal concrete</ENT>
                        <ENT>141</ENT>
                        <ENT>Impact</ENT>
                        <ENT>8</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">24-inch steel shell</ENT>
                        <ENT>116</ENT>
                        <ENT>Vibratory and impact</ENT>
                        <ENT>5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">36-inch steel shell</ENT>
                        <ENT>4</ENT>
                        <ENT>Vibratory and impact</ENT>
                        <ENT>4</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="66276"/>
                <P>Of the 261 piles, about 141 would be 24-inch (in) octagonal concrete piles driven in water depths of 2 to 15 ft mean lower low water. These piles would be driven to a depth of 60 ft below the mudline elevation—like all the other piles—using an impact hammer. Each pile may take 20 minutes to drive into the substrate, which consists of about 20 ft of bay mud underlain by a sand mixture. Up to 800 blows from an impact hammer would be necessary for each concrete pile.</P>
                <P>Of the 261 piles, about 116 would be 24-in steel shell piles driven in water depths of zero to 6 ft mean lower low water. These piles would be installed nearest the shoreline as pier support piles and would be used in place of concrete piles due to the presence of rock dike material along the shore. Installation would include about eight minutes of vibratory pile driving, followed by up to 300 blows from an impact hammer.</P>
                <P>The remaining 4 piles would be 36-in steel shell piles used for the new floating dock. These piles would be installed in water depths of 10 to 15 ft mean lower low water. Each pile installation would begin with five to 15 minutes of vibratory pile driving, followed by about 600 blows from an impact hammer.</P>
                <P>Only one pile type is expected to be installed on any given day. Conservatively assuming the maximum vibratory time and number of impact blows required for each pile, a total of 988 minutes of vibratory driving and 150,000 impact blows would be necessary over the 12-month duration of the project. All vibratory pile driving would use a standard frequency hammer similar to an APE 150, which produces up to 1,800 vibrations per minute. All impact pile driving would use a DelMag D46-32 diesel impact hammer, which produces about 122,000 foot-pounds maximum energy blow at 1.5 seconds per blow on average. A bubble curtain would be used as a sound attenuation device during impact pile driving for the 24-in and 36-in steel shell piles.</P>
                <HD SOURCE="HD2">Region of Activity</HD>
                <P>The proposed activity would occur in the San Francisco Bay at Pier 36, four blocks south of the San Francisco Oakland Bay Bridge. More specifically, this area is located between Pier 30-32 and Pier 38, directly adjacent to the east side of the Embarcadero and within the South of Market district of San Francisco. San Francisco Bay and the adjacent Sacramento-San Joaquin Delta make up one of the largest estuarine systems on the continent. The Bay has undergone extensive industrialization, but remains an important environment for healthy marine mammal populations year round. The area surrounding the proposed activity is an intertidal landscape with heavy industrial use and boat traffic.</P>
                <HD SOURCE="HD2">Dates of Activity</HD>
                <P>Wharf and pier demolition—which is not expected to harass marine mammals—may begin in January 2012 and last for five months. The new wharf construction, including pile driving, is scheduled to begin in May 2012 and end 13 months later; however, pile driving is expected to be complete by December 2012.</P>
                <HD SOURCE="HD2">Sound Propagation</HD>
                <P>For background, sound is a mechanical disturbance consisting of minute vibrations that travel through a medium, such as air or water, and is generally characterized by several variables. Frequency describes the sound's pitch and is measured in hertz (Hz) or kilohertz (kHz), while sound level describes the sound's loudness and is measured in decibels (dB). Sound level increases or decreases exponentially with each dB of change. For example, 10 dB yields a sound level 10 times more intense than 1 dB, while a 20 dB level equates to 100 times more intense, and a 30 dB level is 1,000 times more intense. Sound levels are compared to a reference sound pressure (micro-Pascal) to identify the medium. For air and water, these reference pressures are “re: 20 µPa” and “re: 1 µPa,” respectively. Root mean square (RMS) is the quadratic mean sound pressure over the duration of an impulse. RMS is calculated by squaring all of the sound amplitudes, averaging the squares, and then taking the square root of the average (Urick, 1975). RMS accounts for both positive and negative values; squaring the pressures makes all values positive so that they may be accounted for in the summation of pressure levels (Hastings and Popper, 2005). This measurement is often used in the context of discussing behavioral effects, in part because behavioral effects, which often result from auditory cues, may be better expressed through averaged units rather than by peak pressures.</P>
                <P>A review of numerous pile driving projects with comparable water depth and substrate conditions was conducted to identify source sound level data and estimate potential sound levels for pile driving activities around Pier 36. In their calculations, the Port conservatively assumed that the use of a bubble curtain for steel shell piles would reduce sound levels by 5 dB RMS. A conservative attenuation factor of 16 dB RMS (about 5 dB RMS per doubling of distance) was also assumed in the Port's analysis; sound attenuation would likely be greater than 16 dB RMS for such shallow water pile driving (CalTrans, 2009). Pile driving at Pier 36 is expected to occur in water depths of zero to 15 feet. Maximum sound pressure levels for pile driving activities are shown in Table 2.</P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,r50,xls48,xls48">
                    <TTITLE>Table 2—Measured Unattenuated Sound Pressure Levels in the Near Field (10 m) During Pile Driving in San Francisco Bay (Caltrans, 2009)</TTITLE>
                    <BOXHD>
                        <CHED H="1">Pile type</CHED>
                        <CHED H="1">Attenuation device</CHED>
                        <CHED H="1">
                            Sound level
                            <LI>(impact)</LI>
                        </CHED>
                        <CHED H="1">
                            Sound level
                            <LI>(vibratory)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">24-in octagonal concrete</ENT>
                        <ENT>None</ENT>
                        <ENT>170 dB</ENT>
                        <ENT>n/a</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">24-in steel shell</ENT>
                        <ENT>Bubble curtain</ENT>
                        <ENT>190 dB</ENT>
                        <ENT>165 dB</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">36-in steel shell</ENT>
                        <ENT>Bubble curtain</ENT>
                        <ENT>190 dB</ENT>
                        <ENT>175 dB</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Description of Marine Mammals in the Area of the Specified Activity</HD>
                <P>
                    Marine mammals with confirmed occurrences in San Francisco Bay are the Pacific harbor seal, California sea lion, gray whale, harbor porpoise, humpback whale (
                    <E T="03">Megaptera noveangliae</E>
                    ), and sea otter (
                    <E T="03">Enhydra lutris</E>
                    ). However, humpback whales are considered extremely rare in San Francisco Bay and are highly unlikely to be present in the project vicinity during pile driving. Sea otters are managed by the United States Fish and Wildlife Service. Therefore, these two species are not discussed further.
                    <PRTPAGE P="66277"/>
                </P>
                <HD SOURCE="HD2">Pacific Harbor Seals</HD>
                <P>Pacific harbor seals reside in coastal and estuarine waters off Baja, California, north to British Columbia, west through the Gulf of Alaska, and in the Bering Sea. The most recent harbor seal counts estimate the California stock of Pacific harbor seals at 34,233 individuals. The population appears to be stabilizing at what may be their carrying capacity, and human-caused mortality is declining (NMFS, 2005). The California stock of Pacific harbor seals is not listed under the Endangered Species Act (ESA) nor considered depleted under the MMPA.</P>
                <P>In California, approximately 400-500 harbor seal haul-out sites are widely distributed along the mainland and offshore islands, including intertidal sandbars, rocky shores, and beaches. The northside of Yerba Buena Island is the closest haul-out to the project location, approximately 3.2 km (2 mi) from Pier 36. Although harbor seals use this haul-out year-round, Yerba Buena Island is not considered a pupping site. In California, breeding occurs from March to May, and pupping between April and May depending on local populations. Harbor seals around Pier 36 would likely be transiting to and from their closest haul-out (Yerba Buena Island) or opportunistically foraging. Herring spawning events could result in harbor seals congregating and approaching the action area sporadically in an unpredictable manner (pers. comm., M. DeAngelis to M. Magliocca). </P>
                <P>
                    Pinnipeds produce a wide range of social signals, most occurring at relatively low frequencies (Southall 
                    <E T="03">et al.,</E>
                     2007), suggesting that hearing is keenest at these frequencies. Pinnipeds communicate acoustically both on land and underwater, but have different hearing capabilities dependent upon the medium (air or water). Based on numerous studies, as summarized in Southall 
                    <E T="03">et al.</E>
                     (2007), pinnipeds are more sensitive to a broader range of sound frequencies underwater than in air. Underwater, pinnipeds can hear frequencies from 75 Hz to 75 kHz. In air, pinnipeds can hear frequencies from 75 Hz to 30 kHz (Southall 
                    <E T="03">et al.,</E>
                     2007). 
                </P>
                <HD SOURCE="HD2">California Sea Lions </HD>
                <P>California sea lions reside throughout the Eastern North Pacific Ocean in shallow coastal and estuarine waters, ranging from Central Mexico to British Columbia, Canada. Their primary breeding range extends from Central Mexico to the Channel Islands in Southern California. The United States stock abundance is estimated at 238,000 sea lions (NMFS, 2007). This stock is approaching carrying capacity and is reaching “optimum sustainable population” limits, as defined by the MMPA. California sea lions are not listed under the ESA nor considered depleted under the MMPA. </P>
                <P>Sandy beaches are preferred habitat for haul-out sites, but marina docks, jetties, and buoys are often used in California for resting, breeding, and molting. In San Francisco Bay, sea lions have been observed at Angel Island and are known to haul out on buoys and floating docks near Pier 39, which is about 3.6 km (2.2 mi) north of the proposed project site. Sea lions usually appear at Pier 39 after returning from the Channel Islands at the beginning of August. No other sea lion haul-out sites have been identified in the Bay and no pupping has been observed in the Bay. Sea lions observed within this area may be transiting to and from nearby piers or opportunistically foraging. </P>
                <P>
                    Pinnipeds produce a wide range of social signals, most occurring at relatively low frequencies (Southall 
                    <E T="03">et al.,</E>
                     2007), suggesting that hearing is keenest at these frequencies. Pinnipeds communicate acoustically both on land and underwater, but have different hearing capabilities dependent upon the medium (air or water). Based on numerous studies, as summarized in Southall 
                    <E T="03">et al.</E>
                     (2007), pinnipeds are more sensitive to a broader range of sound frequencies underwater than in air. Underwater, pinnipeds can hear frequencies from 75 Hz to 75 kHz. In air, pinnipeds can hear frequencies from 75 Hz to 30 kHz (Southall 
                    <E T="03">et al.,</E>
                     2007). 
                </P>
                <HD SOURCE="HD2">Harbor Porpoises </HD>
                <P>Harbor porpoises have a wide and discontinuous range that includes the North Atlantic and North Pacific. In the Eastern North Pacific, harbor porpoises are found in coastal and inland waters from Point Conception, California to Alaska. Harbor porpoises in United States waters are divided into 10 stocks, based on genetics, movement patterns, and management. Any harbor porpoises encountered during the proposed project would likely be part of the San Francisco-Russian River stock, which has an estimated abundance of 9,189 animals. This stock appeared to be stable or declining between 1988 and 1991 and has steadily increased since 1993, although not significantly. Harbor porpoises are not commonly sighted in San Francisco Bay, but have been observed traveling in small pods of two to three animals on occasion (pers. comm., M. DeAngelis to M. Magliocca) and sightings have been reported by the California Department of Transportation. The closest sightings to Pier 36 have been near Yerba Buena Island, about 3.2 km (2 mi) away. They may occur in the action area during a time when they could be affected by pile driving activities; however, their presence in the vicinity is rare. Harbor porpoises in California are not listed under the ESA nor considered depleted under the MMPA. </P>
                <P>Cetaceans are divided into three functional hearing groups: low-frequency, mid-frequency, and high-frequency. Harbor porpoises are considered high-frequency cetaceans and their estimated auditory bandwidth (lower to upper frequency hearing cut-off) ranges from 200 Hz to 180 kHz. </P>
                <HD SOURCE="HD2">Gray Whales </HD>
                <P>Gray whales are large mysticetes, or baleen whales, found mainly in shallow coastal waters of the North Pacific Ocean. Two isolated geographic distributions of gray whales exist: the Eastern North Pacific stock and the Western North Pacific stock. The Eastern North Pacific stock migrates as far south as Baja, California for breeding and calving in the winter and as far north as the Bering and Chukchi Seas for summer feeding. During migration, gray whales occasionally enter rivers and bays in very low numbers. They could potentially be in the proposed project area during pile driving activities. The most recent 2008 stock assessment report estimated the Eastern North Pacific stock to be approximately 18,813 individuals with an increasing population trend over the past several decades. Gray whales were delisted from the ESA in 1994 and are not considered depleted under the MMPA. </P>
                <P>
                    Gray whales, like other baleen whales, are in the low-frequency hearing group. There are no empirical data on gray whale hearing; however, Wartzok and Ketten (1999) suggest that mysticete hearing is most sensitive at the same frequencies at which they vocalize. Underwater sounds produced by gray whales range from 20 Hz to 20 kHz (Richardson 
                    <E T="03">et al.,</E>
                     1995). 
                </P>
                <HD SOURCE="HD1">Potential Effects on Marine Mammals </HD>
                <P>
                    The proposed action consists of both in-water and above-water components, but the only activity with the potential to take marine mammals is pile driving. Elevated in-water sound levels from pile driving in the proposed project area may temporarily impact marine mammal behavior. Elevated in-air sound levels are not a concern because the nearest pinniped haul-out is approximately 3.2 km (2 mi) away. Marine mammals are continually exposed to many sources of sound. For example, lightning, rain, sub-sea earthquakes, and animals are 
                    <PRTPAGE P="66278"/>
                    natural sound sources throughout the marine environment. Marine mammals produce sounds in various contexts and use sound for various biological functions including, but not limited to, (1) Social interactions; (2) foraging; (3) orientation; and (4) predator detection. Interference with producing or receiving these sounds may result in adverse impacts. Audible distance or received levels will depend on the sound source, ambient noise, and the sensitivity of the receptor (Richardson 
                    <E T="03">et al.,</E>
                     1995). Marine mammal reactions to sound may depend on sound frequency, ambient sound, what the animal is doing, and the animal's distance from the sound source (Southall 
                    <E T="03">et al.,</E>
                     2007). 
                </P>
                <HD SOURCE="HD2">Hearing Impairment </HD>
                <P>
                    Marine mammals may experience temporary or permanent hearing impairment when exposed to loud sounds. Hearing impairment is classified by temporary threshold shift (TTS) and permanent threshold shift (PTS). There are no empirical data for when PTS first occurs in marine mammals; therefore, it must be estimated from when TTS first occurs and from the rate of TTS growth with increasing exposure levels. PTS is likely if the animal's hearing threshold is reduced by ≥40 dB of TTS. PTS is considered auditory injury (Southall 
                    <E T="03">et al.,</E>
                     2007) and occurs in a specific frequency range and amount. Irreparable damage to the inner or outer cochlear hair cells may cause PTS; however, other mechanisms are also involved, such as exceeding the elastic limits of certain tissues and membranes in the middle and inner ears and resultant changes in the chemical composition of the inner ear fluids (Southall 
                    <E T="03">et al.,</E>
                     2007). Due to proposed mitigation measures and source levels in the proposed project area, NMFS does not expect marine mammals to be exposed to PTS levels. 
                </P>
                <HD SOURCE="HD2">Temporary Threshold Shift (TTS) </HD>
                <P>
                    TTS is the mildest form of hearing impairment that can occur during exposure to a loud sound (Kryter, 1985). While experiencing TTS, the hearing threshold rises and a sound must be louder in order to be heard. TTS can last from minutes or hours to days, occurs in specific frequency ranges (
                    <E T="03">i.e.,</E>
                     an animal might only have a temporary loss of hearing sensitivity between the frequencies of 1 and 10 kHz), and can occur to varying degrees (
                    <E T="03">e.g.,</E>
                     an animal's hearing sensitivity might be reduced by 6 dB or by 30 dB). For sound exposures at or somewhat above the TTS-onset threshold, hearing sensitivity recovers rapidly after exposure to the sound ends. Few data on sound levels and durations necessary to elicit mild TTS have been obtained for marine mammals. Southall 
                    <E T="03">et al.</E>
                     (2007) considers a 6 dB TTS (
                    <E T="03">i.e.,</E>
                     baseline thresholds are elevated by 6 dB) sufficient to be recognized as an unequivocal deviation and thus a sufficient definition of TTS-onset. Because it is non-injurious, NMFS considers TTS as Level B harassment that is mediated by physiological effects on the auditory system; however, NMFS does not consider onset TTS to be the lowest level at which Level B harassment may occur. 
                </P>
                <P>
                    Southall 
                    <E T="03">et al.</E>
                     (2007) summarizes underwater pinniped data from Kastak 
                    <E T="03">et al.</E>
                     (2005), indicating that a tested harbor seal showed a TTS of around 6 dB when exposed to a non-pulse noise at SPL 152 dB re: 1 μPa for 25 minutes. In contrast, a tested sea lion exhibited TTS-onset at 174 dB re: 1 μPa under the same conditions as the harbor seal. Data from a single study on underwater pulses found no signs of TTS-onset in sea lions at exposures up to 183 dB re: 1 μPa (peak-to-peak) (Finneran 
                    <E T="03">et al.,</E>
                     2003). There is no information on species-specific TTS for harbor porpoises or gray whales. 
                </P>
                <HD SOURCE="HD2">Behavioral Effects </HD>
                <P>
                    There are limited data available on the behavioral effects of non-pulse noise (for example, vibratory pile driving) on pinnipeds while underwater; however, field and captive studies to date collectively suggest that pinnipeds do not react strongly to exposures between 90 and 140 dB re: 1 microPa; no data exist from exposures at higher levels. Jacobs and Terhune (2002) observed wild harbor seal reactions to high-frequency acoustic harassment devices around nine sites. Seals came within 44 m of the active acoustic harassment devices and failed to demonstrate any behavioral response when received SPLs were estimated at 120-130 dB. In a captive study (Kastelein, 2006), scientists subjected a group of seals to non-pulse sounds between 8 and 16 kHz. Exposures between 80 and 107 dB did not induce strong behavioral responses; however, a single observation from 100 to 110 dB indicated an avoidance response. The seals returned to baseline conditions shortly following exposure. Southall 
                    <E T="03">et al.</E>
                     (2007) notes contextual differences between these two studies; the captive animals were not reinforced with food for remaining in the noise fields, whereas free-ranging animals may have been more tolerant of exposures because of motivation to return to a safe location or approach enclosures holding prey items. Vibratory and impact pile driving may result in anticipated hydroacoustic levels between 165 and 190 dB root mean square. Southall 
                    <E T="03">et al.</E>
                     (2007) reviewed relevant data from studies involving pinnipeds exposed to pulse sounds and concluded that exposures to 150 to 180 dB generally have limited potential to induce avoidance behavior. 
                </P>
                <P>
                    No known data exist for sound levels resulting from the type of vibratory hammer and pile sizes that would be used at the proposed project site; however, measured sound levels for the “King Kong” vibratory hammer used in Richmond, California ranged between 163 and 180 dB RMS (Illingworth and Rodkin, 2007). Sound levels at the proposed project site are expected to be lower because the vibratory hammer being used has an expected sound level of 165 dB for 24-in piles and 175 dB for 36-in piles. In addition, San Francisco Bay is highly industrialized and masking of the pile driver by other vessels and anthropogenic noise within the action area may, especially in the nearby shipping channel, make construction sounds difficult to hear at greater distances. Underwater ambient noise levels along the San Francisco waterfront may be around 133 dB RMS, based on measurements from the nearby Oakland Outer Harbor (Caltrans, 2009). Seals would likely also exhibit tolerance or habituation (Richardson 
                    <E T="03">et al.,</E>
                     1999) due to the amount of anthropogenic noise within the proposed project area and San Francisco Bay as a whole. 
                </P>
                <P>
                    No impacts to marine mammal reproduction are anticipated because there are no known pinniped haul-outs or rookeries within the proposed project area and San Francisco Bay is not a known breeding ground for cetaceans. Marine mammals may avoid the area around the hammer, thereby reducing their exposure to elevated sound levels. NMFS expects any impacts to marine mammal behavior to be temporary, Level B harassment (for example, avoidance or alteration of behavior). The Port conservatively assumes that five 24-in concrete piles would be installed per day, three 24-in steel piles would be installed per day, and four 36-in steel piles would be installed per day. Considering that only one pile type is expected to be installed on any given day, the maximum number of pile driving days is expected to be 69 over the eight-month period. Marine mammal injury or mortality is not likely, as the 180 dB isopleth (NMFS' Level A harassment threshold for cetaceans) for the impact hammer is 42 m (138 ft) and would be continuously monitored for marine mammals. Impact pile driving would 
                    <PRTPAGE P="66279"/>
                    cease if a marine mammal is observed nearing or within a Level A harassment exclusion zone (50 m [164 ft]). For these reasons, NMFS expects any changes to marine mammal behavior to be temporary. 
                </P>
                <HD SOURCE="HD1">Anticipated Effects on Habitat </HD>
                <P>
                    No permanent detrimental impacts to marine mammal habitat are expected to result from the proposed project. Pile driving (resulting in temporary ensonification) may impact prey species and marine mammals by resulting in avoidance or abandonment of the area; however, these impacts are expected to be local and temporary. Site conditions are expected to be improved or substantively unchanged from existing conditions. The proposed project would result in the net removal of approximately 3,550 ft
                    <SU>2</SU>
                     of pile fill and clearing of 47,000 ft
                    <SU>2</SU>
                     of timber debris that has collapsed at the end of Pier 36. This debris includes 350-400 creosote-treated wood pilings. Creosote can leach out of the wood over time, potentially causing long-term impacts to marine species. The proposed project would also result in a net reduction of 47,000 ft
                    <SU>2</SU>
                     of shadow fill (shading over the water). This increase of unshaded water is expected to be beneficial to benthic invertebrates, fish, and marine mammals through restoration of ambient light conditions and increased biological productivity. Overall, the proposed activity is not expected to cause significant or long-term adverse impacts on marine mammal habitat. 
                </P>
                <HD SOURCE="HD1">Proposed Mitigation </HD>
                <P>In order to issue an IHA under section 101(a)(5)(D) of the MMPA, NMFS must set forth the permissible methods of taking pursuant to such activity, and other means of effecting the least practicable adverse impact on such species or stock and its habitat, paying particular attention to rookeries, mating grounds, and areas of similar significance, and on the availability of such species or stock for taking for certain subsistence uses. </P>
                <P>The Port proposed the following mitigation measures to minimize adverse impacts to marine mammals: </P>
                <HD SOURCE="HD2">Sound Attenuation Device </HD>
                <P>When using impact pile driving to install steel piles in water depths greater than two feet, an unconfined bubble curtain would be used to reduce hydroacoustic sound levels to avoid the potential for injury. The bubble curtain is expected to reduce sound levels by at least 5 dB. </P>
                <HD SOURCE="HD2">Establishment of an Exclusion Zone </HD>
                <P>During all in-water impact pile driving, the Port would establish a preliminary marine mammal exclusion zone with 50 m (164 ft) radius around each pile to avoid exposure to sounds at or above 180 dB. This includes an 8-m (26-ft) buffer zone to further avoid marine mammals from entering the 180 dB isopleth. The exclusion zone would be monitored during all impact pile driving to ensure that no marine mammals enter the 50-m (164-ft) radius. The purpose of this area is to prevent Level A harassment (injury) of any marine mammal species. Once underwater sound measurements are taken, the exclusion zone may be adjusted accordingly so that marine mammals are not exposed to Level A harassment sound pressure levels. A safety zone for vibratory pile driving or installation of concrete piles is unnecessary as source levels would not exceed the Level A harassment threshold. </P>
                <HD SOURCE="HD2">Pile Driving Shut Down and Delay Procedures </HD>
                <P>If a protected species observer sees a marine mammal within or approaching the exclusion zone prior to start of impact pile driving, the observer would notify the on-site resident engineer (or other authorized individual) who would then be required to delay pile driving until the marine mammal has moved outside of the exclusion zone or if the animal has not been resighted within 15 minutes for pinnipeds or 30 minutes for cetaceans. If a marine mammal is sighted within or on a path toward the exclusion zone during pile driving, pile driving should cease until that animal has cleared and is on a path away from the exclusion zone or 15/30 minutes (pinnipeds/cetaceans) has lapsed since the last sighting. </P>
                <HD SOURCE="HD2">Soft-Start Procedures </HD>
                <P>A “soft-start” technique would be used at the beginning of each pile installation to allow any marine mammal that may be in the immediate area to leave before the pile hammer reaches full energy. For vibratory pile driving, the soft-start procedure requires contractors to initiate noise from the vibratory hammer for 15 seconds at 40-60 percent reduced energy followed by a 1-minute waiting period. The procedure would be repeated two additional times before full energy may be achieved. For impact hammering, contractors would be required to provide an initial set of three strikes from the impact hammer at 40 percent energy, followed by a 1-minute waiting period, then two subsequent three-strike sets. Soft-start procedures would be conducted prior to driving each pile if hammering ceases for more than 30 minutes. </P>
                <HD SOURCE="HD2">Monitoring for Herring </HD>
                <P>Monitoring for herring spawning events would be conducted on a daily basis between December 1 and February (although pile driving is expected to be complete in December). If a herring spawning event is observed, in-water work would cease for a period of two weeks following the spawning event (a measure designed to reduce impacts to fish). Pinniped presence can be sporadic and unpredictable during herring runs in San Francisco Bay; therefore, this mitigation measure would minimize impacts to marine mammals. </P>
                <P>NMFS has carefully evaluated the applicant's proposed mitigation measures and considered a range of other measures in the context of ensuring that NMFS prescribes the means of effecting the least practicable adverse impact on the affected marine mammal species and stocks and their habitat. Our evaluation of potential measures included consideration of the following factors in relation to one another: (1) The manner in which, and the degree to which, the successful implementation of the measure is expected to minimize adverse impacts to marine mammals; (2) the proven or likely efficacy of the specific measure to minimize adverse impacts as planned; and (3) the practicability of the measure for applicant implementation, including consideration of personnel safety, and practicality of implementation. </P>
                <P>Based on our evaluation of the applicant's proposed measures, NMFS has preliminarily determined that the proposed mitigation measures provide the means of effecting the least practicable adverse impacts on marine mammals species or stocks and their habitat, paying particular attention to rookeries, mating grounds, and areas of similar significance. </P>
                <HD SOURCE="HD1">Proposed Monitoring and Reporting </HD>
                <P>
                    In order to issue an IHA for an activity, section 101(a)(5)(D) of the MMPA states that NMFS must set forth “requirements pertaining to the monitoring and reporting of such taking.” The MMPA implementing regulations at 50 CFR 216.104 (a)(13) indicate that requests for IHAs must include the suggested means of accomplishing the necessary monitoring and reporting that will result in increased knowledge of the species and of the level of taking or impacts on 
                    <PRTPAGE P="66280"/>
                    populations of marine mammals that are expected to be present. 
                </P>
                <P>Hydroacoustic monitoring would be performed at the initial installation of each pile type (24-in concrete, 24-in steel, and 36-in steel) to ensure that the harassment isopleths are not extending past the calculated distances described in this notice. The Port must designate at least one biologically-trained, on-site individual, approved in advance by NMFS, to monitor the Level B harassment zone area for marine mammals 30 minutes before, during, and 30 minutes after all impact pile driving activities and call for shut down if any marine mammal is observed within or approaching the designated exclusion zone (preliminarily set at 50 m [164 ft]). In addition, at least two NMFS-approved protected species observers would conduct behavioral monitoring out to 1,900 m during all vibratory pile driving for the first two weeks of activity to validate take estimates and evaluate the behavioral impacts piles driving has on marine mammals out to the Level B harassment isopleth. If there are no observations of marine mammals within the Level B harassment isopleth during this time, behavioral monitoring may be reduced to a level agreed upon by the applicant and NMFS. Note that for impact hammering, the initial Level B (160 dB) harassment isopleths are 42 m (138 ft) for the concrete piles and 750 m (2,460 ft) for the steel piles. For vibratory hammering, the initial estimated distance is 1,900 m (6,233 ft). If light condition is low (such as early morning or late afternoon), protected species observers would use infrared scopes to conduct their observations. </P>
                <P>Protected species observers would be provided with the equipment necessary to effectively monitor for marine mammals (for example, high-quality binoculars, spotting scopes, compass, and range-finder) in order to determine if animals have entered into the exclusion zone or Level B harassment isopleth and to record species, behaviors, and responses to pile driving. If hydroacoustic monitoring indicates that threshold isopleths are greater than originally calculated, the Port would contact NMFS within 48 hours and make the necessary adjustments. Likewise, if threshold isopleths are actually less than originally calculated, adjustments may be made. Protected species observers would be required to submit a report to NMFS within 90 days of completion of pile driving. The report would include data from marine mammal sightings (such as species, group size, and behavior), any observed reactions to construction, distance to operating pile hammer, and construction activities occurring at time of sighting. </P>
                <HD SOURCE="HD1">Estimated Take by Incidental Harassment </HD>
                <P>Except with respect to certain activities not pertinent here, the MMPA defines “harassment” as: </P>
                <EXTRACT>
                    <FP>any act of pursuit, torment, or annoyance which (i) Has the potential to injure a marine mammal or marine mammal stock in the wild [Level A harassment]; or (ii) has the potential to disturb a marine mammal or marine mammal stock in the wild by causing disruption of behavioral patterns, including, but not limited to, migration, breathing, nursing, breeding, feeding, or sheltering [Level B harassment]. </FP>
                </EXTRACT>
                <P>Based on the application and subsequent analysis, the impact of the described pile driving operations may result in, at most, short-term modification of behavior by small numbers of marine mammals within the action area. Marine mammals may avoid the area or temporarily alter their behavior at time of exposure. </P>
                <P>
                    Current NMFS practice regarding exposure of marine mammals to anthropogenic noise is that in order to avoid the potential for injury (PTS), cetaceans and pinnipeds should not be exposed to impulsive sounds of 180 and 190 dB or above, respectively. This level is considered precautionary as it is likely that more intense sounds would be required before injury would actually occur (Southall 
                    <E T="03">et al.,</E>
                     2007). Potential for behavioral harassment (Level B) is considered to have occurred when marine mammals are exposed to sounds at or above 160 dB for impulse sounds (such as impact pile driving) and 120 dB for non-pulse noise (such as vibratory pile driving). These levels are also considered precautionary. 
                </P>
                <P>Distances to NMFS' harassment thresholds were calculated based on the sound levels at each source and the expected attenuation rate of sound (Table 3). Two sets of threshold distances were identified: one for concrete piles and one for steel piles. The threshold distances listed for the steel piles are those expected from the 36-in steel pile driving activities, as they would also encompass the isopleths for the 24-in steel piles. The 42-m (268-ft) distance to the Level A harassment threshold provides protected species observers plenty of time and adequate visibility to prevent marine mammals from entering the area during impact pile driving. This would prevent marine mammals from being exposed to sound levels that reach the Level A harassment threshold. In-air sound from pile driving also has the potential to affect marine mammals. However, in-air sound is not a concern here because there are no pinniped haul-outs near the project area.</P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s50,xs100,xs100">
                    <TTITLE>Table 3—Calculated Underwater Distances to NMFS' Marine Mammal Harassment Threshold Levels</TTITLE>
                    <BOXHD>
                        <CHED H="1">Threshold</CHED>
                        <CHED H="1">
                            Distance from source
                            <LI>(24-in concrete piles)</LI>
                        </CHED>
                        <CHED H="1">
                            Distance from source
                            <LI>(36-in steel piles)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">120 dB RMS (Level B—continuous)</ENT>
                        <ENT>n/a</ENT>
                        <ENT>1,900 m (6,233 ft).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">160 dB RMS (Level B—impulse)</ENT>
                        <ENT>42 m (138 ft)</ENT>
                        <ENT>750 m (2,460 ft).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">180/190 dB RMS (Level A)</ENT>
                        <ENT>n/a</ENT>
                        <ENT>42 m (138 ft).</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    The estimated number of marine mammals potentially taken is based on marine mammal monitoring reports prepared by the California Department of Transportation during similar activities in San Francisco Bay and on discussions with the NMFS Southwest Regional Office. The California Department of Transportation's San Francisco-Oakland Bay Bridge marine mammal monitoring reports were used to estimate the number of pinnipeds near the Pier 36/Brannan Street Wharf area as both sites are relatively close in distance and are similar in bathymetric features. However, monitoring conducted for the San Francisco-Oakland Bay Bridge project was in close proximity to a haul-out area, while the Pier 36/Brannan Street Wharf location is in an area of high commercial boat activity and no adjacent haul-outs. Therefore, the Caltrans data likely overestimate marine mammal abundance for the Pier 36/Brannan Street Wharf location. Based on consultation with the NMFS Southwest Regional Office, review of the monitoring reports described above, and the estimated number of pile driving 
                    <PRTPAGE P="66281"/>
                    days, the Port requested authorization for the incidental take of 138 harbor seals (an average of 2 per day), 69 California sea lions (an average of 1 per day), 69 harbor porpoises (an average of 1 per day), and 2 gray whales (2 annually). Based on further consultation with the NMFS Southwest Regional Office and previous authorizations in this region, NMFS is proposing to authorize the take of five gray whales annually, rather than two. These numbers indicate the maximum number of animals expected to occur within the largest Level B harassment isopleth (1,900 m). 
                </P>
                <HD SOURCE="HD3">Negligible Impact and Small Numbers Analysis and Determination</HD>
                <P>NMFS has defined “negligible impact” in 50 CFR 216.103 as “* * *an impact resulting from the specified activity that cannot be reasonably expected to, and is not reasonably likely to, adversely affect the species or stock through effects on annual rates of recruitment or survival.” In making a negligible impact determination, NMFS considers a number of factors which include, but are not limited to, number of anticipated injuries or mortalities (none of which would be authorized here), number, nature, intensity, and duration of Level B harassment, and the context in which takes occur.</P>
                <P>As described above, marine mammals would not be exposed to activities or sound levels which would result in injury (PTS), serious injury, or mortality. Pile driving would occur in shallow coastal waters of the Columbia River. The action area (waters around Terminal 5) is not considered significant habitat for pinnipeds. The closest haul-out is 3.2 km (2 mi) away, which is well outside the project area's largest harassment zone. Marine mammals approaching the action area would likely be traveling or opportunistically foraging. The amount of take the Port has requested, and NMFS proposes to authorize, is considered small (less than one percent) relative to the estimated populations of 34,233 Pacific harbor seals, 238,000 California sea lions, 9,189 harbor porpoises, and 18,813 gray whales. Marine mammals may be temporarily impacted by pile driving noise. However, marine mammals are expected to avoid the area, thereby reducing exposure and impacts. Pile driving activities are expected to occur for approximately 69 days. Furthermore, San Francisco Bay is a highly industrialized area, so animals are likely tolerant or habituated to anthropogenic disturbance, including low level vibratory pile driving operations, and noise from other anthropogenic sources (such as vessels) may mask construction related sounds. There is no anticipated effect on annual rates of recruitment or survival of affected marine mammals.</P>
                <P>Based on the analysis contained herein of the likely effects of the specified activity on marine mammals and their habitat, and taking into consideration the implementation of the mitigation and monitoring measures, NMFS preliminarily determines that the Port's proposed pile driving activities will result in the incidental take of small numbers of marine mammals, by Level B harassment only, and that the total taking from will have a negligible impact on the affected species or stocks.</P>
                <HD SOURCE="HD1">Impact on Availability of Affected Species for Taking for Subsistence Uses</HD>
                <P>There are no relevant subsistence uses of marine mammals implicated by this action.</P>
                <HD SOURCE="HD1">Endangered Species Act (ESA)</HD>
                <P>No marine mammal species listed under the ESA are anticipated to occur within the action area. Therefore, section 7 consultation under the ESA is not required.</P>
                <HD SOURCE="HD1">National Environmental Policy Act (NEPA)</HD>
                <P>
                    In compliance with the National Environmental Policy Act of 1969 (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), as implemented by the regulations published by the Council on Environmental Quality (40 CFR parts 1500-1508), and NOAA Administrative Order 216-6, NMFS is preparing an Environmental Assessment (EA) to consider the direct, indirect, and cumulative effects to marine mammals and other applicable environmental resources resulting from issuance of a one-year IHA and the potential issuance of future authorizations for incidental harassment for the ongoing project. Upon completion, this EA will be available on the NMFS Web site listed in the beginning of this document (see 
                    <E T="02">ADDRESSES</E>
                    ).
                </P>
                <SIG>
                    <DATED>Dated: October 19, 2011.</DATED>
                    <NAME>Helen M. Golde,</NAME>
                    <TITLE>Deputy Director, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27739 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <DEPDOC>[Docket ID DOD-2010-OS-0034]</DEPDOC>
                <SUBJECT>Defense Transportation Regulation, Part IV</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>United States Transportation Command (USTRANSCOM), Department of Defense (DoD).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of announcement.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Reference 
                        <E T="04">Federal Register</E>
                         Notice (FRN), Docket ID: DOD-2010-OS-0034, published April 1, 2010 (75 FR 16445-16446) and subsequently revised April 5, 2011 (76 FR 18737). We have taken industry recommendations into consideration regarding the incorporation of local moves into the intrastate/interstate program. The Surface Deployment and Distribution Command (SDDC) is conducting a Direct Procurement Method (DPM) feasibility study to determine how local moves could be better managed to serve our DoD customers. Industry will be notified of any subsequent DoD decisions associated with the future of local moves. We thank our industry partners for their review and important suggestions to improve the Defense Personal Property Program (DP3).
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Jim Teague, United States Transportation Command, TCJ5/4-PI, 508 Scott Drive, Scott Air Force Base, IL 62225-5357; (618) 220-4803.</P>
                    <SIG>
                        <DATED> Dated: October 21, 2011.</DATED>
                        <NAME>Aaron Siegel,</NAME>
                        <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27654 Filed 10-25-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>
                <SUBJECT>Withdrawal of the Notice of Intent To Prepare a Programmatic Environmental Impact Statement for the Stationing and Operation of Joint High Speed Vessels</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of the Army, DoD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of intent; withdrawal.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On February 5, 2010, the Department of the Army announced in the 
                        <E T="04">Federal Register</E>
                         (75 FR 6003) its intention to prepare a Programmatic Environmental Impact Statement (PEIS) for the stationing and operation of up to 12 Joint High Speed Vessels (JHSVs). In May 2011, the Army's JHSVs were transferred to the U.S. Navy; therefore, 
                        <PRTPAGE P="66282"/>
                        the Army is withdrawing the notice of intent.
                    </P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Questions or comments regarding the withdrawal of this action should be forwarded to: Public Affairs Office, U.S. Army Environmental Command, Bldg 2264, Room 209-006, 2450 Connell Road, Fort Sam Houston, TX 78234-7664.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Public Affairs Office at (210) 466-0677 or e-mail 
                        <E T="03">IMCOM-USAECPublicComments@conus.army.mil.</E>
                    </P>
                    <SIG>
                        <NAME>Brenda S. Bowen,</NAME>
                        <TITLE>Army Federal Register Liaison Officer.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27693 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3710-08-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Department of the Army</SUBAGY>
                <SUBJECT>Army Educational Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of the Army, DoD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of open 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 following meeting notice is announced:</P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         U.S. Army War College Subcommittee of the Army Education Advisory Committee.
                    </P>
                    <P>
                        <E T="03">Dates of Meeting:</E>
                         November 15, 2011.
                    </P>
                    <P>
                        <E T="03">Place of Meeting:</E>
                         U.S. Army War College, 122 Forbes Avenue, Carlisle, PA, Command Conference Room, Root Hall, Carlisle Barracks, Pennsylvania 17013.
                    </P>
                    <P>
                        <E T="03">Time of Meeting:</E>
                         8:30 a.m.-12:30 p.m.
                    </P>
                    <P>
                        <E T="03">Proposed Agenda:</E>
                         Receive various information briefings and updates and dialogue with the Commandant on issues and matters related to the continued growth and development of the United States Army War College.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        To request advance approval or obtain further information, contact COL Donald Myers, (717) 245-3907 or 
                        <E T="03">Donald.myers@us.army.mil.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This meeting is open to the public. Interested persons may submit a written statement for consideration by the U.S. Army War College Subcommittee. Written statements should be no longer than two type-written pages and must address: the issue, discussion, and a recommended course of action. Supporting documentation may also be included as needed to establish the appropriate historical context and to provide any necessary background information.</P>
                <P>Individuals submitting a written statement must submit their statement to the Designated Federal Officer at the following address: Attn: Designated Federal Officer, Dept. of Academic Affairs, 122 Forbes Avenue, Carlisle, PA 17013. At any point, however, if a written statement is not received at least 10 calendar days prior to the meeting, which is the subject of this notice, then it may not be provided to or considered by the U.S. Army War College Subcommittee until its next open meeting.</P>
                <P>The Designated Federal Officer will review all timely submissions with the U.S. Army War College Subcommittee Chairperson, and ensure they are provided to members of the U.S. Army War College Subcommittee before the meeting that is the subject of this notice. After reviewing the written comments, the Chairperson and the Designated Federal Officer may choose to invite the submitter of the comments to orally present their issue during an open portion of this meeting or at a future meeting.</P>
                <P>The Designated Federal Officer, in consultation with the U.S. Army War College Subcommittee Chairperson, may, if desired, allot a specific amount of time for members of the public to present their issues for review and discussion by the U.S. Army War College Subcommittee.</P>
                <SIG>
                    <NAME>Donald Myers,</NAME>
                    <TITLE>Colonel, U.S. Army, Executive Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27695 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3710-08-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Defense Acquisition Regulation System</SUBAGY>
                <DEPDOC>[Docket No. DARS-2011-0068-0001]</DEPDOC>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <P>The Defense Acquisition Regulations System has submitted to OMB for clearance, the following proposal for collection of information under the provisions of the Paperwork Reduction Act (44 U.S.C. chapter 35).</P>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Consideration will be given to all comments received by November 25, 2011.</P>
                    <P>
                        <E T="03">Title, Associated Forms and OMB Number:</E>
                         Defense Federal Acquisition Regulation Supplement (DFARS) Part 216, Types of Contracts, and related clauses at DFARS 252.216-7000, Economic Price Adjustment—Basic Steel, Aluminum, Brass, Bronze, or Copper Mill Products; DFARS 252.216-7001, Economic Price Adjustment—Nonstandard Steel Items, and DFARS 252.216-7003, Economic Price Adjustment—Wage Rates or Material Prices Controlled by a Foreign Government; OMB Control Number 0704-0259.
                    </P>
                    <P>
                        <E T="03">Type of Request:</E>
                         Extension.
                    </P>
                    <P>
                        <E T="03">Number of Respondents:</E>
                         2,247.
                    </P>
                    <P>
                        <E T="03">Responses per Respondent:</E>
                         Approximately 2.
                    </P>
                    <P>
                        <E T="03">Annual Responses:</E>
                         4,488.
                    </P>
                    <P>
                        <E T="03">Average Burden per Response:</E>
                         Approximately 4 hours.
                    </P>
                    <P>
                        <E T="03">Annual Burden Hours:</E>
                         17,952.
                    </P>
                    <P>
                        <E T="03">Needs and Uses:</E>
                         The clauses at DFARS 252.216-7000, 252.216-7001, and 252.216-7003 require contractors with fixed-price economic price adjustment contracts to submit information to the contracting officer regarding changes in established material prices or wage rates. The contracting officer uses this information to make appropriate adjustments to contract prices.
                    </P>
                    <P>
                        <E T="03">Affected Public:</E>
                         Businesses or other for-profit and not-for-profit institutions.
                    </P>
                    <P>
                        <E T="03">Frequency:</E>
                         On occasion.
                    </P>
                    <P>
                        <E T="03">Respondent's Obligation:</E>
                         Required to obtain or maintain benefits.
                    </P>
                    <P>
                        <E T="03">OMB Desk Officer:</E>
                         Ms. Jasmeet Seehra.
                    </P>
                    <P>Written comments and recommendations on the proposed information collection should be sent to Ms. Seehra at the Office of Management and Budget, Desk Officer for DoD, Room 10236, New Executive Office Building, Washington, DC 20503.</P>
                    <P>You may also submit comments, identified by docket number and title, by the following method:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        <E T="03">Intructions:</E>
                         All submissions received must include the agency name, docket number, and title for the 
                        <E T="04">Federal Register</E>
                         document. The general policy for comments and other public 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 provided. To confirm receipt of your comment(s), please check 
                        <E T="03">http://www.regulations.gov</E>
                         approximately two to three days after submission to verify posting (except allow 30 days for posting of comments submitted by mail).
                        <PRTPAGE P="66283"/>
                    </P>
                    <P>
                        <E T="03">DoD Clearance Officer:</E>
                         Ms. Patricia Toppings.
                    </P>
                    <P>Written requests for copies of the information collection proposal should be sent to Ms. Toppings at WHS/ESD/Information Management Division, 4800 Mark Center Drive, 2nd Floor, East Tower, Suite 02G09, Alexandria, VA 22350-3100.</P>
                </DATES>
                <SIG>
                    <NAME>Mary Overstreet,</NAME>
                    <TITLE>Editor, Defense Acquisition Regulations System.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27674 Filed 10-25-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; BOLD Industries, Inc.</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 BOLD Industries, Inc. a revocable, nonassignable, partially exclusive license to practice in the United States, the Government-owned inventions described in U.S. Patent Application No. 20110024405 filed on August 18, 2009: Method of Breaching a Barrier.//U.S. Patent Application No. 20110024403 filed on July 28, 2009: Portable Cutting Device for Breaching a Barrier.//U.S. Patent Application No. 20110036999 filed on August 28, 2009: Countermeasure Method for a Mobile Tracking Device.//U.S. Patent Application No. 20110036998 filed on August 14, 2009: Countermeasure Device for a Mobile Tracking Device.//U.S. Patent Application No. 20110113949 filed on May 12, 2010: Modulation Device for a Mobile Tracking Device.//U.S. Patent Application Serial No. 12/778,643 filed on May 12, 2010: High Powered Laser System.//U.S. Patent Application Serial No. 12/778,892 filed on May 12, 2010: Scene Illuminator.</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 November 10, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Written objections are to be filed with the Naval Surface Warfare Center, Crane Div, Code OOL, Bldg 2, 300 Highway 361, Crane, IN 47522-5001.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Christopher Monsey, Naval Surface Warfare Center, Crane Div, Code OOL, Bldg 2, 300 Highway 361, Crane, IN 47522-5001, telephone 812-854-4100.</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>35 U.S.C. 207, 37 CFR Part 404.</P>
                    </AUTH>
                    <SIG>
                        <DATED>Dated: October 19, 2011.</DATED>
                        <NAME>L.M. Senay,</NAME>
                        <TITLE>Lieutenant, Office of the Judge Advocate, U.S. Navy, Alternate Federal Register Liaison Officer.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27661 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3810-FF-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF EDUCATION</AGENCY>
                <SUBJECT>Committee on Measures of Student Success</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Center for Education Statistics, Institute of Education Sciences, U.S. Department of Education.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of an Open Teleconference Meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice sets forth the schedule and proposed agenda of an upcoming meeting of the Committee on Measures of Student Success (Committee). The notice also describes the functions of the Committee. Notice of this meeting is required by section 10(a)(2) of the Federal Advisory Committee Act (FACA) and is intended to notify the public of their opportunity to attend.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>November 29, 2011.</P>
                    <P>
                        <E T="03">Time:</E>
                         11:00 a.m. to 12:30 p.m. Eastern Standard Time.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The Committee will meet by teleconference. Members of the public may attend and listen to the meeting proceedings in person at 1990 K Street, NW., Washington, DC 20006, 8th Floor Conference Center.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Archie Cubarrubia, Designated Federal Official, Committee on Measures of Student Success, U.S. Department of Education, 1990 K Street, NW., Washington, DC 20006. 
                        <E T="03">E-mail: Archie.Cubarrubia@ed.gov.</E>
                          
                        <E T="03">Telephone:</E>
                         (202) 502-7601.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Committee is established to advise the Secretary of Education in assisting two-year degree-granting institutions of higher education in meeting the completion or graduation rate disclosure requirements outlined in section 485 of the Higher Education Act of 1965, as amended. Specifically, the Committee shall develop recommendations regarding the accurate calculation and reporting of completion or graduation rates of entering certificate/degree-seeking, full-time, undergraduate students by two-year degree granting institutions of higher education. The Committee may also recommend additional or alternative measures of student success that are comparable alternatives to the completion or graduation rates of entering degree-seeking full-time undergraduate students and that consider the mission and role of two-year degree granting higher education institutions. These recommendations shall be provided to the Secretary no later than April 2012.</P>
                <P>The agenda for the meeting will include a discussion among Committee members regarding the Committee's final report to the Secretary.</P>
                <P>
                    Individuals interested in attending the meeting must register in advance because of limited seating. To register, please send an e-mail request to 
                    <E T="03">studentsuccess@ed.gov.</E>
                     Individuals who will need accommodations for a disability in order to attend the meeting (
                    <E T="03">e.g.,</E>
                     interpreting services, assistive listening devices, or materials in alternative format) should notify John Fink at (202) 502-7328 no later than November 21, 2011. We will attempt to meet requests for accommodations after this date but cannot guarantee their availability. The meeting site is accessible to individuals with disabilities.
                </P>
                <P>
                    There will not be a public comment period during this meeting. Opportunities for public comment are available through the Committee's Web site at 
                    <E T="03">http://www2.ed.gov/about/bdscomm/list/acmss.ht</E>
                    ml. Records are kept of all Committee proceedings and are available for public inspection on the Web site and at the National Center for Education Statistics, 1990 K Street, NW., Washington, DC 20006 from the hours of 9:00 a.m. to 5:00 p.m. E.S.T.
                </P>
                <P>
                    <E T="03">Electronic Access to This Document:</E>
                     You may view this document, as well as all other documents of this Department published in the 
                    <E T="04">Federal Register</E>
                    , in text or Adobe Portable Document Format (PDF) on the Internet at the following site: 
                    <E T="03">http://www.ed.gov/news/fed-register/index.html.</E>
                     To use PDF you must have Adobe Acrobat Reader, which is available free at this site. If you have questions about using PDF, call the U.S. Government Printing Office (GPO), toll free at 1-866-512-1830; or in the Washington, DC, area at (202) 512-0000.
                </P>
                <NOTE>
                    <HD SOURCE="HED">Note: </HD>
                    <P>
                        The official version of this document is the document published in the 
                        <E T="04">Federal Register</E>
                        . Free Internet access to the official edition of the 
                        <E T="04">Federal Register</E>
                         and the Code of Federal Regulations is available on GPO Access at: 
                        <E T="03">http://www.gpoaccess.gov/nara/index.html.</E>
                          
                    </P>
                </NOTE>
                <SIG>
                    <NAME>John Q. Easton,</NAME>
                    <TITLE>Director, Institute of Education Sciences.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27655 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4000-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="66284"/>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Office of Energy Efficiency and Renewable Energy</SUBAGY>
                <SUBJECT>Wind and Water Power Program</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 of public meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>All programs with the U.S. Department of Energy's (DOE) Office of Energy Efficiency and Renewable Energy (EERE) are required to undertake rigorous, objective peer review of their funded projects in order to ensure and enhance the management, relevance, effectiveness, and productivity of those projects. The 2011 Wind and Water Power Program, Water Power Peer Review Meeting will review the Program's portfolio of conventional hydropower and marine and hydrokinetic research and development and projects. The 2011 Water Power Peer Review Meeting will be held November 1 through November 3, 2011 in Alexandria, VA.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>DOE will hold a public meeting on Tuesday, November 1, 2011 from 12:45 p.m. to 5:30 p.m.; Wednesday, November 2, 2011 from 8:30 a.m. to 4:35 p.m.; and Thursday, November 3, 2011, from 8:30 a.m. to 5:30 p.m. in Alexandria, VA.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The public meeting will be held at the Hilton Alexandria Mark Center, 500 Seminary Road, Alexandria, VA 22311.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Hoyt Battey, Office of Energy  Efficiency and Renewable Energy, U.S. Department of Energy, 1000 Independence  Avenue, SW., Washington, DC 20585. 
                        <E T="03">Telephone:</E>
                         (202) 586-0143. 
                        <E T="03">E-mail: Hoyt.Battey@ee.doe.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The purpose of this meeting is to:</P>
                <P>• Review the strategy and goals of the Water Power Program; and</P>
                <P>• Review the progress and accomplishments of the Program's conventional hydropower, and marine and hydrokinetics research and projects funded in FY2009 through FY2011</P>
                <P>The purpose of this meeting is for the review of the Program's conventional hydropower, and marine and hydrokinetics research and projects funded in FY2009 through FY2011. Participants should limit information and comments to those based on personal experience, individual advice, information, or facts regarding this topic. It is not the object of this session to obtain any group position or consensus. Rather, this meeting is an opportunity for the peer reviewers to gain an individual understanding of the research and projects. To most effectively use the limited time, please refrain from passing judgment on another participant's recommendations or advice, and instead, concentrate on your individual experiences. Based upon the review of individual projects and the overall Water Power Program research portfolio, a report will be compiled by DOE, which will be publically posted on the DOE Wind and Water Power Program website.</P>
                <P>
                    <E T="03">Public Participation:</E>
                     Principal Investigators, expert reviewers, Water Power Program staff, and contract support staff will be in attendance. The event is open to the public based on space availability. Limited time for questions and answers are included for each project, however, oral questions from expert reviewers will be given priority. Additionally, questions may be submitted in writing during the meeting.
                </P>
                <P>
                    <E T="03">Pre-Registration:</E>
                     To pre-register, please contact Ms. Stacey Young via e-mail at 
                    <E T="03">Stacey_Young@sra.com</E>
                     or by telephone at 240-223-5578. Participants interested in attending should indicate the category or categories you would like to observe, your name, company name or organization (if applicable), telephone number, and email no later than the close of business on Monday, October 28 2011. All Principal Investigators required to present at the meeting must pre-register. Additionally, all expert reviewers, Water Power Program staff, and support contract staff must pre-register.
                </P>
                <P>
                    <E T="03">Agenda:</E>
                     Presentations from industry, academia, and National Laboratories will be time limited. Depending on the type of project, Principal Investigators will have anywhere from 5 to 60 minutes to present. Time is also allotted for question and answer sessions between the Principal Investigators and the expert reviewers.
                </P>
                <P>
                    <E T="03">Information on Services for Individuals with Disabilities:</E>
                     Individuals requiring special accommodations at the meeting, please contact Ms. Young no later than the close of business on October 28, 2011.
                </P>
                <P>
                    <E T="03">Minutes:</E>
                     The minutes of the meeting will be available for public review and  copying at the DOE EERE Online Publication and Product Library at:  
                    <E T="03">http://www1.eere.energy.gov/library/default.aspx.</E>
                </P>
                <SIG>
                    <DATED>Issued in Washington, DC, on October 19, 2011.</DATED>
                    <NAME>Jose Zayas,</NAME>
                    <TITLE>Wind and Water Power Program Manager, Office of Energy Efficiency and Renewable Energy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27682 Filed 10-25-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>
                <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-60-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Duke Energy Corporation.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance Filing of Duke Energy Corporation and Progress Energy, Inc.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/17/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20111017-5129.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Wednesday, November 16, 2011.
                </P>
                <P>Take notice that the Commission received the following exempt wholesale generator filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EG12-3-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     South Chestnut LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Self-Certification of EWG Status of South Chestnut LLC.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/17/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20111017-5042.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, November 07, 2011.
                </P>
                <P>Take notice that the Commission received the following electric rate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-4151-002.
                </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: 2011-10-17 CAISO NRS-RA Compliance Filing to be effective 1/1/2012.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/17/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20111017-5116.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, November 07, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER12-94-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Golden Spread Electric Cooperative, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Golden Spread Electric Cooperative, Inc. submits tariff filing per 35.13(a)(2)(iii: Revised Wholesale Power Contracts Filing to be effective 12/16/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/17/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20111017-5032.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, November 07, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER12-95-000.
                    <PRTPAGE P="66285"/>
                </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: Amended Duke-Vectren (SA 1391) to be effective 10/18/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/17/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20111017-5033.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, November 07, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER12-96-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     South Chestnut LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     South Chestnut LLC submits tariff filing per 35.12: Market-Based Rate Application to be effective 10/18/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/17/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20111017-5041.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, November 07, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER12-97-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Fairchild Energy, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Fairchild Energy, LLC submits tariff filing per 35: Compliance Filing to be effective 9/23/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/17/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20111017-5067.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, November 07, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER12-98-000; ER12-99-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     330 Fund I, L.P., 330 Investment Management, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     330 Investment Management, LLC submits notification of withdrawal of market based rate authority.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/17/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20111017-0201.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, November 07, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER12-100-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Black Oak Capital, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Black Oak Capital, LLC submits tariff filing per 35.12: Normal rate schedules to be effective 10/17/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/17/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20111017-5087.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, November 07, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER12-101-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: C004-P11 FCA (Ameren-Bishop Hill) to be effective 10/18/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/17/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20111017-5095.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, November 07, 2011.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER12-102-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Dominion Energy Brayton Point, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Dominion Energy Brayton Point, LLC submits tariff filing per 35: Compliance Filing—MBR Tariff Order of Affiliate Restrictions to be effective 11/21/2011.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     10/17/2011.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20111017-5115.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. Eastern Time on Monday, November 07, 2011.
                </P>
                <P>The filings are accessible in the Commission's eLibrary system by clicking on the links or querying the docket number.</P>
                <P>Any person desiring to intervene or protest in any of the above proceedings must file in accordance with Rules 211 and 214 of the Commission's Regulations (18 CFR 385.211 and 385.214) on or before 5 p.m. Eastern time on the specified comment date. Protests may be considered, but intervention is necessary to become a party to the proceeding.</P>
                <P>
                    eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, service, and qualifying facilities filings can be found at: 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling/filing-req.pdf.</E>
                     For other information, call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <SIG>
                    <DATED>Dated: October 18, 2011.</DATED>
                    <NAME>Nathaniel J. Davis, Sr.,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27623 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[FRL-9483-3]</DEPDOC>
                <SUBJECT>Clean Air Act Operating Permit Program; Petition for Objection to State Operating Permit for Public Service Company of Colorado dba Xcel Energy—Valmont Power Station</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of final action.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document announces that the EPA Administrator has responded to a citizen petition asking EPA to object to an operating permit issued by the Colorado Department of Public Health and Environment (CDPHE). Specifically, the Administrator has denied the March, 2010, Petition, submitted by WildEarth Guardians (Petitioner), to object to CDPHE's March 1, 2010, title V permit issued to Public Service Company of Colorado dba Xcel Energy (Xcel)—Valmont Power Station.</P>
                    <P>
                        Pursuant to section 505(b)(2) of the Clean Air Act (Act or CAA), Petitioners may seek judicial review of those portions of the petition that EPA denied in the United States Court of Appeals for the appropriate circuit. Any petition for review shall be filed within 60 days from the date this notice appears in the 
                        <E T="04">Federal Register</E>
                        , pursuant to section 307 of the Act.
                    </P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may review copies of the Final Order, the Petition, and other supporting information at the EPA Region 8 Office, 1595 Wynkoop Street, Denver, Colorado 80202-1129. EPA requests that if at all possible, you contact the individual listed in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section to view the copies of the Final Order, the Petition, and other supporting information. You may view the hard copies Monday through Friday, 8 a.m. to 4 p.m., excluding Federal holidays. If you wish to examine these documents, you should make an appointment at least 24 hours in advance. Additionally, the Final Order for Public Service Company of Colorado—Valmont Power Station is available electronically at: 
                        <E T="03">http://www.epa.gov/region07/air/title5/petitiondb/petitions/xcel_valmont_response2011.pdf.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Donald Law, Air Program (8P-AR), EPA Region 8, 1595 Wynkoop Street, Denver, Colorado 80202-1129. 
                        <E T="03">Phone:</E>
                         (303) 312-7015. 
                        <E T="03">E-mail: law.donald@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Act affords EPA a 45-day period to review and object to, as appropriate, a title V operating permit proposed by State permitting authorities. Section 505(b)(2) of the Act authorizes any person to petition the EPA Administrator, within 60 days after the expiration of this review period, to object to a title V operating permit if EPA has not done so. Petitions must be based only on objections to the permit that were raised with reasonable specificity during the public comment period provided by the State, unless the petitioner demonstrates that it was impracticable to raise these issues during the comment period or the grounds for the issues arose after this period. EPA received a petition from WildEarth Guardians dated March 18, 2010, requesting that EPA object to the issuance of the title V operating permit to Public Service Company of Colorado for the operation of the Valmont Power Station. The Petition alleges that the Permit does not comply with 40 CFR part 70 in that it fails to assure compliance with: (I) A compliance plan for opacity monitoring requirements; (II) applicable opacity requirements; (III) particulate matter (PM) limits applicable to the coal-fired boiler; (IV) CAA section 112(j) for air toxics; and (V) PSD 
                    <PRTPAGE P="66286"/>
                    requirements in regard to carbon dioxide (CO
                    <E T="52">2</E>
                    ) emissions.
                </P>
                <P>On September 29, 2011, the Administrator issued an Administrative Order denying the Petition. The Order explains the reasons behind EPA's conclusions.</P>
                <SIG>
                    <DATED>Dated: October 19, 2011.</DATED>
                    <NAME>James B. Martin,</NAME>
                    <TITLE>Regional Administrator, Region 8.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27725 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <DEPDOC>[FRL-9483-2] </DEPDOC>
                <SUBJECT>Clean Air Act Operating Permit Program; Petition for Objection to State Operating Permit for Public Service Company of Colorado dba Xcel Energy—Cherokee Power Station </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of final action.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document announces that the EPA Administrator has responded to a citizen petition asking EPA to object to an operating permit issued by the Colorado Department of Public Health and Environment (CDPHE). Specifically, the Administrator has denied the April 1, 2010, Petition, submitted by WildEarth Guardians (Petitioner), to object to CDPHE's April 1, 2010, title V permit issued to Public Service Company of Colorado dba Xcel Energy (Xcel)—Cherokee Power Station. </P>
                    <P>
                        Pursuant to section 505(b)(2) of the Clean Air Act (Act or CAA), Petitioners may seek judicial review of those portions of the petition that EPA denied in the United States Court of Appeals for the appropriate circuit. Any petition for review shall be filed within 60 days from the date this notice appears in the 
                        <E T="04">Federal Register</E>
                        , pursuant to section 307 of the Act. 
                    </P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may review copies of the Final Order, the Petition, and other supporting information at the EPA Region 8 Office, 1595 Wynkoop Street, Denver, Colorado 80202-1129. EPA requests that if at all possible, you contact the individual listed in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section to view the copies of the Final Order, the Petition, and other supporting information. You may view the hard copies Monday through Friday, 8 a.m. to 4 p.m., excluding Federal holidays. If you wish to examine these documents, you should make an appointment at least 24 hours in advance. Additionally, the Final Order for Public Service Company of Colorado—Cherokee Power Station is available electronically at: 
                        <E T="03">http://www.epa.gov/region07/air/title5/petitiondb/petitions/xcel_cherokee_response2011.pdf.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Donald Law, Air Program (8P-AR), EPA Region 8, 1595 Wynkoop Street, Denver, Colorado 80202-1129. 
                        <E T="03">Phone:</E>
                         (303)312-7015. 
                        <E T="03">E-mail: law.donald@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Act affords EPA a 45-day period to review and object to, as appropriate, a title V operating permit proposed by State permitting authorities. Section 505(b)(2) of the Act authorizes any person to petition the EPA Administrator, within 60 days after the expiration of this review period, to object to a title V operating permit if EPA has not done so. Petitions must be based only on objections to the permit that were raised with reasonable specificity during the public comment period provided by the State, unless the petitioner demonstrates that it was impracticable to raise these issues during the comment period or the grounds for the issues arose after this period. EPA received a petition from WildEarth Guardians dated April 1, 2010, requesting that EPA object to the issuance of the title V operating permit to Public Service Company of Colorado for the operation of the Cherokee Power Station. The Petition alleges that the Permit does not comply with 40 CFR part 70 in that it fails to assure compliance with: (I) A compliance plan for opacity monitoring requirements; (II) applicable opacity requirements; (III) particulate matter (PM) limits applicable to the coal-fired boiler; (IV) CAA section 112(j) for air toxics; and (V) PSD requirements in regard to carbon dioxide (CO
                    <E T="52">2</E>
                    ) emissions. 
                </P>
                <P>On September 29, 2011, the Administrator issued an Administrative Order denying the Petition. The Order explains the reasons behind EPA's conclusions. </P>
                <SIG>
                    <DATED>Dated: October 19, 2011. </DATED>
                    <NAME>James B. Martin, </NAME>
                    <TITLE>Regional Administrator, Region 8. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27734 Filed 10-25-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-2008-0517; FRL-9483-4] </DEPDOC>
                <RIN>RIN 2040-AF06 </RIN>
                <SUBJECT>Notice of Final 2010 Effluent Guidelines Program Plan </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice presents the final 2010 Effluent Guidelines Program Plan(“final 2010 Plan”), which, as required under the Clean Water Act (CWA), identifies any new or existing industrial dischargers, both those discharging directly to surface waters and those discharging to publicly owned treatment works (POTWs), selected for effluent guidelines rulemaking and provides a schedule for such rulemakings. CWA section 304(m) requires EPA to biennially publish such a plan after public notice and comment. The Agency published the preliminary 2010 Plan on December 28, 2009 (74 FR 68599) and solicited comments from the public for 60 days. </P>
                    <P>After considering rulemakings already in development, the 2010 reviews, the preliminary Plan and public comments and input to determine what, if any, new rulemakings should be initiated, EPA has decided to develop effluent guidelines and standards for the discharge of wastewater from the Coalbed Methane Extraction (CBM) industry and will develop pretreatments requirements for discharges of mercury from the Dental industry, and for the discharges of wastewater from the Shale Gas Extraction (SGE) industry. </P>
                    <P>EPA is also issuing the detailed study report for the Coalbed Methane Extraction and the preliminary study report of the Ore Mining and Dressing industry. </P>
                    <P>This notice also solicits public comments on EPA's 2011 reviews pursuant to the authority of CWA sections 304(b), 304(g), 301(d) and 307(b). </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments on or before November 25, 2011. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Submit your comments on the final 2010 Plan, identified by Docket ID No. EPA-HQ-OW-2008-0517, by one of the following methods: </P>
                    <P>
                        (1) 
                        <E T="03">http://www.regulations.gov.</E>
                         Follow the on-line instructions for submitting comments. 
                    </P>
                    <P>
                        (2) 
                        <E T="03">E-mail: OW-Docket@epa.gov,</E>
                         Attention Docket ID No. EPA-HQ-OW-2008-0517. 
                    </P>
                    <P>
                        (3) 
                        <E T="03">Mail:</E>
                         Water Docket, Environmental Protection Agency, 
                        <E T="03">Mailcode:</E>
                         4203M, 
                        <PRTPAGE P="66287"/>
                        1200 Pennsylvania Ave., NW., Washington, DC 20460, Attention Docket ID No. EPA-HQ-OW-2008-0517. Please include a total of 3 copies. 
                    </P>
                    <P>
                        (4) 
                        <E T="03">Hand Delivery:</E>
                         Water Docket, EPA Docket Center, EPA West, Room 3334, 1301 Constitution Ave., NW., Washington, DC, Attention Docket ID No. EPA-HQ-OW-2008-0517. Such deliveries are only accepted during the Docket's normal hours of operation and special arrangements should be made. 
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         Direct your comments to Docket ID No. EPA-HQ-OW-2008-0517. EPA's policy is that all comments received will be included in the public docket without change and may be made available online at 
                        <E T="03">http://www.regulations.gov,</E>
                         including any personal information provided, unless the comment includes information claimed to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute (see below for instructions on submitting CBI). Do not submit information that you consider to be CBI or otherwise protected through 
                        <E T="03">regulations.gov</E>
                         or e-mail. The federal 
                        <E T="03">regulations.gov</E>
                         Web site is an “anonymous access” system, which means EPA will not know your identity or contact information unless you provide it in the body of your comment. If you send an e-mail comment directly to EPA without going through regulations.gov, your e-mail address will be automatically captured and included as part of the comment that is placed in the public docket and made available on the Internet. If you submit an electronic comment, EPA recommends that you include your name and other contact information in the body of your comment, and with any disk or CD-ROM you submit. If EPA cannot read your comment due to technical difficulties and cannot contact you for clarification, EPA may not be able to consider your comment. Electronic files should avoid the use of special characters, any form of encryption, and be free of any defects or viruses. 
                    </P>
                </ADD>
                <HD SOURCE="HD1">Submitting Confidential Business Information </HD>
                <P>
                    Do not submit confidential business information (CBI) to EPA through 
                    <E T="03">http://www.regulations.gov</E>
                     or e-mail. Any CBI you wish to submit should be sent via a trackable physical method, such as Federal Express or United Parcel Service, to Mr. M. Ahmar Siddiqui, Document Control Officer, Engineering and Analysis Division (4303T), Room 6231S EPA West, U.S. EPA, 1200 Pennsylvania Ave, NW., Washington, DC 20460. A CBI package should be double-wrapped, so that the CBI is in one package, which is itself inside another package. Clearly mark the part or all of the information that you claim to be CBI. For CBI information on a disk or CD-ROM that you mail to EPA, mark the outside of the disk or CD-ROM as CBI and then identify electronically within the disk or CD-ROM the specific information that is claimed as CBI. In addition to one complete copy of the material that includes information claimed as CBI, a copy of the material that does not contain the information claimed as CBI must be submitted for inclusion in the public docket. Information marked as CBI will not be disclosed except in accordance with procedures set forth in 40 CFR part 2. 
                </P>
                <P>
                    <E T="03">Docket:</E>
                     All documents in the docket are listed in the index at 
                    <E T="03">http://www.regulations.gov.</E>
                     Although listed in the index, some information is not publicly available, 
                    <E T="03">i.e.,</E>
                     CBI or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, is not placed on the Internet and will be publicly available only in hard copy form. Publicly available docket materials are available either electronically at 
                    <E T="03">http://www.regulations.gov</E>
                     or in hard copy at the Water Docket in the EPA Docket Center, EPA/DC, EPA West, Room 3334, 1301 Constitution Ave., NW., Washington, DC. The Public Reading Room is open from 8:30 a.m. to 4:30 p.m., Monday through Friday, excluding legal holidays. The telephone number for the Public Reading Room is (202) 566-1744, and the telephone number for the Water Docket is (202) 566-2426. 
                </P>
                <P>Key documents providing additional information about EPA's annual reviews and the final 2010 Effluent Guidelines Program Plan include the following: </P>
                <P>• Technical Support Document for the 2010 Effluent Guidelines Program Plan, EPA-820-R-10-021, DCN 07320; </P>
                <P>
                    • 
                    <E T="03">Coalbed Methane Point Source Category:</E>
                     Detailed Study Report, EPA-820-R-10-022, DCN 09999; 
                </P>
                <P>
                    • 
                    <E T="03">Draft Guidance Document:</E>
                     Best Management Practices for Unused Pharmaceuticals at Health Care Facilities, August 26, 2010, EPA-821-R-10-006. 
                </P>
                <P>• Ore Mining and Dressing Category Preliminary Study, EPA-820-R-10-025, DCN 07369. </P>
                <HD SOURCE="HD1">Data and Information for the 2011 Annual Review </HD>
                <P>Submit any data and information you have for the 2011 annual reviews, identified by Docket ID No. EPA-HQ-OW-2010-0824, by one of the methods described above. </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. William F. Swietlik at (202) 566-1129 or 
                        <E T="03">swietlik.william@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION: </HD>
                <HD SOURCE="HD1">How is this document organized? </HD>
                <P>The outline of this notice follows. </P>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. General Information </FP>
                    <FP SOURCE="FP-2">II. Legal Authority </FP>
                    <FP SOURCE="FP-2">
                        III. What is the purpose of this 
                        <E T="04">Federal Register</E>
                         notice? 
                    </FP>
                    <FP SOURCE="FP-2">IV. Background </FP>
                    <FP SOURCE="FP-2">V. EPA's 2010 Annual Review of Existing Effluent Guidelines and Pretreatment Standards Under CWA Sections 301(d), 304(b), 304(g), 304(m), and 307(b) </FP>
                    <FP SOURCE="FP-2">VI. EPA's 2010 Evaluation of Categories of Indirect Dischargers Without Categorical Pretreatment Standards To Identify Potential New Categories for Pretreatment Standards </FP>
                    <FP SOURCE="FP-2">VII. The Final 2010 Effluent Guidelines Program Plan </FP>
                    <FP SOURCE="FP-2">VIII. EPA's 2011 Annual Review of Existing Effluent Guidelines and Pretreatment Standards Under CWA Sections 301(d), 304(b), 304(g), and 307(b) </FP>
                    <FP SOURCE="FP-2">IX. Request for Comment and Information </FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. General Information </HD>
                <HD SOURCE="HD2">A. Does this action apply to me? </HD>
                <P>This notice provides a summary of the Agency's effluent guidelines review and planning processes and priorities at this time, and does not contain any regulatory requirements. This notice also provides a summary of the Agency's pretreatment standards review. </P>
                <HD SOURCE="HD2">B. What should I consider as I prepare my comments for EPA for the 2011 annual review? </HD>
                <HD SOURCE="HD3">1. Tips for Preparing Your Comments </HD>
                <P>
                    <E T="03">When submitting comments, remember to:</E>
                </P>
                <P>
                    • Identify the rulemaking by docket number and other identifying information (subject heading, 
                    <E T="04">Federal Register</E>
                     date and page number). 
                </P>
                <P>• Follow directions—The agency may ask you to respond to specific questions or organize comments by referencing a Code of Federal Regulations (CFR) part or section number. </P>
                <P>• Explain why you agree or disagree; suggest alternatives and substitute language for your requested changes. </P>
                <P>• Describe any assumptions and provide any technical information and/or data that you used. </P>
                <P>• If you estimate potential costs or burdens, explain how you arrived at your estimate in sufficient detail to allow for it to be reproduced. </P>
                <P>
                    • Provide specific examples to illustrate your concerns, and suggest alternatives. 
                    <PRTPAGE P="66288"/>
                </P>
                <P>• Explain your views as clearly as possible. </P>
                <P>• Make sure to submit your comments by the comment period deadline identified. </P>
                <P>• Follow the special procedures for submitting Confidential Business Information (CBI). </P>
                <HD SOURCE="HD1">II. Legal Authority </HD>
                <P>
                    This notice is published under the authority of the CWA, 33 U.S.C. 1251, 
                    <E T="03">et seq.,</E>
                     and in particular sections 301(d), 304(b), 304(g), 304(m), 306, 307(b), 308, 33 U.S.C. 1311(d), 1314(b), 1314(g), 1314(m), 1316, 1317(b), and 1318. 
                </P>
                <HD SOURCE="HD1">
                    III. What is the purpose of this 
                    <E T="04">Federal Register</E>
                     notice? 
                </HD>
                <P>This notice presents EPA's 2010 review of existing effluent guidelines and pretreatment standards under CWA sections 301, 304 and 307. It also presents EPA's evaluation of indirect dischargers without categorical pretreatment standards to identify potential new categories for pretreatment standards under CWA sections 304(g) and 307(b) and (c). This notice presents the final 2010 Effluent Guidelines Program Plan (“final 2010 Plan”), which, as required under CWA section 304(m), identifies any new or existing industrial categories selected for effluent guidelines rulemaking, as well as the establishment or revision of pretreatment standards, and provides a schedule for such rulemakings. CWA section 304(m) requires EPA to biennially publish such a plan after public notice and comment. The Agency published a preliminary 2010 Plan on December 28, 2009 (74 FRN 68599) and solicited comment through February 26, 2010. This notice also provides EPA's preliminary thoughts concerning its 2011 annual reviews under CWA sections 301(d), 304(b), 304(g), 306 and 307(b) and solicits comments, data and information to assist EPA in performing these reviews. </P>
                <HD SOURCE="HD1">IV. Background </HD>
                <HD SOURCE="HD2">A. What are effluent guidelines and pretreatment standards? </HD>
                <P>The CWA directs EPA to promulgate effluent limitations guidelines and standards (“effluent guidelines”) that reflect pollutant reductions that can be achieved by categories or subcategories of industrial point sources using technologies that represent the appropriate level of control. See CWA sections 301(b)(2), 304(b), 306, 307(b), and 307(c). For point sources that introduce pollutants directly into the waters of the United States (direct dischargers), the effluent limitations guidelines and standards promulgated by EPA are implemented through National Pollutant Discharge Elimination System (NPDES) permits. See CWA sections 301(a), 301(b), and 402. For sources that discharge to publicly owned treatment works (POTWs), termed indirect dischargers, EPA promulgates pretreatment standards that apply to those sources and are enforced by the POTWs and State and Federal authorities. See CWA sections 307(b) and (c). </P>
                <HD SOURCE="HD3">1. Best Practicable Control Technology Currently Available (BPT)—CWA Sections 301(b)(1)(A) &amp; 304(b)(1) </HD>
                <P>
                    EPA defines Best Practicable Control Technology Currently Available (BPT) effluent limitations for conventional, toxic, and non-conventional pollutants. Section 304(a)(4) designates the following as conventional pollutants: Biochemical oxygen demand (BOD
                    <E T="52">5</E>
                    ), total suspended solids, fecal coliform, pH, and any additional pollutants defined by the Administrator as conventional. The Administrator designated oil and grease as an additional conventional pollutant on July 30, 1979 (44 FR 44501). EPA has identified 65 pollutants and classes of pollutants as toxic pollutants, of which 126 specific substances have been designated priority toxic pollutants. See Appendix A to part 423. All other pollutants are considered to be non-conventional. 
                </P>
                <P>In specifying BPT, EPA looks at a number of factors. EPA first considers the total cost of applying the control technology in relation to the effluent reduction benefits. The Agency also considers the age of the equipment and facilities, the processes employed, and any required process changes, engineering aspects of the control technologies, non-water quality environmental impacts (including energy requirements), and such other factors as the EPA Administrator deems appropriate. See CWA section 304(b)(1)(B). Traditionally, EPA establishes BPT effluent limitations based on the average of the best performances of facilities within the industry of various ages, sizes, processes, or other common characteristics. Where existing performance is uniformly inadequate, BPT may reflect higher levels of control than currently in place in an industrial category if the Agency determines that the technology can be practically applied. </P>
                <HD SOURCE="HD3">2. Best Conventional Pollutant Control Technology (BCT)—CWA Sections 301(b)(2)(E) &amp; 304(b)(4) </HD>
                <P>The 1977 amendments to the CWA required EPA to identify effluent reduction levels for conventional pollutants associated with Best Conventional Pollutant Control Technology (BCT) for discharges from existing industrial point sources. In addition to considering the other factors specified in section 304(b)(4)(B) to establish BCT limitations, EPA also considers a two part “cost-reasonableness” test. EPA explained its methodology for the development of BCT limitations in 1986. See 51 FR 24974 (July 9, 1986). </P>
                <HD SOURCE="HD3">3. Best Available Technology Economically Achievable (BAT)—CWA Sections 301(b)(2)(A) &amp; 304(b)(2)(B) </HD>
                <P>For toxic pollutants and non-conventional pollutants, EPA promulgates effluent guidelines based on the Best Available Technology Economically Achievable (BAT). See CWA section 301(b)(2)(A), (C), (D) and (F). The factors considered in assessing BAT include the cost of achieving BAT effluent reductions, the age of equipment and facilities involved, the process employed, potential process changes, non-water quality environmental impacts, including energy requirements, and other such factors as the EPA Administrator deems appropriate. See CWA section 304(b)(2)(B). The technology must also be economically achievable. See CWA section 301(b)(2)(A). The Agency retains considerable discretion in assigning the weight accorded to these factors. BAT limitations may be based on effluent reductions attainable through changes in a facility's processes and operations. Where existing performance is uniformly inadequate, BAT may reflect a higher level of performance than is currently being achieved within a particular subcategory based on technology transferred from a different subcategory or category. BAT may be based upon process changes or internal controls, even when these technologies are not common industry practice. </P>
                <HD SOURCE="HD3">4. New Source Performance Standards (NSPS)—CWA Section 306 </HD>
                <P>
                    New Source Performance Standards (NSPS) reflect effluent reductions that are achievable based on the best available demonstrated control technology. New sources have the opportunity to install the best and most efficient production processes and wastewater treatment technologies. As a result, NSPS should represent the most 
                    <PRTPAGE P="66289"/>
                    stringent controls attainable through the application of the best available demonstrated control technology for all pollutants (
                    <E T="03">i.e.,</E>
                     conventional, non-conventional, and priority pollutants). In establishing NSPS, EPA is directed to take into consideration the cost of achieving the effluent reduction and any non-water quality environmental impacts and energy requirements. 
                </P>
                <HD SOURCE="HD3">5. Pretreatment Standards for Existing Sources (PSES)—CWA Section 307(b) </HD>
                <P>Pretreatment Standards for Existing Sources (PSES) are designed to prevent the discharge of pollutants that pass through, interfere with, or are otherwise incompatible with the operation of publicly owned treatment works (POTWs), including sludge disposal methods at POTWs. Pretreatment standards for existing sources are technology-based and are analogous to BAT effluent limitations guidelines. The General Pretreatment Regulations, which set forth the framework for the implementation of national pretreatment standards, are found at 40 CFR part 403. </P>
                <HD SOURCE="HD3">6. Pretreatment Standards for New Sources (PSNS)—CWA Section 307(c) </HD>
                <P>Like PSES, Pretreatment Standards for New Sources (PSNS) are designed to prevent the discharges of pollutants that pass through, interfere with, or are otherwise incompatible with the operation of POTWs. PSNS are to be issued at the same time as NSPS. New indirect dischargers have the opportunity to incorporate into their facilities the best available demonstrated technologies. The Agency considers the same factors in promulgating PSNS as it considers in promulgating NSPS. </P>
                <HD SOURCE="HD2">B. What are EPA's review and planning obligations under sections 301(d), 304(b), 304(g), 304(m), and 307(b)? </HD>
                <HD SOURCE="HD3">1. EPA's Review and Planning Obligations Under Sections 301(d), 304(b), and 304(m)—Direct Dischargers </HD>
                <P>
                    Section 304(b) requires EPA to review its existing effluent guidelines for direct dischargers each year and to revise such regulations “if appropriate.” Section 304(m) supplements section 304(b) by requiring EPA to publish a plan every two years announcing its schedule for performing this annual review and its schedule for rulemaking for any effluent guidelines selected for possible revision as a result of that annual review. Section 304(m) also requires the plan to identify categories of sources discharging toxic or non-conventional pollutants for which EPA has not published effluent limitations guidelines under section 304(b)(2) or NSPS under section 306. See CWA section 304(m)(1)(B); S. Rep. No. 50, 99th Cong., 1st Sess. (1985); WQA87 Leg. Hist. 31 (indicating that section 304(m)(1)(B) applies to “non-trivial discharges.”). Finally, under section 304(m), the plan must present a schedule for promulgating effluent guidelines for industrial categories for which it has not already established such guidelines, providing for final action on such rulemaking not later than three years after the industrial category is identified in a final Plan. See CWA section 304(m)(1)(C); 
                    <E T="03">NRDC et al.</E>
                     v. 
                    <E T="03">EPA,</E>
                     542 F.3d 1235, 1251 (9th Cir. 2008). EPA is required to publish its preliminary Plan for public comment prior to taking final action on the plan. See CWA section 304(m)(2). 
                </P>
                <P>
                    In addition, CWA section 301(d) requires EPA to review every five years the effluent limitations required by CWA section 301(b)(2) and to revise them if appropriate pursuant to the procedures specified in that section. Section 301(b)(2), in turn, requires point sources to achieve effluent limitations reflecting the application of the best practicable control technology (all pollutants), best available technology economically achievable (for toxic pollutants and non-conventional pollutants) and the best conventional pollutant control technology (for conventional pollutants), as determined by EPA under sections 304(b)(1), 304(b)(2) and 304(b)(4), respectively. For over three decades, EPA has implemented sections 301 and 304 through the promulgation of effluent limitations guidelines, resulting in regulations for 57 industrial categories. See 
                    <E T="03">E.I. du Pont de Nemours &amp; Co.</E>
                     v. 
                    <E T="03">Train,</E>
                     430 U.S. 113 (1977). Consequently, as part of its annual review of effluent limitations guidelines under section 304(b), EPA is also reviewing the effluent limitations they contain, thereby fulfilling its obligations under sections 301(d) and 304(b) simultaneously. 
                </P>
                <HD SOURCE="HD3">2. EPA's Review and Planning Obligations Under Sections 304(g) and 307(b)—Indirect Dischargers </HD>
                <P>Section 307(b) requires EPA to revise its pretreatment standards for indirect dischargers “from time to time, as control technology, processes, operating methods, or other alternatives change.” See CWA section 307(b)(2). Section 304(g) requires EPA to annually review these pretreatment standards and revise them “if appropriate.” Although section 307(b) only requires EPA to revise existing pretreatment standards “from time to time,” section 304(g) requires an annual review. Therefore, EPA meets its 304(g) and 307(b) requirements by reviewing all industrial categories subject to existing categorical pretreatment standards on an annual basis to identify potential candidates for revision.</P>
                <P>Section 307(b)(1) also requires EPA to promulgate pretreatment standards for pollutants not susceptible to treatment by POTWs or that would interfere with the operation of POTWs, although it does not provide a timing requirement for the identification of new industries for pretreatment standards. EPA, in its discretion, periodically evaluates indirect dischargers not subject to categorical pretreatment standards to identify potential candidates for new pretreatment standards. The CWA does not require EPA to publish its review of pretreatment standards or identification of potential new categories, although EPA is exercising its discretion to do so in this notice.</P>
                <P>
                    EPA intends to repeat this publication schedule for future pretreatment standards reviews (
                    <E T="03">e.g.,</E>
                     EPA will publish the 2011 annual pretreatment standards review in the notice containing the Agency's 2011 annual review of existing effluent guidelines and the preliminary 2012 plan). EPA intends that these contemporaneous reviews will provide meaningful insight into EPA's effluent guidelines and pretreatment standards program decision-making. Additionally, by providing a single notice for these and future reviews, EPA hopes to provide a consolidated source of information for the Agency's current and future effluent guidelines and pretreatment standards program reviews.
                </P>
                <HD SOURCE="HD1">V. EPA's 2010 Annual Review of Existing Effluent Guidelines and Pretreatment Standards Under CWA Sections 301(d), 304(b), 304(g), 304(m), and 307(b)</HD>
                <HD SOURCE="HD2">A. What process did EPA use to review existing effluent guidelines and pretreatment standards under CWA Section 301(d), 304(b), 304(g), 304(m), and 307(b)?</HD>
                <HD SOURCE="HD3">1. Overview</HD>
                <P>In its 2010 annual review, EPA reviewed all industrial categories subject to existing effluent limitations guidelines and pretreatment standards, representing a total of 57 point source categories and over 450 subcategories. Generally, EPA uses four factors in a phased approach to review existing effluent limitations guidelines and pretreatment standards:</P>
                <P>
                    (1) Pollutants discharged in an industrial category's effluent,
                    <PRTPAGE P="66290"/>
                </P>
                <P>(2) Potential pollution prevention and control technology options,</P>
                <P>(3) Category growth and economic considerations of technology options, and</P>
                <P>(4) Implementation and efficiency considerations of revising existing effluent guidelines or publishing new effluent guidelines (see December 21, 2006; 71 FR 76666).</P>
                <P>In the 2010 annual review EPA incorporated, for the first time, discharge data from approximately 15,000 “minor” industrial dischargers. Point sources are generally classified as major or minor, depending on size and nature of the discharges. A major industrial discharger is a facility scoring over 80 points based on rating criteria. Minor industrial discharges are facilities that score below the criteria score of 80 on the rating scale.</P>
                <HD SOURCE="HD3">2. What analyses did EPA perform for its 2009 and 2010 annual reviews of existing effluent guidelines and pretreatment standards?</HD>
                <HD SOURCE="HD3">a. Screening-Level Review</HD>
                <P>The first component of EPA's 2010 annual review consisted of a screening-level review of all industrial categories subject to existing effluent guidelines or pretreatment standards. EPA focused its efforts on collecting and analyzing data to identify industrial categories whose pollutant discharges potentially are the most significant. EPA used Toxic Release Inventory (TRI), Permit Compliance System (PCS) and Integrated Compliance Information System—National Pollutant Discharge Elimination System (ICIS-NPDES) data to estimate the mass of pollutant discharges from industrial facilities. Because pollutant toxicities are different, EPA converted the toxic and non-conventional pollutant discharges that are reported in a mass unit (pounds) into a measure of relative toxicity—a toxic-weighted pound equivalent or TWPE.</P>
                <P>EPA calculated the TWPE for each pollutant discharged by multiplying the pollutant specific toxic weighting factor (TWF) and the mass of the pollutant discharge. Where data are available, these TWFs reflect both aquatic life and human health effects. EPA ranked point source categories according to their discharges of toxic and non-conventional pollutants (reported in units of TWPE) to assess the significance of these toxic and non-conventional pollutant discharges to human health or the environment. EPA conducted this process for the 2010 annual reviews using the most recent TRI, PCS and ICIS-NPDES data (2008).</P>
                <P>
                    Based on this methodology, EPA prioritized for potential revision industrial categories that offered the greatest potential for reducing hazard to human health and the environment. EPA assigned those categories with the lowest estimates of toxic-weighted pollutant discharges a lower priority for revision (
                    <E T="03">i.e.,</E>
                     industrial categories marked “(3)” in the “Findings” column in Table V-1 in section V.B.4 of this notice).
                </P>
                <P>
                    In order to further focus its inquiry during the 2010 annual review, EPA assigned a lower priority for potential revision to categories for which effluent guidelines had been recently promulgated or revised, or for which effluent guidelines rulemaking was currently underway. EPA removed an industrial point source category from further consideration during the current review cycle if EPA established, revised, or reviewed in a rulemaking context the category's effluent guidelines after August 2003 (
                    <E T="03">i.e.,</E>
                     the last seven years). EPA chose seven years because this is the time it customarily takes for the effects of effluent guidelines or pretreatment standards to be fully reflected in pollutant loading data and TRI reports (in large part because effluent limitations guidelines are often incorporated into NPDES permits only upon re-issuance of those permits, which could be up to five years after the effluent guidelines or pretreatment standards are promulgated). EPA also removed an industrial point source category from further consideration during the current review cycle if EPA recently completed a preliminary study or a detailed study and determined that no further action is necessary at this time. These categories are marked “(1)” in the “Findings” column in Table V-1 in section V.B.4 of this notice.
                </P>
                <P>Because there are 57 point source categories (including over 450 subcategories) with existing effluent guidelines and pretreatment standards that must be reviewed annually, EPA believes it is important to prioritize its review so as to focus on industries where changes to the existing effluent guidelines or pretreatment standards are most likely to result in further pollutant discharge reduction. In general, industries for which effluent guidelines or pretreatment standards have recently been promulgated are less likely to warrant such changes.</P>
                <P>
                    As part of the 2010 annual review, EPA also considered the number of facilities responsible for the majority of the estimated toxic-weighted pollutant discharges associated with an industrial activity. EPA applied a lower priority for potential revision to industrial categories where only a few facilities in a category accounted for the vast majority of toxic-weighted pollutant discharges (
                    <E T="03">i.e.,</E>
                     categories marked “(2)” in the “Findings” column in Table V-1 in section V.B.4 of this notice). EPA believes that revision of individual permits for such facilities may be more effective than a revised national rulemaking. Individual permit requirements can be better tailored to these few facilities and may take considerably less time and resources to establish than revising the national effluent guidelines. The Docket accompanying this notice lists facilities that account for the vast majority of the estimated toxic-weighted pollutant discharges for a particular category (see DCN 07320). For these facilities, EPA will consider identifying pollutant control and pollution prevention technologies that will assist permit writers in developing facility-specific technology-based effluent limitations on a best professional judgment (BPJ) basis. In future annual reviews, EPA also intends to re-evaluate each category based on the information available at the time in order to evaluate the effectiveness of the BPJ permit-based support.
                </P>
                <P>EPA also applied a lower priority to categories without sufficient data to determine whether revision would be appropriate. For any industrial categories marked “(5)” in the “Findings” column in Table V-1 in section V.B.4 of this notice, EPA lacks sufficient information at this time on the magnitude of the toxic-weighted pollutant discharges. EPA will continue reviewing available data on the discharges and will seek additional information on the discharges from these categories in the next annual review in order to determine whether a detailed study is warranted. See the appropriate section in the TSD for the final 2010 Plan (see DCN 07320) for EPA's data needs for these industrial categories. This assessment provides an additional level of quality assurance on the reported pollutant discharges and number of facilities that represent the majority of toxic-weighted pollutant discharges.</P>
                <P>For industrial categories marked “(4)” in the “Findings” column in Table V-1 in section V.B.4 of this notice, EPA had sufficient information on the toxic-weighted pollutant discharges to continue or complete a detailed study of these industrial categories.</P>
                <P>
                    For industrial categories marked “(6)” in the “Findings” column in Table V-1 in section V.B.4 of this notice, EPA is identifying this industry for a revised effluent guidelines rulemaking.
                    <PRTPAGE P="66291"/>
                </P>
                <P>Next, EPA considered the availability of technologies to reduce pollutant discharges. EPA does not have, for all of the 57 existing industrial categories, information about the availability of treatment or process technologies to reduce pollutant wastewater discharges beyond the performance of the technologies upon which existing effluent guidelines and standards were developed. At present 46 states and one U.S. territory are authorized to administer the CWA NPDES program. Under the CWA, permitting authorities must include water-quality based effluent limits where the technology-based effluent limits are not sufficient to meet applicable water quality standards. Therefore, dischargers may have already installed technologies that reduce pollutant discharges to a level below the original technology-based requirements in order to meet such water-quality based effluent limitations.</P>
                <P>Analyzing the significance of the remaining pollutant discharges is most useful for assessing the potential effectiveness of additional technologies because such an analysis focuses on the amount and significance of pollutant discharges that would actually be removed through new, technology-based nationally-applicable regulations for these categories. Where potential pollutant discharge reductions are not significant, there are likely few effective technology options for a technology-based rule. Once EPA determined which industries have the potential for significant additional pollutant removals, EPA further examined the availability of technologies for certain industries. For example, EPA identified technologies to minimize pollutant discharges from coalbed methane extraction facilities (see Coalbed Methane Point Source Category: Detailed Study Report, EPA-820-R-10-022, DCN 09999).</P>
                <P>
                    EPA also considered whether there was a way to develop a suitable tool for comprehensively evaluating the availability and affordability of treatment or process technologies, but determined that there is not, because the universe of facilities is too broad and complex. EPA could not find a reasonable way to prioritize the industrial categories based on readily available engineering and economic data. In the past, EPA has gathered information regarding technologies and economic achievability for one industrial category at a time through detailed questionnaires distributed to hundreds of facilities within a category or subcategory for which EPA has commenced rulemaking. Such information-gathering is subject to the requirements of the Paperwork Reduction Act (PRA), 33 U.S.C. 3501, 
                    <E T="03">et seq.</E>
                     The information acquired in this way is valuable to EPA in its rulemaking efforts, but the process of gathering, validating and analyzing the data can consume considerable time and resources. EPA does not think it is appropriate or feasible to conduct this level of analysis for all point source categories in conducting an annual review. Rather, EPA uses its analyses of existing pollutant discharges to identify the categories with the largest toxic-weighted discharges. From this smaller list of categories, EPA evaluates the possibility of effective technologies and selects certain industries for further examination (
                    <E T="03">e.g.,</E>
                     Preliminary Category Reviews, Detailed Studies).
                </P>
                <P>Additionally, when EPA becomes aware of the growth of a new industrial activity within an existing category or where new concerns are identified for previously unevaluated pollutants discharged by facilities within an industrial category, EPA applies more scrutiny to the category in a subsequent review.</P>
                <P>EPA also considers whether there are industrial activities not currently subject to effluent guidelines or pretreatment standards that should be included with these existing categories, either as part of existing subcategories or as potential new subcategories. These industries are sometimes suggested by commenters during the public comment period or may come to EPA's attention in other ways.</P>
                <P>
                    EPA also continued to use the quality assurance project plan (QAPP) developed for the 2009 annual review to document the type and quality of data needed to make the decisions in this 2010 annual review and to describe the methods for collecting and assessing those data (see EPA-820-R-10-021). EPA performed quality assurance checks on the data used to develop estimates of toxic-weighted pollutant discharges (
                    <E T="03">i.e.,</E>
                     verifying 2008 discharge data reported to TRI, PCS and ICIS-NPDES) to determine whether any of the pollutant discharge estimates relied on incorrect or suspect data. For example, EPA contacted facilities and permit writers to confirm and, as necessary, correct TRI, PCS or ICIS-NPDES data for facilities that EPA had identified in its screening-level review as the significant dischargers.
                </P>
                <P>In summary, through its screening level review, EPA focused on those point source categories that appeared to have the greatest potential for reducing hazard to human health and the environment. This enabled EPA to concentrate its resources on conducting more in-depth reviews of the higher priority categories.</P>
                <HD SOURCE="HD3">b. Further Review of Prioritized Categories</HD>
                <P>EPA conducts a preliminary category review when it lacks sufficient data to determine whether a regulatory revision would be appropriate and for which EPA is performing a further assessment of pollutant discharges before starting a detailed study. These assessments provide an additional level of quality assurance on the reported pollutant discharges and number of facilities that represent the majority of toxic-weighted pollutant discharges.</P>
                <P>In conducting a preliminary category review, EPA uses the same types of data sources used for the detailed studies or effluent guidelines development but in less depth. As part of the preliminary category reviews, EPA may evaluate technologies that could achieve better control of pollutant discharges. EPA might also conduct surveys or collect data from additional sources. The full description of EPA's methodology for the 2010 annual review is presented in the Technical Support Document (TSD) for the final 2010 Plan (see DCN 07320).</P>
                <HD SOURCE="HD3">c. Detailed Studies</HD>
                <P>EPA conducts detailed studies to obtain information on hazard, availability and cost of technology options, and other factors in order to determine if it would be appropriate to identify the category for possible effluent guidelines revision. The full description of EPA's methodology for the 2010 review is presented in the Technical Support Document (TSD) for the final 2010 Plan (see DCN 07320).</P>
                <HD SOURCE="HD3">3. How did EPA's 2009 annual review influence its 2010 annual review of point source categories with existing effluent guidelines and pretreatment standards?</HD>
                <P>
                    In view of the annual nature of its reviews of existing effluent guidelines and pretreatment standards, EPA believes that each annual review can and should influence succeeding annual reviews, 
                    <E T="03">e.g.,</E>
                     by indicating data gaps, identifying new pollutants or pollution reduction technologies, or otherwise highlighting industrial categories for additional scrutiny in subsequent years.
                </P>
                <P>
                    During its 2009 annual review, which concluded the end of December 2009, EPA continued detailed studies of the existing effluent guidelines and pretreatment standards for two industrial categories: Oil and Gas Extraction category (Part 435) for the purpose of assessing whether to revise the limits to include coalbed methane 
                    <PRTPAGE P="66292"/>
                    extraction as a new subcategory, and Hospitals (Part 460) which is part of the Health Care Industry detailed study on the management of unused pharmaceuticals. In addition, EPA conducted a preliminary study of the Ore Mining and Dressing category (part 440) during 2009. EPA used the findings, data and comments on the 2009 annual review to inform its 2010 annual review and the final 2010 Plan. The 2010 review also built on the previous reviews by incorporating some refinements to assigning discharges to categories and updating toxic weighting factors.
                </P>
                <P>EPA published the findings from its 2009 annual review with its preliminary 2010 Plan (December 28, 2009, 74 FRN 68599), making the pollutant discharge and industry profile data available for public comment. Docket No. EPA-HQ-OW-2008-0517.</P>
                <HD SOURCE="HD3">4. How did EPA consider public comments in its 2010 annual review?</HD>
                <P>EPA's annual review process considers information provided by stakeholders regarding the need for new or revised effluent limitations guidelines and pretreatment standards. Public comments received on EPA's prior reviews and Plans helped the Agency prioritize its analysis of existing effluent guidelines and pretreatment standards during the 2010 review. Public comments, depending on the number, the issues, the data and information submitted and the recommendations made therein, can influence the annual review.</P>
                <P>In accordance with CWA section 304(m)(2), EPA published the preliminary 2010 Plan for public comment prior to this publication of the final 2010 Plan. See December 28, 2009 (74 FRN 68599). The Docket accompanying this notice includes a complete set of all of the comments submitted, as well as the Agency's responses (see DCN 07368). The Agency received 51 sets of comments on the preliminary 2010 Plans.</P>
                <P>Commenting organizations representing industry included the American Petroleum Institute, American Health Care Association, Independent Petroleum Association of America, National Association of Clean Water Agencies, American Dental Association, American Water Works Association, and the National Mining Association.</P>
                <P>Six environmental groups commented, including the Northern Plains Resources Council, Earth Justice, Environmental Integrity Project and the Powder River Basin Council.</P>
                <P>Eight states, or state representing organizations, also commented, including the states of WY, MT, NY, WI, OR, FL, ID and the Quicksilver Caucus.</P>
                <P>EPA received comments from 22 private individuals, all addressing the issue of the environmental impacts of hydraulic fracturing used in shale gas extraction. Most of these individuals were from NY and PA, and their comments reflected concerns about shale gas extraction in the Marcellus Shale formation.</P>
                <P>EPA also received comments from one Tribal Nation (the Northern Cheyenne) and four local organizations (Tompkins County Senior Citizen Council, St. Paul MetroCouncil, Bay Area Pollution Prevention Group and Albany Medical College).</P>
                <P>Comments were distributed among the following subject areas, in order of abundance:</P>
                <FP SOURCE="FP-1">—Coalbed Methane and Shale Gas Extraction (40 comments)</FP>
                <FP SOURCE="FP-1">—Health Care Industry—(unused pharmaceuticals) (35 comments)</FP>
                <FP SOURCE="FP-1">—Ore Mining and Dressing (2 comments)</FP>
                <FP SOURCE="FP-1">—Steam Electric Power Generation (2 comments)</FP>
                <FP SOURCE="FP-1">—Effluent limitation guidelines (ELGs) and Plan process in general (2 comments)</FP>
                <FP SOURCE="FP-1">—Dental Amalgam (1 comment)</FP>
                <FP SOURCE="FP-1">—Other (2 comments)</FP>
                <P>For coalbed methane, there were seven comments that also expressed concern with the practice of shale gas extraction; 13 comments requesting that EPA examine shale gas extraction in the coalbed methane detailed study; seven requests to not add shale gas extraction to the coalbed methane study; six commenters who suggested that EPA should do a coalbed methane ELG rule; and seven commenters who suggested that EPA not do a rule.</P>
                <P>For the Health Care industry, in particular the management of unused pharmaceuticals, EPA received three comments supporting the detailed study; three comments suggesting EPA work more closely with the U.S. Drug Enforcement Agency (DEA); four comments that explained EPA should work with the Food and Drug Administration (FDA) and health insurance companies to encourage unused pharmaceutical returns and a coordinated message about such; twelve comments indicating EPA should develop BMPs, disposal guidance, flyers and other disposal information; three comments supporting take-back programs; six comments that suggested current disposal practices are barriers to return/reuse; and four comments indicating that pharmaceutical flushing should be controlled by sewage treatment authorities.</P>
                <P>For the Ore Mining and Dressing category there were two comments that stated EPA should not develop a new ELG.</P>
                <P>For the Steam Electric Power Generation industry, which is currently undergoing a revised ELG as a result of last year's Plan, there was one comment that supported EPA's selection of the steam electric industry for rulemaking, and one commenter that believed EPA made several errors in its detailed study final report.</P>
                <P>One commenter asked EPA to select the dental industry for an ELG rulemaking, arguing that the industry is responsible for half of the national mercury loadings to Publicly Owned Treatment Works (POTWs), and the ongoing activities under the Dental Amalgam control MOU are insufficient.</P>
                <P>A more detailed summary table of the comments can be found in the 2010 TSD, EPA-820-R-10-021 (DCN 07320). EPA carefully considered all public comments and information submitted in developing the final 2010 Plan. A comment response document is also available at (DCN 07368).</P>
                <HD SOURCE="HD2">B. What were EPA's findings from its 2010 annual review for categories subject to existing effluent guidelines and pretreatment standards?</HD>
                <HD SOURCE="HD3">1. Screening-Level Review</HD>
                <P>In its 2010 screening level review, EPA considered hazard, and the other factors described in section V.A.2. above, in prioritizing effluent guidelines for potential revision. See Table V-1 in section V.B.4 of this notice for a summary of EPA's findings with respect to each existing category; see also the TSD for the final 2010 Plan, EPA-820-R-10-021, DCN 07320). Of the categories subject only to the screening level review in 2010, EPA is not identifying any for effluent guidelines rulemaking at this time, based on the factors described in section V.A above and in light of the effluent guidelines rulemakings in progress.</P>
                <P>EPA carefully examined the industrial categories currently regulated by existing effluent guidelines that cumulatively comprise 95% of the reported hazard (reported in units of toxic-weighted pound equivalent or TWPE). The TSD for the preliminary 2010 Plan presents a summary of EPA's review of these 21 industrial categories (see DCN 07320).</P>
                <P>
                    EPA identified one category where additional data are required to evaluate toxic-weighted pollutant discharges. EPA will initiate a preliminary category review for the cellulosic products 
                    <PRTPAGE P="66293"/>
                    segment of the Plastics Molding and Forming (part 463) industrial category.
                </P>
                <P>Although EPA identified only one industrial category for preliminary category review in the 2010 annual review, EPA also identified that estimated toxic-weighted pollutant discharges of lead from the Pulp, Paper, and Paperboard (part 430) industrial category need further investigation. EPA intends to continue reviewing the Pulp, Paper and Paperboard industry during the 2011 annual review.</P>
                <P>EPA identified the need for additional data review as part of the 2011 annual review for three industrial categories. See the appropriate section in the TSD for the final 2010 Plan, EPA-820-R-10-021, (see DCN 07320) for a detailed discussion of EPA's findings for these industrial categories: Mineral Mining and Processing (part 436); Landfills (Part 445); and Waste Combustors (part 444). See Section IX of this notice for the requested public comments. Based on new data submitted with public comment and screening-level data collected as part of the 2011 annual review, EPA intends to re-evaluate the category toxic-weighted pollutant discharges.</P>
                <HD SOURCE="HD3">2. Results of Detailed Studies</HD>
                <HD SOURCE="HD3">Oil and Gas Extraction (part 435)</HD>
                <P>As a result of prior 304(m) planning, EPA initiated a detailed study of the coalbed methane industry and its wastewater discharges. Coalbed methane extraction is considered a subcategory of the Oil and Gas Extraction Point Source Category, although it is not currently subject to the effluent guidelines promulgated for this category. Since 2006, the coalbed methane industry has expanded. In addition, EPA received comments in 2005, 2008, and again during the 2010 review from citizens and environmental advocacy groups requesting development of a regulation for coalbed methane extraction as well as for shale gas extraction, another subcategory of the Oil and Gas Extraction Point Source Category. Unlike coalbed methane extraction, however, shale gas extraction is now subject to effluent guidelines for the Oil and Gas Extraction Point Source Category, although there are currently no applicable categorical pretreatment standards for shale gas extraction.</P>
                <P>Coalbed methane-produced water discharges can impact receiving surface waters and soils. Saline discharges from coalbed methane operations can adversely affect aquatic life. The large volume of water discharged can also cause stream bank erosion and salt deposition, creating hardpan soil. Long-term impacts include sodium buildup, reduction of plant diversity, mobilization of salts and other elements, and alteration of surface and subsurface hydrology.</P>
                <P>Overview of Operations:</P>
                <P>Methane gas is naturally created during the geologic process of converting plant material to coal (coalification). To extract the methane, coalbed methane operators drill wells into coal seams and pump out ground water. Removing the ground water from the formation is necessary to produce coalbed methane, as the water removal reduces the pressure and allows the methane to release from the coal to produce flowing natural gas. In 2008, 252 coalbed methane operators managed approximately 55,500 coalbed methane wells in the U.S. in 13 distinct regions, called basins.</P>
                <HD SOURCE="HD3">Produced Water</HD>
                <P>The ground water that has been pumped out of the well, called “produced water,” like most ground water found deep below the surface of the earth, has high salinity and can include pollutants such as chloride, sodium, sulfate, bicarbonate, fluoride, iron, barium, magnesium, ammonia, and arsenic. To quantify the amount of pollutants in coalbed methane produced waters, EPA relied on measuring total dissolved solids (TDS) and electrical conductivity (EC), which are bulk parameters for quantifying the total amount of dissolved solids in a wastewater.</P>
                <P>A single coalbed methane well can discharge thousands of gallons of produced water per day, and may discharge produced water for anywhere from 5 to 15 years. Coalbed methane wells have a distinctive production history characterized by an early stage when large amounts of water are produced to reduce reservoir pressure which in turn encourages release of gas; a stable stage when quantities of produced gas increase as the quantities of produced water decrease; and a late stage when the amount of gas produced declines and water production remains low.</P>
                <P>The quantity and quality of produced water varies from basin to basin, within a particular basin, from coal seam to coal seam, and over the lifetime of a coalbed methane well. For example, coalbed methane produced water volumes range from 1,000 gallons per day per well in the San Juan Basin to 17,000 gallons per day per well in the Powder River Basin.</P>
                <HD SOURCE="HD3">Management of Produced Water</HD>
                <P>Coalbed methane operators need to dispose of thousands of gallons of produced water per day for each coalbed methane well. Operators can employ a range of options for treatment and management of this wastewater.</P>
                <P>Preliminary estimates based on survey data predict that approximately 47 billion gallons of produced water are pumped annually from coal seams across the country. Approximately 45% of those produced waters are directly discharged to waters of the U.S., for a total national discharge of 22 billion gallons per year.</P>
                <P>Surface water discharge is most prevalent in three U.S. coalbed methane basins: The Black Warrior Basin in Alabama and Mississippi (11% of total coalbed methane surface discharges), the Powder River Basin in Wyoming and Montana (72% of total coalbed methane surface discharges), and the Raton Basin in Colorado and New Mexico (11% of total coalbed methane surface discharges). Many of these discharges are largely untreated. Surface discharge occurs rarely, if at all, in the other major commercial basins.</P>
                <P>
                    In the other commercial basins in the U.S, coalbed methane operators are, for the most part, able to prevent discharging their produced water by discharging the water to land (where there may be other impacts to the soil or vegetation), re-injecting the produced water back into the ground, or using the water in one of many beneficial use options (
                    <E T="03">e.g.,</E>
                     stock watering, irrigation).
                </P>
                <HD SOURCE="HD3">Treatment of Produced Waters</HD>
                <P>Available technology options for adequately removing pollutants from produced water include ion exchange and reverse osmosis.</P>
                <HD SOURCE="HD3">Summary of Outreach</HD>
                <P>
                    In 2007 EPA conducted several site visits to coalbed methane basins throughout the country and gathered information on potential treatment technologies for coalbed methane-produced water discharges. EPA also conducted widespread outreach with stakeholders, both in the industry and from the communities adjacent to coalbed methane basins. EPA conducted more than 30 site visits to locations in six coalbed methane basins and met with over 300 different stakeholders. EPA also conducted 13 meetings and teleconferences with over 150 stakeholders. In addition to the extensive information collection through site visits and outreach, EPA acknowledged that an informed decision about rulemaking would 
                    <PRTPAGE P="66294"/>
                    require even more detailed information. EPA developed an industry questionnaire, solicited public comment twice, and in 2009 obtained OMB approval under the Paperwork Reduction Act, to conduct a mandatory survey directed at operators of coalbed methane projects which consist of a single well or a group of wells operated by the same company. The questionnaire collected technical and economic data in a two-part survey, a screener and a detailed survey, on the operations and operators of coalbed methane projects. Questionnaire responses arrived in early 2010 and the data was used by EPA to create national estimates of pollutant discharges across the country from the coalbed methane industry and to develop an economic profile of the industry.
                </P>
                <P>In response to the 2010 preliminary Plan, EPA received 32 comments on coalbed methane extraction. Comments from industry sources did not support rulemaking for coalbed methane, suggesting an effluent guideline was not appropriate due to the variability of produced water quality, quantity and available management techniques across the country. Additionally, industry stated that the current regulatory framework of site-specific BPJ permits was adequately addressing pollutant discharges from produced water discharges.</P>
                <P>The final detailed study report for coalbed methane is being issued concurrent with the publication of this FR Notice and is a part of the final 2010 Plan. The study report is available at DCN 09999.</P>
                <P>Coalbed methane production represents about 8% of natural gas production in this country, and coalbed methane extraction is expected to continue for decades. Of the 22 billion gallons of water discharged to surface water each year some has high total dissolved solids. The detailed study also found that there are readily available technologies to treat this produced water. As a result of the information gathered in the detailed study, EPA has decided to initiate rulemaking for coalbed methane extraction, a currently unregulated subcategory of the Oil and Gas Extraction Point Source Category.</P>
                <HD SOURCE="HD3">3. Results of Preliminary Category Reviews</HD>
                <HD SOURCE="HD3">Ore Mining and Dressing (Part 440)</HD>
                <P>As discussed in the 2008 Final Effluent Guidelines Program Plan, EPA conducted a preliminary study of facilities covered under 40 CFR part 440 “Ore Mining and Dressing Point Source Category” to examine why toxic weighted pollutant discharges by the ore mining industry ranked relatively high compared to other industries in the 2002 through 2008 annual reviews. The purpose of the study was to identify, collect, and review readily available existing data and information on toxic pollutants in wastewater discharges to determine whether additional analysis or revision of 40 CFR part 440 might be warranted to better control toxic discharges.</P>
                <P>The preliminary study focused on active ore mines covered under 40 CFR part 440 subpart J: “Copper, Lead, Zinc, Gold, Silver, and Molybdenum Ores.” These types of mines comprise approximately 76 percent (263) of the approximately 345 ore mines in the United States. Inactive ore mines were not included as they are not covered by the effluent guidelines.</P>
                <P>Approximately 294 ore mines currently have National Pollutant Discharge Elimination System (NPDES) wastewater discharge permits. There is a difference between the total number of ore mines and the number with NPDES permits because not all ore mines have wastewater discharges. The approximately 1,870 placer mines, covered under 40 CFR part 440 subpart M, were not examined in this study because they employ mining practices and wastewater streams that are fundamentally different from mines covered under the other subparts of 40 CFR part 440.</P>
                <P>The preliminary study examined information pertaining to the two types of wastewater discharged by ore mines: Process wastewater (including mine drainage) and stormwater. Process wastewater is covered under 40 CFR part 440. Stormwater is not covered under 40 CFR part 440 unless it is commingled with process wastewater prior to discharge to a surface waterbody.</P>
                <P>The study was limited by incomplete national-level process wastewater discharge data, and the lack of any nationally representative stormwater data for the ore mines of interest. EPA did review available ore mine-specific process wastewater discharge information, available Total Maximum Daily Load (TMDL) reports, information for ore mine site stormwater discharges, and an industrial wastewater treatment technology, known as high density sludge recycling, which was identified during the course of the study.</P>
                <P>Based on EPA's review of toxic pollutant data, EPA found that in 2007, the most recent year for which quality-checked data are available, approximately only two percent of ore mining facilities were responsible for approximately 90 percent of toxic weighted discharges by the ore mining industry for toxic pollutants.</P>
                <P>Given that only a small percentage of active ore mines account for the majority of toxic weighted discharges, this can best be addressed through permitting, compliance, and enforcement activities for the specific ore mining sources, rather than by revision of 40 CFR part 440.</P>
                <P>While the available toxic pollutant data does not suggest that EPA revisit the ELG for ore mining and dressing (40 CFR part 440) at this time, the Agency currently remains concerned about many other types of mining-related water quality impairments. EPA has a number of activities that address discharges of pollutants from mines including interim guidance on Improving EPA Review of Appalachian Surface Coal Mining Operations Under the Clean Water Act, National Environmental Policy Act, and the Environmental Justice Executive Order, plans to revise the water quality criteria for selenium, increased attention on compliance with, and enforcement of, individual permit limits; improved permitting guidance and more stringent discharge monitoring requirements in permits.</P>
                <P>The Ore Mining Preliminary Study report is being issued concurrent with the publication of this FR Notice and represents a portion of the final 2010 Plan. The Ore Mining Preliminary Study report (EPA-820-R-10-025) is available at DCN 07369.</P>
                <HD SOURCE="HD3">4. Other Reviews</HD>
                <HD SOURCE="HD3">Shale Gas Extraction</HD>
                <HD SOURCE="HD3">Overview</HD>
                <P>As discussed in the March 2011 “Blueprint for a Secure Energy Future,” (“Blueprint”) the production of domestic natural gas enhances energy security and fuels our nation's economy (DCN 07496). In 2010, U.S. natural gas production reached its highest level in more than 30 years with much of the increase resulting from the production of natural gas from shale formations. This is due to recent advances in horizontal drilling and hydraulic fracturing that have made extraction of natural gas from shale formations more technically and economically feasible. The increase is expected to continue. The U.S. Department of Energy projects shale gas production as a percentage of the U.S. natural gas production will increase over the next 25 years from the current level of 14% to an estimated 45%.</P>
                <P>
                    As indicated in the “Blueprint,” the Administration is taking several steps to 
                    <PRTPAGE P="66295"/>
                    ensure natural gas is developed in a safe and environmentally responsible manner. The “Blueprint” lists several initiatives to support these goals, including disclosure of fracturing chemicals, public meetings, EPA- and DOE-led research, the establishment of an expert panel to examine fracturing issues, and technical assistance to State regulators. In particular, the “Blueprint” directed the Secretary of Energy, in consultation with the EPA Administrator and Secretary of the Interior, to task the Secretary of Energy Advisory Board (SEAB) with establishing a subcommittee to examine issues related to shale gas production through hydraulic fracturing. The subcommittee is supported by DOE, EPA and DOI, and its membership extends beyond SEAB members to include leaders from industry, the environmental community, academia, and states. The subcommittee is working to identify both immediate steps that can be taken to improve the safety and environmental performance of fracturing and to provide consensus recommended advice to the agencies on practices for shale extraction to ensure the protection of public health and the environment. On August 11, 2011, the Subcommittee submitted a 90-day report with its preliminary recommendations (DCN 07504). The report recommends measures to increase public disclosure and transparency and address concerns about air and water pollution. The report also recommends a range of tools for implementing these measures, including regulation, continuous improvement in best practices by industry, and ongoing research and development.
                </P>
                <P>Today's decision to initiate rulemaking is consistent with these initiatives in that it addresses potential environmental impacts associated with hydraulic fracturing. This is part of the Administration's commitment in the “Blueprint” to continue to review existing regulatory structures governing both onshore and offshore oil and gas development to identify potential efficiencies in those processes and any crucial gaps that pose safety and environmental risks.</P>
                <P>EPA will carefully consider the SEAB's preliminary and final recommendations as EPA develops regulatory options. EPA's regulatory action will complement and benefit by the initiatives already announced in the President's “Blueprint.”</P>
                <HD SOURCE="HD3">Introduction</HD>
                <P>The production of natural gas from shale formations has increased over the past few years and the upward trend is expected to continue. For example, data from the Pennsylvania Department of Environmental Protection shows that the number of shale gas wells drilled in Pennsylvania increased substantially in the past few years, with more wells drilled and permits issued between January and April of 2010, than during all of 2008 (DCN 07474). As the number of shale gas wells in the U.S. increases, so too does the volume of shale gas wastewater that requires disposal. Wastewater associated with shale gas extraction can contain high levels of total dissolved solids (TDS), fracturing fluid additives, metals, and naturally occurring radioactive materials (NORM).</P>
                <P>EPA requested comments in the 2010 Preliminary Effluent Guidelines Plan on whether to include shale gas extraction as part of the Coal Bed Methane Detailed Study. Many of the comments on this topic expressed general concern about drinking water contamination and water quality impacts from shale gas extraction.</P>
                <P>Industry commenters asserted that a shale gas rulemaking was not needed since existing Oil and Gas Effluent Guidelines require zero discharge from shale gas extraction. Although the existing regulations for onshore oil and gas extraction prohibit direct discharges of wastewaters from shale gas extraction, the current regulations do not contain pretreatment standards for pollutants associated with these discharges. EPA also has data that document pollutants in wastewaters associated with shale gas extraction are not treated by the technologies typically used at publicly and privately owned treatment facilities (DCN 07477 and DCN 07472A1).</P>
                <P>EPA ultimately decided not to expand the Coal Bed Methane Study to include shale gas extraction. However, as a result of public comments, EPA began reviewing available data to inform a decision on whether or not a rulemaking to establish pretreatment standards for shale gas extraction was appropriate.</P>
                <HD SOURCE="HD3">Overview of Shale Gas Operations</HD>
                <P>The term “Shale Gas” is typically used to describe natural gas trapped in underground shale deposits. Well operators use the process of hydraulic fracturing to extract this gas. Hydraulic fracturing is a method of extracting natural gas from highly impermeable rock formations by injecting large amounts of fracturing fluids (typically 3 to 5 million gallons) at high pressures to create a network of fissures, typically 250 feet in length (with occasional fractures as long as 1,000 feet), in the rock formations and provide the natural gas a pathway to travel to the well for extraction.</P>
                <P>
                    While the composition of the fracturing fluids varies from region to region, and is specific to the formation to be fractured, the classes of compounds in the fluids are largely the same. The major components of fracturing fluid are water and proppant (typically sand), used to keep the fractures open after the fracturing has been complete, and chemical additives. EPA has reviewed data presented by industry sources including Chesapeake Energy, Talisman Energy, the Gas Technology Institute (GTI) and Halliburton, regarding the different classes of compounds in fracturing fluids, such as biocides, friction reducers, surfactants, scale and corrosion inhibiters and acids. Additionally, EPA has reviewed a registry developed jointly by the Ground Water Protection Council and the Interstate Oil and Gas Commission of chemicals used in fracturing fluids voluntarily provided by oil and gas companies (
                    <E T="03">http://www.fracfocus.org</E>
                    ).
                </P>
                <P>A portion of the injected fracturing fluid will remain in the fractures. The precise amount of fluid retention is uncertain and depends on the geologic formation. The fluids not retained in the formation will ultimately return to the surface as “flowback” or “produced water.” These wastewaters may contain the chemicals originally found in the fracturing fluids as well as other naturally occurring constituents that may be released into the fluid as the rock formations are broken.</P>
                <HD SOURCE="HD3">Produced Waters From Shale Gas Extraction</HD>
                <P>A shale gas well has two distinct phases of water production from the formation. The first phase typically occurs during the first 30 days following the fracturing process (DCN 07482A10 and DCN 07482A23), also known as the “flowback period.” During this time a portion of the injected fracturing fluid will return to the surface.</P>
                <P>There are varying reports on the actual volume of flowback; multiple studies and presentations report that volumes ranging from 10-75% of the injected fracturing fluids are returned during the flowback period. The amount of “flowback” is dependent, in part, on the geology of the shale basin (DCN 07477).</P>
                <P>
                    After this initial surge of flowback passes, produced water will continue to come to the surface for the life of the well. Chesapeake Energy provided data indicating that “long term” produced water volumes range from 200-1,000 gallons per million cubic feet of gas 
                    <PRTPAGE P="66296"/>
                    produced depending on the basin in which the well is located. Currently, the Barnett shale formation has the highest long term flowback volumes and the Marcellus shale formation has the lowest. While there is no consensus on when the initial “flowback” period ends, some operators choose to view all water passing from the formation up through the wellbore as “produced water” regardless of the time period in which it occurs.
                </P>
                <HD SOURCE="HD3">Pollutants in Shale Gas Wastewaters</HD>
                <P>Produced waters (shale gas wastewaters) generally contain elevated concentrations of fracturing fluid additives, salt content (often expressed as total dissolved solids—TDS), conventional pollutants, organics, metals, and NORM (naturally occurring radioactive material).</P>
                <P>EPA has multiple sources of shale gas produced water characterization data including reports published by the Department of Energy (DCN 07476 and DCN 07474) and industry flowback analysis made available by Chesapeake Energy, Talisman Energy, Devon Energy, Superior Well Services, and GTI.</P>
                <P>Total dissolved solids is the most reported pollutant. Data on TDS concentrations are widely available due to the potential negative impact of high concentrations of TDS on the ability to re-use the shale gas wastewater. Elevated TDS levels may also impact the effectiveness of the additives in the fracturing fluids (DCN 07482A03).</P>
                <P>High concentrations of TDS are common in shale gas wastewater across the country, although the levels may vary from basin to basin. TDS concentrations of 100,000 ppm are typical and can be as high as 400,000 ppm (DCN 07476). For comparison, sea water contains approximately 35,000 ppm TDS. The main component ion of TDS in shale gas wastewater appears to be chloride, which accounts for approximately 60% of the TDS found in shale gas wastewater. Chloride has been measured in shale gas wastewater water at levels of 8,800—153,000 ppm. Other components may include barium (21—13,900 ppm), strontium (Non-Detect—3,700 ppm), calcium (314—23,500 ppm), magnesium (135—5,000 ppm) and sodium (2,800—65,000 ppm). Additionally, the concentrations of TDS in produced water from each well tend to increase over time (DCN 07482A13, DCN 07482A10, DCN 07482A23, and DCN 07482A15).</P>
                <P>Organic and inorganic pollutants appear to be less frequently sampled in comparison to the well documented TDS concentrations. EPA has reviewed limited data on organic pollutants in produced water and found a range of pollutant concentrations: phenol (Non-Detect—3,700 ppb), pyridine (Non-Detect—534 ppb), benzene (1—3,400 ppb), ethyl benzene (Non-Detect—1,400 ppb), toluene (Non-Detect—11,400 ppb), total xylenes (2—14,500 ppb), and glycol (10,000—120,000 ppb). Additionally, bromide linked to shale gas wastewater has been measured in POTW outfalls (1,020—1,100 ppm) (DCN 07481A04, DCN 07481A03, DCN 07479A06, and DCN 07481A02).</P>
                <P>NORM is an acronym for naturally occurring radioactive material. The U.S. Department of Energy published a report in 2009 that includes a description of the process by which NORM in the rock formations would be brought to the surface by hydraulic fracturing (DCN 07476). Radium 226, which has a half life of over 1,000 years, has been found to be present in concentrations up to 16,030 pCi/l in the Marcellus Shale produced water as reported by the New York State Department of Environmental Conservation in 2009 (DCN 07473). This reported radionuclide concentration exceeds the drinking water Maximum Contaminant Level of 5 pCi/L for Radium 226.</P>
                <P>While EPA has some data on the additives in fracturing fluid, EPA is not aware of any substantial sampling data on the presence or absence of these additives in shale gas wastewaters.</P>
                <HD SOURCE="HD3">Shale Gas Wastewater Disposal and Treatment</HD>
                <P>Up to 1 million gallons of shale gas wastewater may be produced from a single well within the first 30 days following fracturing. Smaller volumes of shale gas wastewater will also be produced throughout the life of the well. Many well operators transport this wastewater to Underground Injection Control (UIC) program permitted brine injection wells where the wastewater is permanently emplaced underground, a common practice in the oil and gas industry. The ability to inject shale gas wastewater varies based on local geology and permitting requirements. For example, this practice is widely used in the Barnett (Texas) formation where the state has more than 12,000 brine disposal wells, and less so in the Marcellus formation (PA, WV, OH, NY, MD). For comparison purposes, the Marcellus formation states presently have less than 300 brine disposal wells. The state of Pennsylvania, where most Marcellus shale drilling occurs, has six brine disposal wells.</P>
                <P>
                    Some operators elect to re-use a portion of the wastewater to replace and/or supplement fresh water in formulating fracturing fluid for a future well 
                    <SU>1</SU>
                    <FTREF/>
                    . Re-use of shale gas wastewater is, in part, dependent on the levels of pollutants in the wastewater and the proximity of other fracturing sites that might re-use the wastewater. This practice has increased over the last couple of years, especially in regions of the country where fresh water is not plentiful.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         In order to prepare shale gas wastewater for re-use, the produced water is filtered to remove suspended solids from wastewater and then combined with fresh water and additives to formulate fracturing fluid. Typically re-used shale gas wastewater makes up only a small percentage of water demand for fracturing operations.
                    </P>
                </FTNT>
                <P>
                    When injection and re-use are not viable options for shale gas wastewater disposal, operators may dispose of this wastewater by sending it to POTWs or to private centralized waste treatment facilities (CWTs). The vast majority of POTWs employ equalization, bulk solids removal, biological treatment, and disinfection. POTWs are likely effective in treating only some of the pollutants in shale gas wastewater, such as the conventional and organic pollutants. These treatment technologies are not designed to treat high levels of TDS, NORM, or high levels of metals 
                    <SU>2</SU>
                    <FTREF/>
                    ; it is believed that much of these pollutants pass through the POTW untreated. Many CWTs, of which 90% discharge to POTWs, are similarly not designed to treat for high TDS or NORM (DCN 07474).
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Metcalf &amp; Eddy Inc. (2003) Wastewater Engineering: Treatment and Reuse McGraw-Hill, New York.
                    </P>
                </FTNT>
                <P>High concentrations of TDS may also lead to inhibition or disruptions of POTW treatment efficiency. However, most POTWs that accept shale gas wastewaters blend small volumes with traditional POTW wastewaters (1% shale gas wastewater by volume) to reduce pollutant concentrations through dilution to prevent POTW inhibition (DCN 07474).</P>
                <HD SOURCE="HD3">Local Limits for Shale Gas Extraction Wastewater Introductions to POTWs</HD>
                <P>
                    Under the Clean Water Act statutory and regulatory framework, POTWs must establish requirements for any introduction of wastewater to the POTW or its collection system if it either would cause “pass through” or “interference” (
                    <E T="03">e.g.,</E>
                     cause the POTW to violate its permits limits, or interfere with the operation of the POTW or the beneficial use of its sewage sludge). POTWs are subject to the secondary treatment effluent limitations at 40 CFR part 133, which do not address the parameters of concern in shale gas extraction wastewater (
                    <E T="03">e.g.,</E>
                     TDS, chloride, radionuclides, 
                    <E T="03">etc</E>
                    ). If a water quality 
                    <PRTPAGE P="66297"/>
                    based effluent limit for these parameters is not included in the POTW permit, and if there is no evidence of interference, or sewage sludge contamination, the POTW may not have a basis to develop appropriate local limits. Independent of CWA requirements, POTWs can establish local limits under their sewer use ordinances for any parameters they determine could cause problems at the POTW. Currently, however, it is uncommon that POTWs have established local limits for the parameters of concern here, or that POTWs have water quality-based effluent limitations (WQBELs) for such parameters. Possible Impacts of Shale Gas Wastewater Discharges to Drinking Water Sources and Aquatic Life.
                </P>
                <P>
                    TDS has been shown to have negative impacts on aquatic life and drinking water. The level at which these impacts may occur is far less than the level of TDS typically found in shale gas wastewater. As described above, the average concentration of TDS in shale gas wastewaters is typically 100,000 ppm and can be as high as 400,000 ppm. Available data indicates the levels of TDS in shale gas wastewaters can often exceed recommended drinking water concentrations 
                    <SU>3</SU>
                    <FTREF/>
                     by a factor of 200. Because TDS concentrations in fresh non-brackish drinking water sources are typically well below the recommended drinking water levels, few drinking water treatment facilities have technologies to remove TDS.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Two published standards regarding TDS include EPA's secondary maximum contaminant level for TDS of 500 ppm and the U.S. Public Health Service recommendation that TDS in drinking water should not exceed 500 ppm.
                    </P>
                </FTNT>
                <P>
                    Aquatic life toxicity of freshwater contaminated with high TDS is dependent on the specific ionic composition of the water. In shale gas wastewaters, the largest single contributor to TDS is chlorides. Macroinvertebrates, and more specifically aquatic insects, have an open circulatory system and are more sensitive to pollutants like chloride, which at elevated exposure concentrations, negatively affect their ability to maintain the right concentration of salts and water in the body, which involves excreting metabolic wastes that would be toxic to the organism if allowed to accumulate. Based on laboratory toxicity data from EPA's 1988 chloride criteria document and more recent studies, invertebrate sensitivity to chloride acute effect concentrations ranged from 953 ppm to 13,691 ppm and chronic effect concentrations ranged from 489 ppm to 556 ppm. Aquatic vertebrates such as fish and frogs are less sensitive to chloride with acute effect concentrations ranging from 3,959 ppm to 14,500 ppm and chronic effect concentrations of 646 ppm to 955 ppm (DCN 07483). Available data on maximum chloride concentrations in shale gas wastewaters exceed the acute effect concentration by a factor of over 100 
                    <SU>4</SU>
                    <FTREF/>
                     (DCN 07482A15).
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         As discussed, many of the POTWs that accept shale gas wastewaters blend small volumes with traditional POTW wastewaters and reduce pollutant concentrations through dilution, so high concentrations in shale gas wastewaters do not necessarily lead to concentrations that exceed aquatic life criteria at the point of discharge.
                    </P>
                </FTNT>
                <P>
                    In addition to the laboratory data, EPA also has data from a 2009 Pennsylvania Department of Environmental Protection violation report documenting a fishkill attributed to a spill of diluted produced water in Hopewell Township, PA. A sample of the receiving water at the location of the fishkill was analyzed and TDS was measured as high as 7,000 ppm. The report documents the effects of the TDS on aquatic species such as fish and salamanders and frogs, including mortalities (DCN 07471).
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         While not related to shale gas wastewater, negative impacts of high TDS, including fish kills, were documented during 2009 at Dunkard Creek located in Monongalia County, Pennsylvania.
                    </P>
                </FTNT>
                <P>Moreover, bromide found in shale gas wastewater may react with disinfectants used at water treatment plants, creating potentially harmful disinfection byproducts such as trihalomethane. Bromide, linked to shale gas wastewater, has been recorded in POTW effluents in concentrations as high as 1,100 ppm (DCN 07472 and DCN 07481A02).</P>
                <P>Conclusion:</P>
                <P>Natural gas can increase our domestic energy options, thus, reducing dependence on non-U.S. sources, and it has the potential to improve air quality, increase stability in energy prices, and provide greater certainty about future energy reserves. Also, natural gas can serve as a bridge fuel from coal to even more efficient energy sources that can further reduce greenhouse-gas emissions. Natural gas holds great potential for our energy future and for our environment and EPA supports the commitment in the “Blueprint,” to responsible development of this important domestic resource and to proactively addressing the concerns that have been raised regarding potential negative impacts associated with hydraulic fracturing of shale formations.</P>
                <P>We have heard from the public and environmental organizations that they are concerned about the safety of natural gas production and the possible impacts that shale gas development could have on American communities. Some states have allowed development; others have put a hold on any development, cautious about the environmental impacts of shale gas production. Some states have asked that national standards be promulgated, and have also requested resources to help deal with these possible impacts. We have also heard from industry that shale gas extraction is currently regulated under the existing Oil and Gas Effluent Limitation Guidelines and those regulations are sufficient. What we know is that shale gas extraction generates extremely large volumes of wastewater that contain considerable pollutant loads. Some of this is being responsibly reinjected into appropriate underground wells; other volumes of wastewater are likely not being treated effectively by existing treatment facilities. Resulting discharges have the potential to affect both drinking water supplies and aquatic life. These concerns and issues will not dissipate as shale gas production is expected to increase. As a result, EPA has decided to initiate rulemaking to decide the appropriate level of pretreatment standards for this industry. As noted above, EPA will carefully consider the SEAB's recommendations as EPA develops regulatory options.</P>
                <P>As a first step in developing a regulation, EPA will conduct extensive data gathering, including site visits, stakeholder outreach, and development of a national survey of the industry. More specifically, EPA will visit natural gas extraction operations where hydraulic fracturing is occurring to obtain data directly from the well operators on well drilling and fracturing operations, produced water characteristics, and wastewater management. In addition to the site visits, EPA will reach out to stakeholders and other affected entities to identify and better understand concerns regarding environmental impacts associated with fracturing wastewater and potential industry implications of the regulation. Finally, EPA will begin the process of developing and seeking approval to distribute a nationally representative survey to collect information on the shale gas industry. This survey will assist EPA in obtaining national data on the operations, economics, and wastewater characteristics associated with hydraulic fracturing, as well as data pertaining to available treatment technologies for shale gas wastewater.</P>
                <P>
                    In 2010, Congress directed EPA to “carry out a study on the relationship between hydraulic fracturing and 
                    <PRTPAGE P="66298"/>
                    drinking water, using a credible approach that relies on the best available science, as well as independent sources of information. The conferees expect the study to be conducted through a transparent, peer-reviewed process that will ensure the validity and accuracy of the data.” In accordance with this direction from Congress, EPA conducted extensive stakeholder outreach to solicit advice regarding the design of the study. In February 2011, EPA submitted a draft study plan to the Science Advisory Board for peer review. In March and May 2011, the Science Advisory Board subcommittee met to provide peer review of the EPA's draft study plan. Consistent with the operating procedures of the SAB, an opportunity was provided for stakeholders and the public to provide comments for the SAB to take into account during their review. EPA is revising the study plan in response to the SAB's comments and initial study results are expected by the end of 2012. However, certain portions of the work will be long-term projects that are not likely to be finished at that time. Additional reports of study findings will be published as the longer-term projects progress. While the primary focus of this study is on impacts of hydraulic fracturing on drinking water resources, including surface water impacts, EPA will carefully review and consider any relevant information that is collected to support this study. Likewise, any data collected pursuant to this new rulemaking will be shared with the EPA office that is conducting the Congressionally-mandated study.
                </P>
                <P>Should the report or EPA's rulemaking survey, in combination with other data gathering and public outreach, indicate that POTWs are already adequately treating shale gas wastewater so that it is not causing pass through or interference with POTW operations, including sludge management, EPA is open to adjusting its rulemaking plans accordingly. However, EPA believes that beginning rulemaking now, and particularly the data collection necessary to support such a rule, is an appropriate step given what we already know about wastewater discharges from the industry.</P>
                <HD SOURCE="HD3">5. Summary of 2010 Annual Review Findings</HD>
                <P>The summary of the findings of the 2010 annual review is presented below in Table V-1 (see also the TSD for the final 2010 Plan for greater details). This table uses the following codes to describe the Agency's findings with respect to each existing industrial category.</P>
                <P>(1) Effluent guidelines or pretreatment standards for this industrial category were recently revised through an effluent guidelines rulemaking, or a rulemaking is currently underway. Or EPA recently completed a preliminary study or a detailed study, and no further action is necessary at this time.</P>
                <P>(2) Revising the national effluent guidelines or pretreatment standards is not the best tool for this industrial category because most of the toxic and non-conventional pollutant discharges are from one or a few facilities in this industrial category. EPA will consider assisting permitting authorities in identifying pollutant control and pollution prevention technologies for the development of technology-based effluent limitations by best professional judgment (BPJ) on a facility-specific basis.</P>
                <P>
                    (3) Not identified as a priority based on data available at this time (
                    <E T="03">e.g.,</E>
                     not among industries that cumulatively comprise 95% of discharges as measured in units of TWPE).
                </P>
                <P>(4) EPA intends to start or continue a detailed study of this industry in its 2011 annual review to determine whether to identify the category for effluent guidelines rulemaking.</P>
                <P>(5) EPA is continuing or initiating a preliminary category review or will continue to review discharges using screening-level data because incomplete data are currently available to determine whether to conduct a detailed study or identify for possible revision. EPA typically performs a further assessment of the pollutant discharges before starting a detailed study of the industrial category. This assessment provides an additional level of quality assurance on the reported pollutant discharges and number of facilities that represent the majority of toxic-weighted pollutant discharges. EPA may also develop a preliminary list of potential wastewater pollutant control technologies before conducting a detailed study.</P>
                <P>(6) EPA is identifying this industry for a revision of an existing effluent guideline.</P>
                <P>Note that dental mercury is not included in the analysis below, as dental facilities do not currently have an effluent guideline.</P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="xs50,r50,15,13">
                    <TTITLE>
                        Table V-1—Findings From the 2010 Annual Review of Effluent Guidelines and Pretreatment Standards Conducted Under Section 301(
                        <E T="01">d</E>
                        ), 304(
                        <E T="01">b</E>
                        ), 304(
                        <E T="01">g</E>
                        ), and 307(
                        <E T="01">b</E>
                        ) 
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">No. </CHED>
                        <CHED H="1">
                            Industry category 
                            <LI>(listed alphabetically) </LI>
                        </CHED>
                        <CHED H="1">40 CFR Part </CHED>
                        <CHED H="1">Findings * </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">1 </ENT>
                        <ENT>Aluminum Forming </ENT>
                        <ENT>467 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2 </ENT>
                        <ENT>Asbestos Manufacturing </ENT>
                        <ENT>427 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3 </ENT>
                        <ENT>Battery Manufacturing </ENT>
                        <ENT>461 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4 </ENT>
                        <ENT>Canned and Preserved Fruits and Vegetable Processing </ENT>
                        <ENT>407 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">5</ENT>
                        <ENT>Canned and Preserved Seafood Processing </ENT>
                        <ENT>408 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">6 </ENT>
                        <ENT>Carbon Black Manufacturing </ENT>
                        <ENT>458 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7 </ENT>
                        <ENT>Cement Manufacturing </ENT>
                        <ENT>411 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">8 </ENT>
                        <ENT>Centralized Waste Treatment </ENT>
                        <ENT>437 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">9 </ENT>
                        <ENT>Coal Mining </ENT>
                        <ENT>434 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10 </ENT>
                        <ENT>Coil Coating </ENT>
                        <ENT>465 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">11 </ENT>
                        <ENT>Concentrated Animal Feeding Operations (CAFO) </ENT>
                        <ENT>412 </ENT>
                        <ENT>(1) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">12 </ENT>
                        <ENT>Concentrated Aquatic Animal Production </ENT>
                        <ENT>451 </ENT>
                        <ENT>(1) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">13 </ENT>
                        <ENT>Construction and Development </ENT>
                        <ENT>450 </ENT>
                        <ENT>(1) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">14 </ENT>
                        <ENT>Copper Forming </ENT>
                        <ENT>468 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">15 </ENT>
                        <ENT>Dairy Products Processing </ENT>
                        <ENT>405 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">16 </ENT>
                        <ENT>Electrical and Electronic Components </ENT>
                        <ENT>469 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">17 </ENT>
                        <ENT>Electroplating </ENT>
                        <ENT>413 </ENT>
                        <ENT>(1) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">18 </ENT>
                        <ENT>Explosives Manufacturing </ENT>
                        <ENT>457 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">19 </ENT>
                        <ENT>Ferroalloy Manufacturing </ENT>
                        <ENT>424 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20 </ENT>
                        <ENT>Fertilizer Manufacturing </ENT>
                        <ENT>418 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">21 </ENT>
                        <ENT>Glass Manufacturing </ENT>
                        <ENT>426 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="66299"/>
                        <ENT I="01">22 </ENT>
                        <ENT>Grain Mills </ENT>
                        <ENT>406 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">23 </ENT>
                        <ENT>Gum and Wood Chemicals </ENT>
                        <ENT>454 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">24 </ENT>
                        <ENT>Hospitals </ENT>
                        <ENT>460 </ENT>
                        <ENT>(1) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25 </ENT>
                        <ENT>Ink Formulating </ENT>
                        <ENT>447 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">26 </ENT>
                        <ENT>
                            Inorganic Chemicals 
                            <E T="02">[Note 1]</E>
                              
                        </ENT>
                        <ENT>415 </ENT>
                        <ENT>(1) and (3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">27 </ENT>
                        <ENT>Iron and Steel Manufacturing </ENT>
                        <ENT>420 </ENT>
                        <ENT>(1) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">28 </ENT>
                        <ENT>Landfills </ENT>
                        <ENT>445 </ENT>
                        <ENT>(5) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">29 </ENT>
                        <ENT>Leather Tanning and Finishing </ENT>
                        <ENT>425 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">30 </ENT>
                        <ENT>Meat and Poultry Products </ENT>
                        <ENT>432 </ENT>
                        <ENT>(1) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">31 </ENT>
                        <ENT>Metal Finishing </ENT>
                        <ENT>433 </ENT>
                        <ENT>(1) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">32 </ENT>
                        <ENT>Metal Molding and Casting </ENT>
                        <ENT>464 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">33 </ENT>
                        <ENT>Metal Products and Machinery </ENT>
                        <ENT>438 </ENT>
                        <ENT>(1) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">34 </ENT>
                        <ENT>Mineral Mining and Processing </ENT>
                        <ENT>436 </ENT>
                        <ENT>(5) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">35 </ENT>
                        <ENT>Nonferrous Metals Forming and Metal Powders </ENT>
                        <ENT>471 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">36 </ENT>
                        <ENT>Nonferrous Metals Manufacturing </ENT>
                        <ENT>421 </ENT>
                        <ENT>(2) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">37 </ENT>
                        <ENT>Oil and Gas Extraction </ENT>
                        <ENT>435 </ENT>
                        <ENT>(6) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">38 </ENT>
                        <ENT>Ore Mining and Dressing </ENT>
                        <ENT>440 </ENT>
                        <ENT>(2) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">39 </ENT>
                        <ENT>
                            Organic Chemicals, Plastics, and Synthetic Fibers 
                            <E T="02">[Note 1]</E>
                        </ENT>
                        <ENT>414 </ENT>
                        <ENT>(1) and (3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">40 </ENT>
                        <ENT>Paint Formulating </ENT>
                        <ENT>446 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">41 </ENT>
                        <ENT>Paving and Roofing Materials (Tars and Asphalt) </ENT>
                        <ENT>443 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">42 </ENT>
                        <ENT>Pesticide Chemicals </ENT>
                        <ENT>455 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">43 </ENT>
                        <ENT>Petroleum Refining </ENT>
                        <ENT>419 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">44 </ENT>
                        <ENT>Pharmaceutical Manufacturing </ENT>
                        <ENT>439 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">45 </ENT>
                        <ENT>Phosphate Manufacturing </ENT>
                        <ENT>422 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">46 </ENT>
                        <ENT>Photographic </ENT>
                        <ENT>459 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">47 </ENT>
                        <ENT>Plastic Molding and Forming </ENT>
                        <ENT>463 </ENT>
                        <ENT>(5) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">48 </ENT>
                        <ENT>Porcelain Enameling </ENT>
                        <ENT>466 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">49 </ENT>
                        <ENT>Pulp, Paper, and Paperboard </ENT>
                        <ENT>430 </ENT>
                        <ENT>(5) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">50 </ENT>
                        <ENT>Rubber Manufacturing </ENT>
                        <ENT>428 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">51 </ENT>
                        <ENT>Soaps and Detergents Manufacturing </ENT>
                        <ENT>417 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">52 </ENT>
                        <ENT>Steam Electric Power Generating </ENT>
                        <ENT>423 </ENT>
                        <ENT>(1) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">53 </ENT>
                        <ENT>Sugar Processing </ENT>
                        <ENT>409 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">54 </ENT>
                        <ENT>Textile Mills </ENT>
                        <ENT>410 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">55 </ENT>
                        <ENT>Timber Products Processing </ENT>
                        <ENT>429 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">56 </ENT>
                        <ENT>Transportation Equipment Cleaning </ENT>
                        <ENT>442 </ENT>
                        <ENT>(3) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">57 </ENT>
                        <ENT>Waste Combustors </ENT>
                        <ENT>444 </ENT>
                        <ENT>(5) </ENT>
                    </ROW>
                    <TNOTE>* The descriptions of the “Findings” codes are presented immediately prior to this table. </TNOTE>
                    <TNOTE>
                        <E T="02">Note 1:</E>
                         Two codes (“(1)”  and “(3)”) are used for this category as both codes are applicable to this category and do not overlap. The first code (“(1)”) refers to the ongoing effluent guidelines rulemaking for the Chlorinated and Chlorinated Hydrocarbons (CCH) manufacturing sector, which includes facilities currently regulated by the OCPSF and Inorganics effluent guidelines. The second code (“(3)”) indicates that the remainder of the facilities in these two categories does not represent a hazard priority at this time. 
                    </TNOTE>
                </GPOTABLE>
                <HD SOURCE="HD1">VI. EPA's 2010 Evaluation of Categories of Indirect Dischargers Without Categorical Pretreatment Standards To Identify Potential New Categories for Pretreatment Standards</HD>
                <HD SOURCE="HD2">A. EPA's Evaluation of Pass Through and Interference of Toxic and Non-Conventional Pollutants Discharged to POTWs</HD>
                <P>All indirect dischargers are subject to general pretreatment standards (40 CFR part 403), including a prohibition on discharges causing “pass through” or “interference” (See 40 CFR 403.5). All POTWs with approved pretreatment programs must develop local limits to implement the general pretreatment standards. All other POTWs must develop such local limits where they have experienced “pass through” or “interference” and such a violation is likely to recur. There are approximately 1,500 POTWs with approved pretreatment programs and 13,500 small POTWs that are not required to develop and implement pretreatment programs.</P>
                <P>In addition, EPA establishes technology-based national regulations, termed “categorical pretreatment standards,” for categories of industry discharging pollutants to POTWs that may pass through, interfere with or otherwise be incompatible with POTW operations (CWA section 307(b)). Generally, categorical pretreatment standards are designed such that wastewaters from direct and indirect industrial dischargers are subject to similar levels of treatment. EPA has promulgated such pretreatment standards for 35 industrial categories.</P>
                <P>One of the tools traditionally used by EPA in evaluating whether pollutants “pass through” a POTW, is a comparison of the percentage of a pollutant removed by POTWs with the percentage of the pollutant removed by discharging facilities applying BAT. Pretreatment standards for existing sources are technology based and are analogous to BAT effluent limitations guidelines. In most cases, EPA has concluded that a pollutant passes through the POTW when the median percentage removed nationwide by representative POTWs (those meeting secondary treatment requirements) is less than the median percentage removed by facilities complying with BAT effluent limitations guidelines for that pollutant.</P>
                <P>
                    This approach to the definition of “pass through” satisfies two competing objectives set by Congress: (1) That standards for indirect dischargers be equivalent to standards for direct dischargers; and (2) that the treatment capability and performance of POTWs be recognized and taken into account in 
                    <PRTPAGE P="66300"/>
                    regulating the discharge of pollutants from indirect dischargers.
                </P>
                <P>
                    The term “interference” means a discharge which, alone or in conjunction with a discharge or discharges from other sources, both: (1) Inhibits or disrupts the POTW, its treatment processes or operations, or its sludge processes, use or disposal; and (2) therefore is a cause of a violation of any requirement of the POTW's NPDES permit (including an increase in the magnitude or duration of a violation) or of the prevention of sewage sludge use or disposal in compliance with applicable regulations or permits. See 40 CFR 403.3(k). To determine the potential for “interference,” EPA generally evaluates the industrial indirect discharges in terms of: (1) The compatibility of industrial wastewaters and domestic wastewaters (
                    <E T="03">e.g.,</E>
                     type of pollutants discharged in industrial wastewaters compared to pollutants typically found in domestic wastewaters); (2) concentrations of pollutants discharged in industrial wastewaters that might cause interference with the POTW collection system, the POTW treatment system, or biosolids disposal options; and (3) the potential for variable pollutant loadings to cause interference with POTW operations (
                    <E T="03">e.g.,</E>
                     batch discharges or slug loadings from industrial facilities interfering with normal POTW operations).
                </P>
                <P>
                    If EPA determines a category of indirect dischargers causes pass through or interference, EPA would then consider the BAT and BPT factors (including “such other factors as the Administrator deems appropriate”) specified in section 304(b) to determine whether to establish pretreatment standards for these activities. Examples of “such other factors” include a consideration of the magnitude of the hazard posed by the pollutants discharged as measured by: (1) The total annual TWPE discharged by the industrial sector; and (2) the average TWPE discharged among facilities that discharge to POTWs. Additionally, EPA would consider whether other regulatory tools (
                    <E T="03">e.g.,</E>
                     use of local limits under part 403) or voluntary measures would better control the pollutant discharges from this category of indirect dischargers. For example, EPA relied on a similar evaluation of “pass through potential” in its prior decision not to promulgate national categorical pretreatment standards for the Industrial Laundries industry. See 
                    <E T="03">64 FR 45071</E>
                     (August 18, 1999). EPA noted in this 1999 final action that, “While EPA has broad discretion to promulgate such [national categorical pretreatment] standards, EPA retains discretion not to do so where the total pounds removed do not warrant national regulation and there is not a significant concern with pass through and interference at the POTW.” See 
                    <E T="03">64 FR 45077</E>
                     (August 18, 1999).
                </P>
                <HD SOURCE="HD2">B. Hospitals (Part 460) (Health Care Industry Detailed Study of the Management of Unused Pharmaceuticals)</HD>
                <P>Pharmaceutical chemicals have been detected in our nation's waterways, leading to concerns that these compounds may affect aquatic life and possible human health through drinking water sources. As a result of public comments on the Final 2006 Effluent Guidelines Program Plan, EPA initiated a study of unused pharmaceutical disposal practices at health care facilities. The focus of this study was on disposal to water via sewers. EPA studied medical facilities; including, hospitals, hospices, long-term care facilities, health care clinics, physician offices, and veterinary facilities. A standard disposal practice at many health care facilities is to flush unused pharmaceuticals down the toilet or drain.</P>
                <P>
                    Unused pharmaceuticals include leftover medication that is expired, not dispensed, and/or partially used, and residues from delivery devices. During the study, EPA conducted intensive outreach to over 700 stakeholders and evaluated a range of management practices to reduce the generation of unused pharmaceuticals and their disposal down the drain. Based on the information collected through the outreach, EPA has drafted a guidance document, “Best Management Practices for Unused Pharmaceuticals at Health Care Facilities”. The guidance document was made available for a 60 day public review and comment as announced in a 
                    <E T="04">Federal Register</E>
                     Notice, published on September 8, 2010. The draft guidance document was posted on the Agency's Web site.
                </P>
                <P>In summary, the guidance recommends the following practices to prevent or minimize the amount of pharmaceuticals being disposed in water:</P>
                <FP SOURCE="FP-1">—Conduct an inventory of pharmaceuticals and pharmaceutical waste to quantify the amount of medication the facility is disposing of;</FP>
                <FP SOURCE="FP-1">—Reduce pharmaceutical waste by reviewing purchasing practices, use limited dose or unit dose dispensing, replace pharmaceutical samples with vouchers, and perform on-going inventory control and stock rotation;</FP>
                <FP SOURCE="FP-1">—Reuse or donate unused pharmaceuticals when possible; return unused pharmaceuticals to the pharmacy; send unused pharmaceuticals to a reverse distributor for credit and proper disposal in accordance with the facility's state environmental regulations; properly identify and manage hazardous pharmaceutical wastes in accordance with federal and state regulations; use EPA recommended practices to dispose of non-hazardous pharmaceutical waste at the facility;</FP>
                <FP SOURCE="FP-1">—Segregate waste for disposal to ensure regulations are met;</FP>
                <FP SOURCE="FP-1">—Train staff in proper disposal methods.</FP>
                <P>EPA received 89 comments on the proposed guidance on November 8, 2010 and is reviewing suggested changes to the document and working with relevant Federal Agencies to ensure any incorporated comments are consistent with other Federal laws and policies.</P>
                <HD SOURCE="HD2">C. Dental Amalgam</HD>
                <P>In the 2008 final Plan, EPA decided it would not initiate an effluent limitation guideline rulemaking for discharges of dental amalgam from dentists' offices. However, at that time EPA indicated it would examine whether a significant majority of dentists began utilizing amalgam separators and stated that after such examination, EPA may re-evaluate its decision not to initiate an effluent guidelines rulemaking for this sector.</P>
                <P>After assessing the progress made under the Memorandum of Understanding to Reduce Dental Amalgam Discharges (MOU), and other factors, EPA announced, in September 2010, it will initiate a rulemaking to control mercury associated with dental amalgam discharges to sewer systems from dental offices.</P>
                <HD SOURCE="HD3">Background</HD>
                <P>
                    Across the United States, many States and municipal wastewater treatment plants (publicly owned treatment works—POTWs) are working toward the goal of reducing discharges of mercury into sewer collection systems. Many studies have been conducted in an attempt to identify the sources of mercury entering these collection systems. According to the 2002 Mercury Source Control and Pollution Prevention Program Final Report prepared for the National Association of Clean Water Agencies (NACWA), dental offices are the largest source of mercury discharges to POTWs. The American 
                    <PRTPAGE P="66301"/>
                    Dental Association (ADA) estimated in 2003 that up to 50% of mercury entering POTWs was caused by dental offices (see DCN 04698).
                </P>
                <P>EPA estimates there are approximately 160,000 dentists working in 120,000 dental offices that use or remove amalgam in the United States—almost all of which discharge their wastewater exclusively to POTWs. Mercury in dental wastewater originates from waste particles associated with the placement and removal of amalgam fillings. Most dental offices currently use some type of basic filtration system to reduce the amount of mercury solids passing into the sewer system. However, best management practices and the installation of amalgam separators, which generally have a removal efficiency of 95% or greater, can reduce discharges even further. A recent study funded by NACWA (see DCN 04225) concluded that the use of amalgam separators results in reductions in POTW influent concentrations and biosolids mercury concentrations.</P>
                <P>In December, 2008 EPA entered into the MOU with NACWA and ADA. The purpose of the MOU was to estimate the number of dental facilities with amalgam separators installed, establish interim goals for increases in the number of separators voluntarily installed, and conduct outreach to dentists.</P>
                <P>EPA learned from several states that their efforts to increase the number of amalgam separator installations on a voluntary basis were largely unsuccessful. Additionally, several environmental organizations have urged EPA to establish pretreatment standards for dental amalgam. The Quicksilver Caucus commented on the preliminary 2010 Plan requesting that EPA initiate a rulemaking to establish pretreatment standards for discharges of dental amalgam.</P>
                <P>Given the human health and aquatic-life impacts associated with mercury, the level of stakeholder interest, and the availability of a technological solution, EPA decided to initiate rulemaking to develop pretreatment standards for dental mercury to more thoroughly and expeditiously address this water pollution problem.</P>
                <HD SOURCE="HD1">VII. The Final 2010 Effluent Guidelines Program Plan</HD>
                <P>EPA views the effluent guidelines planning process as a mechanism designed to promote regular and transparent priority-setting on the part of the Agency. A plan is ultimately a statement of choices and priorities. These priorities necessarily need to take into account all the other statutory mandates and policy initiatives designed to implement the CWA's goals and the funds appropriated by Congress to execute them.</P>
                <P>By requiring this planning process, culminating in the publication of a plan after public notice and comment, Congress assured that EPA would regularly re-evaluate its policy choices and priorities (including whether to identify an activity for effluent guidelines rulemaking) to account for changed circumstances. Ultimately, however, Congress left the content of the plan to EPA's discretion—befitting the role that effluent guidelines play in the overall structure of the CWA and their relationship to other tools for addressing water pollution.</P>
                <HD SOURCE="HD2">A. EPA's Schedule for Annual Review and Revision of Existing Effluent Guidelines under Section 304(b)</HD>
                <HD SOURCE="HD3">1. Schedule for 2011 and 2012 Annual Reviews Under Section 304(b)</HD>
                <P>As noted in section IV.B, CWA section 304(m)(1)(A) requires EPA to publish a biennial plan that establishes a schedule for the annual review and revision, in accordance with section 304(b), of the effluent guidelines that EPA has promulgated under that section. Today's plan announces EPA's schedule for performing its section 304(b) reviews for 2011 and 2012. The schedule is to coordinate its annual review of existing effluent guidelines under section 304(b) with its publication of preliminary and final Effluent Guidelines Program Plans under CWA section 304(m). In other words, in odd-numbered years, EPA intends to complete its annual review upon publication of the preliminary Effluent Guidelines Program Plan that EPA must publish for public review and comment under CWA section 304(m)(2). In even-numbered years, EPA intends to complete its annual review upon the publication of the final Plan. EPA's 2011 annual review is the review cycle ending upon the publication of the preliminary Plan in 2011 and its 2012 annual review is the review cycle ending upon publication of the 2012 final Plan.</P>
                <HD SOURCE="HD3">2. Schedule for Revision of Effluent Guidelines Promulgated Under Section 304(b)</HD>
                <P>Currently, EPA is engaged in effluent limitations guideline (ELG) rulemakings to revise the following existing guidelines:</P>
                <P>Steam Electric Power Generation—this rulemaking involves the revision of an existing ELG for about 1200 power-generating facilities with a particular focus on about 500 coal-fired power plants. The decision to revise the current effluent guidelines for this industry was largely driven by the high level of toxic-weighted pollutant discharges from coal fired power plants and the expectation that these discharges will increase significantly in the next few years as new air pollution controls are installed. EPA is under a consent decree obligation to issue a final rule for this industry in 2014.</P>
                <P>• Chlorine and Chlorinated Hydrocarbons Manufacturing—EPA is currently conducting a rulemaking to potentially revise existing effluent guidelines and pretreatment standards for the following categories: Organic Chemicals, Plastics and Synthetic Fibers (OCPSF) and Inorganic Chemicals (to address discharges from Vinyl Chloride and Chlor-Alkali facilities identified for effluent guidelines rulemaking in the final 2004 Plan, now termed the “Chlorine and Chlorinated Hydrocarbon (CCH) manufacturing” rulemaking). EPA previously indicated it would conduct an industry survey for this effluent guidelines rulemaking (April 18, 2006; 71 FR 19887). EPA is considering its next steps for this survey and the rulemaking as it reviews data from a voluntary industry monitoring program. EPA worked with industry to develop the extensive monitoring program to better understand the category's dioxin discharges.</P>
                <P>In addition, EPA is today announcing initiation of an effluent limitations guideline (ELG) rulemaking to revise the following existing guidelines:</P>
                <P>• Oil and Gas Extraction—As explained in Section V.B.2, EPA is initiating a rulemaking for Coalbed Methane Extraction, a currently unregulated subcategory of the Oil and Gas Extraction Point Source Category. Because of concern over high TDS levels in the wastewater for Coalbed, availability of treatment technologies, and the fact that Coalbed Methane production will continue to grow, EPA believes the initiation of a rulemaking to address direct discharges to surface waters and discharges to POTWs is appropriate.</P>
                <HD SOURCE="HD2">B. Identification of Point Source Categories Under CWA Section 304(m)(1)(B)</HD>
                <P>
                    The Effluent Guidelines Program Plan must identify categories of sources discharging non-trivial amounts of toxic or non-conventional pollutants for which EPA has not published effluent limitations guidelines under section 304(b)(2) or new source performance standards NSPS) under section 306. See CWA section 304(m)(1)(B). The Plan 
                    <PRTPAGE P="66302"/>
                    must also establish a schedule for the promulgation of effluent guidelines for the categories identified under section 304(m)(1)(B) not later than three years after such identification. See CWA section 304(m)(1)(C). EPA is currently taking the following actions on new industry categories:
                </P>
                <P>• Airport De-icing—This final ELG rulemaking addresses the environmental impact of aircraft and airfield deicing fluid on the environment at the about 200 airports in this country that conduct deicing operations. This rule is complicated by the shared responsibility for deicing operations between the airports and the airlines that use them. EPA currently plans to issue a final rule for this category in 2011.</P>
                <P>• Drinking Water Treatment Industry—EPA is not at this time continuing its effluent guidelines rulemaking for the Drinking Water Treatment industry. In the 2004 Plan, EPA announced that it would begin development of a regulation to control the pollutants discharged from drinking water treatment plants. See 69 FR 53720 (September 2, 2004). Based on a preliminary study and on public comments, EPA was interested in the potential volume of discharges associated with drinking water facilities. The preliminary data were not conclusive, and the Agency proceeded with additional study and analysis of treatability, including an industry survey. After considering extensive information about the industry, its treatment residuals, wastewater treatment options, and discharge characteristics, and after considering other priorities, EPA has suspended work on this rulemaking.</P>
                <P>The ELG Program is also developing the cooling water intake existing facility rule—Under section 316(b) of the CWA, EPA plans to issue a final rule in 2012 addressing the withdrawal of trillions of aquatic organisms from waters of the U.S. by about 1260 power plants and manufacturing facilities which withdraw water for cooling purposes.</P>
                <P>Also for the 2010 Plan, EPA is issuing the detailed study report for the coalbed methane industry and is issuing the preliminary study report for the Ore Mining and Dressing industry, and will be taking no further action on this industry at this time. EPA initiated a preliminary study of cellulose manufacturers in the Plastic Molding and Forming category (part 463) due, in part, to high carbon disulfide discharges which were revealed during the 2010 review.</P>
                <P>Finally, EPA interprets section 304(m)(1)(B) to give EPA the discretion to identify in the Plan only those potential new categories for which an effluent guidelines rulemaking may be an appropriate tool for controlling discharges. Therefore, EPA does not identify in the Plan all potential new categories discharging toxic and non-conventional pollutants. Rather, EPA identifies only those potential new categories for which it believes that effluent guidelines may be appropriate, taking into account Agency priorities, resources and the full range of other CWA tools available for addressing industrial discharges. In this Plan, EPA is not identifying for rulemaking any new categories discharging toxic and non-conventional pollutants.</P>
                <P>EPA is continuously investigating and solicits comment on how to improve its analyses (see section IX. Request for Comment and Information for the 2011 Annual Reviews).</P>
                <HD SOURCE="HD2">C. Identification of Guidelines for Pretreatment of Pollutants under CWA Section 304(g)(1) and 307(b)(1)</HD>
                <P>EPA has decided to initiate rulemaking for two industries to address their indirect industrial discharges to POTWs. This includes the indirect discharge of dental amalgam from dental offices and wastewater from shale gas extraction to publicly owned treatment works (POTWs) that may cause pass-through, interfere with, or are otherwise incompatible with POTWs.</P>
                <P>With regard to dental amalgam discharges from dental offices, EPA was asked by some states and environmental groups to revisit its 2008 decision not to initiate rulemaking for this industry. Dental amalgam contains mercury, which is a concern to human health because mercury is a persistent, bioaccumulative toxic element. EPA estimates that dentists discharge approximately 3.7 tons of mercury each year to publicly owned treatment works. In addition, EPA has not seen significant increases in the installation of amalgam separators under current voluntary efforts. Consequently, EPA has decided to initiate rulemaking which will reduce mercury discharges from dental facilities more completely, and in a more predictable timeframe than has been demonstrated through voluntary means alone.</P>
                <P>EPA also is initiating rulemaking for shale gas extraction, another subcategory of the Oil and Gas Extraction Point Source Category, which is now subject to effluent guidelines under this Category but not to applicable pretreatment standards. Because of concern over high TDS levels in the wastewater for shale gas extraction, availability of treatment technologies, and the fact that shale gas extraction production will continue to grow, EPA believes the initiation of a rulemaking to address discharges to POTWs is appropriate.</P>
                <HD SOURCE="HD2">D. Current Rulemakings</HD>
                <HD SOURCE="HD3">Airport Deicing and Steam Electric Power Generation:</HD>
                <HD SOURCE="HD3">Schedules</HD>
                <FP SOURCE="FP-2">Airport Deicing:</FP>
                <FP SOURCE="FP1-2">—Final ELG Rule—Fall 2011</FP>
                <FP SOURCE="FP-2">Steam Electric Power Generation:</FP>
                <FP SOURCE="FP1-2">—Proposed Rule—July 2012</FP>
                <FP SOURCE="FP1-2">—Final Rule—January 2014</FP>
                <HD SOURCE="HD2">E. New Rulemakings</HD>
                <HD SOURCE="HD3">Dental Amalgam</HD>
                <FP SOURCE="FP-2">Schedule to Develop the Regulation for Dental Amalgam:</FP>
                <FP SOURCE="FP1-2">—Proposed Rule—October 2011</FP>
                <FP SOURCE="FP1-2">—Final Rule—October 2012</FP>
                <HD SOURCE="HD3">Coalbed Methane Extraction</HD>
                <FP SOURCE="FP-2">Schedule to Develop the Regulation for Coalbed Methane Extraction:</FP>
                <FP SOURCE="FP1-2">—Proposed Rule—2013</FP>
                <HD SOURCE="HD3">Shale Gas Extraction</HD>
                <FP SOURCE="FP-2">Schedule to Develop the Regulation for Shale Gas Extraction:</FP>
                <FP SOURCE="FP1-2">—Proposed Rule—2014</FP>
                <P>These Agency decisions, announcements and the studies described previously fulfill EPA's obligations to annually review both existing effluent limitations guidelines for direct dischargers and existing pretreatment standards for indirect dischargers under CWA sections 304(b) and (g), as well as other review requirements under CWA section 301(d) and 307(b).</P>
                <HD SOURCE="HD1">VIII. EPA's 2011 Annual Review of Existing Effluent Guidelines and Pretreatment Standards Under CWA Sections 301(d), 304(b), 304(g), 304(m) and 307(b)</HD>
                <P>This notice also provides EPA's preliminary thoughts concerning its 2011 annual reviews under CWA sections 304(b) and 304(g) as well as its reviews under 301(d) and 307(b) and solicits comments, data and information to assist EPA in performing these reviews.</P>
                <HD SOURCE="HD2">A. Schedule for the 2011 Annual Reviews Under Section 304(b)</HD>
                <P>
                    As noted in section IV.B, CWA section 304(m)(1)(A) requires EPA to publish a Plan every two years that establishes a schedule for the annual review and revision, in accordance with section 304(b), of the effluent guidelines that EPA has promulgated under that 
                    <PRTPAGE P="66303"/>
                    section. This final 2010 Plan announces EPA's schedule for performing its section 304(b) reviews in 2011.
                </P>
                <P>The schedule is as follows: EPA will coordinate its annual review of existing effluent guidelines with its publication of the preliminary and final Plans under CWA section 304(m). In other words, in odd-numbered years, EPA intends to complete its annual review upon publication of the preliminary Plan that EPA must publish for public review and comment under CWA section 304(m)(2). In even-numbered years, EPA intends to complete its annual review upon the publication of the final Plan. EPA's 2010 annual review is the review cycle ending upon the publication of this final 2010 Plan.</P>
                <P>
                    EPA is coordinating its annual reviews with publication of Plans under section 304(m) for several reasons. First, the annual review is inextricably linked to the planning effort, because the results of each annual review can inform the content of the preliminary and final Plans, 
                    <E T="03">e.g.,</E>
                     by identifying candidates for effluent guidelines revision for which EPA can schedule rulemaking in the Plan, or by calling to EPA's attention point source categories for which EPA has not promulgated effluent guidelines. Second, even though not required to do so under either section 304(b) or section 304(m), EPA believes that the public interest is served by periodically presenting to the public a description of each annual review (including the review process employed) and the results of the review. Doing so at the same time EPA publishes preliminary and final plans makes both processes more transparent. Third, by requiring EPA to regularly review all existing effluent guidelines, Congress appears to have intended that each successive review would build upon the results of earlier reviews. Therefore, by describing the 2010 annual review along with the final 2010 final Plan, EPA hopes to gather and receive data and information that will inform its reviews for 2011 and 2012 and the final 2012 Plan.
                </P>
                <HD SOURCE="HD1">IX. Request for Comment and Information for the 2011 Annual Reviews</HD>
                <HD SOURCE="HD2">A. EPA Requests Information on</HD>
                <HD SOURCE="HD3">1. Data Sources and Methodologies</HD>
                <P>EPA solicits comments on whether EPA used the correct evaluation factors, criteria, and data sources in conducting its annual review and developing this final Plan. EPA also solicits comment on other data sources EPA can use in its annual reviews and biennial planning process. Please see the docket for a more detailed discussion of EPA's analysis supporting the reviews in this notice (see DCN 07320).</P>
                <P>EPA is also soliciting comments on ways to enhance its Plan analysis. In particular: Are there new or additional factors that should be brought to bear for screening existing industries for revisions to their current guidelines? Are there approaches that could be used to better identify new industries that currently do not have guidelines that should? EPA is interested in receiving comment on all aspects of its current methodology.</P>
                <HD SOURCE="HD3">2. Climate Change and Water Efficiency</HD>
                <P>EPA solicits comments, and data and information on whether the actions described under this Plan will have effects on water conservation or on climate change. In particular, will certain technologies or actions help to conserve water, and thereby energy and thus reduce the consumption of fossil fuels, or will the actions envisioned by this plan waste water and/or energy resources. Likewise, will the actions and potential industry changes contemplated by this Plan result in greater emission of green house gases, or are there opportunities for industry to reduce green house gas emissions.</P>
                <HD SOURCE="HD3">3. BPJ Permit-Based Support</HD>
                <P>
                    EPA solicits comments on whether, and if so, how the Agency should provide EPA Regions and States with permit-based support instead of revising effluent guidelines (
                    <E T="03">e.g.,</E>
                     when the vast majority of the hazard is associated with one or a few facilities). EPA solicits comment on categories for which the Agency should provide permit-based support.
                </P>
                <HD SOURCE="HD3">4. Implementation Issues Related to Existing Effluent Guidelines and Pretreatment Standards</HD>
                <P>As a factor in its decision-making, EPA considers opportunities to eliminate inefficiencies or impediments to pollution prevention or technological innovation, or opportunities to promote innovative approaches such as water quality trading, including within-plant trading. Consequently, EPA solicits comment on implementation issues related to existing effluent guidelines and pretreatment standards.</P>
                <HD SOURCE="HD3">5. EPA's Evaluation of Categories of Indirect Dischargers Without Categorical Pretreatment Standards To Identify Potential New Categories for Pretreatment Standards</HD>
                <P>
                    EPA solicits comments on its evaluation of categories of indirect dischargers without categorical pretreatment standards. Specifically, EPA solicits wastewater characterization data (
                    <E T="03">e.g.,</E>
                     wastewater volumes, concentrations of discharged pollutants), current examples of pollution prevention, treatment technologies, and local limits for all industries without pretreatment standards. EPA also solicits comment on whether there are industrial sectors discharging pollutants that cause interference issues that cannot be adequately controlled through the general pretreatment standards. Finally, EPA solicits comment on how better to access and aggregate discharge data reported to local pretreatment programs. Currently, pollutant discharge data are collected by the local pretreatment program to demonstrate compliance with pretreatment standards and local limits but are not typically electronically transmitted to the States or EPA Regions.
                </P>
                <HD SOURCE="HD3">6. Data and Information on Discharges of Pollutants From Waste Combustors</HD>
                <P>EPA solicits data and information on discharges of wastewater from waste combustors. DMR data suggest the consistent discharge of metals and possible discharge of pesticides from waste combustors. EPA's analysis for the 2010 ELG Final Plan shows that pesticides are discharged at concentrations below limits of detection. EPA is requesting information on waste combustors metals and pesticide discharges, to determine if they are present at concentrations below treatable levels.</P>
                <HD SOURCE="HD3">7. Data and Information on Discharges of Pollutants From Shale Gas Extraction</HD>
                <P>EPA solicits data and information on the pollutants generated by the Shale Gas extraction industry. In particular EPA is soliciting data and information on the type of pollutants in shale gas wastewaters, including the type and toxicity of additives, the volumes of flowback and concentrations of the pollutants in the flowback, the fate and transport of pollutants to ground waters, and data and information on the pass-through of pollutants at publicly owned treatment works (POTWs). EPA also solicits documented impacts of these pollutants on aquatic life and human health.</P>
                <HD SOURCE="HD3">8. Data and Information on Discharges of Nanosilver From Industrial Manufacturing</HD>
                <P>
                    Nanosilver is becoming a more commonly used substance in industrial materials and commercial products as an active pesticide ingredient. In some uses, fabric is impregnated with 
                    <PRTPAGE P="66304"/>
                    nanosilver as an anti-microbial during manufacturing and nanosilver discharges may result. In other applications, nanosilver is used as a preservative in textile products which could also lead to nanosilver discharges. Other products, such as household washing machines, are being manufactured with the washer drum coated with nanosilver polymers to kill bacteria during clothes laundering. Since many of the nanosilver applications have the potential to create a source of silver in wastewater discharges from industries using nanosilver in the manufacture of products, or use of products containing nanosilver, EPA is interested in gathering as much information as possible on the fate, transport and effects of nanosilver on the aquatic environment and human health.
                </P>
                <P>EPA is soliciting data and information on the manufacture, use, and environmental release of silver materials, including nanosilver. EPA is requesting information on the manufacturing of silver materials, including:</P>
                <FP SOURCE="FP-1">—Raw silver products, such as colloidal nanosilver;</FP>
                <FP SOURCE="FP-1">—Intermediates such as polymers or fibers embedded with silver, nanosilver, or silver compounds; and</FP>
                <FP SOURCE="FP-1">—End products, such as silver-embedded textile and plastic products, or appliances with nanosilver coated surfaces.</FP>
                <SIG>
                    <DATED>Dated: October 20, 2011.</DATED>
                    <NAME>Nancy K. Stoner,</NAME>
                    <TITLE>Acting Assistant Administrator for Water.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27742 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL MARITIME COMMISSION</AGENCY>
                <SUBJECT>Notice of Agreements Filed</SUBJECT>
                <P>
                    The Commission hereby gives notice of the filing of the following agreements under the Shipping Act of 1984. Interested parties may submit comments on the agreements to the Secretary, Federal Maritime Commission, Washington, DC 20573, within ten days of the date this notice appears in the 
                    <E T="04">Federal Register</E>
                    . Copies of the agreements are available through the Commission's Web site (
                    <E T="03">http://www.fmc.gov</E>
                    ) or by contacting the Office of Agreements at (202) 523-5793 or 
                    <E T="03">tradeanalysis@fmc.gov.</E>
                </P>
                <P>
                    <E T="03">Agreement No.:</E>
                     012032-008.
                </P>
                <P>
                    <E T="03">Title:</E>
                     CMA CGM/MSC/Maersk Line North and Central China-U.S. Pacific Coast Two-Loop Space Charter, Sailing and Cooperative Working Agreement.
                </P>
                <P>
                    <E T="03">Parties:</E>
                     A.P. Moller-Maersk A/S, CMA CGM S.A., and Mediterranean Shipping Company S.A.
                </P>
                <P>
                    <E T="03">Filing Party:</E>
                     Wayne R. Rohde, Esq.; Cozen O'Connor; 1627 I Street, NW., Suite 1100, Washington, DC 20006.
                </P>
                <P>
                    <E T="03">Synopsis:</E>
                     The Amendment provides for a further slot exchange between Maersk Line and MSC with corresponding changes in the Agreement and delays the introduction of a service loop.
                </P>
                <P>
                    <E T="03">Agreement No.:</E>
                     012142.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Vessel Sharing Agreement for Transpacific Service between Hainan P O Shipping Co., Ltd. and T.S. Lines.
                </P>
                <P>
                    <E T="03">Parties:</E>
                     Hainan P O Shipping Co., Ltd. and T.S. Lines Ltd.
                </P>
                <P>
                    <E T="03">Filing Party:</E>
                     Neal A. Mayer, Esq.; Hoppel, Mayer, &amp; Coleman; 1050 Connecticut Avenue, NW., 10th Floor, Washington, DC 20036.
                </P>
                <P>
                    <E T="03">Synopsis:</E>
                     The agreement authorizes the parties to share vessel space in the trade between U.S. West Coast ports and ports in China and Korea.
                </P>
                <SIG>
                    <P>By Order of the Federal Maritime Commission.</P>
                    <DATED>Dated: October 21, 2011.</DATED>
                    <NAME>Karen V. Gregory, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27706 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6730-01-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.
                </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 November 21, 2011.</P>
                <P>A. Federal Reserve Bank of Atlanta (Chapelle Davis, Assistant Vice President) 1000 Peachtree Street, NE., Atlanta, Georgia 30309:</P>
                <P>
                    1. 
                    <E T="03">Raymond James Financial, Inc.,</E>
                     St. Petersburg, Florida; to become a bank holding company by acquiring 100 percent of the voting shares of Raymond James Bank, FSB, St. Petersburg, Florida, to be named Raymond James Bank, N.A., upon its conversion to a national bank.
                </P>
                <P>B. Federal Reserve Bank of Kansas City (Dennis Denney, Assistant Vice President) 1 Memorial Drive, Kansas City, Missouri 64198-0001:</P>
                <P>
                    1. 
                    <E T="03">Bluechip Bancshares,</E>
                     LLC, Oklahoma City, Oklahoma; to become a bank holding company by acquiring 100 percent of the voting shares of Elmore City Bancshares, Inc., and First State Bank, both in Elmore City, Oklahoma.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System.</P>
                    <DATED>Dated: October 21, 2011.</DATED>
                    <NAME>Robert deV. Frierson,</NAME>
                    <TITLE>Deputy Secretary of the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27675 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL RETIREMENT THRIFT INVESTMENT BOARD</AGENCY>
                <SUBJECT>Employee Thrift Advisory Council</SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">TIME AND DATE: </HD>
                    <P>2 p.m. (EST), November 15, 2011.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PLACE: </HD>
                    <P>4th Floor, Conference Room, 1250 H Street, NW., Washington, DC.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">STATUS: </HD>
                    <P>Open.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">MATTERS TO BE CONSIDERED:</HD>
                    <P SOURCE="NPAR">1. Approval of the minutes of the April 18, 2011 meeting.</P>
                    <P>2. Report of the Executive Director on Thrift Savings Plan status:</P>
                    <P>(a) Updated TSP statistics.</P>
                    <P>(b) Update on implementation of Roth TSP accounts.</P>
                    <P>3. Legislation:</P>
                    <P>(a) Update on Board Member nominations.</P>
                    <P>(b) Nonappropriated Fund status.</P>
                    <P>(c) 3-year statute of limitations for claims against the TSP.</P>
                    <P>(d) IRS Levy.</P>
                    <P>
                        (e) TSP contributions from terminal Annual Leave.
                        <PRTPAGE P="66305"/>
                    </P>
                    <P>4. New Business.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION: </HD>
                    <P> Thomas J. Trabucco, Director, Office of External Affairs, (202) 942-1640.</P>
                </PREAMHD>
                <SIG>
                    <DATED>Dated: October 24, 2011.</DATED>
                    <NAME>Thomas K. Emswiler,</NAME>
                    <TITLE>General Counsel, Federal Retirement Thrift Investment Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27886 Filed 10-24-11; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 6760-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <DEPDOC>[Document Identifier: OS-0990-New; 30-Day Notice] </DEPDOC>
                <SUBJECT>Agency Information Collection Request, 30-Day Public Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Secretary, HHS. </P>
                    <P>In compliance with the requirement of section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995, the Office of the Secretary (OS), Department of Health and Human Services, is publishing the following summary of a proposed collection for public comment. Interested persons are invited to send comments regarding this burden estimate or any other aspect of this collection of information, including any of the following subjects: (1) The necessity and utility of the proposed information collection for the proper performance of the agency's functions; (2) the accuracy of the estimated burden; (3) ways to enhance the quality, utility, and clarity of the information to be collected; and (4) the use of automated collection techniques or other forms of information technology to minimize the information collection burden. </P>
                    <P>
                        To obtain copies of the supporting statement and any related forms for the proposed paperwork collections referenced above, e-mail your request, including your address, phone number, OMB number, and OS document identifier, to 
                        <E T="03">Sherette.funncoleman@hhs.gov,</E>
                         or call the Reports Clearance Office on (202) 690-5683. Send written comments and recommendations for the proposed information collections within 30 days of this notice directly to the OS OMB Desk Officer; faxed to OMB at 202-395-5806. 
                    </P>
                    <P>
                        <E T="03">Proposed Project:</E>
                         Multisite Evaluation of the 
                        <E T="03">In Community Spirit</E>
                         Program—Prevention of HIV/AIDS for Native/American Indian and Alaska Native Women Living in Rural and Frontier Indian Country (NEW)—OMB No. 0990-NEW—Office on Women's Health (OWH). 
                    </P>
                    <P>
                        <E T="03">Abstract:</E>
                         The Office on Women's Health (OWH), within the Office of the Assistant Secretary for Health, will conduct the Multisite Evaluation of the 
                        <E T="03">In Community Spirit</E>
                         Program—Prevention of HIV/AIDS for Native/American Indian and Alaska Native (AI/AN) Women Living in Rural and Frontier Indian Country (
                        <E T="03">In Community Spirit</E>
                         Program). The 
                        <E T="03">In Community Spirit</E>
                         Program is an initiative comprising three types of program components being implemented with women in AI/AN communities for HIV prevention: (1) Community awareness, (2) capacity building, and (3) prevention education. The multisite evaluation will provide data on the content and context of programs and the outcomes of program activities on participant knowledge and behavior related to sexual health. 
                    </P>
                    <P>The multisite evaluation is comprised of two main activities across three program components: (1) Surveys and (2) key informant interviews. There are two versions of key informant interviews: baseline and follow-up. There are also two versions of the survey: (1) Community Awareness Version for administration with women targeted through the community awareness activities and (2) Prevention Education Version to be administered to women who receive prevention education through the program. </P>
                    <P>The average annual respondent burden is estimated below. The estimate reflects the average annual number of respondents, the average annual number of responses, the time it will take for each response, and the average annual burden across 3 years of OMB clearance, which includes 2 years of data collection. </P>
                </AGY>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s30,r30,12,11.1,12,12">
                    <TTITLE>Estimated Annualized Burden Table </TTITLE>
                    <BOXHD>
                        <CHED H="1">Form </CHED>
                        <CHED H="1">Type of respondent </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents </LI>
                        </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>responses per </LI>
                            <LI>respondent per year </LI>
                        </CHED>
                        <CHED H="1">Average burden per response (hrs) </CHED>
                        <CHED H="1">Total burden hours </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Key Informant Interviews </ENT>
                        <ENT>Agency Provider (Administrator) </ENT>
                        <ENT>6 </ENT>
                        <ENT>1 </ENT>
                        <ENT>45/60 </ENT>
                        <ENT>5 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Key Informant Interviews </ENT>
                        <ENT>Agency Staff (Health Educators and Support Workers) </ENT>
                        <ENT>24 </ENT>
                        <ENT>1 </ENT>
                        <ENT>45/60 </ENT>
                        <ENT>18 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HEAL Survey—Community Awareness </ENT>
                        <ENT>Community Member </ENT>
                        <ENT>900 </ENT>
                        <ENT>0.5 </ENT>
                        <ENT>15/60 </ENT>
                        <ENT>113 </ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">HEAL Survey—Prevention Education </ENT>
                        <ENT>Community Member </ENT>
                        <ENT>1200 </ENT>
                        <ENT>1.5 </ENT>
                        <ENT>15/60 </ENT>
                        <ENT>450 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT/>
                        <ENT>2130 </ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>586 </ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <NAME>Mary Forbes, </NAME>
                    <TITLE>Office of the Secretary, Paperwork Reduction Act Clearance Officer. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27733 Filed 10-25-11; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4150-33-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <DEPDOC>[Document Identifier OS-0990-New; 30-day notice] </DEPDOC>
                <SUBJECT>Agency Information Collection Request, 30-Day Public Comment Request </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Secretary, HHS. </P>
                </AGY>
                <P>
                    In compliance with the requirement of section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995, the Office of the Secretary (OS), Department of Health and Human Services, is publishing the following summary of a proposed collection for public comment. Interested persons are invited to send comments regarding this burden estimate or any other aspect of this collection of information, including any of the following subjects: (1) The necessity and utility of the proposed information collection for the proper performance of the agency's functions; (2) the accuracy of the estimated 
                    <PRTPAGE P="66306"/>
                    burden; (3) ways to enhance the quality, utility, and clarity of the information to be collected; and (4) the use of automated collection techniques or other forms of information technology to minimize the information collection burden. 
                </P>
                <P>
                    To obtain copies of the supporting statement and any related forms for the proposed paperwork collections referenced above, e-mail your request, including your address, phone number, OMB number, and OS document identifier, to 
                    <E T="03">Sherette.funncoleman@hhs.gov,</E>
                     or call the Reports Clearance Office on (202) 690-5683. Send written comments and recommendations for the proposed information collections within 30 days of this notice directly to the OS OMB Desk Officer; faxed to OMB at 202-395-5806. 
                </P>
                <P>
                    <E T="03">Proposed Project:</E>
                     Descriptive information of solutions provided to the Federal government in response to Challenge and Competition solicitations posted on Challenge.gov—OMB No. 0990-NEW—Immediate Office of the Secretary. 
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This request is to seek generic clearance for the collection of routine information requested of responders to solicitations the Federal government makes during the issuance of challenges and competitions posted on the General Service Administration (GSA)'s Challenge.gov Web site. Since passage of the America COMPETES Act of 2011, challenge competitions are increasingly being used by Federal agencies to solve complex problems and obtain innovative solutions. In this role, the Federal government places a description of a problem and parameters of the solution on the Challenge.gov Web site. The solutions are evaluated by the submitting agency and typically prizes (monetary and non-monetary) are awarded to the winning entries. 
                </P>
                <P>This clearance applies to challenges posted on Challenge.gov which uses a common platform for the solicitation of challenges from the public. Each agency designs the criteria for its solicitations based on the goals of the challenge and the specific needs of the agency. There is no standard submission format for solution providers to follow. We anticipate that approximately 100 challenges would be issued each year by HHS, with an average of 15 submissions to each challenge solicitation. It is expected that other federal agencies will issue a similar number of challenges. There is no set schedule for the issuance of challenges; they are developed and issued on an “as needs” basis in response to issues the federal agency wishes to solve. The respondents to the challenges, who are participating voluntarily, are unlikely to reply to more than one or several of the challenges.</P>
                <P>Although in recent memoranda the GSA and Office of Management and Budget (OMB) described circumstances whereby OMB approval of a PRA request is not needed, program officials at HHS have identified several sets of information that will typically need to be requested of solution providers to enable the solutions to be adequately evaluated by the federal agency issuing the challenge.</P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s30,r30,12,12,12,11.1">
                    <TTITLE>Estimated Annualized Burden Table</TTITLE>
                    <BOXHD>
                        <CHED H="1">Forms</CHED>
                        <CHED H="1">Type of respondent</CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>responses per </LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Average 
                            <LI>burden </LI>
                            <LI>(in hours) </LI>
                            <LI>per response</LI>
                        </CHED>
                        <CHED H="1">
                            Total burden 
                            <LI>hours</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Challenge Template A</ENT>
                        <ENT>Individuals or Households</ENT>
                        <ENT>500</ENT>
                        <ENT>1</ENT>
                        <ENT>20/60</ENT>
                        <ENT>166.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Challenge Template A</ENT>
                        <ENT>Organizations</ENT>
                        <ENT>500</ENT>
                        <ENT>1</ENT>
                        <ENT>20/60</ENT>
                        <ENT>166.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Challenge Template A</ENT>
                        <ENT>Businesses</ENT>
                        <ENT>500</ENT>
                        <ENT>1</ENT>
                        <ENT>20/60</ENT>
                        <ENT>166.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Challenge Template A</ENT>
                        <ENT>State, territory, tribal or local governments</ENT>
                        <ENT>30</ENT>
                        <ENT>1</ENT>
                        <ENT>20/60</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">Challenge Template A</ENT>
                        <ENT>Federal government</ENT>
                        <ENT>30</ENT>
                        <ENT>1</ENT>
                        <ENT>20/60</ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT>1560</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>519.8</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <NAME>Mary Forbes,</NAME>
                    <TITLE>Office of the Secretary, Paperwork Reduction Act Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27730 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4150-03-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBJECT>Announcement of Requirements and Registration for Leading Health Indicators App Challenge</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Health and Human Services, Office of the Secretary, Office of the Assistant Secretary for Health, Office of Disease Prevention and Health Promotion.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> 15 U.S.C. 3719.</P>
                </AUTH>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>October 31, 2011 marks the national release of the Healthy People 2020 leading health indicators (LHIs). The LHIs were developed to communicate high-priority health issues to the public, and actions that can be taken to address them. The Office of Disease Prevention and Health Promotion, in partnership with Health 2.0 and the Office of the National Coordinator of Health IT, is launching an LHI App Challenge to encourage teams of developers and health professionals to build an application that addresses one or more LHI topics on a community level. The overall purpose of the Challenge is to provide public health practitioners, business, elected officials, clinicians and the public with applications to help achieve national priority health goals.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective on October 31, 2011. Important dates include the following:</P>
                    <P>
                        <E T="03">October 31, 2011:</E>
                         Announcement of the LHI App Challenge at the 139th Annual APHA Meeting.
                    </P>
                    <P>
                        <E T="03">March 16, 2012:</E>
                         Deadline for Submissions.
                    </P>
                    <P>
                        <E T="03">April 10, 2012:</E>
                         Winners will be announced during the 2012 Health Promotion Summit in Washington, DC.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Registration opens on challenge.gov and 
                        <E T="03">http://www:health2challenge.org.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Silje Lier, MPH, Communication and eHealth Service Fellow, Office of Disease Prevention and Health Promotion, 
                        <E T="03">Silje.Lier@hhs.gov,</E>
                         240-453-6113.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Subject of Challenge Competition:</E>
                     Leading Health Indicators App Challenge.
                </P>
                <P>
                    <E T="03">Eligibility Rules for Participating in the Competition:</E>
                    <PRTPAGE P="66307"/>
                </P>
                <P>To be eligible to win a prize under this challenge, an individual or entity—</P>
                <P>(1) Shall have registered to participate in the competition under the rules promulgated by HHS;</P>
                <P>(2) Shall have complied with all the requirements under this section;</P>
                <P>(3) In the case of a private entity, shall be incorporated in and maintain a primary place of business in the United States, and in the case of an individual, whether participating singly or in a group, shall be a citizen or permanent resident of the United States; and</P>
                <P>(4) May not be a Federal entity or Federal employee acting within the scope of their employment.</P>
                <P>(5) Shall not be an HHS employee working on their applications or submissions during assigned duty hours.</P>
                <P>(6) Shall not be in the reporting chain of Dr. Howard Koh in the Office of the Assistant Secretary for Health.</P>
                <P>(7) Federal grantees may not use Federal funds to develop COMPETES Act challenge applications unless consistent with the purpose of their grant award.</P>
                <P>(8) Federal contractors may not use Federal funds from a contract to develop COMPETES Act challenge applications or to fund efforts in support of a COMPETES Act challenge submission.</P>
                <P>An individual or entity shall not be deemed ineligible because the individual or entity used Federal facilities or consulted with Federal employees during a competition if the facilities and employees are made available to all individuals and entities participating in the competition on an equitable basis.</P>
                <P>Challenge participants will be expected to sign a liability release as part of the contest registration process. The liability release will use the following language:</P>
                <EXTRACT>
                    <P>By participating in this competition, I agree to assume any and all risks and waive claims against the Federal Government and its related entities, except in the case of willful misconduct, for any injury, death, damage, or loss of property, revenue, or profits, whether direct, indirect, or consequential, arising from my participation in this prize contest, whether the injury, death, damage, or loss arises through negligence or otherwise.</P>
                </EXTRACT>
                <P>
                    <E T="03">Registration Process for Participants:</E>
                </P>
                <P>
                    Participants can register for the Challenge by visiting 
                    <E T="03">http://www.health2challenge.org</E>
                     or 
                    <E T="03">http://www.challenge.gov.</E>
                     Registration will be open from October 31, 2011 to March 15, 2012.
                </P>
                <P>
                    <E T="03">Amount of the Prize:</E>
                </P>
                <P>Challenge winners will be provided monetary cash prizes, totaling $15,000. The first place winner will receive $10,000. The second place winner will receive $3,000. And the third place winner will receive $2,000. Winners will be invited to demonstrate their apps at the 2012 Health Promotion Summit in Washington, DC.</P>
                <P>
                    <E T="03">Basis Upon Which Winner Will be Selected:</E>
                </P>
                <P>Challenge submissions will be reviewed by a panel of judges with relevant expertise in health IT and in Healthy People 2020. Winners will be selected based on the following criteria:</P>
                <P>(1) Easy Access and Navigation.</P>
                <P>(2) Platform Neutrality.</P>
                <P>(3) User Appeal.</P>
                <P>(4) Innovative Design.</P>
                <P>(5) Broad Applicability.</P>
                <P>(6) Integration of Health Data.</P>
                <P>(7) Evidence of Co-Design and Collaboration.</P>
                <P>Judges will also award bonus points to submissions that align with Section 508 of the Rehabilitation Act of 1973, and ones that incorporate plain language and health literacy principles.</P>
                <P>
                    <E T="03">Award Approving Official:</E>
                     Carter Blakey, Acting Director, Office of Disease Prevention and Health Promotion.
                </P>
                <P>
                    <E T="03">Additional Information:</E>
                     The Healthy People Web site, 
                    <E T="03">http://www.HealthyPeople.gov,</E>
                     contains objectives, targets, and baseline data for all of the Healthy People 2020 topic areas. From 
                    <E T="03">healthypeople.gov,</E>
                     challenge participants will also be able to access the corresponding leading health indicators from the HHS Health Indicators Warehouse.
                </P>
                <SIG>
                    <DATED>Dated: October 18, 2011.</DATED>
                    <NAME>Carter Blakey,</NAME>
                    <TITLE>Acting Director, Office of Disease Prevention and Health Promotion.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27681 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4150-32-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Agency for Healthcare Research and Quality</SUBAGY>
                <SUBJECT>Scientific Information Request on Phototherapy for Treatment of Chronic Plaque Psoriasis</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Agency for Healthcare Research and Quality (AHRQ), HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for scientific information submissions.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Agency for Healthcare Research and Quality (AHRQ) is seeking scientific information submissions from manufacturers of Phototherapy medical devices for treatment of chronic plaque psoriasis. Scientific information is being solicited to inform our Comparative Effectiveness Review of Biologic and Nonbiologic Systemic Agents and Phototherapy for Treatment of Chronic Plaque Psoriasis, which is currently being conducted by the Evidence-based Practice Centers for the AHRQ Effective Health Care Program. Access to published and unpublished pertinent scientific information on this device will improve the quality of this comparative effectiveness review. AHRQ is requesting this scientific information and conducting this comparative effectiveness review pursuant to Section 1013 of the Medicare Prescription Drug, Improvement, and Modernization Act of 2003, Public Law 108-173.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submission Deadline on or before November 25, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        <E T="03">Online submissions: http://effectivehealthcare.AHRQ.gov/index.cfm/submit-scientific-information-packets/.</E>
                         Please select the study for which you are submitting information from the list of current studies and complete the form to upload your documents.
                    </P>
                    <P>
                        <E T="03">E-mail submissions: ehcsrc@ohsu.edu</E>
                         (please do not send zipped files—they are automatically deleted for security reasons).
                    </P>
                    <P>
                        <E T="03">Print submissions:</E>
                         Robin Paynter, Oregon Health and Science University, Oregon Evidence-based Practice Center, 3181 SW. Sam Jackson Park Road, Mail Code: BICC, Portland, OR 97239-3098.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Robin Paynter, Research Librarian, 
                        <E T="03">Telephone:</E>
                         503-494-0147 or E-mail: 
                        <E T="03">ehcsrc@ohsu.edu.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In accordance with Section 1013 of the Medicare Prescription Drug, Improvement, and Modernization Act of 2003, Public Law 108-173, the Agency for Healthcare Research and Quality has commissioned the Effective Health Care (EHC) Program Evidence-based Practice Centers to complete a comparative effectiveness review of the evidence for Biologic and Nonbiologic Systemic Agents and Phototherapy for Treatment of Chronic Plaque Psoriasis.</P>
                <P>
                    The EHC Program is dedicated to identifying as many studies as possible that are relevant to the questions for each of its reviews. In order to do so, we are supplementing the usual manual and electronic database searches of the literature by systematically requesting information (
                    <E T="03">e.g.,</E>
                     details of studies conducted) from medical device industry stakeholders through public information requests, including via the 
                    <E T="04">Federal Register</E>
                     and direct postal and/or online solicitations. We are looking 
                    <PRTPAGE P="66308"/>
                    for studies that report on phototherapy for treatment of chronic plaque psoriasis, including those that describe adverse events, as specified in the key questions detailed below. The entire research protocol, including the key questions, is also available online at: 
                    <E T="03">http://effectivehealthcare.AHRQ.gov/index.cfm/search-forouides-reviews-and-reports/?pageaction=displayproduct&amp;productid=793.</E>
                </P>
                <P>This notice is a request for industry stakeholders to submit the following:</P>
                <P>• A current product label, if applicable (preferably an electronic PDF file).</P>
                <P>• Information identifying published randomized controlled trials and observational studies relevant to the clinical outcomes. Please provide both a list of citations and reprints if possible.</P>
                <P>• Information identifying unpublished randomized controlled trials and observational studies relevant to the clinical outcomes. If possible, please provide a summary that includes the following elements: study number, study period, design, methodology, indication and diagnosis, proper use instructions, inclusion and exclusion criteria, primary and secondary outcomes, baseline characteristics, number of patients screened/eligible/enrolled/lost to withdrawn/followup/analyzed, and effectiveness/efficacy and safety results.</P>
                <P>
                    • 
                    <E T="03">Registered ClinicalTrials.gov</E>
                     studies. Please provide a list including the 
                    <E T="03">ClinicalTrials.gov</E>
                     identifier, condition, and intervention.
                </P>
                <P>Your contribution is very beneficial to this program. AHRQ is not requesting and will not consider marketing material, health economics information, or information on other indications. This is a voluntary request for information, and all costs for complying with this request must be borne by the submitter. In addition to your scientific information please submit an index document outlining the relevant information in each file along with a statement regarding whether or not the submission comprises all of the complete information available.</P>
                <NOTE>
                    <HD SOURCE="HED">Please Note: </HD>
                    <P>The contents of all submissions, regardless of format, will be available to the public upon request unless prohibited by law.</P>
                </NOTE>
                <P>
                    The draft of this review will be posted on AHRQ's EHC program Web site and available for public comment for a period of 4 weeks. If you would like to be notified when the draft is posted, please sign up for the e-mail list at: 
                    <E T="03">http://effectivehealthcare.AHRQ.gov/index.cfm/join-the-email-list1/.</E>
                </P>
                <HD SOURCE="HD1">Key Questions</HD>
                <P>Proposed Key Questions (KQs) were posted for public comments and were modified with consideration of the comments received. Since controversy surrounds the classification of psoriasis as mild or moderate-to-severe, moderate-to-severe disease was not included as an explicit inclusion criterion in the systematic search of the literature or in the comparative effectiveness review. As suggested in the public comments, we will consider when evaluating efficacy data whether patients were naïve to biologics, were treated previously with biologics, or were allowed drug holidays. Although a suggestion was made to evaluate combination therapy and to compare harms in patients without psoriasis or untreated controls with psoriasis, such an evaluation falls outside the scope of our review. We have now specified the measures that will be used for health-related quality of life in KQ.</P>
                <P>1. The Psoriasis Area and Severity Index (PAST) score will be considered not only as a binary outcome but as a continuous outcome as suggested. Although we had proposed the Psoriasis Scalp Severity Index (PSSI) and the Nail Psoriasis Severity Index (NAPSI) scores as outcomes, patient-reported improvement in scalp pruritus and scalp pain were suggested as additional outcomes in KQ 1; scalp pruritus and scalp pain are not as commonly reported in the literature and are less likely to add extra value over the body-wide assessments. We have not listed specific malignancies (hepatosplenic T-cell lymphoma and other lymphomas) and infections (tuberculosis and histoplasmosis) in KQ 2 as suggested to be more comprehensive. Weight and impact of neutralizing antibodies have been added as characteristics that will be evaluated in KQ 3. We did not move major adverse cardiovascular events (MACE) from final health outcomes to harms, because this is an outcome of the disease process rather than of therapeutic interventions. Subgroup analyses based on duration of followup were discussed with the Technical Expert Panelists (TEP).</P>
                <P>The acronyms used in the questions below are defined within the text and the list under Definitions of Terms.</P>
                <HD SOURCE="HD1">Question 1</HD>
                <P>
                    In patients with chronic plaque psoriasis, what is the comparative effectiveness of systemic biologic agents and systemic nonbiologic agents (between-class comparisons) or phototherapy when evaluating intermediate (plaque BSA measurement, PAST score, Patient's Assessment of Global Improvement, PGA, and individual symptom improvement) and final health outcomes (mortality, HRQoL [
                    <E T="03">e.g.,</E>
                     DLQI, HAQ-DI, EQ-5D] and other patient-reported outcomes, MACE, diabetes, and psychological comorbidities [
                    <E T="03">e.g.,</E>
                     depression, suicide])?
                </P>
                <HD SOURCE="HD1">Question 2</HD>
                <P>
                    In patients with chronic plaque psoriasis, what is the comparative safety of systemic biologic agents and systemic nonbiologic agents (between-class comparisons) or phototherapy (hepatotoxicity [
                    <E T="03">e.g.,</E>
                     AST, ALT], nephrotoxicity [
                    <E T="03">e.g.,</E>
                     SCr, GFR], hematologic toxicity [
                    <E T="03">e.g.,</E>
                     TCP, anemia, neutropenia], hypertension, alteration in metabolic parameters [
                    <E T="03">e.g.,</E>
                     glucose, lipids, weight, BMI, thyroid function], injection site reaction, malignancy, infection, and study withdrawal)?
                </P>
                <HD SOURCE="HD1">Question 3</HD>
                <P>
                    In patients with chronic plaque psoriasis treated with systemic biologic therapy, systemic nonbiologic therapy, or phototherapy, which patient or disease characteristics (
                    <E T="03">e.g.,</E>
                     age, gender, race, weight, smoking status, psoriasis severity, presence or absence of concomitant psoriatic arthritis, disease duration, baseline disease severity, affected BSA, disease location, number and type of previous treatments, failure of previous treatments and presence of neutralizing antibodies) affect intermediate and final outcomes?
                </P>
                <P>Details regarding the specific therapies considered in each class of interventions and comparators can be found in Tables 1-5. There are no specific requirements in terms of followup period that will be evaluated in these key questions. The setting will include inpatient, outpatient and home therapy.</P>
                <SIG>
                    <DATED>Dated: October 14, 2011.</DATED>
                    <NAME>Carolyn M. Clancy,</NAME>
                    <TITLE> Director, AHRQ.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27563 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-90-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention</SUBAGY>
                <SUBJECT> Statement of Organization, Functions, and Delegations of Authority</SUBJECT>
                <P>
                    Part C (Centers for Disease Control and Prevention) of the Statement of Organization, Functions, and Delegations of Authority of the 
                    <PRTPAGE P="66309"/>
                    Department of Health and Human Services (45 FR 67772-76, dated October 14, 1980, and corrected at 45 FR 69296, October 20, 1980, as amended most recently at 76 FR 50223—50224, dated August 12, 2011) is amended to reflect the reorganization of the Office of Public Health Preparedness and Response, Centers for Disease Control and Prevention.
                </P>
                <P>Section C-B, Organization and Functions, is hereby amended as follows:</P>
                <P>After item (7) in the functional statement for the Office of Public Health Preparedness and Response (CG), Division of Strategic National Stockpile (CGE), Office of the Director (CGE1), insert the following: And (8) provides leadership, guidance, and technical assistance to state, tribal and local territories for healthcare preparedness and emergency response and for the integration of preparedness planning across the public health, healthcare, and emergency management sectors.</P>
                <SIG>
                    <DATED>Dated: October 14, 2011.</DATED>
                    <NAME>Sherri A. Berger,</NAME>
                    <TITLE>Chief Operating Officer, Centers for Disease Control and Prevention.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27497 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4163-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare and Medicaid Services</SUBAGY>
                <DEPDOC>[CMS-3180-N2]</DEPDOC>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2010-N-0308]</DEPDOC>
                <SUBJECT>Pilot Program for Parallel Review of Medical Products; Correction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, Centers for Medicare and Medicaid Services, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; correction.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Food and Drug Administration (FDA) and the Centers for Medicare and Medicaid Services (CMS) are correcting a notice that appeared in the 
                        <E T="04">Federal Register</E>
                         of October 11, 2011 (76 FR 62808). The document announced a pilot program for sponsors of innovative device technologies to participate in a program of parallel FDA-CMS review. The document was published with an incorrect Web page address and an incorrect email address. This document corrects those errors.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jean Olson, Center for Devices and Radiological Health, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 66, rm. 4434, Silver Spring, MD 20993-0002, 301-796-6579.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    In FR Doc. 2011-25907, appearing on page  62808 in the 
                    <E T="04">Federal Register</E>
                     of Tuesday, October 11, 2011, the following corrections are made:
                </P>
                <P>
                    1. On page 62808, in the third column, under the heading “A. 
                    <E T="03">Parallel Review Proposal,</E>
                    ” the Web site address “
                    <E T="03">http://www.parallel-review.fda.gov</E>
                    ” is corrected to read  “
                    <E T="03">http://www.fda.gov/parallel-review</E>
                    ”.
                </P>
                <P>
                    2. On page 62809, in the second column, under the heading “B. 
                    <E T="03">Appropriate Candidates,</E>
                    ” the e-mail address “
                    <E T="03">parallel-review@fda.gov</E>
                    ” is corrected to read “
                    <E T="03">parallel-review@fda.hhs.gov</E>
                    ”.
                </P>
                <P>
                    3. On page 62809, in the third column, under the heading “1. 
                    <E T="03">Nomination,</E>
                    ” the Web site address “
                    <E T="03">http://www.parallel-review.fda.gov</E>
                    ” is corrected to read “
                    <E T="03">http://www.fda.gov/parallel-review</E>
                    ”.
                </P>
                <SIG>
                    <DATED>Dated: October 17, 2011.</DATED>
                    <NAME>Jacquelyn Y. White,</NAME>
                    <TITLE>Director, Office of Strategic Operations and Regulatory Affairs. Centers for Medicare &amp; Medicaid Services.</TITLE>
                    <DATED>Dated: October 19, 2011.</DATED>
                    <NAME>Leslie Kux,</NAME>
                    <TITLE>Acting Assistant Commissioner for Policy, Food and Drug Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27694 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Administration for Children and Families</SUBAGY>
                <SUBJECT>Proposed Information Collection Activity; Comment Request</SUBJECT>
                <P>
                    <E T="03">Title:</E>
                     Affordable Care Act Tribal Maternal, Infant and Early Childhood Home Visiting Program Annual Report.
                </P>
                <P>
                    <E T="03">OMB No.:</E>
                     New.
                </P>
                <HD SOURCE="HD1">Description</HD>
                <P>Section 511(h)(2)(A) of Title V of the Social Security Act, as added by Section 2951 of the Patient Protection and Affordable Care Act of 2010 (Pub. L. 111-148, Affordable Care Act or ACA), authorizes the Secretary of HHS to award grants to Indian Tribes (or a consortium of Indian Tribes), Tribal Organizations, or Urban Indian Organizations to conduct an early childhood home visiting program.</P>
                <P>The legislation sets aside 3 percent of the total ACA Maternal, Infant, and Early Childhood Home Visiting Program appropriation (authorized in Section 511(j)) for grants to Tribal entities and requires that the Tribal grants, to the greatest extent practicable, be consistent with the requirements of the Maternal, Infant, and Early Childhood Home Visiting Program grants to States and territories (authorized in Section 511(c)), and include (1) Conducting a needs assessment similar to the assessment required for all States under the legislation and (2) establishing quantifiable, measurable 3- and 5-year benchmarks consistent with the legislation.</P>
                <P>The Administration for Children and Families, Office of Child Care, in collaboration with the Health Resources and Services Administration, Maternal and Child Health Bureau, has awarded grants for the Tribal Maternal, Infant, and Early Childhood Home Visiting Program (Tribal Home Visiting). The Tribal Home Visiting grant awards support 5-year cooperative agreements to conduct community needs assessments, plan for and implement (in accordance with an Implementation Plan submitted at the end of Year 1) high-quality, culturally-relevant, evidence-based and promising home visiting programs in at-risk Tribal communities, and participate in research and evaluation activities to build the knowledge base on home visiting among Native populations.</P>
                <P>In the Affordable Care Act Tribal Maternal, Infant, and Early Childhood Home Visiting Program Needs Assessment and Plan for Responding to Identified Needs (“Implementation Plan Guidance”) (OMB Control No. 0970-0389, Expiration Date 6/30/14), grantees were notified that in Years 2-5 of their grant they must comply with the requirement for submission of an Annual Report to the Secretary regarding the program and activities carried out under the program.</P>
                <HD SOURCE="HD2">This Report Shall Address the Following</HD>
                <P>Home Visiting Program Goals and Objectives.</P>
                <P>Implementation of Home Visiting Program in Targeted Community(ies).</P>
                <P>Progress toward Meeting Legislatively Mandated Benchmark Requirements.</P>
                <P>Research and Evaluation Update.</P>
                <P>Home Visiting Program Continuous Quality Improvement (CQI) Efforts.</P>
                <P>Administration of Home Visiting Program.</P>
                <P>Technical Assistance Needs.</P>
                <HD SOURCE="HD1">
                    Respondents
                    <PRTPAGE P="66310"/>
                </HD>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s80,12C,12C,12C,12C">
                    <TTITLE>Annual Burden Estimates</TTITLE>
                    <BOXHD>
                        <CHED H="1">Instrument</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses per</LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>burden hours </LI>
                            <LI>per</LI>
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">
                            Total burden
                            <LI>hours</LI>
                        </CHED>
                    </BOXHD>
                    <ROW RUL="n,s">
                        <ENT I="01">Tribal Home Visiting Program Annual Report</ENT>
                        <ENT>25</ENT>
                        <ENT>1</ENT>
                        <ENT>50</ENT>
                        <ENT>1,250</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Estimated Total Annual Burden Hours</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>1,250</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    In compliance with the requirements of Section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995, the Administration for Children and Families is soliciting public comment on the specific aspects of the information collection described above. Copies of the proposed collection of information can be obtained and comments may be forwarded by writing to the Administration for Children and Families, Office of Administration, Office of Information Services, 370 L'Enfant Promenade, SW., Washington, DC 20447, 
                    <E T="03">Attn:</E>
                     ACF Reports Clearance Officer. 
                    <E T="03">E-mail address: infocollection@acf.hhs.gov.</E>
                     All requests should be identified by the title of the information collection.
                </P>
                <P>The Department specifically requests comments on: (a) Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information shall have practical utility; (b) the accuracy of the agency's estimate of the burden of the proposed collection of information; (c) the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or other forms of information technology. Consideration will be given to comments and suggestions submitted within 60 days of this publication.</P>
                <SIG>
                    <NAME>Robert Sargis,</NAME>
                    <TITLE>Reports Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27611 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4184-01-P</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>
                     Annual Report/ACF 204 (State MOE).
                </P>
                <P>
                    <E T="03">OMB No.:</E>
                     0970-0248.
                </P>
                <HD SOURCE="HD1">Description</HD>
                <P>The Administration for Children and Families (ACF) is requesting a three-year extension of the ACF-204 (Annual MOE Report). The report is used to collect descriptive program characteristics information on the programs operated by States and Territories in association with their Temporary Assistance for Needy Families (TANF) programs. All State and Territory expenditures claimed toward States and Territories MOE requirements must be appropriate, i.e., meet all applicable MOE requirements. The Annual MOE Report provides the ability to learn about and to monitor the nature of State and Territory expenditures used to meet States and Territories MOE requirements, and it is an important source of information about the different ways that States and Territories are using their resources to help families attain and maintain self-sufficiency. In addition, the report is used to obtain State and Territory program characteristics for ACFs annual report to Congress, and the report serves as a useful resource to use in Congressional hearings about how TANF programs are evolving, in assessing State the Territory MOE expenditures, and in assessing the need for legislative changes.</P>
                <HD SOURCE="HD1">Respondents</HD>
                <P>The 50 States of the United States, the District of Columbia, Guam, Puerto Rico, and the Virgin Islands.</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,12C,12C,12C,12C">
                    <TTITLE>Annual Burden Estimates</TTITLE>
                    <BOXHD>
                        <CHED H="1">Instrument</CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>responses per respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Average 
                            <LI>burden hours </LI>
                            <LI>per response</LI>
                        </CHED>
                        <CHED H="1">Total burden hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">ACF-204</ENT>
                        <ENT>54</ENT>
                        <ENT>1</ENT>
                        <ENT>118</ENT>
                        <ENT>6,372</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     6,372.
                </P>
                <HD SOURCE="HD1">Additional Information</HD>
                <P>
                    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>
                     ACF Reports Clearance Officer. All requests should be identified by the title of the information collection. 
                    <E T="03">E-mail address: infocollection@acf.hhs.gov.</E>
                </P>
                <HD SOURCE="HD1">OMB Comment</HD>
                <P>
                    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, 
                    <E T="03">Fax:</E>
                     202-395-7285, 
                    <E T="03">E-mail: OIRA_SUBMISSION@OMB.EOP.GOV, Attn:</E>
                     Desk Officer for the Administration for Children and Families.
                </P>
                <SIG>
                    <NAME>Robert Sargis,</NAME>
                    <TITLE>Reports Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27602 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4184-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="66311"/>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2011-N-0724]</DEPDOC>
                <SUBJECT>Draft Documents To Support Submission of an Electronic Common Technical Document; Availability</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA) is announcing the availability of the following draft versions of documents that support making regulatory submissions in electronic format using the electronic Common Technical Document (eCTD) specifications entitled “The eCTD Backbone Files Specification for Module 1, version 2.0” (which includes the U.S. regional document type definition, version 3.0) and “Comprehensive Table of Contents Headings and Hierarchy, version 2.0.” Supporting technical files are also being made available on the Agency Web site. These draft documents represent FDA's major updates to Module 1 of the eCTD, which contains regional information.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit either electronic or written comments on the draft documents by December 27, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit written requests for single copies of the documents to the Division of Drug Information, Center for Drug Evaluation and Research (CDER), Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, rm. 2201, Silver Spring, MD 20993-0002; or Office of Communication, Outreach and Development (HFM-40), Center for Biologics Evaluation and Research (CBER), Food and Drug Administration, 1401 Rockville Pike, suite 200N, Rockville, MD 20852-1448. Send one self-addressed adhesive label to assist that office in processing your requests. See the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for electronic access to the documents.
                    </P>
                    <P>
                        Submit electronic comments on the draft documents to 
                        <E T="03">http://www.regulations.gov.</E>
                         Submit written comments to the Division of Dockets Management (HFA-305), Food and Drug Administration, 5630 Fishers Lane, rm. 1061, Rockville, MD 20852.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Virginia Hussong, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 22, rm. 1161, Silver Spring, MD 20993, 
                        <E T="03">Esub@fda.hhs.gov;</E>
                         or Mary Padgett, Center for Biologics Evaluation and Research (HFM-25), Food and Drug Administration, 1401 Rockville Pike, suite 200N, Rockville, MD 20852, 301-827-0373, 
                        <E T="03">mary.padgett@fda.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>The eCTD is an International Conference on Harmonisation (ICH) standard based on specifications developed by ICH and its member parties. CDERCBER have been receiving submissions in the eCTD format since 2003, and the eCTD has been the standard for electronic submissions to CDER and CBER since January 1, 2008. The majority of new electronic submissions are now received in eCTD format. Since adoption of the eCTD standard, it has become necessary to update the administrative portion of the eCTD (Module 1) to reflect regulatory changes, to provide clarification of business rules for submission processing and review, to refine the characterization of promotional marketing and advertising material, and to facilitate automated processing of submissions. In preparation for the Module 1 update, FDA is making available for comment the following draft documents:</P>
                <P>• “The eCTD Backbone Files Specification for Module 1, version 2.0” provides specifications for creating the eCTD backbone file for Module 1 for submission to CDER and CBER. It should be used in conjunction with the guidance for industry entitled “Providing Regulatory Submissions in Electronic Format—Human Pharmaceutical Applications and Related Submissions,” which will be revised as part of the implementation of the updated eCTD backbone files specification.</P>
                <P>• “The Comprehensive Table of Contents Headings and Hierarchy, version 2.0” reflects updated headings that are specified in the draft document entitled “The eCTD Backbone Files Specification for Module 1, version 2.0,” as well as mappings to regulations and legislation.</P>
                <FP>Supporting technical files are also being made available on the Agency Web site.</FP>
                <P>The draft documents include the following changes:</P>
                <P>
                    • Providing for processing of bundled submissions (
                    <E T="03">e.g.,</E>
                     a supplement can be applied to more than one new drug application or biologics license application),
                </P>
                <P>• Providing detailed contact information so that companies can specify points of contacts to discuss technical matters that may arise with a submission,</P>
                <P>• Clarifying headings, and</P>
                <P>• Using attributes in place of certain headings to provide flexibility for future changes without revising the specification itself.</P>
                <FP>The draft documents contain complete lists of the changes to Module 1.</FP>
                <HD SOURCE="HD1">II. Comments</HD>
                <P>
                    Interested persons may submit to the Division of Dockets Management (see 
                    <E T="02">ADDRESSES</E>
                    ) either electronic or written comments regarding the draft documents. It is only necessary to send one set of comments. It is no longer necessary to send two copies of mailed comments. Identify comments with the docket number found in brackets in the heading of this document. Received comments may be seen in the Division of Dockets Management between 9 a.m. and 4 p.m., Monday through Friday.
                </P>
                <HD SOURCE="HD1">III. Electronic Access</HD>
                <P>
                    Persons with access to the Internet may obtain the documents at either 
                    <E T="03">http://www.fda.gov/Drugs/DevelopmentApprovalProcess/FormsSubmissionRequirements/ElectronicSubmissions/ucm253101.htm, http://www.fda.gov/BiologicsBloodVaccines/GuidanceComplianceRegulatoryInformation/Guidances/default.htm,</E>
                     or 
                    <E T="03">http://www.regulations.gov</E>
                    .
                </P>
                <SIG>
                    <DATED>Dated: October 21, 2011.</DATED>
                    <NAME>Leslie Kux,</NAME>
                    <TITLE>Acting Assistant Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27658 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">ADVISORY COUNCIL ON HISTORIC PRESERVATION</AGENCY>
                <SUBJECT>Notice of ACHP Quarterly Business Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Advisory Council on Historic Preservation.</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 Advisory Council on Historic Preservation (ACHP) will meet Thursday, November 10, 2011. The meeting will be held at 8:30 a.m. in Room M09 in the Old Post Office Building, 1100 Pennsylvania Ave., NW., Washington, DC 20004.</P>
                    <P>
                        The ACHP was established by the National Historic Preservation Act of 1966 (16 U.S.C. 470 
                        <E T="03">et seq.</E>
                        ) to advise the President and Congress on national historic preservation policy and to comment upon federal, federally assisted, and federally licensed undertakings having an effect upon properties listed in or eligible for 
                        <PRTPAGE P="66312"/>
                        inclusion in the National Register of Historic Places. The ACHP's members are the Architect of the Capitol; the Secretaries of the Interior, Agriculture, Defense, Housing and Urban Development, Commerce, Education, Veterans Affairs, and Transportation; the Administrator of the General Services Administration; the Chairman of the National Trust for Historic Preservation; the President of the National Conference of State Historic Preservation Officers; a Governor; a Mayor; a Native American; and eight non-federal members appointed by the President.
                    </P>
                </SUM>
                <FP SOURCE="FP-2">Call to Order_8:30 a.m.</FP>
                <FP SOURCE="FP-2">I. Chairman's Welcome</FP>
                <FP SOURCE="FP-2">II. Presentation of Chairman's Award</FP>
                <FP SOURCE="FP-2">III. Chairman's Report</FP>
                <FP SOURCE="FP-2">IV. ACHP Management Issues</FP>
                <FP SOURCE="FP1-2">A. Credentials Committee Report and Recommendations—Update</FP>
                <FP SOURCE="FP1-2">B. Alumni Foundation Report</FP>
                <FP SOURCE="FP1-2">C.  ACHP FY 2012 Budget</FP>
                <FP SOURCE="FP-2">V. Historic Preservation Policy and Programs</FP>
                <FP SOURCE="FP1-2">A. Preservation Action Federal Preservation Task Force Report and Recommendations</FP>
                <FP SOURCE="FP1-2">B. National Park Service “Call to Action”</FP>
                <FP SOURCE="FP1-2">C. National Trust for Historic Preservation's “Preservation 10X” and the ACHP</FP>
                <FP SOURCE="FP1-2">D. White House American Latino Heritage Initiative</FP>
                <FP SOURCE="FP1-2">E. Legislative Agenda</FP>
                <FP SOURCE="FP1-2">F. Navy War of 1812 Initiative</FP>
                <FP SOURCE="FP1-2">G. Rightsizing Task Force Report</FP>
                <FP SOURCE="FP1-2">H. Sustainability Task Force Report</FP>
                <FP SOURCE="FP1-2">I. Federal Preservation Funding for Disaster Recovery</FP>
                <FP SOURCE="FP-2">VI. Section 106 Issues</FP>
                <FP SOURCE="FP1-2">A. Section 3 Report Development</FP>
                <FP SOURCE="FP1-2">B. Native American Traditional Cultural Landscapes Action Plan</FP>
                <FP SOURCE="FP1-2">C. Department of Veterans Affairs Section 106 Issues</FP>
                <FP SOURCE="FP1-2">D. Administration's Priority Projects—Report</FP>
                <FP SOURCE="FP-2">VII. New Business</FP>
                <FP SOURCE="FP-2">VIII. Adjourn</FP>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>The meetings of the ACHP are open to the public. If you need special accommodations due to a disability, please contact the Advisory Council on Historic Preservation, 1100 Pennsylvania Avenue, NW., Room 803, Washington, DC, (202) 606-8503, at least seven (7) days prior to the meeting. For further information: Additional information concerning the meeting is available from the Executive Director, Advisory Council on Historic Preservation, 1100 Pennsylvania Avenue, NW., #803, Washington, DC 20004.</P>
                </NOTE>
                <SIG>
                    <DATED>Dated: October 19, 2011.</DATED>
                    <NAME>Reid Nelson,</NAME>
                    <TITLE>Acting Executive Director.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27533 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-K6-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <DEPDOC>[Docket No. DHS-2011-0079]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Submission for Review; Information Collection Request for the Department of Homeland Security (DHS), Science and Technology, Biodefense Knowledge Center (BKC)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Science and Technology Directorate, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>30-day Notice and request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Homeland Security (DHS), Science &amp; Technology (S&amp;T) Directorate invites the general public to comment on data collection forms for the Biodefense Knowledge Center (BKC) program. BKC is responsible for coordinating the collection of Life Sciences Subject Matter Experts (SMEs) information with the Office of the Director of National Intelligence (ODNI), which operates under the authority of the National Security act of 1947, as amended by the Intelligence Reform and Terrorism Prevention Act of 2004. These authorities charge the ODNI with responsibility to coordinate and rationalize the activities of the Intelligence Community components. The SME information is necessary to understand who can provide scientific expertise for peer review of life science programs. In addition, the directory makes it easier to identify scientific specialty areas for which there is a shortage of Subject Matter Experts (SMEs) with appropriate security clearances.</P>
                    <P>The DHS invites interested persons to comment on the following form and instructions (hereinafter “Forms Package”) for the S&amp;T BKC: (1) Subject Matter Expert Registration Form (DHS FORM 10043 (2/08)). Interested persons may receive a copy of the Forms Package by contacting the DHS S&amp;T PRA Coordinator. This notice and request for comments is required by the Paperwork Reduction Act of 1995 (Pub. L. 104-13, 44 U.S.C. chapter 35).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments are encouraged and will be accepted until November 25, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested persons are invited to submit written comments on the proposed information collection to the Office of Information and Regulatory Affairs, Office of Management and Budget. Comments should be addressed to: Desk Officer for the Department of Homeland Security, Science and Technology Directorate, and sent via electronic mail to 
                        <E T="03">oira_submission@omb.eop.gov</E>
                         or faxed to (202) 395-6974. Please include docket number DHS-2011-0079 in the subject line of the message.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>DHS S&amp;T PRA Coordinator Millie Ives (202) 254-6828 (Not a toll free number).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The information is collected via the DHS S&amp;T BKC secure Web site at 
                    <E T="03">https://bkms.llnl.gov/sme.</E>
                     The BKC Web site only employs secure web-based technology (
                    <E T="03">i.e.,</E>
                     electronic registration form) to collect information from users to both reduce the burden and increase the efficiency of this collection.
                </P>
                <P>The Department is committed to improving its information collection and urges all interested parties to suggest how these materials can further reduce burden while seeking necessary information under the Act.</P>
                <P>
                    <E T="03">DHS is particularly interested in comments that:</E>
                </P>
                <P>(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;</P>
                <P>(2) Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
                <P>(3) Suggest ways to enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    (4) Suggest 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, 
                    <E T="03">e.g.,</E>
                     permitting electronic submissions of responses.
                </P>
                <HD SOURCE="HD1">Overview of This Information Collection</HD>
                <P>
                    (1) 
                    <E T="03">Type of Information Collection:</E>
                     Renewal of information collection
                </P>
                <P>
                    (2) 
                    <E T="03">Title of the Form/Collection:</E>
                     Science and Technology, Biodefense Knowledge Center (BKC) program.
                </P>
                <P>
                    (3) 
                    <E T="03">Agency Form Number, if any, and the applicable component of the Department of Homeland Security sponsoring the collection:</E>
                     Department of Homeland Security, Science &amp; 
                    <PRTPAGE P="66313"/>
                    Technology Directorate—(1) Subject Matter Expert Registration Form (DHS FORM 10043 (2/08)).
                </P>
                <P>
                    (4) 
                    <E T="03">Affected public who will be asked or required to respond, as well as a brief abstract:</E>
                     The Subject Matter Experts (SME) information is necessary to understand who can provide scientific expertise for peer review of life science programs. The directory makes it easier to identify scientific specialty areas for which there is a shortage of SMEs with appropriate security clearances. SME contact information, scientific expertise, and level of education is collected electronically through a web portal developed by DHS S&amp;T. The SME information is shared with U.S. Government program managers and other members of the biodefense community who have a legitimate need to identify life sciences SMEs. Cleared SMEs are necessary to accomplish scientific reviews and attend topical meetings.
                </P>
                <P>
                    (5) 
                    <E T="03">An estimate of the total number of respondents and the amount of time estimated for an average respondent to respond:</E>
                </P>
                <P>
                    a. 
                    <E T="03">Estimate of the total number of respondents:</E>
                     4000.
                </P>
                <P>
                    b. 
                    <E T="03">An estimate of the time for an average respondent to respond:</E>
                     0.25 burden hours.
                </P>
                <P>
                    c. 
                    <E T="03">An estimate of the total public burden (in hours) associated with the collection:</E>
                     1000 burden hours.
                </P>
                <SIG>
                    <DATED>Dated: October 19, 2011.</DATED>
                    <NAME>Tara O'Toole,</NAME>
                    <TITLE>Under Secretary for Science and Technology.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27636 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-9F-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <DEPDOC>[USCG-2011-0975]</DEPDOC>
                <SUBJECT>National Maritime Security Advisory Committee; Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Federal Advisory Committee Meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The National Maritime Security Advisory Committee (NMSAC) will meet via teleconference on November 15, 2011 to discuss the results of a working group tasked with reviewing the Draft Certain Dangerous Cargo (CDC) Security Strategy. This meeting will be open to the public.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The Committee will meet on Tuesday, November 15, 2011 from 11 a.m. to 1 p.m. This meeting may close early if all business is finished.</P>
                    <P>All written material and requests to make oral presentations should reach the Coast Guard on or before November 7, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The Committee will meet via telephone conference, on November 15, 2011. As there are only 100 teleconference lines, public participation will be on a first come basis. To participate via teleconference, please contact the person listed in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         Section.
                    </P>
                    <P>
                        For information on facilities or services for individuals with disabilities or to request special assistance at the teleconference, contact the person listed in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section as soon as possible.
                    </P>
                    <P>To facilitate public participation, we are inviting public comment on the issues to be considered by the committee as listed in the “Agenda” section below. You may submit written materials and requests to make oral presentations no later than November 7, 2011, and identified by docket number [USCG-2011-0975] using one of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov</E>
                        . Follow the instruction for submitting comments.
                    </P>
                    <P>
                        • 
                        <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. We encourage use of electronic submissions because security screening may delay delivery of mail.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (202) 493-2251.
                    </P>
                    <P>
                        • 
                        <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>
                        <E T="03">Instructions:</E>
                         All submissions received must include the words “Department of Homeland Security” and docket number [USCG-2011-0975]. All submissions received will be posted without alteration at 
                        <E T="03">http://www.regulations.gov</E>
                        , including any personal information provided. 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>
                    <P>
                        <E T="03">Docket:</E>
                         Any background information or presentations available prior to the meeting will be published in the docket. For access to the docket to read background documents or submissions received by the NMSAC, go to 
                        <E T="03">http://www.regulations.gov</E>
                         “USCG-2011-0975) in the “Keyword” box, and then click “Search”.
                    </P>
                    <P>
                        Public comment period will be held during the meeting on November 15, 2011 from 12:30 p.m. to 1 p.m. Speakers are requested to limit their comments to 2 minutes. Please note that the public comment period will end following the last call for comments. Contact the person listed in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section to register as a speaker.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Ryan Owens, Alternate Designated Federal Officer (ADFO) of NMSAC, 2100 2nd Street, SW., Stop 7581, Washington, DC 20593-7581; telephone 202-372-1108 or e-mail 
                        <E T="03">ryan.f.owens@uscg.mil</E>
                        . If you have any 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>Notice of this meeting is given under the Federal Advisory Committee Act, 5 U.S.C. App. NMSAC operates under the authority of 46 U.S.C. 70112. NMSAC provides advice, consults with, and makes recommendations to the Secretary of Homeland Security, via the Commandant of the Coast Guard, on matters affecting national maritime security.</P>
                <HD SOURCE="HD1">Agenda of Meeting</HD>
                <P>As a result of the report issued by NMSAC at its April 2011 meeting and public listening sessions held by the Coast Guard in August 2011, the Coast Guard has developed a Certain Dangerous Cargo (CDC) Security Strategy. A NMSAC working group was created to review the following five goals of the strategy. The committee will review the information presented on each issue, deliberate on any recommendations presented in the Work Group reports, and formulate the recommendations for the Department's consideration.</P>
                <P>a. Provide to internal and external stakeholders real-time national, regional, and local awareness of the risk of intentional attacks on the CDC Marine Transportation System.</P>
                <P>b. Consistently assess vulnerability to threats of intentional attacks on the CDC Marine Transportation System and mitigate the vulnerability to an acceptable level.</P>
                <P>c. Dynamically assess the potential consequences of an intentional attack on the CDC Marine Transportation System and capably mitigate, through coordinated response, the impact of a successful attack.</P>
                <P>d. Lead the development of national, regional, and local resiliency/recovery capability from successful attacks on the CDC Marine Transportation System.</P>
                <P>
                    e. Establish the internal organization and processes, and external stakeholder 
                    <PRTPAGE P="66314"/>
                    relationships, to manage the national maritime CDC security program to an acceptable risk level.
                </P>
                <SIG>
                    <DATED>Dated: October 20, 2011.</DATED>
                    <NAME>K.C. Kiefer,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Office of Port and Facility Activities, Designated Federal Official, NMSAC.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27724 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <DEPDOC>[Docket No. USCG-2011-0724]</DEPDOC>
                <RIN>RIN 1625-1148</RIN>
                <SUBJECT>Lower Mississippi River Waterway Safety Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Federal Advisory Committee Meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Lower Mississippi River Waterway Safety Advisory Committee (LMRWSAC) will hold its bi-annual meeting on December 6, 2011, in New Orleans, Louisiana. The meeting will be open to the public. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES: </HD>
                    <P>LMRWSAC will meet on Tuesday, December 6, 2011, from 9 a.m. to 12 p.m. Please note that the meeting may close early if the committee has completed its business. Written materials and requests to make oral presentation should reach the Coast Guard on or before November 21, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meeting will be held at the U.S. Coast Guard Sector New Orleans Building, 200 Hendee Street, New Orleans, Louisiana 70114, First Floor, Training Room A.</P>
                    <P>For information on facilities or services for individuals with disabilities or to request special assistance at the meeting, contact LCDR Marcie Kohn as soon as possible.</P>
                    <P>To facilitate public participation, we are inviting public comment on the issues to be considered by the committee as listed by the “Agenda” section below. Comments must be submitted in writing no later than November 21, 2011 and must be identified by USCG-2011-0724 and may be submitted by one of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>
                         Follow the instructions for submitting comments (preferred method to avoid delays in processing).
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         202-493-2251.
                    </P>
                    <P>
                        • 
                        <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>
                        • 
                        <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>
                        <E T="03">Instructions:</E>
                         All submissions received must include the words “Department of Homeland Security” and the docket number for this action. Comments received will be posted without alteration at 
                        <E T="03">http://www.regulations.gov,</E>
                         including any personal information provided. 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>
                    <P>
                        <E T="03">Docket:</E>
                         For access to the docket to read background documents or comments related to this notice, go to 
                        <E T="03">http://www.regulations.gov</E>
                        , enter the docket number for this notice (USCG-2011-0724) in the “Keyword” box, and then click “Search.”
                    </P>
                    <P>A public comment period will be held at the end of the meeting on December 6, 2011 from 9 a.m until 12 p.m. Speakers are requested to limit their comments to 10 minutes. Please note that the public comment period may end before the time indicated, following the last call for comments.</P>
                    <P>Contact the individual listed below to register as a speaker.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Lieutenant Marcie Kohn, Assistant Designated Federal Officer of the Lower Mississippi River Waterway Safety Advisory Committee, telephone 504-365-2281 or e-mail at 
                        <E T="03">Marcie.L.Kohn@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>
                    Notice of this meeting is given under the 
                    <E T="03">Federal Advisory Committee Act (FACA),</E>
                     5 U.S.C. App. (Pub. L. 92-463). The LMRWSAC is an advisory committee authorized in Section 19 of the Coast Guard Authorization Act of 1991, (Pub. L. 102-241) as amended by section 621 of the Coast Guard Authorization Act of 2010 (Pub. L. 111-281) and chartered under the provisions of FACA. LMRWSAC provides advice and recommendations to the Department of Homeland Security on matters relating to communications, surveillance, traffic management, anchorages, development and operation of New Orleans Vessel Traffic Service (VTS), and other related topics dealing with navigation safety on the Lower Mississippi River (LMR) as required by the U.S. Coast Guard.
                </P>
                <HD SOURCE="HD1">Agenda</HD>
                <P>(1) Opening comments by Chairman;</P>
                <P>(2) Introduction of committee members and distinguished guests;</P>
                <P>(3) Approval of the March 24th, 2011 meeting minutes;</P>
                <P>(4) Remarks from Coast Guard Captain of the Port, Captain Peter Gautier, Commander, Sector New Orleans, Designated Federal Officer (DFO) of LMRWSAC;</P>
                <P>(5) Remarks from Rear Admiral R. A. Nash, Commander 8th Coast Guard District;</P>
                <P>(6) Committee Administration issues to include nomination and selection of Vice-Chairman;</P>
                <P>(7) Baton Rouge LA Vessel Traffic Operations report;</P>
                <P>(8) Discussion on possible establishment of Belmont Anchorage;</P>
                <P>(9) U.S. Army Corps of Engineers report on Dredging Operations;</P>
                <P>(10) National Oceanic and Administration report;</P>
                <P>(11) Public Comments/Presentations;</P>
                <P>(12) Adjournment.</P>
                <P>
                    <E T="03">Reports and Meeting Minutes:</E>
                     The reports which will be discussed by the Committee and minutes of the meeting may be viewed in our online docket. Go to 
                    <E T="03">http://www.regulations.gov,</E>
                     enter the docket number for this notice (USCG-2011-0724) in the “Keyword” box, and then click “Search.”
                </P>
                <SIG>
                    <DATED>Dated: October 12, 2011.</DATED>
                    <NAME>P. Troedsson,</NAME>
                    <TITLE>Captain, U.S. Coast Guard, Acting Commander, Eighth Coast Guard District.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27643 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-04-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-5480-N-104]</DEPDOC>
                <SUBJECT>Notice of Submission of Proposed Information Collection to OMB Requirements for Single Family Mortgage Instruments</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>
                        This information is used to verify that a mortgage has been properly recorded 
                        <PRTPAGE P="66315"/>
                        and is eligible for FHA mortgage insurance.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments Due Date: November 25, 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 approval Number (2502-0404) and should be sent to: HUD Desk Officer, Office of Management and Budget, New Executive Office Building, Washington, DC 20503; e-mail 
                        <E T="03">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-mail Colette Pollard at 
                        <E T="03">Colette.Pollard@hud.gov;</E>
                         or telephone (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>
                <HD SOURCE="HD1">This Notice Also Lists the Following Information</HD>
                <P>
                    <E T="03">Title of Proposal:</E>
                     Requirements For Single Family Mortgage Instruments.
                </P>
                <P>
                    <E T="03">OMB Approval Number:</E>
                     2502-0404.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     None.
                </P>
                <HD SOURCE="HD1">Description of the Need for the Information and Its Proposed Use</HD>
                <P>This information is used to verify that a mortgage has been properly recorded and is eligible for FHA mortgage insurance.</P>
                <P>
                    <E T="03">Frequency of Submission:</E>
                     On Occasion.
                </P>
                <GPOTABLE COLS="7" OPTS="L1,tp0,i1" CDEF="s30,12C,12C,2,12C,2,12C">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Annual
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">×</CHED>
                        <CHED H="1">
                            Hours per
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">=</CHED>
                        <CHED H="1">
                            Burden
                            <LI>hours</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Reporting Burden</ENT>
                        <ENT>9,000</ENT>
                        <ENT>1</ENT>
                        <ENT> </ENT>
                        <ENT>0.5</ENT>
                        <ENT> </ENT>
                        <ENT>4,500</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Total Estimated Burden Hours:</E>
                     4,500.
                </P>
                <P>
                    <E T="03">Status:</E>
                     Revision of a currently approved 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: October 20, 2011.</DATED>
                    <NAME>Colette Pollard,</NAME>
                    <TITLE>Departmental Reports Management Officer, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27667 Filed 10-25-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-5487-N-18]</DEPDOC>
                <SUBJECT> Notice of Proposed Information Collection for Public Comment for the  Family Unification Program (FUP)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Assistant Secretary for Public and Indian Housing, 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 of 1995 (44 U.S.C. chapter 35, as amended). The Department is soliciting public comments on the subject proposal.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments Due Date: December 27, 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: Colette Pollard, Departmental Reports Management Officer, QDAM, Department of Housing and Urban Development, 451 7th Street, SW. Room 4178, 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 information on the data collected. 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. (Other than the HUD USER information line and TTY numbers, telephone numbers are not toll-free.)
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Arlette A. Mussington, Office of Policy, Programs and Legislative Initiatives, PIH, Department of Housing and Urban Development, 470 L'Enfant Plaza, SW., Suite 2206, Washington, DC 20024, telephone 202-402-4109, (this is not a toll-free number) or e-mail at 
                        <E T="03">Arlette.A.Mussington@hud.gov.</E>
                    </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).</P>
                <P>
                    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 submissions of responses.
                </P>
                <P>
                    <E T="03">This Notice also lists the following information:</E>
                </P>
                <P>
                    <E T="03">Title of Proposal:</E>
                     Family Unification Program (FUP).
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     2577-0259.
                </P>
                <P>
                    <E T="03">Description of the Need for the Information and Proposed Use:</E>
                     The Family Unification Program (FUP) is a program, authorized under section 8(x) of the United States Housing Act of 1937 {42 U.S.C. 1437(X)}, that provides housing choice vouchers to PHAs to assist families for whom the lack of adequate housing is a primary factor in the imminent placement of the family's child, or children, in out-of-home care; or the delay in the discharge of the child, or children, to the family from 
                    <PRTPAGE P="66316"/>
                    out-of-home care. Youths at least 18 years old and not more than 21 years old (have not reached 22nd birthday) who left foster care at age 16 or older and who do not have adequate housing are also eligible to receive housing assistance under the FUP. As required by statute, a FUP voucher issued to such a youth may only be used to provide housing assistance for the youth for a maximum of 18 months.
                </P>
                <P>Vouchers awarded under FUP are administered by PHAs under HUD's regulations for the Housing Choice Voucher program (24 CFR Part 982).</P>
                <P>
                    <E T="03">Agency form numbers:</E>
                     HUD-52515 (OMB Approval #2577-0169), HUD 50058 (OMB approval #2577-0083), HUD-2993 (OMB Approval #2577-0259), HUD-96010 (OMB Approval #2535-0114), HUD 96011 (OMB approval #2535-0118), HUD-2990, HUD-2991 (OMB Approval #2506-0112) and HUD 2880 (OMB Approval #2510-0011), SF-424 (OMB Approval #0348-0043), SF LLL (OMB Approval #0348-0043).
                </P>
                <P>
                    <E T="03">Members of the Affected Public:</E>
                     Public Housing Agencies.
                </P>
                <P>
                    <E T="03">Estimation of the total number of hours needed to prepare the information collection including number of respondents:</E>
                     The total burden for data collection is estimated at 6,188.45 hours. It is anticipated that approximately 265 PHAs will apply for FUP vouchers each year the program is funded. The estimate of the total annual cost burden to respondents/record keepers resulting from the collection of this information is: 6,188.45 burden hours × $34.34 = $212,511.37; assuming a Manager's hourly rate at the GS-13/Step 1 level.
                </P>
                <P>* Burden hours for forms showing zero burden hours in this collection are reflected in the OMB approval number cited or do not have a reportable burden. The burden hours for this collection is 6,188.45.</P>
                <P>
                    <E T="03">Status of the Proposed Information Collection:</E>
                     Revision of a currently approved 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: October 18, 2011.</DATED>
                    <NAME>Merrie Nichols-Dixon,</NAME>
                    <TITLE>Deputy Director for Office of Policy, Program and  Legislative Initiatives.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27683 Filed 10-25-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-106]</DEPDOC>
                <SUBJECT>Notice of Submission of Proposed Information Collection to OMB, Multifamily Insurance Benefits Claims Package</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>When the terms of a Multifamily contract are breached or when a mortgagee meets conditions stated within the Multifamily contract for an automatic assignment, the holder of the mortgage may file for insurance benefits. To receive these benefits, the mortgagee must prepare and submit to HUD the Multifamily Insurance Benefits Claims Package. HUD uses the information collection to determine the insurance benefits owed to the mortgagee.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments Due Date: November 25, 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 approval Number (2502-0418) and should be sent to: HUD Desk Officer, Office of Management and Budget, New Executive Office Building, Washington, DC 20503; e-mail 
                        <E T="03">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-mail Colette Pollard at 
                        <E T="03">Colette.Pollard@hud.gov;</E>
                         or telephone (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>
                <HD SOURCE="HD1">This Notice Also Lists the Following Information</HD>
                <P>
                    <E T="03">Title of Proposal:</E>
                     Multifamily Insurance Benefits Claims Package.
                </P>
                <P>
                    <E T="03">OMB Approval Number:</E>
                     2502-0418.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     HUD-2741, HUD-2742, HUD-2744-A, HUD-2744-B, HUD-2744-C, HUD-2744-D, HUD-2744-E, HUD-434, HUD-1044-D.
                </P>
                <HD SOURCE="HD1">Description of the Need for the Information and Its Proposed Use</HD>
                <P>When the terms of a Multifamily contract are breached or when a mortgagee meets conditions stated within the Multifamily contract for an automatic assignment, the holder of the mortgage may file for insurance benefits. To receive these benefits, the mortgagee must prepare and submit to HUD the Multifamily Insurance Benefits Claims Package. HUD uses the information collection to determine the insurance benefits owed to the mortgagee.</P>
                <P>
                    <E T="03">Frequency of Submission:</E>
                     On Occasion.
                </P>
                <GPOTABLE COLS="7" OPTS="L1,tp0,i1" CDEF="s100,12C,12C,2,12C,2,12C">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Annual 
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">×</CHED>
                        <CHED H="1">
                            Hours per 
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">=</CHED>
                        <CHED H="1">Burden hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Reporting Burden</ENT>
                        <ENT>150</ENT>
                        <ENT>9</ENT>
                        <ENT> </ENT>
                        <ENT>0.471</ENT>
                        <ENT> </ENT>
                        <ENT>637</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Total Estimated Burden Hours:</E>
                     637.
                </P>
                <P>
                    <E T="03">Status:</E>
                     Revision of a currently approved 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>
                    <PRTPAGE P="66317"/>
                    <DATED>Dated: October 20, 2011.</DATED>
                    <NAME>Colette Pollard,</NAME>
                    <TITLE>Departmental Reports Management Officer, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27662 Filed 10-25-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-105]</DEPDOC>
                <SUBJECT>Notice of Submission of Proposed Information Collection to OMB Energy Efficient Mortgages</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>Lenders provide information required to determine the eligibility of a mortgage to be insured under Section 513 of the Housing and Community Development Act of 1992 (Section 106 of the Energy Policy Act of 1992).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments Due Date:</E>
                         November 25, 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 approval Number (2502-0561) and should be sent to: HUD Desk Officer, Office of Management and Budget, New Executive Office Building, Washington, DC 20503; e-mail 
                        <E T="03">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-mail Colette Pollard at 
                        <E T="03">Colette.Pollard@hud.gov;</E>
                         or telephone (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>
                <HD SOURCE="HD1">This Notice Also Lists the Following Information</HD>
                <P>
                    <E T="03">Title of Proposal:</E>
                     Energy Efficient Mortgages.
                </P>
                <P>
                    <E T="03">OMB Approval Number:</E>
                     2502-0561.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     None.
                </P>
                <HD SOURCE="HD1">Description of the Need for the Information and Its Proposed Use</HD>
                <P>Lenders provide information required to determine the eligibility of a mortgage to be insured under Section 513 of the Housing and Community Development Act of 1992 (Section 106 of the Energy Policy Act of 1992).</P>
                <P>
                    <E T="03">Frequency of Submission:</E>
                     On Occasion.
                </P>
                <GPOTABLE COLS="7" OPTS="L1,tp0,i1" CDEF="s30,12C,12C,2,12C,2,12C">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Annual 
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">×</CHED>
                        <CHED H="1">
                            Hours per 
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">=</CHED>
                        <CHED H="1">Burden hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Reporting Burden</ENT>
                        <ENT>1,066</ENT>
                        <ENT>3.5</ENT>
                        <ENT> </ENT>
                        <ENT>1.133</ENT>
                        <ENT> </ENT>
                        <ENT>4,229</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Total Estimated Burden Hours:</E>
                     4,229.
                </P>
                <P>
                    <E T="03">Status:</E>
                     Revision of a currently approved 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: October 20, 2011.</DATED>
                    <NAME>Colette Pollard,</NAME>
                    <TITLE>Departmental Reports Management Officer, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27664 Filed 10-25-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-107]</DEPDOC>
                <SUBJECT>Notice of Submission of Proposed Information Collection to OMB; Management Reviews of Multifamily Housing Programs</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>HUD staff and Contract Administrators complete the form HUD-9834 during on-site reviews. The information gathered from the form is used to evaluate the quality of management, determine causes of problems, and devise corrective actions to safeguard the Department's financial interest and ensure that tenants are provided with decent, safe, and sanitary housing.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments Due Date:</E>
                         November 25, 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 approval Number (2502-0178) and should be sent to: HUD Desk Officer, Office of Management and Budget, New Executive Office Building, Washington, DC 20503; e-mail 
                        <E T="03">OIRA-Submission@omb.eop.gov fax:</E>
                         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-mail Colette Pollard at 
                        <E T="03">Colette.Pollard@hud.gov;</E>
                         or telephone (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 
                    <PRTPAGE P="66318"/>
                    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>
                <HD SOURCE="HD1">This Notice Also Lists the Following Information</HD>
                <P>
                    <E T="03">Title Of Proposal:</E>
                     Management Reviews of Multifamily Housing Programs.
                </P>
                <P>
                    <E T="03">OMB Approval Number:</E>
                     2502-0178.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     HUD 9834.
                </P>
                <HD SOURCE="HD1">Description of the Need for the Information and its Proposed Use</HD>
                <P>HUD staff and Contract Administrators complete the form HUD-9834 during on-site reviews. The information gathered from the form is used to evaluate the quality of management, determine causes of problems, and devise corrective actions to safeguard the Department's financial interest and ensure that tenants are provided with decent, safe, and sanitary housing.</P>
                <P>
                    <E T="03">Frequency Of Submission:</E>
                     On Occasion.
                </P>
                <GPOTABLE COLS="7" OPTS="L1,tp0,i1" CDEF="s100,12C,12C,2,12C,2,12C">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Annual 
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">×</CHED>
                        <CHED H="1">
                            Hours per 
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">=</CHED>
                        <CHED H="1">Burden hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Reporting Burden</ENT>
                        <ENT>25,649</ENT>
                        <ENT>1</ENT>
                        <ENT> </ENT>
                        <ENT>6.956</ENT>
                        <ENT> </ENT>
                        <ENT>178,423</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Total Estimated Burden Hours:</E>
                     178,423.
                </P>
                <P>
                    <E T="03">Status:</E>
                     Revision of a currently approved 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: October 20, 2011.</DATED>
                    <NAME>Colette Pollard,</NAME>
                    <TITLE> Departmental Reports Management Officer, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27660 Filed 10-25-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-41]</DEPDOC>
                <SUBJECT>Announcement of Funding Awards; Limited English Proficiency Initiative Program (LEPI), Fiscal Year 2010/2011</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Assistant Secretary for Fair Housing and Equal Opportunity, the Department of Housing and Urban Development, 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 Housing and Urban Development Reform Act of 1989, this announcement notifies the public of funding decisions made by the Department for funding under the Notice of Funding Availability (NOFA) for the Limited English Proficiency Initiative (LEPI) Program for Fiscal Year (FY) 2010/2011. This announcement contains the names and addresses of those award recipients selected for funding based on the rating and ranking of all applications and the amount of the awards.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Pamela Walsh, Director, Office of Policy, Legislative Initiatives, and Outreach, Office of Fair Housing and Equal Opportunity, Department of Housing and Urban Development, 451 Seventh Street, SW., Room 5246, Washington, DC 20410. Telephone number (202) 402-7017 (this is not a toll-free number). Persons with hearing or speech impairments may access this number through TTY by calling the toll-free Federal Relay Service at 800-877-8339.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Executive Order 13166 signed in August 2000 requires all federal agencies to improve access to federally conducted and federally assisted programs and activities for persons who, as a result of national origin, are limited in the English proficiency (LEP). Each agency is to examine the services they provide, identify any need for services to those with limited English proficiency (LEP), and develop and implement a system to provide those services so LEP persons can have meaningful access to them. This LEPI NOFA sponsors organizations to help ensure that LEP persons can have meaningful access the Department of Housing and Urban Development's programs, services, and activities.</P>
                <P>The Department published its Limited English Proficiency Initiative (LEPI) NOFA on July 11, 2011, amended July 18, 2011, announcing the availability of $650,000 to go to up to seven organizations to make HUD programs more accessible to LEP persons. This Notice announces six grant awards of approximately $100,000 each and one grant award of $50,000 for organizations to assist locally targeted LEP individuals.</P>
                <P>For the FY 2010/2011 NOFA, the Department reviewed, evaluated, and scored the applications received based on the criteria in the FY 2010/2011 LEPI NOFA. As a result, HUD has decided to fund the applications announced in Appendix A, and in accordance with section 102(a)(4)(C) of the Department of Housing and Urban Development Reform Act of 1989 (103 Stat. 1987, 42 U.S.C. 3545), the Department is hereby publishing details concerning the recipients of funding awards in Appendix A of this document.</P>
                <P>The Catalog of Federal Domestic Assistance Number for currently funded Initiatives under the Limited English Proficiency Initiative Program is 14.421.</P>
                <SIG>
                    <DATED>Dated: October 18, 2011.</DATED>
                    <NAME>John D. Trasviña,</NAME>
                    <TITLE>Assistance Secretary for Fair Housing and Equal Opportunity.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Appendix A</HD>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s100,r50,8,12">
                    <TTITLE>FY 2010/2011—Limited English Proficiency Initiative NOFA</TTITLE>
                    <BOXHD>
                        <CHED H="1">Applicant name </CHED>
                        <CHED H="1">Contact </CHED>
                        <CHED H="1">Region </CHED>
                        <CHED H="1">Award amt.</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Chhaya Community Development Center, 37-43 77th Street, 2nd Floor, Jackson Heights, NY 11372-6629</ENT>
                        <ENT>Seema Agnani 718-478-3848</ENT>
                        <ENT>2 </ENT>
                        <ENT>$100,000.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Equal Rights Center, 11 Dupont Circle NW, Washington, DC 20036</ENT>
                        <ENT>Adriana Lopez 202-234-3062</ENT>
                        <ENT>3 </ENT>
                        <ENT>100,000.00</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="66319"/>
                        <ENT I="01">Southwest Minnesota Housing Partnership, 2401 Broadway Avenue, Suite 4, Slayton, MN 56172-1142</ENT>
                        <ENT>Ali Joens 507-836-1605</ENT>
                        <ENT>5 </ENT>
                        <ENT>100,000.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">International Institute of St. Louis, 3654 S. Grand Street, St. Louis, MO 63118-3404</ENT>
                        <ENT>Suzanne LeLaurin 314-773-9090</ENT>
                        <ENT>7 </ENT>
                        <ENT>99,998.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Lutheran Children and Family Services, 5902 North 5th Street, Philadelphia, PA 19120-1824</ENT>
                        <ENT>Rosemary Bauersmith 215-643-6335</ENT>
                        <ENT>3 </ENT>
                        <ENT>99,101.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kurdish Human Rights Center, 10560 Main Street, Suite 207, Fairfax, VA 22030-7176</ENT>
                        <ENT>Pary Karadaghi 703-385-3806</ENT>
                        <ENT>3 </ENT>
                        <ENT>100,000.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Legal Aid Society of Hawaii, 924 Bethel Street, Honolulu, HI 96813-4304</ENT>
                        <ENT>Elise von Dohlen 808-527-8056</ENT>
                        <ENT>9 </ENT>
                        <ENT>50,000.00</ENT>
                    </ROW>
                </GPOTABLE>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27668 Filed 10-25-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-5569-N-01]</DEPDOC>
                <SUBJECT>Notice of Certain Operating Cost Adjustment Factors for 2012</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Assistant Secretary for Housing—Federal Housing Commissioner, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice establishes operating cost adjustment factors (OCAFs) for project based assistance contracts for eligible multifamily housing projects having an anniversary date on or after February 11, 2012. OCAFs are annual factors used to adjust Section 8 rents renewed under section 524 of the Multifamily Assisted Housing Reform and Affordability Act of 1997 (MAHRA).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Dates:</E>
                         February 11, 2012.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Stan Houle, Housing Program Manager, Office of Housing Assistance and Grant Administration, Department of Housing and Urban Development, 451 7th Street, SW., Washington, DC 20410; telephone number 202-402-2572 (this is not a toll-free number). Hearing- or speech-impaired individuals may access this number through TTY by calling the toll-free Federal Relay Service at 800-877-8339.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. OCAFs</HD>
                <P>Section 514(e)(2) of MAHRA requires HUD to establish guidelines for rent adjustments based on an OCAF. The statute requiring HUD to establish OCAFs for LIHPRHA projects and projects with contract renewals or adjustments under section 524(b)(1)(A) of MAHRA is similar in wording and intent. HUD has therefore developed a single factor to be applied uniformly to all projects utilizing OCAFs as the method by which renewal rents are established or adjusted.</P>
                <P>LIHPRHA projects are low-income housing projects insured by the Federal Housing Administration (FHA). LIHPRHA projects are primarily low-income housing projects insured under section 221(d)(3) below-market interest rate (BMIR) and section 236 of the National Housing Act, respectively. Both categories of projects have low-income use restrictions that have been extended beyond the 20-year period specified in the original documents, and both categories of projects also receive assistance under section 8 of the U.S. Housing Act of 1937 to support the continued low-income use.</P>
                <P>MAHRA gives HUD broad discretion in setting OCAFs—referring, for example, in sections 524(a)(4)(C)(i), 524(b)(1)(A), 524(b)(3)(A) and 524(c)(1) simply to “an operating cost adjustment factor established by the Secretary.” The sole limitation to this grant of authority is a specific requirement in each of the foregoing provisions that application of an OCAF “shall not result in a negative adjustment.” Contract rents are adjusted by applying the OCAF to that portion of the rent attributable to operating expenses exclusive of debt service.</P>
                <P>The OCAFs provided in this notice and applicable to eligible projects having a project based assistance contracts anniversary date of on or after February 11, 2012, are calculated using the same method as those published in HUD's 2011 OCAF notice published on November 8, 2010 (75 FR 68616). Specifically, OCAFs are calculated as the sum of weighted average cost changes for wages, employee benefits, property taxes, insurance, supplies and equipment, fuel oil, electricity, natural gas, and water/sewer/trash using publicly available indices. The weights used in the OCAF calculations for each of the nine cost component groupings are set using current percentages attributable to each of the nine expense categories. These weights are calculated in the same manner as in HUD's November 8, 2010, notice. Average expense proportions were calculated using three years of audited Annual Financial Statements from projects covered by OCAFs. The expenditure percentages for these nine categories have been found to be very stable over time, but using three years of data increases their stability. The nine cost component weights were calculated at the state level, which is the lowest level of geographical aggregation with enough projects to permit statistical analysis. These data were not available for the Western Pacific Islands, so data for Hawaii were used as the best available indicator of OCAFs for these areas.</P>
                <P>The best current price data sources for the nine cost categories were used in calculating annual change factors. State-level data for fuel oil, electricity, and natural gas from Department of Energy surveys are relatively current and continue to be used. Data on changes in employee benefits, insurance, property taxes, and water/sewer/trash costs are only available at the national level. The data sources for the nine cost indicators selected used were as follows:</P>
                <P>
                    • 
                    <E T="03">Labor Costs:</E>
                     First quarter, 2011 Bureau of Labor Statistics (BLS) ECI, Private Industry Wages and Salaries, All Workers (Series ID CIU2020000000000I) at the national level and Private Industry Benefits, All Workers (Series ID CIU2030000000000I) at the national level.
                </P>
                <P>
                    • 
                    <E T="03">Property Taxes:</E>
                     2009-2010 Census Quarterly Summary of State and Local Government Tax Revenue—Table 1 
                    <E T="03">http://www2.census.gov/govs/qtax/2011/q1t1.pdf.</E>
                     Annual property taxes are computed as the total of four quarters of tax receipts. Total annual taxes are then divided by number of households to arrive at average annual tax per household. For 2009, the number of households is taken from the estimates program at the Bureau of the Census. 
                    <E T="03">http://www.census.gov/popest/housing/HU-EST2009.html.</E>
                     At the time 
                    <PRTPAGE P="66320"/>
                    of computation data on the number of households was not yet available for 2010 so the 2009 number was used in its place.
                </P>
                <P>
                    • 
                    <E T="03">Goods, Supplies, Equipment:</E>
                     April 2010 to April 2011 Bureau of Labor Statistics (BLS) Consumer Price Index, All Items Less Food, Energy and shelter  (Series ID CUUR0000SA0L12E) at the national level.
                </P>
                <P>
                    • 
                    <E T="03">Insurance:</E>
                     April 2010 to April 2011 Bureau of Labor Statistic (BLS) Consumer Price Index, Tenants and Household Insurance Index (Series ID CUUR0000SEHD) at the national level.
                </P>
                <P>
                    • 
                    <E T="03">Fuel Oil:</E>
                     Energy Information Agency, 2009 to 2010 Retail Price of No. 2 Fuel Oil to Residential Consumers cents per gallon excluding taxes. Department of Energy multi-state fuel oil grouping averages used for the States with insufficient fuel oil consumption to have separate estimates. 
                    <E T="03">http://www.eia.gov/dnav/pet/pet_sum_mkt_a_EPD2_PRT_dpgal_a.htm</E>
                </P>
                <P>
                    • 
                    <E T="03">Electricity:</E>
                     Energy Information Agency, March 2011 “Electric Power Monthly” report, Table 5.6.B. 
                    <E T="03">http://www.eia.doe.gov/cneaf/electricity/epm/epm_sum.html</E>
                </P>
                <P>
                    • 
                    <E T="03">Natural Gas:</E>
                     Energy Information Agency, Natural Gas, Residential Energy Price, 2009-2010 annual prices in dollars per 1,000 cubic feet at the state level. Due to EIA data quality standards several states were missing data for one or two months in 2010; in these cases, data for these missing months were estimated using data from the surrounding months in 2010 and the relationship between that same month and the surrounding months in 2009. 
                    <E T="03">http://www.eia.doe.gov/dnav/ng/ng_pri_sum_a_EPG0_PRS_DMcf_a.htm</E>
                </P>
                <P>
                    • 
                    <E T="03">Water and Sewer:</E>
                     April 2010 to April 2011 Consumer Price Index, All Urban Consumers, Water and Sewer and Trash Collection Services (Series ID CUUR0000SEHG) at the national level.
                </P>
                <P>The sum of the nine cost component percentage weights equals 100 percent of operating costs for purposes of OCAF calculations. To calculate the OCAFs, state-level cost component weights developed from AFS data are multiplied by the selected inflation factors. For instance, if wages in Virginia comprised 50 percent of total operating cost expenses and increased by 4 percent from 2009 to 2010, the wage increase component of the Virginia OCAF for 2012 would be 2.0 percent (50% * 4%). This 2.0 percent would then be added to the increases for the other eight expense categories to calculate the 2012 OCAF for Virginia. The OCAFs for 2012 are included as an Appendix to this Notice.</P>
                <HD SOURCE="HD1">II. MAHRA and LIHPRHA OCAF Procedures</HD>
                <P>
                    MAHRA, as amended, created the Mark-to-Market Program to reduce the cost of federal housing assistance, enhance HUD's administration of such assistance, and ensure the continued affordability of units in certain multifamily housing projects. Section 524 of MAHRA authorizes renewal of Section 8 project-based assistance contracts for projects without restructuring plans under the Mark-to-Market Program, including projects that are not eligible for a restructuring plan and those for which the owner does not request such a plan. Renewals must be at rents not exceeding comparable market rents except for certain projects. As an example, for Section 8 Moderate Rehabilitation projects, other than single room occupancy projects (SROs) under the McKinney-Vento Homeless Assistance Act (42 U.S.C. 11301 
                    <E T="03">et seq.</E>
                    ), that are eligible for renewal under section 524(b)(3) of MAHRA, the renewal rents are required to be set at the lesser of: (1) The existing rents under the expiring contract, as adjusted by the OCAF; (2) fair market rents (less any amounts allowed for tenant-purchased utilities); or (3) comparable market rents for the market area.
                </P>
                <P>LIHPRHA (see, in particular, section 222(a)(2)(G)(i), 12 U.S.C. 4112 (a)(2)(G) and HUD's regulations at 24 CFR. 248.145(a)(9)) requires that future rent adjustments for LIHPRHA projects be made by applying an annual factor, to be determined by HUD to the portion of project rent attributable to operating expenses for the project and, where the owner is a priority purchaser, to the portion of project rent attributable to project oversight costs.</P>
                <HD SOURCE="HD1">III. Findings and Certifications</HD>
                <HD SOURCE="HD2">Environmental Impact</HD>
                <P>This issuance sets forth rate determinations and related external administrative requirements and procedures that do not constitute a development decision affecting the physical condition of specific project areas or building sites. Accordingly, under 24 CFR 50.19(c)(6), this notice is categorically excluded from environmental review under the National Environmental Policy Act of 1969 (42 U.S.C. 4321).</P>
                <HD SOURCE="HD2">Catalog of Federal Domestic Assistance Number</HD>
                <P>The Catalog of Federal Domestic Assistance Number for this program is 14.187.</P>
                <SIG>
                    <DATED>Dated: October 20, 2011.</DATED>
                    <NAME>Carol J. Galante,</NAME>
                    <TITLE>Acting Assistant Secretary for Housing—Federal Housing Commissioner.</TITLE>
                </SIG>
                <APPENDIX>
                    <HD SOURCE="HED">Appendix</HD>
                    <GPOTABLE COLS="2" OPTS="L2,p1,8/9,i1" CDEF="s50,6">
                        <TTITLE>Operating Cost Adjustment Factors for 2012</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1"> </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Alabama</ENT>
                            <ENT>1.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Alaska</ENT>
                            <ENT>2.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Arizona</ENT>
                            <ENT>1.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Arkansas</ENT>
                            <ENT>1.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">California</ENT>
                            <ENT>2.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Colorado</ENT>
                            <ENT>2.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Connecticut</ENT>
                            <ENT>1.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Delaware</ENT>
                            <ENT>1.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">District of Columbia</ENT>
                            <ENT>1.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Florida</ENT>
                            <ENT>1.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Georgia</ENT>
                            <ENT>1.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Hawaii</ENT>
                            <ENT>4.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Idaho</ENT>
                            <ENT>1.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Illinois</ENT>
                            <ENT>2.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Indiana</ENT>
                            <ENT>1.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Iowa</ENT>
                            <ENT>1.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Kansas</ENT>
                            <ENT>2.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Kentucky</ENT>
                            <ENT>1.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Louisiana</ENT>
                            <ENT>2.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Maine</ENT>
                            <ENT>2.5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Maryland</ENT>
                            <ENT>1.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Massachusetts</ENT>
                            <ENT>1.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Michigan</ENT>
                            <ENT>2.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Minnesota</ENT>
                            <ENT>1.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Mississippi</ENT>
                            <ENT>1.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Missouri</ENT>
                            <ENT>2.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Montana</ENT>
                            <ENT>1.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Nebraska</ENT>
                            <ENT>1.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Nevada</ENT>
                            <ENT>1.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">New Hampshire</ENT>
                            <ENT>2.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">New Jersey</ENT>
                            <ENT>1.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">New Mexico</ENT>
                            <ENT>2.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">New York</ENT>
                            <ENT>2.4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">North Carolina</ENT>
                            <ENT>1.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">North Dakota</ENT>
                            <ENT>2.1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Ohio</ENT>
                            <ENT>1.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Oklahoma</ENT>
                            <ENT>2.2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Oregon</ENT>
                            <ENT>2.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pacific Islands</ENT>
                            <ENT>1.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pennsylvania</ENT>
                            <ENT>2.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Puerto Rico</ENT>
                            <ENT>2.0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rhode Island</ENT>
                            <ENT>1.7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">South Carolina</ENT>
                            <ENT>1.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">South Dakota</ENT>
                            <ENT>2.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Tennessee</ENT>
                            <ENT>1.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Texas</ENT>
                            <ENT>1.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Utah</ENT>
                            <ENT>1.8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Vermont</ENT>
                            <ENT>3.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Virgin Islands</ENT>
                            <ENT>2.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Virginia</ENT>
                            <ENT>1.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Washington</ENT>
                            <ENT>2.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">West Virginia</ENT>
                            <ENT>2.3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Wisconsin</ENT>
                            <ENT>1.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Wyoming</ENT>
                            <ENT>1.6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">U.S. Average</ENT>
                            <ENT>1.8</ENT>
                        </ROW>
                    </GPOTABLE>
                </APPENDIX>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27816 Filed 10-24-11; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="66321"/>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Fish and Wildlife Service</SUBAGY>
                <DEPDOC>[FWS-R4-R-2011-N216;40136-1265-0000-S3]</DEPDOC>
                <SUBJECT>Proposed Establishment of Everglades Headwaters National Wildlife Refuge and Conservation Area; Draft Land Protection Plan and Environmental Assessment</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Fish and Wildlife Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability; extension of comment period.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We, the Fish and Wildlife Service (Service), advise the public that we are extending the public comment period for the proposed establishment of the Everglades Headwaters National Wildlife Refuge (NWR) and Conservation Area. If you have previously submitted comments, please do not resubmit them, because we have already incorporated them in the public record and will fully consider them in our final decision.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>To ensure consideration, please send your written comments by November 25, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Send comments concerning the draft land protection plan and environmental assessment to Everglades Headwaters Proposal, by U.S. mail at U.S. Fish and Wildlife Service, P.O. Box 2683, Titusville, FL 32781-2683, by e-mail at 
                        <E T="03">EvergladesHeadwatersProposal@fws.gov,</E>
                         or to 321/861-1276 (fax). For document availability, see below.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ms. Cheri M. Ehrhardt, Natural Resource Planner, at 321/861-2368 (telephone) or Mr. Charlie Pelizza, Refuge Manager, at 772/562-3909, extension 244 (telephone).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On September 8, 2011, we published a 
                    <E T="04">Federal Register</E>
                     notice (76 FR 55699) announcing the proposed establishment of the Everglades Headwaters NWR and Conservation Area in Polk, Osceola, Highlands, and Okeechobee Counties in central and south Florida in accordance with the National Environmental Policy Act (40 CFR 1506.6 (b)) requirements. We originally opened this comment period on September 8, 2011 (76 FR 55699). For background and more information on the proposed establishment of the Everglades Headwaters NWR and Conservation Area, please see that notice. We are extending the public comment period on the proposed establishment of this refuge and conservation area in response to the high level of interest we have received.
                </P>
                <HD SOURCE="HD1">Document Availability</HD>
                <P>
                    Copies of the draft land protection plan and environmental assessment are available by writing to the U.S. mail address and e-mail address under 
                    <E T="02">ADDRESSES</E>
                     as listed above, or by calling 321/861-0067 (telephone), 321/861-1276 (fax). Alternatively, you may download the document from our Internet Site at 
                    <E T="03">http://www.fws.gov/southeast/evergladesheadwaters/.</E>
                </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 may 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">Authority</HD>
                <P>This notice is published under the authority of the National Wildlife Refuge System Improvement Act of 1997, Public Law 105-57.</P>
                <SIG>
                    <DATED>Dated: October 21, 2011.</DATED>
                    <NAME>Paul Steblein,</NAME>
                    <TITLE>Acting Assistant Director, National Wildlife Refuge System.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27748 Filed 10-24-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-55-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Fish and Wildlife Service</SUBAGY>
                <DEPDOC>[FWS-R1-R-2011-N225; 10137-8555-11RG-8H]</DEPDOC>
                <SUBJECT>Long Range Transportation Plan for Fish and Wildlife Service Lands in Hawai`i, Idaho, Northern Nevada, Oregon, Washington, and the Pacific Island Territories; Correction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Fish and Wildlife Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On October 18, 2011, via a 
                        <E T="04">Federal Register</E>
                         notice, we, the U.S. Fish and Wildlife Service, announced the availability of the final draft Long Range Transportation Plan (LRTP) for our lands in Hawai`i, Idaho, Northern Nevada, Oregon, Washington, and the Pacific Island Territories (the Service's Region 1) for public review and comment. However, in that notice we gave an incorrect contact phone number, which we now correct. Note that if you already submitted a comment, you need not resubmit it.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Please provide your comments by November 17, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The Draft LRTP is available on our Web site at 
                        <E T="03">http://www.fws.gov/pacific/planning/.</E>
                         We also have a limited number of printed and CD-ROM copies of the Draft LRTP. You may request a copy or submit comments by any of the following methods:
                    </P>
                    <P>
                        • 
                        <E T="03">E-mail: fw1LRTPComments@fws.gov.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">U.S. Mail:</E>
                         Jeff Holm, Regional Transportation Coordinator, U.S. Fish and Wildlife Service, 911 NE., 11th Avenue, Portland, OR 97232.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         Attn: Jeff Holm, (503) 231-2364.
                    </P>
                    <P>
                        • 
                        <E T="03">In-Person Viewing or Drop-off:</E>
                         During regular business hours to Jeff Holm, Regional Transportation Coordinator, U.S. Fish and Wildlife Service, 911 NE., 11th Avenue, Portland, OR 97232.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jeff Holm, 503-231-2161.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On October 18, 2011, via a 
                    <E T="04">Federal Register</E>
                     notice (76 FR 64376), we announced the availability of the final draft Long Range Transportation Plan (LRTP) for public review and comment. However, in that notice, we gave an incorrect contact phone number under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    . We now supply the correct phone number, which is 503-231-2161. Note that if you already submitted a comment, you need not resubmit it.
                </P>
                <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>
                <P>For more information about the Draft LRTP, and its mission, goals, and objectives, see our October 18, 2011, notice.</P>
                <SIG>
                    <DATED>Dated: October 20, 2011.</DATED>
                    <NAME>Sara Prigan,</NAME>
                    <TITLE>Federal Register Liaison.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27666 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-55-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="66322"/>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Land Management</SUBAGY>
                <DEPDOC>[LLID9570000.LL14200000.BJ0000]</DEPDOC>
                <SUBJECT>Idaho: Filing of Plats of Survey</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Filing of Plats of Surveys.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Bureau of Land Management (BLM) has officially filed the plats of survey of the lands described below in the BLM Idaho State Office, Boise, Idaho, effective 9 a.m., on the dates specified.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Bureau of Land Management, 1387 South Vinnell Way, Boise, Idaho 83709-1657.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>These surveys were executed at the request of the BLM to meet their administrative needs. The lands surveyed are:</P>
                <P>The plat representing the dependent resurvey of portions of T. 7 S., R. 2 E., T. 8 S., R. 4 E., T. 10 S., R. 3 E., and T. 10 S., R. 4 ., of the Boise Meridian, Idaho, Group Number 1317, was accepted July 22, 2011.</P>
                <P>The plat representing the dependent resurvey of a portion of the north boundary and a portion of the subdivisional lines, and a portion of the boundaries of mineral survey No. 3416 in sections 1, 2, and 3, T. 47 N., R. 4 E., of the Boise Meridian, Idaho, Group Number 1246, was accepted September 16, 2011.</P>
                <P>The plat representing the dependent resurvey of a portion of the subdivisional lines, and a metes-and-bounds survey in sections 5 and 8, T. 11 N., R. 17 E., of the Boise Meridian, Idaho, Group Number 1322, was accepted September 19, 2011.</P>
                <P>These surveys were executed at the request of the Bureau of Indian Affairs to meet their administrative needs. The lands surveyed are:</P>
                <P>The plat representing the dependent resurvey of portions of the 7th Standard Parallel North (north boundary) and subdivisional lines, and the subdivision of sections 3, 11, 14, and 23, T. 35 N., R. 1 E., Boise Meridian, Idaho, Group Number 1233, was accepted July 13, 2011.</P>
                <P>The plat representing the dependent resurvey of portions of the west boundary and subdivisional lines, and the subdivision of secs. 19 and 30, and the metes-and-bounds survey of lots 7, 8, 9, and 10, in sec. 30, T. 46 N., R. 4 W., Boise Meridian, Idaho, Group Number 1299, was accepted July 15, 2011.</P>
                <P>The plat representing the dependent resurvey of a portion of the subdivisional lines, and the subdivision of sec. 25, T. 46 N., R. 5 W., Boise Meridian, Idaho, Group Number 1301, was accepted July 15, 2011.</P>
                <P>The plat representing the dependent resurvey of a portion of the west boundary and a metes-and-bounds survey in section 13, T. 45 N., R. 6 W., of the Boise Meridian, Idaho, Group Number 1256, was accepted September 12, 2011.</P>
                <P>The supplemental plat in 34, T. 37 N., R. 1 E., Boise Meridian, Idaho, Group Number 1346, was prepared to show amended lottings, was accepted September 30, 2011.</P>
                <P>These surveys were executed at the request of the U.S. Forest Service to meet their administrative needs. The lands surveyed are:</P>
                <P>The supplemental plat in sec. 22, T. 54 N., R. 2 W., Boise Meridian, Idaho, Group Number 1364, was prepared to show amended lottings, was accepted September 30, 2011.</P>
                <FP>
                    <E T="02">SUMMARY:</E>
                    The Bureau of Land Management (BLM) will file the plat of survey of the lands described below in the BLM Idaho State Office, Boise, Idaho, 30 days from the date of publication in the 
                    <E T="04">Federal Register</E>
                    . This survey was executed at the request of the U.S. Fish and Wildlife Service to meet certain administrative and management purposes.
                </FP>
                <P>The plats constituting the entire survey record of the survey of certain islands in the Snake River, Tps 1 and 2 N., R. 3 W., T. 2 N., R. 4 W., T. 3 N., R. 4 W., T. 3 N., R. 5 W., and T. 4 N., R. 5 W., Boise Meridian, Idaho, were accepted July 29, 2011.</P>
                <SIG>
                    <DATED> Dated: October 7, 2011.</DATED>
                    <NAME>Bruce E. Ogonowski,</NAME>
                    <TITLE>Acting Chief Cadastral Surveyor for Idaho.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27665 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-GG-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Land Management</SUBAGY>
                <DEPDOC>[LLOR957000-L63100000-HD0000: HAG12-0018]</DEPDOC>
                <SUBJECT>Filing of Plats of Survey: Oregon/Washington</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The plats of survey of the following described lands are scheduled to be officially filed in the Bureau of Land Management Oregon/Washington State Office, Portland, Oregon, 30 days from the date of this publication.</P>
                    <EXTRACT>
                        <HD SOURCE="HD1">Willamette Meridian</HD>
                        <HD SOURCE="HD1">Oregon</HD>
                        <FP SOURCE="FP-1">T. 20 S., R. 4 W., </FP>
                        <FP SOURCE="FP1-2">accepted October 7, 2011.</FP>
                        <FP SOURCE="FP-1">T. 29 S., R. 6 W., </FP>
                        <FP SOURCE="FP1-2">accepted October 7, 2011.</FP>
                        <FP SOURCE="FP-1">T. 29 S., R. 7 W., </FP>
                        <FP SOURCE="FP1-2">accepted October 7, 2011.</FP>
                        <FP SOURCE="FP-1">T. 4 S., R. 2 E., </FP>
                        <FP SOURCE="FP1-2">accepted October 7, 2011.</FP>
                        <FP SOURCE="FP-1">T. 9 S., R. 2 E., </FP>
                        <FP SOURCE="FP1-2">accepted October 7, 2011.</FP>
                        <FP SOURCE="FP-1">T. 4 N., R. 3 W., </FP>
                        <FP SOURCE="FP1-2">accepted October 14, 2011.</FP>
                        <FP SOURCE="FP-1">T. 16 S., R. 1 W., </FP>
                        <FP SOURCE="FP1-2">accepted October 14, 2011.</FP>
                        <FP SOURCE="FP-1">T. 27 S., R. 12 W. </FP>
                        <FP SOURCE="FP1-2">accepted October 14, 2011.</FP>
                        <FP SOURCE="FP-1">T. 38 S., R. 1 W., </FP>
                        <FP SOURCE="FP1-2">accepted October 14, 2011.</FP>
                        <HD SOURCE="HD1">Washington</HD>
                        <FP SOURCE="FP-1">T. 23 N., R. 10 W., </FP>
                        <FP SOURCE="FP1-2">accepted October 14, 2011.</FP>
                    </EXTRACT>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>A copy of the plats may be obtained from the Land Office at the Bureau of Land Management, Oregon/Washington State Office, 333 SW., 1st Avenue, Portland, Oregon 97204, upon required payment. A person or party who wishes to protest against a survey must file a notice that they wish to protest (at the above address) with the Oregon/Washington State Director, Bureau of Land Management, Portland, Oregon.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Kyle Hensley, (503) 808-6124, Branch of Geographic Sciences, Bureau of Land Management, 333 SW., 1st Avenue, Portland, Oregon 97204. Persons who use a telecommunications device for the deaf (TDD) may call the Federal Information Relay Service (FIRS) at 1-800-877-8339 to contact the above individual during normal business hours. The FIRS is available 24 hours a day, 7 days a week, to leave a message or question with the above individual. You will receive a reply during normal business hours.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</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 
                    <PRTPAGE P="66323"/>
                    cannot guarantee that we will be able to do so.
                </P>
                <SIG>
                    <NAME>Mary J.M. Hartel, </NAME>
                    <TITLE>Chief, Chief, Cadastral Surveyor of Oregon/Washington.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27649 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-33-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>National Park Service</SUBAGY>
                <DEPDOC>[NPS-WASO-NRNHL-1011-8618; 2200-3200-665]</DEPDOC>
                <SUBJECT>National Register of Historic Places; Notification of Pending Nominations and Related Actions</SUBJECT>
                <P>Nominations for the following properties being considered for listing or related actions in the National Register were received by the National Park Service before October 1, 2011. Pursuant to section 60.13 of 36 CFR part 60, written comments are being accepted concerning the significance of the nominated properties under the National Register criteria for evaluation. Comments may be forwarded by United States Postal Service, to the National Register of Historic Places, National Park Service, 1849 C St., NW., MS 2280, Washington, DC 20240; by all other carriers, National Register of Historic Places, National Park Service,1201 Eye St., NW., 8th floor, Washington DC 20005; or by fax, 202-371-6447. Written or faxed comments should be submitted by November 10, 2011. 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>
                <SIG>
                    <NAME>J. Paul Loether, </NAME>
                    <TITLE>Chief, National Register of Historic Places, National Historic Landmarks Program.</TITLE>
                </SIG>
                <EXTRACT>
                    <HD SOURCE="HD1">AMERICAN SAMOA</HD>
                    <HD SOURCE="HD1">Eastern District</HD>
                    <FP SOURCE="FP-1">U.S. Naval Station Tutuila Samoa Hydro Electric Plant, Pipeline, and Dam, Off end of Main Rd., Fagatogo, 11000789</FP>
                    <HD SOURCE="HD1">GEORGIA</HD>
                    <HD SOURCE="HD1">Crawford County</HD>
                    <FP SOURCE="FP-1">Hawkins, Col. Benjamin, Gravesite, Benjamin Hawkins Rd., Roberta, 11000790</FP>
                    <HD SOURCE="HD1">KENTUCKY</HD>
                    <HD SOURCE="HD1">Calloway County</HD>
                    <FP SOURCE="FP-1">Murray Woman's Club Clubhouse, The, 704 Vine St., Murray, 11000792</FP>
                    <HD SOURCE="HD1">Kenton County</HD>
                    <FP SOURCE="FP-1">LaSalette Academy, 702 Greenup St., Covington, 11000791</FP>
                    <HD SOURCE="HD1">Laurel County</HD>
                    <FP SOURCE="FP-1">London Downtown Historic District, Main St. between W. 6th &amp; W. 5th Sts., London, 11000793</FP>
                    <HD SOURCE="HD1">Livingston County</HD>
                    <FP SOURCE="FP-1">Livingston County Courthouse and Clerk's Offices, 351 Court St., Smithland, 11000794</FP>
                    <HD SOURCE="HD1">Mercer County</HD>
                    <FP SOURCE="FP-1">Lexington and Cane Run Historic District, E. Lexington &amp; Cane Run Sts., Harrodsburg, 11000795</FP>
                    <FP SOURCE="FP-1">North Main Street Historic District, 105-414 N. Main St., 109 W. Lexington, 101 W. Broadway, 163 E. Broadway, Harrodsburg, 11000796</FP>
                    <FP SOURCE="FP-1">Baldwin's Tourist Court Residence—Office, 321 W. Stephen Foster Ave., Bardstown, 11000797</FP>
                    <FP SOURCE="FP-1">Kurtz Restaurant and Bardstown—Parkview Motel—Office, 418 E. Stephen Foster Ave., Bardstown, 11000798</FP>
                    <FP SOURCE="FP-1">Old Kentucky Home Motel, 414 Stephen Foster Ave., Bardstown, 11000799</FP>
                    <FP SOURCE="FP-1">Wilson Motel, 530 N. 3rd St., Bardstown, 11000800</FP>
                    <HD SOURCE="HD1">Todd County</HD>
                    <FP SOURCE="FP-1">Guthrie Historic District, Roughly bounded by Ewing, Park &amp; Cherry Sts., Guthrie, 11000801</FP>
                    <HD SOURCE="HD1">Warren County</HD>
                    <FP SOURCE="FP-1">Hardcastle Store, The, 7286 Cemetery Rd., Bowling Green, 11000802</FP>
                    <HD SOURCE="HD1">Washington County</HD>
                    <FP SOURCE="FP-1">Springfield Main Street Historic District, Roughly Commercial Ave. to College St. &amp; McCord, High Sts. to E. Depot St., Springfield, 11000803</FP>
                    <HD SOURCE="HD1">LOUISIANA</HD>
                    <HD SOURCE="HD1">Orleans Parish</HD>
                    <FP SOURCE="FP-1">Lykes Brothers Steamship Company Historic District, 1770, 1744-46 Tchoupitoulas St., New Orleans, 11000804</FP>
                    <HD SOURCE="HD1">NEW YORK</HD>
                    <HD SOURCE="HD1">Monroe County</HD>
                    <FP SOURCE="FP-1">Brockport Central Rural High School, 40 Allen St., Brockport, 11000805</FP>
                    <HD SOURCE="HD1">TENNESSEE</HD>
                    <HD SOURCE="HD1">Davidson County</HD>
                    <FP SOURCE="FP-1">Park—Elkins Historic District, Roughly along Park &amp; Elkins between 42nd &amp; 50th Aves., Nashville, 11000806</FP>
                    <HD SOURCE="HD1">Lincoln County</HD>
                    <FP SOURCE="FP-1">Whitaker—Motlow House, 740 Lynchburg Hwy., Mulberry, 11000807</FP>
                    <HD SOURCE="HD1">Sullivan County</HD>
                    <FP SOURCE="FP-1">Piney Flats Historic District, Main, McKamey, &amp; Methodist Church Sts. &amp; parts of Tank Hill, Piney Flats, Austin Springs &amp; Mountain View Rds., Piney Flats, 11000808</FP>
                    <HD SOURCE="HD1">Washington County</HD>
                    <FP SOURCE="FP-1">Johnson City Country Club, 1901 E. Unaka Ave., Johnson City, 11000809</FP>
                    <HD SOURCE="HD1">WISCONSIN</HD>
                    <HD SOURCE="HD1">Ozaukee County</HD>
                    <FP SOURCE="FP-1">ISLAND CITY (schooner) Shipwreck, (Great Lakes Shipwreck Sites of Wisconsin MPS) 9 mi. SE. of Port Washington in Lake Michigan, Mequon, 11000810</FP>
                    <HD SOURCE="HD1">Sheboygan County</HD>
                    <FP SOURCE="FP-1">WALTER B. ALLEN (canaller) Shipwreck, (Great Lakes Shipwreck Sites of Wisconsin MPS) 7 mi. NE. of Sheboygan in Lake Michigan, Mosel, 11000811</FP>
                    <P>A request for REMOVAL has been made for the following resources:</P>
                    <HD SOURCE="HD1">TENNESSEE</HD>
                    <HD SOURCE="HD1">Williamson County</HD>
                    <FP SOURCE="FP-1">
                        Lamb—Stevens House, (Williamson County MRA) Burke Hollow Rd. 1
                        <FR>1/2</FR>
                         mi. E of Wilson Pike, Franklin, 88000299
                    </FP>
                    <FP SOURCE="FP-1">
                        Russwurm, John S., House, (Williamson County MRA) Spann Town Rd. 
                        <FR>1/2</FR>
                         mi. E of US Alt. 41, Triune, 88000349
                    </FP>
                </EXTRACT>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27640 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4312-51-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Office of Surface Mining Reclamation and Enforcement</SUBAGY>
                <SUBJECT>Notice of Proposed Information Collection</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Surface Mining Reclamation and Enforcement.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">Summary:</HD>
                    <P>In compliance with the Paperwork Reduction Act of 1995, the Office of Surface Mining Reclamation and Enforcement (OSM) is announcing that the information collection request related to the certification of blasters in Federal program states and on Indian lands, and Form OSM-74, has been forwarded to the Office of Management and Budget (OMB) for review and reauthorization. The information collection package was previously approved and assigned clearance number 1029-0083. This notice describes the nature of the information collection activity and the expected burdens and costs.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        OMB has up to 60 days to approve or disapprove the information collection but may respond after 30 
                        <PRTPAGE P="66324"/>
                        days. Therefore, public comments should be submitted to OMB by November 25, 2011, in order to be assured of consideration.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit comments to the Office of Information and Regulatory Affairs, Office of Management and Budget, 
                        <E T="03">Attention:</E>
                         Department of the Interior Desk Officer, by telefax at (202) 395-5806 or via e-mail to 
                        <E T="03">OIRA_Docket@omb.eop.gov.</E>
                         Also, please send a copy of your comments to John Trelease, Office of Surface Mining Reclamation and Enforcement, 1951 Constitution Ave., NW., Room 203—SIB, Washington, DC 20240, or electronically to 
                        <E T="03">jtrelease@osmre.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        To receive a copy of the information collection request contact John Trelease at (202) 208-2783, or electronically at 
                        <E T="03">jtrelease@osmre.gov.</E>
                         You may also review this collection request by going to 
                        <E T="03">http://www.reginfo.gov</E>
                         (Information Collection Review, Currently Under Review, Agency is Department of the Interior, DOI-OSMRE).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Office of Management and Budget (OMB) regulations at 5 CFR 1320, which implement provisions of the Paperwork Reduction Act of 1995 (Pub. L. 104-13), require that interested members of the public and affected agencies have an opportunity to comment on information collection and recordkeeping activities [see 5 CFR 1320.8(d)]. OSM has submitted a request to OMB to renew its approval for the collection of information for 30 CFR 955 and the Form OSM-74, Certification of Blasters in Federal program states and on Indian lands. OSM is requesting a 3-year term of approval for these information collection activities.</P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB control number. The OMB control number for this collection of information is listed in 30 CFR 955.10 and on the Form OSM-74, which is 1029-0083.</P>
                <P>
                    As required under 5 CFR 1320.8(d), a 
                    <E T="04">Federal Register</E>
                     notice soliciting comments on the collection of information was published on June 28, 2011 (76 FR 37829). No comments were received from that notice. This notice provides the public with an additional 30 days in which to comment on the following information collection activity:
                </P>
                <P>
                    <E T="03">Title:</E>
                     30 CFR 955—Certification of Blasters in Federal Program States and on Indian Lands.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1029-0083.
                </P>
                <P>
                    <E T="03">Summary:</E>
                     This information is being collected to ensure that the applicants for blaster certification are qualified. This information, with blasting tests, will be used to determine the eligibility of the applicant. The affected public will be blasters who want to be certified by the Office of Surface Mining Reclamation and Enforcement to conduct blasting on Indian lands or in Federal program states.
                </P>
                <P>
                    <E T="03">Bureau Form Number:</E>
                     OSM-74.
                </P>
                <P>
                    <E T="03">Frequency of Collection:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     Individuals intent on being certified as blasters in Federal program states and on Indian lands.
                </P>
                <P>
                    <E T="03">Total Annual Responses:</E>
                     44 blasters.
                </P>
                <P>
                    <E T="03">Total Annual Burden Hours:</E>
                     110 hours.
                </P>
                <P>
                    <E T="03">Total Annual Non-Wage Burden Cost:</E>
                     $3,782.
                </P>
                <P>
                    Send comments on the need for the collection of information for the performance of the functions of the agency; the accuracy of the agency's burden estimates; ways to enhance the quality, utility and clarity of the information collection; and ways to minimize the information collection burden on respondents, such as use of automated means of collection of the information, to the addresses listed under 
                    <E T="02">ADDRESSES</E>
                    . Please refer to OMB control number 1029-0083 in your correspondence.
                </P>
                <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>
                <SIG>
                    <DATED>Dated: October 19, 2011.</DATED>
                    <NAME>John A. Trelease, </NAME>
                    <TITLE>Acting Chief, Division of Regulatory Support.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27401 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-05-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N"> DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>Notice Pursuant to the National Cooperative Research and Production Act of 1993—Advanced Media Workflow Association, Inc.</SUBJECT>
                <P>
                    Notice is hereby given that, on September 26, 2011, pursuant to Section 6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (“the Act”), Advanced Media Workflow Association, Inc. has filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing changes in its membership. The notifications were filed for the purpose of extending the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances. Specifically, Isilon Systems, Inc., Seattle, WA; Panasonic AVC Networks Company, Kadoma City, Osaka, JAPAN; VSN Video Steam Networks, S.L., Barcelona, SPAIN; Yangaroo, Inc., Toronto, Ontario, CANADA; Patrick Cusack (individual member), Los Angeles, CA; and James Trainor (individual member), Kanata, Ontario, CANADA, have been added as parties to this venture.
                </P>
                <P>Also, Chime Media, Weston, VA; E!Entertainment, Los Angeles, CA; and MAGIX AG, Berlin, GERMANY, have withdrawn as parties to this venture.</P>
                <P>No other changes have been made in either the membership or planned activity of the group research project. Membership in this group research project remains open, and Advanced Media Workflow Association, Inc. intends to file additional written notifications disclosing all changes in membership.</P>
                <P>
                    On March 28, 2000, Advanced Media Workflow Association, Inc. filed its original notification pursuant to Section 6(a) of the Act. The Department of Justice published a notice in the 
                    <E T="04">Federal Register</E>
                     pursuant to Section 6(b) of the Act on June 29, 2000 (65 FR 40127).
                </P>
                <P>
                    The last notification was filed with the Department on June 23, 2011. A notice was published in the 
                    <E T="04">Federal Register</E>
                     pursuant to Section 6(b) of the Act on July 20, 2011 (76 FR 43347).
                </P>
                <SIG>
                    <NAME>Patricia A. Brink,</NAME>
                    <TITLE>Director of Civil Enforcement, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27399 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-11-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S"> DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT> Notice Pursuant to the National Cooperative Research and Production Act of 1993—Cooperative Research Group on Nasgro Development and Support</SUBJECT>
                <P>
                    Notice is hereby given that, on October 3, 2011, pursuant to Section 6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (“the Act”), Southwest Research Institute—
                    <PRTPAGE P="66325"/>
                    Cooperative Research Group on NASGRO Development and Support (“NASGRO”) has filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing changes in its membership and period of performance. The notifications were filed for the purpose of extending the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances. Specifically, Alcoa Technical Center, New York, NY; Honda R&amp;D Co., Ltd., Saitama, JAPAN; Space Exploration Technologies Corp., Hawthorne, CA; United Launch Alliance, Littleton, CO; Agusta Westland, Casina Costa di Samarate, ITALY; and Mitsubishi Heavy Industries, Ltd., Nagoya, JAPAN, have been added as parties to this venture. Additionally, the period of performance has been extended to June 30, 2013.
                </P>
                <P>No other changes have been made in either the membership or planned activity of the group research project. Membership in this group research project remains open, and NASGRO intends to file additional written notifications disclosing all changes in membership.</P>
                <P>
                    On October 3, 2001, NASGRO filed its original notification pursuant to Section 6(a) of the Act. The Department of Justice published a notice in the 
                    <E T="04">Federal Register</E>
                     pursuant to Section 6(b) of the Act on January 22, 2002 (67 FR 2910).
                </P>
                <P>
                    The last notification was filed with the Department on July 22, 2008. A notice was published in the 
                    <E T="04">Federal Register</E>
                     pursuant to Section 6(b) of the Act on August 18, 2008 (73 FR 48242).
                </P>
                <SIG>
                    <NAME>Patricia A. Brink,</NAME>
                    <TITLE>Director of Civil Enforcement, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27400 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-11-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S"> DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Antitrust Division</SUBAGY>
                <SUBJECT>Notice Pursuant to the National Cooperative Research and Production Act of 1993—Cooperative Research Group on Development of a Predictive Model for Corrosion-Fatigue of Materials in Sour Environment</SUBJECT>
                <P>
                    Notice is hereby given that, on September 26, 2011, pursuant to Section 6(a) of the National Cooperative Research and Production Act of 1993, 15 U.S.C. 4301 
                    <E T="03">et seq.</E>
                     (“the Act”), Southwest Research Institute—Cooperative Research Group on Development of a Predictive Model for Corrosion-Fatigue of Materials in Sour Environment (“Model-CFM”) has filed written notifications simultaneously with the Attorney General and the Federal Trade Commission disclosing changes in its membership. The notifications were filed for the purpose of extending the Act's provisions limiting the recovery of antitrust plaintiffs to actual damages under specified circumstances. Specifically, Shell Global Solutions US Inc., Houston, TX, has been added as a party to this venture.
                </P>
                <P>No other changes have been made in either the membership or planned activity of the group research project. Membership in this group research project remains open, and Model-CFM intends to file additional written notifications disclosing all changes in membership.</P>
                <P>
                    On May 17, 2011, Model-CFM filed its original notification pursuant to Section 6(a) of the Act. The Department of Justice published a notice in the 
                    <E T="04">Federal Register</E>
                     pursuant to Section 6(b) of the Act on July 7, 2011 (76 FR 39901).
                </P>
                <SIG>
                    <NAME>Patricia A. Brink,</NAME>
                    <TITLE>Director of Civil Enforcement, Antitrust Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27398 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-11-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Federal Bureau of Investigation</SUBAGY>
                <DEPDOC>[OMB Number 1110-New]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection, Comments Requested; E-FOIA</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>60-day notice of information collection under review.</P>
                </ACT>
                <P>The Department of Justice, Federal Bureau of Investigation, Records Management Division Record Information Dissemination Section (RIDS) will be submitting the following information collection request to the Office of Management and Budget (OMB) for review and clearance in accordance with established review  procedures of the Paperwork Reduction Act of 1995. The proposed information collection is published to obtain comments from the public and affected agencies. Comments are encouraged and will be accepted until December 27, 2011. This process is conducted in accordance with 5 CFR 1320.10.</P>
                <P>
                    Written comments concerning this information collection should be sent to the Office of Information and Regulatory Affairs, Office of Management and Budget, Attn: DOJ Desk Officer. The best way to ensure your comments are received is to e-mail them to 
                    <E T="03">oira_submission@omb.eop.gov</E>
                     or fax them to 202-395-7285. All comments should reference the 8 digit OMB number for the collection or the title of the collection. If you have questions concerning the collection, please call Jason Combs at 540-868-4995, or the DOJ Desk Officer at 202-395-3176.
                </P>
                <P>Written comments and suggestions from the public and affected agencies concerning the proposed collection of information are encouraged. Comments should address one or more of the following four points:</P>
                <P>(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;</P>
                <P>(2) Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
                <P>(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 through the use of appropriate automated, electronic, mechanical, or other technological collection techniques of other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses.
                </P>
                <HD SOURCE="HD1">Overview of This Information Collection:</HD>
                <P>
                    (1) 
                    <E T="03">Type of information collection:</E>
                     Revision of a currently approved collection.
                </P>
                <P>
                    (2) 
                    <E T="03">The title of the form/collection:</E>
                     E-FOIA Submission Form.
                </P>
                <P>
                    (3) 
                    <E T="03">The agency form number, if any, and the applicable component of the department sponsoring the collection:</E>
                     Records Management Division/Record Information Dissemination Section, Federal Bureau of Investigation, Department of Justice.
                </P>
                <P>
                    (4) 
                    <E T="03">Affected public who will be asked or required to respond, as well as a brief abstract:</E>
                </P>
                <P>
                    <E T="03">Primary:</E>
                     FOIA requesters (general public, educational institutions, commercial requesters 
                    <E T="03">etc</E>
                    ).
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The Record/Information Dissemination Section (RIDS) effectively plans, develops, directs, and manages responses to requests for access to FBI records and information. The requests and disclosure comply with the Freedom of Information and Privacy Acts (Title 5, United States Code, Sections 552 and 552a) and the Freedom 
                    <PRTPAGE P="66326"/>
                    of Information Act Executive Order 13392, as well as the Classified National Security Information Executive Order 13526, other Presidential, Attorney General, and FBI policies, procedures, and mandates; judicial decisions; and Congressional directives.
                </P>
                <P>
                    (5) 
                    <E T="03">An estimate of the total number of respondents and the amount of time estimated for an average respondent to respond:</E>
                     Of the approximately 18,445 government entities that are eligible to submit cases, it is estimated that twenty to thirty percent will actually submit cases to RMD/RIDS. The time burden of the respondents is less than 15 minutes per form.
                </P>
                <P>
                    (6) 
                    <E T="03">An estimate of the total public burden (in hours) associated with this collection:</E>
                     There are approximately 1,350 hours, annual burden, associated with this information collection.
                </P>
                <P>
                    <E T="03">If additional information is required contact:</E>
                     Jerri Murray, Department Clearance Officer, Policy and Planning Staff, Justice Management Division, United States Department of Justice, 145 N Street, NE., Room 2E-508, Washington, DC 20530.
                </P>
                <SIG>
                    <NAME>Jerri Murray,</NAME>
                    <TITLE>Department Clearance Officer, PRA, United States Department of Justice.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27605 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Federal Bureau of Investigation</SUBAGY>
                <SUBJECT>Meeting of the Compact Council for the National Crime Prevention and Privacy Compact</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Bureau of Investigation.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Meeting notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The purpose of this notice is to announce a meeting of the National Crime Prevention and Privacy Compact Council (Council) created by the National Crime Prevention and Privacy Compact Act of 1998 (Compact). Thus far, the Federal Government and 29 states are parties to the Compact which governs the exchange of criminal history records for licensing, employment, and similar purposes. The Compact also provides a legal framework for the establishment of a cooperative federal-state system to exchange such records.</P>
                    <P>The United States Attorney General appointed 15 persons from state and federal agencies to serve on the Council. The Council will prescribe system rules and procedures for the effective and proper operation of the Interstate Identification Index system for noncriminal justice purposes.</P>
                    <P>
                        <E T="03">Matters for discussion are expected to include:</E>
                    </P>
                    <P>(1) Changes to the Security and Management Control Outsourcing Standards;</P>
                    <P>(2) National Fingerprint File (NFF) State Audit Criteria Changes; and</P>
                    <P>(3) Guiding principle documents for privacy during the fingerprint-based background check process.</P>
                    <P>The meeting will be open to the public on a first-come, first-seated basis. Any member of the public wishing to file a written statement with the Council or wishing to address this session of the Council should notify the Federal Bureau Of Investigation (FBI) Compact Officer, Mr. Gary S. Barron at (304) 625-2803, at least 24 hours prior to the start of the session. The notification should contain the requestor's name and corporate designation, consumer affiliation, or government designation, along with a short statement describing the topic to be addressed and the time needed for the presentation. Requesters will ordinarily be allowed up to 15 minutes to present a topic.</P>
                </SUM>
                <PREAMHD>
                    <HD SOURCE="HED">DATES AND TIMES:</HD>
                    <P> The Council will meet in open session from 9 a.m. until 5 p.m., on December 08-09, 2011.</P>
                </PREAMHD>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meeting will take place at the Hyatt Regency Albuquerque, 330 Tijeras Avenue NW., Albuquerque, New Mexico, telephone (505) 842-1234.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Inquiries may be addressed to Mr. Gary S. Barron, FBI Compact Officer, Compact Council Office, Module D3, 1000 Custer Hollow Road, Clarksburg, West Virginia 26306, telephone (304) 625-2803, facsimile (304) 625-2868.</P>
                    <SIG>
                        <DATED>Dated: October 11, 2011.</DATED>
                        <NAME>Kimberly J. Del Greco,</NAME>
                        <TITLE>Section Chief, Biometric Services Section, Criminal Justice Information, Services Division, Federal Bureau of Investigation.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27546 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-02-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <SUBJECT>Agency Information Collection Activities; Submission for OMB Review; Comment Request; Well-Being Supplement to the American Time Use Survey</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Department of Labor (DOL) is submitting the Bureau of Labor Statistics (BLS) sponsored information collection request (ICR) titled, “Well-being Supplement to the American Time Use Survey,” to the Office of Management and Budget (OMB) for review and approval for use in accordance with the Paperwork Reduction Act (PRA) of 1995 (44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                        ).
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments on or before November 25, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        A copy of this ICR with applicable supporting documentation; including a description of the likely respondents, proposed frequency of response, and estimated total burden may be obtained from the 
                        <E T="03">RegInfo.go</E>
                        v Web site, 
                        <E T="03">http://www.reginfo.gov/public/do/PRAMain,</E>
                         on the day following publication of this notice or by contacting Michel Smyth by telephone at 202-693-4129 (this is not a toll-free number) or sending an e-mail to 
                        <E T="03">DOL_PRA_PUBLIC@dol.gov.</E>
                    </P>
                    <P>
                        Submit comments about this request to the Office of Information and Regulatory Affairs, 
                        <E T="03">Attn:</E>
                         OMB Desk Officer for the Department of Labor, Bureau of Labor Statistics (BLS), Office of Management and Budget, Room 10235, Washington, DC 20503, 
                        <E T="03">Telephone:</E>
                         202-395-6929/Fax: 202-395-6881 (these are not toll-free numbers), e-mail: 
                        <E T="03">OIRA_submission@omb.eop.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION: </HD>
                    <P>
                        Contact Michel Smyth by telephone at 202-693-4129 (this is not a toll-free number) or by e-mail at 
                        <E T="03">DOL_PRA_PUBLIC@dol.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This ICR seeks approval for a new information collection. The American Time Use Survey (ATUS) is the first national Federally administered continuous survey on time use in the United States. The ATUS measures, for example, time spent with children, working, sleeping, or doing leisure activities. The Well-being Module questions, if approved, would be asked immediately after the ATUS and would follow up on some of the information ATUS respondents provide in their time diary. The Well-being Module would collect information about how people experience their time, specifically how happy, tired, sad, stressed, and in pain they felt the day before the interview. Respondents would be asked these questions about three randomly selected activities from the activities reported in the ATUS time diary. The time diary refers to the core part of the ATUS, in which respondents report the activities they did from 4 a.m. on the day before the interview to 4 a.m. on the day of the interview. A few activities, such as sleeping and private 
                    <PRTPAGE P="66327"/>
                    activities, will never be selected. The module also would collect data on whether people were interacting with anyone while doing the selected activities and how meaningful the activities were to them. Some general health questions, a question about overall life satisfaction, and a question about respondents' overall emotional experience the day before also would be asked. The proposed Well-being Module is nearly identical to a module that was collected in 2010 under the ATUS, approved under OMB Number (1220-0175).
                </P>
                <P>Data from the proposed Wellbeing Module will support the BLS mission of providing relevant information on economic and social issues. The data also will closely support the mission of the module sponsor, the National Institute on Aging (NIA) of the National Institutes of Health, to improve the health and well-being of older Americans.</P>
                <P>
                    This information collection is subject to the PRA. A Federal agency generally cannot conduct or sponsor a collection of information, and the public is generally not required to respond to an information collection, unless it is approved by the OMB under the PRA and displays a currently valid OMB Control Number. In addition, notwithstanding any other provisions of law, no person shall generally be subject to penalty for failing to comply with a collection of information if the collection of information does not display a valid OMB Control Number. 
                    <E T="03">See</E>
                     5 CFR 1320.5(a) and 1320.6. For additional information, see the related notice published in the 
                    <E T="04">Federal Register</E>
                     on July 13, 2011 (76 FR 41302).
                </P>
                <P>
                    Interested parties are encouraged to send comments to the OMB, Office of Information and Regulatory Affairs at the address shown in the 
                    <E T="02">ADDRESSES</E>
                     section within 30 days of publication of this notice in the 
                    <E T="04">Federal Register</E>
                    . In order to help ensure appropriate consideration, comments should reference OMB ICR Reference Number 201108-1220-001. The OMB is particularly interested in comments that:
                </P>
                <P>• Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>• Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
                <P>• Enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>• Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, e.g., permitting electronic submission of responses.</P>
                <P>
                    <E T="03">Agency:</E>
                     Bureau of Labor Statistics (BLS).
                </P>
                <P>
                    <E T="03">Title of Collection:</E>
                     Well-being Supplement to the American Time Use Survey.
                </P>
                <P>
                    <E T="03">OMB ICR Reference Number:</E>
                     201108-1220-001.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals or Households.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Respondents:</E>
                     12,800.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Responses:</E>
                     12,800.
                </P>
                <P>
                    <E T="03">Total Estimated Annual Burden Hours:</E>
                     1067.
                </P>
                <P>
                    <E T="03">Total Estimated Annual Other Costs Burden:</E>
                     $0.
                </P>
                <SIG>
                    <DATED>Dated: October 20, 2011.</DATED>
                    <NAME>Michel Smyth,</NAME>
                    <TITLE>Departmental Clearance Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27699 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-24-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Employment and Training Administration</SUBAGY>
                <DEPDOC>[TA-W-80,185]</DEPDOC>
                <SUBJECT>Iron Mountain Information Management, Inc., Corporate Service Group, Information Technology (IT) Division, Including On-Site Leased Workers From TEK Systems, Professional Alternative, Randstad US/Sapphire Technologies, Spherion Staffing Services/Technisource, Manpower, Advantage (Formerly Known as TAC), and Mccallion Boston, Massachusetts, and Including Off-Site Workers From California, Florida, Louisiana, Massachusetts, Michigan, Missouri, North Carolina, New Jersey, Nevada, Oregon, Pennsylvania, Texas, Vermont and Washington Reporting to Boston, Massachusetts; Amended Certification Regarding Eligibility To Apply for Worker Adjustment Assistance and Alternative Trade Adjustment Assistance</SUBJECT>
                <P>
                    In accordance with Section 223 of the Trade Act of 1974 (19 U.S.C. 2273), and Section 246 of the Trade Act of 1974 (26 U.S.C. 2813), as amended, the Department of Labor issued a Certification of Eligibility to Apply for Worker Adjustment Assistance and Alternative Trade Adjustment Assistance on September 1, 2011, applicable to workers of Iron Mountain Information Management, Inc., Corporate Service Group, Information Technology (IT) Division, including on-site leased workers from TEK Systems, Professional Alternative, Randstad US/Sapphire Technologies, Spherion Staffing Services/Technisource and Manpower, Boston, Massachusetts and including off-site workers from California, Florida, Louisiana, Massachusetts, Michigan, Missouri, North Carolina, New Jersey, Nevada, Oregon, Pennsylvania, Texas, Vermont and Washington reporting to Boston, Massachusetts. The workers are engaged in activities related to the production of digital imaging software. The notice was published in the 
                    <E T="04">Federal Register</E>
                     on September 19, 2011 (76 FR 58046).
                </P>
                <P>At the request of the State agency, the Department reviewed the certification for workers of the subject firm. New information shows that workers leased from Advantage (formerly known as TAC) and McCallion Staffing were employed on-site at the Boston, Massachusetts location of Iron Mountain Information Management, Inc., Corporate Service Group, Information Technology (IT) Division.</P>
                <P>The Department has determined that these workers were sufficiently under the control of Iron Mountain Information Management, Inc., Corporate Service Group, Information Technology (IT) Division be considered leased workers.</P>
                <P>The intent of the Department's certification is to include all workers of the subject firm adversely affected by actual/likely increase in imports following a shift abroad.</P>
                <P>Based on these findings, the Department is amending this certification to include workers leased from Advantage (formerly known as TAC), and McCallion working on-site at the Boston, Massachusetts location of the subject firm.</P>
                <P>The amended notice applicable to TA-W-80,185 is hereby issued as follows:</P>
                <EXTRACT>
                    <P>
                        All workers of Iron Mountain Management, Inc., Corporate Service Group, Information Technology (IT) Division, including on-site leased workers from TEK Systems, Professional Alternative, Randstad US/Sapphire Technologies, Spherion Staffing Services/Technisource, Manpower Advantage (formerly known as TAC), and McCallion, Boston, Massachusetts including off-site workers from California, Florida, Louisiana, Massachusetts, Michigan, 
                        <PRTPAGE P="66328"/>
                        Missouri, North Carolina, New Jersey, Nevada, Oregon, Pennsylvania, Texas, Vermont and Washington reporting to Boston, Massachusetts, who became totally or partially separated from employment on or after May 17, 2010, through September 1, 2013, are eligible to apply for adjustment assistance under Section 223 of the Trade Act of 1974, and are also eligible to apply for alternative trade adjustment assistance under Section 246 of the Trade Act of 1974.
                    </P>
                </EXTRACT>
                <SIG>
                    <DATED>Signed at Washington, DC, this 13th day of October 2011.</DATED>
                    <NAME>Elliott S. Kushner,</NAME>
                    <TITLE>Certifying Officer, Office of Trade Adjustment Assistance.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27703 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE ;P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Employment and Training Administration</SUBAGY>
                <DEPDOC>[TA-W-80,110]</DEPDOC>
                <SUBJECT>Callaway Golf Ball Operations, Inc., Including On-Site Leased Workers From Reliable Temp Services, Inc., Johnson &amp; Hill Staffing and Apollo Security, Chicopee, MA; Amended Certification Regarding Eligibility To Apply for Worker Adjustment Assistance and Alternative Trade Adjustment Assistance</SUBJECT>
                <P>
                    In accordance with Section 223 of the Trade Act of 1974 (19 U.S.C. 2273), and Section 246 of the Trade Act of 1974 (26 U.S.C. 2813), as amended, the Department of Labor issued a Certification of Eligibility to Apply for Worker Adjustment Assistance and Alternative Trade Adjustment Assistance on June 24, 2011, applicable to workers of Callaway Golf Ball Operations, Inc., including on-site leased workers from Reliable Temp Services, Inc., and Johnson and Hill Staffing, Chicopee, Massachusetts. The workers are engaged in activities related to the production of golf balls. The notice was published in the 
                    <E T="04">Federal Register</E>
                     on July 8, 2011 (76 FR 40401).
                </P>
                <P>At the request of the State agency, the Department reviewed the certification for workers of the subject firm. New information shows that workers leased from Apollo Security were employed on-site at the Chicopee, Massachusetts location of Callaway Golf Ball Operations, Inc. The Department has determined that these workers were sufficiently under the control of Callaway Golf Ball Operations, Inc. to be considered leased workers.</P>
                <P>The intent of the Department's certification is to include all workers of the subject firm adversely affected by increased company imports.</P>
                <P>Based on these findings, the Department is amending this certification to include workers leased from Apollo Security working on-site at the Chicopee, Massachusetts location of the subject firm.</P>
                <P>The amended notice applicable to TA-W-80,110 is hereby issued as follows:</P>
                <EXTRACT>
                    <P>All workers of Callaway Golf Ball Operations, Inc., including on-site leased workers from Reliable Temp Services, Inc., Johnson &amp; Hill Staffing and Apollo Security, Chicopee, Massachusetts, who became totally or partially separated from employment on or after July 1, 2011, through June 24, 2013, are eligible to apply for adjustment assistance under Section 223 of the Trade Act of 1974, and are also eligible to apply for alternative trade  adjustment assistance under Section 246 of the Trade Act of 1974.</P>
                </EXTRACT>
                <SIG>
                    <DATED>Signed at Washington, DC this 12th day of October, 2011.</DATED>
                    <NAME>Del Min Amy Chen,</NAME>
                    <TITLE>Certifying Officer, Office of Trade Adjustment Assistance.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27702 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-FN-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Employment and Training Administration</SUBAGY>
                <SUBJECT>Notice of Determinations Regarding Eligibility To Apply for Worker Adjustment Assistance and Alternative Trade Adjustment Assistance</SUBJECT>
                <P>In accordance with Section 223 of the Trade Act of 1974, as amended (19 U.S.C. 2273) the Department of Labor herein presents summaries of determinations regarding eligibility to apply for trade adjustment assistance for workers (TA-W) number and alternative trade adjustment assistance (ATAA) by (TA-W) number issued during the period of October 11, 2011 through October 14, 2011.</P>
                <P>In order for an affirmative determination to be made for workers of a primary firm and a certification issued regarding eligibility to apply for worker adjustment assistance, each of the group eligibility requirements of Section 222(a) of the Act must be met.</P>
                <P>I. Section (a)(2)(A) all of the following must be satisfied:</P>
                <P>A. A significant number or proportion of the workers in such workers' firm, or an appropriate subdivision of the firm, have become totally or partially separated, or are threatened to become totally or partially separated;</P>
                <P>B. the sales or production, or both, of such firm or subdivision have decreased absolutely; and</P>
                <P>C. increased imports of articles like or directly competitive with articles produced by such firm or subdivision have contributed importantly to such workers' separation or threat of separation and to the decline in sales or production of such firm or subdivision; or</P>
                <P>II. Section (a)(2)(B) both of the following must be satisfied:</P>
                <P>A. A significant number or proportion of the workers in such workers' firm, or an appropriate subdivision of the firm, have become totally or partially separated, or are threatened to become totally or partially separated;</P>
                <P>B. there has been a shift in production by such workers' firm or subdivision to a foreign country of articles like or directly competitive with articles which are produced by such firm or subdivision; and</P>
                <P>C. One of the following must be satisfied:</P>
                <P>1. The country to which the workers' firm has shifted production of the articles is a party to a free trade agreement with the United States;</P>
                <P>2. the country to which the workers' firm has shifted production of the articles to a beneficiary country under the Andean Trade Preference Act, African Growth and Opportunity Act, or the Caribbean Basin Economic Recovery Act; or</P>
                <P>3. there has been or is likely to be an increase in imports of articles that are like or directly competitive with articles which are or were produced by such firm or subdivision.</P>
                <P>Also, in order for an affirmative determination to be made for secondarily affected workers of a firm and a certification issued regarding eligibility to apply for worker adjustment assistance, each of the group eligibility requirements of Section 222(b) of the Act must be met.</P>
                <P>(1) Significant number or proportion of the workers in the workers' firm or an appropriate subdivision of the firm have become totally or partially separated, or are threatened to become totally or partially separated;</P>
                <P>(2) the workers' firm (or subdivision) is a supplier or downstream producer to a firm (or subdivision) that employed a group of workers who received a certification of eligibility to apply for trade adjustment assistance benefits and such supply or production is related to the article that was the basis for such certification; and</P>
                <P>(3) either—</P>
                <P>
                    (A) The workers' firm is a supplier and the component parts it supplied for 
                    <PRTPAGE P="66329"/>
                    the firm (or subdivision) described in paragraph (2) accounted for at least 20 percent of the production or sales of the workers' firm; or
                </P>
                <P>(B) a loss or business by the workers' firm with the firm (or subdivision) described in paragraph (2) contributed importantly to the workers' separation or threat of separation.</P>
                <P>In order for the Division of Trade Adjustment Assistance to issue a certification of eligibility to apply for Alternative Trade Adjustment Assistance (ATAA) for older workers, the group eligibility requirements of Section 246(a)(3)(A)(ii) of the Trade Act must be met.</P>
                <P>1. Whether a significant number of workers in the workers' firm are 50 years of age or older.</P>
                <P>2. Whether the workers in the workers' firm possess skills that are not easily transferable.</P>
                <P>
                    3. The competitive conditions within the workers' industry (
                    <E T="03">i.e.,</E>
                     conditions within the industry are adverse).
                </P>
                <HD SOURCE="HD1">Affirmative Determinations for Worker Adjustment Assistance and Alternative Trade Adjustment Assistance</HD>
                <P>The following certifications have been issued. The date following the company name and location of each determination references the impact date for all workers of such determination.</P>
                <P>The following certifications have been issued. The requirements of Section 222(a)(2)(A) (increased imports) and Section 246(a)(3)(A)(ii) of the Trade Act have been met.</P>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,142; Ditan Distribution, LLC, Forest Park, GA: April 27, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,142A; Ditan Distribution, LLC, Plainfield, IN: April 27, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,307; CommScope, Inc., Catawba, NC: July 20, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,307A; CommScope, Inc., Conover, NC: July 20, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,380; Pulse Electronics, San Diego, CA: August 18, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,444; Spang and Company, East Butler, PA: August 13, 2011</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,444A; Spang and Company, Pittsburgh, PA: August 13, 2011</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,445; Masco, Waverly, OH: October 17, 2011</E>
                </FP>
                <P>The following certifications have been issued. The requirements of Section 222(a)(2)(B) (shift in production) and Section 246(a)(3)(A)(ii) of the Trade Act have been met.</P>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,331; Sloan Transportation Products, Holland, MI: July 22, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,450; Cadent, Inc., Carlstadt, NJ: September 19, 2010</E>
                </FP>
                <P>The following certifications have been issued. The requirements of Section 222(b) (supplier to a firm whose workers are certified eligible to apply for TAA) and Section 246(a)(3)(A)(ii) of the Trade Act have been met.</P>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,388; Phoenix Trim Works, Inc., Williamsport, PA: August 20, 2011</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,422; Coastal Lumber Company, Buckhannon, WV: September 7, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,422A; Coastal Lumber Company, Elgon, WV: September 7, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,422B; Coastal Lumber Company, Elkins, WV: September 7, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,422C; Coastal Lumber Company, Smithburg, WV: September 7, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,422D; Coastal Lumber Company, Frametown, WV: September 7, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,422E; Coastal Lumber Company, Hacker Valley, WV: September 7, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,422F; Coastal Lumber Company, Gassaway, WV: September 7, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,422G; Coastal Lumber Company, Dailey, WV: September 7, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,422H; Coastal Lumber Company, Dailey, WV: September 7, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,422I; Coastal Lumber Company, Charlottesville, WV: September 7, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,422J; Coastal Lumber Company, Hopwood, PA: September 7, 2010</E>
                </FP>
                <HD SOURCE="HD1">Determinations Terminating Investigations of Petitions for Worker Adjustment Assistance</HD>
                <P>
                    After notice of the petitions was published in the 
                    <E T="04">Federal Register</E>
                     and on the Department's Web site, as required by Section 221 of the Act (19 U.S.C. 2271), the Department initiated investigations of these petitions.
                </P>
                <P>The following determinations terminating investigations were issued because the petitioning groups of workers are covered by active certifications. Consequently, further investigation in these cases would serve no purpose since the petitioning group of workers cannot be covered by more than one certification at a time.</P>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,427; Coastal Lumber Company, Hopwood, PA</E>
                </FP>
                <P>
                    I hereby certify that the aforementioned determinations were issued during the period of October 11, 2011 through October 14, 2011. Copies of these determinations may be requested under the Freedom of Information Act. Requests may be submitted by fax, courier services, or mail to FOIA Disclosure Officer, Office of Trade Adjustment Assistance (ETA), U.S. Department of Labor, 200 Constitution Avenue, NW., Washington, DC 20210 or 
                    <E T="03">tofoiarequest@dol.gov.</E>
                     These determinations also are available on the Department's Web site at 
                    <E T="03">http://www.doleta.gov/tradeact</E>
                     under the searchable listing of determinations.
                </P>
                <SIG>
                    <DATED>Dated: October 20, 2011.</DATED>
                    <NAME>Michael W. Jaffe, </NAME>
                    <TITLE>Certifying Officer, Office of Trade Adjustment Assistance.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27701 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-FN-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Employment and Training Administration</SUBAGY>
                <SUBJECT>Notice of Determinations Regarding Eligibility To Apply for Worker Adjustment Assistance and Alternative Trade Adjustment Assistance</SUBJECT>
                <P>In accordance with Section 223 of the Trade Act of 1974, as amended (19 U.S.C. 2273) the Department of Labor herein presents summaries of determinations regarding eligibility to apply for trade adjustment assistance for workers (TA-W) number and alternative trade adjustment assistance (ATAA) by (TA-W) number issued during the period of October 3, 2011 through October 7, 2011.</P>
                <P>In order for an affirmative determination to be made for workers of a primary firm and a certification issued regarding eligibility to apply for worker adjustment assistance, each of the group eligibility requirements of Section 222(a) of the Act must be met.</P>
                <P>I. Section (a)(2)(A), all of the following must be satisfied:</P>
                <P>A. A significant number or proportion of the workers in such workers' firm, or an appropriate subdivision of the firm, have become totally or partially separated, or are threatened to become totally or partially separated;</P>
                <P>B. The sales or production, or both, of such firm or subdivision have decreased absolutely; and</P>
                <P>C. Increased imports of articles like or directly competitive with articles produced by such firm or subdivision have contributed importantly to such workers' separation or threat of separation and to the decline in sales or production of such firm or subdivision; or</P>
                <P>II. Section (a)(2)(B), both of the following must be satisfied:</P>
                <P>
                    A. A significant number or proportion of the workers in such workers' firm, or 
                    <PRTPAGE P="66330"/>
                    an appropriate subdivision of the firm, have become totally or partially separated, or are threatened to become totally or partially separated;
                </P>
                <P>B. There has been a shift in production by such workers' firm or subdivision to a foreign country of articles like or directly competitive with articles which are produced by such firm or subdivision; and</P>
                <P>C. One of the following must be satisfied:</P>
                <P>1. The country to which the workers' firm has shifted production of the articles is a party to a free trade agreement with the United States;</P>
                <P>2. The country to which the workers' firm has shifted production of the articles is a beneficiary country under the Andean Trade Preference Act, African Growth and Opportunity Act, or the Caribbean Basin Economic Recovery Act; or</P>
                <P>3. There has been or is likely to be an increase in imports of articles that are like or directly competitive with articles which are or were produced by such firm or subdivision.</P>
                <P>Also, in order for an affirmative determination to be made for secondarily affected workers of a firm and a certification issued regarding eligibility to apply for worker adjustment assistance, each of the group eligibility requirements of Section 222(b) of the Act must be met.</P>
                <P>(1) Significant number or proportion of the workers in the workers' firm or an appropriate subdivision of the firm have become totally or partially separated, or are threatened to become totally or partially separated;</P>
                <P>(2) The workers' firm (or subdivision) is a supplier or downstream producer to a firm (or subdivision) that employed a group of workers who received a certification of eligibility to apply for trade adjustment assistance benefits and such supply or production is related to the article that was the basis for such certification; and</P>
                <P>(3) Either—</P>
                <P>(A) The workers' firm is a supplier and the component parts it supplied for the firm (or subdivision) described in paragraph (2) accounted for at least 20 percent of the production or sales of the workers' firm; or</P>
                <P>(B) A loss of business by the workers' firm with the firm (or subdivision) described in paragraph (2) contributed importantly to the workers' separation or threat of separation.</P>
                <P>In order for the Division of Trade Adjustment Assistance to issue a certification of eligibility to apply for Alternative Trade Adjustment Assistance (ATAA) for older workers, the group eligibility requirements of Section 246(a)(3)(A)(ii) of the Trade Act must be met.</P>
                <P>1. Whether a significant number of workers in the workers' firm are 50 years of age or older.</P>
                <P>2. Whether the workers in the workers' firm possess skills that are not easily transferable.</P>
                <P>
                    3. The competitive conditions within the workers' industry (
                    <E T="03">i.e.,</E>
                     conditions within the industry are adverse).
                </P>
                <HD SOURCE="HD1">Affirmative Determinations for Worker Adjustment Assistance and Alternative Trade Adjustment Assistance</HD>
                <P>The following certifications have been issued. The date following the company name and location of each determination references the impact date for all workers of such determination.</P>
                <P>The following certifications have been issued. The requirements of Section 222(a)(2)(A) (increased imports) and Section 246(a)(3)(A)(ii) of the Trade Act have been met.</P>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,373 Hamburg Industries, Inc., Hamburg, PA: August 16, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,391; Vertis, Inc., North Haven, CT: August 6, 2011</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,426; PCT International, Jackson, MI: September 8, 2010</E>
                </FP>
                <P>The following certifications have been issued. The requirements of Section 222(a)(2)(B) (shift in production) and Section 246(a)(3)(A)(ii) of the Trade Act have been met.</P>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,376; Nordson Corporation, Norcross, GA: July 8, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,384; Leviton Southern Devices, Morganton, NC: August 19, 2010</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,461; Wilson Sporting Goods Company, Sparta, TN: September 23, 2010</E>
                </FP>
                <HD SOURCE="HD1">Negative Determinations for Worker Adjustment Assistance and Alternative Trade Adjustment Assistance</HD>
                <P>In the following cases, the investigation revealed that the eligibility criteria for worker adjustment assistance have not been met for the reasons specified.</P>
                <P>Because the workers of the firm are not eligible to apply for TAA, the workers cannot be certified eligible for ATAA.</P>
                <P>The investigation revealed that criteria (a)(2)(A)(I.C.) (increased imports) and (a)(2)(B)(II.B.) (shift in production to a foreign country) have not been met.</P>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,199; Stimson Lumber Co., Gaston, OR</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,310; Applabs, Inc., Deerfield Beach, FL</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,334; RR Donnelley, Eldridge, IA</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,379; Hewlett Packard Company, Corvallis, OR</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80.394; Deluxe Printing Co, Inc., Hickory, NC</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,474; Simonton Windows, McAlester, OK</E>
                </FP>
                <P>The workers' firm does not produce an article as required for certification under Section 222 of the Trade Act of 1974.</P>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,407; CHEP USA, Orlando, FL</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,441; Online Buddies, Inc., Cambridge, MA</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,462; Tradewins, LLC, Woodinville, WA</E>
                </FP>
                <HD SOURCE="HD1">Determinations Terminating Investigations of Petitions for Worker Adjustment Assistance</HD>
                <P>
                    After notice of the petitions was published in the 
                    <E T="04">Federal Register</E>
                     and on the Department's Web site, as required by Section 221 of the Act (19 U.S.C. 2271), the Department initiated investigations of these petitions.
                </P>
                <P>The following determinations terminating investigations were issued because the petitioning groups of workers are covered by active certifications. Consequently, further investigation in these cases would serve no purpose since the petitioning group of workers cannot be covered by more than one certification at a time.</P>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,344; Flextronics International USA, Inc., Foothill Ranch, CA</E>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">TA-W-80,364; Gray Interplant Systems, Inc., Peoria, IL</E>
                </FP>
                <P>
                    I hereby certify that the aforementioned determinations were issued during the period of October 3, 2011 through October 7, 2011. Copies of these determinations may be requested under the Freedom of Information Act. Requests may be submitted by fax, courier services, or mail to FOIA Disclosure Officer, Office of Trade Adjustment Assistance (ETA), U.S. Department of Labor, 200 Constitution Avenue, NW., Washington, DC 20210 or 
                    <E T="03">tofoiarequest@dol.gov.</E>
                     These determinations also are available on the Department's Web site at 
                    <E T="03">http://www.doleta.gov/tradeact</E>
                     under the searchable listing of determinations.
                </P>
                <SIG>
                    <DATED>Dated: October 14, 2011.</DATED>
                    <NAME>Michael W. Jaffe, </NAME>
                    <TITLE>Certifying Officer, Office of Trade Adjustment Assistance.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27705 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-FN-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="66331"/>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Employment and Training Administration</SUBAGY>
                <SUBJECT>Investigations Regarding Certifications of Eligibility To Apply for Worker Adjustment Assistance and Alternative Trade Adjustment Assistance</SUBJECT>
                <P>Petitions have been filed with the Secretary of Labor under Section 221 (a) of the Trade Act of 1974 (“the Act”) and are identified in the Appendix to this notice. Upon receipt of these petitions, the Director of the Division of Trade Adjustment Assistance, Employment and Training Administration, has instituted investigations pursuant to Section 221 (a) of the Act.</P>
                <P>The purpose of each of the investigations is to determine whether the workers are eligible to apply for adjustment assistance under title II, chapter 2, of the Act. The investigations will further relate, as appropriate, to the determination of the date on which total or partial separations began or threatened to begin and the subdivision of the firm involved.</P>
                <P>The petitioners or any other persons showing a substantial interest in the subject matter of the investigations may request a public hearing, provided such request is filed in writing with the Director, Office of Trade Adjustment Assistance, at the address shown below, not later than November 7, 2011.</P>
                <P>Interested persons are invited to submit written comments regarding the subject matter of the investigations to the Director, Office of Trade Adjustment Assistance, at the address shown below, not later than November 7, 2011. </P>
                <P>The petitions filed in this case are available for inspection at the Office of the Director, Office of Trade Adjustment Assistance, Employment and Training Administration, U.S. Department of Labor, Room N-5428, 200 Constitution Avenue, NW., Washington, DC 20210.</P>
                <SIG>
                    <DATED>Signed at Washington, DC this 20th day of October 2011</DATED>
                    <NAME>Michael Jaffe,</NAME>
                    <TITLE>Certifying Officer, Office of Trade Adjustment Assistance.</TITLE>
                </SIG>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="xs60,r100,r50,12,12">
                    <TTITLE>Appendix</TTITLE>
                    <TDESC>[20 TAA petitions instituted between 10/10/11 and 10/14/11]</TDESC>
                    <BOXHD>
                        <CHED H="1">TA-W</CHED>
                        <CHED H="1">
                            Subject firm 
                            <LI>(petitioners)</LI>
                        </CHED>
                        <CHED H="1">Location</CHED>
                        <CHED H="1">
                            Date of 
                            <LI>institution</LI>
                        </CHED>
                        <CHED H="1">
                            Date of 
                            <LI>petition</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">80500</ENT>
                        <ENT>IBM (State/One-Stop)</ENT>
                        <ENT>San Francisco, CA</ENT>
                        <ENT>10/11/11 </ENT>
                        <ENT>10/07/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80501</ENT>
                        <ENT>TT Electronics (Company)</ENT>
                        <ENT>Boone, NC</ENT>
                        <ENT>10/11/11 </ENT>
                        <ENT>10/10/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80502</ENT>
                        <ENT>LexisNexis (Company)</ENT>
                        <ENT>Miamisburg, OH</ENT>
                        <ENT>10/11/11 </ENT>
                        <ENT>10/06/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80503</ENT>
                        <ENT>Viam Manufacturing, Inc. (Company)</ENT>
                        <ENT>Santa Fe Springs, CA</ENT>
                        <ENT>10/11/11 </ENT>
                        <ENT>10/06/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80504</ENT>
                        <ENT>BASF Corporation (Company)</ENT>
                        <ENT>Belvidere, NJ</ENT>
                        <ENT>10/14/11 </ENT>
                        <ENT>10/11/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80505</ENT>
                        <ENT>Haldex (State/One-Stop)</ENT>
                        <ENT>Kansas City, MO</ENT>
                        <ENT>10/14/11 </ENT>
                        <ENT>10/12/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80506</ENT>
                        <ENT>JVC-USA Product Return Center (State/One-Stop)</ENT>
                        <ENT>McAllen, TX</ENT>
                        <ENT>10/14/11 </ENT>
                        <ENT>10/12/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80507</ENT>
                        <ENT>Kerry Ingredients &amp; Flavours (Union)</ENT>
                        <ENT>Turtle Lake, WI</ENT>
                        <ENT>10/14/11 </ENT>
                        <ENT>10/12/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80508</ENT>
                        <ENT>Stateline Warehouse (Workers)</ENT>
                        <ENT>Ridgeway, VA</ENT>
                        <ENT>10/14/11 </ENT>
                        <ENT>10/07/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80509</ENT>
                        <ENT>ON Semiconductor (Company)</ENT>
                        <ENT>Phoenix, AZ</ENT>
                        <ENT>10/14/11 </ENT>
                        <ENT>10/06/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80510</ENT>
                        <ENT>Suntron Corporation (Company)</ENT>
                        <ENT>Sugar Land, TX</ENT>
                        <ENT>10/14/11 </ENT>
                        <ENT>10/12/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80511</ENT>
                        <ENT>Specialty Bar Products Co. (Workers)</ENT>
                        <ENT>Blairsville, PA</ENT>
                        <ENT>10/14/11 </ENT>
                        <ENT>10/05/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80512</ENT>
                        <ENT>Pilgrim's Pride—Dallas Processing Plant (State/One-Stop)</ENT>
                        <ENT>Dallas, TX</ENT>
                        <ENT>10/14/11 </ENT>
                        <ENT>09/30/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80513</ENT>
                        <ENT>Centurion Medical Products (Workers)</ENT>
                        <ENT>Jeanette, PA</ENT>
                        <ENT>10/14/11 </ENT>
                        <ENT>10/13/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80514</ENT>
                        <ENT>Intier Magna (State/One-Stop)</ENT>
                        <ENT>Shreveport, LA</ENT>
                        <ENT>10/14/11 </ENT>
                        <ENT>10/13/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80515</ENT>
                        <ENT>AI Android Industries (State/One-Stop)</ENT>
                        <ENT>Shreveport, LA</ENT>
                        <ENT>10/14/11 </ENT>
                        <ENT>10/13/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80516</ENT>
                        <ENT>Travelers (Workers)</ENT>
                        <ENT>Elmira, NY</ENT>
                        <ENT>10/14/11 </ENT>
                        <ENT>10/13/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80517</ENT>
                        <ENT>AGS Automotive (State/One-Stop)</ENT>
                        <ENT>Shreveport, LA</ENT>
                        <ENT>10/14/11 </ENT>
                        <ENT>10/13/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80518</ENT>
                        <ENT>KV Pharmaceuticals (State/One-Stop)</ENT>
                        <ENT>Bridgeton, MO</ENT>
                        <ENT>10/14/11 </ENT>
                        <ENT>10/13/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80519</ENT>
                        <ENT>Verso Paper Corp. (Union)</ENT>
                        <ENT>Bucksport, ME</ENT>
                        <ENT>10/14/11 </ENT>
                        <ENT>10/13/11 </ENT>
                    </ROW>
                </GPOTABLE>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27700 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-FN-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Employment and Training Administration</SUBAGY>
                <SUBJECT>Investigations Regarding Certifications of Eligibility To Apply for Worker Adjustment Assistance and Alternative Trade Adjustment Assistance</SUBJECT>
                <P>Petitions have been filed with the Secretary of Labor under Section 221 (a) of the Trade Act of 1974 (“the Act”) and are identified in the Appendix to this notice. Upon receipt of these petitions, the Director of the Division of Trade Adjustment Assistance, Employment and Training Administration, has instituted investigations pursuant to Section 221(a) of the Act.</P>
                <P>The purpose of each of the investigations is to determine whether the workers are eligible to apply for adjustment assistance under title II, chapter 2, of the Act. The investigations will further relate, as appropriate, to the determination of the date on which total or partial separations began or threatened to begin and the subdivision of the firm involved.</P>
                <P>The petitioners or any other persons showing a substantial interest in the subject matter of the investigations may request a public hearing, provided such request is filed in writing with the Director, Office of Trade Adjustment Assistance, at the address shown below, not later than November 7, 2011.</P>
                <P>Interested persons are invited to submit written comments regarding the subject matter of the investigations to the Director, Office of Trade Adjustment Assistance, at the address shown below, not later than November 7, 2011.</P>
                <P>The petitions filed in this case are available for inspection at the Office of the Director, Office of Trade Adjustment Assistance, Employment and Training Administration, U.S. Department of Labor, Room N-5428, 200 Constitution Avenue, NW., Washington, DC 20210.</P>
                <SIG>
                    <DATED>Signed at Washington, DC, this 12 day of October 2011.</DATED>
                    <NAME>Michael W. Jaffe,</NAME>
                    <TITLE>Certifying Officer, Office of Trade Adjustment Assistance.</TITLE>
                </SIG>
                <PRTPAGE P="66332"/>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="xs60,r100,r50,12,12">
                    <TTITLE>Appendix</TTITLE>
                    <TDESC>[14 TAA petitions instituted between 10/3/11 and 10/7/11]</TDESC>
                    <BOXHD>
                        <CHED H="1">TA-W</CHED>
                        <CHED H="1">
                            Subject Firm
                            <LI>(petitioners)</LI>
                        </CHED>
                        <CHED H="1">Location</CHED>
                        <CHED H="1">
                            Date of 
                            <LI>institution</LI>
                        </CHED>
                        <CHED H="1">
                            Date of 
                            <LI>petition</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">80486</ENT>
                        <ENT>Lattice Semiconductor (Workers)</ENT>
                        <ENT>Bethlehem, PA</ENT>
                        <ENT>10/03/11 </ENT>
                        <ENT>09/22/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80487</ENT>
                        <ENT>Stimson Lumber Company (Workers)</ENT>
                        <ENT>Colville, WA</ENT>
                        <ENT>10/03/11 </ENT>
                        <ENT>09/27/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80488</ENT>
                        <ENT>Plexus Services Corp. (Company)</ENT>
                        <ENT>Nampa, ID</ENT>
                        <ENT>10/03/11 </ENT>
                        <ENT>09/30/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80489</ENT>
                        <ENT>Citi Group (State/One-Stop)</ENT>
                        <ENT>Elk Grove Village, IL</ENT>
                        <ENT>10/03/11 </ENT>
                        <ENT>09/30/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80490</ENT>
                        <ENT>Novartis Pharmaceuticals (State/One-Stop)</ENT>
                        <ENT>East Hanover, NJ</ENT>
                        <ENT>10/04/11 </ENT>
                        <ENT>10/03/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80491</ENT>
                        <ENT>Staffmark (Workers)</ENT>
                        <ENT>Poplar Bluff, MO</ENT>
                        <ENT>10/04/11 </ENT>
                        <ENT>09/30/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80492</ENT>
                        <ENT>Rock-Tenn-Milwaukee Folding Plant (Union)</ENT>
                        <ENT>Milwaukee, WI</ENT>
                        <ENT>10/05/11 </ENT>
                        <ENT>10/04/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80493</ENT>
                        <ENT>Molded Fiber Glass Companies (MFG Texas) (State/One-Stop)</ENT>
                        <ENT>Gainesville, TX</ENT>
                        <ENT>10/05/11 </ENT>
                        <ENT>10/04/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80494</ENT>
                        <ENT>Anthelio Healthcare Solutions Inc. (State/One-Stop)</ENT>
                        <ENT>Dallas, TX</ENT>
                        <ENT>10/05/11 </ENT>
                        <ENT>10/04/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80495</ENT>
                        <ENT>BCI—The Newark Group, Inc. (State/One-Stop)</ENT>
                        <ENT>Fitchburg, MA</ENT>
                        <ENT>10/06/11 </ENT>
                        <ENT>10/05/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80496</ENT>
                        <ENT>Ben-Mar Hosiery (Company)</ENT>
                        <ENT>Ft. Payne, AL</ENT>
                        <ENT>10/07/11 </ENT>
                        <ENT>10/05/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80497</ENT>
                        <ENT>Southwoods, LLC (Company)</ENT>
                        <ENT>Manning, SC</ENT>
                        <ENT>10/07/11 </ENT>
                        <ENT>10/06/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80498</ENT>
                        <ENT>InterMetro Industries (Company)</ENT>
                        <ENT>Fostoria, OH</ENT>
                        <ENT>10/07/11 </ENT>
                        <ENT>10/05/11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">80499</ENT>
                        <ENT>Standard Insurance Company (Workers)</ENT>
                        <ENT>Portland, OR</ENT>
                        <ENT>10/07/11 </ENT>
                        <ENT>09/26/11 </ENT>
                    </ROW>
                </GPOTABLE>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27704 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-FN-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NUCLEAR REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[Docket No. 50-302; NRC-2011-0248]</DEPDOC>
                <SUBJECT>Florida Power Corporation; Notice of Withdrawal of Application for Amendment to Facility Operating License</SUBJECT>
                <P>The U.S. Nuclear Regulatory Commission (NRC or the Commission) has granted the request of Florida Power Corporation (the licensee) to withdraw its March 24, 2011, application for proposed amendment to Facility Operating License No. DPR-72 for the Crystal River Unit 3 Nuclear Generating Plant located in Citrus County, Florida.</P>
                <P>The proposed amendment would have modified the facility technical specifications to adopt Technical Specification Task Force (TSTF), Improved Standard Technical Specifications Change Traveler, TSTF-248, Revision 0, “Revise Shutdown Margin Definition for Stuck Rod Exception.” The proposed amendment would have revised the definition of shutdown margin to include a provision allowing an exception to the highest reactivity worth stuck control rod penalty if there are two independent means of confirming that all control rods are fully inserted in the reactor core.</P>
                <P>
                    The Commission had previously issued a Notice of Consideration of Issuance of Amendment published in the 
                    <E T="04">Federal Register</E>
                     on June 28, 2011 (76 FR 37848). However, by letter dated September 7, 2011, the licensee withdrew the proposed change.
                </P>
                <P>
                    For further details with respect to this action, see the application for amendment dated March 24, 2011, and the licensee's letter dated September 7, 2011, which withdrew the application for license amendment. Documents may be examined, and/or copied for a fee, at the NRC's Public Document Room (PDR), located at One White Flint North, Public File Area O1 F21, 11555 Rockville Pike (first floor), Rockville, Maryland. Publicly available documents created or received at the NRC are accessible electronically through the Agencywide Documents Access and Management System (ADAMS) in the NRC Library at 
                    <E T="03">http://www.nrc.gov/reading-rm/adams.html.</E>
                     Persons who do not have access to ADAMS or who encounter problems in accessing the documents located in ADAMS should contact the NRC PDR Reference staff by telephone at 1-800-397-4209 or 301-415-4737, or by e-mail to 
                    <E T="03">pdr.resource@nrc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated at Rockville, Maryland, this 17th day of October 2011.</DATED>
                    <P>For the Nuclear Regulatory Commission.</P>
                    <NAME>Farideh E. Saba,</NAME>
                    <TITLE>Senior Project Manager, Plant Licensing Branch II-2, Division of Operating Reactor Licensing, Office of Nuclear Reactor Regulation.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27689 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[NRC-2011-0249]</DEPDOC>
                <SUBJECT>Appointments to Performance Review Boards for Senior Executive Service</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Nuclear Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Appointment to Performance Review Boards for Senior Executive Service.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Nuclear Regulatory Commission (NRC) has announced the following appointments to the NRC Performance Review Boards.</P>
                    <P>The following individuals are appointed as members of the NRC Performance Review Board (PRB) responsible for making recommendations to the appointing and awarding authorities on performance appraisal ratings and performance awards for Senior Executives and Senior Level employees:</P>
                    <P>Darren B. Ash, Deputy Executive Director for Corporate Management, Office of the Executive Director for Operations.</P>
                    <P>R.W. Borchardt, Executive Director for Operations.</P>
                    <P>Stephen G. Burns, General Counsel.</P>
                    <P>James E. Dyer, Chief Financial Officer.</P>
                    <P>Kathryn O. Greene, Director, Office of Administration.</P>
                    <P>Catherine Haney, Director, Office of Nuclear Material Safety and Safeguards.</P>
                    <P>Eric J. Leeds, Director, Office of Nuclear Reactor Regulation.</P>
                    <P>Victor M. McCree, Regional Administrator, Region II.</P>
                    <P>Annette L. Vietti-Cook, Secretary of the Commission, Office of the Secretary.</P>
                    <P>Martin J. Virgilio, Deputy Executive Director for Reactor and Preparedness Programs, Office of the Executive Director for Operations.</P>
                    <P>Michael F. Weber, Deputy Executive Director for Materials, Waste, Research, State, Tribal, and Compliance Programs, Office of the Executive Director for Operations.</P>
                    <P>
                        James T. Wiggins, Director, Office of Nuclear Security and Incident Response.
                        <PRTPAGE P="66333"/>
                    </P>
                    <P>The following individuals will serve as members of the NRC PRB Panel that was established to review appraisals and make recommendations to the appointing and awarding authorities for NRC PRB members:</P>
                    <P>Marvin L. Itzkowitz, Associate General Counsel for Hearings, Enforcement, and Administration, Office of the General Counsel.</P>
                    <P>Michael R. Johnson, Director, Office of New Reactors.</P>
                    <P>Mark A. Satorius, Director, Office of Federal and State Materials and Environmental Management Programs.</P>
                    <P>All appointments are made pursuant to Section 4314 of Chapter 43 of Title 5 of the United States Code.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date</E>
                        : October 26, 2011.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Secretary, Executive Resources Board, U.S. Nuclear Regulatory Commission, Washington, DC 20555, (301) 492-2076.</P>
                    <SIG>
                        <DATED>Dated at Bethesda, Maryland, this 18th day of October, 2011.</DATED>
                        <P>For the U.S. Nuclear Regulatory Commission.</P>
                        <NAME>Miriam L. Cohen,</NAME>
                        <TITLE>Secretary, Executive Resources Board.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27688 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[Docket No. 50-261; NRC-2011-0247]</DEPDOC>
                <SUBJECT>Carolina Power &amp; Light Company, H.B. Robinson Steam Electric Plant, Unit No. 2; Environmental Assessment and Finding of No Significant Impact</SUBJECT>
                <P>
                    The U.S. Nuclear Regulatory Commission (NRC) is considering issuance of an exemption pursuant to Title 10 of the 
                    <E T="03">Code of Federal Regulations</E>
                     (10 CFR) 50.46, “Acceptance criteria for emergency core cooling systems for light-water nuclear power reactors,” and 10 CFR part 50, appendix k, “ECCS [Emergency Core Cooling System] Evaluation Models,” to allow for the use of M5 alloy fuel rod cladding for Facility Operating License No. DPR-23, issued to Carolina Power &amp; Light Company (the licensee), for operation of the H. B. Robinson Steam Electric Plant, Unit 2 (HBRSEP), located in Darlington County, South Carolina. In accordance with 10 CFR 51.21, “Criteria for and identification of licensing and regulatory actions requiring environmental assessments,” the NRC staff prepared an environmental assessment documenting its finding. The NRC staff concluded that the proposed action will have no significant environmental impact.
                </P>
                <HD SOURCE="HD1">Environmental Assessment</HD>
                <HD SOURCE="HD2">Identification of the Proposed Action</HD>
                <P>The proposed action would exempt the licensee from certain requirements of 10 CFR 50.46 and appendix K to 10 CFR part 50. Specifically, 10 CFR 50.46, paragraph (a)(1)(i) provides requirements for reactors containing uranium oxide fuel pellets clad in either zircaloy or ZIRLO. Additionally, appendix K to 10 CFR part 50 specifies the use of zircaloy or ZIRLO fuel cladding when doing calculations for energy release, cladding oxidation, and hydrogen generation after a postulated loss-of-coolant accident. Therefore, both of these regulations either state that either zircaloy or ZIRLO is used as the fuel rod cladding material. The proposed exemption would allow the licensee use of M5 cladding fuel assemblies into the core of HBRESP, Unit 2. The proposed action is in accordance with the licensee's application dated October 19, 2010.</P>
                <HD SOURCE="HD2">The Need for the Proposed Action</HD>
                <P>The proposed exemption is needed to allow the licensee to allow for the use of M5 alloy fuel rod cladding at HBRSEP, Unit No. 2. The licensee has requested an exemption from the requirements of 10 CFR 50.46 and 10 CFR part 50, appendix K to allow for loading of M5 cladding fuel assemblies, in lieu of zircaloy or ZIRLO, into the core during Refueling Outage 27 that is currently scheduled to begin on October 29, 2011.</P>
                <HD SOURCE="HD2">Environmental Impacts of the Proposed Action</HD>
                <P>The NRC has completed its evaluation of the proposed action and concludes that there are no environmental impacts associated with the proposed exemption. The details of the NRC staff's safety evaluation will be provided in the exemption that, if approved by the NRC, will be issued as part of the letter to the licensee approving the exemption to the regulation.</P>
                <P>The proposed action will not significantly increase the probability or consequences of accidents. No changes are being made in the types of effluents that may be released offsite. There is no significant increase in the amount of any effluent released offsite. There is no significant increase in occupational or public radiation exposure. Therefore, there are no significant radiological environmental impacts associated with the proposed action.</P>
                <P>With regard to potential nonradiological impacts, the proposed action does not result in changes to land use or water use, or result in changes to the quality or quantity of nonradiological effluents. No changes to the National Pollution Discharge Elimination system permit are needed. No effects on the aquatic or terrestrial habitat in the vicinity or the plant, or to threatened, endangered, or protected specifies under the Endangered Species Act, or impacts to essential fish habitat covered by the Magnuson-Stevens Act are expected. There are no impacts to the air or ambient air quality. There are no impacts to historical and cultural resources. In addition, there are also no known socioeconomic or environmental justice impacts associated with such proposed action. Therefore, there are no significant nonradiological environmental impacts associated with the proposed action.</P>
                <P>Accordingly, the NRC concludes that there are no significant environmental impacts associated with the proposed action.</P>
                <HD SOURCE="HD2">Environmental Impacts of the Alternatives to the Proposed Action</HD>
                <P>
                    As an alternative to the proposed action, the NRC staff considered denial of the proposed action (
                    <E T="03">i.e.,</E>
                     the “no action” alternative). Denial of the exemption request would result in no change in current environmental impacts. If the proposed action was denied, the licensee would have to comply with the ECCS rules in 10 CFR 50.46 and appendix K to 10 CFR part 50 regarding use of M5 cladding into the HBRSEP, Unit 2 core during the upcoming refueling outage. This would cause unnecessary burden on the licensee, without a significant benefit in environmental impacts. The environmental impacts of the proposed exemption and the “no action” alternative are similar.
                </P>
                <HD SOURCE="HD2">Alternative Use of Resources</HD>
                <P>The action does not involve the use of any different resources than those considered in the Final Environmental Statement for the HBRSEP, dated April 1975, as supplemented through the “Generic Environmental Impact Statement for License Renewal of Nuclear Plants: H.B. Robinson Steam Electric Plant, Unit 2—Final Report (NUREG—1437, Supplement 13).”</P>
                <HD SOURCE="HD2">Agencies and Persons Consulted</HD>
                <P>
                    In accordance with its stated policy, on October 17, 2011, the NRC staff consulted with the South Carolina State official, Mark Yeager of the South Carolina Bureau of Land and Waste Management, regarding the environmental impact of the proposed action. The State official had no comments.
                    <PRTPAGE P="66334"/>
                </P>
                <HD SOURCE="HD1">Finding of No Significant Impact</HD>
                <P>Pursuant to 10 CFR 51.32, “Finding of No Significant Impact,” and on the basis of the environmental assessment, the NRC concludes that the proposed action will not have a significant effect on the quality of the human environment. Accordingly, the NRC has determined not to prepare an environmental impact statement for the proposed action.</P>
                <P>
                    For further details with respect to the proposed action, see the licensee's letter dated October 19, 2010 (Agencywide Documents Access and Management System (ADAMS), Accession No. ML102980142). This document may be examined, and/or copied for a fee, at the NRC's Public Document Room (PDR), located at One White Flint North, Public File Area O1 F21, 11555 Rockville Pike (first floor), Rockville, Maryland. Publicly available records are accessible electronically through ADAMS in the NRC Library on the internet at the NRC Web site, 
                    <E T="03">http://www.nrc.gov/reading-rm/adams.html.</E>
                </P>
                <P>
                    Persons who do not have access to ADAMS or who encounter problems in accessing the documents located in ADAMS should contact the NRC PDR Reference staff by telephone at 1-800-397-4209 or 301-415-4737, or send an e-mail to 
                    <E T="03">pdr.resource@nrc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated at Rockville, Maryland, this 17th day of October 2011.</DATED>
                    <P>For the Nuclear Regulatory Commission.</P>
                    <NAME>Farideh E. Saba,</NAME>
                    <TITLE>Senior Project Manager, Plant Licensing Branch II-2, Division of Operating Reactor Licensing, Office of Nuclear Reactor Regulation.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27691 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[NRC-2009-0435]</DEPDOC>
                <SUBJECT>Final Environmental Assessment and Finding of No Significant Impact for the Proposed License Renewal for Nuclear Fuel Services, Inc. in Erwin, TN</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Nuclear Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Availability of Final Environmental Assessment and Finding of No Significant Impact.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given that the U.S. Nuclear Regulatory Commission (NRC) is issuing a final environmental assessment (EA) regarding the proposed renewal of NRC special nuclear material license SNM-124 (License SNM-124), which authorizes operations at the Nuclear Fuel Services, Inc. (NFS) fuel fabrication facility in Erwin, Tennessee. On June 30, 2009, NFS submitted to the NRC an application requesting that License SNM-124 be renewed for a 40-year period. The EA makes a finding of no significant impact (FONSI) regarding the proposed action.</P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You can access publicly available documents related to this document using the following methods:</P>
                    <P>
                        • 
                        <E T="03">NRC's Public Document Room (PDR):</E>
                         The public may examine and have copied, for a fee, publicly available documents related to the NFS facility and license renewal at the NRC's PDR, located at One White Flint North, 11555 Rockville Pike (first floor), Rockville, Maryland 20852. Members of the public can contact the NRC's PDR reference staff by calling 1-800-397-4209, by faxing a request to 301-415-3548, or by e-mail to 
                        <E T="03">pdr.resource@nrc.gov.</E>
                         Hard copies of the documents are available from the PDR for a fee.
                    </P>
                    <P>
                        • 
                        <E T="03">NRC's Agencywide Documents Access and Management System (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 the NRC's public documents. From this Web site, the following documents related to the NRC's environmental review can be obtained by entering the accession numbers provided:
                    </P>
                    <P>The NFS license renewal application (ADAMS Accession Number: ML091880040) and the accompanying environmental report (ADAMS Accession Number: ML091900072);</P>
                    <P>The NRC request for additional information (ADAMS Accession Number: ML100680426); </P>
                    <P>The NFS response providing additional information (ADAMS Accession Number: ML101590160); and</P>
                    <P>The NRC Final EA (ADAMS Accession Number: ML112560265).</P>
                    <P>Additionally, copies of the EA will be available at the following public libraries:</P>
                    <FP SOURCE="FP-1">Unicoi County Public Library, 201 Nolichucky Avenue, Erwin, Tennessee 37650-1239. 423-743-6533.</FP>
                    <FP SOURCE="FP-1">Jonesborough Branch, Washington County Library, 200 Sabin Drive, Jonesborough, Tennessee 37659-1306. 423-753-1800.</FP>
                    <FP SOURCE="FP-1">Greeneville/Green County Public Library, 210 North Main Street, Greeneville, Tennessee 37745-3816. 423-638-5034.</FP>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For information about the EA or the environmental review process, please contact James Park, 
                        <E T="03">telephone:</E>
                         301-415-6935; 
                        <E T="03">e-mail: James.Park@nrc.gov.</E>
                         For general or technical information associated with the ongoing safety review of the NFS license renewal application, please contact Kevin Ramsey, 
                        <E T="03">telephone:</E>
                         301-492-3123; 
                        <E T="03">e-mail: Kevin.Ramsey@nrc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On June 30, 2009, NFS submitted its license renewal application and accompanying environmental report (ER) to the NRC. On October 6, 2009, the NRC provided notice in the 
                    <E T="04">Federal Register</E>
                     (74 FR 51323) of its receipt of the license renewal application and also noticed an opportunity to request a hearing on the application. No requests for a hearing were received. Under the conditions of License SNM-124, NFS operates a nuclear fuel fabrication facility located in Erwin, Tennessee. If granted as requested, the renewed license would allow NFS to continue operations and activities at the site for a 40-year period that would begin with issuance of the renewed license.
                </P>
                <P>
                    The NRC staff's environmental review of the proposed 40-year license renewal is documented in the EA, in accordance with NRC regulations at Title 10 of the 
                    <E T="03">Code of Federal Regulations</E>
                     (10 CFR) part 51, which implement the National Environmental Policy Act of 1969, as amended (NEPA). The EA also follows NRC staff guidance in NUREG-1748, “Environmental Review Guidance for Licensing Actions Associated with NMSS Programs.” The EA identifies and evaluates the potential environmental impacts of the proposed action, and reasonable alternatives. The NRC staff has determined that renewal of License SNM-124 for a 40-year period would not significantly affect the quality of the human environment, and the EA thus makes a FONSI. The NRC staff further finds that preparation of an environmental impact statement (EIS) for the proposed action is not warranted.
                </P>
                <P>
                    The NRC staff published for public comment a draft EA for the proposed action on October 15, 2010 (75 FR 63519). The NRC staff accepted comments on the draft EA until December 31, 2010, and hosted a meeting in Erwin, Tennessee on October 26, 2010, to accept oral and written public comments. Comments were identified from the transcript of statements made at the public meeting, and from letters and e-mails submitted by members of the public. Appendix B of the Final EA includes summaries of 
                    <PRTPAGE P="66335"/>
                    the approximately 375 individual comments identified, and the NRC staff's responses to those comments. The NRC staff revised the draft EA in response to some of the comments.
                </P>
                <P>Preparation of the EA is part of the NRC's process to decide whether to renew the NFS license, pursuant to 10 CFR parts 20 and 70, and thus authorize continued operations at the NFS facility. In accordance with the provisions of 10 CFR part 70, the current license authorizes NFS to receive, possess, store, use, and ship special nuclear material enriched up to 100 percent. Under the proposed action, NFS would continue production of reactor fuel for the U.S. Navy, and for commercial domestic operations.</P>
                <P>In addition to the NFS proposed action to renew its license for 40 years, the NRC staff analyzed two alternatives: (1) The no-action alternative; and (2) renewing the NFS license for 10 years. Under the no-action alternative, NRC would not renew License SNM-124, and operations at the NFS site would no longer be authorized. NFS then would be required under 10 CFR 70.38 to submit a detailed site-wide decommissioning plan, and facility decommissioning would begin upon NRC approval of that plan.</P>
                <P>Regarding the 10-year license renewal alternative, the potential transportation and waste management impacts of this alternative to the proposed action are addressed in the EA. The magnitude of these expected impacts are one-fourth of those projected over the proposed 40-year license renewal period. As shown in the first table below, the local transportation impacts are rated as moderate and the overall transportation impacts are rated as small for both the 10-year and the 40-year proposed license renewal periods. The potential waste management impacts are rated as small for both the 10-year and the 40-year proposed license renewal periods.</P>
                <P>The NRC staff did not separately address the 10-year alternative for the other resource areas evaluated in the EA, because the staff determined that the types of potential environmental impacts associated with site operations during the proposed 40-year license renewal period would be the same as those during a 10-year license renewal period.</P>
                <P>Additionally, for the 10-year alternative, the NRC staff does not consider the potential impacts from NFS discharges of effluents that are in compliance with 10 CFR part 20 annual regulatory limits (and discharges that are in compliance with the permit conditions issued by other Federal, State, or local agencies) to differ either in type or in magnitude with the potential impacts for the requested 40-year period. The annual regulatory limits in 10 CFR part 20 and the respective permit conditions are protective of public health and safety and the environment. Discharges in compliance with those limits and conditions would thus not be expected to pose undue cumulative risks to human health and the environment.</P>
                <P>In response to comments on the draft EA, impacts from site decommissioning are evaluated in the final EA for the proposed action and the 10-year alternative, in addition to the no-action alternative. In doing so, the NRC staff recognizes that site decommissioning will be a reasonably foreseeable future action for the NFS facility and site. In conducting its evaluation, the staff also recognized that continued operations over 40 years or 10 years has the potential for increased site contamination that would need to be addressed in the detailed site decommissioning plan that NFS will be required to submit for NRC review when NFS decides to permanently cease its licensed operations. In further response to comments, the issue of cancer risk is discussed in the final EA's section on potential public health impacts.</P>
                <P>The tables below list the resource areas evaluated in the EA, and provide the findings regarding the potential environmental impacts for each of the three alternatives. In accordance with Council of Environmental Quality regulations (40 CFR 1508.27), the significance of potential impacts of the proposed action have been determined by examining their context and intensity. Context is related to the affected region, the affected interests, and the locality, while intensity refers to the severity of the impact, which is based on a number of considerations. In evaluating the significance of potential impacts, the NRC staff in the EA used the following significance levels identified in NUREG-1748, which account for context and intensity:</P>
                <P>• Small—environmental effects are not detectable or are so minor that they will neither destabilize nor noticeably alter any important attribute of the resource;</P>
                <P>• Moderate—environmental effects are sufficient to alter noticeably, but not to destabilize, important attributes of the resource; or</P>
                <P>• Large—environmental effects are clearly noticeable and are sufficient to destabilize important attributes of the resource.</P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s60,r60,r60,r60">
                    <TTITLE>Summary of Potential Environmental Impacts From Operations</TTITLE>
                    <BOXHD>
                        <CHED H="1">Resource area</CHED>
                        <CHED H="1">Proposed action</CHED>
                        <CHED H="1">10-Year renewal</CHED>
                        <CHED H="1">No-action</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Land Use</ENT>
                        <ENT>SMALL to MODERATE</ENT>
                        <ENT>SMALL to MODERATE</ENT>
                        <ENT>SMALL.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Transportation</ENT>
                        <ENT>SMALL (overall) MODERATE (local)</ENT>
                        <ENT>SMALL (overall) MODERATE (local)</ENT>
                        <ENT>SMALL.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Socioeconomics</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL to MODERATE.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Air Quality</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Water Resources—Surface Water</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Water Resources—Groundwater</ENT>
                        <ENT>SMALL to MODERATE</ENT>
                        <ENT>SMALL to MODERATE</ENT>
                        <ENT>SMALL.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Geology &amp; Soils</ENT>
                        <ENT>SMALL (geology) SMALL to MODERATE (soils)</ENT>
                        <ENT>SMALL (geology) SMALL to MODERATE (soils)</ENT>
                        <ENT>SMALL (geology) SMALL to MODERATE (soils).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ecology</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Noise</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Historic &amp; Cultural</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Scenic &amp; Visual</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Public &amp; Occupational Health</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Public &amp; Occupational Health—Accidents</ENT>
                        <ENT>MODERATE</ENT>
                        <ENT>MODERATE</ENT>
                        <ENT>SMALL.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Waste Management</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL.</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="66336"/>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s60,r60,r60,r60">
                    <TTITLE>Summary of Potential Environmental Impacts From Decommissioning</TTITLE>
                    <BOXHD>
                        <CHED H="1">Resource area</CHED>
                        <CHED H="1">Proposed action</CHED>
                        <CHED H="1">10-Year renewal</CHED>
                        <CHED H="1">No-action</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Land Use</ENT>
                        <ENT>MODERATE</ENT>
                        <ENT>MODERATE</ENT>
                        <ENT>MODERATE.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Transportation</ENT>
                        <ENT>SMALL (overall) MODERATE (local)</ENT>
                        <ENT>SMALL (overall) MODERATE (local)</ENT>
                        <ENT>SMALL (overall) MODERATE (local).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Socioeconomics</ENT>
                        <ENT>SMALL to MODERATE</ENT>
                        <ENT>SMALL to MODERATE</ENT>
                        <ENT>SMALL to MODERATE.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Air Quality</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Water Resources—Surface Water</ENT>
                        <ENT>SMALL to MODERATE</ENT>
                        <ENT>SMALL to MODERATE</ENT>
                        <ENT>SMALL to MODERATE.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Water Resources—Groundwater</ENT>
                        <ENT>SMALL to MODERATE</ENT>
                        <ENT>SMALL to MODERATE</ENT>
                        <ENT>SMALL to MODERATE.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Geology &amp; Soils</ENT>
                        <ENT>SMALL (geology) SMALL to MODERATE (soils)</ENT>
                        <ENT>SMALL (geology) SMALL to MODERATE (soils)</ENT>
                        <ENT>SMALL (geology) SMALL to MODERATE (soils).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Ecology</ENT>
                        <ENT>SMALL to MODERATE</ENT>
                        <ENT>SMALL to MODERATE</ENT>
                        <ENT>SMALL to MODERATE.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Noise</ENT>
                        <ENT>SMALL to MODERATE</ENT>
                        <ENT>SMALL to MODERATE</ENT>
                        <ENT>SMALL to MODERATE.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Historic &amp; Cultural</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Scenic &amp; Visual</ENT>
                        <ENT>MODERATE</ENT>
                        <ENT>MODERATE</ENT>
                        <ENT>MODERATE.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Public &amp; Occupational Health</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL</ENT>
                        <ENT>SMALL.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Public &amp; Occupational Health—Accidents</ENT>
                        <ENT>SMALL to MODERATE</ENT>
                        <ENT>SMALL to MODERATE</ENT>
                        <ENT>SMALL to MODERATE.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Waste Management</ENT>
                        <ENT>MODERATE</ENT>
                        <ENT>MODERATE</ENT>
                        <ENT>MODERATE.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Based on its review of the proposed action relative to the requirements set forth in 10 CFR part 51, the NRC staff has determined that renewal of License SNM-124, for a period of 40 years would not significantly affect the quality of the human environment. In its license renewal request, NFS is proposing no changes in how it processes enriched uranium, and no significant changes in NFS' authorized operations are planned during the proposed license renewal period. The impacts of ongoing and planned construction actions—including those related to the physical protection and safeguarding of licensed materials—are not expected to significantly affect the quality of the human environment. Gaseous emissions and liquid effluents generated by the NFS facility are presently controlled and monitored by permit, and would continue to be required to meet regulatory limits for non-radiological and radiological components. Public and occupational radiological dose exposures that would be generated by continued NFS facility operations would continue to be required to meet 10 CFR part 20 regulatory limits. Pursuant to 10 CFR 51.31 and 51.32, the NRC staff concludes that a FONSI is appropriate, and that preparation of an EIS is not warranted for the proposed action.</P>
                <SIG>
                    <DATED>Dated at Rockville, Maryland, this 20th day of October, 2011.</DATED>
                    <P>For the Nuclear Regulatory Commission.</P>
                    <NAME>Christepher McKenney,</NAME>
                    <TITLE>Acting Deputy Director, Environmental Protection and Performance Assessment Directorate, Division of Waste Management and Environmental Protection, Office of Federal and State Materials and Environmental Management Programs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27685 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">POSTAL REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[Docket No. A2012-11; Order No. 910]</DEPDOC>
                <SUBJECT>Post Office Closing</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Postal Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document informs the public that an appeal of the closing of the Ardenvoir, Washington, post office has been filed. It identifies preliminary steps and provides a procedural schedule. Publication of this document will allow the Postal Service, petitioners, and others to take appropriate action.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Administrative record due (from Postal Service):</E>
                         October 28, 2011; 
                        <E T="03">deadline for notices to intervene:</E>
                         November 14, 2011, 4:30 p.m., eastern time. 
                        <E T="03">See</E>
                         the Procedural Schedule in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for other dates of interest.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit comments electronically by accessing the “Filing Online” link in the banner at the top of the Commission's Web site (
                        <E T="03">http://www.prc.gov</E>
                        ) or by directly accessing the Commission's Filing Online system at 
                        <E T="03">https://www.prc.gov/prc-pages/filing-online/login.aspx.</E>
                         Commenters who cannot submit their views electronically should contact the person identified in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section as the source for case-related information for advice on alternatives to electronic filing.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Stephen L. Sharfman, General Counsel, at 202-789-6820 (case-related information) or 
                        <E T="03">DocketAdmins@prc.gov</E>
                         (electronic filing assistance).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Notice is hereby given that, pursuant to 39 U.S.C. 404(d), on October 13, 2011, the Commission received a petition for review of the Postal Service's determination to close the Ardenvoir post office in Ardenvoir, Washington. The petition for review was filed by Christine Mallon (Petitioner) and is postmarked September 30, 2011. The Commission hereby institutes a proceeding under 39 U.S.C. 404(d)(5) and establishes Docket No. A2012-11 to consider Petitioner's appeal. If Petitioner would like to further explain her position with supplemental information or facts, Petitioner may either file a Participant Statement on PRC Form 61 or file a brief with the Commission no later than November 17, 2011.</P>
                <P>
                    <E T="03">Issues apparently raised.</E>
                     Petitioner contends that: (1) The Postal Service failed to consider the effect of the closing on the community (
                    <E T="03">see</E>
                     39 U.S.C. 404(d)(2)(A)(i)); and (2) the Postal Service failed to consider whether or not it will continue to provide a maximum degree of effective and regular postal services to the community (
                    <E T="03">see</E>
                     39 U.S.C. 404(d)(2)(A)(iii)).
                </P>
                <P>
                    After the Postal Service files the administrative record and the Commission reviews it, the Commission may find that there are more legal issues than those set forth above, or that the Postal Service's determination disposes of one or more of those issues. The deadline for the Postal Service to file the applicable administrative record with the Commission is October 28, 2011. 
                    <E T="03">See</E>
                     39 CFR 3001.113. In addition, the due date for any responsive pleading by the Postal Service to this Notice is October 28, 2011.
                </P>
                <P>
                    <E T="03">Availability; Web site posting.</E>
                     The Commission has posted the appeal and supporting material on its Web site at 
                    <E T="03">http://www.prc.gov.</E>
                     Additional filings in this case and participants' 
                    <PRTPAGE P="66337"/>
                    submissions also will be posted on the Commission's Web site, if provided in electronic format or amenable to conversion, and not subject to a valid protective order. Information on how to use the Commission's Web site is available online or by contacting the Commission's Webmaster via telephone at 202-789-6873 or via electronic mail at 
                    <E T="03">prc-webmaster@prc.gov.</E>
                </P>
                <P>
                    The appeal and all related documents are also available for public inspection in the Commission's docket section. Docket section hours are 8 a.m. to 4:30 p.m., Eastern Time, Monday through Friday, except on Federal government holidays. Docket section personnel may be contacted via electronic mail at 
                    <E T="03">prc-dockets@prc.gov</E>
                     or via telephone at 202-789-6846.
                </P>
                <P>
                    <E T="03">Filing of documents.</E>
                     All filings of documents in this case shall be made using the Internet (Filing Online) pursuant to Commission rules 9(a) and 10(a) at the Commission's Web site, 
                    <E T="03">http://www.prc.gov,</E>
                     unless a waiver is obtained. 
                    <E T="03">See</E>
                     39 CFR 3001.9(a) and 3001.10(a). Instructions for obtaining an account to file documents online may be found on the Commission's Web site or by contacting the Commission's docket section at 
                    <E T="03">prc-dockets@prc.gov</E>
                     or via telephone at 202-789-6846.
                </P>
                <P>The Commission reserves the right to redact personal information which may infringe on an individual's privacy rights from documents filed in this proceeding.</P>
                <P>
                    <E T="03">Intervention.</E>
                     Persons, other than Petitioner and respondent, wishing to be heard in this matter are directed to file a notice of intervention. 
                    <E T="03">See</E>
                     39 CFR 3001.111(b). Notices of intervention in this case are to be filed on or before November 14, 2011. A notice of intervention shall be filed using the Internet (Filing Online) at the Commission's Web site unless a waiver is obtained for hardcopy filing. 
                    <E T="03">See</E>
                     39 CFR 3001.9(a) and 3001.10(a).
                </P>
                <P>
                    <E T="03">Further procedures.</E>
                     By statute, the Commission is required to issue its decision within 120 days from the date it receives the appeal. 
                    <E T="03">See</E>
                     39 U.S.C. 404(d)(5). A procedural schedule has been developed to accommodate this statutory deadline. In the interest of expedition, in light of the 120-day decision schedule, the Commission may request the Postal Service or other participants to submit information or memoranda of law on any appropriate issue. As required by the Commission rules, if any motions are filed, responses are due 7 days after any such motion is filed. 
                    <E T="03">See</E>
                     39 CFR 3001.21.
                </P>
                <P>
                    <E T="03">It is ordered:</E>
                </P>
                <P>1. The Postal Service shall file the applicable administrative record regarding this appeal no later than October 28, 2011.</P>
                <P>2. Any responsive pleading by the Postal Service to this Notice is due no later than October 28, 2011.</P>
                <P>3. The procedural schedule listed below is hereby adopted.</P>
                <P>4. Pursuant to 39 U.S.C. 505, Cassandra L. Hicks is designated officer of the Commission (Public Representative) to represent the interests of the general public.</P>
                <P>
                    5. The Secretary shall arrange for publication of this notice and order in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <P>By the Commission.</P>
                    <NAME>Shoshana M. Grove, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
                <GPOTABLE COLS="2" OPTS="L2,p1,8/9,i1" CDEF="s100,r150">
                    <TTITLE>Procedural Schedule</TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">October 13, 2011</ENT>
                        <ENT>Filing of Appeal.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">October 28, 2011</ENT>
                        <ENT>Deadline for the Postal Service to file the applicable administrative record in this appeal.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">October 28, 2011</ENT>
                        <ENT>Deadline for the Postal Service to file any responsive pleading.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">November 14, 2011</ENT>
                        <ENT>
                            Deadline for notices to intervene (
                            <E T="03">see</E>
                             39 CFR 3001.111(b)).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">November 17, 2011</ENT>
                        <ENT>
                            Deadline for Petitioners' Form 61 or initial brief in support of petition (
                            <E T="03">see</E>
                             39 CFR 3001.115(a) and (b)).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">December 7, 2011</ENT>
                        <ENT>
                            Deadline for answering brief in support of the Postal Service (
                            <E T="03">see</E>
                             39 CFR 3001.115(c)).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">December 22, 2011</ENT>
                        <ENT>
                            Deadline for reply briefs in response to answering briefs (
                            <E T="03">see</E>
                             39 CFR 3001.115(d)).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">December 29, 2011</ENT>
                        <ENT>
                            Deadline for motions by any party requesting oral argument; the Commission will schedule oral argument only when it is a necessary addition to the written filings (
                            <E T="03">see</E>
                             39 CFR 3001.116).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">January 30, 2012</ENT>
                        <ENT>
                            Expiration of the Commission's 120-day decisional schedule (
                            <E T="03">see</E>
                             39 U.S.C. 404(d)(5)).
                        </ENT>
                    </ROW>
                </GPOTABLE>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27646 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-FW-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">POSTAL REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[Docket No. A2012-12; Order No. 911]</DEPDOC>
                <SUBJECT>Post Office Closing</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Postal Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document informs the public that an appeal of the closing of the Ruth, Mississippi, post office has been filed. It identifies preliminary steps and provides a procedural schedule. Publication of this document will allow the Postal Service, petitioners, and others to take appropriate action.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Administrative record due (from Postal Service):</E>
                         October 28, 2011; 
                        <E T="03">deadline for notices to intervene:</E>
                         November 14, 2011, 4:30 p.m., eastern time. 
                        <E T="03">See</E>
                         the Procedural Schedule in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for other dates of interest.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit comments electronically by accessing the “Filing Online” link in the banner at the top of the Commission's Web site (
                        <E T="03">http://www.prc.gov</E>
                        ) or by directly accessing the Commission's Filing Online system at 
                        <E T="03">https://www.prc.gov/prc-pages/filing-online/login.aspx.</E>
                         Commenters who cannot submit their views electronically should contact the person identified in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section as the source for case-related information for advice on alternatives to electronic filing.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Stephen L. Sharfman, General Counsel, at 202-789-6820 (case-related information) or 
                        <E T="03">DocketAdmins@prc.gov</E>
                         (electronic filing assistance).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Notice is hereby given that, pursuant to 39 U.S.C. 404(d), on October 13, 2011, the Commission received a petition for review of the Postal Service's determination to close the Ruth post office in Ruth, Mississippi. The petition for review was filed by Bonnie Ard (Petitioner) and is postmarked October 6, 2011. The Commission hereby 
                    <PRTPAGE P="66338"/>
                    institutes a proceeding under 39 U.S.C. 404(d)(5) and establishes Docket No. A2012-12 to consider Petitioner's appeal. If Petitioner would like to further explain her position with supplemental information or facts, Petitioner may either file a Participant Statement on PRC Form 61 or file a brief with the Commission no later than November 17, 2011.
                </P>
                <P>
                    <E T="03">Issues apparently raised.</E>
                     Petitioner contends that the Postal Service failed to: (1) Consider the effect of the closing on the community (
                    <E T="03">see</E>
                     39 U.S.C. 404(d)(2)(A)(i)); and (2) Petitioner contends that there are factual errors contained in the Final Determination.
                </P>
                <P>
                    After the Postal Service files the administrative record and the Commission reviews it, the Commission may find that there are more legal issues than those set forth above, or that the Postal Service's determination disposes of one or more of those issues. The deadline for the Postal Service to file the applicable administrative record with the Commission is October 28, 2011. 
                    <E T="03">See</E>
                     39 CFR 3001.113. In addition, the due date for any responsive pleading by the Postal Service to this Notice is October 28, 2011.
                </P>
                <P>
                    <E T="03">Availability; Web site posting.</E>
                     The Commission has posted the appeal and supporting material on its Web site at 
                    <E T="03">http://www.prc.gov.</E>
                     Additional filings in this case and participants' submissions also will be posted on the Commission's Web site, if provided in electronic format or amenable to conversion, and not subject to a valid protective order. Information on how to use the Commission's Web site is available online or by contacting the Commission's webmaster via telephone at 202-789-6873 or via electronic mail at 
                    <E T="03">prc-webmaster@prc.gov.</E>
                </P>
                <P>
                    The appeal and all related documents are also available for public inspection in the Commission's docket section. Docket section hours are 8 a.m. to 4:30 p.m., eastern time, Monday through Friday, except on Federal government holidays. Docket section personnel may be contacted via electronic mail at 
                    <E T="03">prc-dockets@prc.gov</E>
                     or via telephone at 202-789-6846.
                </P>
                <P>
                    <E T="03">Filing of documents.</E>
                     All filings of documents in this case shall be made using the Internet (Filing Online) pursuant to Commission rules 9(a) and 10(a) at the Commission's Web site, 
                    <E T="03">http://www.prc.gov,</E>
                     unless a waiver is obtained. 
                    <E T="03">See</E>
                     39 CFR 3001.9(a) and 3001.10(a). Instructions for obtaining an account to file documents online may be found on the Commission's Web site or by contacting the Commission's docket section at 
                    <E T="03">prc-dockets@prc.gov</E>
                     or via telephone at 202-789-6846.
                </P>
                <P>The Commission reserves the right to redact personal information which may infringe on an individual's privacy rights from documents filed in this proceeding.</P>
                <P>
                    <E T="03">Intervention.</E>
                     Persons, other than Petitioner and respondent, wishing to be heard in this matter are directed to file a notice of intervention. 
                    <E T="03">See</E>
                     39 CFR 3001.111(b). Notices of intervention in this case are to be filed on or before November 14, 2011. A notice of intervention shall be filed using the Internet (Filing Online) at the Commission's Web site unless a waiver is obtained for hardcopy filing. 
                    <E T="03">See</E>
                     39 CFR 3001.9(a) and 3001.10(a).
                </P>
                <P>
                    <E T="03">Further procedures.</E>
                     By statute, the Commission is required to issue its decision within 120 days from the date it receives the appeal. 
                    <E T="03">See</E>
                     39 U.S.C. 404(d)(5). A procedural schedule has been developed to accommodate this statutory deadline. In the interest of expedition, in light of the 120-day decision schedule, the Commission may request the Postal Service or other participants to submit information or memoranda of law on any appropriate issue. As required by the Commission rules, if any motions are filed, responses are due 7 days after any such motion is filed. 
                    <E T="03">See</E>
                     39 CFR 3001.21.
                </P>
                <P>
                    <E T="03">It is ordered:</E>
                </P>
                <P>1. The Postal Service shall file the applicable administrative record regarding this appeal no later than October 28, 2011.</P>
                <P>2. Any responsive pleading by the Postal Service to this Notice is due no later than October 28, 2011.</P>
                <P>3. The procedural schedule listed below is hereby adopted.</P>
                <P>4. Pursuant to 39 U.S.C. 505, Patricia A. Gallagher is designated officer of the Commission (Public Representative) to represent the interests of the general public.</P>
                <P>
                    5. The Secretary shall arrange for publication of this notice and order in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <P>By the Commission.</P>
                    <NAME>Shoshana M. Grove, </NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
                <GPOTABLE COLS="2" OPTS="L2,p1,8/9,i1" CDEF="s100,r150">
                    <TTITLE>Procedural Schedule</TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">October 13, 2011</ENT>
                        <ENT>Filing of Appeal.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">October 28, 2011</ENT>
                        <ENT>Deadline for the Postal Service to file the applicable administrative record in this appeal.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">October 28, 2011</ENT>
                        <ENT>Deadline for the Postal Service to file any responsive pleading.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">November 14, 2011</ENT>
                        <ENT>
                            Deadline for notices to intervene (
                            <E T="03">see</E>
                             39 CFR 3001.111(b)).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">November 17, 2011</ENT>
                        <ENT>
                            Deadline for Petitioners' Form 61 or initial brief in support of petition (
                            <E T="03">see</E>
                             39 CFR 3001.115(a) and (b)).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">December 7, 2011</ENT>
                        <ENT>
                            Deadline for answering brief in support of the Postal Service (
                            <E T="03">see</E>
                             39 CFR 3001.115(c)).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">December 22, 2011</ENT>
                        <ENT>
                            Deadline for reply briefs in response to answering briefs (
                            <E T="03">see</E>
                             39 CFR 3001.115(d)).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">December 29, 2011</ENT>
                        <ENT>
                            Deadline for motions by any party requesting oral argument; the Commission will schedule oral argument only when it is a necessary addition to the written filings (
                            <E T="03">see</E>
                             39 CFR 3001.116).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">February 3, 2012</ENT>
                        <ENT>
                            Expiration of the Commission's 120-day decisional schedule (
                            <E T="03">see</E>
                             39 U.S.C. 404(d)(5)).
                        </ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="66339"/>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27648 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7710-FW-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-65602; File No. 4-640]</DEPDOC>
                <SUBJECT>Inaugural Roundtable of the Financial Reporting Series Entitled “Uncertainty in Financial Statements: How Much To Recognize and How Best To Communicate It”</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Securities and Exchange Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of roundtable discussion; request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Commission staff will hold a public roundtable discussion to consider financial statement measurements (and associated disclosures) that incorporate judgments about future events. The discussion will be open to the public with seating on a first-come, first-served basis. Members of the public may also listen by webcast on the SEC Web site at 
                        <E T="03">http://www.sec.gov.</E>
                         The roundtable discussion will take place in the Multipurpose Room (Room L-006) at the SEC Headquarters located at 100 F Street, NE., Washington, DC. Feedback is welcomed regarding any of the topics to be addressed at the roundtable.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The roundtable discussion will take place on Tuesday, November 8, 2011, commencing at 10 a.m. and ending at 5 p.m. The Commission will accept comments regarding issues addressed at the roundtable until December 8, 2011.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>J. Mike Starr, Deputy Chief Accountant, or Eric West, Associate Chief Accountant, at (202) 551-5300, U.S. Securities and Exchange Commission, 100 F Street, NE., Washington, DC 20549.</P>
                </FURINF>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments may be submitted by any of the following methods:</P>
                </ADD>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's Internet comment form (
                    <E T="03">http://www.sec.gov/rules/other.shtml</E>
                    ); or
                </P>
                <P>
                    • Send an e-mail to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include File Number 4-640 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 4-640. This file number should be included on the subject line if e-mail is used. To help us 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</E>
                    ). Comments are also 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. All comments received will be posted without change; we do not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly.
                </FP>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This will be the inaugural roundtable of the Financial Reporting Series. The Financial Reporting Series was instituted by SEC staff to assist in the proactive identification of risks related to, and areas of potential improvements in, the reliability and usefulness of financial information provided to investors. In this regard, the Financial Reporting Series is intended to facilitate balanced discussions of implementation issues or emerging issues in financial reporting.</P>
                <P>Feedback is welcomed regarding any of the topics to be addressed at the roundtable. The panel discussions will focus on the following topics and questions:</P>
                <P>1. Please provide feedback on any topics where the extent of uncertainty in an accounting measurement is less useful to investors and why a more certain measurement would be preferable. Likewise, provide feedback on those topics where a measurement with uncertainty gives investors useful information and why it is preferable to a more certain measurement.</P>
                <P>2. For those topics where uncertain measurements are useful to investors, how should the uncertainties be incorporated into the measure? Please explain the reasons for the measurement method(s) you selected.</P>
                <P>3. What information do investors utilize to understand uncertainty? Please describe why such information is useful and, if it is not disclosed in the financial statements, indicate its source.</P>
                <P>4. What are the challenges for investors in understanding the nature and extent of measurement uncertainty?</P>
                <P>5. As measurement uncertainty increases, please explain whether (and how, if applicable) it changes the investor's expectation of preparers and auditors.</P>
                <P>6. For preparers, what are the challenges in or impediments to providing investors with information to understand the nature and extent of measurement uncertainties?</P>
                <P>7. What are the challenges for auditors in evaluating management's judgments related to measurement uncertainties?</P>
                <P>8. Please provide feedback on whether (and how) a change in the auditor's responsibility or role would enhance the investor's understanding of the nature and extent of measurement uncertainties.</P>
                <P>9. Please provide any additional comments or suggestions pertinent to how much uncertainty to recognize and how best to communicate it.</P>
                <SIG>
                    <DATED>Dated: October 20, 2011.</DATED>
                    <P>By the Commission.</P>
                    <NAME>Elizabeth M. Murphy,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27696 Filed 10-25-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-65601; File No. SR-NYSEArca-2011-63]</DEPDOC>
                <SUBJECT> Self-Regulatory Organizations; NYSE Arca, Inc.; Order Approving a Proposed Rule Change To List and Trade Shares of the United States Metals Index Fund, the United States Agriculture Index Fund and the United States Copper Index Fund Under NYSE Arca Equities Rule 8.200</SUBJECT>
                <DATE>October 20, 2011.</DATE>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    On August 19, 2011, NYSE Arca, Inc. (“Exchange” or “NYSE Arca”) filed with the Securities and Exchange Commission (“Commission”), pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change to list and trade shares of the United States Metals Index Fund (“USMI”), the United States Agriculture Index Fund (“USAI”) and the United States Copper Index Fund (“USCUI”) (collectively, the “Funds”) under NYSE Arca Equities Rule 8.200. The proposed rule change was published for comment in the 
                    <E T="04">Federal Register</E>
                     on September 9, 2011.
                    <SU>3</SU>
                    <FTREF/>
                     The Commission received no comments on the proposal. This order approves the proposed rule change.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 65249 (September 2, 2011), 76 FR 55956 (“Notice”).
                    </P>
                </FTNT>
                <PRTPAGE P="66340"/>
                <HD SOURCE="HD1">II. Description of the Proposed Rule Change</HD>
                <P>
                    The Exchange proposes to list and trade shares (“Units”) of the Funds 
                    <SU>4</SU>
                    <FTREF/>
                     pursuant to NYSE Arca Equities Rule 8.200, Commentary .02, which permits the trading of Trust Issued Receipts either by listing or pursuant to unlisted trading privileges.
                    <SU>5</SU>
                    <FTREF/>
                     The Units represent beneficial ownership interests in the Funds, as described in the Registration Statement. The Funds are commodity pools that are series of the Trust, a Delaware statutory trust. The Funds are managed and controlled by United States Commodity Funds LLC (“Sponsor”). The Sponsor is a Delaware limited liability company that is registered as a commodity pool operator (“CPO”) with the Commodity Futures Trading Commission (“CFTC”) and is a member of the National Futures Association (“NFA”).
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         the Funds' registration statement on Form S-1 for the United States Commodity Index Funds Trust, dated November 24, 2010 (File No. 333-170844) relating to the Funds (“Registration Statement”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Commentary .02 to NYSE Arca Equities Rule 8.200 applies to Trust Issued Receipts that invest in “Financial Instruments.” The term “Financial Instruments,” as defined in Commentary .02(b)(4) to NYSE Arca Equities Rule 8.200, means any combination of investments, including cash; securities; options on securities and indices; futures contracts; options on futures contracts; forward contracts; equity caps, collars and floors; and swap agreements.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">A. USMI</HD>
                <P>
                    USMI's trading advisor is SummerHaven Investment Management, LLC (“SummerHaven”). The Sponsor expects to manage USMI's investments directly, using the trading advisory services of SummerHaven for guidance with respect to the Metals Index and the Sponsor's selection of investments on behalf of USMI. The Sponsor, SummerHaven Indexing and SummerHaven are not affiliated with a broker-dealer and are subject to procedures designed to prevent the use and dissemination of material nonpublic information regarding the Metals Index or USMI's portfolio.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The Sponsor represents that, in the event the Sponsor, SummerHaven Indexing, or SummerHaven becomes affiliated with a broker-dealer, it will implement a fire wall with respect to such broker-dealer regarding access to information concerning the composition and/or changes to a portfolio.
                    </P>
                </FTNT>
                <P>
                    The investment objective of USMI is for the daily changes in percentage terms of its Units' net asset value (“NAV”) to reflect the daily changes in percentage terms of the SummerHaven Dynamic Metals Index Total Return (the “Metals Index”), less USMI's expenses.
                    <SU>7</SU>
                    <FTREF/>
                     The Metals Index is a metal sector index designed to broadly represent industrial and precious metals while overweighting the components that are assessed to be in a low inventory state and underweighting the components assessed to be in a high inventory state. The Metals Index consists of six base metals—aluminum, copper, zinc, nickel, tin, and lead—and four precious metals: gold, silver, platinum, and palladium. Each metal is assigned a base weight in the Metals Index based on an assessment of market liquidity and the metal's overall economic importance.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         The Metals Index is owned and maintained by SummerHaven Index Management, LLC (“SummerHaven Indexing”) and calculated and published by the Exchange.
                    </P>
                </FTNT>
                <P>
                    Futures contracts for metals in the Metals Index that are traded on New York Mercantile Exchange (“NYMEX”), London Metal Exchange (“LME”), and Commodity Exchange, Inc. (“COMEX”) are collectively referred to herein as “Eligible Metals Futures Contracts.” The 10 Eligible Metals Futures Contracts that at any given time have been designated as a component of the Metals Index are referred to as the “Benchmark Component Metals Futures Contracts.” The relative weighting of the Benchmark Component Metals Futures Contracts will change on a monthly basis, based on quantitative formulas developed by SummerHaven Indexing relating to the prices of the Benchmark Component Metals Futures Contracts.
                    <SU>8</SU>
                    <FTREF/>
                     USMI's investments also will be rebalanced on a monthly basis to track the changing nature of the Metals Index.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         More information about the Metals Index is available in the Notice and also may be obtained from SummerHaven Indexing's Web site at 
                        <E T="03">http//www.summerhavenindex.com</E>
                        .
                    </P>
                </FTNT>
                <P>USMI will seek to achieve its investment objective by investing to the fullest extent possible in Benchmark Component Metals Futures Contracts. Then, if constrained by regulatory requirements (as described below) or in view of market conditions (as described below), USMI will invest next in other Eligible Metals Futures Contracts based on the same metal as the futures contracts subject to such regulatory constraints or market conditions, and finally, to a lesser extent, in other exchange-traded futures contracts that are economically identical or substantially similar to the Benchmark Component Metals Futures Contracts if one or more other Eligible Metals Futures Contracts is not available. When USMI has invested to the fullest extent possible in exchange-traded futures contracts, USMI may then invest in other contracts and instruments based on the Benchmark Component Metals Futures Contracts or the metals included in the Metals Index, such as cash-settled options, forward contracts, cleared swap contracts and swap contracts other than cleared swap contracts. Other exchange-traded futures contracts that are economically identical or substantially similar to the Benchmark Component Metals Futures Contracts and other contracts and instruments based on the Benchmark Component Metals Futures Contracts, as well as metals included in the Metals Index, are collectively referred to as “Other Metals-Related Investments,” and together with Benchmark Component Metals Futures Contracts and other Eligible Metals Futures Contracts, “Metals Interests.”</P>
                <P>USMI also invests in short-term Treasury Securities or holds cash to meet its current or potential margin or collateral requirements with respect to its investments in Metals Interests and invests cash not required to be used as margin or collateral.</P>
                <P>
                    <E T="03">Regulatory Requirements.</E>
                     As noted above, USMI may at times invest in other Eligible Metal Futures Contracts based on the same metal as the futures contracts subject to regulatory constraints (as described below), and then, to a lesser extent, in Other Metals-Related Investments in order to comply with regulatory requirements. An example of such regulatory requirements would be if USMI is required by law or regulation, or by one of its regulators, including a futures exchange, to reduce its position in one or more Benchmark Component Metals Futures Contracts to the applicable position limit or to a specified accountability level for such contracts, USMI's assets could be invested in one or more other Eligible Metal Futures Contracts. If one or more such Eligible Metal Futures Contracts were unavailable or economically impracticable, USMI could invest in Other Metals-Related Investments that are intended to replicate the return on the Metals Index or particular Benchmark Component Metals Futures Contracts. Another example would be if, because USMI's assets were reaching higher levels, it exceeded position limits, accountability levels or other regulatory limits and, to avoid triggering such limits or levels, it invested in one or more other Eligible Metal Futures Contracts to the extent practicable and then in Other Metals-Related Investments.
                </P>
                <P>
                    When investing in Other Metals-Related Investments, USMI will first invest in other exchange traded futures contracts that are economically identical or substantially similar to the Benchmark Component Metals Futures Contracts and then in cash-settled 
                    <PRTPAGE P="66341"/>
                    options, forward contracts, cleared swap contracts and swap contracts other than cleared swap contracts.
                </P>
                <P>
                    <E T="03">Market Conditions.</E>
                     As also noted above, there may be market conditions that could cause USMI to invest in other Eligible Metal Futures Contracts that are based on the same metal as the futures contracts subject to such market conditions (as described below). One such type of market condition would be where demand for Benchmark Component Metals Futures Contracts exceeded supply and as a result USMI was able to obtain more favorable terms under other Eligible Metal Futures Contracts. An example of more favorable terms would be where the aggregate costs to USMI from investing in other Eligible Metal Futures Contracts (including actual or expected direct costs such as the costs to buy, hold, or sell such investments, as well as indirect costs such as opportunity costs) were less than the costs of investing in Benchmark Component Metal Futures Contracts. Only after USMI becomes subject to position limits in any Eligible Metal Futures Contracts will USMI invest in Other Metals-Related Investments to replicate exposure to the Eligible Metal Futures Contract that is position-limited. Generally, USMI will only invest in this manner in other Eligible Metal Futures Contracts or Other Metals-Related Investments if it results in materially more favorable terms, and if such investments result in a specific benefit for USMI or its shareholders, such as being able to more closely track its benchmark.
                </P>
                <HD SOURCE="HD2">B. USAI</HD>
                <P>
                    USAI's trading advisor is SummerHaven. The Sponsor expects to manage USAI's investments directly, using the trading advisory services of SummerHaven for guidance with respect to the Agriculture Index and the Sponsor's selection of investments on behalf of USAI. The Sponsor, SummerHaven Indexing and SummerHaven are not affiliated with a broker-dealer and are subject to procedures designed to prevent the use and dissemination of material nonpublic information regarding the Agriculture Index or USAI's portfolio.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See supra</E>
                         note 6.
                    </P>
                </FTNT>
                <P>
                    The investment objective of USAI is for the daily changes in percentage terms of its Units' NAV to reflect the daily changes in percentage terms of the SummerHaven Dynamic Agriculture Index Total Return (the “Agriculture Index”),
                    <SU>10</SU>
                    <FTREF/>
                     less USAI's expenses. The Agriculture Index consists of fourteen agricultural markets: soybeans, corn, soft red winter wheat, hard red winter wheat, soybean oil, soybean meal, canola, sugar, cocoa, coffee, cotton, live cattle, feeder cattle and lean hogs. Each agricultural commodity is assigned a base weight in the Agriculture Index based on an assessment of market liquidity and the commodity's overall economic importance.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         The Agriculture Index is owned and maintained by SummerHaven Indexing and calculated and published by the Exchange.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         More information about the Agriculture Index is available in the Notice and also may be obtained from SummerHaven Indexing's Web site at 
                        <E T="03">http://www.summerhavenindex.com</E>
                        .
                    </P>
                </FTNT>
                <P>Futures contracts for agricultural commodities in the Agriculture Index that are currently traded on the ICE Futures (“ICE Futures”), Chicago Board of Trade (“CBOT”), Chicago Mercantile Exchange (“CME”), Kansas City Board of Trade (“KCBT”) and ICE Futures Canada are collectively referred to herein as “Eligible Agriculture Futures Contracts.” The 14 Eligible Agriculture Futures Contracts that at any given time have been designated as a component of the Agriculture Index are referred to as the “Benchmark Component Agriculture Futures Contracts.” The relative weighting of the Benchmark Component Agriculture Futures Contracts will change on a monthly basis, based on quantitative formulas developed by SummerHaven Indexing relating to the prices of the Benchmark Component Agriculture Futures Contracts. USAI's investments also will be rebalanced on a monthly basis to track the changing nature of the Agriculture Index.</P>
                <P>USAI will seek to achieve its investment objective by investing to the fullest extent possible in Benchmark Component Agriculture Futures Contracts. Then, if constrained by regulatory requirements (described below) or in view of market conditions (described below), USAI will invest next in other Eligible Agriculture Futures Contracts based on the same agricultural commodity as the futures contracts subject to such regulatory constraints or market conditions, and finally, to a lesser extent, in other exchange traded futures contracts that are economically identical or substantially similar to the Benchmark Component Agriculture Futures Contracts, if one or more Eligible Agriculture Futures Contracts is not available. When USAI has invested to the fullest extent possible in exchange-traded futures contracts, USAI may then invest in other contracts and instruments based on the Benchmark Component Agriculture Futures Contracts or the agricultural commodities included in the Agriculture Index, such as cash-settled options, forward contracts, cleared swap contracts and swap contracts other than cleared swap contracts. Other exchange-traded futures contracts that are economically identical or substantially similar to the Benchmark Component Agriculture Futures Contracts and other contracts and instruments based on the Benchmark Component Agriculture Futures Contracts, as well as metals included in the Agriculture Index, are collectively referred to as “Other Agriculture-Related Interests,” and together with Benchmark Component Agriculture Futures Contracts and other Eligible Agriculture Futures Contracts, “Agriculture Interests.”</P>
                <P>USAI also invests in short-term Treasury Securities or holds cash to meet its current or potential margin or collateral requirements with respect to its investments in Agriculture Interests and invests cash not required to be used as margin or collateral.</P>
                <P>
                    <E T="03">Regulatory Requirements.</E>
                     As noted above, USAI may at times invest in Eligible Agriculture Futures Contracts based on the same agricultural commodity as the futures contracts subject to regulatory constraints (as described below), and then to a lesser extent in Other Agriculture-Related Investments in order to comply with regulatory requirements. An example of such regulatory requirements would be if USAI is required by law or regulation, or by one of its regulators, including a futures exchange, to reduce its position in one or more Benchmark Component Agriculture Futures Contracts to the applicable position limit or to a specified accountability level for such contracts, USAI's assets could be invested in one or more other Eligible Agriculture Futures Contracts. If one or more such Eligible Agriculture Futures Contracts was unavailable or economically impracticable, USAI could invest in Other Agriculture-Related Investments that are intended to replicate the return on the Agriculture Index or particular Benchmark Component Agriculture Futures Contracts. Another example would be if because USAI's assets were reaching higher levels, it exceeded position limits, accountability levels or other regulatory limits and, to avoid triggering such limits or levels, it invested in one or more other Eligible Agriculture Futures Contracts to the extent practicable and then in Other Agriculture-Related Investments.
                </P>
                <P>
                    When investing in Other Agriculture-Related Investments, USAI will first invest in other exchange traded futures 
                    <PRTPAGE P="66342"/>
                    contracts that are economically identical or substantially similar to the Benchmark Component Agriculture Futures Contracts and then in cash settled options, forward contracts, cleared swap contracts and swap contracts other than cleared swap contracts.
                </P>
                <P>
                    <E T="03">Market Conditions.</E>
                     As also noted above, there may be market conditions that could cause USAI to invest in other Eligible Agriculture Futures Contracts that are based on the same agricultural commodity as the futures contracts subject to such market conditions (as described below). One such type of market condition would be where demand for Benchmark Component Agriculture Futures Contracts exceeded supply and as a result USAI was able to obtain more favorable terms under other Eligible Agriculture Futures Contracts. An example of more favorable terms would be where the aggregate costs to USAI from investing in other Eligible Agriculture Futures Contracts or Other Agriculture-Related Investments (including actual or expected direct costs such as the costs to buy, hold, or sell such investments, as well as indirect costs such as opportunity costs) were less than the costs of investing in Benchmark Component Agriculture Futures Contracts. Only after USAI becomes subject to position limits in any Eligible Agriculture Futures Contract will USAI invest in Other Agriculture-Related Investments to replicate exposure to the Eligible Agriculture Futures Contract that is position-limited. Generally, USAI will only invest in this manner in other Eligible Agriculture Futures Contracts or Other Agriculture-Related Investments if it results in materially more favorable terms, and if such investments result in a specific benefit for USAI or its shareholders, such as being able to more closely track its benchmark.
                </P>
                <HD SOURCE="HD2">C. USCUI</HD>
                <P>
                    USCUI's trading advisor is SummerHaven. The Sponsor expects to manage USCUI's investments directly, using the trading advisory services of SummerHaven for guidance with respect to the Copper Index and the Sponsor's selection of investments on behalf of USCUI. The Sponsor, SummerHaven Indexing and SummerHaven are not affiliated with a broker-dealer and are subject to procedures designed to prevent the use and dissemination of material nonpublic information regarding the Copper Index or USCUI's portfolio.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See supra</E>
                         note 6.
                    </P>
                </FTNT>
                <P>
                    The investment objective of USCUI is for the daily changes in percentage terms of its Units' NAV to reflect the daily changes in percentage terms of the SummerHaven Copper Index Total Return (the “Copper Index”),
                    <SU>13</SU>
                    <FTREF/>
                     less USCUI's expenses. The Copper Index is designed to reflect the performance of the investment returns from a portfolio of futures contracts for copper that are traded on the COMEX (such futures contracts, collectively, “Eligible Copper Futures Contracts”). The Copper Index attempts to maximize backwardation and minimize contango while utilizing contracts in liquid portions of the futures curve.
                    <SU>14</SU>
                    <FTREF/>
                     The Copper Index is comprised of either two or three Eligible Copper Futures Contracts that are selected on a monthly basis based on quantitative formulas relating to the prices of the Eligible Copper Futures Contracts developed by SummerHaven Indexing. USCUI's positions in Copper Interests will be rebalanced on a monthly basis in order to track the changing nature of the Copper Index.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         The Copper Index is owned and maintained by SummerHaven Indexing and calculated and published by the Exchange.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         More information about the Copper Index is available in the Notice and also may be obtained from SummerHaven Indexing's Web site at 
                        <E T="03">http://www.summerhavenindex.com</E>
                        .
                    </P>
                </FTNT>
                <P>USCUI will seek to achieve its investment objective by investing to the fullest extent possible in the Benchmark Component Copper Futures Contracts, which are the Eligible Copper Futures Contracts that at any given time make up the Copper Index. Then if constrained by regulatory requirements (described below) or in view of market conditions (described below), USCUI will invest next in other Eligible Copper Futures Contracts, and finally to a lesser extent, in other exchange-traded futures contracts that are economically identical or substantially similar to the Benchmark Component Copper Futures Contracts if one or more other Eligible Copper Futures Contracts is not available. When USCUI has invested to the fullest extent possible in exchange-traded futures contracts, USCUI may then invest in other contracts and instruments based on the Benchmark Component Copper Futures Contracts, other Eligible Copper Futures Contracts or copper, such as cash-settled options, forward contracts, cleared swap contracts and swap contracts other than cleared swap contracts. Other exchange-traded futures contracts that are economically identical or substantially similar to the Benchmark Component Copper Futures Contracts and other contracts and instruments based on the Benchmark Component Copper Futures Contracts, are collectively referred to as “Other Copper-Related Investments,” and together with Benchmark Component Copper Futures Contracts and other Eligible Copper Futures Contracts, “Copper Interests.”</P>
                <P>After fulfilling the margin and collateral requirements with respect to USCUI's Copper Interests, the Sponsor will invest the remainder of USCUI's proceeds from the sale of baskets in Treasury Securities or cash equivalents, and/or hold such assets in cash (generally in interest-bearing accounts).</P>
                <P>
                    <E T="03">Regulatory Requirements.</E>
                     As noted above, USCUI may at times invest in other Eligible Copper Futures Contracts based on the same metal as the futures contracts subject to regulatory constraints (as described below), and finally to a lesser extent, in other exchange traded futures contracts that are economically identical or substantially similar to the Benchmark Component Copper Futures Contracts if one or more other Eligible Copper Futures Contracts is not available in order to comply with regulatory requirements. An example of such regulatory requirements would be if USCUI is required by law or regulation, or by one of its regulators, including a futures exchange, to reduce its position in one or more Benchmark Component Copper Futures Contracts to the applicable position limit or to a specified accountability level for such contracts, USCUI's assets could be invested in one or more other Eligible Copper Futures Contracts. If one or more such Eligible Copper Futures Contracts were unavailable or economically impracticable, USCUI could invest in Other Copper-Related Investments that are intended to replicate the return on the Copper Index or particular Benchmark Component Copper Futures Contracts. Another example would be if, because USCUI's assets were reaching higher levels, it exceeded position limits, accountability levels or other regulatory limits and, to avoid triggering such limits or levels, it invested in one or more other Eligible Copper Futures Contracts to the extent practicable and then in Other Copper-Related Investments.
                </P>
                <P>
                    When investing in Other Copper-Related Investments, USCUI will first invest in other exchange traded futures contracts that are economically identical or substantially similar to the Benchmark Component Copper Futures Contracts, other Eligible Copper Futures Contracts, and then in cash-settled options, forward contracts, cleared swap contracts and swap contracts other than cleared swap contracts.
                    <PRTPAGE P="66343"/>
                </P>
                <P>
                    <E T="03">Market Conditions.</E>
                     As also noted above, there may be market conditions that could cause USCUI to invest in other Eligible Copper Futures Contracts that are based on the same metal as the futures contracts subject to such market conditions (as described below). One such type of market condition would be where demand for Benchmark Component Copper Futures Contracts exceeded supply and as a result USCUI was able to obtain more favorable terms under other Eligible Copper Futures Contracts. An example of more favorable terms would be where the aggregate costs to USCUI from investing in other Eligible Copper Futures Contracts (including actual or expected direct costs such as the costs to buy, hold, or sell such investments, as well as indirect costs such as opportunity costs) were less than the costs of investing in Benchmark Component Copper Futures Contracts. Only after USCUI becomes subject to position limits in any Eligible Copper Futures Contract will USCUI invest in Other Copper-Related Investments to replicate exposure to the Eligible Copper Futures Contract that is position-limited. Generally, USCUI will only invest in this manner in other Eligible Copper Futures Contracts or Other Copper-Related Investments if it results in materially more favorable terms, and if such investments result in a specific benefit for USCUI or its shareholders, such as being able to more closely track its benchmark.
                </P>
                <P>
                    Additional details regarding the Trust, Units, trading policies of the Funds, creations and redemptions of the Units, investment risks, Benchmark performance, NAV calculation, the dissemination and availability of information about the underlying assets, trading halts, applicable trading rules, surveillance, and the Information Bulletin, among other things, can be found in the Notice and/or the Registration Statement, as applicable.
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         Notice and Registration Statement, 
                        <E T="03">supra</E>
                         notes 3 and 4, respectively.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Discussion and Commission's Findings</HD>
                <P>
                    After careful review, the Commission finds that the proposed rule change to list and trade the Units of the Funds is consistent with the requirements of Section 6 of the Act and the rules and regulations thereunder applicable to a national securities exchange.
                    <SU>16</SU>
                    <FTREF/>
                     In particular, the Commission finds that the proposed rule change is consistent with the requirements of Section 6(b)(5) of the Act,
                    <SU>17</SU>
                    <FTREF/>
                     which requires, among other things, that the Exchange's rules be designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to foster cooperation and coordination with persons engaged in facilitating transactions in securities, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and, in general, to protect investors and the public interest. The Commission notes that the Funds and the Units must comply with the requirements of NYSE Arca Equities Rule 8.200 and Commentary .02 thereto to be listed and traded on the Exchange.
                </P>
                <P>
                    The Commission finds that the proposal to list and trade the Units on the Exchange is consistent with Section 11A(a)(1)(C)(iii) of the Act,
                    <SU>18</SU>
                    <FTREF/>
                     which sets forth Congress's finding that it is in the public interest and appropriate for the protection of investors and the maintenance of fair and orderly markets to assure the availability to brokers, dealers, and investors of information with respect to quotations for, and transactions in, securities. Quotation and last-sale information for the Units will be available via the Consolidated Tape Association high-speed line, and the underlying index levels will be disseminated by the Exchange and will be updated at least every 15 seconds during NYSE Arca Core Trading Hours, from 9:30 a.m. E.T. to 4 p.m. E.T., except for the period between the close of trading of all applicable futures contracts on futures exchanges and the close of the NYSE Arca Core Trading Session, at which point the underlying index values will be static.
                    <SU>19</SU>
                    <FTREF/>
                     In addition, the Indicative Fund Value (“IFV”) for each Fund will be disseminated on a per-Unit basis by the Exchange at least every 15 seconds during the NYSE Arca Core Trading Session.
                    <SU>20</SU>
                    <FTREF/>
                     The NAV for the Funds' Units will be calculated by the Administrator once a day and will be disseminated daily to all market participants after 4 p.m. E.T. The Funds will provide Web site disclosure of portfolio holdings daily and will include, as applicable, the names and value (in U.S. dollars) of financial instruments and characteristics of such instruments and cash equivalents, and amount of cash held in the portfolios of the Funds. The closing prices and settlement prices of the futures contracts also are readily available from the Web sites of the relevant futures exchanges, automated quotation systems, published or other public sources, or on-line information services such as Bloomberg or Reuters. Complete real-time data for the futures contracts is available by subscription from Reuters and Bloomberg. The relevant futures exchanges also provide delayed futures information on current and past trading sessions and market news free of charge on their respective Web sites. The specific contract specifications for the futures contracts are also available on such Web sites, as well as other financial informational sources. Information regarding exchange-traded cash-settled options and cleared swap contracts will be available from the applicable exchanges and major market data vendors.
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         In approving this proposed rule change, the Commission notes that it has considered the proposed rule's impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         15 U.S.C. 78k-1(a)(1)(C)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         In addition, the closing prices and settlement prices of the futures contracts held by the Funds are readily available from the Web sites of the relevant futures exchanges, automated quotation systems, published or other public sources, or on-line information services such as Bloomberg or Reuters. The relevant futures exchanges also provide delayed futures information on current and past trading sessions and market news free of charge on their respective Web sites.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         The normal trading hours of the relevant futures exchanges vary, with some ending their trading hours before the close of the Core Trading Session on NYSE Arca (for example, the normal trading hours of the NYMEX are 10 a.m. E.T. to 2:30 p.m. E.T.). When a Fund holds applicable Benchmark Component Futures Contracts from futures exchanges with different trading hours than NYSE Arca, there will be a gap in time at the beginning and/or the end of each day during which Units will be traded on NYSE Arca, but real-time futures exchange trading prices for Applicable Benchmark Component Futures Contracts traded on such futures exchanges will not be available. As a result, during those gaps there will be no update to the IFV. A static IFV will be disseminated between the close of trading of all applicable Futures Contracts on futures exchanges and the close of the NYSE Arca Core Trading Session.
                    </P>
                </FTNT>
                <P>
                    The Commission further believes that the proposal to list and trade the Units is reasonably designed to promote fair disclosure of information that may be necessary to price the Units appropriately and to prevent trading when a reasonable degree of transparency cannot be assured. If the Exchange becomes aware that the NAV with respect to the Units is not disseminated to all market participants at the same time, it will halt trading in the Units until such time as the NAV is available to all market participants. Further, the Exchange represents that it may halt trading during the day in which an interruption to the dissemination of the IFV or the value of the underlying futures contracts occurs. If the interruption to the dissemination of the IFV or the value of the underlying futures contracts persists past the trading day in which it occurred, the Exchange will halt trading no later than 
                    <PRTPAGE P="66344"/>
                    the beginning of the trading day following the interruption. In addition, the Web site disclosure of the portfolio composition of each Fund will occur at the same time as the disclosure by the Sponsor of the portfolio composition to authorized participants so that all market participants are provided portfolio composition information at the same time. Therefore, the same portfolio information will be provided on the public Web site as well as in electronic files provided to authorized purchasers. Accordingly, each investor will have access to the current portfolio composition of the Funds through each Fund's Web site. The Exchange may halt trading in the Units if trading is not occurring in the underlying futures contracts or if other unusual conditions or circumstances detrimental to the maintenance of a fair and orderly market are present.
                    <SU>21</SU>
                    <FTREF/>
                     In addition, the Exchange represents that the Sponsor, SummerHaven Indexing and SummerHaven are not affiliated with a broker-dealer and are subject to procedures designed to prevent the use and dissemination of material nonpublic information regarding the underlying index levels or the Funds' portfolios. Lastly, the trading of the Units will be subject to NYSE Arca Equities Rule 8.200, Commentary .02(e), which sets forth certain restrictions on ETP Holders 
                    <SU>22</SU>
                    <FTREF/>
                     acting as registered Market Makers 
                    <SU>23</SU>
                    <FTREF/>
                     in Trust Issued Receipts to facilitate surveillance.
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         With respect to trading halts, the Exchange may consider other relevant factors in exercising its discretion to halt or suspend trading in the Units of the Funds. Trading in the Units of the Funds will be subject to halts caused by extraordinary market volatility pursuant to the Exchange's circuit breaker rules in NYSE Arca Equities Rule 7.12. Trading also may be halted because of market conditions or for reasons that, in the view of the Exchange, make trading in the Units inadvisable.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">See</E>
                         NYSE Arca Equities Rule 1.1(n) (defining ETP Holder).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">See</E>
                         NYSE Arca Equities Rule 1.1(u) (defining Market Maker).
                    </P>
                </FTNT>
                <P>The Exchange has represented that the Units are deemed to be equity securities, thus rendering trading in the Units subject to the Exchange's existing rules governing the trading of equity securities. In support of this proposal, the Exchange has made representations, including:</P>
                <P>(1) The Funds will be subject to the criteria in NYSE Arca Equities Rule 8.200 and Commentary .02 thereto for initial and continued listing of the Units.</P>
                <P>(2) The Exchange has appropriate rules to facilitate transactions in the Units during all trading sessions.</P>
                <P>(3) The Exchange's surveillance procedures are adequate to properly monitor Exchange trading of the Units in all trading sessions and to deter and detect violations of Exchange rules and applicable federal securities laws.</P>
                <P>(4) With respect to the Funds' futures contracts traded on exchanges, not more than 10% of the weight of such futures contracts in the aggregate shall consist of components whose principal trading market is not a member of the Intermarket Surveillance Group or is a market with which the Exchange does not have a comprehensive surveillance sharing agreement.</P>
                <P>(5) Prior to the commencement of trading, the Exchange will inform its ETP Holders in an Information Bulletin of the special characteristics and risks associated with trading the Units. Specifically, the Information Bulletin will discuss the following: (a) The risks involved in trading the Units during the Opening and Late Trading Sessions when an updated IFV will not be calculated or publicly disseminated; (b) the procedures for purchases and redemptions of Units in creation baskets and redemption baskets (and that Units are not individually redeemable); (c) NYSE Arca Equities Rule 9.2(a), which imposes a duty of due diligence on its ETP Holders to learn the essential facts relating to every customer prior to trading the Units; (d) how information regarding the IFV is disseminated; (e) the requirement that ETP Holders deliver a prospectus to investors purchasing newly issued Units prior to or concurrently with the confirmation of a transaction; and (f) trading information.</P>
                <P>(6) A minimum of 100,000 Units for each Fund will be outstanding as of the start of trading on the Exchange.</P>
                <P>
                    (7) With respect to application of Rule 10A-3 
                    <SU>24</SU>
                    <FTREF/>
                     under the Act, the Trust relies on the exception contained in Rule 10A-3(c)(7).
                    <SU>25</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         17 CFR 240.10A-3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         17 CFR 240.10A-3(c)(7).
                    </P>
                </FTNT>
                <P>
                    This approval order is based on the Exchange's representations.
                    <SU>26</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         The Commission notes that it does not regulate the market for futures in which the Fund plans to take positions, which is the responsibility of the Commodity Futures Trading Commission (“CFTC”). The CFTC has the authority to set limits on the positions that any person may take in futures. These limits may be directly set by the CFTC or by the markets on which the futures are traded. The Commission has no role in establishing position limits on futures, even though such limits could impact an exchange-traded product that is under the jurisdiction of the Commission.
                    </P>
                </FTNT>
                <P>
                    For the foregoing reasons, the Commission finds that the proposed rule change is consistent with Section 6(b)(5) of the Act 
                    <SU>27</SU>
                    <FTREF/>
                     and the rules and regulations thereunder applicable to a national securities exchange.
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Conclusion</HD>
                <P>
                    It is therefore ordered, pursuant to Section 19(b)(2) of the Act,
                    <SU>28</SU>
                    <FTREF/>
                     that the proposed rule change (SR-NYSEArca-2011-63) be, and it hereby is, approved.
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>29</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>29</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Kevin M. O'Neill,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27698 Filed 10-25-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-65599; File No. SR-FINRA-2011-043]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Financial Industry Regulatory Authority, Inc.; Order Approving Proposed Rule Change To Amend FINRA Rule 0160 (Definitions in FINRA By-Laws)</SUBJECT>
                <DATE>October 20, 2011.</DATE>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    On August 31, 2011, Financial Industry Regulatory Authority, Inc. (“FINRA”) (f/k/a National Association of Securities Dealers (“NASD”)) filed with the Securities and Exchange Commission (“Commission”), pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change to amend FINRA Rule 1060 (Definitions in FINRA By-Laws). The proposed rule change was published for comment in the 
                    <E T="04">Federal Register</E>
                     on September 16, 2011.
                    <SU>3</SU>
                    <FTREF/>
                     The Commission received no comments on the proposal. This order approves the proposed rule change.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 65313 (September 12, 2011), 76 FR 57784 (“Notice”).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Description of the Proposal</HD>
                <P>
                    FINRA is proposing to amend FINRA Rule 0160 (Definitions in FINRA By-Laws). As part of the process of developing the new consolidated rulebook (“Consolidated FINRA Rulebook”),
                    <SU>4</SU>
                    <FTREF/>
                     the proposed rule change 
                    <PRTPAGE P="66345"/>
                    will amend FINRA Rule 0160. The proposed rule change will transfer certain defined terms from NASD Rule 0120 (Definitions) to FINRA Rule 0160, subject to certain amendments, as well as add new defined terms to reflect the conventions of the Consolidated FINRA Rulebook.
                    <SU>5</SU>
                    <FTREF/>
                     The proposed rule change will also eliminate as unnecessary or duplicative certain definitions contained in NASD Rule 0120. In addition, the proposed rule change will eliminate NASD Rule 0120 from the current FINRA rulebook.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The current FINRA rulebook consists of (1) FINRA Rules; (2) NASD Rules; and (3) rules incorporated from NYSE (“Incorporated NYSE Rules”) (together, the NASD Rules and Incorporated NYSE Rules are referred to as the “Transitional Rulebook”). While the NASD Rules generally apply to all FINRA members, the Incorporated NYSE 
                        <PRTPAGE/>
                        Rules apply only to those members of FINRA that are also members of the NYSE. The FINRA Rules apply to all FINRA members, unless such rules have a more limited application by their terms. For more information about the rulebook consolidation process, 
                        <E T="03">see Information Notice,</E>
                         March 12, 2008 (Rulebook Consolidation Process). For convenience, the Incorporated NYSE Rules are referred to as the NYSE Rules.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         FINRA Rule 0160 would be reorganized so that the defined terms are arranged alphabetically, as amended.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Notwithstanding the proposed transfer of certain defined terms from NASD Rule 0120 to FINRA Rule 0160 in the Consolidated FINRA Rulebook, the defined terms in FINRA Rule 0160 would continue to apply equally to both the Transitional Rulebook and the Consolidated FINRA Rulebook, as applicable. 
                        <E T="03">See also</E>
                         Securities Exchange Act Release No. 58643 (September 25, 2008), 73 FR 57174 (October 1, 2008) (Order Approving SR-FINRA-2008-021), discussing “Rules of General Applicability.”
                    </P>
                </FTNT>
                <P>
                    The proposed rule change will also transfer certain terms with either no or minor substantive changes to FINRA Rule 0160, as well as make minor and conforming changes to NASD Rule 0120(f)(2) and (f)(3) and FINRA Rule 0160(b)(3)(B) and (3)(C). The proposed rule change will also add defined terms to FINRA Rule 0160 because such terms are used throughout the Consolidated FINRA Rulebook.
                    <SU>7</SU>
                    <FTREF/>
                     Although the proposed rule change will not incorporate certain defined terms in NASD Rule 0120, FINRA represents that this will not eliminate any substantive FINRA requirements.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Notice at 57785.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    FINRA will announce the implementation date of the proposed rule change in a 
                    <E T="03">Regulatory Notice</E>
                     to be published no later than 90 days following this Commission approval. The effective date will be no later than 150 days following this Commission approval.
                </P>
                <HD SOURCE="HD1">III. Discussion and Commission Findings</HD>
                <P>
                    After careful review, the Commission finds that the proposed rule change is consistent with Section 15A(b)(6) of the Act,
                    <SU>9</SU>
                    <FTREF/>
                     which requires, among other things, that FINRA rules be designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, and, in general, to protect investors and the public interest. The Commission believes that the proposed rule change will provide clarity with respect to the defined terms for the Consolidated FINRA Rulebook by transferring certain defined terms from NASD Rule 0120 to FINRA Rule 0160 (subject to certain amendments), adding new defined terms to FINRA Rule 0160 to reflect the conventions of the Consolidated FINRA Rulebook and eliminating as unnecessary or duplicative certain definitions contained in NASD Rule 0120.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         15 U.S.C. 78
                        <E T="03">o</E>
                        -3(b)(6).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Conclusion</HD>
                <P>
                    <E T="03">It is therefore ordered,</E>
                     pursuant to Section 19(b)(2) of the Act,
                    <SU>10</SU>
                    <FTREF/>
                     that the proposed rule change (SR-FINRA-2011-043) be, and it hereby is, approved.
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>11</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Kevin M. O'Neill,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27697 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF STATE</AGENCY>
                <DEPDOC>[Public Notice 7650]</DEPDOC>
                <SUBJECT>U.S. Advisory Commission on Public Diplomacy; Notice of Meeting</SUBJECT>
                <P>The U.S. Advisory Commission on Public Diplomacy will hold a public meeting on November 29, 2011, in Santa Monica, CA, in partnership with the RAND Corporation. The meeting will take place at the RAND offices at 1176 Main Street in Santa Monica, CA, in the Forum Auditorium. The meeting will begin at 9 a.m. and end at 3 p.m. (doors open for registration and continental breakfast at 8:30 a.m.).</P>
                <P>
                    <E T="03">The topic is narratives:</E>
                     what they are, how they are shaped and countered. The conference will delve into the impact on narratives of actions and words (primarily U.S. but also others if lessons for us are clearly articulated), and the impact of environmental factors.
                </P>
                <P>
                    This meeting is open to the public, Members and staff of Congress, the State Department, Defense Department, the media, and other governmental and non-governmental organizations. To request further information, or to request reasonable accommodation, contact the Commission at (202) 203-7463 or 
                    <E T="03">pdcommission@state.gov.</E>
                     To attend, contact the RAND Corporation by phone at (412) 683-2300 ext 4906 or e-mail to 
                    <E T="03">maria_falvo@rand.org</E>
                     and provide your full name, citizenship (U.S. citizenship is not required to attend), and institutional/organizational affiliation.
                </P>
                <P>The United States Advisory Commission on Public Diplomacy appraises U.S. Government activities intended to understand, inform, and influence foreign publics. The Advisory Commission may conduct studies, inquiries, and meetings, as it deems necessary. It may assemble and disseminate information and issue reports and other publications, subject to the approval of the Chairperson, in consultation with the Executive Director. The Advisory Commission may undertake foreign travel in pursuit of its studies and coordinate, sponsor, or oversee projects, studies, events, or other activities that it deems desirable and necessary in fulfilling its functions.</P>
                <P>The Commission consists of seven members appointed by the President, by and with the advice and consent of the Senate. The members of the Commission shall represent the public interest and shall be selected from a cross section of educational, communications, cultural, scientific, technical, public service, labor, business, and professional backgrounds. Not more than four members shall be from any one political party. The President designates a member to chair the Commission.</P>
                <P>
                    <E T="03">The current members of the Commission are:</E>
                     Mr. William Hybl of Colorado, Chairman; Ambassador Lyndon Olson of Texas, Vice Chairman; Ambassador Penne Korth-Peacock of Texas; Ms. Lezlee Westine of Virginia; and, Mr. Sim Farar of California. Two seats on the Commission are currently vacant.
                </P>
                <P>The following individual has been nominated to the Commission but awaits Senate confirmation as of this writing: Anne Wedner of Illinois.</P>
                <P>The Advisory Commission was originally established under Section 604 of the United States Information and Exchange Act of 1948, as amended (22 U.S.C. 1469) and Section 8 of Reorganization Plan Numbered 2 of 1977. The U.S. Advisory Commission on Public Diplomacy is authorized by Public Law 101-246 (2009), 22 U.S.C. 6553, and has been further authorized through November 18, 2011. In the absence of subsequent legislation extending the authority for the Commission, this meeting will be cancelled.</P>
                <SIG>
                    <PRTPAGE P="66346"/>
                    <DATED>Dated: October 17, 2011.</DATED>
                    <NAME>Jamice M. Clayton, </NAME>
                    <TITLE>Administrative Assistant, U.S. Department of State.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27732 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4710-11-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Agency Information Collection Activities; Requests for Comments: Clearance of Renewed Approval of Information Collection; Organization Designation Authorization</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with the Paperwork Reduction Act of 1995, FAA invites public comments about our intention to request the Office of Management and Budget (OMB) approval to renew an information collection. The 
                        <E T="04">Federal Register</E>
                         Notice with a 60-day comment period soliciting comments on the following collection of information was published on August 24, 2011, vol. 76, no. 164, page 53023-53024. This collection involves organizations applying to perform certification functions on behalf of the FAA, including approving data and issuing various aircraft and organization certificates.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be submitted by November 25, 2011.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kathy DePaepe at (405) 954-9362, or by e-mail at: 
                        <E T="03">Kathy A. DePaepe @faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">OMB Control Number:</E>
                     2120-0704.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Organization Designation Authorization.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     FAA Forms 8100-11, 8100-12, 8100-13.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Renewal of an information collection.
                </P>
                <P>
                    <E T="03">Background:</E>
                     Subpart D to part 183 allows the FAA to appoint organizations as representatives of the administrator. As authorized, these organizations perform certification functions on behalf of the FAA. Applications are submitted to the appropriate FAA office and are reviewed by the FAA to determine whether the applicant meets the requirements necessary to be authorized as a representative of the Administrator. Procedures manuals are submitted and approved by the FAA as a means to ensure that the correct processes are utilized when performing functions on behalf of the FAA. These requirements are necessary to manage the various approvals issued by the organization and to document approvals issued and must be maintained in order to address potential future safety issues.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Approximately 83 applicants.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Information is collected on occasion.
                </P>
                <P>
                    <E T="03">Estimated Average Burden per Response:</E>
                     41.7 hours.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     5,158 hours.
                </P>
                <FP>
                    <E T="02">ADDRESSES:</E>
                     Interested persons are invited to submit written comments on the proposed information collection to the Office of Information and Regulatory Affairs, Office of Management and Budget. Comments should be addressed to the attention of the Desk Officer, Department of Transportation/FAA, and sent via electronic mail to 
                    <E T="03">oira_submission@omb.eop.gov,</E>
                     or faxed to (202) 395-6974, or mailed to the Office of Information and Regulatory Affairs, Office of Management and Budget, Docket Library, Room 10102, 725 17th Street, NW., Washington, DC 20503.
                </FP>
                <P>
                    <E T="03">Public Comments Invited:</E>
                     You are asked to comment on any aspect of this information collection, including (a) Whether the proposed collection of information is necessary for FAA's performance; (b) the accuracy of the estimated burden; (c) ways for FAA to enhance the quality, utility and clarity of the information collection; and (d) ways that the burden could be minimized 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>
                <SIG>
                    <DATED>Issued in Washington, DC, on October 20, 2011.</DATED>
                    <NAME>Albert R. Spence,</NAME>
                    <TITLE>FAA Assistant Information Collection Clearance Officer, IT Enterprises Business Services Division, AES-200.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27712 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Agency Information Collection Activities; Requests for Comments: Clearance of Renewed Approval of Information Collection; General Aviation and Air Taxi Activity and Avionics Survey</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, FAA invites public comments about our intention to request the Office of Management and Budget (OMB) approval to renew an information collection. Respondents to this survey are owners of general aviation aircraft. This information is used by FAA, NTSB, and other government agencies, the aviation industry, and others for safety assessment, planning, forecasting, cost/benefit analysis, and to target areas for research.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be submitted by December 27, 2011.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kathy DePaepe at (405) 954-9362, or by e-mail at: 
                        <E T="03">Kathy A. DePaepe @faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">OMB Control Number:</E>
                     2120-0060.
                </P>
                <P>
                    <E T="03">Title:</E>
                     General Aviation and Air Taxi Activity and Avionics Survey.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     There are no FAA forms associated with this collection.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Renewal of an information collection.
                </P>
                <P>
                    <E T="03">Background:</E>
                     Title 49, United States Code, empowers the Secretary of Transportation to collect and disseminate information relative to civil aeronautics, to study the possibilities for development of air commerce and the aeronautical industries, and to make long-range plans for, and formulate policy with respect to, the orderly development and use of the navigable airspace, radar installations and all other aids for air navigation. Respondents to this survey are owners of general aviation aircraft. This information is used by FAA, NTSB, and other government agencies, the aviation industry, and others for safety assessment, planning, forecasting, cost/benefit analysis, and to target areas for research.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Approximately 83,500 owners of general aviation aircraft.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Information is collected annually.
                </P>
                <P>
                    <E T="03">Estimated Average Burden per Response:</E>
                     20 minutes.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     13,000 hours.
                </P>
                <P>
                    <E T="02">ADDRESSES:</E>
                     Send comments to the FAA at the following address: Ms. Kathy DePaepe, Room 126B, Federal Aviation Administration, AES-200, 6500 S. MacArthur Blvd, Oklahoma City, OK 73169.
                </P>
                <P>
                    <E T="03">Public Comments Invited:</E>
                     You are asked to comment on any aspect of this information collection, including (a) Whether the proposed collection of information is necessary for FAA's performance; (b) the accuracy of the estimated burden; (c) ways for FAA to 
                    <PRTPAGE P="66347"/>
                    enhance the quality, utility and clarity of the information collection; and (d) ways that the burden could be minimized 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>
                <SIG>
                    <DATED>Issued in Washington, DC on October 20, 2011.</DATED>
                    <NAME>Albert R. Spence,</NAME>
                    <TITLE>FAA Assistant Information Collection Clearance Officer, IT Enterprises Business Services Division, AES-200.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27628 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Agency Information Collection Activities; Requests for Comments: Clearance of Renewed Approval of Information Collection; Type Certification Procedures for Changed Products</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, FAA invites public comments about our intention to request the Office of Management and Budget (OMB) approval to renew an information collection. 14 CFR part 21 may require applicants to demonstrate compliance with the latest regulations in effect on the date of application for amended Type Certificates (TC) or Supplemental TCs for aeronautical products.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be submitted by December 27, 2011.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kathy DePaepe at (405) 954-9362, or by e-mail at: 
                        <E T="03">Kathy A. DePaepe @faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P SOURCE="NPAR">
                    <E T="03">OMB Control Number:</E>
                     2120-0657.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Type Certification Procedures for Changed Products.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     There are no FAA forms associated with this collection.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Renewal of an information collection.
                </P>
                <P>
                    <E T="03">Background:</E>
                     14 CFR part 21 requires that, with certain exceptions, all aviation product changes comply with the latest airworthiness standards when determining the certification basis for aeronautical products. This process is intended to increase safety by applying the latest regulations where practicable. A certification application request, in letter form, and a supporting data package is made to the appropriate Federal Aviation Administration (FAA) Aircraft Certification Office by an aircraft/product manufacturer/modifier.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Approximately 2,558 manufacturers/modifiers.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Information is collected on occasion.
                </P>
                <P>
                    <E T="03">Estimated Average Burden per Response:</E>
                     7.35 hours.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     18,815 hours.
                </P>
                <FP>
                    <E T="02">ADDRESSES:</E>
                     Send comments to the FAA at the following address: Ms. Kathy DePaepe, Room 126B, Federal Aviation Administration, AES-200, 6500 S. MacArthur Blvd., Oklahoma City, OK 73169.
                </FP>
                <P>
                    <E T="03">Public Comments Invited:</E>
                     You are asked to comment on any aspect of this information collection, including (a) Whether the proposed collection of information is necessary for FAA's performance; (b) the accuracy of the estimated burden; (c) ways for FAA to enhance the quality, utility and clarity of the information collection; and (d) ways that the burden could be minimized 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>
                <SIG>
                    <DATED>Issued in Washington, DC on October 19, 2011.</DATED>
                    <NAME>Albert R. Spence,</NAME>
                    <TITLE>FAA Assistant Information Collection Clearance Officer, IT Enterprises Business Services Division, AES-200.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27635 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Agency Information Collection Activities; Requests for Comments: Clearance of Renewed Approval of Information Collection; Hazardous Materials Training Requirements</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with the Paperwork Reduction Act of 1995, FAA invites public comments about our intention to request the Office of Management and Budget (OMB) approval to renew an information collection. The 
                        <E T="04">Federal Register</E>
                         Notice with a 60-day comment period soliciting comments on the following collection of information was published on August 24, 2011, vol. 76, no. 164, page 53024-53025. The collection involves requirements for certain repair stations to provide documentation showing that persons handling hazmat for transportation have been trained following DOT guidelines.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be submitted by November 25, 2011.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kathy DePaepe at (405) 954-9362, or by e-mail at: 
                        <E T="03">Kathy A. DePaepe @faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <P SOURCE="NPAR">
                    <E T="03">OMB Control Number:</E>
                     2120-0705.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Hazardous Materials Training Requirements.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     There are no FAA forms associated with this collection.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Renewal of an information collection.
                </P>
                <P>
                    <E T="03">Background:</E>
                     The FAA, as prescribed in 14 CFR parts 121 and 135, requires certificate holders to submit manuals and hazmat training programs, or revisions to an approved hazmat training program to obtain initial and final approval as part of the FAA certification process. Original certification is completed in accordance with 14 CFR part 119. Continuing certification is completed in accordance with part 121 and part 135. The FAA uses the approval process to determine compliance of the hazmat training programs with the applicable regulations, national policies and safe operating practices. The FAA must ensure that the documents adequately establish safe operating procedures.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Approximately 2,772 operators.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Information is collected on occasion.
                </P>
                <P>
                    <E T="03">Estimated Average Burden per Response:</E>
                     7 hours.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     6,900 hours.
                </P>
                <FP>
                    <E T="02">ADDRESSES:</E>
                    Interested persons are invited to submit written comments on the proposed information collection to the Office of Information and Regulatory Affairs, Office of Management and Budget. Comments should be addressed to the attention of the Desk Officer, Department of Transportation/FAA, and sent via electronic mail to 
                    <E T="03">oira_submission@omb.eop.gov,</E>
                     or faxed to (202) 395-6974, or mailed to the Office of Information and Regulatory Affairs, Office of Management and Budget, Docket Library, Room 10102, 725 17th Street, NW., Washington, DC 20503.
                </FP>
                <P>
                    <E T="03">Public Comments Invited:</E>
                     You are asked to comment on any aspect of this information collection, including (a) Whether the proposed collection of information is necessary for FAA's performance; (b) the accuracy of the estimated burden; (c) ways for FAA to 
                    <PRTPAGE P="66348"/>
                    enhance the quality, utility and clarity of the information collection; and (d) ways that the burden could be minimized 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>
                <SIG>
                    <DATED>Issued in Washington, DC, on October 20, 2011.</DATED>
                    <NAME>Albert R. Spence,</NAME>
                    <TITLE>FAA Assistant Information Collection Clearance Officer, IT Enterprises Business Services Division, AES-200.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27713 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Agency Information Collection Activities; Requests for Comments: Clearance of Renewed Approval of Information Collection; Aviation Insurance</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with the Paperwork Reduction Act of 1995, FAA invites public comments about our intention to request the Office of Management and Budget (OMB) approval to renew an information collection. The 
                        <E T="04">Federal Register</E>
                         Notice with a 60-day comment period soliciting comments on the following collection of information was published on August 24, 2011, vol. 76, no. 164, page 53022-53023. The requested information is included in air carriers applications for insurance when insurance is not available from private sources.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be submitted by November 25, 2011.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kathy DePaepe at (405) 954-9362, or by e-mail at: 
                        <E T="03">Kathy A. DePaepe @faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    <E T="03">OMB Control Number:</E>
                     2120-0514.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Aviation Insurance.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     There are no FAA forms associated with this collection.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Renewal of an information collection.
                </P>
                <P>
                    <E T="03">Background:</E>
                     The information submitted by applicants for insurance under Chapter 443 of Title 49 U.S.C. is used by the FAA to identify the eligibility of parties to be insured, the amount of coverage required, and insurance premiums. Without collection of this information, the FAA would not be able to issue required insurance.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Approximately 61 applicants.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Information is collected on occasion.
                </P>
                <P>
                    <E T="03">Estimated Average Burden per Response:</E>
                     4 hours.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     616 hours.
                </P>
                <FP>
                    <E T="02">ADDRESSES:</E>
                     Interested persons are invited to submit written comments on the proposed information collection to the Office of Information and Regulatory Affairs, Office of Management and Budget. Comments should be addressed to the attention of the Desk Officer, Department of Transportation/FAA, and sent via electronic mail to 
                    <E T="03">oira_submission@omb.eop.gov,</E>
                     or faxed to (202) 395-6974, or mailed to the Office of Information and Regulatory Affairs, Office of Management and Budget, Docket Library, Room 10102, 725 17th Street, NW., Washington, DC 20503.
                </FP>
                <P>
                    <E T="03">Public Comments Invited:</E>
                     You are asked to comment on any aspect of this information collection, including (a) Whether the proposed collection of information is necessary for FAA's performance; (b) the accuracy of the estimated burden; (c) ways for FAA to enhance the quality, utility and clarity of the information collection; and (d) ways that the burden could be minimized 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>
                <SIG>
                    <DATED>Issued in Washington, DC, on October 20, 2011.</DATED>
                    <NAME>Albert R. Spence,</NAME>
                    <TITLE>FAA Assistant Information Collection Clearance Officer, IT Enterprises Business Services Division, AES-200.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27710 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Requests for Comments; Clearance of Renewed Approval of Information Collection: FAA Airport Master Record</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with the Paperwork Reduction Act of 1995, FAA invites public comments about our intention to request the Office of Management and Budget (OMB) approval to renew an information collection. The 
                        <E T="04">Federal Register</E>
                         Notice with a 60-day comment period soliciting comments on the following collection of information was published on August 24, 2011, vol. 76, no. 164, page 53025. The Airport Safety Data Program involves the collection and dissemination of civil aeronautics information.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be submitted by November 25, 2011.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kathy DePaepe at (405) 954-9362, or by e-mail at: 
                        <E T="03">Kathy A. DePaepe @faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">OMB Control Number:</E>
                     2120-0015.
                </P>
                <P>
                    <E T="03">Title:</E>
                     FAA Airport Master Record.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     FAA Forms 5010-1, 5010-2, 5010-3, 5010-5.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Renewal of an information collection.
                </P>
                <P>
                    <E T="03">Background:</E>
                     49 U.S.C. 329(b) empowers and directs the Secretary of Transportation to collect and disseminate information on civil aeronautics. Aeronautical information is required to be collected by the FAA in order to carry out agency missions such as those related to aviation flying safety, flight planning, airport engineering and federal grants analysis, aeronautical chart and flight information publications, and the promotion of air commerce as required by statute.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Approximately 19,800 airport owners/managers and state inspectors.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Information is collected on occasion.
                </P>
                <P>
                    <E T="03">Estimated Average Burden per Response:</E>
                     1 hour.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     8,870 hours.
                </P>
                <FP>
                    <E T="02">ADDRESSES:</E>
                     Interested persons are invited to submit written comments on the proposed information collection to the Office of Information and Regulatory Affairs, Office of Management and Budget. Comments should be addressed to the attention of the Desk Officer, Department of Transportation/FAA, and sent via electronic mail to 
                    <E T="03">oira_submission@omb.eop.gov,</E>
                     or faxed to (202) 395-6974, or mailed to the Office of Information and Regulatory Affairs, Office of Management and Budget, Docket Library, Room 10102, 725 17th Street, NW., Washington, DC 20503.
                </FP>
                <P>
                    <E T="03">Public Comments Invited:</E>
                     You are asked to comment on any aspect of this information collection, including (a) Whether the proposed collection of information is necessary for FAA's performance; (b) the accuracy of the estimated burden; (c) ways for FAA to enhance the quality, utility and clarity 
                    <PRTPAGE P="66349"/>
                    of the information collection; and (d) ways that the burden could be minimized 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>
                <SIG>
                    <DATED>Issued in Washington, DC, on October 20, 2011.</DATED>
                    <NAME>Albert R. Spence,</NAME>
                    <TITLE>FAA Assistant Information Collection Clearance Officer, IT Enterprises Business Services Division, AES-200.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27709 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Agency Information Collection Activities; Requests for Comments: Clearance of Renewed Approval of Information Collection; Training and Qualification Requirements for Check Airmen and Flight Instructors</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, FAA invites public comments about our intention to request the Office of Management and Budget (OMB) approval to renew an information collection. The rule allows some experienced pilots who would otherwise qualify as flight instructors or check airmen, but who are not medically eligible to hold the requisite medical certificate, to perform flight instructor or check airmen functions in a simulator.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be submitted by December 27, 2011.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kathy DePaepe at (405) 954-9362, or by e-mail at: 
                        <E T="03">KathyA.DePaepe@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">OMB Control Number:</E>
                     2120-0600.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Training and Qualification Requirements for Check Airmen and Flight Instructors
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     There are no FAA forms associated with this collection.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Renewal of an information collection.
                </P>
                <P>
                    <E T="03">Background:</E>
                     Federal Aviation Regulations (FAR) Parts 121.411(d), 121.412(d), 135.337(d), and 135.338(d) require the collection of this data. This collection is necessary to insure that instructors and check airmen have completed necessary training and checking required to perform instructor and check airmen functions.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Approximately 3,000 check airmen and flight instructors.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Information is collected on occasion.
                </P>
                <P>
                    <E T="03">Estimated Average Burden per Response:</E>
                     15 seconds.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     13 hours.
                </P>
                <FP>
                    <E T="02">ADDRESSES:</E>
                     Send comments to the FAA at the following address: Ms. Kathy DePaepe, Room 126B, Federal Aviation Administration, AES-200, 6500 S. MacArthur Blvd, Oklahoma City, OK 73169.
                </FP>
                <P>
                    <E T="03">Public Comments Invited:</E>
                     You are asked to comment on any aspect of this information collection, including (a) Whether the proposed collection of information is necessary for FAA's performance; (b) the accuracy of the estimated burden; (c) ways for FAA to enhance the quality, utility and clarity of the information collection; and (d) ways that the burden could be minimized 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>
                <SIG>
                    <DATED>Dated: Issued in Washington, DC on October 20, 2011.</DATED>
                    <NAME>Albert R. Spence,</NAME>
                    <TITLE>FAA Assistant Information Collection Clearance Officer, IT Enterprises Business Services Division, AES-200.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27632 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Agency Information Collection Activities; Requests for Comments: Clearance of Renewed Approval of Information Collection; Financial Responsibility for Licensed Launch Activities</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with the Paperwork Reduction Act of 1995, FAA invites public comments about our intention to request the Office of Management and Budget (OMB) approval to renew an information collection. The 
                        <E T="04">Federal Register</E>
                         Notice with a 60-day comment period soliciting comments on the following collection of information was published on August 24, 2011, vol. 76, no. 164, page 53024. Information is used to determine if licensees have complied with financial responsibility requirements (including maximum probable loss determination) as set forth in FAA regulations.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be submitted by November 25, 2011.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kathy DePaepe at (405) 954-9362, or by e-mail at: 
                        <E T="03">Kathy A. DePaepe @faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P SOURCE="NPAR">
                    <E T="03">OMB Control Number:</E>
                     2120-0601.
                </P>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     Financial Responsibility for Licensed Launch Activities.
                </P>
                <P SOURCE="NPAR">
                    <E T="03">Form Numbers:</E>
                     There are no FAA forms associated with this collection.
                </P>
                <P SOURCE="NPAR">
                    <E T="03">Type of Review:</E>
                     Renewal of an information collection.
                </P>
                <P SOURCE="NPAR">
                    <E T="03">Background:</E>
                     This collection is applicable upon concurrence of requests for conducting commercial launch operations as prescribed in 14 CFR, Parts 401, et al., Commercial Space Transportation Licensing Regulation. A commercial space launch services provider must complete the Launch Operators License, Launch-Specific License or Experimental Permit in order to gain authorization for conducting commercial launch operations.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     6 commercial space launch services providers.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Information is collected on occasion.
                </P>
                <P>
                    <E T="03">Estimated Average Burden per Response:</E>
                     100 hours.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     600 hours.
                </P>
                <FP>
                    <E T="02">ADDRESSES:</E>
                     Interested persons are invited to submit written comments on the proposed information collection to the Office of Information and Regulatory Affairs, Office of Management and Budget. Comments should be addressed to the attention of the Desk Officer, Department of Transportation/FAA, and sent via electronic mail to 
                    <E T="03">oira_submission@omb.eop.gov,</E>
                     or faxed to (202) 395-6974, or mailed to the Office of Information and Regulatory Affairs, Office of Management and Budget, Docket Library, Room 10102, 725 17th Street, NW., Washington, DC 20503.
                </FP>
                <P>
                    <E T="03">Public Comments Invited:</E>
                     You are asked to comment on any aspect of this information collection, including (a) Whether the proposed collection of information is necessary for FAA's performance; (b) the accuracy of the estimated burden; (c) ways for FAA to enhance the quality, utility and clarity of the information collection; and (d) ways that the burden could be minimized 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>
                <SIG>
                    <PRTPAGE P="66350"/>
                    <DATED>Issued in Washington, DC, on October 20, 2011.</DATED>
                    <NAME>Albert R. Spence,</NAME>
                    <TITLE>FAA Assistant Information Collection Clearance Officer, IT Enterprises Business Services Division, AES-200.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27711 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Eighteenth Meeting: RTCA Special Committee 205/EUROCAE WG-71: Software Considerations in Aeronautical Systems</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), U.S. Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of RTCA Special Committee 205/EUROCAE WG-71 meeting: Software Considerations in Aeronautical Systems.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA is issuing this notice to advise the public of a meeting of RTCA Special Committee 205/EUROCAE WG-71: Software Considerations in Aeronautical Systems Agenda for the 18th meeting.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be held November 15-18, 2011, from 8:30 a.m. to 5 p.m.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meeting will be held at Embry-Riddle Aeronautical University Instructional Center Auditorium, Clyde Morris Boulevard, Daytona Beach, FL 32218.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        The RTCA Secretariat, 1150 18th Street, NW., Suite 910, Washington, DC 20036, or by telephone at (202) 833-9339, fax at (202) 833-9434, or Web site at 
                        <E T="03">http://www.rtca.org.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Pursuant to section 10(a)(2) of the Federal Advisory Committee Act (Pub. L. 92-463, 5 U.S.C., App.), notice is hereby given for a Special Committee 205/EUROCAE WG-71, Software Considerations in Aeronautical Systems. The agenda will include the following:</P>
                <HD SOURCE="HD1">Agenda</HD>
                <HD SOURCE="HD2">November 15, 2011</HD>
                <P>• Open Plenary Session</P>
                <P>• Chairman's Introductory Remarks</P>
                <P>• Facilities Review</P>
                <P>• Recognition of the FAA and EASA Representatives</P>
                <P>• Review of Meeting Agenda</P>
                <P>• Review and Approval of Seventeenth Meeting Minutes</P>
                <P>• Road Map to Completion</P>
                <P>• Embry-Riddle Aeronautical University (Host Presentation)</P>
                <P>• Presentation of FRAC/OC Changes and Approval</P>
                <P>• IP60/IP61-12B/DO-178B (Object Oriented and RT), Post FRAC Changes</P>
                <P>• IP58/IP59 (Model Based): Post FRAC Changes</P>
                <P>• Lunch</P>
                <P>• Presentation of FRAC/OC Changes and Approval</P>
                <P>• IP58/IP59 (Model Based): Post FRAC Changes</P>
                <P>• P52/IP53 (Clarifications): Post FRAC Changes</P>
                <P>• Break-out Sessions</P>
                <P>• IP52—Clarifications</P>
                <P>• IP60—Object Oriented</P>
                <P>• IP58—Model Based</P>
                <P>• Others as Required</P>
                <HD SOURCE="HD2">November 16, 2011</HD>
                <P>• Break-out Sessions</P>
                <P>• IP52—Clarifications</P>
                <P>• IP60—Object Oriented</P>
                <P>• IP58—Model Based</P>
                <P>• Others as required</P>
                <P>• Presentation of any Further Corrections and Approval</P>
                <P>• IP52, 58 or 60</P>
                <P>• Lunch</P>
                <P>• Presentation of any Further Corrections and Approval</P>
                <P>• IP52, 58 or 60</P>
                <P>• Break-out Sessions</P>
                <P>• IP52—Clarifications</P>
                <P>• IP60—Object Oriented</P>
                <P>• IP58—Model Based</P>
                <P>• Others as required</P>
                <HD SOURCE="HD2">November 17, 2011</HD>
                <P>• Break-out Sessions (as required to work comments)</P>
                <P>• IP58\8—Model based Design</P>
                <P>• IP60—Object Oriented</P>
                <P>
                    • IP52/IP53—FAQs 
                    <E T="03">et al.</E>
                </P>
                <P>• Presentations of any further Corrections and Approval</P>
                <P>• IP52—Model based Design</P>
                <P>• IP58—Object Oriented</P>
                <P>
                    • IP60—FAQs 
                    <E T="03">et al.</E>
                </P>
                <P>• Lunch</P>
                <P>• Presentations of any further Corrections and Approval</P>
                <P>• IP52—Model based Design</P>
                <P>• IP58—Object Oriented</P>
                <P>
                    • IP60—FAQs 
                    <E T="03">et al.</E>
                </P>
                <P>• Break-out Sessions</P>
                <P>• IP52—Clarifications</P>
                <P>• IP58—Object Oriented</P>
                <P>• IP60—Model Based</P>
                <P>• Others as Required</P>
                <HD SOURCE="HD2">November 18, 2011</HD>
                <P>• Presentations of any further Corrections and Approval</P>
                <P>• IP52, 58 or 60</P>
                <P>• Summary of results of Voting Sessions</P>
                <P>• Closing Remarks</P>
                <P>• Adjourn</P>
                <P>
                    Attendance is open to the interested public but limited to space availability. With the approval of the chairman, members of the public may present oral statements at the meeting. Persons wishing to present statements or obtain information should contact the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section. Members of the public may present a written statement to the committee at any time.
                </P>
                <SIG>
                    <DATED>Issued in Washington, DC, on October 20, 2011.</DATED>
                    <NAME>Robert L. Bostiga,</NAME>
                    <TITLE>Manager, RTCA Advisory Committee.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27708 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Eighth Meeting: RTCA Special Committee 222 Inmarsat Aeronautical Mobile Satellite (Route) Services</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), U.S. Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of RTCA Special Committee 222, Inmarsat Aeronautical Mobile Satellite (Route) Services meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA is issuing this notice to advise the public of a meeting of RTCA Special Committee 222, Inmarsat Aeronautical Mobile Satellite (Route) Services for the Eighth Meeting.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be held November 17, 2011, from 1-5 p.m.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meeting will be held at Inmarsat, 1101 Connecticut Avenue, NW., Suite 1200, Washington, DC 20036.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        The RTCA Secretariat, 1150 18th Street, NW., Suite 910, Washington, DC 20036, or by telephone at (202) 833-9339, fax at (202) 833-9434, or Web site at 
                        <E T="03">http://www.rtca.org.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Pursuant to section 10(a) (2) of the Federal Advisory Committee Act (Pub. L. 92-463, 5 U.S.C., App.), notice is hereby given for a Special Committee 222, Inmarsat Aeronautical Mobile Satellite (Route) Services. The agenda will include the following:</P>
                <HD SOURCE="HD1">Agenda</HD>
                <HD SOURCE="HD2">November 17, 2011</HD>
                <P>• Co-Chair Welcomes &amp; Introductions</P>
                <P>• Review of Minutes of previous meeting</P>
                <P>• Review of topics for current agenda</P>
                <P>
                    • Review of current industry status
                    <PRTPAGE P="66351"/>
                </P>
                <P>• Review of status from briefing to PMC in March 2011.</P>
                <P>• Discuss of PMC request to prepare generic GOLD-based document.</P>
                <P>• Discuss update to terms of reference to be submitted to PMC</P>
                <P>• Review of suggested modifications to MOPS (DO-210 and DO-262 SBB technique-specific) testing and qualification.</P>
                <P>• Review of any new MASPS material.</P>
                <P>• Review of any working papers</P>
                <P>• Discussion of work plan</P>
                <P>• Discussion of next meeting</P>
                <P>• Adjourn</P>
                <P>
                    Attendance is open to the interested public but limited to space availability. With the approval of the chairman, members of the public may present oral statements at the meeting. Persons wishing to present statements or obtain information should contact the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section. Members of the public may present a written statement to the committee at any time.
                </P>
                <SIG>
                    <DATED>Issued in Washington, DC, on October 21, 2011.</DATED>
                    <NAME>Robert L. Bostiga,</NAME>
                    <TITLE>Manager, RTCA Advisory Committee.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27707 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <DEPDOC>[Summary Notice No. PE-2011-47]</DEPDOC>
                <SUBJECT>Petition for Exemption; Summary of Petition Received</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of petition for exemption received.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice contains a summary of a petition seeking relief from specified requirements of 14 CFR. The purpose of this notice is to improve the public's awareness of, and participation in, this aspect of FAA's regulatory activities. Neither publication of this notice nor the inclusion or omission of information in the summary is intended to affect the legal status of the petitions or their final disposition.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on these petitions must identify the petition docket number involved and must be received on or before November 15, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments identified by Docket Number FAA-2011-1084 using any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Government-wide rulemaking Web site:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov</E>
                         and follow the instructions for sending your comments electronically.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Send comments to the Docket Management Facility; U.S. Department of Transportation, 1200 New Jersey Avenue, SE., West Building Ground Floor, Room W12-140, Washington, DC 20590.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         Fax comments to the Docket Management Facility at 202-493-2251.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         Bring comments to the Docket Management Facility in Room W12-140 of the West Building Ground Floor at 1200 New Jersey Avenue, SE., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        <E T="03">Privacy:</E>
                         We will post all comments we receive, without change, to 
                        <E T="03">http://www.regulations.gov,</E>
                         including any personal information you provide. Using the search function of our docket Web site, anyone can find and read the comments received into any of our dockets, including the name of the individual sending the comment (or signing the comment 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-78).
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         To read background documents or comments received, go to 
                        <E T="03">http://www.regulations.gov</E>
                         at any time or to the Docket Management Facility in Room W12-140 of the West Building Ground Floor at 1200 New Jersey Avenue, SE., Washington, DC, 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>Tyneka L. Thomas, 202-267-7626, or Ralen Gao, 202-267-3168, Office of Rulemaking, Federal Aviation Administration, 800 Independence Avenue, SW., Washington, DC 20591.</P>
                    <P>This notice is published pursuant to 14 CFR 11.85.</P>
                    <SIG>
                        <DATED>Issued in Washington, DC, on October 21, 2011.</DATED>
                        <NAME>Dennis R. Pratte,</NAME>
                        <TITLE>Acting Director, Office of Rulemaking.</TITLE>
                    </SIG>
                    <HD SOURCE="HD1">Petition for Exemption</HD>
                    <P>
                        <E T="03">Docket No.:</E>
                         FAA-2011-1084.
                    </P>
                    <P>
                        <E T="03">Petitioner:</E>
                         Era Helicopters, LLC.
                    </P>
                    <P>
                        <E T="03">Section of 14 CFR Affected:</E>
                         Special Federal Aviation Regulations 77.
                    </P>
                    <P>
                        <E T="03">Description of Relief Sought:</E>
                    </P>
                    <P>Era Helicopters, LLC (Era) requests an exemption from Special Federal Aviation Regulations 77 which would allow Era to operate helicopters as a contract carrier primarily for oil companies and other potential clients to transport passengers and provide medevac services.</P>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27735 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <DEPDOC>[Summary Notice No. PE-2011-48]</DEPDOC>
                <SUBJECT>Petition for Exemption; Summary of Petition Received</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of petition for exemption received.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice contains a summary of a petition seeking relief from specified requirements of 14 CFR. The purpose of this notice is to improve the public's awareness of, and participation in, this aspect of FAA's regulatory activities. Neither publication of this notice nor the inclusion or omission of information in the summary is intended to affect the legal status of the petition or its final disposition.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on this petition must identify the petition docket number involved and must be received on or before November 15, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments identified by Docket Number FAA-2011-1129 using any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Government-wide rulemaking Web site:</E>
                         Go to 
                        <E T="03">http://www.regulations.gov</E>
                         and follow the instructions for sending your comments electronically.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Send comments to the Docket Management Facility; U.S. Department of Transportation, 1200 New Jersey Avenue, SE., West Building Ground Floor, Room W12-140, Washington, DC 20590.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         Fax comments to the Docket Management Facility at 202-493-2251.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         Bring comments to the Docket Management Facility in Room W12-140 of the West Building Ground Floor at 1200 New Jersey Avenue, SE., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        <E T="03">Privacy:</E>
                         We will post all comments we receive, without change, to 
                        <E T="03">http://www.regulations.gov,</E>
                         including any personal information you provide. Using the search function of our docket Web site, anyone can find and read the comments received into any of our dockets, including the name of the individual sending the comment (or signing the comment for an association, business, labor union, 
                        <E T="03">etc.</E>
                        ). You may review DOT's complete Privacy Act 
                        <PRTPAGE P="66352"/>
                        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>
                         To read background documents or comments received, go to 
                        <E T="03">http://www.regulations.gov</E>
                         at any time or to the Docket Management Facility in Room W12-140 of the West Building Ground Floor at 1200 New Jersey Avenue, SE., Washington, DC, 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>Keira Jones (202) 267-4024, Tyneka Thomas (202) 267-7626, or David Staples (202) 267-4058, Office of Rulemaking, Federal Aviation Administration, 800 Independence Avenue, SW., Washington, DC 20591.</P>
                    <P>This notice is published pursuant to 14 CFR 11.85.</P>
                    <SIG>
                        <DATED>Issued in Washington, DC, on October 21, 2011.</DATED>
                        <NAME>Dennis R. Pratte,</NAME>
                        <TITLE>Acting Director, Office of Rulemaking.</TITLE>
                    </SIG>
                    <HD SOURCE="HD1">Petition for Exemption</HD>
                    <P>
                        <E T="03">Docket No.:</E>
                         FAA-2011-1129.
                    </P>
                    <P>
                        <E T="03">Petitioner:</E>
                         American Airlines.
                    </P>
                    <P>
                        <E T="03">Section of 14 CFR Affected:</E>
                         14 CFR 60.17(d).
                    </P>
                    <P>
                        <E T="03">Description of Relief Sought:</E>
                         Petitioner requests relief to allow their B757 FSTD to be qualified to Level D and for the FSTD to remain under its initial Qualification Test Guide (QTG) criteria described by Advisory Circular (AC) 120-40B.
                    </P>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27738 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <SUBJECT>Notice of Request To Release Airport Property</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA) DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Intent to Rule on Request to Release Airport Property at the Halifax County Airport (RZZ), Roanoke Rapids, North Carolina.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA proposes to rule and invites public comment on the release of land at the Halifax County Airport (RZZ), Roanoke Rapids, NC under the provisions of 49 U.S.C. 47107(h).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before November 25, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments on this application may be mailed or delivered to the FAA at the following address: Larry F. Clark, Assistant Manager, Federal Aviation Administration, Atlanta Airports District Office, 1701 Columbia Ave., Campus Building, Suite 2-260, College Park, GA 30337.</P>
                    <P>In addition, one copy of any comments submitted to the FAA must be mailed or delivered to: Tony N. Brown, Halifax County Manager, 10 North King Street, Halifax, NC 27839.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Larry F. Clark, Assistant Manager, Federal Aviation Administration, Atlanta Airports District Office,  1701 Columbia Avenue, Campus Building, Suite 2-260, College Park, GA 30337.</P>
                    <P>The request to release property may be reviewed, by appointment, in person at this same location.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The FAA invites public comment on the request to release approximately 292 acres of property known as the Halifax County Airport (RZZ) under the provisions of 49 U.S.C. 47107(h)(2). In May, 2009, the Halifax-Northampton Regional Airport Authority opened the new Halifax-Northampton Regional Airport (IXA) as a replacement for the Halifax County Airport (RZZ). On April 20, 2010, the Chairman of the Board of Commissioners of Halifax County and the Mayor of Roanoke Rapids notified the FAA that because of the opening of the new Halifax-Northampton Regional Airport and the subsequent decommissioning of RZZ that they were officially requesting a full release of the affected property from federal obligations. All operations at RZZ have ceased. The FAA has determined that the request to release property at RZZ submitted by the airport sponsors meets the procedural requirements of the FAA. The release of this property does not and will not impact future aviation needs in the region. The FAA may approve the request in whole no sooner than 30 days after publication of this notice.</P>
                <HD SOURCE="HD1">The Following Is a Brief Overview of the Request</HD>
                <P>The Airport Sponsors are proposing the release of the entire airport property and associated facilities. The release of land is necessary to comply with FAA Grant Assurances that do not allow federally acquired airport property to be used for non-aviation purposes. The permanent abandonment of the subject property will result in the lands of RZZ being changed from aeronautical to nonaeronautical use and release of the lands from the conditions of the AIP Grant Agreement Grant Assurances. In accordance with 49 U.S.C. 47107(c)(2)(B)(i) and (iii), the Airport Sponsor has reinvested an amount equal to the fair market value of RZZ in the recently-constructed IXA.</P>
                <P>
                    Any person may inspect, by appointment, the request in person at the FAA office listed above under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    .
                </P>
                <P>In addition, any person may, upon appointment and request, inspect the application, notice and other documents determined by the FAA to be related to the application in person at the Halifax County Manager's Office, 10 North King Street, Halifax, NC.</P>
                <SIG>
                    <DATED>Issued in College Park, Georgia on October 12, 2011.</DATED>
                    <NAME>Scott L. Seritt,</NAME>
                    <TITLE>Manager, FAA Atlanta Airports District Office.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27634 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-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, DOT.</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 June 24, 2011 [76 FR 37189].
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before November 25, 2011.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>National Highway Traffic Safety Administration, Office of Defects Investigation, 202-493-0210. 1200 New Jersey Avenue, SE., W48-221, Washington, DC 20590.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">National Highway Traffic Safety Administration</HD>
                <P>
                    (1) 
                    <E T="03">Title:</E>
                     Replaceable Light Source Dimensional Information Collection, 49 CFR part 564.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     2127-0563.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Business or other for profit organizations.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The information to be collected is in response to 49 CFR part 564, “Replaceable Light Source 
                    <PRTPAGE P="66353"/>
                    Dimensional Information.” Persons desiring to use newly designed replaceable headlamp light sources are required to submit interchangeability and performance specifications to the agency. After a short agency review to assure completeness, the information is placed in a public docket for use by any person who would desire to manufacture headlamp light sources for highway motor vehicles. In Federal Motor Vehicle Safety Standard No. 108, Lamps, reflective devices and associated equipment,” part 564 submission are referenced as being the source of information regarding the performance and interchangeability information for legal headlamp light sources, whether original equipment or replacement equipment. Thus, the submitted information about headlamp light sources becomes the basis for certification of compliance with safety standards.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     28.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     7.
                </P>
                <P>
                    (2) 
                    <E T="03">Title:</E>
                     Compliance Labeling of Retroreflective Materials heavy Trailer Conspicuity.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     2127-0569.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Business or other for profit organizations.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Federal Motor Vehicle Safety Standard No. 108, “Lamps Reflective Devices, and Associated Equipment,” specifies requirements for vehicle lighting for the purposes of reducing traffic accidents and their tragic results by providing adequate roadway illumination, improved vehicle conspicuity, appropriate information transmission through signal lamps, in both day, night, and other conditions of reduced visibility. For certifications and identification purposes, the Standard requires the permanent marking of the letters “DOT-C2,” “DOT-C3”, or “DOT -C4” at least 3mm high at regular intervals on retroreflective sheeting material having adequate performance to provide effective trailer conspicuity.
                </P>
                <P>The manufacturers of new tractors and trailers are required to certify that their products are equipped with retroreflective material complying with the requirements of the standard. The Federal Motor Carrier Safety Administration (FMCSA) enforces this and other standards through roadside inspections of trucks. There is no practical field test for the performance requirements, and labeling is the only objectives way of distinguishing trailer conspicuity grade material from lower performance material. Without labeling, FMCSA will not be able to enforce the performance requirements of the standard and the compliance testing of new tractors and trailers will be complicated. Labeling is also important to small trailer manufactures because it may help them to certify compliance. Because wider stripes or material of lower brightness also can provide the minimum safety performance, the marking system serves the additional role of identifying the minimum stripe width required for retroreflective brightness of the particular material. Since the differences between the brightness grades of suitable retroreflective conspicuity material is not obvious from inspection, the marking system is necessary for tractor and trailer manufacturers and repair shops to assure compliance and for FMCSA to inspect tractors and trailers in use.    Permanent labeling is used to identify retroreflective material having the minimum properties required for effective conspicuity of trailers at night. The information enables the FMCSA to make compliance inspections, and it aids tractor and trailer owners and repairs shops in choosing the correct repair materials for damaged tractors and trailers. It also aids smaller trailer manufacturers in certifying compliance of their products.</P>
                <P>The FMCSA will not be able to determine whether trailers are properly equipped during roadside inspections without labeling. The use of cheaper and more common reflective materials, which are ineffective for the application, would be expected in repairs without the labeling requirement.</P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     1.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     3.
                </P>
                <SUPLHD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>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.</P>
                    <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 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>
                    <P>A Comment to OMB is most effective if OMB receives it within 30 days of publication.</P>
                </SUPLHD>
                <SIG>
                    <DATED>Issued in Washington, DC, on October 20, 2011.</DATED>
                    <NAME>Nathaniel Beuse,</NAME>
                    <TITLE>Director, Office of Crash Avoidance Standards.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27656 Filed 10-25-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-2010-0047; Notice 2]</DEPDOC>
                <SUBJECT>Tireco, Inc., Grant of Petition for Decision of Inconsequential Noncompliance</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Highway Traffic Safety Administration, DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Grant of Petition for Decision of Inconsequential Noncompliance.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Tireco, Inc., (Tireco), has determined that approximately 6,170 of its “GEO-Trac” brand P235/75R15 passenger car tires, manufactured between June 12, 2009 and August 20, 2009 by the fabricating manufacturer, the Shandong Linglong Tyre Co., Ltd., and imported into the United States by Tireco, do not comply with paragraph S5.5(c) of Federal Motor Vehicle Safety Standard (FMVSS) No. 139, 
                        <E T="03">New pneumatic radial tires for light vehicles.</E>
                         Tireco has filed an appropriate report pursuant to 49 CFR part 573, 
                        <E T="03">Defect and Noncompliance Responsibility and Reports</E>
                         (dated August 31, 2009).
                    </P>
                    <P>Pursuant to 49 U.S.C. 30118(d) and 30120(h) and the rule implementing those provisions at 49 CFR part 556, Tireco 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>
                        Notice of receipt of Tireco's petition was published, with a 30-day public comment period, on April 21, 2010, in the 
                        <E T="04">Federal Register</E>
                         (75 FR 20879). No comments were received. To view the petition and all supporting documents log onto the Federal Docket Management System Web site at: 
                        <E T="03">http://www.regulations.gov/.</E>
                         Then follow the online search instructions to locate docket number “NHTSA-2010-0047.”
                    </P>
                    <P>For further information on this decision, contact Mr. George Gillespie, Office of Vehicle Safety Compliance, the National Highway Traffic Safety Administration (NHTSA), telephone (202) 366-5299, facsimile (202) 366-7002.</P>
                    <P>
                        Affected are approximately 6,170 tires imported into the United States by 
                        <PRTPAGE P="66354"/>
                        Tireco who identified the tires as “Geo-Trac” brand P235/75R15 passenger car tires. In consultation with the fabricating manufacturer, the Shandong Linglong Tyre Co., Ltd., Tireco has determined that all of the noncompliant tires were manufactured between June 12, 2009 (Serial Week 24) and August 20, 2009 (Serial Week 34). A total of 6,170 these noncompliant tires have been recovered from its distributors and dealers and are currently in Tireco's possession for relabeling. The remaining tires (approximately 3,370) are still in the hands of Tireco's customers.
                    </P>
                    <P>Tireco explains that the noncompliance is that the markings on the non-compliant tires specifying the maximum inflation pressure in kPa and in psi are reversed from the order required by paragraph S5.5.5(c). The Company said that the maximum inflation pressure should have been marked as “300 kPa (44 psi)” but were “inadvertently” marked on both sidewalls with a maximum inflation pressure of “44 kPa (300 psi).” Tireco reported that this noncompliance was brought to their attention on August 19, 2009 by one of the company's distributor customers.</P>
                    <P>Tireco argues that no vehicle operator would ever inflate the tires to the incorrect pressures that appear on the sidewalls of the subject tires, and specifically stated that “it would be virtually impossible to do so.” Tireco supports this conclusion with the following statements:</P>
                    <EXTRACT>
                        <P>• With respect to the erroneous psi marking, no commercially available air compressor used in tire retail stores, at gas stations, or for home use has the capacity to inflate tires to 300 psi, and consumers would immediately be aware from their past experience that a pressure of 300 psi could not be correct.</P>
                        <P>• With respect to the erroneous kPa marking, it [is] extremely unlikely that a consumer would attempt to inflate the tires to 44 kPa, since (1) Drivers in the United States almost always utilize the psi parameter rather than kPa value when they inflate their tires; and (2) any driver who used the kPa parameter would know that the 44 kPa value was not correct, since all passenger car tires have a maximum inflation pressure of at least 240 kPa. Moreover, even if a consumer were to attempt to inflate the tires to 44 kPa (which is equivalent to approximately 7 psi), he or she would immediately be aware that the tires were drastically underinflated, and would not be in a drivable state.</P>
                    </EXTRACT>
                    <P>
                        Tireco concludes that the subject non-compliance “cannot result in the tires being overloaded, or any other adverse safety consequence to the tires or to the vehicles on which they are mounted.” Additionally, Tireco cites three cases which it believes support its conclusion that NHTSA has previously granted tire companies inconsequentiality exemptions relating to errors in the marking of maximum inflation pressure. (See 
                        <E T="03">Michelin North America, Inc.,</E>
                         70 FR 10161 (March 2, 2005); 
                        <E T="03">Kumho Tire Co., Inc.,</E>
                         71 FR 6129 (February 6, 2006); and 
                        <E T="03">Michelin North America, Inc.,</E>
                         74 FR 10805 (March 12, 2009).
                    </P>
                    <P>Furthermore, Tireco points out three other substantive factors that support its petition:</P>
                    <EXTRACT>
                        <P>• The subject tires meet or exceed all of the substantive performance requirements of FMVSS No. 139.</P>
                        <P>• There have been no complaints regarding this issue from vehicle owners (the incorrect markings were brought to Tireco's attention by one of its distributors).</P>
                        <P>• The manufacturer of these tires, Shandong Linglong Tyre Co., Ltd., has corrected the molds at its factory, so that this noncompliance will not be repeated in current or future production.</P>
                    </EXTRACT>
                    <P>Supported by all of the above stated reasons, Tireco believes that the described noncompliance of its tires to meet the requirements of FMVSS No. 139 is inconsequential to motor vehicle safety, and that its petition, to exempt it 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>
                        <E T="03">NHTSA Decision:</E>
                         The agency agrees with Tireco that the noncompliance is inconsequential to motor vehicle safety. The agency believes that the true measure of inconsequentiality to motor vehicle safety in this case is that there is no effect of the noncompliances on the operational safety of vehicles on which these tires are mounted. In the agency's judgment, the incorrect labeling of the tire inflation information will not have any consequential effect on motor vehicle safety because it is extremely unlikely that the consumer will inflate the tires to an incorrect pressure.
                    </P>
                    <P>The safety of people working in the tire retread, repair, and recycling industries was also to be considered. As with consumers, it is extremely unlikely that this noncompliance will cause anyone working in those businesses to incorrectly inflate these tires in a manner that will cause a measureable effect on motor vehicle safety.</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, this decision only applies to the 3,370 
                        <SU>1</SU>
                        <FTREF/>
                         passenger car replacement tires that Tireco no longer controlled at the time that it determined that a noncompliance existed.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             Tireco's petition, which was filed under 49 CFR part 556, requests an agency decision to exempt Tireco as a manufacturer from the notification and recall responsibilities of 49 CFR part 573 for 3, 370 of the affected tires. However, a decision on this petition cannot relieve distributors and dealers of the prohibitions on the sale, offer for sale, or introduction or delivery for introduction into interstate commerce of the noncompliant tires under their control after Tireco notified them that the subject noncompliance existed.
                        </P>
                    </FTNT>
                    <P>In consideration of the foregoing, NHTSA has decided that Tireco has met its burden of persuasion that the subject FMVSS No. 139 labeling noncompliances are inconsequential to motor vehicle safety. Accordingly, Tireco's petition is granted and the petitioner is exempted from the obligation of providing notification of, and a remedy for, the subject noncompliance under 49 U.S.C. 30118 and 30120.</P>
                </SUM>
                <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: October 20, 2011.</DATED>
                    <NAME>Claude H. Harris,</NAME>
                    <TITLE>Acting Associate Administrator for Enforcement.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27651 Filed 10-25-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 35544]</DEPDOC>
                <SUBJECT>DesertXpress Enterprises, LLC and DesertXpress HSR Corporation—Construction and Operation Exemption—in Victorville, CA and Las Vegas, NV</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Surface Transportation Board, DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of construction and operation exemption.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Board grants an exemption under 49 U.S.C. 10502 from the prior approval requirements of 49 U.S.C. 10901 for DesertXpress Enterprises, LLC and its subsidiary (DXE) to build and operate a 190-mile rail line between Victorville, Cal. and Las Vegas, Nev., in order to provide high-speed passenger rail service. This exemption is subject to environmental mitigation conditions and the condition that DXE build the route designated as environmentally preferable.</P>
                </SUM>
                <DATES>
                    <PRTPAGE P="66355"/>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The exemption will be effective on November 25, 2011; petitions to reopen must be filed by November 15, 2011.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>An original and 10 copies of all pleadings, referring to Docket No. FD 35544, must be filed with the Surface Transportation Board, 395 E Street, SW., Washington, DC 20423-0001. In addition, one copy of all pleadings must be served on petitioner's representative: Linda J. Morgan, Nossaman LLP, 1666 K Street, NW., Suite 500, Washington, DC 20006.</P>
                    <P>Copies of filings will be available for viewing at the Board's Web site.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Joseph H. Dettmar at 202-245-0395. Assistance for the hearing impaired is available through the Federal Information Relay Service (FIRS) at 1-800-877-8339.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Additional information is contained in the Board's decision, which is available on our Web site at: “
                    <E T="03">http://www.stb.dot.gov</E>
                    ”.
                </P>
                <SIG>
                    <DATED>Decided: October 20, 2011.</DATED>
                    <P>By the Board, Chairman Elliott, Vice Chairman Begeman, and Commissioner Mulvey.</P>
                    <NAME>Jeffrey Herzig,</NAME>
                    <TITLE>Clearance Clerk.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27679 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4915-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <DATE>October 20, 2011.</DATE>
                <P>The Department of the Treasury will submit the following public information collection requirements to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13 on or after the date of publication of this notice. A copy of the submissions may be obtained by calling the Treasury Bureau Clearance Officer listed. Comments regarding these information collections should be addressed to the OMB reviewer listed and to the Treasury PRA Clearance Officer, Department of the Treasury, 1750 Pennsylvania Avenue, NW., Suite 11010, Washington, DC 20220.</P>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before November 25, 2011 to be assured consideration.</P>
                </DATES>
                <HD SOURCE="HD1">Internal Revenue Service (IRS)</HD>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0001.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Employer's Annual Railroad Retirement Tax Return.
                </P>
                <P>
                    <E T="03">Forms:</E>
                     CT-1, CT-1X.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Railroad employers are required to file an annual return to report employer and employee Railroad Retirement Tax Act (RRTA). Form CT-1 is used for this purpose. IRS uses the information to insure that the employer has paid the correct tax.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     39,455.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0003.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Application for Employer Identification Number; Solicitud de Numero de Identificacion Patronal (EIN).
                </P>
                <P>
                    <E T="03">Forms:</E>
                     SS-4, SS-4-PR.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Taxpayers are required to have an identification number for use on any return, statement, or other document must prepare and file Form SS-4 or Form SS-4PR (Puerto Rico only) to obtain a number. The information is used by the IRS and the SSA in tax administration and by the Bureau of the Census for business statistics.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     15,941,913.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0024.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Claim for Refund and Request for Abatement.
                </P>
                <P>
                    <E T="03">Form:</E>
                     843.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     IRC section 6402, 6404, and sections 301.6404-2, and 301.6404-3 of the regulations, allow for refunds of taxes (except income taxes) or refund, abatement, or credit of interest, penalties, and additions to tax in the event of errors or certain action by the IRS. Form 843 is used by taxpayers to claim these refunds, credits, or abatements.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals and Households.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     875,295.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0049.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Form 990-BL, Information and Initial Excise Tax Return for Black Lung Benefit Trusts and Certain Related Persons; Form 6069, Return of Excise Tax on Excess Contributions to BL Trust.
                </P>
                <P>
                    <E T="03">Forms:</E>
                     990-BL, 6069.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     IRS uses Form 990-BL to monitor activities of black lung benefit trusts, and to collect excise taxes on these trusts and certain related persons if they engage in proscribed activities. The tax is figured on Schedule A and attached to Form 990-BL. Form 6069 is used by coal mine operators to figure the maximum deduction to a black lung benefit trust. If excess contributions are made, IRS uses the form to figure and collect the tax on excess contributions.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     563.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0058.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Application for Recognition of Exemption Under Section 521 of the Internal Revenue Code.
                </P>
                <P>
                    <E T="03">Form:</E>
                     1028.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Farmers' cooperatives must file Form 1028 to apply for exemption from Federal income tax as being organizations described in IRC section 521. The information on Form 1028 provides the basis for determining whether the applicants are exempt.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits, Farms.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     2,545.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0152.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Application for Change in Accounting Method.
                </P>
                <P>
                    <E T="03">Form:</E>
                     3115.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Form 3115 is used by taxpayers who wish to change their method of computing their taxable income. The form is used by the IRS to determine if electing taxpayers have met the requirements and are able to change to the method requested.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     929,066.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0216.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     International Boycott Report.
                </P>
                <P>
                    <E T="03">Form:</E>
                     5713 and Schedules A, B, and C to Form 5713.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Form 5713 and related Schedules A, B, and C are used by any entity that has operations in a “boycotting” country. If that entity cooperates with or participates in an international boycott it loses a portion of the foreign tax credit, or deferral of FSC and IC-DISC benefits. The IRS uses Form 5713 to determine if any of the above benefits should be lost. The 
                    <PRTPAGE P="66356"/>
                    information is also used as the basis for a report to the Congress.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     69,495.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0284.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Application for Determination of Employee Stock Ownership Plan.
                </P>
                <P>
                    <E T="03">Form:</E>
                     5309.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Form 5309 is used in conjunction with Form 5300 or Form 5303 when applying for a determination letter as to a deferred compensation plan's qualification status under section 409 or 4975(e)(7) of the Internal Revenue Code. The information is used to determine whether the plan qualifies.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     26,975.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0723.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     T.D. 8043—Manufacturers Excise Taxes and Sporting Goods and Firearms and Other Administrative Provisions of Special Application to Manufacturers and Retailers Excise Taxes.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This document contains final regulations which revise and update the regulations on manufacturers excise taxes on sporting goods and firearms and other administrative provisions especially applicable to manufacturers and retailers excise taxes. These amendments revise and update Part 48 to achieve greater clarity and conform the regulations to numerous amendments to the Internal Revenue Code of 1954 made after 1964. These regulations provide necessary guidance to the public for compliance with the law.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     475,000.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0795.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Exemption From Withholding on Compensation for Independent (and Certain Dependent) Personal Services of a Nonresident Alien Individual.
                </P>
                <P>
                    <E T="03">Form:</E>
                     8233.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Compensation paid to a nonresident alien (NRA) individual for independent personal services (self-employment) is generally subject to 30% withholding or graduated rates. However, compensation may be exempt from withholding because of a U.S. tax treaty or personal exemption amount. Form 8233 is used to request exemption from withholding.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals and Households.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     1,320,000.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0879.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     IA-195-78 (Final) Certain Returned Magazines, Paperbacks or Records.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The regulations provide rules relating to an exclusion from gross income for certain returned merchandise. The regulations provide that in addition to physical return of the merchandise, a written statement listing certain information may constitute evidence of the return. Taxpayers who receive physical evidence of the return may, in lieu of retaining physical evidence, retain documentary evidence of the return. Taxpayers in the trade or business of selling magazines, paperbacks, or records, who elect to use a certain method of accounting, are affected.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     8,125.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0922.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Form 8329, Lender's Information Return for Mortgage Credit Certificates (MCCs); Form 8330, Issuer's Quarterly Information Return for Mortgage Credit Certificates (MCCs).
                </P>
                <P>
                    <E T="03">Forms:</E>
                     8329, 8330.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Form 8329 is used by lending institutions and Form 8330 is used by state and local governments to report on mortgage credit certificates (MCCs) authorized under IRC Section 25. IRS matches the information supplied by lenders and issuers to ensure that the credit is computed properly.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     73,720.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1100.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     REG-209106-89 (NPRM) Changes With Respect to Prizes and Awards and Employee Achievement Awards.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This regulation requires recipients of prizes and awards to maintain records to determine whether a qualifying designation has been made. The affected public are prize and award recipients who seek to exclude the cost of a qualifying prize or award.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals and Households.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     1,275.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1139.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     PS-264-82 (Final) Adjustments to Basis of Stock and Indebtedness to Shareholders of S Corporations and Treatment of Distributions by S Corporations to Shareholders; REG-144859-04—Section 1367 Regard.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The regulations provide the procedures and the statements to be filed by S corporations for making the election provided under section 1368, and by shareholders who choose to reorder items that decrease their basis. Statements required to be filled will be used to verify that taxpayers are complying with the requirements imposed by Congress.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     450.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1269.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     T.D. 8461—Nuclear Decommissioning Fund Qualification Requirements.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This document contains final regulations relating to the qualification requirements of a nuclear decommissioning fund. Pursuant to former section 468A(e)(4)(C) of the Internal Revenue Code, current regulations require that nuclear decommissioning funds invest directly in permissible assets and permitted two or more such funds to combine assets for investment purposes. The Comprehensive National Energy Policy Act of 1992 repealed the investment restriction contained in section 468A(e)(4)(C). These final regulations amend the existing regulations to reflect the statutory change.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     150.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1375.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     T.D. 8537—Carryover of Passive Activity Losses and Credits and At Risk Losses to Bankruptcy Estates of Individuals.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This document contains final regulations relating to the 
                    <PRTPAGE P="66357"/>
                    application of carryover of passive activity losses and credits and at risk losses to the bankruptcy estates of individuals. The final regulations affect individual taxpayers who file bankruptcy petitions under chapter 7 or chapter 11 of title 11 of the United States Code and have passive activity losses and credits under section 469 or losses under section 465.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals and Households.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     100.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1381.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     T.D. 8546—Limitations on Corporate Net Operating Loss.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This document contains final income tax regulations providing rules for allocating net operating loss or taxable income, and net capital loss or gain, within the taxable year in which a loss corporation has an ownership change under section 382 of the Internal Revenue Code of 1986. These regulations permit the loss corporation to elect to allocate these amounts between the period ending on the change date and the period beginning on the day after the change date as if its books were closed on the change date.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     200.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1393.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     EE-14-81 (NPRM) Deductions and Reductions in Earnings and Profits (or Accumulated Profits) With Respect to Certain Foreign Deferred Compensation Plans Maintained by Certain Foreign Corporations or by Foreign Branches of Domestic Corporations.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The regulation provides guidance regarding the limitations on deductions and adjustments to earnings and profits (or accumulated profits) for certain foreign deferred compensation plans. Respondents will be multinational corporations.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     200.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1407.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Consent To Extend the Time to Assess the Branch Profits Tax Under Regulations Sections 1.884-2(a) and (c).
                </P>
                <P>
                    <E T="03">Form:</E>
                     8848.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Form 8848 is used by foreign corporations that have (a) completely terminated all of their U.S. trade or business within the meaning of Temporary Regulations section 1.884-2T(a) during the tax year or (b) transferred their U.S. assets to a domestic corporation in a transaction described in Code section 381(a), if the foreign corporation was engaged in a U.S. trade or business at that time.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     22,500.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1409.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Election to Use Different Annualization Periods for Corporate Estimated Tax.
                </P>
                <P>
                    <E T="03">Form:</E>
                     8842.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Form 8842 is used by corporations (including S corporations), tax-exempt organizations subject to the unrelated business income tax, and private foundations to annually elect the use of an annualization period in section 6655(e)(2)(c)(i) or (ii) for purpose of figuring the corporation's estimated tax payments under the annualized income installment method.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     4,335.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1435.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     TD 8706—Electronic Filing of Form W-4.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This document contains final regulations relating to Form W-4, Employee's Withholding Allowance Certificate. The final regulations authorize employers to establish electronic systems for use by employees in filing their Forms W-4. The regulations provide employers and employees with guidance necessary to comply with the law. The regulations affect employers that establish electronic systems and their employees.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     40,000.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1485.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title</E>
                     T.D. 8743—Sale of Residence From Qualified Personal Residence Trust.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This document contains final regulations permitting the reformation of a personal residence trust or a qualified personal residence trust in order to comply with the applicable requirements for such trusts. The final regulations also provide that the governing instruments of such trusts must prohibit the sale of a residence held in the trust to the grantor of the trust, the grantor's spouse, or an entity controlled by the grantor or the grantor's spouse.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals and Households.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     625.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1486.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title</E>
                     T.D. 8697—Simplification of Entity Classification Rules.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This regulation provides rules to allow certain unincorporated business organizations to elect to be treated as corporations or partnerships for federal tax purposes. The election is made by filing Form 8832, Entity Classification Election. The information collected on the election will be used to verify the classification of electing organizations.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     1.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1491.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title</E>
                     T.D. 8746—Amortizable Bond Premium.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This document contains final regulations relating to the federal income tax treatment of bond premium and bond issuance premium. The regulations reflect changes to the law made by the Tax Reform Act of 1986 and the Technical and Miscellaneous Revenue Act of 1988. The regulations will provide needed guidance to holders and issuers of debt instruments.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     7,500.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1493.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title</E>
                     T.D. 8684—Treatment of Gain From the Disposition of Interest in Certain Natural Resource Recapture Property by S Corporations and Their Shareholders.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This document contains final regulations relating to the tax treatment by S Corporations and their shareholders of gain from the disposition by an S corporation (and a corporation that was formerly an S corporation) of certain natural resource recapture property (section 1254 property after enactment of the Tax Reform Act of 1986 and oil, gas, or 
                    <PRTPAGE P="66358"/>
                    geothermal property before enactment of the Tax Reform Act of 1986), and also rules relating to the disposition of stock in an S corporation that holds certain natural resource recapture property. Changes to the applicable tax law were made by the Tax Reform Act of 1986, and the Subchapter S Revision Act of 1982. The regulations provide the public with guidance in complying with the changed tax laws.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     1,000.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1496.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     REG-209673-93 Mark to Market for Dealers in Securities (TD 8700 (final)).
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Under section 1.475(b)-4, the information required to be recorded is required by the IRS to determine whether exemption from mark-to-market treatment is properly claimed, and will be used to make that determination upon audit of taxpayer's books and records. Also, under section 1.475(c)-1(a)(3)(iii), the information is necessary for the Service to determine whether a consolidated group has elected to disregard inter-member transactions in determining a member's status as a dealer in securities.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     2,950.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1581.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     T.D. 8812—Continuation Coverage Requirements Applicable to Group Health Plans.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The Consolidated Omnibus Budget Reconciliation Act of 1985 (COBRA) added health care continuation requirements that apply to group health plans. Coverage required to be provided under those requirements is referred to as COBRA continuation coverage. This document contains final regulations based on these two sets of proposed regulations. The final regulations also reflect statutory amendments to the COBRA continuation coverage requirements since COBRA was enacted. The regulations will generally affect sponsors of and participants in group health plans and they provide plan sponsors and plan administrators with guidance necessary to comply with the law.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     404,640.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1633.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     T.D. 8802—Certain Asset Transfers to a Tax-Exempt Entity.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This document contains final regulations that implement provisions of the Tax Reform Act of 1986 and the Technical and Miscellaneous Revenue Act of 1988. The final regulations generally affect a taxable corporation that transfers all or substantially all of its assets to a tax-exempt entity or converts from a taxable corporation to a tax-exempt entity in a transaction other than a liquidation, and generally require the taxable corporation to recognize gain or loss as if it had sold the assets transferred at fair market value.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Not-for-profit institutions.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     125.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1641.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Rev. Proc. 99-17—Mark to Market Election for Commodities Dealers and Securities and Commodities Traders.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The revenue procedure prescribes the time and manner for dealers in commodities and traders in securities or commodities to elect to use the mark-to-market method of accounting under Sec. 475(e) or (f) of the Internal Revenue Code. The collections of information in sections 5 and 6 of this revenue procedure are required by the IRS in order to facilitate monitoring taxpayers changing accounting methods resulting from making the elections under Sec. 475(e) or (f).
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     500.  
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1643.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     REG-209484-87 (TD 8814 final) Federal Insurance Contributions Act (FICA) Taxation of Amounts Under Employee Benefit Plans.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This regulation provides guidance as to when amounts deferred under or paid from a nonqualified deferred compensation plan are taken into account as wages for purposes of the employment taxes imposed by the Federal Insurance Contributions Act (FICA). Section 31.3121(v)(2)-1(a)(2) requires that the material terms of a plan be set forth in writing.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     12,500.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1646.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     T.D. 8851—Return Requirement for United States Persons who acquire or dispose of an interest in a foreign partnership, or whose proportional interest in a foreign partnership changes.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This document contains final regulations under section 6046A of the Internal Revenue Code relating to the requirement that United States persons, in certain circumstances, file a return if they acquire or dispose of an interest in a foreign partnership, or if their proportional interest in a foreign partnership changes. The burden of complying with the collection of information is reported on Form 8865.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     1.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1649.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Rev. Proc. 99-21—Disability Suspension.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The information is needed to establish a claim that a taxpayer was financially disabled for purposes of section 6511(h) of the Internal Revenue Code (which was added by section 3203 of the Internal Revenue Service Restructuring and Reform Act of 1998). Under section 6511(h), the statute of limitations on claims for credit or refund is suspended for any period of an individual taxpayer's life during which the taxpayer is unable to manage his or her financial affairs because of a medically determinable mental or physical impairment, if the impairment can be expected to result in death, or has lasted (or can be expected to last) for a continuous period of not less than 12 months. Section 6511(h)(2)(A) requires that proof of the taxpayer's financial disability be furnished to the Internal Revenue Service.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals and Households.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     24,100.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1654.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     T.D. 8902—Capital Gains, Partnership and Subchapter S, and Trust Provisions.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This document contains final regulations relating to sales or exchanges of interests in partnerships, S 
                    <PRTPAGE P="66359"/>
                    corporations, and trusts. The regulations interpret the look-through provisions of section 1(h), added by section 311 of the Taxpayer Relief Act of 1997 and amended by sections 5001 and 6005(d) of the Internal Revenue Service Restructuring and Reform Act of 1998, and explain the rules relating to the division of the holding period of a partnership interest. The regulations affect partnerships, partners, S corporations, S corporation shareholders, trusts, and trust beneficiaries.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     1.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1655
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     T.D. 8861—Private Foundation Disclosure Rules.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This document contains final regulations that amend the regulations relating to the public disclosure requirements described in section 6104(d) of the Internal Revenue Code. These final regulations implement changes made by the Tax and Trade Relief Extension Act of 1998, which extended to private foundations the same rules regarding public disclosure of annual information returns that apply to other tax-exempt organizations. These final regulations provide guidance for private foundations required to make copies of applications for recognition of exemption and annual information returns available for public inspection and to comply with requests for copies of those documents.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Not-for-profit institutions.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     32,596.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1658.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     T.D. 8940—Purchase Price Allocations in Deemed Actual Asset Acquisitions.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This document contains final regulations relating to deemed and actual asset acquisitions under sections 338 and 1060. The final regulations affect sellers and buyers of corporate stock that are eligible to elect to treat the transaction as a deemed asset acquisition. The final regulations also affect sellers and buyers of assets that constitute a trade or business.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     25.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1759.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Amended Quarterly Federal Excise Tax Return.
                </P>
                <P>
                    <E T="03">Form:</E>
                     720X.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Form 720X is used to make adjustments to correct errors on form 720 filed for previous quarters. It can be filed by itself or it can be attached to any subsequent Form 720. Code section 6416(d) allows taxpayers to take a credit on a subsequent return rather than filing a refund claim.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     152,460.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1762.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Direct Deposit of Corporate Tax Refund.
                </P>
                <P>
                    <E T="03">Form:</E>
                     8050.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     File Form 8050 to request that the IRS deposit a corporate income tax refund (including a refund of $1 million or more) directly into an account at any U.S. bank or other financial institution (such as a mutual fund or brokerage firm) that accepts direct deposits.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     348,600.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1763.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Direct Deposit of Refund of $1 Million or more.
                </P>
                <P>
                    <E T="03">Form:</E>
                     8302.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This form is used to request a deposit of a tax refund of $1 million or more directly into an account at any U.S. bank or other financial institution.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     1,088.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1765.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     T.D. 9171—New Markets Tax Credit.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The regulations provide guidance for taxpayers claiming the new markets tax credit under section 45D of the Internal Revenue Code. The reporting requirements in the regulations require a qualified community development entity (CDE) to provide written notice to: (1) Any taxpayer who acquires an equity investment in the CDE at its original issue that the equity investment is a qualified equity investment entitling the taxpayer to claim the new markets tax credits; and (2) each holder of a qualified equity investment, including all prior holders of that investment that a recapture event has occurred. CDE's must comply with such reporting requirements to the Secretary as the Secretary may prescribe.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     210.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1767.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     T.D. 8976—Dollar-Value LIFO Regulations; Inventory Price Index Computation Method.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This document contains final regulations under section 472 of the Internal Revenue Code that relate to accounting for inventories under the last-in, first-out (LIFO) method. The final regulations provide guidance regarding methods of valuing dollar-value LIFO pools and affect persons who elect to use the dollar-value LIFO and inventory price index computation (IPIC) methods or who receive dollar-value LIFO inventories in certain nonrecognition transactions.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     1.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1768.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Revenue Procedure 2003-84, Optional Election to Make Monthly Sec. 706 Allocations.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This revenue procedure allows certain partnerships with money market fund partners to make an optional election to close the partnership's books on a monthly basis with respect to the money market fund partners.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     500.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1773.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Revenue Procedure 2002-23, Taxation of Canadian Retirement Plans Under U.S.-Canada Income Tax Treaty.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This Revenue Procedure provides guidance for the application by U.S. citizens and residents of the U.S.-Canada Income Tax Treaty, as amended by the 1995 protocol, in order to defer U.S. Income taxes on income accrued in certain Canadian retirement plans.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals and Households.
                    <PRTPAGE P="66360"/>
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     10,000.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1776.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     U.S. Income Tax Return for Electing Alaska Native Settlement Trusts.
                </P>
                <P>
                    <E T="03">Form:</E>
                     1041-N.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     An Alaska Native Settlement Trust (ANST) may elect under section 646 to have the special income tax treatment of that section apply to the trust and its beneficiaries. This one-time election is made by filing Form 1041-N and the form is used by the ANST to report its income, etc., and to compute and pay any income tax. Form 1041-N is also used for the special information reporting requirements that apply to ANST's.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     680.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1783.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     TD 8989—Guidance Necessary to Facilitate Electronic Tax Administration.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The regulations provide a regulatory statement of IRS authority to prescribe what return information or documentation must be filed with a return, statement or other document required to be made under any provision of the internal revenue laws or regulations. In addition, the regulations eliminate regulatory impediments to electronic filing of Form 1040.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals and Households.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     1.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1792.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     REG-164754-01 (Final) Split-Dollar Life Insurance Arrangements.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The proposed regulations provide guidance for loans made pursuant to a split-dollar life insurance arrangement. To obtain a particular treatment under the regulations for certain split- dollar loans, the parties to the loan must make a written representation, which must be kept as part of their books and records and a copy filed with their federal income tax returns. In addition, if a split-dollar loan provides for contingent payments, the lender must produce a projected payment schedule for the loan and give the borrower a copy of the schedule. This schedule is used by parties to compute their interest accruals and any imputed transfers for tax purposes.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     32,500.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1794.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     T.D. 9088—Compensatory Stock Options Under Section 482.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This document contains final regulations that provide guidance regarding the application of the rules of section 482 governing qualified cost sharing arrangements. These regulations provide guidance regarding the treatment of stock-based compensation for purposes of the rules governing qualified cost sharing arrangements and for purposes of the comparability factors to be considered under the comparable profits method.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     2,000.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1919.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Prior Government Service Information.
                </P>
                <P>
                    <E T="03">Form:</E>
                     12854.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This product is used to identify applicants who have had prior government services in order to request the OPF from federal records and to identify possible pay setting issues.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals and Households.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     6,230.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1920.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Notice Regarding Repayment of a Buyout Prior to Re-employment with the Federal Government.
                </P>
                <P>
                    <E T="03">Form:</E>
                     12311.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This form outlines the regulations requiring those employees being rehired by the government and received a buyout from their previous job to make repayment of the buyout before they will be hired again.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals and Households.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     2,757.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1921.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Continuation Sheet for Item #16 (Additional Information) OF-306, Declaration for Federal Employment.
                </P>
                <P>
                    <E T="03">Form:</E>
                     12114.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Form 12114 is used as a continuation to the OF-306 to provide additional space for capturing additional information.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals and Households.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     6,203.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1924.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Biodiesel Fuels Credit.
                </P>
                <P>
                    <E T="03">Form:</E>
                     12114.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     IRC section 40A provides a credit for biodiesel or qualified biodiesel mixtures. IRC section 38(b)(17) allows a nonrefundable income tax credit for businesses that sell or use biodiesel. Form 8864 is used to figure the credits.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     310.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1926.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Notice 2005-10, Domestic Reinvestment Plans and Other Guidance under Section 965.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This document provides guidance under new section 965 enacted by the American Jobs Creation Act of 2004 (Pub. L.108-357). In general, and subject to limitations and conditions, section 965(a) provides that a corporation that is a U.S. shareholder of a controlled foreign corporation (CFC) may elect, for one taxable year, an 85 percent dividends received deduction (DRD) with respect to certain cash dividends it receives from its CFC's. Section 965(f) provides that taxpayers may elect the application of section 965 for either the taxpayer's last taxable year which begins before October 22, 2004, or the taxpayer's first taxable year to which the taxpayer intends to elect section 965 to apply prior to the issuance of Form 8895, the election must be made on a statement that is attached to its timely-filed tax return (including extensions) for such taxable year. In addition, because the taxpayer must establish to the satisfaction of the Commissioner that it has satisfied the conditions to take the DRD, the taxpayer is required under this guidance to report specified information and provide specified documentation.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     3,750,000.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1927.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     IRS e-file Electronic Funds Withdrawal Authorization for Form 7004.
                    <PRTPAGE P="66361"/>
                </P>
                <P>
                    <E T="03">Form:</E>
                     8878-A.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Form 8878-A is used by a corporate officer or agent and an electronic return originator (ERO) to use a personal identification number (PIN) to authorize an electronic funds withdrawal for a tax payment made with a request to extend the filing due date for a corporate income tax return.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Private Sector: Businesses or other for-profits.
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     505,400.
                </P>
                <P>
                    <E T="03">Bureau Clearance Officer:</E>
                     Yvette Lawrence, Internal Revenue Service, 1111 Constitution Avenue, NW., Washington, DC 20224; (202) 927-4374.
                </P>
                <P>
                    <E T="03">OMB Reviewer:</E>
                     Shagufta Ahmed, Office of Management and Budget, New Executive Office Building, Room 10235, Washington, DC 20503; (202) 395-7873.
                </P>
                <SIG>
                    <NAME>Dawn D. Wolfgang,</NAME>
                    <TITLE>Treasury PRA Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27671 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Fiscal Service</SUBAGY>
                <SUBJECT>Surety Companies Acceptable on Federal Bonds: Western National Mutual Insurance Company</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Financial Management Service, Fiscal Service, Department of the Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is Supplement No. 2 to the Treasury Department Circular 570, 2011 Revision, published July 1, 2011, at 76 FR 38892.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Surety Bond Branch at (202) 874-6850.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    A Certificate of Authority as an acceptable surety on Federal bonds is hereby issued under 31 U.S.C. 9305 to the following company: Western National Mutual Insurance Company (NA1C # 15377). 
                    <E T="03">Business Address:</E>
                     P.O. Box 1463, Minneapolis, MN 55440. 
                    <E T="03">Phone:</E>
                     (952) 835-5350. 
                    <E T="03">Underwriting Limitation b/:</E>
                     $24,552,000. 
                    <E T="03">Surety Licenses Cl:</E>
                     IL, IA, MN, NE, ND, OR, SD, WI. 
                    <E T="03">Incorporated In:</E>
                     Minnesota.
                </P>
                <P>Federal bond-approving officers should annotate their reference copies of the Treasury Circular 570 (“Circular”), 2011 Revision, to reflect this addition.</P>
                <P>Certificates of Authority expire on June 30th each year, unless revoked prior to that date. The Certificates are subject to subsequent annual renewal as long as the companies remain qualified (see 31 CFR part 223). A list of qualified companies is published annually as of July 1st in the Circular, which outlines details as to the underwriting limitations, areas in which companies are licensed to transact surety business, and other information.</P>
                <P>
                    The Circular may be viewed and downloaded through the Internet at 
                    <E T="03">http://www.fms.treas.gov/c570.</E>
                </P>
                <P>Questions concerning this Notice may be directed to the U.S. Department of the Treasury, Financial Management Service, Financial Accounting and Services Division, Surety Bond Branch, 3700 East-West Highway, Room 6F01, Hyattsville, MD 20782.</P>
                <SIG>
                    <DATED> Dated: October 7, 2011.</DATED>
                    <NAME>Laura Carrico,</NAME>
                    <TITLE>Director, Financial Accounting and Services Division.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2011-27539 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-35-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <SUBJECT>Quarterly Publication of Individuals, Who Have Chosen To Expatriate, as Required by Section 6039G</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice is provided in accordance with IRC section 6039G, as amended, by the Health Insurance Portability and Accountability Act (HIPPA) of 1996. This listing contains the name of each individual losing their United States citizenship (within the meaning of section 877(a) or 877A) with respect to whom the Secretary received information during the quarter ending September 30, 2011.</P>
                </SUM>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="xl130,xl130,xl130">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Last name</CHED>
                        <CHED H="1">First name</CHED>
                        <CHED H="1">Middle name/initials</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">ABRAHAM</ENT>
                        <ENT>GABRIELLE</ENT>
                        <ENT>TONY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ADUSUMILLI</ENT>
                        <ENT>PANDURANGA</ENT>
                        <ENT>R</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AGUILAR</ENT>
                        <ENT>MARIA</ENT>
                        <ENT>L</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AHMAD</ENT>
                        <ENT>IBRAHEEM</ENT>
                        <ENT>MUSTAFA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AJAMI</ENT>
                        <ENT>RAMI</ENT>
                        <ENT>MOHAMAD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ALEXIOU</ENT>
                        <ENT>ANDREW</ENT>
                        <ENT>CHRISTOPHER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ALIREZA</ENT>
                        <ENT>MISHAEL</ENT>
                        <ENT>FAHD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ALTOE</ENT>
                        <ENT>SUSANNE</ENT>
                        <ENT>NICOLE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AMITTAI</ENT>
                        <ENT>DEKEL</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">AMRINE</ENT>
                        <ENT>DOUGLAS</ENT>
                        <ENT>SCOTT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ANDREWS</ENT>
                        <ENT>PHILIP</ENT>
                        <ENT>NEWTON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AOKI</ENT>
                        <ENT>HISAE</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">ARP</ENT>
                        <ENT>WILLIAM</ENT>
                        <ENT>FRED</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ARYA</ENT>
                        <ENT>JAI</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">ARYA</ENT>
                        <ENT>ROHINI</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">ASHKENAZY</ENT>
                        <ENT>ALEXANDRA</ENT>
                        <ENT>INGA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ATKINSON</ENT>
                        <ENT>EVON</ENT>
                        <ENT>ST PATRICK CULLITON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">AUERBACH</ENT>
                        <ENT>MELINA</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">AVERY</ENT>
                        <ENT>THOMAS</ENT>
                        <ENT>YUL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BAER</ENT>
                        <ENT>JULIAN</ENT>
                        <ENT>JULIUS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BAGGETT</ENT>
                        <ENT>SUSAN</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">BANKES</ENT>
                        <ENT>FLORA</ENT>
                        <ENT>JUNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BARBALACO</ENT>
                        <ENT>STEPHEN</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">BATES</ENT>
                        <ENT>LIAM</ENT>
                        <ENT>ROBERT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BAXTER</ENT>
                        <ENT>CALEB</ENT>
                        <ENT>CHRISTOPHER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BERG</ENT>
                        <ENT>SHANE</ENT>
                        <ENT>DAVID</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BERNARD</ENT>
                        <ENT>STEVEN</ENT>
                        <ENT>JACQUES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BERTSCHI</ENT>
                        <ENT>HANSPETER</ENT>
                        <ENT>ANDREA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BINER</ENT>
                        <ENT>ALFRED</ENT>
                        <ENT>ALEXANDER P</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BIRDWELL</ENT>
                        <ENT>NATALIE</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="66362"/>
                        <ENT I="01">BLANK</ENT>
                        <ENT>JASON</ENT>
                        <ENT>MARSHALL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BLIN</ENT>
                        <ENT>JEAN</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">BOEY</ENT>
                        <ENT>MARK</ENT>
                        <ENT>FREDERICK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BONNARD BARBIER</ENT>
                        <ENT>CARINE</ENT>
                        <ENT>AYMONE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BORTHEN</ENT>
                        <ENT>JUST CHRISTPHER</ENT>
                        <ENT>WESTCOTT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BOTNAR</ENT>
                        <ENT>RENE</ENT>
                        <ENT>M</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BRIDGES</ENT>
                        <ENT>STEPHEN</ENT>
                        <ENT>JACK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BRONIMANN</ENT>
                        <ENT>ANDREA</ENT>
                        <ENT>JANE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BROWER</ENT>
                        <ENT>LAWRENCE</ENT>
                        <ENT>EDWARD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BRUNNER</ENT>
                        <ENT>STEPHAN</ENT>
                        <ENT>CONRAD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BURKHARDT</ENT>
                        <ENT>ROBERT</ENT>
                        <ENT>RYAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CALCAGNITI</ENT>
                        <ENT>FRANCISCO</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">CARLIN</ENT>
                        <ENT>ALEXIS</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CASPERS</ENT>
                        <ENT>FLORIAN</ENT>
                        <ENT>BENJAMIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHAE</ENT>
                        <ENT>BRANDON</ENT>
                        <ENT>JAE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHAE</ENT>
                        <ENT>JENNIFER</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHAMPETIER</ENT>
                        <ENT>VINCENT</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHAN</ENT>
                        <ENT>VIOLA</ENT>
                        <ENT>K</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHEE</ENT>
                        <ENT>GLENN</ENT>
                        <ENT>WEN HAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHEN</ENT>
                        <ENT>ANDY</ENT>
                        <ENT>PAUL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHEN</ENT>
                        <ENT>EUNICE</ENT>
                        <ENT>JOY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHEN</ENT>
                        <ENT>MAX</ENT>
                        <ENT>HAN-LI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHENG</ENT>
                        <ENT>HUAYI</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHEONG</ENT>
                        <ENT>TIMOTHY</ENT>
                        <ENT>HSIA WEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHEUNG</ENT>
                        <ENT>SIN</ENT>
                        <ENT>TING ALICE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHIANG</ENT>
                        <ENT>ANDREW</ENT>
                        <ENT>YU-CHING</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHIU</ENT>
                        <ENT>GEORGIANA</ENT>
                        <ENT>KONG SUIT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHO</ENT>
                        <ENT>ALEXANDER</ENT>
                        <ENT>HAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHOI</ENT>
                        <ENT>SUN</ENT>
                        <ENT>YOUNG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHOONG</ENT>
                        <ENT>CAROLINE</ENT>
                        <ENT>VICTORIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHOU</ENT>
                        <ENT>PATRICK</ENT>
                        <ENT>JAMES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHOU</ENT>
                        <ENT>TOM</ENT>
                        <ENT>CHI-KWAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHRISTENSON</ENT>
                        <ENT>DEBORAH</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHRISTENSON</ENT>
                        <ENT>STEPHEN</ENT>
                        <ENT>V</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHUA</ENT>
                        <ENT>CHOON</ENT>
                        <ENT>MUI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHUA</ENT>
                        <ENT>KEVIN</ENT>
                        <ENT>WEI QIANG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CHUNG</ENT>
                        <ENT>JUDY</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">CLUBB</ENT>
                        <ENT>BRYCE</ENT>
                        <ENT>STEVEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">COFFEY</ENT>
                        <ENT>ROSALIND</ENT>
                        <ENT>M</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">COHEN</ENT>
                        <ENT>CLAUDE</ENT>
                        <ENT>SOL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CONGER</ENT>
                        <ENT>RONALD</ENT>
                        <ENT>EUGENE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CONWAY</ENT>
                        <ENT>KATE</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">COTTON</ENT>
                        <ENT>JUDITH</ENT>
                        <ENT>F</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CSAPO</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>FRANK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">D'AMATO</ENT>
                        <ENT>MARCELO</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">DASKALOVIC</ENT>
                        <ENT>MONIQUE</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">DAWSON</ENT>
                        <ENT>HEIDI</ENT>
                        <ENT>KATHRYN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DE MORANVILLE</ENT>
                        <ENT>CLAUDE</ENT>
                        <ENT>V C SELLIERS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DE PAIVA</ENT>
                        <ENT>JULIA</ENT>
                        <ENT>SOUZA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DEAN</ENT>
                        <ENT>JANET</ENT>
                        <ENT>TERESA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DEBLESER</ENT>
                        <ENT>ALEXANDER</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">DENTON</ENT>
                        <ENT>CHRIS</ENT>
                        <ENT>EDWARD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DEURING</ENT>
                        <ENT>ALEXANDER</ENT>
                        <ENT>ALBERT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DI DONATO</ENT>
                        <ENT>ROBERTO</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">DOERHOLT</ENT>
                        <ENT>DOROTHE</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">DORRES LOSCH</ENT>
                        <ENT>PAULA</ENT>
                        <ENT>MICHELLE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DREVER</ENT>
                        <ENT>RONALD</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">DU</ENT>
                        <ENT>YUXIANG</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">DUBE</ENT>
                        <ENT>BRENDA</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DUBE</ENT>
                        <ENT>MICHEL</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">DUGU</ENT>
                        <ENT>NANXUN</ENT>
                        <ENT>NATHAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DUIMICH</ENT>
                        <ENT>RITSUKO</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">EASTON</ENT>
                        <ENT>ANDREW</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">EASTON</ENT>
                        <ENT>ELIZABETH</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">EGBERTS</ENT>
                        <ENT>JAN</ENT>
                        <ENT>H</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ELARDO</ENT>
                        <ENT>MARK</ENT>
                        <ENT>ALLEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ELKIN</ENT>
                        <ENT>SARAH</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">ELLIOTT</ENT>
                        <ENT>SUSAN</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">EMERSON</ENT>
                        <ENT>CATHERINE</ENT>
                        <ENT>E</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EMERSON</ENT>
                        <ENT>DAVID</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">ENDZWEIG</ENT>
                        <ENT>ELIZABETH</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">ERB</ENT>
                        <ENT>PRISCA</ENT>
                        <ENT>REGINA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">EVESTAFF</ENT>
                        <ENT>HATIM</ENT>
                        <ENT>SALIM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FAKHOURIE</ENT>
                        <ENT>SHAHINE</ENT>
                        <ENT>ELIZABETH</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="66363"/>
                        <ENT I="01">FANG</ENT>
                        <ENT>HENRY</ENT>
                        <ENT>H L</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FARSTAD</ENT>
                        <ENT>ANNE</ENT>
                        <ENT>CHRISTINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FENG</ENT>
                        <ENT>DAI</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">FINDANI</ENT>
                        <ENT>ROBERT</ENT>
                        <ENT>M</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FISCHER</ENT>
                        <ENT>JOAN</ENT>
                        <ENT>DORIS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FRAZIER</ENT>
                        <ENT>TATTAYA</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">FRIES</ENT>
                        <ENT>ANNA-</ENT>
                        <ENT>CORINNA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FUSE</ENT>
                        <ENT>TETSUHARU</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">GALBRAITH</ENT>
                        <ENT>JOSEPH</ENT>
                        <ENT>BENSON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GANG</ENT>
                        <ENT>DINESH</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">GANN</ENT>
                        <ENT>HEIDI</ENT>
                        <ENT>CAROL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GARCIA</ENT>
                        <ENT>TERCIO</ENT>
                        <ENT>B</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GASS</ENT>
                        <ENT>VERENA</ENT>
                        <ENT>LIPP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GHAI</ENT>
                        <ENT>CHINTU</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">GIBSON</ENT>
                        <ENT>LORRAINE</ENT>
                        <ENT>FRANCES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GONZALES</ENT>
                        <ENT>REX</ENT>
                        <ENT>BRUCE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GRABER</ENT>
                        <ENT>IRENE</ENT>
                        <ENT>KLARA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GRACIE</ENT>
                        <ENT>JAMES</ENT>
                        <ENT>S</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GRACIE</ENT>
                        <ENT>KATHERINE</ENT>
                        <ENT>J</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GRANOV</ENT>
                        <ENT>ADI</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">GREEN</ENT>
                        <ENT>KATHERINE</ENT>
                        <ENT>LOUISA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GREER</ENT>
                        <ENT>BUEFORD</ENT>
                        <ENT>D</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GRIFFITHS</ENT>
                        <ENT>DAVID</ENT>
                        <ENT>THOMAS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GRIMM</ENT>
                        <ENT>CHRISTOPH</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">GRIMM</ENT>
                        <ENT>KATJA</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">GULINO</ENT>
                        <ENT>SAYAN</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">HABIB</ENT>
                        <ENT>OK</ENT>
                        <ENT>YO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HACKETT</ENT>
                        <ENT>PAMELA</ENT>
                        <ENT>D. J.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HALL</ENT>
                        <ENT>NATALIE</ENT>
                        <ENT>JUDITH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HAMI</ENT>
                        <ENT>AMIR</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">HAMI</ENT>
                        <ENT>HOSSEIN</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">HAN</ENT>
                        <ENT>JIAHUAI</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">HANICK</ENT>
                        <ENT>SUZIE</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">HANSEN</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>LEIF</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HANSSON</ENT>
                        <ENT>KARL</ENT>
                        <ENT>STEFAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HARRIGAN</ENT>
                        <ENT>TERRY</ENT>
                        <ENT>TOLEDO CARADINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HART</ENT>
                        <ENT>MARIANNE</ENT>
                        <ENT>DANIELE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HARVEY</ENT>
                        <ENT>BRUCE</ENT>
                        <ENT>E</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HASSAN</ENT>
                        <ENT>ADRIAN</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">HAYDEN</ENT>
                        <ENT>RICHARD</ENT>
                        <ENT>MICHAEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HEALEY</ENT>
                        <ENT>EDWARD</ENT>
                        <ENT>JAMES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HEALEY</ENT>
                        <ENT>SARAH</ENT>
                        <ENT>ANGELA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HELM</ENT>
                        <ENT>EVA</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">HERRMANN</ENT>
                        <ENT>MARTINE</ENT>
                        <ENT>S</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HESS</ENT>
                        <ENT>CLINTON</ENT>
                        <ENT>A</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HESSER</ENT>
                        <ENT>BORIS</ENT>
                        <ENT>A</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HEUBACH</ENT>
                        <ENT>JOHANN</ENT>
                        <ENT>GABRIEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HEUSS</ENT>
                        <ENT>STELLA</ENT>
                        <ENT>IRENE GERTRUD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HICKERSBERGER</ENT>
                        <ENT>JOSEF</ENT>
                        <ENT>ADRIAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HILLESLAND</ENT>
                        <ENT>SONJA</ENT>
                        <ENT>KARIN LYNCH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HIRAO</ENT>
                        <ENT>HIROKAZU</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">HO</ENT>
                        <ENT>JASON</ENT>
                        <ENT>HON SUM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HO</ENT>
                        <ENT>SALENA</ENT>
                        <ENT>CHI KIT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HOLLENSTEIN</ENT>
                        <ENT>PETER</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">HOLLENSTEIN</ENT>
                        <ENT>URSULA</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">HONG</ENT>
                        <ENT>RICK</ENT>
                        <ENT>KWANGBUM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HOON</ENT>
                        <ENT>ELIZABETH</ENT>
                        <ENT>LI-PING</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HOU</ENT>
                        <ENT>HSIEN</ENT>
                        <ENT>LIANG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">HSU</ENT>
                        <ENT>MIKE</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">HSU</ENT>
                        <ENT>ZE-YI</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">HU</ENT>
                        <ENT>KE</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">IN</ENT>
                        <ENT>KEUN</ENT>
                        <ENT>WOO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ISA</ENT>
                        <ENT>NOOR</ENT>
                        <ENT>LIZA MD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JAFFER</ENT>
                        <ENT>OMER</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">JAGGI MCCOY</ENT>
                        <ENT>ISABELLE</ENT>
                        <ENT>MARY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JARDINE</ENT>
                        <ENT>KATHERINE</ENT>
                        <ENT>ALLEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JOHNSON</ENT>
                        <ENT>ANTHONY</ENT>
                        <ENT>W</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JOHNSON</ENT>
                        <ENT>RICHARD</ENT>
                        <ENT>M</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JOHNSON</ENT>
                        <ENT>RUTH</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">JOSEPH</ENT>
                        <ENT>CHANG</ENT>
                        <ENT>CHO YAM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KANEKO</ENT>
                        <ENT>TAIZO</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">KANG</ENT>
                        <ENT>QIAO</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">KANSEKINE</ENT>
                        <ENT>BETTY</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">KAWKABANI</ENT>
                        <ENT>JAMES</ENT>
                        <ENT>ROBERT</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="66364"/>
                        <ENT I="01">KAZMI</ENT>
                        <ENT>KRISTINA</ENT>
                        <ENT>ZEHRA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KIANG</ENT>
                        <ENT>LILLIAN</ENT>
                        <ENT>SHIN PING</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KIM</ENT>
                        <ENT>CHONG</ENT>
                        <ENT>AE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KIM</ENT>
                        <ENT>JULIA</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">KIM</ENT>
                        <ENT>WILLIAM</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">KINGMAN</ENT>
                        <ENT>MARCUS</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">KOENIG</ENT>
                        <ENT>JENNIFER</ENT>
                        <ENT>RENEE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KONST</ENT>
                        <ENT>SOLVEIG</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">KORZINEK</ENT>
                        <ENT>ROBERT</ENT>
                        <ENT>JAMES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KRAUSE</ENT>
                        <ENT>MARTIN</ENT>
                        <ENT>WERNER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KUSCHILL</ENT>
                        <ENT>TIMOTHY</ENT>
                        <ENT>JOHN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KWAK</ENT>
                        <ENT>PAUL</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">LAGIER</ENT>
                        <ENT>DIANE</ENT>
                        <ENT>LUCE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LAL</ENT>
                        <ENT>DEEPAK</ENT>
                        <ENT>K</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LANDAU</ENT>
                        <ENT>JENNIFER</ENT>
                        <ENT>MAY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LANDI</ENT>
                        <ENT>TOMMASO</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">LANG</ENT>
                        <ENT>VICENTE</ENT>
                        <ENT>C</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LANGHAM</ENT>
                        <ENT>ELAINE</ENT>
                        <ENT>GRACE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LAU</ENT>
                        <ENT>DOROTHY</ENT>
                        <ENT>WAN HANG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LAU</ENT>
                        <ENT>KIMBERLY</ENT>
                        <ENT>SIU YAN KAIULANI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LAU</ENT>
                        <ENT>LUCY</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">LAUBE</ENT>
                        <ENT>WERNER</ENT>
                        <ENT>JOHN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LAULUND</ENT>
                        <ENT>HENRIK</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEE</ENT>
                        <ENT>HAE</ENT>
                        <ENT>WON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEE</ENT>
                        <ENT>HAN</ENT>
                        <ENT>YOUNG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEE</ENT>
                        <ENT>KAI</ENT>
                        <ENT>FU</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEE</ENT>
                        <ENT>SHEN</ENT>
                        <ENT>LING</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEE</ENT>
                        <ENT>YONG</ENT>
                        <ENT>YE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEES</ENT>
                        <ENT>MARIA</ENT>
                        <ENT>ADELAIDA BIBI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEO</ENT>
                        <ENT>LIONEL</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">LERCHBAUMER</ENT>
                        <ENT>ANDREAS</ENT>
                        <ENT>JOSEF</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEUENBERGER</ENT>
                        <ENT>STEPHAN</ENT>
                        <ENT>DAVID</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEUNG</ENT>
                        <ENT>ANDREA</ENT>
                        <ENT>TSE-HING</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEUNG</ENT>
                        <ENT>SUSAN</ENT>
                        <ENT>O</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LEWIS</ENT>
                        <ENT>TODD</ENT>
                        <ENT>GRAHAM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LI</ENT>
                        <ENT>BRYAN</ENT>
                        <ENT>CHEE KEUNG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LI</ENT>
                        <ENT>LYDIA</ENT>
                        <ENT>KWAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LIEBMANN</ENT>
                        <ENT>BRAD</ENT>
                        <ENT>HUNTER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LIM</ENT>
                        <ENT>LILLAN</ENT>
                        <ENT>YUXIAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LIM</ENT>
                        <ENT>VIVIAN</ENT>
                        <ENT>YUJING</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LIN</ENT>
                        <ENT>CHARLYN</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">LINCKE</ENT>
                        <ENT>THOMAS</ENT>
                        <ENT>ROBERT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LING</ENT>
                        <ENT>PHYLLIS</ENT>
                        <ENT>T</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LO</ENT>
                        <ENT>ALEXANDER</ENT>
                        <ENT>CHUN HIM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LOWENHARDT</ENT>
                        <ENT>SANNE</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">LUKAC</ENT>
                        <ENT>SAVA</ENT>
                        <ENT>R</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LUTHI</ENT>
                        <ENT>MAJA</ENT>
                        <ENT>CHRISTINA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MA</ENT>
                        <ENT>YUWEI</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">MAC HALE</ENT>
                        <ENT>LAURA</ENT>
                        <ENT>JANE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MACFARLAND</ENT>
                        <ENT>FREDERIK</ENT>
                        <ENT>CHARLES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MAHON</ENT>
                        <ENT>ALEXANDRA</ENT>
                        <ENT>ROSE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MANINA</ENT>
                        <ENT>GEORGE</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">MANSOUR</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">MAOR</ENT>
                        <ENT>DROR</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">MAPLE</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>RANDALL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MARINCEK</ENT>
                        <ENT>BORIS</ENT>
                        <ENT>CHRISTIAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MARSHALL</ENT>
                        <ENT>PAUL</ENT>
                        <ENT>DUNCAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MATSUNO</ENT>
                        <ENT>SATOSHI</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">MC DANIEL</ENT>
                        <ENT>CRISTINA</ENT>
                        <ENT>ELENA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MCCOY</ENT>
                        <ENT>RAINER</ENT>
                        <ENT>FRANZ</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MEDEIROS</ENT>
                        <ENT>PATRICIA</ENT>
                        <ENT>FARIA VASCONCELLOS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MEHES</ENT>
                        <ENT>ERIKA</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">MEIER WALTER</ENT>
                        <ENT>SUSANNE</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">MELVIN</ENT>
                        <ENT>STEPHEN</ENT>
                        <ENT>JENKINS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MEYER</ENT>
                        <ENT>BARBARA</ENT>
                        <ENT>JEAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MII</ENT>
                        <ENT>MITSUKO</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">MII</ENT>
                        <ENT>NOBUO</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">MOLKO</ENT>
                        <ENT>ALBERT</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">MONAUNI</ENT>
                        <ENT>CHRISTIAN</ENT>
                        <ENT>KARL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MONAUNI</ENT>
                        <ENT>CHRISTINE</ENT>
                        <ENT>G</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MONNIER</ENT>
                        <ENT>CHARLES</ENT>
                        <ENT>EDWARD</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MONNIER</ENT>
                        <ENT>SUSAN</ENT>
                        <ENT>HEFFNER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MORITZ</ENT>
                        <ENT>ERIKA</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">MORITZ</ENT>
                        <ENT>GUNNAR</ENT>
                        <ENT>H</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="66365"/>
                        <ENT I="01">MURPHY</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>N</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MUSE</ENT>
                        <ENT>RODNEY</ENT>
                        <ENT>CHADWICK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NA</ENT>
                        <ENT>EDWARD</ENT>
                        <ENT>YOON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NADRAG</ENT>
                        <ENT>KARIN</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">NADRAG</ENT>
                        <ENT>ROLF</ENT>
                        <ENT>PETER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NARWANI</ENT>
                        <ENT>AMIT</ENT>
                        <ENT>ARJAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NEWMAN</ENT>
                        <ENT>BRIAN</ENT>
                        <ENT>MICHAEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NG</ENT>
                        <ENT>KEILEM</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">NIEM</ENT>
                        <ENT>CHRISTINE</ENT>
                        <ENT>CHEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NIETO</ENT>
                        <ENT>ANTONIO</ENT>
                        <ENT>L</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NITSCHE</ENT>
                        <ENT>MARC</ENT>
                        <ENT>ERIC</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NORSTEBO</ENT>
                        <ENT>ASTRID</ENT>
                        <ENT>CHRISTINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OKHAI</ENT>
                        <ENT>LEYLA</ENT>
                        <ENT>JIHAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ONG</ENT>
                        <ENT>JASMINE</ENT>
                        <ENT>ANGIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OTHON-LEVIN</ENT>
                        <ENT>AURA</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">PALMER</ENT>
                        <ENT>EDWARD</ENT>
                        <ENT>LEWIS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PAN</ENT>
                        <ENT>ANDY</ENT>
                        <ENT>KUO-AN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PAN</ENT>
                        <ENT>THOMAS</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">PANGBURN</ENT>
                        <ENT>STEVEN</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">PAPIN</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>PHILLIP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PARK</ENT>
                        <ENT>JAMES</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">PARK</ENT>
                        <ENT>KYUNG</ENT>
                        <ENT>SOOK</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PATTY</ENT>
                        <ENT>ELAINE</ENT>
                        <ENT>FLORENCE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PIKE</ENT>
                        <ENT>JOE</ENT>
                        <ENT>B</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PIKE</ENT>
                        <ENT>KATHRYN</ENT>
                        <ENT>ANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PIKE</ENT>
                        <ENT>LAURA</ENT>
                        <ENT>A</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">PISTOR</ENT>
                        <ENT>LUDGER</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">PORTER</ENT>
                        <ENT>TINA</ENT>
                        <ENT>DENISE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">POSEN</ENT>
                        <ENT>KEVIN</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">PREET</ENT>
                        <ENT>GARY</ENT>
                        <ENT>V</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">QUEEN</ENT>
                        <ENT>BRENDA</ENT>
                        <ENT>JANE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">QUEK</ENT>
                        <ENT>SARAH</ENT>
                        <ENT>YING HUI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">QUINN</ENT>
                        <ENT>EMMA</ENT>
                        <ENT>JANE VICTORIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REDDING</ENT>
                        <ENT>THURSTAN</ENT>
                        <ENT>LAM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REED</ENT>
                        <ENT>KUN</ENT>
                        <ENT>TIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RICHARD</ENT>
                        <ENT>NANCY</ENT>
                        <ENT>G</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RICHTER</ENT>
                        <ENT>CHRISTOPHER</ENT>
                        <ENT>L</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RICHTER</ENT>
                        <ENT>YVONNE</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">RIGBY</ENT>
                        <ENT>DAVID</ENT>
                        <ENT>KEITH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RILEY</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>SHAWN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RITCHIE</ENT>
                        <ENT>AARON</ENT>
                        <ENT>ROBERT THANKE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ROBERTSON</ENT>
                        <ENT>PENNY</ENT>
                        <ENT>SAMANTHA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ROGER</ENT>
                        <ENT>CHRISTINE</ENT>
                        <ENT>LEE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ROSS</ENT>
                        <ENT>ANNE</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">ROSS</ENT>
                        <ENT>ROBERT</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">RUEGG</ENT>
                        <ENT>JOSEF</ENT>
                        <ENT>NICKOLAUS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RUEGG</ENT>
                        <ENT>URSULA</ENT>
                        <ENT>MARIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RUTLEDGE</ENT>
                        <ENT>TRACY</ENT>
                        <ENT>MARIE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SACHS</ENT>
                        <ENT>ALEXANDER</ENT>
                        <ENT>CLAUS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SACHS</ENT>
                        <ENT>PHILIPP</ENT>
                        <ENT>GUNTER MOHSEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SAGENKAHN</ENT>
                        <ENT>DAVA</ENT>
                        <ENT>ILISE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SALAM</ENT>
                        <ENT>SAED</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">SANNAREDDY</ENT>
                        <ENT>RAVINDRA</ENT>
                        <ENT>B</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SAP</ENT>
                        <ENT>JAN</ENT>
                        <ENT>M</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHAUFELBERGER</ENT>
                        <ENT>HENRI</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHAUFELBERGER</ENT>
                        <ENT>MARGRIT</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHNEIDER</ENT>
                        <ENT>ANETTE</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHNEIDER</ENT>
                        <ENT>MANFRED</ENT>
                        <ENT>OTTO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHROEDER</ENT>
                        <ENT>PETER</ENT>
                        <ENT>L</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHRURS</ENT>
                        <ENT>ALBERT</ENT>
                        <ENT>MAURICE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCHWARZ</ENT>
                        <ENT>MARKUS</ENT>
                        <ENT>WILLIAM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCOTT</ENT>
                        <ENT>JUNE</ENT>
                        <ENT>E</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCOTT</ENT>
                        <ENT>ROBERT</ENT>
                        <ENT>P</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SCOTT</ENT>
                        <ENT>SUSAN</ENT>
                        <ENT>ANN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SEBBA</ENT>
                        <ENT>HENRIETTA</ENT>
                        <ENT>AMY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SEIF- ELYAZAL</ENT>
                        <ENT>HATEM</ENT>
                        <ENT>SAID</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SEILERN</ENT>
                        <ENT>HENRY</ENT>
                        <ENT>OGDEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SENEFF</ENT>
                        <ENT>ELIZABETH</ENT>
                        <ENT>VICTORIA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SHATTAN</ENT>
                        <ENT>COLIN</ENT>
                        <ENT>MICHAEL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SHELTON</ENT>
                        <ENT>SCOTT</ENT>
                        <ENT>H</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SHI</ENT>
                        <ENT>YIGONG</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">SHIA</ENT>
                        <ENT>LOVE</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">SHIPP</ENT>
                        <ENT>TIMOTHY</ENT>
                        <ENT>R</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SHIUE</ENT>
                        <ENT>YEONG</ENT>
                        <ENT>RUEY</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="66366"/>
                        <ENT I="01">SHOKROLLAHI</ENT>
                        <ENT>MOHAMMAD</ENT>
                        <ENT>AMIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SIDERMAN</ENT>
                        <ENT>PETER</ENT>
                        <ENT>M</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SIMON</ENT>
                        <ENT>KENNETH</ENT>
                        <ENT>ROBERT</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SIMPSON</ENT>
                        <ENT>DERMOT</ENT>
                        <ENT>MATTHEW</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SMINKEY (AKA SMINKEY, TAKUMA)</ENT>
                        <ENT>PAUL</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">SOLA</ENT>
                        <ENT>JOHN</ENT>
                        <ENT>BEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SOLARES</ENT>
                        <ENT>SIGMUND</ENT>
                        <ENT>JOSEPH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SON</ENT>
                        <ENT>KENNY</ENT>
                        <ENT>HO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STAVRINOU</ENT>
                        <ENT>ALEXANDROS</ENT>
                        <ENT>IASONAS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STELLING</ENT>
                        <ENT>DONALD</ENT>
                        <ENT>KAY</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STILTNER</ENT>
                        <ENT>MI</ENT>
                        <ENT>RYUNG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STOKES</ENT>
                        <ENT>GWYNETH</ENT>
                        <ENT>EVELYN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">STOPFORD</ENT>
                        <ENT>ROBERT</ENT>
                        <ENT>WOODMAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SU</ENT>
                        <ENT>TSUNG</ENT>
                        <ENT>HSUAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SUBRAMANIAM</ENT>
                        <ENT>SUBITHA</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">SUTTON</ENT>
                        <ENT>RICHARD</ENT>
                        <ENT>DODGE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SUZUKI</ENT>
                        <ENT>AKIKO</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">SUZUKI</ENT>
                        <ENT>KAZUNORI</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">SZABO</ENT>
                        <ENT>EILEEN</ENT>
                        <ENT>ROSE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TABATZNIK</ENT>
                        <ENT>RISA</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">TABATZNIK</ENT>
                        <ENT>SETH</ENT>
                        <ENT>BENJAMIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TAGAMI</ENT>
                        <ENT>MARIKO</ENT>
                        <ENT>K</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TANNER</ENT>
                        <ENT>NICOLE</ENT>
                        <ENT>CAROLINE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THAM</ENT>
                        <ENT>SALOON</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">THE</ENT>
                        <ENT>E</ENT>
                        <ENT>DELORES</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THOMPSON</ENT>
                        <ENT>ALDIN</ENT>
                        <ENT>EUGENE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TIZARD</ENT>
                        <ENT>ROBERT</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">TRAUB</ENT>
                        <ENT>ANJA</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">TRIMBLE</ENT>
                        <ENT>PETER</ENT>
                        <ENT>W</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TSE</ENT>
                        <ENT>MAXIMILIEN</ENT>
                        <ENT>HONG LIN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TSO</ENT>
                        <ENT>REBECCA</ENT>
                        <ENT>MAN CHI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ULIVI</ENT>
                        <ENT>JUAN</ENT>
                        <ENT>ARMANDO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">URBANC</ENT>
                        <ENT>PETER</ENT>
                        <ENT>VLADIMIR</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VALDEZ</ENT>
                        <ENT>LANCE</ENT>
                        <ENT>ORMAND</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VAN DER GRACHT DE ROMMERSWAEL</ENT>
                        <ENT>PHILIPPE</ENT>
                        <ENT>GUY J.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VARGAS</ENT>
                        <ENT>ASTRID</ENT>
                        <ENT>PRAG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VAUGHAN</ENT>
                        <ENT>GREGORY</ENT>
                        <ENT>JEROME</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">VOSSEN</ENT>
                        <ENT>EMILY</ENT>
                        <ENT>SUZANNE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WAIBEL</ENT>
                        <ENT>SIGOURNEY</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">WALKER</ENT>
                        <ENT>DOUGLAS</ENT>
                        <ENT>GORDON</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WALLEY</ENT>
                        <ENT>AMANDA</ENT>
                        <ENT>CLARE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WALTER</ENT>
                        <ENT>FELIX</ENT>
                        <ENT>PAUL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WALZ</ENT>
                        <ENT>GERD</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">WAN</ENT>
                        <ENT>SANDY</ENT>
                        <ENT>SAN-MING</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WANG</ENT>
                        <ENT>DAVID</ENT>
                        <ENT>TSUNG-HO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WANG</ENT>
                        <ENT>WENNING</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">WARMINGTON</ENT>
                        <ENT>CLIFFORD</ENT>
                        <ENT>EVERALD ERROL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WEBER</ENT>
                        <ENT>SONJA</ENT>
                        <ENT>HELENE</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WERREN</ENT>
                        <ENT>MARKUS</ENT>
                        <ENT>PAUL</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WILDE</ENT>
                        <ENT>OSAMU</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">WILLCOCK</ENT>
                        <ENT>KENNETH</ENT>
                        <ENT>MILNER</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WINGERT</ENT>
                        <ENT>MICHAEL</ENT>
                        <ENT>L</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WINGERT</ENT>
                        <ENT>MONICA</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">WITSCHI</ENT>
                        <ENT>MARION</ENT>
                        <ENT>RUTH</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WOLF</ENT>
                        <ENT>LINDA</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">WONG</ENT>
                        <ENT>BYRON</ENT>
                        <ENT>ANDREW</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WONG</ENT>
                        <ENT>CHING</ENT>
                        <ENT>TONG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WONG</ENT>
                        <ENT>DEREK</ENT>
                        <ENT>SHU LUEN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WONG</ENT>
                        <ENT>KATHLEEN</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">WONG</ENT>
                        <ENT>PHYLLIS</ENT>
                        <ENT>PO-YAN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WOU</ENT>
                        <ENT>LYNDON</ENT>
                        <ENT>LIEN-SUN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">WU</ENT>
                        <ENT>BIN</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">WU</ENT>
                        <ENT>HUI-YEN</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">WU</ENT>
                        <ENT>KE</ENT>
                        <ENT>ISABELLA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">XU</ENT>
                        <ENT>HUAZHANG</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">YAMAMOTO</ENT>
                        <ENT>HARUHISA</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">YANG</ENT>
                        <ENT>JUSTIN</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">YANG</ENT>
                        <ENT>ROSA</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">YECHIEL</ENT>
                        <ENT>JORDANA</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">YOAZ</ENT>
                        <ENT>ADIEL</ENT>
                        <ENT>MENACHEM</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YU</ENT>
                        <ENT>BING</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">YUEN</ENT>
                        <ENT>REGINA</ENT>
                        <ENT>SI-HUI</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">YUNG</ENT>
                        <ENT>JEFFREY</ENT>
                        <ENT>YAN-LEUN</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ZEIN</ENT>
                        <ENT>SOLAIMAN</ENT>
                        <ENT>MAZEN</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="66367"/>
                        <ENT I="01">ZHAO</ENT>
                        <ENT>RUI</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">ZORZINO</ENT>
                        <ENT>LUCA</ENT>
                        <ENT>ALESSIO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ZUCKERBRAUN</ENT>
                        <ENT>LOUIS</ENT>
                        <ENT>DAVID</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <DATED>Dated: October 12. 2011.</DATED>
                    <NAME>Ann V. Gaudeli,</NAME>
                    <TITLE>Manager Team 103, Examinations Operations—Philadelphia Compliance Services.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27570 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
                <SUBJECT>Joint Biomedical Laboratory Research and Development and Clinical Science Research and Development Services Scientific Merit Review Board; Notice of Meetings</SUBJECT>
                <P>The Department of Veterans Affairs gives notice under the Public Law 92-463 (Federal Advisory Committee Act) that the panels of the Joint Biomedical Laboratory Research and Development and Clinical Science Research and Development Services Scientific Merit Review Board will meet from 8 a.m. to 5 p.m. on the dates indicated below:</P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,r100,r100">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Panel </CHED>
                        <CHED H="1">Date(s) </CHED>
                        <CHED H="1">Location </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Hematology </ENT>
                        <ENT>November 16, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Neurobiology-A </ENT>
                        <ENT>November 17, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Neurobiology-E </ENT>
                        <ENT>November 17, 2011 </ENT>
                        <ENT>The Sheraton Crystal City.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Endocrinology-B </ENT>
                        <ENT>November 18, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cellular &amp; Molecular Medicine </ENT>
                        <ENT>November 21, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Surgery </ENT>
                        <ENT>November 22, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Endocrinology-A </ENT>
                        <ENT>November 29-30, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Neurobiology-D </ENT>
                        <ENT>November 29, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Neurobiology-C </ENT>
                        <ENT>December 1-2, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Infectious Diseases-B </ENT>
                        <ENT>December 2, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pulmonary Medicine </ENT>
                        <ENT>December 2, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cardiovascular Studies </ENT>
                        <ENT>December 5, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Infectious Diseases-A </ENT>
                        <ENT>December 5, 2011 </ENT>
                        <ENT>*VA Central Office. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Epidemiology </ENT>
                        <ENT>December 7, 2011 </ENT>
                        <ENT>*VA Central Office. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Immunology </ENT>
                        <ENT>December 7, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Nephrology </ENT>
                        <ENT>December 8, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Oncology </ENT>
                        <ENT>December 8-9, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Clinical Research Program </ENT>
                        <ENT>December 8-9, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Gastroenterology </ENT>
                        <ENT>December 9, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mental Hlth &amp; Behav Sci-A </ENT>
                        <ENT>December 12, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mental Hlth &amp; Behav Sci-B </ENT>
                        <ENT>December 14, 2011 </ENT>
                        <ENT>The Sheraton Crystal City. </ENT>
                    </ROW>
                    <TNOTE>The addresses of the hotel and VA Central Office are: </TNOTE>
                    <TNOTE>The Sheraton Crystal City, 1800 Jefferson Davis Highway, Arlington, VA. </TNOTE>
                    <TNOTE>*VA Central Office, 131 M Street, NE., Washington, DC. </TNOTE>
                </GPOTABLE>
                <HD SOURCE="HD1">Teleconference</HD>
                <P>The purpose of the Merit Review Board is to provide advice on the scientific quality, budget, safety and mission relevance of investigator-initiated research proposals submitted for VA merit review consideration. Proposals submitted for review by the Board involve a wide range of medical specialties within the general areas of biomedical, behavioral and clinical science research.</P>
                <P>The panel meetings will be open to the public for approximately one hour at the start of each meeting to discuss the general status of the program. The remaining portion of each panel meeting will be closed to the public for the review, discussion, and evaluation of initial and renewal research proposals.</P>
                <P>The closed portion of each meeting involves discussion, examination, reference to staff and consultant critiques of research proposals. During this portion of each meeting, discussions will deal with scientific merit of each proposal, qualifications of personnel conducting the studies, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy, as well as research information, the premature disclosure of which could significantly frustrate implementation of proposed agency action regarding such research proposals.</P>
                <P>As provided by subsection 10(d) of Public Law 92-463, as amended, closing portions of these panel meetings is in accordance with 5 U.S.C., 552b(c) (6) and (9)(B). Those who plan to attend or would like to obtain a copy of minutes of the panel meetings and rosters of the members of the panels should contact LeRoy G. Frey, Ph.D., Chief, Program Review (10P9B), Department of Veterans Affairs, 810 Vermont Avenue, NW., Washington, DC 20420 at (202) 443-5674.</P>
                <SIG>
                    <DATED>Dated: October 21, 2011.</DATED>
                    <P>By Direction of the Secretary.</P>
                    <NAME>Vivian Drake,</NAME>
                    <TITLE>Committee Management Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2011-27717 Filed 10-25-11; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
    </NOTICES>
    <VOL>76</VOL>
    <NO>207</NO>
    <DATE>Wednesday, October 26, 2011</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="66369"/>
            <PARTNO>Part II</PARTNO>
            <AGENCY TYPE="P">Department of the Interior</AGENCY>
            <SUBAGY>Fish and Wildlife Service</SUBAGY>
            <HRULE/>
            <CFR>50 CFR Part 17</CFR>
            <TITLE>Endangered and Threatened Wildlife and Plants; Review of Native Species That Are Candidates for Listing as Endangered or Threatened; Annual Notice of Findings on Resubmitted Petitions; Annual Description of Progress on Listing Actions; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="66370"/>
                    <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                    <SUBAGY>Fish and Wildlife Service</SUBAGY>
                    <CFR>50 CFR Part 17</CFR>
                    <DEPDOC>[Docket No. FWS-R9-ES-2011-0061; MO-9221050083-B2]</DEPDOC>
                    <SUBJECT>Endangered and Threatened Wildlife and Plants; Review of Native Species That Are Candidates for Listing as Endangered or Threatened; Annual Notice of Findings on Resubmitted Petitions; Annual Description of Progress on Listing Actions</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Fish and Wildlife Service, Interior.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Notice of review.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>
                            In this Candidate Notice of Review (CNOR), we, the U.S. Fish and Wildlife Service (Service), present an updated list of plant and animal species native to the United States that we regard as 
                            <E T="03">candidates</E>
                             for or have proposed for addition to the Lists of Endangered and Threatened Wildlife and Plants under the Endangered Species Act of 1973, as amended. Identification of candidate species can assist environmental planning efforts by providing advance notice of potential listings, allowing landowners and resource managers to alleviate threats and thereby possibly remove the need to list species as endangered or threatened. Even if we subsequently list a candidate species, the early notice provided here could result in more options for species management and recovery by prompting candidate conservation measures to alleviate threats to the species.
                        </P>
                        <P>The CNOR summarizes the status and threats that we evaluated in order to determine that species qualify as candidates and to assign a listing priority number (LPN) to each species or to determine that species should be removed from candidate status. Additional material that we relied on is available in the Species Assessment and Listing Priority Assignment Forms (species assessment forms) for each candidate species.</P>
                        <P>Overall, this CNOR recognizes three new candidates, changes the LPN for seven candidates, and removes three species from candidate status. Combined with other decisions for individual species that were published separately from this CNOR in the past year, the current number of species that are candidates for listing is 244.</P>
                        <P>This document also includes our findings on resubmitted petitions and describes our progress in revising the Lists of Endangered and Threatened Wildlife and Plants (Lists) during the period October 1, 2010, through September 30, 2011.</P>
                        <P>We request additional status information that may be available for the 244 candidate species identified in this CNOR.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>We will accept information on any of the species in this Candidate Notice of Review at any time.</P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>
                            This notice is available on the Internet at 
                            <E T="03">http://www.regulations.gov</E>
                             and 
                            <E T="03">http://www.fws.gov/endangered/what-e-do/cnor.html.</E>
                             Species assessment forms with information and references on a particular candidate species' range, status, habitat needs, and listing priority assignment are available for review at the appropriate Regional Office listed below in 
                            <E T="02">SUPPLEMENTARY INFORMATION</E>
                             or at the Office of Communications and Candidate Conservation, Arlington, VA (see address under 
                            <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                            ), or on our Web site (
                            <E T="03">http://ecos.fws.gov/tess_public/pub/SpeciesReport.do?listingType=C&amp;mapstatus=1</E>
                            ). Please submit any new information, materials, comments, or questions of a general nature on this notice to the Arlington, VA, address listed under 
                            <E T="02">FOR FURTHER INFORMATION CONTACT.</E>
                             Please submit any new information, materials, comments, or questions pertaining to a particular species to the address of the Endangered Species Coordinator in the appropriate Regional Office listed in 
                            <E T="02">SUPPLEMENTARY INFORMATION</E>
                            .
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>The Endangered Species Coordinator(s) in the appropriate Regional Office(s), or Chief, Office of Communications and Candidate Conservation, U.S. Fish and Wildlife Service, 4401 N. Fairfax Drive, Room 420, Arlington, VA 22203 (telephone 703-358-2171). Persons who use a telecommunications device for the deaf (TDD) may call the Federal Information Relay Service (FIRS) at 800-877-8339.</P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>We request additional status information that may be available for any of the candidate species identified in this CNOR. We will consider this information to monitor changes in the status or LPN of candidate species and to manage candidates as we prepare listing documents and future revisions to the notice of review. We also request information on additional species to consider including as candidates as we prepare future updates of this notice.</P>
                    <P>
                        You may submit your information concerning this notice in general or for any of the species included in this notice by one of the methods listed in the 
                        <E T="02">ADDRESSES</E>
                         section.
                    </P>
                    <P>
                        Species-specific information and materials we receive will be available for public inspection by appointment, during normal business hours, at the appropriate Regional Office listed below under Request for Information in 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                        . General information we receive will be available at the Office of Communications and Candidate Conservation, Arlington, VA (see address under 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        ).
                    </P>
                    <HD SOURCE="HD1">Candidate Notice of Review</HD>
                    <HD SOURCE="HD2">Background</HD>
                    <P>
                        The Endangered Species Act of 1973, as amended (16 U.S.C. 1531 
                        <E T="03">et seq.</E>
                        ) (ESA), requires that we identify species of wildlife and plants that are endangered or threatened, based on the best available scientific and commercial information. As defined in section 3 of the ESA, an endangered species is any species which is in danger of extinction throughout all or a significant portion of its range, and a threatened species is any species which is likely to become an endangered species within the foreseeable future throughout all or a significant portion of its range. Through the Federal rulemaking process, we add species that meet these definitions to the List of Endangered and Threatened Wildlife at 50 CFR 17.11 or the List of Endangered and Threatened Plants at 50 CFR 17.12. As part of this program, we maintain a list of species that we regard as candidates for listing. A candidate species is one for which we have on file sufficient information on biological vulnerability and threats to support a proposal to list as endangered or threatened, but for which preparation and publication of a proposal is precluded by higher priority listing actions. We may identify a species as a candidate for listing after we have conducted an evaluation of its status on our own initiative, or after we have made a positive finding on a petition to list a species, in particular we have found that listing is warranted but precluded by other higher priority listing action (see the Petition Findings section, below).
                    </P>
                    <P>
                        We maintain this list of candidates for a variety of reasons: To notify the public that these species are facing threats to their survival; to provide advance knowledge of potential listings that could affect decisions of environmental planners and developers; to provide information that may stimulate and guide conservation efforts that will remove or reduce threats to these species and possibly make listing unnecessary; to request input from interested parties to help us identify 
                        <PRTPAGE P="66371"/>
                        those candidate species that may not require protection under the ESA or additional species that may require the ESA's protections; and to request necessary information for setting priorities for preparing listing proposals. We strongly encourage collaborative conservation efforts for candidate species, and offer technical and financial assistance to facilitate such efforts. For additional information regarding such assistance, please contact the appropriate Regional Office listed under Request for Information or visit our Web site, 
                        <E T="03">http://www.fws.gov/endangered/what-we-do/cca.html.</E>
                    </P>
                    <HD SOURCE="HD2">Previous Notices of Review</HD>
                    <P>
                        We have been publishing candidate notices of review (CNOR) since 1975. The most recent CNOR (prior to this CNOR) was published on November 10, 2010 (75 FR 69222). CNORs published since 1994 are available on our Web site, 
                        <E T="03">http://www.fws.gov/endangered/what-we-do/cnor.html.</E>
                         For copies of CNORs published prior to 1994, please contact the Office of Communications and Candidate Conservation (see 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section above).
                    </P>
                    <P>On September 21, 1983, we published guidance for assigning an LPN for each candidate species (48 FR 43098). Using this guidance, we assign each candidate an LPN of 1 to 12, depending on the magnitude of threats, immediacy of threats, and taxonomic status; the lower the LPN, the higher the listing priority (that is, a species with an LPN of 1 would have the highest listing priority). Section 4(h)(3) of the ESA (15 U.S.C. 1533(h)(3)) requires the Secretary to establish guidelines for such a priority-ranking guidance system. As explained below, in using this system we first categorize based on the magnitude of the threat(s), then by the immediacy of the threat(s), and finally by taxonomic status.</P>
                    <P>Under this priority-ranking system, magnitude of threat can be either “high” or “moderate to low.” This criterion helps ensure that the species facing the greatest threats to their continued existence receive the highest listing priority. It is important to recognize that all candidate species face threats to their continued existence, so the magnitude of threats is in relative terms. For all candidate species, the threats are of sufficiently high magnitude to put them in danger of extinction, or make them likely to become in danger of extinction in the foreseeable future. But for species with higher magnitude threats, the threats have a greater likelihood of bringing about extinction or are expected to bring about extinction on a shorter timescale (once the threats are imminent) than for species with lower magnitude threats. Because we do not routinely quantify how likely or how soon extinction would be expected to occur absent listing, we must evaluate factors that contribute to the likelihood and time scale for extinction. We therefore consider information such as: The number of populations or extent of range of the species affected by the threat(s) or both; the biological significance of the affected population(s), taking into consideration the life-history characteristics of the species and its current abundance and distribution; whether the threats affect the species in only a portion of its range, and if so the likelihood of persistence of the species in the unaffected portions; the severity of the effects and the rapidity with which they have caused or are likely to cause mortality to individuals and accompanying declines in population levels; whether the effects are likely to be permanent; and the extent to which any ongoing conservation efforts reduce the severity of the threat.</P>
                    <P>As used in our priority-ranking system, immediacy of threat is categorized as either “imminent” or “nonimminent” and is based on when the threats will begin. If a threat is currently occurring or likely to occur in the very near future, we classify the threat as imminent. Determining the immediacy of threats helps ensure that species facing actual, identifiable threats are given priority for listing proposals over those for which threats are only potential or species that are intrinsically vulnerable to certain types of threats but are not known to be presently facing such threats.</P>
                    <P>Our priority ranking system has three categories for taxonomic status: Species that are the sole members of a genus; full species (in genera that have more than one species); and subspecies and distinct population segments of vertebrate species (DPS).</P>
                    <P>The result of the ranking system is that we assign each candidate a listing priority number of 1 to 12. For example, if the threat(s) is of high magnitude, with immediacy classified as imminent, the listable entity is assigned an LPN of 1, 2, or 3 based on its taxonomic status (i.e., a species that is the only member of its genus would be assigned to the LPN 1 category, a full species to LPN 2, and a subspecies or DPS would be assigned to LPN 3). In summary, the LPN ranking system provides a basis for making decisions about the relative priority for preparing a proposed rule to list a given species. No matter which LPN we assign to a species, each species included in this notice as a candidate is one for which we have sufficient information to prepare a proposed rule to list it because it is in danger of extinction or likely to become endangered within the foreseeable future throughout all or a significant portion of its range.</P>
                    <P>
                        For more information on the process and standards used in assigning LPNs, a copy of the 1983 guidance is available on our Web site at: 
                        <E T="03">http://www.fws.gov/endangered/esa-library/pdf/48fr43098-43105.pdf.</E>
                         For more information on the LPN assigned to a particular species, the species assessment for each candidate contains the LPN chart and a rationale for the determination of the magnitude and immediacy of threat(s) and assignment of the LPN; that information is summarized in this CNOR.
                    </P>
                    <P>This revised notice supersedes all previous animal, plant, and combined candidate notices of review.</P>
                    <HD SOURCE="HD2">Summary of This CNOR</HD>
                    <P>Since publication of the previous CNOR on November 10, 2010 (75 FR 69222), we reviewed the available information on candidate species to ensure that a proposed listing is justified for each species, and reevaluated the relative LPN assigned to each species. We also evaluated the need to emergency-list any of these species, particularly species with high priorities (i.e., species with LPNs of 1, 2, or 3). This review and reevaluation ensures that we focus conservation efforts on those species at greatest risk first.</P>
                    <P>
                        In addition to reviewing candidate species since publication of the last CNOR, we have worked on numerous findings in response to petitions to list species, and on proposed and final determinations for rules to list species under the ESA. Some of these findings and determinations have been completed and published in the 
                        <E T="04">Federal Register</E>
                        , while work on others is still under way (see 
                        <E T="03">Preclusion and Expeditious Progress,</E>
                         below, for details).
                    </P>
                    <P>
                        Based on our review of the best available scientific and commercial information, with this CNOR we identify 3 new candidate species (see New Candidates, below), change the LPN for 7 candidates (see Listing Priority Changes in Candidates, below) and determine that a listing proposal is not warranted for 3 species and thus remove them from candidate status (see Candidate Removals, below). Combined with the other decisions published separately from this CNOR for individual species that previously were candidates, a total of 244 species (including 104 plant and 140 animal 
                        <PRTPAGE P="66372"/>
                        species) are now candidates awaiting preparation of rules proposing their listing. These 244 species, along with the 48 species currently proposed for listing (includes 4 species proposed for listing due to similarity in appearance), are included in Table 1.
                    </P>
                    <P>Table 2 lists the changes from the previous CNOR, and includes 14 species identified in the previous CNOR as either proposed for listing or classified as candidates that are no longer in those categories. This includes nine species for which we published a final listing rule, one species for which we published an emergency listing rule, one species for which we published a withdrawal of a proposed rule, plus the three species that we have determined do not meet the definition of endangered or threatened and therefore do not warrant listing. We have removed these species from candidate status in this CNOR. Also included in Table 2 are three species for which we published an emergency listing rule due to similarity in appearance; these three species were not previously candidate species.</P>
                    <HD SOURCE="HD1">New Candidates</HD>
                    <P>
                        Below we present a brief summary of one new snail (magnificent ramshorn), one new insect (Poweshiek skipperling), and one new plant candidate (
                        <E T="03">Streptanthus bracteatus</E>
                        ), which are additions to this year's CNOR. Complete information, including references, can be found in the species assessment forms. You may obtain a copy of these forms from the Regional Office having the lead for the species, or from our Web site (
                        <E T="03">http://ecos.fws.gov/tess_public/pub/SpeciesReport.do?listingType=C&amp;mapstatus=1</E>
                        ). For these species, we find that we have on file sufficient information on biological vulnerability and threats to support a proposal to list as endangered or threatened, but that preparation and publication of a proposal is precluded by higher priority listing actions (i.e., it met our definition of a candidate species). We also note below that 18 other species—Pacific walrus, gopher tortoise (eastern population), striped newt, 7 species of Hawaiian yellow-faced bees (
                        <E T="03">Hylaeus anthracinus,</E>
                          
                        <E T="03">H. assimulans,</E>
                          
                        <E T="03">H. facilis,</E>
                          
                        <E T="03">H. hilaris,</E>
                          
                        <E T="03">H. kuakea,</E>
                          
                        <E T="03">H. longiceps,</E>
                         and 
                        <E T="03">H. mana</E>
                        ), Hermes copper butterfly, Mt. Charleston blue butterfly, Puerto Rican harlequin butterfly, 
                        <E T="03">Boechera pusilla</E>
                         (Fremont County rockcress), 
                        <E T="03">Eriogonum soredium</E>
                         (Frisco buckwheat), 
                        <E T="03">Lepidium ostleri</E>
                         (Ostler's peppergrass), 
                        <E T="03">Pinus albicaulis</E>
                         (whitebark pine), 
                        <E T="03">Trifolium friscanum</E>
                         (Frisco clover)—were identified as candidates earlier this year as a result of separate petition findings published in the 
                        <E T="04">Federal Register.</E>
                    </P>
                    <HD SOURCE="HD2">Mammals</HD>
                    <P>
                        Pacific walrus (
                        <E T="03">Odobenus rosmarus divergens</E>
                        )—We previously announced candidate status for this species, and described the reasons and data on which the finding was based, in a separate warranted-but-precluded 12-month petition finding published on February 10, 2011 (76 FR 7634).
                    </P>
                    <HD SOURCE="HD2">Reptiles</HD>
                    <P>
                        Gopher tortoise, eastern population (
                        <E T="03">Gopherus polyphemus</E>
                        )—We previously announced candidate status for this species, and described the reasons and data on which the finding was based, in a separate warranted-but-precluded 12-month petition finding published on July 27, 2011 (76 FR 45130).
                    </P>
                    <HD SOURCE="HD2">Amphibians</HD>
                    <P>
                        Striped newt (
                        <E T="03">Notophthalmus perstriatus</E>
                        )—We previously announced candidate status for this species, and described the reasons and data on which the finding was based, in a separate warranted-but-precluded 12-month petition finding published on June 7, 2011 (76 FR 32911).
                    </P>
                    <HD SOURCE="HD2">Snails</HD>
                    <P>
                        Magnificent ramshorn (
                        <E T="03">Planorbella magnifica</E>
                        )—The following summary is based on information in our files. No new information was provided in the petition received on April 20, 2010 (after we initiated our assessment of this species). The magnificent ramshorn is a freshwater snail in the family Planorbidae (Pilsbry 1903). It is the largest North American snail in this family. The magnificent ramshorn is endemic to the lower Cape Fear River basin, North Carolina. The species has been recorded from only four sites in the lower Cape Fear River Basin in New Hanover and Brunswick Counties, North Carolina, but is believed to be extirpated from all four of these sites. The only known surviving population is a captive population, comprised of approximately 100 adults, being maintained and propagated by a private biologist.
                    </P>
                    <P>Available information indicates that suitable habitat for the species is restricted to relatively shallow, sheltered portions of still or sluggish, freshwater bodies with an abundance and diversity of submerged aquatic vegetation and a circumneutral pH (pH within the range of 6.8-7.5). The only known records for the species are post-1900 and are from manmade millponds constructed in the 1700s to provide a freshwater source for rice agriculture. However, these impoundments closely replicate beaver-pond habitat, and it is plausible that the species was once a faunal component of beaver ponds. The species may also have once inhabited backwater and other sluggish portions of the main channel of lower Cape Fear River.</P>
                    <P>Beaver-pond habitat was eliminated for several decades throughout much of the lower Cape Fear River as a result of the extirpation of the North American beaver due to trapping and hunting during the 19th and early 20th centuries. This, together with draining and destruction of beaver ponds for development, agriculture, and other purposes, is believed to have led to a significant decline in the snail's habitat. Also, dredging and deepening of the Cape Fear River channel, which began as early as 1822, and opening of the Atlantic Intercoastal Waterway (through Snow's Cut) in 1930 for navigational purposes have caused saltwater intrusion, altered the diversity and abundance of aquatic vegetation, and changed flows and current patterns far up the river channel and its lower tributaries. Under these circumstances, the magnificent ramshorn could have survived only in areas of tributary streams not affected by salt water intrusion and other changes, such as the millponds protected from saltwater intrusion by their dams. The species is believed to have been eliminated from the millponds from which it has been recorded due to saltwater intrusion during severe storms (Hurricane Fran) and drought conditions, increased input of nutrients and other pollutants from development activities adversely affecting water quality/chemistry and leading to increased nuisance aquatic plant and algae growth, and efforts, harmful to the snail, by landowners to control nuisance plant and algae growth.</P>
                    <P>
                        While efforts have been made to restore habitat for the magnificent ramshorn at one of the sites known to have previously supported the species, all of the sites known to have previously supported the snail continue to be affected or threatened by most of the same factors (i.e., saltwater intrusion and other water quality degradation, nuisance aquatic plant control, storms, sea level rise, etc.) believed to have resulted in extirpation of the species from the wild. Currently, only a single captive population of the species is known to exist. Although this captive population of the species has been maintained since 1993, a single catastrophic event, such as a severe storm, disease, or predator infestation, affecting this captive population could 
                        <PRTPAGE P="66373"/>
                        result in extinction of the species. Accordingly, the magnitude of the threats to the species' survival is high. The threats are ongoing and therefore imminent. Thus, we have assigned an LPN of 2 to this species.
                    </P>
                    <HD SOURCE="HD2">Insects</HD>
                    <P>
                        Hawaiian yellow-faced bees (
                        <E T="03">Hylaeus anthracinus,</E>
                          
                        <E T="03">H. assimulans,</E>
                          
                        <E T="03">H. facilis,</E>
                          
                        <E T="03">H. hilaris,</E>
                          
                        <E T="03">H. kuakea,</E>
                          
                        <E T="03">H. longiceps,</E>
                         and 
                        <E T="03">H. mana</E>
                        )—We previously announced candidate status for these species, and described the reasons and data on which the finding was based, in a separate warranted-but-precluded 12-month petition finding published on September 6, 2011 (76 FR 55170).
                    </P>
                    <P>
                        Hermes copper butterfly (
                        <E T="03">Hermelycaena</E>
                         [
                        <E T="03">Lycaena</E>
                        ] 
                        <E T="03">hermes</E>
                        )—We previously announced candidate status for this species, and described the reasons and data on which the finding was based, in a separate warranted-but-precluded 12-month petition finding published on April 14, 2011 (76 FR 20918).
                    </P>
                    <P>
                        Mt. Charleston blue butterfly (
                        <E T="03">Plebejus shasta</E>
                          
                        <E T="03">charlestonensis</E>
                        )—We previously announced candidate status for this species, and described the reasons and data on which the finding was based, in a separate warranted-but-precluded 12-month petition finding published on March 8, 2011 (76 FR 12667).
                    </P>
                    <P>
                        Puerto Rican harlequin butterfly (
                        <E T="03">Atlantea tulita</E>
                        )—We previously announced candidate status for this species, and described the reasons and data on which the finding was based, in a separate warranted-but-precluded 12-month petition finding published on May 31, 2011 (76 FR 31282).
                    </P>
                    <P>
                        Poweshiek skipperling (
                        <E T="03">Oarisma poweshiek</E>
                        ) —The following summary is based on information contained in our files. The Poweshiek skipperling is a small butterfly that currently inhabits high-quality tallgrass prairie in Iowa, Minnesota, North Dakota, South Dakota, and Wisconsin and prairie fens in Michigan; it also occurs in the province of Manitoba, Canada. The species is presumed to be extirpated from Illinois and Indiana and from many sites within occupied States.
                    </P>
                    <P>The Poweshiek skipperling is threatened by degradation of its native prairie habitat by overgrazing, invasive species, gravel mining, and herbicide applications; inbreeding, population isolation, and prescribed fire threaten some populations. Prairie succeeds to shrubland or forest without periodic fire, grazing, or mowing; thus, the species is also threatened at sites where such disturbances are not applied. The Service, State agencies, the Sisseton-Wahpeton Sioux Tribe, and private organizations (e.g., The Nature Conservancy) protect and manage some Poweshiek skipperling sites. Careful and considered management is always necessary to ensure its persistence, even at protected sites. The species may be secure at a few sites where public and private landowners manage native prairie in ways that conserve Poweshiek skipperling, but approximately one-quarter of the inhabited sites are privately owned with little or no protection. A few private sites are protected from conversion by easements, but these do not preclude adverse effects from overgrazing. The threats are such that the Poweshiek skipperling warrants listing; the threats are high in magnitude because habitat degradation and other stressors has resulted in sharp declines in the western portion of its range which contains more than 90 percent of the species site records. We assigned this species an LPN of 2 to reflect the ongoing, and therefore, imminent threats to the species' habitat and sharp population declines documented recently, especially in Iowa and Minnesota.</P>
                    <HD SOURCE="HD2">Flowering Plants</HD>
                    <P>
                        <E T="03">Boechera pusilla</E>
                         (Fremont County rockcress) —We previously announced candidate status for this species, and described the reasons and data on which the finding was based, in a separate warranted-but-precluded 12-month petition finding published on June 9, 2011 (76 FR 33924).
                    </P>
                    <P>
                        <E T="03">Eriogonum soredium</E>
                         (Frisco buckwheat)—We previously announced candidate status for this species, and described the reasons and data on which the finding was based, in a separate warranted-but-precluded 12-month petition finding published on February 23, 2011 (76 FR 10166).
                    </P>
                    <P>
                        <E T="03">Lepidium ostleri</E>
                         (Ostler's peppergrass)—We previously announced candidate status for this species, and described the reasons and data on which the finding was based, in a separate warranted-but-precluded 12-month petition finding published on February 23, 2011 (76 FR 10166).
                    </P>
                    <P>
                        <E T="03">Pinus albicaulis</E>
                         (whitebark pine)—We previously announced candidate status for this species, and described the reasons and data on which the finding was based, in a separate warranted-but-precluded 12-month petition finding published on July 19, 2011 (76 FR 42631).
                    </P>
                    <P>
                        <E T="03">Streptanthus bracteatus</E>
                         (bracted twistflower)—The following summary is based on information obtained from our files, on-line herbarium databases, surveys and monitoring data, seed-collection data, and scientific publications. Bracted twistflower, an annual herbaceous plant of the Brassicaceae (mustard family), is endemic to a small portion of the Edwards Plateau of Texas. From 1989 to 2010, 32 populations have been documented in five counties; of these, 15 populations remain with intact habitat, 9 persist in degraded or partially destroyed habitats, and 8 are presumed extirpated. Only 9 of the intact populations occur in protected natural areas.
                    </P>
                    <P>The continued survival of bracted twistflower is imminently threatened by habitat destruction from urban development, severe herbivory from very dense herds of white-tailed deer, and the increased density of woody plant cover. Additional ongoing threats include erosion and trampling from foot and mountain-bike trails, a pathogenic fungus of unknown origin, and insufficient protection by existing regulations. Furthermore, due to the small size and isolation of remaining populations and lack of gene flow between them, several populations are now inbred and may have insufficient genetic diversity for long-term survival. The consistent failure of pilot reintroduction efforts has so far prevented the augmentation and reintroduction of populations in protected, managed sites. Optimal vegetation management of bracted twistflower populations may be incompatible with the management of golden-cheeked warbler nesting habitat. The species is potentially threatened by as-yet unknown impacts of climate change. The Service has established a voluntary Memorandum of Agreement with Texas Parks and Wildlife Department, the City of Austin, Travis County, the Lower Colorado River Authority, and the Lady Bird Johnson Wildflower Center to protect bracted twistflower and its habitats on tracts of Balcones Canyonlands Preserve. The threats to bracted twistflower are of moderate magnitude, and are ongoing and, therefore, imminent. We find that bracted twistflower is warranted for listing throughout all of its range and assigned it an LPN of 8.</P>
                    <P>
                        <E T="03">Trifolium friscanum</E>
                         (Frisco clover)— We previously announced candidate status for this species, and described the reasons and data on which the finding was based, in a separate warranted-but-precluded 12-month petition finding published on February 23, 2011 (76 FR 10166).
                        <PRTPAGE P="66374"/>
                    </P>
                    <HD SOURCE="HD1">Listing Priority Changes in Candidates</HD>
                    <P>We reviewed the LPN for all candidate species and are changing the numbers for the following species discussed below. Some of the changes reflect actual changes in either the magnitude or immediacy of the threats. For some species, the LPN change reflects efforts to ensure national consistency as well as closer adherence to the 1983 guidelines in assigning these numbers, rather than an actual change in the nature of the threats.</P>
                    <HD SOURCE="HD2">Birds</HD>
                    <P>
                        Kittlitz's murrelet (
                        <E T="03">Brachyramphus brevirostris</E>
                        )—The following summary is based on information contained in our files and the petition we received on May 9, 2001. Kittlitz's murrelet is a small diving seabird that inhabits Alaskan coastal waters discontinuously, from Point Lay south to northern portions of southeast Alaska, west to the tip of the Aleutian Islands, and the eastern coastline of Russia. During the breeding season, most Kittlitz's murrelets are associated with tidewater glaciers, but breeding has also been documented throughout their range in areas where glaciers no longer exist. We concluded in the past that the loss of tidewater glaciers was a threat to the species and the magnitude of that threat was high because of the rate of change in the glaciers. There is no doubt that tidewater glaciers are receding most likely due to climate change. It is also clear that in one part of their range, Kittlitz's murrelets are associated with glacially influenced waters during the summer breeding period. What is unclear is the nature of the association and if these areas are more important to the Kittlitz's murrelet's population viability than other areas. Nests have been documented throughout their range; what is unknown is if nest survival is better near glaciers. Although we know that Kittlitz's murrelet habitat will continue to be modified as glaciers continue to recede, we currently do not have evidence that this modification will lead to conditions that will lead to a population-level decline.
                    </P>
                    <P>In the past we had a high level of concern over the population decline and its magnitude. Although we still conclude that the population has declined, based on ongoing analyses, the magnitude of the decline is much less certain. Work is currently underway to evaluate past surveys and the status and trend of Kittlitz's murrelet across its range. We anticipate that our ability to evaluate trends and population size will be greatly improved when these projects are completed and published.</P>
                    <P>Based on new information, the focus of our concern has shifted to the low reproductive success of Kittlitz's murrelet. Our concern is based on three lines of reasoning: at the locations where we have the most complete information, Agattu and Kodiak Islands, nest success is very low (less than 10 percent); few juvenile birds have been documented; and there are indications that few females (approximately 10 percent) are breeding in spite of the fact (based on blood chemistry) that approximately 90 percent appear to be physiologically prepared to breed. Although the implications of these results are serious, we must temper our concern with the knowledge that the results are limited to small parts of the murrelet's range and for a long-lived bird, we have data for relatively few years. Consequently, we conclude that the magnitude of this threat is moderate.</P>
                    <P>For a K-selected species such as Kittlitz's murrelet, loss of the adults is particularly important, and we have identified several sources of adult mortality such as hydrocarbon contamination, entanglement in gillnets, and predation. Although none of these sources of mortality alone rises to the level of a threat, in total, the chronic, low-level loss of adults, in combination with evidence that a small proportion of the population is breeding, and the low reproductive success lead us to conclude that it will be difficult for this species to maintain a stable population level or rebound from a stochastic event that causes population loss. The magnitude of threat from these sources is low to moderate, depending on events that occur in a given year (number and location of oil spills/ship wrecks, number and location of gillnets).</P>
                    <P>For these reasons, this year, our focus shifted from the loss of glaciers to poor reproductive success. Poor nest success (as opposed to adult mortality) could be the underlying reason for the population decline, and if it is occurring rangewide, the population would be expected to continue to decline. Currently, our most detailed nest information comes from Agattu and Kodiak Islands. Whether these locations and the timeframe observed are representative of the rangewide situation is unknown; therefore, we have determined that threat magnitude is moderate, not high. Because the identified threats are currently occurring, they are imminent. Thus, we are changing the LPN from a 2 to an 8.</P>
                    <P>
                        Sprague's pipit (
                        <E T="03">Anthus spragueii</E>
                        )—The following summary is based on information contained in our files and in the petition we received on October 15, 2008. This species occurs in Arizona, Colorado, Kansas, Louisiana, Minnesota, Montana, Nebraska, New Mexico, North Dakota, Oklahoma, South Dakota, Texas, Canada, and Mexico. The Sprague's pipit is a small grassland bird characterized by its high flight display and otherwise very secretive behavior. Sprague's pipits are strongly tied to native prairie (land which has never been plowed) throughout their life cycle.
                    </P>
                    <P>Threats to this species include: Habitat loss and conversion, habitat fragmentation on the breeding grounds, energy development, roads, and inadequacy of existing regulatory mechanisms. Only 15 to 18 percent of the historical breeding habitat in the United States remains due to prairie habitat loss and fragmentation. The Breeding Bird Survey and Christmas Bird Count both show a 40-year decline of 73 to 79 percent (3.23 to 4.1 percent annually). We anticipate that prairie habitat will continue to be converted and fragmented. Most of the breeding range, including those areas where grassland habitat still remains, has been identified as a prime area for wind energy development, and an oil and gas boom is occurring in the central part of the breeding range in the United States and Canada. On the wintering range, conversion of grassland to agriculture and other uses appears to be accelerating. We recently announced candidate status for Sprague's pipit in a warranted-but-precluded 12-month petition finding published on September 15, 2010 (75 FR 56028). Because of an error in our original GIS analysis of the magnitude of the threats (as presented in our 12-month finding), we have now determined that the magnitude of threats is moderate as a smaller area of the range is affected by the threats, thereby reducing the effect of the threats to a lower level. Thus, we are changing the LPN of the Sprague's pipit from a 2 to an 8.</P>
                    <HD SOURCE="HD2">Reptiles</HD>
                    <P>
                        Eastern massasauga rattlesnake (
                        <E T="03">Sistrurus catenatus</E>
                        )—Until 2011, the eastern massasauga was considered one of three recognized subspecies of massasauga. Recent information indicates that the eastern massasauga represents a distinct species, and we recognize it as such beginning in 2011. It is a small, thick-bodied rattlesnake that occupies shallow wetlands and adjacent upland habitat in portions of Illinois, Indiana, Iowa, Michigan, Minnesota, New York, Ohio, Pennsylvania, Wisconsin, and Ontario. Populations in Missouri, formerly included within the previously recognized subspecies of eastern 
                        <PRTPAGE P="66375"/>
                        massasauga, are now considered to be the western massasauga, 
                        <E T="03">Sistrurus tergeminus tergeminus.</E>
                    </P>
                    <P>
                        Although the current range of 
                        <E T="03">S. catenatus</E>
                         resembles the species' historical range, the geographic distribution has been restricted by the loss of the species from much of the area within the boundaries of that range. Approximately 40 percent of the counties that were historically occupied by 
                        <E T="03">S. catenatus</E>
                         no longer support the species. 
                        <E T="03">Sistrurus catenatus</E>
                         is currently listed as endangered in every State and province in which it occurs, except for Michigan where it is designated as a species of special concern. Each State and Canadian province across the range of 
                        <E T="03">S. catenatus</E>
                         has lost more than 30 percent, and for the majority more than 50 percent, of their historical populations. Furthermore, less than 35 percent of the remaining populations are considered secure. Approximately 59 percent of the remaining 
                        <E T="03">S. catenatus</E>
                         populations occur wholly or in part on public land, and Statewide and site-specific Candidate Conservation Agreements with Assurances (CCAAs) are currently being developed for many of these areas in Iowa, Illinois, Michigan, and Wisconsin. In 2004, a Candidate Conservation Agreement (CCA) with the Lake County Forest Preserve District in Illinois was completed. In 2005, a CCA with the Forest Preserve District of Cook County in Illinois was completed. In 2006, a CCAA with the Ohio Department of Natural Resources Division of Natural Areas and Preserves was completed for Rome State Nature Preserve in Ashtabula County.
                    </P>
                    <P>The magnitude of threats is moderate at this time. However, a recently completed extinction risk model, and information provided by species experts, indicates that other populations are likely to suffer additional losses in abundance and genetic diversity and some will likely be extirpated unless threats are removed in the near future. Declines have continued or may be accelerating in several States. Thus, we are monitoring the status of this species to determine if a change in listing priority is warranted. Threats of habitat modification, habitat succession, incompatible land management practices, illegal collection for the pet trade, and human persecution are ongoing and imminent threats to many remaining populations, particularly those inhabiting private lands. We do not believe emergency listing is warranted. We are changing the LPN from a 9 to an 8, reflecting the recent information indicating that this snake should be recognized as a species rather than a subspecies.</P>
                    <HD SOURCE="HD2">Amphibians</HD>
                    <P>
                        Relict leopard frog (
                        <E T="03">Lithobates onca</E>
                        ) (formerly in 
                        <E T="03">Rana</E>
                        )—The following summary is based on information contained in our files. Natural relict leopard frog populations occur in two general areas in Nevada: near the Overton Arm area of Lake Mead and Black Canyon below Lake Mead. These two areas include a small fraction of the historical distribution of the species. Its historical range included springs, streams, and wetlands within the Virgin River drainage downstream from the vicinity of Hurricane, Utah; along the Muddy River, Nevada; and along the Colorado River from its confluence with the Virgin River downstream to Black Canyon below Lake Mead, Nevada and Arizona.
                    </P>
                    <P>Factors contributing to the decline of the species include alteration, loss, and degradation of aquatic habitat due to water developments and impoundments, and scouring and erosion; changes in plant communities that result in dense growth and the prevalence of vegetation; introduced predators; climate change; and stochastic events. The presence of chytrid fungus in relict leopard frogs at Lower Blue Point Spring in 2010 warrants further evaluation of the threat of disease to the relict leopard frog. The size of natural and translocated populations is small, and therefore these populations are vulnerable to stochastic events, such as floods and wildfire. Climate change that results in reduced spring flow, habitat loss, and increased prevalence of wildfire would adversely affect relict leopard frog populations.</P>
                    <P>In 2005, the National Park Service, in cooperation with the Fish and Wildlife Service and other Federal, State, and local partners, developed a conservation agreement and strategy intended to improve the status of the species through prescribed management actions and protection. Conservation actions identified in the agreement and strategy include captive rearing of tadpoles for translocation and refugium populations, habitat and natural history studies, habitat enhancement, population and habitat monitoring, and translocation. New sites within the historical range of the species have been successfully established with captive-reared frogs. Conservation is proceeding under the agreement and strategy; however, additional time is needed to determine whether or not the agreement and strategy will be effective in eliminating or reducing the threats to the point that the relict leopard frog can be removed from candidate status. In consideration of these conservation efforts and the overall threat level to the species, we determined the magnitude of existing threats is moderate to low. However, because water development and other habitat effects, presence of introduced predators, presence of chytrid fungus, limited distribution, small population size, and climate change are ongoing or will occur in the near future, the threats are imminent. The discovery of chytrid fungus in relict leopard frogs in 2010 is a new and potentially serious threat. Therefore, we changed the LPN from an 11 to an 8 for this species.</P>
                    <HD SOURCE="HD2">Snails</HD>
                    <P>
                        Huachuca springsnail (
                        <E T="03">Pyrgulopsis thompsoni</E>
                        )—The following is based on information contained in our files. No new information was provided in the petition received on May 11, 2004. The Huachuca springsnail inhabits approximately 19 springs in southeastern Arizona and two springs in Sonora, Mexico. The springsnail is typically found in shallow water habitats, often in rocky seeps at the spring source. Potential threats include habitat modification and destruction through catastrophic wildfire and unmanaged grazing. Overall, the threats are low in magnitude because threats are not occurring throughout the range of the species uniformly and not all populations would likely be affected simultaneously by the known threats. The available information indicates that threats are not currently ongoing in or adjacent to occupied habitats. Accordingly, threats are nonimminent. Therefore, we are reducing the LPN from an 8 to an 11 for this species.
                    </P>
                    <HD SOURCE="HD2">Insects</HD>
                    <P>
                        Meltwater lednian stonefly (
                        <E T="03">Lednia tumana</E>
                        )—The following summary is based on information contained in our files and in the petition we received on July 30, 2007. This species is an aquatic insect in the order Plecoptera (stoneflies). Stoneflies are primarily associated with clean, cool streams and rivers. Eggs and nymphs (juveniles) of the meltwater lednian stonefly are found in high-elevation, alpine, and subalpine streams, most typically in locations closely linked to glacial runoff. The species is generally restricted to streams with mean summer water temperature less than 10 °C (50 °F). Adults emerge from the nymph stage and mate in streamside vegetation. The only known meltwater lednian stonefly occurrences are within Glacier National Park (NP), Montana. Climate change, and the associated effects of glacier loss (with glaciers predicted to 
                        <PRTPAGE P="66376"/>
                        be gone by 2030), reduced streamflows, and increased water temperatures, is expected to significantly reduce the occurrence of populations and extent of suitable habitat for the species in Glacier NP. In addition, the existing regulatory mechanisms do not address environmental changes due to global climate change. We recently announced candidate status for the meltwater lednian stonefly in a warranted-but-precluded 12-month petition finding published on April 5, 2011 (76 FR 18684). We originally assigned the species an LPN of 4 based on three criteria: (1) The high magnitude of threat, which is projected to substantially reduce the amount of suitable habitat relative to the species' current range; (2) the low imminence of the threat based on the lack of documented evidence that populations are being affected by climate change now; and (3) the taxonomic status of the species, which was the only described member of its genus (monotypic taxon). Recently, stonefly specimens discovered in Mount Rainier NP, North Cascades NP, and in the Sierra Nevada Mountains of California have been formally described as two additional species in the 
                        <E T="03">Lednia</E>
                         genus—
                        <E T="03">L. borealis</E>
                         and 
                        <E T="03">L. sierra</E>
                        —which indicates that the meltwater lednian stonefly is no longer in a monotypic genus. Based on this new taxonomic information, we are changing the LPN of this species from a 4 to a 5.
                    </P>
                    <HD SOURCE="HD2">Arachnids</HD>
                    <P>
                        Warton's cave meshweaver (
                        <E T="03">Cicurina wartoni</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition received on May 11, 2004. Warton's Cave meshweaver is an eyeless, cave-dwelling, unpigmented, 0.23-inch-long invertebrate known only from female specimens. This meshweaver is known to occur in only one cave (Pickle Pit) in Travis County, Texas. Primary threats to the species and its habitat are predation and competition from red-imported fire ants, surface and subsurface effects from polluted runoff from an adjacent subdivision, unauthorized entry into the area surrounding the cave, and trash dumping that may include toxic materials near the feature. The magnitude of threats is low to moderate based on observations made during an April 5, 2011, site visit. In addition, Pickle Pit occurs in a preserve established for mitigation for the endangered golden-cheeked warbler; hence the meshweaver receives some protection. Due to a reduction in the magnitude of threats, we changed the LPN for this species from a 2 to an 8.
                    </P>
                    <HD SOURCE="HD1">Candidate Removals</HD>
                    <P>As summarized below, we have evaluated the threats to the following species and considered factors that, individually and in combination, currently or potentially could pose a risk to these species and their habitats. After a review of the best available scientific and commercial data, we conclude that listing these species under the Endangered Species Act is not warranted because these species are not likely to become an endangered species within the foreseeable future throughout all or a significant portion of their ranges. Therefore, we find that proposing a rule to list them is not warranted, and we no longer consider them to be candidate species for listing. We will continue to monitor the status of these species and to accept additional information and comments concerning this finding. We will reconsider our determination in the event that new information indicates that the threats to the species are of a considerably greater magnitude or imminence than identified through assessments of information contained in our files, as summarized here.</P>
                    <HD SOURCE="HD2">Snails</HD>
                    <P>
                        Gila springsnail (
                        <E T="03">Pyrgulopsis gilae</E>
                        )—The following summary is based on information contained in our files and the petition we received on November 20, 1985. Also see our 12-month petition finding published in the 
                        <E T="04">Federal Register</E>
                         on October 4, 1988 (53 FR 38969). The Gila springsnail is an aquatic species previously known from 13 populations in New Mexico. Surveys conducted in 2008 and 2009 located 37 additional populations, bringing the known total to 50.
                    </P>
                    <P>The long-term persistence of the Gila springsnail is contingent upon protection of the riparian corridor and maintenance of flow to ensure continuous, oxygenated, flowing water within the species' required thermal range. Based on new information, we now foresee no threats to the habitat of the Gila springsnail. Disturbance to the species from recreational activity is occurring rarely, with minimal effects to the species, and is not likely to become a threat in the foreseeable future due to the inaccessibility of the springsnail populations. Livestock grazing may have affected Gila springsnails in the past, but exclusion of livestock from the riparian habitat has removed this threat. Current springsnail populations are located in areas with minimal fire or flood risk. Groundwater use for geothermal development is unlikely to occur within Gila springsnail habitat. Additionally, the discovery of additional populations in 2008 and 2009 reveals the species is secure from stochastic, habitat-modifying events.</P>
                    <P>The distribution of the species and variance in the location of its habitat reduces the risk of the loss of the species from stochastic, habitat-modifying events. We have no indication that collection of the species is occurring, other than rarely by researchers confirming its discovery at new springs. Also, as the Gila springsnail occurs on Forest Service land with limited access, we do not anticipate any future collections for other purposes. There are no known diseases that affect Gila springsnails, and no native or nonnative predators occur at these springs. Additionally, we are not aware of any introduced species at the springs that would affect the springsnails.</P>
                    <P>The effects of future climate change may serve to exacerbate habitat loss from other factors. However, as we have determined that the Gila springsnail is not threatened with habitat loss, we cannot predict with any certainty that the effects of climate change will exacerbate any future habitat concerns sufficiently to consider climate change, on its own, a threat to the species. Therefore, we have determined that climate change is not currently a threat to the Gila springsnail now or in the foreseeable future. In conclusion, due to the lack of threats to the continued existence of the Gila springsnail under any of the five factors now or in the foreseeable future, we find that the Gila springsnail does not meet the definition of a threatened or endangered species and no longer warrants listing throughout all or a significant portion of its range, and we removed it from the candidate list.</P>
                    <P>
                        New Mexico springsnail (
                        <E T="03">Pyrgulopsis thermalis</E>
                        )—The following summary is based on information contained in our files and the petition received on November 20, 1985. Also see our 12-month petition finding published on October 4, 1988 (53 FR 38969). The New Mexico springsnail is an aquatic species that was previously known from only two separate populations associated with a series of spring-brook systems along the Gila River in the Gila National Forest in Grant County, New Mexico. Subsequent surveys in 2008 and 2009 discovered 12 additional populations, for a total of 14 separate populations.
                    </P>
                    <P>
                        The long-term persistence of the New Mexico springsnail is contingent upon protection of the riparian corridor and maintenance of flow to ensure 
                        <PRTPAGE P="66377"/>
                        continuous, oxygenated, flowing water within the species' required thermal range. Based on new information, we now foresee no threats to the habitat of the New Mexico springsnail. Disturbance to the species from recreational activity is occurring rarely, with minimal impacts to the species, and is not likely to become a threat in the foreseeable future due to the inaccessibility of the springsnail populations. Livestock grazing may have affected New Mexico springsnails in the past, but exclusion of livestock from the riparian habitat has removed this threat. Current springsnail populations are located in areas with minimal fire or flood risk. Groundwater use for geothermal development is unlikely to occur within New Mexico springsnail habitat. Additionally, the discovery of additional populations in 2008 and 2009 reveals the species is secure from stochastic, habitat-modifying events.
                    </P>
                    <P>The distribution of the species and variance in the location of its habitat reduces the risk of the loss of the species from stochastic, habitat-modifying events. We have no indication that collection of the species is occurring, other than rarely by researchers confirming its discovery at new springs. Also, as the New Mexico springsnail occurs on Forest Service land with limited access, we do not anticipate any future collections for other purposes. There are no known diseases that affect New Mexico springsnails, and no native or nonnative predators occur at these springs. Additionally, we are not aware of any introduced species at the springs that would affect the springsnails.</P>
                    <P>The effects of future climate change may serve to exacerbate habitat loss from other factors. However, as we have determined that the New Mexico springsnail is not threatened with habitat loss, we cannot predict with any certainty that the effects of climate change will exacerbate any future habitat concerns sufficiently to consider climate change, on its own, a threat to the species. Therefore, we have determined that climate change is not currently a threat to the New Mexico springsnail now or in the foreseeable future.</P>
                    <P>In conclusion, due to the lack of threats to the continued existence of the New Mexico springsnail under any of the five factors now or in the foreseeable future, we find that the New Mexico springsnail does not meet the definition of a threatened or endangered species and no longer warrants listing throughout all or a significant portion of its range. As a result, we have removed it from the candidate list.</P>
                    <HD SOURCE="HD2">Insects</HD>
                    <P>
                        Wekiu bug (
                        <E T="03">Nysius wekiuicola</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The wekiu bug belongs to the true bug family, Lygaeidae, and occurs only on the summit of Mauna Kea on the island of Hawaii. The wekiu bug was believed to be limited in range to six pu'us (cinder cones) in the summit area and was threatened by loss of habitat on Mauna Kea due to development of observatory facilities, which was believed to be causing a severe decline in its numbers. Surveys and other studies carried out over the last 11 years suggest the wekiu bug has a broader distribution on Mauna Kea than previously known. Surveys now indicate that the wekiu bug is currently found on 16 pu'us. Two of these 16 pu'us occur in an area that has undergone development of astronomy observatory facilities. The previous trend toward loss of habitat due to observatory construction has been curtailed, and no new construction, including the currently planned Thirty-meter Telescope project, will occur on any pu'u occupied by the species. Management of the Mauna Kea summit area by the Office of Mauna Kea Management includes continued monitoring of the wekiu bug and its habitat, and scientific studies to assist in managing and protecting wekiu bug populations and habitat. The 2000 Mauna Kea Science Reserve Management Plan, the Mauna Kea Comprehensive Management Plan, the four subplans (natural resources management plan, cultural resources management plan, decommissioning plan, and public access plan), and a procedure for formal review of new projects on Mauna Kea all contribute to the protection and conservation of the wekiu bug.
                    </P>
                    <P>Studies over the last 11 years also indicate the wekiu bug has a stable population, and demonstrate that this species exhibits extreme variability in terms of annual densities at any given site, such that the normal bounds of natural population variance for this species are much wider than previously understood. Based on our review of the best available information we no longer conclude that threats across the wekiu bug's expanded range put the species in danger of extinction. In summary, because the wekiu bug is likely stable in numbers, the wekiu bug is more widespread than previously believed, current threats are minimized and restricted within the larger range of the species, and future potential threats are monitored, we find the wekiu bug does not meet the definition of a threatened or endangered species and no longer warrants listing throughout all or a significant portion of its range. Thus, we have removed it from candidate status.</P>
                    <HD SOURCE="HD1">Petition Findings</HD>
                    <P>The ESA provides two mechanisms for considering species for listing. One method allows the Secretary, on his own initiative, to identify species for listing under the standards of section 4(a)(1). We implement this through the candidate program, discussed above. The second method for listing a species provides a mechanism for the public to petition us to add a species to the Lists. The CNOR serves several purposes as part of the petition process: (1) In some instances (in particular, for petitions to list species that the Service has already identified as candidates on its own initiative), it serves as the petition finding; (2) it serves as a “resubmitted” petition finding that the ESA requires the Service to make each year; and (3) it documents the Service's compliance with the statutory requirement to monitor the status of species for which listing is warranted-but-precluded to ascertain if they need emergency listing.</P>
                    <P>First, the CNOR serves as a petition finding in some instances. Under section 4(b)(3)(A), when we receive a listing petition, we must determine within 90 days, to the maximum extent practicable, whether the petition presents substantial information indicating that listing may be warranted (a “90-day finding”). If we make a positive 90-day finding, we must promptly commence a status review of the species under section 4(b)(3)(A); we must then make and publish one of three possible findings within 12 months of the receipt of the petition (a “12-month finding”):</P>
                    <P>(1) The petitioned action is not warranted;</P>
                    <P>(2) The petitioned action is warranted (in which case we are required to promptly publish a proposed regulation to implement the petitioned action; once we publish a proposed rule for a species, section 4(b)(5) and 4(b)(6) govern further procedures regardless of whether we issued the proposal in response to a petition); or</P>
                    <P>
                        (3) The petitioned action is warranted but (a) the immediate proposal of a regulation and final promulgation of a regulation implementing the petitioned action is precluded by pending proposals to determine whether any species is endangered or threatened, and 
                        <PRTPAGE P="66378"/>
                        (b) expeditious progress is being made to add qualified species to the Lists of Endangered or Threatened Wildlife and Plants. (We refer to this third option as a “warranted-but-precluded finding.”).
                    </P>
                    <P>We define “candidate species” to mean those species for which the Service has on file sufficient information on biological vulnerability and threat(s) to support issuance of a proposed rule to list, but for which issuance of the proposed rule is precluded (61 FR 64481; December 5, 1996). This standard for making a species a candidate through our own initiative is identical to the standard for making a warranted-but-precluded 12-month petition finding on a petition to list, and we add all petitioned species for which we have made a warranted-but-precluded 12-month finding to the candidate list.</P>
                    <P>
                        Therefore, all candidate species identified through our own initiative already have received the equivalent of substantial 90-day and warranted-but-precluded 12-month findings. Nevertheless, we review the status of the newly petitioned candidate species and through this CNOR publish specific section 4(b)(3) findings (i.e., substantial 90-day and warranted-but-precluded 12-month findings) in response to the petitions to list these candidate species. We publish these findings as part of the first CNOR following receipt of the petition. On April 20, 2010, we received a petition to list the magnificent ramshorn (see summary above under New Candidates) after we had initiated our assessment of this species for candidate status. In addition, the following species that were already on our candidate list were also included in this petition: Black Warrior waterdog, sicklefin redhorse, rabbitsfoot, black mudalia, Coleman cave beetle, and 
                        <E T="03">Solidago plumosa</E>
                         (Yadkin River goldenrod). The petition did not provide any new information on these species. We published a separate substantial 90-day finding for all of the above species on September 27, 2011 (76 FR 59836). As part of this notice, we are making the warranted-but-precluded 12-month finding for these species. We have identified the candidate species for which we received petitions by the code “C*” in the category column on the left side of Table 1 below.
                    </P>
                    <P>Second, the CNOR serves as a “resubmitted” petition finding. Section 4(b)(3)(C)(i) of the ESA requires that when we make a warranted-but-precluded finding on a petition, we are to treat such a petition as one that is resubmitted on the date of such a finding. Thus, we must make a 12-month petition finding in compliance with section 4(b)(3)(B) of the ESA at least once a year, until we publish a proposal to list the species or make a final not-warranted finding. We make these annual findings for petitioned candidate species through the CNOR.</P>
                    <P>Third, through undertaking the analysis required to complete the CNOR, the Service determines if any candidate species needs emergency listing. Section 4(b)(3)(C)(iii) of the ESA requires us to “implement a system to monitor effectively the status of all species” for which we have made a warranted-but-precluded 12-month finding, and to “make prompt use of the [emergency listing] authority [under section 4(b)(7)] to prevent a significant risk to the well being of any such species.” The CNOR plays a crucial role in the monitoring system that we have implemented for all candidate species by providing notice that we are actively seeking information regarding the status of those species. We review all new information on candidate species as it becomes available, prepare an annual species assessment form that reflects monitoring results and other new information, and identify any species for which emergency listing may be appropriate. If we determine that emergency listing is appropriate for any candidate we will make prompt use of the emergency listing authority under section 4(b)(7). For example, on August 10, 2011, we emergency listed the Miami blue butterfly (76 FR 49542). We have been reviewing and will continue to review, at least annually, the status of every candidate, whether or not we have received a petition to list it. Thus, the CNOR and accompanying species assessment forms constitute the Service's annual finding on the status of petitioned species under section 4(b)(3)(C)(i) of the ESA.</P>
                    <P>A number of court decisions have elaborated on the nature and specificity of information that must be considered in making and describing the petition findings in the CNOR. The CNOR published on November 9, 2009 (74 FR 57804), describes these court decisions in further detail. As with previous CNORs, we continue to incorporate information of the nature and specificity required by the courts. For example, we include a description of the reasons why the listing of every petitioned candidate species is both warranted and precluded at this time. We make our determinations of preclusion on a nationwide basis to ensure that the species most in need of listing will be addressed first and also because we allocate our listing budget on a nationwide basis (see below). Regional priorities can also be discerned from Table 1, below, which includes the lead region and the LPN for each species. Our preclusion determinations are further based upon our budget for listing activities for unlisted species only, and we explain the priority system and why the work we have accomplished does preclude action on listing candidate species.</P>
                    <P>In preparing this CNOR, we reviewed the current status of, and threats to, the 204 candidates and 5 listed species for which we have received a petition and for which we have found listing or reclassification from threatened to endangered to be warranted but precluded. Included in this work is our review of the current status of, and threats to, the Canada lynx in New Mexico for which we received a petition to add that State to the listed range. We find that the immediate issuance of a proposed rule and timely promulgation of a final rule for each of these species has been, for the preceding months, and continues to be, precluded by higher priority listing actions. Additional information that is the basis for this finding is found in the species assessments and our administrative record for each species.</P>
                    <P>Our review included updating the status of, and threats to, petitioned candidate or listed species for which we published findings, under section 4(b)(3)(B) of the ESA, in the previous CNOR. We have incorporated new information we gathered since the prior finding and, as a result of this review, we are making continued warranted-but-precluded 12-month findings on the petitions for these species.</P>
                    <P>The immediate publication of proposed rules to list these species was precluded by our work on higher priority listing actions, listed below, during the period from October 1, 2010, through September 30, 2011. We will continue to monitor the status of all candidate species, including petitioned species, as new information becomes available to determine if a change in status is warranted, including the need to emergency-list a species under section 4(b)(7) of the ESA.</P>
                    <P>
                        In addition to identifying petitioned candidate species in Table 1 below, we also present brief summaries of why each of these candidates warrants listing. More complete information, including references, is found in the species assessment forms. You may obtain a copy of these forms from the Regional Office having the lead for the species, or from the Fish and Wildlife Service's Internet Web site: 
                        <E T="03">http://ecos.fws.gov/tess_public/pub/SpeciesReport.do?listingType=C&amp;mapstatus=1.</E>
                         As described above, under section 4 of 
                        <PRTPAGE P="66379"/>
                        the ESA, we may identify and propose species for listing based on the factors identified in section 4(a)(1), and section 4 also provides a mechanism for the public to petition us to add species to the Lists of Endangered or Threatened Wildlife and Plants under the ESA. Below we describe the actions that continue to preclude the immediate proposal and final promulgation of a regulation implementing each of the petitioned actions for which we have made a warranted-but-precluded finding, and we describe the expeditious progress we are making to add qualified species to, and remove species from, the Lists of Endangered or Threatened Wildlife and Plants.
                    </P>
                    <HD SOURCE="HD2">Preclusion and Expeditious Progress</HD>
                    <P>Preclusion is a function of the listing priority of a species in relation to the resources that are available and the cost and relative priority of competing demands for those resources. Thus, in any given fiscal year (FY), multiple factors dictate whether it will be possible to undertake work on a listing proposal regulation or whether promulgation of such a proposal is precluded by higher priority listing actions.</P>
                    <P>The resources available for listing actions are determined through the annual Congressional appropriations process. The appropriation for the Listing Program is available to support work involving the following listing actions: Proposed and final listing rules; 90-day and 12-month findings on petitions to add species to the Lists of Endangered and Threatened Wildlife and Plants (Lists) or to change the status of a species from threatened to endangered; annual “resubmitted” petition findings on prior warranted-but-precluded petition findings as required under section 4(b)(3)(C)(i) of the ESA; critical habitat petition findings; proposed and final rules designating critical habitat; and litigation-related, administrative, and program-management functions (including preparing and allocating budgets, responding to Congressional and public inquiries, and conducting public outreach regarding listing and critical habitat). The work involved in preparing various listing documents can be extensive, and may include, but is not limited to: Gathering and assessing the best scientific and commercial data available and conducting analyses used as the basis for our decisions; writing and publishing documents; and obtaining, reviewing, and evaluating public comments and peer-review comments on proposed rules and incorporating relevant information into final rules. The number of listing actions that we can undertake in a given year also is influenced by the complexity of those listing actions; that is, more complex actions generally are more costly. The median cost for preparing and publishing a 90-day finding is $39,276; for a 12-month finding, $100,690; for a proposed rule with critical habitat, $345,000; and for a final listing rule with critical habitat, $305,000.</P>
                    <P>We cannot spend more than is appropriated for the Listing Program without violating the Anti-Deficiency Act (see 31 U.S.C. 1341(a)(1)(A)). In addition, in FY 1998 and for each fiscal year since then, Congress has placed a statutory cap on funds which may be expended for the Listing Program, equal to the amount expressly appropriated for that purpose in that fiscal year. This cap was designed to prevent funds appropriated for other functions under the ESA (for example, recovery funds for removing species from the Lists), or for other Service programs, from being used for Listing Program actions (see House Report 105-163, 105th Congress, 1st Session, July 1, 1997).</P>
                    <P>Since FY 2002, the Service's budget has included a critical habitat subcap to ensure that some funds are available for other work in the Listing Program (“The critical habitat designation subcap will ensure that some funding is available to address other listing activities” (House Report No. 107-103, 107th Congress, 1st Session, June 19, 2001)). In FY 2002 and each year until FY 2006, the Service has had to use virtually the entire critical habitat subcap to address court-mandated designations of critical habitat, and consequently none of the critical habitat subcap funds have been available for other listing activities. In some FYs since 2006, we have been able to use some of the critical habitat subcap funds to fund proposed listing determinations for high-priority candidate species. In other FYs, while we were unable to use any of the critical habitat subcap funds to fund proposed listing determinations, we did use some of this money to fund the critical habitat portion of some proposed listing determinations so that the proposed listing determination and proposed critical habitat designation could be combined into one rule, thereby being more efficient in our work. For FY 2011, we were again able to use some of the critical habitat subcap funds to fund proposed listing determination.</P>
                    <P>We make our determinations of preclusion on a nationwide basis to ensure that the species most in need of listing will be addressed first and also because we allocate our listing budget on a nationwide basis. Through the listing cap, the critical habitat subcap, and the amount of funds needed to address court-mandated critical habitat designations, Congress and the courts have in effect determined the amount of money available for other listing activities nationwide. Therefore, the funds in the listing cap, other than those needed to address court-mandated critical habitat for already listed species, represent the resources we must take into consideration when we make our determinations of preclusion and expeditious progress.</P>
                    <P>Congress identified the availability of resources as the only basis for deferring the initiation of a rulemaking that is warranted. The Conference Report accompanying Public Law 97-304, which established the current statutory deadlines and the warranted-but-precluded finding, states that the amendments were “not intended to allow the Secretary to delay commencing the rulemaking process for any reason other than that the existence of pending or imminent proposals to list species subject to a greater degree of threat would make allocation of resources to such a petition [that is, for a lower-ranking species] unwise.” Although that statement appeared to refer specifically to the “to the maximum extent practicable” limitation on the 90-day deadline for making a “substantial information” finding, that finding is made at the point when the Service is deciding whether or not to commence a status review that will determine the degree of threats facing the species, and therefore the analysis underlying the statement is more relevant to the use of the warranted-but-precluded finding, which is made when the Service has already determined the degree of threats facing the species and is deciding whether or not to commence a rulemaking.</P>
                    <P>
                        In FY 2011, on April 15, 2011, Congress passed the Full-Year Continuing Appropriations Act (Pub. L. 112-10), which provided funding through September 30, 2011. The Service was provided $20,902,000 for the listing program. Of that, the Service used $9,472,000 for determinations of critical habitat for already listed species. Also $500,000 was appropriated for foreign species listings under the ESA. The Service thus had $10,930,000 available to fund work in the following categories: Compliance with court orders and court-approved settlement agreements requiring that petition findings or listing determinations be completed by a specific date; section 4 (of the ESA) listing actions with absolute statutory deadlines; essential 
                        <PRTPAGE P="66380"/>
                        litigation-related, administrative, and listing program-management functions; and high-priority listing actions for some of our candidate species. In FY 2010, the Service received many new petitions and a single petition to list 404 species. The receipt of petitions for a large number of species is consuming the Service's listing funding that is not dedicated to meeting court-ordered commitments. Absent some ability to balance effort among listing duties under existing funding levels, the Service was only able to initiate a few new listing determinations for candidate species in FY 2011.
                    </P>
                    <P>In 2009, the responsibility for listing foreign species under the ESA was transferred from the Division of Scientific Authority, International Affairs Program, to the Endangered Species Program. Therefore, starting in FY 2010, we used a portion of our funding to work on the actions described above for listing actions related to foreign species. In FY 2011, we allocated $500,000 for work on listing actions for foreign species, which reduced funding available for domestic listing actions. Although there are no foreign species issues included in our high-priority listing actions (these are accounted for separately in the Annual Notice of Review for foreign species published on May 3, 2011 (76 FR 25150)), many actions had statutory or court-approved settlement deadlines, thus increasing their priority. The budget allocations for each specific listing action are identified in the Service's FY 2011 Allocation Table (part of our record).</P>
                    <P>Because of the large number of high-priority species, we further ranked the candidate species with an LPN of 2 by using the following extinction-risk type criteria: International Union for the Conservation of Nature and Natural Resources (IUCN) Red list status/rank, Heritage rank (provided by NatureServe), Heritage threat rank (provided by NatureServe), and species currently with fewer than 50 individuals, or 4 or fewer populations. Those species with the highest IUCN rank (critically endangered), the highest Heritage rank (G1), the highest Heritage threat rank (substantial, imminent threats), and currently with fewer than 50 individuals, or fewer than 4 populations, originally comprised a group of approximately 40 candidate species (“Top 40”). These 40 candidate species have had the highest priority to receive funding to work on a proposed listing determination. As we work on proposed and final listing rules for those 40 candidates, we apply the ranking criteria to the next group of candidates with an LPN of 2 and 3 to determine the next set of highest priority candidate species. Finally, proposed rules for reclassification of threatened species to endangered are lower priority, because as listed species, they are already afforded the protections of the ESA and implementing regulations. However, for efficiency reasons, we may choose to work on a proposed rule to reclassify a species to endangered if we can combine this with work that is subject to a court-determined deadline.</P>
                    <P>With our workload so much bigger than the amount of funds we have to accomplish it, it is important that we be as efficient as possible in our listing process. Therefore, as we work on proposed rules for the highest priority species in the next several years, we are preparing multi-species proposals when appropriate, and these may include species with lower priority if they overlap geographically or have the same threats as a species with an LPN of 2. In addition, we take into consideration the availability of staff resources when we determine which high-priority species will receive funding to minimize the amount of time and resources required to complete each listing action.</P>
                    <P>Based on these prioritization factors, we continue to find that proposals to list the petitioned candidate species included in Table 1 are all precluded by higher priority listing actions including those with court-ordered and court-approved settlement agreements, listing actions with absolute statutory deadlines, and work on proposed listing determinations for candidate species with higher listing priorities.</P>
                    <P>As explained above, a determination that listing is warranted but precluded must also demonstrate that expeditious progress is being made to add and remove qualified species to and from the Lists of Endangered and Threatened Wildlife and Plants. As with our “precluded” finding, the evaluation of whether progress in adding qualified species to the Lists has been expeditious is a function of the resources available for listing and the competing demands for those funds. (Although we do not discuss it in detail here, we are also making expeditious progress in removing species from the list under the Recovery program in light of the resource available for delisting, which is funded by a separate line item in the budget of the Endangered Species Program. During FY 2011, we have completed delisting rules for three species.) Given the limited resources available for listing, we find that we made expeditious progress in FY 2011 in the Listing Program. This progress included preparing and publishing the following determinations:</P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,r75,r75,xs85">
                        <TTITLE>FY 2011 Completed Listing Actions</TTITLE>
                        <BOXHD>
                            <CHED H="1">Publication date</CHED>
                            <CHED H="1">Title</CHED>
                            <CHED H="1">Actions</CHED>
                            <CHED H="1">FR pages</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">10/6/2010</ENT>
                            <ENT>Endangered Status for the Altamaha Spinymussel and Designation of Critical Habitat</ENT>
                            <ENT>Proposed Listing Endangered</ENT>
                            <ENT>75 FR 61664-61690</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/7/2010</ENT>
                            <ENT>12-Month Finding on a Petition to list the Sacramento Splittail as Endangered or Threatened</ENT>
                            <ENT>Notice of 12-Month petition finding, Not warranted</ENT>
                            <ENT>75 FR 62070-62095</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/28/2010</ENT>
                            <ENT>Endangered Status and Designation of Critical Habitat for Spikedace and Loach Minnow</ENT>
                            <ENT>Proposed Listing Endangered (uplisting)</ENT>
                            <ENT>75 FR 66481-66552</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11/2/2010</ENT>
                            <ENT>90-Day Finding on a Petition to List the Bay Springs Salamander as Endangered</ENT>
                            <ENT>Notice of 90-day Petition Finding, Not substantial</ENT>
                            <ENT>75 FR 67341-67343</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11/2/2010</ENT>
                            <ENT>Determination of Endangered Status for the Georgia Pigtoe Mussel, Interrupted Rocksnail, and Rough Hornsnail and Designation of Critical Habitat</ENT>
                            <ENT>Final Listing Endangered</ENT>
                            <ENT>75 FR 67511-67550</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11/2/2010</ENT>
                            <ENT>Listing the Rayed Bean and Snuffbox as Endangered</ENT>
                            <ENT>Proposed Listing Endangered</ENT>
                            <ENT>75 FR 67551-67583</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="66381"/>
                            <ENT I="01">11/4/2010</ENT>
                            <ENT>12-Month Finding on a Petition to List Cirsium wrightii (Wright's Marsh Thistle) as Endangered or Threatened</ENT>
                            <ENT>Notice of 12-month petition finding, Warranted but precluded</ENT>
                            <ENT>75 FR 67925-67944</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/14/2010</ENT>
                            <ENT>Endangered Status for Dunes Sagebrush Lizard</ENT>
                            <ENT>Proposed Listing Endangered</ENT>
                            <ENT>75 FR 77801-77817</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/14/2010</ENT>
                            <ENT>12-Month Finding on a Petition to List the North American Wolverine as Endangered or Threatened</ENT>
                            <ENT>Notice of 12-Month petition finding, Warranted but precluded</ENT>
                            <ENT>75 FR 78029-78061</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/14/2010</ENT>
                            <ENT>12-Month Finding on a Petition to List the Sonoran Population of the Desert Tortoise as Endangered or Threatened</ENT>
                            <ENT>Notice of 12-Month petition finding, Warranted but precluded</ENT>
                            <ENT>75 FR 78093-78146</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/15/2010</ENT>
                            <ENT>
                                12-Month Finding on a Petition to List 
                                <E T="03">Astragalus microcymbus</E>
                                 and 
                                <E T="03">Astragalus schmolliae</E>
                                 as Endangered or Threatened
                            </ENT>
                            <ENT>Notice of 12-Month petition finding, Warranted but precluded</ENT>
                            <ENT>75 FR 78513-78556</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12/28/2010</ENT>
                            <ENT>Listing Seven Brazilian Bird Species as Endangered Throughout Their Range</ENT>
                            <ENT>Final Listing Endangered</ENT>
                            <ENT>75 FR 81793-81815</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1/4/2011</ENT>
                            <ENT>
                                90-Day Finding on a Petition to List the Red Knot subspecies 
                                <E T="03">Calidris canutus roselaari</E>
                                 as Endangered
                            </ENT>
                            <ENT>Notice of 90-day Petition Finding, Not substantial</ENT>
                            <ENT>76 FR 304-311</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1/19/2011</ENT>
                            <ENT>Endangered Status for the Sheepnose and Spectaclecase Mussels</ENT>
                            <ENT>Proposed Listing Endangered</ENT>
                            <ENT>76 FR 3392-3420</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2/10/2011</ENT>
                            <ENT>12-Month Finding on a Petition to List the Pacific Walrus as Endangered or Threatened</ENT>
                            <ENT>Notice of 12-Month petition finding, Warranted but precluded</ENT>
                            <ENT>76 FR 7634-7679</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2/17/2011</ENT>
                            <ENT>90-Day Finding on a Petition To List the Sand Verbena Moth as Endangered or Threatened</ENT>
                            <ENT>Notice of 90-day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 9309-9318</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2/22/2011</ENT>
                            <ENT>Determination of Threatened Status for the New Zealand-Australia Distinct Population Segment of the Southern Rockhopper Penguin</ENT>
                            <ENT>Final Listing Threatened</ENT>
                            <ENT>76 FR 9681-9692</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2/22/2011</ENT>
                            <ENT>
                                12-Month Finding on a Petition to List 
                                <E T="03">Solanum conocarpum</E>
                                 (marron bacora) as Endangered
                            </ENT>
                            <ENT>Notice of 12-Month petition finding, Warranted but precluded</ENT>
                            <ENT>76 FR 9722-9733</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2/23/2011</ENT>
                            <ENT>12-Month Finding on a Petition to List Thorne's Hairstreak Butterfly as Endangered</ENT>
                            <ENT>Notice of 12-Month petition finding, Not warranted</ENT>
                            <ENT>76 FR 9991-10003</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2/23/2011</ENT>
                            <ENT>
                                12-Month Finding on a Petition to List 
                                <E T="03">Astragalus hamiltonii, Penstemon flowersii,</E>
                                  
                                <E T="03">Eriogonum soredium, Lepidium ostleri,</E>
                                 and 
                                <E T="03">Trifolium friscanum</E>
                                 as Endangered or Threatened
                            </ENT>
                            <ENT>Notice of 12-Month petition finding, Warranted but precluded &amp; Not Warranted</ENT>
                            <ENT>76 FR 10166-10203</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2/24/2011</ENT>
                            <ENT>90-Day Finding on a Petition to List the Wild Plains Bison or Each of Four Distinct Population Segments as Threatened</ENT>
                            <ENT>Notice of 90-day Petition Finding, Not substantial</ENT>
                            <ENT>76 FR 10299-10310</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2/24/2011</ENT>
                            <ENT>90-Day Finding on a Petition to List the Unsilvered Fritillary Butterfly as Threatened or Endangered</ENT>
                            <ENT>Notice of 90-day Petition Finding, Not substantial</ENT>
                            <ENT>76 FR 10310-10319</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3/8/2011</ENT>
                            <ENT>12-Month Finding on a Petition to List the Mt. Charleston Blue Butterfly as Endangered or Threatened</ENT>
                            <ENT>Notice of 12-Month petition finding, Warranted but precluded</ENT>
                            <ENT>76 FR 12667-12683</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3/8/2011</ENT>
                            <ENT>90-Day Finding on a Petition to List the Texas Kangaroo Rat as Endangered or Threatened</ENT>
                            <ENT>Notice of 90-day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 12683-12690</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3/10/2011</ENT>
                            <ENT>Initiation of Status Review for Longfin Smelt</ENT>
                            <ENT>Notice of Status Review</ENT>
                            <ENT>76 FR 13121-13122</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3/15/2011</ENT>
                            <ENT>Withdrawal of Proposed Rule to List the Flat-tailed Horned Lizard as Threatened</ENT>
                            <ENT>Proposed rule withdrawal</ENT>
                            <ENT>76 FR 14210-14268</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3/15/2011</ENT>
                            <ENT>Proposed Threatened Status for the Chiricahua Leopard Frog and Proposed Designation of Critical Habitat</ENT>
                            <ENT>Proposed Listing Threatened; Proposed Designation of Critical Habitat</ENT>
                            <ENT>76 FR 14126-14207</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3/22/2011</ENT>
                            <ENT>12-Month Finding on a Petition to List the Berry Cave Salamander as Endangered</ENT>
                            <ENT>Notice of 12-Month petition finding, Warranted but precluded</ENT>
                            <ENT>76 FR 15919-15932</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4/1/2011</ENT>
                            <ENT>90-Day Finding on a Petition to List the Spring Pygmy Sunfish as Endangered</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 18138-18143</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4/5/2011</ENT>
                            <ENT>12-Month Finding on a Petition to List the Bearmouth Mountainsnail, Byrne Resort Mountainsnail, and Meltwater Lednian Stonefly as Endangered or Threatened</ENT>
                            <ENT>Notice of 12-Month petition finding, Not Warranted and Warranted but precluded</ENT>
                            <ENT>76 FR 18684-18701</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="66382"/>
                            <ENT I="01">4/5/2011</ENT>
                            <ENT>90-Day Finding on a Petition To List the Peary Caribou and Dolphin and Union population of the Barren-ground Caribou as Endangered or Threatened</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 18701-18706</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4/12/2011</ENT>
                            <ENT>Proposed Endangered Status for the Three Forks Springsnail and San Bernardino Springsnail, and Proposed Designation of Critical Habitat</ENT>
                            <ENT>Proposed Listing Endangered; Proposed Designation of Critical Habitat</ENT>
                            <ENT>76 FR 20464-20488</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4/13/2011</ENT>
                            <ENT>90-Day Finding on a Petition To List Spring Mountains Acastus Checkerspot Butterfly as Endangered</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 20613-20622</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4/14/2011</ENT>
                            <ENT>90-Day Finding on a Petition to List the Prairie Chub as Threatened or Endangered</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 20911-20918</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4/14/2011</ENT>
                            <ENT>12-Month Finding on a Petition to List Hermes Copper Butterfly as Endangered or Threatened</ENT>
                            <ENT>Notice of 12-Month petition finding, Warranted but precluded</ENT>
                            <ENT>76 FR 20918-20939</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4/26/2011</ENT>
                            <ENT>90-Day Finding on a Petition to List the Arapahoe Snowfly as Endangered or Threatened</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 23256-23265</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4/26/2011</ENT>
                            <ENT>90-Day Finding on a Petition to List the Smooth-Billed Ani as Threatened or Endangered</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Not substantial</ENT>
                            <ENT>76 FR 23265-23271</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">5/12/2011</ENT>
                            <ENT>Withdrawal of the Proposed Rule to List the Mountain Plover as Threatened</ENT>
                            <ENT>Proposed Rule, Withdrawal</ENT>
                            <ENT>76 FR 27756-27799</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">5/25/2011</ENT>
                            <ENT>90-Day Finding on a Petition To List the Spot-tailed Earless Lizard as Endangered or Threatened</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 30082-30087</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">5/26/2011</ENT>
                            <ENT>Listing the Salmon-Crested Cockatoo as Threatened Throughout its Range with Special Rule</ENT>
                            <ENT>Final Listing Threatened</ENT>
                            <ENT>76 FR 30758-30780</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">5/31/2011</ENT>
                            <ENT>12-Month Finding on a Petition to List Puerto Rican Harlequin Butterfly as Endangered</ENT>
                            <ENT>Notice of 12-Month petition finding, Warranted but precluded</ENT>
                            <ENT>76 FR 31282-31294</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6/2/2011</ENT>
                            <ENT>
                                90-Day Finding on a Petition to Reclassify the Straight-Horned Markhor (
                                <E T="03">Capra falconeri jerdoni</E>
                                ) of Torghar Hills as Threatened
                            </ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 31903-31906</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6/2/2011</ENT>
                            <ENT>90-Day Finding on a Petition to List the Golden-winged Warbler as Endangered or Threatened</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 31920-31926</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6/7/2011</ENT>
                            <ENT>12-Month Finding on a Petition to List the Striped Newt as Threatened</ENT>
                            <ENT>Notice of 12-Month petition finding, Warranted but precluded</ENT>
                            <ENT>76 FR 32911-32929</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6/9/2011</ENT>
                            <ENT>
                                12-Month Finding on a Petition to List 
                                <E T="03">Abronia ammophila, Agrostis rossiae,</E>
                                  
                                <E T="03">Astragalus proimanthus, Boechera</E>
                                 (
                                <E T="03">Arabis</E>
                                ) 
                                <E T="03">pusilla,</E>
                                 and 
                                <E T="03">Penstemon gibbensii</E>
                                 as Threatened or Endangered
                            </ENT>
                            <ENT>Notice of 12-Month petition finding, Not Warranted and Warranted but precluded</ENT>
                            <ENT>76 FR 33924-33965</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6/21/2011</ENT>
                            <ENT>90-Day Finding on a Petition to List the Utah Population of the Gila Monster as an Endangered or a Threatened Distinct Population Segment</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Not substantial</ENT>
                            <ENT>76 FR 36049-36053</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6/21/2011</ENT>
                            <ENT>Revised 90-Day Finding on a Petition To Reclassify the Utah Prairie Dog From Threatened to Endangered</ENT>
                            <ENT>Notice of 90-day Petition Finding, Not substantial</ENT>
                            <ENT>76 FR 36053-36068</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6/28/2011</ENT>
                            <ENT>
                                12-Month Finding on a Petition to List 
                                <E T="03">Castanea pumila</E>
                                 var. 
                                <E T="03">ozarkensis</E>
                                 as Threatened or Endangered
                            </ENT>
                            <ENT>Notice of 12-Month petition finding, Not warranted</ENT>
                            <ENT>76 FR 37706-37716</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6/29/2011</ENT>
                            <ENT>90-Day Finding on a Petition to List the Eastern Small-Footed Bat and the Northern Long-Eared Bat as Threatened or Endangered</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 38095-38106</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6/30/2011</ENT>
                            <ENT>12-Month Finding on a Petition to List a Distinct Population Segment of the Fisher in Its United States Northern Rocky Mountain Range as Endangered or Threatened with Critical Habitat</ENT>
                            <ENT>Notice of 12-Month petition finding, Not warranted</ENT>
                            <ENT>76 FR 38504-38532</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">7/12/2011</ENT>
                            <ENT>90-Day Finding on a Petition to List the Bay Skipper as Threatened or Endangered</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 40868-40871</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="66383"/>
                            <ENT I="01">7/19/2011</ENT>
                            <ENT>
                                12-Month Finding on a Petition to List 
                                <E T="03">Pinus albicaulis</E>
                                 as Endangered or Threatened with Critical Habitat
                            </ENT>
                            <ENT>Notice of 12-Month petition finding, Warranted but precluded</ENT>
                            <ENT>76 FR 42631-42654</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">7/19/2011</ENT>
                            <ENT>Petition To List Grand Canyon Cave Pseudoscorpion</ENT>
                            <ENT>Notice of 12-Month petition finding, Not warranted</ENT>
                            <ENT>76 FR 42654-42658</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">7/26/2011</ENT>
                            <ENT>
                                12-Month Finding on a Petition to List the Giant Palouse Earthworm (
                                <E T="03">Drilolerius americanus</E>
                                ) as Threatened or Endangered
                            </ENT>
                            <ENT>Notice of 12-Month petition finding, Not warranted</ENT>
                            <ENT>76 FR 44547-44564</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">7/26/2011</ENT>
                            <ENT>12-Month Finding on a Petition to List the Frigid Ambersnail as Endangered</ENT>
                            <ENT>Notice of 12-Month petition finding, Not warranted</ENT>
                            <ENT>76 FR 44566-44569</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">7/27/2011</ENT>
                            <ENT>
                                Determination of Endangered Status for 
                                <E T="03">Ipomopsis polyantha</E>
                                 (Pagosa Skyrocket) and Threatened Status for
                                <E T="03"> Penstemon debilis</E>
                                 (Parachute Beardtongue) and 
                                <E T="03">Phacelia submutica</E>
                                 (DeBeque Phacelia)
                            </ENT>
                            <ENT>Final Listing Endangered, Threatened</ENT>
                            <ENT>76 FR 45054-45075</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">7/27/2011</ENT>
                            <ENT>12-Month Finding on a Petition to List the Gopher Tortoise as Threatened in the Eastern Portion of its Range</ENT>
                            <ENT>Notice of 12-Month petition finding, Warranted but precluded</ENT>
                            <ENT>76 FR 45130-45162</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/2/2011</ENT>
                            <ENT>
                                Proposed Endangered Status for the Chupadera Springsnail (
                                <E T="03">Pyrgulopsis chupaderae</E>
                                ) and Proposed Designation of Critical Habitat
                            </ENT>
                            <ENT>Proposed Listing Endangered</ENT>
                            <ENT>76 FR 46218-46234</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/2/2011</ENT>
                            <ENT>90-Day Finding on a Petition to List the Straight Snowfly and Idaho Snowfly as Endangered</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Not substantial</ENT>
                            <ENT>76 FR 46238-46251</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/2/2011</ENT>
                            <ENT>12-Month Finding on a Petition to List the Redrock Stonefly as Endangered or Threatened</ENT>
                            <ENT>Notice of 12-Month petition finding, Not warranted</ENT>
                            <ENT>76 FR 46251-46266</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/2/2011</ENT>
                            <ENT>Listing 23 Species on Oahu as Endangered and Designating Critical Habitat for 124 Species</ENT>
                            <ENT>Proposed Listing Endangered</ENT>
                            <ENT>76 FR 46362-46594</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/4/2011</ENT>
                            <ENT>90-Day Finding on a Petition To List Six Sand Dune Beetles as Endangered or Threatened</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Not substantial and substantial</ENT>
                            <ENT>76 FR 47123-47133</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/9/2011</ENT>
                            <ENT>Endangered Status for the Cumberland Darter, Rush Darter, Yellowcheek Darter, Chucky Madtom, and Laurel Dace</ENT>
                            <ENT>Final Listing Endangered</ENT>
                            <ENT>76 FR 48722-48741</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/9/2011</ENT>
                            <ENT>12-Month Finding on a Petition to List the Nueces River and Plateau Shiners as Threatened or Endangered</ENT>
                            <ENT>Notice of 12-Month petition finding, Not warranted</ENT>
                            <ENT>76 FR 48777-48788</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/9/2011</ENT>
                            <ENT>Four Foreign Parrot Species [crimson shining parrot, white cockatoo, Philippine cockatoo, yellow-crested cockatoo]</ENT>
                            <ENT>Proposed Listing Endangered and Threatened; Notice of 12-Month petition finding, Not warranted</ENT>
                            <ENT>76 FR 49202-49236</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/10/2011</ENT>
                            <ENT>Proposed Listing of the Miami Blue Butterfly as Endangered, and Proposed Listing of the Cassius Blue, Ceraunus Blue, and Nickerbean Blue Butterflies as Threatened Due to Similarity of Appearance to the Miami Blue Butterfly</ENT>
                            <ENT>Proposed Listing Endangered Similarity of Appearance</ENT>
                            <ENT>76 FR 49408-49412</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/10/2011</ENT>
                            <ENT>90-Day Finding on a Petition To List the Saltmarsh Topminnow as Threatened or Endangered Under the Endangered Species Act</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 49412-49417</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/10/2011</ENT>
                            <ENT>Emergency Listing of the Miami Blue Butterfly as Endangered, and Emergency Listing of the Cassius Blue, Ceraunus Blue, and Nickerbean Blue Butterflies as Threatened Due to Similarity of Appearance to the Miami Blue Butterfly</ENT>
                            <ENT>Emergency Listing Endangered and Similarity of Appearance</ENT>
                            <ENT>76 FR 49542-49567</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/11/2011</ENT>
                            <ENT>Listing Six Foreign Birds as Endangered Throughout Their Range</ENT>
                            <ENT>Final Listing Endangered</ENT>
                            <ENT>76 FR 50052-50080</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8/17/2011</ENT>
                            <ENT>90-Day Finding on a Petition to List the Leona's Little Blue Butterfly as Endangered or Threatened</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 50971-50979</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/01/2011</ENT>
                            <ENT>
                                90-Day Finding on a Petition to List All Chimpanzees (
                                <E T="03">Pan troglodytes</E>
                                ) as Endangered
                            </ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 54423-54425</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="66384"/>
                            <ENT I="01">9/6/2011</ENT>
                            <ENT>12-Month Finding on Five Petitions to List Seven Species of Hawaiian Yellow-faced Bees as Endangered</ENT>
                            <ENT>Notice of 12-Month petition finding, Warranted but precluded</ENT>
                            <ENT>76 FR 55170-55203</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/8/2011</ENT>
                            <ENT>
                                12-Month Petition Finding and Proposed Listing of 
                                <E T="03">Arctostaphylos franciscana</E>
                                 as Endangered
                            </ENT>
                            <ENT>Notice of 12-Month petition finding, Warranted; Proposed Listing Endangered</ENT>
                            <ENT>76 FR 55623-55638</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/8/2011</ENT>
                            <ENT>90-Day Finding on a Petition To List the Snowy Plover and Reclassify the Wintering Population of Piping Plover</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Not substantial</ENT>
                            <ENT>76 FR 55638-55641</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/13/2011</ENT>
                            <ENT>90-Day Finding on a Petition To List the Franklin's Bumble Bee as Endangered</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 56381-56391</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/13/2011</ENT>
                            <ENT>90-Day Finding on a Petition to List 42 Great Basin and Mojave Desert Springsnails as Threatened or Endangered with Critical Habitat</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial and Not substantial</ENT>
                            <ENT>76 FR 56608-56630</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/21/2011</ENT>
                            <ENT>12-Month Finding on a Petition to List Van Rossem's Gull-billed Tern as Endangered or Threatened</ENT>
                            <ENT>Notice of 12-Month petition finding, Not warranted</ENT>
                            <ENT>76 FR 58650-58680</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/22/2011</ENT>
                            <ENT>Determination of Endangered Status for Casey's June Beetle and Designation of Critical Habitat</ENT>
                            <ENT>Final Listing Endangered</ENT>
                            <ENT>76 FR 58954-58998</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/27/2011</ENT>
                            <ENT>
                                12-Month Finding on a Petition to List the Tamaulipan Agapema, 
                                <E T="03">Sphingicampa blanchardi</E>
                                 (no common name), and 
                                <E T="03">Ursia furtiva</E>
                                 (no common name) as Endangered or Threatened
                            </ENT>
                            <ENT>Notice of 12-Month petition finding, Not warranted</ENT>
                            <ENT>76 FR 59623-59634</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/27/2011</ENT>
                            <ENT>Partial 90-Day Finding on a Petition to List 404 Species in the Southeastern United States as Endangered or Threatened With Critical Habitat</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 59836-59862</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9/29/2011</ENT>
                            <ENT>90-Day Finding on a Petition to List the American Eel as Threatened</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial</ENT>
                            <ENT>76 FR 60431-60444</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/4/2011</ENT>
                            <ENT>
                                12-Month Finding on a Petition to List the Lake Sammamish Kokanee Population of 
                                <E T="03">Oncorhynchus nerka</E>
                                 as an Endangered or Threatened Distinct Population Segment
                            </ENT>
                            <ENT>Notice of 12-Month petition finding, Not warranted</ENT>
                            <ENT>76 FR 61298-61307</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/4/2011</ENT>
                            <ENT>
                                12-Month Finding on a Petition to List 
                                <E T="03">Calopogon oklahomensis</E>
                                 as Threatened or Endangered
                            </ENT>
                            <ENT>Notice of 12-Month petition finding, Not warranted</ENT>
                            <ENT>76 FR 61307-61321</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/4/2011</ENT>
                            <ENT>12-Month Finding on a Petition To List the Amargosa River Population of the Mojave Fringe-toed Lizard as an Endangered or Threatened Distinct Population Segment</ENT>
                            <ENT>Notice of 12-Month petition finding, Not warranted</ENT>
                            <ENT>76 FR 61321-61330</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/4/2011</ENT>
                            <ENT>Endangered Status for the Alabama Pearlshell, Round Ebonyshell, Southern Sandshell, Southern Kidneyshell, and Choctaw Bean, and Threatened Status for the Tapered Pigtoe, Narrow Pigtoe, and Fuzzy Pigtoe; with Critical Habitat</ENT>
                            <ENT>Proposed Listing Endangered</ENT>
                            <ENT>76 FR 61482-61529</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10/4/2011</ENT>
                            <ENT>90-Day Finding on a Petition To List 10 Subspecies of Great Basin Butterflies as Threatened or Endangered with Critical Habitat</ENT>
                            <ENT>Notice of 90-Day Petition Finding, Substantial and Not substantial</ENT>
                            <ENT>76 FR 61532-61554</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>
                        Our expeditious progress also included work on listing actions that we funded in FY 2010 and FY 2011 but have not yet been completed to date. These actions are listed below. Actions in the top section of the table are being conducted under a deadline set by a court. Actions in the middle section of the table are being conducted to meet statutory timelines, that is, timelines required under the ESA. Actions in the bottom section of the table are high-priority listing actions. These actions include work primarily on species with an LPN of 2, and, as discussed above, selection of these species is partially based on available staff resources, and when appropriate, include species with a lower priority if they overlap geographically or have the same threats as the species with the high priority. Including these species together in the same proposed rule results in considerable savings in time and funding, compared to preparing separate proposed rules for each of them in the future.
                        <PRTPAGE P="66385"/>
                    </P>
                    <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s250,r100">
                        <TTITLE>Actions Funded in FY 2010 and FY 2011 But Not Yet Completed</TTITLE>
                        <BOXHD>
                            <CHED H="1">Species</CHED>
                            <CHED H="1">Action</CHED>
                        </BOXHD>
                        <ROW EXPSTB="01" RUL="s">
                            <ENT I="21">
                                <E T="02">Actions Subject to Court Order/Settlement Agreement</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">
                                4 parrot species (military macaw, yellow-billed parrot, red-crowned parrot, scarlet macaw) 
                                <SU>5</SU>
                            </ENT>
                            <ENT>12-month petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                4 parrot species (blue-headed macaw, great green macaw, grey-cheeked parakeet, hyacinth macaw) 
                                <SU>5</SU>
                            </ENT>
                            <ENT>12-month petition finding.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Longfin smelt</ENT>
                            <ENT>12-month petition finding.</ENT>
                        </ROW>
                        <ROW EXPSTB="01" RUL="s">
                            <ENT I="21">
                                <E T="02">Actions With Statutory Deadlines</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">5 Bird species from Colombia and Ecuador</ENT>
                            <ENT>Final listing determination.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Queen Charlotte goshawk</ENT>
                            <ENT>Final listing determination.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Ozark hellbender 
                                <SU>4</SU>
                            </ENT>
                            <ENT>Final listing determination.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Altamaha spinymussel 
                                <SU>3</SU>
                            </ENT>
                            <ENT>Final listing determination.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6 Birds from Peru &amp; Bolivia</ENT>
                            <ENT>Final listing determination.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Loggerhead sea turtle (assist National Marine Fisheries Service) 
                                <SU>5</SU>
                            </ENT>
                            <ENT>Final listing determination.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                2 mussels (rayed bean (LPN = 2), snuffbox No LPN) 
                                <SU>5</SU>
                            </ENT>
                            <ENT>Final listing determination.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                CA golden trout 
                                <SU>4</SU>
                            </ENT>
                            <ENT>12-month petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Black-footed albatross</ENT>
                            <ENT>12-month petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Cactus ferruginous pygmy-owl 
                                <SU>1</SU>
                            </ENT>
                            <ENT>12-month petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Northern leopard frog</ENT>
                            <ENT>12-month petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Tehachapi slender salamander</ENT>
                            <ENT>12-month petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Coqui Llanero</ENT>
                            <ENT>12-month petition finding/Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Dusky tree vole</ENT>
                            <ENT>12-month petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Leatherside chub (from 206 species petition)</ENT>
                            <ENT>12-month petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Platte River caddisfly (from 206 species petition) 
                                <SU>5</SU>
                            </ENT>
                            <ENT>12-month petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                3 South Arizona plants (
                                <E T="03">Erigeron piscaticus, Astragalus hypoxylus, Amoreuxia gonzalezii</E>
                                ) (from 475 species petition)
                            </ENT>
                            <ENT>12-month petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">5 Central Texas mussel species (3 from 475 species petition)</ENT>
                            <ENT>12-month petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">14 parrots (foreign species)</ENT>
                            <ENT>12-month petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Mohave Ground Squirrel 
                                <SU>1</SU>
                            </ENT>
                            <ENT>12-month petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Ashy storm-petrel 
                                <SU>5</SU>
                            </ENT>
                            <ENT>12-month petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Honduran emerald</ENT>
                            <ENT>12-month petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Eagle Lake trout 
                                <SU>1</SU>
                            </ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                32 Pacific Northwest mollusks species (snails and slugs) 
                                <SU>1</SU>
                            </ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Spring Mountains checkerspot butterfly</ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11 of 404 Southeast species</ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Aztec gilia 
                                <SU>5</SU>
                            </ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                White-tailed ptarmigan 
                                <SU>5</SU>
                            </ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                San Bernardino flying squirrel 
                                <SU>5</SU>
                            </ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Bicknell's thrush 
                                <SU>5</SU>
                            </ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Sonoran talussnail 
                                <SU>5</SU>
                            </ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                2 AZ Sky Island plants (
                                <E T="03">Graptopetalum bartrami</E>
                                 &amp; 
                                <E T="03">Pectis imberbis</E>
                                ) 
                                <SU>5</SU>
                            </ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                I'iwi 
                                <SU>5</SU>
                            </ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Humboldt marten</ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Desert massasauga</ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Western glacier stonefly (
                                <E T="03">Zapada glacier</E>
                                )
                            </ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Thermophilic ostracod (
                                <E T="03">Potamocypris hunteri</E>
                                )
                            </ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Sierra Nevada red fox 
                                <SU>5</SU>
                            </ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Boreal toad (eastern or southern Rocky Mtn population) 
                                <SU>5</SU>
                            </ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">
                                Alexander Archipelago wolf 
                                <SU>5</SU>
                            </ENT>
                            <ENT>90-day petition finding.</ENT>
                        </ROW>
                        <ROW EXPSTB="01" RUL="s">
                            <ENT I="21">
                                <E T="02">High-Priority Listing Actions</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">
                                20 Maui-Nui candidate species 
                                <SU>2</SU>
                                 (17 plants, 3 tree snails) (14 with LPN = 2, 2 with LPN = 3, 3 with LPN = 8)
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Umtanum buckwheat (LPN = 2) and white bluffs bladderpod (LPN = 9) 
                                <SU>4</SU>
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Grotto sculpin (LPN = 2) 
                                <SU>4</SU>
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                2 Arkansas mussels (Neosho mucket (LPN = 2) &amp; Rabbitsfoot (LPN = 9)) 
                                <SU>4</SU>
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Diamond darter (LPN = 2) 
                                <SU>4</SU>
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Gunnison sage-grouse (LPN = 2) 
                                <SU>4</SU>
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Coral Pink Sand Dunes Tiger Beetle (LPN = 2) 
                                <SU>5</SU>
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Lesser prairie chicken (LPN = 2)</ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                4 Texas salamanders (Austin blind salamander (LPN = 2), Salado salamander (LPN = 2), Georgetown salamander (LPN = 8), Jollyville Plateau (LPN = 8)) 
                                <SU>3</SU>
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                5 West Texas aquatics (Gonzales Spring Snail (LPN = 2), Diamond Y springsnail (LPN = 2), Phantom springsnail (LPN = 2), Phantom Cave snail (LPN = 2), Diminutive amphipod (LPN = 2)) 
                                <SU>3</SU>
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                2 Texas plants (Texas golden gladecress (
                                <E T="03">Leavenworthia texana</E>
                                ) (LPN = 2), Neches River rose-mallow (
                                <E T="03">Hibiscus dasycalyx</E>
                                ) (LPN = 2)) 
                                <SU>3</SU>
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                4 AZ plants (Acuna cactus (
                                <E T="03">Echinomastus erectocentrus</E>
                                 var. 
                                <E T="03">acunensis</E>
                                ) (LPN = 3), Fickeisen plains cactus (
                                <E T="03">Pediocactus peeblesianus fickeiseniae</E>
                                ) (LPN = 3), Lemmon fleabane (
                                <E T="03">Erigeron lemmonii</E>
                                ) (LPN = 8), Gierisch mallow (
                                <E T="03">Sphaeralcea gierischii</E>
                                ) (LPN = 2)) 
                                <SU>5</SU>
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="66386"/>
                            <ENT I="01">
                                FL bonneted bat (LPN = 2) 
                                <SU>3</SU>
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                3 Southern FL plants (Florida semaphore cactus (
                                <E T="03">Consolea corallicola</E>
                                ) (LPN = 2), shellmound applecactus (
                                <E T="03">Harrisia</E>
                                 (=
                                <E T="03">Cereus</E>
                                ) 
                                <E T="03">aboriginum</E>
                                 (=
                                <E T="03">gracilis</E>
                                )) (LPN = 2), Cape Sable thoroughwort (
                                <E T="03">Chromolaena frustrata</E>
                                ) (LPN = 2)) 
                                <SU>5</SU>
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                21 Big Island (HI) species 
                                <SU>5</SU>
                                 (includes 8 candidate species—6 plants &amp; 2 animals; 4 with LPN = 2, 1 with LPN = 3, 1 with LPN = 4, 2 with LPN = 8)
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                12 Puget Sound prairie species (9 subspecies of pocket gopher (
                                <E T="03">Thomomys mazama</E>
                                 ssp.) (LPN = 3), streaked horned lark (LPN = 3), Taylor's checkerspot (LPN = 3), Mardon skipper (LPN = 8)) 
                                <SU>3</SU>
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                2 TN River mussels (fluted kidneyshell (LPN = 2), slabside pearlymussel (LPN = 2)) 
                                <SU>5</SU>
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Jemez Mountain salamander (LPN = 2) 
                                <SU>5</SU>
                            </ENT>
                            <ENT>Proposed listing.</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             Funds for listing actions for these species were provided in previous FYs.
                        </TNOTE>
                        <TNOTE>
                            <SU>2</SU>
                             Although funds for these high-priority listing actions were provided in FY 2008 or 2009, due to the complexity of these actions and competing priorities, these actions are still being developed.
                        </TNOTE>
                        <TNOTE>
                            <SU>3</SU>
                             Partially funded with FY 2010 funds and FY 2011 funds.
                        </TNOTE>
                        <TNOTE>
                            <SU>4</SU>
                             Funded with FY 2010 funds.
                        </TNOTE>
                        <TNOTE>
                            <SU>5</SU>
                             Funded with FY 2011 funds.
                        </TNOTE>
                    </GPOTABLE>
                    <P>We also funded work on resubmitted petitions findings for 204 candidate species (species petitioned prior to the last CNOR). We did not include new information in our resubmitted petition finding for the Columbia Basin population of the greater sage-grouse in this notice, as the significance of the Columbia Basin DPS to the greater sage-grouse will require further review and we will update our finding at a later date (see 75 FR 13910; March 23, 2010). We also did not include new information in our resubmitted petition findings for the 64 candidate species for which we are preparing proposed listing determinations; see summaries below regarding publication of these determinations (these species will remain on the candidate list until a proposed listing rule is published). We also funded revised 12-month petition findings for the candidate species that we are removing from candidate status, which are being published as part of this CNOR (see Candidate Removals). Because the majority of these species were already candidate species prior to our receipt of a petition to list them, we had already assessed their status using funds from our Candidate Conservation Program. We also continue to monitor the status of these species through our Candidate Conservation Program. The cost of updating the species assessment forms and publishing the joint publication of the CNOR and resubmitted petition findings is shared between the Listing Program and the Candidate Conservation Program.</P>
                    <P>During FY 2011, we also funded work on resubmitted petition findings for uplisting two listed species, for which petitions were previously received.</P>
                    <P>Given the limited resources available for listing, we find that we are making expeditious progress to add qualified species to the lists of threatened and endangered species. First, as the tables above show, we are making expeditious progress by listing qualified species. In FY 2011, we resolved the status of 29 species that we determined, or had previously determined, qualified for listing; for 27 of those 29 species, the resolution was to add them to the lists of threatened and endangered species. We also proposed to list an additional 45 qualified species.</P>
                    <P>Second, we are making expeditious progress by working on adding qualified species to the lists. In FY 2011, we worked on developing final listing determinations for an additional 17 species, and proposed listing rules for another 85 species. Although we have not yet completed those actions, we are making expeditious progress towards doing so.</P>
                    <P>Third, we are making expeditious progress to add qualified species to the lists by identifying additional species that qualify for listing. In FY 2011, we completed 90-day petition findings for 480 species, and 12-month petition findings for 52 species. Of those 52 species, we determined that listing of 26 of the species was warranted but precluded. In FY 2011 we also worked on 90-day findings for an additional 50 species and 12-month findings for an additional 43 species.</P>
                    <P>
                        Finally, the Service is making expeditious progress to add qualified species to the list by developing and beginning to implement a work plan that establishes a framework and schedule for resolving by September 30, 2016, the status of all of the species that the Service had determined to be qualified as of the 2010 Candidate Notice of Review. The Service submitted such a work plan to the U.S. District Court for the District of Columbia in 
                        <E T="03">In re Endangered Species Act Section 4 Deadline Litigation,</E>
                         No. 10-377 (EGS), MDL Docket No. 2165 (D. DC May 10, 2011), and obtained the court's approval. The Service has already begun to implement that work plan, because we completed most of the work identified in the above tables in accordance with the schedule set out in that work plan.
                    </P>
                    <P>We have endeavored to make our listing actions as efficient and timely as possible, given the requirements of the relevant law and regulations, and constraints relating to workload and personnel. We are continually considering ways to streamline processes or achieve economies of scale, such as by batching related actions together. Given our limited budget for implementing section 4 of the ESA, the actions described above collectively constitute expeditious progress.</P>
                    <P>
                        Although we have not been able to resolve the listing status of many of the candidates, several programs in the Service contribute to the conservation of these species. In particular, the Candidate Conservation program, which is separately budgeted, focuses on providing technical expertise for developing conservation strategies and agreements to guide voluntary on-the-ground conservation work for candidate and other at-risk species. The main goal of this program is to address the threats facing candidate species. Through this program, we work with our partners (other Federal agencies, State agencies, Tribes, local governments, private landowners, and private conservation organizations) to address the threats to candidate species and other species at-risk. We are currently working with our partners to implement voluntary conservation agreements for more than 140 species covering 5 million acres of habitat. In some instances, the sustained implementation of strategically designed conservation efforts 
                        <PRTPAGE P="66387"/>
                        culminates in making listing unnecessary for species that are candidates for listing or for which listing has been proposed.
                    </P>
                    <HD SOURCE="HD2">Findings for Petitioned Candidate Species</HD>
                    <P>Below are updated summaries for petitioned candidates for which we published findings, under section 4(b)(3)(B). We are making continued warranted-but-precluded 12-month findings on the petitions for these species (for our revised 12-month petition findings for species we are removing from candidate status, see summaries above under “Candidate Removals”).</P>
                    <HD SOURCE="HD2">Mammals</HD>
                    <P>
                        Florida bonneted bat (
                        <E T="03">Eumops floridanus</E>
                        )—The following summary is based on information in our files. No new information was presented in the petition received on January 29, 2010. Endemic to south Florida, this species has been found at 12 locations, 5 on private land and 7 on public land. The entire population may number less than a few hundred individuals. Results from a rangewide acoustical survey found a small number of locations where calls were recorded, and low numbers of calls were recorded at each location. Few active roost sites are known; all are artificial (i.e., bat houses). Prolonged cold temperatures in January and February 2010 affected one active roost. Additional cold temperatures occurred in south Florida in December 2010. In the short term, severe and prolonged cold events resulted in mortality of at least several adult Florida bonneted bats. The long-term effects of prolonged and repeated cold events on the species are not known. Efforts are underway to confirm presence at all previously documented sites. Additionally, a study to determine the northern and southern extent of the species' range and estimate overall abundance was initiated in 2011.
                    </P>
                    <P>Occurrences are threatened by loss and conversion of habitat to other uses and habitat alteration (e.g., removal of old trees with cavities, removal of manmade structures with suitable roosting sites); this threat is expected to continue and increase. Although occurrences on conservation lands are inherently more protected than those on private lands, habitat alteration during management practices may affect natural roosting sites even on conservation lands if Florida bonneted bats are present but undetected. Therefore, occupied and potential habitat on forested or wooded lands, both private and public, continues to be at risk. The species is vulnerable to a wide array of natural and human factors: low population size, restricted range, low fecundity, large distances between occupied locations, and small number of occupied locations. Such factors may make recolonization unlikely if any site is extirpated, and may make the species vulnerable to extinction due to genetic drift, inbreeding depression, extreme weather events, and random or chance changes to the environment. Where the species occurs in or near human dwellings or structures, it is at risk to persecution, removal, and disturbance. Disturbance from humans, either intentional or inadvertent, can take place at any of the occurrences of this bat on either private or conservation lands. Disturbance of maternity roosts is of particular concern due to the low fecundity and small population of this species. Pesticide applications may be affecting its foraging base, especially in coastal areas.</P>
                    <P>Due to its overall vulnerability, intense hurricanes are a significant threat; this threat is expected to continue or increase in the future. Intense storms can cause mortality during the storm, exposure to predation immediately following the storm, loss of roost sites, impacts on foraging areas and insect abundance, and disruption of the maternal period. Prolonged and repeated periods of cold temperatures may have severe impacts on the population and increase risks from other threats by weakening individuals, extirpating colonies, or further reducing colony sizes. Although disease is a significant threat for other bat species, it is not known to be a threat for the Florida bonneted bat at this time. The protection currently afforded the Florida bonneted bat is limited, provides little protection to the species' occupied habitat, and includes no provisions to protect suitable but unoccupied habitat within the vicinity of known colony sites. Overall, we find the magnitude of threats is high due to the severity of the threats to this species. We find that most of the threats are currently occurring and, consequently, overall, threats are imminent. Therefore, we assigned an LPN of 2 to this species.</P>
                    <P>
                        Pacific sheath-tailed bat, American Samoa DPS (
                        <E T="03">Emballonura semicaudata semicaudata</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. This small bat is a member of the Emballonuridae, an Old World bat family that has an extensive distribution, primarily in the tropics. The Pacific sheath-tailed bat was once common and widespread in Polynesia and Micronesia, and it is the only insectivorous bat recorded from a large part of this area. The species as a whole (
                        <E T="03">E. semicaudata</E>
                        ) occurred on several of the Caroline Islands (Palau, Chuuk, and Pohnpei), Samoa (Independent and American), the Mariana Islands (Guam and the Commonwealth of the Northern Mariana Islands (CNMI)), Tonga, Fiji, and Vanuatu. While populations appear to be healthy in some locations, mainly in the Caroline Islands, they have declined substantially in other areas, including Independent and American Samoa, the Mariana Islands, Fiji, and possibly Tonga. Scientists recognize four subspecies: 
                        <E T="03">E. s. rotensis,</E>
                         endemic to the Mariana Islands (Guam and CNMI); 
                        <E T="03">E. s. sulcata,</E>
                         occurring in Chuuk and Pohnpei; 
                        <E T="03">E. s. palauensis,</E>
                         found in Palau; and 
                        <E T="03">E. s. semicaudata,</E>
                         occurring in American and Independent Samoa, Tonga, Fiji, and Vanuatu. This candidate assessment addresses the distinct population segment (DPS) of 
                        <E T="03">E. s. semicaudata</E>
                         that occurs in American Samoa.
                    </P>
                    <P>
                        <E T="03">E. s. semicaudata</E>
                         historically occurred in American and Independent Samoa, Tonga, Fiji, and Vanuatu. It is extant in Fiji and Tonga, but may be extirpated from Vanuatu and Independent Samoa. There is some concern that it is also extirpated from American Samoa, the location of this DPS, where surveys are currently ongoing to ascertain its status. The factors that led to the decline of this subspecies and the DPS are poorly understood; however, current threats to this subspecies and the DPS include habitat loss, predation by introduced species, and its small population size and distribution, which make the taxon extremely vulnerable to extinction due to typhoons and similar natural catastrophes. Thus, since the threats affect the entire DPS, and would likely be permanent, the threats are high in magnitude. The Pacific sheath-tailed bat may also be susceptible to disturbance to roosting caves. The LPN for 
                        <E T="03">E. s. semicaudata</E>
                         is 3 because the magnitude of the threats is high; the threats are ongoing, and therefore imminent; and the taxon is a distinct population segment of a subspecies.
                    </P>
                    <P>
                        Pacific sheath-tailed bat (
                        <E T="03">Emballonura semicaudata rotensis</E>
                        ), Guam and the Commonwealth of the Northern Mariana Islands (CNMI)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. This small bat is a member of the Emballonuridae, an Old World bat family that has an extensive distribution, primarily in the tropics. 
                        <PRTPAGE P="66388"/>
                        The Pacific sheath-tailed bat was once common and widespread in Polynesia and Micronesia, and it is the only insectivorous bat recorded from a large part of this area. 
                        <E T="03">E. s. rotensis</E>
                         is historically known from the Mariana Islands and formerly occurred on Guam and in the CNMI on Rota, Aguiguan, Tinian (known from prehistoric records only), Saipan, and possibly Anatahan and Maug. Currently, 
                        <E T="03">E. s. rotensis</E>
                         appears to be extirpated from all but one island in the Mariana archipelago. The single remaining population of this subspecies occurs on Aguiguan, CNMI.
                    </P>
                    <P>
                        Threats to this subspecies have not changed over the past year. The primary threats to the subspecies are ongoing habitat loss and degradation as a result of feral goat (
                        <E T="03">Capra hircus</E>
                        ) activity on the island of Aguiguan and the taxon's small population size and limited distribution. Predation by nonnative species and human disturbance are also potential threats to the subspecies. The subspecies is believed near the point where stochastic events, such as typhoons, are increasingly likely to affect its continued survival. The disappearance of the remaining population on Aguiguan would result in the extinction of the subspecies. Thus, since the threats affect the entire subspecies, and would likely be permanent, the threats are high in magnitude. The LPN for 
                        <E T="03">E. s. rotensis</E>
                         remains at 3 because the magnitude of the threats is high; the threats are ongoing, and therefore imminent; and the taxon is a subspecies.
                    </P>
                    <P>
                        New England cottontail (
                        <E T="03">Sylvilagus transitionalis</E>
                        )—The following summary is based on information contained in our files and information received in response to our notice published on June 30, 2004, when we announced our 90-day petition finding and initiation of a status review (69 FR 39395). We received the petition on August 30, 2000.
                    </P>
                    <P>
                        The New England cottontail (NEC) is a medium- to large-sized cottontail rabbit that may reach 1,000 grams in weight, and is one of two species within the genus 
                        <E T="03">Sylvilagus</E>
                         occurring in New England. NEC is considered a habitat specialist, in so far as it is dependent upon early-successional habitats typically described as thickets. The species is the only endemic cottontail in New England. Historically, the NEC occurred in seven States and ranged from southeastern New York (east of the Hudson River) north through the Champlain Valley, southern Vermont, the southern half of New Hampshire, and southern Maine and south throughout Massachusetts, Connecticut, and Rhode Island. The current range of the NEC has declined substantially, and occurrences have become increasingly separated. The species' distribution is fragmented into five apparently isolated metapopulations. The area occupied by the cottontail has contracted from approximately 90,000 sq km to 12,180 sq km. Surveys indicate that the long-term decline in NEC continues. For example, surveys for the species in 2009 documented the presence of NEC in only 7 of the 23 New Hampshire locations that were known to be occupied in 2002 and 2003. Similarly, surveys in Maine found the species no longer present in 9 of the 19 towns identified in an extensive survey that spanned the years 2000 to 2004. Similar surveys were conducted during the winter of 2010-2011 in Rhode Island, but the results are not yet available. Rangewide, it is estimated that less than one third of the occupied sites occur on lands in conservation status and fewer than 10 percent are being managed for early-successional forest species.
                    </P>
                    <P>The primary threat to the NEC is loss of habitat through succession and alteration. Isolation of occupied patches by areas of unsuitable habitat and high predation rates are resulting in local extirpation of NECs from small patches. The range of the NEC has contracted by 75 percent or more since 1960, and current land uses in the region indicate that the rate of change, about 2 percent range loss per year, will continue. Additional threats include competition for food and habitat with introduced eastern cottontails and large numbers of native white-tailed deer, inadequate regulatory mechanisms to protect habitat, and mortality from predation. The magnitude of the threats continues to be high, because they occur rangewide and have a negative effect on the survival of the species. The threats are imminent because they are ongoing. Thus, we retained an LPN of 2 for this species. Conservation measures that address the threats to the species are being developed.</P>
                    <P>
                        Fisher, West Coast DPS (
                        <E T="03">Martes pennanti</E>
                        )—The following summary is based on information in our files and in the Service's initial warranted-but-precluded finding published in the 
                        <E T="04">Federal Register</E>
                        <E T="03"/>
                         on April 8, 2004 (69 FR 18770). The fisher is a carnivore in the family Mustelidae, and is the largest member of the genus 
                        <E T="03">Martes.</E>
                         Historically, the West Coast population of the fisher extended south from British Columbia into western Washington and Oregon, and in the North Coast Ranges, Klamath-Siskiyou Mountains, and Sierra Nevada in California. Because of a lack of detections with standardized survey efforts over much of the fisher's historical range, the fisher is believed to be extirpated or reduced to scattered individuals from the lower mainland of British Columbia through Washington and northern Oregon and in the central and northern Sierra Nevada in California. Native extant populations of fisher are isolated to the North Coast of California, the Klamath-Siskiyou Mountains of northern California and southern Oregon, and the southern Sierra Nevada in California. Descendents of a fisher reintroduction effort also occur in the southern Cascades in Oregon. The Washington Department of Fish and Wildlife in conjunction with the Olympic National Park has completed the third year of a reintroduction effort as the State's first step in implementing their recovery goals for fisher. The California Department of Fish and Game and other collaborators are in the second year of their translocation efforts into the northern Sierra Nevada. Both of the reintroduction efforts still need several years to determine if populations are successfully established. Estimates of fisher numbers in native populations of the West Coast DPS vary widely. A rigorous monitoring program is lacking for the northern California-southwestern Oregon and southern Oregon Cascades populations, making estimates of fisher numbers for these two populations difficult. The fisher monitoring program in the southern Sierra Nevada population has provided preliminary estimates indicating no decline in the index of abundance within the monitored portion of the population. The two populations of native fisher in the northern California southern Oregon and southern Sierra Nevada are separated by four times the species' maximum dispersal distance. The extant fisher populations are either small (southern Sierra Nevada and southern Oregon Cascades) or isolated from one another or both.
                    </P>
                    <P>
                        Major threats that fragment or remove key elements of fisher habitat include various forest vegetation management practices such as timber harvest and fuels reduction treatments. Other potential major threats in portions of the range include: Large stand-replacing wildfires, changes in forest composition and structure related to the effects of climate change, forest and fuels management, and urban and rural development. Threats to fishers that lead to direct mortality and injury include: Collisions with vehicles; predation; rodenticides; and viral borne diseases such as rabies, parvovirus, and canine distemper. Existing regulatory mechanisms on Federal, State, and 
                        <PRTPAGE P="66389"/>
                        private lands do not provide sufficient protection for the key elements of fisher habitat, or the certainty that conservation efforts will be effective or implemented. The magnitude of threats is high as they occur across the range of the DPS resulting in negative impacts on fisher distribution and abundance. However, the threats are nonimminent as the greatest long-term risks to the fisher in its west coast range are the subsequent ramifications of the isolation of small populations and their interactions with the listed threats. Therefore, we assigned an LPN of 6 to this DPS.
                    </P>
                    <P>
                        New Mexico meadow jumping mouse (
                        <E T="03">Zapus hudsonius luteus</E>
                        )—The following summary is based on information contained in our files and the petition we received on October 15, 2008. The New Mexico meadow jumping mouse (jumping mouse) is endemic to New Mexico, Arizona, and a small area of southern Colorado. The jumping mouse nests in dry soils but uses moist, streamside, dense, riparian/wetland vegetation. Recent genetic studies confirm that the New Mexico meadow jumping mouse is a distinct subspecies from other 
                        <E T="03">Zapus hudsonius</E>
                         subspecies, confirming the currently accepted subspecies designation.
                    </P>
                    <P>The threats that have been identified are excessive grazing pressure, water use and management, highway reconstruction, development, recreation, and beaver removal.</P>
                    <P>Since the early to mid-1990s, over 100 historical localities have been surveyed. Currently only 25 are believed to be extant including 1 in Colorado, 11 in New Mexico (including one that is contiguous with another Colorado locality), and 13 in Arizona. Moreover, the highly fragmented nature of its distribution is also a major contributor to the vulnerability of this species and increases the likelihood of very small, isolated populations being extirpated. The insufficient number of secure populations, and the destruction, modification, or curtailment of its habitat, continue to pose the most immediate threats to this species. Because the threats affect the jumping mouse in all but two of the extant localities, and the populations are small and fragmented, the impact of the threats on the species is of high severity. Thus, the threats are of a high magnitude. These threats are currently occurring and, therefore, are imminent. Thus, we continue to assign an LPN of 3 to this subspecies.</P>
                    <P>
                        Mazama pocket gopher (
                        <E T="03">Thomomys</E>
                          
                        <E T="03">mazama</E>
                         ssp. 
                        <E T="03">couchi, douglasii,</E>
                          
                        <E T="03">glacialis, louiei,</E>
                          
                        <E T="03">melanops, pugetensis,</E>
                          
                        <E T="03">tacomensis, tumuli,</E>
                          
                        <E T="03">yelmensis</E>
                        ) — We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Canada lynx, within the State of New Mexico (
                        <E T="03">Lynx canadensis</E>
                        )—In our finding of December 17, 2009 (74 FR 66937), we determined that adding the lynx in New Mexico to the listing of the lynx DPS was warranted, because the lynx is now present in the state as a result of the Colorado reintroduction effort, and we assigned an LPN of 12 to amending the listing of lynx to include New Mexico. We reconfirm that assigning an LPN of 12 is appropriate based on nonimminent threats of a low magnitude. The threats to the lynx in New Mexico from human-caused mortality are low in magnitude, because they do not occur at a level that creates a significant threat to the lynx DPS in the contiguous United States. We do not consider lynx in New Mexico, or its habitat in New Mexico, to be essential to the survival or recovery of the DPS; as a result, neither human-caused mortality nor habitat modification in New Mexico occurs at a level such that it creates a significant threat to the lynx DPS in the contiguous United States. Potential impacts to the habitat in New Mexico have not been documented to threaten lynx, either in New Mexico or outside of it. The amount of suitable habitat for lynx in New Mexico is considered negligible relative to the amount of habitat within the listed range, and the majority of lynx habitats within the contiguous United States are already protected by the Act. The threats are also nonimminent, because they occur infrequently. Because lynx in the lower 48 are already listed as a DPS and conditions affecting the lynx in New Mexico are neither imminent nor of sufficient magnitude to pose a threat to the lynx DPS throughout the contiguous United States, the appropriate LPN for this level of magnitude and immediacy of threats is 12.
                    </P>
                    <P>
                        Gunnison's prairie dog (
                        <E T="03">Cynomys gunnisoni</E>
                        )—Gunnison's prairie dogs occur in Arizona, Colorado, New Mexico, and Utah. In our February 5, 2008, 12-month finding (73 FR 6660), we determined that listing the Gunnison prairie dog was warranted but precluded, with an LPN of 6, due to threats in a significant portion of its range—the montane portion of the species' range within Colorado and New Mexico—where the effects from plague and other factors threaten those populations. This finding was challenged by WildEarth Guardians in September of 2008. On September 30, 2010, the Court set aside our 2008 finding and remanded the matter back to us for further action. The Court found that we arbitrarily and capriciously “determined that something other than a species was an endangered or threatened species which warranted listing.”
                    </P>
                    <P>
                        In response to the decision of the Court, we will reevaluate the status of the Gunnison's prairie dog and deliver a revised 12-month finding to the 
                        <E T="04">Federal Register</E>
                        . However, we are currently unable to complete a status review due to budget and workload limitations. Furthermore, initiating a revised status review for the species would be premature at this time because of a significant ongoing genetics study initiated by the Colorado Division of Wildlife (CDOW) addressing Gunnison's prairie dog taxonomy. CDOW indicates preliminarily that this work strongly supports the existence of genetic differences between Gunnison's prairie dogs in the montane and prairie portions of its range indicating that they may constitute two putative subspecies. We anticipate the analysis of these data will likely be completed by the fall of 2011 and we will evaluate the information thereafter. It is critical for us to consider this potentially significant taxonomic revision in our revised status review after the CDOW releases its final genetics report. Gunnison's prairie dogs will remain a candidate within the montane portion of their range until we complete this analysis.
                    </P>
                    <P>
                        Southern Idaho ground squirrel (
                        <E T="03">Spermophilus brunneus</E>
                          
                        <E T="03">endemicus</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The southern Idaho ground squirrel is endemic to four counties in southwest Idaho; its total known range is approximately 426,000 hectares (1,050,000 acres). Threats to southern Idaho ground squirrels include: Habitat degradation and fragmentation; direct killing from shooting, trapping, or poisoning; predation; competition with Columbian ground squirrels; and inadequacy of existing regulatory mechanisms. Habitat degradation and fragmentation appear to be the primary threats to the species. Nonnative annuals now dominate much of this species' range, have changed the species composition of vegetation used as forage for the southern Idaho ground squirrel, and have altered the fire regime by accelerating the frequency of wildfire. Nonnative annuals do not provide 
                        <PRTPAGE P="66390"/>
                        consistent forage quality for southern Idaho ground squirrels as compared to the native vegetation. Habitat deterioration, destruction, and fragmentation contribute to the current patchy distribution of southern Idaho ground squirrels. However, some human-altered landscapes, such as golf courses and row crops of alfalfa, seem to provide habitat sufficient to maintain high densities of southern Idaho ground squirrels.
                    </P>
                    <P>Two candidate conservation agreements with assurances (CCAAs) have been completed for this species. Both CCAAs include conservation measures that minimize ground-disturbing activities, allow for the investigation of methods to restore currently degraded habitat, provide additional protection to southern Idaho ground squirrels from recreational shooting and other direct killing on enrolled lands, and also allow for the translocation of squirrels to or from enrolled lands, if necessary. The acreage enrolled through these two CCAAs is 38,000 ha (94,000 ac), or approximately 9 percent of the approximate known range. While the ongoing conservation efforts have helped to reduce the magnitude of threats to moderate, habitat degradation remains the primary threat to the species throughout most of its range. This threat is imminent due to the ongoing and increasing prevalence of nonnative vegetation, and the current patchy distribution of the species. Thus, we assign an LPN of 9 to this subspecies.</P>
                    <P>
                        Washington ground squirrel (
                        <E T="03">Spermophilus</E>
                          
                        <E T="03">washingtoni</E>
                        )—The following summary is based on information contained in our files and in the petition we received on March 2, 2000. The Washington ground squirrel is endemic to the Deschutes-Columbia Plateau sagebrush-steppe and grassland communities in eastern Oregon and south-central Washington. Although widely abundant historically, recent surveys suggest that its current range has contracted toward the center of its historical range. Approximately two-thirds of the Washington ground squirrel's total historical range has been converted to agricultural and residential uses. The most contiguous, least-disturbed expanse of suitable habitat within the species' range occurs on a site owned by Boeing, Inc., and on the Naval Weapons Systems Training Facility near Boardman, Oregon. In Washington, the largest expanse of known suitable habitat occurs on State and Federal lands.
                    </P>
                    <P>Agricultural, residential, and wind power development, among other forms of development, continue to eliminate Washington ground squirrel habitat in portions of its range. Throughout much of its range, Washington ground squirrels are threatened by the establishment and spread of invasive plant species, particularly cheatgrass, which alter available cover and food quantity and quality, and increase fire intervals. Additional threats include habitat fragmentation, recreational shooting, genetic isolation and drift, and predation. Potential threats include disease, drought, and possible competition with related species in disturbed habitat at the periphery of their range. In Oregon, some threats are being addressed as a result of the State listing of this species, and by implementation of the Threemile Canyon Farms Multi-Species CCAA. In Washington, there are currently no formal agreements with private landowners or with State or Federal agencies to protect the Washington ground squirrel. Additionally, no State or Federal management plans have been developed that specifically address the needs of the species or its habitat. Since current and potential threats are widespread, and, in some areas, severe, we conclude the magnitude of threats remains high. The Washington ground squirrel has both imminent and nonimminent threats. At a range-wide scale, we conclude the threats are nonimminent based largely on the following: The CCAA addressed the imminent loss of a large portion of habitat to agriculture; there are no other large-scale efforts to convert suitable habitat to agriculture; and wind power project impacts can be minimized through compliance with the Oregon State Endangered Species Act (OESA) and/or the Columbia Basin Ecoregion wind energy siting and permitting guidelines. We also consider the potential development of shooting ranges on the Naval Weapons Systems Training Facility as nonimminent, because the proposed action is still being developed, making us unable to assess its timing and impact, which could be minimized through compliance with the OESA. We, therefore, have retained an LPN of 5 for this species.</P>
                    <P>
                        North American wolverine, contiguous U.S. DPS (
                        <E T="03">Gulo gulo luscus</E>
                        )—The following summary is based on information contained in our files, in the petition received July 13, 2000 and in our initial warranted-but-precluded finding published in the 
                        <E T="04">Federal Register</E>
                         on December 14, 2010 (75 FR 78030). The wolverine is a terrestrial mammal that occurs in a wide variety of alpine, boreal, and arctic habitats. Wolverines naturally occur at low densities, and require cold areas that maintain deep, persistent snow cover into the warm season for successful denning. Within the contiguous United States, which constitutes a DPS, wolverine habitat is restricted to high-elevation areas in the West. Their current distribution includes functioning populations in the North Cascades Mountains and the northern Rocky Mountains, as well as populations that have not yet reestablished in the southern Rocky Mountains and the Sierra Nevada. The primary threat to this DPS is from habitat and range loss due to climate warming. Climate changes are predicted to reduce wolverine habitat and range by 23 percent over the next 30 years, and 63 percent over the next 75 years, rendering remaining habitat significantly smaller and more fragmented. This increased fragmentation and isolation of subpopulations is expected to limit the regular dispersal of wolverines that is necessary to maintain genetic exchange and metapopulation dynamics. Other secondary threats to the wolverine that could work in concert with climate change include harvest, disturbance, infrastructure, transportation corridors, and small effective population sizes. The primary threat of habitat and range loss due to climate change would affect wolverine habitat across the entire DPS and, therefore, the magnitude of threats to the wolverine is high. However climate change has not yet had a detectable effect on the DPS to this point in time; the threat is nonimminent. Therefore, we have assigned the wolverine contiguous U.S. DPS an LPN of 6.
                    </P>
                    <HD SOURCE="HD2">Birds</HD>
                    <P>
                        Spotless crake, American Samoa DPS (
                        <E T="03">Porzana tabuensis</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Porzana tabuensis</E>
                         is a small, dark, cryptic rail found in wetlands and rank scrub or forest in the Philippines, Australia, Fiji, Tonga, Society Islands, Marquesas, Independent Samoa, and American Samoa (Ofu, Tau). The genus 
                        <E T="03">Porzana</E>
                         is widespread in the Pacific, where it is represented by numerous island-endemic and flightless species (many of which are extinct as a result of anthropogenic disturbances) as well as several more cosmopolitan species, including 
                        <E T="03">P. tabuensis.</E>
                         No subspecies of 
                        <E T="03">P. tabuensis</E>
                         are recognized.
                    </P>
                    <P>
                        The American Samoa population is the only population of spotless crakes 
                        <PRTPAGE P="66391"/>
                        under U.S. jurisdiction. The available information indicates that distinct populations of the spotless crake, a species not noted for long-distance dispersal, are definable. The population of spotless crakes in American Samoa is discrete in relation to the remainder of the species as a whole, which is distributed in widely separated locations. Although the spotless crake (and other rails) have dispersed widely in the Pacific, island rails have tended to reduce or lose their power of flight over evolutionary time and so become isolated (and vulnerable to terrestrial predators such as rats). The population of this species in American Samoa is therefore distinct based on geographic and distributional isolation from spotless crake populations on other islands in the oceanic Pacific, the Philippines, and Australia. The American Samoa population of the spotless crake links the Central and Eastern Pacific portions of the species' range. The loss of this population would result in an increase of roughly 500 miles (805 kilometers) in the distance between the central and eastern Polynesian portions of the spotless crake's range, and could result in the isolation of the Marquesas and Society Islands populations by further limiting the potential for even rare genetic exchange. Based on the discreteness and significance of the American Samoa population of the spotless crake, we consider this population to be a distinct vertebrate population segment.
                    </P>
                    <P>
                        Threats to this population have not changed over the past year. The population in American Samoa is threatened by small population size, limited distribution, predation by nonnative and native animals, continued development of wetland habitat, and natural catastrophes such as hurricanes. The co-occurrence of a known predator of ground-nesting birds, the Norway rat (
                        <E T="03">Rattus norvegicus</E>
                        ), and native predators, including the Pacific boa (
                        <E T="03">Candoia bibroni</E>
                        ) and the purple swamphen (
                        <E T="03">Porphyrio porphyrio</E>
                        ), along with the extremely restricted observed distribution and low numbers, indicate that the magnitude of the threats to the American Samoa DPS of the spotless crake continues to be high, because the threats have a significant likelihood of bringing about extinction on a short time frame. The threats are ongoing, and therefore imminent. Based on this assessment of existing information about the imminence and high magnitude of these threats, we assigned the spotless crake an LPN of 3.
                    </P>
                    <P>
                        Yellow-billed cuckoo, western U.S. DPS (
                        <E T="03">Coccyzus americanus</E>
                        )—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Friendly ground-dove, American Samoa DPS (
                        <E T="03">Gallicolumba stairi</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The genus 
                        <E T="03">Gallicolumba</E>
                         is distributed throughout the Pacific and Southeast Asia. The genus is represented in the oceanic Pacific by six species: Three are endemic to Micronesian islands or archipelagos, two are endemic to island groups in French Polynesia; and 
                        <E T="03">G. stairi</E>
                         is endemic to Samoa, Tonga, and Fiji. Some authors recognize two subspecies of the friendly ground-dove, one, slightly smaller, in the Samoan archipelago (
                        <E T="03">G. s. stairi</E>
                        ); and one in Tonga and Fiji (
                        <E T="03">G. s.</E>
                          
                        <E T="03">vitiensis</E>
                        ). However, because morphological differences between the two are minimal, we are not recognizing separate subspecies at this time.
                    </P>
                    <P>
                        In American Samoa, the friendly ground-dove has been found on the islands of Ofu and Olosega (Manua Group). Threats to this subspecies have not changed over the past year. Predation by nonnative species and natural catastrophes such as hurricanes are the primary threats to the subspecies. Of these, predation by nonnative species is thought to be occurring now and likely has been occurring for several decades. This predation may be an important impediment to increasing the population. Predation by introduced species has played a significant role in reducing, limiting, and extirpating populations of island birds, especially ground-nesters like the friendly ground-dove, in the Pacific and other locations worldwide. Nonnative predators known or thought to occur in the range of the friendly ground-dove in American Samoa are feral cats (
                        <E T="03">Felis catus</E>
                        ), Polynesian rats (
                        <E T="03">Rattus exulans</E>
                        ), black rats (
                        <E T="03">R. rattus</E>
                        ), and Norway rats (
                        <E T="03">R. norvegicus</E>
                        ).
                    </P>
                    <P>
                        In January 2004 and February 2005, hurricanes virtually destroyed the habitat of 
                        <E T="03">G. stairi</E>
                         in the area on Olosega Island where the species had been most frequently recorded. Although this species has coexisted with severe storms for millennia, this example illustrates the potential for natural disturbance to exacerbate the effects of anthropogenic disturbance on small populations. Consistent monitoring using a variety of methods over the last 5 years yielded few observations and no change in the relative abundance of this taxon in American Samoa. The total population size is poorly known, but is unlikely to number more than a few hundred pairs. The distribution of the friendly ground-dove is limited to steep, forested slopes with an open understory and a substrate of fine scree or exposed earth; this habitat is not common in American Samoa. The threats are ongoing, and therefore imminent, and the magnitude is moderate because the relative abundance has remained the same for several years. Thus, we assign this subspecies an LPN of 9.
                    </P>
                    <P>
                        Streaked horned lark (
                        <E T="03">Eremophila</E>
                          
                        <E T="03">alpestris</E>
                          
                        <E T="03">strigata</E>
                        )—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Red knot (
                        <E T="03">Calidris canutus</E>
                          
                        <E T="03">rufa</E>
                        )—The following summary is based on information contained in our files and information provided by petitioners. Four petitions to emergency list the red knot have been received: one on August 9, 2004, two others on August 5, 2005, and the most recent on February 27, 2008. The 
                        <E T="03">rufa</E>
                         subspecies is one of six recognized subspecies of red knot and one of three subspecies occurring in North America. This subspecies makes one of the longest distance migrations known in the animal kingdom, as it travels between breeding areas in the central Canadian Arctic and wintering areas that are primarily in southern South America along the coast of Chile and Argentina. They migrate along the Atlantic coast of the United States, where they may be found from Maine to Florida.
                    </P>
                    <P>The Delaware Bay area (in Delaware and New Jersey) is the largest known spring migration stopover area, with far fewer migrants congregating elsewhere along the Atlantic coast. The concentration in the Delaware Bay area occurs from the middle of May to early June, corresponding to the spawning season of horseshoe crabs. The knots feed on horseshoe crab eggs, rebuilding energy reserves needed to complete migrations to the Arctic and arrive on the breeding grounds in good condition. In the past, horseshoe crab eggs at Delaware Bay were so numerous that a red knot could dependably eat enough in 2 to 3 weeks to double its weight.</P>
                    <P>
                        Surveys at wintering areas and at Delaware Bay during spring migration indicate a substantial decline in the red knot in recent years. At the Delaware Bay area, peak counts between 1982 and 1998 were as high as 95,360 individuals. 
                        <PRTPAGE P="66392"/>
                        Counts may vary considerably between years. Some of the fluctuations can be attributed to predator-prey cycles on the breeding grounds, and counts show that knots rebound from such reductions. Peak counts of red knots observed during aerial surveys flown in Delaware Bay from 2004 to 2008 were consistently below 16,000 birds, with an all time low of only 12,375 red knots found in 2007. In recent years, the highest concentrations of red knots at the Delaware Bay stopover have been within Mispillion Harbor, Delaware, an area that has likely been undercounted during past aerial surveys.
                    </P>
                    <P>Beginning in 2009, a new survey methodology was implemented for the Delaware Bay stopover area to include ground counts that more accurately reflect concentrations of red knots using Mispillion Harbor and to include aerial surveys of red knots using Atlantic coastal marshes near Stone Harbor, New Jersey. The highest count using the new methodology showed 27,187 red knots in Delaware and 900 in New Jersey, for a total count of 28,087 birds. Poor weather conditions in 2009 prevented aerial surveys during the period when red knots were thought to be at a peak, so no comparison with the past aerial survey peak count method was possible. While the number of red knots using Delaware Bay likely increased in 2009, much of the increase is attributed to improved survey methods and an expanded area of coverage. In 2010, the peak aerial count of red knots was 14,475; however, flight delays and scheduling issues prevented simultaneous aerial and ground counts, so aerial counts could not be calibrated. Further analysis is needed to correlate peak counts using the new methodology with the past aerial-survey-only counts.</P>
                    <P>Counts in recent years in South America also are substantially lower than in the past. In the mid-1980s, an estimated 67,500 red knots were observed from Tierra del Fuego, Chile, and along the coast of Argentina to northern Patagonia. Since 2003, the largest concentrations of red knots have occurred at the principal wintering areas in Bahia Lomas and other portions of Tierra del Fuego and southern Patagonia, with few birds found farther north along the coast of Argentina. More than 50,000 red knots were counted in the principal winter areas in 1985 and 2000. Since 2005, fewer than 18,000 have been counted within the same area, with only 16,260 red knots observed in 2010.</P>
                    <P>The primary threat to the red knot has been attributed to destruction and modification of its habitat, particularly the reduction in key food resources resulting from reductions in horseshoe crabs, which are harvested primarily for use as bait and secondarily to support a biomedical industry. Commercial harvest increased substantially in the 1990s. Research shows that, since 1998, a high proportion of red knots leaving the Delaware Bay failed to achieve threshold departure masses needed to fly to breeding grounds and survive an initial few days of snow cover, and this corresponded to reduced annual survival rates and reduced reproductive success. Since 1999, to protect the Atlantic coast population of the horseshoe crab and to increase availability of horseshoe crab eggs in Delaware Bay for hemispheric migratory shorebird populations, a series of timing restrictions and substantially lower harvest quotas have been adopted by the Atlantic States Marine Fisheries Commission, as well as by the States of New Jersey, Delaware, and Maryland. In March 2008, New Jersey passed legislation imposing a moratorium on horseshoe crab harvest or landing within the State until the red knot has fully recovered.</P>
                    <P>The reductions in commercial horseshoe crab harvest by Atlantic coastal States since 1999 are substantial. From 2004 to 2009, annual landings of horseshoe crabs have been reduced by over 70 percent from the reference period landings of the mid to late 1990s. For Delaware and New Jersey, horseshoe crab landings for bait have decreased from 726,660 reported in 1999, to a preliminary number of 102,659 in Delaware and none in New Jersey in 2009. No horseshoe crabs have been landed for bait in New Jersey since 2007, as a result of the State-imposed harvest moratorium. In the Delaware Bay area, continued recruitment of small horseshoe crabs has been observed, with a substantial increase in numbers of the smallest sizes of immature males and females in 2009 over previous years. The continued increase in immature males and females would be expected in a recovering population and suggests recent harvest restrictions may be having the desired effect, but it may be several more years until this increase is realized in spawning age adults, as horseshoe crabs need 8 to 10 years to reach sexual maturity.</P>
                    <P>Other identified threat factors include habitat destruction due to beach erosion and various shoreline protection and stabilization projects that are affecting areas used by migrating knots for foraging, the inadequacy of existing regulatory mechanisms, human disturbance, and competition with other species for limited food resources. Also, the concentration of red knots in the Delaware Bay areas and at a relatively small number of wintering areas makes the species vulnerable to potential large-scale events such as oil spills or severe weather. Overall, we conclude that the threats, in particular the modification of habitat through the effects, particularly of the past, harvesting of horseshoe crabs, are severe enough to put the viability of the red knot at substantial risk and are therefore of a high magnitude. The threats are currently occurring and therefore imminent because of continuing suppressed horseshoe-crab-egg forage conditions for the red knot within the Delaware Bay stopover. Based on imminent threats of a high magnitude, we retain an LPN of 3 for this species.</P>
                    <P>
                        Yellow-billed loon (
                        <E T="03">Gavia adamsii</E>
                        )—The following summary is based on information contained in our files and the petition we received on April 5, 2004. The yellow-billed loon is a migratory bird. Solitary pairs breed on lakes in the arctic tundra of the United States, Russia, and Canada from June to September. During the remainder of the year, the species winters in more southern coastal waters of the Pacific Ocean and the Norway and North Seas.
                    </P>
                    <P>
                        During most of the year, individual yellow-billed loons are so widely dispersed that high adult mortality from any single factor is unlikely. However, during migration, yellow-billed loons are more concentrated, and hundreds are likely subject to subsistence harvest, based on the best available information; the population could decline substantially if such harvest continues. Future subsistence harvest in Alaska, by itself, constitutes a threat to the species rangewide. This subsistence harvest is occurring despite the species being closed to hunting under the Migratory Bird Treaty Act (16 U.S.C. 703-712). In addition, up to several hundred yellow-billed loons may be taken annually on Russian breeding grounds, and small numbers of yellow-billed loons may be taken in Canada. Other risk factors evaluated were found to be threats to the species; these included oil and gas development (i.e., disturbance, changes in freshwater chemistry and pollutant loads, and changes in freshwater hydrology); pollution; overfishing; climate change; vessel traffic; commercial- and subsistence-fishery bycatch; and contaminants other than those associated with oil and gas. Although these other risk factors may not rise to the level of a threat individually, when taken collectively with the effects of subsistence hunting in other areas, they may reduce the rangewide population even further. The 
                        <PRTPAGE P="66393"/>
                        primary threat of subsistence harvest is currently occurring and one or more of the threats discussed above is occurring throughout the range of the yellow-billed loon, either in its breeding or wintering grounds, or during migration; therefore, the threats are imminent. The magnitude of the primary threat to the species, subsistence harvest, is moderate. Although subsistence harvest is ongoing, the numbers taken have varied substantially between years; however, we have concerns about the accuracy and precision of the numbers reported in harvest surveys. Thus, we assigned the yellow-billed loon an LPN of 8.
                    </P>
                    <P>
                        Kittlitz's murrelet (
                        <E T="03">Brachyramphus brevirostris</E>
                        )—See above in “Listing Priority Changes in Candidates.” The above summary is based on information contained in our files.
                    </P>
                    <P>
                        Xantus's murrelet (
                        <E T="03">Synthliboramphus hypoleucus</E>
                        )—The following summary is based on information contained in our files and the petition we received on April 16, 2002. The Xantus's murrelet is a small seabird in the family Alcidae that occurs along the west coast of North America in the United States, Mexico, and Canada. The species has a limited breeding distribution, only nesting on the Channel Islands in southern California and on islands off the west coast of Baja California, Mexico. Although data on population trends are scarce, the population is suspected to have declined greatly over the last century, mainly due to predators such as rats (
                        <E T="03">Rattus</E>
                         sp.) and feral cats (
                        <E T="03">Felis catus</E>
                        ) introduced to nesting islands, with possible extirpations on three islands in Mexico. A dramatic decline (up to 70 percent) from 1977 to 1991 was detected at the largest nesting colony in southern California, possibly due to high levels of predation on eggs by the endemic deer mouse (
                        <E T="03">Peromyscus maniculatus elusus</E>
                        ). Identified threats include introduced predators at nesting colonies, oil spills and oil pollution, reduced prey availability, human disturbance, and artificial light pollution.
                    </P>
                    <P>Although substantial declines in the Xantus's murrelet population likely occurred over the last century, some of the largest threats are being addressed, and, to some degree, ameliorated. Declines and possible extirpations at several nesting colonies were thought to have been caused by nonnative predators, which have been removed from many of the islands where they once occurred. Most notably, since 1994, Island Conservation and Ecology Group has systematically removed rats, cats, and dogs from every murrelet nesting colony in Mexico, with the exception of cats and dogs on Guadalupe Island. In 2002, rats were eradicated from Anacapa Island in southern California, which has resulted in improvements in reproductive success at that island. In southern California, efforts to restore nesting habitat on Santa Barbara Island through the Montrose Settlements Restoration Project may benefit the Xantus's murrelet population at that island.</P>
                    <P>
                        Artificial lighting from squid fishing and other vessels, or lights on islands, remains a potential threat to the species. Bright lights make Xantus's murrelets more susceptible to predation, and they can also become disoriented and exhausted from continual attraction to bright lights. Chicks can become disoriented and separated from their parents at sea, which could result in death of the dependent chicks. High-wattage lights on commercial market squid (
                        <E T="03">Loligo opalescens</E>
                        ) fishing vessels used at night to attract squid to the surface of the water in the Channel Islands was the suspected cause of unusually high predation on Xantus's murrelets by western gulls (
                        <E T="03">Larus occidentalis</E>
                        ) and barn owls (
                        <E T="03">Tyto alba</E>
                        ) at Santa Barbara Island in 1999. To address this threat, in 2000, the California Fish and Game Commission required light shields and a limit of 30,000 watts per boat; it is unknown if this is sufficient to reduce impacts. Since 1999, no significant squid fishing has occurred near any of the colonies in the Channel Islands; however, this remains a potential future threat.
                    </P>
                    <P>A proposal to build three liquid natural gas facilities near the Channel Islands could affect the nesting colonies due to bright lights at night from the facility and visiting tanker vessels, noise from the facilities or from helicopters visiting the facilities, and the threat of oil spills associated with visiting tanker vessels. However, these facilities are early in the complex and long-term planning processes, and it is possible that none of these facilities will be built. In addition, none of them is directly adjacent to nesting colonies, where the impacts would be expected to be more significant. The remaining threats to the species are of a high magnitude, because they have the potential to compromise the only nesting areas for the species. However, because the liquid natural gas facilities are early in the planning process and may not be completed and currently, little squid fishing vessels occurs near the nesting colonies, the threats are nonimminent. Therefore, we retained a LPN of 5 for this species.</P>
                    <P>
                        Sprague's pipit (
                        <E T="03">Anthus spragueii</E>
                        ) —See above in “Listing Priority Changes in Candidates.” The above summary is based on information contained in our files.
                    </P>
                    <P>
                        Lesser prairie-chicken (
                        <E T="03">Tympanuchus pallidicinctus</E>
                        )—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Gunnison sage-grouse (
                        <E T="03">Centrocercus minimus</E>
                        )—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Greater sage-grouse (
                        <E T="03">Centrocercus urophasianus)</E>
                        —The following summary is based on information in our files and in the petition we received on January 30, 2002. Currently, greater sage-grouse occur in 11 States (Washington, Oregon, California, Nevada, Idaho, Montana, Wyoming, Colorado, Utah, South Dakota, and North Dakota), and 2 Canadian provinces (Alberta and Saskatchewan), occupying approximately 56 percent of their historical range. Greater sage-grouse depend on a variety of shrub-steppe habitats throughout their life cycle, and are considered obligate users of several species of sagebrush. The primary threat to greater sage-grouse is ongoing fragmentation and loss of shrub-steppe habitats through a variety of mechanisms. Most importantly, increasing fire cycles and invasive plants (and the interaction between them) in more westerly parts of the range, along with energy development and related infrastructure in more easterly areas are negatively affecting species' persistence. In addition, direct loss of habitat and fragmentation is occurring due to agriculture, urbanization, and infrastructure such as roads and power lines built in support of several activities. We also have determined that existing regulatory mechanisms are inadequate to protect the species from these ongoing threats. However, many of these habitat impacts are being actively addressed through conservation actions taken by local working groups, and State and Federal agencies. Notably, the National Resource Conservation Service has committed significant financial and technical resources to address threats to this species on private lands through their Sage-grouse Initiative. These efforts, when fully implemented, will potentially provide important conservation benefits to the greater sage-
                        <PRTPAGE P="66394"/>
                        grouse and its habitats. We consider the threats to the greater sage-grouse to be of moderate magnitude, because the threats are not occurring with uniform intensity or distribution across the wide range of the species at this time, and substantial habitat still remains to support the species in many areas. The threats are imminent because the species is currently facing them in many portions of its range. Therefore, we assigned the greater sage-grouse an LPN of 8.
                    </P>
                    <P>
                        Greater sage-grouse, Bi-State DPS (
                        <E T="03">Centrocercus urophasianus</E>
                        ) — We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Greater sage-grouse, Columbia Basin DPS (
                        <E T="03">Centrocercus urophasianus</E>
                        )—The following summary is based on information in our files and a petition, dated May 14, 1999, requesting the listing of the Washington population of the western sage-grouse (
                        <E T="03">C. u. phaios</E>
                        ). On May 7, 2001, we concluded that listing the Columbia Basin DPS of the western sage-grouse was warranted, but precluded by higher priority listing actions (66 FR 22984); this population was historically found in northern Oregon and central Washington. Following our May 7, 2001, finding, the Service received additional petitions requesting listing actions for various other greater sage-grouse populations, including one for the nominal western subspecies, dated January 24, 2002, and three for the entire species, dated June 18, 2002, and March 19 and December 22, 2003. The Service subsequently found that the petition for the western subspecies did not present substantial information (68 FR 6500; February 7, 2003), and that listing the greater sage-grouse throughout its historical range was not warranted (70 FR 2244; January 12, 2005). These two findings were challenged, and remanded to the Service for further consideration. In response, we initiated a new rangewide status review for the entire species (73 FR 10218; February 26, 2008). On March 5, 2010, we found that listing of the greater sage-grouse was warranted but precluded by higher priority listing actions (75 FR 13910; March 23, 2010), and it was added to the list of candidates. We also found that the western subspecies of the greater sage-grouse, the taxonomic entity on which we based our DPS analysis for the Columbia Basin population, was no longer considered a valid subspecies. In light of our conclusions regarding the invalidity of the western sage-grouse subspecies, we will now need to analyze the significance of the Columbia Basin DPS to the greater sage-grouse. As priorities allow, the Service intends to complete an analysis to determine if this population continues to warrant recognition as a DPS in accordance with our Policy Regarding the Recognition of Distinct Vertebrate Population Segments (61 FR 4722; February 7, 1996). Until that time, the Columbia Basin DPS will remain a candidate for listing as a separate population of sage-grouse. Even if this population does not meet our DPS policy, the sage-grouse population in the Columbia Basin will remain a candidate for listing as part of the process for listing the greater sage-grouse entity.
                    </P>
                    <P>
                        Band-rumped storm-petrel, Hawaii DPS (
                        <E T="03">Oceanodroma castro</E>
                        )—The following summary is based on information contained in our files and the petition we received on May 8, 1989. No new information was provided in the second petition received on May 11, 2004. The band-rumped storm-petrel is a small seabird that is found in several areas of the subtropical Pacific and Atlantic Oceans. In the Pacific, there are three widely separated breeding populations: one in Japan, one in Hawaii, and one in the Galapagos. Populations in Japan and the Galapagos are comparatively large and number in the thousands, while the Hawaiian birds represent a small, remnant population of possibly only a few hundred pairs. Band-rumped storm-petrels are most commonly found in close proximity to breeding islands. The three populations in the Pacific are separated by long distances across the ocean where birds are not found. Extensive at-sea surveys of the Pacific have revealed a broad gap in distribution of the band-rumped storm-petrel to the east and west of the Hawaiian Islands, indicating that the distribution of birds in the central Pacific around Hawaii is disjunct from other nesting areas. The available information indicates that distinct populations of band-rumped storm-petrels are definable and that the Hawaiian population is distinct based on geographic and distributional isolation from other band-rumped storm-petrel populations in Japan, the Galapagos, and the Atlantic Ocean. A population also can be considered discrete if it is delimited by international boundaries that have differences in management control of the species. The Hawaiian population of the band-rumped storm-petrel is the only population within U.S. borders or under U.S. jurisdiction. Loss of the Hawaiian population would cause a significant gap in the distribution of the band-rumped storm-petrel in the Pacific, and could result in the complete isolation of the Galapagos and Japan populations without even occasional genetic exchanges. Therefore, the population is both discrete and significant, and constitutes a DPS.
                    </P>
                    <P>
                        The band-rumped storm-petrel probably was common on all of the main Hawaiian Islands when Polynesians arrived about 1,500 years ago, based on storm-petrel bones found in middens on the island of Hawaii and in excavation sites on Oahu and Molokai. Nesting colonies of this species in the Hawaiian Islands currently are restricted to remote cliffs on Kauai and Lehua Island and high-elevation lava fields on Hawaii. Vocalizations of the species were heard in Haleakala Crater on Maui as recently as 2006; however, no nesting sites have been located on the island to date. The significant reduction in numbers and range of the band-rumped storm-petrel is due primarily to predation by nonnative predators introduced by humans, including the domestic cat (
                        <E T="03">Felis catus</E>
                        ), small Indian mongoose (
                        <E T="03">Herpestes auropunctatus</E>
                        ), common barn owl (
                        <E T="03">Tyto alba</E>
                        ), black rat (
                        <E T="03">Rattus rattus</E>
                        ), Polynesian rat (
                        <E T="03">R. exulans</E>
                        ), and Norway rat (
                        <E T="03">R. norvegicus</E>
                        ), which occur throughout the main Hawaiian Islands, with the exception of the mongoose, which is not established on Kauai. Attraction of fledglings to artificial lights, which disrupts their night-time navigation, resulting in collisions with building and other objects, and collisions with artificial structures such as communication towers and utility lines are also threats. Erosion of nest sites caused by the actions of nonnative ungulates is a potential threat in some locations. Efforts are under way in some areas to reduce light pollution and mitigate the threat of collisions, but there are no large-scale efforts to control nonnative predators in the Hawaiian Islands. The threats are imminent because they are ongoing, and they are of a high magnitude because they can severely affect the survival of this DPS throughout its range, leading to a relatively high likelihood of extinction. Therefore, we assign this distinct population segment an LPN of 3.
                    </P>
                    <P>
                        Elfin-woods warbler (
                        <E T="03">Dendroica angelae</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Dendroica angelae,</E>
                         or elfin-woods warbler, is a small, entirely black and white warbler, distinguished by its white eyebrow stripe, white patches on 
                        <PRTPAGE P="66395"/>
                        ear covers and neck, incomplete eye ring, and black crown. The elfin-woods warbler was at first thought to occur only in high elevations at dwarf or elfin forests, but it has since been found at lower elevations including shade coffee plantations and secondary forests. These birds build a compact cup nest, usually close to the trunk and well hidden among the epiphytes of small trees. Its breeding season extends from March to June. Elfin-woods warblers forage in the middle part of trees, gleaning insects from leaves in the outer portion of tree crowns. The species has been documented from four locations in Puerto Rico: Luquillo Mountains, Sierra de Cayey, and the Commonwealth forests of Maricao and Toro Negro. However, it has not been recorded again in Toro Negro and Sierra de Cayey, following the passing of Hurricane Hugo in 1989. In 2003 and 2004, surveys were conducted for the elfin-woods warbler in the Carite Commonwealth Forest, Toro Negro Forest, Guilarte Forest, Bosque del Pueblo, Maricao Forest and the El Yunque National Forest. These surveys only reported sightings at Maricao Commonwealth Forest (778 individuals), and El Yunque National Forest (196 individuals).
                    </P>
                    <P>
                        The elfin-woods warbler is potentially threatened by habitat modification. Elfin-woods warblers have been historically common in the elfin woodland of El Yunque National Forest and the 
                        <E T="03">Podocarpus</E>
                         forest type of Maricao Commonwealth Forest. Removal and replacement of this forest vegetation with infrastructure (e.g., telecommunication towers, recreational facilities) may have impacted the species in the past. Although this loss of habitat has been permanent and restoration process would take a few decades, present regulatory process at both the Commonwealth and Federal levels have reduced this threat. Unrestricted development within the El Yunque buffer zone needs to be addressed to determine the impact on the migratory behavior of the species. Conversion of elfin-woods warbler habitat (e.g., mature secondary forests, young secondary forests, and shaded-coffee plantations) along the periphery of the Maricao Commonwealth Forest to marginal habitat (e.g., pastures, dry slope forests, residential rural forests, gallery forests, and unshaded coffee plantations), has affected potential corridors for the elfin-woods warbler, resulting in a reduced dispersal and expansion capability of the species. These threats are not imminent because most of the range of the species is within protected lands. The magnitude of threat to 
                        <E T="03">Dendroica angelae</E>
                         is low to moderate because there is no indication that the two populations of the elfin-woods warbler are declining in numbers. The species can thrive in disturbed and plantation habitats, although abundance of the species on these habitats is lower than in primary habitats. Moreover, elfin-woods warblers appear to recover well, and in a relatively short time, from damaging effects of hurricanes to the forest structure. Therefore, we assign a listing priority number of 11 to 
                        <E T="03">Dendroica angelae.</E>
                    </P>
                    <HD SOURCE="HD2">Reptiles</HD>
                    <P>
                        Northern Mexican Gartersnake (
                        <E T="03">Thamnophis eques megalops</E>
                        )—The following summary is based on information contained in our files. The northern Mexican gartersnake generally occurs in three types of habitat: (1) Ponds and cienegas; (2) lowland river riparian forests and woodlands; and (3) upland stream gallery forests. Within the United States, the distribution of the northern Mexican gartersnake has been reduced by close to 90 percent, and it occurs in fragmented populations within the middle and upper Verde River drainage, middle and lower Tonto Creek, and the upper Santa Cruz River, as well as in a small number of isolated wetland habitats in southeastern Arizona; its status in New Mexico is uncertain. Within Mexico, the northern Mexican gartersnake is distributed along the Sierra Madre Occidental and the Mexican Plateau in the Mexican States of Sonora, Chihuahua, Durango, Coahila, Zacatecas, Guanajuato, Nayarit, Hidalgo, Jalisco, San Luis Potosí, Aguascalientes, Tlaxacala, Puebla, México, Michoacán, Oaxaca, Veracruz, and Querétaro. The primary threat to the northern Mexican gartersnake is competition and predation from nonnative species such as sportfish, bullfrogs, and crayfish. Degradation and elimination of its habitat and native prey base are also significant threats, most notably in areas where nonnative species co-occur. Threats, particularly competition and predation by nonnative species, are high in magnitude because they result in direct mortality or reduced reproductive capacity and may be irreversible in complex habitat. The threats are ongoing and, therefore, imminent. Thus, we retained an LPN of 3 for this subspecies.
                    </P>
                    <P>
                        Eastern massasauga rattlesnake (
                        <E T="03">Sistrurus catenatus</E>
                        )—See above in “Listing Priority Changes in Candidates.” The above summary is based on information contained in our files.
                    </P>
                    <P>
                        Black pine snake (
                        <E T="03">Pituophis melanoleucus lodingi</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. There are historical records for the black pine snake from one parish in Louisiana, 14 counties in Mississippi, and 3 counties in Alabama west of the Mobile River Delta. Black pine snake surveys and trapping indicate that this species has been extirpated from Louisiana and from four counties in Mississippi. Moreover, the distribution of remaining populations has become highly restricted due to the destruction and fragmentation of the remaining longleaf pine habitat within the range of the subspecies. Most of the known Mississippi populations are concentrated on the DeSoto National Forest. In Alabama, populations occurring on properties managed by State and other governmental agencies, as gopher tortoise mitigation banks or wildlife sanctuaries, represent the best opportunities for long-term survival of the subspecies there. Other factors affecting the black pine snake include vehicular mortality and low reproductive rates, which magnify the threats from destruction and fragmentation of longleaf pine habitat and increase the likelihood of local extinctions. Due to the imminent threats of high magnitude caused by the past destruction of most of the longleaf pine habitat of the black pine snake, and the continuing persistent degradation of the habitat that remains, we assigned an LPN of 3 to this subspecies.
                    </P>
                    <P>
                        Louisiana pine snake (
                        <E T="03">Pituophis ruthveni</E>
                        )—The following summary is based on information contained in our files and the petition we received on July 20, 2000, and updated through April 30, 2011. The Louisiana pine snake historically occurred in the fire-maintained longleaf pine ecosystem within west-central Louisiana and extreme east-central Texas. The historic and ongoing loss of potential habitat (via fire suppression, conversion to pine plantations, increases in the number and width of roads, and urbanization) on private lands in the matrix between these extant populations reduces the potential for dispersal among remnant populations and the potential for natural re-colonization of vacant suitable habitat patches. The primary threats coupled with the disruption of natural fire regimes have reduced the Louisiana pine snake to seven isolated populations. Several of these remnant populations may be vulnerable to factors associated with low population 
                        <PRTPAGE P="66396"/>
                        sizes and demographic isolation such as reduced genetic heterozygosity. Because it is unlikely that corridors linking extant populations will be established, the loss of any extant population is likely to be permanent. Additional threats that may occur even within quality Louisiana pine snake habitat include mortality from on- and off-road mortality, entanglement in erosion control devices installed in rights-of-way, and intentional killing. Finally, the Louisiana pine snake has an extremely low reproductive rate, thereby magnifying the effects of the above listed threats. Currently occupied habitat in Louisiana and Texas is estimated to be approximately 163,000 acres, with 53 percent occurring on public lands and 47 percent in private ownership.
                    </P>
                    <P>Louisiana pine snake populations on Federal lands have received increased management attention (via prescribed burning and thinning) in recent years, and as a result, the successional degradation of occupied and potential habitat within these populations has been stabilized or reversed. Nonetheless, not all areas of occupied habitat on Federal lands have received recent prescribed burning, and in the absence of adequate burning, Louisiana pine snake habitat becomes degraded via vegetative succession. The largest and perhaps most important extant Louisiana pine snake population exists on private industrial timberland. Although two conservation areas are managed to benefit Louisiana pine snakes on this property, the majority of the occupied habitat between the conservation areas is threatened by land management activities (habitat conversion to short-rotation pine plantations) that are expected to decrease habitat quality. The candidate conservation agreement (CCA) for the Louisiana pine snake which includes the Service, U.S. Forest Service, Department of Defense, Texas Parks and Wildlife, and Louisiana Department of Wildlife was completed in 2003, and is currently being implemented. The CCA is designed to identify and establish management for the Louisiana pine snake on Federal lands in Louisiana and Texas, and provides a means for the partnering agencies to work cooperatively on projects that avoid and minimize impacts to the snake. It also sets up a mechanism to exchange information on successful management practices and coordinate research efforts.</P>
                    <P>In 2001, the Service provided funds, through the Private Stewardship Grant Program, to a private landowner for habitat restoration and prescribed burning on several tracts of their Bienville Parish property containing a known Louisiana pine snake population. A habitat management plan for those sites was developed, and in August of 2005, that landowner was awarded a grant for continued habitat improvement on that same property. Subsequently, that property has been transferred to a new landowner. Through the use of those grant funds and voluntary investment, those private landowners have converted lands to longleaf pine within those Core Management Areas and completed prescribed burning.</P>
                    <P>The Louisiana Pine Snake Conservation Group consists of representatives from a variety of organizations having an interest in Louisiana pine snake conservation and includes approximately 90 individuals representing State and Federal government, non-profit and private organizations, zoos, academia, and private landowners. This group has been holding annual stakeholder meetings since 2003. At those meetings, stakeholders discuss issues and threats to the Louisiana pine snake, identify possible strategies to deal with those threats, report on land management activities beneficial to stability or recovery, and discuss and share successful results. Five significant actions have resulted from cooperative efforts of this group's members: (1) Completion of a threats assessment; (2) development and completion of a landscape—scaled resources selection function model; (3) training and experimental testing of a scent dog to assist in survey efforts; (4) initiation of an experimental captive breeding and reintroduction program; and (5) initiation of a DNA microsatellite study that will help define genetic structure among populations.</P>
                    <P>While the extent of Louisiana pine snake habitat loss has been great in the past and much of the remaining habitat has been degraded, habitat loss does not represent an imminent threat, primarily because the rate of habitat loss appears to be declining on public lands. However, all populations require active habitat management, and the lack of adequate habitat remains a threat for several populations. The potential threats to a large percentage of extant Louisiana pine snake populations, coupled with the likely permanence of these effects and the species' low fecundity and low population sizes, lead us to conclude that the threats have significant effects on the survival of the species and therefore remain high in magnitude. Thus, based on nonimminent, high-magnitude threats, we assign a LPN of 5 to this species. We find that listing this species is warranted throughout all its range.</P>
                    <P>
                        Tucson shovel-nosed snake (
                        <E T="03">Chionactis occipitalis klauberi</E>
                        )—The Tucson shovel-nosed snake is a small, burrowing snake in the Colubridae family that occupied a roughly 35-mile-wide swath running along the Phoenix-Tucson corridor in northeastern Pima, southwestern Pinal, and eastern Maricopa Counties, Arizona. No systematic surveys have been conducted to assess the status of the subspecies throughout its range, but it has apparently disappeared from some areas.
                    </P>
                    <P>Threats to the Tucson shovel-nosed snake include urban and rural development; road construction, use, and maintenance; concentration of solar power facilities and transmission corridors; agriculture; wildfires; and lack of adequate management and regulation. Comprehensive plans encompassing the entire range of the snake encourage large growth areas in the next 20 years and beyond. These plans also call for an increase in roads and transportation corridors, which have been documented to affect the snake through direct mortality. Additionally, development of solar energy facilities and transmission corridors throughout the State is being pursued, and demand for these facilities will likely increase. Some of these facilities are being considered within the range of the Tucson shovel-nosed snake. Wildfires due to infestations of nonnative grasses in the snake's habitat, dominated by native plants not adapted to survive wildfires, are likely to increase in frequency and magnitude in the future as these invasive grasses continue to spread rapidly. Regulations are not in place to minimize or mitigate these threats to the Tucson shovel-nosed snake and its habitat, and, therefore, they are likely to put the snake at risk of local extirpation or extinction. These threats, particularly those that lead to a loss of habitat, are likely to reduce the population of the Tucson shovel-nosed snake across its entire range. Given the limited geographic distribution of this snake and the fact that its entire range lies within the path of development in the foreseeable future, these threats are of high magnitude and are imminent. Accordingly, we have assigned an LPN of 3 for the Tucson shovel-nosed snake.</P>
                    <P>
                        Desert tortoise, Sonoran DPS (
                        <E T="03">Gopherus agassizii</E>
                        )—The following summary is based on information contained in our files. Sonoran desert tortoises are most closely associated with Sonoran and Mojave desertscrub vegetation types, but may also be found 
                        <PRTPAGE P="66397"/>
                        in other habitat types within their distribution and elevation range. They occur most commonly on rocky, steep slopes and bajadas in paloverde-mixed cacti associations. Washes and valley bottoms may be used in dispersal and, in some areas, as all or part of home ranges. Most Sonoran desert tortoises in Arizona occur between 904 to 4,198 feet (275 to 1280 meters) in elevation. The Sonoran desert tortoise is distributed south and east of the Colorado River in Arizona in all counties except for Navajo, Apache, Coconino, and Greenlee Counties, south to the Rio Yaqui in southern Sonora, Mexico. A recently published paper on the genetics of desert tortoise indicates this population should be treated as a separate species. We will be analyzing this new information, and will make any necessary changes to the nomenclature and LPN in the next candidate notice.
                    </P>
                    <P>Threats include nonnative plant species invasions and altered fire regimes; urban and agricultural development, and human population growth; barriers to dispersal and genetic exchange; off-highway vehicles; roads and highways; historical ironwood and mesquite tree harvest in Mexico; improper livestock grazing (predominantly in Mexico); undocumented human immigration and interdiction activities; illegal collection; predation from feral dogs; human depredation and vandalism; drought; and climate change. Threats to the Sonoran desert tortoise differ geographically and are highly synergistic in their effects on the population. The threats identified to affect the Sonoran desert tortoise currently or in the foreseeable future are of high magnitude but, overall, are nonimminent. Therefore, we assigned an LPN of 6 to this population of desert tortoise.</P>
                    <P>
                        Sonoyta mud turtle (
                        <E T="03">Kinosternon sonoriense longifemorale</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The Sonoyta mud turtle occurs in a spring and pond at Quitobaquito Springs on Organ Pipe Cactus National Monument in Arizona, and in the Rio Sonoyta and Quitovac Spring of Sonora, Mexico. Loss and degradation of stream habitat from water diversion and groundwater pumping, along with its very limited distribution, are the primary threats to the Sonoyta mud turtle. Sonoyta mud turtles are highly aquatic and depend on permanent water for survival. The area of southwest Arizona and northern Sonora where the Sonoyta mud turtle occurs is one of the driest regions in the Southwest. Due to continued drought, irrigated agriculture, and development in the region, surface water in the Rio Sonoyta can be expected to dwindle further and therefore have a significant impact on the survival of this subspecies, which may also be vulnerable to aerial spraying of pesticides on nearby agricultural fields. We retained an LPN of 3 for this subspecies because threats are of a high magnitude and continue to date, and therefore are imminent.
                    </P>
                    <HD SOURCE="HD2">Amphibians</HD>
                    <P>
                        Columbia spotted frog, Great Basin DPS (
                        <E T="03">Rana luteiventris</E>
                        )—The following summary is based on information contained in our files and the petition we received on May 1, 1989. Currently, Columbia spotted frogs appear to be widely distributed throughout southwestern Idaho, southeastern Oregon, and northeastern and central Nevada, but local populations within this general area appear to be small and isolated from each other. Recent work by researchers in Idaho and Nevada have documented the loss of historically known sites, reduced numbers of individuals within local populations, and declines in the reproduction of those individuals.
                    </P>
                    <P>Small, highly fragmented populations, characteristic of the majority of existing populations of Columbia spotted frogs in the Great Basin, are highly susceptible to extinction processes. Threats to Columbia spotted frog include poor management of habitat including water development, improper grazing, mining activities, and nonnative species, all of which have contributed, and continue to contribute, to the degradation and fragmentation of habitat. Emerging fungal diseases, such as chytridiomycosis, and the spread of parasites may be contributing factors to Columbia spotted frog's population declines throughout portions of its range. Effects of climate change, such as drought, and stochastic events, such as fire, often have detrimental effects to small, isolated populations and can often exacerbate existing threats. A 10-year conservation agreement and strategy was signed in September 2003 for both the Northeast and the Toiyabe subpopulations in Nevada. The goals of the conservation agreements are to reduce threats to Columbia spotted frogs and their habitat to the extent necessary to prevent populations from becoming extirpated throughout all or a portion of their historical range and to maintain, enhance, and restore a sufficient number of populations of Columbia spotted frogs and their habitat to ensure their continued existence throughout their historical range. Additionally, a candidate conservation agreement with assurances was completed in 2006, for the Owyhee subpopulation at Sam Noble Springs, Idaho. Several habitat enhancement projects have been conducted throughout the range that have benefitted these populations. We conclude that the threats are of moderate magnitude, because the DPS is still widely distributed, and several regulatory mechanisms are benefitting the populations and working to reduce threats. Based on imminent threats of moderate magnitude, we assigned an LPN of 9 to this DPS of the Columbia spotted frog.</P>
                    <P>
                        Mountain yellow-legged frog, Sierra Nevada DPS (
                        <E T="03">Rana muscosa</E>
                        )—The following summary is based on information contained in our files and the petition received on February 8, 2000. Also see our 12-month petition finding published on January 16, 2003 (68 FR 2283) and our amended 12-month petition finding published on June 25, 2007 (72 FR 34657). The mountain yellow-legged frog inhabits the high elevation lakes, ponds, and streams in the Sierra Nevada Mountains of California, from near 4,500 feet (ft) (1,370 meters (m)) to 12,000 ft (3,650 m). The distribution of the mountain yellow-legged frog is from Butte and Plumas Counties in the north to Tulare and Inyo Counties in the south. A separate population in southern California is already listed as endangered (67 FR 44382; July 2, 2002). Based on mitochondrial DNA, morphological, and acoustic studies, Vredenburg 
                        <E T="03">et al.</E>
                         recently recognized two distinct species of mountain yellow-legged frog in the Sierra Nevada, 
                        <E T="03">R. muscosa</E>
                         and 
                        <E T="03">R. sierrae.</E>
                         This taxonomic distinction has been recently adopted by the American Society of Ichthyologists and Herpetologists, the Herpetologists' League, and the Society for the Study of Amphibians and Reptiles. The Vredenburg study determined that two species exist, as described by Camp in 1917, but have different geographical ranges than first described. Camp described 
                        <E T="03">R. muscosa</E>
                         as only occurring in southern California. A recent study determined that 
                        <E T="03">R. muscosa</E>
                         also occurs in the southern portion of the Sierra Nevada and that 
                        <E T="03">R. sierrae</E>
                         occurs both in the southern and northern portions of the Sierra Nevada with no range overlap. We accept the taxonomic distinction of two species, and the taxonomic split between the mountain yellow-legged frogs in the northern and central Sierra Nevada Mountains of California (
                        <E T="03">Rana sierrae</E>
                        ) 
                        <PRTPAGE P="66398"/>
                        and the mountain yellow-legged frogs in the southern Sierra Nevada and the mountains of southern California (
                        <E T="03">R. muscosa</E>
                        ) and we intend to propose this taxonomic change in a proposed rule. In the interim, we continue to recognize all mountain yellow-legged frogs in the Sierra Nevada Mountains of California as 
                        <E T="03">R. muscosa</E>
                         and as the candidate entity.
                    </P>
                    <P>Predation by introduced trout is the best-documented cause of the decline of the Sierra Nevada mountain yellow-legged frog, because it has been repeatedly observed that fishes and mountain yellow-legged frogs rarely co-exist. Mountain yellow-legged frogs and trout (native and nonnative) do co-occur at some sites, but these co-occurrences probably are mountain yellow-legged frog populations with negative population growth rates in the absence of immigration. To help reverse the decline of the mountain yellow-legged frog, the Sequoia and Kings Canyon National Parks have been removing introduced trout since 2001. Over 18,000 introduced trout have been removed from 11 lakes since the project started in 2001. The lakes are completely, to mostly, fish-free, and substantial mountain yellow-legged frog population increases have resulted. The California Department of Fish and Game (CDFG) has also removed or is in the process of removing nonnative trout from a total of between 10 and 20 water bodies in the Inyo, Humboldt-Toiyabe, Sierra, and El Dorado National Forests. In the El Dorado National Forest, golden trout were removed from Leland Lake, and attempts have been made to remove trout from two sites near Gertrude Lake, three lakes in the Pyramid Creek watershed, and a tributary of Cole Creek; no data showing increase in mountain yellow-legged frogs at these sites were available.</P>
                    <P>
                        In California, chytridiomycosis, more commonly known as chytrid fungus (
                        <E T="03">Batrachochytrium dendrobatidis</E>
                        ) or Bd, has been detected in many amphibian species, including the mountain yellow-legged frog within the Sierra Nevada. Recent research has shown that this pathogenic fungus has become widely distributed throughout the Sierra Nevada, and that infected mountain yellow-legged frogs often die soon after metamorphosis. Several infected and uninfected populations were monitored in Sequoia and Kings Canyon National Parks over multiple years, documenting dramatic declines and extirpations in infected but not in uninfected populations. In the summer of 2005, 39 of 43 populations assayed in Yosemite National Park were positive for chytrid fungus.
                    </P>
                    <P>
                        The current distribution of the Sierra Nevada mountain yellow-legged frog is restricted primarily to public lands at high elevations, including streams, lakes, ponds, and meadow wetlands located on national forests, including wilderness and non-wilderness on the forests, and national parks. In several areas where detailed studies of the effects of chytrid fungus on the mountain yellow-legged frog are ongoing, substantial declines have been observed over the past several years. For example, in 2007 surveys in Yosemite National Park, mountain yellow-legged frogs were not detectable at 37 percent of 285 sites where they had been observed in 2000-2002; in 2005 in Sequoia and Kings Canyon National Parks, mountain yellow-legged frogs were not detected at 54 percent of sites where they had been recorded 3 to 8 years earlier. A compounding effect of disease-caused extinctions of mountain yellow-legged frogs is that recolonization may never occur because streams connecting extirpated sites to extant populations now contain introduced fishes, which act as barriers to frog movement within metapopulations. The most recent assessment of the species status in the Sierra Nevada indicates that mountain-yellow legged frogs occur at less than 8 percent of the sites from which they were historically observed. A group of prominent scientists further suggest a 10-percent decline per year in the number of remaining 
                        <E T="03">Rana mucosa.</E>
                         Based on threats that are imminent (because they are ongoing) and high-magnitude (because they significantly affect the survival of the DPS throughout its range), we continue to assign the population of mountain yellow-legged frog in the Sierra Nevada an LPN of 3.
                    </P>
                    <P>
                        Oregon spotted frog (
                        <E T="03">Rana pretiosa</E>
                        )—The following summary is based on information contained in our files and the petition we received on May 4, 1989. Historically, the Oregon spotted frog ranged from British Columbia to the Pit River drainage in northeastern California. Based on surveys of historical sites, the Oregon spotted frog is now absent from at least 76 percent of its former range. The majority of the remaining Oregon spotted frog populations are small and isolated.
                    </P>
                    <P>
                        The threats to the species' habitat include development, livestock grazing, introduction of nonnative plant species, vegetation succession, changes in hydrology due to construction of dams and alterations to seasonal flooding, lack of management of exotic vegetation, predators, and poor water quality. Additional threats to the species are predation by nonnative fish and introduced bullfrogs; competition with bullfrogs and nonnative fish for habitat; and diseases, such as oomycete water mold 
                        <E T="03">Saprolegnia</E>
                         and chytrid fungus infections. The magnitude of threat is high for this species because this wide range of threats to both individuals and their habitats could seriously reduce or eliminate any of these isolated populations and further reduce the species' range and potential survival. Habitat restoration and management actions have not prevented population declines. The threats are imminent because each population is faced with multiple ongoing and potential threats as identified above. Therefore, we retain an LPN of 2 for the Oregon spotted frog.
                    </P>
                    <P>
                        Relict leopard frog (
                        <E T="03">Lithobates onca</E>
                        )—See above in “Listing Priority Changes in Candidates.” The above summary is based on information contained in our files.
                    </P>
                    <P>
                        Austin blind salamander (
                        <E T="03">Eurycea waterlooensis</E>
                        )—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Berry Cave salamander (
                        <E T="03">Gyrinophilus gulolineatus</E>
                        )—The following summary is based on information in our files. We have no new information since this species was afforded candidate status through our 12-month warranted-but-precluded finding published on March 22, 2011 (76 FR 15919). The Berry Cave salamander is recorded from Berry Cave in Roane County; from Mud Flats, Aycock Spring, Christian, Meades Quarry, Meades River, and Fifth Caves in Knox County; from Blythe Ferry Cave in Meigs County; and from an unknown cave in Athens, McMinn County, Tennessee. These cave systems are all located within the Upper Tennessee River and Clinch River drainages. A total of 113 caves in Middle and East Tennessee were surveyed from the time period of April 2004 through June 2007, resulting in observations of 63 Berry Cave salamanders. These surveys concluded that Berry Cave salamander populations are robust at Berry and Mudflats Caves, where population declines had been previously reported, and documented two new populations of Berry Cave salamanders at Aycock Spring and Christian caves.
                    </P>
                    <P>
                        Ongoing threats to this species include lye leaching in the Meades Quarry Cave as a result of past quarrying activities, a proposed roadway with potential to impact the recharge area for the Meades Quarry Cave system, urban 
                        <PRTPAGE P="66399"/>
                        development in Knox County, water quality impacts despite existing State and Federal laws, and possibly hybridization between spring salamanders and Berry Cave salamanders in Meades Quarry Cave. These threats, coupled with confined distribution of the species and apparent low population densities, leave the Berry Cave salamander vulnerable to extirpation. We have determined that the Berry Cave salamander faces imminent threats, and that the threats are of moderate magnitude, because some populations appear to be robust and new populations are emerging. We have therefore assigned it an LPN of 8.
                    </P>
                    <P>
                        Georgetown salamander (
                        <E T="03">Eurycea naufragia</E>
                        )—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Jollyville Plateau salamander (
                        <E T="03">Eurycea tonkawae</E>
                        )—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Salado salamander (
                        <E T="03">Eurycea chisholmensis</E>
                        )—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Yosemite toad (
                        <E T="03">Anaxyrus canorus</E>
                        )—The following summary is based on information contained in our files and the petition we received on April 3, 2000. See also our 12-month petition finding published on December 10, 2002 (67 FR 75834). Yosemite toads are moderately sized toads with females having black spots that are edged with white or cream, and set against a grey, tan, or brown background. Males have a nearly uniform coloration of yellow-green to olive drab to greenish brown. Yosemite toads have been grouped within the genus “
                        <E T="03">Bufo.”</E>
                         Recently, Frost 
                        <E T="03">et al.</E>
                         divided the “
                        <E T="03">Bufo”</E>
                         genus into three separate genera, assigning the North American toads to the genus 
                        <E T="03">Anaxyrus.</E>
                         This taxonomic distinction has been recently adopted by the American Society of Ichthyologists and Herpetologists, the Herpetologists' League, and the Society for the Study of Amphibians and Reptiles, and we are acknowledging the change in genus name, and referring to the Yosemite toad accordingly in this document.
                    </P>
                    <P>Yosemite toads are most likely to be found in areas with thick meadow vegetation or patches of low willows near or in water, and use rodent burrows for overwintering and temporary refuge during the summer. Breeding habitat includes the edges of wet meadows, slow-flowing streams, shallow ponds, and shallow areas of lakes. The historic range of Yosemite toads in the Sierra Nevada occurs from the Blue Lakes region north of Ebbetts Pass (Alpine County) to south of Kaiser Pass in the Evolution Lake/Darwin Canyon area (Fresno County). The historic elevational range of Yosemite toads is 1,460 to 3,630 m (4,790 to 11,910 ft).</P>
                    <P>The threats facing the Yosemite toad include cattle grazing, timber harvesting, recreation, disease, and climate change. Inappropriate grazing has been shown to cause loss in vegetative cover and to destroy peat layers in meadows, both of which lower groundwater tables and summer flows of surface water. This may increase the stranding and mortality of tadpoles, or make these areas completely unsuitable for Yosemite toads. Grazing can also degrade or destroy moist upland areas used as non-breeding habitat by Yosemite toads and collapse rodent burrows used by Yosemite toads as cover and hibernation sites. Timber harvesting and associated road construction could severely alter the terrestrial environment and result in the reduction and occasional extirpation of amphibian populations in the Sierra Nevada. Habitat gaps created by timber harvest and road construction may act as dispersal barriers and contribute to the fragmentation of Yosemite toad habitat and populations. Trails (foot, horse, bicycle, or off-highway motor vehicle) compact soil in riparian habitat, which increases erosion, displaces vegetation, and can lower the water table. Trampling or the collapsing of rodent burrows by recreationists, pets, and vehicles could lead to direct mortality of all life stages of the Yosemite toad and disrupt the species' behavior. Various diseases have been confirmed in Yosemite toads. Mass die-offs of amphibians have been attributed to: Chytrid fungal infections of metamorphs and adults; saprolegnia fungal infections of eggs; iridovirus infection of larvae, metamorphs, or adults; and bacterial infections. Yosemite toads probably are exposed to a variety of pesticides and other chemicals throughout their range. Environmental contaminants could negatively affect the species by causing direct mortality; suppressing the immune system; disrupting breeding behavior, fertilization, growth or development of young; and disrupting the ability to avoid predation.</P>
                    <P>There is no indication that any of these threats are ongoing or planned; therefore the threats are nonimminent. In addition, as there are a number of substantial populations and these threats tend to have localized effects, the threats are moderate to low in magnitude. We therefore retained an LPN of 11 for the Yosemite toad.</P>
                    <P>
                        Black Warrior waterdog (
                        <E T="03">Necturus alabamensis</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The Black Warrior waterdog is a salamander that inhabits streams above the Fall Line within the Black Warrior River Basin in Alabama. There is very little specific locality information available on the historical distribution of the Black Warrior waterdog as little attention was given to this species between its description in 1937 and the 1980s. At that time, there were a total of only 11 known historical records from four Alabama counties. Two of these sites have now been inundated by impoundments. Extensive survey work was conducted in the 1990s to look for additional populations. As a result of that work, the species was documented at 14 sites in five counties.
                    </P>
                    <P>
                        Water-quality degradation is the biggest threat to the continued existence of the Black Warrior waterdog. Most streams that have been surveyed for the waterdog showed evidence of pollution and many appeared biologically depauperate. Sources of point and nonpoint pollution in the Black Warrior River Basin have been numerous and widespread. Pollution is generated from inadequately treated effluent from industrial plants, sanitary landfills, sewage treatment plants, poultry operations, and cattle feedlots. Surface mining represents another threat to the biological integrity of waterdog habitat. Runoff from old, abandoned coal mines generates pollution through acidification, increased mineralization, and sediment loading. The North River, Locust Fork, and Mulberry Fork, all streams that this species inhabits, are on the Environmental Protection Agency's list of impaired waters. An additional threat to the Black Warrior waterdog is the creation of large impoundments that have flooded thousands of square hectares of its habitat. These impoundments are likely marginal or unsuitable habitat for the salamander. Suitable habitat for the Black Warrior 
                        <PRTPAGE P="66400"/>
                        waterdog is limited, and available data indicate extant populations are small and their viability is questionable. This situation is pervasive and problematic; water-quality issues are persistent, and regulatory mechanisms are not ameliorating these threats, although we have no indication of population declines, at present. Therefore, the overall magnitude of the threat is moderate. Water-quality degradation in the Black Warrior basin is ongoing. Therefore, the threats are imminent. Additional surveys, initiated in 2011, may clarify the status of populations in the face of existing threats. We assigned an LPN of 8 to this species.
                    </P>
                    <HD SOURCE="HD2">Fishes</HD>
                    <P>
                        Headwater chub (
                        <E T="03">Gila nigra</E>
                        )—The following summary is based on information contained in our files, in the 12-month finding published in the 
                        <E T="04">Federal Register</E>
                         on May 3, 2006 (71 FR 26007), and in the petition received November 9, 2009. The headwater chub is a moderate-sized cyprinid fish. The range of the headwater chub has been reduced by approximately 60 percent. Twenty-three streams (125 miles (200 kilometers) of stream) are thought to be occupied out of 26 streams (312 miles (500 kilometers) of stream) formerly occupied in the Gila River Basin in Arizona and New Mexico. All remaining populations are fragmented and isolated, and threatened by a combination of factors.
                    </P>
                    <P>Headwater chubs are threatened by introduced, nonnative fish that prey on them and compete with them for food. Habitat destruction and modification have occurred and continue to occur as a result of dewatering, impoundment, channelization, and channel changes caused by alteration of riparian vegetation and watershed degradation from mining, grazing, roads, water pollution, urban and suburban development, groundwater pumping, and other human actions. Existing regulatory mechanisms do not appear to be adequate for addressing the impact of nonnative fish and also have not removed or eliminated the threats that continue to be posed through habitat degradation. The fragmented nature and rarity of existing populations makes them vulnerable to other natural or manmade factors, such as drought and wildfire. Climate change is predicted to worsen these threats through increased aridity of the region, thus reducing stream flows and warming aquatic habitats, which makes the habitat more suitable to nonnative species.</P>
                    <P>
                        The Arizona Game and Fish Department has finalized the Arizona Statewide Conservation Agreement for Roundtail Chub (
                        <E T="03">G. robusta</E>
                        ), Headwater Chub, Flannelmouth Sucker (
                        <E T="03">Catostomus latipinnis</E>
                        ), Little Colorado River Sucker (
                        <E T="03">Catostomus</E>
                         spp.), Bluehead Sucker (
                        <E T="03">C. discobolus</E>
                        ), and Zuni Bluehead Sucker (
                        <E T="03">C. discobolus yarrowi</E>
                        ). The New Mexico Department of Game and Fish has listed the headwater chub as endangered and created a recovery plan for the species: Colorado River Basin Chubs (Roundtail Chub, Gila Chub (
                        <E T="03">G. intermedia</E>
                        ), and Headwater Chub) Recovery Plan, which was approved by the New Mexico State Game Commission on November 16, 2006. Both Arizona's agreement and New Mexico's recovery plan recommend preservation and enhancement of extant populations and restoration of historical headwater-chub populations. The recovery and conservation actions prescribed by Arizona's and New Mexico's plans, which we predict will reduce and remove threats to this species, will require further discussions and authorizations before they can be implemented. The recently completed Arizona Game and Fish Department Sportfish Stocking Program's Conservation and Mitigation Program contains significant conservation actions for the headwater chub that will be implemented over the next 10 years.
                    </P>
                    <P>Although threats are ongoing, existing information indicates long-term persistence and stability of existing populations. Currently 7 of the 23 extant stream populations are considered stable based on abundance and evidence of recruitment. We evaluated information provided in the 2009 petition relating to our 2008 change in LPN for the headwater chub from 2 to 8 as part of our annual analysis. In making that 2008 decision, we recognize that we inadvertently relied on some information and did not consider other available information. Additional information will be available on population status and threats later in 2011 that we will use to reassess the LPN for the headwater chub next year. We have retained an LPN of 8 for this species at this time.</P>
                    <P>
                        Least Chub (
                        <E T="03">Iotichthys phlegethontis</E>
                        )—The following summary is based on information contained in our files and in the petition received June 25, 2007. The least chub is a small, colorful fish species in Utah that follows thermal patterns for habitat use. Least chub use flooded, warmer, vegetated marsh areas to spawn in the spring, and retreat to spring heads to overwinter as the water recedes in the late summer and fall. Historically, many least chub occurrences were reported across the State of Utah, but the current distribution of the species is highly reduced from its historic range. Currently, only six known wild populations remain, but one of these is considered functionally extirpated. Least chub also currently exist at several genetic refuge sites. The species faces threats from the effects of livestock grazing, which affects most least chub sites despite efforts to protect least chub habitat with grazing enclosures and management plans. Least chub habitat also is affected by current and proposed future groundwater withdrawals, especially when combined with the threat of drought. These threats also act cumulatively with climate change to put the least chub at further risk. Existing regulatory mechanisms are currently inadequate to regulate groundwater withdrawals and ameliorate their effects on least chub habitat. Nonnative species, particularly mosquitofish, also are a continuing threat to least chub. There is no known means of controlling mosquitofish, and they have already caused the functional extirpation of one wild least chub population.
                    </P>
                    <P>In 1998, several State and Federal agencies including the Service and the Utah Division of Wildlife Resources developed a Least Chub Conservation Agreement and Strategy, and formed the Least Chub Conservation Team. Their objectives are to eliminate or significantly reduce threats to the least chub and its habitat, and to ensure the continued existence of the species by restoring and maintaining a minimum number of least chub populations throughout its historic range. Recent State-led least chub conservation actions have included restoration of habitat affected by grazing, reintroduction and range expansion, nonnative removal, population monitoring, and working cooperatively with landowners to conserve water and aquatic habitat. This group also has recently begun a structured decision making modeling process that will provide additional guidance for conservation activities.</P>
                    <P>Although grazing, groundwater withdrawal, and predation by nonnative species are high magnitude threats to some populations, they are of low magnitude or nonexistent in other populations. Therefore the threats to the least chub are of moderate magnitude overall. The threats are imminent because they are identifiable and the species is currently facing them in many portions of its range. Therefore, we have assigned the least chub an LPN of 7.</P>
                    <P>
                        Roundtail chub (
                        <E T="03">Gila robusta</E>
                        ), Lower Colorado River DPS—The following summary is based on information contained in our files and the 12-month 
                        <PRTPAGE P="66401"/>
                        finding published in the 
                        <E T="04">Federal Register</E>
                         on July 7, 2009 (74 FR 32352). The roundtail chub is a moderate to large cyprinid fish. The range of the roundtail chub has been reduced by approximately 68 to 82 percent. Thirty-two streams are currently occupied, representing approximately 18 to 32 percent of the species' former range, or 800 km (500 miles) to 1,350 km (840 mi) of 3,050 km (1,895 mi) of formerly occupied streams in the Gila River Basin in Arizona and New Mexico. Most of the remaining populations are fragmented and isolated, and all are threatened by a combination of factors.
                    </P>
                    <P>Roundtail chub are threatened by introduced, nonnative fish that prey on them and compete with them for food. Habitat destruction and modification have occurred and continue to occur as a result of dewatering, impoundment, channelization, and channel changes caused by alteration of riparian vegetation and watershed degradation from mining, grazing, roads, water pollution, urban and suburban development, groundwater pumping, and other human actions. Existing regulatory mechanisms do not appear to be adequate for addressing the impact of nonnative fish and also have not removed or eliminated the threats that continue to be posed through habitat destruction or modification. The fragmented nature and rarity of existing populations makes them vulnerable to other natural or manmade factors, such as drought and wildfire. Climate change is predicted to worsen these threats through increased aridity of the region, thus reducing stream flows and warming aquatic habitats, which makes the habitat more suitable to nonnative species.</P>
                    <P>
                        The Arizona Game and Fish Department has finalized the Arizona Statewide Conservation Agreement for Roundtail Chub, Headwater Chub (
                        <E T="03">G. nigra</E>
                        ), Flannelmouth Sucker (
                        <E T="03">Catostomus latipinnis</E>
                        ), Little Colorado River Sucker (
                        <E T="03">Catostomus</E>
                         spp.), Bluehead Sucker (
                        <E T="03">C. discobolus</E>
                        ), and Zuni Bluehead Sucker (
                        <E T="03">C. discobolus yarrowi</E>
                        ). The New Mexico Department of Game and Fish lists the roundtail chub as endangered and has created a recovery plan for the species: Colorado River Basin Chubs (Roundtail Chub, Gila Chub (
                        <E T="03">G. intermedia</E>
                        ), and Headwater Chub) Recovery Plan, which was approved by the New Mexico State Game Commission on November 16, 2006. Both the Arizona Agreement and the New Mexico Recovery Plan recommend preservation and enhancement of extant populations and restoration of historical roundtail chub populations. The recovery and conservation actions prescribed by the Arizona and New Mexico plans, which we predict will reduce and remove threats to this species, will require further discussions and authorizations before they can be implemented, although some actions have been completed and several are planned for the immediate future. The recently completed Arizona Game and Fish Department Sportfish Stocking Program's Conservation and Mitigation Program contains significant conservation actions for the roundtail chub that will be implemented over the next 10 years.
                    </P>
                    <P>Although threats are ongoing, existing information indicates long-term persistence and stability of existing populations. Currently, 9 of the 32 extant stream populations are considered stable, based on abundance and evidence of recruitment. Based on our assessment, threats (primarily nonnative species and habitat loss from land uses) remain imminent and are of a moderate magnitude. Thus, we have retained an LPN of 9 for this distinct population segment.</P>
                    <P>
                        Arkansas darter (
                        <E T="03">Etheostoma cragini</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. This fish species occurs in Arkansas, Colorado, Kansas, Missouri, and Oklahoma. The species is found most often in sand- or pebble-bottomed pools of small, spring-fed streams and marshes, with cool water and broadleaved aquatic vegetation. Its current distribution is indicative of a species that once was widely dispersed throughout its range, but has been relegated to isolated areas surrounded by unsuitable habitat that prevents dispersal. Factors influencing the current distribution include: Surface and groundwater irrigation resulting in decreased flows or stream dewatering; the dewatering of long reaches of riverine habitat necessary for species movement when surface flows do occur; conversion of prairie to cropland, which influences groundwater recharge and spring flows; water quality degradation from a variety of sources; and the construction of dams, which act as barriers preventing emigration upstream and downstream through the reservoir pool. The magnitude of threats facing this species is moderate to low, given the number of different locations where the species occurs and the fact that no single threat or combination of threats affects more than a portion of the widespread population occurrences. Overall, the threats are nonimminent as groundwater pumping is declining and development, spills, and runoff are not currently affecting the species rangewide. Thus, we are retaining an LPN of 11 for the Arkansas darter.
                    </P>
                    <P>
                        Pearl darter (
                        <E T="03">Percina aurora</E>
                        )—The following summary is based on information contained in our files. Little is known about the specific habitat requirements or natural history of the Pearl darter. Pearl darters have been collected from a variety of river/stream attributes, mainly over gravel bottom substrate. This species is historically known only from localized sites within the Pascagoula and Pearl River drainages in Mississippi and Louisiana. Currently, the Pearl darter is considered extirpated from the Pearl River drainage and rare in the Pascagoula River drainage. Since 1983, the range of the Pearl darter has decreased by 55 percent.
                    </P>
                    <P>The Pearl darter is vulnerable to nonpoint source pollution caused by urbanization and other land use activities; gravel mining and resultant changes in river geomorphology, especially head cutting; and the possibility of water quantity decline from the proposed Department of Energy Strategic Petroleum Reserve project and a proposed dam on the Bouie River. Additional threats are posed by the apparent lack of adequate State and Federal water quality regulations due to the continuing degradation of water quality within the species' habitat. The Pearl darter's localized distribution and apparent low population numbers may indicate a species with lower genetic diversity, and this would also make the species more vulnerable to catastrophic events. Threats affecting the Pearl darter are localized in nature, affecting portions of the population within the drainage; thus, a threat magnitude of moderate to low is assigned for this species. In addition, the threats are imminent because the identified threats are currently affecting this species in some portions of its range. Therefore, we have assigned an LPN of 8 for this species.</P>
                    <P>
                        Arctic grayling, Upper Missouri River DPS (
                        <E T="03">Thymallus arcticus</E>
                        )—The following summary is based on information contained in our files. This fish species has a broad, nearly circumpolar distribution, occurring in a variety of cold-water habitats including small streams, large rivers, lakes, and even bogs. We determined in our September 8, 2010, status review (75 FR 54708) that the upper Missouri River population of arctic grayling in Montana and Wyoming represents a DPS because it is discrete due to geographic separation and genetic differences, and it is significant to the taxon as a whole. 
                        <PRTPAGE P="66402"/>
                        The historical range of Arctic grayling in the upper Missouri River basin has declined dramatically in the past century. The five remaining indigenous populations are isolated from one another by dams or other factors.
                    </P>
                    <P>All populations face potential threats from competition with and predation by nonnative trout, and most populations face threats resulting from the alteration of their habitats, such as habitat fragmentation from dams or irrigation diversion structures, stream dewatering, high summer water temperatures, loss of riparian habitats, and entrainment in irrigation ditches. Severe drought likely also affects all populations by reducing water availability and reducing the extent of thermally suitable habitat. Projected climate changes will likely influence the severity and scope of these threats in the future. As applied, existing regulatory mechanisms do not appear to be adequate to address the primary threats to arctic grayling. In addition, four of five populations are at risk from random environmental fluctuations and genetic drift due to their low abundance and isolation. The magnitude of these threats is high because one or more of these threats occurs in each known population in the Missouri River basin. The threats are imminent because they are currently occurring and expected to continue in the foreseeable future. Therefore, we have assigned the upper Missouri River DPS of arctic grayling an LPN of 3.</P>
                    <P>
                        Sicklefin redhorse (
                        <E T="03">Moxostoma</E>
                         sp.)—The following summary is based on information contained in our files. No new information was provided in the petition we received on April 20, 2010. The sicklefin redhorse, a freshwater fish, occupies cool to warm, moderate gradient creeks and rivers; during parts of its early life stages, it also occupies the near-shore areas in large reservoirs. It feeds and spawns in gravel, cobble, and boulder substrates with no, or very little, silt overlay. There are only two metapopulations of the species known to survive: one in the Hiwassee River system in North Carolina and Georgia, and one in the Little Tennessee River system in North Carolina.
                    </P>
                    <P>All of the surviving occurrences of the sicklefin redhorse continue to be restricted to relatively short reaches of the streams they occupy and expansion of the populations is to a large degree prohibited by existing hydropower dams and in several cases cold-water discharges from hydroelectric dam operations. Other impacts and threats to the species and its habitat include: Siltation resulting from inadequate erosion/sedimentation control during agricultural, timbering, and construction activities; run-off and discharge of organic and inorganic pollutants from industrial, municipal, agricultural, and other point and nonpoint sources; habitat alterations associated with channelization and instream dredging/mining activities; and other natural and human-related factors that adversely modify the aquatic environment (e.g., illegal dumping, introduction of invasive predators, drought, flooding). The sicklefin redhorse's limited distribution make the species extremely vulnerable to the effects from single catastrophic events (such as toxic chemical spills, major sedimentation events, channel modification, etc.) and the cumulative effects of lesser impacts to the species habitat and numbers. Although the majority of the streams still occupied by the species occur in areas that are presently primarily rural, many of the communities within the watersheds of these streams are experiencing increasing development pressure, both commercial and residential, and continue to develop and implement plans for upgrading and improving their infrastructure (e.g., roads, water supplies, sewer/wastewater treatment systems, etc.) to provide for increased densities of development. Because of the effects this development can have on water quality and habitat suitability for the sicklefin, along with its restricted distribution, the magnitude of the threat to the species is high; however, although the threats faced by the sicklefin redhorse are significant, it is not anticipated that the species will be subjected to these threats in the immediate future (within the next 1 to 2 years) and the immediacy of the threats thus remains nonimminent. Accordingly, we have assigned an LPN of 5 to this species.</P>
                    <P>
                        Grotto sculpin (
                        <E T="03">Cottus</E>
                         sp., sp. nov.)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Sharpnose shiner (
                        <E T="03">Notropis oxyrhynchus</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The sharpnose shiner is a small, slender minnow, endemic to the Brazos River Basin in Texas. Historically, the sharpnose shiner existed throughout the Brazos River and several of its major tributaries. It has also been found in the Wichita River (within the Red River Basin) where it may have once naturally occurred, but has since been extirpated. Current information indicates that the population upstream of Possum Kingdom Reservoir is apparently stable, while the downstream population may be extirpated, representing a 69-percent reduction of its historical range.
                    </P>
                    <P>The most significant threat to the existence of the sharpnose shiner is reservoir development within its current range. The current water plan for Texas provides several reservoir options that could be implemented within the Brazos River drainage. Additional threats include irrigation and water diversion, sedimentation, desalination, industrial and municipal discharges, agricultural activities, instream sand and gravel mining, and the spread of invasive saltcedar. The current limited distribution of the sharpnose shiner within the Upper Brazos River Basin makes it vulnerable to catastrophic events such as the introduction of competitive species or prolonged drought. The magnitude of threat is considered high as reservoir development within the species' current range may render remaining habitat unsuitable. The immediacy of threat is nonimminent because the most significant threat—major reservoir construction—is not likely to occur in the near future, and there is potential for implementing other water supply options that could preclude reservoir development. For these reasons, we assigned an LPN of 5 to this species.</P>
                    <P>
                        Smalleye shiner (
                        <E T="03">Notropis buccula</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The smalleye shiner is a small, pallid minnow endemic to the Brazos River Basin in Texas. Smalleye shiners were historically known to occur downstream of the three major reservoirs occurring on the Brazos River. Currently, the species is found upstream of Possum Kingdom Reservoir (Upper Brazos River drainage) and may be extirpated from the downstream reach, representing a 54-percent reduction of its historical range.
                    </P>
                    <P>
                        The most significant threat to the existence of the smalleye shiner is reservoir development within its current range. The current water plan for Texas provides several reservoir options that could be implemented within the Brazos River drainage. Additional threats include irrigation and water diversion, sedimentation, desalination, industrial and municipal discharges, agricultural activities, instream sand and gravel mining, and the spread of invasive saltcedar. The current limited distribution of the smalleye shiner within the Upper Brazos River drainage 
                        <PRTPAGE P="66403"/>
                        makes it vulnerable to catastrophic events such as the introduction of competitive species or prolonged drought. State law does not provide protection for the smalleye shiner. The magnitude of threat is considered high, as reservoir development within the species' current range may render remaining habitat unsuitable. The immediacy of threat is nonimminent because the most significant threat—major reservoir construction—is not likely to occur in the near future, and there is potential for implementing other water supply options that could preclude reservoir development. For these reasons, we assigned a LPN of 5 to this species.
                    </P>
                    <P>
                        Zuni bluehead sucker (
                        <E T="03">Catostomus discobolus yarrowi</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The Zuni bluehead sucker is a colorful fish less than 20 centimeters (8 inches) long. The range of the Zuni bluehead sucker has been reduced by over 95 percent. The Zuni bluehead sucker currently occupies 4.8 river kilometers (3 miles) in three headwater streams of the Rio Nutria in New Mexico, and potentially occurs in 44 river kilometers (27.5 miles) in the Kinlichee drainage of Arizona. However, the number of occupied miles in Arizona is unknown, and the genetic composition of these fish is still under investigation.
                    </P>
                    <P>Zuni bluehead sucker's range reduction and fragmentation is caused by discontinuous surface-water flow, introduced species, and habitat degradation from fine sediment deposition. The Zuni bluehead sucker persists in very small creeks that are subject to very low flows and drying during periods of drought. Because of climate change (warmer air temperatures), streamflow is predicted to decrease in the Southwest. Warmer winter and spring temperatures cause an increased fraction of precipitation to fall as rain, resulting in a reduced snow pack, an earlier snow melt, and a longer dry season leading to decreased streamflow in the summer and a longer fire season. These changes would have a negative effect on Zuni bluehead sucker. Another major impact to populations of Zuni bluehead sucker was the application of fish toxicants through at least two dozen treatments in the Rio Nutria and Rio Pescado between 1960 and 1975. Large numbers of Zuni bluehead suckers were killed during these treatments. The Zuni bluehead sucker is most likely extirpated from Rio Pescado, as not one has been collected from that river since 1993.</P>
                    <P>The New Mexico Department of Game and Fish developed a recovery plan for Zuni bluehead sucker, which was approved by the New Mexico State Game Commission on December 15, 2004. The recovery plan recommends preservation and enhancement of extant populations and restoration of historical Zuni bluehead sucker populations. We predict that the recovery actions prescribed by the recovery plan will reduce and remove threats to this subspecies, but these actions will require further development and authorization before they can be implemented and threats are reduced. Because of the ongoing (imminent) threats of high magnitude, including loss of habitat (historical and current from beaver activity), degradation of remaining habitat (nonnative species and land development), drought, fire, and climate change, we maintained an LPN of 3 for this subspecies.</P>
                    <P>
                        Rio Grande cutthroat trout (
                        <E T="03">Oncorhynchus clarki virginalis</E>
                        )—The following summary is based on information contained in our files and our status review published on May 14, 2008 (73 FR 27900). Rio Grande cutthroat trout is one of 14 subspecies of cutthroat trout found in the western United States. Populations of this subspecies are in New Mexico and Colorado in drainages of the Rio Grande, Pecos, and Canadian Rivers. Although once widely distributed in connected stream networks, Rio Grande cutthroat trout populations now occupy about 10 percent of historical habitat, and the populations are fragmented and isolated from one another. The majority of populations occur in high-elevation streams.
                    </P>
                    <P>Major threats include the loss of suitable habitat that has occurred and is likely to continue occurring due to water diversions, dams, stream drying, habitat quality degradation, and, changes in hydrology; introduction of nonnative trout and ensuing competition, predation, and hybridization; and whirling disease. In addition, average air temperatures in the Southwest have increased about 1 °C (2.5 °F) in the past 30 years, and they are projected to increase by another 1.2 to 2.8 °C (3 to 7 °F) by 2050. Because trout require cold water, and water temperatures depend in large part on air temperature, there is concern that the habitat of Rio Grande cutthroat trout will further decrease in response to warmer water temperatures caused by climate change. Wildfire and drought (stream drying) are additional threats to Rio Grande cutthroat trout populations that are likely to increase in magnitude in response to climate change. Research is occurring to assess the effects of climate change on this subspecies, and agencies are working to restore historically occupied streams and develop a conservation plan to direct conservation. The threats are of moderate magnitude because there is good distribution and a comparatively large number of populations across the landscape, some populations have few threats present, and in other areas management actions are being taken to help control the threat of nonnative trout. Overall, the threats are ongoing and, therefore, imminent. Based on imminent threats of moderate magnitude, we assigned an LPN of 9 to this subspecies.</P>
                    <HD SOURCE="HD2">Clams</HD>
                    <P>
                        Texas hornshell (
                        <E T="03">Popenaias popei</E>
                        )—The following summary is based on information contained in our files and information provided by the New Mexico Department of Game and Fish and Texas Parks and Wildlife Department. The Texas hornshell is a freshwater mussel found in the Black River in New Mexico, and in the Rio Grande and the Devils River in Texas. Until March 2008, the only known extant populations were in New Mexico's Black River and one locality in the Rio Grande near Laredo, Texas. In March 2008, two new localities were confirmed in Texas: one in the Devils River, and one in the mainstem Rio Grande in the Rio Grande Wild and Scenic River segment downstream of Big Bend National Park. In 2011, the Rio Grande population near Laredo was resurveyed and found to be large and robust.
                    </P>
                    <P>
                        The primary threats to this species are habitat alterations such as streambank channelization, impoundments, and diversions for agriculture and flood control, including a proposed low-water diversion dam just downstream of the Rio Grande population near Laredo; contamination of water by oil and gas activity; alterations in the natural riverine hydrology; and increased sedimentation and flood pulses from prolonged overgrazing and loss of native vegetation. Although riverine habitats throughout the species' known occupied range are under constant threat from these ongoing or potential activities, numerous conservation actions that will benefit the species are under way in New Mexico, including the completion of a State recovery plan for the species and the drafting of a candidate conservation agreement with assurances, and are beginning in Texas on the Big Bend reach of the Rio Grande. Due to these ongoing conservation efforts, and because at 
                        <PRTPAGE P="66404"/>
                        least one of the populations appears to be robust, the magnitude of the threats is moderate. However, the threats to the species are ongoing, and remain imminent. Thus, we maintained the LPN of 8 for this species.
                    </P>
                    <P>
                        Fluted kidneyshell (
                        <E T="03">Ptychobranchus subtentum</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The fluted kidneyshell is a freshwater mussel (Unionidae) endemic to the Cumberland and Tennessee River systems (Cumberlandian Region) in Alabama, Kentucky, Tennessee, and Virginia. It requires shoal habitats in free-flowing rivers to survive and successfully recruit new individuals into its populations.
                    </P>
                    <P>This species has been extirpated from numerous regional streams and is no longer found in the State of Alabama. Habitat destruction and alteration (e.g., impoundments, sedimentation, and pollutants) are the chief factors that contributed to its decline. The fluted kidneyshell was historically known from at least 37 streams but is currently restricted to no more than 12 isolated populations. Current status information for most of the 12 populations deemed to be extant is available from recent periodic sampling efforts (sometimes annually) and other field studies, particularly in the upper Tennessee River system. Some populations in the Cumberland River system have had recent surveys as well (e.g., Wolf, Little Rivers; Little South Fork; Horse Lick, Buck Creeks). Populations in Buck Creek, Little South Fork, Horse Lick Creek, Powell River, and North Fork Holston River have clearly declined over the past two decades. Based on recent information, the overall population of the fluted kidneyshell is declining rangewide. At this time, there is only one population—the Clinch River/Copper Creek -where the species remains in large numbers and is viable, although smaller, viable populations remain (e.g., Wolf, Little, North Fork Holston Rivers; Rock Creek). Most other populations are of questionable or limited viability, with some on the verge of extirpation (e.g., Powell River; Little South Fork; Horse Lick, Buck, and Indian Creeks). Newly reintroduced populations in the Little Tennessee, Nolichucky, and Duck Rivers will hopefully begin to reverse the downward population trend of this species. The threats are high in magnitude, as the majority of populations of this species are severely affected by numerous threats (impoundments, sedimentation, small population size, isolation of populations, gravel mining, municipal pollutants, agricultural runoff, nutrient enrichment, and coal processing pollution) that result in mortality or reduced reproductive output. As the threats are ongoing, they are imminent. We assigned an LPN of 2 to this mussel species.</P>
                    <P>
                        Neosho mucket (
                        <E T="03">Lampsilis rafinesqueana</E>
                        )—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Slabside pearlymussel (
                        <E T="03">Lexingtonia dolabelloides</E>
                        )—The following summary is based on information contained in our files. The slabside pearlymussel is a freshwater mussel (Unionidae) endemic to the Cumberland and Tennessee River systems (Cumberlandian Region) in Alabama, Kentucky, Tennessee, and Virginia. It requires shoal habitats in free-flowing rivers to survive and successfully recruit new individuals into its populations.
                    </P>
                    <P>Habitat destruction and alteration (e.g., impoundments, sedimentation, and pollutants) are the chief factors contributing to the decline of this species, which has been extirpated from numerous regional streams and is no longer found in Kentucky. The slabside pearlymussel was historically known from at least 32 streams, but is currently restricted to no more than 11 isolated stream segments. Current status information for most of the 11 populations deemed to be extant is available from recent periodic sampling efforts (sometimes annually) and other field studies. Comprehensive surveys have taken place in the Middle and North Forks of the Holston River, Paint Rock River, and Duck River in the past several years. Based on recent information, the overall population of the slabside pearlymussel is declining rangewide. Of the five streams in which the species remains in good numbers (i.e., Clinch, North and Middle Forks of the Holston River, Paint Rock River, and Duck River), the Middle and upper North Fork Holston Rivers have undergone drastic recent declines, while the Clinch population has been in a longer-term decline. Most of the remaining five populations (i.e., Powell River, Big Moccasin Creek, Hiwassee River, Elk River, Bear Creek) have doubtful viability, and several if not all of them may be on the verge of extirpation.</P>
                    <P>The threats remain high in magnitude, as all populations of this species are severely affected in numerous ways (impoundments, sedimentation, small population size, isolation of populations, gravel mining, municipal pollutants, agricultural runoff, nutrient enrichment, and coal processing pollution) that result in mortality or reduced reproductive output. As the threats are ongoing, they are imminent. We assigned an LPN of 2 to this mussel species.</P>
                    <P>
                        Rabbitsfoot (
                        <E T="03">Quadrula cylindrica cylindrica</E>
                        )—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <HD SOURCE="HD2">Snails</HD>
                    <P>
                        Black mudalia (
                        <E T="03">Elimia melanoides</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on April 20, 2010. The black mudalia is a small snail that is found clinging to clean gravel, cobble, boulders and/or logs in flowing water on shoals and riffles. The historical distribution of the black mudalia encompassed over 250 miles of stream channel in the upper the Black Warrior River drainage in Alabama. The species has been extirpated from more than 80 percent of that range by the construction of two major dams on the main stem Black Warrior River and another dam on the lower Sipsey Fork. Other historical causes of range curtailment in the un-dammed river and stream channels of the upper Black Warrior River drainage include coal mine drainage, industrial and municipal pollution events, and agricultural runoff. The mudalia is currently known from 10 shoal populations in five streams.
                    </P>
                    <P>
                        Water quality and habitat degradation are the biggest threats to the continued existence of the black mudalia. Sources of point and nonpoint pollution in the Black Warrior River Basin have been numerous and widespread. Pollution is generated from inadequately treated effluent from industrial plants, sanitary landfills, sewage treatment plants, poultry operations, and cattle feedlots. Surface mining represents another threat to the biological integrity of stream habitats. Runoff from old, abandoned coal mines generates pollution through acidification, increased mineralization, and sediment loading. Most of the stream segments draining into black mudalia habitat currently support their water quality classification standards. However, the reach of the Locust Fork where the species is found is identified on the 
                        <PRTPAGE P="66405"/>
                        Alabama 303(d) List (a list of water bodies failing to meet their designated water-use classifications) as impaired by siltation, nutrients, or other habitat alterations. Additional surveys that were initiated in 2011, will clarify the extent and status of black mudalia populations. Because most of the stream segments currently occupied by black mudalia have sufficient water quality, we conclude that the threats to the species are moderate. Based on ongoing threats of moderate magnitude, we assigned an LPN of 8 to this species.
                    </P>
                    <P>
                        Phantom Cave snail (
                        <E T="03">Cochliopa texana</E>
                        ) and Phantom springsnail (
                        <E T="03">Tryonia cheatumi</E>
                        )—We continue to find that listing these species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Sisi snail (
                        <E T="03">Ostodes strigatus</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The sisi snail is a ground-dwelling species in the Potaridae family, and is endemic to American Samoa. The species is now known from a single population on the island of Tutuila, American Samoa.
                    </P>
                    <P>
                        This species is currently threatened by habitat loss and modification and by predation from nonnative predatory snails. The decline of the sisi snail in American Samoa has resulted, in part, from loss of habitat to forestry and agriculture, and loss of forest structure to hurricanes and alien weeds that establish after these storms. All live sisi snails have been found in the leaf litter beneath remaining intact forest canopy. No snails were found in areas bordering agricultural plots or in forest areas that were severely damaged by three hurricanes (1987, 1990, and 1991). Under natural historical conditions, loss of forest canopy to storms did not pose a great threat to the long-term survival of these snails; enough intact forest with healthy populations of snails would support dispersal back into newly regrown canopy forest. However, the presence of alien weeds such as mile-a-minute vine (
                        <E T="03">Mikania micrantha</E>
                        ) may reduce the likelihood that native forest will re-establish in areas damaged by the hurricanes. This loss of habitat to storms is greatly exacerbated by expanding agriculture. Agricultural plots on Tutuila have spread from low elevations up to middle and some high elevations, greatly reducing the forest area and thus reducing the resilience of native forests and Tutuila's populations of native snails. These reductions also increase the likelihood that future storms will lead to the extinction of populations or species that rely on the remaining canopy forest. In an effort to eradicate the giant African snail (
                        <E T="03">Achatina fulica</E>
                        ), the alien rosy carnivore snail (
                        <E T="03">Euglandia rosea</E>
                        ) was introduced in 1980. The rosy carnivore snail has spread throughout the main island of Tutuila. Numerous studies show that the rosy carnivore snail feeds on endemic island snails including the sisi, and is a major agent in their declines and extirpations. At present, the major threat to long-term survival of the native snail fauna in American Samoa is predation by nonnative predatory snails. These threats are ongoing and are therefore imminent. As the threats occur throughout the entire range of the species and have a severe effect on the survival of the snails, leading to a relatively high likelihood of extinction, they are of a high magnitude. Therefore we assigned this species an LPN of 2.
                    </P>
                    <P>
                        Diamond Y Spring snail (
                        <E T="03">Pseudotryonia adamantina</E>
                        ) and Gonzales springsnail (
                        <E T="03">Tryonia circumstriata</E>
                        )—We continue to find that listing these species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Rosemont talussnail (
                        <E T="03">Sonorella rosemontensis</E>
                        )—the following summary is based on information in our files. The petition we received on June 24, 2010, provided no new information beyond what we had already included in our assessment of this species. The Rosemont talussnail, a land snail in the family Helminthoglyptidae, is known from three talus slopes in the Santa Rita Mountains, Pima County, Arizona. The primary threat to Rosemont talussnail is hard rock mining. The entire range of the species is located on patented mining claims and can reasonably be expected to be subjected to mining activities in the foreseeable future. Hard rock mining typically involves the blasting of hillsides and the crushing of ore-laden rock. Such activities would kill talussnails and render their habitats unsuitable for occupation. Because mining may occur across the entire range of the species within the foreseeable future, potentially resulting in rangewide habitat destruction and population losses, the threats are of a high magnitude. However, mining on patented mining claims, although a reasonably anticipated action, is neither currently ongoing nor imminent. Although the Rosemont Copper Mine is scheduled to commence operations in the near future, there exists uncertainty regarding its scope, and therefore its potential effect on habitat of the Rosemont talussnail. Accordingly, we find that overall threats to the Rosemont talussnail are nonimminent, and we retain an LPN of 5 for this species.
                    </P>
                    <P>
                        Fragile tree snail (
                        <E T="03">Samoana fragilis</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. A tree-dwelling species, the fragile tree snail is a member of the Partulidae family of snails, and is endemic to the islands of Guam and Rota (Mariana Islands). Requiring cool and shaded native forest habitat, the species is now known from one population on Guam and from one population on Rota.
                    </P>
                    <P>
                        This species is currently threatened by habitat loss and modification and by predation from nonnative predatory snails and flatworms. Large numbers of Philippine deer (
                        <E T="03">Cervus mariannus</E>
                        ) (Guam and Rota), pigs (
                        <E T="03">Sus scrofra</E>
                        ) (Guam), water buffalo (
                        <E T="03">Bubalus bubalis</E>
                        ) (Guam), and cattle (
                        <E T="03">Bos taurus</E>
                        ) (Rota) directly alter the understory plant community and overall forest microclimate, making it unsuitable for snails. Predation by the alien rosy carnivore snail (
                        <E T="03">Euglandina rosea</E>
                        ), the Manokwar flatworm (
                        <E T="03">Platydemus manokwari</E>
                        ), and possibly rats (
                        <E T="03">Rattus</E>
                         spp.) is a serious threat to the survival of the fragile tree snail. Field observations have established that the rosy carnivore snail and the Manokwar flatworm will readily feed on native Pacific island tree snails, including the Partulidae, such as those of the Mariana Islands. The rosy carnivore snail has caused the extirpation of many populations and species of native snails throughout the Pacific islands. The Manokwar flatworm has also contributed to the decline of native tree snails, in part due to its ability to ascend into trees and bushes that support native snails. Areas with populations of the flatworm usually lack partulid tree snails or have declining numbers of snails. In addition, predation by rats may be a serious and ongoing threat to the fragile tree snail. Because all of the threats occur rangewide and have a significant effect on the survival of this snail species, leading to a relatively high likelihood of extinction, they are high in magnitude. The threats are also ongoing and thus are imminent. Therefore, we assigned this species an LPN of 2.
                    </P>
                    <P>
                        Guam tree snail (
                        <E T="03">Partula radiolata</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the 
                        <PRTPAGE P="66406"/>
                        petition we received on May 11, 2004. A tree-dwelling species, the Guam tree snail is a member of the Partulidae family of snails and is endemic to the island of Guam. Requiring cool and shaded native forest habitat, the species is now known from 22 populations on Guam.
                    </P>
                    <P>
                        This species is primarily threatened by predation from nonnative predatory snails, flatworms, and possibly rats (
                        <E T="03">Rattus</E>
                         spp.). In addition, the species is also threatened by habitat loss and degradation. Predation by the alien rosy carnivore snail (
                        <E T="03">Euglandina rosea</E>
                        ) and the alien Manokwar flatworm (
                        <E T="03">Platydemus manokwari</E>
                        ) is a serious threat to the survival of the Guam tree snail (see summary for the fragile tree snail, above). In addition, predation by rats may be a serious and ongoing threat to the Guam tree snail. On Guam, open agricultural fields and other areas prone to erosion were seeded with tangantangan (
                        <E T="03">Leucaena leucocephala</E>
                        ) by the U.S. military. Tangantangan grows as a single species stand with no substantial understory. The microclimatic condition is dry with little accumulation of leaf litter humus and is particularly unsuitable as Guam tree snail habitat. In addition, native forest cannot reestablish and grow where this alien weed has become established. Because all of the threats occur rangewide and have a significant effect on the survival of this snail species, leading to a relatively high likelihood of extinction, they are high in magnitude. The threats are also ongoing and thus are imminent. Therefore, we assigned this species an LPN of 2.
                    </P>
                    <P>
                        Humped tree snail (
                        <E T="03">Partula gibba</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. A tree-dwelling species, the humped tree snail is a member of the Partulidae family of snails, and was originally known from the island of Guam and the Commonwealth of the Northern Mariana Islands (islands of Rota, Aguiguan, Tinian, Saipan, Anatahan, Sarigan, Alamagan, and Pagan). Most recent surveys revealed a total of 14 populations on the islands of Guam, Rota, Aguiguan, Sarigan, Saipan, Alamagan, and Pagan. Although still the most widely distributed tree snail endemic in the Mariana Islands, remaining population sizes are often small.
                    </P>
                    <P>
                        This species is currently threatened by habitat loss and modification and by predation from nonnative predatory snails, flat worms, and possibly rats (
                        <E T="03">Rattus</E>
                         spp.). Throughout the Mariana Islands, feral ungulates (pigs (
                        <E T="03">Sus scrofa</E>
                        ), Philippine deer (
                        <E T="03">Cervus mariannus</E>
                        ), cattle (
                        <E T="03">Bos taurus</E>
                        ), water buffalo (
                        <E T="03">Bubalus bubalis</E>
                        ), and goats (
                        <E T="03">Capra hircus</E>
                        )) have caused severe damage to native forest vegetation by browsing directly on plants, causing erosion and retarding forest growth and regeneration. This in turn reduces the quantity and quality of forested habitat for the humped tree snail. Currently, populations of feral ungulates are found on the islands of Guam (deer, pigs, and water buffalo), Rota (deer and cattle), Aguiguan (goats), Saipan (deer, pigs, and cattle), Alamagan (goats, pigs, and cattle), and Pagan (cattle, goats, and pigs). Goats were eradicated from Sarigan in 1998, and the humped tree snail has increased in abundance on that island, likely in response to the removal of all the goats. However, the population of humped tree snails on Anatahan is likely extirpated due to the massive volcanic explosions of the island beginning in 2003 and still continuing, and the resulting loss of up to 95 percent of the vegetation on the island. Predation by the alien rosy carnivore snail (
                        <E T="03">Euglandina rosea</E>
                        ) and the alien Manokwar flatworm (
                        <E T="03">Platydemus manokwari</E>
                        ) is a serious threat to the survival of the humped tree snail (see summary for the fragile tree snail, above). In addition, predation by rats (
                        <E T="03">Rattus</E>
                         spp.) may be a serious and ongoing threat to the humped tree snail. The magnitude of threats is high because these alien predators cause significant population declines to the humped tree snail rangewide. These threats are ongoing and thus are imminent. Therefore, we assigned this species an LPN of 2.
                    </P>
                    <P>
                        Lanai tree snail (
                        <E T="03">Partulina semicarinata</E>
                        )—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Lanai tree snail (
                        <E T="03">Partulina variabilis</E>
                        )—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Langford's tree snail (
                        <E T="03">Partula langfordi</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. A tree-dwelling species, Langford's tree snail is a member of the Partulidae family of snails, and is known from one population on the island of Aguiguan.
                    </P>
                    <P>
                        This species is currently threatened by habitat loss and modification and by predation from nonnative predatory snails. In the 1930s, the island of Aguiguan was mostly cleared of native forest to support sugar cane and pineapple production. The abandoned fields and airstrip are now overgrown with alien weeds. The remaining native forest understory has greatly suffered from large and uncontrolled populations of alien goats and the invasion of weeds. Goats (
                        <E T="03">Capra hircus</E>
                        ) have caused severe damage to native forest vegetation by browsing directly on plants, causing erosion and retarding forest growth and regeneration. This in turn reduces the quantity and quality of forested habitat for Langford's tree snail. Predation by the alien rosy carnivore snail (
                        <E T="03">Euglandina rosea</E>
                        ) and by the Manokwar flatworm (
                        <E T="03">Platydemus manokwari</E>
                        ) (see summary for the fragile tree snail, above) is also a serious threat to the survival of Langford's tree snail. In addition, predation by rats (
                        <E T="03">Rattus</E>
                         spp.) may be a serious and ongoing threat to Langford's tree snail. All of the threats are occurring rangewide, and no efforts to control or eradicate the nonnative predatory snail species or rats, or to reduce habitat loss, are being undertaken. The magnitude of threats is high because they result in direct mortality or significant population declines to Langford's tree snail rangewide. A survey of Aguiguan in November 2006 failed to find any live Langford's tree snails. These threats are also ongoing and thus are imminent. Therefore, we assigned this species an LPN of 2.
                    </P>
                    <P>
                        Newcomb's tree snail (
                        <E T="03">Newcombia cumingi</E>
                        )—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Tutuila tree snail (
                        <E T="03">Eua zebrina</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. A tree-dwelling species, the Tutuila tree snail is a member of the Partulidae family of snails, and is endemic to American Samoa. The species is known from 32 populations on the islands of Tutuila, Nuusetoga, and Ofu.
                    </P>
                    <P>
                        This species is currently threatened by habitat loss and modification and by predation from nonnative predatory snails and rats. All live Tutuila tree snails were found on understory 
                        <PRTPAGE P="66407"/>
                        vegetation beneath remaining intact forest canopy. No snails were found in areas bordering agricultural plots or in forest areas that were severely damaged by three hurricanes (1987, 1990, and 1991). (See summary for the sisi snail, above, regarding impacts of alien weeds and of the rosy carnivore snail.) Rats (
                        <E T="03">Rattus</E>
                         spp.) have also been shown to devastate snail populations, and rat-chewed snail shells have been found at sites where the Tutuila snail occurs. At present, the major threat to the long-term survival of the native snail fauna in American Samoa is predation by nonnative predatory snails and rats. The magnitude of threats is high because they result in direct mortality or significant population declines to the Tutuila tree snail rangewide. The threats are also ongoing and thus are imminent. Therefore, we assigned this species an LPN of 2.
                    </P>
                    <P>
                        Elongate mud meadows springsnail (
                        <E T="03">Pyrgulopsis notidicola</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition received on May 11, 2004. The following summary is based on information contained in our files. 
                        <E T="03">Pyrgulopsis notidicola</E>
                         is endemic to Soldier Meadow, which is located at the northern extreme of the western arm of the Black Rock Desert in the transition zone between the Basin and Range Physiographic Province and the Columbia Plateau Province, Humboldt County, Nevada. The type locality, and the only known location of the species, occurs in four separate stretches of thermal (between 45° and 32 °C, 113° and 90 °F) aquatic habitat. The first stretch is the largest at approximately 600 m (1,968 ft) long and 2 m (6.7 ft) wide. The other stretches where 
                        <E T="03">P. notidicola</E>
                         occurs are less than 6 m (19.7 ft) long and 0.5 m (1.6 ft) wide. 
                        <E T="03">Pyrgulopsis notidicola</E>
                         occurs only in shallow, flowing water on gravel substrate. The species does not occur in deep water (i.e., impoundments) where water velocity is low, gravel substrate is absent, and sediment levels are high.
                    </P>
                    <P>The species and its habitat are threatened by recreational use in the areas where it occurs as well as the ongoing impacts of past water diversions and livestock grazing and current off-highway vehicle travel. Conservation measures implemented by the Bureau of Land Management include installing fencing to exclude livestock, wild horses, burros and other large mammals; closing access roads to spring, riparian, and wetland areas and the limiting vehicles to designated routes; establishing a designated campground away from the habitats of sensitive species; installing educational signage; and increasing staff presence, including law enforcement and a volunteer site steward during the 6-month period of peak visitor use. These conservation measures have reduced the magnitude of threats to the species to moderate to low; all remaining threats are nonimminent and involve long-term changes to the habitat for the species resulting from past impacts. Until we can get data from a monitoring program that allows us to assess the long-term trend of the species, we have assigned a LPN of 11.</P>
                    <P>
                        Gonzales springsnail (
                        <E T="03">Tryonia circumstriata</E>
                        )—See summary above under Diamond Y Spring snail (
                        <E T="03">Pseudotryonia adamantina</E>
                        ).
                    </P>
                    <P>
                        Huachuca springsnail (
                        <E T="03">Pyrgulopsis thompsoni</E>
                        )—See above in “
                        <E T="03">Listing</E>
                         Priority Changes in Candidates.” The above summary is based on information contained in our files.
                    </P>
                    <P>
                        Page springsnail (
                        <E T="03">Pyrgulopsis morrisoni</E>
                        )—The following summary is based on information contained in our files. The Page springsnail is known to exist only within a complex of springs located within an approximately 0.93-mi (1.5-km) stretch along the west side of Oak Creek around the community of Page Springs, and within springs located along Spring Creek, tributary to Oak Creek, Yavapai County, Arizona.
                    </P>
                    <P>The primary threat to the Page springsnail is modification of habitat by domestic use, agriculture, ranching, fish hatchery operations, recreation, and groundwater withdrawal. Many of the springs where the species occurs have been subjected to some level of modification. Based on recent survey data, it appears that the Page springsnail is abundant within natural habitats and persists in modified habitats, albeit at reduced densities. Arizona Game and Fish Department (AGFD) management plans for the Bubbling Ponds and Page Springs fish hatcheries include commitments to replace lost habitat and to monitor remaining populations of invertebrates such as the Page springsnail. The candidate conservation agreement with assurances (CCAA) for the Page springsnail calls for implementation of conservation measures such as restoration and creation of natural springhead integrity, including springs on AGFD properties. In fact, several conservation measures benefitting the species have already been implemented. Additionally, the National Park Service has expressed an interest in restoring natural springhead integrity to Shea Springs, a site historically occupied by Page springsnail. Accordingly, ongoing implementation of the CCAA reduces the magnitude of threats to a moderate level and greatly reduces the chances of extirpation or extinction. The immediacy of the threat of groundwater withdrawal is uncertain, due to conflicting information regarding imminence. However, overall, the threats are imminent, because modification of the species' habitat by threats other than groundwater withdrawal is currently occurring. Therefore, we retain an LPN of 8 for the Page springsnail.</P>
                    <P>
                        Phantom springsnail (
                        <E T="03">Tyronia cheatumi</E>
                        )—See summary above under Phantom Cave snail (
                        <E T="03">Cochliopa texana</E>
                        ).
                    </P>
                    <HD SOURCE="HD2">Insects</HD>
                    <P>
                        Mariana eight spot butterfly (
                        <E T="03">Hypolimnas octucula mariannensis</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The Mariana eight spot butterfly is a nymphalid butterfly species that feeds upon two host plants, 
                        <E T="03">Procris pedunculata</E>
                         and 
                        <E T="03">Elatostema calcareum.</E>
                         Endemic to the islands of Guam and Saipan, the species is now known from 10 populations on Guam. This species is currently threatened by predation and parasitism. The Mariana eight spot butterfly has extremely high mortality of eggs and larvae due to predation by alien ants and wasps. Because the threat of parasitism and predation by nonnative insects occur rangewide and can cause significant population declines to this species, they are high in magnitude. The threats are imminent because they are ongoing. Therefore, we assigned an LPN of 3 for this subspecies.
                    </P>
                    <P>
                        Mariana wandering butterfly (
                        <E T="03">Vagrans egestina</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The Mariana wandering butterfly is a nymphalid butterfly species that feeds upon a single host plant species, 
                        <E T="03">Maytenus thompsonii.</E>
                         Originally known from and endemic to the islands of Guam and Rota, the species is now known from one population on Rota. This species is currently threatened by alien predation and parasitism. The Mariana wandering butterfly is likely predated by alien ants and parasitized by native and nonnative parasitoids. Because the threats of parasitism and predation by nonnative insects occur rangewide and can cause significant population declines to this species, leading to a relatively high likelihood of extinction, they are high in magnitude. These threats are imminent because they are ongoing. Therefore, we assigned an LPN of 2 for this species.
                        <PRTPAGE P="66408"/>
                    </P>
                    <P>
                        Sequatchie caddisfly (
                        <E T="03">Glyphopsyche sequatchie</E>
                        )—The following summary is based on information in our files. No new information was provided in the petition we received on May 11, 2004. The Sequatchie caddisfly is known from two spring runs that emerge from caves in Marion County, Tennessee: Owen Spring Branch (the type locality) and Martin Spring run in the Battle Creek system. In 1998, biologists estimated population sizes at 500 to 5,000 individuals for Owen Spring Branch and 2 to 10 times higher at Martin Spring, due to the greater amount of apparently suitable habitat. In spite of greater amounts of suitable habitat at the Martin Spring run, Sequatchie caddisflies are more difficult to find at this site, and in 2001 (the most recent survey) the Sequatchie caddisfly was relatively “abundant” at the Owen Spring Branch location, while only two individuals were observed at the Martin Spring.
                    </P>
                    <P>Threats to the Sequatchie caddisfly include siltation, point and nonpoint discharges from municipal and industrial activities, and introduction of toxicants during episodic events. These threats, coupled with the extremely limited distribution of the species, its apparent small population size, the limited amount of occupied habitat, ease of accessibility, and the annual life cycle of the species, are all factors that leave the Sequatchie caddisfly vulnerable to extirpation. Therefore, the magnitude of the threat is high. These threats are gradual, and there is no basis to conclude that they are imminent. Based on high-magnitude and nonimminent threats, we assigned this species an LPN of 5.</P>
                    <P>
                        Clifton Cave beetle (
                        <E T="03">Pseudanophthalmus caecus</E>
                        )—The following summary is based upon information contained in our files. No new information was provided in the petition we received on May 11, 2004. Clifton Cave beetle is a small, eyeless, reddish-brown, predatory insect that feeds upon small cave invertebrates. It is cave dependent, and is not found outside the cave environment. Clifton Cave beetle is only known from two privately owned Kentucky caves. Soon after the species was first collected in 1963 in one cave, the cave entrance was enclosed due to road construction. We do not know whether the species still occurs at the original location or if it has been extirpated from the site by the closure of the cave entrance. Other caves in the vicinity of this cave were surveyed for the species during 1995 and 1996, and only one additional site was found to support the Clifton Cave beetle. The limestone caves in which the Clifton Cave beetle is found provide a unique and fragile environment that supports a variety of species that have evolved to survive and reproduce under the demanding conditions found in cave ecosystems. The limited distribution of the species makes it vulnerable to isolated events that would only have a minimal effect on more wide-ranging insects. Events such as toxic chemical spills, discharges of large amounts of polluted water or indirect impacts from off-site construction activities, closure of entrances, alteration of entrances, or the creation of new entrances could have serious adverse impacts on this species. Therefore, the magnitude of threat is high for this species. The threats are nonimminent because there are no known projects planned that would affect the species in the near future. We therefore have assigned an LPN of 5 to this species.
                    </P>
                    <P>
                        Coleman cave beetle (
                        <E T="03">Pseudanophthalmus colemanensis</E>
                        )—The following summary is based upon information contained in our files. No new information was provided in the petition we received on April 20, 2010. The Coleman cave beetle is a small, eyeless, reddish-brown, predatory insect that feeds upon small cave invertebrates. It is cave dependent and is not found outside the cave environment. It is only known from three Tennessee caves.
                    </P>
                    <P>The limestone caves in which this species is found provide a unique and fragile environment that support a variety of species that have evolved to survive and reproduce under the demanding conditions found in cave ecosystems. Caves and the species that are completely dependent upon them receive the energy that forms the basis of the cave food chain from outside the cave. This energy can be in the form of bat guano deposited by cave-dependent bats, large or small woody debris washed or blown into the cave, or tiny bits of organic matter carried into the cave by water through small cracks in the rocks overlaying the cave.</P>
                    <P>The Coleman cave beetle was originally known only from the privately owned Coleman Cave in Montgomery County. This cave formerly supported a colony of endangered gray bats. The bats have abandoned this cave because of air flow changes in the cave caused by closure of an upper entrance to the cave. Although the cave is protected by a cooperative management agreement with the landowner, the upper entrance has not been restored and the bats have not returned to the cave. A new location for the species was discovered during a biological inventory of Foster Cave (also known as Darnell Cave) when one specimen of the species was found during that survey. Foster Cave is on a preserve owned and managed by the Tennessee Department of Conservation. In 2006, specimens of this species were discovered in Bellamy Cave and in Darnell Spring Cave (part of the same cave complex as Foster Cave). All of these sites are in close proximity to each other. Bellamy Cave is owned and managed by the Tennessee Wildlife Resources Agency (TWRA). Both Foster Cave and Bellamy Cave were first acquired and protected by The Nature Conservancy and later transferred to the State for long-term protection and management.</P>
                    <P>The threats are nonimminent because there are no known projects planned that would affect the species in the next few years. Because it occurs at three locations and it receives some protection under a cooperative management agreement and protective ownership, the magnitude of threats is moderate to low. Thus, we have assigned an LPN of 11 to this species.</P>
                    <P>
                        Icebox Cave beetle (
                        <E T="03">Pseudanophthalmus frigidus</E>
                        )—The following summary is based upon information contained in our files. No new information was provided in the petition we received on May 11, 2004. Icebox Cave beetle is a small, eyeless, reddish-brown, predatory insect that feeds upon small cave invertebrates. It is not found outside the cave environment, and is only known from one privately owned Kentucky cave.
                    </P>
                    <P>
                        The limestone cave in which this species is found provides a unique and fragile environment that supports a variety of species that have evolved to survive and reproduce under the demanding conditions found in cave ecosystems. The species has not been observed since it was originally collected, but species experts believe that it may still exist in the cave in low numbers. The limited distribution of the species makes it vulnerable to isolated events that would only have a minimal effect on more wide-ranging insects. Events such as toxic chemical spills or discharges of large amounts of polluted water, or indirect impacts from off-site construction activities, closure of entrances, alteration of entrances, or the creation of new entrances, could have serious adverse impacts on this species. Therefore, the magnitude of threat is high for this species because it is limited in distribution and the threats would result in a high level of mortality or reduced reproductive capacity. The threats are nonimminent because there are no known projects planned that would affect the species in the near 
                        <PRTPAGE P="66409"/>
                        future. We therefore have assigned an LPN of 5 to this species.
                    </P>
                    <P>
                        Inquirer Cave beetle (
                        <E T="03">Pseudanophthalmus inquisitor</E>
                        )—The following summary is based upon information contained in our files. No new information was provided in the petition we received on May 11, 2004. The Inquirer Cave beetle is a fairly small, eyeless, reddish-brown, predatory insect that feeds upon small cave invertebrates. It is not found outside the cave environment, and is only known from one privately owned Tennessee cave.
                    </P>
                    <P>The limestone cave in which this species is found provides a unique and fragile environment that supports a variety of species that have evolved to survive and reproduce under the demanding conditions found in cave ecosystems. The species was last observed in 2006. The limited distribution of the species makes it vulnerable to isolated events that would only have a minimal effect on more wide-ranging insects. The area around the only known site for the species is in a rapidly expanding urban area. The entrance to the cave is protected by the landowner through a cooperative management agreement with the Service, The Nature Conservancy, and Tennessee Wildlife Resources Agency; however, a sinkhole that drains into the cave system is located away from the protected entrance and is near a highway. Events such as toxic chemical spills, discharges of large amounts of polluted water, or indirect impacts from off-site construction activities could adversely affect the species and the cave habitat.</P>
                    <P>The magnitude of threat is high for this species because it is limited in distribution and the threats would have negative impacts on its continued existence. The threats are nonimminent because there are no known projects planned that would affect the species in the near future and the species receives some protection under a cooperative management agreement. We therefore have assigned an LPN of 5 to this species.</P>
                    <P>
                        Louisville Cave beetle (
                        <E T="03">Pseudanophthalmus troglodytes</E>
                        )—The following summary is based upon information contained in our files. No new information was provided in the petition we received on May 11, 2004. The Louisville cave beetle is a small, eyeless, reddish-brown, predatory insect that feeds upon cave invertebrates. It is not found outside the cave environment, and is only known from two privately owned Kentucky caves.
                    </P>
                    <P>The limestone caves in which this species is found provide a unique and fragile environment that supports a variety of species that have evolved to survive and reproduce under the demanding conditions found in cave ecosystems. The limited distribution of the species makes it vulnerable to isolated events that would only have a minimal effect on more wide-ranging insects. Events such as toxic chemical spills, discharges of large amounts of polluted water, or indirect impacts from off-site construction activities, closure of entrances, alteration of entrances, or the creation of new entrances could have serious adverse impacts on this species. The magnitude of threat is high for this species, because it is limited in distribution and the threats would have severe negative impacts on the species. The threats are nonimminent because there are no known projects planned that would affect the species in the near future. We therefore have assigned an LPN of 5 to this species.</P>
                    <P>
                        Tatum Cave beetle (
                        <E T="03">Pseudanophthalmus parvus</E>
                        ) — The following summary is based upon information contained in our files. No new information was provided in the petition we received on May 11, 2004. Tatum Cave beetle is a small, eyeless, reddish-brown, predatory insect that feeds upon cave invertebrates. It is not found outside the cave environment, and is only known from one privately owned Kentucky cave.
                    </P>
                    <P>The limestone cave in which this species is found provides a unique and fragile environment that supports a variety of species that have evolved to survive and reproduce under the demanding conditions found in cave ecosystems. The species has not been observed since 1965, but species experts believe that it still exists in low numbers. The limited distribution of the species makes it vulnerable to isolated events that would only have a minimal effect on more wide-ranging insects. Events such as toxic chemical spills, discharges of large amounts of polluted water, or indirect impacts from off-site construction activities, closure of entrances, alteration of entrances, or the creation of new entrances could have serious adverse impacts on this species. The magnitude of threat is high for this species, because its limited numbers mean that any threats could severely affect its continued existence. The threats are nonimminent because there are no known projects planned that would affect the species in the near future. We therefore have assigned an LPN of 5 to this species.</P>
                    <P>
                        Taylor's (Whulge, Edith's) checkerspot butterfly (
                        <E T="03">Euphydryas</E>
                          
                        <E T="03">editha</E>
                          
                        <E T="03">taylori</E>
                        )—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Orangeblack Hawaiian damselfly (
                        <E T="03">Megalagrion xanthomelas</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The orangeblack Hawaiian damselfly is a stream-dwelling species endemic to the Hawaiian Islands of Kauai, Oahu, Molokai, Maui, Lanai, and Hawaii. The species no longer is found on Kauai, and is now restricted to 16 populations on the islands of Oahu, Maui, Molokai, Lanai, and Hawaii. This species is threatened by predation from alien aquatic species such as fish and predacious insects, and habitat loss through dewatering of streams and invasion by nonnative plants. Nonnative fish and insects prey on the naiads of the damselfly, and loss of water reduces the amount of suitable naiad habitat available. Invasive plants (e.g., California grass (
                        <E T="03">Brachiaria mutica</E>
                        )) also contribute to loss of habitat by forming dense, monotypic stands that completely eliminate any open water. Nonnative fish and plants are found in all the streams the orangeblack damselfly occur in, except the Oahu location, where there are no nonnative fish. We assigned this species an LPN of 8 because, although the threats are ongoing and therefore imminent, they affect the survival of the species in varying degrees throughout the range of the species and are therefore of moderate magnitude.
                    </P>
                    <P>
                        Picture-wing fly (
                        <E T="03">Drosophila digressa</E>
                        )—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Stephan's riffle beetle (
                        <E T="03">Heterelmis stephani</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition received on May 11, 2004. The Stephan's riffle beetle is an endemic riffle beetle found in limited spring environments within the Santa Rita Mountains, Pima County, Arizona. The beetle is known from Sylvester Spring in Madera Canyon, within the Coronado National Forest. Threats to that spring are largely from habitat modification, recreational activities in the springs, and potential changes in water quality and quantity due to 
                        <PRTPAGE P="66410"/>
                        catastrophic natural events and climate change. The threats are of low to moderate magnitude based on our current knowledge of the permanence of threats and the likelihood that the species will persist in areas that are unaffected by the threats. Although the threats from climate change are expected to occur over many years, the threats from recreational use are ongoing. Therefore, the threats are imminent. Thus, we retain an LPN of 8 for the Stephan's riffle beetle.
                    </P>
                    <P>
                        Dakota skipper (
                        <E T="03">Hesperia dacotae</E>
                        )—The following summary is based on information contained in our files, including information from the petition received on May 12, 2003. The Dakota skipper is a small- to mid-sized butterfly that inhabits high-quality tallgrass and mixed-grass prairie in Minnesota, North Dakota and South Dakota in the United States, and the provinces of Manitoba and Saskatchewan in Canada. The species is presumed to be extirpated from Iowa and Illinois and from many sites within occupied U.S. States.
                    </P>
                    <P>The Dakota skipper is threatened by degradation of its native prairie habitat by overgrazing, invasive species, gravel mining, and herbicide applications; inbreeding, population isolation, and prescribed fire threaten some populations. Prairie succeeds to shrubland or forest without periodic fire, grazing, or mowing; thus, the species is also threatened at sites where such disturbances are not applied. The Service and other Federal agencies, State agencies, the Sisseton-Wahpeton Sioux Tribe, and some private organizations (e.g., The Nature Conservancy) protect and manage some Dakota skipper sites. Careful and considered management is always necessary to ensure the species' persistence, even at protected sites. The species may be secure at a few sites where public and private landowners manage native prairie in ways that conserve Dakota skipper, but approximately half of the inhabited sites are privately owned with little or no protection. A few private sites are protected from conversion by easements, but these do not preclude adverse effects from overgrazing. The threats are such that the Dakota skipper warrants listing. The threats are moderate in magnitude because some sites are protected through careful and considered management, and therefore they do not affect the species uniformly throughout its range. The threats are ongoing, and therefore imminent. We assigned this species an LPN of 8 to reflect the immediacy of threats to remnant habitat, particularly on private lands.</P>
                    <P>
                        Mardon skipper (
                        <E T="03">Polites mardon</E>
                        )—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        Meltwater lednian stonefly (
                        <E T="03">Lednia tumana</E>
                        )—See above in “Listing
                        <E T="03"/>
                         Priority Changes in Candidates.” The above summary is based on information contained in our files.
                    </P>
                    <P>
                        Coral Pink Sand Dunes tiger beetle (
                        <E T="03">Cicindela limbata</E>
                          
                        <E T="03">albissima</E>
                        )—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        Highlands tiger beetle (
                        <E T="03">Cicindela highlandensis</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The Highlands tiger beetle is narrowly distributed and restricted to areas of bare sand within scrub and sandhill on ancient sand dunes of the Lake Wales Ridge in Polk and Highlands Counties, Florida. Adult tiger beetles have been most recently found at 40 sites at the core of the Lake Wales Ridge. In 2004-2005 surveys, a total of 1,574 adults were found at 40 sites, compared with 643 adults at 31 sites in 1996, 928 adults at 31 sites in 1995, and 742 adults at 21 sites in 1993. Of the 40 sites in the 2004-2005 surveys with one or more adults, results ranged from 3 sites with large populations of over 100 adults, to 13 sites with fewer than 10 adults. Results from a limited removal study at four sites and similar studies suggest that the actual population size at some survey sites can be as much as two times as high as indicated by the visual index counts. If assumptions are correct and unsurveyed habitat is included, then the total number of adults at all survey sites might be 3,000 to 4,000.
                    </P>
                    <P>Habitat loss and fragmentation and lack of fire and disturbances to create open habitat conditions are serious threats; remaining patches of suitable habitat are disjunct and isolated. Populations occupy relatively small patches of habitat and are small and isolated; individuals have difficulty dispersing between suitable habitats. These factors pose serious threats to the species. Although significant progress in implementing prescribed fire has occurred over the last 10 years through collaborative partnerships and the Lake Wales Ridge Prescribed Fire Team, a backlog of long-unburned habitat within conservation areas remains. Overcollection and pesticide use are additional concerns. Because this species is narrowly distributed with specific habitat requirements and small populations, any of the threats could have a significant impact on the survival of the species. Therefore, the magnitude of threats is high. Although the majority of its historical range has been lost, degraded, and fragmented, numerous sites are protected and land managers are implementing prescribed fire at some sites; these actions are expected to restore habitat and help reduce threats and have already helped stabilize and improve the populations. Therefore, overall, the threats are nonimminent, and we assigned the Highlands tiger beetle an LPN of 5.</P>
                    <HD SOURCE="HD2">Arachnids</HD>
                    <P>
                        Warton's cave meshweaver (
                        <E T="03">Cicurina wartoni</E>
                        )—See above in “Listing Priority Changes in Candidates.” The above summary is based on information contained in our files.
                    </P>
                    <HD SOURCE="HD2">Crustaceans</HD>
                    <P>
                        Anchialine pool shrimp (
                        <E T="03">Metabetaeus lohena</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Metabetaeus lohena</E>
                         is an anchialine pool-inhabiting species of shrimp belonging to the family Alpheidae. This species is endemic to the Hawaiian Islands and is currently known from populations on the islands of Oahu, Maui, and Hawaii. The primary threats to this species are predation by fish (which do not naturally occur in the pools inhabited by this species) and habitat loss from degradation (primarily from illegal trash dumping). The pools where this species occurs on the islands of Maui and Hawaii are located within State Natural Area Reserves (NAR) and in a National Park. Both the State NARs and the National Park prohibit the collection of the species and the disturbance of the pools. However, enforcement of collection and disturbance prohibitions is difficult, and the negative effects from the introduction of fish are extensive and happen quickly. On Oahu, one pool is located in a National Wildlife Refuge, and is protected from collection and disturbance to the pool. However, on State-owned land where the species occurs, there is no protection from collection or disturbance of the pools. Therefore, threats to this species could have a significant adverse effect on the survival of the species, leading to a relatively high likelihood of extinction, 
                        <PRTPAGE P="66411"/>
                        and are of a high magnitude. However, the primary threats of predation from fish and loss of habitat due to degradation are nonimminent overall, because on the islands of Maui and Hawaii no fish were observed in any of the pools where this species occurs and there has been no documented trash dumping in these pools. Only one site on Oahu had a trash dumping instance, and in that case the trash was cleaned up immediately and the species subsequently observed. No additional dumping events are known to have occurred. Therefore, we assigned this species an LPN of 5.
                    </P>
                    <P>
                        Anchialine pool shrimp (
                        <E T="03">Palaemonella burnsi</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Palaemonella burnsi</E>
                         is an anchialine pool-inhabiting species of shrimp belonging to the family Palaemonidae. This species is endemic to the Hawaiian Islands and is currently known from 3 pools on the island of Maui and 22 pools on the island of Hawaii. The primary threats to this species are predation by fish (which do not naturally occur in the pools inhabited by this species) and habitat loss due to degradation (primarily from illegal trash dumping). The pools where this species occurs on Maui are located within a State Natural Area Reserve (NAR). Hawaii's State statutes prohibit the collection of the species and the disturbance of the pools in State NARs. On the island of Hawaii, the species occurs within a State NAR and a National Park, and collection and disturbance are also prohibited. However, enforcement of these prohibitions is difficult, and the negative effects from the introduction of fish are extensive and happen quickly. Therefore, threats to this species could have a significant adverse effect on the survival of the species, leading to a relatively high likelihood of extinction, and are of a high magnitude. However, the threats are nonimminent, because surveys in 2004 and 2007 did not find fish in the pools where these shrimp occur on Maui or the island of Hawaii. Also, there was no evidence of recent habitat degradation at those pools. We assigned this species an LPN of 5.
                    </P>
                    <P>
                        Anchialine pool shrimp (
                        <E T="03">Procaris hawaiana</E>
                        )—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Procaris hawaiana</E>
                         is an anchialine pool-inhabiting species of shrimp belonging to the family Procarididae. This species is endemic to the Hawaiian Islands, and is currently known from 2 pools on the island of Maui and 13 pools on the island of Hawaii. The primary threats to this species are predation from fish (which do not naturally occur in the pools inhabited by this species) and habitat loss due to degradation (primarily from illegal trash dumping). The pools where this species occurs on Maui are located within a State Natural Area Reserve (NAR). Twelve of the pools on the island of Hawaii are located within a State NAR. Hawaii's State statutes prohibit the collection of the species and the disturbance of the pools in State NARs. However, enforcement of these prohibitions is difficult, and the negative effects from the introduction of fish are extensive and happen quickly. In addition, there are no prohibitions for either removal of the species or disturbance to the pool for the one pool located outside a NAR on the island of Hawaii. Therefore, threats to this species could have a significant adverse effect on the survival of the species, leading to a relatively high likelihood of extinction, and thus remain at a high magnitude. However, the threats to the species are nonimminent because, during 2004 and 2007 surveys, no fish were observed in the pools where these shrimp occur on Maui, and no fish were observed in the one pool on the island of Hawaii during a site visit in 2005. In addition, there were no signs of trash dumping or fill in any of the pools where the species occurs. Therefore, we assigned this species an LPN of 5.
                    </P>
                    <P>
                        Anchialine pool shrimp (
                        <E T="03">Vetericaris chaceorum</E>
                        )—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <HD SOURCE="HD2">Flowering Plants</HD>
                    <P>
                        <E T="03">Abronia alpina</E>
                         (Ramshaw Meadows sand-verbena)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Abronia alpina</E>
                         is a small perennial herb, 2.5 to 15.2 centimeters (1 to 6 inches) across, forming compact mats with lavender-pink, trumpet-shaped, and generally fragrant flowers. 
                        <E T="03">Abronia alpina</E>
                         is known from one main population center at Ramshaw Meadow and a smaller population at the adjacent Templeton Meadow. The meadows are located on the Kern River Plateau in the Sierra Nevada, on lands administered by the Inyo National Forest, in Tulare County, California. The total estimated area occupied is approximately 6 hectares (15 acres). The population fluctuates from year to year without any clear trends. Population estimates for the years from 1985 through 2009, ranged from a high of approximately 130,000 plants in 1997, to a low of approximately 40,000 plants in 2003. In 2009, when the population was last monitored, the estimated total population increased again to just over 120,000 plants.
                    </P>
                    <P>
                        The factors currently threatening 
                        <E T="03">Abronia alpina</E>
                         include natural and human habitat alteration, lowering of the water table due to erosion within the meadow system, and recreational use within meadow habitats. Lodgepole pines are encroaching upon meadow habitat with trees germinating within 
                        <E T="03">A. alpina</E>
                         habitat, occupying up to 20 percent of two 
                        <E T="03">A. alpina</E>
                         subpopulations. Lodgepole pine encroachment may alter soil characteristics by increasing organic matter levels, decreasing porosity, and moderating diurnal temperature fluctuations, thus reducing the competitive ability of 
                        <E T="03">A. alpina</E>
                         to persist in an environment more hospitable to other plant species.
                    </P>
                    <P>
                        The habitat occupied by 
                        <E T="03">Abronia alpina</E>
                         directly borders the meadow system, which is supported by the South Fork of the Kern River. The river flows through the meadow, at times coming within 15 m (50 ft) of 
                        <E T="03">Abronia alpina</E>
                         habitat, particularly in the vicinity of five subpopulations. Livestock trampling, along with the removal of bank stabilizing vegetation by grazing livestock, has contributed to downcutting of the river channel through the meadow, leaving the meadow subject to potential alteration by lowering of the water table. In 2001, the U.S. Forest Service began resting the grazing allotment for 10 years, eliminating cattle use up through the present time. The U.S. Forest Service is currently assessing the data collected on the rested allotment and, if the data indicate that sufficient watershed recovery has occurred, may conduct an environmental analysis to consider resumption of grazing.
                    </P>
                    <P>
                        Established hiker, packstock, and cattle trails pass through 
                        <E T="03">A. alpina</E>
                         subpopulations. Two main hiker trails pass through Ramshaw Meadow, but in 1988 and 1997, they were rerouted out of 
                        <E T="03">A. alpina</E>
                         subpopulations where feasible. Occasional incidental use by horses and hikers sometimes occurs on the remnants of cattle trails that pass through subpopulations in several places. The Service has funded studies to determine appropriate conservation measures for the species, and is working 
                        <PRTPAGE P="66412"/>
                        with the U.S. Forest Service on developing a conservation strategy for the species. The threats are of a low magnitude and nonimminent because of the conservation actions already implemented. The LPN for 
                        <E T="03">A. alpina</E>
                         remains an 11, with nonimminent threats of moderate to low magnitude.
                    </P>
                    <P>
                        <E T="03">Arabis georgiana</E>
                         (Georgia rockcress)—The following summary is based on information in our files. No new information was provided in the petition we received on May 11, 2004. The Georgia rockcress grows in a variety of dry situations, including shallow soil accumulations on rocky bluffs, ecotones of gently sloping rock outcrops, and sandy loam along eroding river banks. It is occasionally found in adjacent mesic woods, but it will not persist in heavily shaded conditions. Currently, 16 natural populations are known from the Gulf Coastal Plain, Piedmont, and Ridge and Valley physiographic provinces of Alabama and Georgia. Populations of this species typically have a limited number of individuals over a small area.
                    </P>
                    <P>
                        Habitat degradation, more than outright habitat destruction, is the most serious threat to the continued existence of this species. Disturbance, associated with timber harvesting, road building, and grazing, has created favorable conditions for the invasion of exotic weeds, especially Japanese honeysuckle (
                        <E T="03">Lonicera japonica</E>
                        ), in this species' habitat. A large number of the populations are currently or potentially threatened by the presence of exotics. The heritage programs in Alabama and Georgia have initiated plans for exotic control at several populations. The magnitude of threats to this species is moderate to low due to the number of populations (16) across multiple counties in two States and due to the fact that several sites are protected. However, as a number of the populations are currently being affected by nonnative plants, the threat is imminent. Thus, we assigned an LPN of 8 to this species.
                    </P>
                    <P>
                        <E T="03">Argythamnia blodgettii</E>
                         (Blodgett's silverbush)—The following summary is based on information in our files. No new information was provided in the petition we received on May 11, 2004. Blodgett's silverbush occurs in Florida and is found in open, sunny areas in pine rockland, edges of rockland hammock, edges of coastal berm, and sometimes disturbed areas at the edges of natural areas. Plants can be found growing from crevices on limestone, or on sand. The pine-rockland habitat where the species occurs in Miami-Dade County and the Florida Keys requires periodic fires to maintain habitat with a minimum amount of hardwoods. There are approximately 22 extant occurrences, 12 in Monroe County and 10 in Miami-Dade County; many occurrences are on conservation lands. However, 4 to 5 sites are recently thought to be extirpated. The estimated population size of Blodgett's silverbush in the Florida Keys, excluding Big Pine Key, is roughly 11,000; the estimated population in Miami-Dade County is 375 to 13,650 plants.
                    </P>
                    <P>Blodgett's silverbush is threatened by habitat loss, which is exacerbated by habitat degradation due to fire suppression, the difficulty of applying prescribed fire to pine rocklands, and threats from exotic plants. Remaining habitats are fragmented. Threats such as road maintenance and enhancement, infrastructure, and illegal dumping threaten some occurrences. Blodgett's silverbush is vulnerable to natural disturbances, such as hurricanes, tropical storms, and storm surges. Climatic changes, including sea-level rise, are long-term threats that are expected to continue to affect pine rocklands and ultimately substantially reduce the extent of available habitat, especially in the Keys. Overall, the magnitude of threats is moderate because not all of the occurrences are affected by the threats. In addition, land managers are aware of the threats from exotic plants and lack of fire, and are, to some extent, working to reduce these threats where possible. While a number of threats are occurring in some areas, the threat from development is nonimminent as most occurrences are on public land, and sea level rise is not currently affecting this species. Overall, the threats are nonimminent. Thus, we assigned an LPN of 11 to this species.</P>
                    <P>
                        <E T="03">Artemisia</E>
                          
                        <E T="03">borealis</E>
                         var. 
                        <E T="03">wormskioldii</E>
                         (Northern wormwood)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. Historically known from eight sites, northern wormwood is currently known from two populations in Klickitat and Grant Counties, Washington. This plant is restricted to exposed basalt, cobbly-sandy terraces, and sand habitat along the shore and on islands in the Columbia River. The two populations are separated by 200 miles (322 kilometers) of the Columbia River and three large hydroelectric dams. The Klickitat County population is declining; the status is unclear for the Grant County population; however, both are vulnerable to environmental variability. Numerous surveys have not detected additional plants.
                    </P>
                    <P>
                        Threats to northern wormwood include direct loss of habitat through regulation of water levels in the Columbia River and placement of riprap along the river bank; human trampling of plants from recreation; competition with nonnative, invasive species; burial by wind- and water-borne sediments; small population sizes; susceptibility to genetic drift and inbreeding; and the potential for hybridization with two other species of 
                        <E T="03">Artemisia.</E>
                         Ongoing conservation actions have reduced trampling, but have not eliminated or reduced the other threats at the Grant County site. Active conservation measures are not currently in place at the Miller Island site. The magnitude of threat is high for this subspecies because, although the two remaining populations are widely separated and distributed, one or both populations could be eliminated by a single disturbance. The threats are imminent because recreational use is ongoing; invasive nonnative species occur at both sites; windblown erosion and deposition of the substrate is ongoing at the Klickitat County site; and high water flows may occur unpredictably in any year. Therefore, we have retained an LPN of 3 for this subspecies.
                    </P>
                    <P>
                        <E T="03">Astragalus anserinus</E>
                         (Goose Creek milkvetch)—The following summary is based on information in our files and in the petition received on February 3, 2004. The majority (over 80 percent) of 
                        <E T="03">Astragalus anserinus</E>
                         sites in Idaho, Utah, and Nevada occur on Federal lands managed by the Bureau of Land Management. The rest of the sites occur as small populations on private and State lands in Utah and on private land in Idaho and Nevada. 
                        <E T="03">A. anserinus</E>
                         occurs in a variety of habitats, but is typically associated with dry, tuffaceous (made up of rock consisting of smaller kinds of volcanic detritus) soils from the Salt Lake Formation. The species grows on steep or flat sites, with soil textures ranging from silty to sandy to somewhat gravelly. The species tolerates some level of disturbance, based on its occurrence on steep slopes where downhill movement of soil is common.
                    </P>
                    <P>
                        The primary threats to remaining 
                        <E T="03">A. anserinus</E>
                         individuals consist of habitat degradation and modifications to the ecosystem in which it occurs resulting from an altered wildfire regime, and associated activities to control wildfires and rehabilitate burned-over areas. Other factors that also appear to threaten 
                        <E T="03">A. anserinus</E>
                         include livestock use, invasive nonnative species, and the inadequacy of regulatory mechanisms. Climate change effects to Goose Creek drainage habitats are possible, but we are unable to predict the specific impacts of this change to 
                        <E T="03">A. anserinus</E>
                         at this time. Threats are high in 
                        <PRTPAGE P="66413"/>
                        magnitude, as these threats have the potential to destroy whole populations. The threats are nonimminent because they are not currently ongoing. Thus, we have assigned 
                        <E T="03">A. anserinus</E>
                         an LPN of 5.
                    </P>
                    <P>
                        <E T="03">Astragalus microcymbus</E>
                         (Skiff milkvetch)—The following summary is based on information contained in our files and in the petition we received on July 30, 2007. 
                        <E T="03">Astragalus microcymbus</E>
                         is a perennial forb that dies back to the ground every year. It has a very limited range and a spotty distribution within Gunnison and Saguache Counties in Colorado, where it is found in open, park-like landscapes in the sagebrush steppe ecosystem on rocky or cobbly, moderate to steep slopes of hills and draws. The most significant threats to 
                        <E T="03">A. microcymbus</E>
                         are recreation, roads, trails, the overall inadequacy of existing regulatory mechanisms, and habitat fragmentation and degradation. Recreational impacts are likely to increase given the close proximity of 
                        <E T="03">A. microcymbus</E>
                         to the town of Gunnison and the increasing popularity of mountain biking, motorcycling, and all-terrain vehicles. Furthermore, the Hartman Rocks Recreation Area draws users and contains over 40 percent of the 
                        <E T="03">A. microcymbus</E>
                         units. Other threats to the species include residential and urban development; livestock, deer, and elk use; climate change; and increasing periodic drought, nonnative invasive cheatgrass, and wildfire. We consider the threats to 
                        <E T="03">A. microcymbus</E>
                         to be moderate in magnitude because while serious and occurring rangewide, they do not collectively result in having a greater likelihood of bringing about extinction on a short time scale. The threats are imminent because the species is currently facing them in many portions of its range. Therefore we have assigned 
                        <E T="03">A. microcymbus</E>
                         an LPN of 8.
                    </P>
                    <P>
                        <E T="03">Astragalus schmolliae</E>
                         (Schmoll milkvetch)—The following summary is based on information contained in our files and in the petition we received on July 30, 2007. 
                        <E T="03">Astragalus schmolliae</E>
                         is a narrow endemic perennial plant that grows in the mature pinyon-juniper woodland of mesa tops in the Mesa Verde National Park area and in the Ute Mountain Ute Tribal Park in Colorado. The most significant threats to the species are degradation of habitat by fire, followed by invasion by nonnative cheatgrass and subsequent increase in fire frequency. These threats currently affect about 40 percent of the species' entire known range, and cheatgrass is likely to increase given its rapid spread and persistence in habitat disturbed by wildfires, fire and fuels management and development of infrastructure, and the inability of land managers to control it on a landscape scale. Other threats to 
                        <E T="03">A. schmolliae</E>
                         include fires, fire break clearings, drought, and inadequate regulatory mechanisms. The threats to the species overall are imminent and moderate in magnitude, because the species is currently facing them in many portions of its range, but the threats do not collectively result in having a greater likelihood of bringing about extinction on a short time scale. Therefore we have assigned 
                        <E T="03">A. schmolliae</E>
                         an LPN of 8.
                    </P>
                    <P>
                        <E T="03">Astragalus tortipes</E>
                         (Sleeping Ute milkvetch)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Astragalus tortipes</E>
                         is a perennial plant that grows only on the Smokey Hills layer of the Mancos Shale Formation on the Ute Mountain Ute Indian Reservation in Montezuma County, Colorado. In 2000, 3,744 plants were recorded at 24 locations covering 500 acres within an overall range of 6,400 acres. Available information from 2000 indicates that the species remains stable.
                    </P>
                    <P>Previous and ongoing threats from borrow pit excavation, off-highway vehicles, irrigation canal construction, and a prairie dog colony have had minor impacts that reduced the range and number of plants by small amounts. Off-highway vehicle use of the habitat has reportedly been controlled by fencing. Oil and gas development is active in the general area, but the Service has received no information to indicate that there is development within plant habitat. The Tribe reported that the status of the species remains unchanged, the population is healthy, and a management plan for the species is currently in draft form. Despite these positive indications, we have no documentation concerning the current status of the plants, condition of habitat, and terms of the species management plan being drafted by the Tribe. Thus, at this time, we cannot accurately assess whether populations are being adequately protected from previously existing threats. The threats are moderate in magnitude, because they have had minor impacts. Based on information we have, the population appears to be stable. Until the management plan is completed and made available, there are no regulatory mechanisms in place to protect the species. Overall, we conclude threats are nonimminent. Therefore, we assigned an LPN of 11 to this species.</P>
                    <P>
                        <E T="03">Bidens campylotheca</E>
                         ssp. 
                        <E T="03">pentamera</E>
                         (Kookoolau)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Bidens campylotheca</E>
                         ssp. 
                        <E T="03">waihoiensis</E>
                         (Kookoolau)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Bidens conjuncta</E>
                         (Kookoolau)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Bidens micrantha</E>
                         ssp. 
                        <E T="03">ctenophylla</E>
                         (Kookoolau)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        <E T="03">Brickellia mosieri</E>
                         (Florida brickell-bush)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. This species is restricted to pine rocklands of Miami-Dade County, Florida. This habitat requires periodic prescribed fires to maintain the low understory and prevent encroachment by native tropical hardwoods and exotic plants, such as Brazilian pepper. Only one large occurrence is known to exist; 15 other occurrences contain less than 100 individuals. Eleven occurrences are on conservation lands, while the rest of the extant populations are on private land and are currently vulnerable to habitat loss and degradation.
                    </P>
                    <P>
                        Climatic changes, including sea-level rise, are long-term threats that will reduce the extent of habitat. This species is threatened by habitat loss, which is exacerbated by habitat degradation due to fire suppression, the difficulty of applying prescribed fire to pine rocklands, and threats from exotic plants. Remaining habitats are fragmented. The species is vulnerable to natural disturbances, such as hurricanes, tropical storms, and storm surges. Due to its restricted range and the small sizes of most isolated occurrences, this species is vulnerable to environmental (catastrophic hurricanes), demographic (potential episodes of poor reproduction), and genetic (potential inbreeding 
                        <PRTPAGE P="66414"/>
                        depression) threats. Ongoing conservation efforts include projects aimed at facilitating restoration and management of public and private lands in Miami-Dade County and projects to reintroduce and establish new populations at suitable sites within the species' historical range. The Service is also pursuing additional habitat restoration projects, which could help further improve the status of the species. Because of these efforts, the overall magnitude of threats is moderate. The threats are ongoing and thus imminent. We assigned this species an LPN of 8.
                    </P>
                    <P>
                        <E T="03">Calamagrostis expansa</E>
                         (Maui reedgrass)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Calamagrostis expansa</E>
                         is a perennial grass found in wet forest and bogs, and in bog margins, on the islands of Maui and Hawaii, Hawaii. This species is known from 13 populations totaling fewer than 750 individuals.
                    </P>
                    <P>
                        <E T="03">Calamagrostis expansa</E>
                         is threatened by habitat degradation and loss by feral pigs, and by competition with nonnative plants. Predation by feral pigs is a potential threat to this species. All of the known populations of 
                        <E T="03">C. expansa</E>
                         on Maui occur in managed areas. Pig exclusion fences have been constructed and control of nonnative plants is ongoing within the exclosures. On the island of Hawaii, fencing is planned for the population in the Upper Waiakea Forest Reserve. This species is represented in an ex situ collection. Predation is a nonimminent threat. However, threats to this species from feral pigs and nonnative plants are ongoing, or imminent, and of high magnitude because they significantly affect the species throughout its range, leading to a relatively high likelihood of extinction. Therefore, we retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Calamagrostis hillebrandii</E>
                         (Hillebrand's reedgrass)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Calochortus persistens</E>
                         (Siskiyou mariposa lily)—The following summary is based on information contained in our files and the petition we received on September 10, 2001. The Siskiyou mariposa lily is a narrow endemic that is restricted to three disjunct ridge tops in the Klamath-Siskiyou Range on the California-Oregon border. The southernmost occurrence of this species is composed of nine separate sites on approximately 10 hectares (ha) (24.7 acres (ac)) of Klamath National Forest and privately owned lands that stretch for 6 kilometers (km) (3.7 miles (mi)) along the Gunsight-Humbug Ridge, Siskiyou County, California. In 2007, a new occurrence was confirmed in the locality of Cottonwood Peak and Little Cottonwood Peak, Siskiyou County, where several populations are distributed over 164 ha (405 ac) on three individual mountain peaks in the Klamath National Forest and on private lands. The northernmost occurrence consists of not more than five Siskiyou mariposa lily plants that were discovered in 1998, on Bald Mountain, west of Ashland, Jackson County, Oregon.
                    </P>
                    <P>
                        Major threats include competition and shading by native and nonnative species fostered by suppression of wildfire; increased fuel loading and subsequent risk of wildfire; fragmentation by roads, fire breaks, tree plantations, and radio-tower facilities; maintenance and construction around radio towers and telephone relay stations located on Gunsight Peak and Mahogany Point; and soil disturbance, direct damage, and exotic weed and grass species introduction as a result of heavy recreational use and construction of fire breaks. Dyer's woad (
                        <E T="03">Isatis tinctoria</E>
                        ), an invasive, nonnative plant that may prevent germination of Siskiyou mariposa lily seedlings, is now found throughout the southernmost California occurrence, affecting 75 percent of the known lily habitat on Gunsight-Humbug Ridge. Forest Service staff and the Klamath-Siskiyou Wildlands Center cite competition with dyer's woad as a significant and chronic threat to the survival of Siskiyou mariposa lily.
                    </P>
                    <P>The combination of restricted range, extremely low numbers (five plants) in one of three disjunct populations, poor competitive ability, short seed dispersal distance, slow growth rates, low seed production, apparently poor survival rates in some years, herbivory, habitat disturbance, and competition from exotic plants threaten the continued existence of this species. These threats are of high magnitude because of their potential to affect the overall survival of the species negatively. Because the threats of competition from exotic plants are being addressed, they are not anticipated to overwhelm a large portion of the species' range in the immediate future; in additions the threats from low seed production and survival are longer-term threats. Thus, overall the threats are nonimminent. As such, we assigned an LPN of 5 to this species.</P>
                    <P>
                        <E T="03">Canavalia pubescens</E>
                         (Awikiwiki)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Castilleja christii</E>
                         (Christ's paintbrush)—The following summary is based on information contained in our files and the petition we received on January 2, 2001. 
                        <E T="03">Castilleja christii</E>
                         is found in one population covering approximately 85 ha (220 ac) on the summit of Mount Harrison in Cassia County, Idaho. This endemic species is considered a hemiparasite (dependent on the health of their surrounding native plant community), and it grows in association with subalpine-meadow and sagebrush habitats. The population may be large (greater than 10,000 individual plants); however, the species is considered to be subject to large variations in annual abundance and an accurate current population estimate is not available. Monitoring indicates that reproductive stems per plant and plant density declined between 1995 and 2007. Fluctuations have occurred since 2007, with slight increases in reproductive output and density in 2008 and decreases in 2009. Population monitoring did not occur in 2010.
                    </P>
                    <P>
                        The primary threat to the species is the nonnative, invasive plant smooth brome (
                        <E T="03">Bromus inermis</E>
                        ). Despite cooperative Forest Service and Service efforts to control smooth brome in 2007, 2008, 2009, and 2010, it still persists in 
                        <E T="03">C. christii</E>
                         habitats. Other threats to 
                        <E T="03">C. christii</E>
                         from recreational use and livestock trespass appear to be mostly seasonal and affect only a small portion of the population, and may not occur every year. The magnitude of the threats to this species is moderate at this time because, although the smooth brome control efforts have not eliminated the invasive plant, the Service and Forest Service are continuing their efforts in order to conserve this species. The threat from smooth brome is imminent because the threat still persists at a level that affects the native plant communities that provide habitat for 
                        <E T="03">C. christii.</E>
                         Thus, we assign an LPN of 8 to this species.
                    </P>
                    <P>
                        <E T="03">Chamaecrista lineata</E>
                         var
                        <E T="03">. keyensis</E>
                         (Big Pine partridge pea)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. This pea is endemic to the lower Florida Keys, and restricted to pine rocklands, hardwood hammock edges, and roadsides and firebreaks within these 
                        <PRTPAGE P="66415"/>
                        ecosystems. Historically, it was known from Big Pine, Cudjoe, No Name, Ramrod, and Little Pine Keys (Monroe County, Florida). In 2005, a small population was detected on lower Sugarloaf Key, but this population was not located after Hurricane Wilma; plants were likely killed by the tidal surge from this storm. It presently occurs on Big Pine Key, with a very small population on Cudjoe Key. It is fairly well distributed in Big Pine Key pine rocklands, which encompass approximately 580 hectares (1,433 acres), approximately 360 hectares (890 acres) of which are within the Service's National Key Deer Refuge (NKDR). Over 80 percent of the population probably exists on NKDR, with the remainder distributed among State, County, and private properties. Hurricane Wilma (October 2005) resulted in a storm surge that covered most of Big Pine Key with sea water. The surge reduced the population by as much as 95 percent in some areas.
                    </P>
                    <P>Pine rockland communities are maintained by relatively frequent fires. In the absence of fire, shrubs and trees encroach on pine rockland, and this subspecies is eventually shaded out. NKDR has a prescribed fire program, although with many constraints on implementation. Habitat loss due to development was historically the greatest threat to the pea. Much of the remaining habitat is now protected on public lands. Absence of fire now appears to be the greatest of the deterministic threats. Given the recent increase in hurricane activity, storm surges are the greatest of the stochastic threats. The small range and patchy distribution of the subspecies increase risk from stochastic events. Climatic changes, including sea-level rise, are serious long-term threats. Models indicate that even under the best of circumstances, a significant proportion of upland habitat will be lost on Big Pine Key by 2100. Additional threats include restricted range, invasive exotic plants, roadside dumping, loss of pollinators, seed predators, and development.</P>
                    <P>We maintain the previous assessment that hurricanes, storm surges, lack of fire, and limited distribution result in a moderate magnitude of threat because a large part of the range is on conservation lands where threats are being addressed, although fire management is at much slower rate than is required. The immediacy of hurricane threats is difficult to characterize, but imminence is considered high given that hurricanes (and storm surges) of various magnitudes are frequent and recurrent events in the area. Sea-level rise remains uncontrolled but, overall, is nonimminent. Overall, the threats from limited distribution and inadequate fire management are imminent because they are ongoing. In addition, the most consequential threats (hurricanes, storm surges) are frequent, recurrent, and imminent. Therefore, we retained an LPN of 9 for Big Pine partridge pea.</P>
                    <P>
                        <E T="03">Chamaesyce deltoidea</E>
                         ssp. 
                        <E T="03">pinetorum</E>
                         (Pineland sandmat)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The pineland sandmat is only known from Miami-Dade County, Florida. The largest occurrence, estimated at more than 10,000 plants, is located on Long Pine Key within Everglades National Park. All other occurrences are smaller and are in isolated pine rockland fragments in heavily urbanized Miami-Dade County.
                    </P>
                    <P>Occurrences on private (non-conservation) lands and on one County-owned parcel are at risk from development and habitat degradation and fragmentation. Conditions related to climate change, particularly sea-level rise, will be a factor over the long term. All occurrences of the species are threatened by habitat loss and degradation due to fire suppression, the difficulty of applying prescribed fire, and exotic plants. These threats are severe within small and unmanaged fragments in urban areas. However, the threats of fire suppression and exotics are reduced on lands managed by the National Park Service. Hydrologic changes are considered to be another threat. Hydrology has been altered within Long Pine Key due to artificial drainage, which lowered ground water, and by the construction of roads, which either impounded or diverted water. Regional water management intended to restore the Everglades could negatively affect the pinelands of Long Pine Key in the future. At this time, we do not know whether the proposed restoration and associated hydrological modifications will have a positive or negative effect on pineland sandmat. This narrow endemic may be vulnerable to catastrophic events and natural disturbances, such as hurricanes. Overall, the magnitude of threats to this species is moderate; by applying regular prescribed fire, the National Park Service has kept Long Pine Key's pineland vegetation intact and relatively free of exotic plants, and partnerships are in place to help address the continuing threat of exotics on other pine rockland fragments. Overall, the threats are nonimminent because fire management at the largest occurrence is regularly conducted and sea-level rise and hurricanes are more long-term threats. Therefore, we assigned an LPN of 12 to this subspecies. We will continue to monitor any changes in hydrological management that may affect the magnitude of threats to the species.</P>
                    <P>
                        <E T="03">Chamaesyce deltoidea</E>
                         ssp. 
                        <E T="03">serpyllum</E>
                         (Wedge spurge)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. Systematic surveys of publicly owned pine rockland throughout this plant's range were conducted during 2005-2006 and 2007-2008 to determine population size and distribution. Wedge spurge is a small prostrate herb. It was historically, and remains, restricted to pine rocklands on Big Pine Key in Monroe County, Florida. Pine rocklands encompass approximately 580 hectares (1,433 acres) on Big Pine Key, approximately 360 hectares (890 acres) of which are within the Service's National Key Deer Refuge (NKDR). Most of the species' range falls within the NKDR, with the remainder on State, County, and private properties. It is not widely dispersed within the limited range. Occurrences are sparser in the southern portion of Big Pine Key, which contains smaller areas of NKDR lands than does the northern portion. Wedge spurge inhabits sites with low woody cover (e.g., low palm and hardwood densities) and usually with exposed rock or gravel.
                    </P>
                    <P>
                        Pine rockland communities are maintained by relatively frequent fires. In the absence of fire, shrubs and trees encroach on pine rockland, and the subspecies is eventually shaded out. NKDR has a prescribed fire program, although with many constraints on implementation. Habitat loss due to development was historically the greatest threat to the wedge spurge. Much of the remaining habitat is now protected on public lands. Absence of fire now appears to be the greatest of the deterministic threats. Given the recent increase in hurricane activity, storm surges are the greatest of the stochastic threats. The small range and patchy distribution of the subspecies increases risk from stochastic events. Climatic changes, including sea-level rise, are serious long-term threats. Models indicate that even under the best of circumstances, a significant proportion of upland habitat will be lost on Big Pine Key by 2100. Additional threats include restricted range, invasive exotic plants, roadside dumping, loss of pollinators, seed predators, and development.
                        <PRTPAGE P="66416"/>
                    </P>
                    <P>We maintain the previous assessment that low fire-return intervals plus hurricane-related storm surges, in combination with a limited, fragmented distribution and threats from sea-level rise, result in a moderate magnitude of threat, in part, because a large part of the range is on conservation lands, where some threats can be substantially controlled. The immediacy of hurricane threats is difficult to categorize, but in this case threats are imminent given that hurricanes (and storm surges) of various magnitudes are frequent and recurrent events in the area. Sea-level rise remains uncontrolled, but over much of the range is nonimminent compared to other prominent threats. Threats resulting from limited fire occurrences are imminent. As some of the major threats are ongoing, overall, the threats are imminent. Therefore, we retained an LPN of 9 for this subspecies.</P>
                    <P>
                        <E T="03">Chorizanthe parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         (San Fernando Valley spineflower)—The following summary is based on information contained in our files and the petition we received on December 14, 1999. 
                        <E T="03">Chorizanthe parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         is a low-growing herbaceous, annual plant in the buckwheat family. Germination occurs following the onset of late-fall and winter rains and typically represents different cohorts from the seed bank. Flowering occurs in the spring, generally between April and June. 
                        <E T="03">Chorizanthe parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         grows up to 30 centimeters in height and 5 to 40 centimeters across. The plant currently is known from two disjunct localities: the first is in the southeastern portion of Ventura County on a site within the Upper Las Virgenes Canyon Open Space Preserve, formerly known as Ahmanson Ranch, and the second is in an area of southwestern Los Angeles County known as Newhall Ranch. Investigations of historical locations and seemingly suitable habitat within the range of the species have not revealed any other occurrences.
                    </P>
                    <P>
                        The threats currently facing 
                        <E T="03">Chorizanthe parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         include threatened destruction, modification, or curtailment of its habitat or range, inadequacy of existing regulatory mechanisms, and other natural or manmade factors. The threats to 
                        <E T="03">Chorizanthe parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         from habitat destruction or modification are slightly less than they were 7 years ago. One of the two populations (Upper Las Virgenes Canyon Open Space Preserve) is in permanent, public ownership and is being managed by an agency that is working to conserve the plant; however, the use of adjacent habitat for Hollywood film productions was brought to our attention 2 years ago, and the potential impacts to 
                        <E T="03">Chorizanthe parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         have not yet been evaluated. We will be working with the landowners to manage the site for the benefit of 
                        <E T="03">Chorizanthe parryi</E>
                         var. 
                        <E T="03">fernandina.</E>
                         The other population (Newhall Ranch) is under the threat of development; however, a candidate conservation agreement (CCA) is being developed with the landowner, and it is possible that the remaining plants can also be conserved. Until such an agreement is finalized, the threat of development and the potential damage to the Newhall Ranch population still exists, as shown by the destruction of some plants during installation of an agave farm. Furthermore, cattle grazing on Newhall Ranch may be a threat. Cattle grazing may harm 
                        <E T="03">Chorizanthe parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         by trampling and soil compaction. Grazing activity could also alter the nutrient (e.g., elevated organic material levels) content of the soils for 
                        <E T="03">Chorizanthe parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         habitat through fecal inputs, which in turn may favor the growth of other plant species that would otherwise not grow so readily on the mineral-based soils. Over time, changes in species composition may render the sites less favorable for the persistence of 
                        <E T="03">Chorizanthe parryi</E>
                         var. 
                        <E T="03">fernandina. Chorizanthe parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         may be threatened by invasive, nonnative plants, including grasses, which could potentially displace it from available habitat; compete for light, water, and nutrients; and reduce survival and establishment.
                    </P>
                    <P>
                        <E T="03">Chorizanthe parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         is particularly vulnerable to extinction due to its concentration in two isolated areas. The existence of only two areas of occurrence, and a relatively small range, makes the variety highly susceptible to extinction or extirpation from a significant portion of its range due to random events such as fire, drought, and erosion. We retained an LPN of 6 for 
                        <E T="03">Chorizanthe parryi</E>
                         var. 
                        <E T="03">fernandina</E>
                         due to high-magnitude, nonimminent threats.
                    </P>
                    <P>
                        <E T="03">Chromolaena frustrata</E>
                         (Cape Sable thoroughwort)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. This species is found most commonly in open sun to partial shade at the edges of rockland tropical hammock and in coastal rock barrens. There are nine extant occurrences located on five islands in the Florida Keys and one small area in Everglades National Park (ENP). In the Keys, the plant has been extirpated from half of the islands where it occurred. Prior to Hurricane Wilma in 2005, the population was estimated at roughly 5,000 individuals, with all but 500 occurring on one privately owned island. An estimated 1,500 plants occur on the mainland within ENP.
                    </P>
                    <P>This species is threatened by habitat loss and modification, even on public lands, and habitat loss and degradation due to threats from exotic plants at almost all sites. The species is vulnerable to natural disturbances, such as hurricanes, tropical storms, and storm surges. While these factors may also work to maintain coastal rock barren habitat in the long term, Hurricane Wilma affected occurrences and habitat, at least in the short term. Occurrences probably initially declined due to inundation of its coastal barren and rockland hammock habitats; long-term effects on this species are unknown. Cape Sable thoroughwort appears to be vulnerable to cold temperatures. It is not known to what extent cold temperatures in January and December 2010 affected the species at most locations, or what, if any, long-term effect this may have on the population. Sea-level rise is considered a major threat over the long term. Potential effects from other changes in freshwater deliveries and the construction of the Buttonwood Canal are unknown. Problems associated with small population size and isolation are likely major factors, as occurrences may not be large enough to be viable; this narrowly endemic plant has uncertain viability at most locations. Thus, these factors constitute a high magnitude of threat. The threats of small population size, isolation, and uncertain viability are imminent because they are ongoing. As a result, we assigned an LPN of 2 to this species.</P>
                    <P>
                        <E T="03">Consolea corallicola</E>
                         (Florida semaphore cactus)—The following summary is based on information in our files. No new information was provided in the petition we received on May 11, 2004. The Florida semaphore cactus is endemic to the Florida Keys, and was discovered on Big Pine Key in 1919, but that population was extirpated as a result of road building and poaching. This cactus grows close to salt water on bare rock with a minimum of humus soil cover in or along the edges of hammocks near sea level. The species is known to occur naturally only in two areas, Swan Key within Biscayne National Park and Little Torch Key. Outplantings have been attempted in several locations in the upper and lower Keys; however, success has been low. Few plants remain in the population at The Nature Conservancy's Torchwood 
                        <PRTPAGE P="66417"/>
                        Hammock Preserve on Little Torch Key. During monitoring work conducted in 2005, a total of 655 plants were documented at the Swan Key population. In 2008-2010, the population was estimated by Biscayne National Park staff to consist of approximately 600 individuals. Asexual reproduction is the main life-history strategy of this species. Recent genetic studies have shown no variation within populations and very limited variation between populations. Findings support the conclusion that the Swan Key (upper Keys) and Little Torch Key (lower Keys) populations and an individual plant from Big Pine Key (single plant in
                        <E T="03"> ex situ</E>
                         collection; lower Keys) are clonally derived. Studies examining the reproductive biology of the species indicate that all extant wild and cultivated plants are male.
                    </P>
                    <P>
                        The causes for the population decline of this species include destruction or modification of habitat, predation from nonnative 
                        <E T="03">Cactoblastis cactorum</E>
                         moths and disease, poaching and vandalism, hurricanes, and climatic changes, including sea-level rise. Sea-level rise is considered a serious threat to the species and its habitat; all extant populations are located in low-lying areas. All remaining populations are under threat of predation from the exotic moth, and are susceptible to root-rot disease. Competition from invasive exotic plants is a threat at Swan Key; however, efforts by Biscayne National Park are underway to address this threat. This species is inherently vulnerable to stochastic losses, especially at its smaller populations. A lack of variation and limited sexual reproduction makes the remaining small population even more susceptible to natural or manmade factors. Overall, the magnitude of threats is high. The numerous threats are ongoing and, therefore, are imminent. Thus, we assigned this species an LPN of 2.
                    </P>
                    <P>
                        <E T="03">Cordia rupicola</E>
                         (no common name)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Cordia rupicola</E>
                         is a small shrub that has been described from southwestern Puerto Rico, Vieques Island, and Anegada Island (British Virgin Islands). All these sites lay within the subtropical dry forest life zone overlying a limestone substrate. 
                        <E T="03">Cordia rupicola</E>
                         has a restricted distribution. Currently, approximately 227 individuals are known from 4 locations: Peñuelas, Yauco, Guánica Commonwealth Forests, and Vieques National Wildlife Refuge. Additionally, the species is reported as common in Anegada.
                    </P>
                    <P>
                        This species is threatened by maintenance of trails and power line rights-of-way in the Guánica Commonwealth Forest, and residential and commercial development in Peñuelas, Yauco, and Anegada Island. 
                        <E T="03">Cordia rupicola</E>
                         is also vulnerable to natural (
                        <E T="03">e.g.,</E>
                         hurricanes) or manmade (
                        <E T="03">e.g.,</E>
                         human-induced fires) threats. Furthermore, the population on Anegada Island, which is considered the healthiest population, is expected to be affected sea-level rise as most of the suitable habitat for the species is below 3 meters above sea level. For these reasons, we believe that the magnitude of the current threats should be considered high. About 60 percent of known adult plants are located in protected lands managed for conservation by the Puerto Rico Department of Natural and Environmental Resources or the Service. For these reasons, threats to 
                        <E T="03">Cordia rupicola</E>
                         on the whole are high magnitude and nonimminent, and therefore we have assigned a listing priority number of 5. However, the threats faced by the species are expected to increase in the future, and therefore may become imminent, if conservation measures are not implemented and long-term impacts are not averted.
                    </P>
                    <P>
                        <E T="03">Cyanea asplenifolia</E>
                         (Haha)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Cyanea kunthiana</E>
                         (Haha)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Cyanea obtusa</E>
                         (Haha)—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Cyanea tritomantha</E>
                         (‘Aku)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Cyrtandra filipes</E>
                         (Haiwale)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Cyrtandra oxybapha</E>
                         (Haiwale)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Dalea carthagenensis</E>
                         ssp. 
                        <E T="03">floridana</E>
                        (Florida prairie-clover)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Dalea carthagenensis</E>
                         var. 
                        <E T="03">floridana</E>
                         occurs in Big Cypress National Preserve (BCNP) in Monroe and Collier Counties and at six locations within Miami-Dade County, Florida, albeit mostly in limited numbers. There are a total of nine extant occurrences, seven of which are on conservation lands. In addition, plants were reintroduced to a park in Miami-Dade County in 2006, but only four remained after 8 months.
                    </P>
                    <P>
                        Existing occurrences are extremely small and may not be viable, especially some of the occurrences in Miami-Dade County. Remaining habitats are fragmented. Climatic changes, including sea-level rise, are long-term threats that are expected to reduce the extent of habitat. This plant is threatened by habitat loss and degradation due to fire suppression, the difficulty of applying prescribed fire to pine rocklands, and competition from exotic plants. Damage to plants by off-road vehicles is a serious threat within the BCNP; damage attributed to illegal mountain biking at the R. Hardy Matheson Preserve has been reduced. One location within BCNP is threatened by changes in mowing practices; this threat is low in magnitude. This species is being parasitized by the introduced insect lobate lac scale (
                        <E T="03">Paratachardina pseudolobata</E>
                        ) at some localities (
                        <E T="03">e.g.,</E>
                         R. Hardy Matheson Preserve), but we do not know the extent of this threat. This plant is vulnerable to natural disturbances, such as hurricanes, tropical storms, and storm surges. Due to its restricted range and the small sizes of most isolated occurrences, this species is vulnerable to environmental (catastrophic hurricanes), demographic (potential episodes of poor reproduction), and genetic (potential inbreeding depression) threats. The magnitude of threats is high because of the limited number of occurrences and the small number of individual plants at each occurrence. The threats are imminent; even though many sites are 
                        <PRTPAGE P="66418"/>
                        on conservation lands, these plants still face significant ongoing threats. Therefore, we have assigned an LPN of 3 to Florida prairie-clover.
                    </P>
                    <P>
                        <E T="03">Dichanthelium hirstii</E>
                         (Hirst Brothers' panic grass)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Dichanthelium hirstii</E>
                         is a perennial grass that produces erect, leafy, flowering stems from May to October. 
                        <E T="03">Dichanthelium hirstii</E>
                         occurs in coastal plain intermittent ponds, usually in wet savanna or pine barren habitats, and is found at only two sites in New Jersey, one site in Delaware, and one site in North Carolina. While all four extant 
                        <E T="03">D. hirstii</E>
                         populations are located on public land or privately owned conservation lands, natural threats to the species from encroaching vegetation and fluctuations in climatic conditions remain of concern, and may be exacerbated by anthropogenic factors occurring adjacent to the species' wetland habitat. Given the low number of plants found at each site, even minor changes in the species' habitat could result in local extirpation. Loss of any known sites could result in a serious contraction of the species' range. However, the most immediate and severe threats to this species (
                        <E T="03">i.e.,</E>
                         ditching of the Labounsky Pond site and encroachment of aggressive vegetative competitors) have been curtailed or are being actively managed by The Nature Conservancy at one New Jersey site and by the Delaware Division of Fish and Wildlife and Delaware Natural Heritage Program at the Assawoman Pond, Delaware site. Based on nonimminent threats of a high magnitude, we retain an LPN of 5 for this species.
                    </P>
                    <P>
                        <E T="03">Digitaria pauciflora</E>
                         (Florida pineland crabgrass)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. Pine rocklands in Miami-Dade County have largely been destroyed by residential, commercial, and urban development and by agriculture. With most remaining habitat having been negatively altered, this species has been extirpated from much of its historical range, including extirpation from all areas outside of National Parks. Two large occurrences remain within Everglades National Park and Big Cypress National Preserve; plants on Federal lands are protected from the threat of habitat loss due to development. However, any unknown plants, indefinite occurrences, and suitable habitat remaining on private or non-conservation land are threatened by development. Continued development of suitable habitat diminishes the potential for reintroduction into its historical range. Extant occurrences are in low-lying areas and will be affected by climate change and rising sea level.
                    </P>
                    <P>Fire suppression, the difficulty of applying prescribed fire to pine rocklands, and threats from exotic plants are ongoing threats. As the only known remaining occurrences are on lands managed by the National Park Service, the threats of fire suppression and exotics are somewhat reduced. The presence of the exotic Old World climbing fern is of particular concern due to its ability to spread rapidly. In Big Cypress National Preserve, plants are threatened by off-road vehicle use. Changes to hydrology are a potential threat. Hydrology has been altered within Long Pine Key due to artificial drainage, which lowered ground water, and construction of roads, which either impounded or diverted water. Regional water management intended to restore the Everglades has the potential to affect the pinelands of Long Pine Key, where a large population occurs. At this time, it is not known whether Everglades restoration will have a positive or negative effect. This narrow endemic may be vulnerable to catastrophic events and natural disturbances, such as hurricanes. Overall, the magnitude of threats is high. Only two known occurrences remain and the likelihood of establishing a sizable population on other lands is diminished due to continuing habitat loss. Impacts from climate change and sea-level rise are currently low, but expected to be severe in the future. The majority of threats are nonimminent, as they are long-term in nature (water management, hurricanes, and sea-level rise). Therefore, we assigned an LPN of 5 for this species.</P>
                    <P>
                        <E T="03">Echinomastus erectocentrus</E>
                         var. 
                        <E T="03">acunensis</E>
                         (Acuna cactus)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        <E T="03">Erigeron lemmonii</E>
                         (Lemmon fleabane)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        <E T="03">Eriogonum codium</E>
                         (Umtanum Desert buckwheat)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        <E T="03">Eriogonum corymbosum</E>
                         var. 
                        <E T="03">nilesii</E>
                         (Las Vegas buckwheat)—The following summary is based on information contained in our files and the petition we received on April 23, 2008. 
                        <E T="03">Eriogonum corymbosum</E>
                         var. 
                        <E T="03">nilesii</E>
                         is a woody perennial shrub up to 4 feet high with a mounding shape. The flowers of this plant are numerous, small, and yellow with small, bract-like leaves at the base of each flower. 
                        <E T="03">Eriogonum corymbosum</E>
                         var. 
                        <E T="03">nilesii</E>
                         is very conspicuous when flowering in late September and early October. It is restricted to sparsely vegetated, gypsum soil outcroppings and is found historically only in Clark County, Nevada. In 2004, morphometrics were used to classify this plant as the unique variety 
                        <E T="03">nilesii,</E>
                         and its unique taxonomy was verified using molecular genetic analyses in 2007. Recent surveys have expanded 
                        <E T="03">E. corymbosum</E>
                         var. 
                        <E T="03">nilesii'</E>
                        s range to Lincoln County, Nevada, and Washington County, Utah.
                    </P>
                    <P>
                        <E T="03">Eriogonum corymbosum</E>
                         var. 
                        <E T="03">nilesii</E>
                         was added to the candidate list in December 2007 due to continued loss of habitat from development of over 95 percent of its core historical range and potential habitat. In addition, off-highway vehicle activity and other public land uses (casual public use, mining, and illegal dumping) directly threaten over 95 percent of the remaining habitat. It was petitioned for listing in April 2008 and a warranted-but-precluded determination was made in December 2008 (73 FR 75176; December 10, 2008). To date, regulatory mechanisms to protect 
                        <E T="03">E. corymbosum</E>
                         var. 
                        <E T="03">nilesii</E>
                         are inadequate. Its designation as a Bureau of Land Management (BLM) special status species has not provided adequate protection on lands managed by BLM. 
                        <E T="03">Eriogonum corymbosum</E>
                         var. 
                        <E T="03">nilesii</E>
                         is not protected by the State of Nevada or Utah or by any other regulatory mechanisms on other Federal lands. We have determined that candidate status is warranted for this variety as a result of threats to the remaining habitat and inadequate regulatory mechanisms.
                    </P>
                    <P>
                        Conservation measures are being developed that could reduce the risks to occupied habitat, but these measures are not sufficiently complete as to remove these threats. The magnitude of threats is high because the more significant threats (urban development and surface mining) would result in direct mortality of the plants in over half of the known habitat. While both development and mining are very likely to occur in the 
                        <PRTPAGE P="66419"/>
                        future, they are not expected to happen in the immediate future due to economic decline, and thus, the threats are nonimminent. Accordingly, we assigned 
                        <E T="03">E. corymbosum</E>
                         var. 
                        <E T="03">nilesii</E>
                         an LPN of 6.
                    </P>
                    <P>
                        <E T="03">Eriogonum kelloggii</E>
                         (Red Mountain buckwheat)—The following summary is based on information contained in our files and information provided by the California Department of Fish and Game. No new information was provided in the petition we received on May 11, 2004. Red Mountain buckwheat is a perennial herb endemic to serpentine habitat of lower montane forests found between 1,900 and 4,100 feet. Its distribution is limited to the Red Mountain and Little Red Mountain areas of Mendocino County, California, where it occupies in excess of 81 acres, and 900 square feet, respectively. The known species distribution by ownership is described as follows: Federal (Bureau of Land Management), 83 percent; private, 17 percent; State of California, less than 1 percent. Occupied habitat at Red Mountain is scattered over 4 square miles. Total population size has not been determined, but a preliminary estimate suggests the population may be in excess of 63,000 plants, occupying more than 44 discrete habitat polygons. Intensive monitoring of permanent plots on three study sites in Red Mountain suggests considerable annual variation in plant density and reproduction, but no discernable population trend was evident in two of three study sites. One study site showed a 65 percent decline in plant density over 11 years.
                    </P>
                    <P>
                        The primary threat to this species is the potential for surface mining for chromium and nickel. Virtually the entire distribution of Red Mountain buckwheat is either owned by mining interests, or is covered by existing mining claims, none of which are currently active. Surface mining would destroy habitat suitability for this species. The species is also believed threatened by tree and shrub encroachment into its habitat, in absence of fire. Some 42 percent of its known distribution occurred within the boundary of the Red Mountain Fire of June 2008. However, the extent and manner in which 
                        <E T="03">Eriogonum kelloggii</E>
                         and its habitat were affected by that fire is not yet known. The single population located at Little Red Mountain appears to have been affected, and perhaps eliminated by fire-control efforts. Given the magnitude (high) and immediacy (nonimminent) of the threat to the small, scattered populations, and given its taxonomy (species), we assigned an LPN of 5 to this species.
                    </P>
                    <P>
                        <E T="03">Festuca hawaiiensis</E>
                         (no common name)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. This species is a cespitose (growing in dense, low tufts) annual found in dry forest on the island of Hawaii, Hawaii. 
                        <E T="03">Festuca hawaiiensis</E>
                         is known from 4 populations totaling approximately 1,000 individuals in and around the Pohakuloa Training Area. Historically, this species was also found on Hualalai and Puu Huluhulu, but it no longer occurs at these sites. 
                        <E T="03">Festuca hawaiiensis</E>
                         possibly occurred on Maui.
                    </P>
                    <P>
                        This species is threatened by pigs, goats, mouflon, and sheep that degrade and destroy habitat; fire; military training activities; and nonnative plants that outcompete and displace it. Feral pigs, goats, mouflon, and sheep have been fenced out of a portion of the populations of 
                        <E T="03">F. hawaiiensis,</E>
                         and nonnative plants have been reduced in the fenced area, but the majority of the populations are still affected by threats from ungulates. The threats are imminent because they are not controlled and are ongoing in the remaining, unfenced populations. Firebreaks have been established at two populations, but fire is an imminent threat to the remaining populations that have no firebreaks. The threats are of a high magnitude because they could adversely affect the majority of 
                        <E T="03">F. hawaiiensis</E>
                         populations resulting in direct mortality or reduced reproductive capacity. Therefore, we retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Festuca ligulata</E>
                         (Guadalupe fescue)—The following summary is based on information obtained from the original species petition, received in 1975, and from our files, on-line herbarium databases, and scientific publications. Six small populations of Guadalupe fescue, a member of the Poaceae (grass family), have been documented in mountains of the Chihuahuan desert in Texas and in Coahuila, Mexico. Only two extant populations have been confirmed in the last 5 years, in the Chisos Mountains, Big Bend National Park, Texas, and in the privately owned Area de Protección de Flora y Fauna (Protected Area for Flora and Fauna—APFF) Maderas del Carmen in northern Coahuila. Despite intensive searches, a population known from Guadalupe Mountains National Park, Texas, has not been found since 1952 and is presumed extirpated. In 2009, Mexican botanists confirmed Guadalupe fescue at one site in APFF Maderas del Carmen, but could not find the species at the original site, known as Sierra El Jardín, which was first reported in 1973. Two additional Mexican populations, near Fraile in southern Coahuila, and the Sierra de la Madera in central Coahuila, have not been monitored since 1941 and 1977, respectively. A great amount of potentially suitable habitat in Coahuila has never been surveyed.
                    </P>
                    <P>The potential threats to Guadalupe fescue include changes in the wildfire cycle and vegetation structure, trampling from humans and pack animals, grazing, trail runoff, fungal infection of seeds, small sizes and isolation of populations, and limited genetic diversity. The Service and the National Park Service established a candidate conservation agreement (CCA) in 2008 to provide additional protection for the Chisos Mountains population, and to promote cooperative conservation efforts with U.S. and Mexican partners. The threats to Guadalupe fescue are of moderate magnitude, and are nonimminent, due to the provisions of the CCA and other conservation efforts, as well as the likelihood that other populations exist in mountains of Coahuila that have not been surveyed. Thus, we maintained the LPN of 11 for this species.</P>
                    <P>
                        <E T="03">Gardenia remyi</E>
                         (Nanu)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Gardenia remyi</E>
                         is a tree found in mesic to wet forest on the islands of Kauai, Molokai, Maui, and Hawaii, Hawaii. 
                        <E T="03">Gardenia remyi</E>
                         is known from 19 populations totaling between 85 and 87 individuals.
                    </P>
                    <P>
                        This species is threatened by pigs, goats, and deer that degrade and destroy habitat and possibly prey upon the species, and by nonnative plants that outcompete and displace it. 
                        <E T="03">Gardenia remyi</E>
                         is also threatened by landslides and reduced reproductive vigor on the island of Hawaii. This species is represented in ex situ collections. On Kauai, 
                        <E T="03">G. remyi</E>
                         individuals have been outplanted within ungulate-proof exclosures in two locations. Feral pigs have been fenced out of the west Maui populations of 
                        <E T="03">G. remyi,</E>
                         and nonnative plants have been reduced in those areas. However, these threats are not controlled and are ongoing in the remaining, unfenced populations, and are, therefore, imminent. In addition, the threat from goats and deer is ongoing and imminent throughout the range of the species, because no goat or deer control measures have been undertaken for any of the populations of 
                        <E T="03">G. remyi.</E>
                         All of the threats are of a high magnitude because habitat destruction, predation, and landslides could significantly affect the entire species, 
                        <PRTPAGE P="66420"/>
                        resulting in direct mortality or reduced reproductive capacity, leading to a relatively high likelihood of extinction. Therefore, we retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Geranium hanaense</E>
                         (Nohoanu)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Geranium hillebrandii</E>
                         (Nohoanu)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Gonocalyx concolor</E>
                         (no common name)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Gonocalyx concolor</E>
                         is a small, evergreen, epiphytic or terrestrial shrub. This species is currently known from two populations: one at Cerro La Santa and the other at Charco Azul, both in the Carite Commonwealth Forest. This forest is located in the Sierra de Cayey and extends through the municipalities of Guayama, Cayey, Caguas, San Lorenzo, and Patillas in southeastern Puerto Rico. The population previously reported in the Caribbean National Forest apparently no longer exists. In 1996, approximately 172 plants were reported at Cerro La Santa. However, in 2006, only 25 individuals were reported at this site, and four were located in Charco Azul. At Cerro La Santa, the species is found growing on trees located close to communication towers, roads, plantations, and trails.
                    </P>
                    <P>
                        The 
                        <E T="03">Gonocalyx concolor</E>
                         population found at Cerro La Santa is threatened by habitat destruction and modification caused by vegetation clearing around telecommunication towers. Although the species is located within a Commonwealth forest, which is protected by Law No. 133 (“Ley de Bosques de Puerto Rico” or The Puerto Rico Forest Law), unauthorized maintenance of existing communication facilities continue to result in loss of individuals. 
                        <E T="03">Gonocalyx concolor</E>
                         is not currently listed in the Commonwealth Regulation No. 6766 (“Reglamento para Regir las Especies Vulnerables y en Peligro de Extinción en el Estado Libre Asociado de Puerto Rico”), which provides protection for endangered and threatened species. However, the Natural Heritage Program of the Puerto Rico Department of Natural and Environmental Resources recognizes 
                        <E T="03">Gonocalyx concolor</E>
                         as a critical element. In addition, the Carite Commonwealth Forest is designated as a Critical Wildlife Area by the Commonwealth of Puerto Rico. Despite these conservation efforts, damages to the species still occur due to its restricted distribution and location near telecommunication facilities, which renders the species vulnerable to both natural (e.g., hurricanes, landslides) and manmade impacts. Thus, we consider that existing laws and regulations have not been effectively enforced to protect these populations. Moreover, we believe that inadequacy of regulatory mechanisms is a current threat to the species. Overall, we consider current threats to 
                        <E T="03">Gonocalyx concolor</E>
                         to be high in magnitude but nonimminent, as there are no known projects within the Commonwealth protected area. Habitat modification of this species has been only observed in one site at Cerro La Santa area. Therefore, we have assigned an LPN of 5 to 
                        <E T="03">Gonocalyx concolor.</E>
                    </P>
                    <P>
                        <E T="03">Hazardia orcuttii</E>
                         (Orcutt's hazardia)—The following summary is based on information contained in our files and the petition we received on March 8, 2001. 
                        <E T="03">Hazardia orcuttii</E>
                         is an evergreen shrubby species in the Asteraceae (sunflower) family. The erect shrubs are 50 to 100 centimeters (20 to 40 inches) high. The only known extant native occurrence of this species in the United States occupies 2 ha (5 ac) in the Manchester Conservation Area in northwestern San Diego County, California. This site is managed by Center for Natural Lands Management (CNLM). Using material derived from the native population, the CNLM facilitated the establishment of test populations at four additional sites in northwest San Diego County, California, including a second site in the Manchester Conservation Area, Kelly Ranch Habitat Conservation Area, Rancho La Costa Habitat Conservation Area, and San Elijo Lagoon. 
                        <E T="03">Hazardia orcuttii</E>
                         also occurs at a few coastal sites in Mexico, where it recently became listed as endangered under Mexican environmental law. The total number of plants at the only native site in the United States is approximately 669 adults, and it is unknown if reproduction is occurring. The five additional test populations collectively support approximately 483 adults, 17 juveniles, and 322 seedlings, and reproduction is occurring in three test populations. The population in Mexico is estimated to be 1,100 plants. The occurrences in Mexico are threatened by coastal development from Tijuana to Ensenada.
                    </P>
                    <P>
                        The native population in the United States is within an area that receives public use; however, management at this site has minimized impacts associated with habitat degradation. This species has a very low reproductive output, although the causes are as yet unknown. Competition from invasive, nonnative plants may pose a threat to the reproductive potential of this species. In one study, 95 percent of the flowers examined were damaged by insects or fungal agents or aborted prematurely, and insects or fungal agents damaged 50 percent of the seeds produced. All of the populations in the United States are small and one test population is declining. Small populations are considered subject to random events and reductions in fitness due to low genetic variability. Threats associated with small population size are further exacerbated by the limited range and low reproductive output of this species. However, if low seed production is because of ecosystem disruptions, such as loss of effective pollinators, there could be additional threats that need to be addressed. Due to low abundance and a very small area of occupancy, any regional fire would be a rangewide threat. Furthermore, because the soil seed bank is poor and seed viability is low, recovery from a fire may be especially challenging. The response mechanism of this species to fire is unknown. Overall, the threats to 
                        <E T="03">H. orcuttii</E>
                         are of a high magnitude because they have the potential to significantly reduce the reproductive potential of this species. The threats are nonimminent overall because the most significant threats (invasive, nonnative plants and low reproductive output) are long-term in nature. This species faces high-magnitude nonimminent threats; therefore, we assigned this species an LPN of 5.
                    </P>
                    <P>
                        <E T="03">Hedyotis fluviatilis</E>
                         (Kamapuaa)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Hedyotis fluviatilis</E>
                         is a scandent shrub found in mixed shrubland to wet lowland forest on the islands of Oahu and Kauai, Hawaii. This species is known from 11 populations totaling between 400 and 900 individuals. 
                        <E T="03">Hedyotis fluviatilis</E>
                         is threatened by pigs and goats that degrade and destroy habitat, and by nonnative plants that outcompete and displace it. Landslides and hurricanes are a potential threat to populations on Kauai. Predation by pigs and goats is a likely threat. This species is represented in an ex situ collection; 
                        <PRTPAGE P="66421"/>
                        however, there are no other conservation actions implemented for this species. We retained an LPN of 2 because the severity of the threats to the species is high and the threats are ongoing and, therefore, imminent.
                    </P>
                    <P>
                        <E T="03">Helianthus verticillatus</E>
                         (Whorled sunflower)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. The whorled sunflower is found in moist, prairie-like openings in woodlands and along adjacent creeks. Despite extensive surveys throughout its range, only five populations are known for this species; two populations in Cherokee County, Alabama; one population in Floyd County, Georgia; and one population each in Madison and McNairy Counties, Tennessee. This species appears to have restricted ecological requirements and is dependent upon the maintenance of prairie-like openings for its survival. Active management of habitat is needed to keep competition and shading under control. Much of its habitat has been degraded or destroyed for agricultural, silvicultural, and residential purposes. Populations near roadsides or powerlines are threatened by herbicide usage in association with right-of-way maintenance. The majority of the Georgia population is protected due to its location within a conservation easement; however, only 15 to 20 plants are estimated to occur at this site. The remaining four sites are not formally protected, but efforts have been taken to abate threats associated with highway right-of-way maintenance at one Alabama population. In addition, despite past concerns about threats from timber removal degrading 
                        <E T="03">H. verticillatus</E>
                         habitat, the other Alabama population has responded favorably to canopy removal that took place circa 2001. Therefore, threats are of moderate magnitude, although imminent because they are ongoing. Thus, we assigned this species an LPN of 8.
                    </P>
                    <P>
                        <E T="03">Hibiscus dasycalyx</E>
                         (Neches River rose-mallow)—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        <E T="03">Ivesia webberi</E>
                         (Webber ivesia)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Ivesia webberi</E>
                         is a low, spreading, perennial herb with grayish-green foliage; dark red, wiry stems; and yellow flowers arranged in capitate cymes. 
                        <E T="03">Ivesia webberi</E>
                         occurs very infrequently in Lassen, Plumas, and Sierra Counties in California, and in Douglas and Washoe Counties, Nevada. The species is restricted to sites with sparse vegetation and shallow, rocky soils composed of volcanic ash or derived from andesitic rock. Occupied sites generally occur on mid-elevation flats, benches, or terraces on mountain slopes above large valleys along the transition zone between the eastern edge of the northern Sierra Nevada and the northwestern edge of the Great Basin. Currently, the global population is estimated at approximately 5 million individuals at 16 known sites. The Nevada sites support nearly 98 percent of the total number of individuals (4.9 million) on about 25 acres (10 hectares) of occupied habitat. The California sites are larger in area, totaling about 157 acres (63 hectares), but support fewer individuals (approximately 120,000).
                    </P>
                    <P>
                        The primary threats to 
                        <E T="03">I. webberi</E>
                         include urban and commercial development, authorized and unauthorized roads, off-highway vehicle (OHV) activities, livestock grazing and trampling, wildfire and fire suppression activities, and displacement by invasive species. Despite the high numbers of individuals, direct and indirect impacts to the species and its habitat, specifically from urban development and OHV activity, remain high and are likely to increase. In addition, these threats have a significant likelihood of bringing about extinction on a relative short time scale, and we therefore conclude that the threats are of high magnitude. However, the U.S. Forest Service has developed a conservation strategy that commits to management, monitoring, and research to protect this species on National Forest lands where most populations are found, and the State of Nevada has listed the species as critically endangered, which provides a mechanism to track future impacts on private lands. In addition, both the U.S. Forest Service and State of Nevada have agreed to coordinate closely with the Fish and Wildlife Service on all activities that may affect this species. For these reasons, we have determined that the threats to 
                        <E T="03">I. webberi</E>
                         are nonimminent and we are maintaining an LPN of 5.
                    </P>
                    <P>
                        <E T="03">Joinvillea ascendens</E>
                         ssp. 
                        <E T="03">ascendens</E>
                         (Ohe)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Joinvillea ascendens</E>
                         ssp. 
                        <E T="03">ascendens</E>
                         is an erect herb found in wet to mesic 
                        <E T="03">Metrosideros polymorpha-Acacia koa</E>
                         (ohia-koa) lowland and montane forest on the islands of Kauai, Oahu, Molokai, Maui, and Hawaii, Hawaii. This subspecies is known from 44 widely scattered populations totaling approximately 200 individuals. Plants are typically found as only one or two individuals, with miles between populations.
                    </P>
                    <P>This subspecies is threatened by destruction or modification of habitat by pigs, goats, and deer, and by nonnative plants that outcompete and displace native plants. Predation by pigs, goats, deer, and rats is a likely threat to this species. Landslides are a potential threat to populations on Kauai and Molokai. Seedlings have rarely been observed in the wild. Seeds germinate in cultivation, but most die soon thereafter. It is uncertain if this rarity of reproduction is typical of this subspecies, or if it is related to habitat disturbance. Feral pigs have been fenced out of a few of the populations of this subspecies, and nonnative plants have been reduced in those populations that are fenced. However, these threats are not controlled and are ongoing in the remaining, unfenced populations. This species is represented in ex situ collections. The threats are of high magnitude because habitat degradation, nonnative plants, and predation result in mortality or severely affect the reproductive capacity of the majority of populations of this species, leading to a relatively high probability of extinction. The threats are ongoing, and thus are imminent. Therefore, we retained an LPN of 3 for this subspecies.</P>
                    <P>
                        <E T="03">Leavenworthia crassa</E>
                         (Gladecress)—The following information is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. This species of gladecress is a component of glade flora, occurring in association with limestone outcroppings. 
                        <E T="03">Leavenworthia crassa</E>
                         is endemic to a 13-mile radius area in north central Alabama in Lawrence and Morgan Counties, where only six populations of this species are documented. Glade habitats today have been reduced to remnants fragmented by agriculture and development. Populations of this species are now located in glade-like areas exhibiting various degrees of disturbance including pastureland, roadside rights-of-way, and cultivated or plowed fields. The most vigorous populations of this species are located in areas which receive full, or near full, sunlight with limited herbaceous competition. The magnitude of threat is high for this species, because with the limited number of populations, the threats could result in direct mortality or reduced reproductive 
                        <PRTPAGE P="66422"/>
                        capacity of the species. This species appears to be able to adjust to periodic disturbances and the potential impacts to populations from competition, exotics, and herbicide use are nonimminent. Thus, we assigned an LPN of 5 to this species.
                    </P>
                    <P>
                        <E T="03">Leavenworthia texana</E>
                         (Texas golden gladecress)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        <E T="03">Linum arenicola</E>
                         (Sand flax)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. Sand flax is found in pine rockland and marl prairie habitats which require periodic wildfires in order to maintain an open, shrub free subcanopy and reduce leaf litter levels. Based upon available data, there are 11 extant occurrences of sand flax; 11 others have been extirpated or destroyed. For the most part, only small and isolated occurrences remain in low-lying areas in a restricted range of southern Florida and the Florida Keys.
                    </P>
                    <P>Habitat loss and degradation due to development is a major threat and most of the remaining occurrences are on private land or non-conservation public land. However, a survey conducted in 2009 showed approximately 74,000 plants on a non-conservation, public site in Miami-Dade County; this is far more plants than was previously known. Although a portion of the plants will be affected by development, approximately 60,000 are anticipated to be protected and managed through a conservation easement. Consequently, the majority of the largest occurrence in Miami-Dade County is expected to be conserved and managed. In addition, much of the pine rockland on Big Pine Key, the location of the largest occurrence in the Keys, is protected from development. Climatic changes and sea-level rise are long-term threats that are expected to affect the species and ultimately substantially reduce the extent of available habitat. Nearly all remaining populations are threatened by fire suppression, difficulty in applying prescribed fire, road maintenance activities, exotic species, or illegal dumping. However, some efforts are underway to use prescribed fire to control exotics on conservation lands where this species occurs. In general, viability is uncertain for 9 of 11 occurrences. Sand flax is vulnerable to natural disturbances, such as hurricanes, tropical storms, and storm surges. Hurricane Wilma inundated most of its habitat on Big Pine Key in 2005, and plants were not found 8 to 9 weeks post-storm; the density of sand flax declined to zero in all management units at The Nature Conservancy's preserve in 2006. In a 2007 post-hurricane assessment, sand flax was found in northern plots, but not in any of the southern plots on Big Pine Key. More current data are not available. Due to the small and fragmented nature of the current population, stochastic events, disease, or genetic bottlenecks may strongly affect this species in the Florida Keys. Reduced pollinator activity and suppression of pollinator populations from pesticides used in mosquito control and decreased seed production due to increased seed predation in a fragmented wildland urban interface may also affect sand flax; however, not enough information is known on this species' reproductive biology or life history to assess these potential threats.</P>
                    <P>Overall, the magnitude of threats is high. Because development is not immediate for the majority of the largest population in Miami-Dade County, the threat of habitat loss at this location is nonimminent. In addition, the finding of a larger population than previously known, combined with its location on the mainland, tempers the immediacy of threats of hurricanes and other natural disturbances and catastrophic events. The new sizable, presumably viable population on the mainland provides some assurance that the species could withstand such threats due to the number of individuals and presence at a different geographic location (i.e., mainland versus Keys). Therefore, based on threats that are overall nonimminent but high in magnitude, we assigned this species an LPN of 5.</P>
                    <P>
                        <E T="03">Linum carteri</E>
                         var
                        <E T="03">. carteri</E>
                         (Carter's small-flowered flax)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. This plant occupies open and disturbed sites in pinelands of Miami-Dade County, Florida. Currently, there are nine known occurrences. Occurrences with fewer than 100 individuals are located on three county-owned preserves. A site with more than 100 plants is owned by the U.S. Department of Agriculture, but the site is not managed for conservation.
                    </P>
                    <P>Climatic changes, including sea-level rise, are long-term threats that will likely reduce the extent of habitat. The nine existing occurrences are small and vulnerable to habitat loss, which is exacerbated by habitat degradation due to fire suppression, the difficulty of applying prescribed fire to pine rocklands, and threats from exotic plants. Remaining habitats are fragmented. Non-compatible management practices are also a threat at most protected sites; several sites are mowed during the flowering and fruiting season. In the absence of fire, periodic mowing can, in some cases, help maintain open, shrub-free understory and provide benefits to this plant. However, mowing can also eliminate reproduction entirely in very young plants, delay reproductive maturation, and kill adult plants. With flexibility in timing and proper management, threats from mowing practices can be reduced or negated. Carter's small-flowered flax is vulnerable to natural disturbances, such as hurricanes, tropical storms, and storm surges. This species exists in such small numbers at so few sites, that it may be difficult to develop and maintain viable occurrences on the available conservation lands. Although no population viability analysis has been conducted for this plant, indications are that existing occurrences are at best marginal, and it is possible that none are truly viable. As a result, the magnitude of threats is high. The threats are ongoing, and thus are imminent. Therefore, we assigned an LPN of 3 to this plant variety.</P>
                    <P>
                        <E T="03">Myrsine fosbergii</E>
                         (Kolea)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Myrsine fosbergii</E>
                         is a branched shrub or small tree found in lowland mesic and wet forest, on watercourses or stream banks, on the islands of Kauai and Oahu, Hawaii. This species is currently known from 14 populations totaling a little more than 100 individuals. 
                        <E T="03">Myrsine fosbergii</E>
                         is threatened by feral pigs and goats that degrade and destroy habitat and may prey upon the plant, and by nonnative plants that compete for light and nutrients. This species is represented in an ex situ collection. Although there are plans to fence and remove ungulates from the Helemano area of Oahu, which may benefit this species, no conservation measures have been taken to date to alleviate these threats for this species. Feral pigs and goats are found throughout the known range of 
                        <E T="03">M. fosbergii,</E>
                         as are nonnative plants. The threats from feral pigs, goats, and nonnative plants are of a high magnitude because they pose a severe threat throughout the limited range of this species, and they are ongoing and 
                        <PRTPAGE P="66423"/>
                        therefore imminent. We retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Myrsine vaccinioides</E>
                         (Kolea)—We continue to find that listing this species is warranted but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Narthecium americanum</E>
                         (Bog asphodel)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. Bog asphodel is a perennial herb that is found in savanna areas, usually with water moving through the substrate, as well as in sandy bogs along streams and rivers. The historical range of bog asphodel included New Jersey, Delaware, North Carolina, and South Carolina, although the taxonomic identity of the historic North Carolina specimens is now in question. Previous reports of bog asphodel from New York are now believed erroneous. Extant populations of bog asphodel are now found only within the Pine Barrens region of New Jersey.
                    </P>
                    <P>Bog asphodel has experienced a clear and apparently ongoing curtailment of its geographic range, which leaves it vulnerable to localized and population-level threats. The Pine Barrens savannas that support bog asphodel provide a scarce, specialized habitat that has declined from several thousand acres around 1900 to only a thousand acres in recent decades. This species has been lost from at least 2 States, and now occurs on less than 80 acres of land confined to an area only about 30 miles in diameter. Eight of 26 delineated bog asphodel Element Occurrences in New Jersey are extirpated. The extirpated occurrences are distributed around the periphery of the range, representing a contraction. Many of the remaining occurrences around the periphery of the range are very small and subject to identified threats, making the species vulnerable to further range contractions.</P>
                    <P>Significant threats include unauthorized use of off-road vehicles, deer, beaver, natural succession, and the risk of lowered water tables. Lesser threats include localized indirect effects of upland development, impacts from non-motorized recreational activities, collection, and herbivores other than deer. Because the range of bog asphodel is currently limited to New Jersey's Pinelands Area and Coastal Zone, regulatory protections are generally adequate. More than 95 percent of bog asphodel occurs on protected lands, although enforcement of illegal activity can be lacking, and little active habitat management is taking place. Outright habitat destruction from wetland filling, draining, flooding, and conversion to commercial cranberry bogs likely contributed to the curtailment of this species' range, but these are generally historic not current threats to bog asphodel.</P>
                    <P>Current threats to bog asphodel are low to moderate in magnitude because regulatory protections appear to be adequate so that the threats are not expected to bring about extinction on a relatively short time scale. Several threats are imminent because they are ongoing and expected to continue. Overall, based on these imminent, moderate threats, we retain an LPN of 8 for this species.</P>
                    <P>
                        <E T="03">Nothocestrum latifolium</E>
                         (‘Aiea)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Nothocestrum latifolium</E>
                         is a small tree found in dry to mesic forest on the islands of Kauai, Oahu, Maui, Molokai, and Lanai, Hawaii. 
                        <E T="03">Nothocestrum latifolium</E>
                         is known from 17 steadily declining populations totaling fewer than 1,200 individuals.
                    </P>
                    <P>
                        This species is threatened by feral pigs, goats, and axis deer that degrade and destroy habitat and may prey upon it; by nonnative plants that compete for light and nutrients; and by the loss of pollinators that negatively affect the reproductive viability of the species. This species is represented in an ex situ collection. Ungulates have been fenced out of four areas where 
                        <E T="03">N. latifolium</E>
                         currently occurs, hundreds of 
                        <E T="03">N. latifolium</E>
                         individuals have been outplanted in fenced areas, and nonnative plants have been reduced in some populations that are fenced. However, these ongoing conservation efforts for this species benefit only a few of the known populations. The threats are not controlled and are ongoing in the remaining unfenced populations. In addition, little regeneration is observed in this species. The threats are of a high magnitude, because they are severe enough to affect the continued existence of the species, leading to a relatively high likelihood of extinction. The threats are imminent, as they are ongoing. Therefore, we retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Ochrosia haleakalae</E>
                         (Holei)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Ochrosia haleakalae</E>
                         is a tree found in dry to mesic forest, often on lava, on the islands of Hawaii and Maui, Hawaii. This species is currently known from 8 populations totaling between 64 and 76 individuals.
                    </P>
                    <P>
                        <E T="03">Ochrosia haleakalae</E>
                         is threatened by fire; by feral pigs, goats, and cattle that degrade and destroy habitat and may directly prey upon it; and by nonnative plants that compete for light and nutrients. This species is represented in ex situ collections. Feral pigs, goats, and cattle have been fenced out of one wild and one outplanted population on private lands on the island of Maui and out of one outplanted population in Hawaii Volcanoes National Park on the island of Hawaii. Nonnative plants have been reduced in the fenced areas. The threat from fire is of a high magnitude and imminent because no control measures have been undertaken to address this threat that could adversely affect 
                        <E T="03">O. haleakalae</E>
                         as a whole. The threats from feral pigs, goats, and cattle are ongoing to the unfenced populations of 
                        <E T="03">O. haleakalae.</E>
                         The threat from nonnative plants is ongoing and imminent and of a high magnitude to the wild populations on both islands as this threat adversely affects the survival and reproductive capacity of the majority of the species, leading to a relatively high likelihood of extinction. Therefore, we retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Pediocactus peeblesianus</E>
                         var. 
                        <E T="03">fickeiseniae</E>
                         (Fickeisen plains cactus)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        <E T="03">Penstemon scariosus</E>
                         var. 
                        <E T="03">albifluvis</E>
                         (White River beardtongue)—The following summary is based on information contained in our files and the petition we received on October 27, 1983. This species is restricted to calcareous soils derived from oil shale barrens of the Green River Formation in the Uinta Basin of northeastern Utah and adjacent Colorado. There are 20 occurrences known in Utah and 1 in Colorado. Most of the occupied habitat of the White River beardtongue is within developed and expanding oil and gas fields. The location of the species' habitat exposes it to destruction from road, pipeline, and well site construction in connection with oil and gas development. Grazing by wildlife and livestock is an additional threat. A future threat (and potentially the greatest threat) to the species is oil shale development. Traditional oil and gas energy development is currently occurring and expected to increase within habitat areas for this species, and therefore the threat is imminent. 
                        <PRTPAGE P="66424"/>
                        However, the BLM has adopted a Special Status Species policy and has included in its current Resource Management Plan commitments to protect this species. These protections lessen the extent of traditional oil and gas development impacts to this species, so that although oil and gas development will continue to increase within this species' range, the threat is of moderate magnitude. The threats are ongoing and therefore imminent. Thus, we assigned an LPN of 9 to this plant variety.
                    </P>
                    <P>
                        <E T="03">Peperomia subpetiolata</E>
                         (‘Ala ‘ala wai nui)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Phyllostegia bracteata</E>
                         (no common name)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Phyllostegia floribunda</E>
                         (no common name)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Physaria douglasii</E>
                         ssp. 
                        <E T="03">tuplashensis</E>
                         (White Bluffs bladder-pod)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        <E T="03">Physaria globosa</E>
                         (Desvaux) O'Kane &amp; Al-Shehbaz (Short's bladderpod)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. With this publication of this document, we recognize the proposed reunion of the genus 
                        <E T="03">Lesquerella</E>
                         with 
                        <E T="03">Physaria</E>
                         (O'Kane and Al-Shehbaz 2002 entire) and now refer to Short's bladderpod by the scientific name 
                        <E T="03">Physaria globosa.</E>
                         Short's bladderpod is a perennial member of the mustard family that occurs in Indiana (1 location), Kentucky (6 locations), and Tennessee (22 locations). It grows on steep, rocky, wooded slopes; on talus areas; along cliff tops and bases; and on cliff ledges. It is usually associated with south-to west-facing calcareous outcrops adjacent to rivers or streams.
                    </P>
                    <P>
                        Road construction and road maintenance have played a significant role in the decline of 
                        <E T="03">P. globosa.</E>
                         Specific activities that have affected the species in the past and may continue to threaten it include bank stabilization, herbicide use, mowing during the growing season, grading of road shoulders, and road widening or repaving. Sediment deposition during road maintenance or from other activities also potentially threatens the species. Because the natural processes that maintained habitat suitability and competition from invasive, nonnative vegetation have been interrupted at many locations, active habitat management is necessary at those sites. While threats associated with roadside maintenance activities and habitat alterations by invasive plant encroachment are imminent because they are ongoing, these threats are of moderate magnitude as they are not affecting all locations of this species at this time. Therefore, we assigned an LPN of 8 to this species.
                    </P>
                    <P>
                        <E T="03">Platanthera integrilabia</E>
                         (Correll) Leur (White fringeless orchid)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Platanthera integrilabia</E>
                         is a perennial herb that grows in partially, but not fully, shaded, wet, boggy areas at the head of streams and on seepage slopes in Alabama, Georgia, Kentucky, Mississippi, South Carolina, and Tennessee. Historically, there were at least 90 populations of 
                        <E T="03">P. integrilabia.</E>
                         It is presumed extirpated from North Carolina and Virginia. Currently there are about 60 extant sites supporting the species.
                    </P>
                    <P>Several populations have been destroyed due to road, residential, and commercial construction, and to projects that altered soil and site hydrology such that suitability for the species was reduced. Several of the known populations are in or adjacent to powerline rights-of-way. Mechanical clearing of these areas may benefit the species by maintaining adequate light levels, but can promote development of dense, shrubby vegetation due to extensive suckering of woody species; however, the indiscriminant use of herbicides in these areas could pose a significant threat to the species. All-terrain vehicles have damaged several sites and pose a threat at most sites. Some of the known sites for the species occur in areas that are managed specifically for timber production. Timber management is not necessarily incompatible with the protection and management of the species, but care must be taken during timber management to ensure the hydrology of bogs supporting the species is not altered. Natural succession can result in decreased light levels. Because of the species dependence upon moderate-to-high light levels, some type of active management to prevent complete canopy closure is required at most locations. Collecting for commercial and other purposes is a potential threat. Herbivory (primarily deer) threatens the species at several sites. Due to the alteration of habitat and changes in natural conditions, protection and recovery of this species is dependent upon active management rather than just preservation of habitat. Invasive, nonnative plants such as Japanese honeysuckle and kudzu also threaten several sites. The threats are widespread; however, the impact of those threats on the survival of the species is moderate in magnitude. Several of the sites are protected to some degree from the threats by being within State parks, national forests, wildlife management areas, or other protected land. The threats are, however, imminent because they are ongoing, and we have therefore assigned an LPN of 8 to this species.</P>
                    <P>
                        <E T="03">Platydesma remyi</E>
                         (no common name)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Potentilla basaltica</E>
                         (Soldier Meadow cinquefoil or basalt cinquefoil)—The following summary is based on information contained in our files; the petition we received on May 11, 2004, provided no additional information on the species. 
                        <E T="03">Potentilla basaltica</E>
                         is a low-growing, rhizomatous, herbaceous perennial that forms a basal rosette and has bright yellow flowers. 
                        <E T="03">Potentilla basaltica</E>
                         is associated with alkali meadows, seeps, and occasionally marsh habitats bordering perennial thermal springs, outflows, and meadow depressions. In Nevada, the species is known only from Soldier Meadow in Humboldt County. In northeastern California, a single population occurs in Lassen County. At Soldier Meadow, there are 11 discrete known occurrences (10 on public and 1 on private land) within an area of about 24 acres (9.6 hectares) that support about 130,000 individuals. The California population occurs on private and public land and supports fewer than 1,000 plants. The public land in both California and Nevada has been designated as an Area 
                        <PRTPAGE P="66425"/>
                        of Critical Environmental Concern by the Bureau of Land Management (BLM).
                    </P>
                    <P>The species and its habitat are threatened by recreational use in the areas where it occurs as well as the ongoing impacts of past water diversions, livestock grazing, and off-road vehicle (OHV) travel. Conservation measures implemented recently by the BLM in Nevada include the installation of fencing to exclude livestock, wild horses, and other large mammals; the closure of access roads to spring, riparian, and wetland areas and the restriction of vehicles to designated routes; the establishment of a designated campground away from the habitats of sensitive species; the installation of educational signage; and, an increased staff presence, including law enforcement, a volunteer site steward during the 6-month period of peak visitor use, and noxious weed control. In California, BLM management actions include a proposed long-term monitoring plot, limiting OHV travel to designated routes, and excluding livestock grazing by fencing. These conservation measures have reduced the magnitude of threat to the species to moderate; all remaining threats are nonimminent and involve long-term changes to the habitat for the species resulting from past impacts. Until we can put in place a monitoring program that allows us to assess the long-term trend of the species, we have assigned an LPN of 11.</P>
                    <P>
                        <E T="03">Pseudognaphalium</E>
                         (
                        <E T="03">Gnaphalium</E>
                        ) 
                        <E T="03">sandwicensium</E>
                         var. 
                        <E T="03">molokaiense</E>
                         (Enaena)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Pseudognaphalium sandwicensium</E>
                         var. 
                        <E T="03">molokaiense</E>
                         is a perennial herb found in strand vegetation in dry consolidated dunes on the islands of Molokai and Maui, Hawaii. Historically, this variety was also found on Oahu and Lanai. This variety is known from 5 populations totaling approximately 200 to 20,000 individuals (depending upon rainfall) in the Moomomi area on the island of Molokai, and from 2 populations of a few individuals at Waiehu dunes and at Puu Kahulianapa on west Maui.
                    </P>
                    <P>
                        <E T="03">Pseudognaphalium sandwicensium</E>
                         var. 
                        <E T="03">molokaiense</E>
                         is threatened by feral goats and axis deer that degrade and destroy habitat and possibly prey upon it, and by nonnative plants that compete for light and nutrients. Potential threats also include collection for lei-making, and off-road vehicles that directly damage plants and degrade habitat. Weed control protects one population on Molokai; however, no conservation efforts have been initiated to date for the other populations on Molokai or for the individuals on Maui. This species is represented in an ex situ collection. The ongoing (and therefore imminent) threats from feral goats, axis deer, nonnative plants, collection, and off-road vehicles are of a high magnitude because no control measures have been undertaken for the Maui population or for the Molokai populations, and the threats result in direct mortality or significantly reduce reproductive capacity for the majority of the populations, leading to a relatively high likelihood of extinction. Therefore, we retained an LPN of 3 for this plant variety.
                    </P>
                    <P>
                        <E T="03">Ranunculus hawaiensis</E>
                         (Makou)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Ranunculus hawaiensis</E>
                         is an erect or ascending perennial herb found in mesic to wet forest dominated by 
                        <E T="03">Metrosideros polymorpha</E>
                         (ohia) and 
                        <E T="03">Acacia koa</E>
                         (koa) with scree substrate (loose stones or rocky debris on a slope) on the islands of Maui and Hawaii, Hawaii. This species is currently known from 14 individuals in 6 populations on the island of Hawaii. One population on Maui (Kukui planeze) was not relocated on a survey conducted in 2006. In addition, one wild population at Waikamoi (also on Maui) has not been observed since 1995. 
                        <E T="03">Ranunculus hawaiensis</E>
                         is threatened by direct predation by slugs, feral pigs, goats, cattle, mouflon, and sheep; by pigs, goats, cattle, mouflon, and sheep that degrade and destroy habitat; and by nonnative plants that compete for light and nutrients. Three populations have been outplanted into protected exclosures; however, feral ungulates and nonnative plants are not controlled in the remaining, unfenced populations. In addition, the threat from introduced slugs is of a high magnitude because slugs occur throughout the limited range of this species and no effective measures have been undertaken to control them or prevent them from causing significant adverse impacts to this species. Overall, the threats from pigs, goats, cattle, mouflon, sheep, slugs, and nonnative plants are of a high magnitude, and ongoing (imminent) for 
                        <E T="03">R. hawaiensis.</E>
                         We retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Ranunculus mauiensis</E>
                         (Makou)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Ranunculus mauiensis</E>
                         is an erect to weakly ascending perennial herb found in open sites in mesic to wet forest and along streams on the islands of Maui, Kauai, and Molokai, Hawaii. This species is currently known from 14 populations totaling 198 individuals. 
                        <E T="03">Ranunculus mauiensis</E>
                         is threatened by feral pigs, goats, mule deer, axis deer, and slugs that consume it; by habitat degradation and destruction by feral pigs, goats, and deer; and by nonnative plants that compete for light and nutrients. This species is represented in ex situ collections. Feral pigs have been fenced out of one Maui population of 
                        <E T="03">R. mauiensis,</E>
                         and nonnative plants have been reduced in the fenced area. One individual occurs in the Kamakou Preserve on Molokai, managed by The Nature Conservancy. However, ongoing conservation efforts benefit only two populations. As a result, the threats have the potential of bringing about extinction in a relatively short time scale, and are therefore are of high magnitude. They are also imminent because they are ongoing in the Kauai and the majority of the Maui populations. Therefore, we retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Rorippa subumbellata</E>
                         (Tahoe yellow cress)—The following summary is based on information contained in our files and the petition we received on December 27, 2000. 
                        <E T="03">Rorippa subumbellata</E>
                         is a small, branching, perennial herb with umbel-like inflorescences and yellow flowers. 
                        <E T="03">Rorippa subumbellata</E>
                         is known only from the shores of Lake Tahoe in California and Nevada. Data collected over the last 25 years generally indicate that occurrence of the species fluctuates yearly as a function of both lake level and the amount of exposed habitat. Records kept since 1900 show a preponderance of years with high lake levels that would isolate and reduce 
                        <E T="03">R. subumbellata</E>
                         occurrences at higher beach elevations. From the standpoint of the species, less favorable peak years have occurred almost twice as often as more favorable low-level years. Annual surveys are conducted to determine population numbers, site occupancy, and general disturbance regime. During the 2003 and 2004 annual survey periods, the lake level was approximately 6,224 feet (ft) (1,897.08 meters (m)); 2004 was the fourth consecutive year of low water. 
                        <E T="03">Rorippa subumbellata</E>
                         was present at 46 of the 60 sites surveyed, up from 31 occupied sites in 2001 when the lake level was higher at 6,225 ft (1,897.38 m). Approximately 25,200 stems were present in 2003, whereas during the 2001 annual survey, the estimated number of stems was 6,136. Lake levels rose again in 2006, and less habitat was 
                        <PRTPAGE P="66426"/>
                        available. Lake levels dropped again in 2008 through 2010, leading to an increase in both occupied sites and estimated stem counts. During very low lake levels in 2009, an estimated 27,522 stems were observed at 46 sites, equal to the highest number of occupied sites previously recorded.
                    </P>
                    <P>
                        Many 
                        <E T="03">Rorippa subumbellata</E>
                         sites are intensively used for commercial and public purposes and are subject to various activities such as erosion control, marina developments, pier construction, and recreation. The U.S. Forest Service, California Tahoe Conservancy, and California Department of Parks and Recreation have management programs for 
                        <E T="03">R. subumbellata</E>
                         which include monitoring, fenced enclosures, and transplanting efforts when funds and staff are available. Public agencies (including the Service), private landowners, and environmental groups collaborated to develop a conservation strategy coupled with a memorandum of understanding-conservation agreement. The conservation strategy, completed in 2003, contains goals and objectives for recovery and survival, a research and monitoring agenda, and serves as the foundation for an adaptive management program. Because of the continued commitments to conservation demonstrated by regulatory and land management agencies participating in the conservation strategy, we have determined the threats to 
                        <E T="03">R. subumbellata</E>
                         from various land uses have been reduced to a moderate magnitude. In high lake-level years such as 2005, however, recreational use is concentrated within 
                        <E T="03">R. subumbellata</E>
                         habitat, and we consider this threat in particular to be ongoing and imminent. Therefore, we are maintaining an LPN of 8 for this species.
                    </P>
                    <P>
                        <E T="03">Schiedea pubescens</E>
                         (Maolioli)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Schiedea pubescens</E>
                         is a reclining or weakly climbing vine found in diverse mesic to wet forest on the islands of Maui, Molokai, and Hawaii, Hawaii. It is presumed extirpated from Lanai. Currently, this species is known from 8 populations totaling between 30 and 32 individuals on Maui, from 4 populations totaling between 21 and 22 individuals on Molokai, and from 1 population of 4 to 6 individuals on the island of Hawaii.
                    </P>
                    <P>
                        <E T="03">Schiedea pubescens</E>
                         is threatened by feral pigs and goats that consume it and degrade and destroy habitat, and by nonnative plants that compete for light and nutrients. Feral ungulates have been fenced out of the population of 
                        <E T="03">S. pubescens</E>
                         on the island of Hawaii. Feral goats have been fenced out of a few of the west Maui populations of 
                        <E T="03">S. pubescens.</E>
                         Nonnative plants have been reduced in the populations that are fenced on Maui. However, the threats are not controlled and are ongoing in the remaining unfenced populations on Maui and the four populations on Molokai. Additional fenced areas are planned at Pohakuloa Training Area on the island of Hawaii. Nonnative feral ungulates and nonnative plants will be controlled within these fenced areas. Fire is a potential threat to the Hawaii Island population. In light of the extremely low number of individuals of this species, the threats from goats and nonnative plants are of a high magnitude because they result in mortality and reduced reproductive capacity for the majority of the populations, leading to a relatively high likelihood of extinction. The threats are imminent because they are ongoing with respect to most of the populations. Therefore, we retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Schiedea salicaria</E>
                         (no common name)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Sedum eastwoodiae</E>
                         (Red Mountain stonecrop)—The following summary is based on information contained in our files and information provided by the California Department of Fish and Game. The petition we received on May 11, 2004, provided no new information on the species. Red Mountain stonecrop is a perennial succulent which occupies relatively barren, rocky openings and cliffs in lower montane coniferous forests, between 1,900 and 4,000 feet elevation. Its distribution is limited to Red Mountain, Mendocino County, California, where it occupies in excess of 54 acres scattered over 4 square miles. The species' distribution by ownership is described as follows: Federal (Bureau of Land Management), 95 percent; private, 5 percent. Total population size has not been determined, but a preliminary estimate suggests the population may be in excess of 29,000 plants, occupying more than 27 discrete habitat polygons. Intensive monitoring suggests considerable annual variation in plant seedling success and inflorescence production. The primary threat to the species is the potential for surface mining for chromium and nickel. The entire distribution of Red Mountain stonecrop is either owned by mining interests, or is covered by mining claims, none of which are currently active. Surface mining would destroy habitat suitability for this species. The species is also believed threatened by tree and shrub encroachment into its habitat, in absence of fire. Approximately 25 percent of its known distribution occurred within the boundary of the Red Mountain Fire of June 2008. However, the extent and manner in which Red Mountain stonecrop and its habitat were affected by that fire is not yet known. Given the magnitude (high) and immediacy (nonimminent) of the threat to the small, scattered populations, and its taxonomy (species), we assigned an LPN of 5 to this species.
                    </P>
                    <P>
                        <E T="03">Sicyos macrophyllus</E>
                         (`Anunu)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Solanum conocarpum</E>
                         (marron bacora)—The following summary is based on information in our files and in the petition we received on November 21, 1996. 
                        <E T="03">Solanum conocarpum</E>
                         is a dry-forest shrub in the island of St. John, U.S. Virgin Islands. Its current distribution includes eight localities in the island of St. John, each ranging from 1 to 144 individuals. The species has been reported to occur on dry, poor soils. It can be locally abundant in exposed topography on sites disturbed by erosion, areas that have received moderate grazing, and around ridgelines as an understory component in diverse woodland communities. A habitat suitability model suggests that the vast majority of 
                        <E T="03">Solanum conocarpum</E>
                         habitat is found in the lower elevation coastal scrub forest. Efforts have been conducted to propagate the species to enhance natural populations, and planting of seedlings has been conducted in the island of St. John.
                    </P>
                    <P>
                        <E T="03">Solanum conocarpum</E>
                         is threatened by the lack of natural recruitment, absence of dispersers, fragmented distribution, lack of genetic variation, climate change, and habitat destruction or modification by exotic mammal species. These threats are evidenced by the reduced number of individuals, low number of populations, and lack of connectivity between populations. Overall, we determined the magnitude of the threats to be high as shown by the poor quality of the populations. The majority of threats are ongoing and, therefore, imminent. We assigned an LPN of 2 to this species.
                        <PRTPAGE P="66427"/>
                    </P>
                    <P>
                        <E T="03">Solanum nelsonii</E>
                         (popolo)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Solanum nelsonii</E>
                         is a sprawling or trailing shrub found in coral rubble or sand in coastal sites. This species is known from populations on Molokai (approximately 300 plants), the island of Hawaii (5 plants), and the northwestern Hawaiian Islands (NWHI), Hawaii. The current populations in the NWHI are found on Kure (unknown number of individuals), Midway (approximately 260 plants), Laysan (approximately 490 plants), Pearl and Hermes (unknown number of individuals), and Nihoa (8,000 to 15,000 adult plants). On Molokai, 
                        <E T="03">S. nelsonii</E>
                         is moderately threatened by ungulates that degrade and destroy habitat, and may eat
                        <E T="03"> S. nelsonii.</E>
                         On Molokai and the NWHI, this species is threatened by nonnative plants that outcompete and displace it. 
                        <E T="03">Solanum nelsonii</E>
                         is threatened by predation by a nonnative grasshopper in the NWHI. On Kure, Midway, Laysan, and Pearl and Hermes in the NWHI, tsunamis are also a potential threat to 
                        <E T="03">S. nelsonii.</E>
                         This species is represented in ex situ collections. Ungulate exclusion fences, routine fence monitoring and maintenance, and weed control protect the population of 
                        <E T="03">S. nelsonii</E>
                         on Molokai. Limited weed control is conducted in the NWHI. These threats are of moderate magnitude because of the relatively large number of plants, and the fact that this species is found on more than one island. The threats are imminent for the majority of the populations because they are ongoing and are not being controlled. We therefore retained an LPN of 8 for this species.
                    </P>
                    <P>
                        <E T="03">Solidago plumosa</E>
                         (Yadkin River goldenrod)—The following information is based on information in our files. No new information was provided in the petition we received on April 20, 2010. The global distribution of 
                        <E T="03">Solidago plumosa</E>
                         consists of a single population that occurs in two discrete locations along a 2.5-mile stretch of the Yadkin River in North Carolina. The availability of suitable habitat and the fate of the single known population of this species are primarily determined by the manner in which two hydroelectric projects (the Yadkin River and Yadkin-Pee Dee River Hydroelectric Projects) are operated. Any detrimental effects to 
                        <E T="03">S. plumosa</E>
                         resulting from the construction of these reservoirs occurred decades ago when these projects were built (during the years of 1917 to 1928), and the Service is not aware of any plans to construct additional reservoirs within the current range of this species. However, 
                        <E T="03">S. plumosa</E>
                         continues to be subject to threats from the continued operation of these reservoirs (which has reduced the frequency and severity of scouring floods that help to prevent the establishment of other species within the species' limited habitat) and the encroachment of nonnative, invasive species. Because the species' global distribution consists of a single population, its entire range is affected by these threats. However, because scouring floods (prior to reservoir construction) likely only occurred episodically, and in light of the relatively slow progression of nonnative species into areas of occupied habitat, the magnitude of these threats is moderate to low. However, because these threats (especially those presented by nonnative, invasive plant species) are currently occurring, they are imminent. Thus, we assigned this species an LPN of 8.
                    </P>
                    <P>
                        <E T="03">Sphaeralcea gierischii</E>
                         (Gierisch mallow)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted petition 12-month finding.
                    </P>
                    <P>
                        <E T="03">Stenogyne cranwelliae</E>
                         (no common name)—We continue to find that listing this species is warranted, but precluded as of the date of publication of this notice. However, we are working on a proposed listing rule that we expect to publish prior to making the next annual resubmitted 12-month petition finding.
                    </P>
                    <P>
                        <E T="03">Symphyotrichum georgianum</E>
                         (Georgia aster)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. Georgia aster is a relict species of post oak savanna/prairie communities that existed in the Southeast prior to widespread fire suppression and extirpation of large native grazing animals. Georgia aster currently occurs in the States of Alabama, Georgia, North Carolina, and South Carolina. The species is presumed extant in 8 counties in Alabama, 22 counties in Georgia, 9 counties in North Carolina, and 15 counties in South Carolina. The species appears to have been eliminated from Florida.
                    </P>
                    <P>Most remaining populations survive adjacent to roads, utility rights-of-way, and other openings where current land management mimics natural disturbance regimes. Most populations are small (10 to 100 stems), and because the species' main mode of reproduction is vegetative, each isolated population may represent only a few genotypes. Many populations are currently threatened by one or more of the following factors: woody succession due to fire suppression, development, highway expansion or improvement, and herbicide application. However, the species is still relatively widely distributed, and recent information indicates the species is more abundant than when we initially identified it as a candidate for listing. Taking into account its distribution and abundance, the magnitude of threats is moderate. The threats are currently occurring and therefore are imminent. Thus we assigned an LPN of 8 for this species.</P>
                    <HD SOURCE="HD2">Ferns and Allies</HD>
                    <P>
                        <E T="03">Cyclosorus boydiae</E>
                         (no common name)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. This species is a small- to medium-sized fern found in mesic to wet forest along stream banks on the islands of Oahu and Maui, Hawaii. Historically, this species was also found on the island of Hawaii, but it has been extirpated there. Currently, this species is known from 7 populations totaling approximately 400 individuals. This species is threatened by feral pigs that degrade and destroy habitat and may eat this plant, and by nonnative plants that compete for light and nutrients. Feral pigs have been fenced out of the largest population on Maui, and nonnative plants have been reduced in the fenced area. No conservation efforts are under way to alleviate threats to the other two populations on Maui, or for the two populations on Oahu. This species is represented in an ex situ collection. The magnitude of the threats acting upon the currently extant populations is moderate because the largest population is protected from pigs, and nonnative plants have been reduced in this area. The threats are ongoing and therefore imminent. Therefore, we retained an LPN of 8 for this species.
                    </P>
                    <P>
                        <E T="03">Huperzia stemmermanniae</E>
                         (Waewaeiole)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. This species is an epiphytic pendant clubmoss found in mesic-to-wet 
                        <E T="03">Metrosideros polymorpha-Acacia koa</E>
                         (ohia-koa) forests on the islands of Maui and Hawaii, Hawaii. Only 3 populations are known, on Maui and Hawaii, totaling approximately 30 individuals. The Maui population has not been relocated since 1995. 
                        <E T="03">
                            Huperzia 
                            <PRTPAGE P="66428"/>
                            stemmermanniae
                        </E>
                         is threatened by feral pigs, goats, cattle, and axis deer that degrade and destroy habitat, and by nonnative plants that compete for light, space, and nutrients. 
                        <E T="03">Huperzia stemmermanniae</E>
                         is also threatened by randomly occurring natural events due to its small population size. One individual at Waikamoi Preserve may benefit from fencing for axis deer and pigs. This species is represented in ex situ collections. The threats from pigs, goats, cattle, axis deer, and nonnative plants are of a high magnitude because they are sufficiently severe to adversely affect the species throughout its limited range, resulting in direct mortality or significantly reducing reproductive capacity, leading to a relatively high likelihood of extinction. The threats are imminent because they are ongoing. Therefore, we retained an LPN of 2 for this species.
                    </P>
                    <P>
                        <E T="03">Microlepia strigosa</E>
                         var. 
                        <E T="03">mauiensis</E>
                         (Palapalai)—The following summary is based on information contained in our files. No new information was provided in the petition we received on May 11, 2004. 
                        <E T="03">Microlepia strigosa</E>
                         var. 
                        <E T="03">mauiensis</E>
                         is a terrestrial fern found in mesic-to-wet forests. It is currently found in Hawaii on the islands of Maui, Oahu, and Hawaii, from at least 9 populations totaling at least 50 individuals. There is a possibility that the range of this plant variety could be larger and include the other main Hawaiian Islands. 
                        <E T="03">Microlepia strigosa</E>
                         var. 
                        <E T="03">mauiensis</E>
                         is threatened by feral pigs that degrade and destroy habitat, and by nonnative plants that compete for light and nutrients. Pigs have been fenced out of some areas on east and west Maui, Oahu, and on Hawaii, where 
                        <E T="03">M. strigosa</E>
                         var. 
                        <E T="03">mauiensis</E>
                         currently occurs, and nonnative plants have been reduced in the fenced areas. However, the threats are not controlled and are ongoing in the remaining unfenced populations on Maui, Oahu, and Hawaii. Therefore, the threats from feral pigs and nonnative plants are imminent. The threats are of a high magnitude because they are sufficiently severe to adversely affect the species throughout its range, resulting in direct mortality or significantly reducing reproductive capacity, leading to a relatively high likelihood of extinction. We therefore retained an LPN of 3 for 
                        <E T="03">M. strigosa</E>
                         var. 
                        <E T="03">mauiensis.</E>
                    </P>
                    <HD SOURCE="HD2">Petitions To Reclassify Species Already Listed or To Add to the Listed Range</HD>
                    <P>
                        We previously made warranted-but-precluded findings on five petitions seeking to reclassify threatened species to endangered status. The taxa involved in the reclassification petitions are three populations of the grizzly bear (
                        <E T="03">Ursus arctos</E>
                          
                        <E T="03">horribilis</E>
                        ), delta smelt (
                        <E T="03">Hypomesus transpacificus</E>
                        ), and
                        <E T="03"> Sclerocactus brevispinus</E>
                         (Pariette cactus). Because these species are already listed under the ESA, they are not candidates for listing and are not included in Table 1. However, this notice and associated species assessment forms or 5-year review documents also constitute the resubmitted petition findings for these species. For delta smelt, we have not updated the information included in the 12-month finding (published April 7, 2010, at 75 FR 17667), which serves as our assessment; we are currently conducting a 5-year review, which will provide updated information when we complete it later this year. For the three grizzly bear populations, our recently completed 5-year review serves as our assessment. For 
                        <E T="03">Sclerocactus brevispinus,</E>
                         our updated assessment is provided below. We find that reclassification to endangered status for the three grizzly bear populations, delta smelt, and 
                        <E T="03">Sclerocactus brevispinus</E>
                         are all currently warranted but precluded by work identified above (see “Petition Findings for Candidate Species”). One of the primary reasons that the work identified above is considered higher priority is that the grizzly bear populations, delta smelt, and
                        <E T="03"> Sclerocactus brevispinus</E>
                         are currently listed as threatened, and therefore already receive certain protections under the ESA. We promulgated regulations extending take prohibitions for wildlife and plants under section 9 to threatened species (50 CFR 17.31 and 50 CFR 17.71, respectively). Prohibited actions under section 9 for wildlife include, but are not limited to, take (i.e., to harass, harm, pursue, hunt, shoot, wound, kill, trap, capture, or collect, or attempt to engage in such activity). For plants, prohibited actions under section 9 include removing or reducing to possession any listed plant from an area under Federal jurisdiction (50 CFR 17.61). Other protections include those under section 7(a)(2) of the ESA whereby Federal agencies must insure that any action they authorize, fund, or carry out is not likely to jeopardize the continued existence of any endangered or threatened species.
                    </P>
                    <P>
                        Grizzly bear (
                        <E T="03">Ursus arctos horribilis</E>
                        ) North Cascades ecosystem, Cabinet-Yaak, and Selkirk populations (Region 6)—Between 1986 and 2007, we have received and reviewed 10 petitions requesting a change in status for individual grizzly bear populations (51 FR 16363, May 2, 1986; 55 FR 32103, August 7, 1990; 56 FR 33892, July 24, 1991; 57 FR 14372, April 20, 1992; 58 FR 8250, February 12, 1993; 58 FR 38552, July 19, 1993; 58 FR 43856, August 18, 1993; 58 FR 43857, August 18, 1993; 59 FR 46611, September 9, 1994; 64 FR 26725, May 17, 1999; 72 FR 14866, March 29, 2007). Through this process, we determined the Cabinet-Yaak, Selkirk, and North Cascade ecosystems warrant endangered status. On April 18, 2007, the Service initiated a 5-year review to evaluate the current status of grizzly bears in the lower 48 States (72 FR 19549-19551). This status review, completed on August 29, 2011, and available online at: 
                        <E T="03">http://ecos.fws.gov/speciesProfile/profile/speciesProfile.action?spcode=A001,</E>
                         recommended that the Cabinet-Yaak, Selkirk, and North Cascades Ecosystems remain warranted but precluded for endangered status.
                    </P>
                    <P>
                        Delta smelt (
                        <E T="03">Hypomesus transpacificus</E>
                        ) (Region 8) (see 75 FR 17667; April 7, 2010, for additional information on why reclassification to endangered is warranted but precluded)—In March 2004, we completed a 5-year review for delta smelt in which we determined a change in status from threatened to endangered was not recommended. While none of the threats, other than apparent abundance, show significant differences from 2004, we now have strong evidence, not available at the time of our 5-year review, that at least some of those factors are endangering the species. The primary evidence is the continuing downward trend in delta smelt abundance indices since a significant decline that occurred in 2002. The most recent fall midwater trawl abundance index is the lowest ever recorded—less than one-tenth the level it was in 2003. In addition, a 2005 population viability analysis calculated a 50-percent likelihood that the species could reach effective extinction (8,000 individuals) within 20 years.
                    </P>
                    <P>There are many primary threats to the species including: Direct entrainments by State and Federal water export facilities; summer and fall increases in salinity and water clarity; and effects from introduced species. Additional threats are predation by striped and largemouth bass and inland silversides, entrainment into power plants, contaminants, and small population size. Existing regulatory mechanisms have not proven adequate to halt the decline of delta smelt since the time of listing as a threatened species.</P>
                    <P>
                        As a result of our analysis of the best available scientific and commercial information, we have assigned uplisting the delta smelt an LPN of 2, based on high-magnitude, imminent threats. The 
                        <PRTPAGE P="66429"/>
                        magnitude of the threats is high, because they occur rangewide and result in mortality or significantly reduce the reproductive capacity of the species, leading to a relatively high likelihood of extinction. They are imminent because these threats are ongoing and, in some cases (e.g., nonnative species), considered irreversible.
                    </P>
                    <P>
                        <E T="03">Sclerocactus brevispinus</E>
                         (Pariette cactus) (Region 6) (see 72 FR 53211, September 18, 2007, and the species assessment form (see 
                        <E T="02">ADDRESSES</E>
                        ) for additional information on why reclassification to endangered is warranted but precluded)—
                        <E T="03">Sclerocactus brevispinus</E>
                         is restricted to clay badlands of the Wagon Hound member of the Uinta Formation in the Uinta Basin of northeastern Utah. The species is restricted to one population with an overall range of approximately 10 miles by 5 miles in extent. The species' entire population is within a developed and expanding oil and gas field. The location of the species' habitat exposes it to destruction from road, pipeline, and well-site construction in connection with oil and gas development. The species may be collected as a specimen plant for horticultural use. Recreational off-road vehicle use and livestock trampling are additional potential threats. The species is currently federally listed as threatened by its previous inclusion within the species 
                        <E T="03">Sclerocactus glaucus.</E>
                         Based on current information, we are recommending an LPN of 2 for reclassifying this species as endangered, to reflect that: (1) The threats are of a high magnitude because any one of the threats has the potential to severely affect this species, a narrow endemic with a highly limited range and distribution; and (2) threats are ongoing and, therefore, are imminent.
                    </P>
                    <HD SOURCE="HD1">Current Notice of Review</HD>
                    <P>We gather data on plants and animals native to the United States that appear to merit consideration for addition to the Lists of Endangered and Threatened Wildlife and Plants (Lists). This notice identifies those species that we currently regard as candidates for addition to the Lists. These candidates include species and subspecies of fish, wildlife, or plants and DPSes of vertebrate animals. This compilation relies on information from status surveys conducted for candidate assessment and on information from State Natural Heritage Programs, other State and Federal agencies, knowledgeable scientists, public and private natural resource interests, and comments received in response to previous notices of review.</P>
                    <P>Tables 1 and 2 list animals arranged alphabetically by common names under the major group headings, and list plants alphabetically by names of genera, species, and relevant subspecies and varieties. Animals are grouped by class or order. Plants are subdivided into two groups: (1) Flowering plants and (2) ferns and their allies. Useful synonyms and subgeneric scientific names appear in parentheses with the synonyms preceded by an “equals” sign. Several species that have not yet been formally described in the scientific literature are included; such species are identified by a generic or specific name (in italics), followed by “sp.” or “ssp.” We incorporate standardized common names in these notices as they become available. We sort plants by scientific name due to the inconsistencies in common names, the inclusion of vernacular and composite subspecific names, and the fact that many plants still lack a standardized common name.</P>
                    <P>Table 1 lists all candidate species, plus species currently proposed for listing under the ESA. We emphasize that in this notice we are not proposing to list any of the candidate species; rather, we will develop and publish proposed listing rules for these species in the future. We encourage State agencies, other Federal agencies, and other parties to give consideration to these species in environmental planning.</P>
                    <P>In Table 1, the “category” column on the left side of the table identifies the status of each species according to the following codes:</P>
                    <P>
                        PE—Species proposed for listing as endangered. Proposed species are those species for which we have published a proposed rule to list as endangered or threatened in the 
                        <E T="04">Federal Register</E>
                        . This category does not include species for which we have withdrawn or finalized the proposed rule.
                    </P>
                    <P>PT—Species proposed for listing as threatened.</P>
                    <P>PSAT—Species proposed for listing as threatened due to similarity of appearance.</P>
                    <P>
                        C—Candidates: Species for which we have on file sufficient information on biological vulnerability and threats to support proposals to list them as endangered or threatened. Issuance of proposed rules for these species is precluded at present by other higher priority listing actions. This category includes species for which we made a 12-month warranted-but-precluded finding on a petition to list. We made new findings on all petitions for which we previously made “warranted-but-precluded” findings. We identify the species for which we made a continued warranted-but-precluded finding on a resubmitted petition by the code “C*” in the category column (see “
                        <E T="03">Findings for Petitioned Candidate Species”</E>
                         section for additional information).
                    </P>
                    <P>
                        The “Priority” column indicates the LPN for each candidate species, which we use to determine the most appropriate use of our available resources. The lowest numbers have the highest priority. We assign LPNs based on the immediacy and magnitude of threats, as well as on taxonomic status. We published a complete description of our listing priority system in the 
                        <E T="04">Federal Register</E>
                         (48 FR 43098, September 21, 1983).
                    </P>
                    <P>
                        The third column, “Lead Region,” identifies the Regional Office to which you should direct information, comments, or questions (see addresses under Request for Information at the end of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section).
                    </P>
                    <P>Following the scientific name (fourth column) and the family designation (fifth column) is the common name (sixth column). The seventh column provides the known historical range for the species or vertebrate population (for vertebrate populations, this is the historical range for the entire species or subspecies and not just the historical range for the distinct population segment), indicated by postal code abbreviations for States and U.S. territories. Many species no longer occur in all of the areas listed.</P>
                    <P>Species in Table 2 of this notice are those we included either as proposed species or as candidates in the previous CNOR (published November 10, 2010 at 75 FR 69222) that are no longer proposed species or candidates for listing. Since November 10, 2010, we listed nine species, emergency listed one species, withdrew a proposed rule for one species, and removed three species from candidate status for the reason indicated by the code. Also included in this table are three species that were not previously candidates or proposed species but we emergency listed due to similarity in appearance. The first column indicates the present status of each species, using the following codes (not all of these codes may have been used in this CNOR):</P>
                    <P>E—Species we listed as endangered.</P>
                    <P>T—Species we listed as threatened.</P>
                    <P>Rc—Species we removed from the candidate list because currently available information does not support a proposed listing.</P>
                    <P>Rp—Species we removed from because we have withdrawn the proposed listing.</P>
                    <P>
                        The second column indicates why we no longer regard the species as a 
                        <PRTPAGE P="66430"/>
                        candidate or proposed species using the following codes (not all of these codes may have been used in this CNOR):
                    </P>
                    <P>A—Species that are more abundant or widespread than previously believed and species that are not subject to the degree of threats sufficient to warrant continuing candidate status, or issuing a proposed or final listing.</P>
                    <P>F—Species whose range no longer includes a U.S. territory.</P>
                    <P>I—Species for which we have insufficient information on biological vulnerability and threats to support issuance of a proposed rule to list.</P>
                    <P>L—Species we added to the Lists of Endangered and Threatened Wildlife and Plants.</P>
                    <P>M—Species we mistakenly included as candidates or proposed species in the last notice of review.</P>
                    <P>N—Species that are not listable entities based on the ESA's definition of “species” and current taxonomic understanding.</P>
                    <P>U—Species that are not subject to the degree of threats sufficient to warrant issuance of a proposed listing or continuance of candidate status due, in part or totally, to conservation efforts that remove or reduce the threats to the species.</P>
                    <P>X—Species we believe to be extinct.</P>
                    <P>The columns describing lead region, scientific name, family, common name, and historical range include information as previously described for Table 1.</P>
                    <HD SOURCE="HD1">Request for Information</HD>
                    <P>We request you submit any further information on the species named in this notice as soon as possible or whenever it becomes available. We are particularly interested in any information:</P>
                    <P>(1) Indicating that we should add a species to the list of candidate species;</P>
                    <P>(2) Indicating that we should remove a species from candidate status;</P>
                    <P>(3) Recommending areas that we should designate as critical habitat for a species, or indicating that designation of critical habitat would not be prudent for a species;</P>
                    <P>(4) Documenting threats to any of the included species;</P>
                    <P>(5) Describing the immediacy or magnitude of threats facing candidate species;</P>
                    <P>(6) Pointing out taxonomic or nomenclature changes for any of the species;</P>
                    <P>(7) Suggesting appropriate common names; and</P>
                    <P>(8) Noting any mistakes, such as errors in the indicated historical ranges.</P>
                    <P>Submit information, materials, or comments regarding a particular species to the Regional Director of the Region identified as having the lead responsibility for that species. The regional addresses follow:</P>
                    <P>Region 1. Hawaii, Idaho, Oregon, Washington, American Samoa, Guam, and Commonwealth of the Northern Mariana Islands. Regional Director (TE), U.S. Fish and Wildlife Service, Eastside Federal Complex, 911 N.E. 11th Avenue, Portland, OR 97232-4181 (503/231-6158).</P>
                    <P>Region 2. Arizona, New Mexico, Oklahoma, and Texas. Regional Director (TE), U.S. Fish and Wildlife Service, 500 Gold Avenue SW., Room 4012, Albuquerque, NM 87102 (505/248-6920).</P>
                    <P>Region 3. Illinois, Indiana, Iowa, Michigan, Minnesota, Missouri, Ohio, and Wisconsin. Regional Director (TE), U.S. Fish and Wildlife Service, 5600 American Blvd. West, Suite 990, Bloomington, MN 55437-1458 (612/713-5334).</P>
                    <P>Region 4. Alabama, Arkansas, Florida, Georgia, Kentucky, Louisiana, Mississippi, North Carolina, South Carolina, Tennessee, Puerto Rico, and the U.S. Virgin Islands. Regional Director (TE), U.S. Fish and Wildlife Service, 1875 Century Boulevard, Suite 200, Atlanta, GA 30345 (404/679-4156).</P>
                    <P>Region 5. Connecticut, Delaware, District of Columbia, Maine, Maryland, Massachusetts, New Hampshire, New Jersey, New York, Pennsylvania, Rhode Island, Vermont, Virginia, and West Virginia. Regional Director (TE), U.S. Fish and Wildlife Service, 300 Westgate Center Drive, Hadley, MA 01035-9589 (413/253-8615).</P>
                    <P>Region 6. Colorado, Kansas, Montana, Nebraska, North Dakota, South Dakota, Utah, and Wyoming. Regional Director (TE), U.S. Fish and Wildlife Service, P.O. Box 25486, Denver Federal Center, Denver, CO 80225-0486 (303/236-7400).</P>
                    <P>Region 7. Alaska. Regional Director (TE), U.S. Fish and Wildlife Service, 1011 East Tudor Road, Anchorage, AK 99503-6199 (907/786-3505).</P>
                    <P>Region 8. California and Nevada. Regional Director (TE), U.S. Fish and Wildlife Service, 2800 Cottage Way, Suite W2606, Sacramento, CA 95825 (916/414-6464).</P>
                    <P>We will provide information received in response to the previous CNOR to the Region having lead responsibility for each candidate species mentioned in the submission. We will likewise consider all information provided in response to this CNOR in deciding whether to propose species for listing and when to undertake necessary listing actions (including whether emergency listing under section 4(b)(7) of the ESA is appropriate). Information and comments we receive will become part of the administrative record for the species, which we maintain at the appropriate Regional Office.</P>
                    <P>Before including your address, phone number, e-mail address, or other personal identifying information in your submission, be advised that your entire submission—including your personal identifying information—may be made publicly available at any time. Although you can ask us in your submission to withhold from public review your personal indentifying information, we cannot guarantee that we will be able to do so.</P>
                    <HD SOURCE="HD1">Authority</HD>
                    <P>This notice is published under the authority of the Endangered Species Act of 1973, as amended (16 U.S.C. 1531 et seq.).</P>
                    <SIG>
                        <DATED>Dated: October 7, 2011.</DATED>
                        <FP>Signed:</FP>
                        <NAME>Gregory E. Siekaniec,</NAME>
                        <TITLE>Deputy Director, Fish and Wildlife Service.</TITLE>
                    </SIG>
                    <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="xs36,xs36,xls36,r50,r50,r50,r50">
                        <TTITLE>Table 1—Candidate Notice of Review (Animals and Plants)</TTITLE>
                        <TDESC>
                            [Note: See end of 
                            <E T="02">SUPPLEMENTARY INFORMATION</E>
                             for an explanation of symbols used in this table]
                        </TDESC>
                        <BOXHD>
                            <CHED H="1">Status</CHED>
                            <CHED H="2">Category</CHED>
                            <CHED H="2">Priority</CHED>
                            <CHED H="1">
                                Lead 
                                <LI>region</LI>
                            </CHED>
                            <CHED H="1">Scientific name</CHED>
                            <CHED H="1">Family</CHED>
                            <CHED H="1">Common name</CHED>
                            <CHED H="1">Historical range</CHED>
                        </BOXHD>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">MAMMALS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Eumops floridanus</E>
                            </ENT>
                            <ENT>Molossidae</ENT>
                            <ENT>Bat, Florida bonneted</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Emballonura semicaudata rotensis</E>
                            </ENT>
                            <ENT>Emballonuridae</ENT>
                            <ENT>Bat, Pacific sheath-tailed (Mariana Islands subspecies)</ENT>
                            <ENT>U.S.A. (GU, CNMI).</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="66431"/>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Emballonura semicaudata semicaudata</E>
                            </ENT>
                            <ENT>Emballonuridae</ENT>
                            <ENT>Bat, Pacific sheath-tailed (American Samoa DPS)</ENT>
                            <ENT>U.S.A. (AS), Fiji, Independent Samoa, Tonga, Vanuatu.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R5</ENT>
                            <ENT>
                                <E T="03">Sylvilagus transitionalis</E>
                            </ENT>
                            <ENT>Leporidae</ENT>
                            <ENT>Cottontail, New England</ENT>
                            <ENT>U.S.A. (CT, MA, ME, NH, NY, RI, VT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>6</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Martes pennanti</E>
                            </ENT>
                            <ENT>Mustelidae</ENT>
                            <ENT>Fisher (west coast DPS)</ENT>
                            <ENT>U.S.A. (CA, CT, IA, ID, IL, IN, KY, MA, MD, ME, MI, MN, MT, ND, NH, NJ, NY, OH, OR, PA, RI, TN, UT, VA, VT, WA, WI, WV, WY), Canada.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Zapus hudsonius luteus</E>
                            </ENT>
                            <ENT>Zapodidae</ENT>
                            <ENT>Mouse, New Mexico meadow jumping</ENT>
                            <ENT>U.S.A. (AZ, CO, NM).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Thomomys mazama couchi</E>
                            </ENT>
                            <ENT>Geomyidae</ENT>
                            <ENT>Pocket gopher, Shelton</ENT>
                            <ENT>U.S.A. (WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Thomomys mazama douglasii</E>
                            </ENT>
                            <ENT>Geomyidae</ENT>
                            <ENT>Pocket gopher, Brush Prairie</ENT>
                            <ENT>U.S.A. (WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Thomomys mazama glacialis</E>
                            </ENT>
                            <ENT>Geomyidae</ENT>
                            <ENT>Pocket gopher, Roy Prairie</ENT>
                            <ENT>U.S.A. (WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Thomomys mazama louiei</E>
                            </ENT>
                            <ENT>Geomyidae</ENT>
                            <ENT>Pocket gopher, Cathlamet</ENT>
                            <ENT>U.S.A. (WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Thomomys mazama melanops</E>
                            </ENT>
                            <ENT>Geomyidae</ENT>
                            <ENT>Pocket gopher, Olympic</ENT>
                            <ENT>U.S.A. (WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Thomomys mazama pugetensis</E>
                            </ENT>
                            <ENT>Geomyidae</ENT>
                            <ENT>Pocket gopher, Olympia</ENT>
                            <ENT>U.S.A. (WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Thomomys mazama tacomensis</E>
                            </ENT>
                            <ENT>Geomyidae</ENT>
                            <ENT>Pocket gopher, Tacoma</ENT>
                            <ENT>U.S.A. (WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Thomomys mazama tumuli</E>
                            </ENT>
                            <ENT>Geomyidae</ENT>
                            <ENT>Pocket gopher, Tenino</ENT>
                            <ENT>U.S.A. (WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Thomomys mazama yelmensis</E>
                            </ENT>
                            <ENT>Geomyidae</ENT>
                            <ENT>Pocket gopher, Yelm</ENT>
                            <ENT>U.S.A. (WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Cynomys gunnisoni</E>
                            </ENT>
                            <ENT>Sciuridae</ENT>
                            <ENT>Prairie dog, Gunnison's (populations in central and south-central Colorado, north-central New Mexico)</ENT>
                            <ENT>U.S.A. (CO, NM).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>9</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Spermophilus brunneus endemicus</E>
                            </ENT>
                            <ENT>Sciuridae</ENT>
                            <ENT>Squirrel, Southern Idaho ground</ENT>
                            <ENT>U.S.A. (ID).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Spermophilus washingtoni</E>
                            </ENT>
                            <ENT>Sciuridae</ENT>
                            <ENT>Squirrel, Washington ground</ENT>
                            <ENT>U.S.A. (WA, OR).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>9</ENT>
                            <ENT>R7</ENT>
                            <ENT>
                                <E T="03">Odobenus rosmarus divergens</E>
                            </ENT>
                            <ENT>Odobenidae</ENT>
                            <ENT>Walrus, Pacific</ENT>
                            <ENT>U.S.A. (AK), Canada, Russia.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">C*</ENT>
                            <ENT>6</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Gulo gulo luscus</E>
                            </ENT>
                            <ENT>Mustelidae</ENT>
                            <ENT>Wolverine, North American (Contiguous U.S. DPS)</ENT>
                            <ENT>U.S.A. (CA, CO, ID, MT, OR, UT, WA, WY).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">BIRDS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Porzana tabuensis</E>
                            </ENT>
                            <ENT>Rallidae</ENT>
                            <ENT>Crake, spotless (American Samoa DPS)</ENT>
                            <ENT>U.S.A. (AS), Australia, Fiji, Independent Samoa, Marquesas, Philippines, Society Islands, Tonga.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Coccyzus americanus</E>
                            </ENT>
                            <ENT>Cuculidae</ENT>
                            <ENT>Cuckoo, yellow-billed (Western U.S. DPS)</ENT>
                            <ENT>U.S.A. (Lower 48 States), Canada, Mexico, Central and South America.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>9</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Gallicolumba stairi</E>
                            </ENT>
                            <ENT>Columbidae</ENT>
                            <ENT>Ground-dove, friendly (American Samoa DPS)</ENT>
                            <ENT>U.S.A. (AS), Independent Samoa.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Eremophila alpestris strigata</E>
                            </ENT>
                            <ENT>Alaudidae</ENT>
                            <ENT>Horned lark, streaked</ENT>
                            <ENT>U.S.A. (OR, WA), Canada (BC).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R5</ENT>
                            <ENT>
                                <E T="03">Calidris canutus rufa</E>
                            </ENT>
                            <ENT>Scolopacidae</ENT>
                            <ENT>Knot, red</ENT>
                            <ENT>U.S.A. (Atlantic coast), Canada, South America.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="66432"/>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R7</ENT>
                            <ENT>
                                <E T="03">Gavia adamsii</E>
                            </ENT>
                            <ENT>Gaviidae</ENT>
                            <ENT>Loon, yellow-billed</ENT>
                            <ENT>U.S.A. (AK), Canada, Norway, Russia, coastal waters of southern Pacific and North Sea.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R7</ENT>
                            <ENT>
                                <E T="03">Brachyramphus brevirostris</E>
                            </ENT>
                            <ENT>Alcidae</ENT>
                            <ENT>Murrelet, Kittlitz's</ENT>
                            <ENT>U.S.A. (AK), Russia.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Synthliboramphus hypoleucus</E>
                            </ENT>
                            <ENT>Alcidae</ENT>
                            <ENT>Murrelet, Xantus's</ENT>
                            <ENT>U.S.A. (CA), Mexico.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Anthus spragueii</E>
                            </ENT>
                            <ENT>Motacillidae</ENT>
                            <ENT>Pipit, Sprauge's</ENT>
                            <ENT>U.S.A. (AL, AR, AZ, CA, GA, LA, MA, MI, MN, MS, MT, ND, OH, OK, SC, SD, TX), Canada, Mexico.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Tympanuchus pallidicinctus</E>
                            </ENT>
                            <ENT>Phasianidae</ENT>
                            <ENT>Prairie-chicken, lesser</ENT>
                            <ENT>U.S.A. (CO, KA, NM, OK, TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Centrocercus urophasianus</E>
                            </ENT>
                            <ENT>Phasianidae</ENT>
                            <ENT>Sage-grouse, greater</ENT>
                            <ENT>U.S.A. (AZ, CA, CO, ID, MT, ND, NE, NV, OR, SD, UT, WA, WY), Canada (AB, BC, SK).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Centrocercus urophasianus</E>
                            </ENT>
                            <ENT>Phasianidae</ENT>
                            <ENT>Sage-grouse, greater (Bi-State DPS)</ENT>
                            <ENT>U.S.A. (AZ, CA, CO, ID, MT, ND, NE, NV, OR, SD, UT, WA, WY), Canada (AB, BC, SK).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>6</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Centrocercus urophasianus</E>
                            </ENT>
                            <ENT>Phasianidae</ENT>
                            <ENT>Sage-grouse, greater (Columbia Basin DPS)</ENT>
                            <ENT>U.S.A. (AZ, CA, CO, ID, MT, ND, NE, NV, OR, SD, UT, WA, WY), Canada (AB, BC, SK).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Centrocercus minimus</E>
                            </ENT>
                            <ENT>Phasianidae</ENT>
                            <ENT>Sage-grouse, Gunnison</ENT>
                            <ENT>U.S.A. (AZ, CO, NM, UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Oceanodroma castro</E>
                            </ENT>
                            <ENT>Hydrobatidae</ENT>
                            <ENT>Storm-petrel, band-rumped (Hawaii DPS)</ENT>
                            <ENT>U.S.A. (HI), Atlantic Ocean, Ecuador (Galapagos Islands), Japan.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">C*</ENT>
                            <ENT>11</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Dendroica angelae</E>
                            </ENT>
                            <ENT>Emberizidae</ENT>
                            <ENT>Warbler, elfin-woods</ENT>
                            <ENT>U.S.A. (PR).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">REPTILES</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Thamnophis eques megalops</E>
                            </ENT>
                            <ENT>Colubridae</ENT>
                            <ENT>Gartersnake, northern Mexican</ENT>
                            <ENT>U.S.A. (AZ, NM, NV), Mexico.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Sceloporus arenicolus</E>
                            </ENT>
                            <ENT>Iguanidae</ENT>
                            <ENT>Lizard, sand dune</ENT>
                            <ENT>U.S.A. (TX, NM).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R3</ENT>
                            <ENT>
                                <E T="03">Sistrurus catenatus</E>
                            </ENT>
                            <ENT>Viperidae</ENT>
                            <ENT>Massasauga (= rattlesnake), eastern</ENT>
                            <ENT>U.S.A. (IA, IL, IN, MI, MN, MO, NY, OH, PA, WI), Canada.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pituophis melanoleucus lodingi</E>
                            </ENT>
                            <ENT>Colubridae</ENT>
                            <ENT>Snake, black pine</ENT>
                            <ENT>U.S.A. (AL, LA, MS).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pituophis ruthveni</E>
                            </ENT>
                            <ENT>Colubridae</ENT>
                            <ENT>Snake, Louisiana pine</ENT>
                            <ENT>U.S.A. (LA, TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Chionactis occipitalis klauberi</E>
                            </ENT>
                            <ENT>Colubridae</ENT>
                            <ENT>Snake, Tucson shovel-nosed</ENT>
                            <ENT>U.S.A. (AZ).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>6</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Gopherus agassizii</E>
                            </ENT>
                            <ENT>Testudinidae</ENT>
                            <ENT>Tortoise, desert (Sonoran DPS)</ENT>
                            <ENT>U.S.A. (AZ, CA, NV, UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Gopherus polyphemus</E>
                            </ENT>
                            <ENT>Testudinidae</ENT>
                            <ENT>Tortoise, gopher (eastern population)</ENT>
                            <ENT>U.S.A. (AL, FL, GA, LA, MS, SC).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Kinosternon sonoriense longifemorale</E>
                            </ENT>
                            <ENT>Kinosternidae</ENT>
                            <ENT>Turtle, Sonoyta mud</ENT>
                            <ENT>U.S.A. (AZ), Mexico.</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">AMPHIBIANS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C*</ENT>
                            <ENT>9</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Rana luteiventris</E>
                            </ENT>
                            <ENT>Ranidae</ENT>
                            <ENT>Frog, Columbia spotted (Great Basin DPS)</ENT>
                            <ENT>U.S.A. (AK, ID, MT, NV, OR, UT, WA, WY), Canada (BC).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Rana muscosa</E>
                            </ENT>
                            <ENT>Ranidae</ENT>
                            <ENT>Frog, mountain yellow-legged (Sierra Nevada DPS)</ENT>
                            <ENT>U.S.A (CA, NV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Rana pretiosa</E>
                            </ENT>
                            <ENT>Ranidae</ENT>
                            <ENT>Frog, Oregon spotted</ENT>
                            <ENT>U.S.A. (CA, OR, WA), Canada (BC).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Lithobates onca</E>
                            </ENT>
                            <ENT>Ranidae</ENT>
                            <ENT>Frog, relict leopard</ENT>
                            <ENT>U.S.A. (AZ, NV, UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>3</ENT>
                            <ENT>R3</ENT>
                            <ENT>
                                <E T="03">Cryptobranchus alleganiensis bishopi</E>
                            </ENT>
                            <ENT>Crytobranchidae</ENT>
                            <ENT>Hellbender, Ozark</ENT>
                            <ENT>U.S.A. (AR, MO).</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="66433"/>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Notophthalmus perstriatus</E>
                            </ENT>
                            <ENT>Salamandridae</ENT>
                            <ENT>Newt, striped</ENT>
                            <ENT>U.S.A. (FL, GA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Eurycea waterlooensis</E>
                            </ENT>
                            <ENT>Plethodontidae</ENT>
                            <ENT>Salamander, Austin blind</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Gyrinophilus gulolineatus</E>
                            </ENT>
                            <ENT>Plethodontidae</ENT>
                            <ENT>Salamander, Berry Cave</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Eurycea naufragia</E>
                            </ENT>
                            <ENT>Plethodontidae</ENT>
                            <ENT>Salamander, Georgetown</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Plethodon neomexicanus</E>
                            </ENT>
                            <ENT>Plethodontidae</ENT>
                            <ENT>Salamander, Jemez Mountains</ENT>
                            <ENT>U.S. A. (NM).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Eurycea tonkawae</E>
                            </ENT>
                            <ENT>Plethodontidae</ENT>
                            <ENT>Salamander, Jollyville Plateau</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Eurycea chisholmensis</E>
                            </ENT>
                            <ENT>Plethodontidae</ENT>
                            <ENT>Salamander, Salado</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>11</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Anaxyrus canorus</E>
                            </ENT>
                            <ENT>Bufonidae</ENT>
                            <ENT>Toad, Yosemite</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>3</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Hyla wrightorum</E>
                            </ENT>
                            <ENT>Hylidae</ENT>
                            <ENT>Treefrog, Arizona (Huachuca/Canelo DPS)</ENT>
                            <ENT>U.S.A. (AZ), Mexico (Sonora).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Necturus alabamensis</E>
                            </ENT>
                            <ENT>Proteidae</ENT>
                            <ENT>Waterdog, black warrior (=Sipsey Fork)</ENT>
                            <ENT>U.S.A. (AL).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">FISHES</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Gila nigra</E>
                            </ENT>
                            <ENT>Cyprinidae</ENT>
                            <ENT>Chub, headwater</ENT>
                            <ENT>U.S.A. (AZ, NM).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>7</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Iotichthys phlegethontis</E>
                            </ENT>
                            <ENT>Cyprinidae</ENT>
                            <ENT>Chub, least</ENT>
                            <ENT>U.S.A. (UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>9</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Gila robusta</E>
                            </ENT>
                            <ENT>Cyprinidae</ENT>
                            <ENT>Chub, roundtail (Lower Colorado River Basin DPS)</ENT>
                            <ENT>U.S.A. (AZ, CO, NM, UT, WY).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>11</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Etheostoma cragini</E>
                            </ENT>
                            <ENT>Percidae</ENT>
                            <ENT>Darter, Arkansas</ENT>
                            <ENT>U.S.A. (AR, CO, KS, MO, OK).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R5</ENT>
                            <ENT>
                                <E T="03">Crystallaria cincotta</E>
                            </ENT>
                            <ENT>Percidae</ENT>
                            <ENT>Darter, diamond</ENT>
                            <ENT>U.S.A. (KY, OH, TN, WV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>3</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Etheostoma sagitta spilotum</E>
                            </ENT>
                            <ENT>Percidae</ENT>
                            <ENT>Darter, Kentucky arrow</ENT>
                            <ENT>U.S.A. (KY).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Percina aurora</E>
                            </ENT>
                            <ENT>Percidae</ENT>
                            <ENT>Darter, Pearl</ENT>
                            <ENT>U.S.A. (LA, MS).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Thymallus arcticus</E>
                            </ENT>
                            <ENT>Salmonidae</ENT>
                            <ENT>Grayling, Arctic (upper Missouri River DPS)</ENT>
                            <ENT>U.S.A. (AK, MI, MT, WY), Canada, northern Asia, northern Europe.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Moxostoma sp.</E>
                            </ENT>
                            <ENT>Catostomidae</ENT>
                            <ENT>Redhorse, sicklefin</ENT>
                            <ENT>U.S.A. (GA, NC, TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R3</ENT>
                            <ENT>
                                <E T="03">Cottus sp.</E>
                            </ENT>
                            <ENT>Cottidae</ENT>
                            <ENT>Sculpin, grotto</ENT>
                            <ENT>U.S.A. (MO).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Notropis oxyrhynchus</E>
                            </ENT>
                            <ENT>Cyprinidae</ENT>
                            <ENT>Shiner, sharpnose</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Notropis buccula</E>
                            </ENT>
                            <ENT>Cyprinidae</ENT>
                            <ENT>Shiner, smalleye</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Catostomus discobolus yarrowi</E>
                            </ENT>
                            <ENT>Catostomidae</ENT>
                            <ENT>Sucker, Zuni bluehead</ENT>
                            <ENT>U.S.A. (AZ, NM).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PSAT</ENT>
                            <ENT>N/A</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Salvelinus malma</E>
                            </ENT>
                            <ENT>Salmonidae</ENT>
                            <ENT>Trout, Dolly Varden</ENT>
                            <ENT>U.S.A. (AK, WA), Canada, East Asia.</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">C*</ENT>
                            <ENT>9</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Oncorhynchus clarki virginalis</E>
                            </ENT>
                            <ENT>Salmonidae</ENT>
                            <ENT>Trout, Rio Grande cutthroat</ENT>
                            <ENT>U.S.A. (CO, NM).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">CLAMS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">PE</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Villosa choctawensis</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Bean, Choctaw</ENT>
                            <ENT>U.S.A. (AL, FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R3</ENT>
                            <ENT>
                                <E T="03">Villosa fabalis</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Bean, rayed</ENT>
                            <ENT>U.S.A. (IL, IN, KY, MI, NY, OH, TN, PA, VA, WV), Canada (ON).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Fusconaia rotulata</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Ebonyshell, round</ENT>
                            <ENT>U.S.A. (AL, FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Popenaias popei</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Hornshell, Texas</ENT>
                            <ENT>U.S.A. (NM, TX), Mexico.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Ptychobranchus subtentum</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Kidneyshell, fluted</ENT>
                            <ENT>U.S.A. (AL, KY, TN, VA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Ptychobranchus jonesi</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Kidneyshell, southern</ENT>
                            <ENT>U.S.A. (AL, FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Lampsilis rafinesqueana</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Mucket, Neosho</ENT>
                            <ENT>U.S.A. (AR, KS, MO, OK).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R3</ENT>
                            <ENT>
                                <E T="03">Plethobasus cyphyus</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Mussel, sheepnose</ENT>
                            <ENT>U.S.A. (AL, IA, IL, IN, KY, MN, MO, MS, OH, PA, TN, VA, WI, WV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Margaritifera marrianae</E>
                            </ENT>
                            <ENT>Margaritiferidae</ENT>
                            <ENT>Pearlshell, Alabama</ENT>
                            <ENT>U.S.A. (AL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Lexingtonia dolabelloides</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Pearlymussel, slabside</ENT>
                            <ENT>U.S.A. (AL, KY, TN, VA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PT</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pleurobema strodeanum</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Pigtoe, fuzzy</ENT>
                            <ENT>U.S.A. (AL, FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PT</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Fusconaia escambia</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Pigtoe, narrow</ENT>
                            <ENT>U.S.A. (AL, FL).</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="66434"/>
                            <ENT I="01">PT</ENT>
                            <ENT>11</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Fusconaia (=Quincuncina) burkei</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Pigtoe, tapered</ENT>
                            <ENT>U.S.A. (AL, FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>9</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Quadrula cylindrica cylindrica</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Rabbitsfoot</ENT>
                            <ENT>U.S.A. (AL, AR, GA, IN, IL, KS, KY, LA, MS, MO, OK, OH, PA, TN, WV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Hamiota (=Lampsilis) australis</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Sandshell, southern</ENT>
                            <ENT>U.S.A. (AL, FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R3</ENT>
                            <ENT>
                                <E T="03">Epioblasma triquetra</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Snuffbox</ENT>
                            <ENT>U.S.A. (IN, MI, NY, OH, PA, WV), Canada (ON).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>4</ENT>
                            <ENT>R3</ENT>
                            <ENT>
                                <E T="03">Cumberlandia monodonta</E>
                            </ENT>
                            <ENT>Margaritiferidae</ENT>
                            <ENT>Spectaclecase</ENT>
                            <ENT>U.S.A. (AL, AR, IA, IN, IL, KS, KY, MO, MN, NE, OH, TN, VA, WI, WV).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Elliptio spinosa</E>
                            </ENT>
                            <ENT>Unionidae</ENT>
                            <ENT>Spinymussel, Altamaha</ENT>
                            <ENT>U.S.A. (GA).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">SNAILS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Elimia melanoides</E>
                            </ENT>
                            <ENT>Pleuroceridae</ENT>
                            <ENT>Mudalia, black</ENT>
                            <ENT>U.S.A. (AL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Planorbella magnifica</E>
                            </ENT>
                            <ENT>Planorbidae</ENT>
                            <ENT>Ramshorn, magnificent</ENT>
                            <ENT>U.S.A. (NC).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Ostodes strigatus</E>
                            </ENT>
                            <ENT>Potaridae</ENT>
                            <ENT>Sisi snail</ENT>
                            <ENT>U.S.A. (AS).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Pseudotryonia adamantina</E>
                            </ENT>
                            <ENT>Hydrobiidae</ENT>
                            <ENT>Snail, Diamond Y Spring</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Samoana fragilis</E>
                            </ENT>
                            <ENT>Partulidae</ENT>
                            <ENT>Snail, fragile tree</ENT>
                            <ENT>U.S.A. (GU, MP).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Partula radiolata</E>
                            </ENT>
                            <ENT>Partulidae</ENT>
                            <ENT>Snail, Guam tree</ENT>
                            <ENT>U.S.A. (GU).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Partula gibba</E>
                            </ENT>
                            <ENT>Partulidae</ENT>
                            <ENT>Snail, Humped tree</ENT>
                            <ENT>U.S.A. (GU, MP).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Partulina semicarinata</E>
                            </ENT>
                            <ENT>Achatinellidae</ENT>
                            <ENT>Snail, Lanai tree</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Partulina variabilis</E>
                            </ENT>
                            <ENT>Achatinellidae</ENT>
                            <ENT>Snail, Lanai tree</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Partula langfordi</E>
                            </ENT>
                            <ENT>Partulidae</ENT>
                            <ENT>Snail, Langford's tree</ENT>
                            <ENT>U.S.A. (MP).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Cochliopa texana</E>
                            </ENT>
                            <ENT>Hydrobiidae</ENT>
                            <ENT>Snail, Phantom cave</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Newcombia cumingi</E>
                            </ENT>
                            <ENT>Achatinellidae</ENT>
                            <ENT>Snail, Newcomb's tree</ENT>
                            <ENT>U.S.A. (Hl).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Eua zebrina</E>
                            </ENT>
                            <ENT>Partulidae</ENT>
                            <ENT>Snail, Tutuila tree</ENT>
                            <ENT>U.S.A. (AS).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Pyrgulopsis chupaderae</E>
                            </ENT>
                            <ENT>Hydrobiidae</ENT>
                            <ENT>Springsnail, Chupadera</ENT>
                            <ENT>U.S.A. (NM).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>11</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Pyrgulopsis notidicola</E>
                            </ENT>
                            <ENT>Hydrobiidae</ENT>
                            <ENT>Springsnail, elongate mud meadows</ENT>
                            <ENT>U.S.A. (NV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Tryonia circumstriata (=stocktonensis)</E>
                            </ENT>
                            <ENT>Hydrobiidae</ENT>
                            <ENT>Springsnail, Gonzales</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>11</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Pyrgulopsis thompsoni</E>
                            </ENT>
                            <ENT>Hydrobiidae</ENT>
                            <ENT>Springsnail, Huachuca</ENT>
                            <ENT>U.S.A. (AZ), Mexico.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Pyrgulopsis morrisoni</E>
                            </ENT>
                            <ENT>Hydrobiidae</ENT>
                            <ENT>Springsnail, Page</ENT>
                            <ENT>U.S.A. (AZ).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Tryonia cheatumi</E>
                            </ENT>
                            <ENT>Hydrobiidae</ENT>
                            <ENT>Springsnail (=Tryonia), Phantom</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Pyrgulopsis bernardina</E>
                            </ENT>
                            <ENT>Hydrobiidae</ENT>
                            <ENT>Springsnail, San Bernardino</ENT>
                            <ENT>U.S.A. (AZ), Mexico (Sonora).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Pyrgulopsis trivialis</E>
                            </ENT>
                            <ENT>Hydrobiidae</ENT>
                            <ENT>Springsnail, Three Forks</ENT>
                            <ENT>U.S.A. (AZ).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Sonorella rosemontensis</E>
                            </ENT>
                            <ENT>Helminthoglyptidae</ENT>
                            <ENT>Talussnail, Rosemont</ENT>
                            <ENT>U.S.A. (AZ).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">INSECTS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hylaeus anthracinus</E>
                            </ENT>
                            <ENT>Colletidae</ENT>
                            <ENT>Bee, Hawaiian yellow-faced</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hylaeus assimulans</E>
                            </ENT>
                            <ENT>Colletidae</ENT>
                            <ENT>Bee, Hawaiian yellow-faced</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hylaeus facilis</E>
                            </ENT>
                            <ENT>Colletidae</ENT>
                            <ENT>Bee, Hawaiian yellow-faced</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hylaeus hilaris</E>
                            </ENT>
                            <ENT>Colletidae</ENT>
                            <ENT>Bee, Hawaiian yellow-faced</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hylaeus kuakea</E>
                            </ENT>
                            <ENT>Colletidae</ENT>
                            <ENT>Bee, Hawaiian yellow-faced</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hylaeus longiceps</E>
                            </ENT>
                            <ENT>Colletidae</ENT>
                            <ENT>Bee, Hawaiian yellow-faced</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hylaeus mana</E>
                            </ENT>
                            <ENT>Colletidae</ENT>
                            <ENT>Bee, Hawaiian yellow-faced</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Plebejus shasta charlestonensis</E>
                            </ENT>
                            <ENT>Lycaenidae</ENT>
                            <ENT>Blue, Mt. Charleston</ENT>
                            <ENT>U.S.A. (NV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>3</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Strymon acis bartrami</E>
                            </ENT>
                            <ENT>Lycaenidae</ENT>
                            <ENT>Butterfly, Bartram's hairstreak</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="66435"/>
                            <ENT I="01">PSAT</ENT>
                            <ENT/>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Leptotes cassius theonus</E>
                            </ENT>
                            <ENT>Lycaenidae</ENT>
                            <ENT>Butterfly, cassius blue</ENT>
                            <ENT>U.S.A. (FL), Bahamas, Greater Antilles, Cayman Islands.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PSAT</ENT>
                            <ENT/>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Hemiargus ceraunus antibubastus</E>
                            </ENT>
                            <ENT>Lycaenidae</ENT>
                            <ENT>Butterfly, ceraunus blue</ENT>
                            <ENT>U.S.A. (FL), Bahamas.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>3</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Anaea troglodyta floridalis</E>
                            </ENT>
                            <ENT>Nymphalidae</ENT>
                            <ENT>Butterfly, Florida leafwing</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hypolimnas octucula mariannensis</E>
                            </ENT>
                            <ENT>Nymphalidae</ENT>
                            <ENT>Butterfly, Mariana eight-spot</ENT>
                            <ENT>U.S.A. (GU, MP).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Vagrans egistina</E>
                            </ENT>
                            <ENT>Nymphalidae</ENT>
                            <ENT>Butterfly, Mariana wandering</ENT>
                            <ENT>U.S.A. (GU, MP).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>3</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Cyclargus thomasi bethunebakeri</E>
                            </ENT>
                            <ENT>Lycaenidae</ENT>
                            <ENT>Butterfly, Miami blue</ENT>
                            <ENT>U.S.A. (FL), Bahamas.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PSAT</ENT>
                            <ENT/>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Cyclargus ammon</E>
                            </ENT>
                            <ENT>Lycaenidae</ENT>
                            <ENT>Butterfly, Nickerbean blue</ENT>
                            <ENT>U.S.A. (FL), Bahamas, Cuba.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Atlantea tulita</E>
                            </ENT>
                            <ENT>Nymphalidae</ENT>
                            <ENT>Butterfly, Puerto Rican harlequin</ENT>
                            <ENT>U.S.A. (PR).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Glyphopsyche sequatchie</E>
                            </ENT>
                            <ENT>Limnephilidae</ENT>
                            <ENT>Caddisfly, Sequatchie</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus insularis</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, Baker Station (=insular)</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus caecus</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, Clifton</ENT>
                            <ENT>U.S.A. (KY).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>11</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus colemanensis</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, Coleman</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus fowlerae</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, Fowler's</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus frigidus</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, icebox</ENT>
                            <ENT>U.S.A. (KY).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus tiresias</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, Indian Grave Point (=Soothsayer)</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus inquisitor</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, inquirer</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus troglodytes</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, Louisville</ENT>
                            <ENT>U.S.A. (KY).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus paulus</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, Noblett's</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Pseudanophthalmus parvus</E>
                            </ENT>
                            <ENT>Carabidae</ENT>
                            <ENT>Cave beetle, Tatum</ENT>
                            <ENT>U.S.A. (KY).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Euphydryas editha taylori</E>
                            </ENT>
                            <ENT>Nymphalidae</ENT>
                            <ENT>Checkerspot butterfly, Taylor's (=Whulge)</ENT>
                            <ENT>U.S.A. (OR, WA), Canada (BC).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Hermelycaena [Lycaena] hermes</E>
                            </ENT>
                            <ENT>Lycaenidae</ENT>
                            <ENT>Copper, Hermes</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>9</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Megalagrion nigrohamatum nigrolineatum</E>
                            </ENT>
                            <ENT>Coenagrionidae</ENT>
                            <ENT>Damselfly, blackline Hawaiian</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Megalagrion leptodemas</E>
                            </ENT>
                            <ENT>Coenagrionidae</ENT>
                            <ENT>Damselfly, crimson Hawaiian</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Megalagrion oceanicum</E>
                            </ENT>
                            <ENT>Coenagrionidae</ENT>
                            <ENT>Damselfly, oceanic Hawaiian</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Megalagrion xanthomelas</E>
                            </ENT>
                            <ENT>Coenagrionidae</ENT>
                            <ENT>Damselfly, orangeblack Hawaiian</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>5</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Ambrysus funebris</E>
                            </ENT>
                            <ENT>Naucoridae</ENT>
                            <ENT>Naucorid bug (=Furnace Creek), Nevares Spring</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Drosophila digressa</E>
                            </ENT>
                            <ENT>Drosophilidae</ENT>
                            <ENT>fly, Hawaiian Picture-wing</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Heterelmis stephani</E>
                            </ENT>
                            <ENT>Elmidae</ENT>
                            <ENT>Riffle beetle, Stephan's</ENT>
                            <ENT>U.S.A. (AZ).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R3</ENT>
                            <ENT>
                                <E T="03">Hesperia dacotae</E>
                            </ENT>
                            <ENT>Hesperiidae</ENT>
                            <ENT>Skipper, Dakota</ENT>
                            <ENT>U.S.A. (MN, IA, SD, ND, IL), Canada.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Polites mardon</E>
                            </ENT>
                            <ENT>Hesperiidae</ENT>
                            <ENT>Skipper, Mardon</ENT>
                            <ENT>U.S.A. (CA, OR, WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R3</ENT>
                            <ENT>
                                <E T="03">Oarisma poweshiek</E>
                            </ENT>
                            <ENT>Hesperiidae</ENT>
                            <ENT>Skipperling, Poweshiek</ENT>
                            <ENT>U.S.A. (IA, IL, IN, MI, MN, ND, SD, WI), Canada (MB).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Lednia tumana</E>
                            </ENT>
                            <ENT>Nemouridae</ENT>
                            <ENT>Stonefly, melwater lednian</ENT>
                            <ENT>U.S.A. (MT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Cicindela albissima</E>
                            </ENT>
                            <ENT>Cicindelidae</ENT>
                            <ENT>Tiger beetle, Coral Pink Sand Dunes</ENT>
                            <ENT>U.S.A. (UT).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <PRTPAGE P="66436"/>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Cicindela highlandensis</E>
                            </ENT>
                            <ENT>Cicindelidae</ENT>
                            <ENT>Tiger beetle, highlands</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">ARACHNIDS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Cicurina wartoni</E>
                            </ENT>
                            <ENT>Dictynidae</ENT>
                            <ENT>Meshweaver, Warton's cave</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">CRUSTACEANS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Gammarus hyalleloides</E>
                            </ENT>
                            <ENT>Gammaridae</ENT>
                            <ENT>Amphipod, diminutive</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>8</ENT>
                            <ENT>R5</ENT>
                            <ENT>
                                <E T="03">Stygobromus kenki</E>
                            </ENT>
                            <ENT>Crangonyctidae</ENT>
                            <ENT>Amphipod, Kenk's</ENT>
                            <ENT>U.S.A. (DC).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Metabetaeus lohena</E>
                            </ENT>
                            <ENT>Alpheidae</ENT>
                            <ENT>Shrimp, anchialine pool</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Palaemonella burnsi</E>
                            </ENT>
                            <ENT>Palaemonidae</ENT>
                            <ENT>Shrimp, anchialine pool</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Procaris hawaiana</E>
                            </ENT>
                            <ENT>Procarididae</ENT>
                            <ENT>Shrimp, anchialine pool</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">C*</ENT>
                            <ENT>4</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Vetericaris chaceorum</E>
                            </ENT>
                            <ENT>Procaridae</ENT>
                            <ENT>Shrimp, anchialine pool</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">FLOWERING PLANTS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C*</ENT>
                            <ENT>11</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Abronia alpina</E>
                            </ENT>
                            <ENT>Nyctaginaceae</ENT>
                            <ENT>Sand-verbena, Ramshaw Meadows</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Agave eggersiana</E>
                            </ENT>
                            <ENT>Agavaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (VI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Arabis georgiana</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Rockcress, Georgia</ENT>
                            <ENT>U.S.A. (AL, GA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Arctostaphylos franciscana</E>
                            </ENT>
                            <ENT>Ericaceae</ENT>
                            <ENT>Manzanita, Franciscan</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>11</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Argythamnia blodgettii</E>
                            </ENT>
                            <ENT>Euphorbiaceae</ENT>
                            <ENT>Silverbush, Blodgett's</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Artemisia borealis var. wormskioldii</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Wormwood, northern</ENT>
                            <ENT>U.S.A. (OR, WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Astragalus anserinus</E>
                            </ENT>
                            <ENT>Fabaceae</ENT>
                            <ENT>Milkvetch, Goose Creek</ENT>
                            <ENT>U.S.A. (ID, NV, UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Astragalus cusickii var. packardiae</E>
                            </ENT>
                            <ENT>Fabaceae</ENT>
                            <ENT>Milkvetch, Packard's</ENT>
                            <ENT>U.S.A. (ID).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Astragalus microcymbus</E>
                            </ENT>
                            <ENT>Fabaceae</ENT>
                            <ENT>Milkvetch, skiff</ENT>
                            <ENT>U.S.A. (CO).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Astragalus schmolliae</E>
                            </ENT>
                            <ENT>Fabaceae</ENT>
                            <ENT>Milkvetch, Schmoll</ENT>
                            <ENT>U.S.A. (CO).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>11</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Astragalus tortipes</E>
                            </ENT>
                            <ENT>Fabaceae</ENT>
                            <ENT>Milkvetch, Sleeping Ute</ENT>
                            <ENT>U.S.A. (CO).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Bidens amplectens</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Ko`oko`olau</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Bidens campylotheca pentamera</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Ko`oko`olau</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Bidens campylotheca waihoiensis</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Ko`oko`olau</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Bidens conjuncta</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Ko`oko`olau</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Bidens micrantha ctenophylla</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Ko`oko`olau</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Boechera (Arabis) pusilla</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Rockcress, Fremont County or small</ENT>
                            <ENT>U.S.A. (WY).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Brickellia mosieri</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Brickell-bush, Florida</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Calamagrostis expansa</E>
                            </ENT>
                            <ENT>Poaceae</ENT>
                            <ENT>Reedgrass, Maui</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Calamagrostis hillebrandii</E>
                            </ENT>
                            <ENT>Poaceae</ENT>
                            <ENT>Reedgrass, Hillebrand's</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Calochortus persistens</E>
                            </ENT>
                            <ENT>Liliaceae</ENT>
                            <ENT>Mariposa lily, Siskiyou</ENT>
                            <ENT>U.S.A. (CA, OR).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Canavalia pubescens</E>
                            </ENT>
                            <ENT>Fabaceae</ENT>
                            <ENT>`Awikiwiki</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Castilleja christii</E>
                            </ENT>
                            <ENT>Scrophulariaceae</ENT>
                            <ENT>Paintbrush, Christ's</ENT>
                            <ENT>U.S.A. (ID).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>9</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Chamaecrista lineata var. keyensis</E>
                            </ENT>
                            <ENT>Fabaceae</ENT>
                            <ENT>Pea, Big Pine partridge</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>12</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Chamaesyce deltoidea pinetorum</E>
                            </ENT>
                            <ENT>Euphorbiaceae</ENT>
                            <ENT>Sandmat, pineland</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>9</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Chamaesyce deltoidea serpyllum</E>
                            </ENT>
                            <ENT>Euphorbiaceae</ENT>
                            <ENT>Spurge, wedge</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>6</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Chorizanthe parryi var. fernandina</E>
                            </ENT>
                            <ENT>Polygonaceae</ENT>
                            <ENT>Spineflower, San Fernando Valley</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Chromolaena frustrata</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Thoroughwort, Cape Sable</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Cirsium wrightii</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Thistle, Wright's</ENT>
                            <ENT>U.S.A. (AZ, NM), Mexico.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Consolea corallicola</E>
                            </ENT>
                            <ENT>Cactaceae</ENT>
                            <ENT>Cactus, Florida semaphore</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Cordia rupicola</E>
                            </ENT>
                            <ENT>Boraginaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (PR), Anegada.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyanea asplenifolia</E>
                            </ENT>
                            <ENT>Campanulaceae</ENT>
                            <ENT>Haha</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyanea calycina</E>
                            </ENT>
                            <ENT>Campanulaceae</ENT>
                            <ENT>Haha</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyanea kunthiana</E>
                            </ENT>
                            <ENT>Campanulaceae</ENT>
                            <ENT>Haha</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyanea lanceolata</E>
                            </ENT>
                            <ENT>Campanulaceae</ENT>
                            <ENT>Haha</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="66437"/>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyanea obtusa</E>
                            </ENT>
                            <ENT>Campanulaceae</ENT>
                            <ENT>Haha</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyanea purpurellifolia</E>
                            </ENT>
                            <ENT>Campanulaceae</ENT>
                            <ENT>Haha</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyanea tritomantha</E>
                            </ENT>
                            <ENT>Campanulaceae</ENT>
                            <ENT>`Aku</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyrtandra filipes</E>
                            </ENT>
                            <ENT>Gesneriaceae</ENT>
                            <ENT>Ha`iwale</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyrtandra gracilis</E>
                            </ENT>
                            <ENT>Gesneriaceae</ENT>
                            <ENT>Ha`iwale</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyrtandra kaulantha</E>
                            </ENT>
                            <ENT>Gesneriaceae</ENT>
                            <ENT>Ha`iwale</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyrtandra oxybapha</E>
                            </ENT>
                            <ENT>Gesneriaceae</ENT>
                            <ENT>Ha`iwale</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyrtandra sessilis</E>
                            </ENT>
                            <ENT>Gesneriaceae</ENT>
                            <ENT>Ha`iwale</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyrtandra waiolani</E>
                            </ENT>
                            <ENT>Gesneriaceae</ENT>
                            <ENT>Ha`iwale</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Dalea carthagenensis var. floridana</E>
                            </ENT>
                            <ENT>Fabaceae</ENT>
                            <ENT>Prairie-clover, Florida</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R5</ENT>
                            <ENT>
                                <E T="03">Dichanthelium hirstii</E>
                            </ENT>
                            <ENT>Poaceae</ENT>
                            <ENT>Panic grass, Hirst Brothers'</ENT>
                            <ENT>U.S.A. (DE, GA, NC, NJ).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Digitaria pauciflora</E>
                            </ENT>
                            <ENT>Poaceae</ENT>
                            <ENT>Crabgrass, Florida pineland</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Echinomastus erectocentrus var. acunensis</E>
                            </ENT>
                            <ENT>Cactaceae</ENT>
                            <ENT>Cactus, Acuna</ENT>
                            <ENT>U.S.A. (AZ), Mexico.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Erigeron lemmonii</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Fleabane, Lemmon</ENT>
                            <ENT>U.S.A. (AZ).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Eriogonum codium</E>
                            </ENT>
                            <ENT>Polygonaceae</ENT>
                            <ENT>Buckwheat, Umtanum Desert</ENT>
                            <ENT>U.S.A. (WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>6</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Eriogonum corymbosum var. nilesii</E>
                            </ENT>
                            <ENT>Polygonaceae</ENT>
                            <ENT>Buckwheat, Las Vegas</ENT>
                            <ENT>U.S.A. (NV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>5</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Eriogonum diatomaceum</E>
                            </ENT>
                            <ENT>Polygonaceae</ENT>
                            <ENT>Buckwheat, Churchill Narrows</ENT>
                            <ENT>U.S.A (NV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Eriogonum kelloggii</E>
                            </ENT>
                            <ENT>Polygonaceae</ENT>
                            <ENT>Buckwheat, Red Mountain</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Eriogonum soredium</E>
                            </ENT>
                            <ENT>Polygonaceae</ENT>
                            <ENT>Buckwheat, Frisco</ENT>
                            <ENT>U.S.A. (UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Festuca hawaiiensis</E>
                            </ENT>
                            <ENT>Poaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>11</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Festuca ligulata</E>
                            </ENT>
                            <ENT>Poaceae</ENT>
                            <ENT>Fescue, Guadalupe</ENT>
                            <ENT>U.S.A. (TX), Mexico.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Gardenia remyi</E>
                            </ENT>
                            <ENT>Rubiaceae</ENT>
                            <ENT>Nanu</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Geranium hanaense</E>
                            </ENT>
                            <ENT>Geraniaceae</ENT>
                            <ENT>Nohoanu</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Geranium hillebrandii</E>
                            </ENT>
                            <ENT>Geraniaceae</ENT>
                            <ENT>Nohoanu</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Gonocalyx concolor</E>
                            </ENT>
                            <ENT>Ericaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (PR).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Harrisia aboriginum</E>
                            </ENT>
                            <ENT>Cactaceae</ENT>
                            <ENT>Pricklyapple, aboriginal (shellmound applecactus)</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Hazardia orcuttii</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Orcutt's hazardia</ENT>
                            <ENT>U.S.A. (CA), Mexico.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Hedyotis fluviatilis</E>
                            </ENT>
                            <ENT>Rubiaceae</ENT>
                            <ENT>Kampua`a</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Helianthus verticillatus</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Sunflower, whorled</ENT>
                            <ENT>U.S.A. (AL, GA, TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Hibiscus dasycalyx</E>
                            </ENT>
                            <ENT>Malvaceae</ENT>
                            <ENT>Rose-mallow, Neches River</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Ivesia webberi</E>
                            </ENT>
                            <ENT>Rosaceae</ENT>
                            <ENT>Ivesia, Webber</ENT>
                            <ENT>U.S.A. (CA, NV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Joinvillea ascendens ascendens</E>
                            </ENT>
                            <ENT>Joinvilleaceae</ENT>
                            <ENT>`Ohe</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Korthalsella degeneri</E>
                            </ENT>
                            <ENT>Viscaceae</ENT>
                            <ENT>Hulumoa</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Leavenworthia crassa</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Gladecress, unnamed</ENT>
                            <ENT>U.S.A. (AL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>3</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Leavenworthia exigua var. laciniata</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Gladecress, Kentucky</ENT>
                            <ENT>U.S.A. (KY).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Leavenworthia texana</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Gladecress, Texas golden</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Lepidium ostleri</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Peppergrass, Ostler's</ENT>
                            <ENT>U.S.A. (UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Linum arenicola</E>
                            </ENT>
                            <ENT>Linaceae</ENT>
                            <ENT>Flax, sand</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Linum carteri var. carteri</E>
                            </ENT>
                            <ENT>Linaceae</ENT>
                            <ENT>Flax, Carter's small-flowered</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Melicope christophersenii</E>
                            </ENT>
                            <ENT>Rutaceae</ENT>
                            <ENT>Alani</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Melicope hiiakae</E>
                            </ENT>
                            <ENT>Rutaceae</ENT>
                            <ENT>Alani</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Melicope makahae</E>
                            </ENT>
                            <ENT>Rutaceae</ENT>
                            <ENT>Alani</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>3</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Mimulus fremontii var. vandenbergensis</E>
                            </ENT>
                            <ENT>Phrymaceae</ENT>
                            <ENT>Monkeyflower, Vandenberg</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Myrsine fosbergii</E>
                            </ENT>
                            <ENT>Myrsinaceae</ENT>
                            <ENT>Kolea</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Myrsine vaccinioides</E>
                            </ENT>
                            <ENT>Myrsinaceae</ENT>
                            <ENT>Kolea</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R5</ENT>
                            <ENT>
                                <E T="03">Narthecium americanum</E>
                            </ENT>
                            <ENT>Liliaceae</ENT>
                            <ENT>Asphodel, bog</ENT>
                            <ENT>U.S.A. (DE, NC, NJ, NY, SC).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Nothocestrum latifolium</E>
                            </ENT>
                            <ENT>Solanaceae</ENT>
                            <ENT>`Aiea</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Ochrosia haleakalae</E>
                            </ENT>
                            <ENT>Apocynaceae</ENT>
                            <ENT>Holei</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="66438"/>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Pediocactus peeblesianus var. fickeiseniae</E>
                            </ENT>
                            <ENT>Cactaceae</ENT>
                            <ENT>Cactus, Fickeisen plains</ENT>
                            <ENT>U.S.A. (AZ).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PT</ENT>
                            <ENT>2</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Penstemon grahamii</E>
                            </ENT>
                            <ENT>Scrophulariaceae</ENT>
                            <ENT>Beardtongue, Graham's</ENT>
                            <ENT>U.S.A. (CO, UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>9</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Penstemon scariosus var. albifluvis</E>
                            </ENT>
                            <ENT>Scrophulariaceae</ENT>
                            <ENT>Beardtongue, White River</ENT>
                            <ENT>U.S.A. (CO, UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Peperomia subpetiolata</E>
                            </ENT>
                            <ENT>Piperaceae</ENT>
                            <ENT>`Ala `ala wai nui</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>5</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Phacelia stellaris</E>
                            </ENT>
                            <ENT>Hydrophyllaceae</ENT>
                            <ENT>Phacelia, Brand's</ENT>
                            <ENT>U.S.A. (CA), Mexico.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Phyllostegia bracteata</E>
                            </ENT>
                            <ENT>Lamiaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Phyllostegia floribunda</E>
                            </ENT>
                            <ENT>Lamiaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>9</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Physaria douglasii tuplashensis</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Bladderpod, White Bluffs</ENT>
                            <ENT>U.S.A. (WA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Physaria globosa</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Bladderpod, Short's</ENT>
                            <ENT>U.S.A. (IN, KY, TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Pinus albicaulis</E>
                            </ENT>
                            <ENT>Pinaceae</ENT>
                            <ENT>Pine, whitebark</ENT>
                            <ENT>U.S.A. (CA, ID, MT, NV, OR, WA, WY), Canada (AB, BC).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Platanthera integrilabia</E>
                            </ENT>
                            <ENT>Orchidaceae</ENT>
                            <ENT>Orchid, white fringeless</ENT>
                            <ENT>U.S.A. (AL, GA, KY, MS, NC, SC, TN, VA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Platydesma cornuta var. cornuta</E>
                            </ENT>
                            <ENT>Rutaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Platydesma cornuta var. decurrens</E>
                            </ENT>
                            <ENT>Rutaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Platydesma remyi</E>
                            </ENT>
                            <ENT>Rutaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Pleomele fernaldii</E>
                            </ENT>
                            <ENT>Agavaceae</ENT>
                            <ENT>Hala pepe</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Pleomele forbesii</E>
                            </ENT>
                            <ENT>Agavaceae</ENT>
                            <ENT>Hala pepe</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>11</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Potentilla basaltica</E>
                            </ENT>
                            <ENT>Rosaceae</ENT>
                            <ENT>Cinquefoil, Soldier Meadow</ENT>
                            <ENT>U.S.A. (NV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Pseudognaphalium (=Gnaphalium) sandwicensium var. molokaiense</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>`Ena`ena</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Psychotria hexandra oahuensis</E>
                            </ENT>
                            <ENT>Rubiaceae</ENT>
                            <ENT>Kopiko</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Pteralyxia macrocarpa</E>
                            </ENT>
                            <ENT>Apocynaceae</ENT>
                            <ENT>Kaulu</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Ranunculus hawaiensis</E>
                            </ENT>
                            <ENT>Ranunculaceae</ENT>
                            <ENT>Makou</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Ranunculus mauiensis</E>
                            </ENT>
                            <ENT>Ranunculaceae</ENT>
                            <ENT>Makou</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Rorippa subumbellata</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Cress, Tahoe yellow</ENT>
                            <ENT>U.S.A. (CA, NV).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Schiedea pubescens</E>
                            </ENT>
                            <ENT>Caryophyllaceae</ENT>
                            <ENT>Ma`oli`oli</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Schiedea salicaria</E>
                            </ENT>
                            <ENT>Caryophyllaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>5</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Sedum eastwoodiae</E>
                            </ENT>
                            <ENT>Crassulaceae</ENT>
                            <ENT>Stonecrop, Red Mountain</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Sicyos macrophyllus</E>
                            </ENT>
                            <ENT>Cucurbitaceae</ENT>
                            <ENT>`Anunu</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>12</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Sideroxylon reclinatum austrofloridense</E>
                            </ENT>
                            <ENT>Sapotaceae</ENT>
                            <ENT>Bully, Everglades</ENT>
                            <ENT>U.S.A. (FL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Solanum conocarpum</E>
                            </ENT>
                            <ENT>Solanaceae</ENT>
                            <ENT>Bacora, marron</ENT>
                            <ENT>U.S.A. (PR).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Solanum nelsonii</E>
                            </ENT>
                            <ENT>Solanaceae</ENT>
                            <ENT>Popolo</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Solidago plumosa</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Goldenrod, Yadkin River</ENT>
                            <ENT>U.S.A. (NC).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Sphaeralcea gierischii</E>
                            </ENT>
                            <ENT>Malvaceae</ENT>
                            <ENT>Mallow, Gierisch</ENT>
                            <ENT>U.S.A. (AZ, UT).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Stenogyne cranwelliae</E>
                            </ENT>
                            <ENT>Lamiaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>8</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Streptanthus bracteatus</E>
                            </ENT>
                            <ENT>Brassicaceae</ENT>
                            <ENT>Twistflower, bracted</ENT>
                            <ENT>U.S.A. (TX).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Symphyotrichum georgianum</E>
                            </ENT>
                            <ENT>Asteraceae</ENT>
                            <ENT>Aster, Georgia</ENT>
                            <ENT>U.S.A. (AL, FL, GA, NC, SC).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT/>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Tetraplasandra lydgatei</E>
                            </ENT>
                            <ENT>Araliaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Trifolium friscanum</E>
                            </ENT>
                            <ENT>Fabaceae</ENT>
                            <ENT>Clover, Frisco</ENT>
                            <ENT>U.S.A. (UT).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Zanthoxylum oahuense</E>
                            </ENT>
                            <ENT>Rutaceae</ENT>
                            <ENT>A`e</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">FERNS AND ALLIES</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">C*</ENT>
                            <ENT>8</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Cyclosorus boydiae</E>
                            </ENT>
                            <ENT>Thelypteridaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">PE</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Doryopteris takeuchii</E>
                            </ENT>
                            <ENT>Pteridaceae</ENT>
                            <ENT>No common name</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>2</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Huperzia (= Phlegmariurus) stemmermanniae</E>
                            </ENT>
                            <ENT>Lycopodiaceae</ENT>
                            <ENT>Wawae`iole</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C*</ENT>
                            <ENT>3</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Microlepia strigosa var. mauiensis (= Microlepia mauiensis)</E>
                            </ENT>
                            <ENT>Dennstaedtiaceae</ENT>
                            <ENT>Palapalai</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">C</ENT>
                            <ENT>3</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Trichomanes punctatum floridanum</E>
                            </ENT>
                            <ENT>Hymenophyllaceae</ENT>
                            <ENT>Florida bristle fern</ENT>
                            <ENT>U.S.A. (FL)</ENT>
                        </ROW>
                    </GPOTABLE>
                    <PRTPAGE P="66439"/>
                    <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="xs36,xs36,xs36,r50,r50,r50,r50">
                        <TTITLE>Table 2—Animals and Plants Formerly Candidates or Formerly Proposed for Listing</TTITLE>
                        <TDESC>
                            [Note: See end of 
                            <E T="02">SUPPLEMENTARY INFORMATION</E>
                             for an explanation of symbols used in this table]
                        </TDESC>
                        <BOXHD>
                            <CHED H="1">Status</CHED>
                            <CHED H="2">Code</CHED>
                            <CHED H="2">Expl.</CHED>
                            <CHED H="1">Lead region</CHED>
                            <CHED H="1">Scientific name</CHED>
                            <CHED H="1">Family</CHED>
                            <CHED H="1">Common name</CHED>
                            <CHED H="1">Historical range</CHED>
                        </BOXHD>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">BIRDS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00" RUL="s">
                            <ENT I="01">Rp</ENT>
                            <ENT>A</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Charadrius montanus</E>
                            </ENT>
                            <ENT>Charadriidae</ENT>
                            <ENT>Plover, mountain</ENT>
                            <ENT>U.S.A. (AZ, CA, CO, KS, MT, ND, NE, NM, NV, OK, SD, TX, UT, WY), Canada (AB, SK), Mexico.</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">FISH</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Phoxinus saylori</E>
                            </ENT>
                            <ENT>Cyprinidae</ENT>
                            <ENT>Dace, laurel</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Etheostoma susanae</E>
                            </ENT>
                            <ENT>Percidae</ENT>
                            <ENT>Darter, Cumberland</ENT>
                            <ENT>U.S.A. (KY, TN).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Etheostoma phytophilum</E>
                            </ENT>
                            <ENT>Percidae</ENT>
                            <ENT>Darter, rush</ENT>
                            <ENT>U.S.A. (AL).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Etheostoma moorei</E>
                            </ENT>
                            <ENT>Percidae</ENT>
                            <ENT>Darter, yellowcheek</ENT>
                            <ENT>U.S.A (AR).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Noturus crypticus</E>
                            </ENT>
                            <ENT>Ictaluridae</ENT>
                            <ENT>Madtom, chucky</ENT>
                            <ENT>U.S.A. (TN).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">SNAILS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">Rc</ENT>
                            <ENT>A</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Pyrgulopsis gilae</E>
                            </ENT>
                            <ENT>Hydrobiidae</ENT>
                            <ENT>Springsnail, Gila</ENT>
                            <ENT>U.S.A. (NM).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">Rc</ENT>
                            <ENT>A</ENT>
                            <ENT>R2</ENT>
                            <ENT>
                                <E T="03">Pyrgulopsis thermalis</E>
                            </ENT>
                            <ENT>Hydrobiidae</ENT>
                            <ENT>Springsnail, New Mexico</ENT>
                            <ENT>U.S.A. (NM).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">INSECTS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">T(S/A)</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Leptotes cassius theonus</E>
                            </ENT>
                            <ENT>Lycaenidae</ENT>
                            <ENT>Butterfly, cassius blue</ENT>
                            <ENT>U.S.A. (FL), Bahamas, Greater Antilles, Cayman Islands.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T(S/A)</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Hemiargus ceraunus antibubastus</E>
                            </ENT>
                            <ENT>Lycaenidae</ENT>
                            <ENT>Butterfly, ceraunus blue</ENT>
                            <ENT>U.S.A. (FL), Bahamas.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">E</ENT>
                            <ENT>
                                L 
                                <SU>1</SU>
                            </ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Cyclargus thomasi bethunebakeri</E>
                            </ENT>
                            <ENT>Lycaenidae</ENT>
                            <ENT>Butterfly, Miami blue</ENT>
                            <ENT>U.S.A. (FL), Bahamas.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T(S/A)</ENT>
                            <ENT>L</ENT>
                            <ENT>R4</ENT>
                            <ENT>
                                <E T="03">Cyclargus ammon</E>
                            </ENT>
                            <ENT>Lycaenidae</ENT>
                            <ENT>Butterfly, Nickerbean blue</ENT>
                            <ENT>U.S.A. (FL), Bahamas, Cuba.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rc</ENT>
                            <ENT>A</ENT>
                            <ENT>R1</ENT>
                            <ENT>
                                <E T="03">Nysius wekiuicola</E>
                            </ENT>
                            <ENT>Lygaeidae</ENT>
                            <ENT>Bug, Wekiu</ENT>
                            <ENT>U.S.A. (HI).</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R8</ENT>
                            <ENT>
                                <E T="03">Dinacoma caseyi</E>
                            </ENT>
                            <ENT>Scarabidae</ENT>
                            <ENT>June beetle, Casey's</ENT>
                            <ENT>U.S.A. (CA).</ENT>
                        </ROW>
                        <ROW EXPSTB="06" RUL="s">
                            <ENT I="21">
                                <E T="02">FLOWERING PLANTS</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="01">E</ENT>
                            <ENT>L</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Ipomopsis polyantha</E>
                            </ENT>
                            <ENT>Polemoniaceae</ENT>
                            <ENT>Skyrocket, Pagosa</ENT>
                            <ENT>U.S.A. (CO)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Penstemon debilis</E>
                            </ENT>
                            <ENT>Scrophulariaceae</ENT>
                            <ENT>Beardtongue, Parachute</ENT>
                            <ENT>U.S.A. (CO)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">T</ENT>
                            <ENT>L</ENT>
                            <ENT>R6</ENT>
                            <ENT>
                                <E T="03">Phacelia submutica</E>
                            </ENT>
                            <ENT>Hydrophyllaceae</ENT>
                            <ENT>Phacelia, DeBeque</ENT>
                            <ENT>U.S.A. (CO)</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             Emergency.
                        </TNOTE>
                    </GPOTABLE>
                </SUPLINF>
                <FRDOC>[FR Doc. 2011-27122 Filed 10-25-11; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>76</VOL>
    <NO>207</NO>
    <DATE>Wednesday, October 26, 2011</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="66441"/>
            <PARTNO>Part III</PARTNO>
            <AGENCY TYPE="P">Department of Labor</AGENCY>
            <SUBAGY> Office of Labor-Management Standards</SUBAGY>
            <HRULE/>
            <CFR>29 CFR 404</CFR>
            <TITLE> Labor Organization Officer and Employee Reports; Final Rule</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="66442"/>
                    <AGENCY TYPE="S">DEPARTMENT OF LABOR</AGENCY>
                    <SUBAGY>Office of Labor-Management Standards</SUBAGY>
                    <CFR>29 CFR Part 404</CFR>
                    <RIN>RIN 1215-AB74</RIN>
                    <RIN>RIN 1245-AA01</RIN>
                    <SUBJECT>Labor Organization Officer and Employee Reports</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Office of Labor-Management Standards, Department of Labor.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Final rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>The Office of Labor-Management Standards of the Department of Labor (Department) is revising the Form LM-30 Labor Organization Officer and Employee Report and its instructions upon review of the comments received in response to its August 10, 2010 Notice of Proposed Rulemaking (NRPM). The Form LM-30 implements section 202 of the Labor-Management Reporting and Disclosure Act of 1959 (LMRDA or Act), the purpose of which is to require officers and employees of labor organizations (unions) to publicly disclose possible conflicts between their personal financial interests and their duty to the labor union and its members. The rule revises the Form LM-30 and its instructions, based on an examination of the policy and legal justifications for, and utility of, changes enacted in the Form LM-30 Final Rule (2007 rule), published on July 2, 2007. The principal revisions are: Union leave and no docking payments are not required to be reported on the Form LM-30; union stewards and others representing the union in similar positions are not covered by the Form LM-30 reporting requirements; the requirement to report certain bona fide loans is limited, as is reporting of payments from certain trusts, unions, and employers in competition with employers whose employees are represented by an official's union; and the scope of reporting required of officers and employees of international, national, and intermediate body unions is revised. This rule also establishes a new form and instructions, as well as regulatory text concerning certain reporting obligations. This rule largely implements the Department's proposal in the NPRM, with modifications of several minor aspects of the layout of the form and instructions.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>This rule is effective on November 25, 2011, and it is applicable to Form LM-30 filers with fiscal years beginning on or after January 1, 2012. For filers with fiscal years beginning prior to January 1, 2012, the Department will accept either the Revised Form LM-30 published with this rule, the pre-2007 Form LM-30, or the 2007 Form LM-30.</P>
                    </EFFDATE>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            Andrew R. Davis, Chief of the Division of Interpretations and Standards, Office of Labor-Management Standards, U.S. Department of Labor, 200 Constitution Avenue, NW., Room N-5609, Washington, DC 20210, 
                            <E T="03">olms-public@dol.gov,</E>
                             (202) 693-0123 (this is not a toll-free number), (800) 877-8339 (TTY/TDD).
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>The Regulatory Information Number (RIN) identified for this rulemaking changed with publication of the Spring 2010 Regulatory Agenda due to an organizational restructuring. The old RIN (1215-AB74) was assigned to the Employment Standards Administration, which no longer exists; a new RIN (1245-AA01) has been assigned to the Office of Labor-Management Standards.</P>
                    <HD SOURCE="HD1">I. Background</HD>
                    <HD SOURCE="HD2">A. Introduction</HD>
                    <P>This final rule, which revises the Form LM-30 and its instructions, is part of the Department's ongoing effort to effectively administer the reporting requirements of the LMRDA. The Form LM-30 Labor Organization Officer and Employee Report is designed to provide for the disclosure of payments to, and interests held by, union officers and employees, when such payments and interests pose an actual or potential conflict of interest. In developing the proposed rule and considering and responding to the comments submitted on the proposal, the Department has kept in mind that a fair and transparent reporting system for union officers and employees must consider the interests of unions, their members, and the public, and must balance the benefits served by disclosure with the burden placed on reporting individuals and labor organizations.</P>
                    <P>
                        The Form LM-30 implements section 202 of the LMRDA, 29 U.S.C. 432. Under section 202,
                        <SU>1</SU>
                        <FTREF/>
                         union officers and employees (collectively, union officials) are required to file reports if they, or their spouses or minor children, engage in certain transactions or have financial holdings that may constitute a conflict of interest with their union responsibilities. The Act requires public disclosure of certain financial interests held, transactions engaged in, and income received. Subject to certain exclusions, these interests, transactions, and incomes include:
                    </P>
                    <P>1. Payments or benefits with monetary value from, or interests in, an employer whose employees the filer's union represents or is actively seeking to represent;</P>
                    <P>2. Transactions involving any stock, bond, security, or loan to or from, or other interest in, an employer whose employees the filer's union represents or is actively seeking to represent;</P>
                    <P>3. Income or any other benefit with monetary value from, or other interest in, a business a substantial part of which consists of buying from, selling or leasing to, or otherwise dealing with an employer whose employees the filer's union represents or is actively seeking to represent;</P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             Unless otherwise stated all references to statutory provisions, 
                            <E T="03">e.g.,</E>
                             “section 202,” are to provisions in the LMRDA. 29 U.S.C. 401-531.
                        </P>
                    </FTNT>
                    <P>
                        4. Income or any other benefit with monetary value from, or other interest in, a business any part of which consists of buying from, or selling or leasing directly or indirectly to, or otherwise dealing with the filer's union or a trust in which the filer's union is interested; 
                        <SU>2</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             
                        </P>
                        These trusts are defined by section 3(l) of the Act as:
                        <P>a trust or other fund or organization (1) Which was created or established by a labor organization, or one or more of the trustees or one or more members of the governing body of which is selected or appointed by a labor organization, and (2) a primary purpose of which is to provide benefits for the members of such labor organization or their beneficiaries. </P>
                        <P>Unless otherwise specified, references to “trust” in this preamble are to these statutorily defined trusts, which are sometimes referred to as “section 3(l) trusts.”</P>
                    </FTNT>
                    <P>5. Business transactions or arrangements with an employer whose employees the filer's union represents or is actively seeking to represent; and</P>
                    <P>6. Payment of money or any other thing of value from any employer not covered under the above categories, or payment of money or other thing of value from a person who acts as a labor relations consultant to an employer.</P>
                    <P>
                        The Form LM-30 had remained essentially unchanged from 1963 until 2007. In 2005, the Department published a Notice of Proposed Rulemaking that proposed far-reaching changes to the form. 70 FR 51165 (Aug. 29, 2005). After a notice and comment period, the Department issued the 2007 final rule. 72 FR 36105 (July 2, 2007). The 2007 rule brought significant changes to the LM-30 and its instructions and represented, in some instances, a sharp departure from the Department's previous interpretations of section 202. The rule completely revised the layout and overall structure of the Form LM-30, lengthening the form from two to nine pages with the creation of 
                        <PRTPAGE P="66443"/>
                        five schedules, continuation pages, and various sections consisting of instructions and examples. (The 2007 form and instructions are available at 
                        <E T="03">http://www.dol.gov/olms.</E>
                        )
                    </P>
                    <P>Upon review of the 2007 rule, and input from the regulated community, the Department issued its proposed revisions to that rule on August 10, 2010, stating its view that many of the objectives sought to be met by the 2007 rule—including simplification of the reporting requirements and adherence to the reporting scheme intended by Congress—had not been accomplished. See 75 FR 48416. The Department, at 75 FR 48417, explained that the 2007 rule left unresolved fundamental questions about the reporting obligations of union officials and raised policy and legal issues warranting reexamination by the Department. These fundamental questions regarding the Form LM-30 reporting requirements included—the coverage of stewards and other union representatives serving in similar positions; the reporting of certain loans and union leave and no docking payments; the reporting of payments from certain trusts and unions; the reporting of payments from businesses that compete with an employer whose employees are represented by an official's union or whose employees the union is actively seeking to represent; and reporting by higher level union officials about relationships with businesses and employers that pose conflicts concerning subordinate affiliates of their union. In addition, the Department identified questions concerning the layout of the 2007 Form LM-30 and instructions and whether they provided useful and adequate assistance to filers.</P>
                    <P>
                        Prompted by these uncertainties about the 2007 rule, the Department, on March 19, 2009, issued a non-enforcement policy regarding the 2007 Form LM-30 reporting requirements, allowing filers to use either the pre-2007 or 2007 Form LM-30 report.
                        <SU>3</SU>
                        <FTREF/>
                         Further, the Department held a stakeholder meeting on July 21, 2009 to solicit comments regarding the 2007 rule and potential revisions to the Form LM-30. In the NPRM, the Department invited comment on the proposed changes with respect to their benefits, the ease or difficulty with which union officers and employees would be able to comply with these changes, and whether the changes would better implement the LMRDA. The Department invited general and specific comments on any aspect of this proposal; it also invited comment on specific points, as noted throughout the text of the notice.
                    </P>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             The Department modifies this non-enforcement policy with the publication of today's rule. For filers with reportable payments or interests in fiscal years beginning prior to January 1, 2012, the Department will accept either the Revised Form LM-30 published with this rule, the 2007 Form LM-30, or the pre-2007 Form LM-30. For filers with reportable payments or interests in fiscal years beginning on or after January 1, 2012, the Department will accept only the Revised Form LM-30.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. History of the LMRDA's Reporting Requirements</HD>
                    <P>In enacting the LMRDA in 1959, a bipartisan Congress expressed the conclusion that in the labor and management fields “there have been a number of instances of breach of trust, corruption, disregard of the rights of individual employees, and other failures to observe high standards of responsibility and ethical conduct which require further and supplementary legislation that will afford necessary protection of the rights and interests of employees and the public generally as they relate to the activities of labor organizations, employers, labor relations consultants, and their officers and representatives.” Section 2(b), 29 U.S.C. 401(b).</P>
                    <P>The LMRDA was the direct outgrowth of a Congressional investigation conducted by the Select Committee on Improper Activities in the Labor or Management Field, commonly known as the McClellan Committee. The LMRDA addressed various ills through a set of integrated provisions aimed at labor-management relations governance and management. These provisions include financial reporting and disclosure requirements for labor organizations, their officers and employees, employers, labor relations consultants, and surety companies. See 29 U.S.C. 431-36, 441.</P>
                    <P>To highlight the potential conflicts of interest to which union officers and employees could be susceptible, the Senate Committee Report explained:</P>
                    <EXTRACT>
                        <P>[This section] requires a union officer or employee to disclose any securities or other interest which he has in a business whose employees his labor union represents or “seeks to represent” in collective bargaining. When a prominent union official has an interest in the business with which the union is bargaining, he sits on both sides of the table. He is under temptation to negotiate a soft contract or to refrain from enforcing working rules so as to increase the company's profits. This is unfair to both union members and competing businesses.</P>
                    </EXTRACT>
                    <P>Senate Report No. 187 (1959) (Senate Report) at 15, reprinted in NLRB Legislative History of the Labor-Management Reporting and Disclosure Act of 1959 (2 volumes) (Leg. History), 1 Leg. History, at 411.</P>
                    <P>The Senate Report presented “three reasons for relying upon the milder sanction of reporting and disclosure [relative to establishing criminal penalties] to eliminate improper conflicts of interest,” which can be summarized as follows:</P>
                    <EXTRACT>
                        <P>Disclosure discourages questionable practices. “The searchlight of publicity is a strong deterrent.” Disclosure rules should be tried before more severe methods are employed.</P>
                        <P>Disclosure aids union governance. Reporting and publication will enable unions “to better regulate their own affairs. The members may vote out of office any individual whose personal financial interests conflict with his duties to the members,” and reporting and disclosure would facilitate legal action by members against “officers who violate their duty of loyalty to the members.”</P>
                        <P>Disclosure creates a record. The reports will furnish a “sound factual basis for further action in the event that other legislation is required.”</P>
                    </EXTRACT>
                    <P>Senate Report, at 16, reprinted in 1 Leg. History, at 412.</P>
                    <P>The Report further stated:</P>
                    <EXTRACT>
                        <P>The committee bill attacks the problem [of conflicts of interest] by requiring union officers and employees to file reports with the Secretary of Labor disclosing to union members and the general public any investments or transactions in which their personal financial interests may conflict with their duties to the members. The bill requires only the disclosure of conflicts of interest as defined therein. The other investments of union officials and their other sources of income are left private because they are not matters of public concern. No union officer or employee is obliged to file a report unless he holds a questionable interest in or has engaged in a questionable transaction. The bill is drawn broadly enough, however, to require disclosure of any personal gain which an officer or employee may be securing at the expense of the union members.</P>
                    </EXTRACT>
                    <P>Senate Report, at 14-15, reprinted in 1 Leg. History, at 410-11.</P>
                    <P>Both the Senate and House Reports recognized that a reportable interest was not necessarily an illegal practice. As the House Report stated:</P>
                    <EXTRACT>
                        <P>In some instances matters to be reported are not illegal and may not be improper but may serve to disclose conflicts of interest. Even in such instances disclosure will enable the persons whose rights are affected, the public, and the Government, to determine whether the arrangements or activities are justifiable, ethical, and legal.</P>
                    </EXTRACT>
                    <P>
                        House Report No. 741 (House Report), at 4, reprinted in 1 Leg. History, at 762. See Senate Report, at 38, reprinted in 1 Leg. History, at 434 (“By requiring reports * * *, the committee is not to be construed as necessarily condemning the matters to be reported if they are not specifically declared to be improper or 
                        <PRTPAGE P="66444"/>
                        made illegal under other provisions of the bill or other laws”).
                    </P>
                    <P>Conflict-of-interest standards, including disclosure obligations of individuals and entities occupying positions of trust, are firmly established in U.S. law. As stated in the House Report, repeating almost verbatim the same point in the Senate Report:</P>
                    <EXTRACT>
                        <P>For centuries the law of fiduciaries has forbidden any person in a position of trust subject to such law to hold interests or enter into transactions in which self-interest may conflict with complete loyalty to those whom he serves. * * * The same principle * * * should be equally applicable to union officers and employees [quoting the AFL-CIO's ethical practices code]: “[A] basic ethical principle in the conduct of union affairs is that no responsible trade union official should have a personal financial interest which conflicts with the full performance of his fiduciary duties as a worker's representative.”</P>
                    </EXTRACT>
                    <P>House Report, at 10-11, reprinted at 1 Leg. History, at 768-69. Senate Report, at 14, reprinted in 1 Leg. History, at 410. See generally Restatement (Second) of Trusts (1959) §§ 170, 173; Restatement (Second) of Agency (1958) §§ 381, 387-98.</P>
                    <P>The reporting provisions of the Act represent, in part, an effort to codify various requirements contained in an extensive code of ethics voluntarily adopted by the AFL-CIO in 1957 and applied to its affiliated unions and officials. See Senate Report, at 12-16, reprinted in 1 Leg. History, at 408-12; House Report, at 9-12, reprinted in 1 Leg. History, at 767-70. See also Archibald Cox, Internal Affairs of Labor Unions Under the Labor Reform Act of 1959, 58 Mich. L. Rev. 819, 824-29 (1960). The following excerpts from this code demonstrate the similarities between a union official's fiduciary duty and the disclosure requirements of section 202.</P>
                    <EXTRACT>
                        <P>[A] basic ethical principle in the conduct of union affairs is that no responsible trade union official should have a personal financial interest which conflicts with the full performance of his fiduciary duties as a workers' representative.</P>
                        <P>[U]nion officers and agents should not be prohibited from investing their personal funds in their own way in the American free enterprise system so long as they are scrupulously careful to avoid any actual or potential conflict of interest.</P>
                        <P>In a sense, a trade union official holds a position comparable to that of a public servant. Like a public servant, he has a high fiduciary duty not only to serve the members of his union honestly and faithfully, but also to avoid personal economic interest which may conflict or appear to conflict with the full performance of his responsibility to those whom he serves.</P>
                        <P>There is nothing in the essential ethical principles of the trade union movement which should prevent a trade union official, at any level, from investing personal funds in the publicly traded securities of corporate enterprises unrelated to the industry or area in which the official has a particular trade union responsibility.</P>
                        <P>[These principles] apply not only where the investments are made by union officials, but also where third persons are used as blinds or covers to conceal the financial interests of union officials.</P>
                    </EXTRACT>
                    <P>
                        Ethical Practices Code IV: Investments and Business Interests of Union, 105 Cong. Rec.*16379 (daily ed. Sept. 3, 1959), reprinted in 2 Leg. History, at 1407-08. See also Ethical Practices Code II: Health and Welfare Funds, 
                        <E T="03">Id.,</E>
                         2 Leg. History, at 1406-07.
                    </P>
                    <P>The Act was crafted with particular regard for the unique function and status of labor unions. Then Senator John F. Kennedy, who was the chief sponsor of the Senate bill, S. 505, which served as the foundation for the LMRDA, stated that the legislation was “designed to permit responsible unionism to operate without being undermined by either racketeering tactics or bureaucratic controls. It is designed to strike a balance between the dangers of to [sic] much and too little legislation in this field.” 105 Cong. Rec. S816 (daily ed. Jan. 20, 1959), reprinted in 1 Leg. History, at 969.</P>
                    <P>As noted by Senator Kennedy, a balance of these interests was central to the enactment of the LMRDA. Congress sought to address legitimate concerns about illegal and undemocratic behaviors without permitting that concern to be used as an excuse for undermining organized labor. Further, Congress sought to address the importance of balancing necessary disclosure and regulation with undue intrusion on union operations and the protection of union officers' privacy interests. As stated in the Senate Report, “[t]he committee recognized the desirability of minimum interference by Government in the internal affairs of any private organization * * * in establishing and enforcing statutory standards great care should be taken not to undermine union self-government or weaken unions in their role as collective-bargaining agents.” Senate Report, at p. 7, reprinted in 2 Leg. History, at 403.</P>
                    <P>Professor Archibald Cox played a pivotal role in drafting the legislation that ultimately became the LMRDA. His testimony before the Senate subcommittee that was considering this legislation presaged the language in the Senate Report, describing the reporting obligation as a limited one. He testified: “The bill is narrowly drawn to meet a specific evil. It requires only the disclosure of conflicts of interest. The other investments of union officials and their other sources of income are left private because they are not matters of public concern.” Hearings on S. 505 before the Subcommittee on Labor of the Senate Committee on Labor and Public Welfare (1959) (Senate Hearings), at 123; see Senate Report, at 15, reprinted in 1 Leg. History, at 411. Professor Cox additionally noted that because the reporting requirements were based, in part, upon the Ethical Practices Code formulated by the AFL-CIO, union officials who adhered to this code would have “virtually nothing to disclose in his report to the public.” Senate Hearings, at 123.</P>
                    <HD SOURCE="HD2">C. Statutory Language</HD>
                    <P>
                        <E T="03">Section 202 provides in its entirety:</E>
                    </P>
                    <P>SEC. 202. (a) Every officer of a labor organization and every employee of a labor organization (other than an employee performing exclusively clerical or custodial services) shall file with the Secretary a signed report listing and describing for his preceding fiscal year—</P>
                    <EXTRACT>
                        <P>(1) Any stock, bond, security, or other interest, legal or equitable, which he or his spouse or minor child directly or indirectly held in, and any income or any other benefit with monetary value (including reimbursed expenses) which he or his spouse or minor child derived directly or indirectly from, an employer whose employees such labor organization represents or is actively seeking to represent, except payments and other benefits received as a bona fide employee of such employer;</P>
                        <P>(2) Any transaction in which he or his spouse or minor child engaged, directly or indirectly, involving any stock, bond, security, or loan to or from, or other legal or equitable interest in the business of an employer whose employees such labor organization represents or is actively seeking to represent;</P>
                        <P>(3) Any stock, bond, security, or other interest, legal or equitable, which he or his spouse or minor child directly or indirectly held in, and any income or any other benefit with monetary value (including reimbursed expenses) which he or his spouse or minor child directly or indirectly derived from, any business a substantial part of which consists of buying from, selling or leasing to, or otherwise dealing with, the business of an employer whose employees such labor organization represents or is actively seeking to represent;</P>
                        <P>
                            (4) Any stock, bond, security, or other interest, legal or equitable, which he or his spouse or minor child directly or indirectly held in, and any income or any other benefit with monetary value (including reimbursed expenses) which he or his spouse or minor child directly or indirectly derived from, a business any part of which consists of buying from, or selling or leasing directly or indirectly to, or otherwise dealing with such labor organization;
                            <PRTPAGE P="66445"/>
                        </P>
                        <P>(5) Any direct or indirect business transaction or arrangement between him or his spouse or minor child and any employer whose employees his organization represents or is actively seeking to represent, except work performed and payments and benefits received as a bona fide employee of such employer and except purchases and sales of goods or services in the regular course of business at prices generally available to any employee of such employer; and</P>
                        <P>(6) Any payment of money or other thing of value (including reimbursed expenses) which he or his spouse or minor child received directly or indirectly from any employer or any person who acts as a labor relations consultant to an employer, except payments of the kinds referred to in section 302(c) of the Labor Management Relations Act, 1947, as amended.</P>
                    </EXTRACT>
                    <P>(b) The provisions of paragraphs (1), (2), (3), (4), and (5) of subsection (a) shall not be construed to require any such officer or employee to report his bona fide investments in securities traded on a securities exchange registered as a national securities exchange under the Securities Exchange Act of 1934, in shares in an investment company registered under the Investment Company Act or in securities of a public utility holding company registered under the Public Utility Holding Company Act of 1935, or to report any income derived therefrom.</P>
                    <P>(c) Nothing contained in this section shall be construed to require any officer or employee of a labor organization to file a report under subsection (a) unless he or his spouse or minor child holds or has held an interest, has received income or any other benefit with monetary value or a loan, or has engaged in a transaction described therein. 29 U.S.C. 432.</P>
                    <HD SOURCE="HD2">D. Rationale for Rulemaking on Form LM-30</HD>
                    <P>The Department is modifying the Form LM-30 for the following reasons, which the Department identified in the NPRM as the bases for its proposed changes:</P>
                    <P>(1) The 2007 Form LM-30 rule created uncertainty for the regulated community, presented unresolved questions regarding the rule's reporting requirements, engendered strong objections to key aspects of the rule, such as the reporting of certain loans, including mortgages and student loans; the reporting of union leave and no docking payments; and the extension of the Form LM-30 reporting requirement to individuals serving as union stewards or in similar positions representing the union.</P>
                    <P>(2) The revisions adopted in this rule better balance the disclosure of information and the burden imposed on union officials.</P>
                    <P>(3) The revisions in this rule better clarify the form and instructions and organize the information in a useful format.</P>
                    <P>As explained in the NPRM, the Department fully recognizes the importance of union officer and employee reporting and the disclosure of pertinent financial information to union members and the public. This rule effectuates these purposes and reflects a proper balancing of transparency with the need to maintain union autonomy and to avoid overburdening unions and their officials with unnecessary reporting requirements. Because the 2007 rule did not adequately consider this balance, it did not succeed in properly implementing the LMRDA. The Department has carefully considered the comments received from the regulated community and the public about the 2007 rule and the changes proposed by the Department. Generally, the Department has included in the final rule the changes proposed. Unless otherwise stated herein, the Department has made these changes for the reasons stated in the NPRM. Rather than restate in full the reasons set out at length in the NPRM, the Department has attempted to limit repetition to those instances where a more detailed discussion is needed to provide context to comments received on the proposed rule and the Department's response to those comments.</P>
                    <HD SOURCE="HD2">E. Review of General Comments Received in Response to NPRM</HD>
                    <P>
                        The Department received 62 unique comments to the NPRM, from 286 commenters.
                        <SU>4</SU>
                        <FTREF/>
                         Of the 62 unique comments received, 39 expressed opposition to the Department's proposal to revise Form LM-30, 22 supported the proposal, and an additional comment, from a labor organization, expressed neither support nor opposition to the proposal, but requested an industry-specific exemption to the LM-30 reporting requirement.
                        <SU>5</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             
                        </P>
                        One of the unique comments was a form letter submitted by 225 individuals. Additionally, one commenter submitted two versions of the same comment.
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             
                        </P>
                        The labor organization suggested that the Form LM -30 reporting obligation should not apply to union officials who receive free admission to performances for union-related purposes, or for purposes of voting for industry awards. The union offered clarifying language that would exempt these examples of free admission from Form LM-30 reporting. The issue will be addressed in section III.E. of the preamble.
                    </FTNT>
                    <P>Comments that expressed, in whole or in part, general support or opposition to the NPRM will be discussed in this section of the rule. Comments on specific changes and revisions to Form LM-30 will be addressed in subsequent sections, which are organized by topic.</P>
                    <HD SOURCE="HD3">Review of General Comments in Support of NPRM</HD>
                    <P>Comments submitted by 17 national/international unions, two federations of labor organizations, one local union, one law firm (on behalf of various clients, including unions, insurance companies, and service providers to unions and benefit plans), and one public policy organization generally expressed strong support for the Department's proposed revisions to Form LM-30.</P>
                    <P>Multiple union commenters, a public policy organization, and a law firm generally supported the Department's NPRM, but expressed concerns about certain aspects of the proposal or suggested certain modifications. These issues and proposed modifications will be discussed later in this rule, in the relevant sections to which each topic applies.</P>
                    <HD SOURCE="HD3">Review of General Comments in Opposition to NPRM</HD>
                    <P>The comments submitted in opposition to the NPRM include the above-referenced form letter, 36 additional comments submitted by individuals, and two comments submitted by public policy organizations. A third public policy organization opposed some aspects of the proposal.</P>
                    <P>Most of the opposing comments, apart from those submitted by the public policy organizations, were general in nature and did not directly, if at all, address the Form LM-30 or the Department's proposed revisions. The above-referenced form letter stated that the proposed Form LM-30 regulations should be rejected because they would undermine efforts regarding recent changes made to unions' reporting and disclosure requirements, which were designed to increase transparency. The letter also stated that union members have relied on the LMRDA to “discourage and expose” corruption.</P>
                    <P>
                        Two individuals that identified themselves as union members asserted that conflict-of-interest reporting requirements should not be lessened, and voiced their support of transparency. While some private citizens limited their comments to expressing general dissatisfaction with the current political administration, other commenters expressed general anti-union sentiment, and did not refer to the proposed revisions to Form LM-
                        <PRTPAGE P="66446"/>
                        30 or any aspect of LMRDA reporting requirements. Additional commenters made general statements that unions should be held accountable for potential conflicts of interest, and generally should not be exempt from reporting requirements. Apparently misunderstanding the Department's proposal, multiple commenters erroneously characterized the NPRM as an effort to eliminate conflict-of-interest reporting altogether.
                    </P>
                    <P>In response to these comments, the Department notes that its proposal and this final rule have been drafted with the purpose of best effectuating the disclosure requirements of the LMRDA. The goal has been to revise the 2007 rule in a way that achieves that purpose. Contrary to the suggestions by several commenters, the Department's proposals are not designed to achieve arbitrary goals or political objectives. Indeed, many commenters appear to have overlooked that most aspects of the 2007 rule were left unchanged by the Department's proposal and this final rule. As a matter of policy and statutory interpretation, the Department believes that the approach adopted in this rule reflects an improvement over those aspects of the 2007 rule that have been revised.</P>
                    <P>One public policy organization disputed the Department's statement that the 2007 rule raised “significant policy and law questions.” Rather, in the commenter's view, the objections to the 2007 rule are “political” in nature, deriving from the “regulated community.” The commenter stated that the NPRM should be immediately withdrawn “due to the Department's inconsistent application of the term “employer” to different parts of the LMRDA” (discussed below in section III, part D, of this preamble). The commenter explained its view that the 2007 changes were necessary additions to ensure needed transparency, and urged the Department to enforce the 2007 rule. The Department disagrees with these general comments. In the Department's view, it is evident from a cursory review of the 2007 rule, the compliance issues it presented, the history surrounding the Form LM-30 and its enforcement, and the comments received at the July 21, 2009 stakeholder meeting, that the 2007 rule presented fundamental policy and legal questions deserving of the Department's scrutiny. As a result of its review of the 2007 rule, the Department has developed an approach that more effectively targets actual or potential conflict-of-interest payments and balances the need for transparency with the legitimate interests of union officials and transparent labor-management relations.</P>
                    <P>Another public policy organization voiced strong opposition to the NPRM, and stated that the NPRM “provides no evidence that is consistent with LMRDA language” to justify its proposed revisions to Form LM-30. The commenter stated that “[s]ince 1959, the Department has essentially ignored Form LM-30 reporting and disclosures.” The commenter argued that the NPRM proposes to “hide [union-employer] collusions,” and “essentially abandons individual workers in its analysis.” For the reasons mentioned above in response to a similar comment, the Department disagrees with the assertions. The interest of workers, union members, and the public in labor-management transparency is a significant goal of the statute, and has been a primary consideration in this rulemaking. The importance of balancing the benefits of disclosure against the burdens that recordkeeping and reporting imposed on the legitimate activities of unions and their officials likewise undergirds the proposal and the final rule. The Department fully explains in the sections that follow in this preamble the rationale for the changes made by this final rule and how they comport with the LMRDA's disclosure provisions.</P>
                    <P>
                        One public policy organization challenged the Secretary's authority to make the proposed revisions under section 208 of the LMRDA, and suggested that the proposed rule, therefore, is inval 
                        <E T="03">Id.</E>
                         Section 208 of the LMRDA, 29 U.S.C. 438, authorizes the Secretary of Labor to issue, amend, and rescind rules and regulations to implement the LMRDA's reporting provisions. The commenter reads section 208 as a “one-way ratcheting mechanism” that only permits the Secretary to add additional reporting requirements, not revise existing requirements. In its view, the changes proposed by the Department could be effectuated only if Congress amends the Act.
                    </P>
                    <P>The Department disagrees with the commenter's distinctive view of section 208. Section 208 grants the Secretary authority “to issue, amend, and rescind rules and regulations prescribing the form and publication of reports required to be filed under Title II of the Act.” The verbs “amend” and “rescind” do not constrain this authority; they allow the Secretary to make changes, but do not compel any particular modification. Further, the words themselves do not connote that amendments and rescissions must add to (rather than subtract from) the reporting requirements. The verb “rescind,” for example, suggests removal or abrogation in general, and is equally applicable to both reporting requirements and reporting exemptions.</P>
                    <P>The Department fully understands that its “rules and regulations prescribing the form and publication of reports required to be filed” must conform to the statute. As explained throughout this preamble, the proposed changes, as adopted in this final rule, are entirely consistent with the language and purpose of the LMRDA. By revising the Form LM-30 to feature a simplified format and more concise, clear instructions, the final rule will facilitate filers' compliance with Form LM-30 reporting requirements and increase the form's utility to the public.</P>
                    <P>The same commenter suggests that the Department has disregarded the intent of Congress and conferred upon itself the authority to create administrative exemptions in derogation of the statutory requirements. The Department disagrees, noting, as discussed throughout this preamble, that the changes are based upon the Department's reasoned interpretation of the Act. The Department additionally notes that while the term “administrative exemption” has long been used to describe certain exceptions from a general reporting obligation (as the term was also used in the 2007 rule), they have always been based on a reasonable interpretation of the statute. The commenter overlooks that the Department retains discretion under the statute in crafting rules, and that how this discretion is exercised is appropriately based on policy considerations.</P>
                    <P>The commenter added that the Secretary may limit disclosure by utilizing de minimis thresholds, but argued that union officials must still adhere to record retention requirements in LMRDA section 206. While the intent of the comment is not clear, such recordkeeping requirements apply to records needed to verify required reports and the detail required to be included on the reports. They do not apply to information not required to be reported.</P>
                    <P>
                        Finally, the commenter suggested that a statement used in the 2010 NPRM demonstrates the Department's intention to undermine congressional intent. The NPRM, at 75 FR 48416, states that the LMRDA reporting provisions “are designed to empower labor organizations, their members, and the public.” The commenter reads the statement as proof that “DOL embraces a view that part of the LMRDA's purpose is to `empower labor unions' 
                        <PRTPAGE P="66447"/>
                        when, in fact, its purpose is to shield union members and the public from corrupt union officials.” In response, the Department in no way intended to intimate that the LMRDA was designed to “empower labor organizations,” as distinct from their membership. As the commenter also recognizes, the LMRDA's disclosure provisions provide information that empowers union members and the public by promoting union self-governance and financial integrity. At the same time, and as recognized in the NPRM, the Department cannot disregard the burden that reporting places on unions and union officials. As stated in the 1959 Senate Committee Report and repeated in the NPRM: “The committee recognized the desirability of minimum interference by Government in the internal affairs of any private organization * * * in establishing and enforcing statutory standards great care should be taken not to undermine union self-government or weaken unions in their role as collective-bargaining agents.” Senate Report No. 187, at p. 7, reprinted in 2 Leg. History, at 403, quoted at 75 FR 48418. Thus, in regard to its impact upon unions, the intent of the LMRDA is not to intrude on the legitimate role of unions in labor-management relations, but, rather, to advance the interests of employees by furthering union and workplace democracy and reducing or eliminating labor-management financial corruption.
                    </P>
                    <HD SOURCE="HD3">Comments on Reporting Burden Created by 2007 Rule</HD>
                    <P>Most union commenters asserted that the 2007 changes to the Form LM-30 reporting requirements are not justified in light of the burden they impose, and voiced support for the rescission of some of these requirements, which one commenter described as “extremely burdensome to filers, and confusing and misleading to the public.” Another international union commented that the 2007 revisions to Form LM-30 “impose[d] a severe burden on union filers with no corresponding benefit to union members or the public and raised fundamental legal and policy questions with which OLMS is still struggling.”</P>
                    <P>A federation of labor organizations stated that in challenging the 2007 rule it had argued that the 2007 “changes in the universe of potential Form LM-30 filers and in the scope of interests and receipts subject to reporting exceeded the Department's statutory authority.” The commenter concurs with the NPRM that the 2007 changes to the Form LM-30, had they gone into effect, would have been unduly burdensome and could have deterred people from running for union office. One commenter concurred with the comments submitted by the federation, and stated that “the prior regulatory scheme * * * was unduly burdensome and far beyond the original intent of the law.” Another commenter stated that the 2007 LM-30 reporting requirements “create a trap for even the most scrupulous and detail-oriented union official,” adding that [“b]y setting [a]standard that in some respects is impossible to meet, the current rules discourage involvement in union activities.”</P>
                    <P>Echoing the burden theme, one international union commenter stated that the Form LM-30 reporting requirements outlined in the 2007 rule require “unnecessary reporting of many financial transactions and arrangements that pose no threat of a conflict of interest,” and create a “crushing burden on [its] officers and employees.” It added that these new requirements “discourage[ ] involvement in union activities to the detriment of both the union and its employer partners.” Yet another commenter supported the Department's proposal, as it targeted the “unnecessary over-complication, confusion, and burden caused by its 2007 rule.”</P>
                    <P>One union commenter challenged the 2007 rule as claiming to enhance “transparency,” but rather imposed “expensive and time-consuming” requirements, to the detriment of the members. Noting the increased volume of information required to be reported on the 2007 Form LM-30, another international union questioned whether such additional information would effectively reveal actual or potential conflicts of interest.</P>
                    <HD SOURCE="HD3">Comment on 2007 Rule's Impact on Compliance Assistance Efforts</HD>
                    <P>One local union commenter cited the intensive, multi-faceted training and compliance assistance efforts undertaken by the commenter's union when the 2007 rule was adopted, and supports the proposed changes, as they would reduce the “complication associated with compliance.” The commenter stated that its union “would much rather devote these human resources to matters that have more widespread and direct benefits for our members,” such as negotiating contracts, processing grievances, and organizing unrepresented workers to protect the wages and fringe benefits of its membership.</P>
                    <HD SOURCE="HD3">Comments on Striking a Fair Balance Between the Conflict-of-Interest Disclosure Requirement and Union Officials' Legitimate Privacy Interests</HD>
                    <P>Numerous commenters supported the Department's proposal in its effort to balance the legitimate needs and interests of unions and their officials with the need for conflict-of-interest reporting that advances labor-management relations, union democracy, and union financial integrity. For example, one commenter stated, “The goal of the proposed Rule, to restore a fair balance between the interests of unions, their members and the public, is appropriate and necessary.” Following this theme, another commenter stated that the Department's proposal better balances union officials' privacy interests with the need for members to have information concerning conflicts of interest that could undermine the union's ability to represent the employees. Another commenter, a federation of labor organizations, stated that it supported the Department's proposal “because, in the main, the proposal accomplishes the Department's statutory purpose of striking the proper `balance' between `the interests of labor organizations, their members, and the public, including the benefits served by disclosure, the burden placed on reporting entities, and preserving the independence of unions and their officials from unnecessary government regulation.” 75 FR at 48416. An international union commenter offered support for the proposed changes, stating that they are well grounded, consistent with congressional purpose in drafting the Act, and successful in striking an appropriate balance between the goals of greater conflict-of-interest transparency while not establishing unnecessary burden for union officials.</P>
                    <HD SOURCE="HD1">II. Authority</HD>
                    <HD SOURCE="HD2">A. Legal Authority</HD>
                    <P>The legal authority for this rule is set forth in sections 202 and 208 of the LMRDA, 29 U.S.C. 432, 438. Section 208 of the LMRDA provides that the Secretary of Labor shall have authority to issue, amend, and rescind rules and regulations prescribing the form and publication of reports required to be filed under Title II of the Act and such other reasonable rules and regulations as she may find necessary to prevent the circumvention or evasion of the reporting requirements. 29 U.S.C. 438.</P>
                    <HD SOURCE="HD2">B. Departmental Authorization</HD>
                    <P>
                        Secretary's Order 08-2009, issued November 6, 2009, contains the 
                        <PRTPAGE P="66448"/>
                        delegation of authority and assignment of responsibility for the Secretary's functions under the LMRDA to the Director of the Office of Labor-Management Standards and permits re-delegation of such authority. See 74 FR 58835 (Nov. 13, 2009).
                    </P>
                    <HD SOURCE="HD1">III. Revisions to the 2007 Form LM-30 Reporting Requirements</HD>
                    <P>This rule implements five changes to the Form LM-30 reporting requirements, as proposed in the NPRM: (1) The elimination of reporting of union leave and no docking payments, and, more broadly, a revised interpretation of the bona fide employee exception; (2) the removal from coverage of individuals serving as union stewards or in similar positions representing the union, such as a member of a safety committee or a bargaining committee; (3) the elimination of reporting for certain bona fide loans and other financial transactions on Parts A and B of the form; (4) the limitation on reporting of payments from employers competitive to the represented employer, certain trusts, and unions; and (5) a revision of the reporting required of national, international, and intermediate union officers and employees.</P>
                    <P>First, this rule returns to the historical practice whereby union officers and employees were not required to report compensation they received under union leave and no docking policies established under collective bargaining agreements or pursuant to a custom and practice under such collective bargaining agreements. These payments are made by a represented employer to its employees who are serving on behalf of the union on labor-management relations matters. Under a union leave policy, the employer continues the pay and benefits of an individual who often works full time on such matters. Under a no docking policy, the employer permits individuals to devote portions of their work day or work week to labor-management relations business, such as processing grievances, with no loss of pay. The requirement in the 2007 rule that union officials must report union leave and no docking payments has been strongly criticized as unduly burdensome. The Department agrees that this reporting requirement imposes undue burden and may impede individuals from running for union office and otherwise serving in important union roles. The 2007 rule was based on the premise that such payments are for work performed on the union's behalf, rather than the employer's, and are thus not payments made under the “bona fide employee” exception of section 202 of the LMRDA. Upon reconsideration, the Department has determined that the term “bona fide employee,” as used in that section, is most naturally read to distinguish between, on the one hand, payments that are made to a union official by virtue of his or her employment by the company making the payment, and, on the other hand, payments that are made to union officials without regard to such employment. This interpretation better accords with the purposes of the statute than the interpretation embodied in the 2007 rule that focuses on whether the union or the employer making the payment exercises primary control over an individual's discrete, temporal activities as a union official.</P>
                    <P>Second, this rule returns to the historical practice of excluding union stewards and similar union representatives from Form LM-30 reporting. The Department believes that this practice comports with the language of section 202 and better effectuates labor-management relations than the interpretation embodied in the 2007 rule.</P>
                    <P>
                        Third, this rule establishes administrative exemptions for Parts A and B of the form, whereby union officials generally need only report loans from bona fide credit institutions if such loans are on terms more favorable than those available to the public. The 2007 rule required more extensive reporting and made confusing and complex distinctions among various relationships and credit institutions. This rule also incorporates the clarification, as set forth in 2007 Form LM-30 Frequently Asked Question (FAQ) 70, that union officials as a general rule are not required to report on savings accounts, certificates of deposit (CD), credit cards, etc. where such instruments contain the same terms offered to other customers without regard to an individual's status as a union official.
                        <SU>6</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             See the 2007 Form LM-30 FAQs at 
                            <E T="03">http://www.dol.gov/olms/regs/compliance/RevisedLM30_FAQ.htm.</E>
                        </P>
                    </FTNT>
                    <P>Fourth, this rule limits the reporting obligation with respect to interests in and payments from employers that compete with employers represented by the official's union or that the union actively seeks to represent. Disclosure of such payments is important, but only where an official is involved with the organizing, collective bargaining, or contract administration activities related to a particular represented employer, or possesses significant authority or influence over such activities. Establishing such limitation on disclosure ensures that meaningful information will be provided to union members without imposing undue burden on officials who do not occupy positions of influence over the union's organizing, collective bargaining, or contract administration activities related to the represented employer. Similarly, this rule modifies the scope of reporting insofar as payments from certain trusts and unions are concerned. The Department returns to its historical practice of not requiring officials to report on payments they receive from trusts or, as a general rule, from unions. Officials of a staff union are, however, still required to report on Part A any payments they receive from the union-employer whose employees the staff union represents.</P>
                    <P>
                        Finally, this rule revises and clarifies the scope of “top-down” reporting for officials of international, national, and intermediate unions. This rule effectuates the Department's proposal in the NPRM that officers and certain employees of these higher level unions must look at payments they receive from employers and businesses with relationships with lower levels of their unions (
                        <E T="03">e.g.,</E>
                         a local or other subordinate body), as well as with their own level of the union, when applying the Form LM-30 reporting requirements. However, based on a review of the comments, the Department has determined to adopt a modification of its proposed expansion of the scope of top-down reporting for union employees of national, international, and intermediate body labor organizations. All higher-level union employees that have significant authority or influence with respect to affiliates will also need to report these matters in relation to subordinate affiliates. Higher-level union employees without such significant authority or influence over affiliates or officials of affiliates will not be subject to these top-down reporting obligations.
                    </P>
                    <P>The 2007 rule also established confusing exceptions to the “top-down” reporting obligations. Payments from businesses that dealt with represented employers were exempt, while the instructions did not specify the reportability of payments from businesses that dealt with lower level unions. Further, these officials were not required to report any payments or other financial benefits received by their spouses and minor children from employers and businesses involved with a lower level union. This rule effectuates the Department's proposal to remove these exceptions.</P>
                    <P>
                        In developing this rule, the Department has reviewed the reporting 
                        <PRTPAGE P="66449"/>
                        examples utilized in the 2007 rule and the substantial guidance issued after the rule's publication as answers to FAQs in order to identify the extent to which, if at all, reporting will be changed under this rule. This rule supersedes any inconsistent interpretation or other guidance. The Department identifies in the margin those instances where the rule does not change the reporting obligations under the examples and FAQs.
                        <SU>7</SU>
                        <FTREF/>
                         As discussed later in the text, examples will generally not be included in the revised instructions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             Most of the examples in the 2007 instructions continue to accurately reflect reporting requirements as articulated in this rule. Thus, the following continue to accurately reflect reporting requirements: Examples 2-15, at pp. 3-4 of the instructions; examples 1-2, 4-5, at p. 6 of the instructions; examples 1 and 2, at p. 7 of the instructions; and examples 1, 3-15, and 17, at pp. 8-9 of the instructions. Note that the NPRM had incorrectly stated that example 3, at p. 6 of the instructions would continue to accurately reflect reporting under this rule. Several of the FAQs are based on requirements that the Department changes with this rule.The following FAQs, however, continue to accurately reflect reporting requirements: 2-10, 12-26, 28, 30-37, 39, 44, 47, 49-50, 54, 56-59, 72-76, and 79-88. It should be noted however, that some of the comments and FAQs, such as FAQs 49 and 73, while remaining accurate, were intended to illustrate issues that are less likely to arise under the revised rule. Others, such as FAQs 1 and 77, while largely accurate, contain some statements that are based on or refer to interpretations that are superseded by this rule.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">A. The Bona Fide Employee Reporting Exception Under Section 202</HD>
                    <P>This rule effectuates the Department's proposal to return to its historical position that union officials should not report union leave and no docking payments. 75 FR 48421. As discussed above, these payments are made by a represented employer to its employees who are serving on behalf of the union on labor-management relations matters in accordance with the parties' collective bargaining agreement. First, the historical interpretation under which such compensation was not reported—to which this rule returns—comports more readily with the language in section 202, than the interpretation underlying the Department's 2007 interpretation. Second, such reporting imposes a substantial burden on union officials on matters unlikely to pose conflicts of interest and removing this burden ensures that there will be no undue interference with the internal workings of labor unions and labor-management relations. Third, there is no persuasive reason, as a matter of policy, why union officials must report such payments, while employers making such payments are under no similar obligation. See 75 FR 48421-48423.</P>
                    <P>
                        Sections 202(a)(1) and (5) of the LMRDA require a labor organization officer or employee to report payments that the official, his or her spouse, or minor children receive from an employer whose employees the labor organization represents or is actively seeking to represent, “
                        <E T="03">except payments and other benefits received as a bona fide employee of such employer.”</E>
                         29 U.S.C. 432(a)(1) &amp; (5) (emphasis added).
                    </P>
                    <P>Until the 2007 rule, the Department's policy had been to exclude from reporting payments and other benefits received for activities undertaken on behalf of the union, as well as for any other “activities other than productive work,” but paid for by the employer. Thus, the instructions for the 1963 Form LM-30 stated that the following payments and benefits were exempt from Form LM-30 reporting:</P>
                    <EXTRACT>
                        <P>[p]ayments and benefits received as a bona fide employee of the employer for past or present services, including wages, payments or benefits received under a bona fide health, welfare, pension, vacation, training or other benefit plan; and payments for periods in which such employee engaged in activities other than productive work, if the payments for such period of time are: (a) Required by law or a bona fide collective bargaining agreement, or (b) made pursuant to a custom or practice under such a collective bargaining agreement, or (c) made pursuant to a policy, custom, or practice with respect to employment in the establishment which the employer has adopted without regard to any holding by such employee of a position with a labor organization.</P>
                    </EXTRACT>
                    <P>Pre-2007 Form LM-30 Instructions, Part A (Items 6 and 7) at (iv). See 28 FR 14384 (Dec. 27, 1963).</P>
                    <P>The 2007 rule narrowed the exemption in the Form LM-30 instructions, as quoted above, by limiting it to situations where such payments were made pursuant to a bona fide collective bargaining agreement and totaled 250 or fewer hours during the filer's fiscal year.</P>
                    <HD SOURCE="HD3">1. Review of Comments Received</HD>
                    <P>The Department received 17 substantive comments on the issue of the union leave and no docking payments. Of these 17 comments, 14 supported the removal of reporting for such payments: 12 unions, one law firm, and one public policy organization. Additionally, three comments opposed the change, including two public policy groups, and 225 individuals who sent in form letters.</P>
                    <HD SOURCE="HD3">a. Comments in Support of NPRM</HD>
                    <P>The Department received 13 comments that provided general support for removing union leave and no docking payments from the Form LM-30 reporting requirements, with about one-half providing specific comments in support of the changes. One international union commenter concurred with the view that the “legitimacy” of such payments is established when they are included in a collective bargaining agreement or employment practice, and that they do not pose conflict-of-interest problems like “no show work, featherbedding, or similar practices.” The commenter further stated that requiring reporting for such payments for union officials, and not employers, imposes an “unnecessary burden” on the officials and deters employees from serving as representatives. A national union concurred with the Department's view, as expressed in the NPRM, that such payments do not pose a conflict of interest, and also noted that employers are not required to report such payments on the Form LM-10.</P>
                    <P>Another international union maintained that such reporting would be burdensome, unrelated to the purpose and intent of the statute, and “disruptive of many well-established labor-management relationships.” The commenter also stated that such arrangements are known to the employees, who benefit along with the employer from this practice, and it presented evidence of the burdensome nature of reporting such payments. It explained that union officials would be required to keep track of all hours worked under union leave or no docking arrangements and calculate benefits as well as wages earned, adding that such information would not easily be obtained from the employer, who may not desire to release it. Such reporting, the commenter contended, may discourage employee participation in the union, and would not disclose conflicts of interest in that no docking arrangements are already known to employees in a bargaining unit either by being required by a collective bargaining agreement or being made pursuant to a custom under a collective bargaining agreement. Further, the commenter stated that members know that when stewards or other union representatives “administer the contract, process grievances, or represent members in disciplinary actions,” they are receiving payment from the employer.</P>
                    <P>
                        A national union discussed the burden and disincentive that reporting union leave and no docking payments would have on employees' willingness to serve the union. Another national union emphasized that such payments, received pursuant to a collective bargaining agreement, are made with full knowledge of the employees and 
                        <PRTPAGE P="66450"/>
                        thus reporting is not needed to provide transparency. The union explained that the burden that such reporting would impose would discourage members from representing their fellow employees in “grievances, serving on safety and health committees, and participating in collective bargaining.” An international union stressed that such payments do not pose conflicts of interests, as they “primarily serve” the employers by promoting “prompt and fair resolution of grievances and other workplace issues so that work continues and morale remains high.”
                    </P>
                    <P>Further, a national union stated that in determining whether or not a payment is received “as a bona fide employee,” a distinction must be made between payments made “by virtue” of a union official's employment with the employer and payments made without regard to such relationship. In this union's experience, employees volunteer to serve, on their own personal time, on joint labor-management, safety and health, and other committees, with the collective bargaining agreement only ensuring that they do not lose any compensation or benefits.</P>
                    <P>
                        Finally, a law firm supported the Department's proposed return to its historical position that union leave and no docking payments are not reportable. It urged the Department to clarify that employers are not required to report such payments under section 203 of the Act. The firm asserted that such payments should be considered to be made as “compensation for, or by reason of, [an employee's] service as an employee for such employer.” 
                        <SU>8</SU>
                        <FTREF/>
                         It stated that without such clarification an employer may feel obligated to report such payments, even though union officials are not required to report their receipt of such payments. As the Department discusses in later sections of the preamble, this rulemaking solely addresses reporting under section 202 of the Act and that interpreting section 203 requirements would be beyond its scope.
                    </P>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             The Department of Justice, not this Department, is responsible for interpreting and enforcing section 302 of the Taft-Hartley Act. The language quoted is from section 302(c) of the statue.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments in Opposition to NPRM</HD>
                    <P>The three comments opposing this aspect of the Department's proposal offered arguments in support of the 2007 rule's premise that union leave and no docking payments presented a conflict of interest for union officials and must be reported to ensure appropriate transparency. Two of the commenters argued that the Department's proposal was based on an impermissible reading of the statute.</P>
                    <P>A public policy organization offered some specific observations regarding the effect of allowing union leave and no docking to go unreported. It claimed that the Department lacked authority under the Act to excuse union officials from reporting such payments, suggesting that the proposed rule was based simply on the new Administration's dissatisfaction with the reporting requirement rather than a considered view of the statute's requirements. The comment argued that payments for work done for the union cannot be received as a “bona fide employee.”</P>
                    <P>Additionally, the public policy organization claimed that by eliminating reporting, “de facto no-show jobs” and “featherbedding” would be concealed and substantial payments to union officials would go unreported. Such payments, in its view, constitute an improper “subsidy” for union activity. Another commenter, a public policy organization, argued that the Department's proposal would conceal instances of “no-show jobs,” and other fraudulent arrangements. This public policy organization also asserted that, in proposing to remove union leave and no docking payments from Form LM-30 reporting, the Department was ignoring the structure of the statute and establishing an “administrative exemption.”</P>
                    <P>The individuals who commented by form letter also addressed this issue and stated that no docking reporting should not be removed because most stewards receive no extra compensation for their duties, which could make them susceptible to “other forms of rewards.”</P>
                    <P>The two public policy organizations stated that the burden associated with the 2007 rule is significantly overstated. One organization stated that the Department's proposal overlooked how the 2007 rule mitigated burden by establishing a 250-hour reporting threshold. One of the organizations argued, albeit without further support, that most union officials would not have to report their union leave or no docking payments, because these payments would not meet the 250-hour threshold.</P>
                    <P>The organization also argued that the Department's burden estimates in the 2010 NPRM demonstrated the absence of any significant burden associated with reporting union leave and no docking payment, noting that the Department estimated that the proposed changes would only reduce recordkeeping time by five minutes (15 minutes in the proposed rule as opposed to 20 minutes in the 2007 rule) and the overall reporting by 30 minutes (90 minutes in the proposed rule as opposed to 120 minutes in the 2007 rule).</P>
                    <P>A public policy organization also objected to the Department's assessment of the burden associated with the 2007 rule, as discussed in the NPRM. It stated, on one hand, that any burden is not the result of the 2007 rule but has existed since the enactment of the statute (even if the Department, in the commenter's opinion, did not always enforce the Form LM-30 requirements), and, on the other hand, that the 2007 rule created no additional burden because only “atypical financial arrangements that benefit some union officials” were reportable under the rule.</P>
                    <P>
                        Taking issue with the view that union leave and no docking payments pose no conflict of interest where required by a collective bargaining agreement or made pursuant to a custom under a collective bargaining agreement, another public policy organization argued that these payments create “the definite possibility of becoming a conflict of interest.” In this regard, it cited a dissenting opinion in 
                        <E T="03">Caterpillar</E>
                         v. 
                        <E T="03">UAW,</E>
                         107 F.3d 1052, 1060 (3d
                        <SU>.</SU>
                         Cir. 1997)(Alito, J. dissenting), where the dissenting judge stated such payments create a conflict, because “union negotiators * * * may agree to reduced benefits for employees in exchange for financial support for the union.”
                    </P>
                    <P>
                        One public policy organization acknowledged that the courts have determined that union leave and no docking are not unlawful under LMRA Section 302, but it nevertheless contends that the courts have “misconstrued” such provision, and that such payments, as well as the granting of “super-seniority” to union officials, do create a conflict of interest for the union officials, as the officials could exchange benefits for the bargaining unit as a whole for benefits for themselves. The comment asserted that “any special benefit” creates a conflict of interest, and it cites 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">Phillips,</E>
                         19 F.3d 1565, 1566-69 (11th Cir. 1994), to illustrate this point. It also contended that disclosure furthers the public's and government's ability “to determine the validity of the financial transaction.” Additionally, the commenter rejected the idea that union leave and no docking provided value to the employer, insisting, for example, that the payments did not increase the speed of handling grievances, and that, in any event, such considerations have no relevance to the statute.
                        <PRTPAGE P="66451"/>
                    </P>
                    <P>The public policy organization also contended that any conflict of interest should be disclosed so members can “exercise their democratic rights” when choosing representatives, and that the Department will hamper members' ability to exercise such rights by establishing a Form LM-30 that will provide “less information on the financial activities of their representatives.” Another public policy organization similarly argued that the Department is proposing to reduce the “amount of information” made available to members, the government, and the public regarding payments to union officials.</P>
                    <P>Additionally, the public policy organization argued that the effect of the union leave and no docking payments is to shift costs of union officer, employee, and steward training to the employer and to defray costs involved in the union's political activities. Thus, the commenter contended that reporting is needed for the public to be made aware of these effects. Furthermore, the commenter insisted that the effect of the NPRM's “new definition of `bona fide employee'” will require the filing of other LMRDA reports, including “persuader reports” under section 203 of the Act.</P>
                    <P>Finally, both public policy organization commenters disagreed with the Department's position that, as a matter of policy, there was no persuasive reason why union officials should report union leave and no docking payments while employers are not required to do so pursuant to the Form LM-10, Employer Report, and section 203 of the statute.</P>
                    <HD SOURCE="HD3">2. Response to Comments</HD>
                    <P>In response to the comments received, and for the reasons stated in the NPRM and discussed herein, this rule effectuates the Department's proposal to rescind the requirement in the 2007 rule that union officials report compensation and benefits they receive under employer union leave and no docking policies. In the NPRM, as noted above, the Department advanced three reasons for its proposal: (1) The historical interpretation under which such compensation was not reported comports more readily with the language in section 202 than the interpretation in the 2007 rule; (2) the 2007 rule imposes a substantial burden on union officials to report on matters unlikely to pose conflicts of interest and this burden could unduly interfere with the internal workings of labor unions and labor-management relations; and (3) the absence of any persuasive policy reason why union officials must report receiving such payments while employers making such payments are under no similar obligation. </P>
                    <P>
                        With regard to the language of section 202, the Department believes it is best read to require reporting of payments only when a union official is not a bona fide employee of the employer making the payment. This reading departs from the 2007 rule's approach, which sought to equate payments to “bona fide employees” with payments made to union officials for “productive work” on the employer's behalf. In the 2010 NPRM, the Department made the additional points, discussed below, in rejecting the position taken in the 2007 rule. An individual's status as an employee is based on the various factors articulated in the common law. See 
                        <E T="03">Nationwide Mutual Ins.</E>
                         v. 
                        <E T="03">Darden,</E>
                         503 U.S. 318 (1992). “Bona fide” is synonymous with “good faith” or “genuine,” 
                        <E T="03">i.e.,</E>
                         without fraud or deceit.
                        <SU>9</SU>
                        <FTREF/>
                         Thus, section 202(a)(1) is most naturally read to except from reporting union leave and no docking payments to a current or former employee of the company making the payment unless made under the guise of employment, such as where payment is for a no-show job with the company, in an amount that unreasonably exceeds the value or amount of the work performed, or the payment is made on terms inconsistent with the parties' negotiated agreement or the workplace custom and practice under the agreement. In contrast, where a payment made to an individual working on behalf of the union by his current or past employer is sanctioned by a collective bargaining agreement or by custom or practice of the workplace pursuant to the collective bargaining agreement, the legitimacy or “bona fides” of the payment, received as a result of a genuine employment relationship, is established.
                    </P>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             
                            <E T="03">See Black's Law Dictionary</E>
                             (8th ed. 2004), which defines the term as: “1. Made in good faith; without fraud or deceit. 2. sincere; genuine”; 
                            <E T="03">The Random House Dictionary of the English Language, Unabridged</E>
                             (2d ed. 1987), which defines the term as: “1. made, presented, etc. in good faith; without deception or fraud * * *. 2. genuine.—syn. 1. honest, sincere, lawful, legal. 2. genuine.—ant. spurious, deceitful, false.” 
                            <E T="03">See also Black's</E>
                             “bona fide operation,” defined as “[a] real, ongoing business”; and “bona fides,” defined as “1. Good faith. 2. 
                            <E T="03">Roman law.</E>
                             The standard of conduct expected of a reasonable person, esp. in making contracts ands similar actions; acting without fraudulent intent or malice.” See 75 FR 48422.
                        </P>
                    </FTNT>
                    <P>
                        In response to the comments received, the Department notes that payments received as bona fide employees may include wages and other benefits received as compensation for service as an employee of the employer, 
                        <E T="03">and</E>
                         other compensation, such as jury duty leave, military leave, and maternity and paternity leave. It is not relevant whether or not the payments made to employees are for work or other activities engaged in under the control or direction of the employer, as employers routinely provide payments to employees as bona fide employees in such circumstances, which the 2007 rule also recognized. See the definition of “bona fide employee,” in the 2007 Form LM-30 Instructions, which exempts, in part, payments or benefits received for “leave for jury duty.” Further, the Department does not recognize any difference between union leave and no docking payments from other types of leave payments that are not for “productive work,” assuming that they are all bona fide, or good faith, payments.
                    </P>
                    <P>
                        The Department disagrees with the commenters' conclusions that unless union leave and no docking payments to union representatives are reported there will be no disclosure of de facto “no-show jobs,” “featherbedding,” or similar abuses of the employment relationship.
                        <SU>10</SU>
                        <FTREF/>
                         Contrary to this commenter's view, such payments are reportable on the pre-2007 Form LM-30, the 2007 Form LM-30, 
                        <E T="03">and</E>
                         the revised Form LM-30, as they are payments that are not received as a 
                        <E T="03">bona fide, i.e.,</E>
                         good faith, employee. See IM entry 248.200; see also the NPRM at 75 FR 48422.
                        <SU>11</SU>
                        <FTREF/>
                         Nothing in the Department's proposal suggested otherwise. Regardless of the label the commenter might attach, 
                        <E T="03">e.g.,</E>
                         de facto “no-show job,” what is relevant is whether or not the payment was received as a bona fide employee. Further, as mentioned, the legitimacy of the payment is established when it is made pursuant to the terms of a collective bargaining agreement. Thus, the determination of whether or not such payments are made pursuant to a collective bargaining agreement, or a custom or practice made pursuant to a 
                        <PRTPAGE P="66452"/>
                        collective bargaining agreement, is not only relevant but statutorily necessary. “Bona fide” means “genuine” or in “good faith,” the application of which, in a unionized workplace, must be made in part by analyzing the collective bargaining agreement.
                        <SU>12</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             The Department disagrees with the assertion that a union official remaining on an employer's rolls under a grant of “super-seniority” would have had an obligation, simply upon that status, under the Act to report all payments received from an employer. Like any union official, an official with this status would have been required to report union leave or no docking payments under the 2007 rule. However, payments made to an official for his regular production work have never been reportable under the Act. Payments received for production work are not reportable because they are received as a bona fide employee of the employer making the payment. An employee's super-seniority status does not change this analysis. See 72 FR 36127-28.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             The Department states that, as a general matter, union leave and no docking payments are received by union officials as bona fide employees, but it will evaluate the factual circumstance concerning any type of payment to a union official, on a case-by-case basis, if there is any question whether or not the bona fide nature of the arrangement has been established.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             See 
                            <E T="03">Caterpillar, Inc.</E>
                             v.
                            <E T="03"> UAW,</E>
                             107 F.3d 1052 (3d Cir. 1997) (employer's payments of salary and benefits to union grievance chairpersons did not violate section 302 of the LMRA). The majority stated that the collective bargaining agreement “does not immunize otherwise unlawful subjects but, by defining the basis for the payments, speaks directly to the question posed by the statute as to whether the payments are “compensation for, or by reason of * * * service as an employee.” 
                            <E T="03">Id.</E>
                             at 1057.
                        </P>
                    </FTNT>
                    <P>
                        Further, the Department disagrees with a commenter's suggestion that no docking and union leave payments are a type of “featherbedding” or “no show jobs” and as such are unlawful or at least subject to disapproval on public policy grounds.
                        <SU>13</SU>
                        <FTREF/>
                         Indeed, as just discussed, “no-show jobs,” “featherbedding,” and similar improper payments are distinct from those payments that an employee of the employer receives as a 
                        <E T="03">bona fide</E>
                         employee of such employer. Moreover, it is longstanding Departmental policy that the bona fide employee exemption can only be applied to union officials if they are current or former employees of the employer. See IM entry 243.200 (based on an opinion rendered on August 17, 1962). As stated, the bona fide nature of the payments is established by virtue of the collective bargaining agreement or by custom and practice under the collective bargaining agreement, or by policy, custom, or practice without regard to an employee's position within a labor organization. The Department emphasizes that it did not propose to exempt 
                        <E T="03">any</E>
                         payment from an employer to a union official pursuant to a collective bargaining agreement, nor did it propose to exempt any payment from an employer to a union official simply because the official is also a current or former employee of such employer. Rather, the Department proposed and here adopts the position that payments and other benefits from an employer to a union official are exempt if such payments and other benefits are “received 
                        <E T="03">as</E>
                         a bona fide employee of such employer” (emphasis added). See section 202(a)(1).
                    </P>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             The commenter may have its own distinctive notion of how these terms may be used, but its suggestion that union officials receiving compensation or union leave benefits for the work they perform on labor-management matters is somehow improper or tainted is misplaced. Simply put, the terms “featherbedding” and “no show jobs” cannot be fairly applied to the work undertaken by union officials in representing the union and its members in administering the contract between the union and the employer. The term “featherbedding,” is usually associated with practices to keep workers on a company's payroll, even though the jobs are no longer needed because of changes in production methods. See Robert's Dictionary of Industrial Relations. As there defined, the term refers to “make work for [a union's] members through the limitation of production, the amount of work to be performed, or other make-work arrangements.” 
                            <E T="03">Id.,</E>
                             251. See also 29 U.S.C. 158(b)(6) (making it an unfair labor practice for a union “to cause or attempt to cause an employer to pay or deliver or agree to pay or deliver any money or other thing of value, in the nature of an exaction, for services which are not performed or not to be performed”). “No-show jobs” is a term more commonly associated with extortion or shakedown by criminal elements, rather than as a means of preserving a worker's livelihood in the face of technological change or a payment with the object of promoting constructive labor-management relations. Unlike “no-show jobs” where an individual receives pay for no work, union officials are performing the work for which they are being compensated, work deemed to be in the mutual interest of the union and the employer. Clearly, “featherbedding” and “no-show jobs,” as these terms are commonly understood, cannot fairly be applied to union leave and no docking arrangements in which union officials engaged in activities that advance the collective interests of a company's workers represented by the union. While featherbedding and no-show jobs are reportable on the revised Form LM-30, union leave and no docking payments are not.
                        </P>
                    </FTNT>
                    <P>Additionally, as stated in the NPRM and noted in the 2007 rule, union leave and no docking payments were common at the time the LMRDA was enacted. 72 FR at 36126. As set out in the NPRM, these payments were not an issue of concern in the hearings before the McClellan Committee or in any of the legislative materials relating to the LMRDA, unlike payments such as for no-show work or featherbedding. 75 FR at 48422. As noted in the 2007 rule, the legislative history does not shed light on whether Congress had a specific intention to require or not the reporting of such payments by union officials. See 72 FR at 36126. While, as noted in the 2007 rule, legislative silence is not generally a conclusive guide to interpreting statutory text, it is notable, as explained in the 2010 NPRM, at 75 FR 48422, that Congress did not identify union leave or no docking payments as requiring disclosure to union members and the public as a matter of course. See 72 FR at 36126. Equally significant, such payments were not in any way proscribed by the AFL-CIO codes of ethics that strongly influenced the reporting provisions of the LMRDA. See 72 FR at 36112-13. See Senate Hearings, at 123 (statement by Professor Cox that union officials who followed the AFL-CIO Ethical Practices would have “virtually nothing to disclose in his report to the public”).</P>
                    <P>With regard to the second reason advanced in the NPRM for removing union leave and no docking from the Form LM-30 reporting requirements, the Department continues to believe, as explained below, that such reporting imposes a substantial burden for union officials on matters unlikely to pose conflicts of interest, and thus unduly interferes with the internal workings of labor unions and labor-management relations. In response to those commenters who argued that the Department is downplaying the importance of section 202 reporting, the Department has acknowledged repeatedly in the various LM-30 rulemakings that section 202 is intended to capture payments that, although not necessarily illegal, are “atypical financial arrangements” that should nevertheless be disclosed to union members and the public if they present a potential conflict of interest. Such disclosure aids union democratic self-governance and assists government agencies and the public to identify potential corruption. The Department has also acknowledged that a “special benefit” received by a union official from a represented employer should be disclosed if it would likely constitute an actual or potential conflict of interest. At the same time, however, the Department is mindful that section 202 does not require general reporting of union officials' financial information.</P>
                    <P>
                        In the Department's view, union leave and no docking payments, like other payments received by a bona fide employee, reflect ordinary arrangements, mutually agreed upon by the employer, the union, and the employees, that do not present such a danger of a conflict of interest or corruption. As articulated in the NPRM, the Department does not view union leave and no docking payments as presenting the type of danger that Congress intended to highlight through reporting. Such payments, where established by virtue of the collective bargaining agreement, or by custom and practice under the collective bargaining agreement, or by policy, custom, or practice without regard to an individual's position within a labor organization, do not present the sort of conflicts of interest presented by other payments to union officers and employees. Rather, they serve the mutual goals of employers and unions. They help ensure that individuals with first-hand knowledge of an employer's workplace will be able to take a position with the union, a benefit not only to the union and employer but also the represented employees. Such payments are voluntary; without the assent of both management and labor, the payments 
                        <PRTPAGE P="66453"/>
                        cannot be made. They are not kept secret from employees.
                        <SU>14</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             These payments are usually made under the terms of a collective bargaining agreement and tied to the same rate of pay that the union official would have received under the agreement for time worked at his or her trade. Indeed, the court in 
                            <E T="03">Caterpillar Inc.</E>
                             v. 
                            <E T="03">UAW,</E>
                             stated “each rank-and-file employee has the opportunity to vote” on the collective bargaining agreement, which is ratified by the union membership, and which provides the membership a means to hold officials receiving the payments accountable. The court asserted that such payments thus differ from “bribery, extortion, and other corrupt practices conducted in secret.” See 
                            <E T="03">Caterpillar</E>
                             107 F.3d at 1057. Moreover, under section 104 of the LMRDA, each bargaining unit member may receive and inspect a copy of the collective bargaining agreement.
                        </P>
                    </FTNT>
                    <P>
                        Moreover, the Department is persuaded that an employer's agreement to pay its employees to work for or serve the union does not, in and of itself, have an influence on the duties or loyalties of the union official, since union leave and no docking payments are on the same terms as the payments the bona fide employee would otherwise receive if he or she continued work performed for and under the control of the employer. Indeed, the members themselves are paid by the same employer. Furthermore, when the union official or representative no longer serves in such a labor-management capacity he or she could return to regular full-time production work for the employer receiving the same payments and benefits received while working as a union official or representative.
                        <SU>15</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             The Department also notes that a union official or representative who receives union leave or no docking payments from an employer, as a bona fide employee of the employer, does not, thereby, owe any allegiance to such employer in conflict with any duty to the union and its members, as the union appoints or elects its own representatives.
                        </P>
                    </FTNT>
                    <P>
                        The Department disagrees with the view of a public policy organization that any “special benefit” received by a union official must be reported, or that any “special benefit” nurtures an environment in which self interest takes priority over the interests of a bargaining unit. Relying on 
                        <E T="03">United States</E>
                         v. 
                        <E T="03">Phillips,</E>
                         19 F.3d 1565 (11th Cir. 1994), the commenter suggested that union leave, no docking payments, and “special benefits” create not only a hypothetical conflict of interest, but reflect “in fact, how labor unions operate.” As an initial matter, the Department strongly disagrees with the notion that financial self-interest on the part of union officials animates how unions represent the interests of their members. Additionally, the commenter's reliance on 
                        <E T="03">Phillips</E>
                         is misplaced.
                    </P>
                    <P>
                        The 
                        <E T="03">Phillips</E>
                         decision does not concern union leave and no docking arrangements. In that case, an employer and union officials were convicted, in part, for violating the LMRA by ignoring a collective bargaining agreement and granting 
                        <E T="03">retroactive</E>
                         leaves of absences, and thus pension benefits, to the officials. The Department believes the court reached the right result in that case. Further, the opinion in that case cannot be read to suggest that the improper conduct there involved was at all symptomatic of how union officers conduct their activities on behalf of their members, nor does it affect the reporting of union leave and no docking arrangements. Moreover, the result in that case lends support to the Department's proposal. In 
                        <E T="03">Phillips,</E>
                         the payments received were by union officials who were no longer employees of the employer at the time the benefits were arranged, and the retroactive leave was not provided for in the collective bargaining agreement. Because the benefits there at issue were not received pursuant to union leave or no docking arrangements or otherwise received by union officials as 
                        <E T="03">bona fide</E>
                         employees of the employer, the benefits would have to be reported under both the Department's proposal and the 2007 rule. Moreover, the commenter's reliance on 
                        <E T="03">Phillips</E>
                         is further undercut by that court's recognition, citing 
                        <E T="03">BASF Wyandotte Corporation</E>
                         v.
                        <E T="03"> Local 227,</E>
                         791 F.2d 1046, 1049 (3d Cir. 1986), that no docking payments are not unlawful under the LMRA. See 
                        <E T="03">Phillips,</E>
                         19 F.3d at 1575.
                    </P>
                    <P>
                        The Department finds instructive the discussion concerning union leave and no docking payments in 
                        <E T="03">Caterpillar, Inc.</E>
                         v. 
                        <E T="03">UAW,</E>
                         107 F.3d 1052,1056 (3d Cir. 1997), where the court recognized that such payments, while not compensation “for hours worked in the past, certainly were `by reason of' that service.” The court also noted that the union leave and no docking are arrangements in which “every employee implicitly gave up a small amount in current wages and benefits in exchange for a promise that, if he or she should someday be elected grievance chairperson,” the employer would continue to pay his or her salary. 
                        <E T="03">Id.</E>
                         Thus, such payments only benefit those union officials who are members of the bargaining unit, and all members of the bargaining unit have the potential of receiving such payments if they become union officials. Further, all represented employees benefit from the work of their fellow employees who represent them.
                    </P>
                    <P>In response to the commenter who asserted that union leave and no docking payments constitute an improper “subsidy” to the union, the Department disagrees. These payments are provided by mutual agreement of the union and the employer to facilitate labor-management relations. The payments are made to current or former employees who have been selected by the union to perform this service to the bargaining unit, a practice that provides benefits to both labor and management. These payments are similar to other benefits provided to employees represented by the union such as payment for jury duty, military service, and other situations as discussed above.</P>
                    <P>
                        In response to the commenter who questioned the impact of union leave and no docking reporting on labor-management relations, the Department is particularly concerned about the potential consequence of requiring reporting of payments received under union leave or no docking policies (
                        <E T="03">i.e.,</E>
                         union members will be discouraged from running for union office and others from serving as stewards). The Department believes that its historical position to except union leave and no docking payments from reporting is consistent with the purposes of the LMRDA and with the Congressional plan that the government avoid unnecessary intrusion into internal union affairs. Cf. 
                        <E T="03">Wirtz</E>
                         v.
                        <E T="03"> Local 153, Glass Bottle Blowers Assn.,</E>
                         389 U.S. 463, 470-71 (1968). Employers have historically agreed to compensate stewards, safety and health committee representatives, and others for such work because they see it as adding value to their organizations. As explained in the 2010 NPRM, a number of states require the establishment of joint labor-management safety and health committees. 75 FR 48424. Having employees serve on employee assistance programs and wellness committees is also seen as a cost-effective business decision by many employers. 
                        <E T="03">Id.</E>
                         The Department concurs with those commenters who stated that union leave and no docking arrangements increase the speed of grievance adjustments, and otherwise benefit labor-management relations. The Department does not view the section 202 reporting provisions as requiring the reporting of such mutually beneficial arrangements between employers and employees.
                    </P>
                    <P>
                        Regarding the Department's characterization of the reporting burden as “substantial,” the union commenters generally agreed with this assessment. However, some public policy groups disagreed, with one focusing upon the 250-hour threshold.
                        <SU>16</SU>
                        <FTREF/>
                         As discussed 
                        <PRTPAGE P="66454"/>
                        below, such burden is substantial, even with the 250-hour exemption.
                    </P>
                    <FTNT>
                        <P>
                            <SU>16</SU>
                             The Department also disagrees with the comments regarding the significance of the 250-hour threshold, as it is not clear why the number 
                            <PRTPAGE/>
                            of hours worked pursuant to a union leave or no docking arrangement affects a potential conflict of interest. See 
                            <E T="03">Caterpillar, Inc.</E>
                             v. 
                            <E T="03">UAW at 1056.,</E>
                             in which the majority questions why Congress would sanction multiple employees receiving less than eight hours per day of no-docking payments but would criminalize eight hours of union leave payments per day for a single employee.
                        </P>
                    </FTNT>
                    <P>
                        As noted above, one commenter criticized the Department's description of the burden associated with the 2007 rule, noting that the proposed rule reflected only a five-minute recordkeeping savings. This commenter overlooked that the significant number of union officials who would be excluded from filing under the proposed and final rules will be saved the 120-minute burden imposed by the 2007 rule and, for those who do file, the reporting burden has been reduced by 25 minutes. Further, the burden estimate for the 2007 rule only tracks the number of and burden upon 
                        <E T="03">respondents</E>
                         (
                        <E T="03">i.e.,</E>
                         filers) to the 2007 rule. As such, the 2007 rule did not include the number of and burden on union officials, stewards, and other union representatives who, although not reaching the 250-hour union leave threshold, would need to keep track of such hours to determine whether or not filing would be required for their union leave or no docking payments. See 75 FR 48424, n. 9. Moreover, the burden on respondents and non-respondents is heightened because such payments are not likely to generate a conflict of interest and may discourage individuals from serving as representatives for their fellow workers.
                    </P>
                    <P>Additionally, as articulated by some of the commenters, it may prove difficult for union officials and representatives to obtain information concerning benefit compensation from their employers in order to comply with the union leave and no docking reporting required under the 2007 rule. These practical problems faced by union officials, stewards, and other representatives in maintaining records necessary to meet the reporting burden placed on them were not fully considered in the 2007 rule. Unless the employer has a payroll reporting system that allows the union stewards to clock in and out every time they have to perform union work, the stewards would have to keep their own records. A member's work on behalf of the union is not always performed during a series of discrete intervals where it is easy to determine when union work begins and ends. Sometimes, such representatives will briefly engage in union work when a co-worker comes and speaks to the on-duty steward. Sometimes the conversation occurs when the representative is on the way to the break room or at lunch. Sometimes union work occurs during a work-related conversation with a supervisor or manager and a grievance question comes up. Thus, the amount of time required to perform steward and similar functions may vary significantly from day to day and week to week and is therefore not easy to predict. For example, in the building and construction trades, with its very mobile workforce and short-term employment on construction projects, stewards will change from job to job, not just from week to week.</P>
                    <P>
                        As the Department explained in the NPRM, there is no persuasive policy reason why union officials must report such union leave and no docking payments, and thus bear the burden of such reporting, while employers making such payments are under no similar obligation or burden. As stated in the NPRM, the Department has reexamined the policy underlying the current requirement and has concluded that the inconsistent application is unreasonable regarding the imposition of these reporting requirements on union officials but not employers. 75 FR 48423. The Department disagrees with the commenters' statement that, in making this determination, the Department was ignoring the structure and language of the statute. To the contrary, the Department's view is entirely consistent with the statute. The specific reference in section 203 excepting from reporting “payments of the kind referred to in section 302(c) of the [LMRA]” does not require that section 202 be read to mandate such reporting where such payments are received by an employee.
                        <SU>17</SU>
                        <FTREF/>
                         Indeed, there would appear to be no reason why such payments, regularly made by some employers in the ordinary course of conducting labor relations, would require union officials, as the recipients of such payments, to report their receipt but not require employers making the payments to report them. The commenters have provided no persuasive argument to counter this observation. Additionally, the instructions, as drafted, mitigate any concern that such payments are concealed from union members. Under the rule, union leave and no docking payments must be reported unless they are made pursuant to a collective bargaining agreement, or by custom and practice under a collective bargaining agreement, or by policy, custom, or practice without regard to an individual's position within the union.
                    </P>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             See LMRDA Interpretative Manual, at section 241.600. This section states that the reporting exceptions in section 203 do not affect the reporting by union officers and employees in section 202, “
                            <E T="03">where</E>
                             the applicable provision of section 202 does not provide a pertinent exception.” (emphasis added). Section 202, however, contains a pertinent exception: the bona fide employee exception.
                        </P>
                    </FTNT>
                    <P>Finally, the Department notes that a commenter suggested that the proposed change would create other potential consequences affecting election law, labor-management matters unrelated to the LMRDA, persuader activity reports under section 203 of the Act, and other matters involving public policy. The commenter did not fully explain its concerns, but it appears that some of these issues involve statutes over which the Department has no authority and that none of these concerns are material to the changes proposed by this rulemaking. While the discussion of other LMRDA provisions is obviously necessary to address some issues, this rule only addresses the scope of reporting required by union officers and employees pursuant to LMRDA section 202. As discussed below, other commenters have asked the Department to use this rulemaking to resolve issues that may arise under the Act's other reporting provisions. While these comments are helpful to the Department in identifying concerns among the various regulated communities and informing the Department about how it might best direct its compliance resources, the Department cannot resolve those concerns in this rule.</P>
                    <HD SOURCE="HD2">B. Coverage of Stewards and Similar Union Representatives Under Section 202</HD>
                    <P>
                        The Department is effectuating its proposal to return to its longstanding policy that union stewards and similar volunteer union representatives are not as a general rule covered by the Form LM-30 reporting requirements. A union steward is responsible for informing employees of their rights under the collective bargaining agreement and applicable law, investigating grievances filed by union members, representing union members in presenting those grievances to management, and otherwise enforcing the collective bargaining agreement. See generally Herman Erickson, 
                        <E T="03">The Steward's Role in the Union</E>
                         29-54 (1971).
                    </P>
                    <P>
                        As proposed in the NPRM, 75 FR 48423-25, and as articulated below, the Department rescinds the definition of “labor organization employee” in the 2007 Form LM-30 that extends Form LM-30 coverage to such union representatives and inserts the following language in the revised Form LM-30 
                        <PRTPAGE P="66455"/>
                        Instructions in Section II, Who Must File.
                        <SU>18</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             The definition of “labor organization employee” in the NPRM included the word “exclusively” prior to “as a union steward * * *”
                        </P>
                    </FTNT>
                    <EXTRACT>
                        <P>
                            For purposes of the Form LM-30, an individual who serves the union as a union steward or as a similar union representative, such as a member of a safety committee or a bargaining committee, is not considered to be an employee of the union 
                            <E T="03">by virtue of service in such capacity.</E>
                        </P>
                    </EXTRACT>
                    <P>In the final rule, the Department added the last phrase, in italics, for clarity. As explained in the NPRM, individuals serving as stewards or in other volunteer positions would be subject to the same reporting obligations as other officers and employees, if they are officers pursuant to their union's constitution or bylaws—an atypical situation—or otherwise qualify as a union employee. The italicized words better convey this point than the language proposed in the NPRM, which had used the adverb “exclusively” to qualify the statement.</P>
                    <P>In extending the union officer and employee reporting obligation to union stewards in the 2007 rule, the Department determined that a union steward receiving no docking or union leave payments would be considered to be a labor organization employee within the meaning of the Form LM-30. As stated in the preamble to that rule: “An individual who is paid by an employer to perform union work is an employee of the union if he or she is under the control of the union, while so engaged.” 72 FR at 36109. Stewards were deemed to be “labor organization employees” by virtue of their receiving union leave or no docking payments from an employer.</P>
                    <P>
                        As stated in the 2010 NPRM and upon further review, the Department believes that the 2007 rulemaking did not satisfactorily address or adequately support the expansion of the Form LM-30 reporting requirements to include stewards. Rather, the rule focused on the “bona fide employee” exception of section 202, which, as mentioned, was revised to require the reporting of no docking and union leave payments. (See the discussion above concerning this change to the “bona fide employee exception.”) The rule also provided, almost in passing, that stewards as well as union officers and employees needed to report such payments, based upon whether or not the official qualified as a bona fide employee of the payer-employer 
                        <E T="03">during the time for which payment was made.</E>
                         72 FR 36124. (emphasis added).
                    </P>
                    <P>Upon review and reconsideration, the Department took the position in the 2010 NPRM that the Form LM-30 reporting requirements should not be expanded to include stewards. As there noted, requiring “stewards” to file Form LM-30 reports as “employees,” solely on the basis of having received union leave, “no docking,” or “lost time” payments, raises policy, interpretative, and practical concerns.</P>
                    <P>
                        First, from a policy perspective, imposing obligations on union stewards and other volunteers (
                        <E T="03">e.g.,</E>
                         those who serve on health and safety, productivity improvement, and bargaining committees) intrudes in internal union affairs. Union stewards and other representatives perform valuable tasks and extending reporting requirements to them would significantly hamper union efforts to recruit and retain stewards and other representatives.
                    </P>
                    <P>Second, an examination of the text of the relevant provisions of Title II of the LMRDA suggests that Congress did not intend that stewards be considered to be union employees. While section 202 requires reporting from “every officer of a labor organization and every employee of a labor organization (other than an employee performing exclusively clerical or custodial services),” it does not require reporting from stewards. In contrast, however, Congress expressly required employer payments to stewards to be reportable, pursuant to section 203, subject to certain exceptions. The Department explained in the 2010 NPRM that the absence of similar language in section 202 is a strong indication of Congressional intent to exclude agents, stewards, and similar representatives from the prescribed reporting requirements. Additional support for this position can be gleaned from the LMRDA's legislative history, as explained in the NPRM. Congress, revealingly, did not include the term “stewards” in describing the regulated class established by section 202, despite inserting the term in other LMRDA sections, thus indicating that those members who serve as “shop stewards” are of a different category than “labor organization employees.” When Congress wanted financial payments made to stewards to be reported, it knew how to do so.</P>
                    <HD SOURCE="HD3">1. Review of Comments Received</HD>
                    <P>The Department received 16 comments that specifically addressed this particular issue. Of these 16 comments, 13 supported the return to the historical interpretation that such individuals are not considered union employees for reporting purposes under section 202, 12 unions, and one law firm. Three comments opposed the change, including a public policy group, a legal defense foundation, as well as 225 individuals who sent in a form letter.</P>
                    <HD SOURCE="HD3">a. Comments in Support of NPRM</HD>
                    <P>There were 13 comments in support of the proposal to rescind required reporting by union stewards. A federation of labor unions stated that the 2007 rule significantly increased the universe of potential filers, noting especially the addition of stewards and other “on-the-job union representatives,” as employees of the union. In the commenter's view, this imposed Form LM-30 requirements on “tens of thousands of union members who voluntarily” perform representation functions for fellow workers during the regular workday.</P>
                    <P>An international union supported the Department's view that steward reporting is not required based on legislative intent. The commenter stressed the NPRM's analysis of the structure of the LMRDA, which recognized that “stewards” are not included in section 202, as well as the legislative history and intent, such as a prior draft of section 202 that specified their inclusion. The commenter characterized the removal of stewards reporting to be “reasonable” and consistent with the intent of the Act, and agreed that the inclusion of stewards would hinder members' willingness to volunteer to serve their fellow workers and would be a loss to labor-management relations.</P>
                    <P>A national union stated that subjecting stewards to the reporting requirements would discourage employees from volunteering to serve in that capacity. Another national union also maintained that the 2007 rule greatly expanded the Form LM-30 reporting requirements, and stated that stewards are members who volunteer to “play a key role” in ensuring smooth workplace operations. Thus, they should be “encouraged” to serve the union and not “punished with onerous reporting.”</P>
                    <P>
                        An international union emphasized that requiring stewards to file the Form LM-30 would discourage members from serving in this important position. Further, according to the commenter, stewards benefit management as well as the employees and the union, and removing them from potential reporting obligations furthers labor-management relations. The commenter expressed its view that the Department should not discourage this involvement. Another international union stressed that this change in steward coverage “will end considerable confusion” over the 
                        <PRTPAGE P="66456"/>
                        reporting requirements, which, combined with the burden associated with the form, has, in the commenter's experience, “deterred aspirants” for steward and similar volunteer positions crucial for unions and the workplace.
                    </P>
                    <P>A national union described stewards and similar positions as “voluntary, unpaid positions” that are filled by members who are not officers or employees of the union. Stewards generally handle grievances during breaks or before or after their regular working hours, while they also often receive union leave or no docking payments for union work during the employer's time. Regardless, the commenter contended that imposing coverage on such individuals would “seriously undermine cooperative labor-management relations and productivity.” Not only would individuals be discouraged from volunteering to serve, but those that do may be deterred from doing so during work hours, delaying grievance adjustments.</P>
                    <P>Some union commenters acknowledged that individuals who are union stewards may be required to report “in the unusual circumstances” when the steward is a constitutional officer position, is a paid position in the union, or is an employee of the union under circumstances distinct from his or her status as steward.</P>
                    <P>Further, a law firm also agreed with the Department's view as stated in the NPRM that, if Congress had intended that stewards would be subject to the reporting requirements of section 202, it would have indicated that intention in fashioning the terms of section 202 as it did under section 203. In contrast to section 202, employers are required by the express terms of section 203 to report payments made to stewards.</P>
                    <HD SOURCE="HD3">b. Comments in Opposition to NPRM</HD>
                    <P>In response to the NPRM, OLMS received a form letter signed by 225 individuals in opposition to the Department's proposal. The letter stated that stewards are an “essential part of union representation,” elected by coworkers, to “responsible positions,” and have the status of a “union official.” The letter also noted that because most stewards receive no compensation for performing their duties, they may be more sensitive to other forms of reward, suggesting to these individuals the need for conflict-of-interest reporting by stewards.</P>
                    <P>A few public policy groups also opposed the Department's proposal to rescind the general reporting requirement for stewards. One public policy organization agreed with the Department insofar as union leave and no-docking payments are concerned, but it argued that the NPRM went too far in exempting stewards and similar representatives from all reporting. This commenter stated that these union representatives should report all income received directly or indirectly from employers that is not related to their representation role, such as payments received for mowing the lawn of a management representative or painting the representative's house.</P>
                    <P>
                        Finally, a public policy group claimed, without elaborating, that most stewards perform functions of union officers and therefore are “officers” within the meaning of the LMRDA required to report pursuant to LMRDA section 202.
                        <SU>19</SU>
                        <FTREF/>
                         Moreover, the commenter contended that the Department has no authority to exempt from coverage of the Act as many as 80,000 individuals who, in its view, are covered by the reporting provisions of section 202; this commenter also concurred with the view that stewards are union employees.
                    </P>
                    <FTNT>
                        <P>
                            <SU>19</SU>
                             
                        </P>
                        The commenter further argued that if the Department classifies stewards as “essentially employees of an employer,” then agency fee payers would have no union fees to pay. The commenter offers no further explanation for its conclusion, which is not self-evident. However, as the Department has noted in a previous rule, the Department does not regulate payments by agency fee payers or reports prepared by unions showing how they compute costs that are allocated to agency fee payers. See 68 FR 58395.
                    </FTNT>
                    <HD SOURCE="HD3">2. Response to Comments</HD>
                    <P>The Department concurs with the comments affirming the central and important role that stewards and similar union representatives play in the labor-management context. As stated by many of the commenters, stewards and similar union representatives differ from union officers and employees in that they are union members who volunteer portions of their time to union representation without additional compensation. Additionally, unlike officers, stewards are often appointed; in many construction unions, they are appointed (or removed) by the Business Manager of the local union. Stewards, safety and health, and bargaining committee members are typically created and empowered by the collective bargaining agreement, not by the union's constitution and by-laws. Additionally, the Department concurs with the numerous commenters who confirmed the Department's position in the NPRM that imposing obligations on union stewards and other volunteers may also significantly intrude in internal union affairs and labor-management relations.</P>
                    <P>The Department also concurs with the unions that stated that the 2007 rule increased burden on stewards, in part, through the confusion surrounding their coverage, thus also significantly intruding in internal union affairs and labor-management relations. Although the 2007 rule denied such a chilling effect would be created, the Department has reconsidered this position. The Department has concluded that the impact on those who would have to file, coupled with the confusion and uncertainty created by extending all of the Form LM-30 reporting obligations to stewards and similar union representatives—even for those that actually had no payments or interests to report—invariably would dissuade some individuals from continuing in, or later volunteering for, those positions. Moreover, independent of the reporting required by the 2007 rule, union stewards and other representatives perform valuable tasks and extending onerous reporting requirements to them would “chill” future offers to serve. Imposing reporting burdens on such individuals clearly will temper the willingness of individuals to volunteer to serve in such positions—a loss to the union, the employer, and these individuals' fellow employees, as well as to the effective conduct of labor-management relations.</P>
                    <P>Section 202 does not refer to stewards as union officers or employees. Because other sections of the LMRDA expressly apply to stewards, the Department views their omission from section 202 as an intention to exclude them from its application. As noted in the NPRM, 75 FR 48424, employers must report payments to stewards pursuant to section 203; and stewards are explicitly covered by the fiduciary responsibilities provision of section 501 and the bonding provisions of section 502. The Department acknowledges the central role that stewards play and responsibilities that they exhibit within labor organizations, as demonstrated by the provisions of the LMRDA that apply to them. However, as stated, the statutory structure indicates that Congress deliberately did not apply the section 202 requirements to stewards, presumably because it did not want to unduly interfere with legitimate labor-management relations.</P>
                    <P>
                        Furthermore, the statute provides for disclosure of payments to stewards without imposing reporting obligations on the stewards themselves. Section 203 of the statute requires employers to disclose any payment, subject to certain exemptions, to any “officer, agent, shop steward, or other representative of a labor organization.” Thus, the concerns 
                        <PRTPAGE P="66457"/>
                        of the commenter that was troubled by the prospect that payments to stewards other than those for no docking or union leave would be undisclosed are unwarranted.
                    </P>
                    <P>The Department disagrees with the comment that most union stewards necessarily must be considered union officers and, as such, required to file reports pursuant to section 202. The Act defines union officers as “any constitutional officer * * * and any member of [the union's executive board or similar governing body.” LMRDA, section 3(n). As noted earlier, a steward generally is responsible for informing employees of their rights under a collective bargaining agreement, investigating and presenting grievances, and otherwise enforcing the collective bargaining agreement. These are not executive responsibilities normally associated with union officer positions, as described in union constitutions and bylaws; rather, they draw their essence from the collective bargaining agreement. In unusual situations, the position of steward is a constitutional office in the union (or is authorized to perform the functions of an officer). In other instances, an individual, although serving as a steward, is an employee of the union under circumstances distinct from his or her status as steward. In those circumstances, such individuals, both historically and under this rule, are subject to the reporting requirements of the Form LM-30, as union officers or union employees. The Department notes that several union commenters concurred with this position as well.</P>
                    <P>Finally, the Department disagrees with the suggestion that the Secretary's proposal is inconsistent with the Act and that the Department, in effect, lacks discretion to disregard what the commenter views as the clear command that stewards are employees of the union when they act on the union's behalf. Until the 2007 rule, stewards had not been required to file reports under section 202, and the 2007 rule was based on an interpretation of the ambiguous statutory term “labor organization employee.” 72 FR 36144. The rule did not claim that coverage of stewards was required by the terms of the statute, and indeed it did not place coverage of stewards in the category of revoked “administrative exceptions.” 72 FR 36156.</P>
                    <P>The structure of section 202, itself, demonstrates that Congress did not intend that stewards be considered to be union employees by virtue of service in such capacity. Again, the position of `steward' is not enumerated in section 202 as it is in other provisions of the statute. No commenter challenged this view of the statutory language, and several comments supported it. Rather, under section 202, only union employees and officers are required to submit reports. In sum, for the reasons stated in the NPRM and earlier in this preamble, stewards and other volunteers, as a general rule, are neither officers nor employees of a union. The commenters offer no persuasive argument that the Department has departed from the Act's reporting mandates.</P>
                    <HD SOURCE="HD2">C. Reporting of Loans and Other Transactions With Credit Institutions</HD>
                    <P>This rule effectuates the Department's proposal to amend the Form LM-30 to exempt from reporting marketplace transactions with bona fide credit institutions, including loans, interest, dividends, and payments and credit extended through credit card transactions, provided that they are arm's length transactions in accordance with usual business practice. In so doing, the Department establishes the appropriate balance between privacy and disclosure intended under the LMRDA—to disclose only a union official's actual or potential conflicts of interests, while keeping private bona fide investments “because they are not matters of public concern.” Senate Report, at 15, reprinted in 1 Leg. History, at 411. See 75 FR 48425.</P>
                    <P>
                        The 2007 rule established the general requirement that union officials report the details of any loan received from any business that deals with the official's union, the union's trust, or represented employer (in substantial part). 72 FR at 36133-38. This aspect of the rule engendered strong protests from union officials and some segments of the financial services industry as intrusive and unduly complex. Thus, shortly after the rule's publication, the Department issued guidance to reduce the complexity in the rule and the confusion about its requirements. The Department issued this guidance through a series of Form LM-30 Frequently Asked Questions (FAQs), posted on the Department's Web site,
                        <SU>20</SU>
                        <FTREF/>
                         which identified several kinds of payments from credit institutions that did not require reporting so long as they were arm's length transactions in accordance with usual business practice. These payments included interest and dividends involving savings and checking accounts and certificates of deposit and credit card arrangements.
                    </P>
                    <FTNT>
                        <P>
                            <SU>20</SU>
                             
                            <E T="03">http://www.dol.gov/olms/regs/compliance/RevisedLM30_FAQ.htm.</E>
                             FAQs 70-73 deal with issues surrounding payments from credit institutions. FAQ 70 stated, in part, that union officials do not need to report “credit card transactions (including unpaid balances) and interest and dividends paid on savings accounts, checking accounts or certificates of deposit if the payments and transactions are based upon the credit institution's own criteria and are made on terms unrelated to the official's status in the labor organization.” FAQs 71 and 72 outlined the obligations of union officials regarding home loans, which clarified that such loans must be reported if received from a trust in which the official's union is interested, a business that deals with the official's union or a trust in which the union has an interest, or a business a substantial part of which deals with an employer the official's union represents or is actively seeking to represent. Finally, FAQ 73 affirmed that the de minimis exemption applies to transactions, interests, and dividends from a financial institution, even if it had dealings with the official's union.
                        </P>
                    </FTNT>
                    <P>
                        In the 2010 NPRM, the Department explained that the 2007 rule reflected a policy choice in favor of the disclosure of information, even without a showing of a likely conflict of interest, and even with the risks concerning burden upon and intrusion into the private affairs of union officials. 75 FR 48425. In the 2010 NPRM, the Department further explained that it may not have given sufficient weight in fashioning the 2007 rule to Congress's concern that the LMRDA should not unnecessarily regulate unions and their officials, and that the burden of reporting such routine transactions would outweigh the value of any additional information disclosed. 
                        <E T="03">Id.</E>
                    </P>
                    <P>
                        The Department explained that loans and other transactions made on market terms are usual, regular transactions, unrelated to the officials' status in the union, and are therefore unlikely to pose a conflict of interest with the officials' duties to the union. 75 FR 48426. In contrast to these loans and transactions, a loan, gift, or other benefit obtained from a transaction other than at arm's length provides the union official with a net monetary gain, and consequently a potential motive to deal with a business in a way contrary to the interests of the union. Thus, the Department concluded that the better policy is to require the reporting of loans and other bona fide financial transactions from a credit institution only where the transaction is on other than market terms. 
                        <E T="03">Id.</E>
                    </P>
                    <P>
                        Furthermore, as discussed in the NPRM, the proposed bona fide financial transaction reporting exemption under sections 202(a)(3) and (4) would prevent the submission of superfluous reports that would overwhelm the public with unnecessary information, thus impeding the discovery of true conflict-of-interest payments. 75 FR 48425. The proposal also would prevent unnecessary burdens on union officers and employees and avoid interference with the privacy of such officials. 
                        <E T="03">Id.</E>
                        <PRTPAGE P="66458"/>
                    </P>
                    <P>Additionally, the Department there explained, at 75 FR 48426, that in the 2007 rule the Department excepted from reporting under section 202(a)(6) such bona fide financial transactions with a credit institution because of the burden associated with reporting what “are among the most common financial transactions undertaken by individuals.” 72 FR 36118. The NPRM stated the Department's belief that this reasoning also must apply to the reporting of marketplace loan transactions under sections 202(a)(3) and (4). 75 FR 48426.</P>
                    <P>
                        The NPRM explained that the proposed revision was limited to bona fide loans from legitimate credit institutions. 75 FR 48426. The Department has not changed other longstanding interpretations of section 202 that require union officers and employees to report other payments from vendors, service providers, credit institutions, and other businesses that deal in substantial part with the represented employer or in any part with either the official's union or any trust in which the official's union is interested or loans received from employers or businesses that are not credit institutions.
                        <SU>21</SU>
                        <FTREF/>
                          
                        <E T="03">Id.</E>
                         As explained below, the Department has determined to adopt, without change, the position set forth in the NPRM regarding bona fide financial transactions with credit institutions on Part B of the revised Form LM-30:
                    </P>
                    <FTNT>
                        <P>
                            <SU>21</SU>
                             
                        </P>
                        As stated in the 2010 NPRM:
                        <P>The proposed modification does not relax the obligation to report on loans or other financial transactions (including credit card arrangements and interest-bearing accounts) where a union official receives terms more favorable than the market allows, where for example a union official receives a loan because of the official's status despite a credit history that would normally prevent an individual from receiving credit, or payments on the loan are extended or forgiven because of preferential treatment as a union official.</P>
                        <P>75 FR 48426, n. 11.</P>
                    </FTNT>
                    <P>
                        <E T="03">Bona fide loans.</E>
                         Do not report bona fide loans, including mortgages, received from national or state banks, credit unions, savings or loan associations, insurance companies, or other bona fide credit institutions, if the loans are based upon the credit institution's own criteria and made on terms unrelated to the official's status in the labor organization. Additionally, do not report other marketplace transactions with such bona fide credit institutions, such as credit card transactions (including unpaid balances) and interest and dividends paid on savings accounts, checking accounts or certificates of deposit if the payments and transactions are based upon the credit institution's own criteria and are made on terms unrelated to the official's status in the labor organization.
                    </P>
                    <HD SOURCE="HD3">1. Review of Comments Submitted Concerning the Proposed Changes to the Reporting of Loans Under LMRDA Sections 202(a)(3) and (4)</HD>
                    <P>The Department received 14 comments about the proposed exemption regarding the reporting of loans. Of these 14 comments, two were from public policy organizations, 11 were from national/international unions, and one comment was from a federation of international labor unions.</P>
                    <HD SOURCE="HD3">a. Comments in Support of the Proposed Exemption Regarding Reporting of Loans</HD>
                    <P>Comments submitted by all eleven national/international unions and the federation of international labor unions supported the Department's proposal to exempt the reporting of bona fide market rate loans from credit institutions. There comments expressed many common themes, including union officials' right to privacy in personal, routine financial matters unrelated to their union role, the undue burden associated with reporting bona fide arm's length transactions, and the absence of any link between these transactions and conflict-of-interest concerns.</P>
                    <P>Three commenters agreed that the Department's proposal achieves a correct balance between the privacy of union officers and employees and the Act's goal of disclosing actual or potential conflicts of interest. Another commenter stated that the requirements established by the 2007 rule (apparently as distinct from the interpretation in the FAQs) “intru[des] into [union officials'] private affairs, and would produce information which is irrelevant to their union duties and the purposes of the LMRDA.” As expressed by another commenter, the 2007 rule's “broad requirement does not comport with the Act's intent to require only the disclosure of transactions in which there is actual or potential conflict of interest with an official's duties to his/her union and delves into personal matters that are of absolutely no public concern.”</P>
                    <P>Another commenter noted a parallel between the Department's proposal and the approach used in other “ethics regimes,” such as the financial disclosure rules established by each body of Congress. It explained that Congress does not require its members to report on loans that are made on terms generally available to the public, and that it made sense to treat similarly loans made to union officials on such terms.</P>
                    <HD SOURCE="HD3">b. Comments Opposing the Proposed Section 202(a)(3) and (4) Exemption Regarding Reporting of Loans From Bona Fide Credit Institutions</HD>
                    <P>
                        The two public policy organizations disagreed with the Department's proposal, arguing that such loans should be disclosed by union officials on the Form LM-30. One of these organizations stated that “the fear that seemingly private mortgage information will somehow become public due to the reporting requirements of the Form LM-30 is misplaced,” in that mortgages are public documents that can be obtained from a state recorder's office or, in some cases, accessed online. The same commenter addressed the Department's statement in its proposal, 75 FR 48425, that its revised interpretation “would prevent the submission of superfluous reports that would overwhelm the public with unnecessary information,” expressing its view that this concern is misplaced due to the technological developments of the 21st century. It characterized the Department's view as meaning that “more information actually means less useful information.” The commenter added that OLMS computer systems could easily handle all Form LM-30 reports, and allow cross-checking other forms, and stated that the public can view Form LM-30 data on 
                        <E T="03">http://www.unionreports.gov</E>
                         to “find whatever information they seek.”
                    </P>
                    <P>
                        Another public policy organization commented that the Department's proposed administrative exemption for bona fide loans with terms no more favorable than those available to the public “misses the point of disclosure and the need for it.” The commenter added that, while the loan terms may not be more favorable than those available to the public, there is no “guarantee that the loan was given to a qualified individual union official (
                        <E T="03">e.g.,</E>
                         the union official may have a very low credit score or income insufficient to make the payments).” The commenter also stated that “union officers have been known to have their loans completely forgiven or paid off by another source,” and added, “* * * if there is no disclosure of the loan, then no one will know that a loan should perhaps not have been given or even that a possibly questionable loan exists.” Additionally, this commenter referenced a media report concerning a public official's “special loan” arrangements with a particular mortgage company, asserting that just as voters benefit from such disclosure, union 
                        <PRTPAGE P="66459"/>
                        members would benefit from the disclosure of such loans.
                    </P>
                    <HD SOURCE="HD3">c. Other Comments</HD>
                    <P>Although the Department did not propose to eliminate the requirement that a union official must report loans from a represented employer that is a credit institution, such as a bank whose employees are represented by the official's union, some commenters submitted comments requesting the elimination of this requirement. Such a request is beyond the scope of this rule, but the Department, for completeness, discusses these comments below.</P>
                    <P>
                        A federation of international labor unions urged the Department to create a reporting exemption, under section 202(a)(5) of the LMRDA, for bona fide loans and other bona fide financial transactions between a union official and a credit institution employer whose employees the official's union represents or is actively seeking to represent. An international union concurred with this request. These unions argued that by not applying the same arm's length exemption, as proposed generally in the 2010 NPRM,
                        <SU>22</SU>
                        <FTREF/>
                         to transactions involving credit institutions whose employees are represented by an official's union, the Department would be ignoring the regular course of business exemption in section 202(a)(5), which they assert relieves any reporting on any “regular course of business” transactions.
                        <SU>23</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>22</SU>
                             Union officials must report, pursuant to section 202(a)(5), “any direct or indirect business transaction or arrangement between him or his spouse or minor child and any employer whose employees his organization represents or is actively seeking to represent, except work performed and payments and benefits received as a bona fide employee of such employer and except purchases and sales of goods or services in the regular course of business at prices generally available to any employee of such employer.”
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>23</SU>
                             The commenter notes correctly that the Department did not address its section 202(a)(5) argument in the 2010 NPRM. The Department there noted that any loans from an employer represented by the official's union (or whose employees it actively seeks to represent) must be reported pursuant to section 202(a)(2) of the LMRDA—including bona fide loans from a credit institution employer. See 75 FR 48426., n. 11.
                        </P>
                    </FTNT>
                    <P>The commenter asserted that the section 202(a)(5) marketplace transactions exemption should be applied to bona fide financial transactions with credit institutions. The commenter argued that the Department should give effect to what it sees as the same statutory interests involving routine transactions that would otherwise be reportable under other provisions of section 202. The commenter relied, in part, on its general reading of the Act's legislative history, which it reads to express an intention by Congress to not discourage any arm's length business transactions, which are not “questionable in nature,” illegal, or pose actual or potential conflicts of interests. This, according to the commenter, would also impose a significant burden on union officials whose unions represent or seek to represent employees of credit institutions. The commenter also stated that bona fide loans and other bona fide financial transactions between a credit institution employer and a union official are not reportable by the credit institution employer under section 203, citing the LMRA section 302(c)(3) exemption, 29 U.S.C. 186(c)(3). The commenter argues that, since credit institution employers are not required to report such loans and transactions on the Form LM-10 (Employer Report), then union officials should not be required to report such loans and transactions on Form LM-30.</P>
                    <HD SOURCE="HD3">1. Response to Comments</HD>
                    <P>
                        Upon consideration of the comments received on this issue, the Department has determined to revise the reporting obligation for union officials by adopting an exemption to the reporting of bona fide loans and other financial transactions made on market terms with credit institutions. In the Department's view, loans made on market terms are of little or no interest to union members, yet they disclose to members and the general public matters about which union officials, no less than other individuals, have a legitimate expectation of privacy.
                        <SU>24</SU>
                        <FTREF/>
                         But for the Department's guidance and the position adopted in today's rule, a union official would have to report each mortgage or other bank loan received from any credit institution that deals with his union, a section 3(l) trust, or, in substantial part, with the represented employer. In the Department's view, the burden associated with such requirement would far outweigh the value of any information disclosed. In the 2007 rule, the Department excepted from reporting under section 202(a)(6) arm's length loans, interest, and dividends earned during the regular course of business with a credit institution, because of the burden associated with reporting what “are among the most common financial transactions undertaken by individuals.” 72 FR 36118. The Department believes that this reasoning also must apply to the reporting of marketplace loan transactions under sections 202(a)(3) and (4).
                    </P>
                    <FTNT>
                        <P>
                            <SU>24</SU>
                             As discussed in the text, the proposed modification does not relax the obligation to report on loans or other financial transactions (including credit card arrangements and interest-bearing accounts) where a union official receives terms more favorable than the market allows, where for example a union official receives a loan because of the official's status despite a credit history that would normally prevent an individual from receiving credit, or payments on the loan are extended or forgiven because of preferential treatment as a union official. Moreover, loans received from employers or businesses that are not financial institutions will have to be reported as will any loans on other than market terms from employers or businesses that have a relationship with the official's union.
                        </P>
                    </FTNT>
                    <P>The Department notes that union commenters agreed with the approach proposed in the 2010 NPRM, as well as the supporting rationale the Department offered. These commenters agreed that any benefit associated with disclosing arm's length transactions was heavily outweighed by the burden, loss of privacy, and limited utility that such disclosure would entail.</P>
                    <P>Only two policy organizations submitted comments in opposition to the proposal. One asserted that the Department had overstated the impact that the rule would have on an official's privacy. In this regard, it asserted that some of the same personal financial data that would be reported under the terms of the 2007 rule, such as mortgage information, may already be accessible to the public. However, the Department notes in response to this comment that such information is not made public in a reporting regime intended to disclose actual or potential conflicts of interest, as would be the case with the Form LM-30. That some mortgage information may be available publicly by people with easy access to that data does not excuse the intrusion that results from making public what most people still consider to be private financial information. Requiring a union official to collect and, in effect, publish all such information in the Form LM-30 certainly magnifies the intrusion. Further, that certain financial information can already be accessed by the public does not justify requiring that such information be reported on Form LM-30. Moreover, as discussed, the reporting of routine bona fide loans and similar transactions does not advance the disclosure purposes served by section 202 and therefore the burden associated with such reporting is not warranted.</P>
                    <P>
                        One commenter stated that the Department was mistaken in its view that requiring bona fide loan-type information to be reported on the Form LM-30 could impede the utility of the form to union members and the public. The commenter pointed out that the Department's Form LM-30 Web site employs technology allowing data to be effectively managed and searched. The Department does not disagree with this 
                        <PRTPAGE P="66460"/>
                        characterization of the efficiency of the OLMS Web site, but this observation is not relevant to the issue presented in the NPRM, as the Form LM-30 does not require general financial disclosure. Rather, its purpose is to highlight actual or potential conflicts of interest involving union officials. Thus, collecting large amounts of information with little or no utility can obscure other information concerning possible or actual conflicts of interest, as each report submitted must be searched separately in order to find information relevant to actual or potential conflicts of interest. Intermixing meaningful reports with thousands of innocuous reports impedes easy review of the reports that disclose actual or potential conflicts. Eliminating superfluous information removes an unnecessary burden on union officials and promotes the objective of section 202 to disclose actual and potential conflicts of interests.
                    </P>
                    <P>The commenters expressed understandable concern that any loans or other transactions with terms preferential to union officials be reported. The Department's proposal, however, ensures that any such loans will be disclosed. Only loans and other transactions that reflect market rates are excepted from reporting. These transactions do not carry with them any indicia of a conflict, actual or apparent, between the union official and his or her duty to the union. As discussed in the 2010 NPRM and expressly stated in the Form LM-30 instructions, transactions not “based upon the credit institution's own criteria,” according to “usual business practice,” or “made on terms related to the official's status in the labor organization” must be reported on the revised Form LM-30. For example, if a loan is given to a union official with a low credit score, if a loan is extended or forgiven, if the loan does not reflect market terms, including usual fees, or if it otherwise evinces preferential treatment based upon the officials' union status, it must be reported. Any relaxation of the loan's terms, repayment requirements, or forgiveness must also be reported if based on preferential treatment because of the official's union status. Furthermore, loans received from employers or businesses that are not credit institutions must be reported. The same considerations apply to other transactions with credit institutions, including credit cards and interest-bearing accounts.</P>
                    <P>
                        Finally, as noted, two commenters requested the Department to exempt from reporting loans and related transactions from credit institutions that are represented employers. Because the Department did not propose to eliminate this requirement, no extensive discussion is required. As noted in the NPRM, the Department acknowledged that it was not changing this aspect of the 2007 rule. Further, the Department notes that, historically, the Department has held that any loan to an official from an employer whose employees are represented by the official's union are reportable pursuant to 202(a)(2), without any statutory or other exceptions (other than the de minimis threshold). See IM sections 244.100 and 244.120; see also the pre-2007 Form LM-30 Instructions, Part A, exemption (iii).
                        <SU>25</SU>
                        <FTREF/>
                         The 2007 rule upheld this principle, and the Department stated in the preamble to the 2010 NPRM that a union official would need to report any loans from an employer represented by the official's union (or whose employees it actively seeks to represent).” See 75 FR at 48426 n. 11. Additionally, the Department notes that the appearance of a conflict of interest and any temptation to curry favor by offering what appears to be an arm's length loan or related transaction on favored terms is much greater where the official's union represents (or seeks to represent) the institution's employees than where a loan is made by an institution that has a more attenuated relationship with the official's union.
                    </P>
                    <FTNT>
                        <P>
                            <SU>25</SU>
                             The exemption (iii) of Part A of the pre-2007 Form LM-30 Instructions exempts transactions “involving purchases and sales of goods and services in the regular course of business at prices generally available to any employee of the employer. This does not apply to transactions involving stocks, bonds, securities, or loans, for example.”
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">D. Scope of Reporting Requirements Under Section 202(a)(6)</HD>
                    <P>In the NPRM, the Department proposed to narrow the scope of reporting required under section 202(a)(6) with respect to (1) Payments from business competitors to the employer whose employees the union official's union represents or actively seeks to represent; (2) payments received from trusts; and (3) payments from unions. In this final rule, the Department has adopted its proposals on these points.</P>
                    <P>As explained in the NPRM, sections 202(a)(1)-(5) of the LMRDA establish conflict-of-interest reporting requirements concerning payments received by union officers and employees from two sets of entities: (1) Employers that a union represents or is actively seeking to represent; and (2) businesses, such as vendors and service providers, that buy or sell to the represented and potentially represented employers, the union official's union, or trusts in which the official's union is interested. In each case, the reporting obligation is triggered by the particular relationship between an official's union and the entity from which the official receives a payment or in which the official holds an interest.</P>
                    <P>
                        By contrast, section 202(a)(6) does not specify any relationship between an entity and an official's union, nor does it express when payments must be reported. Rather, it more broadly requires union officials to report any payment of money or other thing of value from “any employer or any person who acts as a labor relations consultant to an employer” (except payments of the kinds referred to in section 302(c) of the Labor Management Relations Act of 1947, as amended (LMRA)). As noted in the NPRM and discussed in the 2007 rule, the Department has long interpreted section 202(a)(6) as a “catch-all” that captures conflict-of-interest payments from employers not otherwise reportable in the previous five subsections of 202. Thus, LMRDA Interpretative Manual section 248.005 states, in part: “[Section] 202(a)(6) is designed for those situations which pose conflict-of-interest problems which are not covered in the previous five sections of 202.” 72 FR at 36129. Further, the 2007 rule made clear that section 202(a)(6) can be read to encompass disclosure of any employer payment that could present a financial conflict of interest for the union official. 
                        <E T="03">Id.</E>
                         The Department did not propose to change this requirement.
                    </P>
                    <P>
                        After a review of the comments received, the Department retains the general requirement, as earlier proposed, that officials report payments from employers and labor relations consultants from whom a payment would create an actual or potential conflict between the filer's personal financial interests and the interests of the filer's labor organization (or the filer's duties to the labor organization). As proposed, the Department included a non-exhaustive list in the instructions for the revised Form LM-30 of examples of such actual or potential conflicts of interest. These examples included payments from business competitors of the employer whose employees the union official's union represents or whose employees the union is actively seeking to represent. Further, to ensure that only actual or potential conflict-of-interest payments are reported, the Department has qualified this requirement so that a union official, as a general rule, must report such financial interests only if the official is 
                        <PRTPAGE P="66461"/>
                        involved with the union's organizing, collective bargaining, or contract administration activities or possesses significant authority or influence over such activities. As explained in the NPRM, an official will be required to report such payments where he or she possesses such authority or influence by virtue of his or her position, even if such authority has not been exercised. This rule also effectuates the proposal to retain the requirement that union officials must report payments received from an employer that is a not-for-profit organization that receives or is actively and directly soliciting (other than by mass mail, telephone bank, or mass media) money, donations, or contributions, from the official's labor organization.
                    </P>
                    <P>The Department is revising, as proposed, the reporting requirements insofar as payments from certain trusts and labor unions pursuant to section 202(a)(6) are concerned. In contrast to the 2007 rule, which required payments from trusts to be reported, the Department proposed to return to its historical position that such payments are not reportable because they do not pose an apparent or actual conflict of interest between the official's personal financial interests and his duty to the union and its members. As explained in the 2010 NPRM and based upon the considered analysis in the Department's 1967 opinion on this issue, the Department believed that these payments pose “no conflict with which Congress was concerned.” 75 FR 48428. Further, the Department believes, as stated in the NPRM, that the better reading of section 202(a)(6) of the LMRDA is that labor unions and trusts are not within the universe of “employers” from which union officials should report payments, as both entities are treated separately from other “employers” under the Act. In drafting the LMRDA reporting and disclosure requirements, Congress delineated separate requirements for these discrete statutory actors (unions and trusts), and reporting of labor organization disbursements is set forth in section 201 of the statute, not section 202. Moreover, the Department maintains that this reading of the statute better implements the labor union and labor-management reporting requirements of the LMRDA.</P>
                    <P>Finally, the Department also retains, as proposed, the requirement that union officials must report five types of payments received from an employer, regardless of the relationship the employer has with the filer's union. These reportable payments to a union official (or the official's spouse or minor child) from any employer or labor relations consultant to an employer are payments for the following purposes: (1) Not to organize employees; (2) to influence employees in any way with respect to their rights to organize; (3) to take any action with respect to the status of employees or others as members of a labor organization; (4) to take any action with respect to bargaining or dealing with employers whose employees the filer's union represents or whose employees the union is actively seeking to represent; and (5) to influence the outcome of an internal union election. 72 FR at 36128, 36173. These payments, per se, create an actual or potential conflict between the filer's financial interests and his or her duties to the labor organization.</P>
                    <P>
                        The Department received 15 comments on the scope of section 202(a)(6), with 12 supporting all of the changes,
                        <SU>26</SU>
                        <FTREF/>
                         one supporting the changes in part and opposing in part, and two comments opposing all of the proposed modifications to this aspect of the NPRM. The comments on specific aspects of the rule are addressed below.
                        <SU>27</SU>
                        <FTREF/>
                         As a preliminary matter, however, the Department believes it important to address the view expressed by two commenters that none of the proposed changes to reporting under section 202(a)(6) are justified.
                    </P>
                    <FTNT>
                        <P>
                            <SU>26</SU>
                             Seven of these commenters supported the proposed changes to the 2007 rule but also opposed other portions and thus suggested additional modifications to the form.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>27</SU>
                             Two commenters suggested that the Department should further revise the section 202(a)(6) requirements to limit reportable interests solely to those payments made by employers that would impact the labor-management relationship between a union and a represented employer. Thus, for example, they would exempt from reporting payments to a union official from a charity to which the official's union contributes. Because the Department did not propose such change, the comments are outside the scope of the rule. The Department briefly notes, however, that the suggestion is at odds with the general “catch-all” purpose of section 202(a)(6), would leave undisclosed conflicts of interest, and is not compelled by the language of section 202(a)(6) or the Act's structure.
                        </P>
                    </FTNT>
                    <P>In essence, these commenters read section 202(a)(6) as a mandate to require a union official to report on his or her financial interests with virtually all employers. The Department disagrees. It remains of the view that its interpretation is sound as a matter of law and policy. Granted, the terms of section 202(a)(6) are expansive, requiring a union official to report “any payment of money or other thing of value * * * which he or his spouse or minor child received directly or indirectly from any employer.” In contrast to the breadth of section 202(a)(6), however, each of the other paragraphs of section 202(a) addresses payments by particular employers or businesses that have dealings with the official's labor organization (202(a)(4)) or an employer whose employees are represented by the official's union or the union actively seeks to represent, (202(a)(1), (2), (3), (5)). The actual or potential conflict of interest for payments from and interests in such entities is evident.</P>
                    <P>The literal language of section 202(a)(6), if applied as the commenters advocate, would render superfluous the limiting language in the other subsections, as it would potentially require reporting from any entity that is an employer, regardless of whether or not the entity had any connection with the union and its represented employers. Given the absurdity of such construction, the Department, mindful of the statute's language and legislative history, has interpreted section 202(a)(6) as a “catch-all” provision, intended by Congress to capture various payments that would pose apparent conflicts of interest, even though outside the literal terms of subsections (a)(1)-(5). The Department has never interpreted this section in the way these two commenters apparently would prefer—as a mandate to require a union official to report on his or her financial interests from virtually all employers. The 2007 rule outlines this longstanding approach by the Department, 72 FR at 36128-30, and the Department has continued the same basic approach in this rulemaking, see 75 FR48426-29, 48434-35. As recognized in the 2007 rule and the 2010 NPRM, the Secretary must interpret the statute to clarify the intended reach of section 202(a)(6). 72 FR 36139-41; 75 FR 48429-30. Here, in contrast to the 2007 rule, the Secretary, in exercising her discretion to interpret that section, has concluded that it does not require union officials to report on certain payments received from employers that compete with represented employers, section 3(l) trusts, and labor organizations.</P>
                    <HD SOURCE="HD3">1. Obligation To Report Payments From Business Competitors of the Employer Whose Employees the Union Official's Union Represents or Whose Employees the Union Is Actively Seeking to Represent</HD>
                    <P>
                        As explained in the 2010 NPRM and reiterated here, the Department has historically viewed subsection 202(a)(6) differently than the other subsections of section 202(a). The relationships addressed in 202(a)(6), such as that between a union official and a competitor employer to a represented employer, are further removed from the 
                        <PRTPAGE P="66462"/>
                        activities of the union than those involving the represented employer and the other business relationships addressed in the first five subsections of section 202. In particular, the competitor employer does not have a current and ongoing relationship with the union; indeed, neither is actively seeking such a relationship (if it did, sections 202(a)(1), (2), and (5) would likely apply). Further, any payment made by a competitor or other employer to not organize or otherwise affect the union official's responsibilities with the union is per se reportable under Part C of the instructions. Moreover, the Department believes that in the outside chance that there could be a conflict concerning a union official and a competitor employer, the Department's “significant authority or influence” test, as shown in italics and discussed below, would ensure its reporting.
                    </P>
                    <P>The instructions to the Form LM-30, as revised in this rule, provide:</P>
                    <EXTRACT>
                        <P>
                            Complete Part C if you, your spouse, or your minor child received, directly or indirectly, any payment of money or other thing of value (including reimbursed expenses) from any employer (other than a Represented Employer under Part A or Business covered under Part B above) from whom a payment would create an actual or potential conflict between these 
                            <SU>28</SU>
                            <FTREF/>
                             financial interests and the interest of your labor organization or your duties to your labor organization. Such employers include, but are not limited to, an employer in competition with an employer whose employees your labor organization represents or whose employees your union is actively seeking to represent, 
                            <E T="03">if you are involved with the organizing, collective bargaining, or contract administration activities or possess significant authority or influence over such activities. You are deemed to have such authority and influence if you possess authority by virtue of your position, even if you did not become involved in these activities.</E>
                              
                        </P>
                    </EXTRACT>
                    <FTNT>
                        <P>
                            <SU>28</SU>
                             The NPRM stated, “between 
                            <E T="03">your</E>
                             financial interests * * *” The Department modified this phrase to read “between 
                            <E T="03">these</E>
                             financial interests,” so filers are aware that they must look at the payments and interests of their spouse and minor children as well as their own.
                        </P>
                    </FTNT>
                    <P>
                        An example illustrates the difference between the 2007 Form LM-30 and the narrower reporting requirement implemented here. First, assume that an individual employed by a union to handle computer problems also works for a technology company that is a competitor of a company whose employees are represented by the union. Under the 2007 rule, the individual would have to file a Form LM-30 to report gifts, gratuities, or other non-exempt payments he or she receives from the technology company.
                        <SU>29</SU>
                        <FTREF/>
                         Under this rule, the individual would not have to report these payments. In contrast, assume that an individual employed by a union as an organizer also works for a technology company that is a competitor of a company whose employees are represented by the union. Under both this rule and the 2007 rule, the individual would have to file a Form LM-30 to report gifts, gratuities, or other non-exempt payments he or she receives from the technology company.
                    </P>
                    <FTNT>
                        <P>
                            <SU>29</SU>
                             It should be noted that such employee would not be required to report his regular wages from the employer. LMRDA, section 202(a)(6), which exempts payments of the kinds referred to in LMRA section 302(c)(1), excepts these payments from reporting. A public policy organization, which offered general opposition to the proposed changes to the reporting of payments from competitor employers, noted that the NPRM indicated that the wages paid by the technology company would be reportable under the 2007 rule, and that this mistake cast doubt on the entire NPRM. The text has been clarified to make plain that regular wage payments are not to be reported.
                        </P>
                    </FTNT>
                    <P>
                        Multiple commenters offered support for the proposal. One national/international union supports the change as it reduces burden on officials and focuses reporting on actual or potential conflict-of-interest scenarios. With respect to burden, the commenter stressed the “layers” of subsidiaries and affiliates that must be researched to identify the represented employer's competitors in order to determine if reporting is required. Moreover, the commenter contended that this information may not be publicly available.
                        <SU>30</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>30</SU>
                             The concerns of the commenters pertaining to the level of “research” that must be conducted in order to determine what payments are reportable are unsubstantiated and exaggerated. As discussed in greater detail in the top-down reporting section of this preamble, III.E., the scope of the official's inquiry is limited to considering non-exempt, atypical payments received from an employer and only 
                            <E T="03">then</E>
                             must the official look at the relationship that the employer has with the official's union. Nevertheless, by limiting this aspect of reporting to officials that possess actual authority or influence over subordinate affiliates, the rule should ameliorate concerns among some filers.
                        </P>
                    </FTNT>
                    <P>One international union supported the change, but also suggested that it should be narrowed further to require reporting of a “gift” only when an official has “actual knowledge” of an employer being a competitor to a represented employer. It explained that such a change would reduce a filer's burden because it would be unnecessary to “research potentially complex chains of business ownerships through webs of subsidiaries and affiliates.” The Department does not concur with this suggestion, as determining if an official had actual knowledge would hinge reporting on a subjective assessment. Rather, a reporting obligation is triggered by objective circumstances that create an actual or potential conflict, or an appearance of one, and then, upon its disclosure, allows members and the public to assess the implications. As discussed in section V.C. of the preamble, the asserted burden associated with this aspect of the rule is overstated. As the Department explains in that section, the rule allows most filers to compile the necessary information through a relatively easy three-step process.</P>
                    <P>Two public interest organizations opposed the change. The first stated that restricting reporting to officials involved in organizing, collective bargaining, or contract administration is contrary to the statutory text and the views Congress expressed in the legislative history. The commenter maintained that this change would remove a “significant amount of disclosure by employers and union officials” who do not engage in these activities. Another public interest organization similarly questioned why the Department would limit reporting to situations “where an official is involved with organizing, collective bargaining,” or so forth, as proposed. The commenter argued that this limitation would run counter to the purposes of the Form LM-30, which is to disclose conflicts of interest, and it does not accurately reflect the administration of most unions, in which any payments to any official, regardless of the formal title, could “easily” influence all the others. The commenter stated that, “any representative in any capacity should be required to report relevant payments from any employer.”</P>
                    <P>
                        The Department disagrees with the contention that this change to section 202(a)(6) reporting is not based in the statute or is contrary to the legislative history. To the contrary, the Department has consistently held that section 202(a)(6) is a “catch-all” for conflicts of interests not otherwise captured in the previous subsections of section 202. The Department's interpretation is consistent with section 202(a)(6), its legislative history, and the purposes served by the Act's disclosure requirements. The Department's proposal, as adopted in the final rule, provides clear examples to the public as to what circumstances trigger reporting, without overburdening union officers and employees. It triggers reporting on the core, essential functions of a labor organization: organizing, collective bargaining, and contract administration. In this regard, the Department notes, contrary to the commenters' apparent suggestion, that the Congressional goal in enacting section 202 was not to require wholesale “disclosure by 
                        <PRTPAGE P="66463"/>
                        employers and union officials,” but, rather, 
                        <E T="03">conflict-of-interest</E>
                         disclosure; the revisions contained in this rule effectuate this purpose.
                    </P>
                    <P>
                        The restriction of reporting to those with influence over organizing and similar areas applies only to the broad “catch-all” provision of section 202(a)(6), and not to the other provisions of section 202. Indeed, pursuant to these other provisions, the Department will continue to require reporting by union officers and non-exempt employees of payments from represented employers and the enumerated businesses with close relationships with the officials' union.
                        <SU>31</SU>
                        <FTREF/>
                         However, the Department does not interpret section 202(a)(6) in the same manner, as a competitor employer is further removed in relationship to the union. The Department notes, though, that Part C of Form LM-30 still requires the reporting of 
                        <E T="03">any</E>
                         payment to 
                        <E T="03">any</E>
                         covered union officer or employee, 
                        <E T="03">if</E>
                         the payment constitutes a per se reportable activity, pursuant to the Revised Form LM-30 Instructions, Part C: Other Employer or Labor Relations Consultant (reportable per se activities). This position is consistent with the Department's longstanding approach treating the broad section 202(a)(6) language as a “catch-all” to capture 
                        <E T="03">likely</E>
                         conflict-of-interest payments not otherwise captured by sections 202(a)(1)-(5).
                    </P>
                    <FTNT>
                        <P>
                            <SU>31</SU>
                             The Department notes that, in interpreting the scope of “top-down” reporting, the Department is only requiring reporting by employees of intermediate and national/international unions of payments from and interests in entities with requisite relationships with lower-level unions, when such employees have significant authority or influence over such lower-level unions. See Part III.E. herein. The Department's approach here with respect to reporting interests in and payments from a competitor of a company whose employees are represented by the union is similar.
                        </P>
                    </FTNT>
                    <P>The Department also notes that a national union objected to the Department's general “catch-all” requirement, retained in the NPRM, that a union official must report any payment from an employer that creates an actual or potential conflict of interest. The commenter described the requirement as confusing and too broad. The commenter objected that the Department's proposal would require reporting of transactions that will have no effect on labor relations or union administration. In response to this comment, the Department cannot delineate every conceivable conflict-of-interest scenario, nor could Congress, which is why it established section 202(a)(6). Generally, entities from which payments are reportable are described in the instructions, and the Department will provide compliance assistance to filers with questions about specific circumstances.</P>
                    <HD SOURCE="HD3">2. Obligation To Report Payments Received From Trusts</HD>
                    <P>In the 2010 NPRM, the Department proposed to return to its longstanding interpretation that union officials are not required to report payments received from trusts in which their unions have an interest. These trusts are defined by section 3(l) of the LMRDA as a “trust or other fund or organization (1) That was created or established by a labor organization, or one or more of the trustees or one or more members of the governing body of which is selected or appointed by a labor organization, and (2) a primary purpose of which is to provide benefits for the members of such labor organization or their beneficiaries.” See Form LM-30 Instructions, p. 13.</P>
                    <P>As explained in the NPRM, this interpretation is reflected in a 1967 opinion signed by the head of OLMS's predecessor agency and the Department's Solicitor. As there stated:</P>
                    <EXTRACT>
                        <P>Congress was concerned with arrangements with the primary employer, that is, the one whose employees the union represents or seeks to represent, which might impair the union officer's loyalty as a representative of that organization [vis-à-vis] the employer. Even assuming that a trust fund could successfully be characterized as a primary employer, which we doubt, we fail to perceive the existence of a conflict where a union official received payments from a trust fund for which he also works, even if this arrangement is approved by employer representatives on the trust. The employer representatives are acting in their role as trustees and thus no conflict-of-interest situation with which Congress was concerned arises.</P>
                    </EXTRACT>
                    <P>
                        <E T="03">Id.,</E>
                         p. 4-5. As the letter notes, payments from trusts to union officers and employees—wages to employees or reimbursed expenses—are payments reported elsewhere and, more importantly, pose “no conflict with which Congress was concerned.” Kleiler-Donahue Ltr., p. 5.
                    </P>
                    <P>A federation of unions, eight national/international unions, and one law firm offered support for the Department's proposal regarding payments from trusts and its stated rationale in the NPRM. In particular, these commenters stressed that payments from section 3(l) trusts to union officials do not pose an actual or potential conflict of interest. One international union emphasized that such trusts are created to benefit the members and their beneficiaries, so a payment from the trust would not pose a conflict of interest for a union official. Another international union added that Congress did not intend union trusts to be treated as employers and other businesses under section 202(a)(6). An international union commented that reporting of expense reimbursements for serving as a trustee of a union benefit fund had never been required, expressing support for the Department's proposal to return to the former practice.</P>
                    <P>Further, one international union stated that the removal of such reporting would eliminate an inconsistency between what union trustees would report and management trustees were not required to report. An international union stressed that reimbursements to union trustees should not be reportable. Another international union offered two technical corrections to the revised Form LM-30 Instructions, in Part C, to make explicit that payments from trusts are not reportable. The Department will address these suggestions later in the preamble section on the revised form and instructions. See Part IV.</P>
                    <P>
                        Two commenters opposed the Department's proposal to eliminate the reporting of payments made by section 3(l) trusts to union officials.
                        <SU>32</SU>
                        <FTREF/>
                         A public interest organization asserted that the Department offered “no good reason” for the return to its “historical position”; that the Department had “found no problem that will be solved” by the modification; and that the proposal was “primarily based on a very old internal” opinion. This commenter, however, provided no basis for rejecting the Department's rationale, nor did it offer any rationale as support for the position taken in the 2007 rule. In the 2010 NPRM, the Department cited the Kleiler-Donahue letter to emphasize the longstanding nature of the position, as well as to explain the letter's reasoning. 75 FR 48428. To reiterate the point made in the NPRM, the preamble to the 2007 rule merely cited the letter without refuting it, and the Department now returns to the position and rationale stated in the letter. 72 FR 36154. Payments received from a section 3(l) trust do not establish a conflict of interest, as the interests of the trust and union, or an official's duties to the union, do not diverge. Indeed, a section 3(l) trust must exist for the primary 
                        <PRTPAGE P="66464"/>
                        purpose of providing benefits to the union members and their beneficiaries. Moreover, requiring Form LM-30 reporting in situations that do not pose a conflict of interest would be inconsistent with the balanced reporting regimen intended by Congress.
                    </P>
                    <FTNT>
                        <P>
                            <SU>32</SU>
                             These organizations also asserted that the Department's proposal as it applies to the reportability of payments to trusts and unions is inconsistent with the Act's language, its structure, and relevant case law. One of the commenters also asserted that the proposal was contrary to the position that the Department has taken in enforcement litigation under section 203 of the Act. Because these assertions are focused primarily on the Department's proposal to revise the reportability of certain payments from unions, these arguments are discussed in the section that follows in the text.
                        </P>
                    </FTNT>
                    <P>Another public interest organization opposed the proposed change contending that a conflict of interest arises and public disclosure is required when an entity spends lavishly on union officials. The comment cited examples of payments from several entities to union officials, including two from filed LM-30 reports that, it asserted, would not be disclosed under the Department's proposal.</P>
                    <P>
                        In response to this comment, the Department again emphasizes that section 202, and the Act as a whole, do not provide for general reporting of any payment by an employer, business, or trust to a union official that may have an undefined, arguable, or even subjective “disclosure value.” To be reportable, a payment must create a divergence between the financial interest of the official and the interests of the official's labor organization. See Revised Form LM-30 Instructions, Part C. Such circumstances do not generally arise regarding a section 3(l) trust, as the union and the trust have a common interest in ensuring that the trust operated for the benefit of their common beneficiaries, the union's members. With regard to the commenter's characterization of certain payments, this rulemaking is not the appropriate place for issuing determinations regarding disclosure in specific factual situations. However, as discussed below, there are reporting requirements that apply in situations such as those described by the commenter.
                        <SU>33</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>33</SU>
                             Although the commenter has identified information that may be of interest to union members, it has provided no information that indicates that those payments, in fact, pose a real or apparent conflict with the official's duty to his union. The information that the union reported just as readily evinces the symbiotic relationship that exists between the official's union and the trust and a unity of interest, rather than divided loyalty. Furthermore, the commenter provides no information to indicate that the reported information would be unavailable to members of the public through public documents required of the trust by other regulatory authorities such as the IRS or banking authorities. Moreover, compliance assistance, not this rulemaking, is the appropriate mechanism to address specific factual circumstances.
                        </P>
                    </FTNT>
                    <P>
                        First, full disclosure is required concerning the financial operations of certain entities previously considered to be section 3(l) trusts that are wholly owned, controlled, and financed by a single labor organization. These are “subsidiary organizations” of a labor organization, and the financial transactions of such subsidiaries would generally need to be reported on the labor organization's annual financial disclosure report, thus providing disclosure. See the Labor Organization Annual Report Form LM-2 Instructions, Section X 
                        <SU>34</SU>
                        <FTREF/>
                         and the Labor Organization Annual Report Form LM-3 Instructions, Section X. Second, although not covered by LMRDA section 202, many section 3(l) trusts, such as pension and welfare plans, including many Taft-Hartley plans, are covered by the Employee Retirement Income Security Act (ERISA), which provides reporting and disclosure requirements as well as other financial safeguards for employee benefit funds. Third, pursuant to a longstanding interpretation retained in the 2007 rule and this rule, while payments from a trust are not reportable by a union official on the revised Form LM-30, payments from and interests in any business that deals with the official's section 3(l) trust are reportable.
                    </P>
                    <FTNT>
                        <P>
                            <SU>34</SU>
                             The Department notes that reporting for subsidiary organizations on the Form LM-2, the annual financial disclosure form for the largest labor unions, was removed from the reporting requirements for that form as a result of revisions made in 2003. See 68 FR 58374 (Oct. 9, 2003). Subsequently, in 2010, the Department returned subsidiary reporting to the Form LM-2 reporting requirements for fiscal years beginning on or after January 1, 2011. See 75 FR 74936 (Dec. 1, 2010).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Obligation To Report Payments From Unions</HD>
                    <P>In the 2010 NPRM, the Department proposed to modify specific aspects of the general requirement that union officials report payments they received from labor organizations. 75 FR 48428. In support of the proposal, the Department relied on its statutory analysis of the Act's reporting provisions, concluding that section 202(a)(6) is better read as limited to payments by employers—distinct from labor unions—notwithstanding the acknowledgment, in discussing the reporting obligations of an official of a staff union, that a union may be an employer. 75 FR 48428-29. Further, as explained in the NPRM, the Department's proposal would not affect a staff union official's obligation to report payments he or she receives from a union-employer whose employees the official's union represents or actively seeks to represent.</P>
                    <P>The Department, in reconsidering the position taken on this question in the 2007 rule, has concluded that a better reading of the LMRDA is that a “labor organization” is distinct from an “employer,” as that term is used in section 202(a)(6). As stated in the NPRM:</P>
                    <EXTRACT>
                        <P>In drafting the LMRDA reporting and disclosure requirements, Congress mandated separate requirements for the discrete statutory actors: “labor organizations,” “labor organization officers” and “labor organization employees,” “employers,” “labor relations consultants,” and “trusts in which a labor organization is interested.” (While there are no reporting requirements for section 3(l) trusts, section 208 authorizes the Secretary to establish such requirements for labor organizations concerning such entities.) Further, the statute separately defined five of these six terms. See sections 3(e), 3(i), 3(l), 3(m), and 3(n) of the LMRDA. </P>
                    </EXTRACT>
                    <P>
                        In the Department's view, section 201 requires “labor organizations” to disclose, among other financial transactions and information, disbursements to many individuals and entities, including employers, businesses, their own officers and employees and, potentially, those of other labor organizations. Section 203, on the other hand, requires “employers” to file certain reports. As applied to section 202, “labor organization” officers and employees must report payments from “employers” and “businesses” that have established certain relationships with the official's “labor organization.” The statute's reporting provisions thus establish “employers” and “labor organizations” as distinct and separate entities. There is nothing in the statute that indicates that Congress intended, for reporting purposes, that the category of employers also would include labor organizations, or that Congress meant for officers and employees to report transactions with labor organizations acting as such. If Congress had intended that result, it seems apparent that in drafting section 202 it would have explicitly identified payments from labor organizations as reportable.
                        <SU>35</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>35</SU>
                             This reasoning is consistent with LMRDA Interpretative Manual section 260.005. This section provides that no report is required for activities performed by an attorney on behalf of a union (distinct from activities performed for an employer), even though the attorney meets the definition of “labor relations consultants” under section 3(m), because the only section of the Act which requires reports from labor relations consultants is section 203(b), which provides for reports from every person who has an agreement with an 
                            <E T="03">employer</E>
                             for certain purposes.
                        </P>
                    </FTNT>
                    <P>
                        The Department holds the view that this reading of the statute better implements the labor union and labor-management reporting requirements of the LMRDA. First, as stated above, conflict-of-interest payments from labor organization-employers represented by staff unions are reportable under sections 202(a)(1), (2), and (5). Second, the various reports required under section 201—Form LM-2, LM-3, and LM-4 Labor Organization Annual 
                        <PRTPAGE P="66465"/>
                        Reports—require all covered labor organizations to disclose any disbursements, including those to officers and employees of other unions. Such disbursements include those addressed in Part B, Schedule 3, Employer's Relationship 5(b)-(e), of the 2007 Form LM-30 that required filers to report payments from certain unions. See 72 FR 36163. All of these disbursements constitute payments from labor organizations in their capacity as the representative of employees, not as an employer of employees. A union member or a member of the public would naturally look to the labor organization's annual financial disclosure report, and not the Form LM-30 reports, to view disbursements from a particular union. Further, pursuant to section 201(c), union members can view the underlying records of their union's reports to ascertain further information related to the payments to third-party union officials.
                    </P>
                    <P>Multiple commenters offered support for the proposal regarding payments from unions and the stated rationale in the NPRM. In particular, multiple national/international union commenters stated that the statute does not allow the reading of “employers” to include “labor organizations,” outside of the staff union context. One international union stressed that section 201 provides for reporting from unions, and that a “plain reading” of the Act clearly distinguishes between “labor organizations” and “employers” for purposes of financial reporting and, with the exception of payments to staff union officials, does not require union officials to report payments received from a union. This union points out that payments by a union are captured on the union's own reports, as prescribed by section 201 of the Act. Two unions emphasized the Act's legislative history as well as the statutory language. One international union also offered support for IM section 260.005. None of these commenters disagreed with the Department's analysis that union-employer payments to staff union officials should be reportable.</P>
                    <P>One commenter based its opposition to the Department's proposal on the LMRDA's definitions of “employer” and “employee.” The commenter contends that these “clearly defined terms” apply to the whole of the Act, and they must include labor organizations and labor organization employees, as one cannot be an “employee” under the Act unless one works for an “employer.” According to the commenter, the 2007 Form LM-30 defined these terms pursuant to the statutory definitions without removing a “subset” of employers from the definition, namely “labor organizations” and section 3(l) trusts. The commenter also asserted that the Department's interpretation in the NPRM causes “structural” problems, as the Department “ignored” that unions are “employers” in areas other than section 202. The commenter cited rules of statutory construction and case law articulating these rules to argue that terms within a statute must be applied consistently throughout the statute. To do otherwise, it asserted would create a “Pandora's Box” of problems, as unions must report payments to their “employees” pursuant to section 201 and union “employees” must comply with the section 202 reporting requirements.</P>
                    <P>
                        Further, the commenter stated that Congress would have excluded “labor organizations” from the definition of “employer” in the LMRDA if it intended for unions to not be covered by section 202(a)(6). The commenter also contended that the Department's “discrete statutory actors” argument was inconsistent with the Department's litigation position in 
                        <E T="03">Warshauer</E>
                         v. 
                        <E T="03">Solis,</E>
                         577 F.3d 1330 (11th Cir. 2009) and the court's holding in that case.
                        <SU>36</SU>
                        <FTREF/>
                         In the commenter's view, the Department there argued that “employer” is not just the represented employer, but any private sector employer. The commenter concluded that the Department cannot have it “both ways,” that “employers,” “labor organizations,” and “labor relations consultants” cannot be discrete actors under the Department's theory in 
                        <E T="03">Warshauer.</E>
                         The commenter also states its view that under the Department's analysis a union-employer and its consultants could be required to file reports under the persuader activity language of section 203.
                    </P>
                    <FTNT>
                        <P>
                            <SU>36</SU>
                             In that case, the court held that an attorney who was designated legal counsel (DLC) (designated by the union to provide legal services to its members for claims relating to workplace injuries) is subject to the LMRDA's section 203 reporting requirements as an “employer” if it has employees and makes reportable payments to unions or union officials.
                        </P>
                    </FTNT>
                    <P>Another public interest organization criticized the position taken by the Department in the NPRM, stating that there is “little basis” for excluding unions from the “employers” of section 202(a)(6). The commenter rejected the idea that “employers” and “labor organizations” are discrete statutory actors, arguing instead that the definition of “employer” is “broad and inclusive” and does not exclude labor organizations. The commenter also rejected the notion that Congress would have included the term “labor organization” in section 202 if it intended for payments from them to be reported by union officials. In its view, such intention is negated because the Act “neither narrowly defines” when a union is an employer, nor “specifically excludes” unions from the definition of the term, thus indicating that the “plain reading” of the statute is that labor organizations can be employers. Further, the commenter cites the National Labor Relations Act (NLRA) definition of employer, which excludes labor organizations (except when acting as an employer). The commenter also asserts that the Department “argues against” itself by asserting that labor organizations can be employers in the context of staff unions. Finally, the commenter referred to the removal of unions and trusts from the scope of “employer” under section 202, as an effort to eliminate “unions and labor union-controlled trusts” from the section LMRDA section 203 reporting requirements concerning employer and labor relations consultants.</P>
                    <P>With regard to the particular contentions by the two commenters, the Department concurs with the observation that “labor organizations” and “employers” are not mutually exclusive. Indeed, labor organizations often act in a dual capacity, as both labor organizations and as employers. Further, the statute does not define “employer” in a manner that excludes “labor organizations” from its definition, which facilitates coverage of staff unions under the Act and labor organization “employees” in various parts of the statute, several of which the commenters cited, including section 202. The Department also acknowledges that the LMRDA defines the term “labor organization” differently than does the NLRA.</P>
                    <P>
                        The Department disagrees with the assertion that it utilizes “employer” inconsistently throughout the Act. As stated in the NPRM, the Department considers that the better application of section 202(a)(6) is to exclude payments from “labor organizations,” as the LMRDA establishes separate reporting requirements for “labor organizations” and “employers,” a statutory construction that reduces redundancy in the reporting requirements and burden on unions and their officials. Indeed, payments from labor organizations are reportable pursuant to section 201, while union officials must report conflicts of interest pursuant to section 202, and employers and labor relations consultants must report under certain circumstances pursuant to section 203. Thus, the “plain reading” of the term “employer” within section 202 does not include labor organizations acting as labor organizations. If Congress 
                        <PRTPAGE P="66466"/>
                        intended for payments from labor organizations to be reported pursuant to sections 202(a)(6) or 203(a)(1), then it would have included the term “labor organization” along with “employer.”
                    </P>
                    <P>Contrary to the commenters' view, the Department's position is consistent with the structure of the Act. For example, section 201 establishes initial and annual reporting requirements for entities that meet the statutory definition of “labor organization,” and when section 201 refers to an “employee” of a labor organization, then it clearly is referring to the subset of labor organizations that also qualify as an “employer,” as this is the only reading of the statute in which labor organizations can have employees. Further, in section 504(a), the statute uses the terms “employer” and “labor organization” separately and explicitly, to enumerate each situation in which a person is barred from serving a union or employer, or as a labor relations consultant for either entity. In section 504(a)(3), the statute bars an individual from serving as a labor relations consultant or adviser to a “person engaged in an industry or activity affecting commerce,” a term that is broader than both “employer” and “labor organization.” See LMRDA section 3(d). Thus, the approach articulated in this rule does not establish any “structural” problems identified by the commenters, nor does it open any “Pandora's Box,” as one commenter suggested.</P>
                    <P>
                        The commenter is mistaken in its understanding of the Department's position in 
                        <E T="03">Warshauer</E>
                         v. 
                        <E T="03">Solis.</E>
                         In that case, the court held that the Department did not act arbitrarily and capriciously in determining that the term “employer” in section 203(a)(1) included employers who did not participate in persuader or other labor relations activities. In 
                        <E T="03">Warshauer,</E>
                         the plaintiff, an attorney providing legal services to members of a union, conceded that he was an “employer” but argued that only employers who persuade employees about their right to organize and bargain collectively must file reports, and that he did not engage in this activity. The pertinent statute, section 203, contained five reporting provisions, four of which were triggered by persuader activity. The remaining provision was not so limited, requiring reporting based solely on certain financial payments, and the Department contended that its plain language required the plaintiff to file a report without regard to whether he engaged in persuader activity. In 
                        <E T="03">Warshauer,</E>
                         like here, the Department interpreted the language in light of the other requirements imposed on filers by the statute (there on “employers,” here on labor union officials), the Department's longstanding interpretation, and, secondarily, on the Act's legislative history. See Brief for Appellee, 2008 WL 526954, Argument at I.A.1. &amp; 2., B. 3.a. &amp; b., C. 1. (brief is without pagination on Westlaw); 577 F.3d 1330, 1335-36 (upholding Secretary's interpretation after considering the language of section 203(a)(1) and its context among the five subsections of section 203).
                    </P>
                    <P>
                        In 
                        <E T="03">Warshauer,</E>
                         the Department did not assert that the term “employer” must be read in a way that would require a labor union with employees to be treated as an employer for all purposes under the Act. Both the Department's brief and the court's opinion focus on the particular language of section 203((a)(1)), there at issue. While the Department argued in that case that section 3(e) of the Act “defines the universe of employers” encompassed by section 203(a)(1)'s employer reporting requirements, neither the Department's brief nor the court's opinion is in any way inconsistent with the Department's interpretation of section 202(a)(6). Further, while the Department argued that “employer” encompassed the universe of employers encompassed in section 3(e) of the Act, it did not assert that every 
                        <E T="03">payment</E>
                         from all such employers was reportable. Rather, in additional guidance, the Department delineated the kinds of relationships that employers must have with unions to trigger reporting for payments to such unions and their officials. See Form LM-10 FAQ 10. The Department's position here is consistent with 
                        <E T="03">Warshauer.</E>
                         The court did not address the issue whether the term “employer” included “labor organizations,” either in section 202 or 203, but instead recognized that Congress specifically limited the “employers” in other subsections of 203, but chose not to in section 203(a)(1). See 
                        <E T="03">Warshauer</E>
                         v. 
                        <E T="03">Solis,</E>
                         577 F.3d at 1335. While 
                        <E T="03">Warshauer</E>
                         stands for the principle that “employer” in section 203(a)(1) is broader than merely employers who participate in persuader or other labor relations activities, it does not address the different question as to whether “labor organizations” acting as such are included within this term, given that the statute delineates separate reporting provisions for “labor organizations” and “employers.” The reasoning in 
                        <E T="03">Warshauer</E>
                         supports the Department's determination here that if Congress intended to include payments from “labor organizations” acting as such in section 202(a)(6), then it would have included the term “labor organization” alongside “employer.”
                    </P>
                    <P>
                        Further, the Department's analysis on this point is also consistent with the one case that addressed the scope of the section 202 reporting requirements. In 
                        <E T="03">U.S. v. McCarthy,</E>
                         300 F. Supp. 716, 720-21 (S.D.N.Y. 1969), the court held that a union officer must report a salary received from a labor relations consultant to an employer, pursuant to section 202(a)(6). The union officer argued that such payments were exempt under LMRA section 302(c)(1) (the section 302 exemptions are relevant because section 202(a)(6) refers to section 302(c)), but the court held that a “labor relations consultant” is not a statutory “employer” under the LMRDA. Otherwise, the court recognized, the intent of section 202, to disclose conflict-of-interest payments, would be circumvented. Hence, the court held that the provision exempting regular wage payments from an employer was not applicable to regular wage payments from the labor relations consultant.
                    </P>
                    <P>There is no merit to the contention that the Department's proposal unreasonably distinguishes between staff unions and other unions that also have employees. The distinction is based on the fact that the payments (such as gratuities) must be reported under sections 202(a)(1)(2), and (5)—as payments by a represented employer to a union official—while in the other circumstances enumerated in the 2007 rule, the union is not making the payments as an employer. This treatment ensures that the Form LM-30 reporting requirements apply to staff union officials as they would to officials of other LMRDA-covered unions.</P>
                    <P>Regarding the commenter's concern that the changes proposed would deny union members any information about payments made by a union to union officials, the Department reiterates the point made in the NPRM that any such payments would be included in the payor-union's annual financial disclosure report, either in the aggregate or, in specified circumstances, itemized when they reach $5,000. See 75 FR 48428-29. If payments in question are exclusively benefits, then they would be included in Schedule 20 of the Form LM-2. Members of the local could also examine the underlying documents related to the reporting, for just cause, pursuant to section 201(c). As stated, the reporting and disclosure of labor organization expenditures are pursuant to LMRDA section 201, not section 202.</P>
                    <P>
                        As to the comment that alleged the Department lacks understanding of the Act, the Department first reiterates that 
                        <PRTPAGE P="66467"/>
                        “labor organizations” can be employers when acting as employers. Thus, payments from a union-employer to a staff union official are reportable on the Form LM-30 pursuant to section 202(a)(1). The result is the same, even if the union-employer is a non-LMRDA covered union, evidencing the consistency in the Department's approach. Moreover, the commenter's argument does not flow logically, as, under the 2007 rule, not all non-exempt payments from LMRDA covered “labor organizations” to union officials were reportable pursuant to section 202(a)(6); just those from “labor organizations” with employees were reportable.
                    </P>
                    <P>Finally, regarding the contention that the Department's interpretation will affect reporting under the persuader activity provisions of section 203, this area is outside the scope of this rule. The Department notes that the suggested problems are not self-evident. See LMRDA Interpretative Manual section 260.005 (discussed earlier in this section) for guidance on the application of section 203 in this respect.</P>
                    <HD SOURCE="HD3">4. Obligation To Report Payments From Charities and Other Not-for-Profit Organizations</HD>
                    <P>In the NPRM, the Department proposed no changes concerning the reporting of payments received by union officials from not-for-profit organizations. Nonetheless, the Department received four comments from unions, asserting that such payments should not be reportable because they do not arise out of labor-management relations. The commenters contend, in essence, that section 202(a)(6), should not be applied to payments that do not take place within this context. Such a request is beyond the scope of this rule, but the Department, for completeness, discusses these comments below.</P>
                    <P>One federation of unions praised the Department's narrowing of reporting on payments received by union officials from trusts and unions. It agreed with the Department's assessment that each entity is a discrete actor not named in section 202. It also contended, however, that the text and legislative history and purpose of section 202 require that “employer” in section 202(a)(6) be read to include only labor relations conflicts of interest not covered in sections 202(a)(1), (2), and (5). The federation asserted that the “employer” in section 202(a)(6) included employers in the same “labor market” or “likely organizing targets.” The comment presented three arguments supporting this view: section 202(a)(6) uses the term “an employer,” like sections 202(a)(1) and (5); the section also uses “labor relations consultant” to an employer, rather than more broadly “any person who acts as a labor relations consultant to an employer”; and the subsection cites the LMRA section 302(c) exceptions, which apply in a labor-management context. An international union stated that extensive reporting concerning charities and other not-for-profit organizations exists elsewhere, citing the Form 990 filed with the IRS and the reporting of payments to such entities from unions on the Form LM-2. Thus, Form LM-30 reporting of payments from such entities to unions, in its view, would be redundant, burdensome, and without a statutory basis.</P>
                    <P>The Department addresses these concerns only briefly. As noted, the Department proposed only limited changes to reporting under section 202(a)(6). Similar arguments directed at restricting the reach of that section were considered and rejected by the Department in the 2007 rule. 72 FR 36130. The Department has not reconsidered this position, but notes that the interpretation suggested by the commenters is not compelled by the language of section 202(a)(6) or the legislative history relied upon by the commenters. Furthermore, the Department notes that payments from a charitable organization to a union official, including director's fees and reimbursed expenses, are potential conflicts of interest, as the union official could be influencing the union to donate to the charity in order to maintain the position and income associated with his or her position on the charity's board, and not based upon the union's best interests. The commenters have offered no persuasive reason why union members should be denied information that allows them to make a determination about a potential conflict of interest. Additionally, while some reporting may be duplicated by other reporting frameworks, the Form LM-30 enables members and the public to view potential conflict-of-interest payments to union officials in one location, which justifies any marginal, additional burden on the union official.</P>
                    <P>Another commenter, a law firm, offered recommendations on reporting regarding payments from charities and other not-for-profit organizations. The commenter argued that requiring reporting of reimbursed expenses would discourage union officials from providing volunteer services to such organizations. The Department considers that any payment, including a payment for expenses incurred in voluntary service, must be reported to serve the conflict-of-interest reporting obligation intended in the Form LM-30 rule. The requirement to report does not apply universally to payments from all charities and non-profits, but only to payments from a charity or other non-profit that “receives or is actively and directly soliciting (other than by mass mailing, telephone bank, or mass media) money, donations, or contributions from the official's labor organization.” In such circumstances, the need for conflict-of-interest reporting is apparent.</P>
                    <P>The commenter also urged the Department to state that a non-profit organization is not actively seeking contributions from a union in receiving a membership dues payment from the union or a payment for advertising in the non-profit's publication. The effect of such a construction would be to exempt union officials from reporting payments from a non-profit under these circumstances, thereby defeating the intended conflict-of-interest disclosure purposes. It should be noted that the issue of what constitutes solicitation of donations is not relevant in the situation posed by the commenter. As presented by the commenter, the non-profit organization actually receives money or contributions from the union. The Form LM-30 rule provides that a union official must report payments received from a charity or non-profit organization if that organization receives money or contributions from the official's union or is actively and directly soliciting donations. Thus, the issue of what constitutes solicitation of donations for purposes of applying the Form LM-30 rule is not relevant. Further, it is beyond the scope of this rulemaking to make a determination concerning what activity constitutes solicitation of donations of union funds.</P>
                    <HD SOURCE="HD2">E. Scope of “Top-Down” Form LM-30 Reporting by National, International, and Intermediate Body Labor Organization Officers and Employees</HD>
                    <P>
                        In the NPRM, the Department proposed to extend the top-down reporting requirements, expressly established for 
                        <E T="03">officers</E>
                         of international, national, and intermediate unions by the 2007 rule, to 
                        <E T="03">employees</E>
                         of such organizations, who had been excepted from reporting under the 2007 rule. Under the proposal, employees of parent and intermediate unions, like the officers of such unions, would be required to report on financial interests in, and payments from, companies that have dealings with their union's subordinate affiliates and their trusts, as well as certain companies doing business with a represented employer. The NPRM also proposed to eliminate 
                        <PRTPAGE P="66468"/>
                        two limited exceptions established by the 2007 rule (sometimes referred to as “carve-outs”) whereby union officers, when applying the top-down reporting requirements, were not required to report on: (1) Payments received by the officer's spouse or minor children as bona fide employees; and (2) financial interests held in companies that did business with an employer whose employees were represented by subordinate affiliates. 72 FR 36122. Apart from eliminating these exemptions, the Department proposed no changes to top-down reporting by officers of parent and intermediate unions.
                    </P>
                    <P>
                        Based on a review of the comments, the Department has modified its proposal insofar as it affects reporting by employees of parent and intermediate unions. In the final rule, the Department requires these employees to report on “top-down” financial interests and payments where they hold positions of significant authority or influence over the subordinate affiliates. The “significant authority or influence” trigger is similar but not identical to the Department's proposal in the 2010 NPRM to reduce the burden associated with the reporting of payments from companies that are in competition with a represented employer.
                        <SU>37</SU>
                        <FTREF/>
                         Comments on the NPRM suggested that a similar approach would eliminate some of the uncertainty and burden surrounding top-down reporting. As discussed in greater detail below, the Department concurs with the suggested approach. It ensures that employees of parent and intermediate unions generally will report any financial interests that could pose a conflict of interest, while eliminating the uncertainty regarding reporting on matters that pose little or no risk of a conflict of interest.
                    </P>
                    <FTNT>
                        <P>
                            <SU>37</SU>
                             In the NPRM, the Department proposed to limit reporting interests in, and payments from, competitors to represented employers. Under the proposal, officers and employees—without regard to their place in the overall hierarchy of their unions—would only have to report on interests and payments from such employers if they hold a position with significant authority or influence over organizing, collective bargaining, or contract administration activities. The Department has adopted this proposal in the final rule. This issue is more fully discussed above in section III. D.1.
                        </P>
                    </FTNT>
                    <P>Additionally, the Department has adopted the proposed elimination of the carve-outs. The Department has accordingly modified the scope of top-down reporting for union officers and employees to read:</P>
                    <EXTRACT>
                        <P>
                            When applying the Form LM-30 reporting requirements, you are required to look at employers and businesses that have specified relationships with the level of the union in which you serve as an officer or employee. However, if you are an officer of a national, international, or intermediate union, you must also look at employers and businesses that have specified relationships with subordinate affiliates (
                            <E T="03">e.g.,</E>
                             a local union or other subordinate body), as well as your own level of the union. These relationships are identified below in the instructions for completing Parts A, B, and C of the form. If you are an employee of a national, international, or intermediate union and possess significant authority or influence (whether or not exercised) over a subordinate affiliate's activities (
                            <E T="03">e.g.,</E>
                             its organizing, collective bargaining, contract enforcement, spending or investment decisions, or union administration), you are also required to look at employers and businesses that have specified relationships with such affiliate, as well as your own level of the union. See instructions below.
                        </P>
                    </EXTRACT>
                    <HD SOURCE="HD3">1. Background</HD>
                    <P>Many labor organizations consist of a three-tier hierarchy: local labor organizations, intermediate bodies, and a “parent” national or international labor organization. This section of the rule concerns the obligation of a union officer or employee of a higher-level union (intermediate or national/international) to report his or her interests in and payments (and those of the filer's spouse and minor children) from employers and businesses that have a relationship with subordinate affiliates of the employee's union.</P>
                    <P>Under sections 202, union officers and employees must report payments from, holdings in, or transactions with:</P>
                    <P>• An employer whose employees the filer's labor organization represents or is actively seeking to represent;</P>
                    <P>• A business a substantial part of which consists of dealing with an employer whose employees the filer's labor organization represents or is actively seeking to represent; or</P>
                    <P>• A business that deals with the filer's labor organization or, as interpreted by the Department, a trust in which the filer's labor organization is interested.</P>
                    <P>The scope of the reporting obligation thus depends on which organizations constitute the filer's “labor organization.” The issue here is the disclosure obligation of potential conflicts of interests that arise between a union official and his or her responsibility to his or her immediate organization as well to any subordinate labor organization(s) within the union's structure.</P>
                    <P>In the rulemaking that culminated in the 2007 final rule, the Department interpreted the language of section 202 to require top-down reporting. In reaching this conclusion, the Department relied on the structure of the statute, the findings by the McClellan Committee concerning conflicts of interest between higher-level officers and subordinate unions, the stated purpose of the LMRDA to redress the problems identified in the McClellan hearings, and the Department's longstanding interpretation in the LMRDA Interpretative Manual that certain top-down reporting was required. 72 FR 36121-24.</P>
                    <P>Although the instructions to the Form LM-30 had historically been silent on this point, there has been longstanding administrative precedent applying the section 202 requirements to higher-level union officials. For example, in Section 241.100 of the LMRDA Interpretative Manual, the Department addressed the reporting standards for international union officers, as follows:</P>
                    <EXTRACT>
                        <P>Section 202(a)(3) of the Act requires reports from “every officer of a labor organization” of income derived from “any business a substantial part of which consists of buying from, selling or leasing to, or otherwise dealing with, the business of an employer whose employees such labor organization represents or is actively seeking to represent.” An international union officer must report his income from such a business even though he is not an officer of the local which represents the employees of the business, and even though his duties as an international officer do not include representation activities.</P>
                    </EXTRACT>
                    <HD SOURCE="HD3">2. Overview of Comments Received and Department's Response</HD>
                    <P>Twelve comments, all from unions, including one federation of unions, specifically discussed the top-down reporting requirement. An additional three union commenters expressed overall support for comments submitted by the federation of unions, which included recommendations on top-down reporting. One international union supported the Department's proposed top-down reporting requirement as articulated in the NPRM. All others expressed opposition, asserting that the Department's proposed top-down approach creates undue burden, and represents a considerable expansion of the scope of top-down reporting requirements set forth in the 2007 rule.</P>
                    <HD SOURCE="HD3">Comments To Eliminate the Top-Down Reporting Requirement  and Department's Response</HD>
                    <P>
                        Six of the commenters who opposed the proposed top-down reporting requirement asserted that this reporting requirement should be eliminated altogether in light of the burden that it imposes. One international union asserted that it not only opposed the 
                        <PRTPAGE P="66469"/>
                        NPRM's proposed expansion to the top-down reporting requirement, but also believes that the 2007 rule's top-down reporting requirement is unnecessary and “of little value in disclosing real conflicts of interest.” Another commenter asserted that both labor organization officers and employees should have to report only in relation to matters involving the level of the union hierarchy that they serve and not any subordinate affiliate.
                    </P>
                    <P>The Department disagrees with this view and does not support the elimination of a top-down reporting obligation. As explained below, the reporting burden associated with top-down reporting has been overstated and is insufficiently supported by the commenters. Further, such a restricted rule on top-down reporting would eliminate all disclosure of any potential conflicts of interests of higher-level union officers and employees concerning subordinate organizations, a position never previously taken by the Department. For example, similar to the situation presented in IM section 241.100, international union officers and employees may encourage subordinate unions to purchase goods or services from a business in which they have an interest, or a business from which they received a gratuity, such as a printing company or travel agency. The subordinate affiliate, fearing repercussions if it does not do business with this vendor, may engage its services, even though other vendors may offer better rates, services, or products.</P>
                    <P>As a further example, a national union officer or employee whose spouse is an employee of a service provider may influence lower-level unions to do business with this provider. Top-down reporting, as well as the other aspects of section 202 of the LMRDA, is intended to obtain disclosure of this kind of conflict-of-interest situation, and such reporting is of value to members and the public. Several commenters acknowledged that higher-level union officers and employees may engage in conduct raising actual or potential conflicts of interest with lower levels of their unions. Eliminating the top-down reporting obligation in its entirety would circumvent the intent of the LMRDA to provide disclosure of actual or potential conflicts of interest.</P>
                    <HD SOURCE="HD3">Comments To Limit Top-Down Reporting to Trusteeship Situations  and Department's Response</HD>
                    <P>Two international unions commented that they favored the elimination of the top-down reporting requirement, but suggested alternatively that the requirement should be limited to situations in which a parent union has placed a subordinate union under trusteeship. They argued that a trusteeship represents the only situation in which parent body officers and employees have financial and managerial control over subordinate affiliates. The Department disagrees with this approach because it would be unduly restrictive in its exclusion of other scenarios—beyond trusteeships—that could present a conflict between union officials' personal financial interests and their duty to the labor union and its members.</P>
                    <HD SOURCE="HD3">Comments on Burden and Department's Response</HD>
                    <P>Several commenters stated that top-down reporting requires union officers and employees to conduct research, often extensive, to identify employers or businesses with which lower-level affiliates bargain or otherwise deal. One commenter described the proposed top-down reporting requirement as “unreasonable and overly burdensome” and expressed concern that inadvertent failure to file Form LM-30 reports could represent a possible Federal law violation. Another commenter expressed concern about the inability of international union officers and employees to obtain information necessary to comply with the reporting obligation, and predicted that, by being overly inclusive, “the result will likely be widespread, though unwitting and unintentional, noncompliance, with no useful information for the public.”</P>
                    <P>Additionally, some commenters stated that the expansion of top-down reporting imposes a far greater burden than the reductions otherwise associated with the proposed rule. Although acknowledging the possibility of potential conflicts of interest between higher-level union officers and employees and business conducted with subordinate affiliates, another commenter stated that such potential conflict does not justify the reporting burden, especially in the absence of a central repository of businesses whose relationships with subordinates could trigger reporting. This commenter noted that compiling and updating such a list would be costly and burdensome.</P>
                    <P>Seven international unions opposed the Department's proposal to eliminate certain top-down reporting exclusions that were established in the 2007 rule. One commenter asserted that “while `top-down' reporting by officers is unnecessary and overly burdensome, expanding such reporting to now include employees is even further removed from capturing the types of conflict-of-interest payments envisioned by the LMRDA.” The commenter added that the requirement places LM-30 filers in a “severely compromising and legally tenuous position,” and expressed concern about the additional reporting and recordkeeping burden associated with the elimination of the “carve-outs” from the 2007 rule.</P>
                    <P>
                        Another commenter expressed concern that the proposal expands the top-down reporting obligation beyond even what the 2007 rule deemed feasible and necessary,” and disagrees with the proposed elimination of the 2007 rule's “three critical narrowing principles” associated with top-down reporting. With respect to the proposal to eliminate the reporting exemption in the 2007 rule for bona fide employee payments to spouses and minor children an international union stated, “It is unreasonable to require that all such things of value, legitimately received by the spouse in the course of his or her own employment, be subject to scrutiny and reporting solely because of some inadvertent common connection to a separate local union or related trust fund, at least where the international officer or employee in question has no authority or ability to influence the local union or trust fund decision-making process.” 
                        <SU>38</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>38</SU>
                             Three international unions stated that the burden associated with the top-down reporting requirements was greatly compounded by the Department's decision to retain the 2007 definitions of “substantial part” and “actively seeking to represent,” by requiring greater research by union officers and employees to determine how the definitions of the terms would apply to lower levels of the officer or employee's union. 
                        </P>
                        <P>Section 202(a)(3) requires a union official to report income and benefits from and interests in businesses that deal in “substantial part” with an employer whose employees the official represents or is “actively seeking” to represent. Sections 202(a)(1), (2), and (5) require the reporting of payments from, interests in, and transactions with employers whose employees the official's union represents or is “actively seeking to represent.”</P>
                        <P>The 2007 rule defines “substantial part” as 10% of the entity's business, and provides that the labor union must take concrete steps that demonstrate that it is “actively seeking” to represent employees of an employer. This rule does not substantively alter these definitions, which affect numerous aspects of reporting pursuant to sections 202(a)(1)-(5), independent of the top-down reporting issue. These issues are also discussed above at section III.F.1. (“substantial part”) and III.F.2 (“actively seeking to represent”).</P>
                    </FTNT>
                    <P>
                        The Department disagrees with these commenters that the burden imposed by full top-down reporting is not justified by the actual or potential conflicts of interest that will be reported. Initially, the Department emphasizes, as articulated above, that top-down reporting is necessary to disclose certain actual or potential conflict-of-interest situations. Further, to illustrate the 
                        <PRTPAGE P="66470"/>
                        Department's contention that the commenters' view of top-down burden is overstated, it is helpful to look at the methodology involved in determining whether a top-down report is owed. The first step is for a union officer or employee to look at the types of interests in, income and benefits received, and transactions engaged in during his or her fiscal year. The second step is to eliminate from this list those that are exempted by the general exclusions, if applicable, such as publicly held stock, income received by the union officer or employee as a bona fide employee of a represented employer, and the de minimis threshold. This step likely will reduce the number of potential reportable transactions. The third step is to then determine whether any of the remaining financial transactions were derived from represented employers, as well as service providers and vendors of the represented employer, the union, and the union's trusts.
                        <SU>39</SU>
                        <FTREF/>
                         The commenters appear to be suggesting that the inquiry would skip the first two steps and go directly to the third.
                    </P>
                    <FTNT>
                        <P>
                            <SU>39</SU>
                             A fourth step could involve the “catch-all” Part C of the revised Form LM-30, pursuant to section 202(a)(6), which would require reporting of any payments from any other employer (other than one already identified in sections 202(a)(1)-(5)) from whom the receipt of the payment by an official would create an actual or potential conflict of interest. But OLMS proposed restricting the reporting of payments from employers in competition with represented employers to union officers and employees with significant influence over organizing, collective bargaining, or contract administration activities related to a particular represented employer, see 75 FR 48427, and this rule adopts that limitation for employees. See discussion above in section III.D.1. This eliminates the top-down issue for most employees of parent and intermediate unions. For those that must report, it is only because they possess the significant authority or influence out of which a conflict may arise.
                        </P>
                    </FTNT>
                    <P>Indeed, officers and employees of parent and intermediate unions will not be required to look at every relationship that lower-level entities have, but, rather, only those that relate to the few, if any, employers and businesses identified in step three of the process. The Form LM-30 report is to be completed by union officers and employees only when reportable transactions occur during a reporting period, usually a calendar year. Reporting is self-initiated. Reportable transactions are generally not the norm. In determining whether a report is owed, an officer or employee of a parent or intermediate union would consider the nature of a transaction or interest of which he or she has knowledge, rather than consider information about the operations of every subordinate affiliate. Moreover, with regard to an officer or employee's dealings with vendors and service providers, not all transactions with such entities must be reported. Instead, only those matters involving financial situations in which one has an interest or derives income or other benefits with monetary value, as required by sections 202(a)(3) and (4), must be reported. Reportable benefits would include gratuities, such as complimentary hotel rooms, but not regular business or commercial transactions in which no such gratuity is conferred. See IM section 246.400. Thus, an officer or employee would not be required to report the value of the hotel room for which he or she paid market value on terms available to the public.</P>
                    <P>Union officers and employees, like most individuals, do not generally receive large gifts and gratuities in connection with their business dealings, and therefore are unlikely to have any reporting obligations. Further, those who do receive such gifts and gratuities are likely to have received them as a result of a vendor or service provider's intent to influence the union officer or employee. In any event, if gifts or other benefits are conveyed or received, a union officer or employee would be in position to seek further information concerning the entity providing the gift or other benefit, and, if the requisite relationships exist, the reporting requirements dictate disclosure so members and the public can determine whether or not a potential conflict of interest exists. Additionally, a union officer or employee with a significant interest in a business, like any similar individual with such an interest, is likely in a position to know the entities with which the business deals. The same risk of conflict exists where a spouse or minor child of an officer or employee with significant authority or influence over a subordinate affiliate works for a company that has business dealings with those affiliates or business with or involving an employer whose employees are represented by the affiliates. Under the 2007 rule, an international officer whose spouse works on commission for a business supply/printing company that sells personal computers, office furniture, and printing services throughout the country to locals affiliated with the international union would not report the spouse's income, even though the potential conflict of interest that such a relationship poses is apparent. Under the revised rule, such income is reportable.</P>
                    <P>Thus, potential filers are not required to engage in extensive research or create a “central repository” to determine the applicability of the Form LM-30 reporting requirements in top-down situations. In instances where the union officer or employee or his or her spouse or minor child is an employee of a vendor or service provider, receives an occasional payment, such as a gift or gratuity or a discount on a purchase, or otherwise has difficulty determining the applicability of the top-down or other reporting requirements, the Department is available to provide compliance assistance. In this regard, the Department advises that any officer or employee who encounters such difficulty should request necessary information in writing from the union, vendor, service provider, or employer. If the entity refuses to provide the information, the officer or employee should contact the Department for assistance in obtaining the information. In the meantime, the union officer or employee should make a good faith determination, based on the information reasonably available, whether reporting is required for the matter involved. If the union officer or employee determines that no report is required, the officer or employee should retain the written request for information that he or she presented to the business, employer, or union and any related documentation.</P>
                    <P>If an investigation is conducted, there is no risk of prosecution absent unusual circumstances calling into doubt the legitimacy of the good faith determination. See 72 FR at 36133. The Department emphasizes that criminal liability only results from a willful action or from knowingly making a false statement or representation of a material fact or knowingly failing to disclose a material fact. See LMRDA Section 209, 29 U.S.C. 439.</P>
                    <P>
                        The Department disagrees with the concern expressed by some commenters that top-down reporting, as prescribed in the 2007 rule, would result in “widespread * * * non-compliance.” The Department expects that union officers and employees will undertake the task responsibly and without undue burden, as the rule reasonably achieves conflict-of-interest reporting without undue burden on filers. In particular, the Department anticipates that the “significant authority or influence” modification it has adopted in the rule will reduce the general level of concern that the proposal may have created among employees of parent and intermediate unions. The Department expects that only a small fraction of such individuals will have any top-down reporting obligations.
                        <PRTPAGE P="66471"/>
                    </P>
                    <HD SOURCE="HD3">Comments To Narrow the Scope of Top-Down Reporting to Individuals Having “Significant Authority or Influence” and Department's Response</HD>
                    <P>
                        A federation of national and international labor unions proposed narrowing the scope of top-down reporting by limiting reporting to situations in which the filer has “significant authority or influence” over the subordinate labor union. The commenter noted that the Department had proposed under Part C of the instructions to limit reporting payments from employers in competition with represented employers to situations in which an employee possessed significant authority or influence over certain union functions, such as negotiations, contract administration, or organizing. The federation noted that the Department justified this Part C limitation by stating that it relieves “the undue burden” of requiring the filer “to undertake research in order to discover” who are “competitors to their union's represented employers.” 75 FR 48427.
                        <SU>40</SU>
                        <FTREF/>
                         The commenter asserted that requiring all national or international union officers and employees to conduct research to identify employers or businesses with which lower-level affiliates bargain or otherwise deal would impose a similar “undue burden.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>40</SU>
                             
                        </P>
                        The commenter is referring to the following statement (implementing section 202(a)(6) of the Act): 
                        <P>[An officer or employee must report a payment received from certain employers, including] an employer in competition with an employer whose employees your organization represents or whose employees your labor organization is actively seeking to represent, if you are involved with the organizing, collective bargaining, or contract administration activities or possess significant authority or influence over such activities. You are deemed to have such authority and influence of you possess authority by virtue of your position, even if you did not become involved in these activities. </P>
                        <P>75 FR 48450. See 75 FR 48420, 48427, 48434 (discussing this part of the instructions). The 2007 rule required that officers and employees report such payments even if they had no involvement with the activities identified above or possessed no significant authority or influence over such activities.</P>
                    </FTNT>
                    <P>
                        Three national/international unions specifically concurred with the federation's proposal to narrow top-down reporting to those officers and employees with “significant authority or influence.” Advocating for limiting the top-down requirement to a “more rational level,” one commenter stated that narrowing the requirement by the “significant authority or influence” variable would “help to lessen the considerable burden of requiring officers or staff to know all the business relationships involving * * * more than a hundred subsidiary entities.” Another commenter stated that a vast majority of its international union officers and employees have no responsibilities or authority with respect to the union's numerous local unions and intermediate bodies, and described the idea of limiting reporting to officers and employees with “significant authority or influence” as “far more practicable, yet still burdensome, and more in tune with the Act's ultimate objective of limiting reporting to areas where there exists an actual or potential conflict of interest.” 
                        <SU>41</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>41</SU>
                             This commenter proposed using criteria set forth under the Fair Labor Standards Act (FLSA) to determine, on a case-by-case basis, if an individual has “significant authority or influence” over the subordinate entity. The commenter, apparently, is referring to the test used for the FLSA's administrative exemption. See 29 CFR 541.201-.203. The Department disagrees with this suggestion regarding the application of the FLSA factors, as these factors will not easily correspond to the activities of union officers and employees and the purpose of the determination regarding such significant authority or influence.
                        </P>
                    </FTNT>
                    <P>
                        Upon consideration of these comments and a further consideration of how best to achieve the Act's intended disclosure without imposing unreasonable burden, the Department has concluded that the federation's suggestion is a better approach than the approaches taken in the 2007 rule and the 2010 NPRM. While the Department disagrees with the view of certain commenters that top-down reporting is not justified—however limited—because of the burden associated with it, the Department concurs that most union employees do not have significant authority or influence over matters related to lower-level unions and therefore would not present the kind of conflict between their personal interests and their responsibilities to the union that the LMRDA intended to disclose. The Department also acknowledges that such employees are likely to be less familiar with the Form LM-30 requirements than officers and employees with significant authority or influence over these affiliates. 
                        <SU>42</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>42</SU>
                             The Department recognizes that some might see a unified approach for officers and employees as preferable to the approach adopted in the final rule. The Department notes, however, that it did not propose any change to the basic approach established for officers in the 2007 rule and supplanting this approach now could be perceived as unfair to commenters. Furthermore, on a practical level, the Department believes that disclosure is equally well served by the approach adopted in the final rule. Generally, an officer of a parent or intermediate union, by virtue of his or her office, exercises significant authority or influence over subordinate affiliates. While the same is not true of most employees of parent and intermediate unions, in those instances where an employee possesses such authority, he or she has the same reporting obligation as an officer.
                        </P>
                    </FTNT>
                    <P>Additionally, those employees who exercise significant authority or influence over subordinates, unlike most employees, are positioned to affect relationships involving subordinate affiliates and to be influenced by a represented employer or a potential or current vendor or service provider of a lower-level union. Thus, the Department is interpreting section 202 in a manner that targets Form LM-30 top-down reporting to those employees with significant authority or influence over lower-level unions, as a reasonable way to capture conflict-of-interest situations while avoiding possible confusion for those employees who are unlikely to have conflicts of interest involving lower-level bodies. This approach ensures that the Form LM-30 reporting requirements do not unnecessarily intrude upon the legitimate internal operations of unions, and thus better implements the Congressional purpose behind section 202. In the Department's view, this approach effectuates the statute's disclosure purpose while limiting unnecessary intrusion on unions and their employees. Further, because of other aspects of this final rule that exempt from reporting such transactions as mortgages, car loans, and similar transactions—so long as they are based on market rates and prices—the burden associated with top-down reporting, as have all aspects of Form LM-30 reporting, has been substantially reduced from the requirements established in the 2007 rule.</P>
                    <P>
                        By requiring employees who exercise authority or influence over subordinate affiliates to report on interests and payments in companies that do business with these affiliates or with represented employers, the Department brings top-down reporting into greater congruence with the language of section 202, which requires conflict-of-interest reporting by both officers and employees. Although there is an inferential basis for the distinction made in the 2007 rule between union officers and union employees, 
                        <E T="03">i.e.,</E>
                         that only relatively few employees (compared to union officers) wield the influence that would give rise to potential conflicts of interest, neither the statute nor the 2007 rule distinguishes between the two categories in any other respect for reporting purposes. Moreover, there is little basis for a blanket exclusion of higher-level union employees, because such individuals (
                        <E T="03">e.g.,</E>
                         union organizers) could exercise significant authority or influence over matters relating to subordinate affiliates.
                    </P>
                    <P>
                        Furthermore, regarding the other 2007 carve-outs to top-down reporting 
                        <PRTPAGE P="66472"/>
                        (payments received by the officer's spouse or minor children as bona fide employees and financial interests held in companies that did business with an employer whose employees are represented by a subordinate affiliate), the statute also does not distinguish between, on one hand, financial interests held by officers and employees, and, on the other hand, financial interests held by their spouses and minor children. Additionally, there is little basis for excluding interests in and income and benefits derived from a business that deals with the employer but not the union and its trusts, and the 2007 rule did not explain any perceived distinction. In the Department's view, this exclusion creates confusion regarding the scope of top-down reporting, as indicated in the comments to the NPRM, which reflected a misunderstanding by the commenters about this aspect of the 2007 rule. It also illustrated potential under-inclusiveness of the “bona fide employee” exception to top-down reporting in the 2007 rule, such as the example of the higher-level union officer who influences affiliates to do business with the company that employs the spouse of the officer or employee. Finally, section 241.100 of the LMRDA Interpretative Manual, upon which reporting by higher level officers was based, involved a conflict-of-interest scenario that would not have been reported under the rule.
                        <SU>43</SU>
                        <FTREF/>
                         Reporting will now be required for that scenario.
                    </P>
                    <FTNT>
                        <P>
                            <SU>43</SU>
                             In short, this section, which had been issued in 1962, provided that an international union officer must report interests that the officer and his spouse had in a company that dealt in substantial part with a represented employer of a subordinate body, despite the officer's lack of specific authority for representation activities. While the interpretation was specific to income received for an entity that had dealings with a subordinate affiliate, neither the interpretation nor the language of the statute supports an argument that limits reporting to these specific factors. The IM section is also consistent with the purpose of the statute, which requires officers and employees to publicly disclose possible conflicts between their personal financial interests and their duty to the labor union and its members.
                        </P>
                    </FTNT>
                    <P>The Department is also not applying the identical standard utilized in Part C of the revised instructions for payments received under section 202(a)(6), regarding payments received from an employer in competition with a represented employer. There, an officer or employee must report a payment from such a competitor employer, if the individual is involved with the organizing, collective bargaining, or contract administration activities or possesses significant authority or influence over such activities. This standard is appropriate under such circumstances, as section 202(a)(6) employers (and particularly the competitor employer example) are further removed from the union than the closer relationships described in section 202(a)(1)-(5).</P>
                    <P>
                        In the top-down reporting scenario, the potential conflicts of interest of union officers and employees with significant authority or influence extend to 
                        <E T="03">any</E>
                         area of union activity engaged in by subordinate affiliates.
                        <SU>44</SU>
                        <FTREF/>
                         These higher-level union employees may exercise control over the actions and decisions of lower-level unions in any area of union activities, including not only organizing, collective bargaining, and contract enforcement, but also including spending or investment decisions and union administration. Further, such higher-level employees may have substantial communication or interaction with officers and employees of subordinate bodies whereby they “significantly influence” the actions by such lower-level bodies. Moreover, union officers of a higher-level body possess significant authority and influence by virtue of their position, and they are covered under this rule's top-down reporting requirements without exception. Such higher-level officers are elected directly by members at lower levels of the union, or indirectly through representatives chosen by such lower-level unions, and thus are accountable to those members and can influence the officers and employees of the lower-level unions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>44</SU>
                             Section 202 assumes that all union officers and employees (other than exclusively clerical or custodial employees) possess sufficient authority and influence, at their level of the union, without reference to specific duties and responsibilities, to warrant conflict of interest reporting if the official receives a payment from or has an interest in the statutorily-enumerated entities. However, the statute is not explicit, in the case of higher-level union officials, as to whether reporting is required with respect to potential conflicts of interest in relation to subordinate affiliates within the union's hierarchy. Nevertheless, it is the Department's view that top-down reporting is necessary to ensure that conflict of interest payments are captured, as illustrated above. Some union commenters, as identified above, explicitly acknowledged that conflict of interest scenarios are possible with transactions involving lower levels of the union.
                        </P>
                    </FTNT>
                    <P>Finally, the Department does not adopt a limitation of the “significant authority or influence” requirement to “a matter potentially implicated by the transaction in question,” as recommended by one commenter, because the potential conflict of interest for an officer (or an employee with significant authority or influence over a subordinate affiliate) is clearly implicated without any further clarification.</P>
                    <HD SOURCE="HD2">F. Other Issues Concerning the Form LM-30 Reporting Requirements</HD>
                    <P>While the Department proposed changes to only five substantive areas of the 2007 rule's reporting requirements, the comments to the NPRM addressed other areas related to Form LM-30 reporting. These issues include: the definitions of “substantial part” and “actively seeking to represent” in LMRDA section 202 (a)(3); the definition of “labor organization officer” in section 202; the reporting of director's fees; the de minimis reporting exemptions; value range reporting; and alternative statutory constructions of section 202. For completeness, the comments on these areas are addressed below. While these comments are helpful to the Department in identifying concerns among the various regulated communities and directing compliance resources, the comments address matters that are beyond the scope of this rule.</P>
                    <HD SOURCE="HD3">1. The Definition of “Substantial Part” in Section 202(a)(3)</HD>
                    <P>
                        LMRDA section 202(a)(3) requires union officials to report any interests in and payments from, “any business a 
                        <E T="03">substantial part</E>
                         of which consists of buying from, selling or leasing to, or otherwise dealing with, the business of an employer whose employees such labor organization represents or is actively seeking to represent” (emphasis added). In the 2007 rule, the Department determined that 10% or more of a business's annual receipts will be considered “a substantial part” of its business. See Definition 15, “substantial part,” in the 2007 Form LM-30 Instructions; 72 FR 36133. In the 2010 NPRM, the Department stated it was retaining the 2007 definition of “substantial part.” See 75 FR 48434.
                    </P>
                    <P>
                        Three national/international union commenters asserted that the definition of “substantial part” in the 2007 rule unnecessarily complicates compliance with the Form LM-30. One commenter, noting the difficulty it poses for top-down reporting by officials of parent and intermediate unions, stated that it unfairly requires a union official to “take affirmative steps to investigate.” Another national/international union commenter argued that defining “substantial part” as 10% or more creates too low a threshold for reporting. The commenter instead suggested that a larger percentage (it did not suggest a particular percentage) would be a more appropriate threshold, citing to section 245.200 in the LMRDA Interpretative Manual, which addresses whether a company's dealings with an employer 
                        <PRTPAGE P="66473"/>
                        that amounted to some 80% of its business was “substantial” within the meaning of section 202(a)(3).
                        <SU>45</SU>
                        <FTREF/>
                         In the commenter's view, setting the threshold at 10% requires reporting about payments received from companies only doing a modest amount of business with a covered employer, requiring, in its view, “an inordinate amount of time to survey and evaluate every single business,” which an official, his or her spouse, or minor child have transactions with or holdings in during the fiscal year. The commenter cited the unfairness in not limiting reporting to situations in which the filer has “actual knowledge.” The commenter added that the filer is at the “mercy of the business” where the information is not publicly available, and that businesses do not have a legal obligation to provide the data and may even be legally obligated to not disclose such information. The two other commenters generally agreed with this commenter's observations.
                        <SU>46</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>45</SU>
                             245.200 Substantiality of Dealing Union Officers 
                            <E T="03">A</E>
                             and 
                            <E T="03">B</E>
                             of a local union are co-owners of a building corporation. The corporation, through intermediaries who are regular meat wholesalers, sold meat to employers who bargain with the local union. In 1962, some 80% of the corporation's business of approximately $100,000 was with such employers. Both 
                            <E T="03">A</E>
                             and 
                            <E T="03">B</E>
                             owe reports for the year 1962 with regard to their interest in and their income from the building corporation pursuant to section 202(a)(3), since both the interest and the income are “derived from, any business a 
                            <E T="03">substantial</E>
                             part of which consists of buying from, selling or leasing to, or otherwise dealing with, the business of an employer whose employees such labor organization represents or is actively seeking to represent.”
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>46</SU>
                             The same theme is repeated in the comments submitted on the Form LM-30 definition of “actively seeking to represent,” as discussed in the next section of the text.
                        </P>
                    </FTNT>
                    <P>The Department does not agree that the definition of “substantial” adds any additional burden, or requires an “inordinate” amount of time to apply, separately from the top-down reporting obligation. The statute establishes reporting in certain enumerated situations involving interests or income or benefits from vendors or service providers, such as where the vendors or service providers deal in substantial part with a represented employer. The purposes served by section 202(a)(3) require a reporting threshold that balances the burden associated with reporting insubstantial matters and the benefit served by the disclosure of any potential conflicts, no matter how small. In this regard, a quantitative approach is appropriate in analyzing the level of business engaged in for a vendor or service provider, and it is relatively easy for a filer to apply, thus reducing burden.</P>
                    <P>A filer does not need to investigate the relationship of every vendor or service provider to each represented employer of his or her union; the filer only needs to look at those in which he or she has an interest or from which he or she has received income or other benefit. Further, the commenter presented no evidence that the 10% threshold constitutes only a “modest” rather than “substantial” percentage of business for most entities, and is therefore unlikely to target likely conflict-of-interest scenarios.</P>
                    <P>As discussed in the preamble to the 2007 rule, 72 FR 36133-34, section 245.200 of the LMRDA Interpretative Manual (set forth in the margin), does not define a reporting threshold. It does not specify or imply that reports would not be required of union officials if the corporation derived less than 80% of its business from the employer. The example's inclusion of the 80% figure illustrates only one “substantial business” relationship that would require a report—not a threshold to use in determining whether a reporting obligation is triggered. Furthermore, no commenter suggested an alternative percentage threshold to 10%.</P>
                    <P>There is no merit to the suggestion that a reporting obligation attaches only where a union official possesses actual knowledge that the vendor's volume of business with a relevant employer was greater than the reporting threshold. This approach would provide an incentive for a union official to remain willfully ignorant of the business relationship between a vendor in which he or she holds an interest or from which he or she receives a payment and a represented employer. A subjective standard in which actual knowledge of the amount of business triggers reporting would also be difficult to implement.</P>
                    <P>The Department recognizes that some union officials may encounter difficulty in learning the amount of business a vendor conducts with the represented employer. The Department, however, believes that the likelihood of such difficulty is overstated, and the filer is not at the “mercy” of a business to determine whether or not the substantiality threshold has been met. This is especially true where the union official holds an ownership or operating interest in the vendor. In those instances, there should be little trouble in obtaining the needed information.</P>
                    <P>There may be some instances where the union official encounters some difficulty in obtaining information, such as where the official is an employee of the vendor or receives a gift or gratuity from, or a discount on a purchase provided by, the vendor. In such instances, the union official should request information in writing from the vendor. If the vendor refuses to provide the information, the official should contact the Department for assistance in obtaining the information. In the meantime, the union official should make a good faith estimate, based on the information reasonably available, of whether the 10% threshold has been met. If such estimate exceeds the 10% threshold, then the union official should file the report and explain that the vendor failed to provide requested information. If the estimate yields a figure less than 10%, no report is required, but the union official should retain the written request for information he or she presented to the vendor and any work sheet used to arrive at the less than 10% figure. See 72 FR at 36133.</P>
                    <P>With regard to the concerns expressed about potential criminal liability from a filer's failure to identify all companies that have conducted substantive business with a represented employer, the Department emphasizes that criminal liability only results from a willful action or from knowingly making a false statement or representation of a material fact or knowingly failing to disclose a material fact. See LMRDA Section 209, 29 U.S.C. 439. Thus, a filer who makes a good faith, conscientious effort to comply with the reporting requirements should have no concern about criminal liability.</P>
                    <HD SOURCE="HD3">2. Definition of “Actively Seeking To Represent” in Section 202</HD>
                    <P>
                        LMRDA sections 202(a)(1), (2), and (5) require union officials to report certain payments, interests, transactions, and arrangements from an employer whose employees its union represents or is 
                        <E T="03">actively seeking to represent.</E>
                         Additionally, LMRDA section 202(a)(3) requires union officials to report any interests in, and payments from, “any business a substantial part of which consists of buying from, selling or leasing to, or otherwise dealing with, the business of an employer whose employees such labor organization represents or is 
                        <E T="03">actively seeking to represent”</E>
                         (emphasis added). The 2007 rule created a definition for “actively seeking to represent,” a term not previously defined in the Form LM-30 and its instructions as follows:
                    </P>
                    <P>
                        “Actively seeking to represent” means that a labor organization has taken steps during the filer's fiscal year to become the bargaining representative of the employees of an employer, including but not limited to:
                        <PRTPAGE P="66474"/>
                    </P>
                    <P>• Sending organizers to an employer's facility;</P>
                    <P>• Placing an individual in a position as an employee of an employer that is the subject of an organizing drive and paying that individual subsidies to assist in the union's organizing activities;</P>
                    <P>• Circulating a petition for representation among employees;</P>
                    <P>• Soliciting employees to sign membership cards;</P>
                    <P>• Handing out leaflets;</P>
                    <P>• Picketing; or</P>
                    <P>• Demanding recognition or bargaining rights or obtaining or requesting an employer to enter into a neutrality agreement (whereby the employer agrees not to take a position for or against union representation of its employees), or otherwise committing labor or financial resources to seek representation of employees working for the employer. Where a filer's union has taken any of the foregoing steps, the filer is required to report a payment or interest received, or transaction conducted, during that reporting period.</P>
                    <NOTE>
                        <HD SOURCE="HED">Note:</HD>
                        <P> Leafleting or picketing, such as purely “informational” or “area standards” picketing, that is wholly without the object of organizing the employees of a targeted employer will not alone trigger a reporting obligation. For example, if a union pickets a sporting goods retailer solely for the purpose of alerting the public that the retailer is selling goods that are made by children working in oppressive conditions in violation of accepted international standards, the picketing would not meet the “actively seeking to represent” standard. </P>
                    </NOTE>
                    <P>The 2007 Form LM-30 Instructions, Definition 1. In the 2010 NPRM, the Department stated that it was leaving unchanged the 2007 definition of “actively seeking to represent.” See 75 FR 48434.</P>
                    <P>The Department received five comments on the Department's 2007 definition of “actively seeking to represent.” One public policy organization supported the definition. Three national/international labor unions criticized the definition, and a federation of international labor unions offered a clarification of the definition.</P>
                    <P>Three national/international union commenters urged the Department to reevaluate the “actively seeking to represent” definition, arguing that the proposed rule's expanded top-down reporting obligation, coupled with this definition, significantly adds to the overall burden on filers. One of these commenters called the 2007 rule's definition “absurdly broad.”</P>
                    <P>One commenter argued that “[i]t is unfair to subject union officers and employees to prosecution for failing to track vaguely-defined activities at every subordinate level of their union.” The commenter urged the Department to adopt a revised definition that is “narrower” and “more objective,” and that is “limited to discrete and enumerated activities that clearly constitute organizing employees, such as a labor organization demanding recognition from an employer or filing an NLRB petition during the reporting period.” Another commenter echoed the concern about the definition's “vague triggers,” and “urge[d] the [Department] to remember that the LMRDA and the LM-30 reporting obligation are subject to criminal penalties.” This commenter suggested that revising the definition to include “unequivocal conduct, such as filing a petition with the NLRB or demanding representation or bargaining rights” would avoid creating a chilling effect for “workers seeking to associate to protect and advance their economic interests.” Further, the commenter noted that the absence of a “durational limit on conduct” will make it even more difficult to determine the reporting obligation, and suggested that “any conduct that constitutes actively seeking to represent should be limited to actions undertaken during the reporting period about which a union official is filing and not extend to conduct completed in prior reporting years.”</P>
                    <P>
                        The Department disagrees with these commenters' criticism of the definition of “actively seeking to represent.” First, the matters related to top-down reporting have been addressed in the previous section on that topic, and the Department reiterates that the limiting of such reporting to union officials with significant authority or influence over lower level unions (all officers and those employees with such influence or authority) will alleviate much of the commenters' concern. Second, the criticism of the definition as overbroad, with “vague triggers,” and without “objective” criteria, is unpersuasive. The definition is narrowly tailored to acts that constitute concrete steps towards organizing, as opposed to merely having an interest in organizing. See the 2007 rule at 72 FR 36131. The enumerated acts are objective in nature, as they are activities that unions as a whole generally take to seek recognition, and they illustrate “concrete steps” toward acquiring exclusive bargaining representative status. Pursuant to the terms of the definition, the activities, as well as the payments to be reported, must occur during the particular fiscal year in question. Limiting “actively seeking to represent” to “demanding recognition or filing an NLRB petition” does not constitute the entire universe of “concrete steps” that a union can take to 
                        <E T="03">actively</E>
                         seek representation. Thus, creating such a limitation would unduly limit reporting.
                    </P>
                    <P>Moreover, while the activities listed are specific, the “otherwise committing labor or financial resources to seek representation of employees working for the employer” language is necessary, as the Department cannot enumerate every conceivable scenario that constitutes a situation in which a union is “actively seeking to represent” employees. In this regard, the term “actively seeking to represent” derives from the statute, and the definition is a reasonable attempt to give meaning to the term. The definition of “actively seeking to represent” will aid filers in complying with the reporting requirements, and, as with the definition of “substantial part,” a filer can request assistance from the Department if he or she is having difficulty determining if reporting is required. Again, pursuant to the statute, criminal liability is triggered only upon a showing of willfulness.</P>
                    <P>A federation of international labor unions urged the Department to make two changes to the definition of “actively seeking to represent.” First, the commenter suggested that the word “concrete” be added before the word “steps,” so that the first sentence of the definition would begin,</P>
                    <P>
                        “
                        <E T="03">Actively Seeking to Represent</E>
                        —means that a labor organization has taken 
                        <E T="03">Concrete</E>
                         steps during your fiscal year to become the bargaining representative of the employees of an employer, including but not limited to * * *” (emphasis added).
                    </P>
                    <P>
                        The commenter noted that adding the word “concrete” would make the definition consistent with the Department's rationale for the definition as stated in the 2007 rule,
                        <SU>47</SU>
                        <FTREF/>
                         and would “advance both the public interest in clarifying the Department's intent and the legitimate interests of union officials subject to the rule.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>47</SU>
                             In the 2007 rule, the Department explained “that the term `actively seeking to represent' is intended to distinguish between situations where a union has taken 
                            <E T="03">concrete steps to organize</E>
                             and those where the union 
                            <E T="03">merely has an interest in organizing</E>
                             employees of the employer in question.” 72 FR 36131 (emphasis added).
                        </P>
                    </FTNT>
                    <P>
                        Second, the commenter stated that two examples of union “steps” that would constitute “actively seeking to represent” are in conflict with the Department's stated rationale for the definition in the 2007 rule. The commenter urged the Department to revise the examples as follows (note that the commenter's suggested additions are 
                        <PRTPAGE P="66475"/>
                        in italics): (1) Sending organizers to an employer's facility 
                        <E T="03">to solicit employee support for the union;</E>
                         and (2) Handing out leaflets 
                        <E T="03">seeking or urging employee support for the union.”</E>
                    </P>
                    <P>
                        The Department believes that the federation's first suggestion, to insert the term “concrete” into the definition of “actively seeking to represent,” would provide filers with additional clarity. The Department considers such addition to be consistent with the stated purpose of the definition, which is to view only 
                        <E T="03">concrete</E>
                         steps as constituting “actively” seeking to represent. The Department does not view this change as a material revision to the current rule and is making the change.
                    </P>
                    <P>The second suggestion would require the rule to be modified in a substantial way and therefore is beyond the scope of this rule. The Department, however, notes its disagreement with the commenter's suggestions, as there are concrete steps that a union can take in actively seeking to represent employees other than sending organizers to an employer's facility expressly soliciting employee support for the union or handing out leaflets expressly seeking or urging employee support for the union.</P>
                    <HD SOURCE="HD3">3. Definition of “Labor Organization Officer” in Section 202</HD>
                    <P>
                        The LMRDA defines “labor organization officer” in section 3(n).
                        <SU>48</SU>
                        <FTREF/>
                         The 2007 Form LM-30 Instructions further clarifies this definition as set out in the margin.
                        <SU>49</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>48</SU>
                             
                        </P>
                        “Officer” means any constitutional officer, any person authorized to perform the functions of president, vice president, secretary, treasurer, or other executive functions of a labor organization, and any member of its executive board or similar governing body. LMRDA section 3(n).
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>49</SU>
                             
                        </P>
                        Labor organization officer means any constitutional officer, any person authorized to perform the functions of president, vice president, secretary, treasurer, or other executive functions of a labor organization, and any member of its executive board or similar governing body. An officer is (1) a person identified as an officer by the constitution and bylaws of the labor organization; (2) any person authorized to perform the functions of president, vice president, secretary, or treasurer; (3) any person who in fact has executive or policy-making authority or responsibility; and (4) a member of a group identified as an executive board or a body which is vested with functions normally performed by an executive board. 
                        <P>
                            <E T="04">Note:</E>
                             Under this definition, an officer includes a trustee appointed by the national or international union to administer a local union in trusteeship. If you are a trustee elected or appointed by the local union to audit and/or hold the assets of the union, you may or may not be a union officer, depending on your union's constitution and other factors. If you serve in your union in any capacity and you are unsure if your position is an officer position, you are likely an officer of a labor organization if any one of the following applies:
                        </P>
                        <P>• Your union's constitution or bylaws refers to your position as an officer of the union </P>
                        <P>• Your union's constitution or bylaws states that your position has the authority to make executive decisions for the union or that you are authorized to perform the functions of president, vice president, secretary, treasurer, or other constitutionally designated officer </P>
                        <P>• Your union's annual Form LM-2 or Form LM-3 lists your position as an officer of the union </P>
                        <P>• In your position, you serve on your union's executive board or similar governing body </P>
                        <P>See Definition 12, 2007 Form LM-30 Instructions.</P>
                    </FTNT>
                    <P>One national/international union commenter requested that the Department amend the definition of “labor organization officer” so that it is limited to “individuals who are named officers holding positions given policy-making authority pursuant to the union constitution and bylaws.” The commenter stated that the Department's definition is overbroad and could result in the Form LM-30 reporting requirements extending to a union member who was unaware that he would be subject to Form LM-30 reporting requirements, including the top-down reporting obligation. The commenter views the current definition as reaching individuals the statute did not intend to reach, such as “unsuspecting rank-and-file members.”</P>
                    <P>The Department disagrees with the commenter's views on this issue. The rule's definition of “labor organization officer” is derived directly from section 3(n) of the statute, and merely provides further clarification of the term and, as an example, states under what circumstances a trustee may be a union officer. The Department does not view the definition as exceeding the scope or intent of section 3(n). Moreover, the Department notes that pursuant to section 3(n) and the “retained” Form LM-30 definition, rank-and-file union members and other volunteers, such as stewards, would not ordinarily be covered union officers.</P>
                    <HD SOURCE="HD3">4. Reporting of Director's Fees</HD>
                    <P>The 2007 rule requires that a union official who receives “director's fees” from an employer generally must report these payments. The Department did not propose to eliminate this requirement. A law firm opposed the requirement to director's fees to be reported on Form LM-30. The Department rejects the suggestion to remove this requirement, as this was not a change proposed in the NPRM, and, furthermore, a union official's service on a board of directors, and the accompanying fee, may influence the official's duties to the union.</P>
                    <HD SOURCE="HD3">5. De Minimis Exemptions</HD>
                    <P>
                        The 2007 rule adopted several de minimis exemptions, including: A $250 reporting threshold; a $20 recordkeeping threshold; and a “widely-attended gathering” standard. The widely-attended gathering provision exempts reporting of payments or gifts received while in attendance at up to two of such gatherings per fiscal year for which an employer or business has spent $125 or less per employee per gathering. See the 2007 Form LM-30 Instructions, page 2. The Department has long had a de minimis exemption for Form LM-30 reporting, which derives from LMRDA Interpretative Manual sections 241.700 and 241.710, although historically the exemption there applied to payments of “insubstantial value,” without providing a quantitative threshold.
                        <SU>50</SU>
                        <FTREF/>
                         The 2007 rule retained a prior $100 exemption for unregistered securities, which existed in the pre-2007 Form LM-30 Instructions. The Department proposed no change to this exemption or the de minimis thresholds.
                    </P>
                    <FTNT>
                        <P>
                            <SU>50</SU>
                             
                        </P>
                        In 2005, a reporting exemption of $25 was established, which the 2007 rule subsequently raised to $250. Additionally, IM section 241.700 requires that the payments of insubstantial value be “given under circumstances unrelated to the recipient's status in a labor organization.” Neither the 2007 rule nor the revised rule have this requirement.
                    </FTNT>
                    <P>
                        Three commenters were pleased that the Department had not proposed to eliminate the de minimis exemption, but suggested that the Department consider revising the dollar thresholds for reporting and linking them to a cost-of-living or other automatic adjustment mechanism. A law firm expressed support for the 2007 rule's de minimis exemptions,
                        <SU>51</SU>
                        <FTREF/>
                         but suggested that the de minimis thresholds be revised. The commenter urged the Department to increase the $20 and $250 de minimis thresholds to $50 and $500, respectively, and to increase the widely-attended gathering exclusion from $125 to $150.
                    </P>
                    <FTNT>
                        <P>
                            <SU>51</SU>
                             
                        </P>
                        This commenter also urged the Department to implement the same de minimis thresholds for Form LM-10 reporting. Since this issue is beyond the scope of this rule, the Department acknowledges this suggestion, but will not address it in this rule.
                    </FTNT>
                    <P>
                        Although the suggestions are beyond the scope of this rule, the Department is not persuaded that a $50 recordkeeping threshold, a $500 reporting threshold, and a $150 widely-attended gathering threshold are more appropriate than the current $20, $250, and $125 thresholds, respectively. The Department views the current levels, based on dollar values, as providing a reasonable distinction, applied nationally, between gifts that may create a conflict of interest and those that do not. The commenter did not provide any persuasive justification for why the increased amounts would better distinguish between gifts that may “conflict” and those that do not.
                        <PRTPAGE P="66476"/>
                    </P>
                    <P>A national/international union commenter urged the Department to revise the de minimis thresholds, arguing that they are too low given the steep costs of meals and entertainment charged by hotels located in large metropolitan areas. The commenter provided examples of conference rates at hotels where meetings are held, and listed examples of the lowest cost food items available, many of which exceed the $20 de minimis threshold.</P>
                    <P>The commenter also expressed concern that reporting such conference and meal rates on Form LM-30 “would very likely mislead union members and provide fodder for anti-union consultants.” The commenter added, “To many union members, disclosing such large sums received for meals might well call to mind lavish entertainment and cause concern about possible susceptibility to improper influence * * * However, the reality would [be] quite different—literally nothing more than a few bagels and sandwiches, which the membership would not care about if they knew the true facts. But under current rules, those members would see a formal Government filing, presumably to deal with something significant, and get exactly the wrong impression about their representatives.”</P>
                    <P>The commenter noted that inflation will decrease the value of all de minimis thresholds contained in the proposed Form LM-30, and cautioned that the de minimis threshold problem will become more significant with time. Finally, the commenter urged the Department to adopt a method for establishing de minimis thresholds that reflect the realities of union officials' circumstances, and cited the per diem rates paid by government agencies as an example.</P>
                    <P>The Department disagrees with this commenter's suggestion to use different de minimis thresholds, varying by locality or setting them to a level based on the charges assessed for “meals and entertainment * * * by hotels located in large metropolitan areas.” In the Department's view, it would be impractical to establish varying rates by locality, and pegging them to the most expensive charges for modest meals and other gratuities would create too high of a dollar threshold, thus potentially excluding from reporting actual or potential conflicts of interest. Moreover, “steep costs” and “large sums” provided by a represented employer and certain key businesses to union officials are precisely the types of payments that should be reported on the Form LM-30, to enable the members and the public to determine the impact, if any, on the officials' duties.</P>
                    <P>The members should have information concerning these payments in order to evaluate for themselves the effect on the officials' duties to the union, such as whether or not they constitute “lavish entertainment” and create possible “susceptibility to improper influence.” An official concerned with the appearance of a particular charge or charges could also provide further information on the Form LM-30 to provide increased context to the payments, which would diminish or eliminate the problem of members being misled or confused by the payments.</P>
                    <P>The Department does not concur with the suggestions to index the de minimis exemption thresholds with inflation or other quantitative or qualitative mechanisms. The exemption is provided to ensure that individuals are not required to report, and in some cases even track, payments that are of insubstantial value and not likely to constitute an actual or potential conflict of interest. Further, establishing a quantitative assessment for determining de minimis amounts is superior to a qualitative approach, as filers will easily know whether or not a payment is exempt, without asking the Department to apply a set of factors and determine whether or not the exemption is appropriate. Indexing the thresholds and establishing a fluctuating standard would jeopardize the convenience of the quantitative assessment and unnecessarily risk increasing the burden on union officials—with no apparent benefit in terms of transparency.</P>
                    <P>A law firm suggested that the Department clarify the exemption for attendance at widely-attended gatherings. In its view, the Department should revise the exemption so that “individuals associated with service providers to multiemployer plans, employers who contribute to such plans, and employer-appointed trustees of plans that are unrelated to the Form LM-30 filer's union may all be considered to be among the `substantial number of individuals with no relationship to a union or a trust in which a labor organization is interested.' ” The commenter argues that, without such clarification, the widely-attended gathering exception would be overly narrow, and union officials would need to “identify by sight the service providers to plans and employer-appointed trustees of plans with no relationship to their union or its affiliated plans in order to ascertain whether an event qualifies as a widely attended gathering.” The Department acknowledges the commenter's concern, but this rulemaking does not lend itself to addressing a particular activity that does not involve a change proposed by the Department. Without expressing a view on this matter, the Department notes that it is available to provide compliance assistance and guidance to filers on a case-by-case basis.</P>
                    <P>Additionally, a federation of international labor unions suggested that the exclusion of income from unregistered securities (on page 5, exclusion (ii)) be raised from $100 to $250 to achieve consistency with the General Exclusion for payments of $250 or less (page 4) of the instructions. A national/international labor union concurred with this suggestion. The Department disagrees with this proposal. In the Department's view, the $100 exemption for unregistered securities is reasonable and consistent with past exclusions provided by the Department. Further, there is no basis for concluding that the de minimis threshold for unregistered securities must be identical to the threshold for payments, such as gifts and gratuities, received.</P>
                    <HD SOURCE="HD3">6. Value Range Reporting of Financial Arrangements and Interests</HD>
                    <P>A national union commenter suggested that item 7(b) in Part A of the revised form, and item 12(b) in Part B, be modified to include valuation categories (covering different ranges of dollar values, such as between $5,000 and $10,000 or $10,000 to $15,000) that filers would use to disclose the estimated value of financial arrangements and interests. The commenter stated that “the applicable statutory language in the LMRDA is completely silent regarding whether union officials have to report the exact value of a financial interest, or whether an approximate range is sufficient.” The commenter stated that, for example, requiring the reporting of a “value range” of a particular stock would adjust for possible fluctuation in the stock's value, and noted the difficulty of determining “a good faith estimate” due to the potential for significant fluctuation in the value of a financial transaction or asset. The commenter also indicated that Congress and the Office of Government Ethics apply these types of valuation categories to the disclosure requirements concerning presidential appointees' financial interests.</P>
                    <P>
                        The Department disagrees that this approach to reporting would increase the utility of the form. Introducing a complex requirement actually may increase the reporting burden on filers. Additionally, the commenter presented 
                        <PRTPAGE P="66477"/>
                        no information or analysis as to how this would increase transparency regarding actual or potential conflicts of interest.
                    </P>
                    <HD SOURCE="HD3">7. Alternative Views of Reporting Required by Section 202</HD>
                    <P>An international union representing professional athletes, supported by a federation of unions, provided statutory analysis in support of an argument that an endorsement arrangement is not reportable on Form LM-30. The commenter asserted that sections 202(a)(3) and (4) should be interpreted to apply only to businesses in which the union official has an ownership interest. The commenter's position, at bottom, reduces to a claim that the use by Congress of the word “derives,” rather than “received” in these sections evinces a plain intention that the interests to be reported are solely “ownership interests.”</P>
                    <P>
                        As a general matter, the language of sections 202(a)(3) and (4) does not provide for this limitation. First, a union officer must file “a signed report listing * * * any * * * interest * * * and any income or other benefit with monetary value (including reimbursed expenses) * * * derived from, 
                        <E T="03">any</E>
                         business.” 29 U.S.C. 432(a)(3), (4) (emphasis added). The term “any business” cannot easily be read to mean “any business in which the union officer or employee owns an interest.” Second, the commenter asserts that in normal usage the word “derives” is used “in lieu of * * * received from” and indicates that the payment is from a business to an individual who holds an ownership interest. But the statute uses the term “derived” to describe a category of income that includes “payments and other benefits received as a bona fide employee.” 29 U.S.C. 432(a)(1), (2). As income “derived” includes “payments received,” Congress was not using “derived” in the limited sense suggested by the commenter. Additionally, the Department notes that the crucial distinction between “derives” and “receives” that the commenter attributes to these terms is not borne out by their common understanding as synonyms. See, 
                        <E T="03">e.g.,</E>
                         “Derive” “to take, receive, or obtain, esp. from a specified source.” Merriam-Webster's Collegiate Dictionary (10th ed. 2002); “Receive” “to come into possession of: ACQUIRE &lt; ~ a gift &gt;”. 
                        <E T="03">Id.</E>
                         There is simply no persuasive argument that the plain language of these sections evinces the “ownership” delimited meaning the commenter would attribute to the use of “derived.”
                    </P>
                    <P>Further, the interpretation would exclude from reporting payments and gratuities provided by a vendor or service provider to a union official seeking to generate business with the official's union. This plain potential conflict of interest would go unreported, unless the union official held an ownership interest in the business.</P>
                    <P>The Department has also considered the additional arguments advanced by the commenter, including its assertion that the legislative history supports its narrow view of what must be reported under these sections. Upon review, the legislative history relied upon by the commenter cannot be fairly read to reflect the narrow construction it would force upon these sections. The commenter also suggests that its preferred reading of sections 202(a)(3) and (4) and the legislative history is embodied in the Department's own early interpretation of these provisions. The commenter relies on a general discussion in the Department's 1961 annual report about its then recent filing experience under the Act. In context, however, it is clear that the Department, in making these statements, was not offering an interpretation of sections 202(a)(3) and (4). Instead, the Department was merely reporting on its early experience with reports under sections 202 and 203 of the Act. Further, in any event, these statements do not evince an interpretation that limits an official's reporting obligation under section 202 to “ownership interests.”</P>
                    <P>
                        The commenter candidly acknowledges that the meaning it attributes to the “1961 interpretation” is at odds with the Department's published interpretation that states: “Union officers who receive complimentary hotel rooms and other gratuities of substantial value from the hotel at which the union holds its convention are required to report pursuant to section 202(a)(4).” Interpretative Manual, section 246.400. Although the commenter indicates that this interpretation was issued by the Department sometime after 1984, the interpretation, in fact, was issued in 1964.
                        <SU>52</SU>
                        <FTREF/>
                         Thus, the position set forth in the LMRDA Interpretative Manual demonstrates that the position taken by the Department in the 2007 rule was not a new one.
                    </P>
                    <FTNT>
                        <P>
                            <SU>52</SU>
                             The LMRDA was enforced by various offices within the Department prior to 1984, when OLMS was established. The commenter inferred that since the interpretation was contained in a publication issued by OLMS, it could not have predated 1984. The Department's internal files show that the interpretation is dated July 1964.
                        </P>
                    </FTNT>
                    <P>
                        The Department believes that its interpretation that requires union officials to report gifts, gratuities, and other payments received by union officials from companies that do business with the official's union or represented employees is faithful to congressional intent. For the same reasons, the Department rejects the commenter's alternative request that even if the Department disagrees with its statutory arguments, the Department should create an exception for its members due to what it considers an unnecessary and undue burden on its officials.
                        <SU>53</SU>
                        <FTREF/>
                         Another commenter representing employees working in the entertainment industry requested that its officials be exempted from reporting certain gratuities, which it claimed were unique to the union and its members' industry. This exemption request is outside of the scope of the rule, would seemingly require a fact-based analysis, and could not in any event be resolved on this limited record.
                    </P>
                    <FTNT>
                        <P>
                            <SU>53</SU>
                             The commenter states that “out of an excess of caution” the union's officials have been reporting these payments because of the difficulty they have in determining whether the companies they receive payments from conduct substantial business (10% or greater) with the league. The Department emphasizes that payments from a company doing business with a represented employer are reportable only if the business is greater than 10% or more of the company's annual receipts. The Department notes that the commenter does not state whether filers have made any inquiries regarding the extent of business conducted between the companies making payments and the league. As stated in the preamble to the 2007 rule, the Department is available to assist filers in obtaining such information if their own efforts are unsuccessful. See 72 FR 36134.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">
                        IV. Revisions to the Regulations, Form, and Instructions 
                        <E T="51">54</E>
                    </HD>
                    <P>
                        This final 
                        <FTREF/>
                        rule revises the Form LM-30 in order to simplify its use by filers by reducing the length of the form (from nine pages to two pages) and its instructions (from 22 pages to 13 pages) and eliminating or modifying some reporting requirements. The Department identifies below the various changes effectuated by the final rule to the Department's regulations implementing section 202, 29 CFR 404.4, the Form LM-30, and its accompanying instructions, which are incorporated into the regulations by reference. 29 CFR 404.3.
                    </P>
                    <FTNT>
                        <P>
                            <SU>54</SU>
                             For the convenience of LM-30 filers and the public, this section restates most of the information contained in the comparable section of the NPRM, revised as necessary to reflect differences between the proposed and final rules. See 74 FR 48430-35.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">A. Regulations</HD>
                    <P>
                        Only one change has been made to the regulatory text. 29 CFR 404.1(f). In section 404.1(f), the Department removes the definition of “labor organization,” which had been added in the 2007 rule to establish the scope of reporting required of higher-level union officers. Paragraphs (g) through (j) of 
                        <PRTPAGE P="66478"/>
                        section 404.1 also will be re-designated as (f) through (i), respectively. The term “labor organization” is separately defined in the LMRDA, and language regarding the scope of reporting for national, international, and intermediate union officers and employees has been added to the revised instructions.
                    </P>
                    <HD SOURCE="HD2">B. Revised Form</HD>
                    <P>The revised Form LM-30 utilizes a simplified format that will better facilitate filers' compliance with Form LM-30 reporting requirements and increase the form's utility to the public. Unless otherwise noted, the revised form and instructions adopted by this rule are the same as those proposed in the NPRM. Further, the Department will address below comments received on the layout of the form and instructions.</P>
                    <P>With respect to layout, the revised form more closely resembles the pre-2007 form than the lengthier 2007 form. The revised form, which is two pages in length, contains four sections: a section that contains basic identifying information on the filer and his or her labor organization, and Parts A through C. Part A is designed to capture reportable transactions between union officials and represented employers. Part B captures reportable transactions with businesses that deal with the official's union or a trust in which the union has an interest, or that have substantial dealings with a represented employer. Part C covers transactions with other employers or labor relations consultants. The form has been simplified by removing numerous schedules, checklists, and examples. While the inclusion of this information in the 2007 form was intended to assist filers, it is the Department's present view that these additions made the form more confusing and difficult to complete.</P>
                    <P>The revised form does not contain the summary schedule that was on the first page (item 5) of the 2007 form. The Department does not believe that requiring a summary schedule to report “total reported income or other payments” and “total reported assets” is useful information, by itself, and may be misleading. Without knowing the context of the reportable transaction or transactions, a viewer does not have a basis to assess the actual or potential conflict of interest and the impact such a conflict would have on the official's duties to the labor organization. For a filer with multiple payments, a summed total on the front page of the form is misleading, even if the totals are separated by assets and other payments, since a viewer of the form can only judge a conflict of interest by looking at the monetary value of the payment or interest along with its source and other pertinent information. A sum of money or other payment or asset, in and of itself, has no meaning, and can lead to confusion for the viewer and reflect unfairly on the filer. Further, presenting a figure for “total reported income or other payments” gives the impression that this total represents payments received by the filer, when in fact, this figure might also include items such as interest in personal or real property, insurance, or share holdings.</P>
                    <P>The revised form does not contain sections on Employer and Business Relationships (items 6 and 7, respectively, on the 2007 form). The Department does not believe that this general information adds to the usefulness of the form, because this information is reported on each schedule. A bulleted checklist listing various reportable relationships has also been eliminated.</P>
                    <P>
                        The revised form's contact information sections in Parts A, B, and C generally collect the same information requested in Schedule 1 of the 2007 form, except that the revised form does not ask whether the filer, filer's spouse, or minor child had a relationship with the employer, business, or labor relations consultant 
                        <E T="03">at the end of the reporting period.</E>
                         The Department received no comments on this proposed change. The revised form also eliminates the requirement that a filer provide the Web site address of the employer, business, or labor relations consultant in which the filer holds an interest or receives a payment. The Department does not believe that the Web site address is necessary, since viewers of the form can independently locate this information.
                    </P>
                    <P>In place of the separate Additional Information Schedule, which was included in the 2007 form, the revised instructions simply provide guidance on how to provide additional information. Filers who choose to complete the Form LM-30 in paper format are instructed to attach a separate letter-size page, with identifying information. Filers who complete the Form LM-30 electronically will be able to add additional information as needed.</P>
                    <P>In response to the NPRM, ten labor organizations—one federation of labor organizations and nine international unions—submitted comments on the content and layout of the LM-30 form and instructions. All ten commenters expressed support of the Department's proposed revisions and endorsed the decision to adopt a form similar to the pre-2007 form. Multiple commenters described this earlier form as “simpler” and “more straight-forward” than the 2007 form. The commenters that generally opposed any changes to the 2007 rule did not comment on the content and layout of the form and instructions.</P>
                    <P>The federation of labor organizations expressed support for the Department's proposed revisions to the form and instructions, with noted exceptions. The commenter stated that its experience providing training to union officials on their reporting obligations “indicates that the vastly more complicated form and instructions adopted by the 2007 rule would have been very difficult for union officials to understand and complete,” and would likely have resulted in a lower level of compliance than under a simpler report. This commenter also suggested several changes to the proposed form and instructions. These suggested modifications will be discussed below, in the specific form/instructions sections to which they pertain. Two international union commenters concurred with the comments submitted by the federation of labor organizations, including suggested changes to the form and instructions.</P>
                    <P>Three international union commenters expressed support for the Department's proposal, but suggested some additional modifications to the form and instructions. These suggestions will be discussed in the relevant form/instructions sections below.</P>
                    <P>Multiple commenters asserted that the 2007 Form LM-30 reporting requirements were overly burdensome, confusing, and complicated, and questioned the purpose of the increased disclosure obligation. An international union commenter stated that “[t]he 2007 form was extremely burdensome to filers, and confusing and misleading to the public.” Another international union commenter described the 2007 form as “virtually indecipherable.” Another international union commenter stated that the trainings for union officers and employees would have been “unnecessarily complicated—to no useful purpose—had the Department determined to use the new form and instructions proposed in 2007.”</P>
                    <P>
                        An additional international union stated that “[t]he Department's proposal correctly recognizes the unnecessary over-complication, confusion, and burden caused by its 2007 rule. The new form and instructions strike the correct balance between the Act's twin goals of requiring disclosure of conflict transactions and not creating unnecessary reporting burdens for union officials.”
                        <PRTPAGE P="66479"/>
                    </P>
                    <P>Another international union commenter stated that “the changes to the form[ ] and instructions improve clarity, eliminate redundancy, and reduce the amount of unnecessary information currently required to be filed.” The commenter added that the changes “permit the DOL to more effectively fulfill the goals of the LMRDA reporting requirements in disclosing conflicts of interest.” This commenter also stated its view that the changes will help filers comply with the LM-30 reporting obligation more “efficiently” and “cost effectively” than under the 2007 rule.</P>
                    <HD SOURCE="HD1">Section-by-Section Discussion of Revised Form</HD>
                    <P>A section-by-section discussion of the revised form follows:</P>
                    <HD SOURCE="HD3">First Section—Basic Identifying Information (Items 1-5)</HD>
                    <P>The first section of the revised form gathers basic information about the filer and his or her labor organization. Item 1 requests the Form LM-30 file number, and item 2 calls for the fiscal year covered in the report. Item 3 provides a box to identify whether the form is being filed as an amended report. The filer must provide his or her contact information in item 4, which includes lines for his or her name and street address (both required), and an email address (optional). In item 5, the filer provides identifying information about his or her labor organization, indicates whether he or she is an officer or employee, and notes his or her officer position or job title. If the filer serves as an officer or employee in more than one labor organization, this information is captured on an item 5 Continuation Page.</P>
                    <P>Below the first section, the revised form states, “Complete Part A, B, or C if, during the past fiscal year, you or your spouse or minor child directly or indirectly had a reportable interest in, transaction or arrangement with, or received income, payment, or benefit from the entities described below.”</P>
                    <HD SOURCE="HD3">Part A—Represented Employer (Items 6 and 7)</HD>
                    <P>In the revised form, “Represented Employer” is defined as “an employer whose employees your labor organization represents or it is actively seeking to represent.” If the filer had a reportable interest, transaction, benefit, arrangement, income, or loan from his/her “Represented Employer,” he or she must provide in item 6 the employer's contact information, including the name and telephone number of a contact person. In item 7a, the filer provides the nature of the interest, transaction, benefit, arrangement, income, or loan; in item 7b, the filer enters its amount or value. As stated above, the Department has removed the requirement that filers report the Web site address for the employer.</P>
                    <P>As will be explained in the Revised Instructions section below, the filer must complete a separate Part A for each transaction reported. A Continuation Button is located below Part A if the filer needs to complete one or more additional Part As.</P>
                    <HD SOURCE="HD3">Part B—Business (Items 8-12)</HD>
                    <P>The revised form requires the filer to complete Part B if he or she had a reportable interest in, transaction or arrangement with, or received income, payment, or benefit from “[a] business, such as a vendor or service provider, (1) A substantial part of which consists of buying from, selling or leasing to, or otherwise dealing with the business of a Represented Employer described in Part A or (2) any part of which consists of buying from or selling or leasing directly or indirectly to, or otherwise dealing with your labor organization or with a trust in which your labor organization is interested.”</P>
                    <P>If the filer has reportable activity with such a business, he or she must provide in item 8 the contact information for the business, including the name and telephone number of a contact person. In item 9, the filer must indicate the entity the business deals with by checking the box for (a) Labor organization, (b) trust, or (c) employer. If the filer checks the box for trust or employer, he or she must provide the trust or employer's name and contact information in item 10. The filer must describe the nature of the dealings in item 11a, and report the value of the dealings in item 11b. Additionally, the filer must describe in item 12a the nature of the interest, benefit, arrangement, or income and report in item 12b the amount or value of the interest, benefit, arrangement, or income. As stated above, the Department has removed the requirement that filers report the Web site address for the business. As will be explained in the Revised Instructions section below, the filer must complete a separate Part B for each transaction reported. A Continuation Button is located below Part B if the filer needs to complete one or more additional Part Bs.</P>
                    <HD SOURCE="HD3">Part C—Other Employer or Labor Relations Consultant (Items 13 and 14)</HD>
                    <P>The revised form requires the filer to complete Part C if he or she had a reportable interest in, transaction or arrangement with, or received income, payment, or benefit from “an employer (other than a Represented Employer or Business covered under Parts A and B above) from whom a payment would create an actual or potential conflict between your personal financial interests and the interests of your labor organization (or your duties to your labor organization); or a labor relations consultant to such an employer or to the Represented Employer listed in Part A.”</P>
                    <P>If the filer has reportable activity with such an employer or labor relations consultant, he or she must provide in item 13a the contact information for the employer or labor relations consultant. In item 13b, the filer must indicate whether the entity is an employer or consultant. The filer must describe the nature of the payment in item 14a, and report the amount or value of the payment in item 14b. As stated above, the Department has removed the requirement that filers report the Web site address for the employer or labor relations consultant.</P>
                    <P>As will be explained in the Revised Instructions section below, the filer must complete a separate Part C for each transaction. A Continuation Button is located below Part C if the filer needs to complete one or more additional Part Cs.</P>
                    <P>In its comments submitted in response to the NPRM, a federation of labor organizations suggested that “Contact name” and “Telephone” be removed from Part A (item 6), Part B (items 8 and 10), and Part C (item 13a). The commenter stated that filers are not in the position to designate a contact person for employers and businesses. The commenter added that “inviting inquiries to the employer or business from members of the general public seems inadvisable,” especially since the Department could make such inquiries. The Department disagrees. In its view, filers should be able to easily ascertain the contact information for an employer or business from which they have received income, a gift, or another benefit, or in which the filer has an interest, or otherwise has engaged in a business transaction or arrangement. Further, the reporting of this contact information will assist union members and the public to cross-check information reported on Forms LM-10 and Forms LM-30, and assist the Department in determining reporting compliance.</P>
                    <HD SOURCE="HD3">Signature and Verification (Item 15)</HD>
                    <P>
                        The filer must provide his or her signature, date, and telephone number in item 15, which is located on the 
                        <PRTPAGE P="66480"/>
                        bottom of the first page. As explained in the instructions, filers are instructed to view the OLMS Web site for further information on how to electronically sign and submit the Form LM-30. The signature line on the revised form is identical to that on the 2007 form, except that the revised form assigns the heading “Signature and Verification” to item 15. The signature line on the 2007 form did not include a heading.
                    </P>
                    <HD SOURCE="HD2">C. Revised Form LM-30 Instructions</HD>
                    <HD SOURCE="HD3">1. General</HD>
                    <P>The revised instructions reflect significant changes in both layout and content from the 2007 form. The content has been changed to reflect the specific changes adopted by this rule, as discussed earlier in this preamble. Other changes have been made to add clarity and eliminate unnecessary repetition. The discussion immediately below highlights significant changes between the revised and 2007 instructions.</P>
                    <P>As noted above, the revised form and instructions reinstate the general “Parts A, B, and C” format featured in the pre-2007 form and instructions, replacing the multiple-schedule format introduced by the 2007 rule. The revised format is clearer and more streamlined and will make the form much easier for filers to understand and complete, without affecting the usefulness of the information disclosed.</P>
                    <P>The revised instructions do not include a separate “Definitions” section, which was included in the 2007 instructions. The revised instructions instead present definitions and clarifications of key terms in the context of the sections in which they first appear in the document. When a definition follows a section of the instructions, the term to be defined is italicized. Further, if a defined term is used in multiple places, the later references refer back to the section in which the term is first used and defined. This approach will help filers understand key terms as they read through the instructions, and will eliminate the need for filers to frequently refer to a separate “Definitions” section to determine what must be reported and how it must be reported.</P>
                    <P>The Department has removed the examples that are dispersed throughout the 2007 instructions. These examples, many of which involved situations confronted by a very small number of filers, made the form unnecessarily complex and difficult to complete, without meeting the intended goal of providing helpful guidance. Following the publication of a revised Form LM-30, the Department intends to provide compliance assistance support to Form LM-30 filers.</P>
                    <P>Additionally, the Department has substantively modified the definitions of some key terms that are found in the 2007 Form LM-30 Instructions. First, the Department has removed the definition of “bona fide employee” as used in the 2007 rule and added the bona fide employee exemption found in the instructions for the pre-2007 form, with minor edits for clarity, as explained below. The language that was added reads:</P>
                    <EXTRACT>
                        <P>
                            Payments and benefits received 
                            <E T="03">as a bona fide employee</E>
                             of the employer for past or present services, including wages, payments or benefits received under a bona fide health, welfare, pension, vacation, training or other benefit plan; and payments for periods in which such employee engaged in activities other than productive work, if the payments for such period of time are: (a) Required by law or a bona-fide collective bargaining agreement, or (b) made pursuant to a custom or practice under such collective bargaining agreement, or (c) made pursuant to a policy, custom or practice with respect to employment in the establishment which the employer has adopted without regard to such employee's position with a labor organization.
                            <SU>55</SU>
                            <FTREF/>
                             (emphasis added). 
                        </P>
                        <FTNT>
                            <P>
                                <SU>55</SU>
                                 The final part of the instructions read, in the pre-2007 Form LM-30 Instructions and in the NPRM, as: “or (c) made pursuant to a policy, custom or practice which the employer has adopted without regard to any holding by such employee of a position with a labor organization.” The Department made changes in the final rule to this language to ensure clarity.
                            </P>
                        </FTNT>
                    </EXTRACT>
                    <P>
                        Second, the Department has modified the definition of “labor organization employee.” As a result, the Department has inserted the following language into the revised Form LM-30 Instructions in Section II, Who Must File: “For purposes of the Form LM-30, an individual who serves the union as a union steward or as a similar union representative, such as a member of a safety committee or a bargaining committee, is not considered to be an employee of the union, 
                        <E T="03">by virtue of service in such capacity.</E>
                        ” (emphasis added). Note that the definition has been slightly modified from the NPRM for clarity purposes, as explained in Part III, Section B, with the addition in italics and removal of the word “exclusively” before the phrase “as a union steward.”
                    </P>
                    <P>Third, the Department has removed the definition of “labor organization” (Part III, D10), which had been added to the 2007 rule in order to describe the top-down reporting obligation of national, international, and intermediate body officers under section 202 of the LMRDA. As explained earlier in this preamble, the term “labor organization” is separately defined in the LMRDA.</P>
                    <P>Fourth, the instructions have been revised to reflect that, under this rule, employees of parent and intermediate unions have top-down reporting obligations if they have significant authority or influence over subordinate affiliates. Two exemptions for top-down reporting, established by the 2007 rule, have been eliminated. The Department had proposed that the top-down reporting obligation would apply to all employees of parent and intermediate unions, as had been established for all officers of such unions by the 2007 rule. In response to comments submitted on the proposal, the final rule has modified this requirement. Under the rule, only employees who possess significant authority or influence over subordinate affiliates must report on financial interests in, and payments from, companies that deal with the subordinate affiliates or companies that deal with or involve employers whose employees are represented by the affiliates.</P>
                    <P>The reasons for these changes are discussed in detail in section III of this rule.</P>
                    <HD SOURCE="HD3">2. Particular Sections and Parts</HD>
                    <P>
                        <E T="03">Section I, Why File:</E>
                         This section presents general information about the reporting requirements of section 202. This information is identical to that presented in the 2007 instructions, except that it has been simplified to refer to the individual completing the form as “you,” instead of “filer.”
                    </P>
                    <P>
                        <E T="03">Section II, Who Must File:</E>
                         The 2007 instructions presented a lengthy 
                        <E T="03">Section II, Who Must File and What Must Be Reported</E>
                         (located on pages 1-9). The revised instructions have divided this into two separate, concise sections, 
                        <E T="03">Section II, Who Must File</E>
                         and 
                        <E T="03">Section III, What Must Be Reported.</E>
                         The Department believes that this change will enable filers to more easily understand this basic information. This section states that “
                        <E T="03">(a)ny officer or employee of a labor organization</E>
                         (other than an employee performing clerical or custodial services exclusively), as defined by the LMRDA, must file Form LM-30 
                        <E T="03">if,</E>
                         during the past fiscal year, the officer or employee, or spouse, or minor child, either directly or indirectly, held any legal or equitable interest, received any payments, or engaged in transactions or arrangements (including loans) of the types described in these instructions.” “Labor organization employee” is defined as “any individual (other than an individual performing exclusively clerical or custodial services) employed by a labor 
                        <PRTPAGE P="66481"/>
                        organization within the meaning of any law of the United States relating to the employment of employees.” It also provides: “For purposes of the Form LM-30, an individual who serves the union as a union steward or as a similar union representative, such as a member of a safety committee or a bargaining committee, is not considered to be an employee of the union by virtue of service in such capacity.” The term “minor child” is also defined as someone younger than 21 years of age.
                    </P>
                    <P>
                        The reporting exceptions for insubstantial payments and gifts, including attendance at widely attended gatherings, are unchanged from the 2007 instructions, but their discussion has been moved to 
                        <E T="03">Section X, Completing Form LM-30.</E>
                    </P>
                    <P>
                        <E T="03">Section III, What Must Be Reported:</E>
                         This revised section simply refers filers to Parts A, B, and C of the instructions for information about financial transactions and interests that must be reported.
                    </P>
                    <P>
                        <E T="03">Section IV, Who Must Sign the Report:</E>
                         This section specifies that the labor organization officer or employee is required to sign the completed Form LM-30.
                    </P>
                    <P>
                        <E T="03">Section V, When to File:</E>
                         The information in this section is substantively identical to the information in 
                        <E T="03">Section IV, When to File</E>
                         in the 2007 instructions.
                    </P>
                    <P>
                        <E T="03">Section VI, How to File:</E>
                         The revised Form LM-30 may be submitted in paper format or electronically. Filers will be able to choose between the two options. Section VI provides information regarding these filing options, including how to obtain the form and instructions on submitting it from the OLMS Web site.
                    </P>
                    <P>The Department has significantly improved the electronic process for submitting the various LMRDA-required reports, including the Form LM-30, which simplifies the electronic signature procedure and eliminates the associated costs to filers. Specifically, the Department has implemented a simplified electronic signature that only requires the filer to acquire a Personal Identification Number (PIN) and password, which the Department provides at no cost to the filer. The Department believes that electronic reporting generally is easier for filers, and that it will enable the Department to better incorporate submitted forms into its Electronic Labor Organization Reporting System (e.LORS), ensuring easy access to information for the public.</P>
                    <P>
                        <E T="03">Section VII, Public Disclosure:</E>
                         With the exception of a slight change in wording, this section is unchanged from the 
                        <E T="03">Public Disclosure</E>
                         section in the 2007 instructions.
                    </P>
                    <P>
                        <E T="03">Section VIII, Officer and Employee Responsibilities and Penalties:</E>
                         With the exception of a slight change in wording in the first sentence (changed “required to file” to “required to sign”), this section of the revised instructions is identical to the information in the 
                        <E T="03">Section VII, Officer or Employee Responsibilities and Penalties</E>
                         in the 2007 instructions.
                    </P>
                    <P>
                        <E T="03">Section IX, Recordkeeping:</E>
                         This section contains information identical to that in the 
                        <E T="03">Recordkeeping</E>
                         section of the 2007 instructions.
                    </P>
                    <P>
                        <E T="03">Section X, Completing Form LM-30:</E>
                         This section presents detailed instructions on completing all of the information items in the Form LM-30. The Department believes that the placement of this section on page 3 of the revised instructions represents a significant improvement over the 2007 instructions, which did not provide this information until page 14.
                    </P>
                    <P>This section begins by providing information on electronically completing the form and explains that the Department will provide compliance assistance support for both paper format and electronic filing. The 2007 instructions did not provide this information. This section also provides information on completing Information Items 1 through 5, which gather basic identifying information about the filer and his or her labor organization. With the exception of minor changes in wording, these “basic identifying” information items are the same as in the 2007 instructions.</P>
                    <P>Next, the revised instructions feature the heading, “Information Items—Parts A, B, and C.” The revised form features the simpler “Parts A through C” approach, as opposed to the multiple-schedule format introduced in the 2007 form.</P>
                    <P>
                        First, the subsection “General Instructions for Reportable Transactions and Interests” begins with: “You must report if, during the past fiscal year you or your spouse or minor child, 
                        <E T="03">directly or indirectly:</E>
                         (1) Held an interest; (2) engaged in a transaction or arrangement (including loans); or (3) received income, payment or other benefit with monetary value covered by the Act.”
                    </P>
                    <P>Next, the instructions provide information on the scope of filing for national, international, and intermediate union officers and employees, which (as explained above in section III, part E, of this notice) requires some union employees (where they have significant authority or influence over subordinate affiliates) to report the same top-down information now required of union officers. This change is discussed in greater detail in section III, part E, of this notice.</P>
                    <P>The definition of “directly or indirectly” is presented immediately after this introductory language. This definition, including its two examples, is unchanged from the 2007 rule.</P>
                    <P>The revised subsection, General Exclusions, describes the general reporting exemptions, “insubstantial payments and gifts” and “widely-attended gatherings,” both of which are unchanged from the 2007 rule. In response to a suggestion submitted by a federation of labor organizations, the Department has moved the definition of “trust in which a labor organization is interested” from the General Instructions section (page 4) to the definition section in Part B (page 7) because the trust definition is relevant only to Part B. An international labor union also commented that the placement of the 3(l) trust definition in the General Exclusions section is confusing. The Department has made this change to eliminate any possible confusion about this point. This commenter also suggested that the instructions would benefit from adding a general exclusion to page 4 to indicate that filers do not have to report benefits received from a trust in which their labor organization is interested. The Department has also made this change, in order to clarify the removal of reporting of payments from trusts pursuant to section 202(a)(6).</P>
                    <P>A federation of labor organizations also suggested that the sentence referring to “director's fees, including reimbursed expenses” should be removed as “redundant and confusing” from the General Exclusions section of the General Instructions section on page 4, because it also appears in the instructions for Parts A and B. The Department disagrees because the instruction on reporting “director's fees” is a general requirement that applies to all three sections of the revised form. An international union commenter also stated that the sentence about “director's fees, including reimbursed expenses” that immediately follows the section 3(l) trust definition in the proposed instructions gives the erroneous impression that reporting such benefits from such trusts is required. The Department disagrees, noting that any such concern has been alleviated by moving the section 3(l) trust definition to the instructions for Part B.</P>
                    <P>
                        Filers are also instructed to complete a separate Part A, B, and/or C if they are reporting more than one entity or transaction. The instructions explain 
                        <PRTPAGE P="66482"/>
                        that additional Parts A, B, and C are available by clicking the Continuation Button on the electronic form or attaching a separate Part A, B, or C, if the filer is using a paper format.
                    </P>
                    <P>A federation of labor organizations suggested that this section, beginning with “Complete a separate Part A, B, and/or C” (page 4, left column), should be placed immediately before the “General Exclusions” instruction (page 4, left column). The commenter stated that the typeface and position of the headings make the “Complete a separate Part A, B, and/or C” section erroneously appear to be an exclusion. The Department agrees that this change would add clarity, and it has thus moved the “Complete a separate Part A, B, and/or C” title and instructions to before the “General Exclusions” section.</P>
                    <P>The commenter suggested that the “loan” example be removed from the instruction regarding completing separate Parts A, B or C (page 4, right column), because its inclusion here may cause confusion for filers because of the final rule's general exclusion for reporting bona fide loans. Instead, the commenter suggested using another reportable receipt, such as a “gift,” in the example. The Department has made this change in order to improve clarity.</P>
                    <PART>
                        <HD SOURCE="HED">PART A (ITEMS 6 AND 7): REPRESENTED EMPLOYER</HD>
                        <P>The revised instructions for Part A present information on how to complete items 6 and 7, which pertain to the Represented Employer. Specifically, the instructions state: “Complete Part A if you (1) Held an interest in, (2) engaged in transactions or arrangements (including loans) with, or (3) derived income or other economic benefit of monetary value from, an employer whose employees your labor organization represents or is actively seeking to represent.” The instructions state that payments received as “director's fees” must be reported. This requirement was contained in the 2007 instructions.</P>
                        <P>Next, the definition for “actively seeking to represent” is provided. This definition has been slightly revised in response to a comment by a federation of labor unions. As explained earlier in this preamble, the change adds clarity to the definition, which requires concrete steps towards organizing. The Department has not made any substantive changes to the definition as some commenters had suggested.</P>
                        <P>
                            The subsection, Part A Exclusions, lists items that do not need to be reported in Part A. The first three exclusions—(i), (ii), and (iii)—are substantively unchanged from the 2007 instructions. These relate, respectively, to holdings, transactions, and income from bona fide investments in securities traded on a national securities exchange; holdings, transactions, and income from other designated securities—of $1,000 or less; and transactions involving the purchases and sale of goods and services in the regular course of business at prices generally available to any employee of the employer (excluding loans or transactions involving interests in the employer).
                            <SU>56</SU>
                            <FTREF/>
                             The fourth exclusion, “Payments and benefits received as a 
                            <E T="03">bona fide employee”</E>
                             (emphasis added), has been modified to incorporate the historical interpretation given payments received by union officials under union leave and no docking policies established by collective bargaining agreements, practice under such agreements, or policy, custom, or practice adopted by an employer without regard to an employee's position with a union.
                        </P>
                        <FTNT>
                            <P>
                                <SU>56</SU>
                                 The exclusions, as published in the instructions to the 2010 NPRM are identical to those in the instant rule. See 75 FR 48450. The description of the exclusions in the preamble to the NPRM, however, did not accurately summarize the instructions. See 75 FR 48434.
                            </P>
                        </FTNT>
                        <P>Since the first Part A Exclusion refers to “bona fide investments,” this term is defined in this section. The definition for “bona fide investment” is unchanged from the 2007 rule. The instructions here advise that filers should not include bank account numbers, policy numbers, social security numbers, or similar identifying information in completing the form.</P>
                        <P>In the revised instructions, the following definitions are presented in connection with Information item 7: “arrangement,” “benefit with monetary value,” “income,” and “legal or equitable interest.” All of these definitions are unchanged from the 2007 rule. A clarifying note relating to the definition of “arrangement” has been revised to eliminate an example that is irrelevant to the definition.</P>
                        <P>A commenter suggested that the definition of “income” in the Part A, item 7 instruction (page 6) be modified to reference the exclusion of payments and benefits received as a “bona fide employee” (page 5). The commenter explained its view that defining “income” as “all income from whatever source derived, including but not limited to, compensation for services” could be confusing for filers as it appears to contradict the “bona fide employee” exclusion. The Department disagrees. Because the exclusions, including those paid to filers as bona fide employees, are first discussed in the instructions, it will be clear to filers that such payments are not reportable. Additionally, specific instructions are provided on how to complete items 6 and 7, which are described in the above subsection, Section-by Section Discussion of Revised Form.</P>
                        <P>This commenter suggested that the two examples preceding the “Other transactions or arrangements” heading in Part A (pages 6-7) be moved to Part B since they concern businesses that deal with the labor organization, not employers. The Department disagrees with the comment, as the examples, which derive from the 2007 instructions, are provided as part of the definition, and are intended to illustrate the application of the term “legal or equitable interest.” Moving the examples could create confusion because the term first appears in Part A of the form. While they contain examples of Part B businesses, the term “legal or equitable interest” appears also in Part A, and the Department believes that definitions should be placed in the part of the instructions where the term first appears.</P>
                    </PART>
                    <PART>
                        <HD SOURCE="HED">PART B (ITEMS 8-12): BUSINESS</HD>
                        <P>In the revised instructions, the filer is instructed:</P>
                        <EXTRACT>
                            <P>Complete Part B if you held an interest in or derived income or other benefit with monetary value, including reimbursed expenses, from a business (1) A substantial part of which consists of buying from, selling or leasing to, or otherwise dealing with the business of an employer whose employees your labor organization represents or is actively seeking to represent, or (2) any part of which consists of buying from or selling or leasing directly or indirectly to, or otherwise dealing with your labor organization or with a trust in which your labor organization is interested. Report payments received as director's fees, including reimbursed expenses.</P>
                        </EXTRACT>
                        <P>Definitions for “substantial part” and “dealing” are provided. These definitions are unchanged from the 2007 rule.</P>
                        <P>
                            The subsection, Part B Exclusions, lists items that do not need to be reported in Part B. Two of the Part B exclusions are retained from the 2007 rule (relating to holdings, transactions and income from bona fide investments in securities traded on a national securities exchange and other designated securities; and holdings or income of $1,000 or less from bona fide investments in other securities). These two Part B exclusions are the same as the exclusions set forth in (i) and (ii) in Part A. However, this rule excepts from reporting marketplace transactions from 
                            <PRTPAGE P="66483"/>
                            bona fide credit institutions, as explained in greater detail in section III, part C, of this notice. Specifically, the revised instructions read:
                        </P>
                        <P>
                            <E T="03">Bona fide loans.</E>
                             Do not report bona fide loans, including mortgages, received from national or state banks, credit unions, savings or loan associations, insurance companies, or other bona fide credit institutions, if the loans are based upon the credit institution's own criteria and made on terms unrelated to your status in the labor organization. Additionally, do not report other marketplace transactions with such bona fide credit institutions, such as credit card transactions (including unpaid balances) and interest and dividends paid on savings accounts, checking accounts or certificates of deposit if the payments and transactions are based upon the credit institution's own criteria and are made on terms unrelated to your status in the labor organization.
                        </P>
                        <P>Additionally, specific instructions are provided on how to complete items 8 through 12, which are described in the above subsection, Revised Form.</P>
                    </PART>
                    <PART>
                        <HD SOURCE="HED">PART C (ITEMS 13 AND 14): OTHER EMPLOYER OR LABOR RELATIONS CONSULTANT</HD>
                        <P>In the revised instructions, the filer is instructed:</P>
                        <EXTRACT>
                            <P>
                                Complete Part C if you, your spouse, or your minor child received, directly or indirectly, any payment of money or other thing of value (including reimbursed expenses) from any employer (other than a Represented Employer under Part A or Business covered under Part B above) from whom a payment would create an actual or potential conflict between these financial interests and the interest of your labor organization or your duties to your labor organization. Such employers include, but are not limited to, an employer in competition with an employer whose employees your labor organization represents or whose employees your union is actively seeking to represent, 
                                <E T="03">if you are involved with the organizing, collective bargaining, or contract administration activities or possess significant authority or influence over such activities. You are deemed to have such authority and influence if you possess authority by virtue of your position, even if you did not become involved in these activities.</E>
                                 Additionally, complete Part C if you received a payment of money or other thing of value from a labor relations consultant to a Represented Employer or Part C employer.
                                <SU>57</SU>
                                <FTREF/>
                            </P>
                            <FTNT>
                                <P>
                                    <SU>57</SU>
                                     As stated earlier in the preamble to this rule, the NPRM stated, “between 
                                    <E T="03">your</E>
                                     financial interests * * *.”  The Department has modified this phrase to “between 
                                    <E T="03">these</E>
                                     financial interests,” so filers are aware that they must look at the payments and interests of their spouse and minor children as well as their own.
                                </P>
                            </FTNT>
                        </EXTRACT>
                        <P>
                            The italicized language represents a change from the 2007 instructions, as explained in section III, part D, of this rule.
                            <SU>58</SU>
                            <FTREF/>
                             The Department removed “labor organizations” and “trusts in which your labor organization is interested” from the scope of Part C, as explained in section III, part D, of this preamble.
                        </P>
                        <FTNT>
                            <P>
                                <SU>58</SU>
                                 The Department notes that this quoted language is identical to the language in the proposed instructions see 75 FR 48450. The language was incorrectly set forth in the discussion of this point in the NPRM. See 75 FR 48434.
                            </P>
                        </FTNT>
                        <P>The subsection, Part C Exclusions, lists items that do not need to be reported in Part C. The first administrative exemption in Part C—relating to payments of the kind referred to in LMRA section 302(c)—remains substantially the same as that in the 2007 instructions; the only change is that LMRA section 302(c) is not quoted in the instructions (instead, the reader is directed to a later part of the instructions where this section is set forth in full).</P>
                        <P>The second administrative exemption in Part C—relating to bona fide loans, interests, or dividends from a bona fide credit institution—is modified slightly from the 2007 rule; specifically, the following sentence, present in the 2007 instructions, is not included in the revised instructions: “This exception does not apply to national or state banks, credit unions, savings or loan associations, insurance companies, or other bona fide credit institutions that constitute a ‘trust in which your labor organization is interested.’ ” Accordingly, this rule excepts from reporting under Part C:</P>
                        <EXTRACT>
                            <P>(ii) Bona fide loans (including mortgages), interest or dividends from national or state banks, credit unions, savings or loan associations, insurance companies, or other bona fide credit institutions, if such loans, interest or dividends are based upon the credit institution's own criteria and made on terms unrelated to your status in a labor organization. Additionally, do not report other marketplace transactions with such bona fide credit institutions, such as credit card transactions (including unpaid balances) and interest and dividends paid on savings accounts, checking accounts or certificates of deposit if the payments and transactions are based upon the credit institution's own criteria and are made on terms unrelated to your status in the labor organization.</P>
                        </EXTRACT>
                        <P>The third administrative exemption in Part C returns to the Department's historical interpretation, exempting:</P>
                        <EXTRACT>
                            <P>(iii) Interest on bonds or dividends on stock, provided such interest or dividends are received, and such bonds or stock have been acquired, under circumstances and terms unrelated to your status in a labor organization and the issuer of such securities is not an enterprise in competition with the employer whose employees your labor organization represents or actively seeks to represent.</P>
                        </EXTRACT>
                        <P>The Department believes that the 2007 rule did not adequately justify the removal of this exemption. Further, interest on bonds or dividends on stock are routine business transactions which do not ordinarily raise conflict-of-interest questions. Their inclusion would increase the burden on union officials, without any apparent benefit to the public. Indeed, the reporting of non conflict-of-interest payments could hide from scrutiny those payments that are in need of transparency. Finally, in order to ensure that actual or potential conflict-of-interest payments are reported, the Department has provided two qualifications on this exemption: the payments must be received under circumstances and terms unrelated to the recipient's status in a labor organization and the issuer of such securities is not an enterprise in competition with the represented employer.</P>
                        <P>
                            A federation of unions suggested that “payments from trusts or other labor organizations” should be included as a fourth express exclusion from Part C, and argued that including this express exclusion will eliminate confusion created by the Department's 2007 Frequently Asked Questions (FAQs 45, 46, 48, 51-53 and 55), which indicated that such payments may be reportable. The Department is persuaded by this suggestion, as it adds clarity to the potential filer on this issue. Thus, the Department has added a fourth exclusion to Part C, specifying that payments received from a section 3(l) trust or labor organization are not reportable. Also, in response to the comment, the Department clarifies that this rule rescinds any example in the 2007 instructions or FAQs that indicated that payments from trusts are reportable.
                            <SU>59</SU>
                            <FTREF/>
                        </P>
                        <FTNT>
                            <P>
                                <SU>59</SU>
                                 See n. 12 herein, which discusses the impact of the final rule on FAQs issues in connection with the 2007 rule and examples in the instructions to the 2007 form.
                            </P>
                        </FTNT>
                        <P>Additionally, specific instructions are provided on how to complete items 13 and 14, which are described in the above subsection, Revised Form.</P>
                        <P>The instructions retain the following requirements that an official report:</P>
                        <P>• Any payment of money or other thing of value from a labor relations consultant to a Part C employer;</P>
                        <P>
                            • Payments from an employer that is a not-for-profit organization that receives or is actively and directly soliciting (other than by mass mail, telephone bank, or mass media) money, 
                            <PRTPAGE P="66484"/>
                            donations, or contributions from the official's union; and
                        </P>
                        <P>• Any payments from an employer (not covered by Parts A or B), or from any labor relations consultant to an employer, for the following purposes:</P>
                        <P>(1) Not to organize employees;</P>
                        <P>(2) To influence employees in any way with respect to their rights to organize;</P>
                        <P>(3) To take any action with respect to the status of employees or others as members of a labor organization;</P>
                        <P>(4) To take any action with respect to bargaining or dealing with employers whose employees your organization represents or seeks to represent; and</P>
                        <P>(5) To influence the outcome of an internal union election.</P>
                        <P>See 72 FR 36128, 36130, 36173.</P>
                        <HD SOURCE="HD3">Remainder of Instructions</HD>
                        <P>The instruction for item 15, Signature and Verification, states that the completed Form LM-30 must be signed by the officer or employee and that forms submitted electronically must use electronic signatures. The instructions indicate that the filer must enter the telephone number used by the filer to conduct official business, and note that the filer does not need to report a private, unlisted telephone number.</P>
                        <P>The revised instructions then feature: “Selected Definitions from the Labor-Management Reporting and Disclosure Act of 1959, as Amended (LMRDA)” [LMRDA section 3]; “Related Provisions of the Labor-Management Reporting and Disclosure Act of 1959, as Amended (LMRDA)—Report of Officers and Employees of Labor Organizations” [LMRDA section 202]; Section 302(c) of the Labor Management Relations Act, 1947, as Amended [Sec. 8(c) of the National Labor Relations Act, as Amended]; and an “If You Need Assistance” section, which includes a list of OLMS field offices and explains the information available on the OLMS Web site. This information is only slightly changed from the 2007 instructions.</P>
                        <HD SOURCE="HD1">V. Regulatory Procedures</HD>
                        <HD SOURCE="HD2">Executive Orders 12866 and 13563</HD>
                        <P>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, 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 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>In the Paperwork Reduction Act (PRA) analysis below, the Department estimates that the rule will result in a total reporting and recordkeeping burden on filing labor organization officers and employees of 2,898 hours and a monetary burden on labor organization officers and employees of approximately $138,621, based on the value of a filer's time. This represents a 10,934 hour reduction from the 13,832 hours estimated in the 2007 rule for filing labor organization officers and employees, and a $170,386 reduction in monetary burden from the estimated $309,007 in the 2007 rule. See 72 FR 36157. This analysis is intended to address the analysis requirements of both the PRA and the Executive Orders.</P>
                        <P>The following is a summary of the need for and objectives of the rule. A more complete discussion of various aspects of the proposal is found elsewhere in the preamble.</P>
                        <P>The LMRDA was enacted to protect the rights and interests of employees, labor organizations, and the public generally as they relate to the activities of labor organizations, employers, labor relations consultants, and labor organization officers, employees, and representatives. The LMRDA includes financial reporting and disclosure requirements for labor organizations and others as set forth in Title II of the Act. See 29 U.S.C. 431-36, 441. The Department has developed several forms to implement the union annual reporting requirements of the LMRDA. Under section 202 of the Act, 29 U.S.C. 432, union officers and employees are required to file reports if they, or their spouses or minor children, engage in certain transactions or have financial holdings that may constitute a conflict of interest. The Department has developed the Form LM-30, Labor Organization Officer and Employee Report, to implement section 202.</P>
                        <P>This rule modifies the Form LM-30, as last revised in 2007. See 72 FR 36106 (July 2, 2007). As discussed above, the revised form has been simplified and will no longer have to be filed by certain individuals, notably stewards, and certain interests and transactions, including most bona fide loans, will not have to be reported. The rule is part of the Department's efforts to meet the goals of greater transparency and disclosure, while mitigating burden on labor organization officers and employees by eliminating reporting on matters without demonstrated utility.</P>
                        <P>The Form LM-30 provides transparency for those financial interests of union officers and employees that may pose conflicts between their own financial interests and their duty to their union and its members. The Act requires the reports to be made available to the public. The reports allow union members to view the information needed by them to monitor their union's affairs and to make informed choices about the leadership of their union and its direction. Accurate disclosure and increased transparency promote the unions' own interests as democratic institutions and the interests of the public and the government. Financial disclosure deters fraud and self-dealing and facilitates the discovery of such misconduct when it does occur.</P>
                        <P>The revised financial disclosure form will promote increased compliance with the statute by clarifying the form and instructions, organizing the information in a more useful format, and modifying it to better meet the requirements of the LMRDA and the Department's policy judgments consistent with its discretion under the Act.</P>
                        <P>Published at the end of this rule are the revised Form LM-30 and instructions. The revised Form LM-30 and instructions also will be made available via the Internet. The information collection requirements contained in this rule have been submitted to OMB for approval.</P>
                        <HD SOURCE="HD2">Unfunded Mandates Reform</HD>
                        <P>This rule will not include any Federal mandate that may result in increased expenditures by State, local, and tribal governments, in the aggregate, of $100 million or more, or in increased expenditures by the private sector of $100 million or more.</P>
                        <HD SOURCE="HD2">Small Business Regulatory Enforcement Fairness Act of 1996</HD>
                        <P>
                            This rule is not a major rule as defined by section 804 of the Small Business Regulatory Enforcement Fairness Act of 1996. This rule will not result in an annual effect on the economy of $100,000,000 or more; a major increase in costs or prices; or significant adverse effects on competition, employment, investment, productivity, innovation, or on the ability of the United States-based companies to compete with foreign-based companies in domestic and export markets.
                            <PRTPAGE P="66485"/>
                        </P>
                        <HD SOURCE="HD2">Executive Order 13132 (Federalism)</HD>
                        <P>The Department has reviewed this rule in accordance with Executive Order 13132 regarding federalism and has determined that the rule does not have federalism implications. Because the economic effects under the rule will not be substantial for the reasons noted above and because the rule has no direct effect on States or their relationship to the Federal government, the rule does not have “substantial direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.”</P>
                        <HD SOURCE="HD2">Regulatory Flexibility Act</HD>
                        <P>The Regulatory Flexibility Act of 1980, 5 U.S.C. 601-612, requires agencies to prepare regulatory flexibility analyses, and to develop alternatives wherever possible, in drafting regulations that will have a significant impact on a substantial number of small entities, including “small businesses,” “small organizations,” and “small governmental jurisdictions.” This rule revises the reporting obligations of union officers and employees, who, as individuals, do not constitute small business entities. Accordingly, the final rule will not have a significant economic impact on a substantial number of small business entities. Therefore, under the Regulatory Flexibility Act, 5 U.S.C. 605(b), a regulatory flexibility analysis is not required.</P>
                        <HD SOURCE="HD2">Paperwork Reduction Act</HD>
                        <P>This rule establishes a new LM-30 reporting form which constitutes a “collection of information” within the meaning of the Paperwork Reduction Act of 1995 (PRA) [44 U.S.C. 3501-3520]. Under the PRA, an agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid control number assigned by the Office of Management and Budget (OMB). In accordance with the PRA, the Department submitted an information collection request (ICR) to OMB. On September 29, 2011, OMB approved the ICR through September 30, 2014, and assigned OMB Control Number 1245-0005 to this version of the LM-30 reporting form.</P>
                        <HD SOURCE="HD3">A. Review of the Comments Received in Response to the NPRM Regarding the Burden Estimate</HD>
                        <P>In accordance with the requirements of the PRA, the Department solicited public comments on the information collection included in the NPRM. Since this rule exclusively amends an information collection, all of the comments received by the Department in response to the NPRM addressed the collection. A discussion of the comments that addressed all aspects of the collection other than the Department's burden estimate is provided above. Here the Department provides a discussion of the comments that addressed the Department's burden estimate.</P>
                        <P>In response to the NPRM, the Department received three comments that addressed the Department's burden analysis in the NPRM. All three comments were limited to the burden associated with top-down reporting. Additionally, as noted in the preamble, several commenters expressed support for the Department's proposals that, if adopted, would reduce the burden of compliance with the Form LM-30 requirements. These proposals included, in part, the return to the historical position that union leave and no docking payments were not reportable and that stewards and other representatives are not covered by the Form LM-30 reporting requirements by virtue of their positions; and the reporting exception for bona fide loans and other credit arrangements with most credit institutions. Further, two commenters who generally are opposed to the Department's proposals expressed the view that the 2007 rule did not impose any undue burden on union officers and employees.</P>
                        <P>As discussed in the NPRM and in earlier sections of this preamble, top-down reporting concerns conflicts of interest that may arise between the financial interests of officers and employees of parent and intermediate unions and business dealings involving their union's subordinate affiliates or employers whose employees are represented by the affiliates. In the NPRM, the Department proposed to require employees of parent and intermediate unions to report such interests; the 2007 rule excepted them from this requirement.</P>
                        <P>Two commenters expressed the view that the increased burden associated with top-down reporting exceeded any burden savings associated with the other changes proposed in the NPRM. One national union took issue with the burden estimates in both the NPRM and the 2007 rule, explaining that its own experience with the pre-2007 Form LM-30 revealed that 12 hours were needed to complete that much simpler form. It estimated that it can take one hour per week for “organizing and categorizing receipts” and another hour per week to confer with a spouse or minor child about links between their employer or other entities and the union. This tracking alone, the commenter states, would exceed the Department's total burden estimate in the 2007 rule and the 2010 NPRM. The commenter also estimates that top-down reporting itself could require 25 hours per year. Other commenters urged the Department to modify or eliminate top-down reporting, which they identified as the most burdensome aspect of LM-30 reporting. The Department has discussed and responded to these comments at length earlier in the preamble and does not restate them here.</P>
                        <P>The Department believes that the NPRM reflects the best estimate of the burdens associated with completing the Form LM-30, as revised by this rule. The Department notes that none of the commenters provided a detailed explanation as to how their estimates were derived, and notes that the time estimates provided for the pre-2007 form and the 25-hour estimate for top-down reporting seem very high, even for the most atypical situations and could not reflect the average burden. The Department's estimate is for an average filer.</P>
                        <P>Further, the Department does not believe that many union officials will be required to file under the top-down reporting framework, and those who do file are already included within the NPRM's estimate for the number of filers. (The Department notes that the estimate for the number of filers does not include a breakdown of the type of transaction being reported, such as a gift or a security or other interest, nor does it indicate whether or not the report is required pursuant to top-down reporting.) Further, none of the commenters challenged the estimated number of filers.</P>
                        <P>Moreover, the burden hour estimates are averages for those who file. Some filers may take more or less time than the estimated 90 minutes, and the Department considers the officials who file as a result of top-down reporting to be already included within the average burden hour estimate. More specifically, the Department does not believe that many, if any, of those who file will take more than 90 minutes to complete the form as a result of the top-down requirements, nor does the Department consider the top-down reporting requirements as altering the 90-minute average. The commenters did not provide any specific information challenging this conclusion.</P>
                        <P>
                            The Department believes that the concerns regarding the burden associated with top-down reporting reflect, to a large extent, a 
                            <PRTPAGE P="66486"/>
                            misunderstanding about what types of payments, interests, and transactions must be reported on the Form LM-30, and how a union official would determine reportability. Moreover, as explained earlier in the preamble, many of the concerns about top-down reporting have been alleviated by specifying that top-down reporting is required only of officers and those employees with “significant authority or influence” over lower-level unions. As stated in the preamble, it is helpful to look at the steps involved in determining whether a top-down report, or any report, is owed. The first step is for a union officer or employee to look at the types of interests held, income and benefits received, and transactions engaged in during the fiscal year. The second step is to eliminate those that are exempted by the general exclusions, such as publicly held stock, income received by the union official as a bona fide employee, and the de minimis threshold. This step will generally greatly reduce potential reportable transactions. The third step is to determine whether any remaining financial transactions were derived from represented employers, as well as service providers and vendors of the union, their trusts, and represented employers. As a part of this step, officers and certain employees of parent and intermediate unions will also have to consider holdings in and payments from entities that have relationships with subordinate affiliates.
                            <SU>60</SU>
                            <FTREF/>
                             Thus, union officials, higher-level or not, have no obligation to research each and every relationship that a union has, at any level, but, rather, only those that relate to the few, if any, employers and businesses identified in step three of the process.
                        </P>
                        <FTNT>
                            <P>
                                <SU>60</SU>
                                 A fourth step could involve review of activities to be reported pursuant to section 202(a)(6) in the “catch-all” Part C of the revised Form LM-30, but OLMS has limited the requirement to report in Part C payments from employers in competition with represented employers to only those union officials with significant influence over organizing. This eliminates the top-down issue involving such employers for most union officials. Further, regarding payments from charities pursuant to section 202(a)(6) and Part C of the proposed form, any payments received as a bona fide employee and as regular marketplace transactions would be excluded, pursuant to the statute.
                            </P>
                        </FTNT>
                        <P>The Department is unpersuaded by the unsubstantiated assertion by one commenter that the top-down burden imposed on union employees exceeds any reduced burden associated with other changes proposed by the NPRM. The Department also disagrees with the assertion that filers are required to track routine financial transactions. Rather, the Form LM-30 only requires tracking and reporting of financial transactions that are actual or potential conflicts of interest, and most union officials will have few, if any, such transactions.</P>
                        <P>Regarding the comment that suggested that the filers should be required to report only top-down interests or payments for which they have “actual, subjective” knowledge, the Department believes that top-down filers (parent and intermediate body union officers and those union employees with significant authority or influence over lower-level unions) will generally have actual, subjective knowledge of the entity's relationship with the union or represented employer, or will be in a position to ascertain this information. Thus, filers will not generally need to contact lower levels of the union to determine reportability, or, if they do need to contact other levels of the union, they will be in position to effectively obtain any needed information.</P>
                        <P>Regarding the comment that suggested that union officials have an “affirmative obligation” to contact subordinate bodies of their union that do not have “systematic records,” the Form LM-30 reporting requirements do not generally require union officials to contact lower level entities of the union. Further, all affiliated unions subject to section 206 of the LMRDA must have adequate records to “provide in sufficient detail” the “necessary basic information and data” from which the annual financial disclosure forms (such as the Form LM-2, Form LM-3, and Form LM-4) submitted to the Department can be verified.</P>
                        <P>Other commenters expressed concern about the burden that an officer or employee of an international, national, or intermediate union would face in determining whether he or she has received a payment from a business a substantial part of which consists of dealing with an employer whose employees the filer's union represents or is actively seeking to represent. Regarding the application of the “substantial part” provision to top-down reporting, the Department notes that this provision actually operates as a general limitation on reporting that applies independently from top-down requirements, as does the “actively seeking to represent” condition for reporting interests in and payments from represented employers. Again, union officials are not generally required to engage in research to identify potential conflict-of-interest relationships. Further, as explained earlier in the preamble, filers should request guidance from the Department if they are unable to determine the application of the reporting requirements, such as the “substantial part” and “actively seeking to represent” provisions.</P>
                        <HD SOURCE="HD3">D. Methodology for the Burden Estimates</HD>
                        <P>The Department first estimated the number of Form LM-30 filers that will submit the revised form. Then, it estimated the number of minutes that each filer will need to meet the reporting and recordkeeping burden imposed by the revised form, as well as the total burden hours. The Department next estimated the cost to each filer for meeting those burden hours, as well as the total cost to filers. The Federal costs associated with the revised rule were also estimated. Please note that some of the burden numbers included in this PRA analysis will not add up due to rounding. Except as noted, the burden analysis in the final rule is substantively identical to that set forth in the NPRM.</P>
                        <HD SOURCE="HD3">1. Number of Revised Form LM-30 Filers</HD>
                        <P>The Department estimates that 1,932 union officers and employees will submit the revised Form LM-30. This figure represents the total pre-2007 and 2007 Form LM-30 reports submitted during Fiscal Year 2009. In that fiscal year, the Department established an enforcement policy that enabled union officers and employees to use either the pre-2007 form or the more complex 2007 version in satisfying their reporting obligation under section 202 of the LMRDA.</P>
                        <HD SOURCE="HD3">2. Hours To Complete and File Revised Form LM-30: Reporting and Recordkeeping</HD>
                        <P>The Department has estimated the number of minutes that each Form LM-30 filer will need for completing and filing the revised form (reporting burden), as well as the minutes needed to track and maintain records necessary to complete the form (recordkeeping burden). The estimates are included in Table 1, which describes the information sought by the revised form and instructions, where the particular information is to be reported, if applicable, and the amount of time estimated for completion of each item of information. The revised reporting regime more closely resembles the pre-2007 Form LM-30, in both form and content, than the 2007 form.</P>
                        <P>
                            Not all union officers and employees will be required to file the Form LM-30, nor will all of those who file need to complete each Part of the form. However, for purposes of assessing an average burden per filer, the Department 
                            <PRTPAGE P="66487"/>
                            assumes that the average filer serves as an officer or employee for one labor organization, and that the filer receives reportable payments or interests for a single entity on Parts A, B, and C, respectively.
                        </P>
                        <P>Additionally, the below estimates are for all filers, including first-time filers and subsequent filers. While the Department considered separately estimating burdens for first-time and subsequent filers, the nature of Form LM-30 reporting militates against this approach. Union officers may serve for relatively short periods of time and reportable transactions may not be reported in subsequent years for a variety of reasons. Where the Department has reduced burden estimates for subsequent year filings of LMRDA reports, it generally did so with regard to required annual reports, specifically labor organization annual reports, Forms LM-2, LM-3, and LM-4. In contrast, the Form LM-30 is only required for union officers and employees in years that they engage in reportable transactions. Further, these officials do not have the same familiarity with reporting as other LM filers. See 72 FR 36157, n. 4. As such, the burden estimates assume that the union officer or employee has never before filed a Form LM-30.</P>
                        <P>
                            <E T="03">Recordkeeping Burden.</E>
                             The recordkeeping estimate of 15 minutes per filer represents a 5-minute change from the 20-minute estimate for the 2007 Form LM-30. 72 FR at 36157. This estimate reflects new exemptions from reporting for union leave and no docking payments, and mortgages and other loans, as well as the decision to eliminate reporting from trusts and unions under section 202(a)(6), which reduce the complexity of the recordkeeping requirements. Additionally, most of the financial books and records needed to complete the form are maintained in the filer's normal course of business, both union and personal. Finally, the 15 minutes accounts for the 5-year retention period required by statute. See section 206, 29 U.S.C. 436.
                        </P>
                        <P>
                            <E T="03">Reporting Burden.</E>
                             The total reporting burden of 75 minutes per respondent addressed in Table 1 reflects the time required to read the Form LM-30 instructions to discover whether or not a report is owed and determine the correct manner to report the necessary information. Of that total amount, it should be noted the Department estimates that the average filer will need 30 minutes to read the instructions, which is substantially less than the 55 minutes estimated for the 2007 Form LM-30. 72 FR 36157.
                            <SU>61</SU>
                            <FTREF/>
                             This reduction is due in part to the reduced scope of required reporting. In particular, the Department has eliminated the requirement to report union leave and no docking payments, bona fide loans, and payments from trusts and unions pursuant to section 202(a)(6). Further, the creation of a more concise and consolidated form and instructions, with definitions and other explanations placed in a more readily accessible format, will enable filers to more quickly ascertain the necessary reporting requirements.
                        </P>
                        <FTNT>
                            <P>
                                <SU>61</SU>
                                 Additionally, the Department estimates that those union officers and employees who are not required to file will spend ten minutes reading the instructions. This burden is not included in the total reporting burden, since these officials do not file and are thus not respondents.
                            </P>
                        </FTNT>
                        <P>In developing the 75-minute estimate, the Department also believes that the simple data entry required by items 1-3 will only require 30 seconds each. A filer will be able to enter his or her own contact information in only two minutes, in item 4. Generally, filers will only need three minutes to enter contact information, such as for their labor organization, in item 5, as well as the contact information for the trust or employer with which the business deals, in item 10. The Department believes, however, that filers will need five minutes, respectively, to enter the contact information for the represented employer in item 6, the business that deals with a labor organization, trust, or employer in item 8, and the “other employer” or labor relations consultant in item 13. Filers will need one minute to complete item 9, which asks filers to indicate whether the business identified deals with a labor organization, trust, or employer.</P>
                        <P>Additionally, filers will need 3 minutes to enter the financial data required in items 7, 12, and 14, and 3.5 minutes to report the nature and value of the dealings in item 11. The Department also believes each filer will spend an average of 5 minutes to check the answers. Finally, the Department estimates that a filer will utilize five minutes to check responses and review the completed report, and will require two minutes to sign and verify the report in item 15. For Form LM-2 Labor Organization Annual Report filers, the Department last year introduced a cost-free and simple electronic filing and signing protocol. The Department intends to provide this feature to Form LM-30 filers in 2012. For this reason, the burden estimate remains constant whether the form is electronically signed, or signed by hand.</P>
                        <P>As a result, the Department estimates that a filer of the revised Form LM-30 will incur 90 minutes in reporting and recordkeeping burden to file a complete form. This compares with the 2007 estimate of 120 minutes per filer.</P>
                        <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s100,r50,xs60">
                            <TTITLE>Table 1—Reporting and Recordkeeping Burden </TTITLE>
                            <TDESC>[In minutes]</TDESC>
                            <BOXHD>
                                <CHED H="1">Burden description</CHED>
                                <CHED H="1">Section of proposed form</CHED>
                                <CHED H="1">
                                    Recurring 
                                    <LI>burden hours</LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">Maintaining and gathering records</ENT>
                                <ENT>Recordkeeping Burden</ENT>
                                <ENT>15 minutes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Reading of the instructions to determine applicability of the form and how to complete it</ENT>
                                <ENT>Report Burden</ENT>
                                <ENT>30 minutes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Reporting LM-30 file number</ENT>
                                <ENT>Item 1</ENT>
                                <ENT>30 seconds.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Reporting covered fiscal year</ENT>
                                <ENT>Item 2</ENT>
                                <ENT>30 seconds.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Identifying if report is amended</ENT>
                                <ENT>Item 3</ENT>
                                <ENT>30 seconds.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Reporting filer's contact information</ENT>
                                <ENT>Item 4</ENT>
                                <ENT>2 minutes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Reporting labor organization contact information</ENT>
                                <ENT>Item 5</ENT>
                                <ENT>3 minutes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Part A: Reporting name and contact information for employer in Part A of form</ENT>
                                <ENT>Item 6</ENT>
                                <ENT>5 minutes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Part A: Reporting the nature of the interest, transaction, arrangement, benefit, or income, as well as the amount, received from the employer identified in Part A</ENT>
                                <ENT>Items 7a and 7b</ENT>
                                <ENT>3 minutes.</ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="66488"/>
                                <ENT I="01">Part B: Reporting contact information for business</ENT>
                                <ENT>Item 8</ENT>
                                <ENT>5 minutes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Part B: Identifying if the business deals with a labor organization, trust, or employer</ENT>
                                <ENT>Item 9</ENT>
                                <ENT>1 minutes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Part B: Reporting the contact information for the trust or employer with which the business deals</ENT>
                                <ENT>Item 10</ENT>
                                <ENT>3 minutes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Part B: Reporting the nature and value of the dealings between the business and employer, union, or trust</ENT>
                                <ENT>Items 11a and 11b</ENT>
                                <ENT>
                                    3 
                                    <FR>1/2</FR>
                                     minutes.
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Part B: Reporting the nature and amount of interest held or income received from the business</ENT>
                                <ENT>Items 12a and 12b</ENT>
                                <ENT>3 minutes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Part C: Reporting the contact information for the employer or labor relations consultant, and identifying the entity as an employer or labor relations consultant</ENT>
                                <ENT>Items 13a and 13b</ENT>
                                <ENT>5 minutes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Part C: Reporting the nature and amount of payment from the employer or labor relations consultant</ENT>
                                <ENT>Items 14a and 14b</ENT>
                                <ENT>3 minutes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Checking responses</ENT>
                                <ENT>N/A</ENT>
                                <ENT>5 minutes.</ENT>
                            </ROW>
                            <ROW RUL="n,s">
                                <ENT I="01">Signature and verification</ENT>
                                <ENT>Item 15</ENT>
                                <ENT>2 minutes.</ENT>
                            </ROW>
                            <ROW RUL="n,s">
                                <ENT I="03">Total Recordkeeping Burden Estimate Per Filer</ENT>
                                <ENT/>
                                <ENT>15 minutes.</ENT>
                            </ROW>
                            <ROW RUL="n,s">
                                <ENT I="03">Total Reporting Burden Estimate Per Filer</ENT>
                                <ENT/>
                                <ENT>75 minutes.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">
                                    <E T="03">TOTAL BURDEN HOUR ESTIMATE PER FILER</E>
                                </ENT>
                                <ENT/>
                                <ENT>
                                    <E T="03">90 minutes.</E>
                                </ENT>
                            </ROW>
                        </GPOTABLE>
                        <P>
                            <E T="03">Total Reporting and Recordkeeping Burden.</E>
                             As stated, the Department estimates that there are 1,932 union officers and employees that will be annually filing the Form LM-30. Thus, the estimated recordkeeping burden for all filers is 28,980 minutes (15 × 1,932 = 28,980 minutes) or 483 hours (28,980/60 = 483). The total estimated reporting burden for all filers is 144,900 minutes (75 × 1,932 = 144,900 minutes) or approximately 2,415 hours (144,900/60 = 2,415 hours). The total estimated burden for all filers is, therefore, 173,880 minutes or approximately 2,898 hours. See Table 2 below.
                        </P>
                        <GPOTABLE COLS="2" OPTS="L2,p1,8/9,i1" CDEF="s75,r50">
                            <TTITLE>Table 2—Total Reporting and Recordkeeping Burden for All 1,932 Estimated Filers</TTITLE>
                            <BOXHD>
                                <CHED H="1"> </CHED>
                                <CHED H="1"> </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">Total Recordkeeping Burden</ENT>
                                <ENT>483 hours.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Total Reporting Burden</ENT>
                                <ENT>2,415 hours.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Total Burden</ENT>
                                <ENT>2,898 hours.</ENT>
                            </ROW>
                        </GPOTABLE>
                        <HD SOURCE="HD3">3. Calculation of Total Monetized Burden Hours Costs for Labor Organization Officers and Employees to Complete the Revised Form LM-30</HD>
                        <P>The Department estimates the dollar cost to filers to complete the Form LM-30 by using fiscal year (FY) 2009 data derived from Form LM-2, Labor Organization Annual Reports, filed with the Department pursuant to section 201 of the LMRDA. The Form LM-2 is the annual financial disclosure report filed by the largest labor organizations, those with $250,000 or more in total annual receipts. The Department notes that many Form LM-30 reports are filed by lower level labor organization officers and employees, whose labor organizations file the less detailed Form LM-3 and Form LM-4 Labor Organization Annual Reports, and who are often part-time officials earning lower salaries than parent body labor organizations that file the more comprehensive Form LM-2. However, because only part-time annual salaries are reported by part-time officers on the Form LM-3 (and individual salaries are not reported on the LM-4), but not the hours upon which those part-time annual salaries are based, it is impractical to calculate an average hourly wage for union officers from the Form LM-3. This contrasts with a Form LM-2 filer, where it can be assumed that the annual salaries for officers are primarily for full-time duties, which makes it possible to determine average hourly wages. Therefore, the Form LM-2 provides the Department with more comprehensive data by which to ascertain a reasonable estimate of union officer and employee salaries.</P>
                        <P>The Department also assumes, as it did for burden estimates under the pre-2007 Form LM-30, that one-third of the forms will be filed by union presidents, secretary-treasurers, and international representatives (the last designation as a proxy for union employees), respectively. The Department derived the average hourly wage for each of these categories by utilizing data from FY 2009 Form LM-2 reports.</P>
                        <P>
                            With respect to the international representative analysis, the salary data derived from the Department's Electronic Labor Organization Reporting System (e.LORS) included only international or national unions and only those employee titles and gross salary data from Form LM-2, Schedule 12 of those international/national unions that included words like “national” or “international” and “representative.” The Department then eliminated blank salary entries (either nothing was listed in the Form LM-2 or a zero was listed) because there are a variety of reasons why the salary can be blank or zero and their inclusion in the calculation of the average would skew the average calculation. Finally, the Department calculated the average hourly wage by dividing the average annual salary by 2,080 hours (40 hours per week times 52 weeks per year). Next, the Department increased these figures by 43.00% to account for total compensation.
                            <SU>62</SU>
                            <FTREF/>
                        </P>
                        <FTNT>
                            <P>
                                <SU>62</SU>
                                 See Employer Costs for Employee Compensation Summary, from the Bureau of Labor Statistics (BLS), at 
                                <E T="03">http://www.bls.gov/news.release/ecec.nr0.htm.</E>
                                 The Department increased the average hourly wage rate for employees ($20.49 in 2008) by the percentage total of the average hourly compensation figure ($8.90 in 2008) over the average hourly wage.
                            </P>
                        </FTNT>
                        <P>
                            The methodology and assumptions are somewhat similar for the president and secretary-treasurers averages. Here, the Department had data from FY 2009 for all Form LM-2 filers with $800,000 or more in annual receipts. The $800,000 figure was selected because it represents roughly the average of all Form LM-2 filers, and we hypothesized that these larger than average Form LM-
                            <PRTPAGE P="66489"/>
                            2 filers are more likely to have presidents and secretary-treasurers who file the Form LM-30.
                        </P>
                        <P>As a result, the Department estimates that union presidents earn an average hourly wage of $34.65 ($49.55 after adjusting by 43.00% for total compensation); union secretary-treasurers, $31.87 ($45.57 after adjusting by 43.00% for total compensation); and international representatives, $33.83 ($48.38 after adjusting by 43.00% for total compensation). The Department also estimated that each of these categories of union officials accounted for one-third of the Form LM-30 reports submitted and thus one-third of the total burden hours (2,898 hours divided by three equals 966). Therefore, the total cost was $138,621 (966 × $49.55 = $47,865.30; 966 × $45.57 = $44,020.62; and 966 × $48.38 = $46,735.08). The estimated cost per filer is approximately $71.75 ($47,865.30 + $44,020.62 + $46,735.08 = $138,621; $138,621/1932 = $71.75).</P>
                        <HD SOURCE="HD3">4. Other Costs (Start-up, Capital, Maintenance, and Operations)</HD>
                        <P>The Department associates no costs with this information collection, beyond the value of a filer's time.</P>
                        <HD SOURCE="HD3">5. Federal Costs</HD>
                        <P>Finally, in its recent submission for revision of OMB #1245-0003 (formerly OMB #1215-0188), which contains all LMRDA forms (except the pre-2007 Form LM-30, 1245-0002, which was approved under OMB #1215-0205, and the 2011 Form LM-30), the Department estimated that its costs associated with the LMRDA forms are $2,710,726 for the OLMS national office and $3,779,778 for the OLMS field offices, for a total Federal cost of $6,490,504. Federal estimated costs include costs for contractors and operational expenses such as equipment, overhead, and printing as well as salaries and benefits for the OLMS staff in the National Office and field offices who are involved with reporting and disclosure activities. These estimates include time devoted to: (a) Receipt and processing of reports; (b) disclosing reports to the public; (c) obtaining delinquent reports; (d) reviewing reports, (e) obtaining amended reports if reports are determined to be deficient; and (f) providing compliance assistance training on recordkeeping and reporting requirements.</P>
                    </PART>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 29 CFR Part 404</HD>
                        <P>Labor union officers and employees; reporting and recordkeeping requirements.</P>
                    </LSTSUB>
                    <HD SOURCE="HD1">Text of Rule</HD>
                    <P>Accordingly, the Department amends part 404 of 29 CFR Chapter IV as set forth below:</P>
                    <REGTEXT TITLE="29" PART="404">
                        <PART>
                            <HD SOURCE="HED">PART 404—LABOR ORGANIZATION OFFICER AND EMPLOYEE REPORTS</HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 404 is revised to read as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P> Labor-Management Reporting and Disclosure Act Secs. 202, 207, 208, 73 Stat. 525, 529 (29 U.S.C. 432, 437, 438); Secretary's Order No. 08-2009, Nov. 6, 2009, 74 FR 58835 (Nov. 13, 2009).</P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="29" PART="404">
                        <SECTION>
                            <SECTNO>§ 404.1 </SECTNO>
                            <SUBJECT>[Amended]</SUBJECT>
                        </SECTION>
                        <AMDPAR>2. In § 404.1, paragraph (f) is removed and paragraphs (g) through (j) are redesignated as (f) through (i), respectively.</AMDPAR>
                        <SIG>
                            <DATED>Signed in Washington, DC, this 6th day of October, 2011.</DATED>
                            <NAME>John Lund,</NAME>
                            <TITLE>Director, Office of Labor-Management Standards.</TITLE>
                        </SIG>
                        <NOTE>
                            <HD SOURCE="HED">Note:</HD>
                            <P>The following appendix will not appear in the Code of Federal Regulations.</P>
                        </NOTE>
                        <HD SOURCE="HD1">Appendix: Revised Form and Instructions</HD>
                    </REGTEXT>
                    <BILCOD>BILLING CODE 4510-CP-P</BILCOD>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66490"/>
                        <GID>ER26OC11.000</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66491"/>
                        <GID>ER26OC11.001</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66492"/>
                        <GID>ER26OC11.002</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66493"/>
                        <GID>ER26OC11.003</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66494"/>
                        <GID>ER26OC11.004</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66495"/>
                        <GID>ER26OC11.005</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66496"/>
                        <GID>ER26OC11.006</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66497"/>
                        <GID>ER26OC11.007</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66498"/>
                        <GID>ER26OC11.008</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66499"/>
                        <GID>ER26OC11.009</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66500"/>
                        <GID>ER26OC11.010</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66501"/>
                        <GID>ER26OC11.011</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66502"/>
                        <GID>ER26OC11.012</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66503"/>
                        <GID>ER26OC11.013</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="441">
                        <PRTPAGE P="66504"/>
                        <GID>ER26OC11.014</GID>
                    </GPH>
                </SUPLINF>
                <FRDOC>[FR Doc. 2011-26816 Filed 10-25-11; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 4510-CP-C</BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
    <VOL>76</VOL>
    <NO>207</NO>
    <DATE>Wednesday, October 26, 2011</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="66505"/>
            <PARTNO>Part IV</PARTNO>
            <AGENCY TYPE="P">Department of Transportation</AGENCY>
            <SUBAGY>Federal Motor Carrier Safety Administration</SUBAGY>
            <HRULE/>
            <CFR>
                49 CFR Parts 360, 365, 366, 
                <E T="03">et al.</E>
            </CFR>
            <TITLE>Unified Registration System; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="66506"/>
                    <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                    <SUBAGY>Federal Motor Carrier Safety Administration</SUBAGY>
                    <CFR>49 CFR Parts 360, 365, 366, 368, 385, 387, 390 and 392</CFR>
                    <DEPDOC>[Docket No. FMCSA-97-2349]</DEPDOC>
                    <RIN>RIN 2126-AA22</RIN>
                    <SUBJECT>Unified Registration System</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Federal Motor Carrier Safety Administration (FMCSA), DOT.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Supplemental Notice of Proposed Rulemaking (SNPRM).</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>The FMCSA amends its proposal regarding establishment of the Unified Registration System (URS) required by the ICC Termination Act of 1995 (ICCTA) and originally announced in a May 19, 2005 notice of proposed rulemaking (NPRM). URS is the replacement system for several existing registration and information systems for motor carriers, property brokers, and freight forwarders under FMCSA jurisdiction. This SNPRM responds to comments to the 2005 URS NPRM, incorporates new proposals implementing requirements imposed by final rules published after the 2005 URS NPRM, and includes new proposals to implement certain provisions of the Safe, Accountable, Flexible, Efficient Transportation Equity Act: A Legacy for Users (SAFETEA-LU). The Agency believes the proposed URS would improve the registration process for motor carriers, property brokers, freight forwarders and other entities that register with FMCSA.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>You must submit comments on or before December 27, 2011.</P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>You may submit comments identified by Federal Docket Management System (FDMS) Docket ID Number FMCSA-97-2349 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., between 9 a.m. and 5 p.m. ET, Monday through Friday, except Federal holidays.
                        </P>
                        <P>
                            • 
                            <E T="03">Fax:</E>
                             202-493-2251.
                        </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 under the Supplementary Information caption 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. Please see the Privacy Act heading below.
                        </P>
                        <P>
                            <E T="03">Privacy Act:</E>
                             Anyone is able to search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, 
                            <E T="03">etc.</E>
                            ). You may review the US Department of Transportation's DOT Privacy Act  System of Records Notice for the DOT Federal Docket Management System published in the 
                            <E T="04">Federal Register</E>
                             on January 17, 2008 (73 FR 3316), or you may visit 
                            <E T="03">http://edocket.access.gpo.gov/2008/pdf/E8-785.pdf.</E>
                        </P>
                        <P>
                            <E T="03">Docket:</E>
                             For access to the docket to read background documents or comments received, go to 
                            <E T="03">http://www.regulations.gov</E>
                             or the street address listed above. Follow the online instructions for accessing the dockets.
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            Mr. Richard Clemente, Transportation Specialist, Driver and Carrier Operations Division, (202) 366-2722, or by e-mail at: 
                            <E T="03">Richard.Clemente@dot.gov.</E>
                             Business hours are from 8 a.m. to 4:30 p.m. ET, Monday through Friday, except Federal holidays.
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <HD SOURCE="HD1">Public Participation</HD>
                    <P>
                        The Federal eRulemaking Portal (
                        <E T="03">http://www.regulations.gov</E>
                        ) is available 24 hours each day, 365 days each year. You can get electronic submission and retrieval help and guidelines under the “How to Use This Site” menu option.
                    </P>
                    <P>Comments received after the comment closing date will be included in the docket and we will consider late comments to the extent practicable. The FMCSA may, however, issue a final rule at any time after the close of the comment period.</P>
                    <HD SOURCE="HD1">Preamble Table of Contents</HD>
                    <P>The following is an outline of the preamble.</P>
                    <EXTRACT>
                        <FP SOURCE="FP-2">I. Legal Basis for the Rulemaking</FP>
                        <FP SOURCE="FP-2">II. Regulatory History</FP>
                        <FP SOURCE="FP1-2">A. Advance Notice of Proposed Rulemaking</FP>
                        <FP SOURCE="FP1-2">B. Notice of Proposed Rulemaking</FP>
                        <FP SOURCE="FP-2">III. Discussion of the Supplemental Notice of Proposed Rulemaking</FP>
                        <FP SOURCE="FP1-2">A. New Regulatory Drafting Strategy</FP>
                        <FP SOURCE="FP1-2">B. The Proposal</FP>
                        <FP SOURCE="FP-2">IV. Regulatory Evaluation of the URS SNPRM: Summary of Benefits and Costs</FP>
                        <FP SOURCE="FP-2">V. Appendix to the Preamble—Proposed Form MCSA-1 and Instructions</FP>
                        <FP SOURCE="FP-2">VI. Rulemaking Analyses and Notices</FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">I. Legal Basis for the Rulemaking</HD>
                    <P>This rulemaking is in response to sec. 103 of the ICC Termination Act of 1995 (ICCTA) [Pub. L. 104-88, 109 Stat. 888, December 29, 1995] and title IV of the Safe, Accountable, Flexible, and Efficient Transportation Equity Act: A Legacy for Users (SAFETEA-LU) [Pub. L. 109-59, 119 Stat. 1714, August 10, 2005]. This rulemaking action is consistent with the requirements of 31 U.S.C. 9701 and 49 U.S.C. 31136(a).</P>
                    <P>In the ICCTA, Congress enacted 49 U.S.C. 13908 directing the Secretary of Transportation (the Secretary), in cooperation with the States, and after notice and opportunity for public comment, to issue regulations to replace the existing information systems listed below with a single, online, Federal system:</P>
                    <P>1. The current Department of Transportation (USDOT) identification number system;</P>
                    <P>2. The single State registration system (SSRS) under [49 U.S.C.] section 14504;</P>
                    <P>3. The registration system contained in 49 U.S.C. chapter 139; and</P>
                    <P>4. The financial responsibility information system under section 13906.</P>
                    <P>Congress also directed the Secretary to consider whether to integrate the requirements of 49 U.S.C. 13304 regarding service of process in court proceedings into the new system. Congress specified that the new URS should serve as a clearinghouse and depository of information on, and identification of, all foreign and domestic motor carriers, property brokers, freight forwarders, and others required to register with the USDOT as well as information on safety fitness and compliance with required levels of financial responsibility. The language of 49 U.S.C. 13908(c) also authorized the Secretary to “establish, under section 9701 of title 31 [of the U.S. Code], a fee system for registration and filing evidence of financial responsibility under the new system under subsection (a). Fees collected under the fee system shall cover the costs of operating and upgrading the registration system, including all personnel costs associated with the system.”</P>
                    <P>
                        The Unified Carrier Registration Act of 2005, subtitle C of title IV of  SAFETEA-LU, modified the requirements for a unified registration system for motor carriers contained in ICCTA. In particular, SAFETEA-LU changed the scope of the Secretary's responsibility for the development of a registration system to replace the SSRS. It also modified the requirement that 
                        <PRTPAGE P="66507"/>
                        fees collected under the new system cover the costs of operating and upgrading the registration system and placed limitations on certain fees that the Agency could charge. Section 4304 of SAFETEA-LU reiterated the congressional requirement for a single, Federal, online system to replace the four individual systems identified under 49 U.S.C. 13908 and also mandated inclusion of the service of process agent systems under 49 U.S.C. 503 and 13304. SAFETEA-LU refers to the Federal online replacement system as the Unified Carrier Registration System. The Agency considers the URS announced in the May 2005 NPRM to be the Unified Carrier Registration System.
                        <SU>1</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             The Unified Carrier Registration (UCR) Agreement mandated under section 4305 of SAFETEA-LU (which enacted 49 U.S.C. 14504a) is the replacement for the Single State Registration System authorized by former 49 U.S.C. 14504. Registration and payment of fees under the UCR Agreement are not the responsibility of FMCSA. However, as provided by 49 U.S.C. 13908(b), information about the compliance of entities subject to the UCR Agreement will be available through the URS when that system has been developed.
                        </P>
                    </FTNT>
                    <P>
                        Congress also repealed the statutory provisions of 49 U.S.C. 14504 governing SSRS. (SAFETEA-LU section 4305(a)).
                        <SU>2</SU>
                        <FTREF/>
                         The legislative history indicates that the purpose of the UCR Plan and Agreement is both to “replace the existing outdated system [SSRS]” for registration of interstate motor carrier entities with the States and to “ensure that States don't lose current revenues derived from SSRS” (S. Rep. 109-120, at 2 (2005)).
                        <SU>3</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             This repeal became effective on January 1, 2007, in accordance with section 4305(a).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             The Senate bill's provisions were enacted “with modifications.” H. Conf. Rep. No. 109-203, at 1020 (2005).
                        </P>
                    </FTNT>
                    <P>
                        The statute provided for a 15-member Board of Directors for the UCR Plan and Agreement (Board) appointed by the Secretary of Transportation. The statute specified that the Board should consist of Federal, State and motor carrier industry representatives. The establishment of the board was announced in the 
                        <E T="04">Federal Register</E>
                         on May 12, 2006 (71 FR 27777). The Board's duties include issuing rules and regulations, recommending fee levels for the system, and designating a revenue depository for the new system. On Friday, August 24, 2007, the Agency published a final rule establishing initial fees for 2007 and a fee bracket structure for the Unified Carrier Registration Agreement in the 
                        <E T="04">Federal Register</E>
                         (72 FR 48585). The FMCSA subsequently adjusted the UCR Agreement fees and fee bracket structure in a final rule dated April 27, 2010 (74 FR 21993).
                    </P>
                    <P>SAFETEA-LU also amended several definitions that affect the coverage of the URS, amended certain financial responsibility requirements, and eliminated the Agency's authority to collect certain fees. Today's proposal incorporates new requirements imposed by SAFETEA-LU.</P>
                    <P>Title 31 U.S.C. 9701 (the so-called “User Fee Statute”) establishes general authority for agencies to “charge for a service or thing of value provided by the Agency.” Accordingly, FMCSA proposes to charge fees under URS that will enable the Agency to recoup costs associated with processing registration applications and administrative filings. Title 49 U.S.C. 13908(d) requires establishment of registration fees that, as nearly as possible, cover the costs of processing the registration, provided the fees do not exceed $300.</P>
                    <P>Section 206 of the Motor Carrier Safety Act of 1984 [Pub. L. 98-554, title II, 98 Stat. 2832, October 30, 1985, 49 U.S.C. App. 2505, recodified at 49 U.S.C. 31136] requires the Secretary to prescribe regulations on commercial motor vehicle safety. The regulations shall prescribe minimum safety standards for commercial motor vehicles (CMVs). At a minimum, the regulations shall ensure that: (1) CMVs are maintained, equipped, loaded, and operated safely; (2) the responsibilities imposed on operators of CMVs do not impair their ability to operate the vehicles safely; (3) the physical conditions of operators of CMVs is adequate to enable them to operate the vehicles safely; and (4) the operation of CMVs does not have a deleterious effect on the physical condition of the operators (49 U.S.C. 31136(a)).</P>
                    <P>This SNPRM is intended to streamline the existing registration process and ensure that FMCSA can more efficiently track motor carriers, freight forwarders, brokers, intermodal equipment providers and cargo tank facilities. It implements the mandate under sec. 31136(a)(1) that FMCSA's regulations ensure that CMVs are maintained and operated safely. This proposal imposes no operational responsibilities on drivers. Therefore, this proposed regulation would not impair a driver's ability to operate vehicles safely (sec. 31136(a)(2)), would not impact the physical condition of drivers (sec. 31136(a)(3)), and would not have a deleterious effect on the physical condition of drivers (sec. 31136(a)(4)).</P>
                    <HD SOURCE="HD1">II. Regulatory History</HD>
                    <HD SOURCE="HD2">A. Advance Notice of Proposed Rulemaking</HD>
                    <P>In response to the ICCTA mandate to develop a unified registration system, the Federal Highway Administration (FMCSA's predecessor agency) issued an advance notice of proposed rulemaking (ANPRM) announcing plans to develop a single, online, Federal information system (61 FR 43816, August 26, 1996). The ANPRM solicited specific detailed information from the public about each of the systems to be replaced by the URS, the conceptual design of the URS, uses and users of the information to be collected, and potential costs.</P>
                    <HD SOURCE="HD2">B. Notice of Proposed Rulemaking</HD>
                    <P>On May 19, 2005, FMCSA published an NPRM describing a proposal to merge all of the prescribed information systems except SSRS into a unified, online, Federal system (70 FR 28990) as set forth below.</P>
                    <HD SOURCE="HD3">1. Entities To Be Included in the Unified Registration System</HD>
                    <P>The Agency proposed to include the following entities in the Unified Registration system: (1) All for-hire motor carriers (including those exempt from the 49 U.S.C. chapter 139 registration requirements), (2) private motor carriers, (3) property brokers, and (4) freight forwarders.</P>
                    <P>In the NPRM, the Agency proposed to exclude the following entities from the Unified Registration System: (1) Mexico-domiciled motor carriers applying to engage in long-haul operations, (2) applicants for hazardous materials safety permits to haul certain hazardous materials under 49 CFR part 385, subpart E, and (3) cargo tank facilities required to register with FMCSA pursuant to 49 CFR 107.502 and 49 U.S.C. 5108. The Agency requested comment on whether the unique conditions of these entities warranted retaining separate registration procedures and application forms or whether they also should be included in the Unified Registration System. The Agency also solicited information on how to most effectively integrate the systems under consideration for merger with URS.</P>
                    <HD SOURCE="HD3">2. Proposed User Fees</HD>
                    <P>
                        The Agency proposed user fees as set forth in the Table to § 360.401 below:
                        <PRTPAGE P="66508"/>
                    </P>
                    <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s150,xs50">
                        <TTITLE>Table to § 360.401—Unified Registration Schedule of Fees</TTITLE>
                        <BOXHD>
                            <CHED H="1">Registration</CHED>
                            <CHED H="1">
                                You must pay
                                <LI>FMCSA</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22">If you:</ENT>
                        </ROW>
                        <ROW RUL="s">
                            <ENT I="03">(a) Are subject to the registration requirements under § 360.3 and are requesting a new application to operate in interstate commerce</ENT>
                            <ENT>$200.</ENT>
                        </ROW>
                        <ROW EXPSTB="01" RUL="s">
                            <ENT I="21">Other Services</ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="22">If you file a:</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">(b) Biennial update of registration</ENT>
                            <ENT>No cost.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">(c) Request for change of name, address, or form of business</ENT>
                            <ENT>No cost.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">(d) Request for cancellation of registration</ENT>
                            <ENT>No cost.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">(e) Request for registration reinstatement</ENT>
                            <ENT>$100.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">(f) Designation of process agent</ENT>
                            <ENT>$10.</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>Additionally, the Agency proposed fees for record searching, reviewing, copying, certifying, and related services under § 360.419(a) through (d) as follows:</P>
                    <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s150,r50">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Description</CHED>
                            <CHED H="1">Fee</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">(a) Certificate of the Director, Office of Information Management, as to the authenticity of documents</ENT>
                            <ENT>$12.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(b) Service involved in locating records to be certified and determining their authenticity, including incidental clerical and administrative work</ENT>
                            <ENT>$21 per hour.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(c) Photocopies of public documents</ENT>
                            <ENT>$.80 per letter- or legal-size page; $5 minimum.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">(d) Search and copying services requiring automated data processing services (ADP), as follows:</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">(1) Professional staff time to fulfill an ADP request</ENT>
                            <ENT>$50 per hour.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">(2) Computer searches</ENT>
                            <ENT>Current rate for computer service as determined by the Office of Information Management (MC-RIS).</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">(3) Printing</ENT>
                            <ENT>Paper—$.10 per page with a $1 minimum; Electronic media—Agency's cost.</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD3">3. Financial Responsibility</HD>
                    <HD SOURCE="HD3">Bodily Injury and Property Damage Insurance (BI &amp; PD) Filing Requirement</HD>
                    <P>
                        Existing regulations prescribe minimum levels of financial responsibility for certain motor carrier classifications. However, only for-hire motor carriers, brokers and certain freight forwarders 
                        <SU>4</SU>
                        <FTREF/>
                         that are subject to the chapter 139 registration requirements must file evidence of financial responsibility with FMCSA as a precondition to receiving and holding chapter 139 operating authority. Evidence of financial responsibility may be in the form of certificates of insurance, surety bonds, proof of qualifications as a self-insurer, endorsements, or trust agreements, as appropriate.
                    </P>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             Household goods freight forwarders performing transfer, collection and delivery service.
                        </P>
                    </FTNT>
                    <P>The Agency proposed to retain the financial responsibility filing requirement for these entities and to extend them to for-hire motor carriers exempt from the chapter 139 registration requirements (hereafter referred to as “exempt for-hire motor carriers”) and to private interstate motor carriers transporting hazardous materials. All such carriers already are required by statute (49 U.S.C. 31138 and 31139) and regulations (49 CFR part 387) to obtain and maintain BI &amp; PD insurance. The NPRM merely proposed to require the filing of evidence of financial responsibility with FMCSA. The Agency believes the proposed filing requirement would provide the public with assurances that all for-hire motor carriers and private carriers transporting hazardous materials in interstate commerce have the financial means to compensate members of the public for injuries or damages caused by negligence. These filings also would increase public accessibility to insurance information and would enable FMCSA to more effectively track insurance cancellations.</P>
                    <P>The filing requirement would not be extended to motor carriers transporting hazardous materials in intrastate commerce; these carriers would continue to maintain evidence of financial responsibility at their principal place of business.</P>
                    <HD SOURCE="HD3">Web-Based Filings by Insurers, Surety Companies, and Financial Institutions</HD>
                    <P>The Agency proposed to require financial responsibility service providers such as insurers to file evidence of financial responsibility using a Web-based (HTML) format. These filings would include evidence of certificates of insurance, proof of qualification to self-insure, endorsements, surety bonds, trust-fund agreements, household goods (HHG) cargo insurance, and notices of cancellations. The FMCSA believes Web-based filings will promote efficiencies for FMCSA, insurers, sureties, financial institutions, and the public. The NPRM solicited comment on whether the proposed mandatory Web-based filing would be a significant burden on small insurers, surety companies, and financial institutions. Also, the Agency invited comments, ideas and suggestions regarding a potential phase-in approach as opposed to immediate mandatory on-line filing.</P>
                    <P>
                        <E T="03">Cargo Insurance.</E>
                         The NPRM included a proposal to eliminate the cargo insurance requirement for all entities except HHG motor carriers and HHG 
                        <PRTPAGE P="66509"/>
                        freight forwarders. Current 49 CFR 387.303(c) and 387.405(a) require non-exempt for-hire motor common carriers of property and freight forwarders, respectively, to maintain cargo insurance in the amount of $5,000 per vehicle, and $10,000 per occurrence, and to file evidence of coverage with FMCSA. Contract carriers are not subject to a requirement to maintain or file evidence of cargo insurance. However, SAFETEA-LU prohibited FMCSA from registering motor carriers as “common” or “contract” carriers, effective January 1, 2007. The Agency proposed to eliminate the cargo insurance requirement for all entities except HHG carriers and HHG freight forwarders based on the assumption that most for-hire motor carriers and freight forwarders carry cargo insurance well above FMCSA limits because their shipper clients generally require it as a condition of doing business. However the Agency deemed it in the public interest to retain the cargo insurance requirement for household goods motor carriers and household goods freight forwarders.
                    </P>
                    <P>
                        <E T="03">Self-Insurance Program.</E>
                         The Agency proposed several changes to the self-insurance program, including changes to the fees charged to applicants seeking approval to self-insure and changes to the fees associated with annual and quarterly reporting by entities approved to self-insure. The Agency announced that it would continue its practice of processing and approving each motor carrier self-insurance application on a case-by-case basis.
                    </P>
                    <P>
                        <E T="03">Insurance Filing Fees.</E>
                         The Agency proposed insurance filing fees as set forth in the Table to § 360.415(b):
                    </P>
                    <GPOTABLE COLS="2" OPTS="L2,p1,8/9,i1" CDEF="s200,14">
                        <TTITLE>Table to § 360.415(b)—Insurance Filing Fees</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1"> </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">(1) Financial responsibility service provider filing evidence of minimum level of insurance, surety bond, or trust fund agreement</ENT>
                            <ENT>$10</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(2) Qualification as a self-insurer for bodily injury, property damage, or environmental restoration</ENT>
                            <ENT>4,200</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(3) Qualification as a self-insurer for cargo insurance</ENT>
                            <ENT>420</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(4) Quarterly self-insurance monitoring filing</ENT>
                            <ENT>500</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(5) Annual self-insurance monitoring filing</ENT>
                            <ENT>
                                (
                                <SU>1</SU>
                                )
                            </ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             No cost.
                        </TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD3">4. Process Agent Designations</HD>
                    <P>
                        Current regulations under 49 CFR part 366 require only motor carriers and brokers that are subject to the 49 U.S.C. chapter 139 commercial registration requirements to designate a process agent.
                        <SU>5</SU>
                        <FTREF/>
                         Today exempt for-hire motor carriers are not subject to FMCSA commercial regulations and thus are not required to designate a process agent. Heretofore, the Agency has not exercised the authority granted under 49 U.S.C. 503 to require private carriers to designate a process agent. However, in the May 2005 NPRM, the Agency proposed to require new and existing private and exempt for-hire motor carriers and freight forwarders to make process agent designation filings with FMCSA. Additionally, private motor carriers that operate in the United States in the course of transportation between points in a foreign country would need to file process agent designations with the Agency.
                    </P>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             Although part 366 does not require process agent designations by freight forwarders, designation of agents for service of process by freight forwarders in connection with Agency proceedings is required under 49 U.S.C. 13303. Consequently, the Agency has required such designations by freight forwarders notwithstanding the omission of freight forwarders in part 366. The Agency proposed to add freight forwarders to part 366 to fully implement section 13303.
                        </P>
                    </FTNT>
                    <P>The FMCSA concluded that extending the requirement to all URS registrants would enhance the public's ability to serve legal process on responsible individuals when seeking compensation for losses resulting from a crash involving a commercial motor vehicle operated by private or exempt for-hire motor carriers. Moreover, FMCSA would be better able to identify among all of its regulated entities the appropriate individual(s) upon whom to serve notices for enforcement actions.</P>
                    <HD SOURCE="HD3">5. Timeframes for Evidence of Financial Responsibility and Process Agent Designation Filings</HD>
                    <P>
                        The Agency proposed to increase to 90 days the maximum time allowed for an applicant to submit evidence of financial responsibility and to designate a process agent (§§ 360.13(a)(6) 
                        <SU>6</SU>
                        <FTREF/>
                         and (a)(7)). Failure to make these filings within 90 days of applying for registration would result in dismissal of the application.
                    </P>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             The May 2005 NPRM incorrectly included two paragraphs (a)(6) under § 360.13. This statement cross references the second paragraph (a)(6).
                        </P>
                    </FTNT>
                    <P>
                        Existing regulations already provide up to 80 days for these filings. Today agents must file evidence of financial responsibility on behalf of non-exempt for-hire motor carriers, brokers and freight forwarders within 20 days of the date of publication of the application in the FMCSA Register (published on the Agency Web site at 
                        <E T="03">http://www.fmcsa.dot.gov</E>
                        ). If the filings are not completed within the 20-day period, FMCSA issues a dismissal warning and may grant a one-time 60-day grace period.
                    </P>
                    <P>The Agency stated that a 90-day filing period for these administrative filings more realistically reflects the actual time necessary to arrange insurance and process agent coverage. The NPRM included a proposal that administrative filings be completed within 90 days after submission of the Form MCSA-1, with no further extensions. If either the insurance or process agent filings were not completed within this 90-day period, the Agency would dismiss the registration request.</P>
                    <P>In addition, the Agency proposed a 180-day grace period for the newly required administrative filings by existing exempt for-hire and covered private motor carriers.</P>
                    <HD SOURCE="HD3">6. USDOT Number as the Sole Identifier for Entities Registered in URS</HD>
                    <P>
                        At the time of publication of the NPRM, FMCSA registration systems used five identification numbers: (1) The USDOT Number; (2) the MC Number (assigned to non-exempt for-hire motor carriers and brokers registering under 49 U.S.C. chapter 139); (3) the FF Number (assigned to freight forwarders); (4) the MX Number (assigned to Mexico-domiciled motor carriers operating exclusively within municipalities in the United States on the U.S.-Mexico international border and the commercial zones of such municipalities; and (5) cargo tank facility (CT) numbers. The Agency proposed to discontinue issuing MC, MX, and FF Number designations and to phase out the use of current MC, MX, and FF Numbers within 2 years of the compliance date for the URS final rule. Thus, the USDOT Number would become the sole identification number for all entities registered by FMCSA (except for cargo tank facilities). This unique USDOT Number would be 
                        <PRTPAGE P="66510"/>
                        displayed on the side of the vehicle pursuant to the CMV marking requirement in 49 CFR 390.21. The FMCSA would issue a USDOT Number with a distinctive suffix to any Mexico-domiciled motor carrier granted registration.
                    </P>
                    <HD SOURCE="HD3">7. The Application Process</HD>
                    <P>The Agency proposed under subpart A to part 360 a new multi-step application process and procedures for issuance of a USDOT Number under which an applicant would begin the registration process by filing a completed Form MCSA-1 and paying the registration fee. If the Agency accepted the Form MCSA-1 application, it would assign a temporary number to track the application through the registration process and enable registrants to make required administrative filings. The applicant's financial responsibility agent would use the tracking number to file evidence of compliance with FMCSA financial responsibility requirements under 49 CFR part 387; the motor carrier or its agent also would use the temporary tracking number to make a process agent designation filing. An applicant would be prohibited from commencing operations until the Agency issues a USDOT Number and grants registration.</P>
                    <P>Upon receipt of the USDOT Number, a motor carrier applicant would be considered a “new entrant” and placed under the appropriate safety monitoring program. A U.S.- or Canada-domiciled motor carrier would be subject to the FMCSA New Entrant Safety Assurance Program described under 49 CFR part 385, subpart D, which includes a safety audit. The provisional registration is the new entrant registration defined at 49 CFR 385.3. New entrant registration for these motor carriers would become permanent only if the applicant satisfactorily completed the New Entrant Safety Assurance Program. Similarly, to receive permanent registration, a Mexico-domiciled new entrant operating exclusively within the border commercial zones would be required to satisfactorily complete the safety monitoring program and safety audit described under 49 CFR part 385, subpart B. Motor carrier operating authority obtained under the procedures in 49 CFR part 365 would not become permanent until an applicant operating commercial motor vehicles satisfactorily completed the New Entrant Safety Assurance Program.</P>
                    <HD SOURCE="HD3">Special procedures for chapter 139 brokers, freight forwarders or motor carriers</HD>
                    <P>Current registration procedures in 49 U.S.C. 13902 allow anyone to oppose a request for permanent operating authority by non-exempt for-hire motor carriers, property brokers, and freight forwarders, provided the protest is based upon the applicant's willingness and ability to comply with: (1) The registration procedures; (2) applicable DOT regulations, including the Federal Motor Carrier Safety Regulations (FMCSRs), Hazardous Materials Regulations (HMRs) and regulations implementing the Americans with Disabilities Act (ADA); (3) the safety fitness standards; and/or (4) the financial responsibility requirements. The proposed unified registration system would continue to allow protests for applications covered under section 13902, but would not extend the right of protest to applications for registration filed by private motor carriers or exempt for-hire motor carriers.</P>
                    <P>In accordance with section 13902, FMCSA must notify the public when applications for authority are under consideration and provide an opportunity for protest. Upon acceptance of an application for registration from a chapter 139 entity, FMCSA would publish notice of the application in the FMCSA Register, initiating a 10-day protest period. The Agency would issue the applicant a temporary tracking number for the purpose of completing administrative filings and tracking the application through the registration process. If the Agency denied an application based on a protest, the application would be dismissed, and the registration fee would not be refunded.</P>
                    <P>If the application of a broker or freight forwarder is not protested or if insufficient grounds exist to deny a protested application, the Agency would issue a USDOT Number and grant permanent registration. Brokers and freight forwarders are not subject to a safety monitoring program.</P>
                    <P>If the application of a non-exempt motor carrier is not protested, or if insufficient grounds exist to deny a protested application, FMCSA would grant the applicant new entrant registration subject to completion of applicable administrative requirements. New entrant registration would become permanent registration only after satisfactory completion of the New Entrant Safety Assurance Program.</P>
                    <HD SOURCE="HD3">8. The Proposed Application Form (MCSA-1)</HD>
                    <P>The FMCSA proposed to combine the data elements now captured on several different licensing, registration and certification forms into a single, new application form called the Form MCSA-1. For those entities subject to URS, Form MCSA-1 would replace the following forms: (1) Motor Carrier Identification Report (Application for USDOT Number), Form MCS-150; (2) Application for Motor Property Carrier and Broker Authority, Form OP-1; (3) Application for Motor Passenger Carrier Authority, Form OP-1(P); (4) Application for Freight Forwarder Authority, Form OP-1(FF); and (5) Application for Mexican Certificate of Registration for Foreign Motor Carriers and Foreign Motor Private Carriers Under 49 U.S.C. 13902, Form OP-2. The NPRM also invited comments on whether the URS should incorporate the data requirements of three other registration processes: (1) Registration of Mexico-domiciled motor carriers seeking to operate between points in Mexico and points in the United States beyond the border commercial zones, Form OP-1(MX); (2) registration of entities requesting a hazardous materials safety permit, Form MCS-150B; and (3) registration of cargo tank facilities (which is requested in a letter submitted by the applicant to FMCSA).</P>
                    <HD SOURCE="HD3">9. Electronic Filing Requirement With Paper Filing Option</HD>
                    <P>The FMCSA proposed an online electronic application process with a paper filing option. The Agency requested comments on the benefits or hardships applicants might experience from a mandatory online electronic filing requirement. The Agency also asked whether it should immediately require online electronic filing or provide a phase-in period. The FMCSA noted several factors in support of an online filing requirement:</P>
                    <P>• There is widespread public access to computers and the Internet;</P>
                    <P>• In 2005 when the Agency published the NPRM, more than 70 percent of U.S. motor carriers had Internet access, with Internet access clearly increasing;</P>
                    <P>• Automated error-checking would result in more accurate information about the applicant;</P>
                    <P>• Online filing would allow USDOT Numbers to be issued faster, substantially reducing the current 2- to 4-week paper-based processing time for registration applications; and</P>
                    <P>
                        • Online filing would be more cost-effective for FMCSA than manually processing applications.
                        <PRTPAGE P="66511"/>
                    </P>
                    <HD SOURCE="HD3">10. Biennial Update Requirement</HD>
                    <P>The FMCSA proposed to require biennial updates using proposed Form MCSA-1 by all motor carriers, brokers and freight forwarders. Passenger and property motor carriers, freight forwarders, and property brokers would have to file regular updates to their registration information every 24 months. At the time the URS NPRM was published (May 19, 2005), existing § 390.19 required only safety registration information filed on Form MCS-150 or Form MCS-150-B to be updated. There was no requirement for non-exempt for-hire motor carriers, property brokers, and freight forwarders to biennially update commercial registration information. In the May 2005 NPRM, the Agency explained that since the Form MCSA-1 would combine safety and commercial registration for most motor carriers, FMCSA had preliminarily concluded it is reasonable to extend the biennial update requirement to all motor carriers subject to FMCSA's commercial and safety jurisdiction. As a result, all motor carriers, property brokers, and freight forwarders would need to file biennial updates. The registration updates would provide valuable motor carrier and fleet information and would be useful in assessing safety performance. A motor carrier that registers its vehicles in a Performance and Registration Information Systems Management (PRISM) Program State would fulfill the biennial update through its annual State re-registration requirement.</P>
                    <HD SOURCE="HD3">11. Transfers of Operating Authority</HD>
                    <P>Existing 49 CFR part 365, subpart D, permits non-exempt for-hire motor carriers, brokers and freight forwarders that register under chapter 139 to merge, transfer or lease their operating authority (indicated by an MC or FF Number), and establishes procedures for Agency approval of these transactions. Currently, these entities are required to file transfer applications with FMCSA and pay a $300 fee.</P>
                    <P>
                        The Agency determined that in enacting the ICCTA, Congress repealed pre-existing statutory authority to approve transfers of operating authority (former 49 U.S.C. 10926). Accordingly, the Agency proposed to discontinue regulation of transfers of operating authority and to remove 49 CFR part 365, subpart D, governing such transfers from the FMCSRs.
                        <SU>7</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             FMCSA (then part of the Federal Highway Administration) initially proposed removal of the transfer regulations in a February 13, 1998 NPRM (63 FR 7362). On May 16, 2001, FMCSA published a notice in the 
                            <E T="04">Federal Register</E>
                             (66 FR 27059) announcing the withdrawal of the February 1998 NPRM with the intention of addressing the transfer issue in the URS rulemaking.
                        </P>
                    </FTNT>
                    <P>The FMCSA proposed to issue only a USDOT Number as an indicator of operating authority. Issuance of MC, MX, and FF Numbers would be discontinued. Unlike chapter 139 certificates and permits, which have traditionally been considered transferable motor carrier assets, a USDOT Number is a unique identifier used to monitor a carrier's safety performance. As such, the USDOT Number never has been subject to transfer.</P>
                    <P>Under the proposal, the Agency would permit retention of an existing USDOT Number in a situation where an entity changed its legal name, form of business, or address, provided that there was no change in the ownership, management, or control of the entity. Thus, the USDOT Number could be retained following a change in the legal name of a sole proprietorship, corporation, or partnership; a change in the trade name or assumed name of an entity; and a change in the form of a business, such as the incorporation of a partnership or sole proprietorship. The Agency proposed that all entities requesting a change in legal name, form of business, or address be required to fill out a revised Form MCSA-1 within 20 days of the precipitating change with a certification that there had been no change in the ownership, management, or control of the entity holding the USDOT Number. Such a certification would have addressed whether the change in name, form of business, or address was associated with a transfer of the operating authority.</P>
                    <HD SOURCE="HD3">12. Cancellation, Reinstatement, and Deactivation of USDOT Registration</HD>
                    <P>Under existing procedures, if a motor carrier, broker or freight forwarder whose operations are authorized under 49 U.S.C. chapter 139 wishes to voluntarily cancel its operating authority, it must submit a notarized Form OCE-46, “Voluntary Revocation Request,” or electronically file its request. In the May 2005 NPRM, the Agency proposed to replace the voluntary revocation request procedure with the procedure now used by motor carriers requesting to discontinue use of a USDOT Number. Motor carriers would be required to mail or electronically submit to the Agency a cancellation request and certification statement under proposed § 360.701. Use of the Form OCE-46 would be discontinued.</P>
                    <P>Under proposed § 360.705, FMCSA would deactivate a motor carrier's USDOT Registration if the carrier failed to comply with the financial responsibility and process agent filing requirements.</P>
                    <P>Under proposed § 360.707, a motor carrier, broker or freight forwarder could reinstate a USDOT Registration that had been deactivated for less than 2 years by making the necessary filings and paying a reinstatement fee. If the USDOT Registration had been deactivated for 2 or more years, the entity would need to request the Agency to activate its USDOT Registration (under the previously-issued USDOT Number) by completing the procedures in proposed subpart A to part 360, including payment of a registration fee. A motor carrier that sought to reinstate its USDOT Registration after 2 years of being deactivated would be classified as a new entrant.</P>
                    <P>In setting the proposed threshold for reclassification of a carrier as a new entrant at 2 years, the Agency sought to prevent carriers that go in and out of business for very short periods of time from being required to re-enter the New Entrant Safety Assurance Program. The 2-year threshold also would parallel the existing 2-year update requirement for motor carrier information.</P>
                    <HD SOURCE="HD3">13. Requirements for Special Transit Operations (Federal Transit Administration (FTA) Grantees)</HD>
                    <P>The Agency proposed to include under URS passenger carriers that provide service funded, in whole or in part, by a grant from the FTA under 49 U.S.C. 5307, 5310, or 5311. (49 U.S.C. 31138(e)(4)). These motor carriers currently are exempt from Federal financial responsibility requirements but must comply with the highest minimum requirement imposed by any State in which they operate. The Agency proposed to waive all fees for FTA grantees, including the registration fee, insurance filing fee, and any fees related to the self-insurance approval process. It also proposed amending 49 CFR part 387 to reflect the financial responsibility requirements unique to FTA grantees.</P>
                    <HD SOURCE="HD1">III. Discussion of the Supplemental Notice of Proposed Rulemaking</HD>
                    <HD SOURCE="HD2">A. New Regulatory Drafting Strategy</HD>
                    <P>
                        The Agency proposes in the SNPRM to use a different regulatory drafting strategy than earlier proposed. The FMCSA would not at this time attempt to combine and redraft within a single CFR part the diverse application and program requirements as proposed in the May 2005 URS NPRM. Instead, the Agency proposes an incremental approach that would establish a general 
                        <PRTPAGE P="66512"/>
                        requirement under 49 CFR part 390, subpart C, for all entities under FMCSA safety or commercial jurisdiction to obtain USDOT Registration. USDOT Registration encompasses all registration requirements for FMCSA regulated entities, including the identification of motor carriers and intermodal equipment providers for safety oversight, as required under 49 U.S.C. 31144, commercial registration required under 49 U.S.C. chapter 139, hazardous materials safety permitting required under 49 U.S.C. 5109, and cargo tank facility registration required under 49 CFR 107.502 and 49 U.S.C. 5108. Existing 49 CFR part 390, subpart C, which includes in-depth information governing intermodal equipment providers, would be re-designated as subpart D to part 390.
                    </P>
                    <P>Fee schedules would remain under 49 CFR part 360, and information regarding designation of process agents would remain under 49 CFR part 366.</P>
                    <P>Conforming amendments would be made to parts 360, 365, 366, 368, and 385 to replace references to obsolete forms in the OP- and MCS-series with references to proposed Form MCSA-1, the Application for USDOT Number/Operating Authority.</P>
                    <P>The new regulatory strategy is necessary because registration requirements vary widely among those entities regulated by FMCSA. Although Congress directed the Secretary to combine several distinct information systems into a new on-line replacement system, it did not direct that there be uniform requirements for all entities under FMCSA jurisdiction. For example, not all of the entities subject to FMCSA safety oversight are subject to its commercial jurisdiction under 49 U.S.C. chapter 139 and thus required to obtain certificates, permits and licenses granted to motor carriers, brokers and freight forwarders, respectively. For this reason, the Unified Registration System would need to accommodate these distinctions as long as they exist.</P>
                    <HD SOURCE="HD2">B. The Proposal</HD>
                    <P>The comment period for the May 2005 URS NPRM closed on August 17, 2005. The FMCSA received a total of 60 comment submissions to the docket from 58 entities, including State and local government agencies, motor carriers, industry trade associations, enforcement associations, safety advocates, and private citizens. Most comments supported creation of a unified registration system. Because the Agency is soliciting additional comments on modifications made to the NPRM, we will not, at this point in the proceeding, address all comments received. Comments will be discussed if they have resulted in changes to the Agency's original proposal. A more detailed response to comments received to both the NPRM and this SNPRM will be included in the preamble to the final URS rule.</P>
                    <P>Major proposals carried over from the 2005 NPRM to this SNPRM include the following:</P>
                    <P>• The URS would combine (1) the USDOT identification number system; (2) the Title 49, chapter 139 commercial registration system; and (3) the 49 U.S.C. 13906 financial responsibility information system into a new single, online system. In accordance with section 4304 of SAFETEA-LU, the Agency also proposes inclusion of the service of process agent designation system in accordance with 49 U.S.C. 503 and 13304.</P>
                    <P>• All regulated entities would be required to update registration information every 2 years.</P>
                    <P>• All entities registered under URS would be identified by FMCSA solely by the USDOT Number. Motor carriers could continue to use obsolete MC Numbers for business and advertising reasons, and the Agency would not require a motor carrier to remove the existing MC Number from its vehicles. But the Agency encourages motor carriers to refrain from displaying the MC Number on new or repainted CMVs once the rule becomes final.</P>
                    <P>• The Agency would no longer accept or review requests for transfers of operating authority.</P>
                    <P>• All existing private motor carriers that transport hazardous materials in interstate commerce would be required to maintain and file evidence of financial responsibility with the Agency. There would be at least a 3-month moratorium on enforcement of the filing requirement after the effective date of the rule. The moratorium would not apply to new entrants.</P>
                    <HD SOURCE="HD3">1. Single State Registration System (SSRS)</HD>
                    <P>Although numerous commenters addressed SSRS issues, section 4305 of SAFETEA-LU repealed the SSRS and placed responsibility for developing an SSRS replacement system with the Unified Carrier Registration Plan (UCR Plan). Under Section 4305(b) of SAFETEA-LU, the UCR Plan is the organization responsible for developing, implementing, and administering the Unified Carrier Registration Agreement (49 U.S.C. 14504a(a)(9)) (UCR Agreement). The UCR Agreement developed by the UCR Plan is the “interstate agreement governing the collection and distribution of registration and financial responsibility information provided and fees paid by motor carriers, motor private carriers, brokers, freight forwarders and leasing companies * * *.” (49 U.S.C. 14504a(a)(8)).</P>
                    <P>
                        The statute provides for a 15-member Board of Directors for the UCR Plan and Agreement (Board) appointed by the Secretary of Transportation, only one of whom shall be from the Department of Transportation. The remaining Board members represent State agencies and the motor carrier industry. The establishment of the Board was announced in the 
                        <E T="04">Federal Register</E>
                         on May 12, 2006 (71 FR 27777).
                    </P>
                    <P>
                        The Board is charged with developing regulations governing the UCR Agreement and recommends the applicable fees to the Secretary of Transportation.
                        <SU>8</SU>
                        <FTREF/>
                         The FMCSA is required by SAFETEA-LU to set the fees within 90 days after receiving the Board's recommendation and after notice and opportunity for public comment (49 U.S.C. 14504a(d)(7)(B)).
                    </P>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             The Secretary's functions under section 14504a have been delegated to the Administrator of the Federal Motor Carrier Safety Administration. 49 CFR 1.73(a)(7), as amended, 71 FR 30833 (May 31, 2006).
                        </P>
                    </FTNT>
                    <P>
                        The FMCSA described the statutory requirements in detail in an NPRM published on May 29, 2007 (72 FR 29472). On Friday, August 24, 2007, the Agency published a final rule establishing initial fees for 2007 and a fee bracket structure for the Unified Carrier Registration Agreement in the 
                        <E T="04">Federal Register</E>
                         (72 FR 48585). The FMCSA subsequently adjusted the UCR Agreement fees and fee bracket structure in a final rule dated April 27, 2010 (74 FR 21993).
                    </P>
                    <P>For reasons stated in Section I of this SNPRM, development of the replacement system for the SSRS is no longer addressed under the URS rulemaking.</P>
                    <HD SOURCE="HD3">2. Entities Subject to the URS Registration Requirement</HD>
                    <P>
                        Except as noted below, the Agency proposes to require all entities which are under FMCSA commercial or safety jurisdiction to register under the Unified Registration System using proposed Form MCSA-1. Section 4304 of SAFETEA-LU amended 49 U.S.C. 13908(b) to require the Federal on-line replacement system to “serve as a clearinghouse and depository of information on, and identification of, all foreign and domestic motor carriers, motor private carriers, brokers, freight forwarders, and others required to register with the Department of Transportation * * *.” The FMCSA 
                        <PRTPAGE P="66513"/>
                        interprets this statute as authorizing the inclusion of all entities regulated by FMCSA in the Unified Registration System.
                    </P>
                    <P>Accordingly, proposed 49 CFR 390.101 would establish a general requirement for all regulated entities, except Mexico-domiciled motor carriers seeking authority to operate beyond the border commercial zones (Mexico-domiciled long-haul carriers), to obtain USDOT Registration by filing proposed Form MCSA-1 and to provide FMCSA biennial updates of the registration information.</P>
                    <P>Under proposed § 390.102, a motor carrier that registers its vehicles in a State that participates in the Performance and Registration Information Systems Management program (PRISM) alternatively could satisfy the USDOT registration and biennial update requirements in § 390.101 by electronically filing the required information with the State Driver Licensing Agency (SDLA) according to its policies and procedures, provided the SDLA has integrated the USDOT registration/update capability into its vehicle registration program. If State procedures do not allow a motor carrier to file the MCSA-1 form or to submit updates within the required 24-month window, the motor carrier would need to complete such filings directly with FMCSA.</P>
                    <P>Proposed § 390.103 would require all for-hire motor carriers and private motor carriers that transport hazardous materials in interstate commerce, as well as brokers and freight forwarders, to file evidence of financial responsibility to receive USDOT Registration.</P>
                    <P>Although seven comments supported the inclusion of Mexico-domiciled long-haul carriers in the unified system, the Agency does not propose to include such carriers at this time. In September 2007, FMCSA began registering Mexico-domiciled long-haul carriers under a limited-term cross-border demonstration project in which participation by Mexican carriers was voluntary. This program was discontinued in March 2009, following enactment of section 136 of the Transportation, Housing and Urban Development, and Related Agencies Appropriations Act, 2009 [Division I, title I of the Omnibus Appropriations Act, 2009, Public Law 111-8, March 11, 2009], which prohibited the use of funds appropriated in that Act to establish, implement, continue, promote, or in any way permit a cross-border demonstration program. Subsequent to enactment of section 136, Congress has not enacted any language that prohibits funding for a new cross-border demonstration program. Currently, FMCSA and USDOT are working closely with the Government of Mexico to implement a new phased-in long-haul cross border trucking program. FMCSA's experiences in implementing this new program will be important in assessing the need to propose further changes in the unified program at a future date. The applicable procedures governing transportation by Mexico-domiciled motor carriers beyond the municipalities and commercial zones along the United States-Mexico international border remain 49 CFR part 365, subpart E, 49 CFR part 385, subpart B, and 49 CFR 390.19.</P>
                    <P>Proposed § 390.105 would list, and provide cross-references to, other governing regulations that are applicable to those requesting USDOT Registration. For-hire and private motor carriers, brokers and freight forwarders additionally would be required to designate a process agent as a pre-condition for receiving USDOT Registration and commercial operating authority, when applicable. U.S. and Canada-domiciled motor carriers must satisfactorily complete the new entrant safety assurance program under 49 CFR part 385, subpart D in order for their USDOT Registration and commercial operating authority, if applicable, to become permanent. A Mexico-domiciled motor carrier is subject to the safety monitoring system under 49 CFR part 385, subpart B. A non-North America-domiciled motor carrier is subject to the requirements of 49 CFR part 385, subpart H, and must complete the safety monitoring program under 49 CFR part 385, subpart I. An intermodal equipment provider is subject to the requirements of 49 CFR part 390, subpart D. A person who applies for a hazardous materials safety permit is subject to the requirements of 49 CFR part 385, subpart E. A cargo tank facility is subject to the requirements of 49 CFR part 107, subpart F, 49 CFR part 172, subpart H, and 49 CFR part 180.</P>
                    <P>Finally, § 390.107 would direct a non-North America-domiciled motor carrier that requests authority to conduct interstate commerce within the United States to § 385.607(a) for detailed information about the requirement to complete a pre-authorization safety audit as a pre-condition for receiving USDOT Registration and commercial operating authority, if applicable.</P>
                    <P>By placing the unified registration requirement under part 390, FMCSA State partners that participate in the Motor Carrier Safety Assistance Program would be able to enforce the registration requirement consistent with the compatibility requirements under 49 CFR parts 350 and 355.</P>
                    <P>All entities required to register under URS are listed in the chart below:</P>
                    <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s100,r300">
                        <TTITLE>Entities Required To Register Under the Unified Registration System</TTITLE>
                        <BOXHD>
                            <CHED H="1">Entity</CHED>
                            <CHED H="1">Description</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22">1. A for hire or private motor carrier domiciled in the U.S., Canada, Mexico or a non-North American country:</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">a. For-hire carrier</ENT>
                            <ENT>A person engaged in the transportation of goods or passengers for compensation.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">i. Exempt</ENT>
                            <ENT>A person engaged in transportation exempt from commercial regulation by the Federal Motor Carrier Safety Administration (FMCSA) under 49 U.S.C. chapter 135. Exempt motor carriers that operate commercial motor vehicles as defined in 49 U.S.C. 31101 are subject to the safety regulations set forth in Part B of Subtitle VI of subchapter B of Title 49 Code of Federal Regulations.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">ii. Non-exempt</ENT>
                            <ENT>A person engaged in transportation subject to commercial regulation by the Federal Motor Carrier Safety Administration (FMCSA) under 49 U.S.C. chapter 139, regardless of whether such transportation is subject to the safety regulations.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">b. Private carrier</ENT>
                            <ENT>A person who provides transportation of property or passengers, by commercial motor vehicle, and is not a for-hire motor carrier.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2. Broker</ENT>
                            <ENT>A person who, for compensation, arranges, or offers to arrange, the transportation of property by a non-exempt for-hire motor carrier.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="66514"/>
                            <ENT I="01">3. Freight forwarder</ENT>
                            <ENT>A person holding itself out to the general public (other than as an express, pipeline, rail, sleeping car, motor, or water carrier) to provide transportation of property for compensation in interstate commerce, and in the ordinary course of its business: (1) performs or provides for assembling, consolidating, break-bulk, and distribution of shipments; (2) assumes responsibility for transportation from place of receipt to destination; and (3) uses for any part of the transportation a carrier subject to FMCSA commercial jurisdiction.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4. Intermodal equipment provider</ENT>
                            <ENT>A person that interchanges intermodal equipment with a motor carrier pursuant to a written interchange agreement or has a contractual responsibility for the maintenance of the intermodal equipment.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">5. Hazardous Materials Safety Permit applicant</ENT>
                            <ENT>A motor carrier that transports in interstate or intrastate commerce any of the hazardous materials, in the quantity indicated for each, listed under 49 CFR 385.403.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6. Cargo tank facility</ENT>
                            <ENT>A cargo tank and cargo tank motor vehicle manufacturer, assembler, repairer, inspector, tester, and design certifying engineer subject to registration requirements under 49 CFR 107.502 and 49 U.S.C. 5108.</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD3">3. Proposed User Fees</HD>
                    <P>The Agency sets forth under § 360.3(f) proposed registration, insurance filing and other services fees as follows.</P>
                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s50,r100,r50">
                        <BOXHD>
                            <CHED H="1">Type of proceeding</CHED>
                            <CHED H="1"> </CHED>
                            <CHED H="1">Fee</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22">Part I: Registration:</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">(1)</ENT>
                            <ENT>An application for USDOT Registration pursuant to 49 CFR part 390, subpart C</ENT>
                            <ENT>$300.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">(2)</ENT>
                            <ENT>An application for motor carrier temporary authority issued in response to a national emergency or natural disaster and following an emergency declaration under § 390.23 of this subchapter</ENT>
                            <ENT>$100.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">(3)</ENT>
                            <ENT>Biennial update of registration</ENT>
                            <ENT>$0.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">(4)</ENT>
                            <ENT>Request for change of name, address, or form of business</ENT>
                            <ENT>$0.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">(5)</ENT>
                            <ENT>Request for cancellation of registration</ENT>
                            <ENT>$0.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">(6)</ENT>
                            <ENT>Request for registration reinstatement</ENT>
                            <ENT>$10.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">(7)</ENT>
                            <ENT>Designation of process agent</ENT>
                            <ENT>$0.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">Part II: Insurance:</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">(8)</ENT>
                            <ENT>A service fee for insurer, surety, or self-insurer accepted certificate of insurance, surety bond, and other instrument submitted in lieu of a broker surety bond</ENT>
                            <ENT>$10 per accepted certificate, surety bond or other instrument submitted in lieu of a broker surety bond.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">(9)</ENT>
                            <ENT>(i) An application for original qualification as self-insurer for bodily injury and property damage insurance (BI&amp;PD)</ENT>
                            <ENT>[Reserved].</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>(ii) An application for original qualification as self-insurer for cargo insurance</ENT>
                            <ENT>[Reserved].</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>(iii) Fee for quarterly self-insurance monitoring filing</ENT>
                            <ENT>[Reserved].</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>(iv) Fee for annual self-insurance monitoring filing</ENT>
                            <ENT>[Reserved].</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>The Agency proposes a $300 registration fee for all registered entities. Please refer to the discussion of the proposed new registration fee under “IV. Regulatory Evaluation of the URS SNPRM: Summary of Benefits and Costs” of the preamble for an explanation of the basis for this proposal. The FMCSA proposes to charge a $10 registration reinstatement fee for those seeking to reinstate USDOT registration as a result of failure to maintain required financial responsibility and process agent designation filings with the Agency. The FMCSA also proposes to change the fee currently charged for reinstating commercial operating authority after such authority has been revoked from $80 to $10. After completion of required filings (financial responsibility or process agent designation) and payment of the reinstatement fee, the information system would match up the payment with the filings and automatically issue a reinstatement letter at 5:00 am on the next business day. Section 360.3(f)(7) would eliminate the existing $10 process agent designation filing fee because section 4304 of SAFETEA-LU amended 49 U.S.C. 13908(d)(2) to prohibit the Agency from charging a fee for filing designation of an agent for service of process.</P>
                    <P>The Agency proposes under § 360.1(e)(1) to exempt any Agency of the Federal Government or a State government or any political subdivision of any such government from paying the fees listed in § 360.3(f) to access or retrieve URS data for its own use. Proposed paragraph (e)(2) would exempt any registered entity within URS from paying fees to access or retrieve its own data.</P>
                    <HD SOURCE="HD3">4. Financial Responsibility</HD>
                    <HD SOURCE="HD3">Bodily Injury and Property Damage Insurance</HD>
                    <P>
                        <E T="03">For-hire motor carriers.</E>
                         Existing regulations require only non-exempt for-hire motor carriers to file evidence of financial responsibility with the Agency. The NPRM included a proposal to require both exempt and non-exempt for-hire motor carriers to file evidence of financial responsibility with the Agency as a precondition to receiving registration. Section 4303(b) of SAFETEA-LU amended financial security requirements under 49 U.S.C. 13906 by requiring “all persons, other than a motor private carrier, registered with the Secretary to provide transportation or service as a motor 
                        <PRTPAGE P="66515"/>
                        carrier under section 13905(b)” to file evidence of financial responsibility with the Agency by December 10, 2005. The Agency believes amended 49 U.S.C. 13906 mandates financial responsibility filings by all for-hire motor carriers. Therefore, the Agency retains its proposal for such filings to be required as a precondition for registration under proposed §§ 390.103(a)(2)(i) and 387.303
                    </P>
                    <P>
                        <E T="03">Private motor carriers hauling hazardous materials.</E>
                         The SNPRM retains under § 390.103(a)(2)(ii) the proposal that a private motor carrier hauling hazardous materials in interstate commerce be required to file evidence of financial responsibility with the Agency to receive registration. However, a private motor carrier hauling hazardous materials in bulk in intrastate commerce would continue to be required to meet the financial responsibility requirements under 49 CFR part 387 and maintain evidence of having met the financial responsibility requirements at its principal place of business.
                        <SU>9</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             The statutory authority to require motor private carriers to file evidence of insurance with FMCSA is codified at 49 U.S.C. 31139(c). This authority expressly applies to minimum levels of financial responsibility established by the Secretary under 49 U.S.C. 31139(b). Section 31139(b) only applies to financial responsibility requirements for transportation in interstate commerce. Although the Secretary has other authority, in 49 U.S.C. 31139(d), to establish minimum levels of financial responsibility for intrastate transportation of hazardous materials, section 31139(d) does not authorize the Secretary to require that evidence of such insurance be filed with FMCSA.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Private motor carriers not hauling hazardous materials.</E>
                         Initially, section 4120(a)(1) of SAFETEA-LU amended 49 U.S.C. 31138(a) and 31139(b)(1) to remove the phrase “for compensation” from the statutes governing financial responsibility and filing of evidence of financial responsibility with the Agency, thereby creating a financial responsibility requirement for private motor carriers, which the Agency was required to implement through rulemaking. Section 4120(a)(2) stated the Agency could require a private non-hazardous materials motor carrier to file evidence of financial responsibility with FMCSA. Section 305(a) of the SAFETEA-LU Technical Corrections Act of 2008 [Pub. L. 110-244, 122 Stat. 1619-1620, June 6, 2008] amended section 31138 by limiting the Secretary's authority to establish minimum levels of financial responsibility for private motor carriers of passengers to those carriers transporting passengers for commercial purposes.
                    </P>
                    <P>The Agency anticipates that a proposal regarding financial responsibility for private non-hazardous materials motor carriers would generate major interest from the private motor carrier community and might cause a significant delay in completing the URS rulemaking. Consequently, FMCSA has decided to address the financial responsibility requirements for private non-hazardous material motor carriers in a separate rulemaking from URS.</P>
                    <P>
                        <E T="03">Brokers and freight forwarders.</E>
                         Brokers and freight forwarders would be required under proposed § 390.103(a)(2) to file evidence of financial responsibility as a pre-condition to registration. This requirement includes only those freight forwarders that perform transfer, collection and delivery service (
                        <E T="03">i.e.,</E>
                         operate a motor vehicle). Under the existing regulations, only HHG freight forwarders performing transfer, collection and delivery service are subject to this requirement. These regulations were transferred without change from the Interstate Commerce Commission following enactment of the ICCTA, which re-regulated general commodities freight forwarders. However, the regulations were not amended to reflect the Agency's broadened jurisdiction. The FMCSA believes there is no basis to limit the requirement to HHG freight forwarders and therefore proposes to extend this requirement to all freight forwarders.
                    </P>
                    <HD SOURCE="HD3">Restoration of Liability Insurance Requirements for Small Freight Vehicles</HD>
                    <P>
                        Section 4120 of SAFETEA-LU removed FMCSA's commercial jurisdiction over for-hire transportation of property in motor vehicles that did not meet the definition of commercial motor vehicle (CMV) under 49 U.S.C. 31132. Consequently, the Agency removed former 49 CFR 387.303(b)(1)(i), which established minimum public liability limits of $300,000 for fleets that consisted only of vehicles with Gross Vehicle Weight Ratings of under 10,000 pounds.
                        <SU>10</SU>
                        <FTREF/>
                         The SAFETEA-LU Technical Corrections Act of 2008 restored the Agency's commercial jurisdiction over these vehicles. Accordingly, the Agency proposes to restore former § 387.303(b)(1)(i) with one minor change, revising 10,000 pounds to 10,001 pounds to be consistent with the statutory definition of CMV.
                    </P>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             See 72 FR 55697, 55702 (October 1, 2007).
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Cargo Insurance.</E>
                         Section 4303(c) of SAFETEA-LU required the Agency to discontinue designating operating authority as common or contract carriage beginning January 1, 2007. The FMCSA concluded that because the cargo insurance requirement is tied to the common/contract distinction, and because we no longer may distinguish between common and contract carriers in the Agency's registration process or base any regulations upon that distinction, it was important to address the cargo insurance issue as quickly as possible. Consequently, the Agency published a separate final rule eliminating the cargo insurance requirement for for-hire motor carriers of property (except household goods motor carriers) and freight forwarders (except household goods freight forwarders), effective March 21, 2011 (75 FR 35318, June 22, 2010). The preamble to that final rule addressed the comments filed in this proceeding regarding the NPRM's cargo insurance proposal.
                    </P>
                    <HD SOURCE="HD3">Web-Based Filing by Insurers, Surety Companies, and Financial Institutions</HD>
                    <P>
                        The Agency would require insurers, surety companies and financial institutions to convert to a Web-based format when electronically filing evidence of financial responsibility. (§ 387.323) These filings would include evidence of surety bonds, certificates of insurance, trust-fund agreements, proof of qualifications to self-insure, and notices of cancellations. The Agency also proposes conforming amendments to miscellaneous sections governing financial responsibility requirements to convey that electronic filing would be mandatory and not optional. (
                        <E T="03">§§ 360.3(a)(2), 387.313(b), 387.313(d), 387.323, 387.413(b), and 387.419)</E>
                    </P>
                    <HD SOURCE="HD3">Self-Insurance Program</HD>
                    <P>Commenters generally supported the proposal to modify fees related to the self-insurance program. Currently, the cost of the program exceeds the amounts recovered from fees collected from those entities that self-insure. The Agency believes that because entities that qualify to self-insure receive a valuable benefit, it is reasonable and appropriate for the fees charged to support the costs of administering the program. However, FMCSA has determined that the proposed fees for the self-insurance program published in the 2005 NPRM are inadequate to recover Agency costs to administer the program, including the costs of evaluating and monitoring the financial health of motor carriers requesting approval to participate in the self-insurance program. The Agency seeks to make the self-insurance program self-sustaining more quickly and is therefore developing a separate rulemaking to address this issue.</P>
                    <HD SOURCE="HD3">Editorial Changes</HD>
                    <P>
                        The Agency proposes to remove obsolete effective dates and liability 
                        <PRTPAGE P="66516"/>
                        information from the schedule of limits on Form MCS-90B, Endorsement for Motor Carrier Policies of Insurance for Public Liability Under Section 18 of the Bus Regulatory Reform Act of 1982 (Illustration I to § 387.39). Also, the Agency would correct an omission in § 387.419 by adding the phrase “notice of cancellations.” Although the existing section heading is “Electronic filing of surety bonds, certificates of insurance and cancellations” the Agency neglected to include information regarding cancellations.
                    </P>
                    <HD SOURCE="HD3">5. Process Agent Designations</HD>
                    <P>The Agency, by proposing to amend 49 CFR 366.1, retains the NPRM proposal to include private and exempt for-hire motor carriers among those entities that would be required to file process agent designations with FMCSA. Private motor carriers are already mandated by 49 U.S.C. 503 to make such filings, although FMCSA has not yet promulgated a rule requiring them to do so. Inasmuch as non-exempt for-hire motor carriers, brokers, and freight forwarders are required to file process agent designations under 49 U.S.C. 13303 and 13304, approximately 90 percent of the entities subject to this rule are required, by statute, to file such designations. Although there is no statutory requirement that exempt for-hire carriers file process agent designations, FMCSA believes that extending the process agent designation requirement to include such carriers, as well as private carriers, would enhance the public's ability to serve legal process on responsible individuals when seeking compensation for losses resulting from a crash involving a commercial motor vehicle operated by any motor carrier, regardless of the carrier's regulatory status. Moreover, FMCSA would be able to better identify the appropriate individual(s) upon whom to serve notices for enforcement actions. The Agency invites comments on whether the process agent filing process can be made less costly.</P>
                    <P>The FMCSA also proposes to amend § 366.1 by including freight forwarders among those entities required to file process agent designations with FMCSA. Under 49 U.S.C. 13303(a), a freight forwarder providing service under FMCSA jurisdiction must designate an agent on whom service of notices in Agency proceedings, as well as service of Agency actions, may be made.</P>
                    <P>The FMCSA proposes to amend § 366.6 to obligate those entities that would be required to file a process agent designation to update FMCSA of any changes to the designated process agent's information, including name, address or contact information. Amended § 366.6 would require the report to be made within 20 days of the change.</P>
                    <HD SOURCE="HD3">6. Timeframes for Filing Evidence of Financial Responsibility and Process Agent Designation</HD>
                    <P>As proposed in the NPRM, the Agency would require new filings of both evidence of financial responsibility and designation of agents for service of process to be completed within 90 days of the date that an application is submitted, or within 90 days of the date that the notice of application is published in the FMCSA Register if a carrier also is seeking commercial operating authority. (§ 365.109) The proposed 90-day time period combines the existing 20-day initial deadline and 60-day extension period and adds 10 more days for Agency processing.</P>
                    <P>Section 4303(b) of SAFETEA-LU amended 49 U.S.C. 13906(a) to establish December 10, 2005 as the deadline for existing exempt for-hire motor carriers to make insurance filings with FMCSA, making it unnecessary to propose a grace period for financial responsibility filings. Inasmuch as section 13906(a) excluded private motor carriers registered with the Agency under 13905(b) from the expedited financial responsibility filing requirement, and in the interest of treating all applicants who must file evidence of financial responsibility equitably, the Agency will not include in proposed § 390.103 a 180-day grace period for financial responsibility filings by existing exempt for-hire or private motor carriers. Such carriers would have to file by the effective date of the final rule.</P>
                    <P>The SNPRM includes, in proposed § 366.2(b), a 180-day grace period for all existing private and exempt for-hire motor carriers to file process agent designations. The grace period would be calculated from the final rule compliance date. The FMCSA believes the 180-day time period for existing private and exempt for-hire motor carriers to make process agent designations is necessary for Agency IT systems to accommodate the anticipated one-time surge in the number of filings from this group and to provide them adequate time to comply with the new filing requirements.</P>
                    <HD SOURCE="HD3">7. The Application Process</HD>
                    <P>The Agency proposed in the NPRM a new multi-step application process and procedures for issuance of a USDOT Number under which applicants would initially be assigned temporary numbers to track the application through the registration process and enable applicants and their agents to make required administrative filings using the tracking number. Under this proposal, an applicant would not receive a USDOT Number until all necessary filings were made and would be prohibited from commencing operations until the USDOT Number was issued.</P>
                    <P>The Owner-Operator Independent Drivers Association, Inc. (OOIDA) and Missouri Department of Transportation (MODOT) supported the proposed multi-phase application process. MODOT further stated that waiting until an application has passed initial screening before issuing a USDOT Number is a valid approach.</P>
                    <P>The American Trucking Associations, Inc. (ATA) commented that because USDOT Numbers and provisional registrations would no longer be issued at the time of application under the NPRM proposal, new carriers may be delayed entry into the market. ATA urged the Agency to supply applicants with temporary tracking numbers immediately upon receipt of the application and provide the applicant a point of contact at FMCSA. Greyhound stated that temporary tracking numbers would cause tremendous confusion and the Agency should issue a tentative USDOT Number at the beginning of the process, making the number permanent at the conclusion of the process.</P>
                    <P>
                        The MODOT, the Iowa Department of Transportation (IADOT), the American Association of Motor Vehicle Administrators (AAMVA), ATA, and the National Conference of State Transportation Specialists (NCSTS) filed comments opposing the proposed system. MODOT commented that as a partner in the implementation of the Federal safety fitness program it should be able to continue to issue USDOT Numbers under PRISM. AAMVA echoed the same concern, adding that if States are not able to issue USDOT Numbers, their resulting inability to deliver accurate and timely customer service will cause substantial delay for carriers wishing to enter the market. ATA found it “very disturbing” that the process for issuing USDOT Numbers and for updating MCS-150 data may conflict with PRISM requirements in such a way as to delay the vehicle registration of International Registration Plan (IRP) fleets. IADOT commented that under the NPRM the States' inability to issue USDOT Numbers to interstate carriers and registrants would have the following adverse impacts: (1) Increased processing time for first-time motor carriers, especially private carriers; and (2) increased costs for private and exempt carriers to operate. 
                        <PRTPAGE P="66517"/>
                        OOIDA urged FMCSA to ensure that States retain the ability to issue USDOT Numbers to registering owner-operators. OOIDA suggested that a simple separate electronic form should be used when a vehicle is registered, and owner-operator USDOT Numbers could be maintained in the URS system.
                    </P>
                    <P>After careful consideration of all filed comments and discussions with PRISM States that issue USDOT Numbers to carriers on FMCSA's behalf, the Agency has withdrawn the proposal to issue a temporary tracking number to applicants and issue a USDOT Number only after applicable administrative filings have been completed. Under proposed § 390.101(c)(2), each applicant would be issued an inactive USDOT Number. The inactive USDOT Number would be activated by the Agency only after the applicant has filed applicable administrative filings such as evidence of financial responsibility or a process agent designation. If a carrier also is seeking operating authority, the USDOT Number would remain inactive until all protests filed under 49 CFR part 365 have been resolved and the applicant has filed applicable administrative filings. The Agency also proposes new § 392.9b to prohibit a motor carrier with an inactive USDOT Number from operating a CMV and to establish penalties for violating the prohibition. This change has been made in order to allow PRISM States to continue to offer one-stop services to carriers and to better enable PRISM States to track and monitor carriers' safety performance. PRISM States and insurance companies would have had to alter their IT systems and administrative processes to accommodate the issuance of temporary tracking numbers, which would have been costly and time-consuming. The FMCSA believes its current proposal is the most transparent and efficient model.</P>
                    <P>The FMCSA plans to collaborate with PRISM States in developing a unified message to notify motor carriers, at the time of registration, that operating with an inactive USDOT Number would result in enforcement at the Federal and State levels. During vehicle registration, PRISM States would inform the motor carrier that its license plates would be suspended if its application for operating authority is denied as a result of the protest process, if appropriate administrative filings are not made within a specified number of days, and/or if its application is rejected during FMCSA review under 49 CFR 365.109.</P>
                    <HD SOURCE="HD3">8. Revisions to Proposed Application Form MCSA-1</HD>
                    <P>
                        The Agency proposed in the NPRM to combine the data elements now captured on several different licensing, registration and certification forms into a single, new application form called the Form MCSA-1. Commenters generally supported the use of a single form but urged that the form be as simple as possible. Although ATA generally supported the scope of the proposed Form MCSA-1, it argued that the benefits the new form could provide may be outweighed by problems caused by an unwieldy, complex, and inconvenient form. ATA urged the Agency to ensure that the form is as simple as possible for use by the majority of the trucking industry, which largely consists of small business entities. In particular, ATA said it is important for the form and its instructions to be clear regarding the transactions for which the form is to be used and the compliance requirements for each transaction type. ATA believes Form MCSA-1 should be concise and devoid of requests for safety- and non-safety-related information that are not required by the current FMCSRs and HMRs. Finally, ATA urged the Agency to review and eliminate all entries on Form MCSA-1 and its appendices that do not contain critical data needed for the registration process (
                        <E T="03">i.e.,</E>
                         research data).
                    </P>
                    <P>The Utah Department of Transportation (UTDOT) and the Utah Trucking Association (UTA) supported combining the filings in one form and using one online central access point for motor carriers, freight forwarders, and property brokers while providing an alternative for “mom and pop” companies that do not utilize computers.</P>
                    <P>The OOIDA supported combining several existing forms into one new form and urged the Agency to make the form available in hard copy to filers who are not “computer-savvy.” OOIDA supported the proposed collection of carrier and cargo classification and HHG arbitration information. OOIDA stated that the Bureau of Transportation Statistics (BTS) should continue to collect motor carrier financial information and sought verification that the collection of information on the new form is not intended to replace BTS information collection activities.</P>
                    <P>Greyhound believed proposed Form MCSA-1 and the instructions for its completion are somewhat confusing and need to be revised to be more user friendly. Greyhound and ABA recommended that the Agency “require applicants to demonstrate they are in compliance with the Americans with Disabilities Act (ADA) [[Pub. L. 101-336, Title I, § 102, July 26, 1990, 104 Stat. 331] as amended].” The Community Transportation Association of America (CTAA) applauded the Agency's efforts to unify all registration information into a single form but suggested some minor modifications to the proposed form.</P>
                    <P>The National Propane Gas Association (NPGA) believed information about gross operating revenue should not be collected. NPGA stated the Form MCSA-1 instructions are unclear regarding whether a hazardous materials shipper is required to file Form MCSA-1 and requested that the Agency modify the instructions to explicitly state that the proposed form would not apply to hazardous materials shippers. The Corporate Transportation Coalition (CTC) stated that there must continue to be a way to distinguish between private and for-hire carriers and recommended that private carriers not be required to submit financial data or other information unrelated to the safe operation of their truck fleets.</P>
                    <P>The American Moving and Storage Association (AMSA) commented that the more detailed and tougher congressional registration requirements for HHG movers should be incorporated in the URS rule. Advocates for Highway and Auto Safety (Advocates) supported the inclusion of the new entrant provisions in the URS rule.</P>
                    <P>The FMCSA agrees that proposed Form MCSA-1 should be as simple and easy to use as possible, consistent with the need to collect the necessary information. The FMCSA has reviewed the draft Form MCSA-1 and instructions in light of the various comments and made revisions to clarify the form and instructions and to eliminate extraneous material.</P>
                    <P>
                        The Agency proposes to revise the MCSA-1 form and instructions to collect registration information from all FMCSA regulated entities, except Mexico-domiciled long-haul carriers. Because hazardous materials shippers are not subject to the FMCSRs, the Agency also proposes to exclude them from the Unified Registration System. Conforming amendments are proposed for Form MCSA-1 and instructions as well. As mentioned previously, the URS rule was impacted by new provisions enacted by SAFETEA-LU and subsequently promulgated final rules, which brought new entities under FMCSA's registration jurisdiction (such as intermodal equipment providers and non-North America-domiciled motor carriers). To accommodate these 
                        <PRTPAGE P="66518"/>
                        changes, the Agency proposes changes to the MCSA-1 form and instructions, including additional questions and new or relocated sections as follows:
                    </P>
                    <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="xl100,r100">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">MCSA-1 Form—URS NPRM version</CHED>
                            <CHED H="1">MCSA-1 Form—URS SNPRM version</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Section A—Business Description</ENT>
                            <ENT>Section A—Business Description</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Section B—Motor Carriers</ENT>
                            <ENT>Section B—General Operational Information</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Section C—Hazardous Materials (HM)</ENT>
                            <ENT>Section C—Hazardous Materials (HM)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Section D—Transportation of Household Goods</ENT>
                            <ENT>Section D—Hazardous Materials Permitting</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Section E—Commercial Zone Operations</ENT>
                            <ENT>Section E—Cargo Tank Facility</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Section F—Additional Information</ENT>
                            <ENT>Section F—Transportation of Household Goods</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Section G—Safety Certifications</ENT>
                            <ENT>Section G—Transportation of Passengers</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Section H—Certifications</ENT>
                            <ENT>Section H—Scope of Authority</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Section I—Cancellation</ENT>
                            <ENT>Section I—Commercial Zone Operations</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Section J—Filing Fee Information</ENT>
                            <ENT>Section J—Non-North America-Domiciled Carriers</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Attachments to Section G (Supplemental information required only from a Mexico-domiciled motor carrier)</ENT>
                            <ENT/>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Section K—Additional Information</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Section L—Safety Certifications (Certifications applicable only to Mexico- or Non-North America-domiciled motor carriers)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Section M—Compliance Certifications</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Section N—Applicant's Oath</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Section O—Filing Fee Information</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Attachments to Section L—Supplemental Information required only from a Mexico- or Non-North America-domiciled motor carrier</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>Consistent with provisions under section 4204 of SAFETEA-LU, FMCSA proposes collection of additional registration information from HHG motor carriers as follows: (1) Evidence of participation in an arbitration program and a copy of the notice of the arbitration program as required by section 14708(b)(2); (2) identification of the carrier's tariff and a copy of the notice of availability of the tariff for inspection as required by section 13702(c); (3) evidence that carriers have access to, have read, are familiar with, and will observe all applicable Federal laws relating to consumer protection, estimating, consumers' rights and responsibilities, and options for limitations of liability for loss and damage; and (4) disclosure of any relationships involving common stock, common ownership, common management, or common familial relationships between filing carriers and any other motor carriers, freight forwarders, or property brokers of HHG within 3 years of the proposed date of registration.</P>
                    <P>The FMCSA also proposes the following improvements to Form MCSA-1 and the instructions:</P>
                    <P>• Elimination of a requirement for U.S.- and Canada-domiciled motor carriers to submit a “description of a retraining and educational program for poorly performing drivers.” The form will continue to require a certification that a motor carrier has in place “a system and procedures for ensuring the continued qualification of drivers to operate safely, including a safety record for each driver, procedures for verification of proper age and licensing of each driver, and procedures for identifying drivers who are not complying with the safety regulations.” The revised certification removes a requirement not contained in the FMCSRs and is less burdensome.</P>
                    <P>• The Agency previously proposed a vehicle certification which read: “My vehicles were manufactured or have been retrofitted in compliance with the applicable USDOT Federal Motor Vehicle Safety Standards.” The SNPRM revises the proposed certification to read “The carrier will ensure, once operations in the United States have begun, that all vehicles it operates in the United States were manufactured or have been retrofitted in compliance with the applicable USDOT Federal Motor Vehicle Safety Standards or Canadian Motor Vehicle Safety Standards in effect at the time of manufacture.” The Agency believes the new language clarifies the carrier's responsibility to ensure that no vehicle may be operated in the United States unless it complies with the applicable vehicle safety standards.</P>
                    <P>• The Agency proposes revisions to Form MCSA-1 to collect information regarding ADA compliance. Although the Over-the-Road Bus Accessibility Act of 2007 [Pub. L. 110-291, 122 Stat. 2915, July 30, 2008] requires FMCSA to consider compliance with DOT's ADA regulations at 49 CFR part 37, subpart A, as an element of an over-the-road bus company's fitness for receiving new operating authority, it does not require the inclusion of detailed ADA compliance information in the application form. Nonetheless, to assist in ensuring ADA compliance, FMCSA will take the following actions:</P>
                    <P>○ Ask the following questions regarding ADA compliance during the new entrant safety audit—</P>
                    <P>• Does the carrier have the means to provide accessible over-the-road bus (OTRB) service on a 48-hour advance notice basis by its owned or leased OTRBs?</P>
                    <P>• If the carrier does not have the means then does the carrier have an arrangement with another carrier that operates accessible OTRBs?</P>
                    <P>○ If noncompliance with DOT's ADA regulations is discovered in the course of a new entrant safety audit or compliance review, FMCSA will either forward the information to the U.S. Department of Justice (DOJ) for appropriate action or conduct its own investigation and attempt to resolve the violations, in accordance with a February 2009 Memorandum of Understanding between DOJ and DOT executed pursuant to Public Law 110-291. (A copy of the Memorandum of Understanding has been placed in the docket for this rulemaking).</P>
                    <P>
                        ○ Refer any non-compliant motor carrier that is also a recipient of DOT financial assistance to FTA for administrative enforcement action, as appropriate. FTA administers a program that provides financial assistance to some over-the-road bus carriers and, consistent with section 504 of the Rehabilitation Act of 1973 (29 U.S.C. 794), as amended, and DOT rules implementing it (49 CFR part 27), cannot provide such assistance to carriers who are out of compliance with their ADA obligations.
                        <PRTPAGE P="66519"/>
                    </P>
                    <P>○ When appropriate, initiate action to amend, suspend, or revoke a carrier's registration based on willful noncompliance with DOT's ADA regulations</P>
                    <P>FMCSA proposes conforming amendments to align 49 CFR 365.105 with certain information on Form MCSA-1. In proposed § 365.105, the Agency replaces references to obsolete OP series forms with “Form MCSA-1” and reduces the number of operational categories from six to three so it is clear that the fee for operating authority applies only to the general categories of motor carrier, broker and freight forwarder and not to each individual subgroup of these categories listed in Section A, question 17 of  Form MCSA-1. (see Instructions for Form MCSA-1, item number 50)</P>
                    <P>In proposed § 365.107, the Agency replaces references to OP series forms with “Form MCSA-1.” Also, the Agency proposes to remove obsolete references to common and contract carriage as required by 49 U.S.C. 13902(f), as amended by section 4303(c) of SAFETEA-LU.</P>
                    <HD SOURCE="HD3">9. Adoption of an Exclusively Online Electronic Registration System</HD>
                    <P>Several commenters filed comments about the effect of a mandatory online filing requirement, including a possible phase-in period for mandatory online filing. ATA supported the emphasis on online filing and said it should be made mandatory with a 2 to 3 year phase-in period. NCSTS stated that a minimum 5-year phase-in period is needed before electronic filing becomes mandatory and suggested that FMCSA maintain an alternative system to allow paper filings during systems failures and computer outages. The Property Casualty Insurers Association of America (PCIAA) also favored phased-in mandatory electronic filing.</P>
                    <P>The Petroleum Marketers Association of America (PMAA), the American Insurance Association (AIA), and OOIDA opposed mandatory electronic filing. PMAA stated that some of its members would be unable to access the Internet and urged the Agency to keep the paper filing option available. OOIDA asserted electronic filing is a hardship for some parties, opposed mandatory electronic filing and stated a 5-year phase-in period is absolutely necessary in the event mandatory electronic filing is adopted. OOIDA also stated that FMCSA should provide an alternative back-up system to online filing.</P>
                    <P>The Agency believes mandatory electronic filing is feasible and would result in substantial cost savings to both filers and FMCSA. Currently, an estimated 88 percent of motor carriers in the United States have Internet access, and this number is steadily growing. Furthermore, the Internet is publicly accessible via libraries and other public facilities. Electronic filing is cost effective and would incorporate automated error checking, reduce processing time, and facilitate faster issuance of USDOT Numbers. A detailed cost/benefit analysis performed by the Agency supporting this position, titled “Report on Benefits and Costs of Mandatory Electronic Filing of FMCSA's Unified Registration System,” is included as Appendix A to the regulatory evaluation. The conclusions of this analysis are reported in the URS SNPRM under Section IV, titled “Regulatory Evaluation of the URS SNPRM: Summary of Benefits and Costs.”</P>
                    <P>Based on the year-to-year increases in the percentage of electronic filings for the Agency's MCMIS data, the Agency estimated that, even in the absence of a mandatory electronic filing requirement, the percentage of electronic filers would range between 80 and 90 percent. The FMCSA developed projections of the numbers of new registrants expected to enter the industry from 2014 to 2023 and assessed the costs of electronic filing both for new registrants and for existing firms that file biennial updates.</P>
                    <P>Mandatory electronic filing would only impose a cost on firms that would otherwise have filed by paper due to a lack of computer skills and/or Internet access. The results of FMCSA's analysis showed that costs to these affected firms would be low, ranging from $12.73 to $80.00 for new registrants and from $3.14 to $51.53 for firms with recent activity filing biennial updates. The low end of these cost ranges are for firms that file their registrations at a public library, and the high end is for firms that would hire another entity to complete the forms on their behalf. The FMCSA also prepared estimates of the benefits of mandatory electronic filing, consisting of estimates of the value of time saved by carriers and the value of substantially more rapid receipt of operating authority, as well as benefits to FMCSA from electronic filing. A comparison of the costs and benefits indicated that mandatory electronic filing would result in anticipated benefits of more than $38 million.</P>
                    <P>The FMCSA confirmed that the Small Business Administration (SBA) would not consider a totally electronic registration system to be a barrier to entry for small businesses, if the cost-benefit analysis supported the proposal. Based on its analysis, FMCSA proposes a mandatory electronic registration system. The system would incorporate electronic signature technology for required signatures. Supplemental documentation required for registration would be accepted electronically as well. The system would include the capability to upload scanned or electronic versions of this information.</P>
                    <P>The Agency does not propose a phase-in period because it anticipates that most entities should have online access when the URS rule becomes effective. The Agency would provide adequate time to adjust to the electronic filing requirement when setting the compliance date for the final rule, and would adopt procedures to ensure continued operational capability in case of system failure.</P>
                    <HD SOURCE="HD3">10. Transfers of Operating Authority</HD>
                    <P>
                        This SNPRM withdraws the proposal that entities, when submitting a revised Form MCSA-1 due to a change of name, form of business, or address, must also submit a certification that there has been no change in the ownership, management, or control of the entity. While the Agency has determined that the ICCTA removed its statutory authority to review transfers of operating authority, the ICCTA did not prohibit such transfers. Therefore, FMCSA also would eliminate 49 CFR part 365, subpart D, governing transfers of operating authority. A motor carrier would be required, however, to identify any current management official (
                        <E T="03">e.g.</E>
                         Owner, President, Vice President, Safety Director, 
                        <E T="03">etc.</E>
                        ) responsible for motor carrier safety in its operation who was hired after the last update when completing the Form MCSA-1 biennial registration update. A motor carrier that changes its name, form of business, or address would retain its existing USDOT Number.
                    </P>
                    <P>
                        Regarding the comments about the practice of “churning” (motor carriers `reincarnating' by registering for a new USDOT Number in an attempt to conceal a negative safety history), the Agency believes that existing regulations, the proposals contained in this SNPRM and the requirements in 49 CFR part 385, together with procedures adopted and recently implemented by the Agency for review of motor carrier applications for operating authority, will discourage this practice. In this SNPRM, the Agency also proposes to require information on motor carrier ownership on the Form MCSA-1 to be filed with the Agency prior to receipt of a new USDOT Number. This information would assist the Agency in identifying individuals involved in churning and rejecting their applications for new registration when 
                        <PRTPAGE P="66520"/>
                        appropriate. The Agency also believes that the requirement under 49 CFR part 385 for all new entrants (carriers receiving a new USDOT Number) to undergo a safety audit within 18 months of beginning operation will deter carriers from engaging in this practice.
                    </P>
                    <P>In addition, motor carriers required to obtain operating authority pursuant to 49 CFR parts 390 and 365 may be subject to FMCSA review procedures established under 49 CFR 365.109. Currently, FMCSA utilizes these procedures for review of applications for household goods motor carrier, broker, freight forwarder or passenger carrier authority. However, in the future the Agency anticipates expanding the program to include applications from all motor carriers that require operating authority. Employing procedures established under § 365.109, the Agency reviews applications for completeness and for conformity with the safety fitness standard. Through this process, if the Agency determines that a carrier is not fit, willing and able to comply with applicable statutes and regulations, the motor carrier's application for operating authority will be rejected. In the event an application is rejected, an appeal may be filed with the Agency pursuant to 49 CFR 365.111. In this SNPRM the Agency proposes revising 49 CFR 365.111 and 365.203 to provide the address and appropriate office for appeals of rejections and for protests.</P>
                    <HD SOURCE="HD3">11. Cancellation, Reinstatement, and Deactivation of USDOT Registration</HD>
                    <P>In the NPRM, the Agency proposed that a motor carrier seeking to reinstate its USDOT Registration more than 2 years after its registration was deactivated would be classified as a new entrant. In setting the proposed threshold for reclassification of a carrier as a new entrant at 2 years, the Agency sought to prevent carriers that go in and out of business for very short periods of time from being required to re-enter the New Entrant Safety Assurance Program.</P>
                    <P>The OOIDA disagreed with the Agency's statement that a carrier that has been inactive for more than 2 years is functionally equivalent to a new entrant. OOIDA explained that many motor carriers, including owner-operators, may operate under another carrier's authority for a period of time for economic reasons. In these cases, OOIDA believes the Agency is not justified in proposing to require the carrier to pay a new registration fee and to undergo a new safety audit as a condition for activating registration.</P>
                    <P>Advocates supported the proposal that carriers that have been inactive for more than 2 years be treated as new entrants and be required to successfully complete the New Entrant Safety Assurance Program.</P>
                    <P>Consistent with the new regulatory drafting strategy for the SNPRM, the Agency is not proposing to make changes to its New Entrant Safety Assurance Program. While the New Entrant Safety Assurance Program is triggered by the registration process, it is a separate program whose governing regulations are codified under 49 CFR parts 365 and 385. This SNPRM addresses cancellation, reinstatement and deactivation of USDOT Registration/operating authority only from the standpoint of fees and other administrative requirements. The Agency recently published revisions to its New Entrant Safety Assurance Program, including regulations governing reinstatement. (“New Entrant Safety Assurance Process; Final Rule,” published on December 16, 2008 at 73 FR 76472).</P>
                    <HD SOURCE="HD3">12. Additional Proposals Regarding Special Transit Operations (Federal Transit Administration (FTA) Grantees)</HD>
                    <P>The non-profit organization CTAA, which represents public and community-based FTA grantees, generally supported the provisions of the NPRM applicable to FTA grantees. However, CTAA suggested that the Agency revise the rule to: (1) Clarify that the requirements would apply to motor carriers of passengers that participate in interlining or through-ticketing arrangements with one or more interstate for-hire motor carriers of passengers; (2) designate an Agency point of contact to assist FTA grantees in completing their applications; and (3) amend proposed Form MCSA-1 to include specific information applicable to FTA grantees, including governmental status, transit areas, certification of compliance with FTA (not FMCSA) drug and alcohol testing regulations, and a statement that FTA grantees need not pay a filing fee. CTAA urged FMCSA to permit risk retention groups and other forms of pooled insurance as ways to satisfy the Agency's financial responsibility requirements. Finally, CTAA stated that the regulations should take into account the effect on FTA programs of the last two comprehensive reauthorization statutes.</P>
                    <P>Greyhound and ABA supported clarifying the status of transit providers that operate entirely within one State but participate in interline relationships with interstate carriers. They agreed that FMCSA should explicitly state that such transit providers are not subject to the FMCSA insurance requirements but rather must meet the insurance requirements of the States in which they operate.</P>
                    <P>The Rhode Island Public Transit Authority (RIPTA) asserted that the NPRM offered little relief from what it considers a burdensome and confusing system of compliance with FMCSA, the Federal Highway Administration (FHWA), and FTA requirements. The Ohio Department of Transportation (ODOT) said the Agency must: (1) Clearly define the difference between a “for-hire” CMV and a public FTA-funded transit vehicle that travels across State lines beyond a contiguous jurisdiction; (2) address the type of public transportation system that is operated by a designated grantee (whether government or private non-profit); (3) exempt vehicles transporting between 9 and 15 passengers and originating and terminating in the same State but traveling through an adjacent State for operational convenience; and (4) permit financial responsibility requirements to be satisfied through participation in shared risk programs, such as Ohio's County Risk Sharing Authority.</P>
                    <P>The OOIDA opposed relieving FTA grantees of the requirement to pay filing fees, contending the NPRM provides no rationale for relieving what are essentially private companies with a government contract of their fair share of the cost of the registration program.</P>
                    <P>
                        In response to these comments, FMCSA proposes under §§ 390.101(b) and 387.33(b) to clarify the specific URS registration and financial responsibility obligations for FTA grantees. Although all FTA grantees would be required to register with FMCSA and would receive a fee waiver, their financial responsibility requirements could differ, depending on the FTA program under which the grantee receives funding. The proposed minimum financial responsibility requirement for a grantee that provides transportation within a transit service area located in more than one State under an agreement with a Federal, State, or local government funded, in whole or in part, with a grant under 49 U.S.C. 5307, 5310 or 5311 is the highest level of financial responsibility required for any of the States in which it operates. An FTA grantee that receives funding under other grant programs (section 5316 and 5317 grantees) would be subject to the general financial responsibility requirements applicable to for-hire passenger carriers that do not receive FTA funding. The different financial responsibility requirements are due to the fact that 49 U.S.C. 31138(e)(4) expressly exempts section 5307, 5310 
                        <PRTPAGE P="66521"/>
                        and 5311 grantees from the Federal general financial responsibility requirements and instead subjects them to applicable State requirements. The exemption does not cover section 5316 and section 5317 grantees; neither the Transportation Equity Act for the 21st Century (TEA-21) [Pub. L. 105-78, 112 Stat. 107, June 9, 1988] nor SAFETEA-LU amended 49 U.S.C. 31138 to expressly exclude them from the Federal financial responsibility requirements.
                    </P>
                    <P>The Agency proposes to incorporate all but one of CTAA's recommended changes to Form MCSA-1. The FMCSA could not add a cross reference to existing FTA drug and alcohol regulations to the Drug and Alcohol Safety Certification because the Drug and Alcohol Safety Certifications under Section L of Form MCSA-1 apply only to Mexico- or non-North America-domiciled motor carrier applicants—entities that are ineligible to receive FTA grants. (See Section L, question 47, III, 1 on proposed Form MCSA-1).</P>
                    <P>With respect to ODOT's suggestion to differentiate between for-hire motor carriers and public transit vehicles, and to exempt certain types of vehicles and transportation from the URS requirements, the Agency notes that public transit vehicles are a subset of for-hire CMVs. Accordingly, the Agency declines to distinguish between for-hire motor carriers and public transit vehicles for purposes of registration under proposed part 390, subpart C. Moreover, the Agency is not authorized to grant ODOT's request to exempt from registration requirements those vehicles transporting between 9 and 15 passengers and originating and terminating in the same State but traveling through an adjacent State for operational convenience. The Agency recognizes the limited exemption from the Federal minimum financial responsibility requirements set forth in proposed § 387.33(b) granted to certain public transit operators, pursuant to 49 U.S.C. 31138(e)(4). However, the exemption from the minimum financial responsibility requirements does not include those operators providing service in more than one State from having to file proof of financial responsibility pursuant to the minimum levels set by State law.</P>
                    <P>The CTAA and ODOT additionally requested that the Agency allow transit operators to satisfy financial responsibility requirements through shared risk programs. CTAA characterizes such shared risk programs as “risk retention groups and other forms of `pooled' insurance * * * .” In responding to these comments, the Agency must first distinguish between risk retention groups and risk pools.</P>
                    <P>Risk retention groups (RRGs) are established under the Liability Risk Retention Act of 1981 [Pub. L. 97-45, 95 Stat. 949, September 25, 1981] and are defined at 15 U.S.C. 3901(a)(4). According to a 1987 ICC Policy Statement, which authorized the Commission to accept certificates of insurance from RRGs, those entities are required by Congress to:</P>
                    <P>(1) Be chartered or licensed under the laws of a State as a liability insurance company and authorized by such State's laws to engage in the business of insurance;</P>
                    <P>(2) [Not] exclude any person from membership solely for the purpose of providing existing members of such group a competitive advantage over the excluded person;</P>
                    <P>(3) Have as its owners only persons who comprise the membership of the Risk Retention Group and who are provided insurance by the group, or has as its sole owner an organization which has as its members only persons who are members of the Risk Retention Group; and</P>
                    <P>
                        (4) Be formed by persons who are engaged in businesses or activities similar or related as to the liability to which they are exposed by virtue of related, similar or common business, 
                        <E T="03">etc.</E>
                    </P>
                    <P>
                        <E T="03">Implementation of Liability Risk Retention Act of 1986,</E>
                         Ex Parte No. MC-178 (Sub-No. 4), 1987 WL 98199, at *1 (decided Mar. 31, 1987) (“ICC Policy Statement”). The ICC Policy Statement indicated that RRGs “are unquestionably insurance companies, and can meet the criteria prescribed for insurance * * * companies in 49 CFR 1043.8 * * *.” 
                        <E T="03">Id.</E>
                         at *2. Former § 1043.8 is the predecessor to current 49 CFR 387.315. The FMCSA continues to accept RRG filings.
                    </P>
                    <P>Insurance risk pools are typically private associations operated on a statewide basis for the benefit of their members. The main distinction between risk pools and RRGs is that risk pools do not meet the statutory requirements established for RRGs under the Liability Risk Retention Act of 1981. The public transit risk pools allow the State and municipal transit operators to achieve economies of scale in purchasing insurance resulting in lower premiums and other benefits to the limited membership. Transit risk pools are generally approved by the State and supported by the State Departments of Transportation.</P>
                    <P>Unlike RRGs, State and local government risk pools generally have not been approved by FMCSA as an acceptable form of insurance pursuant to the section 13906 requirement that the Secretary “register a motor carrier under section 13902 only if the registrant files with the Secretary a bond, insurance policy or other type of security approved by the Secretary * * *.” The Agency's position has been that risk pools do not qualify as a bond or insurance policy, and that a motor carrier may meet the financial responsibility requirements through self-insurance only if the insured applies for approval under the Agency's self-insurance program.</P>
                    <P>This issue is complicated by section 31138(e)(4), which exempts transit operators receiving Federal grants under 49 U.S.C. 5307, 5310, or 5311 from both the amounts and type of financial responsibility that must be provided as evidence of compliance with the financial responsibility requirement. Section 31138(e)(4) further provides, however, that where the transit service area is in more than one State, the minimum level of financial responsibility shall be the highest level required for any of such States. This requirement has been incorporated into proposed § 387.33(b). The above notwithstanding, these exempted transit services operators still are subject to registration under 49 U.S.C. 13902(b)(2) and are required to register and provide proof of insurance pursuant to proposed § 365.109.</P>
                    <P>Pursuant to 49 U.S.C. 13906(a)(1), the “Secretary may register a motor carrier under section 13902 only if the registrant files with the Secretary a bond, insurance policy, or other type of security approved by the Secretary, in an amount not less than such amount as the Secretary prescribes pursuant to, or as is required by, sections 31138 and 31139, and the laws of the State or States in which the registrant is operating, to the extent applicable.” Section 387.301 currently permits motor carriers to satisfy their financial responsibility requirements by filing proof of such “other securities” as the Secretary approves.</P>
                    <P>
                        This proposed rule expressly addresses registration and insurance requirements for certain types of transit operators. It is therefore appropriate to resolve confusion that has arisen in this area. The Agency recognizes that allowing these transit operators to utilize State-approved risk pools would expand the types of security approved by the Secretary for certain transit service operators and harmonize the provisions of sections 31138(e)(4) and 13906(a)(1) by recognizing the State's approved form of financial responsibility for these operators. As a 
                        <PRTPAGE P="66522"/>
                        result, the Agency intends to publish a separate 
                        <E T="04">Federal Register</E>
                         notice that will describe the Agency's proposed change in policy to allow transit service providers that fall under the provisions of proposed § 387.33 to utilize State-approved risk pools in order to meet the State financial responsibility requirements pursuant to section 31138(e)(4) and proposed § 387.33.
                    </P>
                    <HD SOURCE="HD3">13. Temporary Operating Authority</HD>
                    <P>Former 49 U.S.C. 10928(b) allowed the ICC, which was sunsetted in 1995, to issue temporary authority to provide transportation to a place or in an area having no motor carrier capable of meeting the immediate needs of the place or area. Former section 10928(c) permitted the ICC to issue emergency temporary authority if, due to emergency conditions, there was insufficient time to process an application for temporary authority.</P>
                    <P>
                        Temporary authority was originally made available because it took several months for the former ICC to process applications for permanent operating authority, particularly if competing carriers protested the application. Following changes in statutory standards which led to greatly reduced application processing time, the ICC limited the issuance of temporary authority to “exceptional circumstances (
                        <E T="03">i.e.,</E>
                         natural disasters or national emergencies) when evidence of immediate service need can be specifically documented * * *.” [See existing 49 CFR 365.107(g)]. FHWA (and later FMCSA) retained this provision when the ICC operating authority regulations were transferred to USDOT in 1996.
                    </P>
                    <P>The ICCTA repealed 49 U.S.C. 10928(b) and (c) and did not enact any comparable provisions expressly authorizing the issuance of temporary authority. However, the ICCTA does not prohibit the issuance of temporary authority and 49 U.S.C. 13905(c) provides that any registration issued to motor carriers, freight forwarders, and property brokers under chapter 139 shall remain in effect for such period as the Secretary determines appropriate by regulation. Therefore, there is general statutory authority to continue issuing temporary authority. However, the NPRM did not include a provision permitting motor carriers to obtain temporary registration or operating authority.</P>
                    <P>Greyhound requested that the Agency grant temporary operating authority to prevent service disruptions which may occur as a result of Greyhound's restructuring its nationwide service. Greyhound believes replacement companies will not be able to obtain operating authority before it abandons certain routes. Greyhound claimed it provides at least 30 days notice before it discontinues a route and cannot provide more notification time “if the restructuring is to be implemented in a timely manner.” Greyhound proposed the Agency adopt a process by which emergency temporary authority would become effective immediately upon the filing of a temporary authority application and proof of insurance and would remain in effect until FMCSA processed the permanent application, perhaps 90 days. ABA also supported the Greyhound proposal.</P>
                    <P>The FMCSA believes that continued issuance of temporary operating authority as limited under § 365.107(g) is warranted. During the Hurricane Katrina relief effort in 2005, FMCSA received numerous applications for emergency temporary authority pursuant to § 365.107(g) and the Agency believes that having a procedure for the issuance of temporary operating authority will enhance future emergency relief efforts. However, except in extraordinary circumstances such as natural disasters, the Agency does not anticipate many requests for such applications. We believe Greyhound overstates the time it takes FMCSA to currently process applications for operating authority and its comments do not provide a convincing rationale for extending the current requirements to prospective “emergencies” caused by manageable business decisions. Under proposed § 365.107(e), FMCSA would grant temporary operating authority only in cases of national emergency or natural disaster and following an emergency declaration under 49 CFR 390.23. Entities granted temporary operating authority would need to file evidence of financial responsibility with the Agency.</P>
                    <HD SOURCE="HD3">14. NTSB Recommendation Impacting Cargo Tank Applications and Updates</HD>
                    <P>After investigating a 2009 incident involving the rollover of a truck-tractor and cargo tank semitrailer and the resulting fire, the National Transportation Safety Board (NTSB) made 20 draft recommendations to four DOT modal administrations, including FMCSA, and the American Association of State Highway and Transportation Officials. As part of a recommended rollover prevention program, NTSB recommended that FMCSA revise the MCS-150 form to require hazardous materials carriers to report the number and types of U.S. Department of Transportation specification cargo tanks owned or leased by the carriers and provide other pertinent data displayed on the specification plates of such tanks. NTSB recommended that FMCSA require this information to be updated annually. As FMCSA proposes to replace the MCS-150 form with the new MCSA-1 form through this rulemaking, the Agency believes it would be appropriate to solicit information from the public regarding:</P>
                    <P>(1) Whether the MCSA-1 form should be revised to incorporate the NTSB recommendation;</P>
                    <P>(2) Whether the collection of additional information regarding cargo tanks would prove useful in connection with a rollover prevention program;</P>
                    <P>(3) Whether cargo tank carriers should be required to submit updated data more frequently than biennially. If so, what event should trigger the update requirement;</P>
                    <P>(4) What would be the burden associated with collecting additional cargo tank information biennially or more frequently;</P>
                    <P>(5) Whether there are alternatives for collecting this information; and</P>
                    <P>(6) Whether this information is already being collected by other entities, such as State Departments of Motor Vehicles.</P>
                    <HD SOURCE="HD1">IV. Regulatory Evaluation of the URS SNPRM: Summary of Benefits and Costs</HD>
                    <HD SOURCE="HD2">A. Summary</HD>
                    <P>
                        The FMCSA has revised its 2005 NPRM in response to congressional mandates included in SAFETEA-LU and in response to comments to the May 2005 NPRM. In this section of the SNPRM, FMCSA summarizes its calculation of the costs and benefits associated with the changes included in this proposed rulemaking. Although many of the revisions proposed under URS would result in changes to existing fees paid by motor carriers (creation of new fees or elimination of existing fees), these changes would result in a shifting of fees from one group to another and would not result in a net gain (benefit) or loss (cost) from a societal perspective. For example, if FMCSA were to eliminate a fee previously paid by motor carriers, that group would receive a benefit. However, the benefit would be offset by an equal cost to the Agency in the form of lost revenues. The FMCSA classified the costs and benefits calculated in the regulatory evaluation as either changes in fees, resource costs, or benefits. Changes in fees are neutral from a societal perspective, but changes in resource costs and benefits result in either a cost or a benefit to society. The 
                        <PRTPAGE P="66523"/>
                        FMCSA estimated the costs and benefits associated with implementing the following proposed major URS SNPRM provisions:
                    </P>
                    <P>
                        • A new requirement for private and exempt for-hire motor carriers, cargo tank facilities, and intermodal equipment providers (IEPs) to pay FMCSA registration fees; 
                        <SU>11</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             Throughout this section, cargo tank facilities and IEPs are referred to as “other entities.”
                        </P>
                    </FTNT>
                    <P>• A new requirement for private carriers and exempt for-hire motor carriers to file proof of process agent designations with FMCSA;</P>
                    <P>• A new requirement for private HM and exempt for-hire motor carriers to file proof of liability insurance with FMCSA;</P>
                    <P>• A reduction of the current reinstatement fee for non-exempt for-hire motor carriers, brokers and freight forwarders and new reinstatement fees for exempt for-hire and private hazmat motor carriers;</P>
                    <P>• Elimination of operating authority transfers and filing fees for name changes;</P>
                    <P>• Introduction of new Form MCSA-1 filing requirements; and</P>
                    <P>• Mandatory electronic filing of Form MCSA-1.</P>
                    <P>Table 1 presents the total costs associated with the URS SNPRM. The URS proposal results in an anticipated resource cost to industry of $26,342,699 and a resource cost to FMCSA of $135,158 over the 10-year analysis period (2014-2023). The total societal cost of the SNPRM is thus $26.5 million ($26,342,699 + 135,158). The industry also would experience an increase in fees of $65.3 million, and the Agency would experience a decrease in fee revenues of $6.7 million.</P>
                    <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,12,12,12,12">
                        <TTITLE>Table 1—Total Costs of URS Proposed Rule</TTITLE>
                        <BOXHD>
                            <CHED H="1">URS Rule provision</CHED>
                            <CHED H="1">Resource costs</CHED>
                            <CHED H="2">Industry</CHED>
                            <CHED H="2">Agency</CHED>
                            <CHED H="1">Fees paid/lost</CHED>
                            <CHED H="2">Industry</CHED>
                            <CHED H="2">Agency</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Mandatory Electronic Filing</ENT>
                            <ENT>$538,894</ENT>
                            <ENT>$0</ENT>
                            <ENT>$0</ENT>
                            <ENT>$0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Eliminating Transfer/Name Change Requirements</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>1,854,890</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">New Registrant Fee</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>63,583,722</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Insurance Filing</ENT>
                            <ENT>676,723</ENT>
                            <ENT>0</ENT>
                            <ENT>1,691,808</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Process Agent Filing</ENT>
                            <ENT>25,067,012</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Cancellations and Reinstatements</ENT>
                            <ENT>60,070</ENT>
                            <ENT>135,158</ENT>
                            <ENT>0</ENT>
                            <ENT>4,808,126</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">New MCSA-1 Application Form</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total Costs</ENT>
                            <ENT>26,342,699</ENT>
                            <ENT>135,158</ENT>
                            <ENT>65,275,530</ENT>
                            <ENT>6,663,017</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Numbers may not add due to rounding.
                        </TNOTE>
                    </GPOTABLE>
                    <P>Table 2 presents the total benefits of the URS rule for each provision. For the industry, total benefits amount to $3.3 million and fee savings amount to $6.7 million. For the Agency, total benefits amount to $42.7 million and $65.3 million in fees received. This proposal would improve the ability of FMCSA safety investigators to locate small and medium-sized private and exempt for-hire motor carriers for enforcement action because investigators would be able to work with the newly-designated process agents to locate hard-to-find motor carriers. The Agency believes that a more efficient Compliance, Safety, Accountability (CSA) program would lead to increased safety benefits. However, to present a conservative estimate of the benefits of the URS rule, we only estimate the benefit of time saved by the Agency due to a more efficient CSA program.</P>
                    <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,12,12,12,12">
                        <TTITLE>Table 2—Total Benefits of URS Rule</TTITLE>
                        <TDESC>[10-year present value]</TDESC>
                        <BOXHD>
                            <CHED H="1">URS rule provision</CHED>
                            <CHED H="1">Benefits</CHED>
                            <CHED H="2">Industry</CHED>
                            <CHED H="2">Agency</CHED>
                            <CHED H="1">Fees received/saved</CHED>
                            <CHED H="2">Industry</CHED>
                            <CHED H="2">Agency</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Mandatory Electronic Filing</ENT>
                            <ENT>1,964,186</ENT>
                            <ENT>36,190,320</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Eliminating Transfer/Name Change Requirements</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>1,854,890</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">New Registrant Fee</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>63,583,722</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Insurance Filing</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>1,691,808</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Process Agent Filing</ENT>
                            <ENT>0</ENT>
                            <ENT>3,130,736</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Cancellations and Reinstatements</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>4,808,126</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">New MCSA-1 Application Form</ENT>
                            <ENT>1,354,631</ENT>
                            <ENT>3,391,089</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total Benefits</ENT>
                            <ENT>3,318,817</ENT>
                            <ENT>42,712,146</ENT>
                            <ENT>6,663,017</ENT>
                            <ENT>65,275,530</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Numbers may not add due to rounding.
                        </TNOTE>
                    </GPOTABLE>
                    <P>
                        The FMCSA calculated the net societal benefits of the proposed rule by subtracting the total (industry and Agency) 10-year costs from the total 10-year benefits for each provision. The cost to industry associated with fee changes is offset by an equal gain to FMCSA due to increased revenues from fees. Table 3 presents the net benefits of the proposed rule. Net benefits are estimated to be −$23.0 million for the industry and $42.6 million for FMCSA. This results in total societal net benefits of the URS SNPRM of $19.6 million. The industry would experience a total increase in fees of −$58.6 million (including total fees paid and fees saved). This increase in fees to the 
                        <PRTPAGE P="66524"/>
                        industry is offset by a total $58.6 million increase in fees received by FMCSA (including fees lost and fees received). FMCSA believes the fees and costs of the URS rule would not lead to a reduction in competitiveness.
                    </P>
                    <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,12,12,12,12">
                        <TTITLE>Table 3—Net Benefits of URS Proposed Rule</TTITLE>
                        <TDESC>[10-year present value]</TDESC>
                        <BOXHD>
                            <CHED H="1">URS rule provision</CHED>
                            <CHED H="1">Net benefits</CHED>
                            <CHED H="2">Industry</CHED>
                            <CHED H="2">Agency</CHED>
                            <CHED H="1">Net fees</CHED>
                            <CHED H="2">Industry</CHED>
                            <CHED H="2">Agency</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Mandatory Electronic Filing</ENT>
                            <ENT>$1,425,292</ENT>
                            <ENT>$36,190,320</ENT>
                            <ENT>$0</ENT>
                            <ENT>$0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Eliminating Transfer/Name Change Requirements</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>1,854,890</ENT>
                            <ENT>−1,854,890</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">New Registrant Fee</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>−63,583,722</ENT>
                            <ENT>63,583,722</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Insurance Filing</ENT>
                            <ENT>−676,723</ENT>
                            <ENT>0</ENT>
                            <ENT>−1,691,808</ENT>
                            <ENT>1,691,808</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Process Agent Filing</ENT>
                            <ENT>−25,067,012</ENT>
                            <ENT>3,130,736</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Cancellations and Reinstatements</ENT>
                            <ENT>−60,070</ENT>
                            <ENT>−135,158</ENT>
                            <ENT>4,808,126</ENT>
                            <ENT>−4,808,126</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">New MCSA-1 Application Form</ENT>
                            <ENT>1,354,631</ENT>
                            <ENT>3,391,089</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">Net Benefits</ENT>
                            <ENT>−23,023,883</ENT>
                            <ENT>42,576,988</ENT>
                            <ENT>−58,612,513</ENT>
                            <ENT>−58,612,513</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Societal Net Benefits</ENT>
                            <ENT A="01">19,553,105</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Numbers may not add due to rounding.
                        </TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD2">B. Calculation of Costs and Benefits</HD>
                    <P>This section summarizes the calculation of the costs and benefits for each URS provision. All costs and benefits were calculated over a 10-year period in nominal dollars, restated in real 2010 dollars, and discounted to present value using a rate of seven percent per Office of Management and Budget (OMB) guidelines. A full discussion of the data used, assumptions made, and calculations performed can be found in the regulatory evaluation contained in the public docket for the URS SNPRM.</P>
                    <HD SOURCE="HD3">1. Proposed New Registration Fees Under the URS</HD>
                    <P>Currently, only non-exempt for-hire motor carriers, property brokers, and freight forwarders must pay a one-time registration fee to FMCSA of $300. However, under the URS, FMCSA proposes to require exempt for-hire, private motor carriers and other entities to pay a one-time registration fee as well. Section 4304 of SAFETEA-LU provides that the fee for new registrants shall as nearly as possible cover the costs of processing the registration but shall not exceed $300. The FMCSA determined that it would need to charge all new registrants the maximum allowable fee of $300 because the amount needed to cover the 10-year Agency costs associated with processing the registration filings based on projections of annual new registrants and Agency processing costs exceeds the $300 limit.</P>
                    <P>
                        The FMCSA forecasted $360,122,795 in upgrading and operating costs of the registration system over the 10-year period from 2014 through 2023. This total includes the costs to operate the new motor carrier licensing and insurance system. The total also includes the cost for FMCSA to vet all new registrant for-hire carriers.
                        <SU>12</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             The FMCSA has authority to vet all for-hire carriers, but is currently vetting only for-hire household goods and passenger carriers. During the vetting process, FMCSA reviews the application for completeness and determines if the applicant complies with the statutory and regulatory safety fitness requirements. During this review, FMCSA staff compares the applicant's data with existing carrier data in order to identify noncompliant carriers seeking authority under a different name. If an application is incomplete, FMCSA will contact the applicant to obtain missing information. If FMCSA determines that an applicant is an unsafe carrier or the application is materially incomplete, FMCSA will reject the application. The applicant is provided an opportunity to appeal the rejection and submit additional evidence to support its position that the application should be approved.
                        </P>
                    </FTNT>
                    <P>
                        A portion of these licensing, insurance, and vetting costs will be defrayed by fee revenues other than new registrant registration fees. The FMCSA estimated fees collected for various insurance filings to be $6,943,479 over the 10-year period, and subtracted the 10-year present value of other fee revenues ($6,943,479) from the licensing, insurance, and vetting cost estimate to arrive at $353,179,316 in present value costs that the Agency must recover through the registration fee. The FMCSA divided this cost estimate by its projection of dollars collected per dollar of fee ($486,678)
                        <SU>13</SU>
                        <FTREF/>
                         to arrive at a fee of $725. Per Section 4304 of SAFETEA-LU, FMCSA proposes to charge the maximum registration fee permitted by law, $300 per new registrant. Though a portion of the fees could cover some of the costs of FMCSA review of applications, the $300 fee will not be sufficient to cover all of these review costs.
                    </P>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             This number was calculated by multiplying the number of new registrants in each year by $1, discounting to find the present value, and summing over the 10-year period of the analysis.
                        </P>
                    </FTNT>
                    <P>The cost to industry associated with the change would be $63,583,722 in discounted dollars over the 10-year period (shown in Table 4). This cost to industry would be offset by an equal benefit to the Agency resulting from the revenues generated through the new registration fees.</P>
                    <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,14,14,14,14">
                        <TTITLE>Table 4—Proposed Change in FMCSA Registration Fee to New Registrants by Operation and Classification</TTITLE>
                        <BOXHD>
                            <CHED H="1">Operation classification</CHED>
                            <CHED H="1">
                                Number 
                                <LI>(2014-2023)</LI>
                            </CHED>
                            <CHED H="1">
                                Fee 
                                <LI>change</LI>
                            </CHED>
                            <CHED H="1">
                                Total 
                                <LI>(2010 $)</LI>
                            </CHED>
                            <CHED H="1">
                                Total 
                                <LI>(present value)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Exempt For-Hire Carriers</ENT>
                            <ENT>44,449</ENT>
                            <ENT>300</ENT>
                            <ENT>$13,334,700</ENT>
                            <ENT>$10,083,170</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">Private Carriers and other entities *</ENT>
                            <ENT>235,945</ENT>
                            <ENT>300</ENT>
                            <ENT>70,753,500</ENT>
                            <ENT>53,500,522</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT>280,294</ENT>
                            <ENT/>
                            <ENT>84,088,200</ENT>
                            <ENT>63,583,722</ENT>
                        </ROW>
                        <TNOTE>* Cargo tank facilities and IEPs.</TNOTE>
                    </GPOTABLE>
                    <PRTPAGE P="66525"/>
                    <HD SOURCE="HD3">2. Designation of Process Agents</HD>
                    <P>The FMCSA proposes amending 49 CFR part 366 to require private and exempt for-hire carriers to file process agent designation information with the Agency. Although, per SAFETEA-LU, carriers will not be assessed a fee when filing this information, there is still a cost to industry associated with engaging a process agent. The FMCSA estimated, based on price quotes available from process agents, that the cost to engage a process agent is currently about $35 per carrier. This cost was assumed to cover the minimal filing cost to the process agent. No processing cost was assumed for FMCSA for this electronic filing.</P>
                    <P>The FMCSA calculated $7,199,122 in discounted costs to industry associated with new-registrant private and exempt for-hire carrier process agent filings for 2014 through 2023.</P>
                    <P>The FMCSA assumed that no private and exempt for-hire motor carriers with recent activity have designated process agents. The FMCSA calculated one-time compliance costs for affected carriers with recent activity of $910,546,445 based on its estimate of 253,019 private and exempt for-hire carriers with recent activity in 2014.</P>
                    <P>Finally, FMCSA, based on discussions with the FMCSA Commercial Enforcement Division, estimated that 10 percent of private and exempt for-hire motor carriers with recent activity would change their process agents each year. The FMCSA calculated discounted costs to industry of $7,321,445 associated with re-filing activities over the 10-year analysis period. The FMCSA also calculated the Agency resource cost to process the carrier process agent changes.</P>
                    <P>Non-exempt for-hire motor carriers, brokers and freight forwarders currently must file designations of process agents via a “BOC-3” filing. Under the URS SNPRM, FMCSA proposes to require both private and exempt for-hire carriers to make the same filings.</P>
                    <P>This proposal would improve the ability of FMCSA safety investigators to locate small and medium-sized private and exempt for-hire motor carriers for enforcement action because investigators would be able to work with the newly-designated process agents to locate hard-to-find motor carriers. If the time saved were used by safety investigators to conduct more Compliance, Safety, Accountability (CSA) program interventions, the Agency believes this would lead to increased safety benefits. However, to present a conservative estimate of the benefits of the URS rule, we only estimate the benefit of time saved by the Agency due to a more efficient CSA program.</P>
                    <P>The FMCSA investigators sometimes spend 20 hours or more attempting to locate motor carriers for enforcement action, and in some cases are unable to track down the subject carrier. The FMCSA estimated that the availability of process agent information would save field staff an average of 15 hours in cases involving hard-to-locate carriers.</P>
                    <P>In 2002, States conducted 216 carrier searches per year on average. In 2003, FMCSA Division Offices reported between 10 and 100 cases per State in which field staff had significant trouble locating a motor carrier against whom they wished to take enforcement action, with most Division Offices reporting fewer than 25 such instances.</P>
                    <P>The FMCSA estimated that 15 enforcement cases per State per year (or roughly two thirds of the “difficult” cases) would benefit from dramatically reduced search costs because of the proposed requirement for private and exempt for-hire carriers to designate process agents.</P>
                    <P>The estimates of 15 saved hours per difficult case and 15 difficult cases per year per division result in 225 (15 × 15) annual staff hours saved per State, or 11,250 (225 × 50 States) annual staff hours saved in total. Assuming the Agency would allocate all of the annual saved staff hours to reducing labor costs, FMCSA estimated the value of this annual benefit by multiplying the total annual hours saved (11,250) by the Agency wage rate presented above in Section 2. For example, in 2014, the saved staff hours would benefit the Agency by reducing labor costs by $416,585 (11,250 × $37.03).</P>
                    <P>
                        The FMCSA projected this annual benefit over the 10-year analysis period to arrive at a total benefit of $4.2 million in 2010 dollars. The FMCSA discounted this benefit to present value applying a seven percent discount rate consistent with the other portions of this analysis. The Agency arrived at a total benefit due to reduced labor cost (
                        <E T="03">i.e.,</E>
                         increased efficiency) of $3.1 million over the 10-year analysis period.
                    </P>
                    <P>In total, the regulatory changes requiring exempt for-hire and private carriers to file process agent designations would result in a cost of $25,067,012 to industry and a benefit to the Agency of $3,130,736, and thus a societal net benefit of −$21,936,276. The Agency invites comments on whether the process agent filing process can be made less costly. If there are less costly alternatives, please provide specific recommendations along with supporting data.</P>
                    <HD SOURCE="HD3">3. Financial Responsibility</HD>
                    <P>
                        Under the URS SNPRM, all new registrant exempt for-hire and private HM carriers' insurance representatives would need to file evidence of financial responsibility with FMCSA, and the carriers would be assessed a $10 filing fee.
                        <SU>14</SU>
                        <FTREF/>
                         The FMCSA calculated 10-year fee costs of $460,331 to industry using its estimate of new registrant exempt for-hire and private HM carriers. This $460,331 cost to industry is offset by an equal benefit to the Agency resulting from revenues from the new fees.
                    </P>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             Section 4304 of SAFETEA-LU caps financial responsibility filing fees at $10. The filing fee is paid to FMCSA by the insurance company making the filing on behalf of the carrier and is passed on to the carrier by the insurance company.
                        </P>
                    </FTNT>
                    <P>The $10 fee is a transfer from the industry to the Agency, but the industry will incur resource costs associated with filing. The FMCSA assumed it would take insurance companies a minimal amount of time to file the required proof of insurance for each carrier they insure. Because these filings are handled electronically, FMCSA assigned a cost of only $4 per filing, assuming 10 minutes of time for a clerk. The FMCSA calculated the resource cost to new registrant exempt for-hire and private HM carriers by multiplying its projection of filing costs by its estimate of new registrants over the 10-year period to arrive at a total discounted resource cost to industry of $184,132.</P>
                    <P>The FMCSA would require existing exempt for-hire and private HM carriers to file proof of insurance. Using the Agency's 2008 Motor Carrier Management Information System (MCMIS) data, FMCSA estimated that in 2014 there will be 48,308 exempt for-hire carriers with recent activity and 25,019 private HM carriers with recent activity. The FMCSA calculated a discounted cost to industry of $693,890 associated with the fees. This cost to industry is offset by an equal benefit to the Agency due to the revenues from the fees.</P>
                    <P>The FMCSA calculated the resource cost to carriers with recent activity by multiplying its $4 filing cost estimate by the total exempt for-hire and private HM carriers with recent activity to arrive at a discounted resource cost of $733,270.</P>
                    <P>
                        Currently, all for-hire motor carriers, property brokers, and HHG freight forwarders performing transfer, collection and delivery service must maintain current proof of financial responsibility on file with FMCSA to remain in “active” status. If an insurance company or financial institution notifies FMCSA of cancellation of coverage, carriers, 
                        <PRTPAGE P="66526"/>
                        property brokers, and freight forwarders must file evidence of replacement coverage before the policy, bond or trust fund termination date. Under this proposed rule, exempt for-hire and private HM carriers would be subject to the same requirements. There is a $10 fee associated with filing proof of replacement financial responsibility.
                    </P>
                    <P>Based on 2008 MCMIS data, roughly 8.56 percent of non-exempt for-hire carriers with recent activity filed proof of replacement liability insurance coverage with the Agency. The FMCSA assumed the same portion of the exempt for-hire and private HM carriers would file proof of replacement insurance following a policy cancellation. The FMCSA thus calculated the fees associated with evidence of financial responsibility replacement filings resulting from this proposed change by multiplying the $10 filing fee by 8.56 percent of the exempt for-hire and private HM carriers with recent activity each year. This calculation resulted in a discounted cost to industry over the 10-year analysis period of $498,207. This cost to industry would be offset by an equal benefit to the Agency in the form of new fees received.</P>
                    <P>The FMCSA calculated the resource cost to carriers with recent activity by multiplying its replacement filing cost estimate by 8.56 percent of the population of exempt for-hire and private HM carriers with recent activity. This resulted in a total discounted resource cost to operating carriers over the 10-year analysis period of $199,283. Again, no costs were attributed to the Agency for these filings.</P>
                    <P>Changes in requirements for financial responsibility filings resulted in a total 10-year cost to industry of $1,691,808. This cost to industry due to changes in requirements, however, is offset by an equal benefit to FMCSA for revenues from fees associated with the increased number of filings. Therefore, the societal costs due to changes in fees are zero. These proposed changes resulted in total 10-year resource costs to industry of $676,723.</P>
                    <HD SOURCE="HD3">4. Cancellation and Reinstatement of USDOT Numbers/Operating Authority</HD>
                    <P>As discussed in the previous section, non-exempt for-hire motor carriers, property brokers, and certain HHG freight forwarders must maintain current proof of financial responsibility (liability insurance, bond, or trust fund information) with FMCSA to retain their commercial operating authority. If an insurance company or financial institution notifies FMCSA of cancellation of coverage, carriers, property brokers, and HHG freight forwarders must file evidence of replacement coverage before the policy, bond or trust fund termination date. The operating authorities of entities that do not file the required updates are revoked and these entities must apply for reinstatement of their operating authority by making the necessary filings. The FMCSA proposes to require exempt for-hire and private HM carriers and all freight forwarders providing transfer, collection and delivery service to file and maintain proof of liability insurance as a condition for obtaining and retaining an active USDOT Number. The FMCSA would deactivate the USDOT Number of noncompliant entities, who would be required to reactivate their USDOT registrations and resume operations subject to FMCSA jurisdiction.</P>
                    <P>Under the current system, carriers requesting reinstatement of operating authority must file a written request for reinstatement, pay an $80 fee (on-line by credit card, by phone with a credit card, or by mail with a check) and make the applicable financial responsibility filing. Once the payment is received and applicable filings are made, the FMCSA information system matches up the payment with the filings and automatically issues a reinstatement letter at 5 a.m. on the next business day. Under the proposed system, carriers requesting reinstatement would make the request electronically using Form MCSA-1, pay a $10 fee, and complete applicable filings showing that their insurance is back in effect. The Agency aspect of the reinstatement process would remain the same under the proposed system.</P>
                    <P>The FMCSA discusses these changes below in the following categories: (a) Reinstatement for non-exempt for-hire carriers, brokers and freight forwarders; and</P>
                    <P>(b) Reinstatement for exempt for-hire and private hazmat carriers.</P>
                    <HD SOURCE="HD3">Reinstatement, Non-Exempt For-Hire Carriers, Brokers and Freight Forwarders</HD>
                    <P>Under the current system, non-exempt for-hire carriers, brokers and freight forwarders pay an $80 fee and file a written request for reinstatement. Under the proposed system, these carriers would request reinstatement using Form MCSA-1, pay a $10 fee and make the applicable insurance filing. The FMCSA assumed that the cost of this requirement is minimal, and is approximately equal to that of filing proof of insurance ($4). The Agency determined that it incurs slightly less than $10 per request to process reinstatement requests. The $10 reinstatement fee would be sufficient to defray Agency processing costs. The FMCSA calculated savings by non-exempt for-hire carriers, brokers and freight forwarders applying for reinstatement by multiplying the $70 reduction in fees for these carriers by the number of affected carriers to arrive at a 10-year discounted saving of $4,958,302. This industry benefit would be offset by an equal cost to the Agency due to the loss of revenues from the fees.</P>
                    <HD SOURCE="HD3">Reinstatement, Exempt For-Hire and Private Hazmat Carriers</HD>
                    <P>Under the current system, exempt for-hire and private hazmat carriers do not file insurance-related reinstatements. Under the proposed system, these carriers would pay a $10 fee and file updated information. Using 2008 MCMIS data, FMCSA calculated that 2.58 percent of exempt for-hire and private hazmat carriers would let their insurance coverage lapse and later file reinstatement requests. The Agency determined that it incurs slightly less than $10 per request to process reinstatement requests. The $10 reinstatement fee would be sufficient to defray Agency processing costs. The FMCSA calculated fees associated with this activity by multiplying the $10 fee by the number of affected carriers to arrive at a 10-year discounted cost of $150,176. This industry cost would be offset by an equal benefit to the Agency due to the gain in revenues from the fees.</P>
                    <P>There is a resource cost to industry associated with making these reinstatement requests. As above, FMCSA assumed that the costs associated with completing the applicable filings would equal the costs associated with filing proof of insurance and process agent designations ($4). The FMCSA calculated discounted costs to industry of $60,070 associated with filing activities over the 10-year analysis period.</P>
                    <P>The FMCSA calculated discounted costs to the Agency of $135,158 associated with processing exempt for-hire and private hazmat carrier reinstatements over the 10-year analysis period.</P>
                    <HD SOURCE="HD3">Cumulative Reinstatement Costs and Benefits</HD>
                    <P>
                        Changes in fees for reinstatement of USDOT Numbers and/or commercial operating authority resulted in a total 10-year saving to industry of $4,808,126. This saving to industry, however, is offset by an equal cost to FMCSA in lost revenues from fees associated with reinstatements. The proposed changes 
                        <PRTPAGE P="66527"/>
                        resulted in total 10-year resource costs of $60,070 to industry and $135,158 to FMCSA for a total resource cost to society of $195,229.
                    </P>
                    <HD SOURCE="HD3">5. Transfers and Name Changes</HD>
                    <P>Under the URS, the Agency would no longer require ownership/management/control certification when processing applicant requests for name, address, or form of business changes. Motor carriers will be required to report changes in management when completing their Form MCSA-1 biennial updates, and would retain their existing USDOT Number. No new or replacement USDOT Numbers would be issued. There were 196 requests for transfers of operating authority filed with FMCSA in 2008. Each of the carriers who requested a transfer of operating authority paid a $300 filing fee to FMCSA for this activity. Under the URS SNPRM, FMCSA would not accept or review transfer requests. Based on the 2008 data projected to 2014, FMCSA estimated discounted industry benefits of $509,168 over 10 years from the elimination of the transfer fee. This benefit to industry would be offset by an equal cost to the Agency resulting from the loss of revenues from the transfer request filing fee.</P>
                    <P>The FMCSA proposes to eliminate the $14 filing fee currently assessed to non-exempt for-hire motor carriers and others that change their business names. This action would result in a cost savings to industry and a matching cost to the Agency. In 2008, the Agency processed 11,141 name change requests. Based on the 2008 data, projected to 2014, FMCSA estimated 10-year discounted benefits to industry of $1,345,722 over the 10-year period. This $1,345,722 benefit to industry would be offset by an equal cost to the Agency resulting from the loss of name change filing fee revenues.</P>
                    <P>Elimination of transfer and name change filing fees resulted in a total 10-year cost savings to industry of $509,168. The cost savings to industry due to changes in filing fees, however, would be offset by an equal cost to the Agency resulting from reduced revenues from these filing fees. Therefore, the projected societal costs due to elimination of the fees are zero. These proposed changes resulted in no resource costs to either industry or FMCSA. The total reduction in fees for transfers and name changes is the sum of $509,168 and $1,345,722, or $1,854,890; this sum is a gain to industry and an equal loss to FMCSA.</P>
                    <HD SOURCE="HD3">6. The New Application Form—MCSA-1</HD>
                    <P>The new Form MCSA-1 would replace existing FMCSA registration forms. There would be a time cost savings for those who presently file multiple application forms. New registrant non-exempt for-hire motor carriers currently file an OP-1 series form and the MCS-150 form with FMCSA. Property brokers and freight forwarders file an OP-1 series form only. All other carriers file forms in the MCS-150 series.</P>
                    <P>
                        The FMCSA estimated an average completion time of just over 20 minutes each 
                        <SU>15</SU>
                        <FTREF/>
                         for the MCS-150 series forms and 2 hours for the OP-1 forms. The FMCSA determined that 56.45 percent of new registrants file OP-1 series forms, and 92.45 percent of new registrants file MCS-150 forms. Based on these percentages, FMCSA calculated the current average new registrant filing completion time as just under 1 hour and 26 minutes.
                    </P>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             The MCS-150 form has been estimated to require 20 minutes, and the MCS-150B form a slightly longer 26 minutes. Because only about 2 percent of carriers file the MCS-150B, the average is very close to 20 minutes. There is also an MCS-150C form, but it is much less frequently used.
                        </P>
                    </FTNT>
                    <P>The FMCSA proposes to require all new registrants except a Mexico-domiciled motor carrier requesting to conduct long-haul operations within the United States to file only Form MCSA-1. Based on field testing, FMCSA estimated that it would take those new registrants who would have used the OP-1 form 2 hours and 10 minutes to complete the new form. The FMCSA assumes that the time required for entities who would have used only the MCS-150 or 150B would not change if they used the MCSA-1 form instead. Multiplying 2 hours and 10 minutes by 56.45 percent (the percent of new registrants that file OP-1 series forms), and adding just over 20 minutes times the difference between 92.45 percent (the percent of new registrants that file MCS-150 forms) and 56.45 percent yields just over 1 hour and 20 minutes. Thus, FMCSA estimated a weighted average time savings of almost 6 minutes for each new registrant (that is, just under 1 hour and 26 minutes minus just over 1 hour and 20 minutes).</P>
                    <P>
                        Using its adjusted average hourly wage estimate for drivers 
                        <SU>16</SU>
                        <FTREF/>
                         and its projection of new registrants, FMCSA estimated a 10-year discounted resource cost savings to industry of $1,354,631.
                    </P>
                    <FTNT>
                        <P>
                            <SU>16</SU>
                             
                            <E T="04">Note:</E>
                             This activity may be performed by someone other than a driver. However, FMCSA assumed the person performing the activity would earn a wage similar to that of a driver and used the driver wage rate as the best indicator of cost for this activity.
                        </P>
                    </FTNT>
                    <P>The FMCSA also calculated Agency time saved associated with processing the new MCSA-1 form. Based on the Agency's estimate that, due to reductions in data entry, it would save 20 minutes of processing time from not using the OP-1 series form, and its determination that 56.45 percent of new registrants file the form, FMCSA estimated an 11-minute time savings per applicant. The FMCSA multiplied the adjusted average hourly wage estimate for the Agency by the time saved processing the new MCSA-1 form and the number of annual new registrants to obtain a 10-year discounted resource cost savings of $3,391,089.</P>
                    <P>The proposed changes would result in total 10-year resource cost savings to industry of $1,354,621 and resource cost savings to FMCSA of $3,391,089. The sum of the resource cost savings to industry and FMCSA equals $4,745,720, which is the total benefit to society.</P>
                    <HD SOURCE="HD3">7. Mandatory Electronic Filing of the MCSA-1</HD>
                    <P>
                        By requiring electronic submissions, FMCSA expects to reduce processing costs. Mandating electronic filing would also offer a benefit to most carriers through a reduction of the time required for them to receive registration and/or operating authority.
                        <SU>17</SU>
                        <FTREF/>
                         Electronic submissions have the additional benefit of reducing erroneous data through automated data quality checks and increasing the transparency of the data included in the URS. The Agency believes that the cost savings resulting from reduced labor time and paperwork, and the benefits associated with reducing erroneous data and improving data transparency, would be difficult to achieve without mandating electronic filing. This change, however, could impose a burden on entities that do not have the means to file electronically or that do not wish to file electronically.
                    </P>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             Carriers subject to vetting might experience a more prolonged registration process.
                        </P>
                    </FTNT>
                    <P>
                        To assess this potential burden, and to determine what alternatives would be available to small entities, FMCSA conducted a detailed cost/benefit analysis, “Report on Benefits and Costs of Mandatory Electronic Filing for FMCSA's Unified Registration System”, which is included as Appendix A to the regulatory evaluation. The Agency calculated costs and benefits associated with electronic filing by using estimates of the amount of time required to file the form and the number of expected filers. The present value of the benefits resulting from mandatory electronic 
                        <PRTPAGE P="66528"/>
                        filing is $36,190,320 in benefits to FMCSA and $1,964,186 in benefits to industry. The industry also experiences a resource cost of $538,894. Thus, the net present value of the benefits associated with requiring mandatory electronic filing less the costs results in a total net benefit to society of $37,615,613 over a 10-year period.
                    </P>
                    <P>The Agency realizes that a mandatory electronic filing requirement may involve a change of business practices for a small number of regulated entities under its jurisdiction; and with respect to these entities, we invite comments about the following questions:</P>
                    <P>(1) What would be the impact (benefits or hardships) on applicants of a mandatory electronic filing requirement?</P>
                    <P>(2) Would these impacts be different 4 years after the publication date of this notice? If so, how?</P>
                    <P>(3) If the impacts are expected to be adverse, how can they be mitigated?</P>
                    <P>(4) Should FMCSA provide a phase-in period for complying with the mandatory electronic filing requirement? If yes, please recommend appropriate phase-in criteria and time periods, stated in terms relative to the publication date of the final rule.</P>
                    <P>(5) If you believe electronic filing would be burdensome, would the benefits of obtaining operating authority more quickly offset any potential costs associated with electronic filing?</P>
                    <HD SOURCE="HD3">9. Total Net Benefits From the URS SNPRM</HD>
                    <P>The FMCSA calculated the net benefits of the proposed rule by subtracting the total 10-year cost from the total 10-year benefits for each provision. Table 5 presents the net benefits of the proposed rule for each provision presented above. The cost to industry associated with fee changes is offset by an equal gain to FMCSA due to increased revenues from fees. Therefore, the impact to society from the change in fees is zero. Net benefits are estimated to be −$23.0 million for the industry and $42.6 million for FMCSA. This results in total societal net benefits of the URS SNPRM of $19.6 million. The industry would experience a total increase in fees of −$58.6 million (including total fees paid and fees saved). This increase in fees to the industry is offset by a total $58.6 million increase in fees received by FMCSA (including fees lost and fees received).</P>
                    <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,12,12,12,12">
                        <TTITLE>Table 5—Net Benefits of URS Proposed Rule</TTITLE>
                        <TDESC>[10-year present value]</TDESC>
                        <BOXHD>
                            <CHED H="1">URS rule provision</CHED>
                            <CHED H="1">Net benefits</CHED>
                            <CHED H="2">Industry</CHED>
                            <CHED H="2">Agency</CHED>
                            <CHED H="1">Net fees</CHED>
                            <CHED H="2">Industry</CHED>
                            <CHED H="2">Agency</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Mandatory Electronic Filing</ENT>
                            <ENT>$1,425,292</ENT>
                            <ENT>$36,190,320</ENT>
                            <ENT>$0</ENT>
                            <ENT>$0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Eliminating Transfer/Name Change Requirements</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>1,854,890</ENT>
                            <ENT>1,854,890</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">New Registrant Fee</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                            <ENT>−63,583,722</ENT>
                            <ENT>63,583,722</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Insurance Filing</ENT>
                            <ENT>−676,723</ENT>
                            <ENT>0</ENT>
                            <ENT>−1,691,808</ENT>
                            <ENT>1,691,808</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Process Agent Filing</ENT>
                            <ENT>−25,067,012</ENT>
                            <ENT>3,130,736</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Cancellations and Reinstatements</ENT>
                            <ENT>−60,070</ENT>
                            <ENT>−135,158</ENT>
                            <ENT>4,808,126</ENT>
                            <ENT>4,808,126</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">New MCSA-1 Application Form</ENT>
                            <ENT>1,354,631</ENT>
                            <ENT>3,391,089</ENT>
                            <ENT>0</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">Net Benefits</ENT>
                            <ENT>−23,023,883</ENT>
                            <ENT>42,576,988</ENT>
                            <ENT>−58,612,513</ENT>
                            <ENT>58,612,513</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Societal Net Benefits</ENT>
                            <ENT A="01">19,553,105</ENT>
                            <ENT A="01">0</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Numbers may not add due to rounding.
                        </TNOTE>
                    </GPOTABLE>
                    <HD SOURCE="HD1">V. Appendix to the Preamble—Proposed Form MCSA-1 and Instructions</HD>
                    <BILCOD>BILLING CODE 4910-EX-P</BILCOD>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66529"/>
                        <GID>EP26OC11.015</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66530"/>
                        <GID>EP26OC11.016</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66531"/>
                        <GID>EP26OC11.017</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66532"/>
                        <GID>EP26OC11.018</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66533"/>
                        <GID>EP26OC11.019</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66534"/>
                        <GID>EP26OC11.020</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66535"/>
                        <GID>EP26OC11.021</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66536"/>
                        <GID>EP26OC11.022</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66537"/>
                        <GID>EP26OC11.023</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66538"/>
                        <GID>EP26OC11.024</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66539"/>
                        <GID>EP26OC11.025</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66540"/>
                        <GID>EP26OC11.026</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66541"/>
                        <GID>EP26OC11.027</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66542"/>
                        <GID>EP26OC11.028</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66543"/>
                        <GID>EP26OC11.029</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66544"/>
                        <GID>EP26OC11.030</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66545"/>
                        <GID>EP26OC11.031</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66546"/>
                        <GID>EP26OC11.032</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66547"/>
                        <GID>EP26OC11.033</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66548"/>
                        <GID>EP26OC11.034</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66549"/>
                        <GID>EP26OC11.035</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66550"/>
                        <GID>EP26OC11.036</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66551"/>
                        <GID>EP26OC11.037</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66552"/>
                        <GID>EP26OC11.038</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66553"/>
                        <GID>EP26OC11.039</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66554"/>
                        <GID>EP26OC11.040</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66555"/>
                        <GID>EP26OC11.041</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66556"/>
                        <GID>EP26OC11.042</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66557"/>
                        <GID>EP26OC11.043</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66558"/>
                        <GID>EP26OC11.044</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66559"/>
                        <GID>EP26OC11.045</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66560"/>
                        <GID>EP26OC11.046</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66561"/>
                        <GID>EP26OC11.047</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66562"/>
                        <GID>EP26OC11.048</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66563"/>
                        <GID>EP26OC11.049</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66564"/>
                        <GID>EP26OC11.050</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66565"/>
                        <GID>EP26OC11.051</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66566"/>
                        <GID>EP26OC11.052</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66567"/>
                        <GID>EP26OC11.053</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66568"/>
                        <GID>EP26OC11.054</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66569"/>
                        <GID>EP26OC11.055</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66570"/>
                        <GID>EP26OC11.056</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66571"/>
                        <GID>EP26OC11.057</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66572"/>
                        <GID>EP26OC11.058</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66573"/>
                        <GID>EP26OC11.059</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66574"/>
                        <GID>EP26OC11.060</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66575"/>
                        <GID>EP26OC11.061</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66576"/>
                        <GID>EP26OC11.062</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66577"/>
                        <GID>EP26OC11.063</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="66578"/>
                        <GID>EP26OC11.064</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 4910-EX-C</BILCOD>
                    <PRTPAGE P="66579"/>
                    <HD SOURCE="HD1">VI. Rulemaking Analyses and Notices</HD>
                    <HD SOURCE="HD2">Executive Order 12866 (Regulatory Planning and Review) and DOT Regulatory Policies and Procedures</HD>
                    <P>The FMCSA has preliminarily determined that this proposed rule is a significant regulatory action within the meaning of Executive Order 12866, and is significant within the meaning of Department of Transportation regulatory policies and procedures (DOT Order 2100.5 dated May 22, 1980; 44 FR 11034, February 26, 1979) because it is expected to generate significant public interest. However, it is anticipated that the economic impact of the revisions in this SNPRM would not exceed the annual $100 million threshold for economic significance. The Office of Management and Budget (OMB) has reviewed this proposed rule.</P>
                    <HD SOURCE="HD2">Regulatory Flexibility Act</HD>
                    <P>The Regulatory Flexibility Act [Pub. L. 96-354, 5 U.S.C. 601-612] requires Federal agencies to take small businesses' concerns into account when developing, writing, publicizing, promulgating, and enforcing regulations. To achieve this, the Act requires that agencies detail how they have met these concerns through a Regulatory Flexibility Analysis (RFA). An initial RFA, which accompanies an NPRM, must include six elements. The Agency has listed these elements below and addressed each element with regard to FMCSA's SNPRM.</P>
                    <P>
                        <E T="03">(1) A description of the reasons why action by the Agency is being considered.</E>
                         The FMCSA is taking this action in response to section 103 of the ICC Termination Act of 1995 (ICCTA), as amended by section 4304 of SAFETEA-LU, which, among other things, requires the Secretary of Transportation (Secretary) to propose regulations to replace four current identification and registration systems with a single, online, Federal system. The purpose of this proposal is to consolidate and simplify current Federal registration processes and to increase public accessibility to data about interstate motor carriers, property brokers, freight forwarders, and other entities. Pursuant to the statutory mandate, FMCSA proposes to charge registration and administrative fees that would enable FMCSA to recoup the costs associated with processing registration applications and administrative filings and maintaining this system.
                    </P>
                    <P>
                        <E T="03">(2) A succinct statement of the objectives of, and legal basis for, the proposed rule.</E>
                         The ICCTA created a new 49 U.S.C. 13908 directing “[t]he Secretary, in cooperation with the States, and after notice and opportunity for public comment,” * * *  to “issue regulations to replace the current Department of Transportation identification number system, the single State registration system under section 14504, the registration system contained in this chapter, and the financial responsibility information system under section 13906 with a single, on-line, Federal system.”
                    </P>
                    <P>Title 49 U.S.C. 13908(d) authorizes the Secretary to establish, under sections 9701 of title 31, United States Code, a fee system for the Unified Carrier Registration System according to certain guidelines providing for fee limits for registration, filing evidence of financial responsibility and filing information regarding agents for service of process.</P>
                    <P>These directives specifically require FMCSA to undertake some of the actions in this proposal. The remaining related changes facilitate the smooth operation of a unified Federal on-line registration system.</P>
                    <P>
                        <E T="03">(3) A description and, where feasible, an estimate of the number of small entities to which the proposed rule would apply.</E>
                         The FMCSA would subject all motor carriers engaging in interstate commerce (private, exempt and non-exempt for-hire) to this proposal.
                    </P>
                    <P>
                        Not all carriers are required to report their revenue to the Agency; but all carriers are required to provide the Agency with the number of power units they operate when they apply for operating authority and to update this figure biennially. Because FMCSA does not have direct revenue figures, power units serve as a proxy to determine the carrier size that would qualify as a small business given the SBA's revenue threshold. In order to produce this estimate, it is necessary to determine the average revenue generated by a power unit. With regards to truck power units, the Agency determined in the 2003 Hours of Service Rulemaking RIA 
                        <SU>18</SU>
                        <FTREF/>
                         that a power unit produces about $172,000 in revenue annually (adjusted for inflation).
                        <SU>19</SU>
                        <FTREF/>
                         The Small Business Administration (SBA) defines a small entity in the truck transportation sub-sector (North American Industry Classification System [NAICS] 484) as an entity with annual revenue of less than $25.5 million [13 CFR 121.201].
                        <SU>20</SU>
                        <FTREF/>
                         This equates to 148 power units ($25,500,000/$172,000). Thus, FMCSA considers motor carriers with 148 power units or less to be a small business for SBA purposes.
                    </P>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             Regulatory Analysis for: Hours of Service of Drivers; Driver Rest and Sleep for Safe Operations, Final Rule-Federal Motor Carrier Safety Administration. 68 FR 22456-Published 4/23/2003.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>19</SU>
                             The 2000 TTS Blue Book of Trucking Companies, number adjusted to 2008 dollars for inflation.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>20</SU>
                             U.S. Small Business Administration Table of Small Business Size Standards matched to North American Industry Classification (NAIC) System codes, effective August 22, 2008. See NAIC subsector 484, Truck Transportation.
                        </P>
                    </FTNT>
                    <P>
                        With regards to bus power units, the Agency conducted a preliminary analysis to estimate the average number of power units (PUs) for a small entity earning $7 million annually, based on an assumption that a passenger carrying CMV generates annual revenues of $150,000. This estimate compares reasonably to the estimated average annual revenue per power unit for the trucking industry ($172,000). A lower estimate was used because buses generally do not accumulate as many vehicle miles traveled (VMT) per power units as trucks,
                        <SU>21</SU>
                        <FTREF/>
                         and it is assumed therefore that they would generate less revenue on average. The analysis concluded that passenger carriers with 47 PUs or fewer ($7,000,000 divided by $150,000/PU = 46.7 PU) would be considered small entities. The Agency then looked at the number and percentage of passenger carriers registered with FMCSA that would fall under that definition (of having 47 PUs or less). The results show that 28,838 
                        <SU>22</SU>
                        <FTREF/>
                         (or 99%) of all active registered passenger carriers have 47 PUs or less. Therefore, the overwhelming majority of passenger carriers would be considered small entities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>21</SU>
                             FMCSA Large Truck and Bus Crash Facts 2008, Tables 1 and 20; 
                            <E T="03">http://fmcsa.dot.gov/facts-research/LTBCF2008/Index-2008Large TruckandBusCrashFacts.aspx</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>22</SU>
                             FMCSA MCMIS snapshot on 2/19/2010.
                        </P>
                    </FTNT>
                    <P>FMCSA believes that this 150 power unit figure would be applicable to private carriers as well: Because the sizes of the fleets they are able to sustain are indicative of the overall size of their operations, large CMV fleets can generally only be managed by large firms. There is a risk, however, of overstating the number of small businesses because the operations of some large non-truck or bus firms may require only a small number of CMVs.</P>
                    <P>
                        The FMCSA believes the proposed rule would affect roughly 600,000 small carriers with recent activity annually on an ongoing basis.
                        <SU>23</SU>
                        <FTREF/>
                         The Agency expects a larger number of affected entities in the first year of the analysis period when exempt for-hire carriers with 
                        <PRTPAGE P="66580"/>
                        recent activity and private carriers with recent activity make administrative filings for the first time. The estimated first-year costs of the URS rule on new entrants would be equal to 0.250 percent of average revenue for a trucking motor carrier and 0.287 percent of average revenue for a passenger motor carrier. The first-year costs of the URS SNPRM on carriers with recent activity would be equal to 0.079 percent of average revenue for a trucking motor carrier and 0.091 percent of average revenue for a passenger motor carrier. The URS rule is thus not expected to have a significant economic impact on small new entrants and carriers with recent activity.
                    </P>
                    <FTNT>
                        <P>
                            <SU>23</SU>
                             This population estimate originates from tables 1 and 2, above. FMCSA used the median year estimate to account for the net growth in new entrants and the carriers with recent activity.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">(4) A description of the projected reporting, recordkeeping, and other compliance requirements of the proposed rule, including an estimate of the classes of small entities that will be subject to the requirements and the type of professional skills necessary for preparation of the report or record.</E>
                         This proposed rule primarily concerns submission of information to FMCSA in support of registration. While this includes recordkeeping and reporting for non-exempt for-hire carriers, there would only be the replacement of one type of reporting with another. Therefore, there would be no increase in reporting or recordkeeping requirements for non-exempt for-hire carriers. Non-exempt for-hire carriers are already required to pay a $300 registration fee, so there would be no change in financial burden for these entities as a result of the Agency's implementation of the proposed rule. Private and exempt for-hire carriers would have the same replacement reporting and recordkeeping requirements as non-exempt for-hire carriers regarding general registration but would also have to designate a process agent for the first time under the proposed rule. Exempt for-hire and private hazmat carriers would have to file proof of insurance for the first time. These requirements would be new but would not impose significant reporting or recordkeeping requirements on the affected entities, as the filings would be made by insurance companies on the carriers' behalf. New entrant exempt for-hire carriers, private carriers, and other entities are not currently required to pay a registration fee but would be required to pay a $300 registration fee under the proposed rule. For nearly all affected entities, this fee would represent a small fraction (well below one percent, even for very small firms that do little more than operate a single truck) of their annual revenues; on an annualized basis the cost would be even smaller. The FMCSA would require property brokers and freight forwarders to register with FMCSA and obtain USDOT Numbers under the proposed rule, which is a new requirement. However, these entities already register with FMCSA and the USDOT Number would simply be a replacement for the MC Numbers or FF Numbers currently issued to brokers and freight forwarders, respectively. Therefore, FMCSA does not believe the new reporting or recordkeeping requirements would impose any significant burden. Like non-exempt for-hire carriers, new entrant brokers and freight forwarders are currently required to pay a $300 registration fee, so there would be no change in financial burden on these entities.
                    </P>
                    <P>The FMCSA does not expect that any special skills for new registrants would be necessary beyond the ability to access the Internet and respond to questions with information about their organization and operations.</P>
                    <P>
                        <E T="03">(5) An identification, to the extent practicable, of all relevant Federal rules that may duplicate, overlap, or conflict with the proposed rule.</E>
                         The FMCSA is aware of Federal rules that may duplicate this SNPRM to some extent for hazardous materials motor carriers required to register. Although some basic identification information may be filed with both FMCSA and the Pipeline and Hazardous Materials Safety Administration (PHMSA), another USDOT modal administration, there is no conflict. PHMSA requires shippers and transporters of certain types and quantities of hazardous materials to register in its Hazardous Materials Registration System. Transportation modes required to register with PHMSA include motor carriers, airlines, ship lines, and railroads. The PHMSA Hazardous Materials Registration System cannot be combined with URS because entities other than those under FMCSA jurisdiction must register in PHMSA's system.
                    </P>
                    <P>
                        <E T="03">(6) A description of any significant alternatives to the proposed rule which minimize any significant impacts on small entities.</E>
                         The Agency did not identify any significant alternatives to the rule that could lessen the burden on small entities without compromising its goals or the Agency's statutory mandate. Because small businesses are such a large part of the demographic the Agency regulates, providing alternatives to small business to permit noncompliance with FMCSA regulations is not feasible and not consistent with sound public policy.
                    </P>
                    <HD SOURCE="HD2">Unfunded Mandates Reform Act of 1995</HD>
                    <P>The Unfunded Mandates Reform Act of 1995 [Pub. L. 104-4; 2 U.S.C. 1532] requires each Agency to assess the effects of its regulatory actions on State, local, and Tribal governments and the private sector. Any Agency promulgating a rule likely to result in a Federal mandate requiring expenditures by a State, local, or Tribal government or by the private sector of $141.3 million or more in any one year must prepare a written statement incorporating various assessments, estimates, and descriptions that are delineated in the Act. The FMCSA has preliminarily determined that the changes proposed in this SNPRM would not have an impact of $141.3 million or more in any one given year.</P>
                    <HD SOURCE="HD2">National Environmental Policy Act</HD>
                    <P>
                        The Agency analyzed this proposed rule for the purpose of the National Environmental Policy Act of 1969 (NEPA) (42 U.S.C. 4321 
                        <E T="03">et seq.</E>
                        ) and preliminarily determined under our environmental procedures Order 5610.1, issued March 1, 2004 (69 FR 9680), that this action is categorically excluded (CE) under Appendix 2, paragraphs 6.e and 6.h of the Order from further environmental documentation. The CE under Appendix 2, paragraph 6.e relates to establishing regulations and actions taken pursuant to the requirements concerning applications for operating authority and certificates of registration. The CE under Appendix 2, paragraph 6.h relates to establishing regulations and actions taken pursuant to the requirements implementing procedures to collect fees that will be charged for motor carrier registrations and insurance for the following activities: (1) Application filings; (2) records searches; and (3) reviewing, copying, certifying, and related services. In addition, the Agency believes that this proposed action includes no extraordinary circumstances that would have any effect on the quality of the human environment. Thus, the SNPRM does not require an environmental assessment or an environmental impact statement.
                    </P>
                    <P>
                        The FMCSA also has analyzed this SNPRM under the Clean Air Act, as amended (CAA), sec. 176(c) (42 U.S.C. 7401 
                        <E T="03">et seq.</E>
                        ), and implementing regulations promulgated by the Environmental Protection Agency. Approval of this proposal is exempt from the CAA's general conformity requirement because it involves policy development and rulemaking activities regarding registration of regulated entities with FMCSA for commercial, 
                        <PRTPAGE P="66581"/>
                        safety and financial responsibility purposes. See 40 CFR 93.153(c)(2)(vi). The proposed changes would not result in any emissions increases nor would they have any potential to result in emissions that are above the general conformity rule's 
                        <E T="03">de minimis</E>
                         emission threshold levels. Moreover, it is reasonably foreseeable that the proposed changes would not increase total CMV mileage or change the routing of CMVs, how CMVs operate, or the CMV fleet-mix of motor carriers. This SNPRM was mandated under sec. 103 of the ICCTA. It would consolidate and simplify the Federal registration processes and increase public accessibility to data about interstate and foreign motor carriers, property brokers, freight forwarders and other entities.
                    </P>
                    <HD SOURCE="HD2">Paperwork Reduction Act</HD>
                    <P>Under the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501-3520), a Federal Agency must obtain approval from OMB for each collection of information it conducts, sponsors, or requires through regulations. The FMCSA analyzed this proposal and preliminarily determined that its implementation would streamline the information collection burden on motor carriers and other regulated entities, relative to the baseline, or current paperwork collection processes. This includes streamlining the FMCSA registration, insurance and designation of process agent filing processes and implementing mandatory electronic online filing of these applications, as well as eliminating some outdated filing requirements. The above information collection burden reductions would be partially offset in later years because FMCSA plans to implement new filing requirements upon certain groups of carriers/entities within the industry during the first year. This is primarily due to the assumption that all existing private and exempt for-hire carriers would file proof of process agent designation in the first year and the existing private motor carriers transporting hazardous materials interstate and exempt-for-hire carriers would file evidence of insurance, as a result of the new requirements set forth in this SNPRM. However, once the initial process agent and insurance filing requirements for existing carriers are met, the overall net result would be a more streamlined process in future years for FMCSA registration of motor carrier, broker, freight-forwarder and other applicants the Agency regulates.</P>
                    <P>This proposal would create a new information collection to cover the requirements set forth in proposed FMCSA Form MCSA-1. There are also five approved information collections that would be affected by this SNPRM as follows: (1) OMB Control No. 2126-0013, titled “Motor Carrier Identification Report;” (2) OMB Control No. 2126-0015, titled “Designation of Agents, Motor Carriers, Brokers and Freight Forwarders;” (3) OMB Control No. 2126-0016, titled “Licensing Application for Motor Carrier Operating Authority;” (4) OMB Control No. 2126-0017, titled “Financial Responsibility, Trucking, and Freight Forwarding;” and (5) OMB Control No. 2126-0019, titled “Application for Certificate of Registration for Foreign Motor Carriers and Foreign Motor Private Carriers.” The proposed new MCSA-1 Form would replace the forms covered by 2126-0013, 0016, and 0019. The proposed rule would also increase the number of entities that would be required to file information on process agents (2126-0015) and insurance coverage (2126-0017).</P>
                    <P>The total burden for the five approved information collections noted above is 248,355 hours. The table below captures the current and proposed burden hours associated with the five approved information collections.</P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,14,14,14)0">
                        <TTITLE>Current and Proposed Information Collection Burdens</TTITLE>
                        <BOXHD>
                            <CHED H="1">OMB Approval No.</CHED>
                            <CHED H="1">
                                Burden hours currently 
                                <LI>approved</LI>
                            </CHED>
                            <CHED H="1">
                                Burden hours proposed 
                                <SU>1</SU>
                            </CHED>
                            <CHED H="1">Change</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">2126-NEW</ENT>
                            <ENT>0</ENT>
                            <ENT>127,728</ENT>
                            <ENT>127,728</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2126-0013</ENT>
                            <ENT>109,005</ENT>
                            <ENT>0</ENT>
                            <ENT>(109,005)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2126-0015</ENT>
                            <ENT>14,835</ENT>
                            <ENT>69,373</ENT>
                            <ENT>54,538</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2126-0016</ENT>
                            <ENT>55,095</ENT>
                            <ENT>0</ENT>
                            <ENT>(55,095)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2126-0017</ENT>
                            <ENT>66,960</ENT>
                            <ENT>81,193</ENT>
                            <ENT>(14,233)</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">2126-0019</ENT>
                            <ENT>2,460</ENT>
                            <ENT>0</ENT>
                            <ENT>(2,460)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT>248,355</ENT>
                            <ENT>278,293</ENT>
                            <ENT>29,938</ENT>
                        </ROW>
                        <TNOTE>
                            <SU>1</SU>
                             The estimates in this column reflect first year information collection burdens. Many of these information collections would significantly decrease in later years.
                        </TNOTE>
                    </GPOTABLE>
                    <P>An explanation of how each of the six information collections shown above would be affected by this proposal is provided below.</P>
                    <P>
                        <E T="03">OMB Control No. 2126-NEW.</E>
                         Unified Registration System, Form MCSA-1. The new form would replace the forms covered by three existing information collections. The estimated time to complete the form for new entrants, file biennial updates, and request changes is 127,728 burden hours [82,115 hours for new registrants (61,280 new motor carriers, brokers, freight forwarders, and other entities × 1.34 hours per form) + 43,560 hours for biennial updates (261,360 registrants required to file in year one × 10 minutes per form, divided by 60 minutes/hr) + 2,053 hours for name/address change requests (12,317 requests × 0.167 hours)].
                    </P>
                    <P>
                        <E T="03">OMB Control No. 2126-0013.</E>
                         Motor Carrier Identification Report, Applications for USDOT Number. The Agency anticipates that all of the requirements under this information collection covering the MCS-150, MCS-150B, and MCS-150C forms would be folded into OMB Control No. 2126-NEW (see above) and the forms replaced by the MCSA-1.
                    </P>
                    <P>
                        <E T="03">OMB Control No. 2126-0015.</E>
                         Designation of Agents, Motor Carriers, Brokers, and Freight Forwarders. This information collection, which requires motor carriers and others to file the name of process agents that can be served with legal papers, is currently approved at 14,835 burden hours. This information collection would increase to 69,373 burden hours [327,226 new filers × 10 minutes per filing/60 minutes/hr]. This increase is due to FMCSA's proposal to extend the designation of process agent filing requirement to include private motor carriers and exempt for-hire motor carriers. The FMCSA assumes that no existing private or exempt for-hire motor carriers currently have process agents on file and that all would 
                        <PRTPAGE P="66582"/>
                        designate agents with FMCSA as a result of the proposed requirements set forth in this SNPRM.
                    </P>
                    <P>
                        <E T="03">OMB Control No. 2126-0016.</E>
                         Licensing Applications for Motor Carrier Operating Authority. This information collection, which covers for-hire carriers, freight forwarders and property brokers, is currently approved at 55,095 burden hours. Under this proposal, all requirements included in this information collection would be folded into OMB Control No. 2126-NEW (see above) and the forms replaced by the MCSA-1. Basic identification information that registrants complete on these forms and MCS-150 forms will only need to be completed once under the proposed rule.
                    </P>
                    <P>
                        <E T="03">OMB Control No. 2126-0017.</E>
                         Financial Responsibility—Motor Carriers, Freight Forwarders and Brokers. This information collection, which in almost all cases requires insurers to file a certification of coverage for certain entities, is currently approved at 66,960 burden hours. Changes would be required to this information collection due to FMCSA's proposal to require exempt for-hire motor carriers and private interstate motor carriers of hazardous materials to file proof of liability insurance with FMCSA. As all but a few of these filings are electronic (self-insurance filings will still be done on paper), the time required would be adjusted downward to reflect the efficiencies gained. The revised burden would be 81,193 hours [485,956 filings × 10 minutes/60 plus 5 self-insurance filings × 40 hrs]
                    </P>
                    <P>
                        <E T="03">OMB Control No. 2126-0019.</E>
                         Application for Certificate of Registration for Foreign Motor Carriers and Foreign Motor Private Carriers. Under this proposal, the requirements included in this approved information collection for the OP-2 form, which covers operating authority for Mexico-domiciled carriers that operate solely in the commercial zones on the border, would be folded into OMB Control No. 2126-NEW (see above), resulting in a net decrease of 2,460 burden hours. The FMCSA will discontinue this information collection after the final rule is approved for this rulemaking.
                    </P>
                    <P>The proposals contained in this SNPRM, affecting five currently approved information collections and one new information collection, would result in a net increase of 10,787 burden hours in the Agency's information collection budget for the first year.</P>
                    <P>Additional information collection activity and possibly additional OMB forms may be identified and developed as the rulemaking process proceeds. If so, an analysis of any additional information collection activity would be developed by FMCSA. The Agency also would seek OMB approval for any additional burdens proposed, if not already covered by existing OMB approvals given to the Agency.</P>
                    <HD SOURCE="HD2">Executive Order 12630 (Taking of Private Property)</HD>
                    <P>This proposed rule would 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="HD2">Executive Order 12988 (Civil Justice Reform)</HD>
                    <P>This proposed 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="HD2">Executive Order 13045 (Protection of Children)</HD>
                    <P>Executive Order 13045, “Protection of Children from Environmental Health Risks and Safety Risks” (April 23, 1997, 62 FR 19885), requires that agencies issuing economically significant rules, which also concern an environmental health or safety risk that an Agency has reason to believe may disproportionately affect children, must include an evaluation of the environmental health and safety effects of the regulation on children. Section 5 of Executive Order 13045 directs an Agency to submit for a covered regulatory action an evaluation of its environmental health or safety effects on children. The FMCSA has preliminarily determined that this proposed rule is not a covered regulatory action as defined under Executive Order 13045. This determination is based upon the fact that this proposed rule is not economically significant under Executive Order 12866, because the changes proposed in this rule would not have an impact of $100 million or more in any one given year. This proposal would not constitute an environmental health risk or safety risk that would disproportionately affect children.</P>
                    <HD SOURCE="HD2">Executive Order 13132 (Federalism)</HD>
                    <P>This proposed rule has been analyzed in accordance with the principles and criteria in Executive Order 13132, dated August 4, 1999 (64 FR 43255, August 10, 1999). The FMCSA consulted with State licensing agencies participating in its PRISM program to discuss anticipated impacts of the May 2005 NPRM upon their operations. The Agency has taken into consideration their comments in its decisionmaking process for this SNPRM. Thus, FMCSA has preliminarily determined that this proposal would not have significant Federalism implications or limit the policymaking discretion of the States.</P>
                    <HD SOURCE="HD2">Executive Order 12372 (Intergovernmental Review)</HD>
                    <P>The regulations implementing Executive Order 12372 regarding intergovernmental consultation on Federal programs and activities do not apply to this program.</P>
                    <HD SOURCE="HD2">Executive Order 13211 (Energy Supply, Distribution, or Use)</HD>
                    <P>The FMCSA has analyzed this proposed rule under Executive Order 13211, “Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use.” This proposal is not a significant energy action within the meaning of section 4(b) of the Executive Order. This proposal is a procedural action, is not economically significant, and would not have a significant adverse effect on the supply, distribution, or use of energy.</P>
                    <HD SOURCE="HD2">Privacy Impact Analysis</HD>
                    <P>The FMCSA conducted a privacy impact assessment of this rule as required by section 522(a)(5) of division H of the FY 2005 Omnibus Appropriations Act, Pub. L. 108-447, 118 Stat. 3268 (Dec. 8, 2004) [set out as a note to 5 U.S.C. 552a]. The assessment considers any impacts of the final rule on the privacy of information in an identifiable form and related matters. The FMCSA has determined that this SNPRM would impact the handling of PII. The FMCSA has also determined the risks and effects the rulemaking might have on collecting, storing, and sharing PII and has examined and evaluated protections and alternative information handling processes in order to mitigate potential privacy risks. The PIA for this proposed rulemaking is available for review in the docket for this rulemaking.</P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects</HD>
                        <CFR>49 CFR Part 360</CFR>
                        <P>
                            Administrative practice and procedure, Brokers, Buses, Freight forwarders, Hazardous materials transportation, Highway safety, Insurance, Motor carriers, Motor vehicle safety, Moving of household goods, Penalties, Reporting and recordkeeping requirements, Surety bonds.
                            <PRTPAGE P="66583"/>
                        </P>
                        <CFR>49 CFR Part 365</CFR>
                        <P>Administrative practice and procedure, Brokers, Buses, Freight forwarders, Motor carriers, Moving of household goods.</P>
                        <CFR>49 CFR Part 366</CFR>
                        <P>Brokers, Motor carriers, Freight forwarders, Process agents.</P>
                        <CFR>49 CFR Part 368</CFR>
                        <P>Administrative practice and procedure, Insurance, Motor carriers.</P>
                        <CFR>49 CFR Part 385</CFR>
                        <P>Administrative practices and procedure, Highway safety, Motor carriers, Motor vehicle safety, Reporting and recordkeeping requirements.</P>
                        <CFR>49 CFR Part 387</CFR>
                        <P>Buses, Freight, Freight forwarders, Hazardous materials transportation, Highway safety, Insurance, Intergovernmental relations, Motor carriers, Motor vehicle safety, Moving of household goods, Penalties, Reporting and recordkeeping requirements, Surety bonds.</P>
                        <CFR>49 CFR Part 390</CFR>
                        <P>Highway safety, Intermodal transportation, Motor carriers, Motor vehicle safety, reporting and recordkeeping requirements.</P>
                        <CFR>49 CFR Part 392</CFR>
                        <P>Highway safety, Motor carriers.</P>
                    </LSTSUB>
                    <P>For reasons set forth in the preamble, FMCSA proposes to amend title 49, Code of Federal Regulations, chapter III, as follows:</P>
                    <P>1. Revise part 360 to read as follows:</P>
                    <PART>
                        <HD SOURCE="HED">PART 360—FEES FOR MOTOR CARRIER REGISTRATION AND INSURANCE</HD>
                        <CONTENTS>
                            <SECHD>Sec. </SECHD>
                            <SECTNO>360.1 </SECTNO>
                            <SUBJECT>Fees for registration-related services. </SUBJECT>
                            <SECTNO>360.3 </SECTNO>
                            <SUBJECT>Filing fees. </SUBJECT>
                            <SECTNO>360.5 </SECTNO>
                            <SUBJECT>Updating user fees.</SUBJECT>
                        </CONTENTS>
                        <AUTH>
                            <HD SOURCE="HED">Authority: </HD>
                            <P>31 U.S.C. 9701; 49 U.S.C. 13908; and 49 CFR 1.73.</P>
                        </AUTH>
                        <SECTION>
                            <SECTNO>§ 360.1 </SECTNO>
                            <SUBJECT>Fees for registration-related services.</SUBJECT>
                            <P>Certifications and copies of public records and documents on file with the Federal Motor Carrier Safety Administration (FMCSA) will be furnished on the following basis, pursuant to USDOT Freedom of Information Act regulations at 49 CFR Part 7:</P>
                            <P>(a) Certificate of the Director, Office of Management and Information Services, as to the authenticity of documents, $12;</P>
                            <P>(b) Service involved in locating records to be certified and determining their authenticity, including clerical and administrative work incidental thereto, at the rate of $21 per hour;</P>
                            <P>(c) Copies of the public documents, at the rate of $.80 per letter size or legal size exposure. A minimum charge of $5 will be made for this service; and</P>
                            <P>(d) Search and copying services requiring information technology (IT), as follows:</P>
                            <P>(1) A fee of $50 per hour for professional staff time will be charged when it is required to fulfill a request for electronic data.</P>
                            <P>(2) The fee for computer searches will be set at the current rate for computer service. Information on those charges can be obtained from the Office of Information Technology (MC-RI).</P>
                            <P>
                                (3) Printing shall be charged at the rate of $.10 per page of computer-generated output with a minimum charge of $1. There will also be a charge for the media provided (
                                <E T="03">e.g.,</E>
                                 CD ROMs) based on the Agency's costs for such media.
                            </P>
                            <P>
                                (e) 
                                <E T="03">Exception.</E>
                                 No fee shall be charged under this section to the following entities:
                            </P>
                            <P>(1) Any Agency of the Federal Government or a State government or any political subdivision of any such government for access to or retrieval of information and data from the Unified Carrier Registration System for its own use; or</P>
                            <P>(2) Any representative of a motor carrier, motor private carrier, leasing company, broker, or freight forwarder (as each is defined in 49 U.S.C. 13102) for the access to or retrieval of the individual information related to such entity from the Unified Carrier Registration System for the individual use of such entity.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 360.3 </SECTNO>
                            <SUBJECT>Filing fees.</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Manner of payment.</E>
                                 (1) Except for the insurance fees described in the next sentence, all filing fees will be payable at the time the application, petition, or other document is electronically filed. The service fee for insurance, surety or self-insurer accepted certificate of insurance, surety bond or other instrument submitted in lieu of a broker surety bond must be charged to an insurance service account established by FMCSA in accordance with paragraph (a)(2) of this section.
                            </P>
                            <P>
                                (2) 
                                <E T="03">Billing account procedure.</E>
                                 A request must be submitted to the Office of Enforcement and Compliance, Commercial Enforcement Division (MC-ECC) at 
                                <E T="03">http://www.fmcsa.dot.gov</E>
                                 to establish an insurance service fee account.
                            </P>
                            <P>(i) Each account will have a specific billing date within each month and a billing cycle. The billing date is the date that the bill is prepared and printed. The billing cycle is the period between the billing date in one month and the billing date in the next month. A bill for each account which has activity or an unpaid balance during the billing cycle will be sent on the billing date each month. Payment will be due 20 days from the billing date. Payments received before the next billing date are applied to the account. Interest will accrue in accordance with 31 CFR 901.9.</P>
                            <P>(ii) The Federal Claims Collection Standards, including disclosure to consumer reporting agencies and the use of collection agencies, as set forth in 31 CFR part 901 will be utilized to encourage payment where appropriate.</P>
                            <P>
                                (iii) An account holder who files a petition in bankruptcy or who is the subject of a bankruptcy proceeding must provide the following information to the Office of Enforcement and Compliance, Commercial Enforcement Division (MC-ECC) at 
                                <E T="03">http://www.fmcsa.dot.gov:</E>
                            </P>
                            <P>(A) The filing date of the bankruptcy petition;</P>
                            <P>(B) The court in which the bankruptcy petition was filed;</P>
                            <P>(C) The type of bankruptcy proceeding;</P>
                            <P>(D) The name, address, and telephone number of its representative in the bankruptcy proceeding; and</P>
                            <P>(E) The name, address, and telephone number of the bankruptcy trustee, if one has been appointed.</P>
                            <P>(3) Fees will be payable through the U.S. Department of the Treasury secure payment system, Pay.gov and are made directly from the payor's bank account or by credit/debit card.</P>
                            <P>(b) Any filing that is not accompanied by the appropriate filing fee will be rejected.</P>
                            <P>
                                (c) 
                                <E T="03">Fees not refundable.</E>
                                 Fees will be assessed for every filing listed in the schedule of fees contained in paragraph (f) of this section, subject to the exceptions contained in paragraphs (d) and (e) of this section. After the application, petition, or other document has been accepted for filing by FMCSA, the filing fee will not be refunded, regardless of whether the application, petition, or other document is granted or approved, denied, rejected before docketing, dismissed, or withdrawn.
                            </P>
                            <P>
                                (d) 
                                <E T="03">Multiple authorities.</E>
                                 (1) A separate filing fee is required for each type of authority sought in each transportation mode, such as broker authority for motor property carriers.
                            </P>
                            <P>
                                (2) Separate fees will be assessed for the filing of temporary operating authority applications as provided in paragraph (f)(2) of this section, regardless of whether such applications 
                                <PRTPAGE P="66584"/>
                                are related to an application for corresponding permanent operating authority.
                            </P>
                            <P>
                                (e) 
                                <E T="03">Waiver or reduction of filing fees.</E>
                                 It is the general policy of the Federal Motor Carrier Safety Administration not to waive or reduce filing fees except as follows:
                            </P>
                            <P>(1) Filing fees are waived for an application which is filed by a Federal government agency, or a State or local government entity. For purposes of this section the phrases “Federal government agency” or “government entity” do not include a quasi-governmental corporation or government subsidized transportation company.</P>
                            <P>(2) Filing fees are waived for a motor carrier of passengers that receives a grant from the Federal Transit Administration either directly or through a third-party contract to provide passenger transportation under an agreement with a State or local government pursuant to 49 U.S.C. section 5307, 5310, 5311, 5316 or 5317.</P>
                            <P>(3) The FMCSA will consider other requests for waivers or fee reductions only in extraordinary situations and in accordance with the following procedure:</P>
                            <P>
                                (i) 
                                <E T="03">When to request.</E>
                                 At the time that a filing is submitted to FMCSA the applicant may request a waiver or reduction of the fee prescribed in this part. Such request should be addressed to the Director, Office of Information Technology.
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Basis.</E>
                                 The applicant must show the waiver or reduction of the fee is in the best interest of the public, or that payment of the fee would impose an undue hardship upon the requestor.
                            </P>
                            <P>
                                (iii) 
                                <E T="03">FMCSA action.</E>
                                 The Director, Office of Information Technology, will notify the applicant of the decision to grant or deny the request for waiver or reduction.
                            </P>
                            <P>(f) Schedule of filing fees:</P>
                            <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s50,r100,r50">
                                <TTITLE> </TTITLE>
                                <BOXHD>
                                    <CHED H="1">Type of proceeding</CHED>
                                    <CHED H="1"> </CHED>
                                    <CHED H="1">Fee</CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="22">Part I: Registration:</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">(1)</ENT>
                                    <ENT>An application for USDOT Registration pursuant to 49 CFR part 390, subpart C</ENT>
                                    <ENT>$300.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">(2)</ENT>
                                    <ENT>An application for motor carrier temporary authority to provide emergency relief in response to a national emergency or natural disaster following an emergency declaration under § 390.23 of this subchapter</ENT>
                                    <ENT>$100.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">(3)</ENT>
                                    <ENT>Biennial update of registration</ENT>
                                    <ENT>$0.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">(4)</ENT>
                                    <ENT>Request for change of name, address, or form of business</ENT>
                                    <ENT>$0.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">(5)</ENT>
                                    <ENT>Request for cancellation of registration</ENT>
                                    <ENT>$0.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">(6)</ENT>
                                    <ENT>Request for registration reinstatemen</ENT>
                                    <ENT>$10.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">(7)</ENT>
                                    <ENT>Designation of process agen</ENT>
                                    <ENT>$0.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22">Part II: Insurance:</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">(8)</ENT>
                                    <ENT>A service fee for insurer, surety, or self-insurer accepted certificate of insurance, surety bond, and other instrument submitted in lieu of a broker surety bond</ENT>
                                    <ENT>$10 per accepted certificate, surety bond or other instrument submitted in lieu of a broker surety bond.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="03">(9)</ENT>
                                    <ENT>(i) An application for original qualification as self-insurer for bodily injury and property damage insurance (BI&amp;PD)</ENT>
                                    <ENT>[Reserved].</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>(ii) An application for original qualification as self-insurer for cargo insurance</ENT>
                                    <ENT>[Reserved].</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>(iii) Fee for quarterly self-insurance monitoring filing</ENT>
                                    <ENT>[Reserved].</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>(iv) Fee for annual self-insurance monitoring filing</ENT>
                                    <ENT>[Reserved].</ENT>
                                </ROW>
                            </GPOTABLE>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 360.5</SECTNO>
                            <SUBJECT>Updating user fees.</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Update.</E>
                                 Each fee established in this subpart may be updated, as deemed necessary by FMCSA.
                            </P>
                            <P>
                                (b) 
                                <E T="03">Publication and effective dates.</E>
                                 Notice of updated fees will be published in the 
                                <E T="04">Federal Register</E>
                                 in a final rule and will become effective 30 days after publication.
                            </P>
                            <P>
                                (c) 
                                <E T="03">Payment of fees.</E>
                                 Any person submitting a filing for which a filing fee is established must pay the fee applicable on the date of the filing or request for services.
                            </P>
                            <P>
                                (d) 
                                <E T="03">Method of updating fees.</E>
                                 Each fee shall be updated by updating the cost components comprising the fee. However, fees shall not exceed the maximum amounts established by law. Cost components shall be updated as follows:
                            </P>
                            <P>
                                (1) Direct labor costs shall be updated by multiplying base level direct labor costs by percentage changes in average wages and salaries of FMCSA employees. Base level direct labor costs are direct labor costs determined by the cost study in 
                                <E T="03">Regulations Governing Fees For Service,</E>
                                 1 I.C.C. 2d 60 (1984), or subsequent cost studies. The base period for measuring changes shall be April 1984 or the year of the last cost study.
                            </P>
                            <P>(2) Operations overhead shall be developed on the basis of current relationships existing on a weighted basis, for indirect labor applicable to the first supervisory work centers directly associated with user fee activity. Actual updating of operations overhead will be accomplished by applying the current percentage factor to updated direct labor, including current governmental overhead costs.</P>
                            <P>
                                (3)(i) Office general and administrative costs shall be developed on the basis of current levels costs, 
                                <E T="03">i.e.,</E>
                                 dividing actual office general and administrative costs for the current fiscal year by total office costs for the office directly associated with user fee activity. Actual updating of office general and administrative costs will be accomplished by applying the current percentage factor to updated direct labor, including current governmental overhead and current operations overhead costs.
                            </P>
                            <P>
                                (ii) The FMCSA general and administrative costs shall be developed on the basis of current level costs; 
                                <E T="03">i.e.,</E>
                                 dividing actual FMCSA general and administrative costs for the current fiscal year by total Agency expenses for the current fiscal year. Actual updating of FMCSA general and administrative costs will be accomplished by applying the current percentage factor to updated direct labor, including current governmental overhead, operations overhead and office general and administrative costs.
                            </P>
                            <P>
                                (4) Publication costs shall be adjusted on the basis of known changes in the costs applicable to publication of 
                                <PRTPAGE P="66585"/>
                                material in the 
                                <E T="04">Federal Register</E>
                                 or FMCSA Register.
                            </P>
                            <P>
                                (e) 
                                <E T="03">Rounding of updated fees.</E>
                                 (1) Updated fees shall be rounded in the following manner:
                            </P>
                            <P>(i) Fees between $1 and $30 will be rounded to the nearest $1;</P>
                            <P>(ii) Fees between $30 and $100 will be rounded to the nearest $10;</P>
                            <P>(iii) Fees between $100 and $999 will be rounded to the nearest $50; and</P>
                            <P>(iv) Fees above $1,000 will be rounded to the nearest $100.</P>
                            <P>(2) This rounding procedure excludes copying, printing and search fees.</P>
                        </SECTION>
                    </PART>
                    <PART>
                        <HD SOURCE="HED">PART 365—RULES GOVERNING APPLICATIONS FOR OPERATING AUTHORITY</HD>
                        <P>2. The authority citation for part 365 is revised to read as follows:</P>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>5 U.S.C. 553 and 559; 49 U.S.C. 13101, 13301, 13901-13906, 13908, 14708, 31138, and 31144; 49 CFR 1.73.</P>
                        </AUTH>
                        <P>3. Amend § 365.101 by revising paragraphs (a) and (h) to read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 365.101</SECTNO>
                            <SUBJECT>Applications governed by these rules.</SUBJECT>
                            <STARS/>
                            <P>(a) Applications for certificates of motor carrier registration to operate as a motor carrier of property or passengers.</P>
                            <STARS/>
                            <P>(h) Applications for Mexico-domiciled motor carriers to operate in foreign commerce as for hire or private motor carriers of property (including exempt items) between Mexico and all points in the United States. Under NAFTA Annex 1, page I-U-20, a Mexico-domiciled motor carrier may not provide point-to-point transportation services, including express delivery services, within the United States for goods other than international cargo.</P>
                            <STARS/>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 365.103</SECTNO>
                            <SUBJECT>[Removed and reserved]</SUBJECT>
                            <P>4. Remove and reserve § 365.103.</P>
                            <P>5. Revise § 365.105 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 365.105</SECTNO>
                            <SUBJECT>Starting the application process: Form MCSA-1, FMCSA Registration/Update (USDOT Number—Operating Authority Application)</SUBJECT>
                            <P>(a) Each applicant must apply for operating authority by electronically filing Form MCSA-1, FMCSA Registration/Update (USDOT Number—Operating Authority Application), to request authority pursuant to 49 U.S.C. 13902, 13903 or 13904 to operate as described in paragraphs (a)(1) through (a)(3) of this section as a:</P>
                            <P>(1) Motor carrier of property or passengers,</P>
                            <P>(2) Broker of general commodities or household goods, or</P>
                            <P>(3) Freight forwarder of general commodities or household goods.</P>
                            <P>(b) A separate filing fee in the amount set forth at 49 CFR 360.3(f) is required for each type of authority sought in § 365.105(a).</P>
                            <P>
                                (c) Form MCSA-1 is an electronic application and is available, including complete instructions, from the FMCSA Web site at 
                                <E T="03">http://www.fmcsa.dot.gov</E>
                                 (Keyword “MCSA-1”).
                            </P>
                            <P>6. Amend § 365.107 by revising paragraphs (a)(1) through (3), and paragraphs (b) through (e), to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 365.107</SECTNO>
                            <SUBJECT>Types of applications.</SUBJECT>
                            <P>(a) * * *</P>
                            <P>(1) Motor carrier of property (except household goods).</P>
                            <P>(2) Broker of general commodities or household goods.</P>
                            <P>(3) Certain types of motor carrier of passenger applications as described in Form MCSA-1.</P>
                            <P>(b) Motor carrier of passenger “public interest” applications as described in Form MCSA-1.</P>
                            <P>(c) Intrastate motor passenger applications under 49 U.S.C. 13902(b)(3) as described in Form MCSA-1.</P>
                            <P>(d) Motor carrier of household goods applications, including Mexico- or non-North America-domiciled carrier applicants. In addition to meeting the fitness standard under paragraph (a) of this section, an applicant seeking authority to operate as a motor carrier of household goods must:</P>
                            <P>(1) Provide evidence of participation in an arbitration program and provide a copy of the notice of the arbitration program as required by 49 U.S.C. 14708(b)(2);</P>
                            <P>(2) Identify its tariff and provide a copy of the notice of the availability of that tariff for inspection as required by 49 U.S.C. 13702(c);</P>
                            <P>(3) Provide evidence that it has access to, has read, is familiar with, and will observe all applicable Federal laws relating to consumer protection, estimating, consumers' rights and responsibilities, and options for limitations of liability for loss and damage; and</P>
                            <P>(4) Disclose any relationship involving common stock, common ownership, common management, or common familial relationships between the applicant and any other motor carrier, freight forwarder, or broker of household goods within 3 years of the proposed date of registration.</P>
                            <P>
                                (e) 
                                <E T="03">Temporary authority (TA) for motor carriers.</E>
                                 These applications require a finding that there is or soon will be an immediate transportation need that cannot be met by existing carrier service.
                            </P>
                            <P>(1) Applications for TA will be entertained only when an emergency declaration has been made pursuant to § 390.23 of this subchapter.</P>
                            <P>(2) Temporary authority must be requested by filing Form MCSA-1 with the Division Office that has jurisdiction over the State in which the applicant's principal place of business is located.</P>
                            <P>(3) Applications for temporary authority are not subject to protest.</P>
                            <P>(4) Motor carriers granted temporary authority must comply with financial responsibility requirements under part 387 of this subchapter.</P>
                            <P>(5) Only a U.S.-domiciled motor carrier is eligible to receive temporary authority.</P>
                            <P>7. Amend § 365.109 by revising paragraphs (a)(5) and (6) and (b) to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 365.109</SECTNO>
                            <SUBJECT>FMCSA review of the application.</SUBJECT>
                            <P>(a) * * *</P>
                            <P>(5) All applicants must file the appropriate evidence of financial responsibility within 90 days from the date notice of the application is published in the FMCSA Register:</P>
                            <P>
                                (i) 
                                <E T="03">Form BMC-91 or 91X or BMC 82 surety bond</E>
                                —Bodily injury and property damage (motor property and passenger carriers; and freight forwarders that provide pickup or delivery service directly or by using a local delivery service under their control),
                            </P>
                            <P>
                                (ii) 
                                <E T="03">Form BMC-84</E>
                                —Surety bond or 
                                <E T="03">Form BMC-85</E>
                                —trust fund agreement (property brokers of general commodities and household goods).
                            </P>
                            <P>
                                (iii) 
                                <E T="03">Form BMC-34 or BMC 83 surety bond</E>
                                —Cargo liability (household goods motor carriers and household goods freight forwarders).
                            </P>
                            <P>(6) Applicants also must submit Form BOC-3—Designation of Agents—Motor Carriers, Brokers and Freight Forwarders—within 90 days from the date notice of the application is published in the FMCSA Register.</P>
                            <STARS/>
                            <P>(b) A summary of the application will be published in the FMCSA Register to give notice to the public in case anyone wishes to oppose the application.</P>
                            <P>8. Add § 365.110 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 365.110</SECTNO>
                            <SUBJECT>New Entrant Safety Assurance Program.</SUBJECT>
                            <P>
                                For motor carriers operating commercial motor vehicles as defined in 49 U.S.C. 31132, operating authority obtained under procedures in this part does not become permanent until the applicant satisfactorily completes the 
                                <PRTPAGE P="66586"/>
                                New Entrant Safety Assurance Program in part 385 of this subchapter.
                            </P>
                            <P>9. Amend § 365.111 by revising paragraph (a) to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 365.111</SECTNO>
                            <SUBJECT>Appeals to rejections of the application.</SUBJECT>
                            <P>(a) An applicant has the right to appeal rejection of the application. The appeal must be filed at the FMCSA, Office of the Director of Information Technology, 1200 New Jersey Ave., SE., Washington, DC 20590, within 10 days of the date of the letter of rejection.</P>
                            <STARS/>
                            <P>10. Revise § 365.119 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 365.119</SECTNO>
                            <SUBJECT>Opposed applications.</SUBJECT>
                            <P>If the application is opposed, opposing parties are required to send a copy of their protest to the applicant and to FMCSA. All protests must include statements made under oath (verified statements). There are no personal appearances or formal hearings.</P>
                            <P>11. Revise § 365.201 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 365.201</SECTNO>
                            <SUBJECT>Definitions.</SUBJECT>
                            <P>
                                A person wishing to oppose a request for authority files a 
                                <E T="03">protest.</E>
                                 A person filing a valid protest is known as a 
                                <E T="03">protestant.</E>
                            </P>
                            <P>12. Revise § 365.203 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 365.203</SECTNO>
                            <SUBJECT>Time for filing.</SUBJECT>
                            <P>A protest shall be filed (received at the FMCSA, Office of the Associate Administrator for Research and Information Technology, 1200 New Jersey Ave., SE., Washington, DC 20590) within 10 days after notice of the application appears in the FMCSA Register. A copy of the protest shall be sent to applicant's representative at the same time. Failure to timely file a protest waives further participation in the proceeding.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 365.301</SECTNO>
                            <SUBJECT>[Removed and reserved]</SUBJECT>
                            <P>13. Remove and reserve § 365.301.</P>
                            <P>14. Revise the heading of subpart D to read as follows:</P>
                        </SECTION>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart D—Changes to an Entity's Name or Business Form</HD>
                            <SECTION>
                                <SECTNO>§§ 365.401, 365.403, 365.405, 365.407, 365.409, and 365.411</SECTNO>
                                <SUBJECT>[Removed and reserved]</SUBJECT>
                                <P>15. Remove and reserve §§ 365.401, 365.403, 365.405, 365.407, 365.409, and 365.411.</P>
                                <P>16. Amend § 365.507 by revising the heading and paragraph (e)(2) to read as follows</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 365.507</SECTNO>
                                <SUBJECT>FMCSA action on the application.</SUBJECT>
                                <STARS/>
                                <P>(e) * * *</P>
                                <P>(2) Electronically file Form BOC-3—Designation of Agents—Motor Carriers, Brokers and Freight Forwarders, as required by part 366 of this subchapter; and</P>
                                <STARS/>
                                <P>17. Amend § 365.509 by revising paragraph (a) to read as follows:</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 365.509</SECTNO>
                                <SUBJECT>Requirement to notify FMCSA of change in applicant information.</SUBJECT>
                                <P>(a) A motor carrier subject to this subpart must notify FMCSA of any changes or corrections to the information in Section A of Form MCSA-1—FMCSA Registration/Update (USDOT Number—Operating Authority Application), or Form BOC-3—Designation of Agents—Motor Carriers, Brokers and Freight Forwarders, during the application process or after having been granted provisional operating authority. The carrier must notify FMCSA in writing within 20 days of the change or correction.</P>
                                <STARS/>
                            </SECTION>
                        </SUBPART>
                    </PART>
                    <PART>
                        <HD SOURCE="HED">PART 366—DESIGNATION OF PROCESS AGENT</HD>
                        <P>18. The authority citation for part 366 is revised to read as follows:</P>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>49 U.S.C. 502, 503, 13303, 13304 and 13908; and 49 CFR 1.73.</P>
                        </AUTH>
                        <P>19. Revise § 366.1 to read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 366.1</SECTNO>
                            <SUBJECT>Applicability.</SUBJECT>
                            <P>These rules, relating to the filing of designations of persons upon whom court or Agency process may be served, govern for-hire and private motor carriers, brokers, freight forwarders and, as of the moment of succession, their fiduciaries (as defined at 49 CFR 387.319(a)).</P>
                            <P>20. Revise § 366. 2 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 366.2</SECTNO>
                            <SUBJECT>Form of designation.</SUBJECT>
                            <P>(a) Designations shall be made on Form BOC-3—Designation of Agents—Motor Carriers, Brokers and Freight Forwarders. Only one completed current form may be on file. It must include all States for which agent designations are required. One copy must be retained by the carrier, broker or freight forwarder at its principal place of business.</P>
                            <P>(b) Private motor carriers and for-hire motor carriers engaged in transportation exempt from economic regulation by FMCSA under 49 U.S.C. chapter 135 that are registered with FMCSA as of [insert effective date of the final rule] must file a Form BOC-3 designation by no later than [insert date 180 days from compliance date of final rule]. Failure to file a designation in accordance with this paragraph will result in deactivation of the carrier's USDOT Number.</P>
                            <P>21. Revise § 366.3 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 366.3</SECTNO>
                            <SUBJECT>Eligible persons.</SUBJECT>
                            <P>All persons (as defined at 49 U.S.C. 13102(18)) designated must reside or maintain an office in the State for which they are designated. If a State official is designated, evidence of his or her willingness to accept service of process must be furnished.</P>
                            <P>22. Amend § 366.4 by revising paragraph (a) and adding a new paragraph (c) to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 366.4 </SECTNO>
                            <SUBJECT>Required States.</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Motor carriers.</E>
                                 Every motor carrier (of property or passengers, including a private carrier) shall make a designation for each State in which it is authorized to operate and for each State traversed during such operations. Every motor carrier (including a private carrier) operating in the United States in the course of transportation between points in a foreign country shall file a designation for each State traversed.
                            </P>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">Freight forwarders.</E>
                                 Every freight forwarder shall make a designation for each State in which its offices are located or in which contracts will be written.
                            </P>
                            <P>23. Revise § 366.5 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 366.5 </SECTNO>
                            <SUBJECT>Blanket designations.</SUBJECT>
                            <P>Where an association or corporation has filed with the FMCSA a list of process agents for each State, motor carriers (including private carriers), brokers and freight forwarders may make the required designations by using the following statement:</P>
                            <P>Those persons named in the list of process agents on file with the Federal Motor Carrier Safety Administration by </P>
                        </SECTION>
                    </PART>
                    <FP SOURCE="FP-DASH"/>
                    <FP>(name of association or corporation) and any subsequently filed revisions thereof, for the States in which this carrier is or may be authorized to operate (or arrange) as an entity of motor vehicle transportation, including States traversed during such operations, except those States for which individual designations are named.</FP>
                    <P>24. Revise § 366.6 to read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 366.6 </SECTNO>
                        <SUBJECT>Cancellation or change.</SUBJECT>
                        <P>
                            (a) A designation may be canceled or changed only by a new designation except that, where a motor carrier (including a private carrier), broker or freight forwarder ceases to be subject to 
                            <PRTPAGE P="66587"/>
                            § 366.4 in whole or in part for 1 year, designation is no longer required and may be canceled without making another designation.
                        </P>
                        <P>(b) A change to a designation, such as name, address, or contact information, must be reported to FMCSA within 20 days of the change.</P>
                    </SECTION>
                    <PART>
                        <HD SOURCE="HED">PART 368—APPLICATION FOR A CERTIFICATE OF REGISTRATION TO OPERATE IN MUNICIPALITIES IN THE UNITED STATES ON THE UNITED STATES-MEXICO INTERNATIONAL BORDER OR WITHIN THE COMMERCIAL ZONES OF SUCH MUNICIPALITIES</HD>
                        <P>25. The authority citation for part 368 is revised to read as follows:</P>
                        <AUTH>
                            <HD SOURCE="HED">Authority: </HD>
                            <P>49 U.S.C. 13301, 13902 and 13908; Pub. L. 106-159, 113 Stat. 1748; and 49 CFR 1.73.</P>
                        </AUTH>
                        <P>26. Amend § 368.3 by revising paragraphs (a), (b), and (f), and removing and reserving paragraph (e), to read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 368.3 </SECTNO>
                            <SUBJECT>Applying for a certificate of registration.</SUBJECT>
                            <P>(a) If you wish to obtain a certificate of registration under this part, you must electronically file an application that includes the following:</P>
                            <P>(1) Form MCSA-1—FMCSA Registration/Update (USDOT Number—(Operating Authority Application).</P>
                            <P>(2) Form BOC-3—Designation of Agents—Motor Carriers, Brokers and Freight Forwarders or indicate on the application that the applicant will use a process agent service that will submit the Form BOC-3 electronically.</P>
                            <P>(b) The FMCSA will only process your application for a Certificate of Registration if it meets the following conditions:</P>
                            <P>(1) The application must be completed in English;</P>
                            <P>(2) The information supplied must be accurate and complete in accordance with the instructions to Form MCSA-1 and Form BOC-3.</P>
                            <P>(3) The application must include all the required supporting documents and applicable certifications set forth in the instructions to Form MCSA-1 and Form BOC-3.</P>
                            <STARS/>
                            <P>(e) [Reserved]</P>
                            <P>
                                (f) Form MCSA-1 is an electronic application and is available, including complete instructions, from the FMCSA Web site at 
                                <E T="03">http://www.fmcsa.dot.gov</E>
                                 (Keyword  “MCSA-1”).
                            </P>
                            <P>27. Amend § 368.4 by revising paragraph (a) to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 368.4 </SECTNO>
                            <SUBJECT>Requirement to notify FMCSA of change in applicant information.</SUBJECT>
                            <P>(a) You must notify FMCSA of any changes or corrections to the information in Section A of Form MCSA-1—FMCSA Registration/Update (USDOT Number—Operating Authority Application), or the Form BOC-3, Designation of Agents-Motor Carriers, Brokers and Freight Forwarders, during the application process or while you have a Certificate of Registration. You must notify FMCSA in writing within 20 days of the change or correction.</P>
                            <STARS/>
                            <P>28. Revise § 368.8 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 368.8 </SECTNO>
                            <SUBJECT>Appeals.</SUBJECT>
                            <P>An applicant has the right to appeal denial of the application. The appeal must be in writing and specify in detail why the Agency's decision to deny the application was wrong. The appeal must be filed with the FMCSA, Office of the Director of Information Technology within 20 days of the date of the letter denying the application. The decision of the Director will be the final Agency order.</P>
                        </SECTION>
                    </PART>
                    <PART>
                        <HD SOURCE="HED">PART 385—SAFETY FITNESS PROCEDURES</HD>
                        <P>29. The authority citation for part 385 is revised to read as follows:</P>
                        <AUTH>
                            <HD SOURCE="HED">Authority: </HD>
                            <P>49 U.S.C. 113, 504, 521(b), 5105(e), 5109, 5113, 13901-13905, 13908, 31136, 31144, 31148, 31151, and 31502; Sec. 350 of Pub. L. 107-87; and 49 CFR 1.73.</P>
                        </AUTH>
                        <P>30. Revise § 385.301 to read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 385.301 </SECTNO>
                            <SUBJECT>What is a motor carrier required to do before beginning interstate operations?</SUBJECT>
                            <P>(a) Before a motor carrier of property or passengers begins interstate operations, it must register with FMCSA and receive a USDOT Number. In addition, for-hire motor carriers must obtain operating authority from FMCSA, unless providing transportation exempt from the Title 49 U.S.C. chapter 139 commercial registration requirements. Both the USDOT Number and operating authority are obtained by following registration procedures described in 49 CFR part 390, subpart C. Title 49 CFR part 365 provides detailed instructions for obtaining operating authority.</P>
                            <P>(b) This subpart applies to motor carriers domiciled in the United States and Canada.</P>
                            <P>(c) The regulations in this subpart do not apply to a Mexico-domiciled motor carrier. A Mexico-domiciled motor carrier of property or passengers must register with FMCSA by following the registration procedures described in 49 CFR parts 365, 368 and 390. Title 49 CFR parts 365 and 368 provide detailed information about how a Mexico-domiciled motor carrier may obtain operating authority.</P>
                            <P>31. Revise § 385.303 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 385.303 </SECTNO>
                            <SUBJECT>How does a motor carrier register with the FMCSA?</SUBJECT>
                            <P>
                                A motor carrier registers with FMCSA by completing Form MCSA-1, which is an electronic application that must be completed on-line at the FMCSA Web site at 
                                <E T="03">http://www.fmcsa.dot.gov</E>
                                 (Keyword “MCSA-1”). Complete instructions for the Form MCSA-1 also are available at the same location.
                            </P>
                            <P>32. Revise § 385.305 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 385.305 </SECTNO>
                            <SUBJECT>What happens after the FMCSA receives a request for new entrant registration?</SUBJECT>
                            <P>
                                (a) The applicant for new entrant registration will be directed to the FMCSA Internet Web site (
                                <E T="03">http://www.fmcsa.dot.gov</E>
                                ) to secure and/or complete the application package online.
                            </P>
                            <P>(b) The application package will include the following:</P>
                            <P>(1) Educational and technical assistance material regarding the requirements of the FMCSRs and HMRs, if applicable.</P>
                            <P>(2) Form MCSA-1—FMCSA Registration/Update (USDOT Number—Operating Authority Application). This form is used to obtain both a USDOT Number and operating authority.</P>
                            <P>(c) Upon completion of the application form, the new entrant will be issued an inactive USDOT Number. An applicant may not begin operations nor mark a commercial motor vehicle with the USDOT Number until after the date of the Agency's written notice that the USDOT Number has been activated. Violations of this section may be subject to the penalties under § 392.9b(b) of this subchapter.</P>
                            <P>(d) For-hire motor carriers, unless providing transportation exempt from the Title 49 U.S.C. chapter 139 commercial registration requirements, must obtain operating authority as prescribed under § 390.105(b) and 49 CFR part 365 of this subchapter before operating in interstate commerce.</P>
                            <P>33. Amend § 385.329 by revising paragraphs (b)(1), (c)(1) and (d) to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 385.329 </SECTNO>
                            <SUBJECT>May a new entrant that has had its USDOT new entrant registration revoked and its operations placed out of service reapply?</SUBJECT>
                            <STARS/>
                            <P>
                                (b) * * *
                                <PRTPAGE P="66588"/>
                            </P>
                            <P>(1) Submit an updated Form MCSA-1.</P>
                            <STARS/>
                            <P>(c) * * *</P>
                            <P>(1) Submit an updated Form MCSA-1.</P>
                            <STARS/>
                            <P>(d) If the new entrant is a for-hire motor carrier subject to the registration provisions of Title 49 U.S.C. chapter 139 and also has had its operating authority revoked, it must re-apply for operating authority as set forth in § 390.105(b) and 49 CFR part 365 of this chapter.</P>
                            <P>34. Revise § 385.405 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 385.405 </SECTNO>
                            <SUBJECT>How does a motor carrier apply for a safety permit?</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Application form.</E>
                                 (1) To apply for a new safety permit or renewal of the safety permit, a motor carrier must complete and submit Form MCSA-1—FMCSA Registration/Update (USDOT Number—Operating Authority Application) and meet the requirements under 49 CFR part 390, subpart C.
                            </P>
                            <P>(2) The Form MCSA-1 also will also satisfy the requirements for obtaining and renewing a USDOT Number.</P>
                            <P>
                                (b) 
                                <E T="03">Where to get forms and instructions.</E>
                                 Form MCSA-1 is an electronic application and is available, including complete instructions, from the FMCSA Web site at 
                                <E T="03">http://www.fmcsa.dot.gov</E>
                                 (Keyword “MCSA-1”).
                            </P>
                            <P>
                                (c) 
                                <E T="03">Signature and certification.</E>
                                 An official of the motor carrier must sign and certify that the information is correct on each form the motor carrier submits.
                            </P>
                            <P>
                                (d) 
                                <E T="03">Updating information.</E>
                                 A motor carrier holding a safety permit must report to FMCSA any change in the information on its Form MCSA-1 within 20 days of the change. The motor carrier must use Form MCSA-1 to report the new information.
                            </P>
                            <P>35. Amend § 385.409 by revising paragraph (a) to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 385.409 </SECTNO>
                            <SUBJECT>When may a temporary safety permit be issued to a motor carrier?</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Temporary safety permit.</E>
                                 If a motor carrier does not meet the criteria of § 385.407(a), FMCSA may issue it a temporary safety permit. To obtain a temporary safety permit a motor carrier must certify on Form MCSA-1 that it is operating in full compliance with the HMRs, with the FMCSRs, and/or comparable State regulations, whichever is applicable; and with the minimum financial responsibility requirements in part 387 of this subchapter or in State regulations, whichever is applicable.
                            </P>
                            <STARS/>
                            <P>36. Revise § 385.419 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 385.419 </SECTNO>
                            <SUBJECT>How long is a safety permit effective?</SUBJECT>
                            <P>Unless suspended or revoked, a safety permit (other than a temporary safety permit) is effective for two years, except that:</P>
                            <P>(a) A safety permit will be subject to revocation if a motor carrier fails to submit a renewal application (Form MCSA-1) in accordance with the schedule set forth for filing Form MCSA-1 in part 390 subpart C of this subchapter; and</P>
                            <P>(b) An existing safety permit will remain in effect pending FMCSA's processing of an application for renewal if a motor carrier submits the required application (Form MCSA-1) in accordance with the schedule set forth in part 390 subpart C of this subchapter.</P>
                            <P>37. Amend § 385.421 by revising paragraphs (a)(1) and (a)(2) to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 385.421 </SECTNO>
                            <SUBJECT>Under what circumstances will a safety permit be subject to revocation or suspension by FMCSA?</SUBJECT>
                            <P>(a) * * *</P>
                            <P>(1) A motor carrier fails to submit a renewal application (Form MCSA-1) in accordance with the schedule set forth in part 390 subpart C of this subchapter.</P>
                            <P>(2) A motor carrier provides any false or misleading information on its application form (Form MCSA-1) or as part of updated information it is providing on Form MCSA-1 (see § 385.405(d)).</P>
                            <STARS/>
                            <P>38. Revise § 385.603 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 385.603 </SECTNO>
                            <SUBJECT>Application.</SUBJECT>
                            <P>(a) Each applicant applying under this subpart must submit an application that consists of:</P>
                            <P>(1) Form MCSA-1, FMCSA Registration/Update (USDOT Number—Operating Authority Application); and</P>
                            <P>(2) A notification of the means used to designate process agents, either by submission in the application package of Form BOC-3, Designation of Agents—Motor Carriers, Brokers and Freight Forwarders, or a letter stating that the applicant will use a process agent service that will submit the Form BOC-3 electronically.</P>
                            <P>(b) The FMCSA will process an application only if it meets the following conditions:</P>
                            <P>(1) The application must be completed in English.</P>
                            <P>(2) The information supplied must be accurate, complete, and include all required supporting documents and applicable certifications in accordance with the instructions to Form MCSA-1 and Form BOC-3.</P>
                            <P>(3) The application must include the filing fee payable to the FMCSA in the amount set forth at 49 CFR 360.3(f)(1).</P>
                            <P>(4) The application must be signed by the applicant.</P>
                            <P>(c) An applicant must electronically file Form MCSA-1.</P>
                            <P>
                                (d) Form MCSA-1 is an electronic application and is available, including complete instructions, from the FMCSA Web site at 
                                <E T="03">http://www.fmcsa.dot.gov</E>
                                 (Keyword “MCSA-1”).
                            </P>
                            <P>39. Amend § 385.607 by revising paragraph (e)(2) to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 385.607 </SECTNO>
                            <SUBJECT>FMCSA action on the application.</SUBJECT>
                            <STARS/>
                            <P>(e) * * *</P>
                            <P>(2) File or have its process agent(s) electronically submit, Form BOC-3—Designation of Agents—Motor Carriers, Brokers and Freight Forwarders, as required by part 366 of this subchapter.</P>
                            <STARS/>
                            <P>40. Amend § 385.609 by revising paragraph (a)(2) and removing paragraph (a)(3) to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 385.609 </SECTNO>
                            <SUBJECT>Requirement to notify FMCSA of change in applicant information.</SUBJECT>
                            <P>(a) * * *</P>
                            <P>(2) A motor carrier subject to this subpart must notify FMCSA of any changes or corrections to the information in Section A of Form MCSA-1 that occur during the application process or after the motor carrier has been granted new entrant registration. The motor carrier must report the changes or corrections within 20 days of the change. The motor carrier must use Form MCSA-1 to report the new information.</P>
                            <STARS/>
                            <P>41. Amend § 385.713 by revising paragraphs (b)(1), (c)(1), and (d) to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 385.713 </SECTNO>
                            <SUBJECT>Reapplying for new entrant registration.</SUBJECT>
                            <STARS/>
                            <P>(b) * * *</P>
                            <P>(1) Submit an updated Form MCSA-1, FMCSA Registration/Update (USDOT Number—Operating Authority Application);</P>
                            <STARS/>
                            <P>(c) * * *</P>
                            <P>(1) Submit an updated Form MCSA-1, FMCSA Registration/Update (USDOT Number—Operating Authority Application);</P>
                            <STARS/>
                            <P>
                                (d) If the new entrant is a for-hire carrier subject to the registration 
                                <PRTPAGE P="66589"/>
                                provisions under 49 U.S.C. 13901 and also has had its operating authority revoked, it must reapply for operating authority as set forth in § 390.105(b) and 49 CFR part 365 of this subchapter.
                            </P>
                        </SECTION>
                    </PART>
                    <PART>
                        <HD SOURCE="HED">PART 387—MINIMUM LEVELS OF FINANCIAL RESPONSIBILITY FOR MOTOR CARRIERS</HD>
                        <P>42. The authority citation for part 387 is revised to read as follows:</P>
                        <AUTH>
                            <HD SOURCE="HED">Authority: </HD>
                            <P>49 U.S.C. 13101, 13301, 13906, 13908, 14701, 31138, and 31139; and 49 CFR 1.73.</P>
                        </AUTH>
                        <P>43. Add § 387.19 to subpart A to read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 387.19 </SECTNO>
                            <SUBJECT>Electronic filing of surety bonds, trust fund agreements, certificates of insurance and cancellations.</SUBJECT>
                            <P>(a) Insurers of exempt motor carriers, as defined in § 390.5 of this subchapter, and private motor carriers that transport hazardous materials in interstate commerce must file certificates of insurance, surety bonds, and other securities and agreements with FMCSA electronically in accordance with the requirements and procedures set forth at § 387.323.</P>
                            <P>(b) The requirements of this section do not apply to motor carriers excepted under § 387.7(b)(3).</P>
                            <P>44. Revise § 387.33 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 387.33 </SECTNO>
                            <SUBJECT>Financial responsibility, minimum levels.</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">General limits.</E>
                                 The minimum levels of financial responsibility referred to in § 387.31 of this subpart are hereby prescribed as follows:
                            </P>
                            <HD SOURCE="HD1">Schedule of Limits</HD>
                            <HD SOURCE="HD2">Public Liability</HD>
                            <P>For-hire motor carriers of passengers operating in interstate or foreign commerce.</P>
                            <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s30,10">
                                <TTITLE> </TTITLE>
                                <BOXHD>
                                    <CHED H="1">Vehicle seating capacity</CHED>
                                    <CHED H="1">Minimum limits</CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="01">
                                        (1) Any vehicle with a seating capacity of 16 passengers or more, including the driver 
                                        <SU>1</SU>
                                    </ENT>
                                    <ENT>$5,000,000</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">
                                        (2) Any vehicle with a seating capacity of 15 passengers or less, including the driver 
                                        <SU>2</SU>
                                    </ENT>
                                    <ENT>1,500,000</ENT>
                                </ROW>
                                <TNOTE>
                                    <E T="51">1 2</E>
                                     Except as provided in § 387.27(b).
                                </TNOTE>
                            </GPOTABLE>
                            <P>
                                (b) 
                                <E T="03">Limits applicable to transit service providers.</E>
                                 Notwithstanding the provisions of paragraph (a) of this section, the minimum level of financial responsibility for a motor vehicle used to provide transportation services within a transit service area located in more than one State under an agreement with a Federal, State, or local government funded, in whole or in part, with a grant under 49 U.S.C. 5307, 5310 or 5311, including transportation designed and carried out to meet the special needs of elderly individuals and individuals with disabilities, will be the highest level required for any of the States in which it operates. Transit service providers conducting such operations must register as for-hire passenger carriers under part 390, subpart C of this subchapter, identify the States in which they operate under the applicable grants, and certify on their registration documents that they have in effect financial responsibility levels in an amount equal to or greater than the highest level required by any of the States in which they are operating under a qualifying grant.
                            </P>
                            <P>45. Amend § 387.39 by revising Form MCS-90B to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 387.39 </SECTNO>
                            <SUBJECT>Forms.</SUBJECT>
                            <STARS/>
                            <BILCOD>BILLING CODE 4910-EX-P</BILCOD>
                            <GPH SPAN="3" DEEP="600">
                                <PRTPAGE P="66590"/>
                                <GID>EP26OC11.065</GID>
                            </GPH>
                            <BILCOD>BILLING CODE 4910-EX-C</BILCOD>
                            <PRTPAGE P="66591"/>
                            <STARS/>
                            <P>46. Add § 387.43 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 387.43 </SECTNO>
                            <SUBJECT>Electronic filing of surety bonds, trust fund agreements, certificates of insurance and cancellations.</SUBJECT>
                            <P>(a) Insurers of for-hire motor carriers of passengers must file certificates of insurance, surety bonds, and other securities and agreements electronically in accordance with the requirements and procedures set forth at § 387.323.</P>
                            <P>(b) This section does not apply to motor carriers excepted under § 387.31(b)(3).</P>
                            <P>47. Amend § 387.303 by revising paragraph (b) to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 387.303 </SECTNO>
                            <SUBJECT>Security for the protection of the public: Minimum limits.</SUBJECT>
                            <STARS/>
                            <P>(b)(1) Motor carriers subject to § 387.303(a)(1) are required to have security for the required minimum limits as follows:</P>
                            <P>
                                (i) 
                                <E T="03">Small freight vehicles:</E>
                            </P>
                            <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,r100,14">
                                <TTITLE> </TTITLE>
                                <BOXHD>
                                    <CHED H="1">Kind of equipment</CHED>
                                    <CHED H="1">Transportation provided</CHED>
                                    <CHED H="1">
                                        Minimum 
                                        <LI>limits</LI>
                                    </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="01">Fleet including only vehicles under 10,001 pounds (4,536 kilograms) GVWR</ENT>
                                    <ENT>Property (non-hazardous)</ENT>
                                    <ENT>$300,000</ENT>
                                </ROW>
                            </GPOTABLE>
                            <P>
                                (ii) 
                                <E T="03">Passenger carriers:</E>
                            </P>
                            <GPOTABLE COLS="2" OPTS="L2,il" CDEF="s200,14">
                                <TTITLE>Passenger Carriers: Kind of Equipment</TTITLE>
                                <BOXHD>
                                    <CHED H="1">Vehicle seating capacity</CHED>
                                    <CHED H="1">
                                        Minimum 
                                        <LI>limits</LI>
                                    </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="01">(A) Any vehicle with a seating capacity of 16 passengers or more (including the driver)</ENT>
                                    <ENT>$5,000,000</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">(B) Any vehicle designed or used to transport 15 passengers or less (including the driver) for compensation </ENT>
                                    <ENT>1,500,000</ENT>
                                </ROW>
                            </GPOTABLE>
                            <P> (2) Motor carriers subject to § 387.301(a)(2) are required to have security for the required minimum limits as follows:</P>
                            <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,r100,14">
                                <TTITLE> </TTITLE>
                                <BOXHD>
                                    <CHED H="1">Kind of equipment</CHED>
                                    <CHED H="1">Commodity transported</CHED>
                                    <CHED H="1">
                                        Minimum
                                        <LI>limits</LI>
                                    </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="01">(i) Freight vehicles of 10,001 pounds (4,536 kilograms) or more GVWR</ENT>
                                    <ENT>Property (non-hazardous)</ENT>
                                    <ENT>$750,000</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">(ii) Freight vehicles of 10,001 pounds (4,536 kilograms) or more GVWR</ENT>
                                    <ENT>Hazardous substances, as defined in § 171.8 of this title, transported in cargo tanks, portable tanks, or hopper-type vehicles with capacities in excess of 3,500 water gallons, or in bulk explosives Division 1,1, 1.2 and 1.3 materials. Division 2.3, Hazard Zone A material; in bulk Division 2.1 or 2.2; or highway route controlled quantities of a Class 7 material, as defined in § 173.403 of this title</ENT>
                                    <ENT>5,000,000</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">(iii) Freight vehicles of 10,001 pounds (4,536 kilograms) or more GVWR</ENT>
                                    <ENT>Oil listed in § 172.101 of this title; hazardous waste, hazardous materials and hazardous substances defined in § 171.8 of this title and listed in § 172.101 of this title, but not mentioned in (b) above or (d) below</ENT>
                                    <ENT>1,000,000</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">(iv) Freight vehicles under 10,001 pounds (4,536 kilograms) GVWR</ENT>
                                    <ENT>Any quantity of Division 1.1, 1.2, or 1.3 material; any quantity of a Division 2.3, Hazard Zone A, or Division 6.1, Packing Group I, Hazard Zone A material; or highway route controlled quantities of Class 7 material as defined in § 173.455 of this title</ENT>
                                    <ENT>5,000,000</ENT>
                                </ROW>
                            </GPOTABLE>
                            <STARS/>
                            <P>48. Amend § 387.313 by revising paragraphs (b) and (d) to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 387.313</SECTNO>
                            <SUBJECT>Forms and procedures.</SUBJECT>
                            <STARS/>
                            <P>
                                (b) 
                                <E T="03">Filing and copies.</E>
                                 Certificates of insurance, surety bonds, and notices of cancellation must be filed with the FMCSA.
                            </P>
                            <STARS/>
                            <P>
                                (d) 
                                <E T="03">Cancellation notice.</E>
                                 Except as provided in paragraph (e) of this section, surety bonds, certificates of insurance and other securities or agreements shall not be cancelled or withdrawn until 30 days after written notice has been submitted to 
                                <E T="03">http://fmcsa.dot.gov</E>
                                 on the prescribed form (Form BMC-35, Notice of Cancellation Motor Carrier Policies of Insurance under 49 U.S.C. 13906, and BMC-36, Notice of Cancellation Motor Carrier and Broker Surety Bonds, as appropriate) by the insurance company, surety or sureties, motor carrier, broker or other party thereto, as the case may be, which period of thirty (30) days shall commence to run from the date such notice on the prescribed form is filed with FMCSA at 
                                <E T="03">http://fmcsa.dot.gov.</E>
                            </P>
                            <STARS/>
                            <P>49. Revise § 387.323 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 387.323</SECTNO>
                            <SUBJECT>Electronic filing of surety bonds, trust fund agreements, certificates of insurance and cancellations.</SUBJECT>
                            <P>(a) Insurers must electronically file forms BMC 34, BMC 35, BMC 36, BMC 82, BMC 83, BMC 84, BMC 85, BMC 91, and BMC 91X in accordance with the requirements and procedures set forth in paragraphs (b) through (d) of this section.</P>
                            <P>
                                (b) Each insurer must obtain authorization to file electronically by registering with the FMCSA. An individual account number and 
                                <PRTPAGE P="66592"/>
                                password for computer access will be issued to each registered insurer.
                            </P>
                            <P>
                                (c) Filings must be transmitted online via the Internet at 
                                <E T="03">http://fmcsa.dot.gov.</E>
                            </P>
                            <P>(d) All registered insurers agree to furnish upon request to the FMCSA a copy of any policy (or policies) and all certificates of insurance, endorsements, surety bonds, trust fund agreements, proof of qualification to self-insure or other insurance filings.</P>
                            <P>50. Revise § 387.403 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 387.403</SECTNO>
                            <SUBJECT>General requirements.</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Cargo.</E>
                                 A household goods freight forwarder may not operate until it has filed with FMCSA an appropriate surety bond, certificate of insurance, qualifications as a self-insurer, or other securities or agreements, in the amounts prescribed at § 387.405, for loss of or damage to household goods.
                            </P>
                            <P>
                                (b) 
                                <E T="03">Public liability.</E>
                                 A freight forwarder may not perform transfer, collection, and delivery service until it has filed with the FMCSA an appropriate surety bond, certificate of insurance, qualifications as a self-insurer, or other securities or agreements, in the amounts prescribed at § 387.405, conditioned to pay any final judgment recovered against such freight forwarder for bodily injury to or the death of any person, or loss of or damage to property (except cargo) of others, or, in the case of freight vehicles described at 49 CFR 387.303(b)(2), for environmental restoration, resulting from the negligent operation, maintenance, or use of motor vehicles operated by or under its control in performing such service.
                            </P>
                            <P>51. Amend § 387.413 by revising paragraph (b) to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 387.413</SECTNO>
                            <SUBJECT>Forms and procedures.</SUBJECT>
                            <STARS/>
                            <P>
                                (b) 
                                <E T="03">Procedure.</E>
                                 Certificates of insurance, surety bonds, and notices of cancellation must be electronically filed with the FMCSA.
                            </P>
                            <STARS/>
                            <P>52. Revise § 387.419 to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 387.419</SECTNO>
                            <SUBJECT>Electronic filing of surety bonds, certificates of insurance and cancellations.</SUBJECT>
                            <P>Insurers must electronically file certificates of insurance, surety bonds, and other securities and agreements and notice of cancellation in accordance with the requirements and procedures set forth at § 387.323.</P>
                        </SECTION>
                    </PART>
                    <PART>
                        <HD SOURCE="HED">PART 390—FEDERAL MOTOR CARRIER SAFETY REGULATIONS; GENERAL</HD>
                        <P>53. The authority citation for part 390 is revised to read as follows:</P>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>49 U.S.C. 508, 13301, 13902, 13908, 31132, 31133, 31136, 31502, 31504; sec. 114, Pub. L. 103-311, 108 Stat. 1673, 1677; secs. 217, 229; Pub. L. 106-159, 113 Stat. 1748, 1767, 1773; and 49 CFR 1.73.</P>
                        </AUTH>
                        <P>54. Revise § 390.3 to read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 390.3</SECTNO>
                            <SUBJECT>General applicability.</SUBJECT>
                            <P>(a) The rules in subchapter B of this chapter are applicable to all employers, employees, and commercial motor vehicles, which transport property or passengers in interstate commerce.</P>
                            <P>(b) The rules in part 383, Commercial Driver's License Standards; Requirements and Penalties, are applicable to every person who operates a commercial motor vehicle, as defined in § 383.5 of this subchapter, in interstate or intrastate commerce and to all employers of such persons.</P>
                            <P>(c) The rules in part 387, Minimum Levels of Financial Responsibility for Motor Carriers, are applicable to motor carriers as provided in § 387.3 or § 387.27 of this subchapter.</P>
                            <P>
                                (d) 
                                <E T="03">Additional requirements.</E>
                                 Nothing in subchapter B of this chapter shall be construed to prohibit an employer from requiring and enforcing more stringent requirements relating to safety of operation and employee safety and health.
                            </P>
                            <P>
                                (e) 
                                <E T="03">Knowledge of and compliance with the regulations.</E>
                                 (1) Every employer shall be knowledgeable of and comply with all regulations contained in this subchapter which are applicable to that motor carrier's operations.
                            </P>
                            <P>(2) Every driver and employee shall be instructed regarding, and shall comply with, all applicable regulations contained in this subchapter.</P>
                            <P>(3) All motor vehicle equipment and accessories required by this subchapter shall be maintained in compliance with all applicable performance and design criteria set forth in this subchapter.</P>
                            <P>
                                (f) 
                                <E T="03">Exceptions.</E>
                                 Unless otherwise specifically provided, the rules in this subchapter do not apply to—
                            </P>
                            <P>(1) All school bus operations as defined in § 390.5;</P>
                            <P>(2) Transportation performed by the Federal government, a State, or any political subdivision of a State, or an agency established under a compact between States that has been approved by the Congress of the United States;</P>
                            <P>(3) The occasional transportation of personal property by individuals not for compensation and not in the furtherance of a commercial enterprise;</P>
                            <P>(4) The transportation of human corpses or sick and injured persons;</P>
                            <P>(5) The operation of fire trucks and rescue vehicles while involved in emergency and related operations;</P>
                            <P>(6) The operation of commercial motor vehicles designed or used to transport between 9 and 15 passengers (including the driver), not for direct compensation, provided the vehicle does not otherwise meet the definition of a commercial motor vehicle, except that motor carriers operating such vehicles are required to comply with §§ 390.15, 390.21(a) and (b)(2), 390.101 and 390.103.</P>
                            <P>(7) Either a driver of a commercial motor vehicle used primarily in the transportation of propane winter heating fuel or a driver of a motor vehicle used to respond to a pipeline emergency, if such regulations would prevent the driver from responding to an emergency condition requiring immediate response as defined in § 390.5.</P>
                            <P>
                                (g) 
                                <E T="03">Motor carriers that transport hazardous materials in intrastate commerce.</E>
                                 The rules in the following provisions of subchapter B of this chapter apply to motor carriers that transport hazardous materials in intrastate commerce and to the motor vehicles that transport hazardous materials in intrastate commerce:
                            </P>
                            <P>(1) Part 385, subparts A and E, for carriers subject to the requirements of § 385.403 of this subchapter.</P>
                            <P>(2) Part 386, Rules of Practice for Motor Carrier, Intermodal Equipment Provider, Broker, Freight Forwarder, and Hazardous Materials Proceedings, of this subchapter.</P>
                            <P>(3) Part 387, Minimum Levels of Financial Responsibility for Motor Carriers, to the extent provided in § 387.3 of this subchapter.</P>
                            <P>(4) Subpart C of this part, Unified Registration System, and § 390.21, Marking of CMVs, for carriers subject to the requirements of § 385.403 of this subchapter. Intrastate motor carriers operating prior to January 1, 2005, are excepted from § 390.101.</P>
                            <P>
                                (h) 
                                <E T="03">Intermodal equipment providers.</E>
                                 The rules in the following provisions of subchapter B of this chapter apply to intermodal equipment providers:
                            </P>
                            <P>(1) Subpart F, Intermodal Equipment Providers, of Part 385, Safety Fitness Procedures.</P>
                            <P>(2) Part 386, Rules of Practice for Motor Carrier, Intermodal Equipment Provider, Broker, Freight Forwarder, and Hazardous Materials Proceedings.</P>
                            <P>(3) Part 390, Federal Motor Carrier Safety Regulations; General, except § 390.15(b) concerning accident registers.</P>
                            <P>(4) Part 393, Parts and Accessories Necessary for Safe Operation.</P>
                            <P>(5) Part 396, Inspection, Repair, and Maintenance.</P>
                            <P>
                                (i) 
                                <E T="03">Brokers.</E>
                                 The rules in the following provisions of subchapter B of this chapter apply to brokers that are 
                                <PRTPAGE P="66593"/>
                                required to register with the Agency pursuant to 49 U.S.C. chapter 139.
                            </P>
                            <P>(1) Part 386, Rules of Practice for Motor Carrier, Intermodal Equipment Provider, Broker, Freight Forwarder, and Hazardous Materials Proceedings.</P>
                            <P>(2) Part 387, Minimum Levels of Financial Responsibility for Motor Carriers, to the extent provided in subpart C.</P>
                            <P>(3) Subpart C of this part, Unified Registration System</P>
                            <P>
                                (j) 
                                <E T="03">Freight forwarders.</E>
                                 The rules in the following provisions of subchapter B of this chapter apply to freight forwarders that are required to register with the Agency pursuant to 49 U.S.C. chapter 139.
                            </P>
                            <P>(1) Part 386, Rules of Practice for Motor Carrier, Intermodal Equipment Provider, Broker, Freight Forwarder, and Hazardous Materials Proceedings.</P>
                            <P>(2) Part 387, Minimum Levels of Financial Responsibility for Motor Carriers, to the extent provided in subpart D of this part.</P>
                            <P>(3) Subchapter C of this part, Unified Registration System.</P>
                            <P>
                                (k)
                                <E T="03"> Cargo tank facilities.</E>
                                 The rules in Subpart C of this part, Unified Registration System, apply to each cargo tank and cargo tank motor vehicle manufacturer, assembler, repairer, inspector, tester, and design certifying engineer that is subject to registration requirements under 49 CFR 107.502 and 49 U.S.C. 5108.
                            </P>
                            <P>55. Amend § 390.5 by revising the definition of “Exempt motor carrier” to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 390.5</SECTNO>
                            <SUBJECT>Definitions.</SUBJECT>
                            <STARS/>
                            <P>
                                <E T="03">Exempt motor carrier</E>
                                 means a person engaged in transportation exempt from economic regulation by the Federal Motor Carrier Safety Administration (FMCSA) under 49 U.S.C. chapter 135. “Exempt motor carriers” are subject to the safety regulations set forth in this subchapter.
                            </P>
                            <STARS/>
                            <P>56. Revise § 390.19 to read follows.</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 390.19</SECTNO>
                            <SUBJECT>Motor carrier identification reports for certain Mexico-domiciled motor carriers.</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Applicability.</E>
                                 A Mexico-domiciled motor carrier requesting authority to provide transportation of property or passengers in interstate commerce between Mexico and points in the United States beyond the municipalities and commercial zones along the United Sates-Mexico international border must file Form MCS-150 with FMCSA as follows:
                            </P>
                            <P>
                                (b) 
                                <E T="03">Filing schedule.</E>
                                 Each motor carrier must file the appropriate form under paragraph (a) of this section at the following times:
                            </P>
                            <P>(1) Before it begins operations; and</P>
                            <P>(2) Every 24 months, according to the following schedule:</P>
                            <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s30,r30">
                                <TTITLE> </TTITLE>
                                <BOXHD>
                                    <CHED H="1" O="L">
                                        USDOT No. ending 
                                        <LI>in . . . </LI>
                                    </CHED>
                                    <CHED H="1" O="L">
                                        Must file by last 
                                        <LI>day of . . . </LI>
                                    </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="01">1</ENT>
                                    <ENT>January.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">2</ENT>
                                    <ENT>February.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">3</ENT>
                                    <ENT>March.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">4</ENT>
                                    <ENT>April.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">5</ENT>
                                    <ENT>May.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">6</ENT>
                                    <ENT>June.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">7</ENT>
                                    <ENT>July.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">8</ENT>
                                    <ENT>August.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">9</ENT>
                                    <ENT>September.</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">0</ENT>
                                    <ENT>October.</ENT>
                                </ROW>
                            </GPOTABLE>
                            <P>(3) If the next-to-last digit of its USDOT Number is odd, the motor carrier shall file its update in every odd-numbered calendar year. If the next-to-last digit of the USDOT Number is even, the motor carrier shall file its update in every even-numbered calendar year.</P>
                            <P>
                                (c) 
                                <E T="03">Availability of forms.</E>
                                 The Form MCS-150 and complete instructions are available from the FMCSA Web site at 
                                <E T="03">http://www.fmcsa.dot.gov</E>
                                 (Keyword “MCS-150”); from all FMCSA Service Centers and Division offices nationwide; or by calling 1-800-832-5660.
                            </P>
                            <P>
                                (d) 
                                <E T="03">Where to file.</E>
                                 The Form MCS-150 must be filed with FMCSA Office of Information Management. The form may be filed electronically according to the instructions at the Agency's Web site, or it may be sent to Federal Motor Carrier Safety Administration, Office of Information Management, MC-RIO, 1200 New Jersey Avenue, SE., Washington, DC 20590.
                            </P>
                            <P>
                                (e) 
                                <E T="03">Special instructions.</E>
                                 A motor carrier should submit the Form MCS-150 along with its application for operating authority (OP-1(MX)), to the appropriate address referenced on that form, or may submit it electronically or by mail separately to the address mentioned in paragraph (d) of this section.
                            </P>
                            <P>(f) Only the legal name or a single trade name of the motor carrier may be used on the Form MCS-150.</P>
                            <P>(g) A motor carrier that fails to file the Form MCS-150 or furnishes misleading information or makes false statements upon the form, is subject to the penalties prescribed in 49 U.S.C. 521(b)(2)(B).</P>
                            <P>(h)(1) Upon receipt and processing of the form described in paragraph (a) of this section, FMCSA will issue the motor carrier or intermodal equipment provider an identification number (USDOT Number).</P>
                            <P>(2) A Mexico-domiciled motor carrier seeking to provide transportation of property or passengers in interstate commerce between Mexico and points in the United States beyond the municipalities and commercial zones along the United States-Mexico international border must pass the pre-authorization safety audit under § 365.507 of this subchapter. The Agency will not issue a USDOT Number until expiration of the protest period provided in § 365.115 of this subchapter or—if a protest is received—after FMCSA denies or rejects the protest.</P>
                            <P>(3) The motor carrier must display the number on each self-propelled CMV, as defined in § 390.5, along with the additional information required by § 390.21.</P>
                            <P>57a. Redesignate subpart C, consisting of §§ 390.40, 390.42, 390.44, and 390.46, as subpart D, consisting of §§ 390.201, 390.203, 390.205, and 390.207.</P>
                            <P>57b. Add a new subpart C to read as follows:</P>
                            <CONTENTS>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart C—Unified Registration System</HD>
                                    <SECHD>Sec.</SECHD>
                                    <SECTNO>390.101 </SECTNO>
                                    <SUBJECT>USDOT Registration.</SUBJECT>
                                    <SECTNO>390.102 </SECTNO>
                                    <SUBJECT>PRISM State registration/biennial updates.</SUBJECT>
                                    <SECTNO>390.103 </SECTNO>
                                    <SUBJECT>Special requirements for registration.</SUBJECT>
                                    <SECTNO>390.105 </SECTNO>
                                    <SUBJECT>Other governing regulations.</SUBJECT>
                                    <SECTNO>390.107 </SECTNO>
                                    <SUBJECT>Pre-authorization safety audit.</SUBJECT>
                                </SUBPART>
                            </CONTENTS>
                        </SECTION>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart C—Unified Registration System</HD>
                            <SECTION>
                                <SECTNO>§ 390.101 </SECTNO>
                                <SUBJECT>USDOT Registration.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Purpose.</E>
                                     This section establishes who must register with FMCSA under the Unified Registration System, the filing schedule, and general information pertaining to persons subject to the Unified Registration System registration requirements.
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Applicability.</E>
                                     (1) Except as provided in paragraph (g) of this section, each motor carrier (including a private motor carrier, an exempt for-hire motor carrier, a non-exempt for-hire motor carrier, and a motor carrier of passengers that participates in a through ticketing arrangement with one or more interstate for-hire motor carriers of passengers), intermodal equipment provider, broker and freight forwarder subject to the requirements of 49 CFR chapter III, subchapter B must file Form MCSA-1 with FMCSA in order to:
                                </P>
                                <P>(i) Identify its operations with the Federal Motor Carrier Safety Administration for safety oversight, as authorized under 49 U.S.C. 31144, as applicable;</P>
                                <P>(ii) Obtain operating authority required under Title 49 U.S.C. chapter 139, as applicable; and</P>
                                <P>
                                    (iii) Obtain a hazardous materials safety permit as required under 49 U.S.C. 5109, as applicable.
                                    <PRTPAGE P="66594"/>
                                </P>
                                <P>(2) A cargo tank and cargo tank motor vehicle manufacturer, assembler, repairer, inspector, tester, and design certifying engineer that is subject to registration requirements under 49 CFR 107.502 and 49 U.S.C. 5108 must satisfy those requirements by electronically filing Form MCSA-1 with FMCSA.</P>
                                <P>
                                    (c) 
                                    <E T="03">General.</E>
                                     (1)(i) A person that fails to file Form MCSA-1 pursuant to paragraph (d)(1) of this section is subject to the penalties prescribed in 49 U.S.C. 521(b)(2)(B) or 49 U.S.C. 14901(a), as appropriate.
                                </P>
                                <P>(ii) A person that fails to complete biennial updates to the information on Form MCSA-1 pursuant to paragraph (d)(2) of this section is subject to the penalties prescribed in 49 U.S.C. 521(b)(2)(B) or 49 U.S.C. 14901(a), as appropriate, and inactivation of its USDOT Number.</P>
                                <P>(iii) A person that furnishes misleading information or makes false statements upon Form MCSA-1 is subject to the penalties prescribed in 49 U.S.C. 521(b)(2)(B), 49 U.S.C. 14901(a) or 49 U.S.C. 14907, as appropriate.</P>
                                <P>(2) Upon receipt and processing of Form MCSA-1, FMCSA will issue the applicant an inactive identification number (USDOT Number). FMCSA will activate the USDOT Number after completion of applicable administrative filings pursuant to § 390.103(a) of this chapter, unless the applicant is subject to § 390.103(b). An applicant may not begin operations nor mark a commercial motor vehicle with the USDOT Number until after the date of the Agency's written notice that the USDOT Number has been activated.</P>
                                <P>(3) The motor carrier must display a valid USDOT Number on each self-propelled CMV, as defined in § 390.5, along with the additional information required by § 390.21.</P>
                                <P>
                                    (d) 
                                    <E T="03">Filing schedule.</E>
                                     Each person listed under paragraph (b) of this section must electronically file Form MCSA-1 at the following times:
                                </P>
                                <P>(1) Before it begins operations; and</P>
                                <P>(2) Every 24 months as prescribed in paragraph (d)(3) or (d)(4) of this section, as applicable.</P>
                                <P>(3) Persons assigned a USDOT Number prior to [Insert final rule compliance date] must file an updated Form MCSA-1 every 24 months, according to the following schedule:</P>
                                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s30,r30">
                                    <TTITLE> </TTITLE>
                                    <BOXHD>
                                        <CHED H="1" O="L">
                                            USDOT No. ending 
                                            <LI>in . . .</LI>
                                        </CHED>
                                        <CHED H="1" O="L">
                                            Must file by last 
                                            <LI>day of . . .</LI>
                                        </CHED>
                                    </BOXHD>
                                    <ROW>
                                        <ENT I="01">1</ENT>
                                        <ENT>January.</ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="01">2</ENT>
                                        <ENT>February.</ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="01">3</ENT>
                                        <ENT>March.</ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="01">4</ENT>
                                        <ENT>April.</ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="01">5</ENT>
                                        <ENT>May.</ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="01">6</ENT>
                                        <ENT>June.</ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="01">7</ENT>
                                        <ENT>July.</ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="01">8</ENT>
                                        <ENT>August.</ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="01">9</ENT>
                                        <ENT>September.</ENT>
                                    </ROW>
                                    <ROW>
                                        <ENT I="01">0</ENT>
                                        <ENT>October.</ENT>
                                    </ROW>
                                </GPOTABLE>
                                <FP>If the next-to-last digit of its USDOT Number is odd, the person must file its update in every odd-numbered calendar year. If the next-to-last digit of the USDOT Number is even, the person must file its update in every even-numbered calendar year.</FP>
                                <P>(4) Persons assigned a USDOT Number on or after [Insert final rule compliance date] must file an updated Form MCSA-1 every 24 months, according to the date of Agency's written notice that the USDOT Number has been activated pursuant to § 390.101(c)(2).</P>
                                <P>
                                    (5) 
                                    <E T="03">When there is a change in legal name, form of business, or address.</E>
                                     A registered entity must notify the Agency of a change in legal name, form of business, or address within 20 days of the change by filing an updated Form MCSA-1 reflecting the revised information.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Availability of form.</E>
                                     Form MCSA-1 is an electronic application and is available, including complete instructions, from the FMCSA Web site at 
                                    <E T="03">http://www.fmcsa.dot.gov</E>
                                     (Keyword “MCSA-1”).
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Where to file.</E>
                                     Persons subject to the registration requirements under this subpart must electronically file Form MCSA-1 on the FMCSA Web site at 
                                    <E T="03">http://www.fmcsa.dot.gov.</E>
                                </P>
                                <P>
                                    (g) 
                                    <E T="03">Exception.</E>
                                     The rules in this subpart do not govern the application by a Mexico-domiciled motor carrier to provide transportation of property or passengers in interstate commerce between Mexico and points in the United States beyond the municipalities and commercial zones along the United States-Mexico international border. The applicable procedures governing transportation by Mexico-domiciled motor carriers are provided in § 390.19 of this subchapter.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 390.102 </SECTNO>
                                <SUBJECT>PRISM State registration/biennial updates.</SUBJECT>
                                <P>(a) A motor carrier that registers its vehicles in a State that participates in the Performance and Registration Information Systems Management (PRISM) program (authorized under section 4004 of the Transportation Equity Act for the 21st Century [Pub. L. 105-178, 112 Stat. 107]) alternatively may satisfy the requirements set forth in § 390.101 by electronically filing all the required USDOT registration and biennial update information with the State Driver Licensing Agency (SDLA) according to its policies and procedures, provided the SDLA has integrated the USDOT registration/update capability into its vehicle registration program.</P>
                                <P>(b) If the SDLA procedures do not allow a motor carrier to file the Form MCSA-1 or to submit updates within the periods specified in § 390.101(a)(2), a motor carrier must complete such filings directly with FMCSA.</P>
                                <P>(c) A for-hire motor carrier, unless providing transportation exempt from Title 49 U.S.C. chapter 139 commercial registration requirements, must obtain operating authority as prescribed under § 390.105(b) and 49 CFR part 365 of this chapter before operating in interstate commerce.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 390.103 </SECTNO>
                                <SUBJECT>Special requirements for registration.</SUBJECT>
                                <P>
                                    (a)(1) 
                                    <E T="03">General.</E>
                                     A person applying to operate as a motor carrier, broker or freight forwarder under this subpart must make the additional filings described in paragraphs (a)(2) and (a)(3) of this section as a condition for registration under this subpart within 90 days of the date on which the application is filed:
                                </P>
                                <P>
                                    (2) 
                                    <E T="03">Evidence of financial responsibility.</E>
                                     (i) A person that registers to conduct operations in interstate commerce as a for-hire motor carrier, a broker or a freight forwarder must file evidence of financial responsibility as required under part 387, subparts C and D of this subchapter.
                                </P>
                                <P>(ii) A person that registers to transport hazardous materials as defined in § 383.5 of this subchapter in interstate commerce must file evidence of financial responsibility as required under part 387, subpart C of this subchapter.</P>
                                <P>
                                    (3) 
                                    <E T="03">Designation of agent for service of process.</E>
                                     All motor carriers (both private and for-hire), brokers and freight forwarders required to register under this subpart must designate an agent for service of process (a person upon whom court or Agency process may be served) following the rules in part 366 of this subchapter:
                                </P>
                                <P>(b) The Agency will not activate a USDOT Number until expiration of the protest period provided in § 365.115 of this subchapter or—if a protest is received—after FMCSA denies or rejects the protest, as applicable.</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 390.105 </SECTNO>
                                <SUBJECT>Other governing regulations.</SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Motor carriers.</E>
                                     (1) A motor carrier granted registration under this part must successfully complete the applicable New Entrant Safety Assurance Program as described in paragraphs (a)(1)(i) 
                                    <PRTPAGE P="66595"/>
                                    through (a)(1)(iv) of this section as a condition for permanent registration:
                                </P>
                                <P>(i) A U.S.- or Canada-domiciled motor carrier is subject to the new entrant safety assurance program under 49 CFR part 385, subpart D.</P>
                                <P>(ii) A Mexico-domiciled motor carrier is subject to the safety monitoring program under 49 CFR part 385, subpart B.</P>
                                <P>(iv) A Non-North America-domiciled motor carrier is subject to the safety monitoring program under 49 CFR part 385, subpart I.</P>
                                <P>(2) [Reserved]</P>
                                <P>
                                    (b) 
                                    <E T="03">Brokers, freight forwarders and non-exempt for-hire motor carriers.</E>
                                     (1) A broker or freight forwarder must obtain operating authority pursuant to part 365 of this subchapter as a condition for obtaining USDOT Registration.
                                </P>
                                <P>(2) A motor carrier registering to engage in transportation that is not exempt from economic regulation by FMCSA must obtain operating authority pursuant to part 365 of this subchapter as a condition for obtaining USDOT Registration.</P>
                                <P>
                                    (c) 
                                    <E T="03">Intermodal equipment providers.</E>
                                     An intermodal equipment provider is subject to the requirements of subpart D of this part.
                                </P>
                                <P>(1) Only the legal name or a single trade name of the motor carrier or intermodal equipment provider may be used on the Form MCSA-1.</P>
                                <P>(2) The intermodal equipment provider must identify each unit of interchanged intermodal equipment by its assigned USDOT Number.</P>
                                <P>
                                    (d) 
                                    <E T="03">Hazardous materials safety permit applicants.</E>
                                     A person who applies for a hazardous materials safety permit is subject to the requirements of part 385, subpart E of this subchapter.
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Cargo tank facilities.</E>
                                     A cargo tank facility is subject to the requirements of 49 CFR part 107, subpart F, 49 CFR part 172, subpart H, and 49 CFR part 180.
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 390.107 </SECTNO>
                                <SUBJECT>Pre-authorization safety audit.</SUBJECT>
                                <P>A non-North America-domiciled motor carrier seeking to provide transportation of property or passengers in interstate commerce within the United States must pass the pre-authorization safety audit under § 385.607(c) of this subchapter as a condition for receiving registration under this part.</P>
                                <P>58. Amend newly redesignated § 390.201 by revising paragraph (a) to read as follows:</P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 390.201 </SECTNO>
                                <SUBJECT>What responsibilities do intermodal equipment providers have under the Federal Motor Carrier Safety Regulations (49 CFR parts 350-399)?</SUBJECT>
                                <STARS/>
                                <P>(a) Identify its operations to the FMCSA by filing the Form MCSA-1 required by § 390.101.</P>
                                <STARS/>
                            </SECTION>
                        </SUBPART>
                    </PART>
                    <PART>
                        <HD SOURCE="HED">PART 392—DRIVING OF COMMERCIAL MOTOR VEHICLES</HD>
                        <P>59. The authority citation for part 392 is revised to read as follows:</P>
                        <AUTH>
                            <HD SOURCE="HED">Authority: </HD>
                            <P>49 U.S.C. 521, 13902, 13908, 31136, 31502; and 49 CFR 1.73.</P>
                        </AUTH>
                        <P>60. Add § 392.9b to read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 392.9b </SECTNO>
                            <SUBJECT>USDOT Registration.</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">USDOT Registration required.</E>
                                 A motor vehicle providing transportation must not be operated without a USDOT Registration and an active USDOT Number.
                            </P>
                            <P>
                                (b) 
                                <E T="03">Penalties.</E>
                                 If it is determined that the motor carrier responsible for the operation of such a vehicle is operating in violation of paragraph (a) of this section, it may be subject to penalties in accordance with 49 U.S.C. 521 and inactivation of its USDOT Number.
                            </P>
                        </SECTION>
                        <SIG>
                            <DATED>Issued on: October 11, 2011.</DATED>
                            <NAME>Anne S. Ferro,</NAME>
                            <TITLE>Administrator.</TITLE>
                        </SIG>
                    </PART>
                </SUPLINF>
                <FRDOC>[FR Doc. 2011-26958 Filed 10-25-11; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 4910-EX-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>76</VOL>
    <NO>207</NO>
    <DATE>Wednesday, October 26, 2011</DATE>
    <UNITNAME>Presidential Documents</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="66597"/>
            <PARTNO>Part V</PARTNO>
            <PRES>The President</PRES>
            <PNOTICE>Notice of October 25, 2011—Continuation of the National Emergency With Respect to the Situation in or in Relation to the Democratic Republic of the Congo</PNOTICE>
        </PTITLE>
        <PRESDOCS>
            <PRESDOCU>
                <PRNOTICE>
                    <TITLE3>Title 3—</TITLE3>
                    <PRES>
                        The President
                        <PRTPAGE P="66599"/>
                    </PRES>
                    <PNOTICE>Notice of October 25, 2011</PNOTICE>
                    <HD SOURCE="HED">Continuation of the National Emergency With Respect to the Situation in or in Relation to the Democratic Republic of the Congo</HD>
                    <FP>On October 27, 2006, by Executive Order 13413, the President declared a national emergency with respect to the situation in or in relation to the Democratic Republic of the Congo and, pursuant to the International Emergency Economic Powers Act (50 U.S.C. 1701-1706), ordered related measures blocking the property of certain persons contributing to the conflict in that country.  The President took this action to deal with the unusual and extraordinary threat to the foreign policy of the United States constituted by the situation in or in relation to the Democratic Republic of the Congo, which has been marked by widespread violence and atrocities that continue to threaten regional stability.</FP>
                    <FP>Because this situation continues to pose an unusual and extraordinary threat to the foreign policy of the United States, the national emergency declared on October 27, 2006, and the measures adopted on that date to deal with that emergency, must continue in effect beyond October 27, 2011.  Therefore, in accordance with section 202(d) of the National Emergencies Act (50 U.S.C. 1622(d)), I am continuing for 1 year the national emergency declared in Executive Order 13413.</FP>
                    <FP>
                        This notice shall be published in the 
                        <E T="03">Federal Register </E>
                        and transmitted to the Congress.
                    </FP>
                    <GPH SPAN="1" DEEP="62" HTYPE="RIGHT">
                        <GID>OB#1.EPS</GID>
                    </GPH>
                    <PSIG> </PSIG>
                    <PLACE>THE WHITE HOUSE,</PLACE>
                    <DATE>October 25, 2011.</DATE>
                    <FRDOC>[FR Doc. 2011-27922</FRDOC>
                    <FILED>Filed 10-25-11; 12:00 pm]</FILED>
                    <BILCOD>Billing code 3295-F2-P</BILCOD>
                </PRNOTICE>
            </PRESDOCU>
        </PRESDOCS>
    </NEWPART>
</FEDREG>
