<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="fedregister.xsl"?>
<FEDREG xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FRMergedXML.xsd">
  <VOL>78</VOL>
  <NO>2</NO>
  <DATE>Thursday, January 3, 2013</DATE>
  <UNITNAME>Contents</UNITNAME>
  <CNTNTS>
    <AGCY>
      <EAR>Agricultural Marketing</EAR>
      <PRTPAGE P="iii"/>
      <HD>Agricultural Marketing Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Standards for Grades of Eggplant,</DOC>
          <PGS>283</PGS>
          <FRDOCBP D="0" T="03JAN1.sgm">2012-31611</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Agriculture</EAR>
      <HD>Agriculture Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Agricultural Marketing Service</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Food Safety and Inspection Service</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>281-283</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31566</FRDOCBP>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31640</FRDOCBP>
          <FRDOCBP D="0" T="03JAN1.sgm">2012-31641</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Census Bureau</EAR>
      <HD>Census Bureau</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Resumption of the Population Estimates Challenge Program,</DOC>
          <PGS>255-260</PGS>
          <FRDOCBP D="5" T="03JAR1.sgm">2012-31598</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Centers Disease</EAR>
      <HD>Centers for Disease Control and Prevention</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>305-308</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31182</FRDOCBP>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31599</FRDOCBP>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31600</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Centers Medicare</EAR>
      <HD>Centers for Medicare &amp; Medicaid Services</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Medicare Program:</SJ>
        <SJDENT>
          <SJDOC>Hospital and Vendor Readiness for Electronic Health Records Hospital Inpatient Quality Data Reporting,</SJDOC>
          <PGS>308-310</PGS>
          <FRDOCBP D="2" T="03JAN1.sgm">2012-31582</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Coast Guard</EAR>
      <HD>Coast Guard</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Moving Security Zones around Escorted Vessels:</SJ>
        <SJDENT>
          <SJDOC>Lower Mississippi River,</SJDOC>
          <PGS>261-263</PGS>
          <FRDOCBP D="2" T="03JAR1.sgm">2012-31559</FRDOCBP>
        </SJDENT>
        <SJ>Safety Zones:</SJ>
        <SJDENT>
          <SJDOC>TEMCO Grain Facilities; Columbia and Willamette Rivers,</SJDOC>
          <PGS>263-266</PGS>
          <FRDOCBP D="3" T="03JAR1.sgm">2012-31561</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Commerce</EAR>
      <HD>Commerce Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Census Bureau</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>International Trade Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Institute of Standards and Technology</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Oceanic and Atmospheric Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Patent and Trademark Office</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Defense Department</EAR>
      <HD>Defense Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Defense Intelligence Agency Advisory Board,</SJDOC>
          <PGS>295</PGS>
          <FRDOCBP D="0" T="03JAN1.sgm">2012-31579</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Education Department</EAR>
      <HD>Education Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Membership:</SJ>
        <SJDENT>
          <SJDOC>National Advisory Committee on Institutional Quality and Integrity,</SJDOC>
          <PGS>295-296</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31620</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Energy Department</EAR>
      <HD>Energy Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Energy Regulatory Commission</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Environmental Protection</EAR>
      <HD>Environmental Protection Agency</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>NPDES Permit Regulation and Effluent Limitations Guidelines Standards:</SJ>
        <SJDENT>
          <SJDOC>Concentrated Animal Feeding Operations,</SJDOC>
          <PGS>277-278</PGS>
          <FRDOCBP D="1" T="03JAP1.sgm">2012-31091</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Environmental Laboratory Advisory Board,</SJDOC>
          <PGS>299</PGS>
          <FRDOCBP D="0" T="03JAN1.sgm">2012-31536</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR/>
      <HD>Executive Office of the President</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Presidential Documents</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Federal Aviation</EAR>
      <HD>Federal Aviation Administration</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Airworthiness Directives:</SJ>
        <SJDENT>
          <SJDOC>REIMS AVIATION S.A. Airplanes,</SJDOC>
          <PGS>275-277</PGS>
          <FRDOCBP D="2" T="03JAP1.sgm">2012-31602</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Communications</EAR>
      <HD>Federal Communications Commission</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Radio Broadcasting Services:</SJ>
        <SJDENT>
          <SJDOC>Maysville, GA,</SJDOC>
          <PGS>266-267</PGS>
          <FRDOCBP D="1" T="03JAR1.sgm">2012-31563</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Energy</EAR>
      <HD>Federal Energy Regulatory Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Combined Filings,</DOC>
          <PGS>296-299</PGS>
          <FRDOCBP D="2" T="03JAN1.sgm">2012-31580</FRDOCBP>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31612</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Mine</EAR>
      <HD>Federal Mine Safety and Health Review Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Meetings; Sunshine Act,</DOC>
          <PGS>299-300</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31684</FRDOCBP>
          <FRDOCBP D="0" T="03JAN1.sgm">2012-31690</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Reserve</EAR>
      <HD>Federal Reserve System</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Changes in Bank Control:</SJ>
        <SJDENT>
          <SJDOC>Acquisitions of Shares of Bank or Bank Holding Company,</SJDOC>
          <PGS>300</PGS>
          <FRDOCBP D="0" T="03JAN1.sgm">2012-31575</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Formations of, Acquisitions by, and Mergers of Bank Holding Companies,</DOC>
          <PGS>300</PGS>
          <FRDOCBP D="0" T="03JAN1.sgm">2012-31576</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Trade</EAR>
      <HD>Federal Trade Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Proposed Consent Orders:</SJ>
        <SJDENT>
          <SJDOC>IDEXX Laboratories, Inc.,</SJDOC>
          <PGS>300-303</PGS>
          <FRDOCBP D="3" T="03JAN1.sgm">2012-31571</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Fish</EAR>
      <HD>Fish and Wildlife Service</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Endangered and Threatened Wildlife and Plants:</SJ>
        <SJDENT>
          <SJDOC>Designation of Critical Habitat for Southwestern Willow Flycatcher,</SJDOC>
          <PGS>344-534</PGS>
          <FRDOCBP D="190" T="03JAR2.sgm">2012-30634</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Endangered and Threatened Wildlife and Plants:</SJ>
        <SJDENT>
          <SJDOC>Reclassification of Continental U.S. Breeding Population of Wood Stork from Endangered to Threatened; Correction,</SJDOC>
          <PGS>278-279</PGS>
          <FRDOCBP D="1" T="03JAP1.sgm">2012-31718</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Food and Drug</EAR>
      <HD>Food and Drug Administration</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Nicotine Replacement Therapies and Smoking-Cessation Products:</SJ>
        <SJDENT>
          <SJDOC>Report to Congress on Innovative Products and Treatments for Tobacco Dependence; Public Hearing,</SJDOC>
          <PGS>277</PGS>
          <FRDOCBP D="0" T="03JAP1.sgm">2012-31578</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Guidance for Industry on Providing Regulatory Submissions in Electronic Format:</SJ>
        <SJDENT>
          <SJDOC>Certain Human Pharmaceutical Product Applications, etc. Using Electronic Common Technical Document Specifications,</SJDOC>
          <PGS>310-311</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31577</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Food Safety</EAR>
      <PRTPAGE P="iv"/>
      <HD>Food Safety and Inspection Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>2013 Rate Changes for Basetime, Overtime, Holiday, and Laboratory Services Rates,</DOC>
          <PGS>283-285</PGS>
          <FRDOCBP D="2" T="03JAN1.sgm">2012-31556</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>General Services</EAR>
      <HD>General Services Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Office of Citizen Services and Innovative Technologies; Data.gov Feedback Mechanisms,</SJDOC>
          <PGS>304-305</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31621</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Proposal to Lease Space, GSA Form 1364,</SJDOC>
          <PGS>303-304</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31622</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Health and Human</EAR>
      <HD>Health and Human Services Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Centers for Disease Control and Prevention</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Centers for Medicare &amp; Medicaid Services</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Food and Drug Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Institutes of Health</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Substance Abuse and Mental Health Services Administration</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Homeland</EAR>
      <HD>Homeland Security Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Coast Guard</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>U.S. Customs and Border Protection</P>
      </SEE>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Provisional Unlawful Presence Waivers of Inadmissibility for Certain Immediate Relatives,</DOC>
          <PGS>536-578</PGS>
          <FRDOCBP D="42" T="03JAR3.sgm">2012-31268</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>Continuum of Care Program Application - Technical Submission,</SJDOC>
          <PGS>315-316</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31184</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Order of Succession for the Office of Housing,</DOC>
          <PGS>316-317</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31628</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Redelegation of Authority to the Deputy Assistant Secretary for Housing Counseling,</DOC>
          <PGS>317-318</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31626</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Interior</EAR>
      <HD>Interior Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Fish and Wildlife Service</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Land Management Bureau</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>International Trade Adm</EAR>
      <HD>International Trade Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Antidumping Duty Administrative Reviews; Results, Extensions, Amendments, etc.:</SJ>
        <SJDENT>
          <SJDOC>Circular Welded Carbon Steel Pipes and Tubes from Turkey,</SJDOC>
          <PGS>286-287</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31638</FRDOCBP>
        </SJDENT>
        <SJ>Antidumping or Countervailing Duty Orders, Findings, or Suspended Investigations:</SJ>
        <SJDENT>
          <SJDOC>Advance Notification of Sunset Reviews,</SJDOC>
          <PGS>287-288</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31543</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Opportunity to Request Administrative Review,</SJDOC>
          <PGS>288-290</PGS>
          <FRDOCBP D="2" T="03JAN1.sgm">2012-31544</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Land</EAR>
      <HD>Land Management Bureau</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Filings of Plats of Surveys:</SJ>
        <SJDENT>
          <SJDOC>Eastern States; North Carolina,</SJDOC>
          <PGS>318-319</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31583</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Maritime</EAR>
      <HD>Maritime Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Requested Administrative Waivers of Coastwise Trade Laws:</SJ>
        <SJDENT>
          <SJDOC>Vessel HALCYON,</SJDOC>
          <PGS>337</PGS>
          <FRDOCBP D="0" T="03JAN1.sgm">2012-31637</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR/>
      <HD>Mine Safety and Health Federal Review Commission</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Mine Safety and Health Review Commission</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>National Institute</EAR>
      <HD>National Institute of Standards and Technology</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>National Conference on Weights and Measures,</SJDOC>
          <PGS>290-292</PGS>
          <FRDOCBP D="2" T="03JAN1.sgm">2012-31596</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Visiting Committee on Advanced Technology,</SJDOC>
          <PGS>292</PGS>
          <FRDOCBP D="0" T="03JAN1.sgm">2012-31597</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Institute</EAR>
      <HD>National Institutes of Health</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Center for Scientific Review,</SJDOC>
          <PGS>312-313</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31553</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Cancer Institute,</SJDOC>
          <FRDOCBP D="0" T="03JAN1.sgm">2012-31550</FRDOCBP>
          <FRDOCBP D="0" T="03JAN1.sgm">2012-31551</FRDOCBP>
          <PGS>312-314</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31552</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Institute of Allergy and Infectious Diseases,</SJDOC>
          <PGS>314</PGS>
          <FRDOCBP D="0" T="03JAN1.sgm">2012-31549</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>Inseason Adjustment to 2013 Bering Sea and Aleutian Islands Pollock, Atka Mackerel, and Pacific Cod Total,</SJDOC>
          <PGS>270-274</PGS>
          <FRDOCBP D="4" T="03JAR1.sgm">2012-31635</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Inseason Adjustment to 2013 Gulf of Alaska Pollock and Pacific Cod Total Allowable Catch Amounts,</SJDOC>
          <PGS>267-270</PGS>
          <FRDOCBP D="3" T="03JAR1.sgm">2012-31627</FRDOCBP>
        </SJDENT>
        <SJ>Fisheries Off West Coast States; Pacific Coast Groundfish Fishery:</SJ>
        <SJDENT>
          <SJDOC>2013-2014 Biennial Specifications and Management Measures,</SJDOC>
          <PGS>580-644</PGS>
          <FRDOCBP D="64" T="03JAR4.sgm">2012-31134</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Atlantic Highly Migratory Species:</SJ>
        <SJDENT>
          <SJDOC>2006 Consolidated Highly Migratory Species Fishery Management Plan; Amendment 5,</SJDOC>
          <PGS>279-280</PGS>
          <FRDOCBP D="1" T="03JAP1.sgm">2012-31629</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Nuclear Regulatory</EAR>
      <HD>Nuclear Regulatory Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <FRDOCBP D="0" T="03JAN1.sgm">2012-31618</FRDOCBP>
          <PGS>319-320</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31619</FRDOCBP>
        </DOCENT>
        <SJ>Applications:</SJ>
        <SJDENT>
          <SJDOC>Arkansas Nuclear One, Units 1 and 2; Creation of Holding Company and Transfer of Facility Operating Licenses, etc.,</SJDOC>
          <PGS>328-330</PGS>
          <FRDOCBP D="2" T="03JAN1.sgm">2012-31614</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Grand Gulf Nuclear Station, Unit 1; Creation of Holding Company and Transfer of Facility Operating License, etc.,</SJDOC>
          <PGS>325-328</PGS>
          <FRDOCBP D="3" T="03JAN1.sgm">2012-31615</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>River Bend Station, Unit 1; Creation of Holding Company and Transfer of Facility Operating License, etc.,</SJDOC>
          <PGS>320-322</PGS>
          <FRDOCBP D="2" T="03JAN1.sgm">2012-31616</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Waterford Steam Electric Station, Unit 3; Creation of Holding Company and Transfer of Facility Operating License and Opportunity for Hearing,</SJDOC>
          <PGS>323-325</PGS>
          <FRDOCBP D="2" T="03JAN1.sgm">2012-31617</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Patent</EAR>
      <HD>Patent and Trademark Office</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Roundtable Events for Partnership for Enhancement of Quality of Software-Related Patents,</DOC>
          <PGS>292-295</PGS>
          <FRDOCBP D="3" T="03JAN1.sgm">2012-31594</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Presidential Documents</EAR>
      <HD>Presidential Documents</HD>
      <CAT>
        <HD>EXECUTIVE ORDERS</HD>
        <SJ>Government Agencies and Employees:</SJ>
        <SJDENT>
          <SJDOC>Rates of Pay; Adjustment (EO 13635),</SJDOC>
          <PGS>649-660</PGS>
          <FRDOCBP D="11" T="03JAE0.sgm">2013-00002</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>ADMINISTRATIVE ORDERS</HD>
        <SJ>Government Agencies and Employees:</SJ>
        <SJDENT>
          <SJDOC>Federal Employee Pay Schedules and Rates (Memorandum of December 21, 2012),</SJDOC>
          <PGS>645-647</PGS>
          <FRDOCBP D="2" T="03JAO0.sgm">2013-00001</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Public Debt</EAR>
      <HD>Public Debt Bureau</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>341</PGS>
          <FRDOCBP D="0" T="03JAN1.sgm">2012-31625</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Rural Utilities</EAR>
      <PRTPAGE P="v"/>
      <HD>Rural Utilities Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
        <SJDENT>
          <SJDOC>Healy Power Generation Unit 2, Healy, AK,</SJDOC>
          <PGS>285-286</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31643</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Securities</EAR>
      <HD>Securities and Exchange Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
        <SJDENT>
          <SJDOC>ICE Clear Europe Ltd.,</SJDOC>
          <PGS>330-335</PGS>
          <FRDOCBP D="2" T="03JAN1.sgm">2012-31568</FRDOCBP>
          <FRDOCBP D="2" T="03JAN1.sgm">2012-31569</FRDOCBP>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31570</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>New York Stock Exchange LLC,</SJDOC>
          <PGS>335-337</PGS>
          <FRDOCBP D="2" T="03JAN1.sgm">2012-31572</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Substance</EAR>
      <HD>Substance Abuse and Mental Health Services Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Laboratories and Instrumented Initial Testing Facilities that Meet Minimum Standards, etc.,</DOC>
          <PGS>314-315</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31573</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Surface Transportation</EAR>
      <HD>Surface Transportation Board</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Abandonment Exemptions:</SJ>
        <SJDENT>
          <SJDOC>CSX Transportation, Inc., Ewing Township, Mercer County, NJ,</SJDOC>
          <PGS>338</PGS>
          <FRDOCBP D="0" T="03JAN1.sgm">2012-31606</FRDOCBP>
        </SJDENT>
        <SJ>Acquisitions and Operation Exemptions:</SJ>
        <SJDENT>
          <SJDOC>Buckeye Hammond Railroad, LLC from Buckeye Partners, L.P.,</SJDOC>
          <PGS>338-339</PGS>
          <FRDOCBP D="1" T="03JAN1.sgm">2012-31439</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>Maritime 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>Public Debt Bureau</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>339-341</PGS>
          <FRDOCBP D="2" T="03JAN1.sgm">2012-31564</FRDOCBP>
          <FRDOCBP D="0" T="03JAN1.sgm">2012-31581</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Customs</EAR>
      <HD>U.S. Customs and Border Protection</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Reopenings of Application Periods:</SJ>
        <SJDENT>
          <SJDOC>Air Cargo Advance Screening Pilot Program,</SJDOC>
          <PGS>315</PGS>
          <FRDOCBP D="0" T="03JAN1.sgm">C1--2012--30922</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>344-534</PGS>
        <FRDOCBP D="190" T="03JAR2.sgm">2012-30634</FRDOCBP>
      </DOCENT>
      <HD>Part III</HD>
      <DOCENT>
        <DOC>Homeland Security Department,</DOC>
        <PGS>536-578</PGS>
        <FRDOCBP D="42" T="03JAR3.sgm">2012-31268</FRDOCBP>
      </DOCENT>
      <HD>Part IV</HD>
      <DOCENT>
        <DOC>Commerce Department, National Oceanic and Atmospheric Administration,</DOC>
        <PGS>580-644</PGS>
        <FRDOCBP D="64" T="03JAR4.sgm">2012-31134</FRDOCBP>
      </DOCENT>
      <HD>Part V</HD>
      <DOCENT>
        <DOC>Presidential Documents,</DOC>
        <PGS>645-647, 649-660</PGS>
        <FRDOCBP D="11" T="03JAE0.sgm">2013-00002</FRDOCBP>
        <FRDOCBP D="2" T="03JAO0.sgm">2013-00001</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>78</VOL>
  <NO>2</NO>
  <DATE>Thursday, January 3, 2013</DATE>
  <UNITNAME>Rules and Regulations</UNITNAME>
  <RULES>
    <RULE>
      <PREAMB>
        <PRTPAGE P="255"/>
        <AGENCY TYPE="F">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>Bureau of the Census</SUBAGY>
        <CFR>15 CFR Part 90</CFR>
        <DEPDOC>[Docket Number 111215758-2650-04]</DEPDOC>
        <RIN>RIN 0607-AA51</RIN>
        <SUBJECT>Resumption of the Population Estimates Challenge Program</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Bureau of the Census, Department of Commerce.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Bureau of the Census (Census Bureau) is resuming the Population Estimates Challenge Program to provide eligible governmental units the opportunity to file requests for the review of population estimates for 2011 and subsequent years. The Census Bureau is amending its regulations to: Update references to the method by which population estimates are officially released; clarify when a challenge of a population estimate can be requested; specify who may file a request for a population estimate challenge; remove all references to the per capita income estimates program and the Office of General Revenue Sharing; change the regulation title of a current program from “Procedure for Challenging Certain Population and Income Estimates” to “Procedure for Challenging Population Estimates” to reflect the removal of the per capita income estimates program; revise the requirements of the challenge process; and remove all references to a formal challenge process. The changes to the procedure for the Population Estimates Challenge Program clarify and streamline the procedures for local units of general-purpose government. The Census Bureau is removing the references for the per capita income estimates changes because the Census Bureau no longer produces per capita income estimates. The program that used those estimates, the General Revenue Sharing program, was eliminated for the States in 1980 and was not reauthorized for local governments after fiscal year 2000.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This Final Rule is effective on February 4, 2013.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Mr. Rodger V. Johnson, Chief, Local Government Estimates and Migration Processing Branch, Population Division, U.S. Census Bureau, Room 6H480, Mail Stop 8800, Washington, DC 20233-8800, by telephone on (301) 763-2461, by FAX (301) 763-2516, or by email at<E T="03">rodger.v.johnson@census.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Background</HD>

        <P>The Census Bureau is mandated to release population estimates annually in accordance with Title 13 of the United States Code (U.S.C.). These estimates are based upon the most recent Decennial Census of Population and Housing and compiled from the most current administrative and survey data available for that purpose. As part of its authorization, the Census Bureau offers an opportunity for local units of general-purpose government (hereinafter collectively “governmental unit”) to challenge these official estimates through its Population Estimates Challenge Program. Under this program, a sub-state governmental unit may challenge their population estimate by submitting additional data to the Census Bureau for evaluation. If the additional data are accepted during the review period by the Census Bureau, resulting in an updated population estimate, the Census Bureau will provide a written notification to the governmental unit and publish the revised estimate at<E T="03">www.census.gov.</E>If the additional data are not accepted for a revised estimate, the Census Bureau will notify the governmental unit. In those instances where a non-functioning county-level government or statistical equivalent exists, the State member agencies of the Federal-State Cooperative for Population Estimates (FSCPE) program may represent the area.</P>
        <P>Changes to the challenge process for this decade are based on results of evaluations of the accuracy of the Census Bureau's current methodology for producing population estimates compared with the accuracy of alternative approaches. In the previous decade, the Census Bureau modified the standard methodology to accommodate challenges by allowing housing unit based estimates to supplant cohort-component based estimates at the county level, and eliminating key sets of population controls generally imposed on county and subcounty estimates. The evaluations show that the challenge procedure used in the previous decade resulted in less accurate estimates of the population of governmental units. This has led the Census Bureau to revise the challenge process to no longer accept estimates developed from methods different from those used by the Census Bureau. In the revised challenge process, the Census Bureau will only accept a challenge when the evidence provided identifies the use of incorrect data, processes, or calculations in the estimates.</P>

        <P>The Census Bureau is resuming the Population Estimates Challenge Program to provide eligible governmental units the opportunity to challenge population estimates for 2011 and subsequent years. Previously, the Census Bureau published a final rule on January 4, 2010, in the<E T="04">Federal Register</E>(75 FR 44) to announce that beginning on February 3, 2010, the Census Bureau would temporarily suspend the Population Estimates Challenge Program during the decennial census year and the following year to accommodate the taking of the 2010 Census, and indefinitely suspend the Per Capita Income Estimates Challenge Program. The suspension of the program was followed up on August 10, 2012, by the Census Bureau with a Notice of Proposed Rulemaking and Request for Comments in the<E T="04">Federal Register</E>(77 FR 47783) for its program, entitled “Resumption of the Population Estimates Challenge Program and Proposed Changes to the Program.” In that announcement, the Census Bureau proposed resuming the Population Estimates Challenge Program in 2012 to provide eligible entities the opportunity to file requests for the review of population estimates for 2011 and subsequent years. The proposal was available for comment during a 30-day period that ended on September 10, 2012. The Census Bureau has now reviewed these comments and responded to them below in this final rule.<PRTPAGE P="256"/>
        </P>
        <HD SOURCE="HD1">Summary of Comments and Responses</HD>
        <P>The Census Bureau received eight sets of comments during the comment period. A summary of these comments and the detailed responses by the Census Bureau are provided below:</P>
        <P>
          <E T="03">Commenter 1.</E>The commenter stated that the Census Bureau's proposal greatly reduces the opportunities for localities to challenge county-level population estimates that the Census Bureau initially produces through the cohort-component or Administrative Records (ADREC) method. The commenter agreed that this method overall produced the most accurate county-level estimates, as compared to the 2010 Census counts, nevertheless, the commenter pointed out that there were exceptions in which a housing unit based method did produce an estimate closer to the 2010 Census results. The commenter also suggested that the Census Bureau continue to pursue research on alternate methods of population estimation in the event that these methods that were proven to be less useful at one point in time, may be more useful in the future. More specifically, the commenter suggested that the Census Bureau consider a pilot program in which a small cross-section of jurisdictions, with participation through the FSCPE member agencies, provide information towards the next round of evaluative studies.</P>
        <P>
          <E T="03">Response 1.</E>The Census Bureau acknowledges that a variant of the housing unit based method did produce more accurate results in some instances, as compared to the 2010 Census. However, the ADREC method consistently produced county-level estimates closer to the 2010 Census results, whereas the housing unit based population estimates were upwardly biased. The program changes will enable eligible governmental units to focus their comments upon the data used to produce population estimates and to provide alternative or supplemental data to the Census Bureau to evaluate for use in revising the original estimate under the existing methodology. Incorporating this challenge-based data systematically each year will improve the credibility and accuracy of the subsequent estimates and contribute to a longer-term goal of continuous improvement in the estimation process. The Census Bureau accepts the suggestion to continue to work with the FSCPE member agencies, county, and local governments to maintain a research agenda that addresses alternate methods of estimation, not as official estimates, but to help inform a population estimates program that focuses upon improving the accuracy of the estimates.</P>
        <P>
          <E T="03">Commenter 2.</E>The commenter wrote in with concern towards one part of the notice that stated that “sub-state governmental units be the sole entity to request a challenge * * * for their respective jurisdictions.” The commenter noted that in states of the Northeast, counties exist that do not serve legally as functioning general-purpose governmental units. In such instances, there would be no functioning governmental body to represent the area. In these states or in certain counties within them, often the only governmental units in place are minor civil divisions in the form of towns or equivalent areas that are subdivisions of their respective counties. The commenter requested that the Census Bureau reconsider this rule and provide for some flexibility in the rule in order to allow State level representation of these non-functioning counties should the state representative find issues with regard to the population estimates and the components.</P>
        <P>
          <E T="03">Response 2.</E>The Census Bureau acknowledges the issue and concurs that it is necessary to implement appropriate wording changes to define a role for States to represent these non-functioning governmental units for the purposes of the challenge program. None of the counties in Connecticut or Rhode Island are classified by the Census Bureau as active functioning general-purpose governmental units; in Massachusetts, nine of its fourteen counties are not classified as active functioning general-purpose governmental units. In Maine, New Hampshire, and Vermont, the Census Bureau classifies all counties as active functioning general-purpose governmental units. In Alaska, the county-equivalent Census Areas are statistical units and therefore may need representation by the State government should an issue arise with regard to their estimates and component data. The Census Bureau has amended the regulations in this final rule to recognize the FSCPE member agencies in the challenge program in order to present appropriate data on behalf of these non-functioning entities. The Census Bureau will continue to monitor legal status changes in the future that may result in one or more counties changing from active, general-purpose governmental units into non-functioning governmental entities to ensure coverage by the FSCPE member agencies.</P>
        <P>
          <E T="03">Commenter 3.</E>The commenter stated that the proposal would make the challenge program essentially meaningless by cutting off any options for localities to offer an alternative approach for county-level population estimates; the commenter offered several comments to support this viewpoint. The commenter stated that “no one estimates methodology has proven itself to be accurate for all types of areas in the country” and that “reliance on a single Administrative Records (ADREC) method for production of county population estimates and a variation of the housing unit method for subcounty estimates simply ignores the fact that alternative methods and data sources can produce quality estimates at any given point in time and for any given area.” The commenter argued that the proposal not to allow alternative estimates was to some degree influenced by potential difficulty that the Census Bureau would experience in incorporating alternate challenges into the existing production environment that the Census Bureau uses to produce the estimates in the first place. The commenter stated that the Census Bureau should allow alternative based estimates that meet certain tests of the accuracy of these methods against established decennial census results. Finally, the commenter suggested noting the FSCPE member agencies as a potential technical resource available to sub-state governmental units.</P>
        <P>
          <E T="03">Response 3.</E>During the temporary suspension the Population Estimates and the Per Capita Income Estimates Challenge Programs attendant to the 2010 Census, the Census Bureau evaluated the 2010 population estimates and the methods used to create them. These evaluations also were meant to inform the redesign of the challenge program. As part of this process, the Census Bureau assessed the county-level population estimates produced with the ADREC and housing unit methods against 2010 Census results. (These results were publicly released on the Census Bureau's Web site).</P>

        <P>It was clear that the best overall and defensible approach to estimation of county-level governmental units was through the ADREC method. In addition, it also became clear that the employment of a variation on the housing unit based method generally produced estimates that were more biased than the ADREC method when compared to the 2010 Census results. The evaluations also did not identify a clear-cut means to determine for any given county or equivalent when a housing unit based method would yield a more accurate estimate than that produced by the ADREC method. Given these factors, it became evident that in<PRTPAGE P="257"/>redesigning the challenge program, the Census Bureau needed to build a process that would capture the most accurate demographic components that were consistent and complementary with the existing estimates program methodologies. The Census Bureau did not accept the assertion from the commenter that the Census Bureau should accept alternative methods with a provision for testing against decennial census results. However, the Census Bureau has indicated its willingness to work with localities through the FSCPE member agencies to provide information towards the next round of evaluative studies. Please see Response to Commenter 1.</P>
        <P>
          <E T="03">Commenter 4.</E>The commenter provided essentially the same observation as the second commenter with regard to the representation for non-functioning counties or statistical equivalents.</P>
        <P>
          <E T="03">Response 4.</E>The Census Bureau concurs with the fourth commenter. Please see Response to Commenter 2.</P>
        <P>
          <E T="03">Commenter 5.</E>The commenter supports the rule change from reliance upon alternative estimates to a process whereby governmental units provide evidence of the use of incorrect data, processes, or calculations in the estimates and not necessarily alternative estimates. The commenter expressed concern for the potential of a challenge to be denied because a full explication of the criteria, standards, and regular processes the Census Bureau employs to generate the population estimates was not available in the notice. Therefore, the commenter requested that the Census Bureau recognize an advisory role to the Census Bureau by the FSCPE member agencies to “to gauge how well the challenge and estimates program complement each other.” The commenter also requested that outside experts like the FSCPE member agencies be provided with all communications between the Census Bureau and the challenging governmental unit, suggested that the FSCPE member agencies could advise the Census Bureau on changes in either the Estimates or the Challenge program, as they have excellent knowledge of the estimates process and can represent the interests of local governmental units.</P>
        <P>
          <E T="03">Response 5.</E>The Census Bureau appreciates the expression of support for the new challenge program. As stated in the responses to other comments, the Census Bureau will appropriately consult with the FSCPE member agencies during the course of the program.</P>
        <P>
          <E T="03">Commenter 6.</E>The commenter was concerned about the lack of representation for non-functioning county-level entities. The commenter also requested that we continue to accept housing conversion data for non-residential to residential use and accept locally documented data on demolitions.</P>
        <P>Response 6. The Census Bureau concurs with the sixth commenter on the issue of non-functioning county-level entities. Please see Response to Commenter 2. In response to the second concern about conversions of non-residential to residential units and demolitions, the Census Bureau will continue to accept properly documented data, including basic street address and unit (apartment, etc.) designations of the converted units. Data that are to substitute or replace the Census Bureau estimated housing loss figures must include residential housing condemnations, demolitions, and/or units that are uninhabitable, in order to be as comprehensive in scope as the original survey data used to estimate housing loss.</P>
        <P>
          <E T="03">Commenter 7.</E>The commenter is opposed to the exclusion of housing based methods to estimate county-level governmental units. The commenter would like the Census Bureau to continue to leave open the option for a challenging county-level governmental unit to provide a housing based alternative as opposed to providing updated data for the Census Bureau's cohort component (ADREC) based estimate. The writer also expressed the view “that the proposed policy flies in the face of all available scientific evidence as well as good judgment.”</P>
        <P>
          <E T="03">Response 7.</E>The Census Bureau consulted a variety of stakeholders on the elements of the proposal in order to design a program based upon the evaluation research conducted during the 2010 Census. The research conducted jointly by the Census Bureau and its partners in the FSCPE pointed to the overall accuracy of the ADREC method when compared to the 2010 Census results. However, as stated in the third response, the research evaluations also did not identify a clear-cut means to determine for any given county or equivalent when a housing based method would yield a more accurate estimate than that produced by the ADREC method. The Census Bureau has designed a program with guiding principles to govern outcomes more consistent with the current evaluation results. The Census Bureau also will continue to conduct research work with the FSCPE and others towards the next evaluation period to improve upon the challenge and estimates programs and, if possible, to determine means to identify alternate approaches to the current estimates that are based upon systematically identifiable and unbiased criteria.</P>
        <P>
          <E T="03">Commenter 8.</E>The eighth commenter suggested that the Census Bureau clarify in its challenge program documentation that the FSCPE member agencies be specified as a potential technical resource to localities that are contemplating challenging a population estimate. The second point from this commenter was that the challenge program from the previous decade added approximately 770,000 people to the national estimate. In addition, the commenter suggested that the Bureau look at a threshold based on the estimates evaluation research that would allow an estimate challenge using other data and methods, specifically the housing estimate, if the difference between the two estimates exceeded that threshold. Finally, the commenter suggested that the Census Bureau engage the FSCPE member agencies as technical experts in reviewing a challenge and/or another state agency that may have expertise to help review the alternative estimate.</P>
        <P>
          <E T="03">Response 8.</E>The Census Bureau concurs with the first suggestion that we incorporate into the program documentation that FSCPE member agencies could assist a locality in mounting a challenge. In regard to the second point, we note that the additional population incorporated into the national total did not systematically address the error of closure between the 2000 and the 2010 Census nor did it address shortfalls in the identification of immigration, therefore, it cannot be judged as a positive aspect of the former challenge program to emulate. The third suggestion is one that we will consider as part of the ongoing research agenda with the FSCPE member agencies and others, but not to produce an official revised estimate to replace the ADREC method results. The Census Bureau also accepts the suggestion that the FSCPE member agencies also be consulted to assist in evaluating challenges from their respective sub-state governments. This is substantially the same response as that to the fifth commenter.</P>
        <HD SOURCE="HD1">Changes From Proposed Rule</HD>

        <P>As commenters noted in their comments, the proposed rule made no provision for representation of counties in selected states of the Northeast that do not serve legally as functioning general-purpose governmental units. In such instances, no functioning county-level governmental body exists to represent the area. The commenters requested that the Census Bureau<PRTPAGE P="258"/>provide for some flexibility in the rule in order to allow State-level representation of these non-functioning counties with regard to the population estimates and the components. The Census Bureau acknowledged the issue, noted that it also existed for some parts of Alaska, and agreed to implement appropriate wording changes to define a role for States to represent these non-functioning governmental units in the challenge program. Specifically, the Census Bureau added a new definition for the term non-functioning governmental units at paragraph (f) to Section § 90.3, and re-designated the language formerly at paragraph (f) in new paragraph (g). Paragraph (g) also acknowledges non-functioning governmental units as an eligible governmental unit for the purposes of the challenge program. The Census Bureau also revised Section § 90.5 to acknowledge non-functioning governmental units.</P>
        <HD SOURCE="HD1">Summary of Provisions Implemented by This Final Rule</HD>
        <P>The Census Bureau is resuming the Population Estimates Challenge Program to provide governmental units the opportunity to challenge population estimates for 2011 and subsequent years. The Census Bureau is amending its regulations to: (1) Update references to the method by which population estimates are officially released; (2) clarify when a challenge of a population estimate can be requested; (3) specify who may file a request for a population estimate challenge; (4) remove all references to per capita income estimates and the Office of General Revenue Sharing; (5) change the regulation title of a current program from “Procedure for Challenging Certain Population and Income Estimates” to “Procedure for Challenging Population Estimates” to reflect the removal of the per capita income estimates program; (6) revise the requirements of the challenge process; and (7) remove all references to a formal challenge process.</P>

        <P>These changes to the regulations clarify the procedure for seeking a population estimate challenge by a governmental unit and to make the regulations clearer by eliminating out-of-date provisions. The Census Bureau in § 90.6 is updating references to the method by which population estimates are officially released to reflect widespread use of the Internet (rather than the<E T="04">Federal Register</E>) for disseminating official demographic data. For example, governmental units may initiate the challenge process after the population estimates are posted on the Census Bureau's Internet site (rather than published in the<E T="04">Federal Register</E>).</P>
        <P>Section 90.6 reduces the time period when a challenge to a population estimate may be filed from 180 days to 90 days after the release of the estimates by the Census Bureau. In the Census Bureau's judgment, 90 days are sufficient for an applicant to review the population estimate and to submit additional data to update the population estimate. This change ensures that, in most instances, the Census Bureau reviews and incorporates accepted data into subsequent estimates releases in a timely manner.</P>
        <P>Section 90.8 specifies that the types of data that are submitted must be consistent with the criteria, standards, and regular processes the Census Bureau employs to generate the population estimate. The Census Bureau will provide additional Web-based information describing the data that are required and how the governmental unit may contact the Census Bureau. Section § 90.8 specifies what methods can be used in the challenge process.</P>

        <P>Section 90.9 specifies that the Census Bureau will work with the governmental unit to verify the data that it has submitted, evaluate the data submitted, and render its decision in writing to the governmental unit. The Census Bureau will also post the revised population estimate at<E T="03">www.census.gov.</E>
        </P>
        <P>Furthermore, new § 90.5 specifies who may file a request for a challenge to a population estimate. Under the revised regulations, the chief executive officer or highest elected official of the requesting governmental unit is the only individual authorized to submit such requests. This change ensures that persons authorized by law to commit the governmental unit to a particular course of action have approved the request for a challenge prior to submission to the Census Bureau. The Census Bureau revises all applicable sections of the Population Estimates Challenge Program regulations to specify that the sub-state governmental units be the sole entity to request a challenge for the population estimates for their respective jurisdictions. In the event that a county-level governmental unit or statistical equivalent is not an active general-purpose government, the FSCPE member agency may serve as sponsor of the challenge and the governor will serve as the highest elected official. Additional detail on this exception is noted in the following paragraph.</P>
        <P>Under the method employed by the Census Bureau, state-level population estimates are a summary of the estimates for each county or statistical equivalent that comprise each state. Therefore, sub-state governmental units are the most appropriate level to request a challenge of the population estimates for their respective jurisdictions. In addition, the Census Bureau and the state governments have formally established and have maintained a long-term working relationship through the Federal-State Cooperative for Population Estimates (FSCPE). State agencies, designated by their respective governors, work in cooperation with the Census Bureau to produce population estimates. The Census Bureau initiates the process of preparing population estimates by updating population information from the most recent decennial census with information found in the annual administrative records of Federal and state agencies. The Federal agencies provide tax records, Medicare records, and some vital statistics and group quarters information. The FSCPE member agencies supply vital statistics and information about group quarters like college dorms or prisons. The Census Bureau combines census base data, administrative records, and selected survey data to produce current population estimates consistent with the last decennial census results. Moreover, the Census Bureau provides preliminary governmental unit estimates to the FSCPE member agencies for review and comment to resolve data processing issues identified during that period. Under the challenge program, the FSCPE member agencies, appointed by their respective governors, will be eligible to represent counties or statistical equivalents that do not function as active general-purpose governmental units. This situation exists in Connecticut, Rhode Island, for selected counties in Massachusetts, and for the Census Areas in Alaska. For the purposes of this program, the District of Columbia is treated as a statistical equivalent of a county and, therefore, also eligible to participate.</P>

        <P>Existing §§ 90.9 through 90.18 are deleted. In the Census Bureau's judgment, these sections are unnecessary, as the Population Estimates Challenge Program does not include a formal challenge process. This change is consistent with the procedures advanced in § 90.8 and § 90.9 to specify the required data and to verify that data are accurate and complete before the Census Bureau reviews the data and renders its decision on whether or not to update the population estimate. Ending the formal process removes a redundant procedure and, therefore, enables the<PRTPAGE P="259"/>Census Bureau to render a more timely decision during the review and update process. The Census Bureau is eliminating all references to the per capita income estimates program and the General Revenue Sharing Program from its regulations at 15 CFR part 90 because the Census Bureau no longer produces per capita income estimates. The Census Bureau generated the per capita income estimates for the General Revenue Sharing Program, pursuant to Section 109(a) of the State and Local Fiscal Assistance Act of 1972 (Pub. L. 92-512, section 109(a), 86 Stat. 919, 929 (1972)). The General Revenue Sharing Program was eliminated for the States in 1980 under the State and Local Fiscal Assistance Act Amendments of 1980 (Pub. L. 96-604, section 2, 94 Stat. 3516 (1980)), and was not reauthorized for local governments after fiscal year 2000 (See Pub. L. 103-322, section 31001, 108 Stat. 1796, 1859 (1994)). Due to the discontinuation of the General Revenue Sharing Program, the Census Bureau no longer needs to generate and publish per capita income estimates. In order to avoid any confusion regarding the status of the per capita income estimates program, the Census Bureau is eliminating all references to per capita income from the regulations. The Census Bureau is changing the titling of the program to reflect the fact that the Census Bureau no longer generates per capita income estimates previously mandated by law.</P>
        <P>The Census Bureau is making minor technical changes to the regulations, such as renumbering sections and heading titles to reconcile the changes proposed in this rule. The following chart reflects the renumbering of sections and revisions to heading titles, with new and revised sections noted in parentheses, for the public's convenience:</P>
        <GPOTABLE CDEF="s100,r100" COLS="2" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Former</CHED>
            <CHED H="1">Effective February 4, 2013</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">PART 90 PROCEDURE FOR CHALLENGING CERTAIN POPULATION AND INCOME ESTIMATES</ENT>
            <ENT>PART 90 PROCEDURE FOR CHALLENGING POPULATION ESTIMATES</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.1Scope and applicability</ENT>
            <ENT>90.1Scope and applicability.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.2Policy of the Census Bureau</ENT>
            <ENT>90.2Policy of the Census Bureau.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.3Definitions</ENT>
            <ENT>90.3Definitions.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.4General</ENT>
            <ENT>90.4General.</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>(New) 90.5Who may file a challenge.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.5When an informal challenge may be filed</ENT>
            <ENT>90.6When a challenge may be filed.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.6Where to file challenge</ENT>
            <ENT>(Revised) 90.7Where to file a challenge.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.7Evidence required</ENT>
            <ENT>(Revised) 90.8Evidence required.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.8Review of challenge</ENT>
            <ENT>(Revised) 90.9Review of challenge.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.9When formal procedure may be invoked</ENT>
            <ENT>(Deleted).</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.10Form of formal challenge and time limit for filing</ENT>
            <ENT>(Deleted).</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.11Appointment of hearing officer</ENT>
            <ENT>(Deleted).</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.12Qualifications of hearing officer</ENT>
            <ENT>(Deleted).</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.13Offer of hearing</ENT>
            <ENT>(Deleted).</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.14Hearing</ENT>
            <ENT>(Deleted).</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.15Decision by Director</ENT>
            <ENT>(Deleted).</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.16Notification of adjustment</ENT>
            <ENT>(Deleted).</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.17Timing for hearing and decision</ENT>
            <ENT>(Deleted).</ENT>
          </ROW>
          <ROW>
            <ENT I="01">90.18Representation</ENT>
            <ENT>(Deleted).</ENT>
          </ROW>
        </GPOTABLE>
        <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
        <P>The Chief Counsel for Regulation of the Department of Commerce certified to the Chief Counsel for Advocacy of the Small Business Administration during the proposed rule stage that this action would not have a significant economic impact on a substantial number of small entities. The factual basis for this determination was published in the proposed rule and is not repeated here. No comments were received regarding the certification. As a result, a regulatory flexibility analysis was not required and none was prepared.</P>
        <HD SOURCE="HD1">Executive Orders</HD>
        <P>This rule has been determined to be not significant for purposes of Executive Order 12866. This rule does not contain policies with federalism implications as that term is defined in Executive Order 13132.</P>
        <HD SOURCE="HD1">Paperwork Reduction Act</HD>
        <P>This notice of final rulemaking does not contain a collection of information subject to the requirements of the Paperwork Reduction Act (PRA), 44 U.S.C., Chapter 35. Notwithstanding any other provision of the law, no person is required to respond to, nor shall any person be subject to a penalty for failure to comply with, a collection of information subject to the requirements of the PRA, unless that collection of information displays a currently valid OMB Control Number.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 15 CFR part 90</HD>
          <P>Administrative practice and procedure, Census data, Population census, Statistics.</P>
        </LSTSUB>
        
        <P>For the reasons stated in the preamble, the Census Bureau is amending 15 CFR part 90 to read as follows:</P>
        <REGTEXT PART="90" TITLE="15">
          <PART>
            <HD SOURCE="HED">PART 90—[AMENDED]</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 90 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>13 U.S.C. 4 and 181.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="90" TITLE="15">
          <AMDPAR>2. Lift the stay on part 90 published at 75 FR 46, Jan. 4, 2010.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="90" TITLE="15">
          <AMDPAR>3. Revise 15 CFR part 90 to read as follows:</AMDPAR>
          <PART>
            <HD SOURCE="HED">PART 90—PROCEDURE FOR CHALLENGING POPULATION ESTIMATES</HD>
            <CONTENTS>
              <SECHD>Sec.</SECHD>
              <SECTNO>90.1</SECTNO>
              <SUBJECT>Scope and applicability.</SUBJECT>
              <SECTNO>90.2</SECTNO>
              <SUBJECT>Policy of the Census Bureau.</SUBJECT>
              <SECTNO>90.3</SECTNO>
              <SUBJECT>Definitions.</SUBJECT>
              <SECTNO>90.4</SECTNO>
              <SUBJECT>General.</SUBJECT>
              <SECTNO>90.5</SECTNO>
              <SUBJECT>Who may file a challenge.</SUBJECT>
              <SECTNO>90.6</SECTNO>
              <SUBJECT>When a challenge may be filed.</SUBJECT>
              <SECTNO>90.7</SECTNO>
              <SUBJECT>Where to file a challenge.</SUBJECT>
              <SECTNO>90.8</SECTNO>
              <SUBJECT>Evidence required.</SUBJECT>
              <SECTNO>90.9</SECTNO>
              <SUBJECT>Review of challenge.</SUBJECT>
            </CONTENTS>
            <AUTH>
              <HD SOURCE="HED">Authority:</HD>
              <P>13 U.S.C. 4 and 181.</P>
            </AUTH>
            <SECTION>
              <SECTNO>§ 90.1</SECTNO>
              <SUBJECT>Scope and applicability.</SUBJECT>

              <P>Between decennial censuses, the Census Bureau annually prepares statistical estimates of the number of people residing in states and their governmental units. In general, these estimates are developed by updating the population counts produced in the most recent decennial census with demographic components of change data and/or other indicators of<PRTPAGE P="260"/>population change. These rules prescribe the administrative procedure available to governmental units to request a challenge to the most current of these estimates.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 90.2</SECTNO>
              <SUBJECT>Policy of the Census Bureau.</SUBJECT>
              <P>It is the policy of the Census Bureau to provide the most accurate population estimates possible given the constraints of time, money, and available statistical techniques. It is also the policy of the Census Bureau to provide governmental units the opportunity to seek a review and provide additional data to these estimates and to present evidence relating to the accuracy of the estimates.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 90.3</SECTNO>
              <SUBJECT>Definitions.</SUBJECT>
              <P>As used in this part (except where the context clearly indicates otherwise) the following definitions shall apply:</P>
              <P>(a)<E T="03">Census Bureau</E>means the U.S. Census Bureau, Department of Commerce.</P>
              <P>(b)<E T="03">Population Estimates Challenge</E>means, in accordance with this part, the process a governmental unit may use to provide additional input data for the Census Bureau's population estimate and the submission of substantive documentation in support thereof.</P>
              <P>(c)<E T="03">Director</E>means Director of the Census Bureau, or an individual designated by the Director to perform under this part.</P>
              <P>(d)<E T="03">Population estimate</E>means a statistically developed calculation of the number of people living in a governmental unit to update the preceding census or earlier estimate.</P>
              <P>(e) A<E T="03">governmental unit</E>means the government of a county, municipality, township, incorporated place, or other minor civil division, which is a unit of general-purpose government below the State.</P>
              <P>(f) A<E T="03">non-functioning county or statistical equivalent</E>means a sub-state entity that does not function as an active general-purpose governmental unit. This situation exists in Connecticut, Rhode Island, for selected counties in Massachusetts, and for the Census Areas in Alaska.</P>
              <P>(g) For the purposes of this program, an<E T="03">eligible governmental unit</E>also includes the District of Columbia and non-functioning counties or statistical equivalents represented by a FSCPE member agency.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 90.4</SECTNO>
              <SUBJECT>General.</SUBJECT>
              <P>This part provides a procedure for a governmental unit to request a challenge of a population estimate of the Census Bureau. The Census Bureau, upon receipt of the appropriate documentation, will attempt to resolve the estimate with the governmental unit.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 90.5</SECTNO>
              <SUBJECT>Who may file a challenge.</SUBJECT>
              <P>A request for a challenge of a population estimate generated by the Census Bureau may be filed only by the chief executive officer or highest elected official of a governmental unit. In those instances where the FSCPE member agency represents a non-functioning county or statistical equivalent, the governor will serve as the chief executive officer or highest elected official.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 90.6</SECTNO>
              <SUBJECT>When a challenge may be filed.</SUBJECT>

              <P>(a) A request for a challenge to a population estimate may be filed any time up to 90 days after the release of the estimate by the Census Bureau. Publication by the Census Bureau on its Web site (<E T="03">www.census.gov</E>) shall constitute release. Documentation requesting a challenge of any estimate may also be filed any time up to 90 days after the date the Census Bureau, on its own initiative, revises that estimate.</P>
              <P>(b) If, however, a governmental unit has a sufficiently meritorious reason for not filing in a timely manner, the Census Bureau has the discretion to accept the late request.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 90.7</SECTNO>
              <SUBJECT>Where to file a challenge.</SUBJECT>
              <P>A request for a population estimate challenge must be prepared in writing by the governmental unit and filed with the Chief, Population Division, Census Bureau, Room 5H174, Mail Stop 8800, Washington, DC 20233. The governmental unit must designate a contact person who can be reached by telephone during normal business hours should questions arise with regard to the submitted materials.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 90.8</SECTNO>
              <SUBJECT>Evidence required.</SUBJECT>
              <P>(a) The governmental unit shall provide whatever evidence it has relevant to the request at the time of filing. The Census Bureau may request further evidence when necessary. The evidence submitted must be consistent with the criteria, standards, and regular processes the Census Bureau employs to generate the population estimate. The Census Bureau has revised the challenge process to no longer accept estimates developed from methods different from those used by the Census Bureau. In the revised challenge process, the Census Bureau will only accept a challenge when the evidence provided identifies the use of incorrect data, processes, or calculations in the estimates.</P>
              <P>(b) For counties and statistical equivalents, the Census Bureau uses a cohort-component of change method to produce population estimates. Each year, the components of change are updated. These components include births, deaths, migration, and change in the group quarters population. The Census Bureau will consider a challenge based on additional information on one or more of the components of change or about the group quarters population in a locality.</P>
              <P>(c) For minor civil divisions and incorporated places, the Census Bureau uses a housing unit method to distribute the county population. The components in this method include housing units, occupancy rates, and persons per household plus an estimate of the population in group quarters. The Census Bureau will consider a challenge based on data related to changes in an area's housing stock, such as data on demolitions, condemned units, uninhabitable units, building permits, or mobile home placements or other comparable housing inventory based data. The Census Bureau will also consider a challenge based on additional information about the group quarters population in a locality.</P>
              <P>(d) The Census Bureau will also provide a guide on its Web site as a reference for governmental units to use in developing their data as evidence to support a challenge to the population estimate. In addition, a governmental unit may address any additional questions by contacting the Census Bureau at the address provided in § 90.7.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 90.9</SECTNO>
              <SUBJECT>Review of challenge.</SUBJECT>

              <P>The Chief, Population Division, Census Bureau, or the Chief's designee shall review the evidence provided with the request for the population estimate challenge, shall work with the governmental unit to verify the data provided by the governmental unit, and evaluate the data to resolve the issues raised by the governmental unit. Thereafter, the Census Bureau shall respond in writing with a decision to accept or deny the challenge. In the event that the Census Bureau finds that the population estimate should be updated, it will also post the revised estimate on the Census Bureau's Web site (<E T="03">www.census.gov</E>).</P>
            </SECTION>
          </PART>
        </REGTEXT>
        <SIG>
          <DATED>Dated: December 26, 2012.</DATED>
          <NAME>Thomas L. Mesenbourg, Jr.,</NAME>
          <TITLE>Acting Director, Bureau of the Census.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31598 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-07-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <PRTPAGE P="261"/>
        <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Coast Guard</SUBAGY>
        <CFR>33 CFR Part 165</CFR>
        <DEPDOC>[Docket Number USCG-2012-1078]</DEPDOC>
        <RIN>RIN 1625-AA87</RIN>
        <SUBJECT>Moving Security Zone Around Escorted Vessels on the Lower Mississippi River</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Coast Guard, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Temporary final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Captain of the Port of New Orleans (COTP New Orleans) is establishing a Moving Security Zone on the Mississippi river, mile marker 88.0 through mile marker 106.0, extending 300 yards on all sides of vessels being escorted by one or more Coast Guard assets or other federal, state, or local law enforcement agency assets. A vessel may request permission of the COTP New Orleans or the on-scene Coast Guard or enforcement agency asset to enter the security zone, and if permitted, must proceed at the minimum safe speed and must comply with the orders of the COTP New Orleans or the on-scene asset. The COTP New Orleans will inform the public of the existence or status of the security zones around escorted vessels in the regulated area by Marine Safety Information Bulletins or Broadcast Notice to Mariners. This moving security zone is necessary to protect vessels deemed to be in need of escort protection by the COTP New Orleans for security reasons.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective from January 1, 2013, through March 31, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Documents mentioned in this preamble are part of docket [USCG-2012-1078]. To view documents mentioned in this preamble as being available in the docket, go to<E T="03">http://www.regulations.gov,</E>type the docket number in the “SEARCH” box and click “SEARCH.” Click on Open Docket Folder on the line associated with this rulemaking. 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.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>If you have questions on this rule, call or email Lieutenant Commander (LCDR) Kenneth Blair, Sector New Orleans, U.S. Coast Guard; telephone (504) 365-2392, email<E T="03">Kenneth.E.Blair@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">Table of Acronyms</HD>
        <EXTRACT>
          <FP SOURCE="FP-1">DHS—Department of Homeland Security</FP>
          <FP SOURCE="FP-1">FR—Federal Register</FP>
          <FP SOURCE="FP-1">NPRM—Notice of Proposed Rulemaking</FP>
        </EXTRACT>
        <HD SOURCE="HD1">A. Regulatory History and Information</HD>
        <P>The Coast Guard is issuing this final rule without prior notice and opportunity to comment pursuant to authority under section 4(a) of the Administrative Procedure Act (APA) (5 U.S.C. 553(b)). This provision authorizes an agency to issue a rule without prior notice and opportunity to comment when the agency for good cause finds that those procedures are “impracticable, unnecessary, or contrary to the public interest.” Under 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule. Based on a risk evaluation conducted on December 4, 2012, the Coast Guard has decided that a moving security zone regulation is required from on or about January 1 until March 31, 2013. This security zone is required to protect escorted vessels and personnel from destruction, loss, or injury from sabotage or other subversive acts, accidents, or other causes of similar nature. The NPRM process would unnecessarily delay the effective dates and would be contrary to public interest by delaying or foregoing the necessary protections required for the escorted vessels and personnel.</P>

        <P>Under 5 U.S.C. 553(d)(3), the Coast Guard finds that good cause exists for making this rule effective less than 30 days after publication in the<E T="04">Federal Register</E>. This temporary final rule is needed to protect escorted vessels and personnel from destruction, loss, or injury from sabotage or other subversive acts, accidents, or other causes of a similar nature. The 30-day notice period would be impracticable and unnecessarily delay the effective dates and protections required for these escorted vessels and personnel.</P>
        <HD SOURCE="HD1">B. Basis and Purpose</HD>
        <P>The purpose of this rule is to provide enhanced protection of escorted vessels on a portion of the Lower Mississippi River between January and April 2013. Certain vessels, including high capacity passenger vessels, vessels carrying certain dangerous cargoes as defined in 33 CFR part 60, tank vessels constructed to carry oil or hazardous materials in bulk, and vessels carrying liquefied hazardous gas as defined in 33 CFR part 127 have been deemed by the COTP New Orleans to require escort protection during transit between mile marker 88.0 and mile marker 106.0 of the Lower Mississippi River, between January and April, 2013. Establishment of a moving security zone allows the Coast Guard to provide enhanced security of escorted vessels during transit, thereby protecting the escorted vessels and the public from destruction, loss, or injury from sabotage or other subversive acts, accidents, or other causes of similar nature. When considering this rule the Coast Guard considered the alternative option of vessel traffic restrictions during the transit of vessels deemed in need of escorts. We determined that establishment of a moving security zone provides for enhanced protection of escorted vessels while causing little if any disruption to other routine navigation since most vessels will be allowed to transit within the outer 250 yards of the security zone once a deviation to the rule is requested and granted.</P>
        <P>The legal basis and authorities for this rule are found in 33 U.S.C. 1231, 46 U.S.C. Chapter 701, 3306, 3703; 50 U.S.C. 191, 195; 33 CFR 1.05-1, 6.04-1, 6.04-6, and 160.5; Public Law 107-295, 116 Stat. 2064; and Department of Homeland Security Delegation No. 0170.1, which collectively authorize the Coast Guard to propose, establish, and define regulatory safety zones.</P>
        <HD SOURCE="HD1">C. Discussion of the Final Rule</HD>

        <P>The Coast Guard is establishing moving security zones for escorted vessels to protect the escorted vessels and personnel. While this rule is effective, when an escorted vessel is transiting between miles 88 and 106 on the Lower Mississippi River, there will be a 300-yard security zone around the escorted vessel. The COTP New Orleans may permit persons and vessels to transit through the security zone at a minimum safe speed, so long as no vessel or person enters within the 50-yard portion of the security zone closest to the vessel. Permission to enter the security zone may be requested from the COTP New Orleans through the on-scene Coast Guard or enforcement agency asset, via VHF-FM Ch.12, VHF-FM Ch. 67, or the Coast Guard Vessel Traffic Center at (504) 365-2330. The COTP New Orleans will inform the public of the existence or status of the security zones around escorted vessels in the regulated area by Marine Safety Information Bulletins or Broadcast Notice to Mariners. Coast Guard assets<PRTPAGE P="262"/>or other Federal, State or local law enforcement agency assets will be clearly identified by lights, vessel markings, or with agency insignia.</P>
        <HD SOURCE="HD1">D. Regulatory Analyses</HD>
        <P>We developed this rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on a number of these statutes or executive orders.</P>
        <HD SOURCE="HD2">1. Regulatory Planning and Review</HD>
        <P>This rule is not a significant regulatory action under section 3(f) of Executive Order 12866, Regulatory Planning and Review, 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. It is not “significant” under the regulatory policies and procedures of the Department of Homeland Security (DHS). The impact of this security zone will be minimal as the zone will only be enforced for short periods of time while escorted vessels transit through an 18-mile stretch of the Lower Mississippi River. Other vessel traffic on the river will be able to transit through the outer 250 yards of the security zone with the permission of the COTP. Additionally, the security zone location is within the New Orleans Harbor Vessel Service Area that requires vessels transiting to check in when entering the area or when departing berth. This pre-existing check in requirement will assist in granting early permission for deviation from the rule allowing vessels to pass through the zone.</P>
        <HD SOURCE="HD2">2. Impact on Small Entities</HD>
        <P>The Regulatory Flexibility Act of 1980 (RFA), 5 U.S.C. 601-612, as amended, requires federal agencies to consider the potential impact of regulations on small entities during rulemaking. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
        <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities. This rule will affect the following entities, some of which may be small entities: the owners and operators of vessels intending to transit in the vicinity of mile marker 88.0 through mile marker 106.0 of the Lower Mississippi River, extending 300 yards in all directions of an escorted vessel. This security zone would not have a significant economic impact on a substantial number of small entities for the following reasons. This security zone would be activated, and thus subject to enforcement, for only those times when a vessel is under escort. The security zone location is within the New Orleans Harbor Vessel Service Area that requires vessels transiting to check in when entering the area or when departing berth. This pre-existing check in requirement will assist in granting early permission for deviation from the rule allowing vessels to pass through the zone. Although the safety zone would apply 300 yards around the escorted vessel and encompass almost the entire width of the river, traffic would be allowed to pass through the zone with the permission of the Captain of the Port. Before the activation of the zone, we would issue maritime advisories widely available to users of the river.</P>
        <HD SOURCE="HD2">3. Assistance for Small Entities</HD>

        <P>Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we want to assist small entities in understanding this rule. 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 in the<E T="02">FOR FURTHER INFORMATION CONTACT</E>, above.</P>
        <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.</P>
        <HD SOURCE="HD2">4. Collection of Information</HD>
        <P>This rule will not call for a new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
        <HD SOURCE="HD2">5. Federalism</HD>
        <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has 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. We have analyzed this rule under that Order and determined that this rule does not have implications for federalism.</P>
        <HD SOURCE="HD2">6. Protest Activities</HD>

        <P>The Coast Guard respects the First Amendment rights of protesters. Protesters are asked to contact the person listed in the<E T="02">FOR FURTHER INFORMATION CONTACT</E>section to coordinate protest activities so that your message can be received without jeopardizing the safety or security of people, places, or vessels.</P>
        <HD SOURCE="HD2">7. Unfunded Mandates Reform Act</HD>
        <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or more in any one year. Though this rule will not result in such an expenditure, we do discuss the effects of this rule elsewhere in this preamble.</P>
        <HD SOURCE="HD2">8. Taking of Private Property</HD>
        <P>This rule will not cause a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.</P>
        <HD SOURCE="HD2">9. Civil Justice Reform</HD>
        <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.</P>
        <HD SOURCE="HD2">10. Protection of Children</HD>
        <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or risk to safety that may disproportionately affect children.</P>
        <HD SOURCE="HD2">11. Indian Tribal Governments</HD>

        <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the<PRTPAGE P="263"/>Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
        <HD SOURCE="HD2">12. Energy Effects</HD>
        <P>This action is not a “significant energy action” under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use.</P>
        <HD SOURCE="HD2">13. Technical Standards</HD>
        <P>This rule does not use technical standards. Therefore, we did not consider the use of voluntary consensus standards.</P>
        <HD SOURCE="HD2">14. Environment</HD>

        <P>We have analyzed this rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA) (42 U.S.C. 4321-4370f), and have determined that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment. This rule involves the establishment of a moving security zone around escorted vessels. This rule is categorically excluded from further review under paragraph 34(g) of Figure 2-1 of the Commandant Instruction. An environmental analysis checklist supporting this determination and a Categorical Exclusion Determination are available in the docket where indicated under<E T="02">ADDRESSES</E>. We seek any comments or information that may lead to the discovery of a significant environmental impact from this rule.</P>
        <HD SOURCE="HD1">E. List of Subjects in 33 CFR Part 165</HD>
        <P>Harbors, Marine safety, Navigation (water), Reporting and recordkeeping requirements, Security measures, Waterways.</P>
        
        <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165 as follows:</P>
        <REGTEXT PART="165" TITLE="33">
          <PART>
            <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 165 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>33 U.S.C. 1231; 46 U.S.C. Chapter 701, 3306, 3703; 50 U.S.C. 191, 195; 33 CFR 1.05-1, 6.06-1, 6.05-6 and 160.5; Pub. L. 107-295, 116 stat. 2064; Department of Homeland Security Delegation No. 0170.1.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="165" TITLE="33">
          <AMDPAR>2. Add temporary § 165.T08-1078 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 165.T08-1078</SECTNO>
            <SUBJECT>Moving Security Zone around escorted vessels on the Lower Mississippi River.</SUBJECT>
            <P>(a)<E T="03">Location.</E>The following areas are security zones: Navigable waters of the Lower Mississippi River, from mile marker 88.0 to mile marker 106.0, extending 300 yards in all directions of escorted vessels. Escorted vessels will be escorted by one or more Coast Guard assets or other federal, state, or local law enforcement agency assets clearly identifiable by lights, vessel markings, or with agency insignia.</P>
            <P>(b)<E T="03">Effective Period.</E>This rule is effective January 1, 2013 through March 31, 2013.</P>
            <P>(c)<E T="03">Regulations.</E>(1) Under the general regulations in § 165.33 of this part, vessels are prohibited from entering or transiting the security zones described in paragraph (a) of this temporary section, § 165.T08-1078.</P>
            <P>(2) If granted permission to enter a security zone, a vessel must operate at the minimum speed necessary to maintain a safe course, unless required to maintain speed by the Navigation Rules, and shall proceed as directed by the Coast Guard. When within the security zone, no vessel or person is allowed within 50 yards of the escorted vessel unless authorized by the Coast Guard.</P>
            <P>(3) Persons or vessels requiring deviations from this rule must request permission from the Captain of the Port New Orleans through the on-scene Coast Guard or other enforcement agency asset, via VHF-FM Ch. 12, VHF-FM Ch. 67, or the Coast Guard Vessel Traffic Center at (504) 365-2330.</P>

            <P>(4) All persons and vessels granted permission to enter a security zone must comply with the instructions of the Captain of the Port New Orleans and designated personnel. Designated personnel include commissioned, warrant and petty officers of the U.S. Coast Guard, and local, state, and federal law enforcement officers on clearly identified law enforcement agency vessels<E T="03">.</E>
            </P>
            <P>(d)<E T="03">Informational broadcasts.</E>The Captain of the Port or a designated representative will inform the public through marine safety information bulletins or broadcast notices to mariners of the enforcement of the security zone.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: December 19, 2012.</DATED>
          <NAME>P.W. Gautier,</NAME>
          <TITLE>Captain, U.S. Coast Guard, Captain of the Port New Orleans.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31559 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-04-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Coast Guard</SUBAGY>
        <CFR>33 CFR Part 165</CFR>
        <DEPDOC>[Docket Number USCG-2012-1068]</DEPDOC>
        <RIN>RIN 1625-AA00</RIN>
        <SUBJECT>Safety Zones; TEMCO Grain Facilities; Columbia and Willamette Rivers</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Coast Guard, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Temporary final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Coast Guard is establishing temporary safety zones around the TEMCO grain facilities on the Columbia River in Kalama, WA and the Willamette River in Portland, OR. These safety zones extend to the waters of the Columbia and Willamette Rivers, respectively, approximately between the navigable channel and the facility described. These safety zones are being established to ensure that protest activities relating to a labor dispute involving these facilities do not create hazardous navigation conditions for vessels in the navigable channel or vessels attempting to moor at the facilities.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective January 3, 2013 and has been enforced with actual notice since December 7, 2012 and it will be enforced until February 4, 2013.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Documents mentioned in this preamble are part of docket [USCG-2012-1068]. To view documents mentioned in this preamble as being available in the docket, go to<E T="03">http://www.regulations.gov</E>, type the docket number in the “SEARCH” box and click “SEARCH.” Click on Open Docket Folder on the line associated with this rulemaking. 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.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>If you have questions on this rule, call or email Ensign Ian P. McPhillips, Waterways Management Division, Marine Safety Unit Portland, U.S. Coast Guard; telephone (503) 240-9319, email<E T="03">MSUPDXWWM@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">Table of Acronyms</HD>
        <EXTRACT>
          <P>DHSDepartment of Homeland Security<PRTPAGE P="264"/>
          </P>
          <P>FRFederal Register</P>
          <P>NPRMNotice of Proposed Rulemaking</P>
        </EXTRACT>
        <HD SOURCE="HD1">A. Regulatory History and Information</HD>
        <P>The Coast Guard is issuing this final rule without prior notice and opportunity to comment pursuant to authority under section 4(a) of the Administrative Procedure Act (APA) (5 U.S.C. 553(b)). This provision authorizes an agency to issue a rule without prior notice and opportunity to comment when the agency for good cause finds that those procedures are “impracticable, unnecessary, or contrary to the public interest.” Under 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule because to do so would be impracticable since delayed promulgation may result in injury or damage to the maritime public, vessel crews, the vessels themselves, the facilities, and law enforcement personnel from protest activities that could occur prior to conclusion of a notice and comment period.</P>

        <P>Under 5 U.S.C. 553(d)(3), the Coast Guard finds that good cause exists for making this rule effective less than 30 days after publication in the<E T="04">Federal Register</E>because to do otherwise would be impracticable since the arrival of grain-shipment vessels cannot be delayed by the Coast Guard and protest activities are unpredictable and potentially volatile and may result in injury to persons, property, or the environment. Delaying the effective date until 30 days after publication may mean that grain-shipment vessels calling on the Columbia Grain or United Grain Corporation facilities will have arrived and/or departed before the end of a 30-day period. This delay would eliminate the safety zones' effectiveness and usefulness in protecting persons, property, and the safe navigation of maritime traffic during the 30-day period.</P>
        <HD SOURCE="HD1">B. Basis and Purpose</HD>
        <P>These safety zones are being implemented to help ensure the safe navigation of maritime traffic on the Columbia and Willamette Rivers while grain-shipment vessels transit to and from the TEMCO grain facilities. These safety zones apply equally to all waterway users and are intended to allow maximum use of the waterway consistent with safe navigation and to ensure that protestors and other river users are not injured by deep-draft vessels with maneuvering characteristics with which they may be unfamiliar. In addition, these safety zones around the grain facilities are intended to ensure that protestors are not injured due to the effects of the strong river currents around the facilities' docks, piers, and wharves.</P>
        <HD SOURCE="HD1">C. Discussion of the Final Rule</HD>
        <P>This rule establishes temporary safety zones around the TEMCO grain facility located on the Columbia River in Kalama, WA and the TEMCO grain facility located on the Willamette River in Portland, OR.</P>
        <P>The safety zone around the TEMCO grain facility in Kalama, WA is enclosed by three lines and the shoreline: line one starting on the shoreline at 45-59′10″ N/122-50′09″ W then heading 150 yards offshore to 45-59′09″ N/122-50′14″ W then heading up river 385 yards to 45-58′58″ N/122-50′07″ then heading 150 yards to the shoreline ending at 45-59′00″ N/122-50′01″ W. In essence, these boundaries extend from the shoreline of the facility 150 yards onto the river from each corner of the facility and encompass all waters and structures therein. No person or vessel may enter or remain in the safety zone unless authorized by the Sector Columbia River Captain of the Port or his designated representatives.</P>
        <P>The safety zone around the TEMCO grain facility in Portland, OR is also enclosed by three lines and the shoreline: line one starting on the shoreline at 45-32′10″ N/122-40′34″ W then heading 150 yards offshore to 45-32′09″ N/122-40′39″ W then heading up river 275 yards to 45-32′01″ N/122-40′33″ then heading 150 yards to the shoreline ending at 45-32′04″ N/122-40′28″ W. In essence, these boundaries extend from the shoreline of the facility 150 yards onto the river from each corner of the facility and encompass all waters and structures therein. No person or vessel may enter or remain in the safety zone unless authorized by the Sector Columbia River Captain of the Port or his designated representatives.</P>

        <P>This rule has been enforced with actual notice since December 7, 2012 and it will be enforced until 30 days from date of publication in the<E T="04">Federal Register</E>.</P>
        <HD SOURCE="HD1">D. Regulatory Analyses</HD>
        <P>We developed this rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on these statutes and executive orders.</P>
        <HD SOURCE="HD2">1. Regulatory Planning and Review</HD>
        <P>This rule is not a significant regulatory action under section 3(f) of Executive Order 12866, Regulatory Planning and Review, 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. Although this rule will restrict access to the regulated areas, the effect of this rule will not be significant because: (i) The safety zones are limited in size; (ii) the official on-scene patrol may authorize access to the safety zones; (iii) the safety zones will effect limited geographical locations for a limited time; and (iv) the Coast Guard will make notifications via maritime advisories so mariners can adjust their plans accordingly.</P>
        <HD SOURCE="HD2">2. Impact on Small Entities</HD>
        <P>The Regulatory Flexibility Act of 1980 (RFA), 5 U.S.C. 601-612, as amended, requires federal agencies to consider the potential impact of regulations on small entities during rulemaking. 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. The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities. This rule will not have a significant economic impact on a substantial number of small entities for the following reasons: (i) The safety zones are limited in size; (ii) the official on-scene patrol may authorize access to the safety zones; (iii) the safety zones will effect limited geographical locations for a limited time; and (iv) the Coast Guard will make notifications via maritime advisories so mariners can adjust their plans accordingly.</P>
        <HD SOURCE="HD2">3. Assistance for Small Entities</HD>

        <P>Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we want to assist small entities in understanding this rule. 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 in the<E T="02">FOR FURTHER INFORMATION CONTACT</E>, above.</P>

        <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman<PRTPAGE P="265"/>and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.</P>
        <HD SOURCE="HD2">4. Collection of Information</HD>
        <P>This rule will not call for a new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
        <HD SOURCE="HD2">5. 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.</P>
        <P>We believe that this rule and the process by which it was drafted adhere to the federalism principles outlined in Executive Order 13132. The Coast Guard has coordinated with the officials from the states of Oregon and Washington in drafting this rule. By allowing state enforcement of this rule, it is in accord with paragraph (h) of section 2 of the Executive Order, which encourages recognition of responsibility of localities and their sub-units to pursue objectives through their own means. This rule puts no obligation on state or municipal governments, but simply allows for their participation in enforcement activities.</P>
        <HD SOURCE="HD2">6. Protest Activities</HD>
        <P>The Coast Guard respects the First Amendment rights of protesters. In preparing this temporary rule, the Coast Guard carefully considered the rights of lawful protestors. The safety zones created by this rule do not prohibit members of the public from assembling on shore or expressing their points of view from locations on shore. In addition, the Captain of the Port has identified waters adjacent to this safety zone where those desiring to do so can assemble and express their views without compromising the safety navigational safety. These suggested protest areas are as follows: TEMCO Kalama Facility from the shoreline at 45-59′10″ N/122-50′09″ W a line heading offshore 150 yards to 45-59′09″ N/122-50′14″ W then heading up river 350 yards to 45-58′58″ N/122-50′07″ W then heading to the shoreline, ending at 45-59′00″ N/122-50′01″ W. TEMCO Irving Facility from the shoreline at 45-32′10″ N/122-40′34″ W a line heading offshore 150 yards to 45-32′09″ N/122-40′39″ W then heading up river 275 yards to 45-32′01″ N/122-40′33″ then heading to the shoreline, ending at 45-32′04″ N/122-40′28″ W.</P>
        <P>Protesters are asked to contact the person listed in the<E T="02">FOR FURTHER INTFORMATION CONTACT</E>section to coordinate protest activities so that your message can be received without jeopardizing the safety or security of people, places or vessels.</P>
        <HD SOURCE="HD2">7. Unfunded Mandates Reform Act</HD>
        <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or more in any one year. Though this rule will not result in such an expenditure, we do discuss the effects of this rule elsewhere in this preamble.</P>
        <HD SOURCE="HD2">8. Taking of Private Property</HD>
        <P>This rule will not cause a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.</P>
        <HD SOURCE="HD2">9. Civil Justice Reform</HD>
        <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.</P>
        <HD SOURCE="HD2">10. Protection of Children</HD>
        <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or risk to safety that may disproportionately affect children.</P>
        <HD SOURCE="HD2">11. Indian Tribal Governments</HD>
        <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
        <HD SOURCE="HD2">12. Energy Effects</HD>
        <P>This action is not a “significant energy action” under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use.</P>
        <HD SOURCE="HD2">13. Technical Standards</HD>
        <P>This rule does not use technical standards. Therefore, we did not consider the use of voluntary consensus standards.</P>
        <HD SOURCE="HD2">14. Environment</HD>

        <P>We have analyzed this rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA) (42 U.S.C. 4321-4370f), and have determined that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment. This rule involves the establishment of temporary safety zones around the Columbia Grain facility on the Willamette River in Portland, OR and the United Grain Corporation facility on the Columbia River in Vancouver, WA. This rule is categorically excluded from further review under paragraph 34(g) of Figure 2-1 of the Commandant Instruction. An environmental analysis checklist supporting this determination and a Categorical Exclusion Determination are available in the docket where indicated under<E T="02">ADDRESSES</E>. We seek any comments or information that may lead to the discovery of a significant environmental impact from this 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, Waterways.</P>
        </LSTSUB>
        
        <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165 as follows:</P>
        <REGTEXT PART="165" TITLE="33">
          <PART>
            <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 165 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>33 U.S.C. 1226, 1231; 46 U.S.C. Chapter 701, 3306, 3703; 50 U.S.C. 191, 195; 33 CFR 1.05-1, 6.04-1, 6.04-6, and 160.5; Pub. L. 107-295, 116 Stat. 2064; Department of Homeland Security Delegation No. 0170.1.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="165" TITLE="33">
          <AMDPAR>2. Add § 165.T13.237 to read as follows:</AMDPAR>
          <SECTION>
            <PRTPAGE P="266"/>
            <SECTNO>§ 165.T13.237</SECTNO>
            <SUBJECT>Safety Zones; TEMCO Grain Facilities; Columbia and Willamette Rivers.</SUBJECT>
            <P>(a)<E T="03">Definitions.</E>As used in this section:</P>
            <P>(1)<E T="03">Federal Law Enforcement Officer</E>means any employee or agent of the United States government who has the authority to carry firearms and make warrantless arrests and whose duties involve the enforcement of criminal laws of the United States.</P>
            <P>(2)<E T="03">Navigable waters of the United States</E>means those waters defined as such in 33 CFR part 2.</P>
            <P>(3)<E T="03">Navigation Rules</E>means the Navigation Rules, International-Inland.</P>
            <P>(4)<E T="03">Official Patrol</E>means those persons designated by the Captain of the Port to monitor a safety zone, permit entry into the zone, give legally enforceable orders to persons or vessels within the zone and take other actions authorized by the Captain of the Port. Federal Law Enforcement Officers authorized to enforce this section are designated as the Official Patrol.</P>
            <P>(5)<E T="03">Public vessel</E>means vessels owned, chartered, or operated by the United States, or by a State or political subdivision thereof.</P>
            <P>(6)<E T="03">Oregon Law Enforcement Officer</E>means any Oregon Peace Officer as defined in Oregon Revised Statutes section 161.015.</P>
            <P>(7)<E T="03">Washington Law Enforcement Officer</E>means any General Authority Washington Peace Officer, Limited Authority Washington Peace Officer, or Specially Commissioned Washington Peace Officer as defined in Revised Code of Washington section 10.93.020.</P>
            <P>(b)<E T="03">Locations.</E>The following areas are safety zones:</P>
            <P>(1) TEMCO Kalama: All navigable waters of the United States within the Sector Columbia River Captain of the Port Zone enclosed by three lines and the shoreline: Line one starting on the shoreline at 45-59′10″ N/122-50′09″ W then heading 150 yards offshore to 45-59′09″ N/122-50′14″ W then heading up river 385 yards to 45-58′58″ N/122-50′07″ then heading 150 yards to the shoreline ending at 45-59′00″ N/122-50′01″ W.</P>
            <P>(2) TEMCO Portland: All navigable waters of the United States within the Sector Columbia River Captain of the Port Zone enclosed by three lines and the shoreline: Line one starting on the shoreline at 45-32′10″ N/122-40′34″ W then heading 150 yards offshore to 45-32′09″ N/122-40′39″ W then heading up river 275 yards to 45-32′01″ N/122-40′33″ then heading 150 yards to the shoreline ending at 45-32′04″ N/122-40′28″ W.</P>
          </SECTION>
        </REGTEXT>
        <P>(c)<E T="03">Effective period.</E>The safety zones created in this section will be in effect from December 7, 2012 and will be enforced until 30 days from date of publication in the<E T="04">Federal Register</E>. They will be activated for enforcement as described in paragraph (d) of this section.</P>
        <P>(d)<E T="03">Enforcement periods.</E>(1) The Sector Columbia River Captain of the Port will cause notice of the enforcement of these safety zones to be made by all appropriate means to effect the widest publicity among the affected segments of the public as practicable, in accordance with 33 CFR 165.7. Such means of notification may include, but are not limited to, Broadcast Notices to Mariners or Local Notices to Mariners. The Sector Columbia River Captain of the Port will issue a Broadcast Notice to Mariners and Local Notice to Mariners notifying the public when enforcement of these safety zones is suspended.</P>
        <P>(2) Upon notice of enforcement by the Sector Columbia River Captain of the Port the Coast Guard will enforce these safety zones in accordance with rules set out in this section. Upon notice of suspension of enforcement by the Sector Columbia River Captain of the Port, all persons and vessels are authorized to enter, transit, and exit the safety zones, consistent with the Navigation Rules.</P>
        <P>(e)<E T="03">Regulation.</E>(1) In accordance with the general regulations in § 165.23 of this part, entry into or movement within these zones is prohibited unless authorized by the Sector Columbia River Captain of the Port, the official patrol, or other designated representatives of the Captain of the Port.</P>
        <P>(2) To request authorization to enter or operate within these safety zones contact the on-scene official patrol on VHF-FM channel 16 or 13. Authorization will be granted based on the necessity of access and consistent with safe navigation.</P>
        <P>(3) Vessels authorized to enter or operate within these safety zones shall operate at the minimum speed necessary to maintain a safe course and shall proceed as directed by the on-scene official patrol. The Navigation Rules shall apply at all times within the safety zones.</P>
        <P>(f)<E T="03">Exemption.</E>Public vessels as defined in paragraph (a) of this section are exempt from complying with paragraph (e) of this section.</P>
        <P>(g)<E T="03">Enforcement.</E>Any Coast Guard commissioned, warrant, or petty officer may enforce the rules in this section. In the navigable waters of the United States to which this section applies, when immediate action is required and representatives of the Coast Guard are not present or are not present in sufficient force to provide effective enforcement of this section, any Federal Law Enforcement Officer, Oregon Law Enforcement Officer, or Washington Law Enforcement Officer may enforce the rules contained in this section pursuant to 46 U.S.C. 70118. In addition, the Captain of the Port may be assisted by other federal, state, or local agencies in enforcing this section.</P>
        <P>(h)<E T="03">Waiver.</E>The Sector Columbia River Captain of the Port may waive any of the requirements of this section for any vessel or class of vessels upon finding that operational conditions or other circumstances are such that application of this section is unnecessary or impractical for the purpose of port safety or environmental safety.</P>
        <SIG>
          <DATED>Dated: December 7, 2012.</DATED>
          <NAME>B.C. Jones,</NAME>
          <TITLE>Captain, U.S. Coast Guard, Captain of the Port, Sector Columbia River.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31561 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-04-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
        <CFR>47 CFR Part 73</CFR>
        <DEPDOC>[MB Docket No. 12-270; RM-11676; DA 12-2024]</DEPDOC>
        <SUBJECT>Radio Broadcasting Services; Maysville, GA</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Communications Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Audio Division, at the request of Appalachian Broadcasting Company, Inc., allots Channel 265A at Maysville, Georgia, as the community's second local service. A staff engineering analysis confirms that Channel 265A can be allotted to Maysville consistent with the minimum distance separation requirements of the Rules with a site restriction 13.4 kilometers (8.3 miles) northwest of the community. The reference coordinates for Channel 265A at Maysville are 34-20-16 NL and 83-39-52 WL.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Effective January 27, 2013.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Secretary, Federal Communications Commission, 445 12th Street SW., Washington, DC 20554.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Rolanda F. Smith, Media Bureau, (202) 418-2700.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>This is a synopsis of the Commission's<E T="03">Report and Order,</E>adopted December 13, 2012, and released December 14, 2012. The full text of this Commission decision is available for inspection and copying<PRTPAGE P="267"/>during normal business hours in the FCC's Reference Information Center at Portals II, CY-A257, 445 12th SW., Washington, DC 20554. This document may also be purchased from the Commission's duplicating contractors, Best Copy and Printing, Inc., 445 12th Street SW., Room CY-B402, Washington, DC 20554, telephone 1-800-378-3160 or via email<E T="03">www.BCPIWEB.com</E>. This document does not contain proposed information collection requirements subject to the Paperwork Reduction Act of 1995, Public Law 104-13. The Commission will send a copy of this<E T="03">Report and Order</E>in a report to be sent to Congress and the Government Accountability Office pursuant to the Congressional Review Act,<E T="03">see</E>5 U.S.C. 801(a)(1)(A).</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 47 CFR Part 73</HD>
          <P>Radio, Radio broadcasting.</P>
        </LSTSUB>
        <SIG>
          <FP>Federal Communications Commission.</FP>
          <NAME>Nazifa Sawez,</NAME>
          <TITLE>Assistant Chief, Audio Division, Media Bureau.</TITLE>
        </SIG>
        <P>For the reasons discussed in the preamble, the Federal Communications Commission amends 47 CFR part 73 as follows:</P>
        <REGTEXT PART="73" TITLE="47">
          <PART>
            <HD SOURCE="HED">PART 73—RADIO BROADCAST SERVICES</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 73 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>47 U.S.C. 154, 303, 334, 336 and 339.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="73" TITLE="47">
          <SECTION>
            <SECTNO>§ 73.202</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. Section 73.202(b), the Table of FM Allotments under Georgia, is amended by adding Channel 265A at Maysville.</AMDPAR>
        </REGTEXT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31563 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6712-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <CFR>50 CFR Part 679</CFR>
        <DEPDOC>[Docket No. 111207737-2141-02]</DEPDOC>
        <RIN>RIN 0648-XC422</RIN>
        <SUBJECT>Fisheries of the Exclusive Economic Zone Off Alaska; Inseason Adjustment to the 2013 Gulf of Alaska Pollock and Pacific Cod Total Allowable Catch Amounts</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; inseason adjustment; request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>NMFS is adjusting the 2013 total allowable catch (TAC) amounts for the Gulf of Alaska (GOA) pollock and Pacific cod fisheries. This action is necessary because NMFS has determined these TACs are incorrectly specified, and will ensure the GOA pollock and Pacific cod TACs are the appropriate amounts based on the best available scientific information for pollock and Pacific cod in the GOA. This action is consistent with the goals and objectives of the Fishery Management Plan for Groundfish of the Gulf of Alaska.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>

          <P>Effective 1200 hrs, Alaska local time (A.l.t.), December 28, 2012, until the effective date of the final 2013 and 2014 harvest specifications for GOA groundfish, unless otherwise modified or superseded through publication of a notification in the<E T="04">Federal Register</E>.</P>
          <P>Comments must be received at the following address no later than 4:30 p.m., A.l.t., January 18, 2013.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments on this document, identified by FDMS Docket Number NOAA-NMFS-2012-0252 by any of the following methods:</P>
          <P>•<E T="03">Electronic Submission:</E>Submit all electronic public comments via the Federal e-Rulemaking Portal. Go to<E T="03">www.regulations.gov/#!docketDetail;D=NOAA-NMFS-2012-0252,</E>click the “Comment Now!” icon, complete the required fields, and enter or attach your comments.</P>
          <P>•<E T="03">Mail:</E>Address written comments to Glenn Merrill, Assistant Regional Administrator, Sustainable Fisheries Division, Alaska Region NMFS, Attn: Ellen Sebastian. Mail comments to P.O. Box 21668, Juneau, AK 99802-1668.</P>
          <P>•<E T="03">Fax:</E>Address written comments to Glenn Merrill, Assistant Regional Administrator, Sustainable Fisheries Division, Alaska Region NMFS, Attn: Ellen Sebastian. Fax comments to 907-586-7557.</P>
          <P>•<E T="03">Hand delivery to the Federal Building:</E>Address written comments to Glenn Merrill, Assistant Regional Administrator, Sustainable Fisheries Division, Alaska Region NMFS, Attn: Ellen Sebastian. Deliver comments to 709 West 9th Street, Room 420A, Juneau, AK.</P>
          <P>
            <E T="03">Instructions:</E>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 by NMFS. All comments received are a part of the public record and will generally be posted for public viewing on<E T="03">www.regulations.gov</E>without change. All personal identifying information (e.g., name, address, etc.), confidential business information, or otherwise sensitive information submitted voluntarily by the sender will be publicly accessible. 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, Excel, or Adobe PDF file formats only.</P>
        </ADD>
        <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 (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 final 2012 and 2013 harvest specifications for groundfish in the GOA (77 FR 15194, March 14, 2012) set the 2013 pollock TAC at 125,334 metric tons (mt) and the 2013 Pacific cod TAC at 68,250 mt in the GOA. In December 2012, the North Pacific Fishery Management Council (Council) recommended a 2013 pollock TAC of 121,046 mt for the GOA, which is less than the 125,334 mt established by the final 2012 and 2013 harvest specifications for groundfish in the GOA. The Council also recommended a 2013 Pacific cod TAC of 60,600 mt for the GOA, which is less than the 68,250 mt established by the final 2012 and 2013 harvest specifications for groundfish in the GOA. The Council's recommended 2013 TACs, and the area and seasonal apportionments, are based on the Stock Assessment and Fishery Evaluation report (SAFE), dated November 2012, which NMFS has determined is the best available scientific information for these fisheries.</P>

        <P>Steller sea lions occur in the same location as the pollock and Pacific cod fisheries and are listed as endangered under the Endangered Species Act (ESA). Pollock and Pacific cod are a principal prey species for Steller sea lions in the GOA. The seasonal apportionment of pollock and Pacific cod harvest is necessary to ensure the groundfish fisheries are not likely to cause jeopardy of extinction or adverse modification of critical habitat for Steller sea lions. The regulations at § 679.20(a)(5)(iv) specify how the pollock TAC will be apportioned. The<PRTPAGE P="268"/>regulations at § 679.20(a)(6)(ii) and § 679.20(a)(12)(i) specify how the Pacific cod TAC will be apportioned.</P>
        <P>In accordance with § 679.25(a)(1)(iii) and (a)(2)(i)(B), the Administrator, Alaska Region, NMFS (Regional Administrator), has determined that, based on the November 2012 SAFE report for this fishery, the current GOA pollock and Pacific cod TACs are incorrectly specified. Consequently, pursuant to § 679.25(a)(1)(iii), the Regional Administrator is adjusting the 2013 GOA pollock TAC to 121,046 mt and the 2013 GOA Pacific cod TAC to 60,600 mt. Therefore, Table 2 of the final 2012 and 2013 harvest specifications for groundfish in the GOA (77 FR 15194, March 14, 2012) is revised consistent with this adjustment.</P>
        <P>Pursuant to § 679.20(a)(5)(iv), Table 4 of the final 2012 and 2013 harvest specifications for groundfish in the GOA (77 FR 15194, March 14, 2012) is revised for the 2013 TACs of pollock in the Central and Western Regulatory Area of the GOA.</P>
        <GPH DEEP="279" SPAN="3">
          <GID>ER03JA13.077</GID>
        </GPH>
        <P>Pursuant to § 679.20(a)(6)(ii) and § 679.20(a)(12)(i), Table 6 of the final 2012 and 2013 harvest specifications for groundfish in the GOA (77 FR 15194, March 14, 2012) is revised for the 2013 seasonal apportionments and allocation of Pacific cod TAC in the GOA consistent with this adjustment.</P>

        <P>The proposed 2013 and 2014 harvest specifications for groundfish of the GOA were published in the<E T="04">Federal Register</E>on December 5, 2012 (77 FR 72297). In accordance with the FMP, the annual jig sector allocations may increase to up to 6 percent of the annual Western and Central GOA Pacific cod TACs depending on the annual performance of the jig sector. NMFS has proposed increasing the jig sector's Pacific cod allocation in the Western GOA to 2.5 percent of the annual Pacific cod TAC. This includes a base allocation of 1.5 percent and an additional 1.0 percent because this sector harvested greater than 90 percent of its initial 2012 allocation in the Western GOA. NMFS also has proposed increasing the jig sector's Pacific cod allocation in the Central GOA to 2.0 percent of the annual Pacific cod TAC. This includes a base allocation of 1.0 percent and an additional 1.0 percent because this sector harvested greater than 90 percent of its initial 2012 allocation in the Central GOA. Therefore, as described in the proposed 2013 and 2014 harvest specifications for the GOA (December 5, 2012, 77 FR 72297), the final 2013 and 2014 Pacific cod sector allocations may be adjusted to incorporate the increased allocation to the jig sector. The proposed increased percentage allocations to the jig sectors in the Western and Central GOA are not included in the following table.</P>
        <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        <GPH DEEP="582" SPAN="3">
          <PRTPAGE P="269"/>
          <GID>ER03JA13.078</GID>
        </GPH>
        <BILCOD>BILLING CODE 3510-22-C</BILCOD>
        <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 allow for harvests that exceed the appropriate allocations for Pacific cod based on the best scientific information available. NMFS was unable to publish a notice providing time for public comment because the most recent,<PRTPAGE P="270"/>relevant data only became available as of December 27, 2012, and additional time for prior public comment would result in conservation concerns for the ESA-listed Steller sea lions.</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>Under § 679.25(c)(2), interested persons are invited to submit written comments on this action to the above address until January 18, 2013.</P>
        <P>This action is required by § 679.20 and § 679.25 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: December 28, 2012.</DATED>
          <NAME>Lindsay Fullenkamp,</NAME>
          <TITLE>Acting Deputy Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31627 Filed 12-28-12; 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. 111207737-2141-02]</DEPDOC>
        <RIN>RIN 0648-XC423</RIN>
        <SUBJECT>Fisheries of the Exclusive Economic Zone Off Alaska; Inseason Adjustment to the 2013 Bering Sea and Aleutian Islands Pollock, Atka Mackerel, and Pacific Cod Total Allowable Catch Amounts</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; inseason adjustment; request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>NMFS is adjusting the 2013 total allowable catch (TAC) amounts for the Bering Sea and Aleutian Islands (BSAI) pollock, Atka mackerel, and Pacific cod fisheries. This action is necessary because NMFS has determined these TACs are incorrectly specified, and will ensure the BSAI pollock, Atka mackerel, and Pacific cod TACs are the appropriate amounts based on the best available scientific information. This action is consistent with the goals and objectives of the Fishery Management Plan for Groundfish of the Bering Sea and Aleutian Islands Management Area.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>

          <P>Effective 1200 hrs, Alaska local time (A.l.t.), December 28, 2012, until the effective date of the final 2013 and 2014 harvest specifications for BSAI groundfish, unless otherwise modified or superseded through publication of a notification in the<E T="04">Federal Register</E>.</P>
          <P>Comments must be received at the following address no later than 4:30 p.m., A.l.t., January 18, 2013.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments on this document, identified by FDMS Docket Number NOAA-NMFS-2012-0253 by any of the following methods:</P>
          <P>•<E T="03">Electronic Submission:</E>Submit all electronic public comments via the Federal e-Rulemaking Portal. Go to<E T="03">www.regulations.gov/#!docketDetail;D=NOAA-NMFS-2012-0253,</E>click the “Comment Now!” icon, complete the required fields, and enter or attach your comments.</P>
          <P>•<E T="03">Mail:</E>Address written comments to Glenn Merrill, Assistant Regional Administrator, Sustainable Fisheries Division, Alaska Region NMFS, Attn: Ellen Sebastian. Mail comments to P.O. Box 21668, Juneau, AK 99802-1668.</P>
          <P>•<E T="03">Fax:</E>Address written comments to Glenn Merrill, Assistant Regional Administrator, Sustainable Fisheries Division, Alaska Region NMFS, Attn: Ellen Sebastian. Fax comments to 907-586-7557.</P>
          <P>•<E T="03">Hand delivery to the Federal Building:</E>Address written comments to Glenn Merrill, Assistant Regional Administrator, Sustainable Fisheries Division, Alaska Region NMFS, Attn: Ellen Sebastian. Deliver comments to 709 West 9th Street, Room 420A, Juneau, AK.</P>
          <P>
            <E T="03">Instructions:</E>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 by NMFS. All comments received are a part of the public record and will generally be posted for public viewing on<E T="03">www.regulations.gov</E>without change. All personal identifying information (<E T="03">e.g.,</E>name, address, etc.), confidential business information, or otherwise sensitive information submitted voluntarily by the sender will be publicly accessible. 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, Excel, or Adobe PDF file formats only.</P>
        </ADD>
        <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 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 final 2012 and 2013 harvest specifications for groundfish in the BSAI (77 FR 10669, February 23, 2012) set the 2013 BSAI pollock TAC at 1,220,900 metric tons (mt), the 2013 BSAI Atka mackerel TAC at 42,083 mt, and the 2013 BSAI Pacific cod TAC at 262,900 mt. In December 2012, the North Pacific Fishery Management Council (Council) recommended a 2013 BSAI pollock TAC of 1,266,100 mt, which is more than the 1,220,900 mt TAC established by the final 2012 and 2013 harvest specifications for groundfish in the BSAI. The Council also recommended a 2013 BSAI Atka mackerel TAC of 25,920 mt, which is less than the 42,083 mt TAC established by the final 2012 and 2013 harvest specifications for groundfish in the BSAI. Furthermore, the Council recommended a 2013 BSAI Pacific cod TAC of 260,000 mt, which is less than the 262,900 mt TAC established by the final 2012 and 2013 harvest specifications for groundfish in the BSAI. The Council's recommended 2013 TACs, and the area and seasonal apportionments, are based on the Stock Assessment and Fishery Evaluation report (SAFE), dated November 2012, which NMFS has determined is the best available scientific information for these fisheries.</P>
        <P>Steller sea lions occur in the same location as the pollock, Atka mackerel, and Pacific cod fisheries and are listed as endangered under the Endangered Species Act (ESA). Pollock, Atka mackerel, and Pacific cod are a principal prey species for Steller sea lions in the BSAI. The seasonal apportionment of pollock, Atka mackerel, and Pacific cod harvest is necessary to ensure the groundfish fisheries are not likely to cause jeopardy of extinction or adverse modification of critical habitat for Steller sea lions. The regulations at § 679.20(a)(5) specify how the BS pollock TAC will be apportioned. The regulations at § 679.20(a)(7) specify how the BSAI Pacific cod TAC will be apportioned. The regulations at § 679.20(a)(8) specify how the BSAI Atka mackerel TAC will be apportioned.</P>

        <P>In accordance with § 679.25(a)(1)(iii), (a)(2)(i)(B), and (a)(2)(iv), the Administrator, Alaska Region, NMFS<PRTPAGE P="271"/>(Regional Administrator), has determined that, based on the November 2012 SAFE report for this fishery, the current BSAI pollock, Atka mackerel, and Pacific cod TACs are incorrectly specified. Pursuant to § 679.25(a)(1)(iii), the Regional Administrator is adjusting the 2013 BSAI pollock TAC to 1,266,100 mt, the 2013 BSAI Atka mackerel TAC to 25,920 and the 2013 BSAI Pacific cod TAC to 260,000 mt. Therefore, Table 1 of the final 2012 and 2013 harvest specifications for groundfish in the BSAI (77 FR 10669, February 23, 2012) is revised consistent with this adjustment.</P>
        <P>Pursuant to § 679.20(a)(5)(i), Table 3 of the final 2012 and 2013 harvest specifications for groundfish in the BSAI (77 FR 10669, February 23, 2012) and reallocation (77 FR 12214, February 29, 2012) is revised for the 2013 BSAI allocations of pollock TAC to the directed pollock fisheries and to the Community Development Quota (CDQ) directed fishing allowances consistent with this adjustment.</P>
        <GPH DEEP="565" SPAN="3">
          <GID>ER03JA13.074</GID>
        </GPH>
        <PRTPAGE P="272"/>
        <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        <P>Pursuant to § 679.20(a)(8), Table 4 of the final 2012 and 2013 harvest specifications for groundfish in the BSAI (77 FR 10669, February 23, 2012) and reallocation (77 FR 61300, October 9, 2012) is revised for the 2013 seasonal and spatial allowances, gear shares, CDQ reserve, incidental catch allowance, and Amendment 80 allocation of the BSAI Atka mackerel TAC.</P>
        <GPH DEEP="620" SPAN="3">
          <GID>ER03JA13.076</GID>
        </GPH>
        <PRTPAGE P="273"/>
        <P>Pursuant to § 679.20(a)(7), Table 5b of the final 2012 and 2013 harvest specifications for groundfish in the BSAI (77 FR 10669, February 23, 2012) is revised for the 2013 gear shares and seasonal allowances of the BSAI Pacific cod TAC consistent with this adjustment.</P>
        <GPH DEEP="523" SPAN="3">
          <GID>ER03JA13.075</GID>
        </GPH>
        <BILCOD>BILLING CODE 3510-22-C</BILCOD>
        <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 allow for harvests that exceed the appropriate allocations for pollock, Atka mackerel, and Pacific cod in the BSAI based on the best scientific information available. NMFS was unable to publish a notice providing time for public comment because the most recent, relevant data only became available as of December 26, 2012, and additional<PRTPAGE P="274"/>time for prior public comment would result in conservation concerns for the ESA-listed Steller sea lions.</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>Under § 679.25(c)(2), interested persons are invited to submit written comments on this action to the above address until January 18, 2013.</P>
        <P>This action is required by § 679.20 and § 679.25 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: December 28, 2012.</DATED>
          <NAME>Lindsay Fullenkamp,</NAME>
          <TITLE>Acting Deputy Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31635 Filed 12-28-12; 4:15 pm]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </RULE>
  </RULES>
  <VOL>78</VOL>
  <NO>2</NO>
  <DATE>Thursday, January 3, 2013</DATE>
  <UNITNAME>Proposed Rules</UNITNAME>
  <PRORULES>
    <PRORULE>
      <PREAMB>
        <PRTPAGE P="275"/>
        <AGENCY TYPE="F">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Federal Aviation Administration</SUBAGY>
        <CFR>14 CFR Part 39</CFR>
        <DEPDOC>[Docket No. FAA-2012-1346; Directorate Identifier 2012-CE-047-AD]</DEPDOC>
        <RIN>RIN 2120-AA64</RIN>
        <SUBJECT>Airworthiness Directives; REIMS Aviation S.A. Airplanes</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Aviation Administration (FAA), Department of Transportation (DOT).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of proposed rulemaking (NPRM).</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>We propose to adopt a new airworthiness directive (AD) for REIMS AVIATION S.A. Model F406 airplanes. 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 fretting (wear and/or chafing) found between the elevator pushrod assembly and horizontal tail structure, which could cause the elevator pushrod to jam and could result in loss of control. We are issuing this proposed AD to require actions to address the unsafe condition on these products.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>We must receive comments on this proposed AD by February 19, 2013.</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 20590, 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 REIMS Aviation Industries, Aérodrome de Reims Prunay, 51360 Prunay, France; telephone: 03.26.48.46.65; fax: 03.26.49.18.57; Internet:<E T="03">http://www.geciaviation.com/en/</E>. You may review copies of the referenced service information at the FAA, Small Airplane Directorate, 901 Locust, Kansas City, Missouri 64106. For information on the availability of this material at the FAA, call (816)  329-4148.</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 (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>Albert Mercado, Aerospace Engineer, FAA, Small Airplane Directorate, 901 Locust, Room 301, Kansas City, Missouri 64106; telephone: (816) 329-4119; fax: (816) 329-4090; email:<E T="03">albert.mercado@faa.gov</E>.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Comments Invited</HD>

        <P>We invite you to send any written relevant data, views, or arguments about this proposed AD. Send your comments to an address listed under the<E T="02">ADDRESSES</E>section. Include “Docket No. FAA-2012-1346; Directorate Identifier 2012-CE-047-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 http://regulations.gov, including any personal information you provide. We will also post a report summarizing each substantive verbal contact we receive about this proposed AD.</P>
        <HD SOURCE="HD1">Discussion</HD>
        <P>The European Aviation Safety Agency (EASA), which is the Technical Agent for the Member States of the European Community, has issued AD No. 2012-0164, dated August 28, 2012 (referred to after this as “the MCAI”), to correct an unsafe condition for the specified products. The MCAI states:</P>
        
        <EXTRACT>
          <P>During maintenance, fretting has been found between the elevator pushrod assembly and horizontal tail structure on Reims F406 aeroplanes. In addition, bending was found on a pushrod assembly Part Number (P/N) 6015034-1. The investigation has not yet established the exact cause(s) of these occurrences.</P>
          <P>This condition, if not detected and corrected, could lead to failure of a pushrod and consequent jamming of the elevator controls, possibly resulting in loss of control of the aeroplane.</P>
          <P>For the reasons described above, this AD requires inspection of the pushrods and horizontal tail structure to detect fretting, bending or eccentricity and, depending on findings, replacement with a serviceable pushrod, or repair. This AD also requires the return on replaced pushrods to RAI for investigation.</P>
          <P>This AD is considered to be an interim action and further AD action may follow.</P>
        </EXTRACT>
        
        <P>You may obtain further information by examining the MCAI in the AD docket.</P>
        <HD SOURCE="HD1">Relevant Service Information</HD>
        <P>REIMS Aviation Industries has issued Service Bulletin No. F406-70, dated July 16, 2012. The actions described in this service information are intended to correct the unsafe condition identified in the MCAI.</P>
        <HD SOURCE="HD1">FAA's Determination and Requirements of the Proposed AD</HD>

        <P>This product has been approved by the aviation authority of another country, and is approved for operation in the United States. Pursuant to our bilateral agreement with this State of Design Authority, they have notified us of the unsafe condition described in the MCAI and service information referenced above. We are proposing this AD because we evaluated all information and determined the unsafe condition exists and is likely to exist or develop on other products of the same type design.<PRTPAGE P="276"/>
        </P>
        <HD SOURCE="HD1">Costs of Compliance</HD>
        <P>We estimate that this proposed AD would affect 7 products of U.S. registry. We also estimate that it would take about 4 work-hours per product to comply with the basic requirements of this proposed AD. The average labor rate is $85 per work-hour.</P>
        <P>Based on these figures, we estimate the cost of this proposed AD on U.S. operators to be $2,380, or $340 per product.</P>
        <P>In addition, we estimate that any necessary follow-on actions would take about 2.5 work-hours and require parts costing $1,900, for a cost of $2,112.50 per product. We have no way of determining the number of products that may need these actions.</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),</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>
        </PART>
        <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>49 U.S.C. 106(g), 40113, 44701.</P>
        </AUTH>
        <SECTION>
          <SECTNO>§ 39.13</SECTNO>
          <SUBJECT>[Amended]</SUBJECT>
        </SECTION>
        <AMDPAR>2. The FAA amends § 39.13 by adding the following new AD:</AMDPAR>
        
        <EXTRACT>
          <FP SOURCE="FP-2">
            <E T="04">REIMS Aviation S.A.:</E>Docket No. FAA-2012-1346; Directorate Identifier 2012-CE-047-AD.</FP>
          <HD SOURCE="HD1">(a) Comments Due Date</HD>
          <P>We must receive comments by February 19, 2013.</P>
          <HD SOURCE="HD1">(b) Affected ADs</HD>
          <P>None.</P>
          <HD SOURCE="HD1">(c) Applicability</HD>
          <P>This AD applies to Reims Aviation S.A. Model F406 airplanes, serial numbers F406-0001 through F406-0096, certificated in any category.</P>
          <HD SOURCE="HD1">(d) Subject</HD>
          <P>Air Transport Association of America (ATA) Code 27: Flight Controls.</P>
          <HD SOURCE="HD1">(e) Reason</HD>
          <P>This AD was prompted by reports of fretting (wear and/or chafing) found between the elevator pushrod assembly and horizontal tail structure. We are issuing this AD to detect and correct any discrepancies with the elevator pushrod assembly and the horizontal tail structure, which could cause the elevator pushrod to fail. Failure of the elevator pushrod could cause the flight control to jam, which could result in loss of control.</P>
          <HD SOURCE="HD1">(f) Actions and Compliance</HD>
          <P>Unless already done, do the following actions:</P>
          <P>(1) Within the next 4 months after the effective date of this AD, inspect the elevator pushrod assemblies, part number (P/N) 6015034-1, and the horizontal tail structure following the Accomplishment Instructions in REIMS Aviation Industries Service Bulletin No. F406-70, dated July 16, 2012.</P>
          <P>(2) Before further flight after the inspection required in paragraph (f)(1) of this AD, if fretting is found on the horizontal tail structure, or the clearance between the elevator pushrod assemblies and the horizontal tail structure is found to be insufficient, or looseness at riveted end fittings is found on the elevator pushrods, contact REIMS Aviation Industries at the address specified in paragraph (h) of this AD for a repair scheme and incorporate the repair scheme.</P>
          <P>(3) Before further flight after the inspection required in paragraph (f)(1) of this AD, if bending or eccentricity of an elevator pushrod is found that exceeds the allowable limits, replace each affected elevator pushrod with a serviceable part following REIMS Aviation Industries Service Bulletin No. F406-70, dated July 16, 2012.</P>
          <HD SOURCE="HD1">(g) Other FAA AD Provisions</HD>
          <P>The following provisions also apply to this AD:</P>
          <P>(1)<E T="03">Alternative Methods of Compliance (AMOCs):</E>The Manager, Standards Office, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. Send information to ATTN: Albert Mercado, Aerospace Engineer, FAA, Small Airplane Directorate, 901 Locust, Room 301, Kansas City, Missouri 64106; telephone: (816) 329-4119; fax: (816) 329-4090; email:<E T="03">albert.mercado@faa.gov</E>. Before using any approved AMOC on any airplane to which the AMOC applies, notify your appropriate principal inspector (PI) in the FAA Flight Standards District Office (FSDO), or lacking a PI, your local FSDO.</P>
          <P>(2)<E T="03">Airworthy Product:</E>For any requirement in this AD to obtain corrective actions from a manufacturer or other source, use these actions if they are FAA-approved. Corrective actions are considered FAA-approved if they are approved by the State of Design Authority (or their delegated agent). You are required to assure the product is airworthy before it is returned to service.</P>
          <P>(3)<E T="03">Reporting Requirements:</E>For any reporting requirement in this AD, a federal agency may not conduct or sponsor, and a person is not required to respond to, nor shall a person be subject to a penalty for failure to comply with a collection of information subject to the requirements of the Paperwork Reduction Act unless that collection of information displays a current valid OMB Control Number. The OMB Control Number for this information collection is 2120-0056. Public reporting for this collection of information is estimated to be approximately 5 minutes per response, including the time for reviewing instructions, completing and reviewing the collection of information. All responses to this collection of information are mandatory. Comments concerning the accuracy of this burden and suggestions for reducing the burden should be directed to the FAA at: 800 Independence Ave. SW., Washington, DC 20591, Attn: Information Collection Clearance Officer, AES-200.</P>
          <HD SOURCE="HD1">(h) Related Information</HD>

          <P>Refer to MCAI European Aviation Safety Agency (EASA) AD No. 2012-0164, dated August 28, 2012, and REIMS Aviation Industries Service Bulletin No. F406-70, dated July 16, 2012, for related information. For service information related to this AD, contact REIMS Aviation Industries, Aérodrome de Reims Prunay, 51360 Prunay,<PRTPAGE P="277"/>France; telephone: 03.26.48.46.65; fax: 03.26.49.18.57; Internet:<E T="03">http://www.geciaviation.com/en/.</E>You may review copies of the referenced service information at the FAA, Small Airplane Directorate, 901 Locust, Kansas City, Missouri 64106. For information on the availability of this material at the FAA, call (816)  329-4148.</P>
        </EXTRACT>
        <SIG>
          <DATED>Issued in Kansas City, Missouri, on December 27, 2012.</DATED>
          <NAME>John Colomy,</NAME>
          <TITLE>Acting Manager, Small Airplane Directorate, Aircraft Certification Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31602 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-13-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Food and Drug Administration</SUBAGY>
        <CFR>21 CFR Part 15</CFR>
        <DEPDOC>[Docket No. FDA-2012-N-1148]</DEPDOC>
        <SUBJECT>Food and Drug Administration Actions Related to Nicotine Replacement Therapies and Smoking-Cessation Products; Report to Congress on Innovative Products and Treatments for Tobacco Dependence; Public Hearing; Extension of Comment Period</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Food and Drug Administration, HHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notification of public hearing; Extension of comment period.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The Food and Drug Administration (FDA) is extending the comment period for the notice of public hearing that appeared in the<E T="04">Federal Register</E>of November 28, 2012 (77 FR 70955). In the public hearing notice, FDA requested comments on FDA consideration of applicable approval mechanisms and additional indications for nicotine replacement therapies (NRTs), and input on a report to Congress examining the regulation and development of innovative products and treatments for tobacco dependence. The Agency is taking this action to allow interested persons additional time to submit comments.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Submit either electronic or written comments by January 16, 2013.</P>
        </EFFDATE>
        <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. Identify comments 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>Ayanna Augustus, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave. Bldg. 22, Rm. 3219, Silver Spring, MD 20993, 301-796-3980, FAX: 301-796-2310, email:<E T="03">Section918PublicMeeting@fda.hhs.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background</HD>
        <P>In the<E T="04">Federal Register</E>of November 28, 2012, FDA published a document announcing a public meeting on December 17, 2012, and the opening of a public docket to receive comments related to the implementation of section 918 of the FD&amp;C Act (21 U.S.C. 387r), as amended by the Tobacco Control Act (Pub. L. 111-31). Under Section 918(a), the Secretary of the Department of Health and Human Services (the Secretary of HHS) is required to consider certain new approval mechanisms and additional indications for NRTs. Several NRTs, including nicotine-containing gums, patches, and lozenges, are already marketed for smoking cessation. Section 918(b) requires that the Secretary of HHS, after consultation with recognized scientific, medical, and public health experts, submit a report to Congress examining how best to regulate, promote, and encourage the development of “innovative products and treatments (including nicotine-based and non-nicotine-based products and treatments)” to better achieve the following three goals: (1) Total abstinence from tobacco use, (2) reductions in consumption of tobacco, and (3) reductions in the harm associated with continued tobacco use. FDA will consider the information it obtains from the public hearing and related docket submissions in its implementation of the requirements of section 918, including in drafting the report to Congress required by section 918(b).</P>
        <HD SOURCE="HD1">II. Submission of Comments</HD>

        <P>Interested persons may submit either electronic comments regarding this document to<E T="03">http://www.regulations.gov</E>or written comments to the Division of Dockets Management (see<E T="02">ADDRESSES</E>). It is only necessary to send one set of 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, and will be posted to the docket at<E T="03">http://www.regulations.gov</E>.</P>
        <SIG>
          <DATED>Dated: December 27, 2012.</DATED>
          <NAME>Leslie Kux,</NAME>
          <TITLE>Assistant Commissioner for Policy.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31578 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4160-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <CFR>40 CFR Parts 9, 63, 80, 85, 122, 123, and 412</CFR>
        <DEPDOC>[EPA-HQ-OW-2012-0813, FRL-9764-8]</DEPDOC>
        <SUBJECT>Section 610 Review of NPDES Permit Regulation and Effluent Limitations Guidelines Standards for Concentrated Animal Feeding Operations (CAFOs); Extension of Comment Period</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Extension of public comment period.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>On October 31, 2012 the EPA published a request for comments on a Regulatory Flexibility Act section 610 review titled, Section 610 Review of NPDES Permit Regulation and Effluent Limitations Guidelines Standards for Concentrated Animal Feeding Operations (CAFOs). As initially published in the<E T="04">Federal Register</E>, written comments were to be submitted to the EPA on or before December 31, 2012 (a 60-day public comment period). Since publication, the EPA has received a request for additional time to submit comments. Therefore, the EPA is extending the public comment period for 60 days until March 1, 2013.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>The public comment period for the review published October 31, 2012 (77 FR 65840) is being extended for 60 days to March 1, 2013 in order to provide the public additional time to submit comments and supporting information.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P SOURCE="NPAR">
            <E T="03">Comments:</E>Submit your comments, identified by Docket ID No. EPA-HQ-OW-2012-0813, by one of the following methods:</P>
          <P>•<E T="03">http://www.regulations.gov:</E>Follow the on-line instructions for submitting comments.</P>
          <P>•<E T="03">Email: rfa-sbrefa@epa.gov,</E>Attention Docket ID No. EPA-HQ-OW-2012-0813.</P>
          <P>•<E T="03">Fax:</E>(202) 566-9744.</P>
          <P>•<E T="03">Mail:</E>Water Docket, Environmental Protection Agency, Mailcode: 28221T, Attention Docket ID No. EPA-HQ-OW-2012-0813, 1200 Pennsylvania Ave. NW., Washington, DC 20460.</P>
          <P>•<E T="03">Hand Delivery:</E>EPA Docket Center, EPA West, Room 3334, 1301<PRTPAGE P="278"/>Constitution Avenue NW., Washington, DC, Attention Docket ID No. EPA-HQ-OW-2012-0813. Such deliveries are accepted only during the Docket Center's normal hours of operation, and special arrangements should be made for deliveries of boxed information.</P>
          <P>
            <E T="03">Instructions:</E>Direct your comments to Docket ID No. EPA-HQ-OW-2012-0813. The EPA's policy is that all comments received will be included in the public docket without change and could be made available online at<E T="03">www.regulations.gov,</E>including any personal information provided, unless the comment includes information claimed to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Do not submit information that you consider to be CBI or otherwise protected through<E T="03">www.regulations.gov</E>or email. The<E T="03">www.regulations.gov</E>Web site is an “anonymous access” system, which means that the EPA will not know your identity or contact information unless you provide it in the body of your comment. If you send an email comment directly to the EPA without going through<E T="03">www.regulations.gov</E>your email 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, the 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 the EPA cannot read your comment because of technical difficulties and cannot contact you for clarification, the EPA might 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. For additional information about the EPA's public docket visit the EPA Docket Center homepage at<E T="03">http://www.epa.gov/epahome/dockets.htm.</E>For additional instructions on submitting comments, go to the<E T="02">SUPPLEMENTARY INFORMATION</E>section of this document.</P>
          <P>
            <E T="03">Docket:</E>All documents in the docket are listed in the<E T="03">www.regulations.gov</E>index. Although listed in the index, some information is not publicly available, e.g., CBI or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, will be publicly available only in hard copy. Publicly available docket materials are available either electronically in<E T="03">www.regulations.gov</E>or in hard copy at the Water Docket, EPA/DC, EPA West, Room 3334, 1301 Constitution Ave. NW., Washington, DC 20004. The Public Reading Room is open from 8:30 a.m. to 4:30 p.m., Monday through Friday, excluding federal 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>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>For additional information contact, Hema Subramanian, Office of Wastewater Management (4203M), U.S. Environmental Protection Agency, 1200 Pennsylvania Ave. NW., Washington, DC 20460; telephone number: (202) 564-5041; fax number: (202) 564-6384; email address:<E T="03">subramanian.hema@epa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. General Information</HD>
        <P>Section 610 of the Regulatory Flexibility Act requires that an agency review, within 10 years of promulgation, each rule that has or will have a significant economic impact on a substantial number of small entities (SISNOSE). The EPA undertakes section 610 reviews to decide whether the agency should continue a rule unchanged, amend it, or withdraw it. We encourage small entities to provide comments on the need to change these rules, and in particular, how the rules could be made clearer, more effective, or if there is need to remove conflicting or overlapping requirements with other Federal or State regulations.</P>
        <P>The EPA promulgated revised regulations for CAFOs on February 12, 2003 (68 FR 7175). The “2003 CAFO Rule” expanded the number of operations covered by the CAFO regulations and included requirements to address the land application of manure from CAFOs. The 2003 CAFO Rule required all CAFOs to seek NPDES permit coverage. The EPA developed a Final Regulatory Flexibility Analysis (FRFA) for the 2003 CAFO Rule. In the 2003 CAFO Rule, the EPA took several steps to minimize its impacts on small businesses, including regulatory revisions designed to focus on the largest producers, eliminating the “mixed” animal calculation for operations with more than a single animal type for determining which AFOs are CAFOs, raising the duck threshold for dry manure handling duck operations, and adopting a dry-litter chicken threshold higher than proposed.</P>
        <P>Subsequently, a series of court decisions based on legal challenges to the rulemaking have limited the requirement for NPDES permit coverage specifically to CAFOs that discharge. In response to these court decisions, the EPA made revisions to the CAFO regulations in 2008 (73 FR 70418) and 2012 (77 FR 44494). In promulgating the 2008 regulatory revision, the EPA certified that the 2008 rule would not have a significant adverse economic impact on a substantial number of small entities. In promulgating the 2012 regulatory revision, the 2012 rule was not subject to the RFA because the RFA applies only to rules subject to notice and comment rulemaking requirements under the Administrative Procedure Act (APA) or any other statute, and the 2012 rule was not subject to notice and comment requirements. Both rules reduced the potential impact of the EPA's CAFO regulations on small entities by reducing the universe of CAFOs that must apply for NPDES permits. Although the EPA has made these subsequent revisions to the CAFO regulations, the scope of this 610 review is limited to the impacts on small entities of the 2003 CAFO Rule as amended.</P>
        <HD SOURCE="HD1">II. Extension of Comment Period for the Section 610 Review of the 2003 CAFO Rule</HD>
        <P>The EPA is extending the deadline for submitting comments on the section 610 review of the CAFO Rule to March 1, 2013. The original deadline for comments, based on a 60-day comment period, was December 31, 2012. The EPA's decision responds to a request to extend the comment deadline. The EPA believes that this 60-day extension will assist in providing an adequate amount of additional time for the public to review the action and to provide written comments.</P>
        <SIG>
          <DATED>Dated: December 19, 2012.</DATED>
          <NAME>Alexander Cristofaro,</NAME>
          <TITLE>Director, Office of Regulatory Policy and Management.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31091 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-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>[Docket No. FWS-R4-ES-2012-0020; 92220-1113-0000-C6]</DEPDOC>
        <RIN>RIN 1018-AX60</RIN>
        <SUBJECT>Endangered and Threatened Wildlife and Plants; Reclassification of the Continental United States Breeding Population of the Wood Stork From Endangered to Threatened; Correction</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Fish and Wildlife Service, Interior.</P>
        </AGY>
        <ACT>
          <PRTPAGE P="279"/>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed rule and notice of petition finding; correction.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>On December 26, 2012, we, the U.S. Fish and Wildlife Service, published a proposed rule and petition finding to reclassify the continental United States (U.S.) breeding population of wood stork from endangered to threatened under the Endangered Species Act of 1973, as amended (Act). In that publication, we supplied an incorrect docket number for commenters to use when they send us comments. The correct docket number is FWS-R4-ES-2012-0020.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>

          <P>We will accept comments received or postmarked on or before February 25, 2013. We must receive requests for a public hearing in writing, at the address shown in the<E T="02">FOR FURTHER INFORMATION CONTACT</E>section, by February 11, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments 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 on Docket No. FWS-R4-ES-2012-0020.</P>
          <P>•<E T="03">U.S. mail or hand-delivery:</E>Public Comments Processing, Attn: FWS-R4-ES-2012-0020; Division of Policy and Directives Management; U.S. Fish and Wildlife Service; 4401 N. Fairfax Drive, Suite 222; Arlington, VA 22203.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Field Supervisor, North Florida Ecological Services Field Office, 7915 Baymeadows Way, Suite 200, Jacksonville, FL 32256; telephone 904-731-3336; facsimile 904-731-3045. If you use a telecommunications device for the deaf, please call the Federal Information Relay Service at 800-877-8339, 24 hours a day, 7 days a week.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Correction of Error</HD>
        <P>On December 26, 2012 (77 FR 75947), we published a petition finding and proposed rule to reclassify the continental U.S. breeding population of wood stork from endangered to threatened under the Act (16 U.S.C. 1531 et seq.). In that publication, we supplied an incorrect docket number for commenters to use when they send us comments. We are publishing this notice to clarify that the correct docket number is FWS-R4-ES-2012-0020. However, if you already submitted a comment, you need not resubmit it.</P>
        <HD SOURCE="HD2">Commenting Online</HD>
        <P>In our December<E T="04">Federal Register</E>publication, we inadvertently asked commenters wishing to submit comments online via<E T="03">http://www.regulations.gov</E>to search for our docket using the incorrect docket number, which actually did not appear anywhere on the regulations.gov site. However, users who searched based on key words (e.g., species name) rather than on the incorrect docket number were able to find the document and comment successfully. These comments have been placed into the correct docket. Therefore, if you already submitted a comment via regulations.gov, you need not resubmit it.</P>
        <HD SOURCE="HD2">Commenting via U.S. Mail or Hand-Delivery</HD>
        <P>We also asked commenters submitting hardcopy comments to refer to this incorrect docket number in their comments. However, comments we received by U.S. mail or hand delivery will be routed to the correct docket. If you already submitted a hardcopy comment, you need not resubmit it.</P>
        <HD SOURCE="HD1">Background</HD>

        <P>For the petition finding and proposed rule, please see our original<E T="04">Federal Register</E>document at 77 FR 75947.</P>
        <SIG>
          <NAME>Sara Prigan,</NAME>
          <TITLE>Federal Register Liaison.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31718 Filed 1-2-13; 1:55 pm]</FRDOC>
      <BILCOD>BILLING CODE 4310-55-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <CFR>50 CFR Part 635</CFR>
        <RIN>RIN 0648-BB29</RIN>
        <SUBJECT>Atlantic Highly Migratory Species; 2006 Consolidated Highly Migratory Species Fishery Management Plan; Amendment 5</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 hearings.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>On November 26, 2012, NMFS published a proposed rule for Amendment 5 to the 2006 Consolidated Highly Migratory Species (HMS) Fishery Management Plan (FMP) in response to several shark stock assessments that were completed from 2009 to 2012. As described in the proposed rule, NMFS is proposing measures that would reduce fishing mortality and effort in order to rebuild overfished Atlantic shark species while ensuring that a limited sustainable shark fishery can be maintained consistent with our legal obligations and the 2006 Consolidated HMS FMP as amended. The proposed measures include changes to commercial quotas and species groups, the creation of several time/area closures, a change to an existing time/area closure, an increase in the recreational minimum size restrictions, and the establishment of recreational reporting for certain species of sharks. Comments received by NMFS will be considered in the development and finalization of Amendment 5 to the 2006 Consolidated HMS FMP. This notice announces the rescheduling of the Louisiana public hearing and the addition of two public hearings in Maryland and Texas.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>

          <P>Written comments will be accepted until February 12, 2013. Public hearings, conference calls, and an HMS Advisory Panel meeting for the Amendment 5 proposed rule will be held from December 2012 to February 2013. See<E T="02">SUPPLEMENTARY INFORMATION</E>for meeting dates, times, and locations.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Additional and rescheduled public hearings will be held in Maryland, Texas, and Louisiana. See<E T="02">SUPPLEMENTARY INFORMATION</E>for dates, times, and locations.</P>
          <P>You may submit comments on this document, identified by NOAA-NMFS-2012-0161, by any of the following methods:</P>
          <P>•<E T="03">Electronic Submission:</E>Submit all electronic public comments via the Federal e-Rulemaking Portal. Go to<E T="03">http://www.regulations.gov/#!documentDetail;D=NOAA-NMFS-2012-0161,</E>click the “Comment Now!” icon, complete the required fields, and enter or attach your comments.</P>
          <P>•<E T="03">Mail:</E>Submit written comments to Peter Cooper, SF1/NMFS/NOAA, Highly Migratory Species Management Division, 1315 East-West Highway, Silver Spring, MD 20910. Please mark the outside of the envelope “Comments on the Draft Amendment 5 to the 2006 Consolidated HMS FMP.”</P>
          <P>•<E T="03">Fax:</E>301-713-1917; Attn: Peter Cooper.</P>

          <P>Instructions: 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 generally will be posted for public viewing on<E T="03">www.regulations.gov</E>without change. All personal identifying information (e.g., name, address, etc.) submitted voluntarily by the sender will be<PRTPAGE P="280"/>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>Peter Cooper, Guý DuBeck, Jennifer Cudney or Karyl Brewster-Geisz at 301-427-8503.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>The Atlantic shark fisheries are managed under the Magnuson-Stevens Act. Management of these species is described in the 2006 Consolidated HMS FMP and its amendments, which are implemented by regulations at 50 CFR part 635. Copies of the 2006 Consolidated HMS FMP and amendments are available from NMFS on request (see<E T="02">FOR FURTHER INFORMATION CONTACT</E>).</P>
        <P>On November 26, 2012, NMFS published a proposed rule (77 FR 70552) for draft Amendment 5 to the 2006 Consolidated HMS FMP based on several shark stock assessments that were completed from 2009 to 2012. The assessments for Atlantic blacknose, dusky, and scalloped hammerhead sharks indicated that these species are overfished and experiencing overfishing. As described in the proposed rule, NMFS is proposing measures that would reduce fishing mortality and effort in order to rebuild overfished Atlantic shark species while ensuring that a limited sustainable shark fishery can be maintained consistent with our legal obligations and the 2006 Consolidated HMS FMP. The proposed measures include changes to commercial quotas and species groups, the creation of several time/area closures, a change to an existing time/area closure, an increase in the recreational minimum size restrictions, and the establishment of recreational reporting for certain species of sharks. Any comments received during the comment period will be considered in the development and finalization of Amendment 5 to the 2006 Consolidated HMS FMP.</P>
        <HD SOURCE="HD1">Request for Comments</HD>

        <P>Public hearings in Florida (2), Louisiana, Massachusetts, New Jersey, and North Carolina were recently announced in the<E T="04">Federal Register</E>to provide the opportunity for public comment on the measures described in the proposed rule and draft Amendment 5 (77 FR 73608; December 11, 2012). NMFS will also hold two public conference calls/webinars to provide individuals opportunities to submit public comment if they are unable to attend a public hearing. NMFS has rescheduled the public hearing in Louisiana due to a previously scheduled event in the New Orleans area, which may affect constituent traveling to the public hearing location. Also, NMFS announces two additional public hearings that will be held in Maryland and Texas. The Maryland public hearing will be held in conjunction with a state stakeholder meeting being held by the Maryland Department of Natural Resources on Draft Amendment 5.</P>
        <GPOTABLE CDEF="s50,r50,r50,r100" COLS="4" OPTS="L2,i1">
          <TTITLE>Table 1—Dates, Times and Locations of Upcoming Additional and Rescheduled Public Hearings.</TTITLE>
          <BOXHD>
            <CHED H="1">Venue</CHED>
            <CHED H="1">Date/time</CHED>
            <CHED H="1">Meeting locations</CHED>
            <CHED H="1">Location contact information</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Public Hearing</ENT>
            <ENT>January 15, 2013<LI>5 p.m.-8 p.m.</LI>
            </ENT>
            <ENT>Belle Chasse, LA</ENT>
            <ENT>Belle Chasse Auditorium, 8398 Hwy 23, Belle Chasse, LA 70037.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Public Hearing</ENT>
            <ENT>January 30, 2013<LI>5 p.m.-8 p.m.</LI>
            </ENT>
            <ENT>Ocean Pines, MD</ENT>
            <ENT>Ocean Pines Branch, Worcester County Library, 11107 Cathell Road, Ocean Pines, MD 21811, (410) 208-4014.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Public Hearing</ENT>
            <ENT>February 7, 2013<LI>5 p.m.-8 p.m.</LI>
            </ENT>
            <ENT>Houston, TX</ENT>
            <ENT>Clear Lake City-County Freeman Branch Library, 16616 Diana Lane, Houston, Texas 77062, 281-488-1906</ENT>
          </ROW>
        </GPOTABLE>
        <P>NMFS welcomes comments on any aspect of, or alternative considered, in the proposed rule. NMFS is specifically seeking comments on the administration of dusky shark bycatch caps program in select areas given limited additional observer program resources; the name of reconfigured groupings of sharks that would continue to be managed collectively in the reminder of what is currently the large coastal shark complex for quota monitoring purposes; suggestions for improving angler identification of shark species and reducing dusky shark mortality in the recreational fishery; and whether NMFS should permit the transit of closed areas if certain otherwise prohibited gear is properly stowed and inoperable.</P>
        <HD SOURCE="HD1">Public Hearing Code of Conduct</HD>
        <P>The public is reminded that NMFS expects participants at public hearings and on phone conferences to conduct themselves appropriately. At the beginning of each meeting, a representative of NMFS will explain the ground rules (e.g., alcohol is prohibited from the meeting room; attendees will be called to give their comments in the order in which they registered to speak; each attendee will have an equal amount of time to speak; attendees may not interrupt one another; etc.). The NMFS representative will structure the meeting so that all attending members of the public will be able to comment, if they choose, regardless of the controversial nature of the subject(s). Attendees are expected to respect the ground rules, and those that do not will be asked to leave the meeting.</P>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>16 U.S.C. 971<E T="03">et seq.;</E>16 U.S.C. 1801<E T="03">et seq.</E>
          </P>
        </AUTH>
        <SIG>
          <DATED>Dated: December 27, 2012.</DATED>
          <NAME>Lindsay Fullenkamp,</NAME>
          <TITLE>Acting Deputy Director, Office of Sustainable Fisheries, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31629 Filed 12-28-12; 4:15 pm]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </PRORULE>
  </PRORULES>
  <VOL>78</VOL>
  <NO>2</NO>
  <DATE>Thursday, January 3, 2013</DATE>
  <UNITNAME>Notices</UNITNAME>
  <NOTICES>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="281"/>
        <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
        <DATE>December 28, 2012.</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 and Plant Health Inspection Service</HD>
        <P>
          <E T="03">Title:</E>Stakeholder/Customer Satisfaction Survey.</P>
        <P>
          <E T="03">OMB Control Number:</E>0579-0360.</P>
        <P>
          <E T="03">Summary of Collection:</E>In 2003, the Plant Health Program (PHP) unit, Plant Protection and Quarantine, Animal and Plant Health Inspection Service (APHIS), obtained from the International Organization of Standardization (ISO, nongovernmental worldwide network of national standards institutes) certification in the ISO 9001;2008 standard for its permit services. To meet the ISO 9001;2008 standards, an organization must demonstrate its ability to consistently provide a product that meets customer quality requirements and applicable regulatory requirements, while aiming to enhance customer satisfaction through effective application of the system, including processes for continual improvement of its performance. In order to remain in compliance with Clause 8.2.1 (Customer Satisfaction) of the ISO 9001;2008 standard, PHP must measure the performance of its quality management system by monitoring information related to customer perception in relationship to customer requirements. PHP has determined that the best method for obtaining this information is through the use of stakeholder/customer satisfaction surveys.</P>
        <P>
          <E T="03">Need and Use of the Information:</E>PHP will collect information from the survey to solicit stakeholder and customer feedback with regards to their satisfaction with the regulatory services of Permit Services and Pest Permit Evaluations.</P>
        <P>
          <E T="03">Description of Respondents:</E>Business or other for-profit.</P>
        <P>
          <E T="03">Number of Respondents:</E>500.</P>
        <P>
          <E T="03">Frequency of Responses:</E>Reporting: On occasion.</P>
        <P>
          <E T="03">Total Burden Hours:</E>48.</P>
        <SIG>
          <NAME>Ruth Brown,</NAME>
          <TITLE>Departmental Information Collection Clearance Officer.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31641 Filed 1-2-13; 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>December 27, 2012.</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.</P>

        <P>Comments regarding this information collection received by February 4, 2013 will be considered. Written comments should be addressed to: Desk Officer for Agriculture, Office of Information and Regulatory Affairs, Office of Management and Budget (OMB), New Executive Office Building, 725-17th Street NW., Washington, DC 20502. Commenters are encouraged to submit their comments to OMB via email to:<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. 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>Brucellosis Program.</P>
        <P>
          <E T="03">OMB Control Number:</E>0579-0047.<PRTPAGE P="282"/>
        </P>
        <P>
          <E T="03">Summary of Collection:</E>The Animal Health Protection Act (AHPA) of 2002 is the primary Federal law governing the protection of animal health. The AHPA is contained in Title X, Subtitle E, Sections 10401-18 of Public Law 107-171, May 13 2002, the Farm Security and Rural Investment Act of 2002. Brucellosis is an infectious disease of animals and humans caused by bacteria of the genus<E T="03">Brucella.</E>Veterinary Services, a division with USDA's Animal and Plant Health Inspection Service (APHIS), is responsible for administering regulations intended to protect the health of the U.S. livestock population. The continued presence of brucellosis in a herd seriously threatens the health, welfare, and economic viability of the livestock industry. There is no economically feasible treatment for brucellosis in livestock. The Cooperative State-Federal Brucellosis Eradication Program is a national program to eliminate this serious disease of livestock. APHIS will collect information using various forms.</P>
        <P>
          <E T="03">Need and Use of the Information:</E>APHIS will use the information collected from the forms to demonstrate that program requirements are being met for State and herd status. APHIS also uses the information to demonstrate that program-allowed activities, such as testing, vaccinating, and movement, are being conducted in accordance with program rules. Without the information, APHIS would not be able to conduct an effective bovine brucellosis surveillance and eradication program.</P>
        <P>
          <E T="03">Description of Respondents:</E>Business; State, Local or Tribal Government.</P>
        <P>
          <E T="03">Number of Respondents:</E>89,464.</P>
        <P>
          <E T="03">Frequency of Responses:</E>Recordkeeping; Reporting: On occasion; Quarterly; Monthly.</P>
        <P>
          <E T="03">Total Burden Hours:</E>252,331.</P>
        <HD SOURCE="HD1">Animal and Plant Health Inspection Service</HD>
        <P>
          <E T="03">Title:</E>Horse Protection Regulations.</P>
        <P>
          <E T="03">OMB Control Number:</E>0579-0056.</P>
        <P>
          <E T="03">Summary of Collection:</E>9 CFR Part 11, Regulations, implement the Horse Protection Act of 1970 (Pub. L. 91-540), as amended July 13, 1976 (Pub. L. 94-360), and are authorized under Section 9 of the Act. The Horse Protection Legislation was enacted to prevent showing, exhibiting, selling, or auctioning of “sore” horses, and certain transportation of sore horses in connection therewith at horse shows, horse exhibitions, horse sales, and horse auctions. A sore horse is a horse that has received pain-provoking practices that cause the horse to have an accentuated, high stepping gait. Sored horses cannot be entered in an event by any person, including trainers, riders, or owners. Management of shows, sales, exhibitions, or auctions must identify sored horses to prevent their participation under the Horse Protection Act.</P>
        <P>
          <E T="03">Need and Use of the Information:</E>APHIS will collect information at specified intervals from Horse Industry Organizations (HIO) and show management. HIOs must maintain an acceptable Designated Qualified Person (DQP) program and recordkeeping system as outlined in the regulations. Information provided by the HIOs through DQPs allows APHIS to monitor and enforce the Horse Protection Act, its regulations, and certifying programs.</P>
        <P>
          <E T="03">Description of Respondents:</E>Business or other for-profit.</P>
        <P>
          <E T="03">Number of Respondents:</E>1.514.</P>
        <P>
          <E T="03">Frequency of Responses:</E>Recordkeeping; Reporting: Quarterly; Monthly; Annually.</P>
        <P>
          <E T="03">Total Burden Hours:</E>2,266.</P>
        <SIG>
          <NAME>Ruth Brown,</NAME>
          <TITLE>Departmental Information Collection Clearance Officer.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31566 Filed 1-2-13; 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>December 28, 2012.</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 and 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), Washington, DC,<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-8681.</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">Forest Service</HD>
        <P>
          <E T="03">Title:</E>Application and Permit for Non-Federal Commercial Use of Roads, Trails and Areas Restricted by Regulation or Order.</P>
        <P>
          <E T="03">OMB Control Number:</E>0596-0016.</P>
        <P>
          <E T="03">Summary of Collection:</E>Authority for permits for use of National Forest System (NFS) roads, trails, and areas on NFS lands restricted by order or regulation drives from the National Forest Roads and Trails Act (16 U.S.C. 532-538). The authority for the Road Use Permit process comes from 36 CFR 212.5, 36 CFR 212.9 and 36 CFR 261.54. Section 212.9 authorizes the Forest Service (FS) to develop a road system with private holders that is mutually beneficial to both parties. The FS transportation system includes approximately 380,000 miles of roads. These roads are grouped into five maintenance levels. Level one includes roads, which are closed and maintained only to protect the environment to level five, which is maintained for safe passenger car use. The roads usually provide the only access to commercial products including timber and minerals found on both Federal and private lands within and adjacent to National Forests. Annual maintenance not performed becomes a backlog that creates a financial burden for the FS. To remedy the backlog and pay for needed maintenance the FS requires commercial users to apply and pay for a permit to use the FS Road System. Maintenance resulting from commercial use is accomplished through collection of funds or requiring the commercial users to perform the maintenance.</P>
        <P>
          <E T="03">Need and Use of the Information:</E>Information is collected from individuals, corporations, or organizations on the FS-7700-40 “Application for a Permit for Use of Roads, Trails and Areas Restricted by Regulation or Order” along with FS-<PRTPAGE P="283"/>7700-40a “Commercial Use Attachment” or FS-7700-40b “Oversize Vehicle Attachment” if applicable. The forms provide identifying information about the applicant such as, the name; address; and telephone number; description of mileage of roads; purpose of use; use schedule; and plans for future use. FS will use the information to prepare the applicant's permit, FS-7700-41 or FS-7700-48, to identify the road maintenance that is the direct result of the applicant's traffic, to calculate any applicable collections for recovery of past Federal investments in roads and assure that the requirements are met. Without the Road Use Permit, the backlog of maintenance would increase and the FS would have great difficulty providing the transportation system necessary to meet our mission.</P>
        <P>
          <E T="03">Description of Respondents:</E>Business or other for-profit; Individuals or households; State, Local or Tribal Government; Not-for-profit institutions.</P>
        <P>
          <E T="03">Number of Respondents:</E>2000.</P>
        <P>
          <E T="03">Frequency of Responses:</E>Reporting: On occasion.</P>
        <P>
          <E T="03">Total Burden Hours:</E>196.</P>
        <SIG>
          <NAME>Charlene Parker,</NAME>
          <TITLE>Departmental Information Collection Clearance Officer.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31640 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-11-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Agricultural Marketing Service</SUBAGY>
        <DEPDOC>[Doc. Number FV-11-0052]</DEPDOC>
        <SUBJECT>United States Standards for Grades of Eggplant</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Agricultural Marketing Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Agricultural Marketing Service (AMS), of the Department of Agriculture (USDA), is revising the voluntary United States Standards for Grades of Eggplant. AMS has reviewed the fresh fruit and vegetable grade standards for usefulness in serving the industry. As a result, AMS will amend the similar varietal characteristic requirement in the U.S. Fancy and No. 1 grades to allow mixed colors and/or types of eggplant when designated as a mixed or specialty pack. In addition, AMS will remove the “Unclassified” category from the standards.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>February 4, 2013.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Dave Horner, Standardization Branch, Specialty Crops Inspection Division, (540) 361-1128. The United States Standards for Grades of Eggplant are available through the Specialty Crops Inspection Division Web site at<E T="03">http://www.ams.usda.gov/freshinspection.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>Section 203(c) of the Agricultural Marketing Act of 1946 (7 U.S.C. 1621-1627), as amended, directs and authorizes the Secretary of Agriculture “to develop and improve standards of quality, condition, quantity, grade and packaging and recommend and demonstrate such standards in order to encourage uniformity and consistency in commercial practices.” AMS is committed to carrying out this authority in a manner that facilitates the marketing of agricultural commodities and makes copies of official standards available upon request. The United States Standards for Grades of Fruits and Vegetables not connected with Federal Marketing Orders or U.S. Import Requirements, no longer appear in the Code of Federal Regulations, but are maintained by USDA, AMS, Fruit and Vegetable Programs, and are available on the internet at<E T="03">www.ams.usda.gov/freshinspection.</E>
        </P>
        <P>AMS is revising the voluntary United States Standards for Grades of Eggplant procedures that appear in Part 36, Title 7 of the Code of Federal Regulations (7 CFR part 36).</P>
        <HD SOURCE="HD1">Background and Comments</HD>
        <P>On February 9, 2012, AMS published a notice in the<E T="04">Federal Register</E>(77 FR 6774), soliciting comments regarding amending the varietal characteristic requirement in the U.S. Fancy and No. 1 grades, removing the unclassified section, and any other possible revision to the United States Standards for Grades of Eggplant. The public comment period closed on April 9, 2012, with no responses.</P>
        <P>Based on the information gathered, AMS believes that permitting mixed colors and/or type packs will facilitate the marketing of eggplant by providing the industry with more flexibility that reflects current marketing practices and consumer demand. Therefore, AMS will revise provisions concerning the “U.S. Fancy” and “U.S. No. 1” grades by adding “except when specified as a mixed or specialty pack” to the similar varietal characteristics requirement. In addition, AMS will remove the “Unclassified” category from the standards.</P>
        <P>The official grade of a lot of eggplant covered by these standards will be determined by the procedures set forth in the Regulations Governing Inspection, Certification, and Standards of Fresh Fruits, Vegetables and Other Products (Sec. 51.1 to 51.61).</P>

        <P>The United States Standards for Grades of Eggplant will be effective 30 days after publication of this notice in the<E T="04">Federal Register</E>.</P>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>7 U.S.C. 1621-1627.</P>
        </AUTH>
        <SIG>
          <DATED>Dated: December 28, 2012.</DATED>
          <NAME>Rex A. Barnes,</NAME>
          <TITLE>Administrator, Agricultural Marketing Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31611 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-02-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Food Safety and Inspection Service</SUBAGY>
        <DEPDOC>[Docket Number FSIS-2012-0048]</DEPDOC>
        <RIN>RIN 0583-AD40</RIN>
        <SUBJECT>2013 Rate Changes for the Basetime, Overtime, Holiday, and Laboratory Services Rates</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Food Safety and Inspection Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMMARY:</HD>
          <P>The Food Safety and Inspection Service (FSIS) is announcing the 2013 rates it will charge meat and poultry establishments, egg products plants, and importers and exporters for providing voluntary, overtime, and holiday inspection and identification, certification, and laboratory services. The 2013 basetime, overtime, holiday, and laboratory services rates will be applied on the first FSIS pay period at the beginning of the calendar year, January 13, 2013.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>FSIS will charge the rates announced in this notice beginning January 13, 2013.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>For further information contact Michael Toner, Director, Budget Division, Office of Management, FSIS, U.S. Department of Agriculture, Room 2159 South Building, 1400 Independence Avenue SW., Washington, DC 20250-3700; Telephone (202) 720-8700, Fax (202) 690-4155.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Background</HD>
        <P>On April 12, 2011, FSIS published a final rule amending its regulations to establish formulas for calculating the rates it charges meat and poultry establishments, egg products plants, and importers and exporters for providing voluntary, overtime, and holiday inspection and identification, certification, and laboratory services (76 FR 20220).</P>

        <P>In the final rule, FSIS stated that it would use the formulas to calculate the<PRTPAGE P="284"/>annual rates, publish the rates in<E T="04">Federal Register</E>notices prior to the start of each calendar year, and apply the rates on the first FSIS pay period at the beginning of the calendar year.</P>
        <P>This notice provides the 2013 rates, which will be applied starting on January 13, 2013.</P>
        <HD SOURCE="HD1">2013 Rates and Calculations</HD>
        <P>The following table lists the 2013 Rates per hour, per employee, by type of service:</P>
        <GPOTABLE CDEF="s50,16" COLS="2" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Service</CHED>
            <CHED H="1">2013 Rate<LI>(estimates</LI>
              <LI>rounded to reflect</LI>
              <LI>billable quarters)</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Basetime</ENT>
            <ENT>$55.18</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Overtime</ENT>
            <ENT>69.36</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Holiday</ENT>
            <ENT>83.54</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Laboratory</ENT>
            <ENT>69.01</ENT>
          </ROW>
        </GPOTABLE>
        <P>FSIS determined the 2013 rates using the following calculations:</P>
        <P>
          <E T="03">Basetime Rate</E>= The quotient of dividing the Office of Field Operations (OFO) plus Office of International Affairs (OIA) inspection program personnel's previous fiscal year's regular direct pay by the previous fiscal year's regular hours, plus the quotient multiplied by the calendar year's percentage of cost of living increase, plus the benefits rate, plus the travel and operating rate, plus the overhead rate, plus the allowance for bad debt rate.</P>
        <P>The calculation for the 2013 basetime rate per hour per program employee is:</P>
        
        <FP SOURCE="FP-1">[FY 2012 OFO and OIA Regular Direct Pay divided by the previous fiscal year's Regular Hours ($463,760,597/16,663,724)] = $27.83 + ($27.83 * 1.9% (calendar year 2013 Cost of Living Increase)) = $28.36 + $8.96(benefits rate) + $.70 (travel and operating rate) + $17.15 (overhead rate) + $.01 (bad debt allowance rate) = $55.18.</FP>
        
        <P>
          <E T="03">Overtime Rate</E>= The quotient of dividing the Office of Field Operations (OFO) plus Office of International Affairs (OIA) inspection program personnel's previous fiscal year's regular direct pay by the previous fiscal year's regular hours, plus that quotient multiplied by the calendar year's percentage of cost of living increase, multiplied by 1.5, plus the benefits rate, plus the travel and operating rate, plus the overhead rate, plus the allowance for bad debt rate.</P>
        <P>The calculation for the 2013 overtime rate per hour per program employee is:</P>
        
        <FP SOURCE="FP-1">[FY 2012 OFO and OIA Regular Direct Pay divided by previous fiscal year's Regular Hours ($463,760,597/16,663,724)]= $27.83 + ($27.83 * 1.9% (calendar year 2013 Cost of Living Increase)) =$28.36 * 1.5 = $42.54 + $8.96 (benefits rate) + $.70 (travel and operating rate) + $17.15 (overhead rate) + $.01 (bad debt allowance rate) = $69.36.</FP>
        
        <P>
          <E T="03">Holiday Rate</E>= The quotient of dividing the Office of Field Operations (OFO) plus Office of International Affairs (OIA) inspection program personnel's previous fiscal year's regular direct pay by the previous fiscal year's regular hours, plus that quotient multiplied by the calendar year's percentage of cost of living increase, multiplied by 2, plus the benefits rate, plus the travel and operating rate, plus the overhead rate, plus the allowance for bad debt rate.</P>
        <P>The calculation for the 2013 holiday rate per hour per program employee calculation is:</P>
        
        <FP SOURCE="FP-1">[FY 2012 OFO and OIA Regular Direct Pay divided by Regular Hours ($463,760,597/16,663,724)]= $27.83 + ($27.83 * 1.9% (calendar year 2013 Cost of Living Increase)) =$28.36 * 2 = $56.72 + $8.96(benefits rate) + $.70 (travel and operating rate) + $17.15 (overhead rate) + $.01 (bad debt allowance rate) = $83.54.</FP>
        
        <P>
          <E T="03">Laboratory Services Rate</E>= The quotient of dividing the Office of Public Health Science (OPHS) previous fiscal year's regular direct pay by the OPHS previous fiscal year's regular hours, plus the quotient multiplied by the calendar year's percentage cost of living increase, plus the benefits rate, plus the travel and operating rate, plus the overhead rate, plus the allowance for bad debt rate.</P>
        <P>The calculation for the 2013 laboratory services rate per hour per program employee is:</P>
        
        <FP SOURCE="FP-1">[FY 2012 OPHS Regular Direct Pay/OPHS Regular hours ($22,908,043/553,403)] = $41.39 + ($41.39 * 1.9% (calendar year 2013 Cost of Living Increase)) = $42.18 + $8.96 (benefits rate) + $.70 (travel and operating rate) + $17.15 (overhead rate) + $.01 (bad debt allowance rate) = $69.01.</FP>
        <HD SOURCE="HD1">Calculations for the Benefits, Travel and Operating, Overhead, and Allowance for Bad Debt Rates</HD>
        <P>These rates are components of the basetime, overtime, holiday, and laboratory services rates formulas.</P>
        <P>
          <E T="03">Benefits Rate:</E>The quotient of dividing the previous fiscal year's direct benefits costs by the previous fiscal year's total hours (regular, overtime, and holiday), plus that quotient multiplied by the calendar year's percentage cost of living increase. Some examples of direct benefits are health insurance, retirement, life insurance, and Thrift Savings Plan basic and matching contributions.</P>
        <P>The calculation for the 2013 benefits rate per hour per program employee is:</P>
        
        <FP SOURCE="FP-1">[FY 2012 Direct Benefits/(Total Regular hours + Total Overtime hours + Total Holiday hours) ($171,649,295/19,514,555)] = $8.80 + ($8.80 * 1.9% (calendar year 2013 Cost of Living Increase) = $8.96.</FP>
        
        <P>
          <E T="03">Travel and Operating Rate:</E>The quotient of dividing the previous fiscal year's total direct travel and operating costs by the previous fiscal year's total hours (regular, overtime, and holiday), plus that quotient multiplied by the calendar year's percentage of inflation.</P>
        <P>The calculation for the 2013 travel and operating rate per hour per program employee is:</P>
        
        <FP SOURCE="FP-1">[FY 2012 Total Direct Travel and Operating Costs/(Total Regular hours + Total Overtime hours + Total Holiday hours) ($13,351,831/19,514,555)] = $.68 + ($.68 * 1.6% (2013 Inflation) = $.70.</FP>
        
        <P>
          <E T="03">Overhead Rate:</E>The quotient of dividing the previous fiscal year's indirect costs plus the previous fiscal year's information technology (IT) costs in the Public Health Data Communication Infrastructure System Fund plus the previous fiscal year's Office of Management Program cost in the Reimbursable and Voluntary Funds plus the provision for the operating balance less any Greenbook costs (i.e., costs of USDA support services prorated to the service component for which fees are charged) that are not related to food inspection by the previous fiscal year's total hours (regular, overtime, and holiday) worked across all funds, plus the quotient multiplied by the calendar year's percentage of inflation.</P>
        <P>The calculation for the 2013 overhead rate per hour per program employee is:</P>
        
        <FP SOURCE="FP-1">[FY 2012 Total Overhead/(Total Regular hours + Total Overtime hours + Total Holiday hours)($329,449,845/19,514,555)] = $16.88 + ($16.88 * 1.6% (2013 Inflation) = $17.15.</FP>
        
        <P>
          <E T="03">Allowance for Bad Debt Rate</E>= Previous fiscal year's total allowance for bad debt (for example, debt owed that is not paid in full by plants and establishments that declare bankruptcy) divided by previous fiscal year's total hours (regular, overtime, and holiday) worked.</P>
        <P>The 2013 calculation for bad debt rate per hour per program employee is:</P>
        

        <FP SOURCE="FP-1">[FY 2012 Total Bad Debt/(Total Regular hours + Total Overtime hours + Total Holiday hours) = ($286,335/19,514,555)] = $.01.<PRTPAGE P="285"/>
        </FP>
        <HD SOURCE="HD1">Additional Public Notification</HD>

        <P>FSIS will announce this notice online through the FSIS Web page located at<E T="03">http://www.fsis.usda.gov/regulations_&amp;_policies/Federal_Register_Notices/index.asp.</E>
        </P>
        <P>FSIS will also make copies of this<E T="04">Federal Register</E>publication available through the FSIS Constituent Update, which is used to provide information regarding FSIS policies, procedures, regulations,<E T="04">Federal Register</E>notices, FSIS public meetings, and other types of information that could affect or would be of interest to constituents and stakeholders. The Constituent Update is communicated via Listserv, a free electronic mail subscription service for industry, trade groups, consumer interest groups, health professionals, and other individuals who have asked to be included. The Update is also available on the FSIS Web page. In addition, FSIS offers an electronic mail subscription service which provides automatic and customized access to selected food safety news and information. This service is available at<E T="03">http://www.fsis.usda.gov/News_&amp;_Events/Email_Subscription/.</E>Options range from recalls to export information to regulations, directives and notices. Customers can add or delete subscriptions themselves, and have the option to password protect their accounts.</P>
        <HD SOURCE="HD1">USDA Nondiscrimination Statement</HD>
        <P>The U.S. Department of Agriculture (USDA) prohibits discrimination in all its programs and activities on the basis of race, color, national origin, gender, religion, age, disability, political beliefs, sexual orientation, and marital or family status. (Not all prohibited bases apply to all programs.)</P>
        <P>Persons with disabilities who require alternative means for communication of program information (Braille, large print, audiotape, etc.) should contact USDA's Target Center at 202-720-2600 (voice and TTY).</P>
        <P>To file a written complaint of discrimination, write USDA, Office of the Assistant Secretary for Civil Rights, 1400 Independence Avenue SW., Washington, DC 20250-9410 or call 202-720-5964 (voice and TTY). USDA is an equal opportunity provider and employer.</P>
        <SIG>
          <DATED>Done at Washington, DC, on: December 26, 2012.</DATED>
          <NAME>Alfred V. Almanza,</NAME>
          <TITLE>Administrator.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31556 Filed 1-2-13; 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>Supplemental Final Environmental Impact Statement for Healy Power Generation Unit #2, Healy, AK</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Rural Utilities Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of Intent to Prepare a Supplemental Final Environmental Impact Statement.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Rural Utilities Service (RUS), an agency within the U.S. Department of Agriculture (USDA), intends to prepare a supplemental final environmental impact statement (SFEIS) to update information in the Department of Energy's (DOE's) “Final Environmental Impact Statement for the Proposed Healy Clean Coal Project” (FEIS), completed in 1993. The FEIS evaluated potential impacts to the human environment from DOE's proposal to partially fund the Healy Clean Coal Project (HCCP) in cooperation with the Alaska Industrial Development and Export Authority (AIDEA). The DOE published a Record of Decision for HCCP in 1994, and in 1997 Healy Unit #2 was constructed as a major modification to the existing Healy power plant, now known as Healy Unit #1. Healy Unit #1 is a 25 megawatt (MW) coal-fired boiler that has been owned and operated by Golden Valley Electric Association (GVEA) since 1967. Healy Unit #2 is a 50 MW coal-fired steam generator owned by AIDEA, which underwent test operation for two years as part of DOE's Clean Coal Technology Program. Unit #2 has been in warm layup since late 1999.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>

          <P>The Draft SFEIS is scheduled for publication in February 2013. A notice of availability will be published in the<E T="04">Federal Register</E>announcing the review period of the SFEIS.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>You may submit comments on the SFEIS by any of the following methods: Mail: Deirdre M. Remley, Environmental Protection Specialist, RUS, Water and Environmental Programs, Engineering and Environmental Staff, 1400 Independence Avenue SW., Stop 1571, Washington, DC 20250-1571; Telephone: (202) 720-9640; or email:<E T="03">deirdre.remley@wdc.usda.gov.</E>
          </P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Deirdre Remley: (202) 720-9640,<E T="03">deirdre.remley@wdc.usda.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>RUS makes loans and loan guarantees to finance new infrastructure and upgrades to existing facilities in the areas of electricity, telecommunications, and water and wastewater in rural areas that qualify for federal assistance. During the 1994 USDA reorganization, the former Rural Electrification Administration (REA) utility programs were consolidated under RUS. The RUS Electric Program is authorized to make loans and loan guarantees that finance the construction of electric distribution, transmission, and generation facilities, including system improvements and replacements required to furnish and improve electric service in rural areas, as well as demand side management, energy conservation programs, and on-grid and off-grid renewable energy systems.</P>
        <P>GVEA is a not-for-profit cooperative formed in 1946 with financing from REA to provide electric service to rural communities in interior Alaska. Because GVEA is an RUS borrower, RUS holds liens on GVEA assets and transfers of borrower assets in which RUS holds an interest require lien accommodations. AIDEA provides support for the Alaska Energy Authority whose mission is to reduce the cost of energy in Alaska. AIDEA partially funded HCCP in cooperation with DOE's Clean Coal Technology Program. AIDEA currently owns Healy Unit #2 and wishes to sell it to GVEA.</P>
        <P>RUS's predecessor, REA, was a cooperating agency on DOE's FEIS for HCCP, because it had administrative actions related to its lien interests in GVEA holdings. Recently, AIDEA and GVEA reached an agreement for GVEA to purchase Unit #2. Subsequent to the transfer of ownership, GVEA's subsidiary, Tri-Valley Electrical Cooperative (Tri-VEC), would begin generating electrical power for commercial use in GVEA's service territory.</P>
        <P>GVEA proposes to install additional emission controls to both Unit #1 and Unit #2 and to operate Unit #2 for the remainder of the plant's operational life. GVEA plans to request financial assistance from RUS to purchase and install additional emission control devices. Additionally, actions GVEA may request from RUS include any or all of the following:</P>
        <P>• Approve a Power Sales Agreement from Tri-VEC to GVEA as required under Section 5(c) of RUS Loan Contract dated February 2, 2004 between GVEA and the United States of America.</P>

        <P>• Approve a release of RUS's existing lien on the HCCP site at the time of its sale to Tri-VEC from GVEA, as provided to RUS under the Restated Mortgage and Security Agreement dated February 2, 2004, between GVEA and the United States of America.<PRTPAGE P="286"/>
        </P>
        <P>• Providing financial assistance to GVEA or Tri-VEC for purchase and installation of emission control equipment.</P>

        <P>As applicable, the SFEIS will document changes in the affected environment and environmental consequences that may have occurred since the FEIS was published in 1993. The FEIS is available on GVEA's Web site at<E T="03">http://www.gvea.com/energy/hccp,</E>and the SFEIS will incorporate this document by reference and include only those topics that have changed since the FEIS was finalized.</P>
        <SIG>
          <DATED>Dated: December 4, 2012.</DATED>
          <NAME>Mark S. Plank,</NAME>
          <TITLE>Director, Engineering and Environmental Staff, USDA/Rural Utilities Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31643 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>International Trade Administration</SUBAGY>
        <DEPDOC>[A-489-501]</DEPDOC>
        <SUBJECT>Circular Welded Carbon Steel Pipes and Tubes From Turkey; Amended Final Results of Antidumping Duty Administrative Review; 2010 to 2011</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Import Administration, International Trade Administration, Department of Commerce.</P>
        </AGY>
        
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>On December 6, 2012, the Department of Commerce (the Department) published its final results of the administrative review of the antidumping duty order on circular welded carbon steel pipes and tubes from Turkey for the period of review (POR) May 1, 2010, through April 30, 2011.<SU>1</SU>
            <FTREF/>We are amending our final results to correct a ministerial error made in the calculation of the weighted-average dumping margin for the Borusan Group (Borusan),<SU>2</SU>
            <FTREF/>pursuant to section 751(h) of the Tariff Act of 1930, as amended (the Act).</P>
          <FTNT>
            <P>
              <SU>1</SU>
              <E T="03">See Circular Welded Carbon Steel Pipes and Tubes from Turkey; Final Results of Antidumping Duty Administrative Review; 2010 to 2011,</E>77 FR 72818 (December 6, 2012) (<E T="03">Final Results</E>).</P>
          </FTNT>
          <FTNT>
            <P>

              <SU>2</SU>The Borusan Group includes the following entities: Borusan Mannesmann Boru Sanayi ve Ticaret A.S., Borusan Birlesik Boru Fabrikalari San ve Tic., Borusan Istikbal Ticaret T.A.S., Boruson Gemlik Boru Tesisleri A.S., Borusan Ihracat Ithalat ve Dagitim A.S., Borusan Ithicat ve Dagitim A.S., and Tubeco Pipe and Steel Corporation.<E T="03">See Final Results,</E>77 FR at 72818.</P>
          </FTNT>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>January 3, 2013.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Christopher Hargett, AD/CVD Operations, Office 3, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue NW., Washington, DC 20230; telephone: (202) 482-4161.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Background</HD>
        <P>On December 5, 2012, pursuant to 19 CFR 351.224(c), Borusan alleged that the Department committed a ministerial error and requested that the Department correct this error.<SU>3</SU>
          <FTREF/>Specifically, Borusan alleged that the margin program contains a programming error in identifying the month of sale for U.S. sales with the result that U.S. sales are matched first to home market sales in a month outside of the 90-60 day window.<SU>4</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>3</SU>
            <E T="03">See</E>Letter to the Department from Borusan entitled “Ministerial Error Allegation Submitted on Behalf of Borusan Mannesmann Boru Sanayi ve Ticaret A.S.,” dated December 5, 2012.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>4</SU>
            <E T="03">See id.</E>at 2-3.</P>
        </FTNT>
        <P>On December 10, 2012, U.S. Steel Corporation (U.S. Steel) submitted comments on Borusan's ministerial error allegation.<SU>5</SU>
          <FTREF/>In its submission, U.S. Steel contends that, if the Department accepts Borusan's proposed changes to the margin calculations, the Department also should make an additional modification to the margin program to ensure that the targeted dumping analysis is performed correctly.<SU>6</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>5</SU>
            <E T="03">See</E>Letter to the Department from U.S. Steel regarding the ministerial error allegation submitted by Borusan, dated December 10, 2012.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>6</SU>
            <E T="03">See id.</E>at 2.</P>
        </FTNT>
        <HD SOURCE="HD1">Scope of the Order</HD>
        <P>The products covered by the order include circular welded non-alloy steel pipes and tubes, of circular cross-section, not more than 406.4 millimeters (16 inches) in outside diameter, regardless of wall thickness, surface finish (black, galvanized, or painted), or end finish (plain end, beveled end, threaded and coupled). Those pipes and tubes are generally known as standard pipe, though they may also be called structural or mechanical tubing in certain applications. All carbon steel pipes and tubes within the physical description outlined above are included in the scope of this order, except for line pipe, oil country tubular goods, boiler tubing, cold-drawn or cold-rolled mechanical tubing, pipe and tube hollows for redraws, finished scaffolding, and finished rigid conduit.</P>
        <P>Imports of these products are currently classifiable under the following Harmonized Tariff Schedule of the United States (“HTSUS”) subheadings: 7306.30.10.00, 7306.30.50.25, 7306.30.50.32, 7306.30.50.40, 7306.30.50.55, 7306.30.50.85, and 7306.30.50.90. Although the HTSUS subheadings are provided for convenience and customs purposes, our written description of the scope of this proceeding is dispositive.<SU>7</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>7</SU>For the complete scope of this review,<E T="03">see Certain Welded Carbon Steel Pipe and Tube From Turkey: Notice of Final Results of Antidumping Duty Administrative Review,</E>76 FR 76939 (December 9, 2011).</P>
        </FTNT>
        <HD SOURCE="HD1">Amended Final Results of Review</HD>
        <P>After analyzing Borusan's comments, we have determined, in accordance with section 751(h) of Act and 19 CFR 351.224, that the Department made a ministerial error in the calculation for Borusan regarding the assignment of the sales month for U.S. and home market sales.<SU>8</SU>
          <FTREF/>In particular, the Department correctly stated in the final results that, consistent with our practice, we implemented certain changes to include home market sales starting on November 1, 2009; however, in so doing, we did not implement these changes to the U.S. sales data such that sales made in contemporaneous months in the home market and U.S. market would be matched for calculation of the weighted average dumping margin.<SU>9</SU>
          <FTREF/>Therefore, the Department finds that it made a clerical error when it inadvertently failed to subtract home market sales prices from U.S. sales prices made in contemporaneous months to calculate the weighted-average dumping margin. The Department also finds that U.S. Steel is correct that the margin program must be updated to ensure that the targeted dumping analysis is performed correctly.<SU>10</SU>
          <FTREF/>The Department has now corrected these errors and, consequently, Borusan's final weighted-average dumping margin.</P>
        <FTNT>
          <P>
            <SU>8</SU>
            <E T="03">See</E>Analysis Memorandum for the Borusan Group, dated concurrently with this notice (Borusan Calc Memo).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>9</SU>
            <E T="03">See Final Results,</E>77 FR at 72818, and accompanying Issues and Decision Memorandum at Comment 2.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>10</SU>
            <E T="03">See</E>Borusan Calc Memo.</P>
        </FTNT>

        <P>In accordance with section 751(h) of the Act, we are amending the final results of the antidumping duty administrative review of circular welded carbon steel pipes and tubes from Turkey for the period May 1, 2010, through April 30, 2011. As a result of correcting the ministerial error discussed above, the following weighted-average dumping margin applies:<PRTPAGE P="287"/>
        </P>
        <GPOTABLE CDEF="s50,20C,20C" COLS="3" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Exporter/<LI>manufacturer</LI>
            </CHED>
            <CHED H="1">Final weighted-average dumping margin<LI>(percent)</LI>
            </CHED>
            <CHED H="1">Amended final weighted-average dumping margin<LI>(percent)</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Borusan</ENT>
            <ENT>6.05</ENT>
            <ENT>3.55</ENT>
          </ROW>
        </GPOTABLE>
        <HD SOURCE="HD1">Assessment</HD>
        <P>Pursuant to section 751(a)(2)(A) of the Act and 19 CFR 351.212(b), the Department will determine, and CBP shall assess, antidumping duties on all appropriate entries of subject merchandise in accordance with the amended final results of this review. The Department intends to issue assessment instructions to CBP 15 days after the date of publication of these amended final results of review.</P>

        <P>For assessment purposes, the Department applied the assessment rate calculation method adopted in<E T="03">Antidumping Proceedings: Calculation of the Weighted-Average Dumping Margin and Assessment Rate in Certain Antidumping Proceedings: Final Modification,</E>77 FR 8101 (February 14, 2012).</P>

        <P>We calculated importer-specific rates based on the ratio of the total amount of dumping calculated for the examined sales for a given importer to the total entered value of such sales. If an importer-specific assessment rate is zero or<E T="03">de minimis</E>(<E T="03">i.e.,</E>less than 0.50 percent), the Department will instruct CBP to liquidate that importer's entries of subject merchandise without regard to antidumping duties, in accordance with 19 CFR 351.106(c)(2).</P>
        <P>The Department clarified its “automatic assessment” regulation on May 6, 2003.<SU>11</SU>
          <FTREF/>This clarification will apply to entries of subject merchandise during the POR produced by companies included in these amended final results of review for which the reviewed companies did not know their merchandise was destined for the United States. In such instances, we will instruct CBP to liquidate unreviewed entries at the country-specific, all-others rate established in the less-than-fair-value (“LTFV”) investigation if there is no rate for the intermediate company(ies) involved in the transaction.</P>
        <FTNT>
          <P>
            <SU>11</SU>
            <E T="03">See Antidumping and Countervailing Duty Proceedings: Assessment of Antidumping Duties,</E>68 FR 23954 (May 6, 2003).</P>
        </FTNT>
        <HD SOURCE="HD1">Cash Deposit Requirements</HD>
        <P>The following cash deposit requirements will be effective upon publication of this notice of amended final results of the administrative review for all shipments of subject merchandise entered or withdrawn from warehouse, for consumption, on or after the publication date, as provided by section 751(a)(2)(C) of the Act: (1) For Borusan, the cash deposit rate will be the rate listed above; (2) for all other companies, the cash deposit rate will be the respective rates established in the final results.<SU>12</SU>
          <FTREF/>These cash deposit requirements, when imposed, shall remain in effect until further notice.</P>
        <FTNT>
          <P>
            <SU>12</SU>
            <E T="03">See Final Results,</E>77 FR at 72820.</P>
        </FTNT>
        <HD SOURCE="HD1">Notification to Importers</HD>
        <P>This notice serves as a final reminder to importers of their responsibility under 19 CFR 351.402(f)(2) to file a certificate regarding the reimbursement of antidumping duties prior to liquidation of the relevant entries during this review period. Failure to comply with this requirement could result in the Secretary's presumption that reimbursement of antidumping duties occurred and the subsequent increase in antidumping duties by the amount of antidumping duties reimbursed.</P>
        <HD SOURCE="HD1">Notification to Interested Parties</HD>
        <P>This notice serves as the only reminder to parties subject to administrative protective order (“APO”) of their responsibility concerning the disposition of proprietary information disclosed under APO in accordance with 19 CFR 351.305(a)(3). Timely written notification of the return or destruction of APO materials or conversion to judicial protective order is hereby requested. Failure to comply with the regulations and the terms of an APO is a sanctionable violation.</P>
        <P>We are issuing and publishing these amended final results of administrative review and notice in accordance with sections 751(a)(1) and (h), and 777(i)(1) of the Act.</P>
        <SIG>
          <DATED>Dated: December 26, 2012.</DATED>
          <NAME>Lynn Fischer Fox,</NAME>
          <TITLE>Deputy Assistant Secretary for Policy and Negotiations.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31638 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>International Trade Administration</SUBAGY>
        <SUBJECT>Antidumping or Countervailing Duty Order, Finding, or Suspended Investigation; Advance Notification of Sunset Reviews</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Import Administration, International Trade Administration, Department of Commerce.</P>
        </AGY>
        <HD SOURCE="HD1">Background</HD>
        <P>Every five years, pursuant to section 751(c) of the Tariff Act of 1930, as amended (“the Act”), the Department of Commerce (“the Department”) and the International Trade Commission automatically initiate and conduct a review to determine whether revocation of a countervailing or antidumping duty order or termination of an investigation suspended under section 704 or 734 of the Act would be likely to lead to continuation or recurrence of dumping or a countervailable subsidy (as the case may be) and of material injury.</P>
        <HD SOURCE="HD1">Upcoming Sunset Reviews for February 2013</HD>
        <P>The following Sunset Reviews are scheduled for initiation in February 2013 and will appear in that month's Notice of Initiation of Five-Year Sunset Review.</P>
        <HD SOURCE="HD2">Antidumping Duty Proceedings</HD>
        <P>Sodium Hexametaphosphate from China (A-570-908) (1st Review)</P>
        <HD SOURCE="HD2">Department Contact</HD>
        <P>Jennifer Moats (202) 482-5047</P>
        <HD SOURCE="HD2">Countervailing Duty Proceedings</HD>
        <P>No Sunset Review of countervailing duty orders is scheduled for initiation in February 2013.</P>
        <HD SOURCE="HD2">Suspended Investigations</HD>
        <P>No Sunset Review of suspended investigations is scheduled for initiation in February 2013.</P>

        <P>The Department's procedures for the conduct of Sunset Reviews are set forth in 19 CFR 351.218. Guidance on methodological or analytical issues relevant to the Department's conduct of Sunset Reviews is set forth in the Department's Policy Bulletin 98.3—<E T="03">Policies Regarding the Conduct of Five-year (“Sunset”) Reviews of Antidumping and Countervailing Duty<PRTPAGE P="288"/>Orders;  Policy Bulletin,</E>63 FR 18871 (April 16, 1998). The Notice of Initiation of Five-Year (“Sunset”) Reviews provides further information regarding what is required of all parties to participate in Sunset Reviews.</P>
        <P>Pursuant to 19 CFR 351.103(c), the Department will maintain and make available a service list for these proceedings. To facilitate the timely preparation of the service list(s), it is requested that those seeking recognition as interested parties to a proceeding contact the Department in writing within 10 days of the publication of the Notice of Initiation.</P>
        <P>Please note that if the Department receives a Notice of Intent to Participate from a member of the domestic industry within 15 days of the date of initiation, the review will continue. Thereafter, any interested party wishing to participate in the Sunset Review must provide substantive comments in response to the notice of initiation no later than 30 days after the date of initiation.</P>
        <P>This notice is not required by statute but is published as a service to the international trading community.</P>
        <SIG>
          <DATED>Dated: December 5, 2012.</DATED>
          <NAME>Christian Marsh,</NAME>
          <TITLE>Deputy Assistant Secretary for Antidumping and Countervailing Duty Operations.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31543 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>International Trade Administration</SUBAGY>
        <SUBJECT>Antidumping or Countervailing Duty Order, Finding, or Suspended Investigation; Opportunity To Request Administrative Review</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Import Administration, International Trade Administration, Department of Commerce.</P>
        </AGY>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Brenda E. Waters, Office of AD/CVD Operations, Customs Unit, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue NW., Washington, DC 20230, telephone: (202) 482-4735.</P>
          <HD SOURCE="HD1">Background</HD>
          <P>Each year during the anniversary month of the publication of an antidumping or countervailing duty order, finding, or suspended investigation, an interested party, as defined in section 771(9) of the Tariff Act of 1930, as amended (“the Act”), may request, in accordance with 19 CFR 351.213, that the Department of Commerce (“the Department”) conduct an administrative review of that antidumping or countervailing duty order, finding, or suspended investigation.</P>
          <P>All deadlines for the submission of comments or actions by the Department discussed below refer to the number of calendar days from the applicable starting date.</P>
          <HD SOURCE="HD1">Respondent Selection</HD>

          <P>In the event the Department limits the number of respondents for individual examination for administrative reviews initiated pursuant to requests made for the orders identified below, except for the review of the antidumping duty order on Wooden Bedroom Furniture from the People's Republic of China (A-570-890), as discussed below, the Department intends to select respondents based on U.S. Customs and Border Protection (“CBP”) data for U.S. imports during the period of review. We intend to release the CBP data under Administrative Protective Order (“APO”) to all parties having an APO within five days of publication of the initiation notice and to make our decision regarding respondent selection within 21 days of publication of the initiation<E T="04">Federal Register</E>notice. Therefore, we encourage all parties interested in commenting on respondent selection to submit their APO applications on the date of publication of the initiation notice, or as soon thereafter as possible. The Department invites comments regarding the CBP data and respondent selection within five days of placement of the CBP data on the record of the review.</P>

          <P>If the Department limits the number of respondents selected for individual examination in the administrative review of the antidumping duty order on Wooden Bedroom Furniture from the People's Republic of China (A-570-890), it intends to select respondents based on volume data contained in responses to quantity and value questionnaires since the units used to measure import quantities are not consistent for the HTSUS headings identified in the scope of this case. In the past the Department has limited the number of quantity and value questionnaires issued in the Wooden Bedroom Furniture review based on CBP data. However, we have received comments concerning this practice and are considering the respondent selection process and information that must be submitted by all respondents. We ask that parties wishing to comment on this process or to the petitioner's December 3, 2012 submission do so by January 31, 2013. We will detail all requirements for respondents in the Wooden Bedroom Furniture review in the publication of the initiation<E T="04">Federal Register</E>notice.</P>
          <P>In the event the Department decides it is necessary to limit individual examination of respondents and conduct respondent selection under section 777A(c)(2) of the Act:</P>

          <P>In general, the Department has found that determinations concerning whether particular companies should be “collapsed” (<E T="03">i.e.,</E>treated as a single entity for purposes of calculating antidumping duty rates) require a substantial amount of detailed information and analysis, which often require follow-up questions and analysis. Accordingly, the Department will not conduct collapsing analyses at the respondent selection phase of this review and will not collapse companies at the respondent selection phase unless there has been a determination to collapse certain companies in a previous segment of this antidumping proceeding (<E T="03">i.e.,</E>investigation, administrative review, new shipper review or changed circumstances review). For any company subject to this review, if the Department determined, or continued to treat, that company as collapsed with others, the Department will assume that such companies continue to operate in the same manner and will collapse them for respondent selection purposes. Otherwise, the Department will not collapse companies for purposes of respondent selection. Parties are requested to (a) identify which companies subject to review previously were collapsed, and (b) provide a citation to the proceeding in which they were collapsed. Further, if companies are requested to complete the Quantity and Value Questionnaire for purposes of respondent selection, in general each company must report volume and value data separately for itself. Parties should not include data for any other party, even if they believe they should be treated as a single entity with that other party. If a company was collapsed with another company or companies in the most recently completed segment of this proceeding where the Department considered collapsing that entity, complete quantity and value data for that collapsed entity must be submitted.</P>
          <HD SOURCE="HD1">Deadline for Withdrawal of Request for Administrative Review</HD>

          <P>Pursuant to 19 CFR 351.213(d)(1), a party that has requested a review may withdraw that request within 90 days of the date of publication of the notice of initiation of the requested review. The regulation provides that the Department may extend this time if it is reasonable<PRTPAGE P="289"/>to do so. In order to provide parties additional certainty with respect to when the Department will exercise its discretion to extend this 90-day deadline, interested parties are advised that, with regard to reviews requested on the basis of anniversary months on or after January 2013, the Department does not intend to extend the 90-day deadline unless the requestor demonstrates that an extraordinary circumstance has prevented it from submitting a timely withdrawal request. Determinations by the Department to extend the 90-day deadline will be made on a case-by-case basis.</P>
          <P>The Department is providing this notice on its Web site, as well as in its “Opportunity to Request Administrative Review” notices, so that interested parties will be aware of the manner in which the Department intends to exercise its discretion in the future.</P>
          <P>Opportunity to Request a Review: Not later than the last day of January 2013,<SU>1</SU>
            <FTREF/>interested parties may request administrative review of the following orders, findings, or suspended investigations, with anniversary dates in January for the following periods:</P>
          <FTNT>
            <P>
              <SU>1</SU>Or the next business day, if the deadline falls on a weekend, federal holiday or any other day when the Department is closed.</P>
          </FTNT>
          <GPOTABLE CDEF="s200,15" COLS="2" OPTS="L2,tp0,i1">
            <TTITLE/>
            <BOXHD>
              <CHED H="1"/>
              <CHED H="1">Period of Review</CHED>
            </BOXHD>
            <ROW>
              <ENT I="21">
                <E T="02">Antidumping Duty Proceedings</E>
              </ENT>
            </ROW>
            
            <ROW>
              <ENT I="01">BRAZIL: Prestressed Concrete Steel Wire Strand A-351-837</ENT>
              <ENT>1/1/12-12/31/12</ENT>
            </ROW>
            <ROW>
              <ENT I="01">INDIA:Prestressed Concrete Steel Wire Strand A-533-828</ENT>
              <ENT>1/1/12-12/31/12</ENT>
            </ROW>
            <ROW>
              <ENT I="01">MEXICO:Prestressed Concrete Steel Wire Strand A-201-831</ENT>
              <ENT>1/1/12-12/31/12</ENT>
            </ROW>
            <ROW>
              <ENT I="01">REPUBLIC OF KOREA: Prestressed Concrete Steel Wire Strand A-580-852</ENT>
              <ENT>1/1/12-12/31/12</ENT>
            </ROW>
            <ROW>
              <ENT I="01">THAILAND: Prestressed Concrete Steel Wire Strand A-549-820</ENT>
              <ENT>1/1/12-12/31/12</ENT>
            </ROW>
            <ROW>
              <ENT I="01">SOUTH AFRICA: Ferrovanadium A-791-815</ENT>
              <ENT>1/1/12-12/31/12</ENT>
            </ROW>
            <ROW>
              <ENT I="01" O="xl">THE PEOPLE'S REPUBLIC OF CHINA:</ENT>
            </ROW>
            <ROW>
              <ENT I="03">Crepe Paper Products A-570-895</ENT>
              <ENT>1/1/12-12/31/12</ENT>
            </ROW>
            <ROW>
              <ENT I="03">Ferrovanadium A-570-873</ENT>
              <ENT>1/1/12-12/31/12</ENT>
            </ROW>
            <ROW>
              <ENT I="03">Folding Gift Boxes A-570-866</ENT>
              <ENT>1/1/12-12/31/12</ENT>
            </ROW>
            <ROW>
              <ENT I="03">Multilayered Wood Flooring<SU>2</SU>A-570-970</ENT>
              <ENT>5/26/11—11/30/12</ENT>
            </ROW>
            <ROW>
              <ENT I="03">Potassium Permanganate A-570-001</ENT>
              <ENT>1/1/12-12/31/12</ENT>
            </ROW>
            <ROW>
              <ENT I="03">Wooden Bedroom Furniture A-570-890</ENT>
              <ENT>1/1/12-12/31/12</ENT>
            </ROW>
            <ROW>
              <ENT I="21">
                <E T="02">Countervailing Duty Proceedings</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="01">ARGENTINA: Honey<SU>3</SU>C-357-813</ENT>
              <ENT>1/1/12-8/1/12</ENT>
            </ROW>
            <ROW>
              <ENT I="01" O="xl">THE PEOPLE'S REPUBLIC OF CHINA:</ENT>
            </ROW>
            <ROW>
              <ENT I="03">Certain Oil Country Tubular Goods C-570-944</ENT>
              <ENT>1/1/12-12/31/12</ENT>
            </ROW>
            <ROW>
              <ENT I="03">Circular Welded Carbon Quality Steel Line Pipe C-570-936</ENT>
              <ENT>1/1/12-12/31/12</ENT>
            </ROW>
            <ROW>
              <ENT I="21">
                <E T="02">Suspension Agreements</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="01">MEXICO:Fresh Tomatoes A-201-820</ENT>
              <ENT>1/1/12-12/31/12</ENT>
            </ROW>
            <ROW>
              <ENT I="01">RUSSIA:Certain Cut-To-Length Carbon Steel Plate A-821-808</ENT>
              <ENT>1/1/12-12/31/12</ENT>
            </ROW>
          </GPOTABLE>
          <P>In accordance with 19 CFR 351.213(b), an interested party as defined by section 771(9) of the Act may request in writing that the Secretary conduct an administrative review. For both antidumping and countervailing duty reviews, the interested party must specify the individual producers or exporters covered by an antidumping finding or an antidumping or countervailing duty order or suspension agreement for which it is requesting a review. In addition, a domestic interested party or an interested party described in section 771(9)(B) of the Act must state why it desires the Secretary to review those particular producers or exporters.<SU>4</SU>
            <FTREF/>If the interested party intends for the Secretary to review sales of merchandise by an exporter (or a producer if that producer also exports merchandise from other suppliers) which were produced in more than one country of origin and each country of origin is subject to a separate order, then the interested party must state specifically, on an order-by-order basis, which exporter(s) the request is intended to cover.</P>
          <FTNT>
            <P>
              <SU>2</SU>In the notice of opportunity to request administrative reviews that published on December 3, 2012 (77 FR 71579) the Department listed the period of review for case Multilayered Wood Flooring from PRC (A-570-970) incorrectly. The correct period of review for this case is listed above.</P>
            <P>
              <SU>3</SU>In the notice of opportunity to request administrative reviews that published on December 3, 2012 (77 FR 71579) the Department listed the period of review for case Honey from Argentina (C-357-813) incorrectly. The correct period of review for this case is listed above.</P>
            <P>
              <SU>4</SU>If the review request involves a non-market economy and the parties subject to the review request do not qualify for separate rates, all other exporters of subject merchandise from the non-market economy country who do not have a separate rate will be covered by the review as part of the single entity of which the named firms are a part.</P>
          </FTNT>
          <P>Please note that, for any party the Department was unable to locate in prior segments, the Department will not accept a request for an administrative review of that party absent new information as to the party's location. Moreover, if the interested party who files a request for review is unable to locate the producer or exporter for which it requested the review, the interested party must provide an explanation of the attempts it made to locate the producer or exporter at the same time it files its request for review, in order for the Secretary to determine if the interested party's attempts were reasonable, pursuant to 19 CFR 351.303(f)(3)(ii).</P>
          <P>As explained in<E T="03">Antidumping and Countervailing Duty Proceedings: Assessment of Antidumping Duties,</E>68 FR 23954 (May 6, 2003), the Department has clarified its practice with respect to the collection of final antidumping duties on imports of merchandise where intermediate firms are involved. The public should be aware of this clarification in determining whether to request an administrative review of merchandise subject to antidumping findings and orders.<E T="03">See also</E>the Import Administration Web site at<E T="03">http://ia.ita.doc.gov.</E>
          </P>

          <P>All requests must be filed electronically in Import Administration's Antidumping and Countervailing Duty Centralized Electronic Service System (“IA ACCESS”) on the IA ACCESS Web site at<E T="03">http://iaaccess.trade.gov. See Antidumping and Countervailing Duty Proceedings: Electronic Filing Procedures; Administrative Protective Order Procedures,</E>76 FR 39263 (July 6, 2011). Further, in accordance with 19 CFR 351.303(f)(l)(i), a copy of each request must be served on the petitioner<PRTPAGE P="290"/>and each exporter or producer specified in the request.</P>
          <P>The Department will publish in the<E T="04">Federal Register</E>a notice of “Initiation of Administrative Review of Antidumping or Countervailing Duty Order, Finding, or Suspended Investigation” for requests received by the last day of January 2013. If the Department does not receive, by the last day of January 2013, a request for review of entries covered by an order, finding, or suspended investigation listed in this notice and for the period identified above, the Department will instruct CBP to assess antidumping or countervailing duties on those entries at a rate equal to the cash deposit of (or bond for) estimated antidumping or countervailing duties required on those entries at the time of entry, or withdrawal from warehouse, for consumption and to continue to collect the cash deposit previously ordered.</P>
          <P>For the first administrative review of any order, there will be no assessment of antidumping or countervailing duties on entries of subject merchandise entered, or withdrawn from warehouse, for consumption during the relevant provisional-measures “gap” period, of the order, if such a gap period is applicable to the period of review.</P>
          <P>This notice is not required by statute but is published as a service to the international trading community.</P>
          <SIG>
            <DATED>Dated: December 21, 2012.</DATED>
            <NAME>Christian Marsh,</NAME>
            <TITLE>Deputy Assistant Secretary for Antidumping and Countervailing Duty Operations.</TITLE>
          </SIG>
        </FURINF>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31544 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Institute of Standards and Technology</SUBAGY>
        <SUBJECT>National Conference on Weights and Measures 98th Interim Meeting</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>National Institute of Standards and Technology, Commerce.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The 2013 Interim Meeting of the National Conference on Weights and Measures (NCWM) will be held January 27 to 30, 2013. This notice contains information about significant items on the NCWM Committee agendas, but does not include all agenda items. As a result, the items are not consecutively numbered.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The meeting will be held January 27 to 30, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The meeting will be held at the Francis Marion Hotel located at 387 King Street, Charleston, South Carolina 29403.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Ms. Carol Hockert, Chief, NIST, Office of Weights and Measures, 100 Bureau Drive, Stop 2600, Gaithersburg, MD 20899-2600. You may also contact Ms. Hockert at (301) 975-5507 or by email at<E T="03">carol.hockert@nist.gov.</E>The meetings are open to the public, but a paid registration is required. Please see NCWM Publication 15 “Interim Meeting Agenda” (<E T="03">www.ncwm.net</E>) to view the meeting agendas, registration forms and hotel reservation information.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Publication of this notice on the NCWM's behalf is undertaken as a public service; NIST does not endorse, approve, or recommend any of the proposals or other information contained in this notice or in the publications of the NCWM.</P>
        <P>The NCWM is an organization of weights and measures officials of the states, counties, and cities of the United States, federal agencies, and representatives from the private sector. These meetings bring together government officials and representatives of business, industry, trade associations, and consumer organizations on subjects related to the field of weights and measures technology, administration and enforcement. NIST participates to encourage cooperation between federal agencies and the states in the development of legal metrology requirements. NIST also promotes uniformity among the states in laws, regulations, methods, and testing equipment that comprise the regulatory control of commercial weighing and measuring devices, packaged goods, and other trade and commerce issues.</P>
        <P>The following are brief descriptions of some of the significant agenda items that will be considered along with other issues at the NCWM Interim Meeting. Comments will be taken on these and other issues during several public comment sessions. At this stage, the items are proposals. This meeting also includes work sessions in which the Committees may also accept comments, and where they will finalize recommendations for NCWM consideration and possible adoption at its 2013 Annual Meeting that will be held at the Seelbach Hilton Hotel located at 500 South Fourth Street in Lexington, Kentucky, on July 14-18, 2013. The Committees may withdraw or carryover items that need additional development.</P>
        <P>Some of the items listed below provide notice of projects under development by groups working to develop specifications, tolerances, and other requirements for devices used in retail sales of electricity for recharging vehicles and in sub-metering applications and the use of Global Positioning System (GPS) devices for fare determinations in the vehicle-for-hire industry (e.g., taxis and limousines). Also included are notices about efforts to establish methods of sale for pressurized containers and to develop test procedures for verifying the net contents of printer ink and toner cartridges. These notices are intended to make interested parties aware of these development projects and to make them aware that reports on the status of the project will be given at the Interim Meeting. The notices are also presented to invite the participation of manufacturers, experts, consumers, users and others who may be interested in these efforts.</P>
        <P>The Specifications and Tolerances Committee (S&amp;T Committee) will consider proposed amendments to NIST Handbook 44, “Specifications, Tolerances, and other Technical Requirements for Weighing and Measuring Devices.” Those items address weighing and measuring devices used in commercial applications, that is, devices that are used to buy from or sell to the public or used for determining the quantity of product sold among businesses. Issues on the agenda of the NCWM Laws and Regulations Committee (L&amp;R Committee) relate to proposals to amend NIST Handbook 130, “Uniform Laws and Regulations in the area of Legal Metrology and Engine Fuel Quality” and NIST Handbook 133, “Checking the Net Contents of Packaged Goods.”</P>
        <HD SOURCE="HD3">NCWM Specifications and Tolerances Committee</HD>
        <P>The following items are proposals to amend NIST Handbook 44:</P>
        <HD SOURCE="HD3">Scales</HD>
        <HD SOURCE="HD3">Item 320-1: S.6.4. Railway Track Scales and Appendix D—Definitions</HD>

        <P>Railway track scales are used throughout the country for the determination of freight charges and for commercial transactions for a wide variety of commodities (e.g., coal, grains and chemicals) totaling billions of dollars each year. The intent of this proposal is to amend NIST Handbook 44 to recognize changes to the definition of how nominal capacity is determined for railway track scales. The new definition was recently developed by Committee 34—Scales, of the American Railway Engineering and Maintenance-of-Way Association and approved for inclusion<PRTPAGE P="291"/>in the American Association of Railroads (AAR) Scale Handbook. Adoption of the proposed revision will ensure that NIST Handbook 44 is consistent with the AAR Scale Handbook, thus, ensuring uniformity in state laws and regulations, which apply to railway scales, that are used extensively in interstate commerce.</P>
        <HD SOURCE="HD3">Vehicle Tank Meters</HD>
        <HD SOURCE="HD3">Item 331-2: T.4. Product Depletion Test</HD>
        <P>The vehicle tank meters mounted on multi-compartment tank trucks are used to deliver a wide variety of fuels and other products to businesses and consumers alike (e.g., diesel fuel, home heating fuel). A product depletion test is conducted to ensure that the performance accuracy of a meter remains within tolerance when one compartment in the tank truck empties of product and the delivery is continued from another compartment. This proposal would amend NIST Handbook 44 to base the product depletion test tolerances on the meter's maximum flow rate (a marking required on all meters), rather than the marked meter size (this marking is required for meters manufactured in 2009 or later). The intent of this proposal is to ensure consistent application of the tolerances to product depletion tests conducted on older and newer meters. It will also eliminate an unintentional gap that allows an unreasonably large tolerance to be applied to small meters.</P>
        <HD SOURCE="HD3">Mass Flow Meters</HD>
        <HD SOURCE="HD3">Item 337-1: Appendix D—Definitions: Diesel Liter and Diesel Gallon Equivalents of Natural Gas</HD>
        <P>In 1994 both liter and gallon equivalents for gasoline (based on an “average” equivalent energy content developed by the industry) were established by the NCWM based on the industry's request to provide a means for consumers to make value and fuel economy comparisons between compressed natural gas (CNG) and a liter or gallon of gasoline in order to promote broader acceptance and use of CNG as a vehicle fuel. This proposal would establish a “diesel liter equivalent (DLE)” and a “diesel gallon equivalent (DGE)” and equivalent mass values for these units when they are used in retail vehicle refueling applications. The use of these units is to inform consumers that a DLE or DGE of “compressed” or “liquefied” natural gas contains approximately the same amount of energy they would receive if they purchased a liter or gallon of diesel fuel. The submitter of this proposal believes that adoption and use of the DLE or DGE in retail fuel sales would make it easier for consumers to make price, value, and fuel economy comparisons between an equivalent liter or gallon of compressed natural gas and diesel fuel. See also Item 337-2: S.1.2. Compressed Natural Gas Dispensers, S.1.3.1.1., Compressed Natural Gas Used as an Engine Fuel, and S.5.2. Marking of Gasoline Volume Equivalent Conversion Factor, and Item 232-1: Section 2.27. Retail Sales of Natural Gas Sold as a Vehicle Fuel in the Laws and Regulations Committee Agenda.</P>
        <HD SOURCE="HD3">Use of GPS Systems for Fare Determinations—Developing Item</HD>
        <HD SOURCE="HD3">Item 360-6: Global Positioning Systems for Fare Determinations in the Vehicle for Hire Industry</HD>
        <P>This item is presented to raise awareness of work that is underway to amend Section 5.54. “Taximeters” to incorporate specifications, tolerances, user and other technical requirements for devices that incorporate Global Positioning Satellite (GPS) systems, and associated software commercially to compute fares or fees based upon distance and/or time measurements. GPS systems and applications designed to compute fares based upon distance and/or time measurements are being introduced into the vehicle for-hire industry (e.g., taxicabs, limousines) across the country. Appropriate technical and device accuracy requirements must be developed for manufacturers and users of these devices, and for weights and measures officials so that consumers can be assured of accurate fares associated with the transportation service provided and to enable consumers to make value comparisons between competing services.</P>
        <HD SOURCE="HD3">NCWM Laws and Regulations Committee (L &amp; R Committee)</HD>
        <P>The following items are proposals to amend NIST Handbook 130 or NIST Handbook 133:</P>
        <HD SOURCE="HD3">NIST Handbook 130—Uniform Regulation for the Method of Sale of Commodities</HD>
        <HD SOURCE="HD3">Item 231-2: Section 10.3. Aerosols and Similar Pressurized Containers</HD>
        <P>This proposal is intended to provide an appropriate method of sale (i.e., the product must be offered for sale by either weight or fluid volume but not both) for packages utilizing the Bag on Valve (BOV) technology. BOV means a pressurized package where a propellant is not expelled with the product when the valve is activated. BOV packaging has been in the marketplace for many years and is used to sell the same products sold in aerosol containers (e.g., sunscreen, wound wash, shaving cream, and car products). Some BOV packages have their net contents declared in terms of fluid volume. Section 10.3. currently requires aerosols and similar pressurized containers to disclose their net quantity in terms of weight. Because BOV containers (net contents in fluid volume) are being used to sell the same type of products dispensed from aerosol containers (net contents in weight), consumers are unable to make value comparisons.</P>
        <HD SOURCE="HD3">Item 232-6: Packaged Printer Ink and Toner Cartridges</HD>
        <P>This proposal was originally intended to establish a method of sale for inkjet and toner cartridges to ensure that consumers are informed about the net quantity of contents of packages and so they can make value comparisons. The original proposals would have required manufacturers (and aftermarket refillers) to declare net quantities to facilitate both value comparison by consumers and verification by weights and measures officials, and to ensure equity between buyer and seller and fair competition between sellers, manufacturers and refillers. At the 2012 NCWM Annual Meeting a newly formed Printer Ink and Toner Cartridge Gravimetric Package Testing Task Group (Task Group) met to consider test methods that could be used to verify the net contents of packages. The Task Group will report on its progress at the meeting. See also Item 260-3 Gravimetric Testing of Printer Ink and Toner Cartridges for more information.</P>
        <HD SOURCE="HD3">Retail Sale of Electricity for Vehicle Recharging—Developing Item</HD>
        <HD SOURCE="HD3">Item 270-2: Uniform Method of Sale Regulation, Section 2.XX. Retail Sale of Electricity/Vehicle</HD>

        <P>A workgroup on retail sales of electricity for vehicle recharging has been formed to engage manufacturers, users and others involved in vehicle recharging and the weights and measures community in helping to develop a proposed method of sale for electricity sold at the retail level to recharge vehicles. Any stakeholder, including vehicle and device manufacturers, consumers, public utility commissions, weights and measures officials, smart grid experts, and all others interested in the development of a method of sale for electricity and other requirements for devices use to sell electricity to recharge vehicles are invited to participate in this effort. In addition to method of sale<PRTPAGE P="292"/>requirements, the workgroup will consider proposals for specifications, tolerances, and user requirements for measuring devices, and possible requirements for device security and information posting requirements (e.g., information on service fees, charging rates and how to contact the party responsible for the device). A work group report will be presented at the meeting.</P>
        <HD SOURCE="HD3">Uniform Engine Fuels and Automotive Lubricants Regulation</HD>
        <HD SOURCE="HD3">Item 237-2: Section 2.1.4. Minimum Antiknock Index (AKI), Section 2.1.5. Minimum Motor Octane Number and Table 1. Minimum Antiknock Index Requirements</HD>
        <P>This is a proposal to discontinue the obsolete practice of altitude de-rating of octane, to establish a national octane baseline, and to establish uniform octane labeling requirements. The proposal will amend the Engine Fuels and Automotive Lubricants Regulation to bring it into agreement with efforts underway in the ASTM Gasoline and Oxygenates Subcommittee to include a minimum motor octane number (MON) performance limit in its specifications for gasoline. Vehicles manufactured after 1984 include engine computer controls that maintain optimal performance when they use gasoline with an octane of 87 AKI or higher. The current practice of altitude de-rating of octane, results in octanes below 87 AKI which reduces a vehicle's efficiency and fuel economy. Increasingly, more vehicles are boosted (turbocharged/supercharged) eliminating the intake air effects caused by altitude. Additionally, consumers using gasoline with an octane AKI below 87 may void their vehicle warranty.</P>
        <SIG>
          <DATED>Dated: December 28, 2012.</DATED>
          <NAME>Willie E. May,</NAME>
          <TITLE>Associate Director for Laboratory Programs.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31596 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-13-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Institute of Standards and Technology</SUBAGY>
        <SUBJECT>Visiting Committee on Advanced Technology</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>National Institute of Standards and Technology, Department of Commerce.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of Public Meeting.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Visiting Committee on Advanced Technology (VCAT or Committee), National Institute of Standards and Technology (NIST), will meet in open session on Wednesday, February 6, 2013, from 11:00 a.m. to 5:00 p.m. Eastern Time and Thursday, February 7, 2013, from 8:30 a.m. to 11:15 a.m. Eastern Time. The VCAT is composed of fifteen members appointed by the Under Secretary of Commerce for Standards and Technology who are eminent in such fields as business, research, new product development, engineering, labor, education, management consulting, environment, and international relations.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The VCAT will meet on Wednesday, February 6, 2013, from 11:00 a.m. to 5:00 p.m. Eastern Time and Thursday, February 7, 2013, from 8:30 a.m. to 11:15 a.m. Eastern Time.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>The meeting will be held in the Portrait Room, Administration Building, at NIST, 100 Bureau Drive, Gaithersburg, Maryland, 20899. Please note admittance instructions under the<E T="02">SUPPLEMENTARY INFORMATION</E>section of this notice.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Stephanie Shaw, VCAT, NIST, 100 Bureau Drive, Mail Stop 1060, Gaithersburg, Maryland 20899-1060, telephone number 301-975-2667. Ms. Shaw's email address is<E T="03">stephanie.shaw@nist.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>15 U.S.C. 278 and the Federal Advisory Committee Act, as amended, 5 U.S.C. App.</P>
        </AUTH>
        

        <P>The purpose of this meeting is for the VCAT to review and make recommendations regarding general policy for NIST, its organization, its budget, and its programs within the framework of applicable national policies as set forth by the President and the Congress. The agenda will include an update on NIST followed by presentations and discussions on the Administration's priorities for 2013 in science and technology and in manufacturing, NIST's safety metrics, and NIST's activities related to the Manufacturing Extension Partnership and the Baldrige Performance Excellence Program. The VCAT Subcommittee on Safety will review its recommendations for deliberation by the Committee. The meeting will also include presentations and discussions on the VCAT agenda for 2013 and initial observations, findings, and recommendations for the 2012 VCAT Annual Report. The agenda may change to accommodate Committee business. The final agenda will be posted on the NIST Web site at<E T="03">http://www.nist.gov/director/vcat/agenda.cfm.</E>
        </P>

        <P>Individuals and representatives of organizations who would like to offer comments and suggestions related to the Committee's affairs are invited to request a place on the agenda. On February 7, approximately one-half hour will be reserved in the morning for public comments and speaking times will be assigned on a first-come, first-serve basis. The amount of time per speaker will be determined by the number of requests received, but is likely to be about 3 minutes each. The exact time for public comments will be included in the final agenda that will be posted on the NIST Web site at<E T="03">http://www.nist.gov/director/vcat/agenda.cfm.</E>Questions from the public will not be considered during this period. Speakers who wish to expand upon their oral statements, those who had wished to speak, but could not be accommodated on the agenda, and those who were unable to attend in person are invited to submit written statements to VCAT, NIST, 100 Bureau Drive, MS 1060, Gaithersburg, Maryland, 20899, via fax at 301-216-0529 or electronically by email to<E T="03">gail.ehrlich@nist.gov.</E>
        </P>

        <P>All visitors to the NIST site are required to pre-register to be admitted. Please submit your name, time of arrival, email address and phone number to Stephanie Shaw by 5:00 p.m. Eastern Time, Thursday, January 31, 2013. Non-U.S. citizens must also submit their country of citizenship, title, employer/sponsor, and address. Ms. Shaw's email address is<E T="03">stephanie.shaw@nist.gov</E>and her phone number is 301-975-2667.</P>
        <SIG>
          <DATED>Dated: December 28, 2012.</DATED>
          <NAME>Willie E. May,</NAME>
          <TITLE>Associate Director for Laboratory Programs.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31597 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-13-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>United States Patent and Trademark Office</SUBAGY>
        <DEPDOC>[Docket No. PTO-P-2012-0052]</DEPDOC>
        <SUBJECT>Request for Comments and Notice of Roundtable Events for Partnership for Enhancement of Quality of Software-Related Patents</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>United States Patent and Trademark Office, Commerce.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Request for comments. Notice of meetings.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The United States Patent and Trademark Office (USPTO) seeks to form a partnership with the software community to enhance the quality of<PRTPAGE P="293"/>software-related patents (Software Partnership). Members of the public are invited to participate. The Software Partnership will be an opportunity to bring stakeholders together through a series of roundtable discussions to share ideas, feedback, experiences, and insights on software-related patents. To commence the Software Partnership and to provide increased opportunities for all to participate, the USPTO is sponsoring two roundtable events with identical agendas, one in Silicon Valley, and the other in New York City. Each roundtable event will provide a forum for an informal and interactive discussion of topics relating to patents that are particularly relevant to the software community. While public attendees will have the opportunity to provide their individual input, group consensus advice will not be sought.</P>
          <P>For these initial roundtable events, this notice sets forth several topics to begin the Software Partnership discussion. The first topic relates to how to improve clarity of claim boundaries that define the scope of patent protection for claims that use functional language. The second topic requests that the public identify additional topics for future discussion by the Software Partnership. The third topic relates to a forthcoming Request for Comments on Preparation of Patent Applications and offers an opportunity for oral presentations on the Request for Comments at the Silicon Valley and New York City roundtable events. Written comments are requested in response to the first two discussion topics. Written comments on the third discussion topic must be submitted as directed in the forthcoming Request for Comments on Preparation of Patent Applications.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Events:</E>The Silicon Valley event will be held on Tuesday, February 12, 2013, beginning at 9 a.m. Pacific Standard Time (PST) and ending at 12 p.m. PST. The New York City event will be held on Wednesday, February 27, 2013, beginning at 9 a.m. Eastern Standard Time (e.s.t.) and ending at 12 p.m. e.s.t.</P>
          <P>
            <E T="03">Comments:</E>To be ensured of consideration, written comments must be received on or before March 15, 2013. No public hearing will be held.</P>
          <P>
            <E T="03">Registration:</E>Registration for both roundtable events is requested by February 4, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>
            <E T="03">Events:</E>The Silicon Valley event will be held at: Stanford University, Paul Brest Hall, 555 Salvatierra Walk, Stanford, CA 94305-2087.</P>
          <P>The New York City event will be held at: New York University, Henry Kaufman Management Center, Faculty Lounge, Room 11-185, 44 West 4th St., New York, NY 10012.</P>
          <P>
            <E T="03">Comments:</E>Written comments should be sent by electronic mail addressed to<E T="03">SoftwareRoundtable2013@uspto.gov.</E>Comments may also be submitted by mail addressed to: Mail Stop Comments—Patents, Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313-1450, marked to the attention of Seema Rao, Director Technology Center 2100. Although comments may be submitted by mail, the USPTO prefers to receive comments via the Internet.</P>

          <P>The comments will be available for public inspection at the Office of the Commissioner for Patents, located in Madison East, Tenth Floor, 600 Dulany Street, Alexandria, Virginia, and will be available via the USPTO Internet Web site at<E T="03">http://www.uspto.gov.</E>Because comments will be available for public inspection, information that is not desired to be made public, such as an address or phone number, should not be included in the comments. Parties who would like to rely on confidential information to illustrate a point are requested to summarize or otherwise submit the information in a way that will permit its public disclosure.</P>
          <P>
            <E T="03">Registration:</E>Two separate roundtable events will occur, with the first in Silicon Valley and the second event in New York City. Registration is required, and early registration is recommended because seating is limited. There is no fee to register for the roundtable events, and registration will be on a first-come, first-served basis. Registration on the day of the event will be permitted on a space-available basis beginning 30 minutes before the event.</P>
          <P>To register, please send an email message to<E T="03">SoftwareRoundtable2013@uspto.gov</E>and provide the following information: (1) Your name, title, and if applicable, company or organization, address, phone number, and email address; (2) which roundtable event you wish to attend (Silicon Valley or New York City); and (3) if you wish to make an oral presentation at the event, the specific topic or issue to be addressed and the approximate desired length of your presentation. Each attendee, even if from the same organization, must register separately.</P>

          <P>The USPTO will attempt to accommodate all persons who wish to make a presentation at the roundtable events. After reviewing the list of speakers, the USPTO will contact each speaker prior to the event with the amount of time available and the approximate time that the speaker's presentation is scheduled to begin. Speakers must then send the final electronic copies of their presentations in Microsoft PowerPoint or Microsoft Word to<E T="03">SoftwareRoundtable2013@uspto.gov</E>by February 1, 2013, so that the presentation can be displayed at the events.</P>

          <P>The USPTO plans to make the roundtable events available via Web cast. Web cast information will be available on the USPTO's Internet Web site before the events. The written comments and list of the event participants and their affiliations will be posted on the USPTO's Internet Web site at<E T="03">www.uspto.gov.</E>
          </P>
          <P>If you need special accommodations due to a disability, please inform the contact persons identified below.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Seema Rao, Director Technology Center 2100, by telephone at 571-272-3174, or by electronic mail message at<E T="03">seema.rao@uspto.gov</E>or Matthew J. Sked, Legal Advisor, by telephone at (571) 272-7627, or by electronic mail message at<E T="03">matthew.sked@uspto.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <P SOURCE="NPAR">I.<E T="03">Purpose of Notice:</E>This notice is directed to announcing the Software Partnership which is a cooperative effort between the USPTO and the software community to explore ways to enhance the quality of software-related patents. The Software Partnership will commence with the two bi-coastal roundtable events. The initial topics selected for comment and discussion have been chosen based on input the USPTO has received regarding software-related patents. The input has been gleaned from public commentary on patent quality, dialogue with stakeholders that have requested that the USPTO take a closer look at the quality of software-related patents, and from insight based on court cases in which software-related patents have been the subject of litigation. The public is invited to provide comments on these initial topics and to identify future topics for discussion.</P>
        <P>II.<E T="03">Background on Initiative to Enhance Quality of Software-Related Patents:</E>The USPTO is continuously seeking ways to improve the quality of patents. A quality patent is defined, for purposes of this notice, as a patent: (a) For which the record is clear that the application has received a thorough and complete examination, addressing all issues on the record, all examination having been done in a manner lending confidence to the public and patent owner that the resulting patent is most<PRTPAGE P="294"/>likely valid; (b) for which the protection granted is of proper scope; and (c) which provides sufficiently clear notice to the public as to what is protected by the claims.</P>
        <P>Software-related patents pose unique challenges from both an examination and an enforcement perspective. One of the most significant issues with software inventions is identifying the scope of coverage of the patent claims, which define the boundaries of the patent property right. Software by its nature is operation-based and is typically embodied in the form of rules, operations, algorithms or the like. Unlike hardware inventions, the elements of software are often defined using functional language. While it is permissible to use functional language in patent claims, the boundaries of the functional claim element must be discernible. Without clear boundaries, patent examiners cannot effectively ensure that the claims define over the prior art, and the public is not adequately notified of the scope of the patent rights. Compliance with 35 U.S.C. 112(b) (second paragraph prior to enactment of the Leahy-Smith America Invents Act (AIA)) ensures that a claim is definite.</P>
        <P>There are several ways to draft a claim effectively using functional language and comply with section 112(b). One way is to modify the functional language with structure that can perform the recited function. Another way is to invoke 35 U.S.C. 112(f) (sixth paragraph pre-AIA) and employ so-called “means-plus-function” language. Under section 112(f), an element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material or acts in support thereof, and shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof. As is often the case with software-related claims, an issue can arise as to whether sufficient structure is present in the claim or in the specification, when section 112(f) is invoked, in order to satisfy the requirements of section 112(b) requiring clearly defined claim boundaries. Defining the structure can be critical to setting clear claim boundaries.</P>
        <P>III.<E T="03">Topics for Public Comment and Discussion at the Roundtable Events:</E>The USPTO is seeking input on the following topics relating to enhancing the quality of software-related patents. These initial topics are intended to be the first of many topics to be explored in a series of roundtables that may ultimately be used for USPTO quality initiatives, public education or examiner training. First, written and oral comments are sought on input regarding improving the clarity of claim boundaries for software-related claims that use functional language by focusing on 35 U.S.C. 112 (b) and (f) during prosecution of patent applications. Second, written and oral comments are sought on future topics for the Software Partnership to address. Third, oral comments are sought on the forthcoming Request for Comments on Preparation of Patent Applications to the extent that the topics of that notice particularly pertain to software-related patents.</P>
        <P>
          <E T="03">The initial topics for which the USPTO is requesting written and, if desired, oral comments are as follows:</E>
        </P>
        <HD SOURCE="HD1">Topic 1: Establishing Clear Boundaries for Claims That Use Functional Language</HD>
        <P>The USPTO seeks comments on how to more effectively ensure that the boundaries of a claim are clear so that the public can understand what subject matter is protected by the patent claim and the patent examiner can identify and apply the most pertinent prior art. Specifically, comments are sought on the following questions. It is requested that, where possible, specific claim examples and supporting disclosure be provided to illustrate the points made.</P>
        <P>1. When means-plus-function style claiming under 35 U.S.C. 112(f) is used in software-related claims, indefinite claims can be divided into two distinct groups: claims where the specification discloses no corresponding structure; and claims where the specification discloses structure but that structure is inadequate. In order to specify adequate structure and comply with 35 U.S.C. 112(b), an algorithm must be expressed in sufficient detail to provide means to accomplish the claimed function. In general, are the requirements of 35 U.S.C. 112(b) for providing corresponding structure to perform the claimed function typically being complied with by applicants and are such requirements being applied properly during examination? In particular:</P>
        <P>(a) Do supporting disclosures adequately define any structure corresponding to the claimed function?</P>
        <P>(b) If some structure is provided, what should constitute sufficient `structural' support?</P>
        <P>(c) What level of detail of algorithm should be required to meet the sufficient structure requirement?</P>
        <P>2. In software-related claims that do not invoke 35 U.S.C. 112(f) but do recite functional language, what would constitute sufficient definiteness under 35 U.S.C. 112(b) in order for the claim boundaries to be clear? In particular:</P>
        <P>(a) Is it necessary for the claim element to also recite structure sufficiently specific for performing the function?</P>
        <P>(b) If not, what structural disclosure is necessary in the specification to clearly link that structure to the recited function and to ensure that the bounds of the invention are sufficiently demarcated?</P>
        <P>3. Should claims that recite a computer for performing certain functions or configured to perform certain functions be treated as invoking 35 U.S.C. 112(f) although the elements are not set forth in conventional means-plus-function format?</P>
        <HD SOURCE="HD1">Topic 2: Future Discussion Topics for the Software Partnership</HD>
        <P>The USPTO is seeking public input on topics related to enhancing the quality of software-related patents to be discussed at future Software Partnership events. The topics will be used in an effort to extend and expand the dialogue between the public and the USPTO regarding enhancing quality of software-related patents. The Software Partnership is intended to provide on-going, interactive opportunities and a forum for engagement with the USPTO and the public on software-related patents. Therefore, to plan future events, the USPTO seeks input on which topics, and in what order of priority, are of most interest to the public. Input gathered from these events, may be used as the basis for internal training efforts and quality initiatives. One potential topic for future discussion is how determinations of obviousness or non-obviousness of software inventions can be improved. Another potential topic is how to provide the best prior art resources for examiners beyond the body of U.S. Patents and U.S. Patent Publications. Additional topics are welcomed.</P>
        
        <FP SOURCE="FP-1">
          <E T="03">Another topic for which the USPTO is requesting oral comment at the roundtable events is as follows:</E>
        </FP>
        <HD SOURCE="HD1">Topic 3: Oral Presentations on Preparation of Patent Applications</HD>

        <P>In the near future, the USPTO will issue a Request for Comments on Preparation of Patent Applications. The purpose of this forthcoming Request for Comments is to seek public input on whether certain practices could or should be used during the preparation of an application to place the application in the best possible condition for examination and whether the use of these practices would assist<PRTPAGE P="295"/>the public in determining the scope of the claims as well as the meaning of the claim terms in the specification. To ensure proper consideration, written comments to the forthcoming Request for Comments should only be submitted in response to that notice to<E T="03">QualityApplications_Comments@uspto.gov</E>. However, registrants may make oral presentations at the Silicon Valley and New York City roundtable events on the topics related to the forthcoming Request for Comments to the extent that the topics pertain to software-related inventions. Note particularly two questions from the forthcoming Request for Comments, which are previewed below. Oral comments are requested on the advantages and disadvantages of applicants employing the following practices when preparing patent applications as they relate to software claims.</P>
        <P>• Expressly identifying clauses within particular claim limitations for which the inventor intends to invoke 35 U.S.C. 112(f) and pointing out where in the specification corresponding structures, materials, or acts are disclosed that are linked to the identified 35 U.S.C. 112(f) claim limitations; and</P>
        <P>• Using textual and graphical notation systems known in the art to disclose algorithms in support of computer-implemented claim limitations, such as C-like pseudo-code or XML-like schemas for textual notation and Unified Modeling Language (UML) for graphical notation.</P>
        <SIG>
          <DATED>Dated: December 27, 2012.</DATED>
          <NAME>David J. Kappos,</NAME>
          <TITLE>Under Secretary of Commerce for Intellectual Property and Director of the United States Patent and Trademark Office.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31594 Filed 1-2-13; 12:09 pm]</FRDOC>
      <BILCOD>BILLING CODE 3510-16-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <SUBJECT>Federal Advisory Committee; Defense Intelligence Agency (DIA) Advisory Board; Closed Meeting</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>DIA, Department of Defense (DoD).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Meeting notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Under the provisions of the Federal Advisory Committee Act of 1972 (5 U.S.C. Appendix 2 (2001)), the Government in the Sunshine Act of 1976 (5 U.S.C. 552b), and 41 CFR 102-3.10, DoD hereby announces that the DIA Advisory Board will meet on January 22, 2013. The meeting is closed to the public. The meeting necessarily includes discussions of classified information relating to DIA's intelligence operations including its support to current operations.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The meeting will be held on January 22, 2013, from 9:00 a.m. to 4:00 p.m.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The meeting will be held at Joint-Base Bolling-Anacostia, Washington, DC.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ms. Ellen M. Ardrey, (202) 231-0800, Designated Federal Officer, DIA Office for Congressional and Public Affairs, Pentagon 1A874, Washington, DC 20340-5100.</P>
          <P>
            <E T="03">Committee's Designated Federal Officer:</E>Ms. Ellen M. Ardrey, (202) 231-0800, DIA Office for Congressional and Public Affairs, Pentagon 1A874, Washington, DC 20340-5100.<E T="03">Ellen.ardrey@dodiis.mil.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Purpose of the Meeting</HD>
        <P>For the Advisory Board to discuss DIA operations and capabilities in support of current intelligence operations.</P>
        <HD SOURCE="HD1">Agenda</HD>
        <P>
          <E T="03">January 22, 2013:</E>
        </P>
        <GPOTABLE CDEF="s100,r100,xs188" COLS="3" OPTS="L2,tp0,p1,8/9,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1"/>
            <CHED H="1"/>
            <CHED H="1"/>
            <CHED H="1">9:00 a.m.</CHED>
            <CHED H="1">Call to Order</CHED>
            <CHED H="1">Ms. Ellen M. Ardrey, Designated Federal Officer,<LI>Mrs. Mary Margaret Graham, Chairman.</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">9:00 a.m.</ENT>
            <ENT>Call to Order</ENT>
            <ENT>Ms. Ellen M. Ardrey, Designated Federal Officer,<LI>Mrs. Mary Margaret Graham, Chaiman.</LI>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="01">9:00 a.m.</ENT>
            <ENT>Administrative Business</ENT>
          </ROW>
          <ROW>
            <ENT I="01">10:00 a.m.</ENT>
            <ENT>Classified Discussion with Director, DIA</ENT>
            <ENT>LTG Michael T. Flynn, USA, Director, DIA.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">11:30 a.m.</ENT>
            <ENT>Working Lunch</ENT>
          </ROW>
          <ROW>
            <ENT I="01">12:45 p.m.</ENT>
            <ENT>Classified Briefing</ENT>
            <ENT>DIA Staff.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">1:30 p.m.</ENT>
            <ENT>Advisory Board Work Session</ENT>
          </ROW>
          <ROW>
            <ENT I="01">3:30 p.m.</ENT>
            <ENT>Classified Discussion with Director, DIA</ENT>
            <ENT>LTG Michael T. Flynn, USA, Director, DIA.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">4:00 p.m.</ENT>
            <ENT>Wrap-up/Adjourn</ENT>
          </ROW>
        </GPOTABLE>
        <P>Pursuant to 5 U.S.C. 552b, as amended, and 41 CFR 102-3.155, the Director, DIA, has determined that the meeting shall be closed to the public. The Director, DIA, in consultation with the DIA Office of the General Counsel, has determined in writing that the public interest requires that all sessions of the Board's meetings be closed to the public because they include discussions of classified information and matters covered by 5 U.S.C. 552b(c)(1).</P>
        <HD SOURCE="HD1">Written Statements</HD>

        <P>Pursuant to 41 CFR 102-3.105(j) and 102-3.140, and section 10(a)(3) of the Federal Advisory Board Committee Act of 1972, the public or interested organizations may submit written statements at any time to the DIA Advisory Board regarding its missions and functions. All written statements shall be submitted to the Designated Federal Official for the DIA Advisory Board. The Designated Federal Official will ensure that written statements are provided to the Board for its consideration. Written statements may also be submitted in response to the stated agenda of planned board meetings. Statements submitted in response to this notice must be received by the Designated Federal Officer at least five calendar days prior to the meeting which is the subject of this notice. Written statements received after that date may not be provided or considered by the Board until its next meeting. All submissions provided before that date will be presented to the Board before the meeting that is subject of this notice. Contact information for the Designated Federal Officer is listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>.</P>
        <SIG>
          <DATED>Dated: December 28, 2012.</DATED>
          <NAME>Aaron Siegel,</NAME>
          <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31579 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF EDUCATION</AGENCY>
        <SUBJECT>National Advisory Committee on Institutional Quality and Integrity: Notice of Membership</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>

          <P>National Advisory Committee on Institutional Quality and Integrity, Office of Postsecondary Education, Department of Education.<PRTPAGE P="296"/>
          </P>
        </AGY>
        <HD SOURCE="HD1">What is the purpose of this notice?</HD>
        <P>The purpose of this notice is to list the members of the National Advisory Committee on Institutional Quality and Integrity (NACIQI). This notice is required under Section 114(e)(1) of the Higher Education Act (HEA) of 1965, as amended.</P>
        <HD SOURCE="HD1">What is the role of NACIQI?</HD>
        <P>The NACIQI is established under Section 114 of the HEA, and is composed of 18 members appointed—</P>
        <P>(A) On the basis of the individuals' experience, integrity, impartiality, and good judgment;</P>
        <P>(B) From among individuals who are representatives of, or knowledgeable concerning, education and training beyond secondary education, representing all sectors and types of institutions of higher education; and,</P>
        <P>(C) On the basis of the individuals' technical qualifications, professional standing, and demonstrated knowledge in the fields of accreditation and administration of higher education.</P>
        
        <FP>The NACIQI meets at least twice a year and provides recommendations to the Secretary of Education pertaining to:</FP>
        <P>• The establishment and enforcement of the standards of accrediting agencies or associations under subpart 2 of part H of Title IV, HEA.</P>
        <P>• The recognition of specific accrediting agencies or associations.</P>
        <P>• The preparation and publication of the list of nationally recognized accrediting agencies and associations.</P>
        <P>• The eligibility and certification process for institutions of higher education under Title IV of the HEA.</P>
        <P>• The relationship between (1) accreditation of institutions of higher education and the certification and eligibility of such institutions, and (2) State licensing responsibilities with respect to such institutions.</P>
        <P>• Any other advisory functions relating to accreditation and institutional eligibility that the Secretary may prescribe by regulation.</P>
        <HD SOURCE="HD1">What are the terms of office for the committee members?</HD>
        <P>The term of office of each member is six years, except that the terms of office for the initial members of the Committee shall be three years for members appointed by the Secretary; four years for members appointed by the Speaker of the House of Representatives; and six years for members appointed by the President Pro Tempore of the Senate. Any member appointed to fill a vacancy occurring prior to the expiration of the term for which the member's predecessor was appointed is appointed for the remainder of the term.</P>
        <HD SOURCE="HD1">Who are the current members of the committee?</HD>
        <P>The current members of the NACIQI are:</P>
        <HD SOURCE="HD2">Members Appointed by Secretary of Education Arne Duncan With Terms Expiring September 30, 2013</HD>
        <P>• Jamienne S. Studley, J.D., NACIQI Chair, President and Chief Executive Officer (CEO), Public Advocates, Inc., San Francisco, California.</P>
        <P>• Earl Lewis, Ph.D., Provost and Executive Vice President for Academic Affairs, Emory University, Atlanta, Georgia.</P>
        <P>• Susan D. Phillips, Ph.D., Provost and Vice President for Academic Affairs, The State University of New York at Albany, Albany, New York.</P>
        <P>• Beter-Aron Shimeles, Student Member, Operations Coordinator, Peer Health Exchange NYC, Brooklyn, NY.</P>
        <P>• Frank H. Wu, J.D., Chancellor and Dean, University of California, Hastings College of the Law, San Francisco, California.</P>
        <P>• Federico Zaragoza, Ph.D., Vice Chancellor of Economic and Workforce Development, Alamo Community College District, San Antonio, Texas.</P>
        <HD SOURCE="HD2">Members Appointed by Speaker of the House of Representatives With Terms Expiring September 30, 2014</HD>
        <P>• Arthur J. Rothkopf, J.D., NACIQI Vice-Chair, President Emeritus, Lafayette College, Easton, Pennsylvania. (Mr. Rothkopf resides in Washington, DC)</P>
        <P>• Arthur Keiser, Ph.D., Chancellor, Keiser University, Fort Lauderdale, Florida.</P>
        <P>• William E. Kirwan, Ph.D., Chancellor, University System of Maryland, College Park, Maryland.</P>
        <P>• William Pepicello, Ph.D., President, University of Phoenix, Phoenix, Arizona.</P>
        <P>• Carolyn G. Williams, Ph.D., President Emeritus, Bronx Community College, City University of New York, Bronx, New York.</P>
        <P>• George T. French, Jr., Ph.D., President, Miles College, Fairfield, Alabama.</P>
        <HD SOURCE="HD2">Members Appointed by President Pro Tempore of the Senate With Terms Expiring September 30, 2016</HD>
        <P>• Bruce Cole, Ph.D., Senior Fellow, Hudson Institute, Washington, DC.</P>
        <P>• Jill Derby, Ph.D., Governance Consultant, Association of Governing Boards of Colleges and Universities.</P>
        <P>• Wilfred McClay, Ph.D., SunTrust Bank Chair of Excellence in Humanities, University of Tennessee at Chattanooga, Chattanooga, Tennessee.</P>
        <P>• Anne D. Neal, J.D., President, American Council of Trustees and Alumni, Washington, DC.</P>
        <P>• Cameron C. Staples, J.D., President and Chief Executive Officer (CEO), New England Association of Schools and Colleges, Bedford, Massachusetts.</P>
        <P>• Larry N. Vanderhoef, Ph.D., Chancellor Emeritus, University of California—Davis, Davis, California.</P>
        <HD SOURCE="HD1">How can I obtain additional information?</HD>

        <P>If you have any specific questions about the NACIQI, please contact Carol Griffiths, Executive Director, NACIQI Committee, telephone (202) 219-7009, fax (202) 502-7874, email:<E T="03">Carol.Griffiths@ed.gov,</E>between 9:00 a.m. and 5:00 p.m., Monday through Friday.</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 Federal Digital System at<E T="03">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 the 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">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>
        <SIG>
          <DATED>Dated: December 27, 2012.</DATED>
          <NAME>Arne Duncan,</NAME>
          <TITLE>Secretary of Education.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31620 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4000-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <SUBJECT>Combined Notice of Filings #1</SUBJECT>
        <P>Take notice that the Commission received the following electric rate filings:</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER10-2294-003; ER11-3808-002; ER11-3980-002.</P>
        <P>
          <E T="03">Applicants:</E>ORNI 18 LLC, ORNI 39 LLC, ORNI 14 LLC.</P>
        <P>
          <E T="03">Description:</E>Notice of Non-Material Change-in-Status of ORNI 18 LLC,<E T="03">et al.</E>
        </P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.<PRTPAGE P="297"/>
        </P>
        <P>
          <E T="03">Accession Number:</E>20121221-5316.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER10-3063-001.</P>
        <P>
          <E T="03">Applicants:</E>Green Country Energy, LLC.</P>
        <P>
          <E T="03">Description:</E>Green Country Energy, LLC submits Triennial Market Power Update for the Southwest Power Pool, Inc. Region.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5186.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 2/19/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER12-574-000.</P>
        <P>
          <E T="03">Applicants:</E>ITC Midwest LLC.</P>
        <P>
          <E T="03">Description:</E>Filing of a Refund Report to be effective N/A.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5148.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER12-718-003.</P>
        <P>
          <E T="03">Applicants:</E>PJM Interconnection, L.L.C. and New York Independent System Operator, Inc.</P>
        <P>
          <E T="03">Description:</E>Joint Waiver Request of PJM Interconnection, L.L.C. and New York Independent System Operator, Inc.</P>
        <P>
          <E T="03">Filed Date:</E>12/24/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121224-5111.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/4/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER12-2178-003; ER10-2172-014; ER11-2016-009; ER10-2184-014; ER10-2183-011; ER10-1048-011; ER10-2176-015; ER10-2192-014; ER11-2056-008; ER10-2178-014; ER10-2174-014; ER11-2014-011; ER11-2013-011; ER10-3308-013; ER10-1020-010; ER10-1145-010; ER10-1144-009; ER10-1078-010; ER10-1080-010; ER11-2010-011 ER10-1081-010; ER10-2180-014; ER11-2011-010; ER12-2528-002; ER11-2009-010; ER10-1143-010; ER12-1829-003 ER11-2007-009; ER12-1223-008; ER11-2005-011.</P>
        <P>
          <E T="03">Applicants:</E>AV Solar Ranch 1, LLC, Baltimore Gas and Electric Company, Cassia Gulch Wind Park, CER Generation, LLC, CER Generation II, LLC, Commonwealth Edison Company, Constellation Energy Commodities Group, Inc, Constellation Energy Commodities Group Maine, LLC, Constellation Mystic Power, LLC, Constellation NewEnergy, Inc., Constellation Power Source Generation, Inc., Cow Branch Wind Power, L.L.C., CR Clearing, LLC, Criterion Power Partners, LLC, Exelon Framingham LLC, Exelon Generation Company, LLC, Exelon New Boston, LLC, Exelon West Medway, LLC, Exelon Wind 4, LLC, Handsome Lake Energy, LLC, Harvest WindFarm, LLC, High Mesa Energy, LLC, Michigan Wind 1, LLC, PECO Energy Company, Shooting Star Wind Project, LLC, Tuana Springs Energy, LLC, Wildcat Wind, LLC, Wind Capital Holdings, LLC, Exelon Wyman, LLC.</P>
        <P>
          <E T="03">Description:</E>Updated Market Power Analysis of AV Solar Ranch 1, LLC,<E T="03">et al.</E>for the Southwest Power Pool Inc. Region.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5329.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 2/19/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER12-2701-001.</P>
        <P>
          <E T="03">Applicants:</E>Pacific Gas and Electric Company.</P>
        <P>
          <E T="03">Description:</E>Transmission Owner Rate Case 2013 (TO14) Compliance Filing to be effective 5/1/2013.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5070.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-263-001.</P>
        <P>
          <E T="03">Applicants:</E>Midwest Independent Transmission System Operator, Inc.</P>
        <P>
          <E T="03">Description:</E>12-21-12 Attachment MM Amendment to be effective 1/1/2013.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5302.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-286-001.</P>
        <P>
          <E T="03">Applicants:</E>AEP Generating Company.</P>
        <P>
          <E T="03">Description:</E>Unit Power Agreements Amendment of Pending to be effective 12/31/2012.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5098.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-534-001.</P>
        <P>
          <E T="03">Applicants:</E>Mammoth One, LLC.</P>
        <P>
          <E T="03">Description:</E>Mammoth One LLC Amendment to Petition to be effective 2/1/2013.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5173.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-613-000.</P>
        <P>
          <E T="03">Applicants:</E>Pacific Gas and Electric Company.</P>
        <P>
          <E T="03">Description:</E>Transmission Access Charge Balancing Account Adjustment (TACBAA) 2013 to be effective 5/1/2013.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5114.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-614-000.</P>
        <P>
          <E T="03">Applicants:</E>Kincaid Generation, L.L.C.</P>
        <P>
          <E T="03">Description:</E>Initial Rate Schedules (35.12) to be effective 3/1/2013.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5215.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-615-000.</P>
        <P>
          <E T="03">Applicants:</E>High Mesa Energy, LLC.</P>
        <P>
          <E T="03">Description:</E>Compliance Filing of Revised Market-Based Rate Tariff to be effective 1/1/2013.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5245.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-616-000.</P>
        <P>
          <E T="03">Applicants:</E>Pacific Gas and Electric Company.</P>
        <P>
          <E T="03">Description:</E>Existing Transmission Contract (ETC) Rate Filing 2013 to be effective 3/1/2013.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5258.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-616-001.</P>
        <P>
          <E T="03">Applicants:</E>Pacific Gas and Electric Company.</P>
        <P>
          <E T="03">Description:</E>Existing Transmission Contract (ETC) Rate Filing 2013, First Amendment to be effective 3/1/2013.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5301.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-616-002.</P>
        <P>
          <E T="03">Applicants:</E>Pacific Gas and Electric Company.</P>
        <P>
          <E T="03">Description:</E>Existing Transmission Contract (ETC) Rate Filing 2013, Second Amendment to be effective 3/1/2013.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5303.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-617-000.</P>
        <P>
          <E T="03">Applicants:</E>Shooting Star Wind Project, LLC.</P>
        <P>
          <E T="03">Description:</E>Compliance Filing of Revised Market-Based Rate Tariff to be effective 1/1/2013.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5267.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-618-000.</P>
        <P>
          <E T="03">Applicants:</E>WPS Westwood Generation, LLC.</P>
        <P>
          <E T="03">Description:</E>Notice of Non-Material Change to be effective 12/20/2012.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5272.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-619-000.</P>
        <P>
          <E T="03">Applicants:</E>PacifiCorp.</P>
        <P>
          <E T="03">Description:</E>BPA General Transfer Agreement (West) to be effective 12/31/2012.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5284.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-620-000.</P>
        <P>
          <E T="03">Applicants:</E>Northern States Power Company, a Wisconsin corporation.</P>
        <P>
          <E T="03">Description:</E>20121221_G3_Bloomer_ESA to be effective 12/21/2012.</P>
        <P>
          <E T="03">Filed Date:</E>12/24/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121224-5000.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/14/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-621-000.</P>
        <P>
          <E T="03">Applicants:</E>Pacific Gas and Electric Company.</P>
        <P>
          <E T="03">Description:</E>CCSF IA-2013 Annual Transmission Rate Adjustment to be effective 1/1/2013.<PRTPAGE P="298"/>
        </P>
        <P>
          <E T="03">Filed Date:</E>12/24/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121224-5001.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/14/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ER13-622-000.</P>
        <P>
          <E T="03">Applicants:</E>Pacific Gas and Electric Company.</P>
        <P>
          <E T="03">Description:</E>2nd Amendment to Extend the PG&amp;E-SVP Interconnection Agreement to be effective 2/28/2013.</P>
        <P>
          <E T="03">Filed Date:</E>12/24/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121224-5002.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/14/13.</P>
        
        <P>Take notice that the Commission received the following electric securities filings:</P>
        
        <P>
          <E T="03">Docket Numbers:</E>ES13-12-000.</P>
        <P>
          <E T="03">Applicants:</E>ITC Midwest LLC.</P>
        <P>
          <E T="03">Description:</E>ITC Midwest LLC submits Application Under Section 204 of the Federal Power Act for Authorization to Issue Debt Securities.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5318.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</P>
        
        <P>Take notice that the Commission received the following foreign utility company status filings:</P>
        
        <P>
          <E T="03">Docket Numbers:</E>FC13-1-000; FC13-2-000; FC13-3-000; FC13-4-000; FC13-5-000; FC13-6-000.</P>
        <P>
          <E T="03">Applicants:</E>Pacific Northern Gas Ltd., AtlaGas Utilities Inc., Heritage Gas Ltd., McNair Creek Hydro Limited Partnership, AtlaGas Pipeline Partnership, Bear Mountain Wind Limited Partnership.</P>
        <P>
          <E T="03">Description:</E>Self-Certification of foreign utility company subsidiaries of AltaGas Ltd.</P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5042.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</P>
        
        <P>Take notice that the Commission received the following public utility holding company filings:</P>
        
        <P>
          <E T="03">Docket Numbers:</E>PH13-6-000.</P>
        <P>
          <E T="03">Applicants:</E>Enbridge Inc.</P>
        <P>
          <E T="03">Description:</E>Enbridge Inc. submits FERC-65B Waiver Notification,<E T="03">et al.</E>
        </P>
        <P>
          <E T="03">Filed Date:</E>12/21/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121221-5327.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/11/13.</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:00 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: December 26, 2012.</DATED>
          <NAME>Nathaniel J. Davis, Sr.,</NAME>
          <TITLE>Deputy Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31580 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <SUBJECT>Combined Notice of Filings</SUBJECT>
        <P>Take notice that the Commission has received the following Natural Gas Pipeline Rate and Refund Report filings:</P>
        <HD SOURCE="HD1">Filings Instituting Proceedings</HD>
        <P>
          <E T="03">Docket Numbers:</E>RP13-415-000.</P>
        <P>
          <E T="03">Applicants:</E>Texas Eastern Transmission, LP.</P>
        <P>
          <E T="03">Description:</E>Texas Eastern Transmission, LP submits tariff filing per 154.403: EPC FEB 2013 FILING to be effective 2/1/2013.</P>
        <P>
          <E T="03">Filed Date:</E>12/27/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121227-5048.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 1/8/13.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP12-308-000.</P>
        <P>
          <E T="03">Applicants:</E>Golden Pass Pipeline LLC.</P>
        <P>
          <E T="03">Description:</E>Annual Report of Penalty Revenue and Costs of Golden Pass to be effective N/A.</P>
        <P>
          <E T="03">Filed Date:</E>12/13/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121213-5086.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 12/28/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP13-385-000.</P>
        <P>
          <E T="03">Applicants:</E>Gulf South Pipeline Company, LP.</P>
        <P>
          <E T="03">Description:</E>Amendment to Neg Rate Agmt (Sequent 34693-13) to be effective 12/18/2012.</P>
        <P>
          <E T="03">Filed Date:</E>12/13/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121213-5027.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 12/28/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP13-386-000.</P>
        <P>
          <E T="03">Applicants:</E>Texas Eastern Transmission, LP.</P>
        <P>
          <E T="03">Description:</E>Termination of KGen Hinds Non-Conforming Agreement to be effective 12/13/2012.</P>
        <P>
          <E T="03">Filed Date:</E>12/13/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121213-5103.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 12/28/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP13-387-000.</P>
        <P>
          <E T="03">Applicants:</E>Ozark Gas Transmission, L.L.C.</P>
        <P>
          <E T="03">Description:</E>KGen-Entergy Arkansas Permanent Release to be effective 12/13/2012.</P>
        <P>
          <E T="03">Filed Date:</E>12/13/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121213-5134.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 12/28/12.</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:00 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>
        <HD SOURCE="HD1">Filings in Existing Proceedings</HD>
        <P>
          <E T="03">Docket Numbers:</E>RP12-1065-001.</P>
        <P>
          <E T="03">Applicants:</E>Steckman Ridge, LP.</P>
        <P>
          <E T="03">Description:</E>RP12-1065-000 Compliance Filing to be effective 3/1/2013.</P>
        <P>
          <E T="03">Filed Date:</E>12/13/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121213-5039.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 12/28/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP12-1086-001.</P>
        <P>
          <E T="03">Applicants:</E>Pine Needle LNG Company, LLC.</P>
        <P>
          <E T="03">Description:</E>Pine Needle Order No. 587-V (NAESB 2.0) Second Compliance to be effective 12/1/2012.</P>
        <P>
          <E T="03">Filed Date:</E>12/13/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121213-5070.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 12/28/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP12-1094-001.</P>
        <P>
          <E T="03">Applicants:</E>Bobcat Gas Storage.</P>
        <P>
          <E T="03">Description:</E>RP12-1094-000 Compliance Filing to be effective 3/1/2013.</P>
        <P>
          <E T="03">Filed Date:</E>12/13/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121213-5036.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 12/28/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP12-1096-001.</P>
        <P>
          <E T="03">Applicants:</E>Egan Hub Storage, LLC.</P>
        <P>
          <E T="03">Description:</E>RP12-1096-000  Compliance Filing to be effective 3/1/2013.</P>
        <P>
          <E T="03">Filed Date:</E>12/13/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121213-5037.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 12/28/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP12-1099-001.</P>
        <P>
          <E T="03">Applicants:</E>Saltville Gas Storage Company L.L.C.</P>
        <P>
          <E T="03">Description: Filed Date:</E>12/13/2012.</P>
        <P>
          <E T="03">Accession Number:</E>20121213-5038.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 12/28/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP13-1-001.</P>
        <P>
          <E T="03">Applicants:</E>KO Transmission Company.</P>
        <P>
          <E T="03">Description:</E>Compliance Filing in Docket No. RP13-1 to be effective 12/1/2012.</P>
        <P>
          <E T="03">Filed Date:</E>12/13/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121213-5019.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 12/28/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP13-106-001.</P>
        <P>
          <E T="03">Applicants:</E>Young Gas Storage Company, Ltd.</P>
        <P>
          <E T="03">Description:</E>Young NAESB 2.0 Compliance Filing to be effective 12/1/2012.<PRTPAGE P="299"/>
        </P>
        <P>
          <E T="03">Filed Date:</E>12/13/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121213-5104.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 12/28/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP13-60-002.</P>
        <P>
          <E T="03">Applicants:</E>Tennessee Gas Pipeline Company, L.L.C.</P>
        <P>
          <E T="03">Description:</E>NAESB V2.0 Compliance 12-13-12 to be effective 12/1/2012.</P>
        <P>
          <E T="03">Filed Date:</E>12/13/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121213-5069.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 12/28/12.</P>
        
        <P>
          <E T="03">Docket Numbers:</E>RP13-81-002.</P>
        <P>
          <E T="03">Applicants:</E>Caledonia Energy Partners, L.L.C.</P>
        <P>
          <E T="03">Description:</E>Correction to FERC Gas Tariff to Comply with FERC Order No. 587-V to be effective 12/1/2012.</P>
        <P>
          <E T="03">Filed Date:</E>12/13/12.</P>
        <P>
          <E T="03">Accession Number:</E>20121213-5133.</P>
        <P>
          <E T="03">Comments Due:</E>5 p.m. ET 12/28/12.</P>
        
        <P>Any person desiring to protest in any of the above proceedings must file in accordance with Rule 211 of the Commission's Regulations (18 CFR 385.211) on or before 5:00 p.m. Eastern time on the specified comment date.</P>
        <P>The filings are accessible in the Commission's eLibrary system by clicking on the links or querying the docket number.</P>

        <P>eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, and service 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: December 27, 2012.</DATED>
          <NAME>Nathaniel J. Davis, Sr.,</NAME>
          <TITLE>Deputy Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31612 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <DEPDOC>[FRL-9765-2]</DEPDOC>
        <SUBJECT>Environmental Laboratory Advisory Board Meeting Dates and Agenda</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of teleconference and face-to-face meetings.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Environmental Protection Agency's Environmental Laboratory Advisory Board (ELAB), as previously announced, holds teleconference meetings the third Wednesday of each month at 1:00 p.m. Eastern Time (ET) and two face-to-face meetings each calendar year.</P>
        </SUM>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Written comments on laboratory accreditation issues and/or environmental monitoring or measurement issues are encouraged and should be sent to Ms. Lara P. Phelps, Designated Federal Official, U.S. EPA, 109 T. W. Alexander Drive, Mail Code E243-05, Research Triangle Park, NC 27709 or emailed to<E T="03">phelps.lara@epa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>For 2013, teleconference only meetings will be February 20, 2013 at 1:00 p.m. ET; March 20, 2013 at 1:00 p.m. ET; April 17, 2013 at 1:00 p.m. ET; May 15, 2013 at 1:00 p.m. ET; June 19, 2013 at 1:00 p.m. ET; July 17, 2013 at 1:00 p.m. ET; September 18, 2013 at 1:00 p.m. ET; October 16, 2013 at 1:00 p.m. ET; November 20, 2013 at 1:00 p.m. ET; and December 18, 2013 at 1:00 p.m. ET to discuss the ideas and views presented at the previous ELAB meetings, as well as new business. Items to be discussed by ELAB over these coming meetings include: (1) Issues in continuing the expansion of national environmental accreditation; (2) ELAB support to the Agency's on issues relating to measurement and monitoring for all programs; and (3) follow-up on some of ELAB's past recommendations and issues. In addition to these teleconferences, ELAB will be hosting their two face-to-face meetings with teleconference line also available on January 14, 2013 at the Hyatt Regency Denver in Denver, CO at 8:00 a.m. Mountain Time and on August 5, 2013 at the Hyatt Regency San Antonio in San Antonio, TX at 9:00 a.m. Central Time.</P>
        <P>Members of the public are invited to listen to the teleconference calls, and time permitting, will be allowed to comment on issues discussed during this and previous ELAB meetings. Those persons interested in attending should call Lara P. Phelps on (919) 541-5544 to obtain teleconference information. For information on access or services for individuals with disabilities, please contact Lara P. Phelps on the number above. To request accommodation of a disability, please contact Lara P. Phelps, preferably at least 10 days prior to the meeting, to give the EPA as much time as possible to process your request.</P>
        <SIG>
          <DATED>Dated: December 18, 2012.</DATED>
          <NAME>Glenn Paulson,</NAME>
          <TITLE>EPA Science Advisor.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31536 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL MINE SAFETY AND HEALTH REVIEW COMMISSION</AGENCY>
        <SUBJECT>Sunshine Act Notice</SUBJECT>
        <DATE>December 28, 2012.</DATE>
        <PREAMHD>
          <HD SOURCE="HED">TIME AND DATE:</HD>
          <P>10:00 a.m., Thursday, January 17, 2013 (to commence shortly after completion of meeting on first scheduled case).</P>
        </PREAMHD>
        <PREAMHD>
          <HD SOURCE="HED">PLACE:</HD>
          <P>The Richard V. Backley Hearing Room, Room 511N, 1331 Pennsylvania Avenue NW., Washington, DC 20004 (entry from F Street entrance).</P>
        </PREAMHD>
        <PREAMHD>
          <HD SOURCE="HED">STATUS:</HD>
          <P>Open.</P>
        </PREAMHD>
        <PREAMHD>
          <HD SOURCE="HED">MATTERS TO BE CONSIDERED:</HD>

          <P>The Commission will consider and act upon the following in open session:<E T="03">Clintwood Elkhorn Mining Co.</E>v.<E T="03">Secretary of Labor,</E>Docket Nos. KENT 2011-40-R, et al. (Issues include whether the Administrative Law Judge erred in dismissing a citation because it was issued during an investigation rather than during an inspection.)</P>
          <P>Any person attending this meeting who requires special accessibility features and/or auxiliary aids, such as sign language interpreters, must inform the Commission in advance of those needs. Subject to 29 CFR 2706.150(a)(3) and 2706.160(d).</P>
        </PREAMHD>
        <PREAMHD>
          <HD SOURCE="HED">CONTACT PERSON FOR MORE INFO:</HD>
          <P>Jean Ellen (202) 434-9950/(202) 708-9300 for TDD Relay/1-800-877-8339 for toll free.</P>
        </PREAMHD>
        <SIG>
          <NAME>Emogene Johnson,</NAME>
          <TITLE>Administrative Assistant.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31690 Filed 12-31-12; 11:15 am]</FRDOC>
      <BILCOD>BILLING CODE 6735-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">FEDERAL MINE SAFETY AND HEALTH REVIEW COMMISSION</AGENCY>
        <SUBJECT>Sunshine Act Meeting Notice</SUBJECT>
        <DATE>December 28, 2012.</DATE>
        <PREAMHD>
          <HD SOURCE="HED">TIME AND DATE:</HD>
          <P>10:00 a.m., Thursday, January 17, 2013.</P>
        </PREAMHD>
        <PREAMHD>
          <HD SOURCE="HED">PLACE:</HD>
          <P>The Richard V. Backley Hearing Room, Room 511N, 1331 Pennsylvania Avenue NW., Washington, DC 20004 (entry from F Street entrance).</P>
        </PREAMHD>
        <PREAMHD>
          <HD SOURCE="HED">STATUS:</HD>
          <P>Open.</P>
        </PREAMHD>
        <PREAMHD>
          <HD SOURCE="HED">MATTERS TO BE CONSIDERED:</HD>

          <P>The Commission will consider and act upon the following in open session:<E T="03">Secretary of Labor</E>v.<E T="03">Consolidation Coal Co.,</E>Docket No. WEVA 2009-371. (Issues include whether the Administrative Law Judge erred in concluding that certain violations of safety standards were “significant and substantial.”)</P>

          <P>Any person attending this meeting who requires special accessibility features and/or auxiliary aids, such as<PRTPAGE P="300"/>sign language interpreters, must inform the Commission in advance of those needs. Subject to 29 CFR 2706.150(a)(3) and 2706.160(d).</P>
        </PREAMHD>
        <PREAMHD>
          <HD SOURCE="HED">CONTACT PERSON FOR MORE INFO:</HD>
          <P>Jean Ellen (202) 434-9950/(202) 708-9300 for TDD Relay/1-800-877-8339 for toll free.</P>
        </PREAMHD>
        <SIG>
          <NAME>Emogene Johnson,</NAME>
          <TITLE>Administrative Assistant.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31684 Filed 12-31-12; 11:15 am]</FRDOC>
      <BILCOD>BILLING CODE 6735-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL RESERVE SYSTEM</AGENCY>
        <SUBJECT>Change in Bank Control Notices; Acquisitions of Shares of a Bank or Bank Holding Company</SUBJECT>
        <P>The notificants listed below have applied under the Change in Bank Control Act (12 U.S.C. 1817(j)) and § 225.41 of the Board's Regulation Y (12 CFR 225.41) to acquire shares of a bank or bank holding company. The factors that are considered in acting on the notices are set forth in paragraph 7 of the Act (12 U.S.C. 1817(j)(7)).</P>
        <P>The notices are available for immediate inspection at the Federal Reserve Bank indicated. The notices also will be available for inspection at the offices of the Board of Governors. Interested persons may express their views in writing to the Reserve Bank indicated for that notice or to the offices of the Board of Governors. Comments must be received not later than January 18, 2013.</P>
        <P>A. 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">Davis Family Trust; Steven C. Davis, P.C.; the Steven C. Davis Succession Trust; the Ricky J. Davis Succession Trust; and the Kenneth R. Davis Succession Trust, all of Oklahoma City, Oklahoma; and Scott R. Duncan, Oklahoma City, Oklahoma, as trustee of the Steven C. Davis Succession Trust, the Ricky J. Davis Succession Trust, and the Kenneth R. Davis Succession Trust,</E>to become a part of the group acting in concert to acquire control of First Commercial Bancshares, Inc., and thereby acquire control of First Commercial Bank, both of Edmond, Oklahoma.</P>
        <SIG>
          <DATED>Board of Governors of the Federal Reserve System, December 28, 2012.</DATED>
          <NAME>Robert deV. Frierson,</NAME>
          <TITLE>Secretary of the Board.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31575 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6210-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
        <SUBJECT>Formations of, Acquisitions by, and Mergers of Bank Holding Companies</SUBJECT>

        <P>The companies listed in this notice have applied to the Board for approval, pursuant to the Bank Holding Company Act of 1956 (12 U.S.C. 1841<E T="03">et seq.</E>) (BHC Act), Regulation Y (12 CFR Part 225), and all other applicable statutes and regulations to become a bank holding company and/or to acquire the assets or the ownership of, control of, or the power to vote shares of a bank or bank holding company and all of the banks and nonbanking companies owned by the bank holding company, including the companies listed below.</P>
        <P>The applications listed below, as well as other related filings required by the Board, are available for immediate inspection at the Federal Reserve Bank indicated. The applications will also 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 January 29, 2013.</P>
        <P>A. Federal Reserve Bank of St. Louis (Glenda Wilson, Community Affairs Officer) P.O. Box 442, St. Louis, Missouri 63166-2034:</P>
        <P>1.<E T="03">M&amp;P Community Bancshares, Inc., 401(k) Employee Stock Ownership Plan,</E>to acquire additional shares of M&amp;P Community Bancshares, Inc., for a total of ownership of up to 37 percent and thereby indirectly control Merchants and Planters Bank, all of Newport, Arkansas.</P>
        <SIG>
          <DATED>Board of Governors of the Federal Reserve System, December 28, 2012.</DATED>
          <NAME>Robert deV. Frierson,</NAME>
          <TITLE>Secretary of the Board.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31576 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6210-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL TRADE COMMISSION</AGENCY>
        <DEPDOC>[File No. 101 0023]</DEPDOC>
        <SUBJECT>IDEXX Laboratories, Inc.; Analysis of Proposed Consent Order To Aid Public Comment</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Trade Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed Consent Agreement.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The consent agreement in this matter settles alleged violations of federal law prohibiting unfair or deceptive acts or practices or unfair methods of competition. The attached Analysis to Aid Public Comment describes both the allegations in the draft complaint and the terms of the consent order—embodied in the consent agreement—that would settle these allegations.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be received on or before January 24, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Interested parties may file a comment at<E T="03">https://ftcpublic.commentworks.com/ftc/idexxlabconsent</E>online or on paper, by following the instructions in the Request for Comment part of the<E T="02">SUPPLEMENTARY INFORMATION</E>section below. Write “IDEXX, File No. 101 0023” on your comment and file your comment online at<E T="03">https://ftcpublic.commentworks.com/ftc/idexxlabconsent</E>by following the instructions on the Web-based form. If you prefer to file your comment on paper, mail or deliver your comment to the following address: Federal Trade Commission, Office of the Secretary, Room H-113 (Annex D), 600 Pennsylvania Avenue NW., Washington, DC 20580.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Lisa Kopchik (202-326-3139), FTC, Bureau of Competition, 600 Pennsylvania Avenue NW., Washington, DC 20580.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>Pursuant to Section 6(f) of the Federal Trade Commission Act, 15 U.S.C. 46(f), and FTC Rule 2.34, 16 CFR 2.34, notice is hereby given that the above-captioned consent agreement containing a consent order to cease and desist, having been filed with and accepted, subject to final approval, by the Commission, has been placed on the public record for a period of thirty (30) days. The following Analysis to Aid Public Comment describes the terms of the consent agreement, and the allegations in the complaint. An electronic copy of the full text of the consent agreement package can be obtained from the FTC Home Page (for December 21, 2012), on the World Wide Web, at<E T="03">http://www.ftc.gov/os/actions.shtm.</E>A paper copy can be obtained from the FTC<PRTPAGE P="301"/>Public Reference Room, Room 130-H, 600 Pennsylvania Avenue NW., Washington, DC 20580, either in person or by calling (202) 326-2222.</P>

        <P>You can file a comment online or on paper. For the Commission to consider your comment, we must receive it on or before January 24, 2013. Write “IDEXX, File No. 101 0023” on your comment. Your comment—including your name and your state—will be placed on the public record of this proceeding, including, to the extent practicable, on the public Commission Web site, at<E T="03">http://www.ftc.gov/os/publiccomments.shtm.</E>As a matter of discretion, the Commission tries to remove individuals' home contact information from comments before placing them on the Commission Web site.</P>
        <P>Because your comment will be made public, you are solely responsible for making sure that your comment does not include any sensitive personal information, like anyone's Social Security number, date of birth, driver's license number or other state identification number or foreign country equivalent, passport number, financial account number, or credit or debit card number. You are also solely responsible for making sure that your comment does not include any sensitive health information, like medical records or other individually identifiable health information. In addition, do not include any “[t]rade secret or any commercial or financial information which * * * is privileged or confidential,” as discussed in Section 6(f) of the FTC Act, 15 U.S.C. 46(f), and FTC Rule 4.10(a)(2), 16 CFR 4.10(a)(2). In particular, do not include competitively sensitive information such as costs, sales statistics, inventories, formulas, patterns, devices, manufacturing processes, or customer names.</P>
        <P>If you want the Commission to give your comment confidential treatment, you must file it in paper form, with a request for confidential treatment, and you have to follow the procedure explained in FTC Rule 4.9(c), 16 CFR 4.9(c).<SU>1</SU>
          <FTREF/>Your comment will be kept confidential only if the FTC General Counsel, in his or her sole discretion, grants your request in accordance with the law and the public interest.</P>
        <FTNT>
          <P>

            <SU>1</SU>In particular, the written request for confidential treatment that accompanies the comment must include the factual and legal basis for the request, and must identify the specific portions of the comment to be withheld from the public record.<E T="03">See</E>FTC Rule 4.9(c), 16 CFR 4.9(c).</P>
        </FTNT>

        <P>Postal mail addressed to the Commission is subject to delay due to heightened security screening. As a result, we encourage you to submit your comments online. To make sure that the Commission considers your online comment, you must file it at<E T="03">https://ftcpublic.commentworks.com/ftc/idexxlabconsent</E>by following the instructions on the web-based form. If this Notice appears at<E T="03">http://www.regulations.gov/#!home,</E>you also may file a comment through that Web site.</P>
        <P>If you file your comment on paper, write “IDEXX, File No. 101 0023” on your comment and on the envelope, and mail or deliver it to the following address: Federal Trade Commission, Office of the Secretary, Room H-113 (Annex D), 600 Pennsylvania Avenue NW., Washington, DC 20580. If possible, submit your paper comment to the Commission by courier or overnight service.</P>
        <P>Visit the Commission Web site at<E T="03">http://www.ftc.gov</E>to read this Notice and the news release describing it. The FTC Act and other laws that the Commission administers permit the collection of public comments to consider and use in this proceeding as appropriate. The Commission will consider all timely and responsive public comments that it receives on or before January 24, 2012. You can find more information, including routine uses permitted by the Privacy Act, in the Commission's privacy policy, at<E T="03">http://www.ftc.gov/ftc/privacy.htm.</E>
        </P>
        <HD SOURCE="HD1">Analysis of Agreement Containing Consent Order To Aid Public Comment</HD>
        <P>The Federal Trade Commission has accepted for public comment an Agreement Containing Consent Order to Cease and Desist (“Agreement”) with IDEXX Laboratories, Inc. (“IDEXX”). The Agreement seeks to resolve charges that IDEXX engaged in exclusionary conduct to maintain its monopoly power in the companion animal diagnostic testing equipment and supplies industry in violation of Section 5 of the Federal Trade Commission Act, 15 U.S.C. 45.</P>
        <P>Specifically, the proposed Complaint that accompanies the Agreement (“Complaint”) alleges that IDEXX has used its monopoly power to impose exclusive deals with its distributors. As a result, IDEXX has foreclosed rivals from key distribution channels and limited competition in the relevant market, leading to higher prices, lower output, reduced innovation and diminished consumer choice.</P>
        <P>The Commission anticipates that the competitive issues described in the Complaint will be resolved by accepting the proposed Order, subject to final approval, contained in the Agreement. The Agreement has been placed on the public record for 30 days for receipt of comments from interested members of the public. Comments received during this period will become part of the public record. After 30 days, the Commission will again review the Agreement and comments received, and will decide whether it should withdraw from the Agreement or make final the Order contained in the Agreement. IDEXX has already entered into a non-exclusive distribution agreement with MWI Veterinarian Supply Co., Inc. (“MWI”), and that distribution agreement has been incorporated into the terms of the proposed Order.</P>
        <P>The purpose of this Analysis to Aid Public Comment is to invite and facilitate public comment concerning the proposed Order. It is not intended to constitute an official interpretation of the Agreement and proposed Order or in any way to modify their terms.</P>
        <P>The Agreement is for settlement purposes only and does not constitute an admission by IDEXX that the law has been violated as alleged in the Complaint or that the facts alleged in the Complaint, other than jurisdictional facts, are true.</P>
        <HD SOURCE="HD1">I. The Complaint</HD>
        <P>The Complaint makes the following allegations.</P>
        <HD SOURCE="HD2">A. Industry Background</HD>
        <P>Point of care (“POC”) diagnostic products include rapid assay tests, equipment and supplies that permit a companion animal veterinarian to test, diagnose and treat certain conditions such as heartworm during a single office visit. POC diagnostic products provide real-time results that cannot be obtained through other testing alternatives, such as services offered by outside reference labs.</P>
        <P>Veterinarians are the primary consumers of POC diagnostic products. Veterinarians use POC diagnostic products to assess the general health of animals and to identify pathologies. Veterinarians perform diagnostic testing at veterinary clinics with instruments or test kits manufactured and sold by IDEXX and its competitors. POC testing provides veterinarians and pet owners the medical advantage and convenience of almost-immediate results.</P>
        <P>As of 2009, more than 75% of veterinarians used POC diagnostic testing. Each year, veterinarians in the United States purchase approximately $500 million worth of POC diagnostic products.</P>

        <P>There are no close substitutes for POC diagnostic products. Although veterinarians can purchase some diagnostic services by sending<PRTPAGE P="302"/>specimens to outside laboratories, POC testing allows veterinarians to provide timely, state-of-the-art care. Veterinarians value faster results, particularly when testing is associated with emergencies, pre-surgery, and for diagnoses of conditions that may require the veterinarians to perform follow-up testing or dispense or prescribe medicine as soon as possible.</P>
        <P>Nearly all veterinarians buy their supplies, including POC diagnostic products, from distributors who specialize in supplying companion animal veterinary clinics. Veterinarians overwhelmingly prefer to buy through distributors because of the efficiency and customer service they offer. Other purchasing options are less efficient and more costly.</P>
        <P>Most veterinarians buy a majority of their equipment and supplies from a preferred distributor. More than 75% of veterinarians name Butler Schein Animal Health (“Butler”), Webster Veterinary Supply, Inc. (“Webster”), MWI, Midwest Veterinary Supply, Inc. (“Midwest”), or Victor Medical Company (“Victor”), as their preferred distributor. Combined, these top tier distributors sell more than 85%, by revenue, of the products sold to companion animal veterinarians in the United States.</P>
        <P>Butler, Webster and MWI are recognized by manufacturers, distributors and veterinarians as the pre-eminent national companion animal veterinary supply distributors in the United States. There are no other distributors that provide equivalent levels of service to manufacturers and regularly visit veterinarians in as wide a geographic area as Butler, Webster or MWI. Midwest and Victor are large, regional distributors, also with strong reputations for high-quality service.</P>
        <P>IDEXX and other POC diagnostic product manufacturers use distributors because distributors provide important services to the manufacturer and are the most efficient way for the manufacturer to channel their products to veterinarians. Manufacturers who do not use distributors face more significant obstacles to sales, marketing and delivery than manufacturers who use distributors.</P>
        <P>The top tier distributors provide better services to their manufacturer clients than other distributors. Those better services can include, but are not limited to, more sales, better sales and inventory data transfer, more experienced sales representatives, better market forecasting, more timely payments, and more frequent visits to veterinarian clients.</P>
        <HD SOURCE="HD2">B. The Respondent</HD>
        <P>IDEXX Laboratories, Inc. is a corporation with its principal place of business located in Westbrook, Maine. IDEXX develops, manufactures and sells diagnostic products to veterinarians through distributors. IDEXX has monopoly power in the POC diagnostic products market.</P>
        <P>IDEXX's core business is companion animal diagnostics, including POC instruments and their related consumables, rapid assay test kits (SNAP© tests), digital radiography equipment, practice management software, and diagnostic services through wholly owned and operated reference laboratories. IDEXX's share of the POC diagnostic products market has been at least 70% during each of the past five years (2006-2011). No other firm had more than a 20% share of the relevant market in those same five years.</P>
        <HD SOURCE="HD2">C. IDEXX's Conduct</HD>
        <P>IDEXX bars its distributors from carrying any competing POC diagnostic testing products. IDEXX distributors include all three of the major, national distributors of these products and the two large, regional distributors named above. As noted previously, these distributors sell 85% of equipment and supplies that companion animal veterinarians buy through distributors.</P>
        <HD SOURCE="HD2">D. Competitive Impact of IDEXX's Conduct</HD>
        <P>Because IDEXX has a broad line of products and a dominant position in the POC market, large distributors need to carry the IDEXX line. While distributors need to carry the IDEXX line, they would prefer to carry competing products as well. However, by insisting that distributors make an “all-or-nothing” choice, IDEXX compels distributors to forgo competitors' products. The features of the market that make anticompetitive exclusion possible—IDEXX's status as a “must carry” supplier coupled with its insistence on exclusivity—have endured for many years, and thus the relatively short nominal duration of IDEXX's distribution contracts has not mitigated the anticompetitive effects of the exclusive deals.</P>
        <P>IDEXX's control of distributors means that it forecloses its competition from effectively and efficiently reaching large segments of the veterinarian market, and forces veterinarians to incur greater costs to obtain non-IDEXX products.</P>
        <P>IDEXX has used its monopoly power, the threat of termination, and explicit agreements to prevent those top tier distributors from selling rival POC diagnostic products that the distributors would otherwise choose to sell. As a result, IDEXX has foreclosed its competitors from distributors that sell over 85% of all products purchased through distribution by companion animal veterinary clinics in the United States, and those competitors are impeded from effectively and efficiently marketing their POC diagnostic products to veterinarians.</P>
        <P>IDEXX's exclusionary practices have blocked rivals from the most efficient sales channel. IDEXX has used its exclusionary practices to successfully diminish, marginalize or force its competitors from the U.S. market.</P>
        <P>IDEXX intentionally engages more distribution than it needs, even though that excess distribution is costly and inefficient for IDEXX. Nevertheless, IDEXX continues to engage the excess distribution because it allows IDEXX to block its rivals from using those distributors and insulates IDEXX from competition from its rivals. Thus, IDEXX maintains its monopoly and harms both distributors who would prefer to offer a greater variety of POC diagnostic products, and veterinarians who could buy cheaper, superior, and more convenient POC diagnostic products. IDEXX's exclusionary acts and practices require competing manufacturers to settle for less efficient means to sell their products to veterinarians.</P>
        <P>IDEXX's exclusionary acts and practices erect significant barriers to entry for those manufacturers that have developed, would otherwise have developed, or offered for sale POC diagnostic products that would compete with IDEXX products, thereby resulting in reduced choice for veterinarians.</P>
        <HD SOURCE="HD1">II. Legal Analysis</HD>
        <P>The offense of monopolization under § 2 of the Sherman Act has two elements: (1) the possession of monopoly power in the relevant market; and (2) the willful acquisition, enhancement or maintenance of that power through exclusionary conduct.<SU>2</SU>
          <FTREF/>Exclusive dealing by a monopolist is condemned when the challenged conduct significantly impairs the ability of rivals to compete effectively with the respondent and thus limits the ability of those rivals to constrain the exercise of monopoly power.<SU>3</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>2</SU>
            <E T="03">Verizon Commc'ns</E>v.<E T="03">Law Offices of Curtis</E>v.<E T="03">Trinko LLP.,</E>540 U.S. 398, 407 (2004);<E T="03">United States</E>v.<E T="03">Grinnell Corp.,</E>384 U.S. 563, 570-71 (1966).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>3</SU>
            <E T="03">See, e.g., Aspen Skiing Co.</E>v.<E T="03">Aspen Highlands Skiing Corp.,</E>472 U.S. 585,605 &amp; n.32 (1985) (exclusionary conduct “tends to impair the opportunities of rivals” but “either does not further competition on the merits or does so in an<PRTPAGE/>unnecessarily restrictive way”) (citations omitted);<E T="03">Lorain Journal Co.</E>v.<E T="03">United States,</E>342 U.S. 143, 151-54 (1951) (condemning newspaper's refusal to deal with customers that also advertised on rival radio station because it harmed the radio station's ability to compete);<E T="03">United States</E>v.<E T="03">Microsoft,</E>253 F.3d 34, 68-71 (DC Cir. 2001) (condemning exclusive agreements because they prevented rivals from “pos[ing] a real threat to Microsoft's monopoly”);<E T="03">United States</E>v.<E T="03">Dentsply,</E>399 F.3d 181, 191 (3d Cir. 2005) (“test is not total foreclosure but whether the challenged practices bar a substantial number of rivals or severely restrict the market's ambit”);<E T="03">LePage's, Inc.</E>v.<E T="03">3M,</E>324 F.3d 141, 159-60 (3d Cir. 2003) (same).</P>
        </FTNT>
        <PRTPAGE P="303"/>
        <P>The Complaint alleges that IDEXX has monopoly power and used it to create competitive harm. IDEXX's policy of requiring exclusivity from its distributors has foreclosed its rivals from over 85 percent of available sales opportunities at this level of the distribution chain. This foreclosure is particularly significant because nearly all POC diagnostics are sold to veterinarians through distributors, and other channels to the veterinarians are inconvenient, impractical and more expensive for both the veterinarians and IDEXX's competitors.</P>
        <P>A monopolist may rebut a showing of competitive harm by demonstrating that the challenged conduct is reasonably necessary to achieve a pro-competitive benefit.<SU>4</SU>
          <FTREF/>Any proffered justification, if proven, must be balanced against the harm caused by the challenged conduct.<SU>5</SU>
          <FTREF/>In this case, however, no pro-competitive efficiency justifies IDEXX's exclusionary and anticompetitive conduct. Further, IDEXX cannot show that the exclusive arrangements were reasonably necessary to achieve a procompetitive benefit.</P>
        <FTNT>
          <P>
            <SU>4</SU>
            <E T="03">E.g., Microsoft,</E>253 F.3d at 59.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>5</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <P>A concern about interbrand free-riding also does not justify the substantial anticompetitive effects found here.<SU>6</SU>
          <FTREF/>Free-riding might occur if, for example, IDEXX provided a great deal of training or services to its distributors, and if the training or services help promote the product category as a whole rather than just IDEXX's product. In such an instance, promotion of the competitors' products would “free-ride” on IDEXX's activities. In this case, however, the vast majority of IDEXX's promotional efforts are relevant to IDEXX's products only, thereby reducing the risk of free-riding by IDEXX's competitors. While IDEXX's marketing efforts may generate some consumer interest in the product category as a whole—and not just in IDEXX's own products—this is a part of the natural competitive process. This type of consumer response does not raise a free-riding concern sufficient to justify the substantial anticompetitive effects found here.<SU>7</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>6</SU>“Interbrand free-riding” occurs when a manufacturer provides services, training, or other incentives in the promotion of its products for which it cannot easily charge its dealer, and that dealer “free-rides” on these demand-generating services by substituting a cheaper, more profitable product made by another manufacturer that does not invest in comparable services.<E T="03">See generally,</E>Howard P. Marvel,<E T="03">Exclusive Dealing,</E>25 J.L. &amp; ECON. 1, 8 (1982).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>7</SU>
            <E T="03">See United States</E>v.<E T="03">Dentsply Int'l, Inc.,</E>277 F. Supp. 2d 387, 445 (D. Del. 2003),<E T="03">aff'd in rel. part,</E>399 F.3d at 196-97; Marvel,<E T="03">Exclusive Dealing,</E>25 J.L. &amp; ECON. at 8 (explaining that an interbrand free-riding justification “does not apply if the promotional investment is purely brand specific. In such cases, the dealer will not be in a position to switch customers from brand to brand.”).</P>
        </FTNT>
        <HD SOURCE="HD1">III. The Order</HD>
        <P>Together with the distribution agreement between IDEXX and MWI Veterinary Supply, Inc., signed in September 2012, the proposed Consent Order is designed to make the market for POC diagnostic testing products more competitive. Generally, the Order prohibits IDEXX from maintaining exclusive distribution arrangements with all three national distributors. Specifically, Part II of the Order addresses this core provision. Part III imposes reporting requirements for four years. Parts IV and V impose other reporting and compliance requirements. Unless otherwise indicated, the Order will expire in ten years.</P>
        <P>The Order defines the “national distributors” as Butler, MWI and Webster, so long as they continue to distribute companion animal POC diagnostic equipment and supplies. Starting in January, 2013, MWI can distribute both IDEXX products and competitive products. Either IDEXX or MWI can terminate the agreement. If the parties agree that MWI will return to an exclusive arrangement with IDEXX, IDEXX must have a non-exclusive agreement with one of the two other national distributors.</P>
        <P>All future non-exclusive agreements between IDEXX and a national distributor must meet the requirements of the Order. Paragraph II.B requires that such an agreement begin with a two year term, and provide for additional renewal terms of at least one year; that IDEXX shall not urge, induce, coerce, threaten, pressure, penalize, withhold the sale of product, or otherwise retaliate against the non-exclusive national distributor in order to limit its sales of other manufacturers' products.</P>
        <P>Paragraph II.B also requires IDEXX to notify the Federal Trade Commission about the termination of any non-exclusive distribution agreement. Paragraph II.C orders that IDEXX show any future non-exclusive distribution agreement to the Commission at least thirty (30) days before it is signed.</P>
        <P>Further, if the non-exclusive national distributor merges with, acquires, or is acquired by a distributor that has an exclusive distribution arrangement with IDEXX, the non-exclusive distribution agreement stays in effect.</P>
        <SIG>
          <P>By direction of the Commission, Commissioner Ohlhausen abstaining.</P>
          <NAME>Richard C. Donohue,</NAME>
          <TITLE>Acting Secretary.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31571 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6750-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">GENERAL SERVICES ADMINISTRATION</AGENCY>
        <DEPDOC>[OMB Control No. 3090-0086; Docket 2012-0001; Sequence 18]</DEPDOC>
        <SUBJECT>General Services Administration Acquisition Regulation; Information Collection; Proposal To Lease Space, GSA Forms 1364A, 1364A-1, 1364B, 1364C, 1364D</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of the Chief Acquisition Officer, General Services Administration (GSA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of request for comments regarding an extension of an information collection requirement for an existing OMB clearance.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Under the provisions of the Paperwork Reduction Act, the General Services Administration will be submitting to the Office of Management and Budget (OMB) a request to review and approve an extension of a previously approved information collection requirement for Proposal to Lease Space, GSA Form 1364. The General Services Administration (GSA) has various mission responsibilities related to the acquisition and provision of real property management, and disposal of real and personal property. These mission responsibilities generate requirements that are realized through the solicitation and award of leasing contracts. Individual solicitations and resulting contracts may impose unique information collection/reporting requirements on contractors, not required by regulation, but necessary to (1) evaluate whether the physical attributes of offered properties meet the Government's requirements and (2) compare the owner/offeror's price proposal against competing offers.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Submit comments on or before: March 4, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Submit comments identified by Information Collection 3090-0086, Proposal to Lease Space, GSA Forms 1364A, 1364A-1, 1364B,<PRTPAGE P="304"/>1364C and 1364D by any of the following methods:</P>
          <P>•<E T="03">Regulations.gov: http://www.regulations.gov.</E>Submit comments via the Federal eRulemaking portal by inputting “Information Collection 3090-0086, Proposal to Lease Space, GSA Form 1364D” under the heading “Enter Keyword or ID” and selecting “Search”. Select the link “Submit a Comment” that corresponds with “Information Collection 3090-0086, Proposal to Lease Space, GSA Form 1364”. Follow the instructions provided at the “Submit a Comment” screen. Please include your name, company name (if any), and “Information Collection 3090-0086, Proposal to Lease Space, GSA Form 1364” on your attached document.</P>
          <P>•<E T="03">Fax:</E>202-501-4067.</P>
          <P>•<E T="03">Mail:</E>General Services Administration, Regulatory Secretariat (MVCB), 1275 First Street NE., Washington, DC 20417. ATTN: Hada Flowers/IC 3090-0086, Proposal to Lease Space, GSA Form 1364D.</P>
          <P>
            <E T="03">Instructions:</E>Please submit comments only and cite Information Collection 3090-0086, Proposal to Lease Space, GSA Form 1364, in all correspondence related to this collection. All comments received will be posted without change to<E T="03">http://www.regulations.gov,</E>including any personal and/or business confidential information provided.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Ms. Kathy Rifkin, Procurement Analyst, General Services Acquisition Policy Division, GSA (816) 823-2170 or via email at<E T="03">kathy.rifkin@gsa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">A. Purpose</HD>
        <P>The approval is requested for 5 versions of the form, GSA Forms 1364A, 1364A-1, 1364B, 1364C, and 1364D. These forms are used to obtain information for offer evaluation and lease award purposes regarding property being offered for lease to house Federal agencies. This includes financial aspects of offers for analysis and negotiation, such as real estate taxes, adjustments for vacant space, and offerors' construction overhead fees.</P>
        <P>These Form 1364 versions are products of a GSA Lease Reform Initiative to improve the lease acquisition process for GSA, client agencies, and the private sector. Process reform over the past 2 years has brought reform to GSA leasing by implementing a variety of enhancements and improvements to the methods by which GSA procures space. As a direct result of the reform, five new lease contract models have been developed that are targeted to meet the needs of the national leased portfolio. Four of the lease models require offerors to complete a GSA Form 1364. The new versions of GSA Form 1364 require the submission of information specifically aligned with the leasing models and avoid mandating submission of information that is not required for use in evaluation and award under each model. The Simplified Lease Model uses GSA Forms 1364A and 1364A-1. This model obtains a firm, fixed price for rent, which includes the cost of tenant improvement construction. Therefore, leases using the Simplified model do not include post-award tenant improvement cost information on the form.</P>
        <P>The 1364A includes rental rate components and cost data that becomes part of the lease contract and that is necessary to satisfy GSA pricing policy requirements.</P>
        <P>The 1364A-1 is a checklist that addresses technical requirements as referenced in the Request for Lease Proposals. The 1364A-1 is separate from the proposal itself and maintained in the lease file; it does not become an exhibit to the lease. The 1364A-1 may contain proprietary offeror information that cannot be released under the Freedom of Information Act.</P>
        <P>The Streamlined Lease Model uses GSA Form 1364B. The Streamlined Lease model is a unique model that was designed to support small to mid-size leases up to $500,000 average net annual rent and occupancies that fall under Interagency Security Committee Security Levels I, II, and III. The Streamlined Lease model is not used for projects requiring lease construction or leases employing the best value trade-off evaluation process.</P>
        <P>The Standard Lease Model, which relies on an allowance instead of firm fixed pricing for initial tenant improvements, uses GSA Form 1364C. The 1364C captures an offeror's proposed interest rate and amortization period for the tenant improvements, in addition to the lessor's overhead fees.</P>
        <P>The Succeeding and Superseding Lease Model uses GSA Form 1364D. These leases are negotiated with the existing lessor after advertisements and cost benefit analyses result in a determination that such a lease is in the best interests of the government. The form has less data input required than for a Standard lease; it also includes current rental rate information, supplied by the Government.</P>
        <P>The 1364A-1, 1364B, and 1364C summarize an offeror's technical compliance with some important statutory and regulatory requirements to make the overall offer process easier for offerors to understand (e.g., accessibility and seismic standards, flood plain compliance, asbestos). The 1364C also limits the collection of tenant improvement overhead fees to the architect/engineering fees and lessor's project management fees.</P>
        <HD SOURCE="HD1">B. Annual Reporting Burden</HD>
        <P>
          <E T="03">Respondents:</E>3565.</P>
        <P>
          <E T="03">Responses per Respondent:</E>1.</P>
        <P>
          <E T="03">Hours per Response:</E>2.4238 (average).</P>
        <P>
          <E T="03">Total Burden Hours:</E>8641.</P>
        <P>
          <E T="03">Obtaining Copies of Proposals:</E>Requesters may obtain a copy of the information collection documents from the General Services Administration, Regulatory Secretariat, 1275 First Street NE., Washington, DC 20417, telephone (202) 501-4755. Please cite OMB Control No. 3090-0086, GSA Form 1364, Proposal to Lease Space, in all correspondence.</P>
        <SIG>
          <DATED>Dated: December 21, 2012.</DATED>
          <NAME>Joseph A. Neurauter,</NAME>
          <TITLE>Director, Office of Acquisition Policy &amp; Senior Procurement Executive (MV).</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31622 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6820-61-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">GENERAL SERVICES ADMINISTRATION</AGENCY>
        <DEPDOC>[OMB Control No. 3090-0284; Docket 2012-0001; Sequence 14]</DEPDOC>
        <SUBJECT>Office of Citizen Services and Innovative Technologies; Submission for OMB Review; Data.gov Feedback Mechanisms</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>General Services Administration (GSA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of a request for comments regarding an extension of an existing information collection.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>Under the provisions of the Paperwork Reduction Act, the General Services Administration will be submitting to the Office of Management and Budget (OMB) a request to review and approve a previously approved information collection requirement regarding Data.gov Feedback Mechanisms. A notice was published in the<E T="04">Federal Register</E>at 77 FR 59614, on September 28, 2012. No comments were received.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Submit comments on or before:</E>February 4, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Submit comments identified by Information Collection 3090-0284, Data.gov Feedback Mechanisms, by any of the following methods:</P>
          <P>•<E T="03">Regulations.gov: http://www.regulations.gov.</E>Submit comments<PRTPAGE P="305"/>via the Federal eRulemaking portal by searching the OMB control number. Select the link “Submit a Comment” that corresponds with “Information Collection 3090-0284, Data.gov Feedback Mechanisms”. Follow the instructions provided at the “Submit a Comment” screen. Please include your name, company name (if any), and “Information Collection 3090-0284, Data.gov Feedback Mechanisms” on your attached document.</P>
          <P>•<E T="03">Fax:</E>202-501-4067.</P>
          <P>•<E T="03">Mail:</E>General Services Administration, Regulatory Secretariat (MVCB), 1275 First Street NE., Washington, DC 20417. ATTN: Hada Flowers/IC 3090-0284, Data.gov Feedback Mechanisms.</P>
          <P>
            <E T="03">Instructions:</E>Please submit comments only and cite Information Collection 3090-0284, Data.gov Feedback Mechanisms, in all correspondence related to this collection. All comments received will be posted without change to<E T="03">http://www.regulations.gov,</E>including any personal and/or business confidential information provided.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Marion Royal, General Services Administration, Office of Citizen Services and Innovative Technologies, 1275 First Street NE., Washington, DC 20417; telephone number: 202-208-4643; fax number: 202-357-0077; email address:<E T="03">datagov@gsa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">A. Purpose</HD>
        <P>Pursuant to section 3506(c)(2)(A) of the PRA, GSA specifically solicits comments and information to enable it to:</P>
        <P>(i) 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>(ii) 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>(iii) Enhance the quality, utility, and clarity of the information to be collected; and</P>

        <P>(iv) Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated electronic, mechanical, or other technological collection techniques or other forms of information technology,<E T="03">e.g.,</E>permitting electronic submission of responses. In particular, GSA is requesting comments from very small businesses (those that employ less than 25) on examples of specific additional efforts that GSA could make to reduce the paperwork burden for very small businesses affected by this collection.</P>
        <HD SOURCE="HD2">What should I consider when I prepare my comments for GSA?</HD>
        <P>You may find the following suggestions helpful for preparing your comments.</P>
        <P>1. Explain your views as clearly as possible and provide specific examples.</P>
        <P>2. Describe any assumptions that you used.</P>
        <P>3. Provide copies of any technical information and/or data you used that support your views.</P>
        <P>4. If you estimate potential burden or costs, explain how you arrived at the estimate that you provide.</P>
        <P>5. Offer alternative ways to improve the collection activity.</P>

        <P>6. Make sure to submit your comments by the deadline identified under<E T="02">DATES</E>.</P>

        <P>7. To ensure proper receipt by GSA, be sure to identify the ICR title on the first page of your response. You may also provide the<E T="04">Federal Register</E>citation.</P>
        
        <FP>Data.gov is inspired by the President's program for “Open Government” and “Transparency”. In response to the President's direction to improve the transparency of government, the Federal Chief Information Officer (CIO) Council created a Web site/portal that improves public access to a wide variety of U.S. Government data. Data.gov is a public-friendly Web site that provides descriptions of the federal datasets, information on how to access the datasets, points of contact information, metadata information, interactive datasets, “Communities” areas centered on specific topics, and links to publicly accessible applications that leverage the datasets. This information collection request is being submitted in order to fulfill the public feedback aspects of this important initiative. Data.gov visitors will be provided opportunities to provide feedback and ratings in the spirit of the President's open government and transparency initiative. Examples of feedback mechanisms are:</FP>
        <P>(1) A five-star rating system to give visitors information about which datasets other visitors found most useful and interesting on the Data.gov Web page,</P>
        <P>(2) A “Suggest Other Datasets” entry page for the public to submit ideas for datasets with an optional contact email address provided for those visitors wishing to identify themselves,</P>
        <P>(3) A “Contact Us” entry page with an optional contact email address for those visitors wishing to identify themselves,</P>
        <P>(4) Pages for visitors to advise how they leverage the datasets in new and different ways to build applications, conduct analysis, and perform research,</P>
        <P>(5) Pages for visitors to rate the benefit of the reported new solutions, etc.</P>
        <HD SOURCE="HD1">B. Annual Reporting Burden</HD>
        <P>
          <E T="03">Number of Respondents:</E>9882.</P>
        <P>
          <E T="03">Total Annual Responses:</E>9882.</P>
        <P>
          <E T="03">Average Hours per Response:</E>0.017.</P>
        <P>
          <E T="03">Total Burden Hours:</E>168.</P>
        <P>
          <E T="03">Obtaining Copies of Proposals:</E>Requesters may obtain a copy of the information collection documents from the General Services Administration, Regulatory Secretariat Division (MVCB), 1275 First Street NE., Washington, DC 20417, telephone (202) 501-4755. Please cite OMB Control No. 3090-0284, Data.gov Feedback Mechanisms, in all correspondence.</P>
        <SIG>
          <DATED>Dated: December 19, 2012.</DATED>
          <NAME>Casey Coleman,</NAME>
          <TITLE>Chief Information Officer.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31621 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6820-WY-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Centers for Disease Control and Prevention</SUBAGY>
        <DEPDOC>[60 Day-13-0739]</DEPDOC>
        <SUBJECT>Proposed Data Collections Submitted for Public Comment and Recommendations</SUBJECT>

        <P>In compliance with the requirement of Section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995 for opportunity for public comment on proposed data collection projects, the Centers for Disease Control and Prevention (CDC) will publish periodic summaries of proposed projects. To request more information on the proposed projects or to obtain a copy of the data collection plans and instruments, call 404-639-7570 or send comments to Ron Otten, 1600 Clifton Road, MS D-74, Atlanta, GA 30333 or send an email to<E T="03">omb@cdc.gov.</E>
        </P>

        <P>Comments are invited on: (a) Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information shall have practical utility; (b) the accuracy of the agency's estimate of the burden of the proposed collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents, including through the<PRTPAGE P="306"/>use of automated collection techniques or other forms of information technology. Written comments should be received within 60 days of this notice.</P>
        <HD SOURCE="HD1">Proposed Project</HD>
        <P>CDC Oral Health Management Information System (OMB No. 0920-0739, exp. 5/31/2013)—Extension—National Center for Chronic Disease Prevention and Public Health Promotion (NCDDPHP), Centers for Disease Control and Prevention (CDC).</P>
        <HD SOURCE="HD2">Background and Brief Description</HD>
        <P>The CDC seeks to improve the oral health of the nation by targeting efforts to improve the infrastructure of state and territorial oral health departments, strengthen and enhance program capacity related to monitoring the population's oral health status and behaviors, develop effective programs to improve the oral health of children and adults, evaluate program accomplishments, and inform key stakeholders, including policy makers, of program results. Through a cooperative agreement program (Program Announcement DP08-802 and DP10-1012), CDC has provided funding to 20 states to strengthen their core oral health infrastructure and capacity. CDC funding also helps states reduce health disparities among high-risk populations including, but not limited to, those of lower socioeconomic status (SES), Hispanic Americans, African Americans, and other ethnic groups.</P>
        <P>NCCDPHP is currently pursuing a key initiative to improve the efficiency and effectiveness of CDC project officers who oversee the state and territorial oral health programs. An electronic management information system (MIS) to support program management, consulting and evaluation has been developed in support of the cooperative agreement. The MIS provides a central repository of information, such as the plans of the state or territorial oral health programs (their goals, objectives, performance milestones and indicators), as well as state and territorial oral health performance activities including programmatic and financial information. State oral health programs have used the MIS to submit their required semi-annual reports to CDC (CDC Oral Health Management Information System, OMB No. 0920-0739, exp. 5/31/2013). The last report under the current Funding Opportunity Announcement (FOA) is due on October 31, 2013.</P>
        <P>CDC is requesting OMB approval to extend clearance for the MIS until December 31, 2013. Information will be reported to CDC once during this period. The extension will allow CDC to receive final reports from the state oral health programs and to provide any technical assistance or follow-up support that may be needed to produce accurate final reports. The estimated burden per response is 11 hours.</P>
        <P>All information will be collected electronically. There is no change to the estimated number of respondents or the burden per response. There are no costs to respondents other than their time.</P>
        <GPOTABLE CDEF="s130,12C,12C,12C,12C" COLS="5" OPTS="L2,i1">
          <TTITLE>Estimated Annualized Burden Hours</TTITLE>
          <BOXHD>
            <CHED H="1">Type of respondents</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 per</LI>
              <LI>response</LI>
              <LI>(in hours)</LI>
            </CHED>
            <CHED H="1">Total burden<LI>(in hours)</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">State Oral Health Programs</ENT>
            <ENT>20</ENT>
            <ENT>1</ENT>
            <ENT>11</ENT>
            <ENT>220</ENT>
          </ROW>
        </GPOTABLE>
        <SIG>
          <DATED>Dated: December 27, 2012.</DATED>
          <NAME>Ron A. Otten,</NAME>
          <TITLE>Director, Office of Scientific Integrity (OSI), Office of the Associate Director for Science (OADS), Office of the Director, Centers for Disease Control and Prevention.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31600 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4163-18-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Centers for Disease Control and Prevention</SUBAGY>
        <DEPDOC>[60 Day-13-0850]</DEPDOC>
        <SUBJECT>Proposed Data Collections Submitted for Public Comment and Recommendations</SUBJECT>

        <P>In compliance with the requirement of Section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995 for opportunity for public comment on proposed data collection projects, the Centers for Disease Control and Prevention (CDC) will publish periodic summaries of proposed projects. To request more information on the proposed projects or to obtain a copy of the data collection plans and instruments, call 404-639-7570 and send comments to Ron Otten, 1600 Clifton Road MS-D74, Atlanta, GA 30333 or send an email to<E T="03">omb@cdc.gov.</E>
        </P>
        <P>Comments are invited on (a) whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information shall have a practical utility; (b) the accuracy of the agency's estimate of the burden of the proposed collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or other forms of information technology. Written comments should be received within 60 days of this notice.</P>
        <HD SOURCE="HD1">Proposed Project</HD>
        <P>Laboratory Response Network (LRN) (OMB No. 0920-0850, Exp. 5/31/2013)—Extension—National Center for Emerging and Zoonotic Infections (NCEZID, Centers for Disease Control and Prevention (CDC).</P>
        <HD SOURCE="HD2">Background and Brief Description</HD>
        <P>The Laboratory Response Network (LRN) was established by the Department of Health and Human Services (HHS), Centers for Disease Control and Prevention (CDC) in accordance with Presidential Decision Directive 39, which outlined national anti-terrorism policies and assigned specific missions to Federal departments and agencies. The LRN's mission is to maintain an integrated national and international network of laboratories that can respond to suspected acts of biological, chemical, or radiological threats and other public health emergencies.</P>

        <P>When Federal, State and local public health laboratories voluntarily join the LRN, they assume specific responsibilities and are required to provide information to the LRN Program Office at CDC. Each laboratory must submit and maintain complete information regarding the testing capabilities of the laboratory. Biennially, laboratories are required to review, verify and update their testing capability information. Complete testing capability information is required in<PRTPAGE P="307"/>order for the LRN Program Office to determine the ability of the Network to respond to a biological or chemical threat event. The sensitivity of all information associated with the LRN requires the LRN Program Office to obtain personal information about all individuals accessing the LRN Web site. In addition, the LRN Program Office must be able to contact all laboratory personnel during an event so each laboratory staff member that obtains access to the restricted LRN Web site must provide his or her contact information to the LRN Program Office.</P>
        <P>As a requirement of membership, LRN Laboratories must report all biological and chemical testing results to the LRN Program at CDC using a CDC developed software tool called the LRN Results Messenger. This information is essential for surveillance of anomalies, to support response to an event that may involve multiple agencies and to manage limited resources. LRN Laboratories must also participate in and report results for Proficiency Testing Challenges or Validation Studies. LRN Laboratories participate in multiple Proficiency Testing Challenges, Exercises and/or Validation Studies every year consisting of five to 500 simulated samples provided by the LRN Program Office. It is necessary to conduct such challenges in order to verify the testing capability of the LRN Laboratories.</P>
        <P>The rarity of biological or chemical agents perceived to be of bioterrorism concern prevent some LRN Laboratories from maintaining proficiency as a result of day-to-day testing. Simulated samples are therefore distributed to ensure proficiency across the LRN. The results obtained from testing these simulated samples must also be entered into Results Messenger for evaluation by the LRN Program Office.</P>
        <P>During a surge event resulting from a bioterrorism or chemical terrorism attack, LRN Laboratories are also required to submit all testing results using LRN Results Messenger. The LRN Program Office requires these results in order to track the progression of a bioterrorism event and respond in the most efficient and effective way possible and for data sharing with other Federal partners involved in the response. The number of samples tested during a response to a possible event could range from 10,000 to more than 500,000 samples depending on the length and breadth of the event. Since there is potentially a large range in the number of samples for a surge event, CDC estimates the annualized burden for this event will be 2,250,000 hours or 625 responses per respondent.</P>
        <P>Semiannually the LRN Program Office may conduct a Special Data Call to obtain additional information from LRN Member Laboratories in regards to biological or chemical terrorism preparedness. Special Data Calls are conducted using the LRN Web site. There is no cost to the respondents other than their time.</P>
        <GPOTABLE CDEF="s125,r125,12,12,12,12" COLS="6" OPTS="L2,i1">
          <TTITLE>Estimated Annualized Burden Hours</TTITLE>
          <BOXHD>
            <CHED H="1">Type of respondents</CHED>
            <CHED H="1">Form name</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 per</LI>
              <LI>response</LI>
              <LI>(in hrs)</LI>
            </CHED>
            <CHED H="1">Total<LI>burden</LI>
              <LI>(in hrs)</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Public Health Laboratories</ENT>
            <ENT>Biennial Requalification</ENT>
            <ENT>150</ENT>
            <ENT>1</ENT>
            <ENT>2</ENT>
            <ENT>300</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Public Health Laboratories</ENT>
            <ENT>General Surveillance Testing Results</ENT>
            <ENT>150</ENT>
            <ENT>25</ENT>
            <ENT>24</ENT>
            <ENT>90,000</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Public Health Laboratories</ENT>
            <ENT>Proficiency Testing/Validation Testing Results</ENT>
            <ENT>150</ENT>
            <ENT>5</ENT>
            <ENT>56</ENT>
            <ENT>42,000</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Public Health Laboratories</ENT>
            <ENT>Surge Event Testing Results</ENT>
            <ENT>150</ENT>
            <ENT>625</ENT>
            <ENT>24</ENT>
            <ENT>2,250,000</ENT>
          </ROW>
          <ROW RUL="n,n,s">
            <ENT I="01">Public Health Laboratories</ENT>
            <ENT>Special Data Call</ENT>
            <ENT>150</ENT>
            <ENT>10</ENT>
            <ENT>2</ENT>
            <ENT>3,000</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Total</ENT>
            <ENT/>
            <ENT/>
            <ENT/>
            <ENT/>
            <ENT>2,385,300</ENT>
          </ROW>
        </GPOTABLE>
        <SIG>
          <DATED>Dated: December 20, 2012.</DATED>
          <NAME>Ron Otten,</NAME>
          <TITLE>Director, Office of Science Integrity, Office of the Associate Director for Science, Office of the Director, Centers for Disease Control and Prevention.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31182 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4163-18-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Centers for Disease Control and Prevention</SUBAGY>
        <DEPDOC>[30 Day-13-0696]</DEPDOC>
        <SUBJECT>Agency Forms Undergoing Paperwork Reduction Act Review</SUBJECT>

        <P>The Centers for Disease Control and Prevention (CDC) publishes a list of information collection requests under review by the Office of Management and Budget (OMB) in compliance with the Paperwork Reduction Act (44 U.S.C. Chapter 35). To request a copy of these requests, call (404) 639-7570 or send an email to<E T="03">omb@cdc.gov.</E>Send written comments to CDC Desk Officer, Office of Management and Budget, Washington, DC 20503 or by fax to (202) 395-5806. Written comments should be received within 30 days of this notice.</P>
        <HD SOURCE="HD1">Proposed Project</HD>
        <P>National HIV Prevention Program Monitoring and Evaluation (NHM&amp;E) (OMB 0920-0696, Expiration 08/31/2013)—Revision—National Center for HIV/AIDS, Viral Hepatitis, STD, and TB Prevention (NCHHSTP), Centers for Disease Control and Prevention (CDC).</P>
        <HD SOURCE="HD2">Background and Brief Description</HD>
        <P>CDC is requesting a 3-year approval for revision to the previously approved project.</P>
        <P>The purpose of this revision is to continue collecting standardized HIV prevention program evaluation data from health departments and community-based organizations (CBOs) who receive federal funds for HIV prevention activities. Grantees have the option of key-entering or uploading data to a CDC-provided web-based software application (EvaluationWeb®).</P>

        <P>The following changes have occurred since project 0920-0696 has been implemented:(1) The previous reporting system (PEMS) has been replaced by a more efficient reporting software. (2) Many data variables that were previously required or optional but reported have been deleted in order to reduce data reporting burden on grantees. Other variables have been added or modified to adapt to changes in HIV prevention and the National HIV/AIDS Strategic Plan. (3) reporting has been changed from quarterly to semiannual. (4) the number of grantees has changed as new FOAs were awarded.<PRTPAGE P="308"/>
        </P>
        <P>The evaluation and reporting process is necessary to ensure that CDC receives standardized, accurate, thorough evaluation data from both health department and CBO grantees. For these reasons, CDC developed standardized NHM&amp;E variables through extensive consultation with representatives from health departments, CBOs, and national partners (e.g., The National Alliance of State and Territorial AIDS Directors, Urban Coalition of HIV/AIDS Prevention Services, and National Minority AIDS Council).</P>
        <P>CDC requires CBOs and health departments who receive federal funds for HIV prevention to report non-identifying, client-level and aggregate-level, standardized evaluation data to: (1) Accurately determine the extent to which HIV prevention efforts are carried out, what types of agencies are providing services, what resources are allocated to those services, to whom services are being provided, and how these efforts have contributed to a reduction in HIV transmission; (2) improve ease of reporting to better meet these data needs; and (3) be accountable to stakeholders by informing them of HIV prevention activities and use of funds in HIV prevention nationwide.</P>
        <P>CDC HIV prevention program grantees will collect, enter or upload, and report agency-identifying information, budget data, intervention information, and client demographics and behavioral risk characteristics with an estimate of 200,846 burden hours. Data collection will include searching existing data sources, gathering and maintaining data, document compilation, review of data, and data entry or upload into the web-based system.</P>
        <P>There are no additional costs to respondents other than their time. The total estimated annual burden hours are 206,226.</P>
        <GPOTABLE CDEF="s125,r125,12,12,12" COLS="5" OPTS="L2,i1">
          <TTITLE>Estimated Annualized Burden Hours</TTITLE>
          <BOXHD>
            <CHED H="1">Type of respondents</CHED>
            <CHED H="1">Form name</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 per</LI>
              <LI>response</LI>
              <LI>(in hours)</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Health jurisdictions</ENT>
            <ENT>Agency Data</ENT>
            <ENT>69</ENT>
            <ENT>2</ENT>
            <ENT>1377</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>HE/RR Data</ENT>
            <ENT>69</ENT>
            <ENT>2</ENT>
            <ENT>67</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>HIV Testing Data</ENT>
            <ENT>69</ENT>
            <ENT>2</ENT>
            <ENT>1,229</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>NEM&amp;E Data Training</ENT>
            <ENT>69</ENT>
            <ENT>2</ENT>
            <ENT>52</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Community-based Organizations</ENT>
            <ENT>Agency Data</ENT>
            <ENT>200</ENT>
            <ENT>2</ENT>
            <ENT>30/60</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>HE/RR Data</ENT>
            <ENT>200</ENT>
            <ENT>2</ENT>
            <ENT>20</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT>NHM&amp;E Data Training</ENT>
            <ENT>200</ENT>
            <ENT>2</ENT>
            <ENT>20</ENT>
          </ROW>
        </GPOTABLE>
        <SIG>
          <DATED>Dated: December 27, 2012.</DATED>
          <NAME>Ron A. Otten,</NAME>
          <TITLE>Director, Office of Scientific Integrity (OSI), Office of the Associate Director for Science (OADS), Office of the Director, Centers for Disease Control and Prevention.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31599 Filed 1-2-13; 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 &amp; Medicaid Services</SUBAGY>
        <DEPDOC>[CMS-3278-NC]</DEPDOC>
        <SUBJECT>Medicare Program; Request for Information on Hospital and Vendor Readiness for Electronic Health Records Hospital Inpatient Quality Data Reporting</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Centers for Medicare &amp; Medicaid Services (CMS), HHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Request for information.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This document is a request for information from hospitals, electronic health record (EHR) vendors, and other interested parties regarding hospital readiness beginning calendar year 2014 discharges to electronically report certain patient-level data under the Hospital Inpatient Quality Reporting (IQR) Program using the Quality Reporting Document Architecture (QRDA) Category I.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The information solicited in this document must be received at the address provided below, no later than 5 p.m. eastern standard time (e.s.t.) on January 22, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>In commenting, refer to file code CMS-3278-NC. Because of staff and resource limitations, we cannot accept comments by facsimile (FAX) transmission.</P>
          <P>You may submit comments in one of four ways (please choose only one of the ways listed):</P>
          <P>1.<E T="03">Electronically.</E>You may submit electronic comments on this regulation to<E T="03">http://www.regulations.gov.</E>Follow the “Submit a comment” instructions.</P>
          <P>2.<E T="03">By regular mail.</E>You may mail written comments to the following address only: Centers for Medicare &amp; Medicaid Services, Department of Health and Human Services, Attention: CMS-3278-NC, P.O. Box 8013, Baltimore, MD 21244-8013.</P>
          <P>Please allow sufficient time for mailed comments to be received before the close of the comment period.</P>
          <P>3.<E T="03">By express or overnight mail.</E>You may send written comments to the following address only: Centers for Medicare &amp; Medicaid Services, Department of Health and Human Services, Attention: CMS-3278-NC, Mail Stop C4-26-05, 7500 Security Boulevard, Baltimore, MD 21244-1850.</P>
          <P>4.<E T="03">By hand or courier.</E>Alternatively, you may deliver (by hand or courier) your written comments ONLY to the following addresses:</P>
          <P>a. For delivery in Washington, DC—Centers for Medicare &amp; Medicaid Services, Department of Health and Human Services, Room 445-G, Hubert H. Humphrey Building, 200 Independence Avenue SW., Washington, DC 20201.</P>
          <P>(Because access to the interior of the Hubert H. Humphrey Building is not readily available to persons without Federal government identification, commenters are encouraged to leave their comments in the CMS drop slots located in the main lobby of the building. A stamp-in clock is available for persons wishing to retain a proof of filing by stamping in and retaining an extra copy of the comments being filed.)</P>
          <P>b. For delivery in Baltimore, MD—Centers for Medicare &amp; Medicaid Services, Department of Health and Human Services, 7500 Security Boulevard, Baltimore, MD 21244-1850.</P>
          <P>If you intend to deliver your comments to the Baltimore address, call telephone number (410) 786-9994 in advance to schedule your arrival with one of our staff members.</P>

          <P>Comments erroneously mailed to the addresses indicated as appropriate for hand or courier delivery may be delayed and received after the comment period.<PRTPAGE P="309"/>
          </P>

          <P>For information on viewing public comments, see the beginning of the<E T="02">SUPPLEMENTARY INFORMATION</E>section.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Maria Harr, (410) 786-6710.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <P SOURCE="NPAR">
          <E T="03">Inspection of Public Comments:</E>All comments received before the close of the comment period are available for viewing by the public, including any personally identifiable or confidential business information that is included in a comment. We post all comments received before the close of the comment period on the following Web site as soon as possible after they have been received:<E T="03">http://www.regulations.gov.</E>Follow the search instructions on that Web site to view public comments.</P>
        <P>Comments received timely will also be available for public inspection as they are received, generally beginning approximately 3 weeks after publication of a document, at the headquarters of the Centers for Medicare &amp; Medicaid Services, 7500 Security Boulevard, Baltimore, Maryland 21244, Monday through Friday of each week from 8:30 a.m. to 4 p.m. To schedule an appointment to view public comments, phone 1-800-743-3951.</P>
        <HD SOURCE="HD1">I. Background</HD>
        <P>We are interested in increasing efficiency and reducing the burden associated with hospital collection and submission of patient-level data on clinical quality measures (CQMs) and are exploring ways that hospitals might be able to report data on a subset of Hospital Inpatient Quality Reporting (IQR) Program measures specified under section 1886(b)(3)(B)(viii) of the Social Security Act (the Act) using the same certified electronic health record technology (CEHRT) that is used for reporting under the Electronic Health Record (EHR) Incentive Program as authorized by section 4102 of the American Recovery and Reinvestment Act of 2009 (ARRA). The goals of aligning quality measurement and reporting among our quality reporting programs are all of the following:</P>
        <P>• Streamline our quality reporting programs through automatic collection and reporting of data on CQMs using CEHRT.</P>
        <P>• Reduce burden to hospitals by allowing them to use EHRs to submit data on CQMs that are adopted for both the Hospital IQR Program and the EHR Incentive Program.</P>
        <P>• Develop a single set of electronic specifications for CQMs adopted under multiple quality reporting programs.</P>
        <P>• Support quality care improvement.</P>
        <P>• Adopt data standards to facilitate hospitals' capturing, transmitting, and formatting data elements consistently and clearly.</P>
        <P>The Health Information Technology for Economic and Clinical Health (HITECH) Act, part of the American Recovery and Reinvestment Act of 2009 (ARRA, Pub. L. 111-5), authorized Medicare and Medicaid incentive payments to eligible professionals and eligible hospitals when they adopt and meaningfully use CEHRT, as well as payment adjustments under Medicare beginning in 2015 for failure to demonstrate meaningful use. We have promulgated regulations establishing the criteria for Stage 1 and Stage 2 of meaningful use. More than 120,000 eligible health care professionals and more than 3,300 hospitals have qualified to participate in the program and receive an incentive payment since it began in January 2011.</P>
        <P>The EHR Incentive Program Stage 2 final rule (77 FR 53968) outlines our commitment to aligning quality measurement and reporting programs, including the Hospital IQR program, the Physician Quality Reporting System (PQRS), the Children's Health Insurance Program (CHIP), and the Pioneer Accountable Care Organization (ACO) Model. The automatic collection and reporting of data elements for many measures through CEHRT is expected to greatly simplify reporting for various quality reporting programs. We envisage that hospitals will be able to switch primarily to EHR-based reporting of clinical quality data for many measures that are currently manually chart-abstracted and submitted to CMS for the Hospital IQR Program.</P>
        <P>The Hospital IQR Program (<E T="03">http://www.qualitynet.org/dcs/ContentServer?cid=1138115987129&amp;pagename=QnetPublic%2FPage%2FQnetTier2&amp;c=Page</E>), which is authorized by section 1886(b)(3)(B)(viii) of the Act, is intended to equip patients with hospital quality of care information to make informed decisions about healthcare options and is also intended to encourage hospitals and clinicians to improve the quality of inpatient care provided to all patients. Hospital IQR Program data is available to consumers on the Hospital Compare Web site (<E T="03">http://www.hospitalcompare.hhs.gov/</E>).</P>
        <P>Under the Hospital IQR Program, subsection (d) hospitals report data on selected quality measures to CMS. In selecting measures for the program, we strive to be consistent with the priorities identified in the National Quality Strategy. Subsection (d) hospitals report quality measures of process, structure, outcomes, patient perspectives on care, and efficiency that relate to services furnished in an inpatient acute care hospital setting in order to receive the full annual payment update (APU). Sections 1886(b)(3)(B)(viii)(I) of the Act states that the applicable percentage increase, for FY 2007 and each subsequent fiscal year, shall be reduced by 2.0 percentage points (or, beginning with FY 2015, by one-quarter of such applicable percentage increase (determined without regard to sections 1886(b)(3)(B)(ix), (xi), or (xii) of the Act)) for any subsection (d) hospital that does not submit quality data in a form and manner, and at a time, specified by the Secretary.</P>
        <HD SOURCE="HD1">II. Solicitation for Information</HD>
        <P>We are soliciting information from hospitals, EHR vendors, and other interested parties on a variety of subject matters.</P>
        <P>The following questions are intended for all hospitals, EHR vendors, and other interested parties:</P>
        <P>• How do hospitals and vendors perceive the alignment of EHR-based reporting and hospital quality reporting programs? What are the foreseen benefits and challenges?</P>
        <P>• Do hospitals and vendors envision being able to meet the criteria for reporting clinical quality measures electronically for the EHR Incentive Program as set forth in the EHR Incentive Program—Stage 2 final rule (77 FR  53968) and any related guidance issued? If not, what are the issues in meeting the requirements and what additional information is needed?</P>
        <P>We are specifically soliciting comments from hospitals and other interested parties on the following topics:</P>
        <P>• Is the hospital planning to adopt EHR technology that has been certified to the 2014 Edition EHR certification criteria during or before calendar year (CY) 2014?</P>
        <P>• Is the hospital aware of the payment adjustments authorized under the HITECH Act beginning in FY 2015 for failing to demonstrate meaningful use under the Medicare EHR Incentive Program?</P>
        <P>• Is the hospital planning to<E T="03">electronically</E>report CQM data—specifically venous thromboembolism (VTE) and stroke (STK) and emergency department (ED) measures—under the Medicare EHR Incentive Program in FY 2014?</P>

        <P>• Is the hospital already participating in or planning to participate in the 2013 Medicare EHR Incentive Program Electronic Reporting Pilot for Eligible Hospitals and Critical Access Hospitals<PRTPAGE P="310"/>(CAHs) (“Pilot”)? The pilot provides eligible hospitals and CAHs with an opportunity to meet the CQM reporting requirements of the Medicare EHR Incentive Program through electronic submission of CQM data. The pilot is a voluntary electronic reporting method used to satisfy the CQM reporting requirements for the Medicare EHR Incentive Program. If not, what barriers prevent the hospital from participating?</P>
        <P>• Does the hospital plan to report data leveraging any state health information exchange (HIE) initiative?</P>
        <P>• Does the hospital plan to report data leveraging the Nationwide Health Information Network (NwHIN) Exchange, which is now the eHealth Exchange?</P>
        <P>• Will the hospital use a third party to report quality data required under the EHR Incentive Program?</P>
        <P>• Are there operational challenges to electronically reporting quality data? If so, does the hospital have mitigation plans to overcome these challenges?</P>
        <P>• Has the hospital chief information officer (CIO) and/or chief operating officer (COO) prioritized electronically reporting quality data over the next 3 years (2013 through 2015)?</P>
        <P>• Are there any evaluation or data validation methodologies that have been used by the hospital to assess the accuracy and reliability of clinical process of care quality data using QRDA category I standards?</P>
        <P>• What barriers and opportunities would be created by including sampling criteria for electronically reported measures under the EHR Incentive Program?</P>
        <P>We are specifically soliciting comments from EHR vendors and other interested parties in the following areas:</P>
        <P>• Is the EHR vendor's technology currently certified under the Office of the National Coordinator for Health Information Technology (ONC) Health Information Technology (HIT) Certification Program to the 2001 Edition EHR Certification Criteria? Does the vendor intend to have its EHR technology certified to the 2014 Edition EHR Certification Criteria? If so, when?</P>
        <P>• What are the top three operational challenges facing EHR vendors over the next 3 years (2013 through 2015)? Of those identified, does the EHR vendor have mitigation plans to overcome these challenges?</P>
        <P>• Are there any evaluation or data validation methodologies that have been used to assess the accuracy and reliability of clinical process of care quality data using QRDA category I standards?</P>
        <P>• Have vendors included random sampling functionalities in currently certified systems? If yes, what guidance for random sampling has been employed, if any? If no, what barriers are presented by adding this functionality to your currently certified systems?</P>
        <HD SOURCE="HD1">III. Response to Comments</HD>

        <P>Because of the large number of public comments we normally receive on<E T="04">Federal Register</E>documents, we are not able to acknowledge or respond to them individually. We will consider all comments we receive by the date and time specified in the<E T="02">DATES</E>section of this request for information, and, when we proceed with a subsequent document, we will respond to the comments in that document.</P>
        
        <EXTRACT>
          <FP>(Catalog of Federal Domestic Assistance Program No. 93.773, Medicare—Hospital Insurance; and Program No. 93.774, Medicare—Supplementary Medical Insurance Program)</FP>
        </EXTRACT>
        <SIG>
          <DATED>Dated:<E T="03">December 21, 2012.</E>
          </DATED>
          <NAME>Marilyn Tavenner,</NAME>
          <TITLE>Acting Administrator, Centers for Medicare &amp; Medicaid Services.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31582 Filed 12-28-12; 11:15 am]</FRDOC>
      <BILCOD>BILLING CODE 4120-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Food and Drug Administration</SUBAGY>
        <DEPDOC>[Docket No. FDA-2012-D-1256]</DEPDOC>
        <SUBJECT>Draft Revision of Guidance for Industry on Providing Regulatory Submissions in Electronic Format—Certain Human Pharmaceutical Product Applications and Related Submissions Using the Electronic Common Technical Document Specifications; Availability</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Food and Drug Administration, HHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Food and Drug Administration (FDA) is announcing the availability of draft guidance for industry entitled “Providing Regulatory Submissions in Electronic Format—Certain Human Pharmaceutical Product Applications and Related Submissions Using the eCTD Specifications.” The draft guidance announced in this notice is being issued in accordance with the Food and Drug Administration Safety and Innovation Act (FDASIA) which amended the Federal Food, Drug, and Cosmetic Act (the FD&amp;C Act) to require that certain submissions under the FD&amp;C Act and Public Health Service Act (PHS Act) be submitted in electronic format, beginning no earlier than 2 years after publication of the final version of the draft guidance. The draft guidance describes how FDA plans to implement the requirements for the electronic submission of applications for certain human pharmaceutical products and is being issued for public comment. In its final form, this document will also supersede the guidance titled “Guidance for Industry Providing Regulatory Submissions in Electronic Format—Human Pharmaceutical Product Applications and Related Submissions Using the eCTD Specifications” that was issued in October 2005 and revised in April 2006 and June 2008.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Although you can comment on any guidance at any time (see 21 CFR 10.115(g)(5)), to ensure that the Agency considers your comment on this draft guidance before it begins work on the final version of the guidance, submit either electronic or written comments on the draft guidance by March 4, 2013.</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, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, Rm. 2201, Silver Spring, MD 20993-0002 or the Office of Communication, Outreach and Development (HFM-40), Center for Biologics Evaluation and Research, 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 guidance 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/>

          <FP SOURCE="FP-1">Virginia Hussong, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 22, Rm. 1161, Silver Spring, MD 20993, email:<E T="03">virginia.hussong@fda.hhs.gov;</E>
          </FP>
          
          <FP>or</FP>
          
          <FP SOURCE="FP-1">Stephen Ripley, Center for Biologics Evaluation and Research (HFM-17), Food and Drug Administration, 1401 Rockville Pike, Suite 200N, Rockville, MD 20852, 301-827-6210.</FP>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background</HD>

        <P>The electronic Common Technical Document (eCTD) is an International Conference on Harmonisation (ICH) standard based on specifications<PRTPAGE P="311"/>developed by ICH and its member parties. FDA's Center for Drug Evaluation and Research (CDER) and Center for Biologics Evaluation and Research (CBER) have been receiving submissions in the eCTD format since 2003, and the eCTD has been the recommended format for electronic submissions to CDER and CBER since January 1, 2008. The majority of new electronic submissions are now received in eCTD format.</P>
        <P>FDASIA (Pub. L. 112-144, 126 Stat. 993 (2012)), signed by the President on July 9, 2012, amended the FD&amp;C Act to add section 745A, titled “Electronic Format for Submissions.” Section 745A(a)(1) of the FD&amp;C Act requires that submissions under section 505(b), (i), or (j) of the FD&amp;C Act, and submissions under sections 351(a) or (k) of the PHS Act, be submitted to FDA in electronic format no earlier than 24 months after FDA issues the final guidance described in this section.</P>
        <P>In accordance with section 745A(a)(1) of the FD&amp;C Act, FDA is issuing this draft guidance, announcing its determination that submission types identified in this draft guidance must be submitted electronically (except for submissions that are exempted), in a format that FDA can process, review, and archive. Currently, the Agency can process, review, and archive electronic submissions made using the eCTD version 3.2.2 specifications. Requirements for electronic submission will be phased in according to the following schedule: (1) 24 months after publication of the final version of this draft revised guidance, the requirements will apply to new drug application (NDA), abbreviated new drug application (ANDA), and biologics license application (BLA) submissions and (2) 36 months after publication of the final guidance, the requirements will apply to investigational new drug application (IND) submissions. Section 745A(a) of the FD&amp;C Act does not apply to master files and advertising and promotional labeling submissions. However, FDA accepts and strongly encourages the submission of master files and advertising and promotional labeling materials electronically, as described in the draft guidance.</P>

        <P>In Section 745A(a), Congress granted explicit authorization to FDA to implement the statutory electronic submission requirements by specifying the format for such submissions in guidance. To the extent that the draft guidance provides such requirements under section 745A(a) of the FD&amp;C Act, indicated by the use of the words<E T="03">must</E>or<E T="03">required,</E>it is not subject to the usual restrictions in FDA's good guidance practice (GGP) regulations, such as the requirement that guidances not establish legally enforceable responsibilities. See 21 CFR 10.115(d).</P>

        <P>At the same time, the draft guidance also provides guidance on FDA's interpretation of the statutory electronic submission requirement and the Agency's current thinking on the best means for implementing other aspects of the electronic submission program. Therefore, to the extent that the draft guidance includes provisions that are not part of the requirements under section 745A(a), it is being issued in accordance with FDA's GGP regulation (21 CFR 10.115). Such parts of the draft guidance, when finalized, will represent the Agency's current thinking on this topic, and do not create or confer any rights for or on any person and do not operate to bind FDA or the public. You can use an alternative approach for these recommendations if such an approach would satisfy the requirements of the applicable statutes and regulations. The use of the word<E T="03">should</E>in the draft guidance means that something is suggested or recommended, but not required. Accordingly, the final guidance will contain both binding and nonbinding provisions.</P>
        <HD SOURCE="HD1">II. Paperwork Reduction Act of 1995</HD>
        <P>The draft guidance refers to collections of information that are subject to review by the Office of Management and Budget (OMB) under the Paperwork Reduction Act of 1995 (the PRA) (44 U.S.C. 3501-3520). The draft guidance pertains to sponsors and applicants making regulatory submissions to FDA in electronic format for NDAs, ANDAs, BLAs, INDs, master files, and advertising and promotional labeling. The information collection discussed in the draft guidance is contained in our IND regulations (21 CFR part 312) and approved under OMB control number 0910-0014, our NDA regulations (including ANDAs) (21 CFR part 314) and approved under OMB control number 0910-0001, and our BLA regulations (21 CFR part 601) and approved under OMB control number 0910-0338.</P>
        <P>Sponsors and applicants have been submitting NDAs, ANDAs, BLAs, and INDs electronically since 2003, and the majority of these submissions are already received in electronic format. Under FDASIA, sponsors and applicants will be required to make all of these submissions electronically. These requirements will be phased in over 2 and 3 year periods after the issuance of the final guidance.</P>
        <P>There may be new costs, including capital costs or operating and maintenance costs, which would result from the requirements under FDASIA and the final guidance, because some sponsors and applicants would have to convert from paper-based submissions to electronic submissions. In accordance with the PRA, prior to publication of the final guidance document, FDA intends to solicit public comment and obtain OMB approval for any costs that are new or that would represent material modifications to these previously approved collections of information found in FDA regulations.</P>
        <HD SOURCE="HD1">III. Comments</HD>
        <P>Interested persons may submit either electronic comments to<E T="03">http://www.regulations.gov</E>or written comments regarding this document to the Division of Dockets Management (see<E T="02">ADDRESSES</E>). It is only necessary to send one set of 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, and will be posted to the docket at<E T="03">http://www.regulations.gov.</E>
        </P>
        <HD SOURCE="HD1">IV. Electronic Access</HD>

        <P>Persons with access to the Internet may obtain the document at either<E T="03">http://www.fda.gov/Drugs/DevelopmentApprovalProcess/FormsSubmissionRequirements/ElectronicSubmissions/ucm253101.htm,  http://www.regulations.gov,</E>or<E T="03">http://www.fda.gov/BiologicsBloodVaccines/GuidanceComplianceRegulatoryInformation/Guidances/default.htm.</E>
        </P>

        <P>Persons with access to the Internet may obtain the document at either<E T="03">http://www.fda.gov/Drugs/DevelopmentApprovalProcess/FormsSubmissionRequirements/ElectronicSubmissions/ucm253101.htm, http://www.regulations.gov,</E>or<E T="03">http://www.fda.gov/BiologicsBloodVaccines/GuidanceComplianceRegulatoryInformation/Guidances/default.htm.</E>
        </P>
        <SIG>
          <DATED>Dated: December 27, 2012.</DATED>
          <NAME>Leslie Kux,</NAME>
          <TITLE>Assistant Commissioner for Policy.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31577 Filed 12-31-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4160-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="312"/>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>National Institutes of Health</SUBAGY>
        <SUBJECT>National Cancer Institute; Notice of Closed Meetings</SUBJECT>
        <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meetings.</P>
        <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
        
        <EXTRACT>
          <P>
            <E T="03">Name of Committee:</E>National Cancer Institute Special Emphasis Panel, U.S.—China Program for Biomedical Collaborative Research (R01).</P>
          <P>
            <E T="03">Date:</E>January 28, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 5:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Hilton Washington/Rockville, 1750 Rockville Pike, Rockville, MD 20852.</P>
          <P>
            <E T="03">Contact Person:</E>Zhiqiang Zou, MD, Ph.D., Scientific Review Officer, Special Review and Logistics Branch,  Division of Extramural Activities,  National Cancer Institute, NIH, 6116 Executive Blvd., Room 8055A, MSC 8329, Bethesda, MD 20892, 301-402-9415,<E T="03">zouzhiq@mail.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>National Cancer Institute Special Emphasis Panel, NCI SPORE III.</P>
          <P>
            <E T="03">Date:</E>February 6-7, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 5:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Bethesda North Marriott Hotel &amp; Conference Center, Montgomery County Conference Center Facility, 5701 Marinelli Road, North Bethesda, MD 20852.</P>
          <P>
            <E T="03">Contact Person:</E>David G. Ransom, Ph.D., Scientific Review Officer, Research Programs Review Branch, Division of Extramural Activities, National Cancer Institute, NIH, 6116 Executive Blvd., Room 8133, Bethesda, MD 20892-8328, 301-451-4757,<E T="03">david.ransom@nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>National Cancer Institute Special Emphasis Panel, NCI SPORE II.</P>
          <P>
            <E T="03">Date:</E>February 6-7, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 5:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Bethesda North Marriott Hotel &amp; Conference Center, Montgomery County Conference Center Facility, 5701 Marinelli Road, North Bethesda, MD 20852.</P>
          <P>
            <E T="03">Contact Person:</E>Wlodek Lopaczynski, MD, Ph.D.,  Scientific Review Officer, Research Programs Review Branch, Division of Extramural Activities, National Cancer Institute, NIH, 6116 Executive Blvd. Room 8131, Bethesda, MD 20892, 301-594-1402,<E T="03">lopacw@mail.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>National Cancer Institute Special Emphasis Panel, NCI Program Project Meeting III.</P>
          <P>
            <E T="03">Date:</E>February 19-20, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 5:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Hilton Washington/Rockville, 1750 Rockville Pike, Rockville, MD 20852.</P>
          <P>
            <E T="03">Contact Person:</E>Jeannette F. Korczak, Ph.D., Scientific Review Officer, Research Programs Review Branch, Division of Extramural Activities, National Cancer Institute, NIH, 6116 Executive Blvd., Room 8115, Bethesda, MD 20892, 301-496-9767,<E T="03">korczakj@mail.nih.gov.</E>
          </P>
          
          <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.392, Cancer Construction; 93.393, Cancer Cause and Prevention Research; 93.394, Cancer Detection and Diagnosis Research; 93.395, Cancer Treatment Research; 93.396, Cancer Biology Research; 93.397, Cancer Centers Support; 93.398, Cancer Research Manpower; 93.399, Cancer Control, National Institutes of Health, HHS)</FP>
        </EXTRACT>
        <SIG>
          <DATED>Dated: December 27, 2012.</DATED>
          <NAME>Melanie J. Gray,</NAME>
          <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31551 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4140-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>National Institutes of Health</SUBAGY>
        <SUBJECT>National Cancer Institute; Notice of Meeting</SUBJECT>
        <P>Pursuant to section 10(a) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of a meeting of the National Cancer Institute Clinical Trials and Translational Research Advisory Committee.</P>
        <P>The meeting will be open to the public, with attendance limited to space available. Individuals who plan to attend and need special assistance, such as sign language interpretation or other reasonable accommodations, should notify the Contact Person listed below in advance of the meeting.</P>
        
        <EXTRACT>
          <P>
            <E T="03">Name of Committee:</E>National Cancer Institute Clinical Trials and Translational Research Advisory Committee.</P>
          <P>
            <E T="03">Date:</E>March 13, 2013.</P>
          <P>
            <E T="03">Time:</E>9:00 a.m. to 4:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>Strategic Discussion of NCI's Clinical and Translational Research Programs.</P>
          <P>
            <E T="03">Place:</E>National Institutes of Health, Building 31, C-Wing, 6th Floor, Conference Rooms 9 and 10, 31 Center Drive, Bethesda, MD 20892.</P>
          <P>
            <E T="03">Contact Person:</E>Sheila A. Prindiville, MD, MPH, Director, Coordinating Center for Clinical Trials, Office of the Director, National Cancer Institute, National Institutes of Health, 6120 Executive Blvd., 3rd Floor Suite, Bethesda, MD 20892, 301-451-5048,<E T="03">prindivs@mail.nih.gov.</E>
          </P>
          

          <P>Information is also available on the Institute's/Center's home page:<E T="03">http://deainfo.nci.nih.gov/advisory/ctac/ctac.htm,</E>where an agenda and any additional information for the meeting will be posted when available.</P>
          <P>Any interested person may file written comments with the committee by forwarding the statement to the Contact Person listed on this notice. The statement should include the name, address, telephone number and when applicable, the business or professional affiliation of the interested person.</P>
          
          <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.392, Cancer Construction; 93.393, Cancer Cause and Prevention Research; 93.394, Cancer Detection and Diagnosis Research; 93.395, Cancer Treatment Research; 93.396, Cancer Biology Research; 93.397, Cancer Centers Support; 93.398, Cancer Research Manpower; 93.399, Cancer Control, National Institutes of Health, HHS)</FP>
        </EXTRACT>
        <SIG>
          <DATED>Dated: December 27, 2012.</DATED>
          <NAME>Melanie J. Gray,</NAME>
          <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31550 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4140-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>National Institutes of Health</SUBAGY>
        <SUBJECT>Center for Scientific Review; Notice of Closed Meetings</SUBJECT>
        <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meetings.</P>
        <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
        
        <EXTRACT>
          <P>
            <E T="03">Name of Committee:</E>Integrative, Functional and Cognitive Neuroscience Integrated Review Group Neurotoxicology and Alcohol Study Section.</P>
          <P>
            <E T="03">Date:</E>February 4, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 6:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.<PRTPAGE P="313"/>
          </P>
          <P>
            <E T="03">Place:</E>Sheraton Delfina Santa Monica Hotel, 530 West Pico Boulevard, Santa Monica, CA 90405.</P>
          <P>
            <E T="03">Contact Person:</E>Christine Melchior, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 5176 MSC 7844, Bethesda, MD 20892, (301) 435-1713,<E T="03">melchioc@csr.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>Digestive, Kidney and Urological Systems Integrated Review Group Clinical, Integrative and Molecular Gastroenterology Study Section.</P>
          <P>
            <E T="03">Date:</E>February 4, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 7:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Residence Inn Bethesda, 7335 Wisconsin Avenue, Bethesda, MD 20814.</P>
          <P>
            <E T="03">Contact Person:</E>Mushtaq A. Khan, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 2176, MSC 7818, Bethesda, MD 20892,  301-435-1778,<E T="03">khanm@csr.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>Digestive, Kidney and Urological Systems Integrated Review Group, Pathobiology of Kidney Disease Study Section.</P>
          <P>
            <E T="03">Date:</E>February 4, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 7:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Hyatt Regency Bethesda, One Bethesda Metro Center, 7400 Wisconsin Avenue, Bethesda, MD 20814.</P>
          <P>
            <E T="03">Contact Person:</E>Atul Sahai, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 2188, MSC 7818, Bethesda, MD 20892, 301-435-1198,<E T="03">sahaia@csr.nih.gov</E>.</P>
          
          <P>
            <E T="03">Name of Committee:</E>Oncology 2—Translational Clinical Integrated Review Group, Developmental Therapeutics Study Section.</P>
          <P>
            <E T="03">Date:</E>February 4-5, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 6:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Sheraton La Jolla Hotel, 3299 Holiday Court, La Jolla, CA 92037.</P>
          <P>
            <E T="03">Contact Person:</E>Sharon K. Gubanich, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 6214, MSC 7804, Bethesda, MD 20892, (301) 408-9512,<E T="03">gubanics@csr.nih.gov</E>.</P>
          
          <P>
            <E T="03">Name of Committee:</E>Cell Biology Integrated Review Group, Molecular and Integrative Signal Transduction Study Section.</P>
          <P>
            <E T="03">Date:</E>February 4, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 5:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Embassy Suites Chevy Chase, 4300 Military Road  Northwest, Washington, DC 20015.</P>
          <P>
            <E T="03">Contact Person:</E>Raya Mandler, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 5134, MSC 7840, Bethesda, MD 20892, (301) 402-8228,<E T="03">rayam@csr.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>Oncology 2—Translational Clinical Integrated Review Group, Clinical Oncology Study Section.</P>
          <P>
            <E T="03">Date:</E>February 4, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 6:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Crowne Plaza Tyson's Corner, 1960 Chain Bridge Road, Mclean, VA 22102.</P>
          <P>
            <E T="03">Contact Person:</E>Malaya Chatterjee, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 6192, MSC 7804, Bethesda, MD 20892, 301-806-2515,<E T="03">chatterm@csr.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>Risk, Prevention and Health Behavior Integrated Review Group, Behavioral Medicine, Interventions and Outcomes Study Section.</P>
          <P>
            <E T="03">Date:</E>February 4-5, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 5:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Doubletree Guest Suites Santa Monica, 1707 Fourth Street, Santa Monica, CA 90401.</P>
          <P>
            <E T="03">Contact Person:</E>Lee S. Mann, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 3186, MSC 7848, Bethesda, MD 20892, 301-435-0677,<E T="03">mannl@csr.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>Cell Biology Integrated Review Group, Development—2 Study Section.</P>
          <P>
            <E T="03">Date:</E>February 4-5, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 5:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Embassy Suites at the Chevy Chase Pavilion, 4300 Military Road NW., Washington, DC 20015.</P>
          <P>
            <E T="03">Contact Person:</E>Rass M. Shayiq, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institute of Health, 6701 Rockledge Drive, Room 2182, MSC 7818, Bethesda, MD 20892, (301) 435-2359,<E T="03">shayiqr@csr.nih.gov</E>.</P>
          
          <P>
            <E T="03">Name of Committee:</E>Center for Scientific Review Special Emphasis Panel, RFA Panel: Investigations on Primary Immunodeficiency Diseases.</P>
          <P>
            <E T="03">Date:</E>February 4, 2013.</P>
          <P>
            <E T="03">Time:</E>12:00 p.m. to 3:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (Virtual Meeting).</P>
          <P>
            <E T="03">Contact Person:</E>Scott Jakes, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 4198, MSC 7812, Bethesda, MD 20892, 301-495-1506,<E T="03">jakesse@mail.nih.gov.</E>
          </P>
          
          <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.306, Comparative Medicine; 93.333, Clinical Research, 93.306, 93.333, 93.337, 93.393-93.396, 93.837-93.844, 93.846-93.878, 93.892, 93.893, National Institutes of Health, HHS)</FP>
        </EXTRACT>
        <SIG>
          <DATED>Dated: December 27, 2012.</DATED>
          <NAME>David Clary,</NAME>
          <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31553 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4140-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>National Institutes of Health</SUBAGY>
        <SUBJECT>National Cancer Institute; Notice of Meeting</SUBJECT>

        <P>Pursuant to section 10(a) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of a meeting of the National Cancer Institute Board of Scientific Advisors<E T="03">ad hoc</E>Subcommittee on HIV and AIDS Malignancy.</P>
        <P>The meeting will be open to the public, with attendance limited to space available. Individuals who plan to attend and need special assistance, such as sign language interpretation or other reasonable accommodations, should notify the Contact Person listed below in advance of the meeting.</P>
        
        <EXTRACT>

          <P>Name of Committee: National Cancer Institute Board of Scientific Advisors<E T="03">Ad hoc</E>Subcommittee on HIV and AIDS Malignancy.</P>
          <P>Date: February 14, 2013.</P>
          <P>Time: 9:00 a.m. to 4:00 p.m.</P>
          <P>Agenda: Discussion of HIV and AIDS Malignancy.</P>
          <P>Place: National Institutes of Health, Natcher Building, Conference Room A, 45 Center Drive, Bethesda, MD 20892.</P>

          <P>Contact Person: Robert Yarchoan, MD, Director, HIV/AIDS Management Branch, NIH/NCI, Building 10, Room 10S255, 10 Center Drive, Bethesda, MD 20892-186, 301-496-0328,<E T="03">yarchoan@helix.nih.gov.</E>
          </P>
          <P>Any interested person may file written comments with the committee by forwarding the statement to the Contact Person listed on this notice. The statement should include the name, address, telephone number and when applicable, the business or professional affiliation of the interested person.</P>
          <P>In the interest of security, NIH has instituted stringent procedures for entrance onto the NIH campus. All visitor vehicles, including taxicabs, hotel, and airport shuttles will be inspected before being allowed on campus. Visitors will be asked to show one form of identification (for example, a government-issued photo ID, driver's license, or passport) and to state the purpose of their visit.</P>

          <P>Information is also available on the Institute's/Center's home page:<E T="03">http://deainfo.nci.nih.gov/advisory/bsa/bsa.htm,</E>where an agenda and any additional information for the meeting will be posted when available.</P>
          

          <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.392, Cancer Construction; 93.393, Cancer Cause and Prevention<PRTPAGE P="314"/>Research; 93.394, Cancer Detection and Diagnosis Research; 93.395, Cancer Treatment Research; 93.396, Cancer Biology Research; 93.397, Cancer Centers Support; 93.398, Cancer Research Manpower; 93.399, Cancer Control, National Institutes of Health, HHS)</FP>
        </EXTRACT>
        <SIG>
          <DATED>Dated: December 27, 2012.</DATED>
          <NAME>Melanie J. Gray,</NAME>
          <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31552 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4140-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>National Institutes of Health</SUBAGY>
        <SUBJECT>National Institute of Allergy and Infectious Diseases; Notice of Closed Meeting</SUBJECT>
        <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meeting.</P>
        <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
        
        <EXTRACT>
          <P>
            <E T="03">Name of Committee:</E>National Institute of Allergy and Infectious Diseases Special Emphasis Panel, “NIAID Investigator Initiated Program Applications (P01).”</P>
          <P>
            <E T="03">Date:</E>January 30, 2013.</P>
          <P>
            <E T="03">Time:</E>12:00 p.m. to 4:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>National Institutes of Health, 6700B Rockledge Drive, Bethesda, MD 20817, (Telephone Conference Call).</P>
          <P>
            <E T="03">Contact Person:</E>Nancy Vazquez-Maldonado, Ph.D., Scientific Review Officer, Scientific Review Program, DEA/NIAID/NIH/DHHS, 6700B Rockledge Drive, MSC-7616, Bethesda, MD 20892-7616, 301-496-3253,<E T="03">nvazquez@niaid.nih.gov.</E>
          </P>
          
          <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.855, Allergy, Immunology, and Transplantation Research; 93.856, Microbiology and Infectious Diseases Research, National Institutes of Health, HHS)</FP>
        </EXTRACT>
        <SIG>
          <DATED>Dated: December 27, 2012.</DATED>
          <NAME>David Clary,</NAME>
          <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31549 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4140-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Substance Abuse and Mental Health Services Administration</SUBAGY>
        <SUBJECT>Current List of Laboratories and Instrumented Initial Testing Facilities Which Meet Minimum Standards To Engage in Urine Drug Testing for Federal Agencies</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Substance Abuse and Mental Health Services Administration, HHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The Department of Health and Human Services (HHS) notifies Federal agencies of the Laboratories and Instrumented Initial Testing Facilities (IITF) currently certified to meet the standards of the Mandatory Guidelines for Federal Workplace Drug Testing Programs (Mandatory Guidelines). The Mandatory Guidelines were first published in the<E T="04">Federal Register</E>on April 11, 1988 (53 FR 11970), and subsequently revised in the<E T="04">Federal Register</E>on June 9, 1994 (59 FR 29908); September 30, 1997 (62 FR 51118); April 13, 2004 (69 FR 19644); November 25, 2008 (73 FR 71858); December 10, 2008 (73 FR 75122); and on April 30, 2010 (75 FR 22809).</P>

          <P>A notice listing all currently certified Laboratories and Instrumented Initial Testing Facilities (IITF) is published in the<E T="04">Federal Register</E>during the first week of each month. If any Laboratory/IITF's certification is suspended or revoked, the Laboratory/IITF will be omitted from subsequent lists until such time as it is restored to full certification under the Mandatory Guidelines.</P>
          <P>If any Laboratory/IITF has withdrawn from the HHS National Laboratory Certification Program (NLCP) during the past month, it will be listed at the end and will be omitted from the monthly listing thereafter.</P>
          <P>This notice is also available on the Internet at<E T="03">http://www.workplace.samhsa.gov</E>and<E T="03">http://www.drugfreeworkplace.gov.</E>
          </P>
        </SUM>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Mrs. Giselle Hersh, Division of Workplace Programs, SAMHSA/CSAP, Room 2-1042, One Choke Cherry Road, Rockville, Maryland 20857; 240-276-2600 (voice), 240-276-2610 (fax).</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The Mandatory Guidelines were initially developed in accordance with Executive Order 12564 and section 503 of Public Law 100-71. The “Mandatory Guidelines for Federal Workplace Drug Testing Programs”, as amended in the revisions listed above, requires strict standards that Laboratories and Instrumented Initial Testing Facilities (IITF) must meet in order to conduct drug and specimen validity tests on urine specimens for Federal agencies.</P>
        <P>To become certified, an applicant Laboratory/IITF must undergo three rounds of performance testing plus an on-site inspection. To maintain that certification, a Laboratory/IITF must participate in a quarterly performance testing program plus undergo periodic, on-site inspections.</P>
        <P>Laboratories and Instrumented Initial Testing Facilities (IITF) in the applicant stage of certification are not to be considered as meeting the minimum requirements described in the HHS Mandatory Guidelines. A Laboratory/IITF must have its letter of certification from HHS/SAMHSA (formerly: HHS/NIDA) which attests that it has met minimum standards.</P>
        <P>In accordance with the Mandatory Guidelines dated November 25, 2008 (73 FR 71858), the following Laboratories and Instrumented Initial Testing Facilities (IITF) meet the minimum standards to conduct drug and specimen validity tests on urine specimens:</P>
        <HD SOURCE="HD1">Instrumented Initial Testing Facilities (IITF)</HD>
        <P>None.</P>
        <HD SOURCE="HD2">Laboratories</HD>
        <FP SOURCE="FP-1">ACL Laboratories, 8901 W. Lincoln Ave., West Allis, WI 53227, 414-328-7840/800-877-7016, (Formerly: Bayshore Clinical Laboratory)</FP>
        <FP SOURCE="FP-1">ACM Medical Laboratory, Inc., 160 Elmgrove Park, Rochester, NY 14624, 585-429-2264</FP>
        <FP SOURCE="FP-1">Advanced Toxicology Network, 3560 Air Center Cove, Suite 101, Memphis, TN 38118, 901-794-5770/888-290-1150</FP>
        <FP SOURCE="FP-1">Aegis Analytical Laboratories, 345 Hill Ave., Nashville, TN 37210, 615-255-2400, (Formerly: Aegis Sciences Corporation, Aegis Analytical Laboratories, Inc.)</FP>
        <FP SOURCE="FP-1">Alere Toxicology Services, 1111 Newton St., Gretna, LA 70053, 504-361-8989/800-433-3823, (Formerly: Kroll Laboratory Specialists, Inc., Laboratory Specialists, Inc.)</FP>
        <FP SOURCE="FP-1">Alere Toxicology Services, 450 Southlake Blvd., Richmond, VA 23236, 804-378-9130, (Formerly: Kroll Laboratory Specialists, Inc., Scientific Testing Laboratories, Inc.; Kroll Scientific Testing Laboratories, Inc.)</FP>

        <FP SOURCE="FP-1">Baptist Medical Center-Toxicology Laboratory, 11401 I-30, Little Rock, AR 72209-7056, 501-202-2783, (Formerly: Forensic Toxicology Laboratory Baptist Medical Center)<PRTPAGE P="315"/>
        </FP>
        <FP SOURCE="FP-1">Clinical Reference Lab, 8433 Quivira Road, Lenexa, KS 66215-2802, 800-445-6917</FP>
        <FP SOURCE="FP-1">Doctors Laboratory, Inc., 2906 Julia Drive, Valdosta, GA 31602, 229-671-2281</FP>
        <FP SOURCE="FP-1">DrugScan, Inc., 200 Precision Road, Suite 200, Horsham, PA 19044, 800-235-4890</FP>
        <FP SOURCE="FP-1">ElSohly Laboratories, Inc., 5 Industrial Park Drive, Oxford, MS 38655, 662-236-2609</FP>
        <FP SOURCE="FP-1">Gamma-Dynacare Medical Laboratories,* a Division of the Gamma-Dynacare Laboratory Partnership, 245 Pall Mall Street, London, ONT, Canada N6A 1P4, 519-679-1630</FP>
        <FP SOURCE="FP-1">Laboratory Corporation of America Holdings, 7207 N. Gessner Road, Houston, TX 77040, 713-856-8288/800-800-2387</FP>
        <FP SOURCE="FP-1">Laboratory Corporation of America Holdings, 69 First Ave., Raritan, NJ 08869, 908-526-2400/800-437-4986, (Formerly: Roche Biomedical Laboratories, Inc.)</FP>
        <FP SOURCE="FP-1">Laboratory Corporation of America Holdings, 1904 Alexander Drive, Research Triangle Park, NC 27709, 919-572-6900/800-833-3984, (Formerly: LabCorp Occupational Testing Services, Inc., CompuChem Laboratories, Inc.; CompuChem Laboratories, Inc., a Subsidiary of Roche Biomedical Laboratory; Roche CompuChem Laboratories, Inc., a Member of the Roche Group)</FP>
        <FP SOURCE="FP-1">Laboratory Corporation of America Holdings, 1120 Main Street, Southaven, MS 38671, 866-827-8042/800-233-6339, (Formerly: LabCorp Occupational Testing Services, Inc.; MedExpress/National Laboratory Center)</FP>
        <FP SOURCE="FP-1">LabOne, Inc. d/b/a Quest Diagnostics, 10101 Renner Blvd., Lenexa, KS 66219, 913-888-3927/800-873-8845, (Formerly: Quest Diagnostics Incorporated; LabOne, Inc.; Center for Laboratory Services, a Division of LabOne, Inc.)</FP>
        <FP SOURCE="FP-1">MedTox Laboratories, Inc., 402 W. County Road D, St. Paul, MN 55112, 651-636-7466/800-832-3244</FP>
        <FP SOURCE="FP-1">MetroLab-Legacy Laboratory Services, 1225 NE 2nd Ave., Portland, OR 97232, 503-413-5295/800-950-5295</FP>
        <FP SOURCE="FP-1">Minneapolis Veterans Affairs Medical Center, Forensic Toxicology Laboratory, 1 Veterans Drive, Minneapolis, MN 55417, 612-725-2088</FP>
        <FP SOURCE="FP-1">National Toxicology Laboratories, Inc., 1100 California Ave., Bakersfield, CA 93304, 661-322-4250/800-350-3515</FP>
        <FP SOURCE="FP-1">One Source Toxicology Laboratory, Inc., 1213 Genoa-Red Bluff, Pasadena, TX 77504, 888-747-3774, (Formerly: University of Texas Medical Branch, Clinical Chemistry Division; UTMB Pathology-Toxicology Laboratory)</FP>
        <FP SOURCE="FP-1">Pacific Toxicology Laboratories, 9348 DeSoto Ave., Chatsworth, CA 91311, 800-328-6942, (Formerly: Centinela Hospital Airport Toxicology Laboratory)</FP>
        <FP SOURCE="FP-1">Pathology Associates Medical Laboratories, 110 West Cliff Dr., Spokane, WA 99204, 509-755-8991/800-541-7891 x7</FP>
        <FP SOURCE="FP-1">Phamatech, Inc., 10151 Barnes Canyon Road, San Diego, CA 92121, 858-643-5555</FP>
        <FP SOURCE="FP-1">Quest Diagnostics Incorporated, 1777 Montreal Circle, Tucker, GA 30084, 800-729-6432, (Formerly: SmithKline Beecham Clinical Laboratories; SmithKline Bio-Science Laboratories)</FP>
        <FP SOURCE="FP-1">Quest Diagnostics Incorporated, 400 Egypt Road, Norristown, PA 19403, 610-631-4600/877-642-2216, (Formerly: SmithKline Beecham Clinical Laboratories; SmithKline Bio-Science Laboratories)</FP>
        <FP SOURCE="FP-1">Quest Diagnostics Incorporated, 8401 Fallbrook Ave., West Hills, CA 91304, 818-737-6370, (Formerly: SmithKline Beecham Clinical Laboratories)</FP>
        <FP SOURCE="FP-1">Redwood Toxicology Laboratory, 3650 Westwind Blvd., Santa Rosa, CA 95403, 707-570-4434</FP>
        <FP SOURCE="FP-1">South Bend Medical Foundation, Inc., 530 N. Lafayette Blvd., South Bend, IN 46601, 574-234-4176 x1276</FP>
        <FP SOURCE="FP-1">Southwest Laboratories, 4625 E. Cotton Center Boulevard, Suite 177, Phoenix, AZ 85040, 602-438-8507/800-279-0027</FP>
        <FP SOURCE="FP-1">STERLING Reference Laboratories, 2617 East L Street, Tacoma, Washington 98421, 800-442-0438</FP>
        <FP SOURCE="FP-1">Toxicology &amp; Drug Monitoring Laboratory, University of Missouri Hospital &amp; Clinics, 301 Business Loop 70 West, Suite 208, Columbia, MO 65203, 573-882-1273</FP>
        <FP SOURCE="FP-1">U.S. Army Forensic Toxicology Drug Testing Laboratory, 2490 Wilson St., Fort George G. Meade, MD 20755-5235, 301-677-7085</FP>
        
        <P>The following laboratory voluntarily withdrew from the NLCP on December 31, 2012:</P>
        
        <FP SOURCE="FP-1">Maxxam Analytics,* 6740 Campobello Road, Mississauga, ON, Canada L5N 2L8, 905-817-5700, (Formerly: Maxxam Analytics Inc., NOVAMANN (Ontario), Inc.)</FP>
        
        <EXTRACT>
          <P>* The Standards Council of Canada (SCC) voted to end its Laboratory Accreditation Program for Substance Abuse (LAPSA) effective May 12, 1998. Laboratories certified through that program were accredited to conduct forensic urine drug testing as required by U.S. Department of Transportation (DOT) regulations. As of that date, the certification of those accredited Canadian laboratories will continue under DOT authority. The responsibility for conducting quarterly performance testing plus periodic on-site inspections of those LAPSA-accredited laboratories was transferred to the U.S. HHS, with the HHS' NLCP contractor continuing to have an active role in the performance testing and laboratory inspection processes. Other Canadian laboratories wishing to be considered for the NLCP may apply directly to the NLCP contractor just as U.S. laboratories do.</P>

          <P>Upon finding a Canadian laboratory to be qualified, HHS will recommend that DOT certify the laboratory (<E T="04">Federal Register</E>, July 16, 1996) as meeting the minimum standards of the Mandatory Guidelines published in the<E T="04">Federal Register</E>on April 30, 2010 (75 FR 22809). After receiving DOT certification, the laboratory will be included in the monthly list of HHS-certified laboratories and participate in the NLCP certification maintenance program.</P>
        </EXTRACT>
        <SIG>
          <NAME>Janine Denis Cook,</NAME>
          <TITLE>Chemist, Division of Workplace Programs, Center for Substance Abuse Prevention, SAMHSA.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31573 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4160-20-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>U.S. Customs and Border Protection</SUBAGY>
        <SUBJECT>Reopening of Application Period for Participation in the Air Cargo Advance Screening (ACAS) Pilot Program</SUBJECT>
        <HD SOURCE="HD2">Correction</HD>
        <P>In notice document 2012-30922, appearing on page 76064 in the issue of Wednesday, December 26, 2012, make the following correction:</P>
        <P>In the second column, in the first line, “January 8, 2013” is corrected to read “January 10, 2013”.</P>
        <P>In the third column, in the 8th line, “January 8, 2013” is corrected to read “January 10, 2013”.</P>
        
      </PREAMB>
      <FRDOC>[FR Doc. C1-2012-30922 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 1505-01-D</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
        <DEPDOC>[Docket No. FR-5604-N-17]</DEPDOC>
        <SUBJECT>Notice of Proposed Information; Collection for Public Comment; Continuum of Care Program Application—Technical Submission</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of the Assistant Secretary for Community Planning and Development, HUD.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of proposed information collection.</P>
        </ACT>
        <SUM>
          <PRTPAGE P="316"/>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The proposed information collection requirement described below will be submitted to the Office of Management and Budget (OMB) for review, as required by the Paperwork Reduction Act. The Department is soliciting public comments on the subject proposal.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Comments Due Date:</E>February 26, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Interested persons are invited to submit comments regarding this proposal. Comments should refer to the proposal by name/or OMB Control number and should be sent to: Colette Pollard, Departmental Reports Management Officer, QDAM, Department of Housing and Urban Development, 451 7th Street SW., Room 4160, Washington, DC 20410-5000; telephone (202) 402-3400, (this is not a toll-free number) or email Ms. Pollard at<E T="03">Colette_Pollard@hud.gov</E>for a copy of proposed forms, or other available information. Persons with hearing or speech impairments may access this number through TTY by calling the toll-free Federal Information Relay Service at (800) 877-8339.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ann Marie Oliva, Director, Office of Special Needs Assistance Programs, Office of Community Planning and Development, Department of Housing and Urban Development, 451 7th Street SW., Room 7262,  Washington, DC 20410; telephone (202) 708-1590 (This is not a toll-free number).</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The Department will submit the proposed information collection to OMB for review, as required by the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35, as amended). This Notice is soliciting comments from members of the public and affected agencies concerning the proposed collection of information to: (1) Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; (2) evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information; (3) enhance the quality, utility, and clarity of the information to be collected; and (4) minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated collection techniques or other forms of information technology; e.g., permitting electronic submission of responses.</P>
        <P>This Notice also lists the following information:</P>
        <P>
          <E T="03">Title of Proposal:</E>Continuum of Care Program Application—Technical Submission.</P>
        <P>
          <E T="03">Description of the need for the information proposed:</E>This submission is to request a reinstatement with revisions of an expired information collection for reporting burden associated with the Technical Submission phase of the Continuum of Care (CoC) Program Application. This submission is limited to the Technical Submission process under the CoC Program interim rule, formerly under the Supportive Housing Program and the Shelter Plus Care Program and changed to match the new program name created through the HEARTH Act.</P>
        <P>Applicants who are successful in the Continuum of Care Program Homeless Assistance Grant competition are required to submit more detailed technical information before grant agreement. The information to be collected will be used to ensure that technical requirements are met prior to the execution of a grant agreement. The technical requirements relate to a more extensive description of the budgets for supportive services and operations, as well as acquisition, rehabilitation, new construction, rental assistance, leasing, and sources of financing documentation. HUD will use this detailed information to determine if a project is financially feasible and whether all proposed activities are eligible.</P>

        <P>All information collected is used to carefully consider conditional applicants for funding. If HUD collects less information, or collected it less frequently, the Department could not make a final determination concerning the eligibility of applicants for grant funds and conditional applicants would not be eligible to sign grant agreements and receive funding. To see the regulations for the new CoC Program and applicable supplementary documents, visit HUD's Homeless Resource Exchange CoC page at<E T="03">http://www.hudhre.info/coc/.</E>The statutory provisions and the implementing interim rule (also found at 24 CFR part 587) that govern the program require the information provided by the Technical Submission.</P>
        <P>
          <E T="03">Agency Form Numbers:</E>HUD-40090-3a, HUD-40090-3b.</P>
        <P>
          <E T="03">Members of the affected public:</E>Conditional recipients of new CoC Program grant awards, including nonprofit organizations, local and state governments.</P>
        <P>
          <E T="03">Estimation of the total number of hours needed to prepare the information collection including number of respondents, frequency of response, and hours of response:</E>Once a project is conditionally awarded, all applicants with new projects must complete the appropriate Technical Submission forms in e-snaps to receive funding. Each type of project will require a unique set of forms to meet compliance, and so the estimates below represent an average of applicants that have several forms to complete. We are anticipating a maximum of 750 responses this year, with each respondent completing only 1 technical submission at 8 hours per response for a total of 6,000 hours. While much of the content remains the same as in the previous collection, we have estimated that the move to an electronic collection will save a minimum average of 1 hour per response, for a total savings of 750 hours.</P>
        <P>
          <E T="03">Status of proposed information collection:</E>Reinstatement, with change, of previously approved collection for which approval has expired.</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: December 20, 2012.</DATED>
          <NAME>Mark Johnston,</NAME>
          <TITLE>Deputy Assistant Secretary for Special Needs Programs.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31184 Filed 12-27-12; 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-5673-D-01]</DEPDOC>
        <SUBJECT>Order of Succession for the Office of Housing</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 of Order of Succession.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In this notice, the Acting Assistant Secretary for Housing designates the Order of Succession for the Office of Housing. This Order of Succession supersedes all prior Orders of Succession for the Assistant Secretary for Housing, including that published on June 20, 2012 (77 FR 37237).</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>December 28, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Laura Marin, Acting General Deputy Assistant Secretary, Office of Housing, Department of Housing and Urban Development, 451 Seventh Street SW., Room 9110, Washington, DC 20410-0500; telephone number 202-402-2689 (this is not a toll-free number). Persons with hearing or speech impairments<PRTPAGE P="317"/>may call HUD's toll-free Federal Relay Service at 800-877-8339.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The Acting Assistant Secretary for Housing for the Department of Housing and Urban Development is issuing this Order of Succession of officials authorized to perform the functions and duties of the Office of Housing when, by reason of absence, disability, or vacancy in office, the Acting Assistant Secretary is not available to exercise the powers or perform the duties of the office. This Order of Succession is subject to the provisions of the Federal Vacancies Reform Act of 1998 (5 U.S.C. 3345-3349d). This publication supersedes the Order of Succession notice published on June 20, 2012 (77 FR 37237).</P>
        <P>Accordingly, the Acting Assistant Secretary for Housing designates the following Order of Succession:</P>
        <HD SOURCE="HD1">Section A. Order of Succession</HD>
        <P>Subject to the provisions of the Federal Vacancies Reform Act of 1998, during any period when, by reason of absence, disability, or vacancy in office, the Acting Assistant Secretary for Housing for the Department of Housing and Urban Development is not available to exercise the powers or perform the duties of the Office of the Assistant Secretary for Housing, the following officials within the Office of Housing are hereby designated to exercise the powers and perform the duties of the Acting Assistant Secretary for Housing, including the authority to waive regulations:</P>
        <P>(1) General Deputy Assistant Secretary for Housing;</P>
        <P>(2) Deputy Assistant Secretary for Single Family Housing;</P>
        <P>(3) Deputy Assistant Secretary for Multifamily Housing;</P>
        <P>(4) Deputy Assistant Secretary for Housing Counseling;</P>
        <P>(5) Associate General Deputy Assistant Secretary for Housing;</P>
        <P>(6) Deputy Assistant Secretary for Risk Management and Regulatory Affairs;</P>
        <P>(7) Deputy Assistant Secretary for Finance and Budget;</P>
        <P>(8) Deputy Assistant Secretary for Operations;</P>
        <P>(9) Deputy Assistant Secretary for Healthcare Programs.</P>
        <P>These officials shall perform the functions and duties of the office in the order specified herein, and no official shall serve unless all other officials whose position titles precede his/hers in this order are unable to act by reason of absence, disability, or vacancy in office.</P>
        <HD SOURCE="HD1">Section B. Authority Superseded</HD>
        <P>This Order of Succession supersedes all prior Orders of Succession for the Assistant Secretary for Housing, including that published on June 20, 2012 (77 FR 37237).</P>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>Section 7(d), Department of Housing and Urban Development Act, 42 U.S.C. 3535(d).</P>
        </AUTH>
        <SIG>
          <DATED>Dated: December 28, 2012.</DATED>
          <NAME>Carol J. Galante,</NAME>
          <TITLE>Acting Assistant Secretary for Housing-—Federal Housing Commissioner.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31628 Filed 1-2-13; 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-5672-D-01]</DEPDOC>
        <SUBJECT>Redelegation of Authority to the Deputy Assistant Secretary for Housing Counseling</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 of redelegation of uthority.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Dodd-Frank Wall Street Reform and Consumer Protection Act of 2010 (Dodd-Frank Act), amends section 106 of the Housing and Urban Development Act of 1968 and authorizes the establishment of an Office of Housing Counseling in the Department of Housing and Urban Development. This Notice describes specific organizational steps that HUD has taken to establish an Office of Housing Counseling and redelegates authority to the Deputy Assistant Secretary for Housing Counseling, a new position established to have primary responsibility within HUD for all activities and matters relating to homeownership and rental housing counseling consistent with section 1442 of the Dodd-Frank Act.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>December 28, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Office of the Deputy Assistant Secretary for Housing Counseling, 451 7th Street SW., Room 9224, Washington, DC, 20410, Telephone: 202-708-0317. (This is not a toll-free number). Persons with hearing or speech impairments may access this number by calling HUD's toll-free Federal Relay Service number at 800-877-8339.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>In general, HUD's major program for housing counseling is authorized by section 106 of the Housing and Urban Development Act of 1968 (12 U.S.C. 1701x<E T="03">et seq.</E>)(1968 Act). Other statutory authority also requires HUD to provide, or cause to be provided, counseling assistance, including sections 255(f) and (l) of the National Housing Act (relating to Home Equity Conversion Mortgages) (12 U.S.C. 1715z-20) and section 2128 of the Housing and Economic Recovery Act of 2008 (relating to a pre-homeownership counseling demonstration project) (12 U.S.C. 1701x note). Other authority for HUD's housing counseling program is referenced in section 1442 of the Dodd-Frank Act (Pub. L. 111-203, approved July 21, 2010). As the primary authority for HUD's housing counseling program, section 106 is funded annually through appropriations action under a specific appropriations account for housing counseling. Activities under section 106 include pre-purchase and post-purchase homeownership counseling, default and foreclosure prevention counseling, counseling for renter households, counseling in connection with reverse mortgages and counseling to protect consumers from mortgage fraud. Counseling is provided through HUD-approved housing counseling agencies which receive grants from HUD to provide these services.</P>

        <P>Subtitle D of Title XIV of the Dodd-Frank Act, which consists of sections 1440 through 1452, makes several amendments to strengthen HUD's housing counseling program. Section 1442 amends section 4 of the Department of Housing and Urban Development Act (42 U.S.C. 3533) (Department of HUD Act) to establish an Office of Housing Counseling within HUD specifically devoted to administration and oversight of housing counseling agencies, individual counselors and the counseling services offered under the program. Sections 1443, 1444, 1445 and 1448 of the Dodd-Frank Act amend section 106 of the 1968 Act to improve the effectiveness of HUD's housing counseling program by, among other things, defining certain commonly used terms in the program; ensuring that HUD-approved counselors provide counseling covering the entire process of homeownership from the purchase of a home to its disposition, ensuring that rental or homeownership counseling required under certain HUD programs is administered in accordance with procedures established by HUD, and requiring that all HUD-related homeownership counseling and rental housing counseling is provided by HUD-certified housing counseling agencies through HUD-certified housing counselors.<PRTPAGE P="318"/>
        </P>
        <P>Under delegations of authority published in the<E T="04">Federal Register</E>on June 20, 2012 (77 FR 37252), the authority for carrying out section 106 of the Housing and Urban Development Act of 1968 and other counseling provisions established in National Housing Act programs was delegated from the Secretary of HUD to the Assistant Secretary for Housing-Federal Housing Commissioner and the General Deputy Assistant Secretary for Housing-Deputy Federal Housing Commissioner. In turn, this authority was redelegated to the Deputy Assistant Secretary for Single Family Programs and the Associate Deputy Assistant Secretary and through them to certain managers within that organization.</P>
        <P>To implement the Dodd-Frank Act and consolidate responsibility for homeownership and rental housing counseling within HUD, the Department assessed its existing organizational framework for providing housing counseling services and, with the approval of the Congress, determined to establish a new Office of the Deputy Assistant Secretary for Housing Counseling located within the Office of Housing. The Office of Housing Counseling would continue and expand upon the major homeownership and rental counseling services already performed by the Office of Housing. The functions of the new office are described in Section A., below.</P>
        <P>Today's notice also redelegates authority from the Assistant Secretary for Housing to the Deputy Assistant Secretary for Housing Counseling to carry out the major homeownership and rental housing counseling programs, including section 106 activities. To the extent that today's notice redelegates authority to administer HUD's housing counseling program, this notice supersedes the redelegation of authority to the Deputy Assistant Secretary for Single Family Housing published on June 20, 2012, with respect to homeownership and rental housing counseling.</P>
        <HD SOURCE="HD1">Section A. Office of the Deputy Assistant Secretary for Housing Counseling</HD>
        <P>The Office of the Deputy Assistant Secretary for Housing Counseling, directed by a Deputy Assistant Secretary for Housing Counseling and an Associate Deputy Assistant Secretary for Housing Counseling, provides overall program and grant management, policy direction, and strategy (including outreach activities) for homeownership and rental housing counseling (including certification) and also provides direction and coordination of internal and external relationships. Three offices report to the Office of the Deputy Assistant Secretary for Housing Counseling:</P>
        <P>•<E T="03">The Office of Policy and Grant Administration.</E>This office carries out research and evaluation activities, grant making and administration functions, development of program policies, procedures and regulations, and coordination with other offices within and without HUD which operate housing counseling programs. The office is headed by an Office Director and a Deputy Office Director.</P>
        <P>•<E T="03">The Office of Outreach and Capacity Building.</E>This office conducts outreach, education, training and consultation services for program participants, including housing counseling agencies and state and local governments. The office develops marketing and educational campaigns and provides training, technical assistance, and program materials to program participants. The office provides a central point of contact for program participants. The office ensures that evaluation results are integrated into its outreach activities. The office is headed by a Director and Deputy Director.</P>
        <P>•<E T="03">The Office of Oversight and Accountability.</E>Functions of the office include review of applications for approval of agencies and counselors, monitoring and evaluation of agencies and grantees to ensure compliance with counseling program requirements, tracking and oversight of grant funds, and initiating actions to remove or sanction non-compliant program participants. The office assists with program evaluation, grant making, and certification functions. The office is headed by a Director and Deputy Director.</P>
        <HD SOURCE="HD1">Section B. Authority Delegated</HD>
        <P>The Assistant Secretary for Housing—Federal Housing Commissioner hereby redelegates to the Deputy Assistant Secretary for Housing Counseling and the Associate Deputy Assistant Secretary for Housing Counseling the authority to sign documents, establish procedures for, and carry out all enumerated functions in connection with homeownership counseling and rental housing counseling, including but not limited to making grants, conducting demonstration and outreach projects, evaluating program performance, imposing sanctions on program participants, developing certification requirements and providing training and technical assistance.</P>
        <HD SOURCE="HD1">Section C. Authority Excepted</HD>
        <P>The authority redelegated in Section B does not include the authority to sue or be sued or to appoint members of any advisory committee established to advise the Office of the Deputy Assistant Secretary for Housing Counseling. The authority redelegated in Section B does not include authority to issue or waive any statutory or regulatory requirement for the program.</P>
        <HD SOURCE="HD1">Section D. Authority to Redelegate</HD>
        <P>The authority redelegated in Section B may be redelegated to the Office Directors and Deputy Directors commensurate with the respective functions of their office and may be further redelegated as appropriate.</P>
        <HD SOURCE="HD1">Section E. Authority Superseded</HD>
        <P>This redelegation supersedes all previous redelegations of authority with respect to homeownership and rental housing counseling including the redelegation of authority published on June 20, 2012 (77 FR 37252).</P>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>Section 7(d) of the Department of Housing and Urban Development Act (42 U.S.C. 3535(d)); Section 4(g) of the Department of Housing and Urban Development Act (42 U.S.C. 3533(g)), as amended by Section 1442 of the Dodd-Frank Wall Street Reform and Consumer Protection Act of 2010.</P>
        </AUTH>
        <SIG>
          <DATED>Dated: December 28, 2012.</DATED>
          <NAME>Carol J. Galante,</NAME>
          <TITLE>Acting Assistant Secretary for Housing—Federal Housing Commissioner.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31626 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4210-67-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
        <SUBAGY>Bureau of Land Management</SUBAGY>
        <DEPDOC>[LLES956000-L14200000-BJ0000]</DEPDOC>
        <SUBJECT>Eastern States: Filing of Plat of Survey, North Carolina</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 Bureau of Land Management (BLM) will file the plat of survey of the land described below in the BLM—Eastern States office in Springfield, Virginia, 30 calendar days from the date of publication in the<E T="04">Federal Register</E>.</P>
        </SUM>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Bureau of Land Management—Eastern States, 7450 Boston Boulevard, Springfield, Virginia 22153. Attn: Dominica Van Koten. Persons who use a telecommunications device for the<PRTPAGE P="319"/>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>The survey was requested by the Bureau of Indian Affairs, Eastern Region.</P>
        <P>The lands surveyed are:</P>
        <HD SOURCE="HD1">Swain County, North Carolina</HD>
        <P>The plats of survey represent the dependent resurvey of a portion of the Qualla Indian Boundary, lands held in trust for the Eastern Band of Cherokee Indians, Swain County, in the State of North Carolina, and was accepted December 19, 2012.</P>
        <HD SOURCE="HD1">Swain County, North Carolina</HD>
        <P>The plat of survey represents the dependent resurvey of a portion of the Qualla Indian Boundary, lands held in trust for the Eastern Band of Cherokee Indians, Swain County, in the State of North Carolina, and was accepted December 17, 2012.</P>
        <P>We will place copies of the plats we described in the open files. They will be available to the public as a matter of information.</P>
        <P>If BLM receives a protest against a survey, as shown on the plat, prior to the date of the official filing, we will stay the filing pending our consideration of the protest.</P>
        <P>We will not officially file the plat until the day after we have accepted or dismissed all protests and they have become final, including decisions on appeals.</P>
        <SIG>
          <DATED>Dated: December 27, 2012.</DATED>
          <NAME>Dominica Van Koten,</NAME>
          <TITLE>Chief Cadastral Surveyor.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31583 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">NUCLEAR REGULATORY COMMISSION</AGENCY>
        <DEPDOC>[Docket No. NRC-2012-0178]</DEPDOC>
        <SUBJECT>Agency Information Collection Activities: Submission for the Office of Management and Budget (OMB) Review; Comment Request</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Nuclear Regulatory Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of the OMB review of information collection and solicitation of public comment.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The U.S. Nuclear Regulatory Commission (NRC) has recently submitted to OMB for review the following proposal for the collection of information under the provisions of the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35). The NRC hereby informs potential respondents that an agency may not conduct or sponsor, and that a person is not required to respond to, a collection of information unless it displays a currently valid OMB control number. The NRC published a<E T="04">Federal Register</E>Notice with a 60-day comment period on this information collection on September 21, 2012 (77 FR 58586).</P>
          <P>1.<E T="03">Type of submission, new, revision, or extension:</E>Extension.</P>
          <P>2.<E T="03">The title of the information collection:</E>NRC Form 790, Classification Record.</P>
          <P>3.<E T="03">Current OMB approval number:</E>3150-0052.</P>
          <P>4.<E T="03">The form number if applicable:</E>NRC Form 790.</P>
          <P>5.<E T="03">How often the collection is required:</E>On occasion.</P>
          <P>6.<E T="03">Who will be required or asked to report:</E>NRC licensees, contractors, and certificate holders who classify and declassify NRC information.</P>
          <P>7.<E T="03">An estimate of the number of annual responses:</E>2,500.</P>
          <P>8.<E T="03">The estimated number of annual respondents:</E>11 (9 NRC licensees and licensees' contractors and two certificate holders).</P>
          <P>9.<E T="03">An estimate of the total number of hours needed annually to complete the requirement or request:</E>125.</P>
          <P>10.<E T="03">Abstract:</E>Completion of the NRC Form 790 is a mandatory requirement for NRC licensees, contractors, and only certificate holder who classifies and declassifies NRC information in accordance with Executive Order 13526, “Classified National Security Information,” the Atomic Energy Act, and implementing directives.</P>

          <P>The public may examine and have copied for a fee publicly available documents, including the final supporting statement, at the NRC's Public Document Room, Room O-1F21, One White Flint North, 11555 Rockville Pike, Rockville, Maryland. OMB clearance requests are available at the NRC worldwide Web site:<E T="03">http://www.nrc.gov/public-involve/doc-comment/omb/.</E>The document will be available on the NRC home page site for 60 days after the signature date of this notice.</P>
          <P>Comments and questions should be directed to the OMB reviewer listed below by February 4, 2013. Comments received after this date will be considered if it is practical to do so, but assurance of consideration cannot be given to comments received after this date.</P>
          
          <FP SOURCE="FP-1">Chad Whiteman, Desk Officer, Office of Information and Regulatory Affairs (3150-0052), NEOB-10202, Office of Management and Budget, Washington, DC 20503.</FP>
          
          <P>Comments can also be emailed to<E T="03">Chad_S_Whiteman@omb.eop.gov</E>or submitted by telephone at 202-395-4718.</P>
          <P>The NRC Clearance Officer is Tremaine Donnell, 301-415-6258.</P>
        </SUM>
        <SIG>
          <DATED>Dated at Rockville, Maryland, this 28th day of December 2012.</DATED>
          
          <P>For the Nuclear Regulatory Commission.</P>
          <NAME>Tremaine Donnell,</NAME>
          <TITLE>NRC Clearance Officer, Office of Information Services.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31618 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 7590-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION</AGENCY>
        <DEPDOC>[Docket No. NRC-2012-0190]</DEPDOC>
        <SUBJECT>Agency Information Collection Activities: Submission for the Office of Management and Budget (OMB) Review; Comment Request</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Nuclear Regulatory Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of the OMB review of information collection and solicitation of public comment.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The U.S. Nuclear Regulatory Commission (NRC) has recently submitted to OMB for review the following proposal for the collection of information under the provisions of the Paperwork Reduction Act of 1995 (44 U.S.C. chapter 35). The NRC hereby informs potential respondents that an agency may not conduct or sponsor, and that a person is not required to respond to, a collection of information unless it displays a currently valid OMB control number. The NRC published a<E T="04">Federal Register</E>Notice with a 60-day comment period on this information collection on September 21, 2012 (77 FR 58585).</P>
          <P>1.<E T="03">Type of submission, new, revision, or extension:</E>Extension.</P>
          <P>2.<E T="03">The title of the information collection:</E>NRC Form 531, “Request for Taxpayer Identification Number.”</P>
          <P>3.<E T="03">Current OMB approval number:</E>3150-0188.</P>
          <P>4.<E T="03">The form number if applicable:</E>NRC Form 531.</P>
          <P>5.<E T="03">How often the collection is required:</E>One time from each applicant or individual to enable the Department of the Treasury to process electronic payments or collect debts owed to the Government.</P>
          <P>6.<E T="03">Who will be required or asked to report:</E>All individuals doing business<PRTPAGE P="320"/>with the U.S. Nuclear Regulatory Commission, including contractors and recipients of credit, licenses, permits, and benefits.</P>
          <P>7.<E T="03">An estimate of the number of annual responses:</E>300.</P>
          <P>8.<E T="03">The estimated number of annual respondents:</E>300.</P>
          <P>9.<E T="03">An estimate of the total number of hours needed annually to complete the requirement or request:</E>25.</P>
          <P>10.<E T="03">Abstract:</E>The Debt Collection Improvement Act of 1996 requires that agencies collect taxpayer identification numbers (TINs) from individuals who do business with the Government, including contractors and recipients of credit, licenses, permits, and benefits. The TIN will be used to process all electronic payments (refunds) made to licensees by electronic funds transfer by the Department of the Treasury. The Department of the Treasury will use the TIN to determine whether the refund can be used to administratively offset any delinquent debts reported to the Treasury by other government agencies. In addition, the TIN will be used to collect and report to the Department of the Treasury any delinquent indebtedness arising out of the licensee's or applicant's relationship with the NRC.</P>

          <P>The public may examine and have copied for a fee publicly available documents, including the final supporting statement, at the NRC's Public Document Room, Room O-1F21, One White Flint North, 11555 Rockville Pike, Rockville, Maryland. OMB clearance requests are available at the NRC worldwide Web site:<E T="03">http://www.nrc.gov/public-involve/doc-comment/omb/.</E>The document will be available on the NRC home page site for 60 days after the signature date of this notice.</P>
          <P>Comments and questions should be directed to the OMB reviewer listed below by February 4, 2013. Comments received after this date will be considered if it is practical to do so, but assurance of consideration cannot be given to comments received after this date.</P>
          
          <FP SOURCE="FP-1">Chad Whiteman, Desk Officer, Office of Information and Regulatory Affairs (3150-0188), NEOB-10202, Office of Management and Budget, Washington, DC 20503.</FP>
          
          <P>Comments can also be emailed to<E T="03">Chad_S_Whiteman@omb.eop.gov</E>or submitted by telephone at 202-395-4718.</P>
          <P>The NRC Clearance Officer is Tremaine Donnell, 301-415-6258.</P>
        </SUM>
        <SIG>
          <DATED>Dated at Rockville, Maryland, this 28th day of December, 2012.</DATED>
          
          <P>For the Nuclear Regulatory Commission.</P>
          <NAME>Tremaine Donnell,</NAME>
          <TITLE>NRC Clearance Officer, Office of Information Services.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31619 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 7590-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION</AGENCY>
        <DEPDOC>[Docket Nos. 50-458; NRC-2012-0318]</DEPDOC>
        <SUBJECT>Consideration of Approval of Application Regarding Proposed Creation of a Holding Company and Transfer of Facility Operating License and Opportunity for a Hearing; River Bend Station, Unit 1</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Nuclear Regulatory Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Request for license transfer; opportunity to comment; opportunity to request a hearing and petition for leave to intervene.</P>
        </ACT>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be filed by February 4, 2013. A request for a hearing must be filed by January 23, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>You may access information and comment submissions related to this document, which the NRC possesses and are publicly available, by searching on<E T="03">http://www.regulations.gov</E>under Docket ID NRC-2012-0318. You may submit comments by any of the following methods:</P>
          <P>•<E T="03">Federal rulemaking Web site:</E>Go to<E T="03">http://www.regulations.gov</E>and search for Docket ID NRC-2012-0318. Address questions about NRC dockets to Carol Gallagher; telephone: 301-492-3668; email:<E T="03">Carol.Gallagher@nrc.gov.</E>
          </P>
          <P>•<E T="03">Mail comments to:</E>Cindy Bladey, Chief, Rules, Announcements, and Directives Branch (RADB), Office of Administration, Mail Stop: TWB-05-B01M, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001.</P>
          <P>•<E T="03">Fax comments to:</E>RADB at 301-492-3446.</P>

          <P>For additional direction on accessing information and submitting comments, see “Accessing Information and Submitting Comments” in the<E T="02">SUPPLEMENTARY INFORMATION</E>section of this document.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Alan Wang, Project Manager, Plant Licensing Branch IV, Division of Operating Reactor Licensing, Office of Nuclear Reactor Regulation, U.S. Nuclear Regulatory Commission, Washington, DC 20555. Telephone: 301-415-1445; fax number: 301-415-2102; email:<E T="03">Alan.Wang@nrc.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Accessing Information and Submitting Comments</HD>
        <HD SOURCE="HD2">A. Accessing Information</HD>
        <P>Please refer to Docket ID NRC-2012-0318 when contacting the NRC about the availability of information regarding this document. You may access information related to this document, which the NRC possesses and are publicly available, by any of the following methods:</P>
        <P>•<E T="03">Federal Rulemaking Web Site:</E>Go to<E T="03">http://www.regulations.gov</E>and search for Docket ID NRC-2012-0318.</P>
        <P>•<E T="03">NRC's Agencywide Documents Access and Management System (ADAMS):</E>You may access publicly available documents online in the NRC Library at<E T="03">http://www.nrc.gov/reading-rm/adams.html.</E>To begin the search, select “ADAMS Public Documents” and then select “Begin Web-based ADAMS Search.” For problems with ADAMS, please contact the NRC's Public Document Room (PDR) reference staff at 1-800-397-4209, 301-415-4737, or by email to<E T="03">pdr.resource@nrc.gov.</E>The application dated September 27, 2012, is available electronically under ADAMS Accession No. ML12275A013.</P>
        <P>•<E T="03">NRC's PDR:</E>You may examine and purchase copies of public documents at the NRC's PDR, Room O1-F21, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852.</P>
        <HD SOURCE="HD2">B. Submitting Comments</HD>
        <P>Please include Docket ID NRC-2012-0318 in the subject line of your comment submission, in order to ensure that the NRC is able to make your comment submission available to the public in this docket.</P>

        <P>The NRC cautions you not to include identifying or contact information that you do not want to be publicly disclosed in you comment submission. The NRC will post all comment submissions at<E T="03">http://www.regulations.gov</E>as well as enter the comment submissions into ADAMS. The NRC does not routinely edit comment submissions to remove identifying or contact information.</P>

        <P>If you are requesting or aggregating comments from other persons for submission to the NRC, then you should inform those persons not to include identifying or contact information that they do not want to be publicly disclosed in their comment submission. Your request should state that the NRC does not routinely edit comment submissions to remove such information before making the comment submissions available to the public or<PRTPAGE P="321"/>entering the comment submissions into ADAMS.</P>
        <HD SOURCE="HD1">II. Introduction</HD>

        <P>The U.S. Nuclear Regulatory Commission (NRC or the Commission) is considering the issuance of an order under section 50.80 of Title 10 of the<E T="03">Code of Federal Regulations</E>(10 CFR) approving the direct transfer of the Facility Operating License, which is numbered NPF-47, for the River Bend Station, Unit 1 (RBS), and associated Independent Spent Fuel Storage Installation, currently held by Entergy Gulf States Louisiana, LLC (EGS-LA), as owner and Entergy Operations, Inc. (EOI), as licensed operator of RBS. The direct transfer of the RBS license would be to a new limited liability company also named Entergy Gulf States Louisiana, LLC (New EGS-LA). According to an application for approval filed by EOI on behalf of EGS-LA, New EGS-LA would acquire ownership of the facility previously owned by EGS-LA following approval of the proposed license transfer. EOI would remain responsible for the operation and maintenance of RBS.</P>
        <P>In addition, the Commission is also considering approving associated indirect license transfers to the extent such would be affected by a formation of a new intermediary holding company. According to an application for approval filed by EOI, on behalf of EGS-LA, Entergy Corporation will remain as the ultimate parent company, but a new, intermediate company, Entergy Utilities Holdings, LLC, a Delaware limited liability company, will be created, which will be the direct parent company of New EGS-LA and EOI. The New EGS-LA will own the facility and EOI would remain responsible for the operation and maintenance of RBS.</P>
        <P>No physical changes to the RBS facility or operational changes are being proposed in the application.</P>
        <P>Pursuant to 10 CFR 50.80, no license, or any right thereunder, shall be transferred, directly or indirectly, through transfer of control of the license, unless the Commission shall give its consent in writing. The Commission will approve an application for the direct transfer of a license, if the Commission determines that the proposed transferee is qualified to hold the license, and that the transfer is otherwise consistent with applicable provisions of law, regulations, and orders issued by the Commission pursuant thereto. The Commission will approve an application for the indirect transfer of a license, if the Commission determines that the proposed establishment of a new holding company will not affect the qualifications of the licensee to hold the license, and that the transfer is otherwise consistent with applicable provisions of law, regulations, and orders issued by the Commission pursuant thereto.</P>
        <P>As provided in 10 CFR 2.1315, unless otherwise determined by the Commission with regard to a specific application, the Commission has determined that any amendment to the license of a utilization facility which does no more than conform the license to reflect the transfer action involves no significant hazards consideration. No contrary determination has been made with respect to this specific license amendment application. In light of the generic determination reflected in 10 CFR 2.1315, no public comments with respect to significant hazards considerations are being solicited, notwithstanding the general comment procedures contained in 10 CFR 50.91.</P>
        <P>The filing of requests for hearing and petitions for leave to intervene, and written comments with regard to the license transfer application, are discussed below.</P>
        <HD SOURCE="HD1">III. Opportunity To Request a Hearing; Petition for Leave To Intervene</HD>

        <P>Within 20 days from the date of publication of this notice, any person(s) whose interest may be affected by the Commission's action on the application may request a hearing and intervention via electronic submission through the NRC's E-filing system. Requests for a hearing and petitions for leave to intervene should be filed in accordance with the Commission's rules of practice set forth in Subpart C “Rules of General Applicability: Hearing Requests, Petitions to Intervene, Availability of Documents, Selection of Specific Hearing Procedures, Presiding Officer Powers, and General Hearing Management for NRC Adjudicatory Hearings,” of 10 CFR part 2. In particular, such requests and petitions must comply with the requirements set forth in 10 CFR 2.309, which is available at the NRC's PDR, located at O1F21, 11555 Rockville Pike (first floor), Rockville, Maryland 20852. The NRC regulations are accessible electronically from the NRC Library on the NRC's public Web site at<E T="03">http://www.nrc.gov/reading-rm/doc-collections/cfr/.</E>
        </P>
        <P>A State, local governmental body, Federally-recognized Indian Tribe, or agency thereof may submit a petition to the Commission to participate as a party under 10 CFR 2.309(h)(1) and (2). The petition should state the nature and extent of the petitioner's interest in the proceeding. The petition should be submitted to the Commission by January 23, 2013. The petition must be filed in accordance with the filing instructions in section IV of this document, and should meet the requirements for petitions for leave to intervene set forth in this section, except that under 2.309(h)(2) a State, local governmental body, or Federally-recognized Indian tribe does not need to address the standing requirements in 10 CFR 2.309(d) if the facility is located within its boundaries. A State, local governmental body, Federally-recognized Indian Tribe, or agency thereof may also have the opportunity to participate under 10 CFR 2.315(c).</P>
        <P>Requests for hearing, petitions for leave to intervene, and motions for leave to file new or amended contentions that are filed after the 20-day deadline will not be entertained absent a determination by the presiding officer that the filing demonstrates good cause by satisfying the following three factors in 10 CFR 2.309(c)(1): (i) The information upon which the filing is based was not previously available; (ii) the information upon which the filing is based is materially different from information previously available; and (iii) the filing has been submitted in a timely fashion based on the availability of the subsequent information.</P>
        <HD SOURCE="HD1">IV. Electronic Submissions (E-Filing)</HD>
        <P>All documents filed in NRC adjudicatory proceedings, including a request for hearing, a petition for leave to intervene, any motion or other document filed in the proceeding prior to the submission of a request for hearing or petition to intervene, and documents filed by interested governmental entities participating under 10 CFR 2.315(c), must be filed in accordance with the NRC's E-Filing rule (72 FR 49139; August 28, 2007). The E-Filing process requires participants to submit and serve all adjudicatory documents over the internet, or in some cases to mail copies on electronic storage media. Participants may not submit paper copies of their filings unless they seek an exemption in accordance with the procedures described below.</P>

        <P>To comply with the procedural requirements of E-Filing, at least 10 days prior to the filing deadline, the participant should contact the Office of the Secretary by email at<E T="03">hearing.docket@nrc.gov,</E>or by telephone at 301-415-1677, to request (1) a digital identification (ID) certificate, which allows the participant (or its counsel or representative) to digitally sign<PRTPAGE P="322"/>documents and access the E-Submittal server for any proceeding in which it is participating; and (2) advise the Secretary that the participant will be submitting a request or petition for hearing (even in instances in which the participant, or its counsel or representative, already holds an NRC-issued digital ID certificate). Based upon this information, the Secretary will establish an electronic docket for the hearing in this proceeding if the Secretary has not already established an electronic docket.</P>

        <P>Information about applying for a digital ID certificate is available on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals/apply-certificates.html.</E>System requirements for accessing the E-Submittal server are detailed in the NRC's “Guidance for Electronic Submission,” which is available on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals.html.</E>Participants may attempt to use other software not listed on the Web site, but should note that the NRC's E-Filing system does not support unlisted software, and the NRC Meta System Help Desk will not be able to offer assistance in using unlisted software.</P>

        <P>If a participant is electronically submitting a document to the NRC in accordance with the E-Filing rule, the participant must file the document using the NRC's online, Web-based submission form. In order to serve documents through the Electronic Information Exchange System, users will be required to install a Web browser plug-in from the NRC's public Web site. Further information on the Web-based submission form, including the installation of the Web browser plug-in, is available on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals.html.</E>
        </P>

        <P>Once a participant has obtained a digital ID certificate and a docket has been created, the participant can then submit a request for hearing or petition for leave to intervene. Submissions should be in Portable Document Format (PDF) in accordance with NRC guidance available on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals.html.</E>A filing is considered complete at the time the documents are submitted through the NRC's E-Filing system. To be timely, an electronic filing must be submitted to the E-Filing system no later than 11:59 p.m. Eastern Time on the due date. Upon receipt of a transmission, the E-Filing system time-stamps the document and sends the submitter an email notice confirming receipt of the document. The E-Filing system also distributes an email notice that provides access to the document to the NRC's Office of the General Counsel and any others who have advised the Office of the Secretary that they wish to participate in the proceeding, so that the filer need not serve the documents on those participants separately. Therefore, applicants and other participants (or their counsel or representative) must apply for and receive a digital ID certificate before a hearing request/petition to intervene is filed so that they can obtain access to the document via the E-Filing system.</P>

        <P>A person filing electronically using the NRC's adjudicatory E-Filing system may seek assistance by contacting the NRC Meta System Help Desk through the “Contact Us” link located on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals.html,</E>by email to<E T="03">MSHD.Resource@nrc.gov,</E>or by a toll-free call to 1-866-672-7640. The NRC Meta System Help Desk is available between 8 a.m. and 8 p.m., Eastern Time, Monday through Friday, excluding government holidays.</P>
        <P>Participants who believe that they have a good cause for not submitting documents electronically must file an exemption request, in accordance with 10 CFR 2.302(g), with their initial paper filing requesting authorization to continue to submit documents in paper format. Such filings must be submitted by: (1) First class mail addressed to the Office of the Secretary of the Commission, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, Attention: Rulemaking and Adjudications Staff; or (2) courier, express mail, or expedited delivery service to the Office of the Secretary, Sixteenth Floor, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852, Attention: Rulemaking and Adjudications Staff. Participants filing a document in this manner are responsible for serving the document on all other participants. Filing is considered complete by first-class mail as of the time of deposit in the mail, or by courier, express mail, or expedited delivery service upon depositing the document with the provider of the service. A presiding officer, having granted an exemption request from using E-Filing, may require a participant or party to use E-Filing if the presiding officer subsequently determines that the reason for granting the exemption from use of E-Filing no longer exists.</P>

        <P>Documents submitted in adjudicatory proceedings will appear in NRC's electronic hearing docket which is available to the public at<E T="03">http://ehd1.nrc.gov/ehd/,</E>unless excluded pursuant to an order of the Commission, or the presiding officer. Participants are requested not to include personal privacy information, such as social security numbers, home addresses, or home phone numbers in their filings, unless an NRC regulation or other law requires submission of such information. With respect to copyrighted works, except for limited excerpts that serve the purpose of the adjudicatory filings and would constitute a Fair Use application, participants are requested not to include copyrighted materials in their submission.</P>

        <P>The Commission will issue a notice or order granting or denying a hearing request or intervention petition, designating the issues for any hearing that will be held and designating the Presiding Officer. A notice granting a hearing will be published in the<E T="04">Federal Register</E>and served on the parties to the hearing.</P>

        <P>Within 30 days from the date of publication of this notice, persons may submit written comments regarding the license transfer application, as provided for in 10 CFR 2.1305. The Commission will consider and, if appropriate, respond to these comments, but such comments will not otherwise constitute part of the decisional record. Comments should be submitted to the Secretary, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, Attention: Rulemakings and Adjudications Staff, and should cite the publication date and page number of this<E T="04">Federal Register</E>notice.</P>
        <P>For further details with respect to this application, see the application dated September 27, 2012.</P>
        <SIG>
          <DATED>Dated at Rockville, Maryland, this 21st day of December 2012.</DATED>
          
          <P>For the Nuclear Regulatory Commission.</P>
          <NAME>Nageswaran Kalyanam,</NAME>
          <TITLE>Project Manager, Plant Licensing Branch IV, Division of Operating Reactor Licensing, Office of Nuclear Reactor Regulation.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31616 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 7590-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="323"/>
        <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION</AGENCY>
        <DEPDOC>[Docket No. 50-382; NRC-2012-0317]</DEPDOC>
        <SUBJECT>Notice of Consideration of Approval of Application Regarding Proposed Creation of a Holding Company and Transfer of Facility Operating License and Opportunity for a Hearing; Waterford Steam Electric Station, Unit 3</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Nuclear Regulatory Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Request for license transfer; opportunity to comment; opportunity to request a hearing and petition for leave to intervene.</P>
        </ACT>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be filed by February 4, 2013. A request for a hearing must be filed by January 23, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>You may access information and comment submissions related to this document, which the NRC possesses and are publicly available, by searching on<E T="03">http://www.regulations.gov</E>under Docket ID NRC-2012-0317. You may submit comments by any of the following methods:</P>
          <P>•<E T="03">Federal rulemaking Web site:</E>Go to<E T="03">http://www.regulations.gov</E>and search for Docket ID NRC-2012-0317. Address questions about NRC dockets to Carol Gallagher; telephone: 301-492-3668; email:<E T="03">Carol.Gallagher@nrc.gov.</E>
          </P>
          <P>•<E T="03">Mail comments to:</E>Cindy Bladey, Chief, Rules, Announcements, and Directives Branch (RADB), Office of Administration, Mail Stop: TWB-05-B01M, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001.</P>
          <P>•<E T="03">Fax comments to:</E>RADB at 301-492-3446.</P>

          <P>For additional direction on accessing information and submitting comments, see “Accessing Information and Submitting Comments” in the<E T="02">SUPPLEMENTARY INFORMATION</E>section of this document.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Alan Wang, Project Manager, Plant Licensing Branch IV, Division of Operating Reactor Licensing, Office of Nuclear Reactor Regulation, U.S. Nuclear Regulatory Commission, Washington, DC 20555. Telephone: 301-415-1445; fax: 301-415-2102; email:<E T="03">Alan.Wang@nrc.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Accessing Information and Submitting Comments</HD>
        <HD SOURCE="HD2">A. Accessing Information</HD>
        <P>Please refer to Docket ID NRC-2012-0317 when contacting the NRC about the availability of information regarding this document. You may access information related to this document, which the NRC possesses and are publicly available, by any of the following methods:</P>
        <P>•<E T="03">Federal Rulemaking Web Site:</E>Go to<E T="03">http://www.regulations.gov</E>and search for Docket ID NRC-2012-0317.</P>
        <P>•<E T="03">NRC's Agencywide Documents Access and Management System (ADAMS):</E>You may access publicly available documents online in the NRC Library at<E T="03">http://www.nrc.gov/reading-rm/adams.html.</E>To begin the search, select “<E T="03">ADAMS Public Documents</E>” and then select “<E T="03">Begin Web-based ADAMS Search.</E>” For problems with ADAMS, please contact the NRC's Public Document Room (PDR) reference staff at 1-800-397-4209, 301-415-4737, or by email to<E T="03">pdr.resource@nrc.gov.</E>The application dated September 27, 2012, is available electronically under ADAMS Accession No. ML12275A013.</P>
        <P>•<E T="03">NRC's PDR:</E>You may examine and purchase copies of public documents at the NRC's PDR, Room O1-F21, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852.</P>
        <HD SOURCE="HD2">B. Submitting Comments</HD>
        <P>Please include Docket ID NRC-2012-0317 in the subject line of your comment submission, in order to ensure that the NRC is able to make your comment submission available to the public in this docket.</P>

        <P>The NRC cautions you not to include identifying or contact information that you do not want to be publicly disclosed in you comment submission. The NRC will post all comment submissions at<E T="03">http://www.regulations.gov</E>as well as enter the comment submissions into ADAMS. The NRC does not routinely edit comment submissions to remove identifying or contact information.</P>
        <P>If you are requesting or aggregating comments from other persons for submission to the NRC, then you should inform those persons not to include identifying or contact information that they do not want to be publicly disclosed in their comment submission. Your request should state that the NRC does not routinely edit comment submissions to remove such information before making the comment submissions available to the public or entering the comment submissions into ADAMS.</P>
        <HD SOURCE="HD1">II. Introduction</HD>

        <P>The U.S. Nuclear Regulatory Commission (NRC or the Commission) is considering the issuance of an order under section 50.80 of Title 10 of the<E T="03">Code of Federal Regulations</E>(10 CFR) approving the direct transfer of the Facility Operating License, which is numbered NPF-38, for the Waterford Steam Electric Station, Unit 3 (WF3), and associated Independent Spent Fuel Storage Installation, currently held by Entergy Louisiana, LLC (ELL), as owner and Entergy Operations, Inc. (EOI), as licensed operator of WF3. The direct transfer of the WF3 license would be to a new limited liability company also named Entergy Louisiana, LLC (New ELL). According to an application for approval filed by EOI on behalf of ELL, New ELL would acquire ownership of the facility previously owned by ELL following approval of the proposed license transfer. EOI would remain responsible for the operation and maintenance of WF3.</P>
        <P>In addition, the Commission is also considering approving associated indirect license transfers to the extent such would be affected by a formation of a new intermediary holding company. According to an application for approval filed by EOI, on behalf of ELL, Entergy Corporation will remain as the ultimate parent company, but a new, intermediate company, Entergy Utilities Holdings, LLC, a Delaware limited liability company, would be created, which will be the direct parent company of New ELL and EOI. New ELL will own the facility and EOI would remain responsible for the operation and maintenance of WF3.</P>
        <P>No physical changes to the WF3 facility or operational changes are being proposed in the application.</P>
        <P>Pursuant to 10 CFR 50.80, no license, or any right thereunder, shall be transferred, directly or indirectly, through transfer of control of the license, unless the Commission shall give its consent in writing. The Commission will approve an application for the direct transfer of a license, if the Commission determines that the proposed transferee is qualified to hold the license, and that the transfer is otherwise consistent with applicable provisions of law, regulations, and orders issued by the Commission pursuant thereto. The Commission will approve an application for the indirect transfer of a license, if the Commission determines that the proposed establishment of a new holding company will not affect the qualifications of the licensee to hold the license, and that the transfer is otherwise consistent with applicable provisions of law, regulations, and orders issued by the Commission pursuant thereto.</P>

        <P>As provided in 10 CFR 2.1315, unless otherwise determined by the<PRTPAGE P="324"/>Commission with regard to a specific application, the Commission has determined that any amendment to the license of a utilization facility which does no more than conform the license to reflect the transfer action involves no significant hazards consideration. No contrary determination has been made with respect to this specific license amendment application. In light of the generic determination reflected in 10 CFR 2.1315, no public comments with respect to significant hazards considerations are being solicited, notwithstanding the general comment procedures contained in 10 CFR 50.91.</P>
        <P>The filing of requests for hearing and petitions for leave to intervene, and written comments with regard to the license transfer application, are discussed below.</P>
        <HD SOURCE="HD1">III. Opportunity To Request a Hearing; Petition for Leave To Intervene</HD>

        <P>Within 20 days from the date of publication of this notice, any person(s) whose interest may be affected by the Commission's action on the application may request a hearing and intervention via electronic submission through the NRC's E-filing system. Requests for a hearing and petitions for leave to intervene should be filed in accordance with the Commission's rules of practice set forth in Subpart C “Rules of General Applicability: Hearing Requests, Petitions to Intervene, Availability of Documents, Selection of Specific Hearing Procedures, Presiding Officer Powers, and General Hearing Management for NRC Adjudicatory Hearings,” of 10 CFR Part 2. In particular, such requests and petitions must comply with the requirements set forth in 10 CFR 2.309, which is available at the NRC's PDR, located at O1F21, 11555 Rockville Pike (first floor), Rockville, Maryland 20852. The NRC regulations are accessible electronically from the NRC Library on the NRC's public Web site at<E T="03">http://www.nrc.gov/reading-rm/doc-collections/cfr/.</E>
        </P>
        <P>A State, local governmental body, Federally-recognized Indian Tribe, or agency thereof may submit a petition to the Commission to participate as a party under 10 CFR 2.309(h)(1) and (2). The petition should state the nature and extent of the petitioner's interest in the proceeding. The petition should be submitted to the Commission by January 23, 2013. The petition must be filed in accordance with the filing instructions in section IV of this document, and should meet the requirements for petitions for leave to intervene set forth in this section, except that under 2.309(h)(2) a State, local governmental body, or Federally-recognized Indian tribe does not need to address the standing requirements in 10 CFR 2.309(d) if the facility is located within its boundaries. A State, local governmental body, Federally-recognized Indian Tribe, or agency thereof may also have the opportunity to participate under 10 CFR 2.315(c).</P>
        <P>Requests for hearing, petitions for leave to intervene, and motions for leave to file new or amended contentions that are filed after the 20-day deadline will not be entertained absent a determination by the presiding officer that the filing demonstrates good cause by satisfying the following three factors in 10 CFR 2.309(c)(1): (i) The information upon which the filing is based was not previously available; (ii) the information upon which the filing is based is materially different from information previously available; and (iii) the filing has been submitted in a timely fashion based on the availability of the subsequent information.</P>
        <HD SOURCE="HD1">IV. Electronic Submissions (E-Filing)</HD>
        <P>All documents filed in NRC adjudicatory proceedings, including a request for hearing, a petition for leave to intervene, any motion or other document filed in the proceeding prior to the submission of a request for hearing or petition to intervene, and documents filed by interested governmental entities participating under 10 CFR 2.315(c), must be filed in accordance with the NRC's E-Filing rule (72 FR 49139; August 28, 2007). The E-Filing process requires participants to submit and serve all adjudicatory documents over the internet, or in some cases to mail copies on electronic storage media. Participants may not submit paper copies of their filings unless they seek an exemption in accordance with the procedures described below.</P>

        <P>To comply with the procedural requirements of E-Filing, at least ten (10) days prior to the filing deadline, the participant should contact the Office of the Secretary by email at<E T="03">hearing.docket@nrc.gov,</E>or by telephone at 301-415-1677, to request (1) a digital identification (ID) certificate, which allows the participant (or its counsel or representative) to digitally sign documents and access the E-Submittal server for any proceeding in which it is participating; and (2) advise the Secretary that the participant will be submitting a request or petition for hearing (even in instances in which the participant, or its counsel or representative, already holds an NRC-issued digital ID certificate). Based upon this information, the Secretary will establish an electronic docket for the hearing in this proceeding if the Secretary has not already established an electronic docket.</P>

        <P>Information about applying for a digital ID certificate is available on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals/apply-certificates.html.</E>System requirements for accessing the E-Submittal server are detailed in the NRC's “Guidance for Electronic Submission,” which is available on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals.html.</E>Participants may attempt to use other software not listed on the Web site, but should note that the NRC's E-Filing system does not support unlisted software, and the NRC Meta System Help Desk will not be able to offer assistance in using unlisted software.</P>

        <P>If a participant is electronically submitting a document to the NRC in accordance with the E-Filing rule, the participant must file the document using the NRC's online, Web-based submission form. In order to serve documents through the Electronic Information Exchange System, users will be required to install a Web browser plug-in from the NRC's public Web site. Further information on the Web-based submission form, including the installation of the Web browser plug-in, is available on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals.html.</E>
        </P>

        <P>Once a participant has obtained a digital ID certificate and a docket has been created, the participant can then submit a request for hearing or petition for leave to intervene. Submissions should be in Portable Document Format (PDF) in accordance with NRC guidance available on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals.html.</E>A filing is considered complete at the time the documents are submitted through the NRC's E-Filing system. To be timely, an electronic filing must be submitted to the E-Filing system no later than 11:59 p.m. Eastern Time on the due date. Upon receipt of a transmission, the E-Filing system time-stamps the document and sends the submitter an email notice confirming receipt of the document. The E-Filing system also distributes an email notice that provides access to the document to the NRC's Office of the General Counsel and any others who have advised the Office of the Secretary that they wish to participate in the proceeding, so that the filer need not serve the documents on those participants separately. Therefore, applicants and other participants (or<PRTPAGE P="325"/>their counsel or representative) must apply for and receive a digital ID certificate before a hearing request/petition to intervene is filed so that they can obtain access to the document via the E-Filing system.</P>

        <P>A person filing electronically using the NRC's adjudicatory E-Filing system may seek assistance by contacting the NRC Meta System Help Desk through the “Contact Us” link located on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals.html,</E>by email to<E T="03">MSHD.Resource@nrc.gov,</E>or by a toll-free call to 1-866-672-7640. The NRC Meta System Help Desk is available between 8 a.m. and 8 p.m., Eastern Time, Monday through Friday, excluding government holidays.</P>
        <P>Participants who believe that they have a good cause for not submitting documents electronically must file an exemption request, in accordance with 10 CFR 2.302(g), with their initial paper filing requesting authorization to continue to submit documents in paper format. Such filings must be submitted by: (1) first class mail addressed to the Office of the Secretary of the Commission, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, Attention: Rulemaking and Adjudications Staff; or (2) courier, express mail, or expedited delivery service to the Office of the Secretary, Sixteenth Floor, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852, Attention: Rulemaking and Adjudications Staff. Participants filing a document in this manner are responsible for serving the document on all other participants. Filing is considered complete by first-class mail as of the time of deposit in the mail, or by courier, express mail, or expedited delivery service upon depositing the document with the provider of the service. A presiding officer, having granted an exemption request from using E-Filing, may require a participant or party to use E-Filing if the presiding officer subsequently determines that the reason for granting the exemption from use of E-Filing no longer exists.</P>

        <P>Documents submitted in adjudicatory proceedings will appear in NRC's electronic hearing docket which is available to the public at<E T="03">http://ehd1.nrc.gov/ehd/,</E>unless excluded pursuant to an order of the Commission, or the presiding officer. Participants are requested not to include personal privacy information, such as social security numbers, home addresses, or home phone numbers in their filings, unless an NRC regulation or other law requires submission of such information. With respect to copyrighted works, except for limited excerpts that serve the purpose of the adjudicatory filings and would constitute a Fair Use application, participants are requested not to include copyrighted materials in their submission.</P>

        <P>The Commission will issue a notice or order granting or denying a hearing request or intervention petition, designating the issues for any hearing that will be held and designating the Presiding Officer. A notice granting a hearing will be published in the<E T="04">Federal Register</E>and served on the parties to the hearing.</P>

        <P>Within 30 days from the date of publication of this notice, persons may submit written comments regarding the license transfer application, as provided for in 10 CFR 2.1305. The Commission will consider and, if appropriate, respond to these comments, but such comments will not otherwise constitute part of the decisional record. Comments should be submitted to the Secretary, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, Attention: Rulemakings and Adjudications Staff, and should cite the publication date and page number of this<E T="04">Federal Register</E>notice.</P>
        <P>For further details with respect to this application, see the application dated September 27, 2012.</P>
        <SIG>
          <DATED>Dated at Rockville, Maryland, this 21st day of December 2012.</DATED>
          
          <P>For the Nuclear Regulatory Commission.</P>
          <NAME>Nageswaran Kalyanam,</NAME>
          <TITLE>Project Manager, Plant Licensing Branch IV, Division of Operating Reactor Licensing, Office of Nuclear Reactor Regulation.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31617 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 7590-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION</AGENCY>
        <DEPDOC>[Docket Nos. 50-416; NRC-2012-0319]</DEPDOC>
        <SUBJECT>Consideration of Approval of Application Regarding Proposed Creation of a Holding Company and Transfer of Facility Operating License and Conforming Amendment and Opportunity for a Hearing; Grand Gulf Nuclear Station, Unit 1</SUBJECT>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Request for license transfer; opportunity to comment; opportunity to request a hearing and petition for leave to intervene.</P>
        </ACT>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be filed by February 4, 2013. A request for a hearing must be filed by January 23, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>You may access information and comment submissions related to this document, which the NRC possesses and are publicly available, by searching on<E T="03">http://www.regulations.gov</E>under Docket ID NRC-2012-0319. You may submit comments by any of the following methods:</P>
          <P>•<E T="03">Federal rulemaking Web site:</E>Go to<E T="03">http://www.regulations.gov</E>and search for Docket ID NRC-2012-0319. Address questions about NRC dockets to Carol Gallagher; telephone: 301-492-3668; email:<E T="03">Carol.Gallagher@nrc.gov.</E>
          </P>
          <P>•<E T="03">Mail comments to:</E>Cindy Bladey, Chief, Rules, Announcements, and Directives Branch (RADB), Office of Administration, Mail Stop: TWB-05-B01M, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001.</P>
          <P>•<E T="03">Fax comments to:</E>RADB at 301-492-3446.</P>

          <P>For additional direction on accessing information and submitting comments, see “Accessing Information and Submitting Comments” in the<E T="02">SUPPLEMENTARY INFORMATION</E>section of this document.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Alan Wang, Project Manager, Plant Licensing Branch IV, Division of Operating Reactor Licensing, Office of Nuclear Reactor Regulation, U.S. Nuclear Regulatory Commission, Washington, DC 20555. Telephone: 301-415-1445; fax number: 301-415-2102; email:<E T="03">Alan.Wang@nrc.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Accessing Information and Submitting Comments</HD>
        <HD SOURCE="HD2">A. Accessing Information</HD>
        <P>Please refer to Docket ID NRC-2012-0319 when contacting the NRC about the availability of information regarding this document. You may access information related to this document, which the NRC possesses and are publicly available, by any of the following methods:</P>
        <P>•<E T="03">Federal Rulemaking Web Site:</E>Go to<E T="03">http://www.regulations.gov</E>and search for Docket ID NRC-2012-0319.</P>
        <P>•<E T="03">NRC's Agencywide Documents Access and Management System (ADAMS):</E>You may access publicly available documents online in the NRC Library at<E T="03">http://www.nrc.gov/reading-rm/adams.html.</E>To begin the search, select “<E T="03">ADAMS Public Documents</E>” and then select “<E T="03">Begin Web-based ADAMS Search.</E>” For problems with ADAMS, please contact the NRC's Public Document Room (PDR) reference staff at 1-800-397-4209, 301-415-4737, or by email to<E T="03">pdr.resource@nrc.gov.</E>The application dated September 27, 2012,<PRTPAGE P="326"/>is available electronically under ADAMS Accession No. ML12275A013.</P>
        <P>•<E T="03">NRC's PDR:</E>You may examine and purchase copies of public documents at the NRC's PDR, Room O1-F21, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852.</P>
        <HD SOURCE="HD2">B. Submitting Comments</HD>
        <P>Please include Docket ID NRC-2012-0319 in the subject line of your comment submission, in order to ensure that the NRC is able to make your comment submission available to the public in this docket.</P>

        <P>The NRC cautions you not to include identifying or contact information that you do not want to be publicly disclosed in your comment submission. The NRC will post all comment submissions at<E T="03">http://www.regulations.gov</E>as well as enter the comment submissions into ADAMS. The NRC does not routinely edit comment submissions to remove identifying or contact information.</P>
        <P>If you are requesting or aggregating comments from other persons for submission to the NRC, then you should inform those persons not to include identifying or contact information that they do not want to be publicly disclosed in their comment submission. Your request should state that the NRC does not routinely edit comment submissions to remove such information before making the comment submissions available to the public or entering the comment submissions into ADAMS.</P>
        <HD SOURCE="HD1">II. Introduction</HD>

        <P>The U.S. Nuclear Regulatory Commission (the Commission) is considering the issuance of an order under section 50.80 Title 10 of the<E T="03">Code of Federal Regulations (10 CFR)</E>approving the direct transfer of the Facility Operating License, NPF-29, for the Grand Gulf Nuclear Station, Unit 1 (GGNS), and associated Independent Spent Fuel Storage Installation, currently held by System Energy Resources, Inc. (SERI), and South Mississippi Electric Power Association, as owners and Entergy Operations, Inc. (EOI), as licensed operator of GGNS. The direct transfer of the GGNS license would be to a new limited liability company, System Energy Resource, LLC (SERL). According to an application for approval filed by EOI on behalf of SERI, SERL would acquire ownership of the facility previously owned by SERI following approval of the proposed license transfer. EOI would remain responsible for the operation and maintenance of GGNS. The Commission is also considering amending the license for administrative purposes to reflect the proposed direct transfer. The proposed amendment would replace references to SERI in the license with references to System Energy Resource, LLC, to reflect the proposed transfer. In addition, the proposed amendment would replace references to Entergy Mississippi, Inc., in the license with Entergy Mississippi, LLC. Entergy Mississippi, Inc., is referenced in the license, however, is not a licensee entity.</P>
        <P>In addition, the Commission is also considering approving the associated indirect license transfer to the extent such would be affected by a formation of a new intermediary holding company. According to an application for approval filed by EOI, on behalf of SERI, Entergy Corporation will remain as the ultimate parent company, but a new, intermediate company, Entergy Utilities Holdings, LLC, a Delaware limited liability company, will be created, which will be the direct parent company of SERL and EOI. SERL and South Mississippi Electric Power Association will own the facility and EOI will remain responsible for the operation and maintenance of GGNS.</P>
        <P>No physical changes to the GGNS facility or operational changes are being proposed in the application.</P>
        <P>Pursuant to 10 CFR 50.80, no license, or any right thereunder, shall be transferred, directly or indirectly, through transfer of control of the license, unless the Commission shall give its consent in writing. The Commission will approve an application for the direct transfer of a license, if the Commission determines that the proposed transferee is qualified to hold the license, and that the transfer is otherwise consistent with applicable provisions of law, regulations, and orders issued by the Commission pursuant thereto. The Commission will approve an application for the indirect transfer of a license, if the Commission determines that the proposed establishment of a new holding company will not affect the qualifications of the licensee to hold the license, and that the transfer is otherwise consistent with applicable provisions of law, regulations, and orders issued by the Commission pursuant thereto.</P>
        <P>Before issuance of the proposed conforming license amendment, the Commission will have made findings required by the Atomic Energy Act of 1954, as amended (the Act), and the Commission's regulations.</P>
        <P>As provided in 10 CFR 2.1315, unless otherwise determined by the Commission with regard to a specific application, the Commission has determined that any amendment to the license of a utilization facility which does no more than conform the license to reflect the transfer action involves no significant hazards consideration. No contrary determination has been made with respect to this specific license amendment application. In light of the generic determination reflected in 10 CFR 2.1315, no public comments with respect to significant hazards considerations are being solicited, notwithstanding the general comment procedures contained in 10 CFR 50.91.</P>
        <P>The filing of requests for hearing and petitions for leave to intervene, and written comments with regard to the license transfer application, are discussed below.</P>
        <HD SOURCE="HD1">III. Opportunity To Request a Hearing; Petition for Leave To Intervene</HD>

        <P>Within 20 days from the date of publication of this notice, any person(s) whose interest may be affected by the Commission's action on the application may request a hearing and intervention via electronic submission through the NRC's E-filing system. Requests for a hearing and petitions for leave to intervene should be filed in accordance with the Commission's rules of practice set forth in Subpart C “Rules of General Applicability: Hearing Requests, Petitions to Intervene, Availability of Documents, Selection of Specific Hearing Procedures, Presiding Officer Powers, and General Hearing Management for NRC Adjudicatory Hearings,” of 10 CFR Part 2. In particular, such requests and petitions must comply with the requirements set forth in 10 CFR 2.309, which is available at the NRC's PDR, located at O1F21, 11555 Rockville Pike (first floor), Rockville, Maryland 20852. The NRC regulations are accessible electronically from the NRC Library on the NRC's public Web site at<E T="03">http://www.nrc.gov/reading-rm/doc-collections/cfr/.</E>
        </P>

        <P>A State, local governmental body, Federally-recognized Indian Tribe, or agency thereof may submit a petition to the Commission to participate as a party under 10 CFR 2.309(h)(1) and (2). The petition should state the nature and extent of the petitioner's interest in the proceeding. The petition should be submitted to the Commission by January 23, 2013. The petition must be filed in accordance with the filing instructions in section IV of this document, and should meet the requirements for petitions for leave to intervene set forth in this section, except that under 2.309(h)(2) a State, local governmental body, or Federally-recognized Indian<PRTPAGE P="327"/>tribe does not need to address the standing requirements in 10 CFR 2.309(d) if the facility is located within its boundaries. A State, local governmental body, Federally-recognized Indian Tribe, or agency thereof may also have the opportunity to participate under 10 CFR 2.315(c).</P>
        <P>Requests for hearing, petitions for leave to intervene, and motions for leave to file new or amended contentions that are filed after the 20-day deadline will not be entertained absent a determination by the presiding officer that the filing demonstrates good cause by satisfying the following three factors in 10 CFR 2.309(c)(1): (i) The information upon which the filing is based was not previously available; (ii) the information upon which the filing is based is materially different from information previously available; and (iii) the filing has been submitted in a timely fashion based on the availability of the subsequent information.</P>
        <HD SOURCE="HD1">IV. Electronic Submissions (E-Filing)</HD>
        <P>All documents filed in NRC adjudicatory proceedings, including a request for hearing, a petition for leave to intervene, any motion or other document filed in the proceeding prior to the submission of a request for hearing or petition to intervene, and documents filed by interested governmental entities participating under 10 CFR 2.315(c), must be filed in accordance with the NRC's E-Filing rule (72 FR 49139; August 28, 2007). The E-Filing process requires participants to submit and serve all adjudicatory documents over the Internet, or in some cases to mail copies on electronic storage media. Participants may not submit paper copies of their filings unless they seek an exemption in accordance with the procedures described below.</P>

        <P>To comply with the procedural requirements of E-Filing, at least 10 days prior to the filing deadline, the participant should contact the Office of the Secretary by email at<E T="03">hearing.docket@nrc.gov,</E>or by telephone at 301-415-1677, to request (1) a digital identification (ID) certificate, which allows the participant (or its counsel or representative) to digitally sign documents and access the E-Submittal server for any proceeding in which it is participating; and (2) advise the Secretary that the participant will be submitting a request or petition for hearing (even in instances in which the participant, or its counsel or representative, already holds an NRC-issued digital ID certificate). Based upon this information, the Secretary will establish an electronic docket for the hearing in this proceeding if the Secretary has not already established an electronic docket.</P>

        <P>Information about applying for a digital ID certificate is available on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals/apply-certificates.html.</E>System requirements for accessing the E-Submittal server are detailed in the NRC's “Guidance for Electronic Submission,” which is available on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals.html.</E>Participants may attempt to use other software not listed on the Web site, but should note that the NRC's E-Filing system does not support unlisted software, and the NRC Meta System Help Desk will not be able to offer assistance in using unlisted software.</P>

        <P>If a participant is electronically submitting a document to the NRC in accordance with the E-Filing rule, the participant must file the document using the NRC's online, Web-based submission form. In order to serve documents through the Electronic Information Exchange System, users will be required to install a Web browser plug-in from the NRC's public Web site. Further information on the Web-based submission form, including the installation of the Web browser plug-in, is available on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals.html.</E>
        </P>

        <P>Once a participant has obtained a digital ID certificate and a docket has been created, the participant can then submit a request for hearing or petition for leave to intervene. Submissions should be in Portable Document Format (PDF) in accordance with NRC guidance available on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals.html.</E>A filing is considered complete at the time the documents are submitted through the NRC's E-Filing system. To be timely, an electronic filing must be submitted to the E-Filing system no later than 11:59 p.m. Eastern Time on the due date. Upon receipt of a transmission, the E-Filing system time-stamps the document and sends the submitter an email notice confirming receipt of the document. The E-Filing system also distributes an email notice that provides access to the document to the NRC's Office of the General Counsel and any others who have advised the Office of the Secretary that they wish to participate in the proceeding, so that the filer need not serve the documents on those participants separately. Therefore, applicants and other participants (or their counsel or representative) must apply for and receive a digital ID certificate before a hearing request/petition to intervene is filed so that they can obtain access to the document via the E-Filing system.</P>

        <P>A person filing electronically using the NRC's adjudicatory E-Filing system may seek assistance by contacting the NRC Meta System Help Desk through the “Contact Us” link located on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals.html,</E>by email to<E T="03">MSHD.Resource@nrc.gov,</E>or by a toll-free call to 1-866-672-7640. The NRC Meta System Help Desk is available between 8 a.m. and 8 p.m., Eastern Time, Monday through Friday, excluding government holidays.</P>
        <P>Participants who believe that they have a good cause for not submitting documents electronically must file an exemption request, in accordance with 10 CFR 2.302(g), with their initial paper filing requesting authorization to continue to submit documents in paper format. Such filings must be submitted by: (1) First class mail addressed to the Office of the Secretary of the Commission, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, Attention: Rulemaking and Adjudications Staff; or (2) courier, express mail, or expedited delivery service to the Office of the Secretary, Sixteenth Floor, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852, Attention: Rulemaking and Adjudications Staff. Participants filing a document in this manner are responsible for serving the document on all other participants. Filing is considered complete by first-class mail as of the time of deposit in the mail, or by courier, express mail, or expedited delivery service upon depositing the document with the provider of the service. A presiding officer, having granted an exemption request from using E-Filing, may require a participant or party to use E-Filing if the presiding officer subsequently determines that the reason for granting the exemption from use of E-Filing no longer exists.</P>

        <P>Documents submitted in adjudicatory proceedings will appear in NRC's electronic hearing docket which is available to the public at<E T="03">http://ehd1.nrc.gov/ehd/,</E>unless excluded pursuant to an order of the Commission, or the presiding officer. Participants are requested not to include personal privacy information, such as social security numbers, home addresses, or home phone numbers in their filings, unless an NRC regulation or other law requires submission of such information. With respect to copyrighted works, except for limited<PRTPAGE P="328"/>excerpts that serve the purpose of the adjudicatory filings and would constitute a Fair Use application, participants are requested not to include copyrighted materials in their submission.</P>

        <P>The Commission will issue a notice or order granting or denying a hearing request or intervention petition, designating the issues for any hearing that will be held and designating the Presiding Officer. A notice granting a hearing will be published in the<E T="04">Federal Register</E>and served on the parties to the hearing.</P>

        <P>Within 30 days from the date of publication of this notice, persons may submit written comments regarding the license transfer application, as provided for in 10 CFR 2.1305. The Commission will consider and, if appropriate, respond to these comments, but such comments will not otherwise constitute part of the decisional record. Comments should be submitted to the Secretary, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, Attention: Rulemakings and Adjudications Staff, and should cite the publication date and page number of this<E T="04">Federal Register</E>notice.</P>
        <P>For further details with respect to this application, see the application dated September 27, 2012.</P>
        <SIG>
          <DATED>Dated at Rockville, Maryland, this 21st day of December 2012.</DATED>
          
          <P>For the Nuclear Regulatory Commission.</P>
          <NAME>Nageswaran Kalyanam,</NAME>
          <TITLE>Project Manager, Plant Licensing Branch IV, Division of Operating Reactor Licensing, Office of Nuclear Reactor Regulation.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31615 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 7590-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION</AGENCY>
        <DEPDOC>[Docket Nos. 50-313 and 50-368; NRC-2012-0320]</DEPDOC>
        <SUBJECT>Consideration of Approval of Application Regarding Proposed Creation of a Holding Company and Transfer of Renewed Facility Operating Licenses and Conforming Amendments and Opportunity for a Hearing; Arkansas Nuclear One, Units 1 and 2</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Nuclear Regulatory Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Request for license transfer; opportunity to comment; opportunity to request a hearing and petition for leave to intervene.</P>
        </ACT>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be filed by February 4, 2013. A request for a hearing must be filed by January 23, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>You many access information and comment submissions related to this document, which the NRC possesses and are publicly available, by searching on<E T="03">http://www.regulations.gov</E>under Docket ID NRC-2012-0320. You may submit comments by any of the following methods:</P>
          <P>•<E T="03">Federal rulemaking Web site:</E>Go to<E T="03">http://www.regulations.gov</E>and search for Docket ID NRC-2012-0320. Address questions about NRC dockets to Carol Gallagher; telephone: 301-492-3668; email:<E T="03">Carol.Gallagher@nrc.gov.</E>
          </P>
          <P>•<E T="03">Mail comments to:</E>Cindy Bladey, Chief, Rules, Announcements, and Directives Branch (RADB), Office of Administration, Mail Stop: TWB-05-B01M, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001.</P>
          <P>•<E T="03">Fax comments to:</E>RADB at 301-492-3446.</P>

          <P>For additional direction on accessing information and submitting comments, see “Accessing Information and Submitting Comments” in the<E T="02">SUPPLEMENTARY INFORMATION</E>section of this document.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Alan Wang, Project Manager, Plant Licensing Branch IV, Division of Operating Reactor Licensing, Office of Nuclear Reactor Regulation, U.S. Nuclear Regulatory Commission, Washington, DC 20555. Telephone: 301-415-1445; fax number: 301-415-2102; email:<E T="03">Alan.Wang@nrc.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Accessing Information and Submitting Comments</HD>
        <HD SOURCE="HD2">A. Accessing Information</HD>
        <P>Please refer to Docket ID NRC-2012-0320 when contacting the NRC about the availability of information regarding this document. You may access information related to this document, which the NRC possesses and are publicly available, by any of the following methods:</P>
        <P>•<E T="03">Federal Rulemaking Web Site:</E>Go to<E T="03">http://www.regulations.gov</E>and search for Docket ID NRC-2012-0320.</P>
        <P>•<E T="03">NRC's Agencywide Documents Access and Management System (ADAMS):</E>You may access publicly available documents online in the NRC Library at<E T="03">http://www.nrc.gov/reading-rm/adams.html.</E>To begin the search, select “<E T="03">ADAMS Public Documents</E>” and then select “<E T="03">Begin Web-based ADAMS Search</E>.” For problems with ADAMS, please contact the NRC's Public Document Room (PDR) reference staff at 1-800-397-4209, 301-415-4737, or by email to<E T="03">pdr.resource@nrc.gov.</E>The application dated September 27, 2012, is available electronically under ADAMS Accession No. ML12275A013.</P>
        <P>•<E T="03">NRC's PDR:</E>You may examine and purchase copies of public documents at the NRC's PDR, Room O1-F21, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852.</P>
        <HD SOURCE="HD2">B. Submitting Comments</HD>
        <P>Please include Docket ID NRC-2012-0320 in the subject line of your comment submission, in order to ensure that the NRC is able to make your comment submission available to the public in this docket.</P>

        <P>The NRC cautions you not to include identifying or contact information that you do not want to be publicly disclosed in you comment submission. The NRC will post all comment submissions at<E T="03">http://www.regulations.gov</E>as well as enter the comment submissions into ADAMS. The NRC does not routinely edit comment submissions to remove identifying or contact information.</P>
        <P>If you are requesting or aggregating comments from other persons for submission to the NRC, then you should inform those persons not to include identifying or contact information that they do not want to be publicly disclosed in their comment submission. Your request should state that the NRC does not routinely edit comment submissions to remove such information before making the comment submissions available to the public or entering the comment submissions into ADAMS.</P>
        <HD SOURCE="HD1">II. Introduction</HD>

        <P>The U.S. Nuclear Regulatory Commission (the Commission) is considering the issuance of an order under section 50.80 of Title 10 of the<E T="03">Code of Federal Regulations</E>(10 CFR) approving the direct transfer of the Renewed Facility Operating Licenses, which are numbered DPR-51 and NPF-6, for the Arkansas Nuclear One, Units 1 and 2 (ANO-1, ANO-2), and associated Independent Spent Fuel Storage Installation, currently held by Entergy Arkansas, Inc. (EAI), as owner and Entergy Operations, Inc. (EOI), as licensed operator of ANO-1 and ANO-2. The direct transfer of the ANO-1 and ANO-2 licenses would be to a new limited liability company, Entergy Arkansas, LLC (EAL). According to an application for approval filed by EOI on behalf of EAI, EAL would acquire ownership of the facility following approval of the proposed license<PRTPAGE P="329"/>transfer. EOI would remain responsible for the operation and maintenance of ANO-1 and ANO-2. The Commission is also considering amending the license for administrative purposes to reflect the proposed direct transfer. The proposed amendment would replace references to EAI in the license with references to Entergy Arkansas, LLC, to reflect the proposed transfer.</P>
        <P>In addition, the Commission is also considering approving associated indirect license transfers to the extent such would be affected by a formation of a new intermediary holding company. According to an application for approval filed by EOI, on behalf of EAI, Entergy Corporation will remain as the ultimate parent company, but a new, intermediate company, Entergy Utilities Holdings, LLC, a Delaware limited liability company, will be created, which will be the direct parent company of EAL and EOI. EAL will own the facility and EOI would remain responsible for the operation and maintenance of ANO-1 and ANO-2.</P>
        <P>No physical changes to the ANO-1 and ANO-2 facility or operational changes are being proposed in the application.</P>
        <P>Pursuant to 10 CFR 50.80, no license, or any right thereunder, shall be transferred, directly or indirectly, through transfer of control of the license, unless the Commission shall give its consent in writing. The Commission will approve an application for the direct transfer of a license, if the Commission determines that the proposed transferee is qualified to hold the license, and that the transfer is otherwise consistent with applicable provisions of law, regulations, and orders issued by the Commission pursuant thereto. The Commission will approve an application for the indirect transfer of a license, if the Commission determines that the proposed establishment of a new holding company will not affect the qualifications of the licensee to hold the license, and that the transfer is otherwise consistent with applicable provisions of law, regulations, and orders issued by the Commission pursuant thereto.</P>
        <P>Before issuance of the proposed conforming license amendment, the Commission will have made findings required by the Atomic Energy Act of 1954, as amended (the Act), and the Commission's regulations.</P>
        <P>As provided in 10 CFR 2.1315, unless otherwise determined by the Commission with regard to a specific application, the Commission has determined that any amendment to the license of a utilization facility which does no more than conform the license to reflect the transfer action involves no significant hazards consideration. No contrary determination has been made with respect to this specific license amendment application. In light of the generic determination reflected in 10 CFR 2.1315, no public comments with respect to significant hazards considerations are being solicited, notwithstanding the general comment procedures contained in 10 CFR 50.91.</P>
        <P>The filing of requests for hearing and petitions for leave to intervene, and written comments with regard to the license transfer application, are discussed below.</P>
        <HD SOURCE="HD1">III. Opportunity To Request a Hearing; Petition for Leave To Intervene</HD>

        <P>Within 20 days from the date of publication of this notice, any person(s) whose interest may be affected by the Commission's action on the application may request a hearing and intervention via electronic submission through the NRC's E-filing system. Requests for a hearing and petitions for leave to intervene should be filed in accordance with the Commission's rules of practice set forth in Subpart C “Rules of General Applicability: Hearing Requests, Petitions to Intervene, Availability of Documents, Selection of Specific Hearing Procedures, Presiding Officer Powers, and General Hearing Management for NRC Adjudicatory Hearings,” of 10 CFR part 2. In particular, such requests and petitions must comply with the requirements set forth in 10 CFR 2.309, which is available at the NRC's PDR, located at O1F21, 11555 Rockville Pike (first floor), Rockville, Maryland 20852. The NRC regulations are accessible electronically from the NRC Library on the NRC's public Web site at<E T="03">http://www.nrc.gov/reading-rm/doc-collections/cfr/.</E>
        </P>
        <P>A State, local governmental body, Federally-recognized Indian Tribe, or agency thereof may submit a petition to the Commission to participate as a party under 10 CFR 2.309(h)(1) and (2). The petition should state the nature and extent of the petitioner's interest in the proceeding. The petition should be submitted to the Commission by January 23, 2013. The petition must be filed in accordance with the filing instructions in section IV of this document, and should meet the requirements for petitions for leave to intervene set forth in this section, except that under 2.309(h)(2) a State, local governmental body, or Federally-recognized Indian tribe does not need to address the standing requirements in 10 CFR 2.309(d) if the facility is located within its boundaries. A State, local governmental body, Federally-recognized Indian Tribe, or agency thereof may also have the opportunity to participate under 10 CFR 2.315(c).</P>
        <P>Requests for hearing, petitions for leave to intervene, and motions for leave to file new or amended contentions that are filed after the 20-day deadline will not be entertained absent a determination by the presiding officer that the filing demonstrates good cause by satisfying the following three factors in 10 CFR 2.309(c)(1): (i) The information upon which the filing is based was not previously available; (ii) the information upon which the filing is based is materially different from information previously available; and (iii) the filing has been submitted in a timely fashion based on the availability of the subsequent information.</P>
        <HD SOURCE="HD1">IV. Electronic Submissions (E-Filing)</HD>
        <P>All documents filed in NRC adjudicatory proceedings, including a request for hearing, a petition for leave to intervene, any motion or other document filed in the proceeding prior to the submission of a request for hearing or petition to intervene, and documents filed by interested governmental entities participating under 10 CFR 2.315(c), must be filed in accordance with the NRC's E-Filing rule (72 FR 49139; August 28, 2007). The E-Filing process requires participants to submit and serve all adjudicatory documents over the internet, or in some cases to mail copies on electronic storage media. Participants may not submit paper copies of their filings unless they seek an exemption in accordance with the procedures described below.</P>

        <P>To comply with the procedural requirements of E-Filing, at least 10 days prior to the filing deadline, the participant should contact the Office of the Secretary by email at<E T="03">hearing.docket@nrc.gov,</E>or by telephone at 301-415-1677, to request (1) a digital identification (ID) certificate, which allows the participant (or its counsel or representative) to digitally sign documents and access the E-Submittal server for any proceeding in which it is participating; and (2) advise the Secretary that the participant will be submitting a request or petition for hearing (even in instances in which the participant, or its counsel or representative, already holds an NRC-issued digital ID certificate). Based upon this information, the Secretary will establish an electronic docket for the hearing in this proceeding if the Secretary has not already established an electronic docket.<PRTPAGE P="330"/>
        </P>

        <P>Information about applying for a digital ID certificate is available on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals/apply-certificates.html.</E>System requirements for accessing the E-Submittal server are detailed in the NRC's “Guidance for Electronic Submission,” which is available on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals.html.</E>Participants may attempt to use other software not listed on the Web site, but should note that the NRC's E-Filing system does not support unlisted software, and the NRC Meta System Help Desk will not be able to offer assistance in using unlisted software.</P>

        <P>If a participant is electronically submitting a document to the NRC in accordance with the E-Filing rule, the participant must file the document using the NRC's online, Web-based submission form. In order to serve documents through the Electronic Information Exchange System, users will be required to install a Web browser plug-in from the NRC's public Web site. Further information on the Web-based submission form, including the installation of the Web browser plug-in, is available on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals.html.</E>
        </P>

        <P>Once a participant has obtained a digital ID certificate and a docket has been created, the participant can then submit a request for hearing or petition for leave to intervene. Submissions should be in Portable Document Format (PDF) in accordance with NRC guidance available on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals.html.</E>A filing is considered complete at the time the documents are submitted through the NRC's E-Filing system. To be timely, an electronic filing must be submitted to the E-Filing system no later than 11:59 p.m. Eastern Time on the due date. Upon receipt of a transmission, the E-Filing system time-stamps the document and sends the submitter an email notice confirming receipt of the document. The E-Filing system also distributes an email notice that provides access to the document to the NRC's Office of the General Counsel and any others who have advised the Office of the Secretary that they wish to participate in the proceeding, so that the filer need not serve the documents on those participants separately. Therefore, applicants and other participants (or their counsel or representative) must apply for and receive a digital ID certificate before a hearing request/petition to intervene is filed so that they can obtain access to the document via the E-Filing system.</P>

        <P>A person filing electronically using the NRC's adjudicatory E-Filing system may seek assistance by contacting the NRC Meta System Help Desk through the “Contact Us” link located on the NRC's public Web site at<E T="03">http://www.nrc.gov/site-help/e-submittals.html,</E>by email to<E T="03">MSHD.Resource@nrc.gov,</E>or by a toll-free call to 1-866-672-7640. The NRC Meta System Help Desk is available between 8 a.m. and 8 p.m., Eastern Time, Monday through Friday, excluding government holidays.</P>
        <P>Participants who believe that they have a good cause for not submitting documents electronically must file an exemption request, in accordance with 10 CFR 2.302(g), with their initial paper filing requesting authorization to continue to submit documents in paper format. Such filings must be submitted by: (1) first class mail addressed to the Office of the Secretary of the Commission, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, Attention: Rulemaking and Adjudications Staff; or (2) courier, express mail, or expedited delivery service to the Office of the Secretary, Sixteenth Floor, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852, Attention: Rulemaking and Adjudications Staff. Participants filing a document in this manner are responsible for serving the document on all other participants. Filing is considered complete by first-class mail as of the time of deposit in the mail, or by courier, express mail, or expedited delivery service upon depositing the document with the provider of the service. A presiding officer, having granted an exemption request from using E-Filing, may require a participant or party to use E-Filing if the presiding officer subsequently determines that the reason for granting the exemption from use of E-Filing no longer exists.</P>

        <P>Documents submitted in adjudicatory proceedings will appear in NRC's electronic hearing docket which is available to the public at<E T="03">http://ehd1.nrc.gov/ehd/,</E>unless excluded pursuant to an order of the Commission, or the presiding officer. Participants are requested not to include personal privacy information, such as social security numbers, home addresses, or home phone numbers in their filings, unless an NRC regulation or other law requires submission of such information. With respect to copyrighted works, except for limited excerpts that serve the purpose of the adjudicatory filings and would constitute a Fair Use application, participants are requested not to include copyrighted materials in their submission.</P>

        <P>The Commission will issue a notice or order granting or denying a hearing request or intervention petition, designating the issues for any hearing that will be held and designating the Presiding Officer. A notice granting a hearing will be published in the<E T="04">Federal Register</E>and served on the parties to the hearing.</P>

        <P>Within 30 days from the date of publication of this notice, persons may submit written comments regarding the license transfer application, as provided for in 10 CFR 2.1305. The Commission will consider and, if appropriate, respond to these comments, but such comments will not otherwise constitute part of the decisional record. Comments should be submitted to the Secretary, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, Attention: Rulemakings and Adjudications Staff, and should cite the publication date and page number of this<E T="04">Federal Register</E>notice.</P>
        <P>For further details with respect to this application, see the application dated September 27, 2012.</P>
        <SIG>
          <DATED>Dated at Rockville, Maryland, this 21st day of December 2012.</DATED>
          
          <P>For the Nuclear Regulatory Commission.</P>
          <NAME>Nageswaran Kalyanam,</NAME>
          <TITLE>Project Manager, Plant Licensing Branch IV, Division of Operating Reactor Licensing, Office of Nuclear Reactor Regulation.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31614 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 7590-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
        <DEPDOC>[Release No. 34-68540; File No. SR-ICEEU-2012-18]</DEPDOC>
        <SUBJECT>Self-Regulatory Organizations; ICE Clear Europe Limited; Notice of Filing and Immediate Effectiveness of Proposed Rule Change To Amend SPAN Margin Parameters for ICE OTC Natural Gas Liquids Contracts</SUBJECT>
        <DATE>December 27, 2012.</DATE>
        <P>Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”),<SU>1</SU>
          <FTREF/>and Rule 19b-4 thereunder,<SU>2</SU>

          <FTREF/>notice is hereby given that on December 19, 2012, ICE Clear Europe Limited (“ICE Clear Europe”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I, II and III below, which Items have been prepared<PRTPAGE P="331"/>primarily by ICE Clear Europe. ICE Clear Europe filed the proposal pursuant to Section 19(b)(3)(A)(iii) of the Act,<SU>3</SU>
          <FTREF/>and Rule 19b-4(f)(4)(ii) thereunder,<SU>4</SU>
          <FTREF/>so that the proposal was effective upon filing with the Commission. The Commission is publishing this notice to solicit comments on the proposed change from interested persons.</P>
        <FTNT>
          <P>
            <SU>1</SU>15 U.S.C. 78s(b)(1).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>2</SU>17 CFR 240.19b-4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>3</SU>15 U.S.C. 78s(b)(3)(A)(iii).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>4</SU>17 CFR 240.19b-4(f)(4)(ii).</P>
        </FTNT>
        <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
        <P>The purpose of the change is to amend SPAN Margin Parameters for ICE OTC Natural Gas Liquids (NGL) Contracts. All capitalized terms not defined herein are defined in the ICE Clear Europe Rules.</P>
        <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
        <P>In its filing with the Commission, ICE Clear Europe included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. ICE Clear Europe has prepared summaries, set forth in sections A, B, and C below, of the most significant aspects of these statements.<SU>5</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>5</SU>The Commission has modified the text of the summaries prepared by ICE Clear Europe.</P>
        </FTNT>
        <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
        <P>In addition to providing clearing services for credit default swaps, ICE Clear Europe also provides clearing services for non-securities contracts in energy and emissions markets (“Energy Futures Products”). SPAN®<SU>6</SU>

          <FTREF/>is a risk evaluation and margin framework algorithm employed to calculate Original Margin for certain Energy Futures Products. As of September 20, 2011, ICE Clear Europe changed the SPAN margin parameters for ICE OTC NGL Contracts. All updated SPAN® margin parameters can be found at:<E T="03">https://www.theice.com/clear_europe_span_parameters.jhtml</E>.</P>
        <FTNT>
          <P>
            <SU>6</SU>SPAN is a registered trademark of Chicago Mercantile Exchange Inc., used herein under license. Chicago Mercantile Exchange Inc. assumes no responsibility in connection with the use of SPAN by any person or entity.</P>
        </FTNT>
        <P>Section 17A(b)(3)(F) of the Act<SU>7</SU>
          <FTREF/>requires, among other things, that the rules of a clearing agency be designed to promote the prompt and accurate clearance and settlement of securities transactions and, to the extent applicable, derivative agreements, contracts, and transactions. ICE Clear Europe believes that the proposed change with respect to Energy Futures Products is consistent with the requirements of the Act and the rules and regulations thereunder applicable to ICE Clear Europe, in particular, with Section 17A(b)(3)(F),<SU>8</SU>
          <FTREF/>because improved margining of NGL contracts protects investors and the public interest.</P>
        <FTNT>
          <P>
            <SU>7</SU>15 U.S.C. 78q-1(b)(3)(F).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>8</SU>15 U.S.C. 78q-1(b)(3)(F).</P>
        </FTNT>
        <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
        <P>ICE Clear Europe does not believe the proposed change would have any impact, or impose any burden, on competition.</P>
        <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants or Others</HD>
        <P>Written comments relating to the proposed change have not been solicited or received. ICE Clear Europe will notify the Commission of any written comments received by ICE Clear Europe.</P>
        <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
        <P>The foregoing rule change has become effective upon filing pursuant to Section 19(b)(3)(A)(iii) of the Act<SU>9</SU>
          <FTREF/>and Rule 19b-4(f)(4)(ii)<SU>10</SU>
          <FTREF/>thereunder because it primarily affects the futures clearing operations of the clearing agency with respect to futures that are not security futures, and does not significantly affect any securities clearing operations of the clearing agency or any related rights or obligations of the clearing agency or persons using such service. At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act.<SU>11</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>9</SU>15 U.S.C. 78s(b)(3)(A)(iii).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>10</SU>17 CFR 240.19b-4(f)(4)(ii).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>11</SU>15 U.S.C. 78s(b)(3)(C).</P>
        </FTNT>
        <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
        <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
        <HD SOURCE="HD2">Electronic Comments</HD>
        <P>• Use the Commission's Internet comment form (<E T="03">http://www.sec.gov/rules/sro.shtml</E>) or</P>
        <P>• Send an email to<E T="03">rule-comments@sec.gov.</E>Please include File Number SR-ICEEU-2012-18 on the subject line.</P>
        <HD SOURCE="HD2">Paper Comments</HD>
        <P>• Send paper comments in triplicate to Elizabeth M. Murphy, Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.</P>
        

        <FP>All submissions should refer to File Number SR-ICEEU-2012-18. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (<E T="03">http://www.sec.gov/rules/sro.shtml</E>). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for Web site viewing and printing in the Commission's Public Reference Room, 100 F Street NE., Washington, DC 20549, on official business days between the hours of 10:00 a.m. and 3:00 p.m. Copies of such filings will also be available for inspection and copying at the principal office of ICE Clear Europe and on ICE Clear Europe's Web site at<E T="03">https://www.theice.com/publicdocs/regulatory_filings/ICEU_SEC_121912_2012-18.pdf</E>.</FP>
        <P>All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-ICEEU-2012-18 and should be submitted on or before January 24, 2013.</P>
        <SIG>
          <PRTPAGE P="332"/>
          <P>For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.<SU>12</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>12</SU>17 CFR 200.30-3(a)(12).</P>
          </FTNT>
          <NAME>Elizabeth M. Murphy,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31568 Filed 1-2-13; 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-68542; File No. SR-ICEEU-2012-20]</DEPDOC>
        <SUBJECT>Self-Regulatory Organizations; ICE Clear Europe Limited; Notice of Filing and Immediate Effectiveness of Proposed Rule Change Related to SPAN Margin Methodology Enhancements to Inter-Contract Credits and Average Option Pricing Model for Energy Clearing Members</SUBJECT>
        <DATE>December 27, 2012.</DATE>
        <P>Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”),<SU>1</SU>
          <FTREF/>and Rule 19b-4 thereunder,<SU>2</SU>
          <FTREF/>notice is hereby given that on December 19, 2012, ICE Clear Europe Limited (“ICE Clear Europe”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I, II and III below, which Items have been prepared primarily by ICE Clear Europe. ICE Clear Europe filed the proposal pursuant to Section 19(b)(3)(A)(iii) of the Act,<SU>3</SU>
          <FTREF/>and Rule 19b-4(f)(4)(ii) thereunder,<SU>4</SU>
          <FTREF/>so that the proposal was effective upon filing with the Commission. The Commission is publishing this notice to solicit comments on the proposed change from interested persons.</P>
        <FTNT>
          <P>
            <SU>1</SU>15 U.S.C. 78s(b)(1).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>2</SU>17 CFR 240.19b-4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>3</SU>15 U.S.C. 78s(b)(3)(A)(iii).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>4</SU>17 CFR 240.19b-4(f)(4)(ii).</P>
        </FTNT>
        <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
        <P>The purpose of the change is to implement changes to the SPAN® for ICE Margining algorithm employed to calculate Original Margin (“Margin”) on Clearing Member positions. All capitalized terms not defined herein are defined in the ICE Clear Europe Rules.</P>
        <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
        <P>In its filing with the Commission, ICE Clear Europe included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. ICE Clear Europe has prepared summaries, set forth in sections A, B, and C below, of the most significant aspects of these statements.<SU>5</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>5</SU>The Commission has modified the text of the summaries prepared by ICE Clear Europe.</P>
        </FTNT>
        <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
        <P>In addition to providing clearing services for credit default swaps, ICE Clear Europe also provides clearing services for non-securities contracts in energy and emissions markets (“Energy Futures Products”). Position Allocation Methodology is an enhancement to the SPAN®<SU>6</SU>
          <FTREF/>for the ICE Margining algorithm employed to calculate Original Margin for certain Energy Futures Products. This feature is applied for certain Energy Futures Products where the position in such a product can be better represented as one or more positions in alternate products for the purposes of calculating Original Margin. This Position Allocation Methodology will result in new enhanced positions, but the SPAN margin calculation algorithm itself has not been changed. These changes will impact both the algorithm employed and the format of SPAN for ICE Array Files (“SPAN Array Files”) published by ICE Clear Europe and will necessitate changes to the applications used by Energy Clearing Members to calculate margin on their Proprietary and Customer positions. ICE Clear Europe has updated the original technical specification, at the request of Clearing Members, in order to provide further clarification and examples relating to implementation of Volatility Credit.</P>
        <FTNT>
          <P>
            <SU>6</SU>SPAN is a registered trademark of Chicago Mercantile Exchange Inc., used herein under license. Chicago Mercantile Exchange Inc. assumes no responsibility in connection with the use of SPAN by any person or entity. SPAN is a risk evaluation and margin framework algorithm.</P>
        </FTNT>
        <P>As of April 2, 2012, a change to the calculation of the inter-contract credit that implements an additional credit, the Volatility Credit, was made. The change to the Inter-Contract Credit algorithm yields an additional credit that is included in the existing inter-contract credit. Since April 2, 2012, the SPAN Arrays published by ICE Clear Europe include the Volatility Risk Credit Rate (the Offset Rate) within the type 14 records.</P>
        <P>Since March 30 2012, the Volatility Credit is introduced in respect of the following SPAN Combined Contract pairings:</P>
        <P>• BRN/BSP, Brent Futures/Brent Option vs. Brent First Line Swap/Brent Average Price Option.</P>
        <P>• GAS/GSP, Gas Oil Futures/Gas Oil Option vs. Gas Oil Front Line Swap/Gas Oil Average Price Option.</P>
        <P>• ULS/ULA, Low-Sulphur Gas Oil Futures/Low Sulphur Gas Oil Option vs. Low Sulphur Gas Oil Front Line Swap/Low-Sulphur Gas Oil Average Price Option.</P>
        <P>• WBS/WSP, WTI Future/WTI Option vs. WTI First Line Swap/WTI Average Price Option.</P>
        <P>Going forward, ICE Clear Europe will notify Clearing Members of the applicable Volatility Credit rates in due course. Inter-contract spreads in respect of all other products are unaffected.</P>
        <P>At end of day on April 6, 2012, the Clearing House enabled the Average Price Option model for Options on Brent, Gas Oil, Low-Sulphur Gas Oil and WTI First Line Swaps (Commodity Codes I, GSP, ULA and R).</P>
        <P>As of April 9, 2012, a modified Black 76 pricing model has been used to determine scanning losses in respect of Average Price Options. This model reflects the risk reduction inherent within these options during the averaging period prior to final settlement. This change has no impact on Clearing Member systems as this change is reflected within the SPAN Array Files and requires no changes to any software or algorithms within the SPAN methodology.</P>
        <P>All updated SPAN® margin parameters can be found at:<E T="03">https://www.theice.com/clear_europe_span_parameters.jhtml.</E>
        </P>
        <P>ICE Clear Europe has also published test SPAN Array Files conforming to the new SPAN Array File Format, v2.5, which incorporates credit rates in respect of the product pairings identified above. The test files are available from the file download service (AFTS) and are located in the “/test” sub-directory of the standard SPAN Array download location on AFTS.</P>
        <P>These files are named according to the test file naming convention below:</P>
        <P>IPEmmddT.csv.zip or IPEmmddT.sp5.zip, where,</P>
        <P>• mmdd represents the business month and day;</P>
        <P>• The sp5 file is of the same format as the pa5 format file that Members might download from the CME ftp site.</P>
        <P>Section 17A(b)(3)(F) of the Act<SU>7</SU>

          <FTREF/>requires, among other things, that the rules of a clearing agency be designed to promote the prompt and accurate<PRTPAGE P="333"/>clearance and settlement of securities transactions and, to the extent applicable, derivative agreements, contracts, and transactions. ICE Clear Europe believes that the proposed change with respect to Energy Futures Products is consistent with the requirements of the Act and the rules and regulations thereunder applicable to ICE Clear Europe, in particular, with Section 17A(b)(3)(F),<SU>8</SU>
          <FTREF/>because improved margining protects investors and the public interest.</P>
        <FTNT>
          <P>
            <SU>7</SU>15 U.S.C. 78q-1(b)(3)(F).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>8</SU>15 U.S.C. 78q-1(b)(3)(F).</P>
        </FTNT>
        <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
        <P>ICE Clear Europe does not believe the proposed change would have any impact, or impose any burden, on competition.</P>
        <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants or Others</HD>
        <P>Written comments relating to the proposed change have not been solicited or received. ICE Clear Europe will notify the Commission of any written comments received by ICE Clear Europe.</P>
        <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
        <P>The foregoing rule change has become effective upon filing pursuant to Section 19(b)(3)(A)(iii) of the Act<SU>9</SU>
          <FTREF/>and Rule 19b-4(f)(4)(ii)<SU>10</SU>
          <FTREF/>thereunder because it primarily affects the futures clearing operations of the clearing agency with respect to futures that are not security futures, and does not significantly affect any securities clearing operations of the clearing agency or any related rights or obligations of the clearing agency or persons using such service. At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act.<SU>11</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>9</SU>15 U.S.C. 78s(b)(3)(A)(iii).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>10</SU>17 CFR 240.19b-4(f)(4)(ii).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>11</SU>15 U.S.C. 78s(b)(3)(C).</P>
        </FTNT>
        <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
        <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
        <HD SOURCE="HD2">Electronic Comments</HD>
        <P>• Use the Commission's Internet comment form (<E T="03">http://www.sec.gov/rules/sro.shtml</E>) or</P>
        <P>• Send an email to<E T="03">rule-comments@sec.gov.</E>Please include File Number SR-ICEEU-2012-20 on the subject line.</P>
        <HD SOURCE="HD2">Paper Comments</HD>
        <P>• Send paper comments in triplicate to Elizabeth M. Murphy, Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.</P>
        

        <FP>All submissions should refer to File Number SR-ICEEU-2012-20. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (<E T="03">http://www.sec.gov/rules/sro.shtml</E>). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for Web site viewing and printing in the Commission's Public Reference Room, 100 F Street NE., Washington, DC 20549, on official business days between the hours of 10:00 a.m. and 3:00 p.m. Copies of such filings will also be available for inspection and copying at the principal office of ICE Clear Europe and on ICE Clear Europe's Web site at<E T="03">https://www.theice.com/publicdocs/regulatory_filings/ICEU_SEC_121912_2012-20.pdf.</E>
        </FP>
        <P>All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-ICEEU-2012-20 and should be submitted on or before January 24, 2013.</P>
        <SIG>
          <P>For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.<SU>12</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>12</SU>17 CFR 200.30-3(a)(12).</P>
          </FTNT>
          <NAME>Elizabeth M. Murphy,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31570 Filed 1-2-13; 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-68541; File No. SR-ICEEU-2012-19]</DEPDOC>
        <SUBJECT>Self-Regulatory Organizations; ICE Clear Europe Limited; Notice of Filing and Immediate Effectiveness of Proposed Rule Change Related to Delivery Margin Rates for Physically Deliverable Contracts for Energy Clearing Members</SUBJECT>
        <DATE>December 27, 2012.</DATE>
        <P>Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”),<SU>1</SU>
          <FTREF/>and Rule 19b-4 thereunder,<SU>2</SU>
          <FTREF/>notice is hereby given that on December 19, 2012, ICE Clear Europe Limited (“ICE Clear Europe”) filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I, II and III below, which Items have been prepared primarily by ICE Clear Europe. ICE Clear Europe filed the proposal pursuant to Section 19(b)(3)(A)(iii) of the Act,<SU>3</SU>
          <FTREF/>and Rule 19b-4(f)(4)(ii) thereunder,<SU>4</SU>
          <FTREF/>so that the proposal was effective upon filing with the Commission. The Commission is publishing this notice to solicit comments on the proposed change from interested persons.</P>
        <FTNT>
          <P>
            <SU>1</SU>15 U.S.C. 78s(b)(1).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>2</SU>17 CFR 240.19b-4.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>3</SU>15 U.S.C. 78s(b)(3)(A)(iii).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>4</SU>17 CFR 240.19b-4(f)(4)(ii).</P>
        </FTNT>
        <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>
        <P>The purpose of the change is to implement enhancements to the margining of physically deliverable positions that have expired and are in tender/delivery. The new delivery margin rates and contingent variation margin price sources have been proposed by ICE Clear Europe. All capitalized terms not defined herein are defined in the ICE Clear Europe Rules.</P>
        <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>

        <P>In its filing with the Commission, ICE Clear Europe included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. ICE Clear Europe has prepared summaries, set forth in sections A, B, and C below,<PRTPAGE P="334"/>of the most significant aspects of these statements.<SU>5</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>5</SU>The Commission has modified the text of the summaries prepared by ICE Clear Europe.</P>
        </FTNT>
        <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>

        <P>In addition to providing clearing services for credit default swaps, ICE Clear Europe also provides clearing services for non-securities contracts in energy and emissions markets (“Energy Futures Products”). ICE Clear Europe implemented enhancements to the margining of physically deliverable positions for certain Energy Futures Products that have expired and are in tender/delivery. In doing so, ICE Clear Europe has eliminated the use of SPAN for calculating margin for physically-deliverable positions and instead replaced it with calculation of a separate Delivery Margin for certain Energy Futures Products. The Delivery Margin parameters can be found at<E T="03">https://www.theice.com/ClearEuropeSpanParameterFiles.shtml</E>in the Deliverable Contracts Security Rates file. All of the SPAN®<SU>6</SU>
          <FTREF/>margin parameters for positions that are not in tender/delivery remain unchanged.</P>
        <FTNT>
          <P>
            <SU>6</SU>SPAN is a registered trademark of Chicago Mercantile Exchange Inc., used herein under license. Chicago Mercantile Exchange Inc. assumes no responsibility in connection with the use of SPAN by any person or entity. SPAN is a risk evaluation and margin framework algorithm.</P>
        </FTNT>
        <P>Data from the sources referenced below will be used in connection with the Contingent Variation Margin calculations.</P>
        <GPOTABLE CDEF="xs40,xs80,r50,r50" COLS="4" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">ICE<LI>physical</LI>
              <LI>code</LI>
            </CHED>
            <CHED H="1">Description</CHED>
            <CHED H="1">Platts code</CHED>
            <CHED H="1">Description</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Y</ENT>
            <ENT>UK Base</ENT>
            <ENT>AASTN00</ENT>
            <ENT>Base Week Ahead + 1.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">P</ENT>
            <ENT>UK Peak</ENT>
            <ENT>AASTP00</ENT>
            <ENT>Peak Week Ahead + 1.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">M</ENT>
            <ENT>UK Nat Gas</ENT>
            <ENT>NGAAC00</ENT>
            <ENT>Balance of Month.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">TTF</ENT>
            <ENT>TTF Nat Gas</ENT>
            <ENT>GTFTM01</ENT>
            <ENT>Prompt Month.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">NGM</ENT>
            <ENT>NCG Nat Gas</ENT>
            <ENT>GERTM00</ENT>
            <ENT>Prompt Month.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">GPM</ENT>
            <ENT>Gaspool Nat Gas</ENT>
            <ENT>GBBTM00</ENT>
            <ENT>Prompt Month.</ENT>
          </ROW>
        </GPOTABLE>
        <P>The mid-prices are used and calculated where only bid and offer prices are available. Rounding conventions will be the same as those that currently apply to the relevant future contracts.</P>
        <P>Section 17A(b)(3)(F) of the Act<SU>7</SU>
          <FTREF/>requires, among other things, that the rules of a clearing agency be designed to promote the prompt and accurate clearance and settlement of securities transactions and, to the extent applicable, derivative agreements, contracts, and transactions. ICE Clear Europe believes that the proposed change with respect to Energy Futures Products is consistent with the requirements of the Act and the rules and regulations thereunder applicable to ICE Clear Europe, in particular, with Section 17A(b)(3)(F),<SU>8</SU>
          <FTREF/>because enhancements to the margining of physically deliverable positions for certain Energy Futures Products that have expired and are in tender/delivery protects investors and the public interest.</P>
        <FTNT>
          <P>
            <SU>7</SU>15 U.S.C. 78q-1(b)(3)(F).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>8</SU>15 U.S.C. 78q-1(b)(3)(F).</P>
        </FTNT>
        <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
        <P>ICE Clear Europe does not believe the proposed change would have any impact, or impose any burden, on competition.</P>
        <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
        <P>Written comments relating to the proposed change have not been solicited or received. ICE Clear Europe will notify the Commission of any written comments received by ICE Clear Europe.</P>
        <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
        <P>The foregoing rule change has become effective upon filing pursuant to Section 19(b)(3)(A)(iii) of the Act<SU>9</SU>
          <FTREF/>and Rule 19b-4(f)(4)(ii)<SU>10</SU>
          <FTREF/>thereunder because it primarily affects the futures clearing operations of the clearing agency with respect to futures that are not security futures, and does not significantly affect any securities clearing operations of the clearing agency or any related rights or obligations of the clearing agency or persons using such service. At any time within 60 days of the filing of the proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act.<SU>11</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>9</SU>15 U.S.C. 78s(b)(3)(A)(iii).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>10</SU>17 CFR 240.19b-4(f)(4)(ii).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>11</SU>15 U.S.C. 78s(b)(3)(C).</P>
        </FTNT>
        <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
        <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
        <HD SOURCE="HD2">Electronic Comments</HD>
        <P>• Use the Commission's Internet comment form (<E T="03">http://www.sec.gov/rules/sro.shtml</E>) or</P>
        <P>• Send an email to<E T="03">rule-comments@sec.gov.</E>Please include File Number SR-ICEEU-2012-19 on the subject line.</P>
        <HD SOURCE="HD2">Paper Comments</HD>
        <P>• Send paper comments in triplicate to Elizabeth M. Murphy, Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.</P>
        

        <FP>All submissions should refer to File Number SR-ICEEU-2012-19. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (<E T="03">http://www.sec.gov/rules/sro.shtml</E>). Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the<PRTPAGE P="335"/>public in accordance with the provisions of 5 U.S.C. 552, will be available for Web site viewing and printing in the Commission's Public Reference Room, 100 F Street NE., Washington, DC 20549, on official business days between the hours of 10:00 a.m. and 3:00 p.m. Copies of such filings will also be available for inspection and copying at the principal office of ICE Clear Europe and on ICE Clear Europe's Web site at<E T="03">https://www.theice.com/publicdocs/regulatory_filings/ICEU_SEC_121912_2012-19.pdf.</E>
        </FP>
        <P>All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-ICEEU-2012-19 and should be submitted on or before January 24, 2013.</P>
        <SIG>
          <P>For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.<SU>12</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>12</SU>17 CFR 200.30-3(a)(12).</P>
          </FTNT>
          <NAME>Elizabeth M. Murphy,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31569 Filed 1-2-13; 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-68538; File No. SR-NYSE-2012-71]</DEPDOC>
        <SUBJECT>Self-Regulatory Organizations; New York Stock Exchange LLC; Notice of Filing and Immediate Effectiveness of Proposed Rule Change Amending the Price List To Waive Certain Fees for Floor Brokers for November and December 2012</SUBJECT>
        <DATE>December 27, 2012.</DATE>
        <P>Pursuant to Section 19(b)(1)<SU>1</SU>
          <FTREF/>of the Securities Exchange Act of 1934 (the “Act”)<SU>2</SU>
          <FTREF/>and Rule 19b-4 thereunder,<SU>3</SU>
          <FTREF/>notice is hereby given that December 17, 2012, New York Stock Exchange LLC (“NYSE” or the “Exchange”) filed with the Securities and Exchange Commission (the “Commission”) the proposed rule change as described in Items I and II below, which Items have been prepared by the self-regulatory organization. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons.</P>
        <FTNT>
          <P>
            <SU>1</SU>15 U.S.C. 78s(b)(1).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>2</SU>15 U.S.C. 78a.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>3</SU>17 CFR 240.19b-4.</P>
        </FTNT>
        <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change</HD>

        <P>The Exchange proposes to amend its Price List to provide relief for Floor brokers from the Annual Telephone Line Charge and the Annual Fee for November and December 2012, which the Exchange proposes to become operative as of November 1, 2012. The text of the proposed rule change is available on the Exchange's Web site at<E T="03">www.nyse.com,</E>at the principal office of the Exchange, and at the Commission's Public Reference Room.</P>
        <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
        <P>In its filing with the Commission, the self-regulatory organization included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.</P>
        <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
        <HD SOURCE="HD3">1. Purpose</HD>
        <P>The Exchange proposes to amend its Price List to provide relief for Floor brokers from the Annual Telephone Line Charge and the Annual Fee for November and December 2012, which the Exchange proposes to become operative as of November 1, 2012.</P>
        <P>Currently, member organizations are charged an Annual Telephone Line Charge of $400 per phone number. The Exchange proposes to waive the fee for Floor brokers for November and December 2012 on a prorated basis because Hurricane Sandy affected the ability of Floor brokers to communicate with customers from the Floor.</P>
        <P>The Exchange has been advised by its third-party carrier that the damage to the telephone connections is very extensive, and as a result, the telephone line connections for Floor brokers still are not fully operational and may not be so for at least another month, and possibly longer, given the type of work that needs to be completed to restore the telephone services. In particular, the Exchange notes that the telephone lines that support both the wired and wireless connections for Floor brokers are based in an area of lower Manhattan that suffered extensive damage as a result of Hurricane Sandy. The type of damage that was sustained will require the third-party carrier to rebuild the infrastructure that supports the telephone services, rather than engage in repairs of the existing lines.<SU>4</SU>
          <FTREF/>In addition to the damage to telephone lines, internet bandwidth has been reduced considerably. The Exchange notes that it is waiving the fee for Floor brokers only because off-Floor member firms were not impacted by these services. In addition, DMMs are on the Floor but do not engage in an agency business with customers from the Floor and, therefore, were not impacted by the telecommunications issues. The proposed waiver would be $33.33 for each month.</P>
        <FTNT>
          <P>

            <SU>4</SU>The Exchange filed a rule change to temporarily suspend those aspects of Rules 36.20, 36.21, and 36.30 that would not permit Floor brokers and Designated Market Makers (“DMMs”) to use personal portable phone devices on the Floor following the aftermath of Hurricane Sandy and during the period that phone service was not fully functional.<E T="03">See</E>Securities Exchange Act Release No. 68137 (November 1, 2012), 77 FR 66893 (November 7, 2012) (SR-NYSE-2012-58). The temporary suspension was subsequently extended for Floor brokers and DMMs, and again extended for Floor brokers after the Exchange was able to restore service for DMMs.<E T="03">See</E>Securities Exchange Act Release No. 68161 (November 5, 2012), 77 FR 67704 (November 13, 2012) (SR-NYSE-2012-61) and File No. SR-NYSE-2012-64.</P>
        </FTNT>
        <P>Currently, member organizations are charged an Annual Fee of $40,000 per license (the equivalent of $3,333.33 per month) for the first two licenses held by a member organization and $25,000 per license (the equivalent of $2,083.33 per month) for additional licenses held by a member organization. The Exchange proposes to provide a monthly credit of $2,000 for the first and second Floor broker licenses held by a member organization and a monthly credit of $500 for each additional Floor broker license held by a member organization for November and December 2012 because of the impact of Hurricane Sandy on Floor brokers. For example, a member organization with only one Floor broker license would receive a $2,000 credit in November and December 2012, and a member organization with three Floor broker licenses would receive a total of $4,500 in credits for November and December 2012.</P>

        <P>As stated above, Hurricane Sandy had a disproportionate impact on Floor brokers compared with off-Floor member firms and DMMs, including limited telephone service, no direct customer telephone lines, limited Internet service, intermittent cellular telephone service at the Exchange, and<PRTPAGE P="336"/>persistent busy signals.<SU>5</SU>
          <FTREF/>As a result, Floor brokers face greater operating challenges and have experienced reduced activity from certain accounts and customers compared with pre-Hurricane Sandy levels. Therefore, Floor brokers are not getting the full benefit of their licenses.</P>
        <FTNT>
          <P>
            <SU>5</SU>As part of the proposed rule change, the Exchange proposes to renumber the footnotes in the Price List accordingly.</P>
        </FTNT>
        <P>The proposed waivers would apply retroactively and would be reflected in the December 2012 and January 2013 billing statements.</P>
        <P>The proposed changes are not otherwise intended to address any other problem, and the Exchange is not aware of any significant problem that the affected member organizations would have in complying with the proposed changes.</P>
        <HD SOURCE="HD3">2. Statutory Basis</HD>
        <P>The Exchange believes that the proposed rule change is consistent with Section 6(b) of the Act,<SU>6</SU>
          <FTREF/>in general, and furthers the objectives of Section 6(b)(4) of the Act,<SU>7</SU>
          <FTREF/>in particular, because it provides for the equitable allocation of reasonable dues, fees, and other charges among its members and issuers and other persons using its facilities and does not unfairly discriminate between customers, issuers, brokers, or dealers. The Exchange also believes that the proposed rule change is consistent with Section 6(b)(5) of the Act,<SU>8</SU>
          <FTREF/>in particular, because it is designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade, to foster cooperation and coordination with persons engaged in regulating, clearing, settling, processing information with respect to, and facilitating transactions in securities, to remove impediments to, and perfect the mechanisms of, a free and open market and a national market system and, in general, to protect investors and the public interest and because it is not designed to permit unfair discrimination between customers, issuers, brokers, or dealers.</P>
        <FTNT>
          <P>
            <SU>6</SU>15 U.S.C. 78f(b).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>7</SU>15 U.S.C. 78f(b)(4).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>8</SU>15 U.S.C. 78f(b)(5).</P>
        </FTNT>
        <P>The Exchange believes that waiving the Annual Telephone Line Charge and providing a monthly credit for the Annual Fee for Floor brokers for November and December 2012 is reasonable because Hurricane Sandy affected the ability of Floor brokers to communicate with customers and the ease with which they could represent public orders on the Floor. Therefore, the Exchange believes it is reasonable to provide relief for Floor brokers in this regard.</P>
        <P>The Exchange believes the proposed change to the Annual Telephone Line Charge and Annual Fee for Floor brokers is equitable and not unfairly discriminatory because Floor brokers are the only class of member organization that was affected by the telecommunications issues, which has impacted their ability to conduct their regular business and has resulted in reduced activity from certain accounts and customers. Therefore, it is equitable and not unfairly discriminatory to offer the fee waiver and credit only to Floor brokers, which is the only class of Floor members not getting the full benefit of their licenses. In addition, the Exchange believes that because communications with customers is a vital part of a Floor broker's role as agent, during the period when phone service continues to be intermittent, Floor brokers should receive relief from the Annual Telephone Line Charge.</P>
        <P>The Exchange believes that the proposed monthly credit of $2,000 for the first and second licenses held by a Floor broker for November and December 2012 is reasonable because all Floor brokers hold at least one license, and as such, all member organizations that have a Floor broker license will receive at least a $2,000 per month credit for November and December 2012. The Exchange believes that the proposed monthly credit of $500 for each additional Floor broker license held by a member organization for November and December 2012 is reasonable because it will provide additional compensation to a member organization that holds and pays for more than two Floor broker licenses. In addition, the Exchange believes that the proposed credits are equitable and not unfairly discriminatory because member organizations that hold only one or two Floor broker licenses are generally smaller and are less able to absorb the operating impact resulting from the infrastructure damage caused by Hurricane Sandy. In addition, member organizations that hold more than two Floor broker licenses pay a reduced Annual Fee for additional licenses, and therefore, it is equitable and not unfairly discriminatory to provide a lower monthly credit for each additional Floor broker license.</P>
        <P>The Exchange believes that the proposed relief for Floor brokers removes impediments to and perfects the mechanism of a free and open market and national market system because it would provide relief for Floor brokers that are experiencing ongoing issues with telephone service while they are conducting their regular business on the Floor. The Exchange further believes that the proposed waiver and credit do not permit unfair discrimination because they would provide relief for Floor brokers that have been disproportionally impacted in their ability to operate as agents for customers during this time of unprecedented weather disruptions.</P>
        <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition</HD>
        <P>The Exchange does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act.</P>
        <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
        <P>No written comments were solicited or received with respect to the proposed rule change.</P>
        <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action</HD>
        <P>Because the proposed rule change does not: (i) Significantly affect the protection of investors or the public interest; (ii) impose any significant burden on competition; and (iii) become operative prior to 30 days from the date on which it was filed, or such shorter time as the Commission may designate, if consistent with the protection of investors and the public interest, the proposed rule change has become effective pursuant to Section 19(b)(3)(A) of the Act<SU>9</SU>
          <FTREF/>and Rule 19b-4(f)(6)(iii) thereunder.<SU>10</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>9</SU>15 U.S.C. 78s(b)(3)(A).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>10</SU>17 CFR 240.19b-4(f)(6)(iii). In addition, Rule 19b-4(f)(6) requires a self-regulatory organization to give the Commission written notice of its intent to file the proposed rule change, along with a brief description and text of the proposed rule change, at least five business days prior to the date of filing of the proposed rule change, or such shorter time as designated by the Commission. The Exchange has satisfied this requirement.</P>
        </FTNT>
        <P>A proposed rule change filed under Rule 19b-4(f)(6)<SU>11</SU>
          <FTREF/>normally does not become operative prior to 30 days after the date of the filing. However, pursuant to Rule 19b-4(f)(6)(iii),<SU>12</SU>

          <FTREF/>the Commission may designate a shorter time if such action is consistent with the protection of investors and the public interest. The Exchange has asked the Commission to waive the 30-day operative delay so that the proposal may become operative immediately upon filing. The Commission believes that waiving the 30-day operative delay is<PRTPAGE P="337"/>consistent with the protection of investors and the public interest. The Commission notes that doing so will allow the Exchange to provide the proposed relief during the billing period in which the Floor brokers were affected. Therefore, the Commission hereby waives the 30-day operative delay and designates the proposal operative upon filing.<SU>13</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>11</SU>17 CFR 240.19b-4(f)(6).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>12</SU>17 CFR 240.19b-4(f)(6)(iii).</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>13</SU>For purposes only of waiving the 30-day operative delay, the Commission has considered the proposed rule's impact on efficiency, competition, and capital formation.<E T="03">See</E>15 U.S.C. 78c(f).</P>
        </FTNT>
        <P>At any time within 60 days of the filing of such proposed rule change, the Commission summarily may temporarily suspend such rule change if it appears to the Commission that such action is necessary or appropriate in the public interest, for the protection of investors, or otherwise in furtherance of the purposes of the Act.</P>
        <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
        <P>Interested persons are invited to submit written data, views, and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
        <HD SOURCE="HD2">Electronic Comments</HD>
        <P>• Use the Commission's Internet comment form (<E T="03">http://www.sec.gov/rules/sro.shtml</E>); or</P>
        <P>• Send an email to<E T="03">rule-comments@sec.gov</E>. Please include File Number SR-NYSE-2012-71 on the subject line.</P>
        <HD SOURCE="HD2">Paper Comments</HD>
        <P>• Send paper comments in triplicate to Elizabeth M. Murphy, Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.</P>
        

        <FP>All submissions should refer to File Number SR-NYSE-2012-71. This file number should be included on the subject line if email is used. To help the Commission process and review your comments more efficiently, please use only one method. The Commission will post all comments on the Commission's Internet Web site (<E T="03">http://www.sec.gov/rules/sro.shtml.</E>) Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for Web site viewing and printing in the Commission's Public Reference Room, 100 F Street NE., Washington, DC 20549, on official business days between the hours of 10:00 a.m. and 3:00 p.m. Copies of the filing also will be available for inspection and copying at the principal office of the Exchange. All comments received will be posted without change; the Commission does not edit personal identifying information from submissions. You should submit only information that you wish to make available publicly. All submissions should refer to File Number SR-NYSE-2012-71 and should be submitted on or before January 24, 2013.</FP>
        <SIG>
          <P>For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.<SU>14</SU>
            <FTREF/>
          </P>
          <FTNT>
            <P>
              <SU>14</SU>17 CFR 200.30-3(a)(12).</P>
          </FTNT>
          <NAME>Lynn M. Powalski,</NAME>
          <TITLE>Deputy Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31572 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 8011-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Maritime Administration</SUBAGY>
        <DEPDOC>[Docket No. MARAD-2012-0114]</DEPDOC>
        <SUBJECT>Requested Administrative Waiver of the Coastwise Trade Laws: Vessel HALCYON; Invitation for Public Comments</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Maritime Administration, Department of Transportation.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>As authorized by 46 U.S.C. 12121, the Secretary of Transportation, as represented by the Maritime Administration (MARAD), is authorized to grant waivers of the U.S.-build requirement of the coastwise laws under certain circumstances. A request for such a waiver has been received by MARAD. The vessel, and a brief description of the proposed service, is listed below.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Submit comments on or before February 4, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Comments should refer to docket number MARAD-2012-0114. Written comments may be submitted by hand or by mail to the Docket Clerk, U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE., Washington, DC 20590. You may also send comments electronically via the Internet at<E T="03">http://www.regulations.gov.</E>All comments will become part of this docket and will be available for inspection and copying at the above address between 10 a.m. and 5 p.m., E.T., Monday through Friday, except federal holidays. An electronic version of this document and all documents entered into this docket is available on the World Wide Web at<E T="03">http://www.regulations.gov.</E>
          </P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Linda Williams, U.S. Department of Transportation, Maritime Administration, 1200 New Jersey Avenue SE., Room W23-453, Washington, DC 20590. Telephone 202-366-0903, Email<E T="03">Linda.Williams@dot.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>As described by the applicant the intended service of the vessel HALCYON is:</P>
        <P>
          <E T="03">Intended Commercial Use of Vessel:</E>“Private yacht charters.”</P>
        <P>
          <E T="03">Geographic Region:</E>“Florida.”</P>

        <P>The complete application is given in DOT docket MARAD-2012-0114 at<E T="03">http://www.regulations.gov.</E>Interested parties may comment on the effect this action may have on U.S. vessel builders or businesses in the U.S. that use U.S.-flag vessels. If MARAD determines, in accordance with 46 U.S.C. 12121 and MARAD's regulations at 46 CFR Part 388, that the issuance of the waiver will have an unduly adverse effect on a U.S.-vessel builder or a business that uses U.S.-flag vessels in that business, a waiver will not be granted. Comments should refer to the docket number of this notice and the vessel name in order for MARAD to properly consider the comments. Comments should also state the commenter's interest in the waiver application, and address the waiver criteria given in § 388.4 of MARAD's regulations at 46 CFR Part 388.</P>
        <HD SOURCE="HD1">Privacy Act</HD>

        <P>Anyone is able to search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review DOT's complete Privacy Act Statement in the<E T="04">Federal Register</E>published on April 11, 2000 (Volume 65, Number 70; Pages 19477-78).</P>
        <SIG>
          <P>By Order of the Maritime Administrator.</P>
          
          <DATED>Dated: December 28, 2012.</DATED>
          <NAME>Thomas M. Hudson,</NAME>
          <TITLE>Assistant Secretary, Maritime Administration.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31637 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-81-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="338"/>
        <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Surface Transportation Board</SUBAGY>
        <DEPDOC>[Docket No. AB 55 (Sub-No. 724X)]</DEPDOC>
        <SUBJECT>CSX Transportation, Inc.; Abandonment Exemption—in Ewing Township, Mercer County, NJ</SUBJECT>

        <P>CSX Transportation, Inc. (CSXT) has filed a verified notice of exemption under 49 CFR part 1152 subpart F—<E T="03">Exempt Abandonments</E>to abandon an approximately 1.67-mile rail line on its Northern Region, Albany Division, Trenton Subdivision, between milepost QAT 32.82, near the connection to CSXT's main line located near Railroad Avenue and Water Drive, and the end of the track at milepost QAT 34.49, in Ewing Township, Mercer County, N.J. (the Line). The Line traverses United States Postal Service Zip Codes 08628 and 08618, and includes the West Trenton Station located at milepost QAT 33.</P>
        <P>In the notice, CSXT explains that, following abandonment, it intends to reclassify a 1.40-mile portion of the Line between milepost QAT 32.80 and milepost QAT 34.20 as industry lead track for future transportation needs. CSXT also intends to transfer the remaining 0.29-mile portion of the Line to the Christina Seix Academy to be used as a roadway for access to the school. CSXT states that the Line may be suitable for other public purposes, but may be subject to reversionary interests.</P>
        <P>CSXT has certified that: (1) No local traffic has moved over the Line for at least two years; (2) any overhead traffic can be rerouted over other lines; (3) no formal complaint filed by a user of rail service on the Line (or by a state or local government entity acting on behalf of such user) regarding cessation of service over the Line either is pending with the Surface Transportation Board (Board) or with any U.S. District Court or has been decided in favor of complainant within the two-year period; and (4) the requirements at 49 CFR 1105.7(c) (environmental report), 49 CFR 1105.11 (transmittal letter), 49 CFR 1105.12 (newspaper publication), and 49 CFR 1152.50(d)(1) (notice to governmental agencies) have been met.</P>

        <P>As a condition to this exemption, any employee adversely affected by the abandonment shall be protected under<E T="03">Oregon Short Line Railroad—Abandonment Portion Goshen Branch Between Firth &amp; Ammon, in Bingham &amp; Bonneville Counties, Idaho,</E>360 I.C.C. 91 (1979). To address whether this condition adequately protects affected employees, a petition for partial revocation under 49 U.S.C. 10502(d) must be filed.</P>
        <P>Provided no formal expression of intent to file an offer of financial assistance (OFA) has been received, this exemption will be effective on February 2, 2013, unless stayed pending reconsideration. Petitions to stay that do not involve environmental issues,<SU>1</SU>
          <FTREF/>formal expressions of intent to file an OFA under 49 CFR 1152.27(c)(2),<SU>2</SU>
          <FTREF/>and trail use/rail banking requests under 49 CFR 1152.29 must be filed by January 14, 2013. Petitions to reopen or requests for public use conditions under 49 CFR 1152.28 must be filed by January 23, 2013, with the Surface Transportation Board, 395 E Street SW., Washington, DC 20423-0001.</P>
        <FTNT>
          <P>

            <SU>1</SU>The Board will grant a stay if an informed decision on environmental issues (whether raised by a party or by the Board's Office of Environmental Analysis (OEA) in its independent investigation) cannot be made before the exemption's effective date.<E T="03">See Exemption of Out-of-Serv. Rail Lines,</E>5 I.C.C.2d 377 (1989). Any request for a stay should be filed as soon as possible so that the Board may take appropriate action before the exemption's effective date.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>2</SU>Each OFA must be accompanied by the filing fee, which is currently set at $1,600.<E T="03">See Regulations Governing Fees for Servs. Performed in Connection with Licensing &amp; Related Servs.—2012 Update,</E>EP 542 (Sub-No. 20) (STB served July 27, 2012).</P>
        </FTNT>
        <P>A copy of any petition filed with the Board should be sent to CSXT's representative: Louis E. Gitomer, Law Offices of Louis E. Gitomer, LLC, 600 Baltimore Avenue, Suite 301, Towson, MD 21204.</P>

        <P>If the verified notice contains false or misleading information, the exemption is void<E T="03">ab initio.</E>
        </P>
        <P>CSXT has filed environmental and historic reports that address the effects, if any, of the abandonment on the environment and historic resources. OEA will issue an environmental assessment (EA) by January 8, 2013. Interested persons may obtain a copy of the EA by writing to OEA (Room 1100, Surface Transportation Board, Washington, DC 20423-0001) or by calling OEA at (202) 245-0305. Assistance for the hearing impaired is available through the Federal Information Relay Service at 1-800-877-8339. Comments on environmental and historic preservation matters must be filed within 15 days after the EA becomes available to the public.</P>
        <P>Environmental, historic preservation, public use, or trail use/rail banking conditions will be imposed, where appropriate, in a subsequent decision.</P>
        <P>Pursuant to the provisions of 49 CFR 1152.29(e)(2), CSXT shall file a notice of consummation with the Board to signify that it has exercised the authority granted and fully abandoned the line. If consummation has not been effected by CSXT's filing of a notice of consummation by January 3, 2014, and there are no legal or regulatory barriers to consummation, the authority to abandon will automatically expire.</P>

        <P>Board decisions and notices are available on our Web site at<E T="03">www.stb.dot.gov.</E>
        </P>
        <SIG>
          <DATED>Decided: December 26, 2012.</DATED>
          
          <P>By the Board, Rachel D. Campbell, Director, Office of Proceedings.</P>
          <NAME>Jeffrey Herzig,</NAME>
          <TITLE>Clearance Clerk.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31606 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4915-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Surface Transportation Board</SUBAGY>
        <DEPDOC>[Docket No. FD 35697]</DEPDOC>
        <SUBJECT>Buckeye Hammond Railroad, L.L.C.; Acquisition and Operation Exemption; Buckeye Partners, L.P.</SUBJECT>
        <P>Buckeye Hammond Railroad, L.L.C. (BHRR), a noncarrier, has filed a verified notice of exemption under 49 CFR 1150.31<SU>1</SU>
          <FTREF/>to acquire from Buckeye Partners, L.P., a noncarrier, and to operate approximately 6,797 feet (1.29 miles) of track,<SU>2</SU>
          <FTREF/>existing railroad right-of-way, and bulk liquid transloading facilities in Hammond, Ind. BHRR will interchange traffic with the Indiana Harbor Belt Railroad Company.</P>
        <FTNT>
          <P>
            <SU>1</SU>The notice was initially filed on December 6, 2012, but it did not meet the Board's regulatory requirements. BHRR filed supplements on December 17 and 18, 2012. Because the notice was not complete until the December 18 filing, that date will be considered the actual filing date.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>2</SU>Applicant states that the track does not have designated mileposts.</P>
        </FTNT>
        <P>The transaction may be consummated on or after January 17, 2013 (30 days after the notice of exemption was filed).</P>
        <P>BHRR certifies that its projected annual revenues as a result of this transaction will not exceed those that would qualify it as a Class III rail carrier and will not exceed $5 million.</P>

        <P>If the verified notice contains false or misleading information, the exemption is void<E T="03">ab initio.</E>Petitions to revoke the exemption under 49 U.S.C. 10502(d) may be filed at any time. The filing of a petition to revoke will not automatically stay the effectiveness of the exemption. Petitions to stay must be filed no later than January 10, 2013 (at least seven days before the exemption becomes effective).</P>

        <P>An original and 10 copies of all pleadings, referring to Docket No. FD 35697, must be filed with the Surface Transportation Board, 395 E Street SW.,<PRTPAGE P="339"/>Washington, DC 20423-0001. In addition, a copy of each pleading must be served on David C. Dillon, 111 West Washington Street, Suite 1023, Chicago, IL 60602.</P>

        <P>Board decisions and notices are available on our Web site at<E T="03">www.stb.dot.gov</E>.</P>
        <SIG>
          <DATED>Decided: December 26, 2012.</DATED>
          
          <P>By the Board, Rachel D. Campbell, Director, Office of Proceedings.</P>
          
          <NAME>Jeffrey Herzig,</NAME>
          <TITLE>Clearance Clerk.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31439 Filed 1-2-13; 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>December 28, 2012.</DATE>
        <P>The Department of the Treasury will submit the following information collection request to the Office of Management and Budget (OMB) for review and clearance in accordance with the Paperwork Reduction Act of 1995, Public Law 104-13, on or after the date of publication of this notice.</P>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments should be received on or before February 4, 2013 to be assured of consideration.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Send comments regarding the burden estimate, or any other aspect of the information collection, including suggestion for reducing the burden, to (1) Office of Information and Regulatory Affairs, Office of Management and Budget, Attention: Desk Officer for Treasury, New Executive Office Building, Room 10235, Washington, DC 20503, or email at<E T="03">OIRA_Submission@OMB.EOP.GOV</E>and (2) Treasury PRA Clearance Officer, 1750 Pennsylvania Ave. NW., Suite 8140, Washington, DC 20220, or email at<E T="03">PRA@treasury.gov.</E>
          </P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Copies of the submission(s) may be obtained by calling (202) 927-5331, email at<E T="03">PRA@treasury.gov,</E>or the entire information collection request maybe found at<E T="03">www.reginfo.gov.</E>
          </P>
          <HD SOURCE="HD1">Community Development Financial Institutions (CDFI) Fund</HD>
          <P>
            <E T="03">OMB Number:</E>1559-0021.</P>
          <P>
            <E T="03">Type of Review:</E>Revision of a currently approved collection.</P>
          <P>
            <E T="03">Title:</E>Financial Assistance (FA) and Technical Assistance (TA) Component Application—CDFI Program.</P>
          <P>
            <E T="03">Abstract:</E>The CDFI Fund provides financial assistance in the form of grants, loans, equity investments and deposits to community development financial institutions providing capital and financial services to underserved markets.</P>
          <P>
            <E T="03">Affected Public:</E>Private Sector: Businesses or other for-profits; not-for-profit institutions.</P>
          <P>
            <E T="03">Estimated Total Burden Hours:</E>20,000.</P>
          <SIG>
            <NAME>Robert Dahl,</NAME>
            <TITLE>Treasury PRA Clearance Officer.</TITLE>
          </SIG>
        </FURINF>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31581 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4810-70-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
        <SUBJECT>Proposed Collections; Comment Requests</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Departmental Offices; Department of the Treasury.</P>
        </AGY>
        
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Department of the Treasury, as part of its continuing effort to reduce paperwork burdens, invites the general public and other Federal agencies to comment on revisions of an information collection that are proposed for approval by the Office of Management and Budget. The Office of International Affairs within the Department of the Treasury is soliciting comments concerning the revisions of the Treasury International Capital (TIC) Forms BC, BL-1, BL-2, BQ-1, BQ-2, and BQ-3 (called the “TIC B forms”).</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Written comments should be received on or before March 4, 2013 to be assured of consideration.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Direct all written comments to Dwight Wolkow, International Portfolio Investment Data Systems, Department of the Treasury, Room 5422, 1500 Pennsylvania Avenue NW., Washington, DC 20220. In view of possible delays in mail delivery, please also notify Mr. Wolkow by email (<E T="03">comments2TIC@treasury.gov</E>), fax (202-622-2009) or telephone (202-622-1276).</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Copies of the proposed forms and instructions are available on the Treasury's TIC Forms Web page,<E T="03">http://www.treasury.gov/resource-center/data-chart-center/tic/Pages/forms.aspx.</E>Requests for additional information should be directed to Mr. Wolkow.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P SOURCE="NPAR">
          <E T="03">Titles:</E>Treasury International Capital (TIC) Form BC “Monthly Report of U.S. Dollar Claims of Depository Institutions, Bank Holding Companies/Financial Holding Companies, Brokers, and Dealers on Foreigners;” TIC BL-1 “Monthly Report of U.S. Dollar Liabilities of Depository Institutions, Bank Holding Companies/Financial Holding Companies, Brokers, and Dealers to Foreign Residents;” TIC BL-2 “Monthly Report of Customers' U.S. Dollar Liabilities to Foreigners;” TIC BQ-1 “Quarterly Report of Customers' U.S. Dollar Claims on Foreigners;” TIC BQ-2 “Part 1: Quarterly Report of Foreign Currency Liabilities and Claims of Depository Institutions, Bank Holding Companies/Financial Holding Companies, Brokers and Dealers, and of Their Domestic Customers Visa-A-Vis Foreigners” and “Part 2: The Report of Customers' Foreign Currency Liabilities to Foreigners;” and TIC BQ-3 “Quarterly Report of Maturities of Selected Liabilities of Depository Institutions, Bank Holding Companies/Financial Holding Companies, Brokers, and Dealers to Foreigners.”</P>
        <P>
          <E T="03">OMB Numbers:</E>1505-0017 (TIC BC), 1505-0019 (TIC BL-1), 1505-0018 (TIC BL-2), 1505-0016 (TIC BQ-1), 1505-0020 (TIC BQ-2), and 1505-0189 (TIC BQ-3).</P>
        <P>
          <E T="03">Abstract:</E>Forms BC, BL-1, BL-2, BQ-1, BQ-2, BQ-3 are part of the Treasury International Capital (TIC) reporting system, which is required by law (22 U.S.C. 286f; 22 U.S.C. 3103; E.O. 10033; 31 CFR 128) and are designed to collect timely information on international portfolio capital movements. These forms are filed by all U.S.-resident banks, other depository institutions, brokers and dealers, and Bank Holding Companies/Financial Holding Companies (BHC/FHC). On the monthly forms, these organizations report their own claims on (BC), their own liabilities to (BL-1), and their U.S. customers' liabilities to (BL-2) foreign residents, denominated in U.S. dollars. On the quarterly forms, these organizations report their U.S.-resident customers' U.S. dollar claims on foreign residents (BQ-1), and their own and their domestic customers' claims and liabilities with foreign residents, where all claims and liabilities are denominated in foreign currencies (BQ-2). On the quarterly BQ-3 form, these organizations report the remaining maturities of all their own U.S. dollar and foreign currency liabilities (excluding securities) to foreign residents. This information is necessary for compiling the U.S. balance of payments accounts and the U.S. international investment position, and for use in formulating U.S. international financial and monetary policies.</P>
        <P>
          <E T="03">Current Actions:</E>As a consequence of the recent global financial crisis, international reporting standards for collecting and reporting economic and financial data have been enhanced, especially regarding each country's<PRTPAGE P="340"/>external claims and liabilities. TIC forms are consequently revised to reflect the new standards. Provided below is a list of the revisions to reporting forms and instructions, effective beginning with reports as of June 30, 2013.</P>
        <P>
          <E T="03">The following changes apply to all TIC B forms:</E>
        </P>
        <P>(a) The “who must report” section of the instructions is revised. Beginning with the reports as of June 30, 2013, the organizations required to file the TIC B forms will include all types of U.S.-resident financial institutions (including, but not limited to banks, other depository institutions, brokers/dealers, bank/financial holding companies, investment banks, insurance companies, credit card issuers, money market funds, pension funds, private equity funds, hedge funds, trusts, finance companies, mortgage companies, commodity brokers and dealers, investment advisors and managers, loan brokers). More specifically, all financial institutions that previously filed TIC C forms (form CQ-1 and form CQ-2) will file TIC B forms beginning with the reports as of June 30, 2013. Those financial institutions changing from filing the TIC C forms to filing the TIC B forms will not be required to file the TIC C forms after the reports as of May 31, 2013. This change affecting many U.S.-resident financial institutions, from reporting on the TIC C forms to reporting on the TIC B forms, is designed to improve the coverage of international financial transactions and positions in the U.S. balance of payments and in the U.S. international investment position, and reflects the change in the international statistical standards to include in portfolio investment (PI) most international positions between financial institutions. All financial transactions and positions between U.S. residents and foreign residents are either PI or direct investment (DI), and all organizations with such positions (above the amounts declared exempt in the reporting instructions), must report them to either the TIC (which collects PI information) or BEA (which collects DI information).</P>
        <P>(b) The instructions for these forms have been updated to add guidance for reporting on the new “of which” rows described in (g) through (l) below and the new section and columns described in (l). (c) The General Instructions have been reorganized and contain new guidance on reporting accrued interest and insurance/reinsurance business, and on where to report. (d) Several sections of the instructions, including the glossary, incorporate changes to clarify the reporting requirements, such as the consolidation/combination rules, valuation rules, and reporting the location of foreign counterparties.</P>
        <P>(e) Except for the TIC BQ-3, the list of countries for reporting the location of foreign counterparties will be increased by six. This is the result of deleting Netherlands Antilles (3720-6), removing “Montenegro” from “Serbia and Montenegro (1321-8),” and adding Kosovo (1347-1), Montenegro (1362-5), Bonaire, Sint Eustatius and Saba (3616-1), Curaçao (3618-8), St. Martin and St. Barthelemy (3647-1), Sint Maarten (3619-6), and South Sudan (5339-2). (f) These changes (a) through (l) will be effective beginning with the reports as of June 30, 2013.</P>
        <HD SOURCE="HD2">(g) Changes to Form BC</HD>
        <P>1. As a result of the action in (a) above, the title of Form BC is changed to “Report of U.S. Dollar Claims of Financial Institutions on Foreign Residents.”</P>
        <P>2. In the “of which” items at the end of the form, a new row has been added to collect “Claims on Foreign-Resident Non-Bank Financial Institutions.” Data are reportable in columns 4, 5, 6, 8 and 9.</P>
        <P>3. In the “of which” items at the end of the form, a new row has been added to collect “Unpaid Insurance Claims.” Data are reportable in columns 3, 5, 6 and 8.</P>
        <HD SOURCE="HD2">(h) Changes to Form BL-1</HD>
        <P>1. As a result of the action in (a) above, the title of Form BL-1 is changed to “Report of U.S. Dollar Liabilities of Financial Institutions to Foreign Residents.”</P>
        <P>2. In the “of which” items at the end of the form, a new row has been added to collect “Liabilities to Foreign-Resident Non-Bank Financial Institutions.” Data are reportable in columns 5 through 9.</P>
        <P>3. In the “of which” items at the end of the form, a new row has been added to collect “Unpaid Insurance Claims and Prepaid Insurance Premiums.” Data are reportable in columns 2, 4, 6, 7 and 8.</P>
        <HD SOURCE="HD2">(i) Changes to Form BL-2</HD>
        <P>1. As a result of the action in (a) above, the title of Form BL-2 is changed to “Report of Customers' U.S. Dollar Liabilities to Foreign Residents.”</P>
        <P>2. In the memorandum section at the end of the current form, the eight rows are changed to eight “of which” rows that have the same eleven columns as do the other rows in the form. The first, fourth and fifth “Of Which” rows (8102-7, 8144-2, 8146-9) are unchanged and data are reportable in column 10. In the second “of which” item for “Total U.S.—Resident Bank Debt; Loans to Banks” (8141-8), data are reportable in columns 3, 6, 9 and10. This item previously collected data for only the “Grand Total” column (Column 10).</P>
        <P>3. In the “of which” item at the end of the form for “Total U.S.—Resident Bank Debt; Short-Term Negotiable Securities Issued by Banks” (8142-6), data are reportable in columns 2, 5, 8 and10. This item previously collected data for only the “Grand Total” column (Column 10).</P>
        <P>4. The sixth row of the “of which” items, that was previously labeled “Liabilities of Other U.S. Debtor Sectors,” is now labeled “Liabilities of U.S.-Resident Non-Bank Financial Institutions (NBFIs)” and a new code has been added in the code column. Data are reportable only in column 10. Previously, there was no data collected on this row.</P>
        <P>5. The seventh row (8150-3), which was previously labeled “Other short-term negotiable securities” is now labeled “Short-term Negotiable Securities issued by NBFIs.” Data are reportable only in columns 2, 5, 8 and 10. This item previously collected data for only the “Grand Total” column (Column 10).</P>
        <P>6. The eighth row (8155-8), which was previously labeled “Loans to Others,” is now labeled “Loans to NBFIs.” Data are reportable only in columns 3, 6, 9 and 10. This item previously collected data for only the “Grand Total” column (Column 10).</P>
        <HD SOURCE="HD2">(j) Changes to Form BQ-1</HD>
        <P>1. As a result of the action in (a) above, the title of Form BQ-1 is changed to “Report of Customers' U.S. Dollar Claims on Foreign Residents.”</P>
        <P>2. In the “of which” items at the end of the form, a new row has been added to collect ”Claims of U.S.-Resident Non-Bank Financial Institutions.” Data are reportable in columns 1, 2, 3, 4 and 5.</P>
        <HD SOURCE="HD2">(k) Changes to Form BQ-2</HD>
        <P>1. As a result of the action in (a) above, the title caption of Form BQ-2, Part I, is changed to “Report of Foreign Currency Liabilities and Claims of U.S. Financial Institutions, and of their Domestic Customers' Foreign Currency Claims with Foreign Residents” and the title caption of Part II is changed to “Report of Customers' Foreign Currency Liabilities to Foreign Residents.”</P>

        <P>2. In the “of which” items at the end of the form, a new row has been added to collect claims and liabilities denominated in Swiss francs. Data are reportable in columns 1 through 6.<PRTPAGE P="341"/>
        </P>
        <P>3. In the “of which” items at the end of the form, a new row has been added to collect “Unpaid Insurance Claims and Prepaid Insurance Premiums.” Data are reportable in columns 2 and 4.</P>
        <P>4. In the “of which” items at the end of the form, a new row has been added to collect “Claims on/Liabilities to Foreign-Resident Banks.” Data are reportable in columns 1 through 7.</P>
        <P>5. In the “of which” items at the end of the form, a new row has been added to collect ”Claims on/Liabilities to Foreign-Resident Non-Bank Financial Institutions.” Data are reportable in columns 1 through 7.</P>
        <HD SOURCE="HD2">(l) Changes to Form BQ-3</HD>
        <P>1. The name of the form is changed to “Report of Maturities of Selected Claims and Liabilities of Financial Institutions with Foreign Residents”. This and the following revisions of the form respond to the changes in (a) above and to international reporting standards calling for reporting of maturities of claims and liabilities.</P>
        <P>2. The title “Part 1: Liabilities to Foreign Residents—Remaining Maturities” is added at the top of page 2 to describe the existing one-half page table that collects information on liabilities.</P>
        <P>3. A new section is added on page 2 of the form entitled “Part 2: Claims on Foreign Residents—Remaining Maturities” that collects information on claims. The new section has three rows labeled: “Demand Deposits, Arrears, Resale Agreements Under Continuing Contract, and Items With No Fixed Maturity;” “Maturing in 1 Year or Less;” and “Maturing In Over 1 Year.” The new section has four columns for data entry with the following titles: column 1 is “Non-Negotiable Foreign Deposits &amp; Brokerage Balances [reported on BC (col. 1) &amp; BQ-2, Part 1 (col. 3)];” column 2 is “Resale Agreements &amp; Other Claims [reported on BC (cols. 3, 5) &amp; BQ-2, Part 1 (col. 4)];” column 3 is “Loan Claims Excluding Resale Agreements [reported on BC (cols. 3, 5) &amp; BQ-2, Part 1 (col. 4)];” and column 4 is “Grand Total [sum of columns 1-3].”</P>
        <P>
          <E T="03">Type of Review:</E>Revision of a currently approved collection.</P>
        <P>
          <E T="03">Affected Public:</E>Business or other for-profit organizations.</P>
        <P>Forms BC, BL-1, BL-2, BQ-1, BQ-2, and BQ-3.</P>
        <P>
          <E T="03">Estimated Number of Respondents:</E>BC, 302; BL-1, 348; BL-2, 80; BQ-1, 77; BQ-2, 149 and BQ-3, 117.</P>
        <P>
          <E T="03">Estimated Average Time per Respondent per Filing:</E>BC, 9.9 hours; BL-1, 7.1 hours; BL-2, 8.25 hours; BQ-1, 3.1 hours; BQ-2, 6.6 hours; and BQ-3, 4.0 hours. The average time varies, and is estimated to be generally twice as many hours for major data reporters as for other reporters.</P>
        <P>
          <E T="03">Estimated Total Annual Burden Hours:</E>BC, 35,856 hours for 12 reports per year; BL-1, 29,484 hours for 12 reports per year; BL-2, 7,920 hours for 12 reports per year; BQ-1, 963 hours for 4 reports per year, BQ-2, 3,938 hours for 4 reports per year, and BQ-3, 1,872 hours for 4 reports per year.</P>
        <P>
          <E T="03">Request for Comments:</E>Comments submitted in response to this notice will be summarized and/or included in the request for Office of Management and Budget approval. All comments will become a matter of public record. The public is invited to submit written comments concerning: (a) Whether Forms BC, BL-1, BL-2, BQ-1, BQ-2, and BQ-3 are necessary for the proper performance of the functions of the Office, including whether the information will have practical uses; (b) the accuracy of the above estimate of the burdens; (c) ways to enhance the quality, usefulness and clarity of the information to be collected; (d) ways to minimize the reporting and/or record keeping burdens on respondents, including the use of information technologies to automate the collection of the data; and (e) estimates of capital or start-up costs of operation, maintenance and purchase of services to provide information.</P>
        <SIG>
          <NAME>Dwight Wolkow,</NAME>
          <TITLE>Administrator, International Portfolio Investment Data Systems.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31564 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4810-25-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
        <SUBAGY>Bureau of the Public Debt</SUBAGY>
        <SUBJECT>Proposed Information Collection; Comment Request</SUBJECT>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice and request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Department of the Treasury, as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on proposed and/or continuing information collections, as required by the Paperwork Reduction Act of 1995, Public Law 104-13 (44 U.S.C. 3506(c)(2)(A). Currently the Bureau of the Public Debt within the Department of the Treasury is soliciting comments concerning collections of information required to comply with the terms and conditions of FHA debentures.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Written comments should be received on or before March 2, 2013 to be assured of consideration.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Direct all written comments to Bureau of the Public Debt, Bruce A. Sharp, 200 Third Street A4-A, Parkersburg, WV 26106-1328, or<E T="03">bruce.sharp@bpd.treas.gov.</E>The opportunity to make comments online is also available at<E T="03">www.pracomment.gov.</E>
          </P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Requests for additional information or copies should be directed to Bruce A. Sharp, Bureau of the Public Debt, 200 Third Street A4-A, Parkersburg, WV 26106-1328, (304) 480-8150.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P SOURCE="NPAR">
          <E T="03">Form Numbers and Title:</E>PD F 5354—FHA Transaction Request; PD F 5366—FHA New Account Request; PD F 5367—FHA Debenture Transfer Request.</P>
        <P>
          <E T="03">OMB Number:</E>1535-0102.</P>
        <P>
          <E T="03">Abstract:</E>The information is used to (1) Establish a book-entry account; (2) change information on a book-entry account; and (3) transfer ownership of a book-entry account on the HUD system, maintained by the Federal Reserve Bank of Philadelphia.</P>
        <P>
          <E T="03">Current Actions:</E>None.</P>
        <P>
          <E T="03">Type of Review:</E>Extension.</P>
        <P>
          <E T="03">Affected Public:</E>Individuals or Households.</P>
        <P>
          <E T="03">Estimated Number of Respondents:</E>300.</P>
        <P>
          <E T="03">Estimated Time per Respondent:</E>10 minutes.</P>
        <P>
          <E T="03">Estimated Total Annual Burden Hours:</E>50.</P>
        <P>
          <E T="03">Request for Comments:</E>Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. All comments will become a matter of public record. 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 shall have practical utility; (b) the accuracy of the agency's estimate of the burden of the collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; (d) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or other forms of information technology; and (e) estimates of capital or start-up costs and costs of operation, maintenance, and purchase of services to provide information.</P>
        <SIG>
          <DATED>Dated: December 28, 2012.</DATED>
          <NAME>Bruce A. Sharp,</NAME>
          <TITLE>Bureau Clearance Officer .</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31625 Filed 1-2-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4810-39-P</BILCOD>
    </NOTICE>
  </NOTICES>
  <VOL>78</VOL>
  <NO>2</NO>
  <DATE>Thursday, January 3, 2013</DATE>
  <UNITNAME>Rules and Regulations</UNITNAME>
  <NEWPART>
    <PTITLE>
      <PRTPAGE P="343"/>
      <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; Designation of Critical Habitat for Southwestern Willow Flycatcher; Final Rule</TITLE>
    </PTITLE>
    <RULES>
      <RULE>
        <PREAMB>
          <PRTPAGE P="344"/>
          <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
          <SUBAGY>Fish and Wildlife Service</SUBAGY>
          <CFR>50 CFR Part 17</CFR>
          <DEPDOC>[Docket No. FWS-R2-ES-2011-0053; 4500030114]</DEPDOC>
          <RIN>RIN 1018-AX43</RIN>
          <SUBJECT>Endangered and Threatened Wildlife and Plants; Designation of Critical Habitat for Southwestern Willow Flycatcher</SUBJECT>
          <AGY>
            <HD SOURCE="HED">AGENCY:</HD>
            <P>Fish and Wildlife Service, Interior.</P>
          </AGY>
          <ACT>
            <HD SOURCE="HED">ACTION:</HD>
            <P>Final rule.</P>
          </ACT>
          <SUM>
            <HD SOURCE="HED">SUMMARY:</HD>

            <P>We, the U.S. Fish and Wildlife Service (Service), designate revised critical habitat for the southwestern willow flycatcher (<E T="03">Empidonax traillii extimus</E>) (flycatcher) under the Endangered Species Act. In total, approximately 1,975 stream kilometers (1,227 stream miles) are being designated as critical habitat. These areas are designated as stream segments, with the lateral extent including the riparian areas and streams that occur within the 100-year floodplain or flood-prone areas encompassing a total area of approximately 84,569 hectares (208,973 acres). The critical habitat is located on a combination of Federal, State, tribal, and private lands in Inyo, Kern, Los Angeles, Riverside, Santa Barbara, San Bernardino, San Diego, and Ventura Counties in California; Clark, Lincoln, and Nye Counties in southern Nevada; Kane, San Juan, and Washington Counties in southern Utah; Alamosa, Conejos, Costilla, and La Plata Counties in southern Colorado; Apache, Cochise, Gila, Graham, Greenlee, La Paz, Maricopa, Mohave, Pima, Pinal, Santa Cruz, and Yavapai Counties in Arizona; and Catron, Grant, Hidalgo, Mora, Rio Arriba, Socorro, Taos, and Valencia Counties in New Mexico. The effect of this regulation is to conserve the flycatcher's habitat under the Endangered Species Act.</P>
          </SUM>
          <EFFDATE>
            <HD SOURCE="HED">DATES:</HD>
            <P>This rule becomes effective on February 4, 2013.</P>
          </EFFDATE>
          <ADD>
            <HD SOURCE="HED">ADDRESSES:</HD>
            <P>This final rule is available on the Internet at<E T="03">http://www.regulations.gov</E>, Docket No. FWS-R2-ES-2011-0053. Comments and materials received, as well as supporting documentation used in preparing this final rule, are available for public inspection, by appointment, during normal business hours, at the U.S. Fish and Wildlife Service, Arizona Ecological Services Office, 2321 West Royal Palm Rd., Suite 103, Phoenix, AZ 85021; telephone 602-242-0210; facsimile 602-242-2513.</P>

            <P>The coordinates or plot points or both from which the critical habitat maps are generated are included in the administrative record for this critical habitat designation and are available at<E T="03">http://www.fws.gov/southwest/es/arizona</E>,<E T="03">www.regulations.gov</E>at Docket No. FWS-R2-ES-2011-0053, and at the Arizona Ecological Services Office (see<E T="02">FOR FURTHER INFORMATION CONTACT</E>). Any additional tools or supporting information that we may develop for this critical habitat designation will also be available at the Fish and Wildlife Service Web site and Field Office set out above, and may also be included in the preamble or at<E T="03">http://www.regulations.gov</E>.</P>
          </ADD>
          <FURINF>
            <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
            <P>Steve Spangle, Field Supervisor, U.S. Fish and Wildlife Service, Arizona Ecological Services Office, 2321 West Royal Palm Rd., Suite 103, Phoenix, AZ 85021; telephone 602-242-0210; facsimile 602-242-2513. If you use a telecommunications device for the deaf (TDD), call the Federal Information Relay Service (FIRS) at 800-877-8339.</P>
          </FURINF>
        </PREAMB>
        <SUPLINF>
          <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
          <HD SOURCE="HD1">Executive Summary</HD>
          <P>
            <E T="03">Why we need to publish a rule.</E>This is a final rule to revise the designation of critical habitat for the southwestern willow flycatcher (flycatcher). Under the Endangered Species Act (Act), any species that is determined to be an endangered or threatened species requires critical habitat to be designated, to the maximum extent prudent and determinable. Designations and revisions of critical habitat can only be completed by issuing a rule.</P>
          <P>The revised critical habitat areas we are designating in this rule constitute our current best assessment of the areas that meet the definition of flycatcher critical habitat. In total, we are designating as flycatcher critical habitat approximately 1,975 stream kilometers (km) (1,227 stream miles (mi)) encompassing a total area of approximately (84,569 hectares (ha), (208,973 acres (ac)) in 24 Management Units.</P>
          <P>
            <E T="03">We have prepared an economic analysis and environmental assessment for the designation of critical habitat.</E>In order to consider economic impacts, we have prepared an analysis of the economic impacts of the critical habitat designations and related factors. The purpose of the environmental assessment, prepared pursuant to the National Environmental Policy Act (NEPA), is to identify and disclose the environmental consequences resulting from the proposed action of designating revised critical habitat for the flycatcher. We announced the availability of the draft economic analysis and draft environmental assessment in the<E T="04">Federal Register</E>on July 12, 2012 (77 FR 41147), allowing the public to provide comments on our analyses. We have considered the comments and have completed the final economic analysis and final environmental assessment concurrently with this final determination.</P>
          <P>
            <E T="03">Peer review and public comment.</E>We sought comments from independent specialists to ensure that our designation is based on scientifically sound data and analyses. We obtained opinions from four knowledgeable individuals with scientific expertise to review our technical assumptions, analysis, and whether or not we had used the best available information. These peer reviewers generally concurred with our methods and conclusions and provided additional information, clarifications, and suggestions to improve this final rule. Information we received from peer review is incorporated in this final revised designation. We also considered all comments and information received from the public during the comment period.</P>
          <HD SOURCE="HD1">Previous Federal Actions</HD>

          <P>The flycatcher was listed as endangered under the Act (16 U.S.C. 1531<E T="03">et seq.</E>) on February 27, 1995 (60 FR 10694). On July 22, 1997, we published a final critical habitat designation for the flycatcher along 964 river km (599 river mi) in Arizona, California, and New Mexico (62 FR 39129). We published a correction notice on August 20, 1997, on the lateral extent of critical habitat (62 FR 44228).</P>
          <P>As a result of a 1998 lawsuit from the New Mexico Cattle Growers' Association, on October 19, 2005 (70 FR 60886), we published a revised final flycatcher critical habitat rule for portions of Arizona, California, New Mexico, Nevada, and Utah, totaling approximately 48,896 ha (120,824 ac) or 1,186 km (737 mi). River segments were designated as critical habitat in 15 of the 32 Management Units described in the Recovery Plan (Service 2002, p. 63).</P>

          <P>We were sued by the Center for Biological Diversity over our 2005 critical habitat rule, and on July 13, 2010, we agreed to redesignate critical habitat. The resulting settlement left the existing critical habitat designation from 2005 in effect. We proposed a flycatcher critical habitat revision on August 15, 2011 (76 FR 50542), and additional<PRTPAGE P="345"/>proposal information was included in our July 12, 2012 (77 FR 41147), rule reopening the comment period. We requested and received an extension to allow a final rule to be delivered to the<E T="04">Federal Register</E>by December 14, 2012.</P>
          <HD SOURCE="HD1">Background</HD>

          <P>Additional background information on the flycatcher, beyond what is provided below, can be found in the proposed revision of flycatcher critical habitat published on August 15, 2011 (76 FR 50542), as well as the final flycatcher critical habitat rule published in the<E T="04">Federal Register</E>on October 19, 2005 (70 FR 60886); our October 12, 2004, proposed critical habitat rule (69 FR 60706); the Southwestern Willow Flycatcher Recovery Plan (Recovery Plan) (Service 2002, entire); our first flycatcher critical habitat designation, published July 22, 1997 (62 FR 39129), and August 20, 1997 (62 FR 44228); the final flycatcher listing rule (60 FR 10694, February 27, 1995); the 10-year flycatcher study in central Arizona (Paxton<E T="03">et al.</E>2007, entire); the 2007 rangewide status report (Durst<E T="03">et al.</E>2008, entire); and flycatcher survey protocol and natural history summary (Sogge<E T="03">et al.</E>2010, entire). Other reports can be retrieved from the U.S. Geological Survey's (USGS) flycatcher site at<E T="03">http://sbsc.wr.usgs.gov/cprs/research/projects/swwf</E>.</P>
          <HD SOURCE="HD2">Taxonomy</HD>

          <P>The flycatcher, from the taxonomic order Passeriformes, is one of four subspecies of the willow flycatcher currently recognized (Hubbard 1987, pp. 3-6; Unitt 1987, pp. 137-144), although Browning (1993, p. 248) suggests a possible fifth subspecies (<E T="03">Empidonax traillii campestris</E>) in the central and midwestern United States.</P>
          <HD SOURCE="HD2">Species Description</HD>

          <P>The flycatcher is a small, insect-eating generalist (Service 2002, p. 26), neotropical migrant bird. It grows to about 15 centimeters (5.8 inches) in length. It eats a wide range of invertebrate prey including flying, and ground- and vegetation-dwelling, insect species of terrestrial and aquatic origins (Drost<E T="03">et al.</E>2003, pp. 96-102). The flycatcher spends the winter in locations such as southern Mexico, Central America, and probably South America (Ridgely and Gwynne 1989, p. 303; Stiles and Skutch 1989, pp. 321-322; Howell and Webb 1995, pp. 496-497; Unitt 1997, pp. 70-73; Koronkiewicz<E T="03">et al.</E>1998, p. 12; Unitt 1999, p. 14).</P>
          <HD SOURCE="HD2">Distribution</HD>

          <P>The known geographical area historically occupied by migrating and breeding flycatchers includes southern California, southern Nevada, southern Utah, southern Colorado, Arizona, New Mexico, western Texas, and extreme northwestern Mexico (Hubbard 1987, pp. 6-10; Unitt 1987, pp. 144-152; Browning 1993, pp. 248, 250). The flycatcher's current range is similar to the historical range, but the quantity of suitable habitat within that range is reduced from historical levels (Service 2002, pp. 7-10). Flycatchers nest within the southwestern United States from about May to September (Sogge<E T="03">et al.</E>2010, p. 11).</P>
          <P>At the time of listing in February 1995 (60 FR 10694), the distribution and abundance of nesting flycatchers, their natural history, and areas occupied by breeding, nonbreeding, migrating, and dispersing flycatchers were not well known. In February 1995, 359 breeding territories were known only from California, Arizona, and New Mexico. Unitt (1987, p. 156) estimated the entire population was “well under a 1000 pairs, more likely 500,” and 230 to 500 breeding territories (see definition below) were estimated to exist in the July 23, 1993, flycatcher listing proposal (58 FR 39495, p. 39498).</P>

          <P>At the end of 2007, 1,299 flycatcher breeding territories were estimated to occur throughout southern California, southern Nevada, southern Utah, southern Colorado, Arizona, and New Mexico (Durst<E T="03">et al.</E>2008, p. 4). Some of the flycatcher breeding sites (see definition below) having the highest number of territories are found along the middle Rio Grande and upper Gila River in New Mexico, and Roosevelt Lake and the San Pedro and Gila River confluence area in central Arizona.</P>

          <P>A breeding site is simply an area along the river that has been described while surveying for flycatcher territories (Service 2002, p. C-4; Sogge<E T="03">et al.</E>2010, p. 34). A breeding site can contain none, only one, or many territories. However, within this final rule, we refer to breeding sites as areas where flycatcher territories were detected. A territory is defined as a discrete area defended by a single flycatcher or pair of flycatchers within a single breeding season (Sogge<E T="03">et al.</E>2010, p. 34). The territory is usually evidenced by the presence of a singing male, and possibly one or more mates (Sogge<E T="03">et al.</E>2010, p. 34). When we discuss locations occupied by flycatchers, those are locations not just of those areas used as breeding territories, but also of those areas used by foraging, migrating, and dispersing flycatchers for food, cover, and shelter.</P>
          <P>At the time of listing, breeding sites in California, Nevada, Utah, and Colorado described by Unitt (1987, pp. 149-152) were adopted as the subspecies' northern boundary. However, the collection and analysis of genetic material across this part of the flycatcher's range has since refined this boundary (Paxton 2000, pp. 3, 18-20), and reduced the extent of the northern boundary of the southwestern subspecies in Utah and Colorado (Service 2002, Figure 3). Territories once believed to be held by southwestern willow flycatchers in Utah and Colorado are now more accurately known to be occupied by a different, non-listed willow flycatcher subspecies. As a result, the southwestern subspecies' range only occurs in the southernmost portions of Utah and Colorado. This genetic work also confirmed the identity of southwestern willow flycatcher subspecies throughout the rest of its range.</P>

          <P>The USGS has continued to collect genetic information to help refine the northern boundary of the subspecies' range in Utah, Colorado, and New Mexico (Paxton<E T="03">et al.</E>2007a, entire). They reconfirmed the genetic markers that identify differences among flycatcher subspecies, with breeding sites clustering into two groups separated approximately along the currently recognized boundary; however, they noted a distinct genetic boundary line between the subspecies does not exist (Paxton<E T="03">et al.</E>2007a, p. 17). Instead of a distinct boundary, they suggested that the boundary should be thought of as a “region of genetic overlap” (Paxton<E T="03">et al.</E>2007a, p. 17). They also described that this genetic overlap region will likely widen and contract over time based upon habitat changes (Paxton<E T="03">et al.</E>2007a, p. 17). An additional complication in refining the subspecies' northern boundary is that this region is sparsely populated with breeding flycatchers, and therefore only minimal information is available that would help narrow down the location of a boundary (Paxton<E T="03">et al.</E>2007a, p.16). We continue to seek out territories and collect genetic samples to further our understanding of this area, but we currently recognize the northern geographic boundary of the flycatcher as described in the Recovery Plan (Service 2002, Figures 3, 4).</P>

          <P>All willow flycatcher subspecies spend time migrating in the United States from April to June and from July through September. Willow flycatchers, like most small, migratory, insect-eating birds, require food-rich stopover areas<PRTPAGE P="346"/>in order to replenish energy reserves and continue their northward or southward migration (Finch<E T="03">et al.</E>2000, pp. 71, 78, and 79; Service 2002, pp. E-3, 42). Migration stopover areas are likely critically important for flycatcher productivity and survival (Sogge<E T="03">et al.</E>1997, p. 13; Yong and Finch 1997, p. 253; Service 2002, pp. E-3, 19).</P>
          <HD SOURCE="HD2">Habitat</HD>

          <P>The flycatcher currently breeds in areas from near sea level to over 2,600 meters (m) (8,500 feet (ft)) (Durst<E T="03">et al.</E>2008, p. 14) in vegetation alongside rivers, streams, or other wetlands (riparian habitat). It establishes nesting territories, builds nests, and forages where mosaics of relatively dense and expansive growths of trees and shrubs are established, near or adjacent to surface water or underlain by saturated soil (Sogge<E T="03">et al.</E>2010, p. 4). Habitat characteristics such as dominant plant species, size and shape of habitat patch, tree canopy structure, vegetation height, and vegetation density vary widely among breeding sites. Nests are typically placed in trees where the plant growth is most dense, where trees and shrubs have vegetation near ground level, and where there is a low-density canopy. Some of the more common tree and shrub species currently known to comprise nesting habitat include Gooddings willow (<E T="03">Salix gooddingii</E>), coyote willow (<E T="03">Salix exigua</E>), Geyer's willow (<E T="03">Salix geyeriana</E>), arroyo willow (<E T="03">Salix lasiolepis</E>), red willow (<E T="03">Salix laevigata</E>), yewleaf willow (<E T="03">Salix taxifolia</E>), boxelder (<E T="03">Acer negundo</E>), tamarisk (also known as saltcedar,<E T="03">Tamarix ramosissima</E>), and Russian olive (<E T="03">Elaeagnus angustifolia</E>) (Service 2002, p. D-2). While there are exceptions, generally flycatchers are not found nesting in areas without willows, tamarisk, or both.</P>

          <P>Use of riparian habitats along major drainages in the Southwest during migration has been documented (Sogge<E T="03">et al.</E>1997, pp. 3-4; Yong and Finch 1997, p. 253; Johnson and O'Brien 1998, p. 2; McKernan and Braden 1999, p. 17; Koronkiewicz<E T="03">et al.</E>2004, pp. 9-11). Many of the willow flycatchers found migrating are detected in riparian habitats or patches (small areas of riparian vegetation) that would be unsuitable for nest placement (the vegetation structure is too short or sparse, or the patch of vegetation is too small). In these drainages, migrating flycatchers may use a variety of riparian habitats, including ones dominated by native or exotic plant species, or mixtures of both (Service 2002, p. E-3).</P>
          <HD SOURCE="HD2">Life History</HD>
          <P>Flycatchers are believed to exist and interact as groups of metapopulations (Service 2002, p. 72). A metapopulation is a group of geographically separate flycatcher breeding populations connected to each other by immigration and emigration (Service 2002, p. 72). Flycatcher populations are most stable where many connected sites or large populations exist (Service 2002, p. 72). Metapopulation persistence or stability is more likely to improve by adding more breeding sites rather than adding more territories to existing sites (Service 2002, p. 72). This would distribute birds across a greater geographical range, minimize risk of simultaneous catastrophic population loss, and avoid genetic isolation (Service 2002, p. 72).</P>

          <P>Flycatchers have higher site fidelity (to a local area) than nest fidelity (to a specific nest location) and can move among sites within stream drainages and between drainages (Kenwood and Paxton 2001, pp. 29-31). Within-drainage movements are more common than between-drainage movements (Kenwood and Paxton 2001, p. 18). Juvenile flycatchers were the group of flycatchers that moved (dispersed) the farthest to new and distant breeding sites from the area where they hatched (Paxton<E T="03">et al.</E>2007, p. 74). The USGS's 10-year flycatcher study in central Arizona (Paxton<E T="03">et al.</E>2007, entire) is the key movement study that has generated these conclusions, augmented by other flycatcher banding and re-sighting studies (Sedgwick 2004, p. 1103; McLeod<E T="03">et al.</E>2008, p. 110).</P>

          <P>The difference in flycatcher dispersal distance among different study areas and regions reflects the varying spatial arrangement of breeding habitat, illustrating how dispersal tendencies are influenced by the geographic distribution of habitat at the stream segment, drainage, and landscape scales (Paxton<E T="03">et al.</E>2007, p. 75). While USGS's study focused its effort in central Arizona at two of the largest breeding sites, it also included multiple auxiliary sites (up to 444 km (275 mi) away), along with other researchers and surveyors across the flycatcher's range paying attention to whether flycatchers were banded or not. As a result, the broad scope of the study of flycatcher movement extends broadly beyond a localized, regional area, where habitat configuration dominates the results.</P>
          <P>Banded flycatchers from season to season (and sometimes within season) were recorded moving from 50 m (150 feet) to 444 km (275 mi) to try to nest. Some long-distance season-to-season movement records captured flycatchers moving from the Basin and Mojave Recovery Units to the Lower Colorado Recovery Unit and from the Lower Colorado Recovery Unit to the Gila Recovery Unit.</P>

          <P>The USGS assimilated all of the flycatcher movement information and concluded that rapid colonization and increased metapopulation stability could be accomplished by establishing breeding sites within 30 to 40 km (18 to 25 mi) of each other (Paxton<E T="03">et al.</E>2007, p. 4). Flycatchers at breeding sites configured in this way would be able to regularly disperse to new breeding sites or move between known breeding sites within the same year or from year-to-year. This proximity of sites would increase the connectivity and stability of the metapopulation and smaller, more distant breeding sites.</P>
          <HD SOURCE="HD2">Recovery Planning</HD>
          <P>Because the breeding range of the flycatcher encompasses a broad geographic area with much site variation, the Recovery Plan divides the flycatcher's range into six Recovery Units, each of which are further subdivided into four to seven Management Units (for a total of 32 Management Units) (Service 2002, pp. 61-63). This provides an organizational strategy to “characterize flycatcher populations, structure recovery goals, and facilitate effective recovery actions that should closely parallel the physical, biological, and logistical realities on the ground” (Service 2002, p. 61). Recovery Units are defined based on large watershed and hydrologic units. Within each Recovery Unit, Management Units are based on watershed or major drainage boundaries at the Hydrologic Unit Code Cataloging Unit level (standard watershed boundaries which have already been defined for other purposes). The “outer” boundaries of some Recovery Units and Management Units were defined by the flycatcher's range boundaries. Recovery goals are recommended for 29 of the 32 Management Units, and this designation of critical habitat is organized geographically within these Recovery Units and Management Units (see “Methodology Overview” section below).</P>

          <P>The Service's 2002 Recovery Plan provides reasonable actions recommended to recover the flycatcher and provides two criteria, either of which can be met, in order to consider downlisting the species to threatened (Service 2002, pp. 77-78). The first alternative for downlisting requires reaching a total population of 1,500 flycatcher territories geographically distributed among all Recovery Units<PRTPAGE P="347"/>and maintained for 3 years with habitat protections (Service 2002, pp. 77-78). Habitat protections include a variety of options such as habitat conservation plans (HCPs), conservation easements, or safe harbor agreements. The second alternative approach for downlisting calls for reaching a population of 1,950 territories also strategically distributed among all Recovery and Management Units for 5 years without additional habitat protection (Service 2002, pp. 77-78).</P>
          <P>In order to delist this flycatcher subspecies (to remove it from the List of Endangered and Threatened Wildlife), the Recovery Plan recommends that a minimum of 1,950 territories are geographically distributed among all Recovery and Management Units, and that twice the amount of habitat is provided to maintain these territories over time. Second, these habitats must be protected from threats to assure maintenance of these populations and habitat for the foreseeable future through development and implementation of conservation management agreements (Service 2002, pp. 79-80). Third, all of these delisting criteria must be accomplished and their effectiveness demonstrated for a period of 5 years (Service 2002, pp. 79-80). This critical habitat designation is structured to allow the Service to work toward achieving the numerical, geographical, and habitat-related recovery goals.</P>
          <P>Twice the amount of suitable habitat is needed to support the numerical territory goals because the long-term persistence of flycatcher populations cannot be assured by protecting only those habitats in which flycatchers currently breed (Service 2002, p. 80). It is important to recognize that most flycatcher breeding habitats are susceptible to future changes in site hydrology (natural or human-related), human impacts such as development or fire, and natural catastrophic events such as flood or drought (Service 2002, p. 80). Furthermore, as the vegetation at sites matures, it can lose the structural characteristics that make it suitable for breeding flycatchers (Service 2002, p. 80). These and other factors can destroy or degrade breeding sites, such that one cannot expect any given breeding site to remain suitable in perpetuity (Service 2002, p. 80). Thus, it is necessary to have additional suitable habitat available to which flycatchers can readily move if displaced by such habitat loss or change (Service 2002, p. 80).</P>
          <HD SOURCE="HD1">Summary of Changes From Proposed Rule</HD>
          <P>In developing the final revised flycatcher critical habitat designation, we reviewed public comments received on the proposed August 15, 2011 (76 FR 50542), revision to critical habitat and the draft economic analysis, draft environmental assessment, and proposed revisions document made available to the public published on July 12, 2012 (77 FR 41147). We also conducted further evaluation of lands proposed as critical habitat; refined our mapping methodologies; and excluded areas from the final designation pursuant to section 4(b)(2) of the Act (16 U.S.C. 1531 et seq.). We are making the following changes to the final rule from the proposed August 15, 2011, revision and subsequent July 12, 2012, document.</P>
          <HD SOURCE="HD2">Proposed Areas Removed From Final Designation</HD>
          <P>(1) We excluded a number of river segments and reservoir bottoms under section 4(b)(2) of the Act that we identified as being considered for exclusion in the proposed rule (see Exclusions section below). In this final rule, we did not exclude every area that was identified in the proposed rule as being considered for exclusion. For a complete discussion and analysis of areas excluded and an explanation of the basis for exclusion see the Exclusions section. This is the primary source of reduction in the total designated critical habitat area compared to what we identified in the proposal.</P>
          <P>(2) In California, based on information received from public comments, we reviewed maps and reports and reevaluated Little Tujunga Creek in the Santa Clara Management Unit. We discovered that the 2.2-km (1.4-mi) segment of the Little Tujunga Creek is not essential for the flycatcher because it provides minimal habitat, metapopulation stability, and prevention against catastrophic loss. As a result, we determined that it was not essential for flycatcher conservation and did not include it in this final revised critical habitat designation.</P>
          <P>(3) In California, we reevaluated mapped information and proposed critical habitat along the Santa Ana River within the Prado Basin in the Santa Ana Management Unit (76 FR 50542, August 15, 2011, pp. 50563-50564). We detected, through additional analysis, several groundwater recharge ponds and areas at, or below, the 154-m (505-ft) elevation line that will be subject to regular inundation. These areas total approximately 900.2 ha (2,224.5 ac), and they do not represent areas that currently have or can develop flycatcher habitat. As a result, we determined that these locations were not essential for flycatcher conservation and do not include them in this final revised critical habitat designation.</P>
          <P>(4) In Arizona, in response to comments, we reevaluated information through maps, reports, and site-specific knowledge about the proposed segments of the San Francisco River in the San Francisco Management Unit (76 FR 50542, August 15, 2011, p. 50576). This evaluation resulted in determining that a 2.7-km (1.7-mi) segment of the San Francisco River at Luna Lake, Arizona, which we proposed for designation, does not contain the essential physical or biological features of flycatcher habitat, and it does not appear to have the ability to develop into flycatcher nesting habitat. The habitat surrounding Luna Lake is comprised of cattails and meadow grasses, and a narrow section of stream downstream from the lake primarily consists of conifers. As a result, we determined that this portion of the San Francisco River was not essential for flycatcher conservation and do not include it in this final revised critical habitat designation.</P>
          <P>(5) In Arizona, in response to comments, we reevaluated approximately 6.8 ha (16.8 ac) of land within the proposed segment along Pinal Creek, representing about 4 percent of the land outside of the Freeport McMoRan (FMC) administered Pinal Creek Management Area. These lands are located primarily at the perimeter of the floodplain and end of the proposed segment. Because of their placement, these lands provide limited value for the flycatcher outside of the conservation area. As a result, we determined that these disconnected portions of the Pinal Creek floodplain were not essential for flycatcher conservation and do not include them in this final revised critical habitat designation.</P>

          <P>(6) In Nevada, we reevaluated the 17.3-km (10.8-mi) stream and other bodies of water in Pahranagat Valley (hereinafter referred to as the Pahranagat River in this final rule) proposed in the Pahranagat National Wildlife Refuge (NWR) in the Pahranagat Management Unit (76 FR 50542, August 15, 2011, p. 50570). Based on our reevaluation, we determined that the southern 13.7 km (8.5 mi) of this segment is not essential for flycatcher conservation. The habitat along this segment consists of open water, marsh, wet meadow, alkali flats, and upland salt desert shrub. The water along this segment is standing, is<PRTPAGE P="348"/>ephemeral, or has been channelized in ditches. These areas do not currently consist of riparian tree and shrub species and are unlikely to develop the necessary vegetation for flycatcher habitat in the future. As a result, we determined that these locations were not essential for flycatcher conservation and do not include it in this final revised critical habitat designation.</P>
          <P>(7) In Nevada, within the Pahranagat Management Unit, we inaccurately described the Key Pittman Wildlife Area as a 6.3-km (3.9-mi) single stream segment along the Pahranagat River (76 FR 50542, August 15, 2011, p. 50570) and also inaccurately described the area we were considering for exclusion, under section 4(b)(2) of the Act, as a single 4.0-km (2.5-mi) segment (76 FR 50542, p. 50583). The Key Pittman Wildlife Area is more accurately described as being comprised of two separate stream segments, one 2.5 km (1.6 mi) long and the other 1.4 km (0.9 mi) long. Between these two portions of the Key Pittman Wildlife Area is a 2.4-km (1.5-mi) segment of private land, which consists of agricultural fields, and limited water and riparian habitat. Therefore, because of the lack of both flycatcher habitat and likelihood of developing flycatcher habitat in the future, this area between the separate portions of the Key Pittman Wildlife Area should not have been identified as an essential area for flycatcher conservation, and we do not include it in our final critical habitat designation. We are excluding the two stream segments on Key Pittman Wildlife Area under section 4(b)(2) of the Act (see Exclusions section).</P>
          <P>(8) In Colorado, we reevaluated information about the habitat on the Los Pinos River in the San Juan Management Unit (76 FR 50542, August 15, 2011, p. 50571) through maps, reports, and site visits (Ireland T. 2012, entire). We found that the northern 9.1-km (5.6-mi) portion of the Los Pinos River is at a high elevation, with a steep stream slope, and the vegetation composition is not consistent with flycatcher habitat. The plant species adjacent to this stream are mostly comprised of those not used by nesting flycatchers (such as alders and conifers). Therefore, this segment does not currently consist of the riparian tree and shrub species used by flycatchers, and it is unlikely to develop them in the future. As a result, we determined that this portion of the Los Pinos River was not essential for flycatcher conservation, and do not include it in this final revised critical habitat designation.</P>
          <P>(9) In Colorado, there is a collection of checker-boarded parcels of private land interspersed with Southern Ute tribal land along the Los Pinos River within the San Juan Management Unit that, upon further analysis, we do not consider critical habitat because they are not essential for flycatcher conservation. At the perimeter of Southern Ute tribal lands along the Los Pinos River, but outside of tribal jurisdiction, are collectively about 2.7 intermittent river km (1.7 mi) of private lands. Additionally, at the southern end of the Southern Ute Reservation, approximately 1.2 km (0.8 mi) or less of scattered private land parcels occur. Individually, these parcels are at the perimeter of the floodplain, are small in size, and are not contiguous. Collectively, they represent a small fraction of the area we considered for critical habitat along the Los Pinos River. As result of their small size and limited extent of habitat, we do not consider these segments essential to flycatcher conservation and do not include them in this final revised critical habitat designation.</P>
          <P>(10) In Colorado, there are five small parcels of BLM land on the Rio Grande in the San Luis Valley Management Unit that were included in the proposed critical habitat. The farthest upstream section is west of Del Norte and is 300 m (980 feet) long. The other four parcels are south of Alamosa NWR near the Conejos and Costilla County border. The boundary of the first parcel does not intersect with the river but is within the lateral extent of proposed critical habitat and constitutes 3.73 ha (9.21 ac). The second parcel is 135 m (443 feet) long. The third parcel is 0.96 km (0.59 mi) long. The boundary of the fourth parcel also does not intersect the river but is within the lateral extent of proposed critical habitat and constitutes 2.77 ha (6.85 ac). Because these five small, scattered, and limited sections of habitat are not essential to flycatcher recovery, we do not include them in this final revised critical habitat designation.</P>

          <P>(11) In New Mexico, in response to comments, we reevaluated information about the Elephant Butte Reservoir portion of the proposed 211.8-km-km (131.6-mi) Rio Grande segment in the Middle Rio Grande Management Unit (76 FR 50542, August 15, 2011). This evaluation resulted in our determination that the downstream 31.4 km (19.5 mi) of the proposed segment within the active conservation pool of Elephant Butte Reservoir is not critical habitat. The 31.4 km (19.5 mi) downstream portion of the proposed segment that is within the active storage pool of Elephant Butte Reservoir is not necessary for the conservation of flycatcher, as the Unit without this portion meets the quantity of habitat and territories identified as essential for this Management Unit (refer to our<E T="03">Criteria Used To Identify Critical Habitat</E>section). Therefore, we are not including this portion in the designation for this Management Unit.</P>
          <P>More specifically, although the segment contains some elements of the physical or biological features of flycatcher habitat along the reservoir edge, the habitat features in the downstream portion are not essential to flycatcher conservation because the number of flycatcher territories and amount of habitat in the farther upstream portion of this segment have already far exceeded the recovery goals for this Management Unit. The recovery goals in this Management Unit are for 100 flycatcher territories, and the most recent survey data from 2012 found 327 territories in this management unit (USBR 2012, p. 1). Only 33 of these territories occurred in the downstream portion along Elephant Butte Reservoir. Therefore, the upstream portion of the proposed segment within Socorro County has about three times more flycatcher territories than the recovery goals for this management unit. As a result, the lower portion of this segment, where reservoir inundation is more likely, and flycatcher habitat may be less persistent over time, is not needed to reach recovery goals in this management unit. This is consistent with other areas (such as the Roosevelt Management Unit) where we used the numerical and habitat-related recovery goals from the Recovery Plan, along with the current and previous number of known flycatcher territories, to guide the endpoints of critical habitat segments along areas with large populations (see “Methodology Overview,” “Areas with Large Populations”). As a result, we have determined this downstream 31.4 km (19.5 mi) portion of the Rio Grande in Elephant Butte Reservoir does not meet our criteria for, and, therefore, the definition of, critical habitat for the flycatcher, and we have removed it from our final critical habitat designation.</P>
          <HD SOURCE="HD2">Other Changes</HD>
          <P>(12) In California, after further analysis of maps and using information received during comments, we have made three revisions to the approximate stream lengths along tribal lands within the San Diego Management Unit. These lands were subsequently excluded from our final designation under section 4(b)(2) of the Act (see Exclusions section).</P>

          <P>We incorrectly described the length of the San Diego River occurring along the<PRTPAGE P="349"/>Barona Group of Capitan Grande Band of Mission Indians of the Barona Reservation, California and the Viejas (Baron Long) Group of Capitan Grande Mission Indians of the Viejas Reservation, California, as 4.7 km (2.9 mi) (76 FR 50542, August 15, 2011, p. 55082). We have corrected the distance to 0.9 km (0.6 mi) along the San Diego River, consisting of approximately 9.0 ha (22 ac) to accurately reflect tribal ownership of these lands being excluded under section 4(b)(2) of the Act (see Exclusions section).</P>
          <P>We incorrectly described the length of the San Luis Rey River occurring along the tribal lands of the Pala Band of Luiseño Mission Indians, California, as 3.7 km (2.3 mi) (76 FR 50542, August 15, 2011, p. 55082). We have corrected the distance to 8.3 km (5.2 mi) along the San Luis Rey River, to accurately reflect tribal ownership of these lands being excluded under section 4(b)(2) of the Act (see Exclusions section).</P>
          <P>We incorrectly described the length of the San Luis Rey River occurring along the tribal lands of the Rincon Band of Luiseño Mission Indians, California, as 2.4 km (1.5 mi) (76 FR 50542, August 15, 2011, p. 55082). We have corrected the distance to 4.3 km (2.7 mi) along the San Luis Rey River, to accurately reflect tribal ownership of these lands being excluded under section 4(b)(2) of the Act (see Exclusions section).</P>
          <P>(13) In California, we inadvertently did not include the Pala Band of Luiseño Mission Indians' tribal fee lands, currently being brought into trust, for exclusion from the revised critical habitat designation under section (4)(b)(2) of the Act. Subsequently, we received information from them explaining where these fee lands are located, have included them in our exclusion analysis, and are excluding them under section 4(b)(2) of the Act (see Exclusions section).</P>

          <P>(14) In California, we inaccurately described the length of a proposed segment of the Santa Ynez River within the Santa Ynez Management Unit within the unit description portion of our proposed rule (76 FR 50542, August 15, 2011, p. 50563). However, we correctly described the end points on the maps within the<E T="04">Federal Register</E>notice and maps and electronic maps provided on the Internet and at<E T="03">http://www.regulations.gov</E>. The lower Santa Ynez River segment above Vandenberg Air Force Base should more accurately be described as 42.3-km (26.3-mi) segment, not the 27.6-km (17.2-mi) segment described in our proposal.</P>
          <P>(15) In California, we inaccurately described the length of a proposed segment of the Santa Ysabel River within the San Diego Management Unit (76 FR 50542, August 15, 2011, p. 50565). The upper San Ysabel River segment that is contiguous with Temescal Creek should more accurately be described as 8.7-km (5.4-mi) segment, not the 9.8-km (6.1-mi) segment described in our proposal.</P>
          <P>(16) In California, we inaccurately described the length of a proposed segment of the Cañada Gobernadora Creek within the San Diego Management Unit (76 FR 50542, August 15, 2011, p. 50565). The mapped Cañada Gobernadora Creek segment inadvertently included a portion of San Juan Creek. As a result, the portion of San Juan Creek is not included in this designation, and our Cañada Gobernadora Creek segment is now more accurately a 4.7-km (2.9-mi) segment, not the 5.9-km (3.7-mi) segment described in our proposal.</P>
          <P>(17) In Arizona, while we identified San Carlos Apache tribal lands as areas we were considering for exclusion under section 4(b)(2) of the Act, we received new information about parcels of San Carlos Apache tribal lands along the lower San Pedro River between the Aravaipa Creek and Gila River confluence, totaling about 1.0 km (0.6 mi) and 75 ha (185 ha). Subsequently, we have included these separate parcels in our exclusion analysis, and are excluding them under section 4(b)(2) of the Act (see Exclusions section).</P>
          <P>(18) In New Mexico, we inaccurately identified and mapped the location of Navajo Nation (Ramah Navajo) as just south of Zuni Pueblo. The most downstream portion of the Zuni River is not on Navajo Nation (Ramah Navajo) lands, but more accurately part of Zuni Pueblo. This portion of the Zuni River on Zuni Pueblo is excluded from this final revised designation of critical habitat under section 4(b)(2) of the Act (see Exclusions section).</P>
          <P>(19) In New Mexico, we inaccurately described the length of a proposed segment of the Gila River within the Upper Gila Management Unit (76 FR 50542, August 15, 2011, p. 50574). The Gila River segment from the downstream end of the Middle Gila Box Canyon near the Town of Red Rock downstream across the Arizona State line through the Town of Duncan, Arizona, should more accurately be described as 65.3-km (40.6-mi) segment, not the 62.2-km (38.7-mi) segment described in our proposal.</P>
          <P>(20) In Colorado, we included an area within our electronic map of the proposed rule along the Conejos River that was an error. As a result of correcting that error, we are not including an area about 1.6 km (1 mi) in length that was represented as a lateral extent of the Conejos River in this final critical habitat designation. This area included a portion of the Rio Grande National Forest in addition to private land.</P>
          <P>(21) While mapping the lateral extent of critical habitat, some side drainages, tributaries, or washes were included within our electronic maps that extend beyond the confluence of the streams we described in the proposal. These areas sometimes extended well beyond the reasonable confluence area, sometimes about 3 km (1.9 mi) up a tributary. For example, portions of San Juan or San Francisquito Creeks in California, or West Clear Creek and Beaver Creek in Arizona, occurred on our electronic maps. We did not describe these segments in the text of the proposed rule, because they were not intended to be part of our proposal. We have truncated these segments to the best of our ability in the final critical habitat maps, so only those habitats on the rivers described are included in the final designation. The removal of these segments resulted in an overall minor reduction in the amount of critical habitat.</P>
          <P>(22) While mapping the lengths of stream segments electronically, the results can vary as GIS programs attempt to account for the bends and turns along a stream. Additionally, the irregular shape of properties and the exclusion or revision of segments caused challenges in trying to accurately describe a length of a stream segment. Even when the end points of a segment did not change, as we continued to reassess and recalculate stream lengths and round to the nearest tenth, a change in a few tenths of a kilometer or mile sometimes occurred. Therefore, there is expected to be some minor change in stream lengths between our proposal and this final rule.</P>

          <P>(23) Although we attempted to remove as many developed areas as possible (areas that have no conservation value as flycatcher habitat) before publishing the proposed rule, we were not able to eliminate all developed areas. Since publication of the proposed rule and the receipt of more accurate mapping data and information, we were able to further refine the designation, which has resulted in a more precise delineation of habitat containing the physical or biological features necessary to support flycatcher life-history requirements. This resulted in a minor reduction for some segments from the amounts of critical habitat published in the proposed rule. However, it is not possible to remove each and every one of these developed areas even at the<PRTPAGE P="350"/>refined mapping scale used; therefore, the maps of the designation may contain areas that do not contain the physical or biological features necessary for the flycatcher. These areas, which include locations such as roads, cement pads, utility substations, agricultural fields, housing, etc., are not critical habitat and are therefore excluded by text in this final rule.</P>
          <HD SOURCE="HD1">Critical Habitat</HD>
          <HD SOURCE="HD2">Background</HD>
          <P>Critical habitat is defined in section 3 of the Act as:</P>
          <P>(1) The specific areas within the geographical area occupied by the species, at the time it is listed in accordance with the Act, on which are found those physical or biological features:</P>
          <P>(a) Essential to the conservation of the species, and</P>
          <P>(b) Which may require special management considerations or protection; and</P>
          <P>(2) Specific areas outside the geographical area occupied by the species at the time it is listed, upon a determination that such areas are essential for the conservation of the species.</P>
          <P>Conservation, as defined under section 3 of the Act, means to use and the use of all methods and procedures that are necessary to bring an endangered or threatened species to the point at which the measures provided pursuant to the Act are no longer necessary. Such methods and procedures include, but are not limited to, all activities associated with scientific resources management such as research, census, law enforcement, habitat acquisition and maintenance, propagation, live trapping, and transplantation, and, in the extraordinary case where population pressures within a given ecosystem cannot be otherwise relieved, may include regulated taking.</P>
          <P>Critical habitat receives protection under section 7 of the Act through the requirement that Federal agencies ensure, in consultation with the Service, that any action they authorize, fund, or carry out is not likely to result in the destruction or adverse modification of critical habitat. The designation of critical habitat does not affect land ownership or establish a refuge, wilderness, reserve, preserve, or other conservation area. Such designation does not allow the government or public to access private lands. Such designation does not require implementation of restoration, recovery, or enhancement measures by non-Federal landowners. Where a landowner requests Federal agency funding or authorization for an action that may affect a listed species or critical habitat, the consultation requirements of section 7(a)(2) of the Act would apply, but even in the event of a destruction or adverse modification finding, the obligation of the Federal action agency and the landowner is not to restore or recover the species, but to implement reasonable and prudent alternatives to avoid destruction or adverse modification of critical habitat.</P>
          <P>Under the first prong of the Act's definition of critical habitat, areas within the geographical area occupied by the species at the time it was listed are included in a critical habitat designation if they contain physical or biological features (1) which are essential to the conservation of the species and (2) which may require special management considerations or protection. For these areas, critical habitat designations identify, to the extent known using the best scientific and commercial data available, those physical or biological features that are essential to the conservation of the species (such as space, food, cover, and protected habitat). In identifying those physical and biological features within an area, we focus on the principal biological or physical constituent elements (primary constituent elements such as roost sites, nesting grounds, seasonal wetlands, water quality, tide, soil type) that are essential to the conservation of the species. Primary constituent elements are those specific elements of the physical or biological features that provide for a species' life-history processes and are essential to the conservation of the species.</P>
          <P>Under the second prong of the Act's definition of critical habitat, we can designate critical habitat in areas outside the geographical area occupied by the species at the time it is listed, upon a determination that such areas are essential for the conservation of the species. For example, an area currently occupied by the species but that was not occupied at the time of listing may be essential to the conservation of the species and may be included in the critical habitat designation. We designate critical habitat in areas outside the geographical area occupied by a species only when a designation limited to its range would be inadequate to ensure the conservation of the species.</P>

          <P>Section 4 of the Act requires that we designate critical habitat on the basis of the best scientific and commercial data available. Further, our Policy on Information Standards Under the Act (published in the<E T="04">Federal Register</E>on July 1, 1994 (59 FR 34271)), the Information Quality Act (section 515 of the Treasury and General Government Appropriations Act for Fiscal Year 2001 (Pub. L. 106-554; H.R. 5658)), and our associated Information Quality Guidelines, provide criteria, establish procedures, and provide guidance to ensure that our decisions are based on the best scientific data available. They require our biologists, to the extent consistent with the Act and with the use of the best scientific data available, to use primary and original sources of information as the basis for recommendations to designate critical habitat.</P>
          <P>When we are determining which areas should be designated as critical habitat, our primary source of information is generally the information developed during the listing process for the species. Additional information sources may include the recovery plan for the species, articles in peer-reviewed journals, conservation plans developed by States and counties, scientific status surveys and studies, biological assessments, other unpublished materials, or experts' opinions or personal knowledge.</P>

          <P>Habitat is dynamic, and species may move from one area to another over time. This is particularly true for the flycatcher because its riparian vegetation it uses is prone to alteration and regrowth from periodic disturbance, such as flooding. We recognize that critical habitat designated at a particular point in time may not include all of the habitat areas that we may later determine are necessary for the recovery of the species. For these reasons, a critical habitat designation does not signal that habitat outside the designated area is unimportant or may not be needed for recovery of the species. Areas that are important to the conservation of the species, both inside and outside the critical habitat designation, will continue to be subject to: (1) Conservation actions implemented under section 7(a)(1) of the Act; (2) regulatory protections afforded by the requirement in section 7(a)(2) of the Act for Federal agencies to insure their actions are not likely to jeopardize the continued existence of any endangered or threatened species; and (3) section 9 of the Act's prohibitions on taking any individual of the species, including taking caused by actions that affect habitat. Federally funded or permitted projects affecting listed species outside their designated critical habitat areas may still result in jeopardy findings in some cases. These protections and conservation tools will<PRTPAGE P="351"/>continue to contribute to recovery of this species. Similarly, critical habitat designations made on the basis of the best available information at the time of designation will not control the direction and substance of future recovery plans, HCPs, or other species conservation planning efforts if new information available at the time of these planning efforts calls for a different outcome.</P>
          <HD SOURCE="HD2">Physical or Biological Features</HD>
          <P>In accordance with section 3(5)(A)(i) and 4(b)(1)(A) of the Act and regulations at 50 CFR 424.12, in determining which areas within the geographical area occupied by the species at the time of listing to designate as critical habitat, we consider the physical or biological features essential to the conservation of the species and which may require special management considerations or protection. These include, but are not limited to:</P>
          <P>(1) Space for individual and population growth and for normal behavior;</P>
          <P>(2) Food, water, air, light, minerals, or other nutritional or physiological requirements;</P>
          <P>(3) Cover or shelter;</P>
          <P>(4) Sites for breeding, reproduction, or rearing (or development) of offspring; and</P>
          <P>(5) Habitats that are protected from disturbance or are representative of the historical, geographical, and ecological distributions of a species.</P>

          <P>We derive the specific physical or biological features essential for the flycatcher from studies of this species' habitat, ecology, and life history as described below. Additional information can be found in the final listing rule published in the<E T="04">Federal Register</E>on February 27, 1995 (60 FR 10694), and the Flycatcher Recovery Plan (Service 2002, entire), Survey Protocol and Natural History Summary (Sogge<E T="03">et al.</E>2010, entire), and the 10-year central Arizona ecology study (Paxton<E T="03">et al.</E>2007, entire).</P>
          <P>In general, the areas designated as critical habitat are designed to provide sufficient riparian habitat for breeding, non-breeding, territorial, dispersing, and migrating flycatchers in order to reach the geographic distribution, abundance, and habitat-related recovery goals described in the Recovery Plan (Service 2002, pp. 77-85). We are not designating any areas as critical habitat solely because they serve as a migration habitat. Instead, the areas we are designating serve a variety of functions, including habitat to be used by migrating flycatchers. The habitat components important for conservation of this subspecies were determined from studies of flycatcher behavior and habitat use throughout the bird's range (see Background section).</P>

          <P>In general, the physical or biological features of critical habitat for nesting flycatchers are found in the riparian areas within the 100-year floodplain or flood-prone area. Flycatchers use riparian habitat for feeding, sheltering, and cover while breeding, migrating, and dispersing. It is important to recognize that flycatcher habitat is ephemeral in its presence, and its distribution is dynamic in nature because riparian vegetation is prone to periodic disturbance (such as<E T="03"/>flooding) (Service 2002, p. 17). Even with the dynamic shifts in habitat conditions, one or more of the primary constituent elements described below are found throughout each of the units that we are designating as critical habitat.</P>
          <P>Flycatcher habitat may become unsuitable for breeding through maturation or disturbance of the riparian vegetation, but it may remain suitable for use during migration or for foraging. This situation may be only temporary, and vegetation may cycle back into suitability as breeding habitat (Service 2002, p. 17). Therefore, it is not practical to assume that any given breeding habitat area will remain suitable over the long term or persist in the same location (Service 2002, p. 17). Over a 5-year period, flycatcher habitat can, in optimum conditions, germinate, be used for migration or foraging, continue to grow, and eventually be used for nesting. Thus, flycatcher habitat that is not currently suitable for nesting at a specific time, but is useful for foraging and migration, can still be important for flycatcher conservation. Feeding sites and migration stopover areas are important components for the flycatcher's survival, productivity, and health, and they can also be areas where new breeding habitat develops as nesting sites are lost or degraded (Service 2002, p. 42). These successional cycles of habitat change are important for long-term persistence of flycatcher habitat.</P>
          <P>Based on our current knowledge of the life history and ecology of the flycatcher and the relationship of its life-history functions to its habitat, as summarized in the Background section above and in more detail in the Recovery Plan (Service 2002, Chapter II), it is important to recognize the interconnected nature of the physical or biological features that provide the primary constituent elements of critical habitat. Specifically, we consider the relationships between river function, hydrology, floodplains, aquifers, and plant growth, which form the environment essential to flycatcher conservation.</P>

          <P>The hydrologic regime (stream flow pattern) and supply of (and interaction between) surface and subsurface water is a driving factor in the long-term maintenance, growth, recycling, and regeneration of flycatcher habitat (Service 2002, p. 16). As streams reach the lowlands, their gradients typically flatten and surrounding terrain opens into broader floodplains (Service 2002, p. 32). In these geographic settings, the stream-flow patterns (frequency, magnitude, duration, and timing) will provide the necessary stream-channel conditions (wide configuration, high sediment deposition, periodic inundation, recharged aquifers, lateral channel movement, and elevated groundwater tables throughout the floodplain) that result in the development of flycatcher habitat (Poff<E T="03">et al.</E>1997, pp. 770-772; Service 2002, p. 16). Allowing the river to flow over the width of the floodplain, when overbank flooding occurs, is integral to allow deposition of fine moist soils, water, nutrients, and seeds that provide the essential material for plant germination and growth. An abundance and distribution of fine sediments extending farther laterally across the floodplain and deeper underneath the surface retains much more subsurface water, which in turn supplies water for the development of the vegetation that provides flycatcher habitat and micro-habitat conditions (Service 2002, p. 16). The interconnected interaction between groundwater and surface water contributes to the quality of riparian vegetation community (structure and plant species) and will influence the germination, density, vigor, composition, and the ability of vegetation to regenerate and maintain itself (Arizona Department of Water Resources 1994, pp. 31-32).</P>

          <P>In many instances, flycatcher breeding sites occur along streams where human impacts are minimized enough to allow more natural processes to create, recycle, and maintain flycatcher habitat. However, there are also breeding sites that are supported by various types of supplemental water including agricultural and urban run-off, treated water outflow, irrigation or diversion ditches, reservoirs, and dam outflows (Service 2002, p. D-15). Although the waters provided to these habitats might be considered “artificial,” they are often important for maintaining the habitat in appropriate condition for breeding flycatchers within the existing environment.<PRTPAGE P="352"/>
          </P>

          <P>In considering the specific physical or biological features essential for flycatcher conservation, it is also important to consider longer-term processes that may influence habitat changes over time, such as climate change. Climate change is a long-term shift in the statistics of the weather (including its averages). In its<E T="03">Fourth Assessment Report,</E>the Intergovernmental Panel on Climate Change (IPCC) defines climate change as, “a change in the state of the climate that can be identified by changes in the mean and/or variability of its properties and that persists for an extended period, typically decades or longer” (Solomon<E T="03">et al.</E>2007, p. 943). Changes in climate already are occurring. Examples of observed changes in the physical environment include an increase in global average sea level and declines in mountain glaciers and average snow cover in both the northern and southern hemispheres (IPCC 2007a, p. 30). At continental, regional, and ocean basin scales, observed changes in long-term trends of other aspects of climate include: a substantial increase in precipitation in eastern parts of North American and South America, northern Europe, and northern and central Asia; declines in precipitation in the Mediterranean, southern Africa, and parts of southern Asia; and an increase in intense tropical cyclone activity in the North Atlantic since about 1970 (IPCC 2007a, p. 30).</P>

          <P>Projections of climate change globally and for broad regions through the 21st century are based on the results of modeling efforts using state-of-the-art Atmosphere-Ocean General Circulation Models and various greenhouse gas emissions scenarios (Meehl<E T="03">et al.</E>2007, p. 753; Randall<E T="03">et al.</E>2007, pp. 596-599). As is the case with all models, there is uncertainty associated with projections due to assumptions used and other features of the models. However, despite differences in assumptions and other parameters used in climate change models, the overall surface air temperature trajectory is one of increased warming in comparison to current conditions (Meehl<E T="03">et al.</E>2007, p. 762; Prinn<E T="03">et al.</E>2011, p. 527). Among the IPCC's projections for the 21st century are the following: (1) It is virtually certain there will be warmer and more frequent hot days and nights over most of the earth's land areas; (2) it is very likely there will be increased frequency of warm spells and heat waves over most land areas, and the frequency of heavy precipitation events will increase over most areas; and (3) it is likely that increases will occur in the incidence of extreme high sea level (excludes tsunamis), intense tropical cyclone activity, and the area affected by droughts in various regions of the world (IPCC 2007b, p. 8).</P>
          <P>Changes in climate can have a variety of direct and indirect ecological impacts on species, and can exacerbate the effects of other threats. Climate-associated environmental changes to the landscape, such as decreased stream flows, increased water temperatures, reduced snowpack, and increased fire frequency, affect species and their habitats. The vulnerability of a species to climate change impacts is a function of the species' sensitivity to those changes, its exposure to those changes, and its capacity to adapt to those changes. The best available science is used to evaluate the species' response to these stressors. We recognize that future climate change may present a particular challenge evaluating habitat conditions for species like the flycatcher because the additional stressors may push species beyond their ability to survive in their present location.</P>

          <P>Exactly how climate change will affect precipitation in the specific areas with flycatcher habitat is uncertain. However, consistent with recent observations of regional effects of climate change, the projections presented for the Southwest predict warmer, drier, and more drought-like conditions (Hoerling and Eischeid 2007, p. 19; Seager<E T="03">et al.</E>2007, p. 1181). For example, climate simulations of the Palmer Drought Severity Index (a calculation of the cumulative effects of precipitation and temperature on surface moisture balance) for the Southwest for the periods of 2006 to 2030 and 2035 to 2060 show an increase in drought severity with surface warming. Additionally, drought still increases even during wetter simulations because of the effect of heat-related moisture loss through evaporation and evapotranspiration (Hoerling and Eischeid 2007, p. 19). Annual mean precipitation is likely to decrease in the Southwest, as is the length of snow season and snow depth (IPCC 2007b, p. 887). Most models project a widespread decrease in snow depth in the Rocky Mountains and earlier snowmelt (IPCC 2007b, p. 891). In summary, we expect that climate change will result in a warmer, drier climate, and reduced surface water across the flycatcher's range.</P>

          <P>In the recent past, drought has had both negative and positive effects on breeding flycatchers and their habitat, which can provide insight into how climate change may affect flycatchers and flycatcher habitat. For example, the extreme drought of 2002 caused near complete reproductive failure of the 146 flycatcher territories at Roosevelt Lake in central Arizona (Smith<E T="03">et al.</E>2003, pp. 8, 10), and caused a dramatic rise in the prevalence of non-breeding and unpaired flycatchers (Paxton<E T="03">et al.</E>2007, p. 4). While extreme drought during a single year can generate impacts to breeding success, drought can also have localized short-term benefits in some regulated environments. For instance, at some reservoirs (such as Roosevelt Lake, Arizona, and Lake Isabella, California), drought led to reduced water storage, which increased the exposure of wet soils at the lake's perimeter. Continued drought in those areas allowed the exposed areas to grow vegetation and become new flycatcher nesting habitat (Ellis<E T="03">et al.</E>2008, p. 44). These short-term and localized habitat increases are not likely sustainable with persistent drought or long-term predictions of a drier environment, because of the overall importance of the presence of surface water and elevated groundwater needed to grow dense riparian forests for flycatcher habitat. As a result, we expect long-term climate trends associated with a drier climate to have an overall negative effect on the available rangewide habitat for flycatchers.</P>
          <P>Considering these issues and other information regarding the biology and ecology of the species, we have determined that the flycatcher requires the essential physical or biological features described below.</P>
          <HD SOURCE="HD3">Space for Individual and Population Growth and for Normal Behavior</HD>

          <P>Streams of lower gradient and more open valleys with a wide and broad floodplain are the geological settings that are known to support flycatcher breeding habitat from near sea level to about 2,600 m (8,500 ft) in elevation in southern California, southern Nevada, southern Utah, southern Colorado, Arizona, and New Mexico (Service 2002, p. 7). Lands with moist conditions that support riparian plant communities are areas that provide flycatcher habitat. Conditions like these typically develop in lower elevation floodplains as well as where streams enter impoundments, either natural (such as beaver ponds) or human-made (reservoirs). Low-gradient stream conditions may also occur at high elevations, as in the marshy mountain meadows supporting flycatchers in the headwaters of the Little Colorado River near Greer, Arizona, or the flat-gradient portions of the upper Rio Grande in south-central Colorado and northern New Mexico (Service 2002, p. 32). Sometimes, the<PRTPAGE P="353"/>low-gradient wider floodplain exists only at the habitat patch itself within a stream that is otherwise steeper in gradient (Service 2002, p. D-12).</P>
          <P>Relatively steep, confined streams can also support flycatcher breeding habitat (Service 2002, p. D-13). For instance, a portion of the San Luis Rey River in California supports a substantial flycatcher population and stands out among flycatcher habitats as having a relatively high gradient and being confined in a fairly narrow, steep-sided valley (Service 2002, p. D-13). Even a steep, confined canyon or mountain stream may present local conditions where just a small area less than a hectare (acre) in size of flycatcher breeding habitat may develop (Service 2002, p. D-13). Such sites are important individually and in aggregate to contribute to metapopulation stability, site connectivity, and gene flow (Service 2002, p. D-13). Flycatchers can occupy very small, isolated habitat patches and may occur in fairly high densities within those small patches.</P>

          <P>Many willow flycatchers are found along streams using riparian habitat during migration (Yong and Finch 1997, p. 253; Service 2002, p. E-3). Migration stopover areas can be similar to breeding habitat or riparian habitats with less vegetation density and abundance compared to areas for nest placement (the vegetation structure is too short or sparse or the patch is too small) (Service 2002, p. E-3). For example, many locations where migrant flycatchers were detected on the lower Colorado River (LCR) (Koronkiewicz<E T="03">et al.</E>2004, pp. 9-11) and throughout Arizona in 2004 (Munzer<E T="03">et al.</E>2005, Appendix C) were areas surveyed for territories, but none were detected. Such migration stopover areas, even though not used for breeding, are critically important resources affecting productivity and survival (Service 2002, p. E-3). The variety of riparian habitat occupied by migrant flycatchers ranges from small patches with shorter and sparser vegetation to larger more complex breeding habitats.</P>
          <P>Therefore, based on the information above, we identify streams of lower gradient and more open valleys with a wide or broad floodplain an essential physical or biological feature of flycatcher habitat. In some instances, streams in relatively steep, confined areas can also support flycatcher breeding habitat (Service 2002, p. D-13). These areas support the abundance of riparian vegetation used for flycatcher nesting, foraging, dispersal, and migration.</P>
          <HD SOURCE="HD3">Food, Water, Air, Light, Minerals, or Other Nutritional or Physiological Requirements</HD>
          <HD SOURCE="HD3">Food</HD>

          <P>The flycatcher is somewhat of an insect generalist (Service 2002, p. 26), taking a wide range of invertebrate prey including flying, and ground- and vegetation-dwelling species of terrestrial and aquatic origins (Drost<E T="03">et al.</E>2003, pp. 96-102). Wasps and bees (Hymenoptera) are common food items, as are flies (Diptera), beetles (Coleoptera), butterflies, moths and caterpillars (Lepidoptera), and spittlebugs (Homoptera) (Beal 1912, pp. 60-63; McCabe 1991, pp. 119-120). Plant foods such as small fruits have also been reported (Beal 1912, pp. 60-63; Roberts 1932, p. 20; Imhof 1962, p. 268), but are not a significant food during the breeding season (McCabe 1991, pp. 119-120). Diet studies of adult flycatchers (Drost<E T="03">et al.</E>1998, p.1; DeLay<E T="03">et al.</E>1999, p. 216) found a wide range of prey taken. Major prey items were small (flying ants) (Hymenoptera) to large (dragonflies) (Odonata) flying insects, with Diptera and Hemiptera (true bugs) comprising half of the prey items. Willow flycatchers also took non-flying species, particularly Lepidoptera larvae. From an analysis of the flycatcher diet along the South Fork of the Kern River, California (Drost<E T="03">et al.</E>2003, p. 98), flycatchers consumed a variety of prey from 12 different insect groups. Flycatchers have been identified targeting seasonal hatchings of aquatic insects along the Salt River arm of Roosevelt Lake, Arizona (Paxton<E T="03">et al.</E>2007, p. 75).</P>
          <P>Flycatcher food availability may be largely influenced by the density and species of vegetation, proximity to and presence of water, saturated soil levels, and microclimate features such as temperature and humidity (Service 2002, pp. 18, D-12). Flycatchers forage within and above the tree canopy, along the patch edge, in openings within the territory, over water, and from tall trees as well as herbaceous ground cover (Bent 1960, pp. 209-210; McCabe 1991, p. 124). Flycatchers employ a “sit and wait” foraging tactic, with foraging bouts interspersed with longer periods of perching (Prescott and Middleton 1988, p. 25).</P>
          <P>Therefore, based on the information above, we identify the presence of a wide range of invertebrate prey, including flying and ground- and vegetation-dwelling species of terrestrial and aquatic origins to be an essential physical or biological feature of flycatcher habitat.</P>
          <HD SOURCE="HD3">Water</HD>

          <P>Flycatcher nesting habitat is largely associated with perennial (persistent) stream flow that can support the expanse of vegetation characteristics needed by breeding flycatchers, but there are exceptions. Flycatcher nesting habitat can persist on intermittent (ephemeral) streams that retain local conditions favorable to riparian vegetation (Service 2002, p. D-12). The range and variety of stream flow conditions (frequency, magnitude, duration, and timing) (Poff<E T="03">et al.</E>1997, pp. 770-772) that will establish and maintain flycatcher habitat can arise in different types of both regulated and unregulated flow regimes throughout its range (Service 2002, p. D-12). Also, flow conditions that will establish and maintain flycatcher habitat can be achieved in regulated streams, depending on scale of operation and the interaction of the primary physical characteristics of the landscape (Service 2002, p. D-12).</P>
          <P>In the Southwest, hydrological conditions at a flycatcher breeding site can vary remarkably within a season and between years (Service 2002, p. D-12). At some locations, particularly during drier years, water or saturated soil is only present early in the breeding season (May and part of June) (Service 2002, p. D-12). At other sites, vegetation may be immersed in standing water during a wet year but be hundreds of meters from surface water in dry years (Service 2002, p. D-12). This is particularly true of reservoir sites such as the Kern River at Lake Isabella, California; Roosevelt Lake, Arizona; and Elephant Butte Reservoir, New Mexico (Service 2002, p. D-12). Similarly, where a river channel has changed naturally, there may be a total absence of water or visibly saturated soil for several years. In such cases, the riparian vegetation and any flycatchers breeding within it may persist for several years (Service 2002, p. D-12).</P>

          <P>In some areas, natural or managed hydrologic cycles can create temporary flycatcher habitat, but may not be able to support it for an extended amount of time, or may support varying amounts of habitat at different points in the cycle. Some dam operations create varied situations that allow different plant species to thrive when water is released below a dam, held in a lake, or removed from a lakebed, and consequently, varying degrees of flycatcher habitat are available as a result of dam operations (Service 2002, p. 33). The riparian vegetation that constitutes flycatcher breeding habitat requires substantial water (Service 2002,<PRTPAGE P="354"/>p. D-12). Because flycatcher breeding habitat is often where there is slow-moving or still water, these slow and still water conditions may also be important in influencing the production of insect prey base for flycatcher food (Service 2002, p. D-12). These slow-moving water situations can also be managed or mimicked through manipulated supplemental water originating from sources such as agricultural return flows or irrigation canals (Service 2002, p. D-15).</P>
          <P>Therefore, based on the information above, we identify flowing streams with a wide range of stream flow conditions that support expansive riparian vegetation as an essential physical feature of flycatcher habitat. The most common stream flow conditions are largely perennial (persistent) stream flow with a natural hydrologic regime (frequency, magnitude, duration, and timing). However, in the Southwest, hydrological conditions can vary, causing some flows to be intermittent, but the floodplain can retain surface moisture conditions favorable to expansive and flourishing riparian vegetation. These appropriate conditions can be supported by managed water sources and hydrological cycles that mimic key components of the natural hydrologic cycle.</P>
          <HD SOURCE="HD3">Sites for Germination or Seed Dispersal</HD>
          <P>Subsurface hydrologic conditions may in some places (particularly at the more arid locations of the Southwest) be equally important to surface water conditions in determining riparian vegetation patterns (Lichivar and Wakely 2004, p. 92). Where groundwater levels are elevated to the point that riparian forest plants can directly access those waters, it can be an area for breeding, non-breeding, territorial, dispersing, foraging, and migrating flycatchers. Elevated groundwater helps create moist soil conditions believed to be important for nesting conditions and prey populations (Service 2002, pp. 11, 18), as further discussed below.</P>
          <P>Depth to groundwater plays an important part in the distribution of riparian vegetation (Arizona Department of Water Resources 1994, p. 31) and, consequently, flycatcher habitat. The greater the depth to groundwater below the land surface, the less abundant the riparian vegetation (Arizona Department of Water Resources 1994, p. 31). Localized, perched aquifers (a saturated area that sits above the main water table) can and do support some riparian habitat, but these systems are not extensive (Arizona Department of Water Resources 1994, p. 31).</P>
          <P>The abundance and distribution of fine sediment deposited on floodplains is critical for the development, abundance, distribution, maintenance, and germination of the plants that grow into flycatcher habitat (Service 2002, p. 16). Fine sediments provide seed beds to facilitate the growth of riparian vegetation for flycatcher habitat. In almost all cases, moist or saturated soil is present at or near breeding sites during wet and non-drought years (Service 2002, p. 11). The saturated soil and adjacent surface water may be present early in the breeding season, but only damp soil is present by late June or early July (Service 2002, p. D-3). Microclimate features (temperature and humidity) facilitated by moist or saturated soil, are believed to play an important role where flycatchers are detected and nest, their breeding success, and availability and abundance of food resources (Service 2002, pp. 18, D-12).</P>
          <P>Therefore, based on the information above, we identify elevated subsurface groundwater taZbles and appropriate floodplain fine sediments as essential physical or biological features of flycatcher habitat. These features provide water and seedbeds for the germination, growth, and maintenance of expansive growth of riparian vegetation needed by the flycatcher.</P>
          <HD SOURCE="HD3">Cover or Shelter</HD>
          <P>Riparian vegetation (described more in detail within the “Sites for Breeding, Reproduction, or Rearing (or Development) of Offspring” section) also provides the flycatcher cover and shelter while migrating and nesting. Placing nests in dense vegetation provides cover and shelter from predators or nest parasites that would seek out flycatcher adults, nestlings, or eggs. Similarly, using riparian vegetation for cover and shelter during migration provides food-rich stopover areas, a place to rest, and shelter or cover along migratory flights (Service 2002, pp. D-14, F-16). Riparian vegetation used by migrating flycatchers can sometimes be less dense and abundant than areas used for nesting (Service 2002, p. D-19). However, migration stopover areas, even though not used for breeding, may be critically important resources affecting local and regional flycatcher productivity and survival (Service 2002, p. D-19).</P>
          <P>Therefore, based on the information above, we identify riparian tree and shrub species (described in more detail below) that provide cover and shelter for nesting, breeding, foraging, dispersing, and migrating flycatchers as essential physical or biological features of flycatcher habitat.</P>
          <HD SOURCE="HD3">Sites for Breeding, Reproduction, or Rearing (or Development) of Offspring</HD>
          <HD SOURCE="HD3">Reproduction and Rearing of Offspring</HD>
          <P>Riparian habitat characteristics such as dominant plant species, size and shape of habitat patches, tree canopy structure, vegetation height, and vegetation density are important parameters of flycatcher breeding habitat, although they may vary widely at different sites (Service 2002, p. D-1). The accumulating knowledge of flycatcher breeding sites reveals important areas of similarity, which constitute the basic concept of what is suitable breeding habitat (Service 2002, p. D-2). These habitat features are generally discussed below.</P>
          <P>Flycatchers nest in thickets of trees and shrubs ranging in height from 2 m to 30 m (6 to 98 ft) (Service 2002, p. D-3). Lower-stature thickets (2-4 m or 6-13 ft tall) tend to be found at higher elevation sites, with tall-stature habitats at middle- and lower-elevation riparian forests (Service 2002, p. D-2). Nest sites typically have dense foliage at least from the ground level up to approximately 4 m (13 ft) above ground, although dense foliage may exist only at the shrub level, or as a low, dense tree canopy (Service 2002, p. D-3).</P>

          <P>Regardless of the plant species' composition or height, breeding sites usually consist of dense vegetation in the patch interior, or an aggregate of dense patches interspersed with openings creating a mosaic that is not uniformly dense (Service 2002, p. 11). Common tree and shrub species currently known to comprise nesting habitat include Gooddings willow, coyote willow, Geyer's willow, arroyo willow, red willow, yewleaf willow, pacific willow (<E T="03">Salix lasiandra</E>), boxelder, tamarisk, and Russian olive (Service 2002, pp. D-2, D-11). Other plant species used for nesting have been buttonbush (<E T="03">Cephalanthus occidentalis</E>), cottonwood, stinging nettle (<E T="03">Urtica dioica</E>), alder (<E T="03">Alnus rhombifolia, Alnus oblongifolia, Alnus tenuifolia</E>), velvet ash (<E T="03">Fraxinus velutina</E>), poison hemlock (<E T="03">Conium maculatum</E>), blackberry (<E T="03">Rubus ursinus</E>), seep willow (<E T="03">Baccharis salicifolia, Baccharis glutinosa</E>), oak (<E T="03">Quercus agrifolia, Quercus chrysolepis</E>), rose (<E T="03">Rosa californica, Rosa arizonica, Rosa multiflora</E>), sycamore (<E T="03">Platanus wrightii</E>), giant reed (<E T="03">Arundo donax</E>), false indigo (<E T="03">Amorpha californica</E>), Pacific poison ivy (<E T="03">Toxicodendron diversilobum</E>), grape<PRTPAGE P="355"/>(<E T="03">Vitis arizonica</E>), Virginia creeper (<E T="03">Parthenocissus quinquefolia</E>), Siberian elm (<E T="03">Ulmus pumila</E>), and walnut (<E T="03">Juglans hindsii</E>) (Service 2002, pp. D-3, D-5, D-9). Other species used by nesting flycatchers may become known over time as more studies and surveys occur.</P>
          <P>Canopy density (the amount of cover provided by tree and shrub branches measured from the ground) at various nest sites ranged from 50 to 100 percent (Service 2002, p. D-3). Flycatcher breeding habitat can be generally organized into three broad habitat types—those dominated by native vegetation (typically willow), by exotic (nonnative) vegetation (typically salt cedar), and those with mixed native and those dominated by exotic plants (typically salt cedar and willow).</P>
          <P>These broad habitat descriptors reflect the fact that flycatchers inhabit riparian habitats dominated by both native and nonnative plant species. Salt cedar and Russian olive are two exotic plant species used by flycatchers for nest placement and also foraging and shelter (Service 2002, p. D-4). The riparian patches used by breeding flycatchers vary in size and shape (Service 2002, p. D-2). They may be relatively dense, linear, contiguous stands or irregularly-shaped mosaics of dense vegetation with open areas (Service 2002, pp. D-2-D-11).</P>

          <P>Flycatchers use tamarisk (or salt cedar) and Russian olive for nest placement, foraging, roosting, cover, migration, and dispersal. Fewer than half (44 percent) of the known flycatcher territories occur in habitat patches that are greater than 90 percent native vegetation in composition (Durst<E T="03">et al.</E>2008, p.15). About 50 percent of all known flycatcher territories are located at breeding sites that include mixtures of native and exotic plant species (mostly tamarisk) (Durst<E T="03">et al.</E>2008, p.15). In many of these areas, exotic plant species are significant contributors to the habitat structure by providing the dense lower strata vegetation that flycatchers prefer (Durst<E T="03">et al.</E>2008, p.15). A USGS comparative study (Sogge<E T="03">et al.</E>2005, p. 1) found no difference in flycatcher physiology, immunology, site fidelity, productivity, or survivorship between flycatchers nesting in tamarisk-dominated habitat versus native-dominated habitats. Tamarisk habitats vary with respect to suitability for breeding flycatchers across their range, just as do native habitats (Sogge<E T="03">et al.</E>2005, p.1). While the literature refutes or questions the negative environmental impacts of tamarisk (Glenn and Nagler 2005, pp. 1-2; USGS 2010, pp. vi-xviii), many riparian vegetation improvement projects focus on the eradication or control of tamarisk. The implementation of these projects requires careful evaluation (see Special Management Considerations or Protections below) and success can rely on the improvement of the physical or biological features included in this determination associated with river flow and groundwater (Service 2002, Appendices H and K).</P>

          <P>Flycatchers have been recorded nesting in patches as small as 0.1 ha (0.25 ac) along the Rio Grande, and as large as 70 ha (175 ac) in the upper Gila River, New Mexico (Service 2002, p. 17). The mean reported size of flycatcher breeding patches was 8.6 ha (21.2 ac), with the majority of sites toward the smaller end, as evidenced by a median patch size of 1.8 ha (4.4 ac) (Service 2002, p. 17). Mean patch size of breeding sites supporting 10 or more flycatcher territories was 24.9 ha (62.2 ac). Aggregations of occupied breeding patches within a breeding site may create a riparian mosaic as large as 200 ha (494 ac), such as areas like the Kern River (Whitfield 2002, p. 2), Alamo Lake, Roosevelt Lake (Paradzick<E T="03">et al.</E>1999, pp. 6-7), and Lake Mead (McKernan 1997, p. 13).</P>

          <P>Flycatchers can cluster their territories into small portions of riparian sites (Whitfield and Enos 1996, p. 2; Sogge<E T="03">et al.</E>1997, p. 24), and major portions of the site may only be used briefly or not at all in any given year. Habitat modeling based on remote sensing and electronic Geographic Information System (GIS) data has found that breeding site occupancy at reservoir sites in Arizona is influenced by vegetation characteristics of habitat adjacent to the actual nesting areas (Hatten and Paradzick 2003, pp. 774, 782); therefore, areas adjacent to nest sites can be an important component of a breeding site. How size and shape of riparian patches relate to factors such as flycatcher nest-site selection and fidelity, reproductive success, predation, and brood parasitism is unknown (Service 2002, p. D-11).</P>
          <P>With only some exceptions, flycatchers are generally not found nesting in confined floodplains (typically those bound within a narrow canyon) (Hatten and Paradzick 2003, p. 780) or where only a single narrow strip of riparian vegetation less than approximately 10 m (33 ft) wide develops (Service 2002, p. D-11). While riparian vegetation too mature, too immature, or of lesser quality in abundance and breadth may not be used for nesting, it can be used by breeding flycatchers for foraging (especially if it extends out from larger patches) or during migration for foraging, cover, and shelter (Sogge and Tibbitts 1994, p. 16; Sogge and Marshall 2000, p. 53).</P>
          <P>Therefore, based on the information above, we identify a variety of riparian tree and shrub species as essential physical or biological features of flycatcher habitat. Typically, dense expansive riparian forests provide habitat to place nests. Riparian vegetation of broader quality, with a mosaic of open spaces, typically surround locations to place nests or along river segments and provide vegetation for foraging, perching, dispersal, and migration, and habitat that can develop into nesting areas through time.</P>
          <HD SOURCE="HD2">Primary Constituent Elements for Flycatcher</HD>
          <P>Under the Act and its implementing regulations, we are required to identify the physical or biological features essential to flycatcher conservation in areas occupied at the time of listing, focusing on the features' primary constituent elements. Primary constituent elements are those specific elements of the physical or biological features that provide for a species' life-history processes and are essential to the conservation of the species.</P>
          <P>Based on our current knowledge of the physical or biological features and habitat characteristics required to sustain the species' life-history processes, we determine that the primary constituent elements specific to the flycatcher are:</P>
          <P>(1) Primary Constituent Element 1—<E T="03">Riparian vegetation.</E>Riparian habitat along a dynamic river or lakeside, in a natural or manmade successional environment (for nesting, foraging, migration, dispersal, and shelter) that is comprised of trees and shrubs (that can include Gooddings willow, coyote willow, Geyer's willow, arroyo willow, red willow, yewleaf willow, pacific willow, boxelder, tamarisk, Russian olive, buttonbush, cottonwood, stinging nettle, alder, velvet ash, poison hemlock, blackberry, seep willow, oak, rose, sycamore, false indigo, Pacific poison ivy, grape, Virginia creeper, Siberian elm, and walnut) and some combination of:</P>
          <P>(a) Dense riparian vegetation with thickets of trees and shrubs that can range in height from about 2 to 30 m (about 6 to 98 ft). Lower-stature thickets (2 to 4 m or 6 to 13 ft tall) are found at higher elevation riparian forests and tall-stature thickets are found at middle- and lower-elevation riparian forests;</P>

          <P>(b) Areas of dense riparian foliage at least from the ground level up to<PRTPAGE P="356"/>approximately 4 m (13 ft) above ground or dense foliage only at the shrub or tree level as a low, dense canopy;</P>
          <P>(c) Sites for nesting that contain a dense (about 50 percent to 100 percent) tree or shrub (or both) canopy (the amount of cover provided by tree and shrub branches measured from the ground);</P>
          <P>(d) Dense patches of riparian forests that are interspersed with small openings of open water or marsh or areas with shorter and sparser vegetation that creates a variety of habitat that is not uniformly dense. Patch size may be as small as 0.1 ha (0.25 ac) or as large as 70 ha (175 ac).</P>
          <P>(2) Primary Constituent Element 2—<E T="03">Insect prey populations.</E>A variety of insect prey populations found within or adjacent to riparian floodplains or moist environments, which can include: flying ants, wasps, and bees (Hymenoptera); dragonflies (Odonata); flies (Diptera); true bugs (Hemiptera); beetles (Coleoptera); butterflies, moths, and caterpillars (Lepidoptera); and spittlebugs (Homoptera).</P>
          <P>With this critical habitat designation, we intend to identify the physical or biological features essential to the conservation of the species, through the identification of the features' primary constituent elements sufficient to support the life-history processes of the species.</P>
          <HD SOURCE="HD2">Physical or Biological Features and Primary Constituent Elements Summary</HD>
          <P>The discussion above outlines those physical or biological features essential to flycatcher conservation and presents our rationale as to why those features were selected. The primary constituent elements described above are results of the dynamic river or lakeside environment that germinates, develops, maintains, and regenerates the riparian forest and provides food for breeding, non-breeding, dispersing, territorial, and migrating flycatchers.</P>
          <P>Anthropogenic factors such as dams, irrigation ditches, or agricultural field return flow can assist in providing or mimicking the conditions that support flycatcher habitat. In regulated environments, riparian vegetation improvement projects associated with planting, irrigation, and cultivation may also require manual manipulation to maintain suitability over the long term.</P>
          <P>Because the flycatcher exists in disjunct breeding populations across a wide geographic and elevation range and its habitat is subject to dynamic events (such as flooding and drying), the quantity and spatial arrangement of critical habitat river segments described below are essential for the flycatcher to maintain metapopulation stability, connectivity, and gene flow, and to protect against catastrophic loss. All river segments designated as flycatcher critical habitat are either: (1) Within the known range of the subspecies, representing areas known to be occupied at the time of listing; or (2) essential areas for the conservation of the species not known to be occupied by the flycatcher at the time of listing, but now may or may not be known to have flycatchers present. These areas contain at least one the primary constituent elements of the physical or biological features essential for the conservation of the subspecies. It is important to recognize that the primary constituent elements such as riparian vegetation with trees and shrubs of a certain type and insect prey populations are present throughout the river segments selected, but the specific quality of riparian habitat for nesting (which involve elements such as specific configuration of riparian foliage, sites for nesting, and interspersion of small openings), migration, foraging, and shelter will not remain constant in condition or location over time due to succession (plant germination and growth) and the dynamic environment in which they exist.</P>

          <P>In order to reach the goal of conserving the subspecies by recovering an adequate geographical distribution that represents ecological diversity of the flycatcher populations, the distribution and abundance of flycatcher habitat and breeding populations must improve across the 29 Management Units (see Background section). The recovery goal is 1,950 flycatcher territories geographically and numerically distributed in the appropriate Management Units along with twice the habitat needed to maintain these territories (see Background section). Also, these areas must hold these populations for a number of years and be protected through conservation agreements or other means. The most recent rangewide flycatcher assessment estimated that there were about 1,300 flycatcher territories (Durst<E T="03">et al.</E>2008, p. 13). The Lower Colorado, Upper Colorado, and Basin and Range Recovery Units need the most growth in known territories and habitat to reach recovery goals. While there is still great variance in the known number of territories within the Coastal California, Gila, and Rio Grande Recovery Units, these areas are closer in number of territories and amount of habitat to the established recovery goals. The numeric territory goals established per Management Unit are in denominations of 25. The goal for some Management Units may be as few as 25 territories or as many as 325.</P>
          <P>With this designation of critical habitat, we intend to identify the physical or biological features essential to the conservation of the species, through the identification of the features' primary constituent elements sufficient to support the life-history processes of the species.</P>
          <HD SOURCE="HD2">Special Management Considerations or Protections</HD>
          <P>When designating critical habitat, we assess whether the specific areas within the geographical area occupied by the species at the time of listing contain features that are essential to the conservation of the species and which may require special management considerations or protection.</P>
          <P>As mentioned briefly or referenced in this rule, the flycatcher and its habitat are threatened by a multitude of factors occurring at once. Threats to those features that define critical habitat (elements of physical or biological features) are caused by various factors. We believe the essential features within the critical habitat areas will require some level of management or protection (or both) to address the current and future threats and maintain the quality, quantity, and arrangement of the elements of physical or biological features essential to flycatcher conservation.</P>
          <P>Essential features in need of special management occur not only at the immediate locations where the flycatcher may be present, but at additional areas needed to reach recovery goals and areas that can provide for normal population fluctuations and habitat succession that may occur in response to natural and unpredictable events. The flycatcher may be dependent upon habitat components beyond the immediate areas where individuals of the species occur if they are important in maintaining ecological processes such as hydrologic regimes; plant germination, growth, maintenance, and regeneration (succession); sedimentation; groundwater elevations; plant health and vigor; or maintenance of prey populations.</P>

          <P>The designation of critical habitat does not imply that lands outside of critical habitat do not play an important role in flycatcher conservation. Federal activities outside of critical habitat are still subject to review under section 7 of the Act if they may affect the flycatcher or its critical habitat (such as groundwater pumping, developments, watershed condition). Prohibitions of<PRTPAGE P="357"/>section 9 of the Act also continue to apply both inside and outside of designated critical habitat.</P>
          <P>A detailed discussion of threats to the flycatcher and its habitat can be found in the final listing rule (60 FR 10694, February 27, 1995), the previous critical habitat designations (62 FR 39129, July 22, 1997; 70 FR 60886, October 19, 2005), and the final Recovery Plan (Service 2002, pp. 33-42, Appendix F). Some of the special management actions that may be needed for essential features of flycatcher habitat are briefly summarized below.</P>
          <P>(1) Restore adequate water-related elements to improve and expand the quality, quantity, and distribution of riparian habitat. Special management may: increase efficiency of groundwater management; use urban water outfall and irrigation delivery and tail waters for vegetation improvement; maintain, improve, provide, or reestablish instream flows to expand the quality, distribution, and abundance of riparian vegetation; increase the width between levees to expand the active channel during overbank flooding; and manage regulated river flows to more closely resemble the natural hydrologic regime.</P>
          <P>(2) Retain riparian vegetation in the floodplain. Special management may include the following actions: avoid clearing channels for flood flow conveyance or plowing of flood plains; and implement projects to minimize clearing of vegetation (including exotic vegetation) to help ensure that desired native species and exotic vegetation persist until an effective riparian vegetation improvement plan can be implemented.</P>
          <P>(3) Manage biotic elements and processes. Special management may include the following actions: manage livestock grazing to increase flycatcher habitat quality and quantity by determining appropriate areas, seasons, and use consistent within the natural historical norm and tolerances; reconfigure grazing units, improve fencing, and improve monitoring and documentation of grazing practices; manage wild and feral hoofed-mammals (ungulates) (e.g., elk, horses, burros) to increase flycatcher habitat quality and quantity; and manage keystone species such as beaver to restore desired processes to increase habitat quality and quantity.</P>
          <P>(4) Protect riparian areas from recreational impacts. Special management may include actions such as managing trails, campsites, off-road vehicles, and fires to prevent habitat development and degradation in flycatcher habitat.</P>
          <P>(5) Manage exotic plant species, such as tamarisk or Russian olive, by reducing conditions that allow exotics to be successful, and restoring or reestablishing conditions that allow native plants to thrive. Throughout the range of the flycatcher, the success of exotic plants within river floodplains is largely a symptom of land and water management (for example, groundwater withdrawal, surface water diversion, dam operation, and unmanaged grazing) that has created conditions favorable to exotic plants over native plants. Special management may include the following actions: eliminate or reduce dewatering stressors such as surface water diversion and groundwater pumping to increase stream flow and groundwater elevations; reduce salinity levels by modifying agricultural practices and restoring natural hydrologic regimes and flushing flood flows; in regulated streams, restore more natural hydrologic regimes that favor germination and growth of native plant species. Improve timing of water draw down in lake bottoms to coincide with the seed dispersal and germination of native species; and restore ungulate herbivory to intensities and levels under which native riparian species are more competitive.</P>
          <P>(6) Manage fire to maintain and enhance habitat quality and quantity. Special management may include the following actions: suppress fires that occur; and reduce risk of fire by restoring elevated groundwater levels, base flows, flooding, and natural hydrologic regimes in order to prevent drying of riparian areas and more flammable exotic plant species from developing; and reduce risk of recreational fires.</P>
          <P>(7) Evaluate and conduct exotic plant species removal and native plant species management on a site-by-site basis. If habitat assessments reveal a sustained increase in exotic plant abundance, conduct an evaluation of the underlying causes and conduct vegetation improvement under measures described in the Recovery Plan (Service 2002, Appendices H and K). Remove exotics only if: underlying causes for dominance have been addressed; there is evidence that exotic species will be replaced by vegetation of higher functional value; and the action is part of an overall vegetation improvement plan. Native riparian vegetation improvement plans should include: a staggered approach to create mosaics of different aged successional tree and shrub stands; consideration of whether the sites are presently occupied by nesting flycatchers; and management of stressors that can improve the germination, growth, and maintenance of preferred vegetation.</P>

          <P>(8) Manage or reduce the occurrence, spread, and effects of biocontrol agents on flycatcher habitat. Exotic biocontrol tamarisk leaf beetle insects (leaf beetles) were brought into and released in many locations throughout the western United States. This specific U.S. Department of Agriculture program was terminated in 2010, largely because these insects are moving farther and thriving in the southwestern United States (within the flycatcher's breeding range) where it was initially believed they would not persist (APHIS 2010, p. 2). However, leaf beetles still exist within the United States, and specifically within the northern range of the flycatcher in Nevada, Arizona, and New Mexico. It is unknown to what extent these leaf beetles will continue to move throughout the Southwest. Their overall impact or benefit to the flycatcher, flycatcher habitat, and other wildlife species is also unknown, but there are predictions that the beetles could occur throughout the western United States and into northern Mexico (Tracy<E T="03">et al.</E>2008, pp. 1-3). There is concern about effects to the flycatcher in places throughout much of its range where the landscape does not support healthy native riparian vegetation (even in the absence of tamarisk). Along the Virgin River in southwestern Utah, flycatcher breeding attempts have failed concurrent with leaf beetle impacts to the vegetation (Paxton<E T="03">et al.</E>2010, p.1). Rangewide, tamarisk is a habitat component of over half of all known flycatcher territories (Durst<E T="03">et al.</E>2007, p. 15). Therefore, it would be beneficial to prevent purposeful or accidental intra- or interstate transport of leaf beetles to locations that would increase the likelihood of beetles dispersing to flycatcher habitat. Similarly, because insects can travel or be moved large distances, prevent the additional release of leaf beetles (in all their varieties) into the environment where they can eventually occur within flycatcher habitat. Where leaf beetle-related impacts may occur or are happening, consider the previous items in this list and the Recovery Plan for strategies to help improve the germination and growth of native plants (Service 2002, p. Appendix K).</P>
          <HD SOURCE="HD2">Criteria Used To Identify Critical Habitat</HD>

          <P>As required by section 4(b)(1)(A) of the Act, we use the best scientific and commercial data available to designate critical habitat. We review available information pertaining to the habitat requirements of the species (or in this<PRTPAGE P="358"/>instance, a willow flycatcher subspecies). In accordance with the Act and its implementing regulation at 50 CFR 424.12(e), we consider whether designating additional areas—outside those currently occupied as well as those occupied at the time of listing—are necessary to ensure the conservation of this flycatcher subspecies.<E T="03"/>As defined under section 3(5)(A)(i) of the Act, we are designating critical habitat in areas within the geographical area known to be occupied by nesting flycatchers at the time of listing in 1995 that contain the essential physical or biological features and require special management or protections. As defined under section 3(5)(A)(ii) of the Act, we also are designating specific areas outside the geographical area occupied by nesting flycatchers at the time of listing (but that are within its known historical breeding distribution), because such areas are essential for the conservation of the species as supported by the geographical and numerical flycatcher territory and habitat-related recovery goals established in the Recovery Plan (Service 2002, pp. 84-85).</P>
          <HD SOURCE="HD3">Stream Segments as Critical Habitat</HD>

          <P>We are designating “stream segments” as the descriptor for the designated area of flycatcher critical habitat (which in some areas also includes exposed reservoir bottoms). Stream segments are appropriate for delineating critical habitat because in addition to providing stream-side vegetation for flycatchers to place nests, stream segments satisfy other various flycatcher life needs adjacent to or between nesting sites (foraging habitat, streams, elevated groundwater tables, moist soils, flying insects, and other alluvial floodplain habitats) (see<E T="03">Physical or Biological Features</E>section). Also, the dynamic processes of riparian vegetation succession (loss and regrowth) and river hydrology allow for stream segments to provide both current and future areas for flycatcher habitat to grow. Riparian vegetation in these segments is expected to naturally expand and contract from flooding, inundation, drought, and the resulting changes in the extent and location of floodplains and river channels (Service 2002, pp. 18, D-13-D-15). Therefore, while one or more of the physical or biological features are currently present, over time these habitat features will fluctuate in quality or location throughout these stream segments. Management of stream flows and other anthropogenic (manmade) factors, such as agricultural practices or dam operations, can also influence the location and quality of the riparian vegetation in many of these stream segments. The lateral extent of each river segment occurs within the 100-year floodplain (see<E T="03">Physical or Biological Features</E>section) and is further described below (see Lateral Extent section). Therefore, designating stream segments as critical habitat will provide for the variety of flycatcher uses and allow for ever-changing streamside vegetation habitat quality (in location and abundance).</P>
          <HD SOURCE="HD3">Occupancy at the Time of Listing</HD>
          <P>We identified areas occupied at the time of listing in 1995 as those streams where flycatcher territories were detected in any one season from surveys conducted from 1991 to 1994 (Sogge and Durst 2008). The flycatcher rangewide database (Sogge and Durst 2008) is the authoritative source for determining territories because our 1995 flycatcher listing rule did not list all known data regarding flycatcher distribution and abundance. We considered a broader area to be occupied than just the specific site where a territory was located because flycatchers are a neotropical migrant traveling between Central America (and possibly northern South America) and the United States using migration stopover areas for food, cover, and shelter, and they are known to move to different nest areas from year to year.</P>

          <P>Because flycatchers are neotropical migrants that occupy riparian areas along rivers while traveling between wintering and breeding grounds, we expect that abundant small areas along long stretches of stream can be irregularly occupied by migrant flycatchers from year-to-year. North- and south-bound migrating flycatchers are frequently found occupying stopover areas along streams upstream of, downstream of, and between known breeding sites (Yong and Finch 1997, pp. 265-266; Service 2002, pp. E2-E3; Koronkiewicz<E T="03">et al.</E>2004, pp. 9-11). In Arizona, migrant flycatchers were detected at 204 sites statewide along 15 of 19 river drainages surveyed for nesting flycatchers over a 10-year period (Ellis<E T="03">et al.</E>2008, p. 26). Over 600 migrant willow flycatchers (subspecies not known) were detected along the length of the LCR in 2004 (Ellis<E T="03">et al.</E>2008, p. 26), where only a relatively few known breeding sites and territories exist.</P>

          <P>Similarly, flycatchers are known to have fidelity to a larger area along stream drainages (rather than specific nest site fidelity), and can move their territory locations about 30 to 40 km (18 to 25 mi) from year to year (Paxton<E T="03">et al.</E>2007, p. 4). Locations with breeding habitat that are within 30 to 40 km (18 to 25 mi) of each other will have higher metapopulation connectivity, and there is a higher probability of colonization of new habitats that are within this distance (Paxton<E T="03">et al.</E>2007, p. 76). Sometimes, flycatchers can even move to a very distant location, dispersing as far as 444 km (275 mi) from a previous year's nesting area (Paxton<E T="03">et al.</E>2007, p. 2). These year-to-year movements are facilitated by the dynamic nature of flycatcher habitat, changing in quality and location over time. More dramatic changes in habitat quality caused by events such as flooding or inundation can force flycatchers to move their breeding location, thus causing them to use broader locations and habitat quality.</P>
          <P>Therefore, for this wide-ranging bird, it is difficult to precisely determine known occupied areas due to the following considerations: (1) The flycatcher's neotropical migratory habits of occupying stopover areas along streams upstream of, downstream of, and between breeding sites; and (2) the season-to-season variation in habitat quality and subsequent lack of specific nest-site fidelity. As a result, for the purpose of this critical habitat designation, we believe it is most conservative and reasonable to conclude that any stream segment along a stream where flycatcher territories were detected from 1991 to 1994 also be considered occupied at the time of listing. Those stream segments considered occupied at the time of listing and those considered not occupied at the time of listing that we are designating as revised critical habitat are organized by Recovery and Management Units (see below) and described briefly in the unit descriptions below. All of the stream segments occupied at the time of listing contain one or more of the primary constituent elements supported by the physical or biological features, which may require special management considerations, or protection as described above. We also include whether flycatcher territories were detected on stream segments not known to be occupied at the time of listing (but are essential for flycatcher conservation).</P>
          <HD SOURCE="HD3">Recovery Plan Guidance</HD>

          <P>We relied heavily on the Recovery Plan (Service 2002) to help identify the areas that we are designating as revised critical habitat because the Recovery Plan represents a compilation of the best scientific data available to us. We particularly used the information from the Recovery Plan, such as distribution and abundance of flycatchers, flycatcher<PRTPAGE P="359"/>natural history and habitat needs, and stream segments with substantial recovery value, to help identify stream segments with features essential to flycatcher conservation.</P>
          <P>The Recovery Plan's strategy, rationale, and science for conservation of the flycatcher guided our efforts to identify essential features (elements in sufficient quantity and spatial arrangement) and areas of critical habitat (Service 2002, pp. 61-95). Because of the wide distribution of this bird and the dynamic nature of its habitat, it was important to designate critical habitat in areas throughout all of the breeding range of the flycatcher that have stated recovery goals. This widespread distribution of habitat is intended to allow flycatchers to function as a group of metapopulations, realize gene flow throughout its range, provide ecological connectivity among disjunct populations, allow for breeding site colonization potential, and prevent catastrophic population losses.</P>
          <P>The Recovery Plan (Service 2002, pp. 74-76) identifies important factors to consider in minimizing the likelihood of extinction. These factors were also considered in our approach to designating areas for critical habitat: (1) The territory is the appropriate unit of measure for numerical flycatcher recovery goals; (2) populations should be distributed throughout the bird's range; (3) populations should be distributed close enough to each other to allow for movement among them; (4) large populations contribute most to metapopulation stability, while smaller populations can contribute to metapopulation stability when arrayed in a matrix with high connectivity; (5) as the population of a site increases, the potential to disperse and colonize increases; (6) increase and decrease in one population affects other populations; (7) some Recovery and Management Units have stable metapopulations, but others do not; (8) maintaining or augmenting (or both) existing populations is a greater priority than establishing new populations; and (9) establishing habitat close to existing breeding sites increases the chance of colonization.</P>
          <HD SOURCE="HD3">Methodology Overview</HD>
          <P>Our goal was to propose stream segments as critical habitat within 29 of the 32 Management Units (which are geographic areas clustered within 6 Recovery Units) in order to meet the specific numerical flycatcher territory and habitat-related recovery goals (Service 2002, pp. 84-85), which are the same criteria that we are using to identify physical or biological features and designate areas that are essential to flycatcher conservation. Three of the 32 Management Units (Lower Gila, Pecos, and Texas) do not have any goals identified in the Recovery Plan because of either the lack of habitat, the inability for habitat to recover, or the determination that meaningful populations could not be established and persist. Therefore, no critical habitat was proposed or designated within these three Management Units. Numerical flycatcher territory recovery goals for each of the 29 Management Unit vary throughout the flycatcher's range from as few as 25 territories to as many as 325 (Service 2002, pp. 84-85).</P>
          <P>In relying on these recovery goals and strategies, we used a methodology with two basic strategies to identify areas and, subsequently, river segments within those areas to propose and consider as critical habitat. First, we identified areas based upon the presence of large breeding populations and areas with multiple small breeding populations that when found in proximity, form a large population. Once these areas were established, we identified the specific end points of the stream segments of flycatcher habitat. Second, for those Management Units with a specific number of territories required to meet recovery goals, but no, or very few, known flycatcher territories, we used information from the Recovery Plan (Service 2002, pp. 86-92) and other relevant sources to identify river segments with flycatcher habitat. The results of this strategy were the identification of streams that: (1) Were within the geographical area known to be occupied by flycatchers at the time of listing with elements of the physical or biological features; (2) the identification of essential areas that were not known to be occupied by flycatchers at the time of listing but that also include elements of the physical or biological features of critical habitat; and (3) the identification of areas for critical habitat that have never been known to be occupied by flycatchers but are essential for the conservation of the flycatcher in order to meet recovery goals.</P>
          <HD SOURCE="HD3">Areas With Large Populations</HD>

          <P>To identify the areas with flycatcher habitat in each Management Unit, we first considered specific areas that are known since 1991 to have had large populations of nesting flycatchers. Since the time of listing in 1995, the known distribution and abundance of flycatcher territories has increased primarily due to increased survey effort (Durst<E T="03">et al.</E>2008, p. 4). Population increases have also been detected at specific areas where habitat quality and quantity improved. As a result of more extensive surveys and research, and in particular re-establishing known occupancy of breeding sites in Nevada, Utah, and Colorado, the extent of streams known to be used by migrating, non-breeding, and dispersing flycatchers has also expanded. Following the most recent rangewide estimate in 2007, 1,299 territories were described occurring in California, Nevada, Utah, Colorado, Arizona, and New Mexico (Durst<E T="03">et al.</E>2008, p. 4). Additional sites have been detected in the following years, but an updated rangewide estimate has not yet been compiled.</P>

          <P>The locations of breeding sites were generated from standardized flycatcher surveys conducted from 1991 to 2010. There has been a standardized survey protocol since the 1995 listing of the flycatcher that biologists have used to confirm the presence of flycatcher territories that has produced reliable and accurate information (Tibbitts<E T="03">et al.</E>1994, p. 1; Sogge<E T="03">et al.</E>1997, p. 1; Sogge<E T="03">et al.</E>2010, p. 1). To help ensure the protocol is being used properly, the Service and our partners provide annual training on protocol implementation and flycatcher status, identification, and natural history.</P>

          <P>A variety of sources were used to determine breeding site location and information from 1991 to 2010. The Recovery Plan (Service 2002), the USGS flycatcher rangewide database (Sogge and Durst 2008), the 2007 flycatcher rangewide report (Durst<E T="03">et al.</E>2008), and recent survey information for the 2008, 2009, and 2010 breeding seasons were all used as authoritative sources of information on breeding flycatcher distribution and abundance. The flycatcher rangewide database developed and maintained by USGS (Sogge and Durst 2008) compiles the results of surveys conducted throughout the bird's range since 1991. The most recent rangewide assessment of flycatcher distribution and abundance analyzed by USGS (Durst<E T="03">et al.</E>2008) estimates the number of territories that occur following the 2007 breeding season, taking into account that the entire range of the flycatcher is not surveyed completely in any single year. A summary of known historical breeding records can be found in the Recovery Plan (Service 2002, pp. 8-10). We also evaluated data in reports submitted during section 7 consultations and by biologists holding section 10(a)(1)(A) recovery permits; research published in peer-reviewed articles, agency reports, and databases;<PRTPAGE P="360"/>and regional GIS coverages and habitat models.</P>

          <P>We also examined 2008 to 2010 data that the Service in Arizona, Nevada, Utah, and Colorado compiled and entered into separate databases and spreadsheets and data from the USGS and U.S. Bureau of Reclamation (USBR) for California and New Mexico, respectively. These data were compatible and therefore able to be added to results of the 2007 USGS rangewide database (Sogge and Durst 2008) and report (Durst<E T="03">et al.</E>2008, entire) to identify breeding site locations, territory abundance and distribution, and large populations. However, these additional 3 years of raw data have not been synthesized by USGS into their overall USGS rangewide database (Sogge and Durst 2008) and analyzed (consistent with Durst<E T="03">et al.</E>2008, entire) to estimate the overall existing number of territories across the flycatcher's range in a single year. Since this newer information has not be analyzed along with the remainder of the data, the data up to 2007 were the best available information for us to identify the overall number of estimated territories known to occur across a geographic area, such as a Management Unit or Recovery Unit. Therefore, the best available information for estimating the number of territories rangewide is the compiled information up through the 2007 breeding season (Durst<E T="03">et al.</E>2008, entire; Sogge and Durst 2008).</P>
          <P>In order to identify areas with large flycatcher populations, we first considered and defined a “large” population. We defined a large population as a single breeding site or collection of smaller connected breeding sites that support 10 or more territories in a single year. We selected 10 or more territories to identify a large population because the flycatcher population viability analysis indicates a breeding site exhibits greatest long-term stability with at least 10 territories (Service 2002, p. 72). Large populations persist longer than small ones, and produce more dispersers capable of emigrating to other populations or colonizing new areas (Service 2002, p. 74). In addition, smaller populations with high connectivity to other small populations can provide as much or more stability than a single isolated larger population with the same number of territories because of the potential to disperse colonizers throughout the network of breeding sites (Service 2002, p. 75).</P>

          <P>Once the distribution and abundance of flycatcher breeding sites were identified and mapped, we considered the degree of connectivity to assign smaller separate flycatcher breeding sites and the distance from large populations to evaluate these areas as critical habitat. In other words, how much area around breeding sites should be considered as critical habitat? To determine these distances, we examined the known between-year movements of banded adult and juvenile flycatchers. The USGS's 10-year flycatcher study in central Arizona is the key movement study that has generated these conclusions (Paxton<E T="03">et al.</E>2007, pp. 59-80), augmented by other flycatcher banding and re-sighting studies (Sedgwick 2004, p. 1103; McLeod<E T="03">et al.</E>2008, pp. 93-112). These studies found that flycatchers have higher site fidelity than nest fidelity and can move among breeding sites within drainages and between drainages (Kenwood and Paxton 2001, pp. 30-31). Within-drainage movements are more common than between-drainage movements (Paxton<E T="03">et al.</E>2007, p. 77). Juveniles disperse the farthest and were the only group of flycatchers to connect very distant populations (Paxton<E T="03">et al.</E>2007, p. 74). Banded flycatchers from season-to-season were recorded moving across a wide area from 50 m (150 feet) to 444 km (275 mi) (Paxton<E T="03">et al.</E>2007, p. 2).</P>

          <P>Because of the broad range of flycatcher movements, it is a challenge to apply a single distance to characterize the degree of connectivity of separated flycatcher breeding sites. However, USGS (Paxton<E T="03">et al.</E>2007, pp. 4, 76, 84, 139, 140) assimilated all of the movement information and concluded that rapid colonization of flycatcher breeding sites and increased metapopulation stability could be accomplished by establishing breeding sites within 30 to 40 km (18 to 25 mi) of each other. Flycatchers at these breeding sites can disperse or move between sites within the same year or from year-to-year. This proximity of these sites would increase the connectivity and stability of the metapopulation and smaller, more distant breeding sites.</P>
          <P>As a result of USGS's conclusion, we decided to use 35 km (22 mi), the average of the reported range, as a radius to identify an area surrounding known large flycatcher breeding sites and the distance to connect smaller populations to identify a large population. Because there was no distinction by USGS of a distance within this 30 to 40 km (18 to 25 mi) range that was more valuable to flycatchers, we believe the average is the best representation. After a large population area was established, we determined whether other breeding sites in proximity occurred. If so, this would add to our large population area, generate an additional 35-km (22-mi) radius and extend our area, and so on. We also used this 35-km (22-mi) radius to identify those highly connected breeding sites with a small number of territories that together equaled a large flycatcher population.</P>
          <P>Following the identification of these areas that surround large flycatcher populations, we determined where flycatcher habitat occurred on streams and where to establish end points for critical habitat. We used the Recovery Plan and other literature sources and local knowledge to identify stream segments. In combination with these areas of flycatcher habitat, we then considered the numerical and habitat-related recovery goals, and current and previous number of known territories. We also considered site-specific knowledge of these streams, aerial photography, agency reports, and input from other resource managers. The proximity and connectivity of segments to known populations and metapopulation stability were also key aspects of the flycatcher's natural history we considered in delineating river segment end points.</P>

          <P>In both the Roosevelt and Middle Rio Grande Management Units, our methods identified a large population area where the current number of flycatcher territories needed to reach management unit recovery goals has been surpassed by two and three times, respectively. In order to identify stream segments and end points for critical habitat that supports our recovery goals in this unique situation, we considered additional factors such as the known fluctuation and persistence of territories over time (such as those associated with reservoir inundation), territory proximity, and metapopulation stability. Both Management Units have large flycatcher populations located within the conservation space of reservoirs, which can produce a large amount of habitat and number of territories. But the persistence of these reservoir habitats and territories can also be lessened as a result of precipitation, river inflow, and dam operations that affect habitat availability over time. Therefore, because of the dynamic fluctuation of habitat and territories within these reservoirs, we selected areas of habitat that overall can contain a greater number of territories than are identified in the Recovery Plan in order to meet the goals for habitat and territory persistence over time. These habitats included portions of reservoirs and streamside habitat outside of these reservoirs, which together, can support the goals of territory and habitat<PRTPAGE P="361"/>persistence through time when lake elevations remain high. With the number of current territories far exceeding recovery goals in these Management Units, we found that some occupied habitats at the perimeter of our large population areas became less important to reach recovery goals. Because of the unique situation where the number of territories exceeds the numerical goals established in the Recovery Plan, we did not identify some portions of stream segments with territories along the Rio Grande and Salt River as critical habitat. Although these areas were occupied at the time of listing and had some of the elements of physical and biological features, they were determined not to be essential for flycatcher conservation and were not included as critical habitat.</P>
          <P>Nearly the entire areas of the San Diego and Santa Ana Management Units in the Coastal California Recovery Unit were identified as a large population area because of the wide distribution and proximity of occupied streams segments within them. In contrast to other Management Units, our methods were unable to distinguish more specific areas to designate within these Management Units.</P>
          <P>Also, our methodology discussed above was unable to distinguish areas within some Management Units where neither large populations nor small populations with high connectivity were known to occur. For example, in the Amargosa, Santa Cruz, San Francisco, Hassayampa and Agua Fria, San Juan, Powell, and Lower Rio Grande Management Units, there are no known breeding sites with 10 or more flycatcher territories, nor are any known territories in high connectivity that create a large population. Similarly, in some Management Units a large population and surrounding area was identified, but that area was found not to be of adequate size to include enough river segments needed to support the number of territories called for in the recovery goals. This situation occurred in the Little Colorado, Santa Ynez, and Santa Clara Management Units. In all of these cases, we used the guidance from the Recovery Plan, local knowledge about habitat, and other information available to identify additional stream segments as important to meet recovery goals, and therefore, essential for the conservation of flycatcher.</P>
          <P>When generating the river segments in the situations where there were few territories to help guide us, we relied heavily upon recommendations and strategies provided in the Recovery Plan and local knowledge of habitat conditions, maps, and flycatcher natural history. We also sought information from other sources through this critical habitat designation process. The Recovery Plan identified portions of streams for each Management Unit that would contribute significantly toward recovery (Service 2002, pp. 86-92). These streams were not listed for the purpose of designating critical habitat nor were they intended to be the only streams that were important for recovery, but they did identify streams of substantial recovery value. Also, we have generated additional information since the Recovery Plan was completed about river segments and whether they have or do not have substantial recovery value. Still, the list of stream segments described in the Recovery Plan (Service 2002, pp. 86-92) provides important guidance, especially for Management Units where there are few known flycatcher sites, to guide our critical habitat designation. Site-specific knowledge of these streams, aerial photography, agency reports, and input from other resource managers were also considered. The proximity and connectivity of segments to known populations and metapopulation stability were also key aspects of the flycatcher's natural history we considered in delineating these areas.</P>
          <P>The streams designated as revised flycatcher critical habitat are described below. Those streams not within the geographical area known to be occupied at the time of listing were determined to be essential for flycatcher conservation.</P>
          <HD SOURCE="HD3">Migratory Habitat</HD>

          <P>Habitat for migrating flycatchers is captured in this revised designation by our approach to identify critical habitat as “river segments” and distributing segments across the flycatcher's breeding range within the southwestern United States. We are currently unable to distinguish the value of specific locations along particular streams for flycatcher migration, because stopover areas contain broad habitat quality in wide-ranging locations, are only for short-term use, and have uncertain occurrence from year-to-year (Finch<E T="03">et al.</E>2000, pp. 73, 76-77). Additionally, flycatchers are difficult to distinguish from other flycatcher species and subspecies during migration (Finch<E T="03">et al.</E>2000, pp. 71-72). Migrant flycatchers can sometimes be found in unusual locations away from riparian areas (Finch<E T="03">et al.</E>2000, p. 76), but many, if not most, are detected while searching for nesting flycatchers (McLeod<E T="03">et al.</E>2005, pp. 9-11; Ellis<E T="03">et al.</E>2008, pp. 26-27). An extensive study of flycatcher habitat use along the LCR (from Lake Mead to Mexico) and some of its major tributaries in Arizona and southern Nevada and Utah found migrating flycatchers in consecutive years occurring in nearly all study areas and over half of the survey sites (McLeod<E T="03">et al.</E>2005, pp. 9-11; Koronkiewicz<E T="03">et al.</E>2006, pp. 11-13). Similarly, migratory flycatcher movement was regularly detected along the Middle Rio Grande (Yong and Finch 1997, p. 255). As a result of these factors, we expect similar flycatcher migration behavior for the other major drainages where flycatchers breed throughout its range and where these locations are included within this designation. Therefore, flycatcher migration habitat is captured within our methods for identifying critical habitat to reach recovery goals, because: (1) We are designating areas as broader river segments; (2) our areas will be geographically located across a broad area of the Southwest encompassing most of the range of the flycatcher; and (3) we are identifying areas surrounding territory and breeding sites where migrant flycatchers are most often detected.</P>
          <HD SOURCE="HD3">Lateral Extent</HD>
          <P>For the lateral extent or width of flycatcher critical habitat, we considered the variety of purposes riparian habitat serves the flycatcher; the dynamic nature of rivers and riparian habitat; the relationship between the location of rivers, flooding, and riparian habitat; and the expected boundaries, over time, of these habitats. The condition or quality of riparian habitat that flycatchers use adjacent to streams for breeding, feeding, sheltering, cover, dispersal, and migration stopover areas varies. Riparian habitat is dependent on the location of river channels, floodplain soils, subsurface water, and floodplain shape, and is driven by the wide variety of high, medium, and low flow events. In addition, manmade factors such as diversion ditches or agricultural return flows can also influence riparian vegetation distribution. Over time, river channels can braid or move from one side of the floodplain to the other. Flooding occurs at periodic frequencies that recharge aquifers and that deposit and moisten fine floodplain soils which create seedbeds for riparian vegetation germination and growth within these boundaries.</P>

          <P>In this designation, we consider the riparian zone where flycatcher habitat occurs to be the area surrounding the select river segment that is directly influenced by river functions. The present boundaries, for mapping purposes, of the lateral extent or riparian zone (in other words, the<PRTPAGE P="362"/>surrogate for the delineation of the lateral boundaries of critical habitat within stream segments) were derived by one of two methods. The area was either captured from existing digital data sources (listed below) or created through expert visual interpretation of remotely sensed data (aerial photographs and satellite imagery—also listed below). GIS technology was utilized throughout the lateral extent determination. ESRI, Inc. ArcInfo 8.3 was used to perform all mapping functions and image interpretation. Pre-existing data sources used to assist in the process of delineating the lateral extent of the riparian zones for this designation included: (1) National Wetlands Inventory digital data from the mid-1980s, 2001, and 2002; (2) Federal Emergency Management Agency 1995, Q3 100 year flood data; (3) U.S. Census Bureau Topologically Integrated Geographic Encoding and Referencing (TIGER); and (4) 2000 digital data. The riparian zone is anticipated to occur within the 100-year floodplain.</P>
          <P>Where pre-existing data may not have been available to readily define riparian zones, visual interpretation of remotely sensed data was used to define the lateral extent. Data sources used in this included: (1) Terraserver online Digital Orthophoto Quarter Quads, black and white, 1990s era and 2001; (2) USGS Digital Orthophoto Quarter Quads 1997; (3) USGS aerial photographs, 1 meter, color-balanced, and true color, 2002; (4) Landsat 5 and Landsat 7 Thematic Mapper, bands 4, 2, 3, 1990-2000; (5) Emerge Corp, 1 meter, true color imagery, 2001; (6) Local Agency Partnership, 2 foot, true color, 2000; and (7) NWI aerial photographs, 2001-2002.</P>

          <P>We refined all lateral extents for this designation by creating electronic maps of the lateral extent and attributing them according to the following riparian sub-classifications. Riparian developed areas, as defined below, are not included in our critical habitat designation since these areas do not contain the primary constituent elements (see<E T="03">Primary Constituent Elements for the Flycatcher</E>section above), are not considered essential to flycatcher conservation and, therefore, do not meet the definition of critical habitat. We separated riparian areas into the following two categories: (1) Riparian Vegetated: This class is used to describe areas still in natural unvegetated wetlands, water bodies, and any undeveloped or unmanaged lands within the approximate riparian zone. (2) Riparian Developed: This class is used to describe all developed areas, such as urban and suburban development, agriculture, utility structures and stations, mining, and extraction.</P>
          <HD SOURCE="HD3">Mapping</HD>
          <P>When determining critical habitat boundaries within this final rule, we made every effort to avoid including developed areas such as lands covered by buildings, pavement, and other structures because such lands lack physical or biological features for the flycatcher. These types of developments are not often found adjacent to rivers within floodplains, and may not be found on recent maps. The scale of the maps we prepared under the parameters for publication within the Code of Federal Regulations may not reflect the removal of such developed lands. Any such developed lands inadvertently left inside critical habitat boundaries shown on the maps of this final rule have been excluded by text in the rule and are not designated as critical habitat. Therefore, a Federal action involving these developed lands will not trigger section 7 consultation with respect to critical habitat and the requirement of no adverse modification unless the specific action would affect the physical or biological features in the adjacent critical habitat.</P>

          <P>The critical habitat designation is defined by the map or maps, as modified by any accompanying regulatory text, presented at the end of this document in the rule portion. We include more detailed information on the boundaries of the critical habitat designation in the preamble of this document. We will make the coordinates or plot points or both on which each map is based available to the public on<E T="03">http://www.regulations.gov</E>at Docket No. FWS-R2-ES-2011-0053 on our Internet site at<E T="03">http://www.fws.gov/southwest/es/arizona/</E>, and at the field office responsible for the designation (see<E T="02">FOR FURTHER INFORMATION CONTACT</E>above).</P>
          <HD SOURCE="HD3">Summary of Criteria Used To Identify Critical Habitat</HD>
          <P>Our initial steps and approach in generating areas for flycatcher critical habitat were to identify areas: (1) Known to be within the specific geographic area occupied by the flycatcher at the time of listing (from surveys occurring from 1991 to 1994) that contain the physical or biological features which may require special management or protections; and (2) that are essential to flycatcher conservation based on the Recovery Plan goals.</P>
          <P>Following the evaluation of the two factors above, our goal was to incorporate the conservation strategies described in the Recovery Plan. These strategies describe the importance of flycatcher habitat to support stable and growing breeding populations, to provide migration stopover areas, to protect against simultaneous catastrophic loss, to maintain gene flow, to prevent isolation and extirpation, and to provide colonizers to use new areas. Also, the Recovery Plan describes the importance of habitat that supports large breeding populations of flycatchers and small populations that, when in proximity, equal a large population. To achieve these goals, the Recovery Plan describes a recovery strategy of distributing flycatcher habitat that could hold a specific minimum number of breeding territories across 29 different Management Units in portions of California, Nevada, Utah, Colorado, Arizona, and New Mexico.</P>
          <P>We therefore created criteria and methodology to identify areas surrounding large populations and small populations, in proximity, that equaled a large population. We used a 35-km (22-mi) distance as a radius to identify areas around large flycatcher populations (those with at least 10 territories) and small populations in high connectivity that together equal a large population.</P>
          <P>We chose to generate critical habitat in “river segments” to account for the dynamic aspects of flycatcher riparian habitat, the changing locations of flycatcher habitat due to these dynamic conditions, population growth, and the variety of other life-history needs such as nest placement, foraging, dispersing, cover, shelter, and migration habitat. Once these broad areas were established, we identified stream segments with flycatcher habitat that we believe will support the numerical territory and habitat-related recovery goals for the 29 Management Units described in the Recovery Plan.</P>
          <P>Some Management Units with recovery goals do not have known large populations or small populations that equal a large population in high connectivity. Also, in some Management Units, an area may not contain enough habitat to reach the number of territories stated in the Recovery Plan. In these instances, we relied upon the Recovery Plan guidance (recovery strategy, stream identification, and habitat descriptions), flycatcher detections, and local expertise in habitat quality to identify river segments considered essential for the conservation of the species.</P>

          <P>The lateral extent of river segments designated as critical habitat represent the riparian zone, which is an area that is most directly influenced by river functions and is anticipated to occur<PRTPAGE P="363"/>within the 100-year floodplain. We created these boundaries from existing digital sources and visual interpretation.</P>
          <P>Overall, these designated stream segments represent flycatcher habitat known to be occupied at the time of listing and essential areas that have high recovery value. The designated areas support stable and growing breeding populations, provide migration stopover areas, protect against simultaneous catastrophic loss, maintain gene flow, prevent isolation and extirpation, and encourage colonizers to use new areas. All stream segments provide habitat for a wide distribution of flycatcher territories, including areas for population growth to meet numerical and habitat-related recovery goals. The designated areas also support other important flycatcher needs such as migration, dispersal, foraging, and shelter to reach the geographic distribution and habitat-related recovery goals.</P>
          <P>We are designating as critical habitat lands that we have determined were occupied at the time of listing and contain sufficient elements of physical or biological features to support life-history processes essential for the conservation of the species (as defined under section 3(5)(A)(i) of the Act), and lands outside of the geographical area occupied at the time of listing that we have determined are essential for flycatcher conservation (as defined under section 3(5)(A)(ii) of the Act). The occupied stream segments are designated based on sufficient elements of physical or biological features being present to support flycatcher life processes. Some segments contain all of the identified elements of physical or biological features and support multiple life processes. Some segments contain only some elements of the physical or biological features necessary to support the flycatcher's particular use of that habitat.</P>
          <HD SOURCE="HD1">Final Critical Habitat Designation</HD>
          <P>We are designating stream segments in 24 Management Units found in six Recovery Units as flycatcher critical habitat. Following our evaluation and analysis under section 4(b)(2) of the Act, stream segments in five Management Units (Owens, Middle Colorado, Hoover to Parker Dam, Parker Dam to Southerly International Border, and Lower Rio Grande Management Units) where recovery goals occur and critical habitat was proposed were excluded in their entirety (see Exclusions section). The designated stream segments occur in California, Nevada, Utah, Colorado, Arizona and New Mexico and include a total of approximately 1,975 km (1,227 mi) of streams. The following list represents the names of the portions of streams that are being designated as flycatcher critical habitat organized by Recovery and Management Unit. In order to help further understand the location of these designated stream segments, please see the associated maps found within the Regulation Promulgation section of this final rule.</P>
          <HD SOURCE="HD2">Coastal California Recovery Unit in California</HD>
          <P>(1) Santa Ynez Management Unit—Santa Ynez River and Mono Creek.</P>
          <P>(2) Santa Clara Management Unit—Santa Clara River, Ventura River, Piru Creek, Castaic Creek, Big Tujunga Canyon, and San Gabriel River.</P>
          <P>(3) Santa Ana Management Unit—Bear Creek, Mill Creek, Oak Glen Creek, San Timoteo Creek, Santa Ana River (including portions of Prado Basin), Waterman Creek, and Bautista Creek.</P>
          <P>(4) San Diego Management Unit—Santa Margarita River, DeLuz Creek, San Luis Rey River, Pilgrim Creek, Agua Hedionda Creek, Santa Ysabel Creek, Temescal Creek, Temecula Creek, Sweetwater River, and San Diego River.</P>
          <HD SOURCE="HD2">Basin and Mojave Recovery Unit in California and Nevada</HD>
          <P>(5) Kern Management Unit—South Fork Kern River (including upper Lake Isabella) and Canebrake Creek, California.</P>
          <P>(6) Mojave Management Unit—Deep Creek, Holcomb Creek, Mojave River, and West Fork Mojave River, California.</P>
          <P>(7) Salton Management Unit—San Felipe Creek and Mill Creek, California.</P>
          <P>(8) Amargosa Management Unit—Willow Creek, California; Amargosa River, California and Nevada; and five separate riparian areas within Ash Meadows National Wildlife Refuge, Nevada.</P>
          <HD SOURCE="HD2">Lower Colorado Recovery Unit in Nevada, California and Arizona Border, Arizona, Utah, and New Mexico</HD>
          <P>(9) Little Colorado Management Unit—Little Colorado River and West Fork Little Colorado River, Arizona.</P>
          <P>(10) Virgin Management Unit—Virgin River, Nevada, Arizona, and Utah.</P>
          <P>(11) Pahranagat Management Unit—Pahranagat River, Nevada.</P>
          <P>(12) Bill Williams Management Unit— Big Sandy River, Bill Williams River, and Santa Maria Rivers (including upper Alamo Lake), Arizona.</P>
          <HD SOURCE="HD2">Upper Colorado Recovery Unit in Arizona, Utah, Colorado, and New Mexico</HD>
          <P>(13) San Juan Management Unit—Los Pinos River, Colorado; San Juan River (north bank), Utah.</P>
          <P>(14) Powell Management Unit—Paria River, Utah.</P>
          <HD SOURCE="HD2">Gila Recovery Unit in Arizona and New Mexico</HD>
          <P>(15) Verde Management Unit—Verde River, Arizona.</P>
          <P>(16) Roosevelt Management Unit—Salt River and Tonto Creek, Arizona.</P>
          <P>(17) Middle Gila and San Pedro Management Unit—Gila River and San Pedro River, Arizona.</P>
          <P>(18) Upper Gila Management Unit—Gila River in Arizona and New Mexico.</P>
          <P>(19) Santa Cruz Management Unit—Santa Cruz River, Empire Gulch, and Cienega Creek, Arizona.</P>
          <P>(20) San Francisco Management Unit—San Francisco River, Arizona and New Mexico.</P>
          <P>(21) Hassayampa and Agua Fria Management Unit—Hassayampa River, Arizona.</P>
          <HD SOURCE="HD2">Rio Grande Recovery Unit in New Mexico and Colorado</HD>
          <P>(22) San Luis Valley Management Unit—Conejos River and Rio Grande, Colorado.</P>
          <P>(23) Upper Rio Grande Management Unit—Coyote Creek, Rio Grande, Rio Grande del Rancho, and Rio Fernando, New Mexico.</P>
          <P>(24) Middle Rio Grande Management Unit—Rio Grande, New Mexico.</P>
          <P>Table 1 below lists all the streams included in this revised designation and whether they are considered occupied at the time of listing and whether they are currently considered  occupied.</P>

          <P>We note which streams were within the geographical area known to be occupied at time of listing, based upon our criteria (1991-1994), and are therefore being designated under section 3(5)(A)(i) of the act because they contain essential physical or biological features that require special management or protections. Streams not known to be occupied at the time of listing are being designated as critical habitat under section 3(5)(A)(ii) of the act because they are essential for the conservation of the species. We also note which streams have had flycatcher territories detected between 1991 and 2010.<PRTPAGE P="364"/>
          </P>
          <GPOTABLE CDEF="s50,r50,r50,xls56,xls56" COLS="5" OPTS="L2,i1">
            <TTITLE>TABLE 1—Portion of Streams Designated for Flycatcher Critical Habitat</TTITLE>
            <BOXHD>
              <CHED H="1">Recovery unit</CHED>
              <CHED H="1">Management unit</CHED>
              <CHED H="1">Portion of streams</CHED>
              <CHED H="1">Known to be occupied at time of listing (1991-1994)</CHED>
              <CHED H="1">Territories detected (1991-2010)</CHED>
            </BOXHD>
            <ROW>
              <ENT I="01">Coastal California</ENT>
              <ENT>Santa Ynez</ENT>
              <ENT>Mono Creek</ENT>
              <ENT>No</ENT>
              <ENT>No.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Santa Ynez River</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Santa Clara</ENT>
              <ENT>Big Tujunga Canyon</ENT>
              <ENT>No</ENT>
              <ENT>No.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Castaic Creek</ENT>
              <ENT>No</ENT>
              <ENT>No.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Piru Creek</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>San Gabriel River</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Santa Clara River</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Ventura River</ENT>
              <ENT>No</ENT>
              <ENT>No.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Santa Ana</ENT>
              <ENT>Bautista Creek</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Bear Creek</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Mill Creek</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Oak Glen Creek</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>San Timoteo Creek</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Santa Ana River</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Waterman Creek</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>San Diego</ENT>
              <ENT>Agua Hedionda Creek</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>DeLuz Creek</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Pilgrim Creek</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>San Diego River</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>San Luis Rey River</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Santa Margarita River</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Santa Ysabel Creek</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Sweetwater River</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Temecula Creek</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Temescal Creek</ENT>
              <ENT>No</ENT>
              <ENT>No.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Basin and Mojave</ENT>
              <ENT>Kern</ENT>
              <ENT>Canebrake Creek</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>South Fork Kern River</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Mohave</ENT>
              <ENT>Deep Creek</ENT>
              <ENT>No</ENT>
              <ENT>No.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>West Fork Mojave River</ENT>
              <ENT>No</ENT>
              <ENT>No.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Holcomb Creek</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Mojave River</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Salton</ENT>
              <ENT>Mill Creek</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>San Felipe Creek</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Amargosa</ENT>
              <ENT>Amargosa River</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Willow Creek</ENT>
              <ENT>No</ENT>
              <ENT>No.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Ash Meadows Riparian Areas</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Lower Colorado</ENT>
              <ENT>Little Colorado</ENT>
              <ENT>Little Colorado River</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>West Fork Little Colorado River</ENT>
              <ENT>No</ENT>
              <ENT>No.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Virgin</ENT>
              <ENT>Virgin River</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Pahranagat</ENT>
              <ENT>Pahranagat River</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Bill Williams</ENT>
              <ENT>Big Sandy River</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Bill Williams River</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Santa Maria River</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Upper Colorado</ENT>
              <ENT>San Juan</ENT>
              <ENT>San Juan River</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Los Pinos River</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Powell</ENT>
              <ENT>Paria River</ENT>
              <ENT>No</ENT>
              <ENT>No.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gila</ENT>
              <ENT>Verde</ENT>
              <ENT>Verde River</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Roosevelt</ENT>
              <ENT>Tonto Creek</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Salt River</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Middle Gila and San Pedro</ENT>
              <ENT>San Pedro River</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Gila River</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Upper Gila</ENT>
              <ENT>Gila River</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Santa Cruz</ENT>
              <ENT>Santa Cruz River</ENT>
              <ENT>No</ENT>
              <ENT>No.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Cienega Creek</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Empire Gulch</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>San Francisco</ENT>
              <ENT>San Francisco River</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Hassayampa and Agua Fria</ENT>
              <ENT>Hassayampa River</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Rio Grande</ENT>
              <ENT>San Luis Valley</ENT>
              <ENT>Rio Grande</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Conejos River</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Upper Rio Grande</ENT>
              <ENT>Coyote Creek</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Rio Fernando</ENT>
              <ENT>No</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Rio Grande</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT O="xl"/>
              <ENT>Rio Grande Del Rancho</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Middle Rio Grande</ENT>
              <ENT>Rio Grande</ENT>
              <ENT>Yes</ENT>
              <ENT>Yes.</ENT>
            </ROW>
          </GPOTABLE>

          <P>Approximate land ownership in each State where the designated critical habitat occurs is provided below in Table 2.<PRTPAGE P="365"/>
          </P>
          <GPOTABLE CDEF="xs36,r50,r50,r50,r50,r50" COLS="6" OPTS="L2,i1">
            <TTITLE>TABLE 2—Land Ownership, by State, of Revised Designated Critical Habitat Areas for Southwestern Willow Flycatcher, Listed as Approximate Stream Lengths in km (mi); and Approximate Area in ha (ac)</TTITLE>
            <BOXHD>
              <CHED H="1">State</CHED>
              <CHED H="1">Federal</CHED>
              <CHED H="1">State</CHED>
              <CHED H="1">Private</CHED>
              <CHED H="1">Other/Unclassified</CHED>
              <CHED H="1">Total</CHED>
            </BOXHD>
            <ROW>
              <ENT I="01">AZ</ENT>
              <ENT>365 (227); 9,869 (24,387)</ENT>
              <ENT>50 (31); 3,012 (7,443)</ENT>
              <ENT>369 (229); 19,436 (48,026)</ENT>
              <ENT>0 (0); 0 (0)</ENT>
              <ENT>784 (487); 32,317 (79,856).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">CA</ENT>
              <ENT>188 (117); 2,688 (6,642)</ENT>
              <ENT>26 (16); 619 (1,529)</ENT>
              <ENT>78 (48); 1,089 (2,692)</ENT>
              <ENT>316 (196); 11,470 (28,342)</ENT>
              <ENT>609 (378); 15,866 (39,205).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">CO</ENT>
              <ENT>43 (27); 4,063 (10,040)</ENT>
              <ENT>0 (0); 0 (0)</ENT>
              <ENT>7 (5); 221 (547)</ENT>
              <ENT>0 (0); 0 (0)</ENT>
              <ENT>51 (31); 4,284 (10,586).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">NV</ENT>
              <ENT>29 (18); 1,451 (3,584)</ENT>
              <ENT>7 (4); 649 (1,603)</ENT>
              <ENT>19 (12); 1,383 (3,416)</ENT>
              <ENT>0 (0); 0 (0)</ENT>
              <ENT>54 (34); 3,482 (8,603).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">NM</ENT>
              <ENT>125 (78); 6,318 (15,613)</ENT>
              <ENT>29 (18); 4,780 (11,812)</ENT>
              <ENT>248 (154); 14,817 (36,613)</ENT>
              <ENT>0 (0); 0 (0)</ENT>
              <ENT>402 (250); 25,916 (64,039).</ENT>
            </ROW>
            <ROW RUL="n,s">
              <ENT I="01">UT</ENT>
              <ENT>41 (25); 1,544 (3,816)</ENT>
              <ENT>0 (0); 15 (38)</ENT>
              <ENT>35 (22); 1,146 (2,831)</ENT>
              <ENT>0 (0); 0 (0)</ENT>
              <ENT>76 (47); 2,705 (6,685).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Total</ENT>
              <ENT>791 (492); 25,933 (64,082)</ENT>
              <ENT>112 (69); 9,075 (22,424)</ENT>
              <ENT>756 (470); 38,091 (94,125)</ENT>
              <ENT>316 (196); 11,470 (28,342)</ENT>
              <ENT>1,975 (1,227); 84,569 (208,973).</ENT>
            </ROW>
            <TNOTE>
              <E T="02">Notes:</E>No tribal lands were included in the final revised designation. Totals do not sum because some stream segments have different ownership on each side of the bank resulting in those segments being counted twice. Other/Unclassified includes some local government ownership and unclassified segments (where land ownership was not available).</TNOTE>
          </GPOTABLE>
          <P/>
          <HD SOURCE="HD2">Critical Habitat Unit Descriptions</HD>

          <P>We present brief descriptions below of all critical habitat units and reasons why they meet the definition of critical habitat for the flycatcher. The units are organized by Recovery Unit and then Management Unit. For each Recovery Unit we provide a broad overview of the recent distribution and abundance of flycatcher territories. Based upon our criteria, we also specifically list those streams designated as critical habitat within that Recovery Unit that were known to be occupied by flycatchers at the time of listing, and possess the physical or biological features that may require special management considerations or protection. Detailed site and territory summary information used for Recovery and Management Units are primarily generated from the USGS Rangewide Database (Sogge and Durst 2008, entire) and Flycatcher Rangewide Report (Durst<E T="03">et al.</E>2008, entire).</P>

          <P>Because of the abundance of information presented in each Management Unit description, this paragraph is a brief overview of the order of information presented in each unit description. For each Management Unit, we begin by stating the numerical territory goal described in the Recovery Plan and, in many instances, a brief note about flycatcher territory distribution. We next explain whether the Management Unit supported a large flycatcher nesting population (as defined in the<E T="03">Criteria Used To Identify Critical Habitat,</E>“Areas with Large Populations” section) in order to establish the areas where we initially focused our selection of stream segments to propose as critical habitat. For Management Units where there was a large population, we provide more specific information about the occurrence of flycatcher territories within that large population area. If there was no known large flycatcher nesting population, we provide information about known flycatcher distribution and abundance with that Management Unit. We next present those stream segments we are designating as critical habitat and appropriate location and length descriptions. Any stream segments we designate that were not known to be occupied at the time of listing, we described as an “essential” segment for flycatcher conservation in order to reach the stated recovery goals for this Management Unit. We reiterate the description of those designated segments that were known to be occupied by flycatchers at the time of listing. Finally, we explain how the critical habitat designation of stream segments supports the science and conservation goals established in the Recovery Plan, and for those streams not occupied at the time of listing, we offer information supporting why they are considered essential for flycatcher conservation.</P>

          <P>For each stream segment being designated as critical habitat, we identify the State and County where it occurs and list the stream length being designated rounded up to the nearest tenth of a kilometer and mile. The specific beginning and ending points of each designated stream segment can be found below in the combination of textual descriptions and associated maps for each critical habitat unit in the Regulation Promulgation section of this document. In addition, GIS data for all designated stream segments, which include more specific lateral extent critical habitat information, may be downloaded online at<E T="03">http://www.fws.gov/southwest/es/arizona/southwes.htm</E>. We also note in our descriptions which stream segments which were proposed for critical habitat were exempted under section 4(a)(3) under the Act or were excluded from critical habitat under section 4(b)(2) of the Act. For more explanation of why any stream is being exempted or excluded, see the discussions under the Exemptions and Exclusions sections below.</P>
          <P>All of the designated stream segments provide flycatcher habitat for breeding, feeding, sheltering, and migration, and subsequently provide metapopulation stability, gene flow of the subspecies, protection against catastrophic population losses, and connectivity between neighboring Management Units and Recovery Units (Service 2002, pp. 74-75, 86-92). They also provide habitat to help meet the numerical and habitat-related goals identified in the Recovery Plan (Service 2002, pp. 77-92). Most of the segments are a subset of those identified in the Recovery Plan as areas that provide substantial recovery value (Service 2002, pp. D-12-D-15). Since completion of the Recovery Plan, additional segments of substantial recovery value have been identified through continued survey, analysis, and habitat evaluation, and have been included in this designation when needed to reach recovery goals. The distribution and abundance of territories and habitat within each designated segment are expected to shift over time as a result of natural disturbance events such as flooding that reshape floodplains, river channels, and riparian habitat (Service 2002, pp. 18, D-11-D-13, D-15).</P>
          <HD SOURCE="HD3">Coastal California Recovery Unit</HD>

          <P>This Recovery Unit stretches along the coast of southern California from just north of Point Conception south to<PRTPAGE P="366"/>the Mexico border. In 2002, 167 flycatcher territories were estimated to occur in this Recovery Unit (14 percent of the rangewide total) (Sogge<E T="03">et al.</E>2003); however the most recent 2007 rangewide assessment estimated that the number of territories has declined to 120 (9 percent of rangewide total) (Durst<E T="03">et al.</E>2008, p. 12). Since the completion of the Recovery Plan, territories have been distributed along 15 relatively small watersheds, mostly in the southern third of the Recovery Unit (Service 2002, p. 64; Sogge and Durst 2008). Unlike most other Recovery Units, the Coastal California Unit possesses many streams in proximity to one another. However, most breeding sites are small (fewer than five territories); the largest populations occur along the San Luis Rey, Santa Margarita, and Santa Ynez Rivers (Service 2002, p. 64). In 2001, all territories occurred in habitats dominated by native plants, and over 60 percent were on government-managed lands (Federal, State, and local) (Service 2002, p. 64). This Recovery Unit contains the Santa Ynez, Santa Clara, Santa Ana, and San Diego Management Units. The stream segments designated as critical habitat are described below under their appropriate Management Units.</P>

          <P>Based upon our occupancy criteria (see above) within the Coastal California Recovery Unit, the Santa Ynez (1991), Santa Clara (1994), and San Luis Rey (1993) Rivers, and Pilgrim Creek (1994) are streams that were within the geographical area known to be occupied at the time of listing (1991-1994) (Sogge and Durst 2008) where we are designating critical habitat segments. Below we identify that each listed item described in our<E T="03">Special Management Considerations or Protection</E>section (see above) applies to the streams described in each Management Unit within the Coastal California Recovery Unit.</P>
          <P>Santa Ynez Management Unit, California</P>
          <P>The Recovery Plan describes a goal of 75 flycatcher territories in the Santa Ynez Management Unit (Service 2002, p. 84). The Santa Ynez River is the only stream in this Management Unit known to have flycatcher territories (Sogge and Durst 2008).</P>
          <P>We identified a large flycatcher nesting population surrounding the lowest portion of the Santa Ynez River in Santa Barbara County, California. Flycatcher territories were detected on the Santa Ynez River in 1991 (Sogge and Durst 2008). A total of four breeding sites are known to occur within our large population area. A high of 26 flycatcher territories was detected on the lower Santa Ynez River in 1996, but the known number of territories has fluctuated greatly from year-to-year (from 1 to 26) (Sogge and Durst 2008). As a result, more critical habitat than just the large population area is expected to be needed to meet the Recovery Plan goal of 75 territories.</P>
          <P>To help reach the Recovery Plan goals, we identified two additional areas of flycatcher habitat on the upper Santa Ynez River that are considered occupied at the time of listing and a short segment of Mono Creek farther upstream outside of our large population area (near Gibraltar Reservoir) that was not occupied at the time of listing. As a result, we are designating three Santa Ynez River segments and a segment of Mono Creek as flycatcher critical habitat. The lower 42.3-km (26.3-mi) Santa Ynez River segment occurs immediately upstream from Vandenberg AFB. The upper 6.1-km (3.8-mi) and 7.6-km (4.7-mi) segments of the Santa Ynez River occur near Gibraltar Reservoir. We are also designating the lowest 2.6 km (1.6 mi) of Mono Creek, also in Santa Barbara County.</P>
          <P>The stream segments along the Santa Ynez River were occupied by flycatchers at the time of listing and contain the physical or biological features essential to the conservation of the species which may require special management considerations or protection, for the reasons described above. Mono Creek was not occupied at the time of listing, but is an essential area for flycatcher conservation in order to help meet recovery goals (see below).</P>
          <P>The Santa Ynez River and its tributaries (including Mono Creek and other unnamed tributaries) were described as having substantial recovery value in the Recovery Plan (Service 2002, p. 86). The Santa Ynez River and Mono Creek segments are anticipated to provide habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <P>A 14.7-km (9.1-mi) portion of the lower Santa Ynez River segment that was occupied at the time of listing and contains the physical or biological features essential to the conservation of the species which may require special management considerations or protection, occurs within the boundaries of Vandenberg AFB. We are exempting this portion of the river from designation as critical habitat, under section 4(a)(3) of the Act, based on the implementation of their Integrated Natural Resources Management Plan (INRMP) which provides a benefit to the flycatcher (see Exemptions section below).</P>
          <HD SOURCE="HD3">Santa Clara Management Unit, California</HD>
          <P>The Recovery Plan describes a goal of 25 flycatcher territories in the Santa Clara Management Unit (Service 2002, p. 84). Flycatcher territories have been detected in small numbers and sporadically over a broad area in this Management Unit.</P>
          <P>There are no large flycatcher nesting populations in the Santa Clara Management Unit to help guide us toward a critical habitat area. As a result, we sought known flycatcher territories and breeding sites, guidance from the Recovery Plan, and knowledge about stream habitat to determine critical habitat segments that may be within the geographical area known to be occupied at the time of listing and others essential for flycatcher conservation (see below). Flycatcher territories have been detected in small numbers in the Santa Clara Management Unit, ranging from zero to seven territories annually between 1995 and 2001 (Sogge and Durst 2008). Three breeding sites have been detected on the Santa Clara River and two breeding sites each on Piru Creek and the San Gabriel River (Sogge and Durst 2008).</P>
          <P>We are designating as critical habitat a 75.2 km (46.7 mi) segment of the Santa Clara River in Ventura and Los Angeles Counties. These segments were within the geographical area known to be occupied by flycatchers at the time of listing (Sogge and Durst 2008) and have the physical or biological features essential to the conservation of the species which may require special management consideration or protection, for the reasons described above. We are also designating as flycatcher critical habitat segments of the Ventura River (27.5 km, 17.1 mi) in Ventura County; and segments of Castaic Creek (4.8 km, 3.0 mi), Piru Creek (41.9 km, 26.0 mi), Big Tujunga (4.9 km, 3.0 mi) Canyon, and the San Gabriel River (14.2 km, 8.8 mi) in Los Angeles County. These segments were not occupied at the time of listing, but are essential for flycatcher conservation in order to help meet recovery goals, as explained below.</P>

          <P>The Santa Clara, Ventura, and San Gabriel Rivers, Piru Creek and Big Tujunga Canyon, were identified in the<PRTPAGE P="367"/>Recovery Plan as having substantial recovery value in the Santa Clara Management Unit (Service 2002, p. 86). Together with Castaic Creek, these six stream segments are essential to flycatcher conservation because they are anticipated to provide habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <P>Habitat along the Santa Clara River east of Interstate 5 (4.4 km, 2.7 mi) with features essential for flycatcher conservation, owned and managed by Newall Land and Farming Company, is excluded from this critical habitat designation based upon the habitat management provided under a conservation easement (see Exclusions section below).</P>
          <HD SOURCE="HD3">Santa Ana Management Unit, California</HD>
          <P>The Recovery Plan describes a goal of 50 flycatcher territories in the Santa Ana Management Unit (Service 2002, p. 84). Flycatcher territories have been detected from the headwaters and tributaries of the Santa Ana River in the San Bernardino Mountains in San Bernardino County, California, down to breeding sites in Riverside County at Prado Basin and other nearby separate streams. None of the seven streams (eight stream segments) within the Santa Ana Management Unit were within the geographical area known to be occupied at listing; however, all seven streams have had territories identified since listing.</P>

          <P>We identified a large flycatcher nesting population that surrounds the Santa Ana River and its tributaries in San Bernardino and Riverside Counties. Because of the wide distribution and close proximity of flycatcher territories, nearly all the streams within the Santa Ana Management Unit were included in the large population area. A survey in 2007 detected 30 breeding sites along the Santa Ana River (Durst<E T="03">et al.</E>2008, p. 11). Since 1995, flycatcher territories have been detected along the Santa Ana River, and tributaries such as Bear Creek, Mill Creek, Oak Glen Creek, Waterman Creek, San Timoteo Creek, and Bautista Creek (Sogge and Durst 2008). While breeding sites are numerous, the number of territories detected at each site was typically less than five (Sogge and Durst 2008). Throughout the entire Management Unit, a high of 49 territories was detected in 2001 (Sogge and Durst 2008), but limited on-the-ground surveys only detected one territory in 2007 (Sogge and Durst 2008). In 2007, Durst<E T="03">et al.</E>(2008, p. 12) estimated that 28 territories occurred in this Management Unit. The combination of these streams provides riparian habitat for breeding, migrating, dispersing, non-breeding and territorial flycatchers, metapopulation stability, gene flow, connectivity, population growth, and prevention against catastrophic loss.</P>
          <P>The Santa Ana River is the single largest river system in southern California with flycatchers distributed throughout the stream from its headwaters and tributaries in the San Bernardino Mountains in San Bernardino County, downstream to Riverside County. We are designating three segments—an upper 42.5-km (26.4-mi) segment in the San Bernardino National Forest, a middle 13.4-km (8.3-mi) segment in San Bernardino County (just above the Riverside County line), and a lower 1.9 km (1.2 mi) portion (consisting of about 4 separate parcels) located about 2.3 km (1.4 mi) northeast of Prado Basin flood control dam—of the Santa Ana River in San Bernardino County and other segments with high connectivity near its headwaters. In San Bernardino County we are designating 5.2 km (3.2 mi) of Waterman Creek (including portions of the Left and Right Fork), 14.7 km (9.2 mi) of Bear Creek, 4.1 km (2.6 mi) of San Timoteo Creek, 19.3 km (12.0 mi) of Mill Creek, and 4.7 km (2.9 mi) of Oak Glen Creek as critical habitat.</P>
          <P>We are designating three segments of Bautista Creek on Federal Lands within the San Bernardino National Forest. The most eastern segment occurs for 2.0 km (1.3 mi), upstream of the Ramona Band of Cahuilla Reservation. West of tribal land is an 11.4-km (7.1-mi) stream segment that extends through the San Bernardino National Forest until a segment of private land occurs. West of this portion of private land is another San Bernardino National Forest segment that is 5.9 km (3.7 mi) long.</P>

          <P>Portions of the Santa Ana Watershed in Riverside County identified as being essential for flycatcher conservation (the lower Santa Ana River (including Prado Basin), San Timoteo Creek, and Bautista Creek) fall within the boundaries of the Western Riverside County Multiple Species Habitat Conservation Plan (Western Riverside County MSHCP). All non-Federal and tribal lands that fall within the Western Riverside County Multispecies Habitat Conservation Plan are being excluded from critical habitat designation under section 4(b)(2) of the Act (see Exclusions<E T="03"/>section below).</P>
          <P>Habitat with features essential for the flycatcher was also identified within the boundaries of the Ramona Band of Cahuilla Reservation on Bautista Creek. We are excluding these tribal lands from the critical habitat designation under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <P>This diverse and widely distributed group of seven streams was identified in the Recovery Plan (although Oak Glen Creek was not specifically named as a tributary to the Santa Ana River) as areas of substantial recovery value (Service 2002, p. 86). Together, these stream segments are essential for flycatcher conservation because they are anticipated to provide habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and provide for population growth and colonization potential. As a result, these river segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <HD SOURCE="HD3">San Diego Management Unit, California</HD>
          <P>The Recovery Plan describes a goal of 125 flycatcher territories in the San Diego Management Unit (Service 2002, p. 84). Flycatcher territories have been detected throughout this Management Unit primarily along the rivers and tributaries of the largest river drainages in the area, such as the San Luis Rey, Santa Margarita, and San Diego Rivers.</P>

          <P>We identified a large flycatcher nesting population that includes nearly all of the streams within the San Diego Management Unit. Within the San Diego Management Unit, about 24 breeding sites are known to occur (Durst<E T="03">et al.</E>2008, p. 12). A high of 86 flycatcher territories were detected in 2001 (Sogge and Durst 2008). In 2003, Durst<E T="03">et al.</E>(2005, p. 10) estimated a total of 100 territories for the entire San Diego Management Unit, with 86 territories on San Luis Rey and Santa Margarita Rivers. In 2007, Durst<E T="03">et al.</E>(2008, p. 11) estimated a total of 77 territories at 24 breeding sites for the entire San Diego Management Unit, with 69 territories at 12 breeding sites on these two river drainages.</P>

          <P>Within this large population area, we identified flycatcher habitat on 18 different streams within the San Diego Management Unit that occur in San Diego, Riverside, and Orange Counties, California. The streams we identified in San Diego County are: San Mateo Creek,<PRTPAGE P="368"/>Cristianitos Creek, San Onofre Creek, Las Flores Creek, Las Pulgas Creek, Fallbrook Creek, Santa Margarita River, DeLuz Creek, San Luis Rey River (two segments), Pilgrim Creek, Agua Hedionda Creek, San Dieguito River, Santa Ysabel Creek, San Diego River (two segments), Temescal Creek, and Sweetwater River. A segment of Temecula Creek travels across San Diego and Riverside Counties and a Cañada Gobernadora Creek segment occurs in Orange County.</P>
          <P>The longest two streams in the San Diego Management Unit are the San Luis Rey and Santa Margarita Rivers, which contain the largest numbers of flycatcher territories within this Management Unit. In addition to these two streams, we are designating a collection of smaller streams within the Unit.</P>
          <P>We are designating a 9.3-km (5.8-mi) segment of the Santa Margarita River and a 3.3-km (2.1-mi) segment of De Luz Creek in San Diego County, upstream of Marine Corps Base, Camp Pendleton (Camp Pendleton). Territories have been detected on the Santa Margarita River on Camp Pendleton. The segment upstream from Camp Pendleton maintains a diversity of riparian vegetation used by dispersing and migrating flycatchers and the ability to develop breeding habitat for population growth or discovery of undetected territories.</P>

          <P>We are designating seven segments of the San Luis Rey River and a 5-km (3.1-mi) segment of Pilgrim Creek in San Diego County. Four separate upper San Luis Rey segments of critical habitat occur upstream (7.4 km, 4.6 mi), between (0.8 km, 0.5 mi and 0.9 km, 0.6 mi), and downstream (3.1 km, 1.9 mi) of the La Jolla Band of Luiseño Indians and the Rincon Band of Luiseño Mission Indians tribal lands from Lake Henshaw downstream to the Puma Valley Country Club. The western most three segments of the San Luis Rey River (30.8 km, 19.1 mi; 5.1 km; 3.2 mi; and 8.5 km, 5.3 mi) occur surrounding the Pala Band of Luiseño Mission Indians tribal lands from Interstate 5 upstream to the Puma Valley Country Club. Flycatcher breeding sites have been detected since 1991 on Pilgrim Creek and the San Luis Rey River. Durst<E T="03">et al.</E>(2008, p. 11) reported 55 territories from the San Luis Rey River drainage. A 2007 survey of Pilgrim Creek did not identify any territories (Durst<E T="03">et al.</E>2008, p. 28).</P>
          <P>We are designating a segment of Agua Hedionda Creek, which include small portions of the right and left forks. The upstream forks extend from La Mirada Drive (right fork) (0.4 km, 0.2 mi) and Sycamore Avenue (left fork) (1.0 km, 0.6 mi) and then downstream along the mainstem Agua Hedionda Creek for 2.5 km (1.6 mi). A single breeding site and flycatcher territory was detected on Agua Hedionda Creek in 1998 and 1999 (Sogge and Durst 2008). The segments of Agua Hedionda Creek were not within the geographical area known to be occupied at the time of listing, but are essential for conservation in order to meet recovery goals.</P>
          <P>We are designating joining segments of Temescal Creek (7.6 km, 4.7 mi) and Santa Ysabel River (6.5 km, 4.0 mi) in San Diego County. Both segments are found upstream of known breeding sites (within areas that were proposed as critical habitat but are being excluded from the revised final designation). These two upstream segments currently provide habitat for dispersing and migrating flycatchers and locations for population growth or discovery of undetected territories.</P>
          <P>We are designating a 5.2-km (3.2-mi) segment of Temecula Creek in San Diego County. Two breeding sites are known from Temecula Creek, with one occurring on the designated segment. Territories were first detected in 1997, and Sogge and Durst (2008) reported a single territory for 2003. A 2007 survey of Temecula Creek did not identify any territories (Sogge and Durst 2008).</P>
          <P>On the San Diego River north of the El Capitan Reservoir, we are designating a 3.8-km (2.4-mi) segment downstream and 2.2-km (1.4-mi) segment upstream of land (proposed but excluded from flycatcher critical habitat) that is jointly managed by the Barona Group of Capitan Grande Band of Mission Indians and the Viejas (Baron Long) Group of Capitan Grande Band of Mission Indians. Territories in this stream were not identified at listing, but two territories were detected in 2001 (USGS 2007).</P>
          <P>Proposed critical habitat on the San Dieguito River, San Diego River, non-Federal lands on the Sweetwater River, and a portion of Santa Ysabel Creek within the boundaries of the San Diego County MSCP are being excluded from this critical habitat designation under section 4(b)(2) of the Act. However, we are designating 4.5 km (2.8 mi) of federally owned lands on the Sweetwater River within the boundaries of the San Diego County MSCP (see Exclusions  section below).</P>
          <P>Proposed critical habitat on Agua Hedionda Creek identified within the boundaries of the City of Carlsbad's Habitat Management Plan is being excluded from this critical habitat designation under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <P>Proposed critical habitat on Cañada Gobernadora Creek identified within the boundaries of the Orange County Southern Subarea Plan is being excluded from this critical habitat designation under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <P>Proposed critical habitat on the San Luis Rey River was identified within the boundaries of tribal lands of the Pala Band of Luiseño Mission, Rincon Band of Luiseño Mission Indians, and La Jolla Band of Luiseño Indians. We are excluding these tribal lands from the critical habitat designation under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <P>Proposed critical habitat on the San Diego River was identified within the boundaries of tribal lands of the Barona Group of Capitan Grande Band of Mission Indians and the Viejas (Baron Long) Group of Capitan Grande Band of Mission Indians of the Capitan Grande Band of Diegueno Mission Indians. We are excluding these tribal lands from the critical habitat designation under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <P>Critical habitat considered within the boundaries of Marine Corps Base, Camp Pendleton on Cristianitos Creek, San Mateo Creek, San Onofre Creek, Los Flores/Las Pulgas Creek, Pilgrim Creek, DeLuz Creek, and the Santa Margarita River was exempted from this critical habitat designation (76 FR 50542, August 15, 2011, p. 50579). Critical habitat considered on portions of the Santa Margarita River located within the boundaries of the Seal Beach Naval Weapons Station, Fallbrook Detachment was also exempted from this critical habitat designation (76 FR 50542, August 15, 2011, p. 50580) (see Exemptions section below).</P>
          <P>The San Luis Rey River and Pilgrim Creek are the only streams in this management unit within the geographical area known to be occupied by flycatchers at the time of listing. The remaining critical habitat stream segments will help reach flycatcher recovery goals within the San Diego Management Unit. Collectively, these segments contain essential features for breeding, non-breeding, territorial, migrating, and dispersing flycatchers and help provide metapopulation stability, population growth, gene flow, connectivity, and protection against catastrophic losses.</P>
          <HD SOURCE="HD3">Basin and Mojave Recovery Unit</HD>

          <P>The Basin and Mojave Recovery Unit is comprised of a broad geographic area including the arid interior lands of southern California and a small portion of extreme southwestern Nevada. In<PRTPAGE P="369"/>2002, there were a total of 69 known flycatcher territories estimated to occur (7 percent of the rangewide total), but have declined to an estimated 51 territories in 2007 (Durst<E T="03">et al.</E>2008. p.12). With the exception of breeding sites on the Owens and Kern Rivers, all known breeding sites have fewer than five territories (Service 2002, p.64). As of 2002, all flycatcher territories were in riparian habitats dominated by native plants, and approximately 70 percent are on privately owned lands (Service 2002, p. 64). Because there has been little change in the amount of known flycatcher breeding sites since completion of the Recovery Plan and the number of estimated territories has declined, flycatcher habitat use and land ownership are likely similar today. The Recovery Unit contains the Owens, Kern, Mojave, Salton, and Amargosa Management Units.</P>

          <P>Based upon our occupancy criteria (see above), within the Basin and Mojave Recovery Unit, the South Fork Kern (1993) and Owens Rivers (1993) are streams that were within the geographical area known to be occupied at the time of listing (1991-1994) (Sogge and Durst 2008). Below we identify that each listed item described in our<E T="03">Special Management Considerations or Protection</E>section (see above) applied to the streams described in each Management Unit within the Basin and Mojave Recovery Unit.</P>
          <HD SOURCE="HD3">Owens Management Unit, California</HD>
          <P>The Recovery Plan describes a goal of 50 flycatcher territories in the Owens Management Unit (Service 2002, p. 84). The Owens River is the only stream in the Management Unit known to have flycatcher territories and is the most northern in the Basin and Mojave Recovery Unit.</P>
          <P>We identified a large flycatcher nesting population along the Owens River within Mono and Inyo Counties, California. Nesting flycatchers have been detected at four sites within this area, with a high of 29 territories detected in 1999 (Sogge and Durst 2008). Within this large population area, we proposed as critical habitat a 128.5-km (79.9-mi) continuous segment of the Owens River (from Long Valley Dam to just north of Tinemaha Reservoir).</P>
          <P>This segment of the Owens River is within the geographical area known to be occupied by flycatchers at the time of listing, and contains the physical or biological features essential to the conservation of the species, which may require special management considerations or protection, for the reasons described above.</P>
          <P>The Owens River is the only stream identified in the Recovery Plan as having substantial recovery value within the Owens Management Unit (Service 2002, p. 88). The Owens River segment is anticipated to provide habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, this river segment and associated flycatcher habitat is anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <P>The flycatcher habitat essential for conservation identified along the Owens River is being managed by the Los Angeles Department of Water and Power (LADWP) and is being conserved through implementation of their Southwestern Willow Flycatcher Conservation Strategy. LADWP entered into a Memorandum of Understanding with the Service to implement these conservation actions. As a result, the entire 128.5-km (79.8-mi) Owens River, in Inyo and Mono Counties, California, is being excluded from this critical habitat designation (see Exclusions section below).</P>
          <HD SOURCE="HD3">Kern Management Unit, California</HD>
          <P>The Recovery Plan describes a goal of 75 flycatcher territories in the Kern Management Unit (Service 2002, p. 84). The South Fork Kern River and Canebrake Creek within Kern County, California, are the only streams known to have flycatcher territories within this Management Unit.</P>
          <P>We identified a large flycatcher nesting population along the lower portion of the South Fork Kern River. Flycatchers were first detected nesting on the South Fork Kern River in 1993 and have been detected annually through at least 2007 (Sogge and Durst 2008). A high of 38 territories were detected in 1997 within this Management Unit (Sogge and Durst 2008). The South Fork Kern River is within the geographical area known to be occupied by flycatchers at the time of listing, and contains the physical or biological features essential to the conservation of the species, which may require special management considerations or protection, as described above.</P>
          <P>Because of the need to increase the abundance of flycatcher territories to reach recovery goals in the Kern Management Unit, we also identified a small portion of Canebrake Creek in Kern County within our large population areas as being essential to flycatcher conservation. Canebrake Creek (a tributary to the South Fork Kern River) was not within the geographical area known to be occupied at the time of listing, but territories were detected in 1998 (Sogge and Durst 2008).</P>
          <P>We are designating as critical habitat a 23.6-km (14.6-mi) portion of the South Fork Kern River (including the upper 1.0-km (0.6-mi) portion of Lake Isabella) and a 1.7-km (1.0-mi) segment of Canebrake Creek in Kern County, California. Along this segment of the South Fork Kern River, two pieces of private land that are woven within this segment, the Hafenfeld Ranch (0.30 km, 0.20 mi of stream on the south side of the river) and Sprague Ranch (4.0 km, 2.5 mi on north side of the river), are being excluded from the final designation (see below and Exclusions section).</P>
          <P>The South Fork Kern River segment was the lone segment identified within this Management Unit as having substantial recovery value in the Recovery Plan (Service 2002, p. 88). The South Fork Kern River and the additional Canebrake Creek segment are important for flycatcher conservation because they are anticipated to provide habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <P>Flycatcher habitat on the Hafenfeld Ranch along the South Fork of the Kern River is being excluded under section 4(b)(2) of the Act due to a conservation easement established with the National Resource Conservation Service (NRCS) specific to protecting flycatcher habitat. As a result of the habitat protections provided through this easement, this property is being excluded from this critical habitat designation (see Exclusions section below).</P>

          <P>Flycatcher habitat on the Sprague Ranch along the South Fork of the Kern River is being excluded under section 4(b)(2) of the Act due to protections assured by their long-term commitments to management programs specific to the riparian habitat and needs of the flycatcher. The Sprague Ranch was acquired specifically for flycatcher conservation and is co-managed by the Corps, the California Department of Fish and Game (CDFG), and the National<PRTPAGE P="370"/>Audubon Society (Audubon) (see Exclusions section below).</P>
          <HD SOURCE="HD3">Mojave Management Unit, California</HD>
          <P>The Recovery Plan describes a goal of 25 territories in the Mojave Management Unit (Service 2002, p. 84). The Mojave River and Holcomb Creek are the only streams known to have flycatcher territories within the Mojave Management Unit (Sogge and Durst 2008).</P>
          <P>There are no large flycatcher nesting populations in the Mojave Management Unit to help guide us toward a critical habitat area, and no areas were known to be occupied at the time of listing. Therefore, to identify the areas that would contribute to meeting recovery goals for this Management Unit, we used information based on currently known flycatcher territories and breeding sites, guidance from the Recovery Plan, and knowledge about stream habitat to determine areas essential for flycatcher conservation.</P>
          <P>Flycatchers were first detected nesting on the Mojave River in 1995 and Holcomb Creek in 1999. A total of five breeding sites occur along the Mojave River and one site at Holcomb Creek (Sogge and Durst 2008). A high of 12 territories were detected at these breeding sites in 2001 (Sogge and Durst 2008). In addition, we found additional areas that would contribute to meeting recovery goals in the West Fork Mojave River and Deep Creek.</P>
          <P>We are designating as flycatcher critical habitat a 35.7-km (22.2-mi) segment of the Mojave River, an 11.2-km (6.9-mi) segment of the West Fork Mojave River, a 19.6-km (12.2-mi) segment of Holcomb Creek, and a 20.0-km (12.5-mi) segment of Deep Creek (including Mojave River Forks Reservoir) in San Bernardino County, California, near the Town of Victorville. Deep Creek connects Holcomb Creek with the Mojave Forks Reservoir. All of these segments were not within the geographical area known to be occupied at the time of listing, but are essential for flycatcher conservation because they will help meet recovery goals.</P>
          <P>Three of these streams (Mojave River, West Fork Mojave River, and Deep Creek) were identified as having substantial recovery value in the Recovery Plan (Service 2002, p. 88). Holcomb Creek was not specifically identified in the Recovery Plan, but since flycatcher territories have been detected there we find it also important to meet recovery goals. Together, these four critical habitat segments are essential to flycatcher conservation because they are anticipated to provide habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <HD SOURCE="HD3">Salton Management Unit, California</HD>
          <P>The Recovery Plan describes a goal of 25 flycatcher territories in the Salton Management Unit (Service 2002, p. 84). A single known flycatcher breeding site occurs along San Felipe Creek in this Management Unit.</P>
          <P>There are no large flycatcher nesting populations solely in the Salton Management Unit, and no areas were within the geographical area known to be occupied at the time of listing. However, portions of the Salton Management Unit were part of a large population area because of the proximity of flycatcher territories in the adjacent San Diego and Santa Ana Management Units. Therefore, to identify the areas that would contribute to meeting recovery goals for this Management Unit, we used information based on currently known flycatcher territories and breeding sites, guidance from the Recovery Plan, and knowledge about stream habitat to determine areas essential for flycatcher conservation (see below). From 1998 to 2002, flycatcher territories were detected in small numbers (2 to 4 territories) at single breeding site on San Felipe Creek within this Management Unit (Sogge and Durst 2008).</P>
          <P>We are designating as flycatcher critical habitat a 19.7-km (12.3-mi) segment of San Felipe Creek and a short 0.9-km (0.6 mi) segment of Mill Creek in San Diego County, California. This short portion of Mill Creek is connected to the Mill Creek segment within the Santa Ana Management Unit. We find that both of the segments are essential for flycatcher conservation because they will help meet recovery goals.</P>
          <P>Although the San Felipe Creek segment proposed as critical habitat was the only river segment identified in the Recovery Plan as having substantial recovery value (Service 2002, p. 88), the additional Mill Creek segment was identified within the Santa Ana Management Unit as having substantial recovery value (Service 2002, p.88). As a result, the San Felipe and Mill Creek segments, along with the other populations and river segments in proximity within the adjacent San Diego and Santa Ana Management Units are essential to flycatcher conservation because they are anticipated to provide habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <P>A small portion of San Felipe Creek (1.6 km, 1.0 mi) that occurs within the Iipay Nation of Santa Ysabel, California (formerly the Santa Ysabel Band of Diegueno Mission Indians of the Santa Ysabel Reservation), was identified as having features essential to the flycatcher. Because of our partnership with the Tribe toward conservation of flycatcher habitat, the portion of San Felipe Creek that occurs on the Iipay Nation lands is being excluded from the final critical habitat designation under section 4(b)(2) of the Act (see Exclusions  section below).</P>
          <HD SOURCE="HD3">Amargosa Management Unit, California and Nevada</HD>
          <P>The Recovery Plan describes a goal of 25 flycatcher territories in the Amargosa Management Unit (Service 2002, p. 84). Flycatcher territories have been detected in small numbers within this Management Unit.</P>
          <P>There are no large flycatcher nesting populations in the Amargosa Management Unit to help guide us toward a critical habitat area, and no areas were within the geographical area known to be occupied at the time of listing. Therefore, to identify the areas that would contribute to meeting recovery goals for this Management Unit, we used information based on currently known flycatcher territories and breeding sites, guidance from the Recovery Plan, and knowledge about stream habitat to determine areas essential for flycatcher conservation (see below).</P>
          <P>Within the Amargosa Management Unit, one breeding site has been detected on the Amargosa River and two breeding sites are known within the Ash Meadows NWR (Sogge and Durst 2008). From 1998 to 2007, one to seven territories were detected at these breeding sites within this Management Unit (Sogge and Durst 2008). Therefore, we sought additional areas for critical habitat that could contribute to recovery goals in this Management Unit.</P>

          <P>We refined our proposal within the Amargosa Management Unit in our July 12, 2012 (77 FR 41147), Notice of<PRTPAGE P="371"/>Availability, by identifying five specific stream segments and their management within the Ash Meadows NWR, in Nye County, Nevada. These areas were not within the geographical area known to be occupied by the flycatcher at the time of listing.</P>
          <P>We are designating as flycatcher critical habitat five areas on the Ash Meadows NWR in Nye County, Nevada: Soda Spring segment (0.5 km, 0.3 mi); Lower Fairbanks segment (0.8 km, 0.5 mi); Crystal Reservoir segment (0.5 km, 0.3 mi); North Tubbs segment (0.2 km, 0.1 mi); and South Tubbs segment (0.4 km, 0.2 mi). We are also designating segments of the Amargosa River (12.3 km, 7.7 mi) and Willow Creek (3.5 km, 2.2 mi) in Inyo and San Bernardino Counties, California. No known breeding sites have yet to be detected on the Amargosa River and Willow Creek segments in California. None of the segments were within the geographical area known to be occupied at the time of listing.</P>
          <P>The Ash Meadows NWR and the Amargosa River in California, were described in the Recovery Plan as having substantial recovery value (Service 2002, p. 88). Willow Creek was also determined to be essential in order to reach recovery goals in this Management Unit. Together, these segments are essential to flycatcher conservation because they are anticipated to provide habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <HD SOURCE="HD3">Lower Colorado Recovery Unit</HD>
          <P>This is a geographically large and ecologically diverse Recovery Unit, encompassing the Colorado River and its major tributaries (such as the Virgin, Pahranagat, Muddy, and Little Colorado Rivers) from the high-elevation streams in White Mountains of East-Central Arizona and Central Western New Mexico to the mainstem Colorado River through the Grand Canyon downstream through the arid lands along the LCR to the Mexico border (Service 2002, p. 64).</P>

          <P>In 2002, despite its size, the Lower Colorado Recovery Unit had only 127 known flycatcher territories (11 percent of the rangewide total), most of which occur away from the mainstem Colorado River (Sogge<E T="03">et al.</E>2003, p. 10). In 2007, 150 territories were estimated to occur within this Recovery Unit (also 11 percent of the rangewide total) (Durst<E T="03">et al.</E>2008, p. 12). Most sites included fewer than 5 territories; the largest populations (most of which are fewer than 10 territories) are found on the Bill Williams, Virgin, and Pahranagat Rivers (Service 2002, p. 64). Approximately 69 percent of territories are found on government-managed lands and 8 percent are on tribal lands (Service 2002, p. 64). Habitat characteristics range from purely native (including high-elevation and low-elevation willow) to exotic (primarily tamarisk)-dominated stands (Service 2002, p. 64). Because of the similarity in abundance and distribution of territories since 2002, these land ownership and habitat-use statistics are likely similar today. This Recovery Unit contains the Little Colorado, Middle Colorado, Virgin, Pahranagat, Bill Williams, Hoover to Parker Dam, and Parker Dam to Southerly International Border Management Units.</P>

          <P>Based upon our occupancy criteria (see above), within the Lower Colorado Recovery Unit, the Colorado (1993), Little Colorado (1993), Bill Williams (1994), Big Sandy (1994), Santa Maria (1994), and Zuni (1993) Rivers, and Rio Nutria (1993) are streams that were within the geographical area known to be occupied at the time of listing (1991-1994) (Sogge and Durst 2008) where we proposed critical habitat segments. At the time of listing only specific sites on the Colorado River within the Middle Colorado Management Unit were known to be specifically occupied with territories, but based upon our criteria and the wide-ranging nature of this bird as a neotropical migrant and its use of migration stop-over habitat, we also consider the Colorado River within the Hoover to Parker Dam and Parker Dam to Southerly International Border Management Units occupied at the time of listing. Below we identify that each listed item described in our<E T="03">Special Management Considerations or Protection</E>section (see above) applies to the streams described in each Management Unit within the Lower Colorado Recovery Unit.</P>
          <HD SOURCE="HD3">Little Colorado Management Unit, Arizona and New Mexico</HD>
          <P>The Recovery Plan describes a goal of 50 flycatcher territories in the Little Colorado Management Unit (Service 2002, p. 84). Flycatcher territories have been detected on the Little Colorado and Zuni Rivers and Rio Nutria within this large area along the New Mexico and Arizona border (Sogge and Durst 2008).</P>
          <P>We identified a large flycatcher nesting population surrounding the Little Colorado River, near the Town of Greer in Apache County, Arizona. Flycatcher territories have been detected along the Little Colorado River, Zuni River, and Rio Nutria since 1993. A high of 16 territories were detected on these river segments in 1996, but known territories have declined, with only two and six territories detected in 2005 and 2006, respectively (Sogge and Durst 2008). Because of the need to increase the abundance of flycatcher territories to reach recovery goals, we also identified the Zuni River and Rio Nutria in McKinley County, New Mexico, and the West Fork Little Colorado River, in Apache County, Arizona. No flycatcher territories are known from the West Fork Little Colorado River.</P>
          <P>We are designating as flycatcher critical habitat a contiguous 8.8-km (5.5-mi) segment of the West Fork Little Colorado River and a 17.6-km (10.9-mi) segment of the Little Colorado River. This West Fork and Little Colorado River segment begins where USFS (Forest Service) Road 113 crosses the West Fork and extends downstream to its confluence with the Little Colorado River, through the Town of Greer, and ends at the Diversion Ditch. The Little Colorado River was within the geographical area known to be occupied at the time of listing, and contains the physical or biological features essential to the conservation of the species which may require special management considerations or protection, as described above. The West Fork Little Colorado River is not within the geographical area known to be occupied at the time of listing, but is essential to flycatcher conservation of the flycatcher in order to meet recovery goals, as described above.</P>
          <P>The Little Colorado River and the West Fork Little Colorado River segments were identified in the Recovery Plan as areas with substantial recovery value (Service 2002, p. 89). These two stream segments are anticipated to provide habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>

          <P>Proposed segments along the Rio Nutria (55.4 km, 34.4 mi) and Zuni River (35.8 km, 22.2 mi), occurring on<PRTPAGE P="372"/>Zuni Pueblo in New Mexico, are within the geographical area known to be occupied by flycatchers at the time of listing, and contain the physical or biological features essential to the conservation of the species which may require special management considerations or protection. Because of our partnership with Zuni Pueblo toward wildlife conservation, and their development, completion, and implementation of actions described in their Flycatcher Management Plan, we have excluded the Rio Nutria and Zuni River stream segments that occur on Zuni Pueblo under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <HD SOURCE="HD3">Virgin Management Unit, Utah, Arizona and Nevada</HD>
          <P>The Recovery Plan describes a goal of 100 flycatcher territories in the Virgin Management Unit (Service 2002, p. 84). Flycatcher territories have been detected along a broad area of the Virgin River within this Management Unit through the States of Utah, Arizona, and Nevada (Sogge and Durst 2008).</P>

          <P>We identified a large flycatcher nesting population along an essential segment of the Virgin River where it occurs through Washington County, Utah; Mohave County, Arizona; and Clark County, Nevada. Flycatchers were first detected nesting on this portion of the Virgin River in 1995. A total of seven breeding sites have been detected within this large population area through 2007 (Durst<E T="03">et al.</E>2008, p. 12). Also, a high of 43 territories were estimated to occur within this Management Unit in 2007 (Durst<E T="03">et al.</E>2008, p. 12), most occurring within the State of Nevada, although territories are also known along the Virgin River in Utah and Arizona.</P>
          <P>We are designating as flycatcher critical habitat a 152.0-km (94.4-mi) segment (total length) of the Virgin River that begins at Berry Springs in Washington County, Utah, continues 47.5 km (29.5 mi) through the State of Utah, then extends 56.0 km (34.8 mi) through the Town of Littlefield and the State of Arizona, and then 48.4 km (30.0 mi) through the State of Nevada until it ends at Colorado River Mile 280 at the upper end of Lake Mead, Clark County, Nevada. This segment is not within the geographical area known to be occupied at the time of listing, but is being designated as critical habitat because it is essential for flycatcher conservation in the Virgin River Management Unit in order to meet recovery goals.</P>
          <P>The Virgin River was identified as having substantial recovery value in the Recovery Plan (Service 2002, p. 89). This essential segment of the Virgin River we are designating as critical habitat within the Virgin River Management Unit is anticipated to provide habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, this river segment and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <HD SOURCE="HD3">Middle Colorado Management Unit, Arizona</HD>
          <P>The Recovery Plan describes a goal of 25 flycatcher territories in the Middle Colorado Management Unit (Service 2002, p. 84).</P>

          <P>We identified a large flycatcher nesting population along the lower portion of the Colorado River within the Grand Canyon (including upper Lake Mead) in Mohave County, Arizona. Flycatchers were first detected nesting along the Colorado River within the Middle Colorado Management Unit in 1993. A total of 16 breeding sites have been detected in our selected segment through 2007. Also, a high of 16 territories was detected within this Management Unit in 1998 (Sogge and Durst 2008), but has declined to an estimated 4 territories in 2007 (Durst<E T="03">et al.</E>2008, p. 12).</P>
          <P>We proposed as critical habitat a 74.1-km (46.0-mi) segment of the Colorado River that extends from the middle of Lake Mead upstream to Colorado River Mile 243. This entire segment is within the full pool elevation of Lake Mead. The Colorado River in Mohave County, Arizona, is within the geographical area known to be occupied by flycatchers at the time of listing, and contains the physical or biological features essential to the conservation of the species which may require special management considerations or protection, as described above.</P>
          <P>This Middle Colorado River segment was identified as having substantial recovery value in the Recovery Plan (Service 2002, p. 89). The portion of the Colorado River we proposed as critical habitat, within the Middle Colorado Management Unit, is anticipated to provide habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, this river segment and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <P>The conservation space of Lake Mead and the Colorado River immediately upstream is within the planning area of the LCR Multi-Species Conservation Plan (LCR MSCP) up to full pool elevation of Lake Mead. The full pool elevation is defined by water surface elevation 1,229 feet National Geodetic Vertical Datum, which extends up to near river mile 235 at Separation Canyon. The Hualapai Nation, which also occurs within this segment, is also within the planning area of the LCR MSCP. The Nation developed, completed, and is implementing actions described in their Flycatcher Management Plan. As a result of the upper portion of Lake Mead and the Colorado River through river mile 235 being included in the planning area of the LCR MSCP, this entire segment is being excluded from this critical habitat designation under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <HD SOURCE="HD3">Pahranagat Management Unit, Nevada</HD>
          <P>The Recovery Plan describes a goal of 50 flycatcher territories in the Pahranagat Management Unit (Service 2002, p. 84).</P>
          <P>We identified a large flycatcher nesting population along the Pahranagat River and the Muddy River. Flycatchers were first detected nesting on these portions of the Pahranagat and Muddy Rivers in 1997. Through 2007, a total of three breeding sites were known to occur within these segments, with a high of 38 territories detected in 2006 (Sogge and Durst 2008).</P>
          <P>We are designating as flycatcher critical habitat a 3.6-km (2.3-mi) segment of the Pahranagat River through the Pahranagat NWR in Nye County, Nevada. This segment is not within the geographical area known to be occupied at the time of listing, but is being designated as critical habitat because it is essential for flycatcher conservation in order to meet recovery goals in the Pahranagat Management Unit.</P>

          <P>The Pahranagat River segment was identified as having substantial recovery value in the Recovery Plan (Service 2002, pp. 89-90). This essential river segment we are designating as critical habitat within the Pahranagat Management Unit is anticipated to provide habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, this river segment and associated flycatcher habitat is anticipated to<PRTPAGE P="373"/>support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <P>The Pahranagat River (2.5 km, 1.6 mi and 1.4 km, 0.9 mi) segments within the Key Pittman State Wildlife Area in Lincoln County and the 3.1-km (1.9-mi) Muddy River segment within the boundaries of the Overton State Wildlife Area in Clark County, Nevada, were also identified as being essential to flycatcher conservation. As a result of the State of Nevada's management of the Key Pittman and Overton State Wildlife Areas for wildlife and riparian habitat for the flycatcher, both of these proposed segments in this Management Unit are being excluded from this designation under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <HD SOURCE="HD3">Bill Williams Management Unit, Arizona</HD>
          <P>The Recovery Plan describes a goal of 100 flycatcher territories in the Bill Williams Management Unit (Service 2002, p. 84). Flycatcher territories are distributed across a broad area of the Bill Williams Management Unit.</P>
          <P>We identified a large flycatcher nesting population in the Bill Williams Management Unit. It encompasses areas along the Big Sandy River near the Town of Wikieup in Mohave County; the Big Sandy, Santa Maria, and Bill Williams Rivers at the upper end of Alamo Lake in La Paz County; and along the Bill Williams River between Alamo Dam and the Colorado River in La Paz and Mohave Counties. Flycatchers were first detected nesting on the Big Sandy, Santa Maria, and Bill Williams Rivers in 1994 (Sogge and Durst 2008). Through 2007, a total of 9 breeding sites occurred within these segments with a high of 61 territories detected in 2004 (Sogge and Durst 2008). Since 2007, an additional breeding site was discovered on the upper Big Sandy River and an additional two sites discovered along the Bill Williams River.</P>
          <P>We are designating as flycatcher critical habitat a 35.3-km (21.9-mi) segment of the upper Big Sandy River from the Town of Wikieup to Groom Peak Wash in La Paz County, Arizona. At upper Alamo Lake where the Big Sandy (9.6 km, 6.0 mi), Santa Maria (8.4 km, 5.2 mi), and Bill Williams Rivers (5.4 km, 3.3 mi) converge, we are designating collectively, a 23.4-km (14.5-mi) portion of these three streams in La Paz County. Between Alamo Dam and the Colorado River, we are designating as critical habitat a 17.8-km (11.0-mi) segment of the Bill Williams River near Lincoln Ranch in La Paz and Mohave Counties, Arizona. Also below Alamo Dam, closer to the Colorado River, we are designating as critical habitat a 12.4 km (7.7 mi) of the Bill Williams River from Casteñeda Wash downstream of Planet Ranch to the middle of the Bill Williams NWR, where it meets the boundary of the LCR MSCP planning area. All of these areas are within the geographical area known to be occupied by flycatchers at the time of listing, and contain the physical or biological features essential for the conservation of the species which may require special management considerations or protection, as described above.</P>
          <P>The Big Sandy, Santa Maria, and Bill Williams Rivers were identified as having substantial recovery value in the Recovery Plan (Service 2002, p. 90). These river segments we are designating within the Bill Williams Management Unit are anticipated to provide habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river segments and associated flycatcher habitat is anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <P>An 8.9-km (5.6-mi) section of the lower Bill Williams River within the Bill Williams River NWR is also within the geographical area known to be occupied by flycatchers at the time of listing, and contains the physical or biological features essential to the conservation of the species, which may require special management considerations or protection. This portion of the Bill Williams River occurs within the planning area of the LCR MSCP. As a result of the conservation provided the flycatcher within the LCR MSCP planning area, this portion of the Bill Williams River is being excluded from this critical habitat designation under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <HD SOURCE="HD3">Hoover to Parker Dam Management Unit, Arizona and California</HD>
          <P>The Recovery Plan describes a goal of 50 flycatcher territories in the Hoover to Parker Dam Management Unit (Service 2002, p. 84).</P>
          <P>We identified a large flycatcher nesting population along the Colorado River (and a small portion of the Bill Williams River) within Mohave and La Paz Counties, Arizona, and San Bernardino County, California. Flycatchers were first detected on this portion of the Colorado River in 1995 (Sogge and Durst 2008). Through 2007, a total of 6 breeding sites occurred within this segment (Durst 2008, p. 12) with a high of 34 territories detected in 2004 (Sogge and Durst 2008).</P>
          <P>These segments of the Colorado River and Bill Williams River were identified as having substantial recovery value in the Recovery Plan (Service 2002, p. 90). These river segments are anticipated to provide flycatcher habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <P>These segments of the Colorado River (107.0 km, 66.4 mi) and Bill Williams River (1.7 km, 1.0 mi) are within the geographical area known to be occupied by flycatchers at the time of listing, and contain the physical or biological features essential to the conservation of the species, which may require special management considerations or protection. The entirety of the segments proposed as flycatcher critical habitat occur within the planning area of the LCR MSCP. The Fort Mojave and Chemehuevi Tribes also occur within this segment and are also within the planning area of the LCR MSCP. These tribes have developed, completed, and are implementing actions described in their Flycatcher Management Plans. As a result of the flycatcher conservation occurring along the Colorado River and Bill Williams River as a result of being included within the planning area of the LCR MSCP, these entire segments are being excluded from this critical habitat designation under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <HD SOURCE="HD3">Parker Dam to Southerly International Border Management Unit, Arizona and California</HD>
          <P>The Recovery Plan describes a goal of 150 flycatcher territories in the Parker Dam to Southerly International Border Management Unit (Service 2002, p. 84).</P>

          <P>We identified a large flycatcher nesting population along the Colorado River within La Paz and Yuma Counties, Arizona, and San Bernardino, Riverside, and Imperial Counties, California. Flycatcher territories were first detected on this portion of the Colorado River in 1995 (Sogge and Durst 2008). Through 2007, a total of 16 breeding sites occurred within this Management Unit (Durst 2008, p.12), with a high of 15<PRTPAGE P="374"/>territories detected in 1996 (Sogge and Durst 2008). In 2007, it was estimated that only one territory occurred within this Management Unit (Sogge and Durst 2008).</P>
          <P>This segment of the Colorado River was identified as having substantial recovery value in the Recovery Plan (Service 2002, p. 90). This portion of the LCR is anticipated to provide flycatcher habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, this portion of the LCR and associated flycatcher habitat is anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <P>The LCR within the Parker to Southerly International Border Management Unit is within the geographical area known to be occupied by flycatchers at the time of listing, and contains the physical or biological features essential to flycatcher conservation which may require special management considerations or protection. The entirety of the segments proposed as flycatcher critical habitat occurs within the planning area of the LCR MSCP. The Colorado Indian and Quechan (Fort Yuma) tribal lands occur within these segments and are also within the planning area of the LCR MSCP. These tribes have developed, completed, and are implementing actions described in their Flycatcher Management Plans. As a result of the flycatcher conservation occurring along the Colorado River from being included within the planning area of the LCR MSCP, these segments are being excluded from this critical habitat designation under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <HD SOURCE="HD3">Upper Colorado Recovery Unit</HD>

          <P>The Upper Colorado Recovery Unit is comprised of a broad geographic area covering much of the Four Corners area of southeastern Utah and southwestern Colorado, with smaller portions of northwestern Arizona and northeastern New Mexico. Ecologically, this area may be an intergradation area between the southwestern willow flycatcher subspecies and the Great Basin willow flycatcher subspecies (Service 2002, p. 64). Flycatchers are only known to breed at five breeding sites across this broad Recovery Unit, representing an estimated high of 10 territories occurring in 2007 (Durst<E T="03">et al.</E>2008, p.13). However, this low number of breeding sites and territories (less than 1 percent of the rangewide total) is probably a function of relatively low survey effort rather than an accurate reflection of the bird's actual numbers and distribution (Service 2002, p. 64). Much willow riparian habitat occurs along drainages within this Recovery Unit and remains to be surveyed (Service 2002, p. 64). The Upper Colorado Recovery Unit contains the Powell and San Juan Management Units.</P>

          <P>Based upon our occupancy criteria (see above), within the Upper Colorado Recovery Unit, no streams were known to be occupied at the time of listing (1991-1994) (Sogge and Durst 2008). Below we identify that each listed item described in our<E T="03">Special Management Considerations or Protection</E>section (see above) applies to the streams described in each Management Unit within the Upper Colorado Recovery Unit.</P>
          <HD SOURCE="HD3">San Juan Management Unit, Colorado, New Mexico, Arizona, and Utah</HD>
          <P>The Recovery Plan describes a goal of 25 flycatcher territories in the San Juan Management Unit (Service 2002, p. 84). Flycatcher territories have been detected in small numbers over a broad area of the southwestern Colorado and northwestern New Mexico within the Management Unit.</P>

          <P>There were no large flycatcher nesting populations in the San Juan Management Unit to help guide us toward a critical habitat area, and no areas were known to be occupied at the time of listing. Therefore, to identify the areas that would contribute to meeting recovery goals for this Management Unit, we used information based on known flycatcher territories and breeding sites, guidance from the Recovery Plan, and knowledge about stream habitat to determine critical habitat segments that may be essential for flycatcher conservation (see below). In 2007, 10 territories were estimated to occur (within a total of 3 breeding sites) along the Los Pinos River in southwestern Colorado in La Plata County, Colorado, and along the San Juan River in San Juan County, New Mexico (Durst<E T="03">et al.</E>2008, p. 13). Through 2007, no known breeding sites have yet to be detected in the Utah portion of this Management Unit (Sogge and Durst 2008).</P>
          <P>Following our August 15, 2011, proposal, we reevaluated the Los Pinos River segment following further habitat analysis (Ireland, T. 2012, entire) and determined that the upper portion of this stream contained habitat, vegetation, and features that do not support flycatcher habitat. As a result, this reduced the overall length of the Los Pinos River that we considered essential for flycatcher conservation and were considering for flycatcher critical habitat (see Summary of Changes from Proposed Rule above).</P>
          <P>We are designating as flycatcher critical habitat a segment of the Los Pinos River in La Plata County, Colorado (7.2 km, 4.5 mi), and the northern bank of the San Juan River in San Juan County, Utah (43.5 km, 27.0 mi). The Los Pinos River segment begins at a private road crossing of the Los Pinos River west of the Pine River Ranch Road, approximately 3.7 km (2.3 mi) north of Highway 160 near the town of Bayfield, and ends at the northern boundary of Southern Ute tribal land. The north bank of the San Juan River in Utah occurs from the Navajo Nation boundary downstream to Chinle Creek. These segments were not within the geographical area known to be occupied at the time of listing, but are essential for flycatcher conservation in order to help meet recovery goals in this Management Unit.</P>
          <P>These segments of the San Juan and Los Pinos Rivers were identified as having substantial recovery value in the Recovery Plan (Service 2002, p. 88). These essential river segments are anticipated to provide flycatcher habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>

          <P>Segments along the Los Pinos River that occur on Southern Ute tribal land in Colorado, and San Juan River on the Navajo Nation in New Mexico and Utah (southern bank), were not within the geographical area known to be occupied by flycatchers at the time of listing, but essential for flycatcher conservation in order to meet recovery. Because of our partnership with the Southern Ute Tribe and Navajo Nation toward wildlife conservation, and their development, completion, and implementation of actions described in their Flycatcher Management Plans, we have excluded the portions of the Los Pinos River in Colorado and San Juan River in New Mexico and Utah (south bank) that occur tribal lands under section 4(b)(2) of the Act (see Exclusions section below).<PRTPAGE P="375"/>
          </P>
          <HD SOURCE="HD3">Powell Management Unit, Utah and Arizona</HD>
          <P>The Recovery Plan describes a goal of 25 flycatcher territories in the Powell Management Unit (Service 2002, p. 84). No flycatcher territories have been detected in this Management Unit (Sogge and Durst 2008).</P>
          <P>There were no large flycatcher nesting populations in the Powell Management Unit to help guide us toward a critical habitat area, and no areas were known to be occupied at the time of listing. Therefore, to identify the areas that would contribute to meeting recovery goals for this Management Unit, we used information based on guidance from the Recovery Plan and available information about stream habitats to determine critical habitat segments that may be essential for flycatcher conservation (see below).</P>
          <P>We are designating as flycatcher critical habitat a segment of the Paria River in Kane County, Utah (19.0 km, 11.8 mi). This Paria River segment occurs from its confluence with Cottonwood Wash and ends at Highway 89. This segment was not within the geographical area known to be occupied by flycatchers at the time of listing. This river segment may be able develop and sustain flycatcher habitat and territories and therefore is essential to flycatcher conservation in order to help meet recovery goals in this Management Unit.</P>
          <P>This segment of the Paria River was identified as having substantial recovery value in the Recovery Plan (Service 2002, p. 88). This essential river segment is anticipated to provide flycatcher habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, this river segment and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <HD SOURCE="HD3">Gila Recovery Unit</HD>

          <P>The Gila Recovery Unit includes the Gila River watershed, from its headwaters in southwestern New Mexico downstream across the State of Arizona toward the confluence with the Colorado River, in southwest Arizona (Service 2002, p. 65). In 2002, 588 flycatcher territories (51 percent of the estimated rangewide total) were estimated to occur, distributed primarily on the Gila and lower San Pedro Rivers (Sogge<E T="03">et al.</E>2003, pp. 10-11). From the latest rangewide estimate, the number of known territories grew to 659 within this Recovery Unit (50 percent of the estimated rangewide total) (Durst<E T="03">et al.</E>2008, p. 12).</P>

          <P>Many breeding sites have small numbers of territories within the Gila Recovery Unit, but along sections of the upper and middle Gila River, lower San Pedro River, lower Tonto Creek, and the Tonto Creek and Salt River confluence within the water conservation space of Roosevelt Lake, abundant breeding sites occur over a relatively broad geographic range that together comprise many flycatcher territories. Following the 2007 rangewide estimate (Durst<E T="03">et al.</E>2008, p. 12), the Upper Gila, Middle Gila and San Pedro, and Roosevelt Management Units had surpassed numerical recovery goals. Within the Gila Recovery Unit, there are concentrations of flycatcher territories in the Cliff-Gila Valley, New Mexico, and at Roosevelt Lake, Arizona, that can be some of the largest across its range.</P>
          <P>Flycatcher territories in the Gila Recovery Unit occurred primarily on lands managed by private and Federal land managers and in a variety of habitat types dominated by both native and exotic plants. In 2001, private lands hosted 50 percent of the territories (mostly on the San Pedro River and Gila River), including one of the largest known flycatcher populations, in the Cliff-Gila Valley, New Mexico (Service 2002, p. 65). Almost the remaining 50 percent of the territories were on government-managed lands (Service 2002, p. 65). While in 2001 (Service 2002, p. 65), 58 percent of territories were in habitats dominated by native plants, flycatchers in this Recovery Unit also make extensive use of exotic (77 territories) or exotic-dominated (108 territories) vegetation (primarily tamarisk). Because the current distribution of breeding sites in this Recovery Unit is similar, we believe these statistics are mostly accurate today. This Recovery Unit contains the Verde, Hassayampa and Agua Fria, Roosevelt, San Francisco, Upper Gila, Middle Gila and San Pedro, and Santa Cruz Management Units.</P>

          <P>Based upon our occupancy criteria (see above), within the Gila Recovery Unit, the Gila (1993), San Pedro (1993), San Francisco (1993), Verde (1993), and Salt (1993) Rivers, and Tonto Creek (1993) are streams that were within the geographical area known to be occupied at the time of listing (1991-1994) (Sogge and Durst 2008) where we are designating critical habitat segments. At the time of listing, only specific sites on the Gila River within the Middle Gila and San Pedro and Upper Gila Management Units were known to be specifically occupied by nesting birds, but based upon our criteria and the wide-ranging nature of this neotropical migrant, the Gila River within the Hassayampa and Agua Fria Management Unit is also considered occupied at the time of listing. Below we identify that each listed item described in our<E T="03">Special Management Considerations or Protection</E>section (see above) applies to the streams described in each Management Unit within the Gila Recovery Unit.</P>
          <HD SOURCE="HD3">Verde Management Unit, Arizona</HD>
          <P>The Recovery Plan describes a goal of 50 flycatcher territories in the Verde Management Unit (Service 2002, p. 85).</P>
          <P>We identified a large flycatcher nesting population along the Verde River within Yavapai, Gila, and Maricopa Counties, Arizona. Flycatchers were first detected nesting on the Verde River in 1993; a total of six breeding sites are known and are spread out from the Verde Valley near the towns of Clarkdale and Camp Verde and downstream near Horseshoe Lake (Sogge and Durst 2008). A high of 23 territories were detected within this Management Unit in 2005 (Sogge and Durst 2008).</P>

          <P>We are designating as flycatcher critical habitat five separate segments of the Verde River (three segments on upper Verde River and two segments along the middle Verde River). Along the upper Verde River through the Verde Valley, in Yavapai County, we are designating a 42.0-km (26.1-mi) segment of the that occurs from above Tuzigoot National Monument near the Town of Clarkdale, downstream through the towns of Cottonwood to the north end of Yavapai Apache tribal land. At the southern end of Yavapai Apache tribal land the next segment (15.3 km, 9.5 mi) extends toward Camp Verde where it meets the north end of another, separate piece of Yavapai Apache tribal land. At the southern end of this additional piece of Yavapai Apache tribal land, the third and last river segment along the upper Verde River extends 14.0 km (8.7 mi) to Beasley Flat. We are also designating a 46.3-km (28.8-mi) segment in the middle Verde River that extends from the East Verde River confluence down to the upper end of Horseshoe Lake. The last (6.7 km, 4.2 mi) segment of the Verde River designated as flycatcher critical habitat occurs from Horseshoe Dam and ends a short distance downstream to the USGS gauging station and cable crossing. These segments of the Verde River are within the geographical area known to be occupied by flycatchers at the time of listing, and contain the physical or<PRTPAGE P="376"/>biological features essential to the conservation of the species which may require special management considerations or protection, as described above.</P>
          <P>The Verde River was the lone river identified within this Management Unit as having substantial recovery value in the Recovery Plan (Service 2002, p. 91). These river segments are anticipated to provide flycatcher habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <P>The conservation space of Horseshoe Lake is within the planning area of the Horseshoe and Bartlett Dams HCP. As a result of the management and protection provided flycatcher habitat within the conservation space of Horseshoe Lake due to its inclusion in the HCP, this portion of the Verde River (9.6 km, 6.0 mi) is being excluded from this critical habitat designation under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <P>Two separate sections (2.1 km, 1.3 mi and 0.7 km, 0.4 mi) of the upper Verde River occur on Yavapai Apache tribal lands. Because of our partnership with the Yavapai Apache Tribe toward wildlife conservation, and their development, completion, and implementation of actions described in their Flycatcher Management Plan, we have excluded these two sections of the Verde River that occur on their tribal lands under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <HD SOURCE="HD3">Roosevelt Management Unit, Arizona</HD>
          <P>The Recovery Plan describes a goal of 50 flycatcher territories in the Roosevelt Management Unit (Service 2002, p. 85).</P>
          <P>We identified a large flycatcher nesting population surrounding the Roosevelt Lake area along Tonto Creek, the Salt River, and Pinal Creek in Gila and Pinal Counties, Arizona. Flycatchers were first detected nesting on Tonto Creek and the Salt River within the conservation space of Roosevelt Lake in 1993 (Sogge and Durst 2008).</P>
          <P>Because of the anticipated water level fluctuations at Roosevelt Lake, which inundates many flycatcher territories and limits the number of territories that can be sustained over time, this is the only Management Unit within the flycatcher's range where the recovery goal was smaller than the known number of territories at the time of the Recovery Plan completion. As a result, river segments and the lakebed together provide habitat that allow flycatcher territories to persist over time due to dynamic river and lake flooding events. For example, a high of 196 flycatcher territories occurred in 2004 (mostly within the conservation space of Roosevelt Lake), but in the following years after the lake level was raised, the known number of territories declined to 75 in 2007 (Sogge and Durst 2008). Since the raising of the water level in Roosevelt Lake, flycatchers have expanded their known distribution throughout adjacent areas along Tonto Creek, Salt River, and Pinal Creek (Sogge and Durst 2008).</P>
          <P>We are designating as flycatcher critical habitat a segment of lower Tonto Creek and a segment of the upper Salt River. The lower Tonto Creek segment extends for 49.0-km (30.5-mi) and occurs from the south end of the Town of Gisela downstream to the western high-water-mark side of the conservation space of Roosevelt Lake. On the eastern side of Roosevelt Lake, we are designating a 38.9-km (24.2-mi) segment from the Salt River confluence with Cherry Creek downstream to the high water mark of the conservation space of Roosevelt Lake. These segments are within the geographical area known to be occupied by flycatchers at the time of listing, and contain the physical or biological features essential to the conservation of the species which may require special management considerations or protection, as described above.</P>
          <P>The segments of Tonto Creek and the Salt River were identified as having substantial recovery value in the Recovery Plan (Service 2002, p. 91). These segments are anticipated to provide flycatcher habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <P>The confluence of Tonto Creek and the Salt River (29.1 km, 18 mi) that make up Roosevelt Lake below the elevation of 2151 feet, occurs within the planning area of the Roosevelt Lake HCP. As a result of the conservation provided the flycatcher within the Roosevelt Lake HCP planning area through the implementation of this HCO and the management support from the Tonto National Forest, the length of Roosevelt Lake is being excluded from this critical habitat designation under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <P>Essential flycatcher habitat along Pinal Creek (5.8 km, 3.6 mi), not within the geographical area known to be occupied at the time of listing, managed by FMC, is being excluded under section 4(b)(2) of the Act due to our conservation partnership and their implementation of a management plan specific to protecting flycatcher habitat (see Exclusions section below).</P>
          <HD SOURCE="HD3">Middle Gila and San Pedro Management Unit, Arizona</HD>
          <P>The Recovery Plan describes a goal of 150 flycatcher territories in the Middle Gila and San Pedro Management Unit (Service 2002, p. 85).</P>
          <P>We identified a large flycatcher nesting population surrounding the Gila and San Pedro River confluence area within Cochise, Pima, Pinal, and Gila Counties, Arizona. Flycatchers were first detected nesting in this Management Unit in 1993, with abundant breeding sites occurring throughout this Management Unit. A high of 195 territories was detected in 2005 (Sogge and Durst 2008).</P>
          <P>We are designating as flycatcher critical habitat the lowest 126.2-km (78.4-mi) segment of the middle and lower San Pedro River across portions of Cochise, Pima, and Pinal Counties, Arizona, and a 80.6-km (50.1-mi) Gila River segment that extends from near Dripping Springs Wash downstream past the San Pedro and Gila River confluence to the Ashehurst Hayden Diversion Dam in Gila and Pinal Counties, Arizona. The Gila and San Pedro Rivers are within the geographical area known to be occupied by flycatchers at the time of listing, and contain the physical or biological features essential to the conservation of the species which may require special management considerations or protection, as described above.</P>

          <P>The San Pedro and Gila Rivers were the only two rivers identified within this Management Unit as having substantial recovery value in the Recovery Plan (Service 2002, p. 91). These river segments are anticipated to provide flycatcher habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river<PRTPAGE P="377"/>segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <P>Parcels of San Carlos Apache lands, totaling about 0.9 km (0.6 mi) and 75 ha (185 ha) occur along the lower San Pedro River between the Aravaipa Creek and Gila River confluence. Because of our partnership with the San Carlos Apache Tribe toward wildlife conservation, and their development, completion, and implementation of actions described in their Flycatcher Management Plan, we have excluded these parcels along the San Pedro River that occur on their tribal lands under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <HD SOURCE="HD3">Upper Gila Management Unit, Arizona and New Mexico</HD>
          <P>The Recovery Plan describes a goal of 325 flycatcher territories in the Upper Gila Management Unit (Service 2002, p. 85). Flycatcher territories are known throughout the Gila River in New Mexico and Arizona within this Management Unit.</P>

          <P>We identified a large flycatcher nesting population across a broad area of the upper Gila River occurring within Gila, Pinal, Graham, and Greenlee Counties, Arizona, and Grant and Hildalgo Counties, New Mexico. Flycatchers were first detected nesting in this Management Unit in 1993 (Sogge and Durst 2008). Flycatcher territories at 22 breeding sites occur throughout three separate river segments of the Gila River, with a high of 329 territories estimated following the 2007 breeding season (Durst<E T="03">et al.</E>2008, p. 12). A single breeding site along the most upstream segment in the Cliff-Gila Valley in Grant County, New Mexico, has held over 200 flycatcher territories in a single season (Sogge and Durst 2008). The Gila River is within the geographical area known to be occupied by flycatchers at the time of listing, and contains the physical or biological features essential to the conservation of the species which may require special management considerations or protection, as described above.</P>
          <P>We are designating four Gila River stream segments as flycatcher critical habitat between the Turkey Creek-Gila River confluence on the Gila National Forest, New Mexico, and the San Carlos Apache tribal Land boundary, Arizona. There are three segments we are designating as flycatcher critical habitat that occur almost entirely on the upper Gila River in southwestern New Mexico (Grant and Hildalgo Counties). Within a stretch of stream in the Cliff-Gila Valley, New Mexico, which extends into the Gila National Forest, there are checker-boarded lands that occur within the final designation and are excluded from critical habitat (U-Bar Ranch). A fourth Arizona Gila River segment occurs through the Safford Valley in Gila, Graham, and Pinal Counties.</P>
          <P>The most upstream Gila River flycatcher critical habitat segment extends for 16.9 km (10.5 mi) from the Turkey Creek-Gila River confluence on the Gila National Forest, New Mexico, downstream to the upstream boundary of the U-Bar Ranch in the Cliff-Gila Valley, New Mexico. We are excluding the U-Bar Ranch from this point downstream for approximately 26.4 km (16.4 mi) to the last U-Bar Ranch parcel, which occurs just within the Gila National Forest Boundary. Along this approximate 26.4 km (16.4 mi) stretch of the Gila River, the U-Bar Ranch contains about 13.6 km (8.6 mi) of check-boarded property which is not included in the final designation; a 12.8 km (8.0 mi) portion of stream is included within the final designation. The second Gila River segment extends from the downstream boundary of the U-Bar Ranch within the Gila National Forest for 6.0 km (3.7 mi) to the upstream end of the middle Gila Box, New Mexico. The third segment begins at the Gila River gauging station above the Town of Red Rock in Grant County, New Mexico, at the downstream end of the middle Gila Box and extends for 65.3 km (40.6 mi) into Hidalgo County, New Mexico, and just across the New Mexico-Arizona State line through the town of Duncan in Greenlee County, Arizona. A fourth Gila River segment extends for 76.4 km (47.5 mi) from the upper end of Earven Flat in Arizona, above the Town of Safford, through the Safford Valley to the San Carlos Apache tribal boundary in Gila, Graham, and Pinal Counties, Arizona.</P>
          <P>These Gila River segments were identified in the Recovery Plan as areas with substantial recovery value (Service 2002, p. 91) and are anticipated to provide flycatcher habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <P>Because of our partnership with the San Carlos Apache Tribe and their development, completion, and implementation of actions described in their Flycatcher Management Plan, we have excluded the 31.3 km (19.5 mi) portion of the Gila River (upstream of the San Carlos Reservoir) that occurs within their tribal lands under section 4(b)(2) of the Act (see Exclusions section below). Also because of our tribal trust responsibilities with both the San Carlos Apache Tribe and Gila River Indian Community (GRIC), we are excluding the Federal land that occurs along the Gila River (26.8 km, 16.6 mi) within the conservation space of San Carlos Reservoir under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <P>Because of the development, completion, and implementation of actions described in FMC's Flycatcher Management Plan for the U-Bar Ranch in the Cliff-Gila Valley, New Mexico, we are excluding the 13.8 km (8.6 mi) portions of the Gila River occurring on these lands under section 4(b)(2) of the Act due to our conservation partnership and their implementation of a management plan specific to protecting flycatcher habitat (see Exclusions section below).</P>
          <HD SOURCE="HD3">Santa Cruz Management Unit, Arizona</HD>
          <P>The Recovery Plan describes a goal of 25 flycatcher territories in the Santa Cruz Management Unit (Service 2002, p. 84).</P>
          <P>There were no large flycatcher nesting populations in the Santa Cruz Management Unit to help guide us toward a critical habitat area, and no areas were known to be occupied at the time of listing. Therefore, to identify the areas that would contribute to meeting recovery goals for this Management Unit, we used information based on known flycatcher territories and breeding sites, guidance from the Recovery Plan, and knowledge about stream habitat to determine critical habitat segments that may be essential for flycatcher conservation. A single flycatcher territory was detected on Cienega Creek in 2001 (Sogge and Durst 2008) and Empire Gulch in 2011 (a tributary to Cienega Creek). No flycatcher territories have been detected on the Santa Cruz River.</P>

          <P>Within Pima and Santa Cruz Counties, Arizona, we are designating flycatcher critical habitat along Cienega Creek, Empire Gulch, and the Santa Cruz River. Within Las Cienegas National Conservation Area in Pima County, we are designating a 17.9-km (11.1-mi) segment of Cienega Creek and two segments of Empire Gulch; an isolated 0.4-km (0.3-mi) upper segment of Empire Gulch and a second 1.3-km (0.8-mi) lower segment of Empire Gulch that connects to Cienega Creek. Along<PRTPAGE P="378"/>the Santa Cruz River, we are designating a 26.7-km (16.6-mi) segment from the Nogales Waste Water Treatment Plant to Chavez Siding Road in Santa Cruz County, Arizona. These segments were not within the geographical area known to be occupied at the time of listing; however, they are essential to flycatcher conservation because they may be able to develop and sustain flycatcher habitat and territories to help meet recovery goals in this Management Unit.</P>
          <P>The Santa Cruz River and Cienega Creek segments were identified in the Recovery Plan as areas with substantial recovery value (Service 2002, p. 91), while the adjacent Empire Gulch was only recently detected as having a flycatcher territory. These segments are anticipated to provide flycatcher habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <HD SOURCE="HD3">San Francisco Management Unit, Arizona and New Mexico</HD>
          <P>The Recovery Plan describes a goal of 25 flycatcher territories in the San Francisco Management Unit (Service 2002, p. 84). Small numbers of flycatcher territories are known to occur along the San Francisco River in this Management Unit in both Arizona and New Mexico.</P>
          <P>There were no known large flycatcher nesting populations in the San Francisco Management Unit to help guide us toward a critical habitat area. Therefore, to identify the areas that would contribute to meeting recovery goals for this Management Unit, we used information based on known flycatcher territories and breeding sites, guidance from the Recovery Plan, and knowledge about stream habitat to determine critical habitat segments for flycatcher conservation (see below). Four flycatcher breeding sites have been detected on these river segments, with the first territories found in 1993 (Sogge and Durst 2008). The number of territories detected has fluctuated annually between one and seven from 1993 to 2007 (Sogge and Durst 2008). The San Francisco River is within the geographical area known to be occupied by flycatchers at the time of listing, and contains the physical or biological features essential for the conservation of the species which may require special management considerations or protection, as described above.</P>
          <P>We are designating as flycatcher critical habitat four segments of the San Francisco River in Arizona and New Mexico. We are designating two segments of the San Francisco River between the Town of Alpine, Arizona, and Centerfire Creek in Catron County, New Mexico, that are separated by a 2.7 km (1.7 mi) area at Luna Lake, Arizona. These two segments extend for 11.3-km (7.0-mi) west of Luna Lake in Apache County, Arizona, and beginning just downstream of Luna Lake, for 28.2-km (17.5.mi) in Apache County and Catron County. A third 36.4-km (22.6-mi) segment extends from the Deep Creek confluence to San Francisco Hot Springs, in Catron County, New Mexico. The fourth, 36.7-km (22.8-mi) segment extends from the Arizona and New Mexico State line border to the western boundary of the Apache-Sitgreaves National Forest, in Apache County, Arizona.</P>
          <P>These San Francisco River segments were identified in the Recovery Plan as having substantial recovery value (Service 2002, pp. 90-91). These San Francisco River segments are anticipated to provide flycatcher habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <HD SOURCE="HD3">Hassayampa and Agua Fria Management Unit, Arizona</HD>
          <P>The Recovery Plan describes a goal of 25 flycatcher territories in the Hassayampa and Agua Fria Management Unit (Service 2002, p. 84).</P>
          <P>There were no large flycatcher nesting populations in the Hassayampa and Agua Fria Management Unit to help guide us toward a critical habitat area. Therefore, to identify the areas that would contribute to meeting recovery goals for this Management Unit, we used information based on known flycatcher territories and breeding sites, guidance from the Recovery Plan, and knowledge about stream habitat to determine critical habitat segments that may be essential for flycatcher conservation (see below). A single breeding site along the Hassayampa River was detected within this Management Unit, with the number of territories ranging from one and three (Sogge and Durst 2008).</P>
          <P>We are designating as flycatcher critical habitat a 7.4-km (4.6-mi) segment of the Hassayampa River that occurs south of the Highway 60 Bridge in the Town of Wickenburg in Maricopa County, Arizona. This segment was not within the geographical area known to be occupied at the time of listing; however, it is essential for flycatcher conservation because it will help meet recovery goals in this Management Unit.</P>
          <P>The Hassayampa River was identified in the Recovery Plan as having substantial recovery value (Service 2002, p. 91). This river segment is anticipated to provide flycatcher habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, this segment and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <P>The 8.7 km (5.4 mi) Gila River segment that occurs within the Tres Rios Safe Harbor Agreement Area will be excluded under section 4(b)(2) of the Act (see Exclusions section below) as a result of the habitat development and management by the City of Phoenix associated with their Safe Harbor Agreement with the Service.</P>
          <HD SOURCE="HD3">Rio Grande Recovery Unit</HD>
          <P>This Recovery Unit primarily includes the Rio Grande watershed from its headwaters in southern Colorado downstream to the Pecos River confluence in Texas. Other areas and drainages that occur within this Recovery Unit include the Rio Grande in Texas and Pecos watershed in New Mexico and Texas. No recovery goals were established for Management Units in those areas, so no critical habitat is being designated in those areas.</P>

          <P>There have been large increases in the number of estimated and known territories within the Rio Grande Recovery Unit, primarily due to increasing population numbers within the Middle Rio Grande Management Unit. In 2002, a total of 197 territories (17 percent of the rangewide total) were estimated to occur within the Recovery Unit, primarily occurring along the mainstem Rio Grande (Sogge<E T="03">et al.</E>2003). At the end of the 2007 breeding season, the Recovery Unit had increased to an estimated 230 territories (17 percent of the rangewide total), primarily due to territory increases in the Middle Rio Grande (Durst<E T="03">et al.</E>
            <PRTPAGE P="379"/>2008, p.13). In the subsequent years, the number of known territories has continued to increase within the Middle Rio Grande Management Unit with approximately 350 territories detected in 2009, with most territories detected within the San Marcial reach near Elephant Butte Reservoir (Moore and Ahlers 2010, p. 1).</P>

          <P>Both the San Luis Valley Management Unit in southern Colorado and Middle Rio Grande Management Unit in New Mexico have surpassed their numerical territory goals. A total of 50 territories are needed in the San Luis Valley Management Unit and 56 territories were estimated to occur in 2007 (Durst<E T="03">et al.</E>2008, p. 13). In the Middle Rio Grande Management Unit, the numerical goal of 100 territories has been surpassed with about 350 territories detected in 2009 (Moore and Ahlers 2010, p.1).</P>
          <P>Most sites are in habitats dominated by native plants, while habitat dominated by exotic plants include primarily tamarisk or Russian olive (Service 2002, p. 65). In 2001, 43 of the 56 nests (77 percent) that were described in the middle and lower Rio Grande in New Mexico, used tamarisk as the nest substrate (Service 2002, p. 65). In 2001, government-managed lands accounted for 63 percent of the territories in this unit; tribal lands supported an additional 23 percent (Service 2002). While the number of territories has increased, the known distribution of sites is similar. As a result, we expect a larger proportion of territories to occur on government-managed lands in the Middle Rio Grande Management Unit.</P>
          <P>This Recovery Unit contains the San Luis Valley, Upper Rio Grande, Middle Rio Grande, and Lower Rio Grande Management Units.</P>
          <P>Based upon our occupancy criteria (see above), within the Rio Grande Recovery Unit, the Rio Grande (1993), Rio Grande del Rancho (1993), and Coyote Creek (1993) are streams that were within the geographical area known to be occupied at the time of listing (1991-1994) (Sogge and Durst 2008) where we are designating critical habitat segments. These streams have the physical or biological features of critical habitat that may require special management considerations or protection.</P>

          <P>At the time of listing, only specific sites on the Rio Grande within the Upper, Middle, and Lower Rio Grande Management Units were known to be specifically occupied by nesting birds, but based upon our criteria and the wide-ranging nature of this neotropical migrant, the Rio Grande within the San Luis Valley Management Unit is also considered occupied at the time of listing. Below we identify that each listed item described in our<E T="03">Special Management Considerations or Protection</E>section (see above) applies to the streams described in each Management Unit within the Rio Grande Recovery Unit.</P>
          <HD SOURCE="HD3">San Luis Valley Management Unit, Colorado</HD>
          <P>The Recovery Plan describes a goal of 50 flycatcher territories in the San Luis Valley Management Unit (Service 2002, p. 85).</P>
          <P>We identified a large flycatcher nesting population in the San Luis Valley in Costilla, Conejos, Alamosa, and Rio Grande Counties, Colorado. Flycatchers were first detected nesting in this Management Unit in 1997, and a high of 71 territories were detected along the Rio Grande and Conejos River in 2003 (Sogge and Durst 2008).</P>
          <P>We are designating as flycatcher critical habitat two segments of the Rio Grande, which are within close proximity to each other, within the San Luis Valley. The northern-most segment on the Rio Grande is an 18.4-km (11.4-mi) segment constituting 3,377 ha (8345 ac) within the Alamosa NWR. The more southerly segment is on BLM land (on the west side of the Rio Grande) and is 20.4 km (12.7 mi) long constituting 182.8 ha (451.7 ac). The Rio Grande is within the geographical area known to be occupied by flycatchers at the time of listing, and contains the physical or biological features essential for the conservation of the species that may require special management considerations or protection, as described above.</P>
          <P>We are also designating as flycatcher critical habitat three segments in close proximity on the Conejos River that, in total, are 4.7-km (2.9-mi) long constituting 502.9 ha (1242.7 ac). The Conejos River was not within the geographical area known to be occupied at the time of listing; however, it is essential for flycatcher conservation because it will help meet recovery goals in this Management Unit.</P>
          <P>The Rio Grande and the Conejos River segments were identified within this Management Unit as having substantial recovery value in the Recovery Plan (Service 2002, p. 92). These river segments are anticipated to provide flycatcher habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <P>Large sections of non-federal lands occur along both the Rio Grande and Conejos River within the conservation planning area established by the San Luis Valley Partnership and within their HCP; as a result, we excluded 184.5 km (114.7 mi) constituting 27,566.6 ha (68,118.2 ac) of habitat along the Conejos River and Rio Grande within this conservation and planning area under section 4(b)(2) of the Act (see Exclusions).</P>
          <HD SOURCE="HD3">Upper Rio Grande Management Unit, New Mexico</HD>
          <P>The Recovery Plan describes a goal of 75 flycatcher territories in the Upper Rio Grande Management Unit (Service 2002, p. 85).</P>
          <P>We identified a large flycatcher nesting population on the upper Rio Grande in Taos, Santa Fe, and Mora Counties, New Mexico. Flycatchers were first detected nesting in this Management Unit in 1993, and a high of 39 territories were detected in 2000 along the Rio Grande, Rio Grande Del Rancho, and Coyote Creek (Sogge and Durst 2008). These segments are within the geographical area known to be occupied by flycatchers at the time of listing, and contain the physical or biological features essential for the conservation of the species which may require special management considerations or protection. Flycatcher territories were recently detected on the Rio Fernando, which was not within the geographical area known to be occupied by flycatchers at the time of listing, but is considered essential for conservation.</P>

          <P>We are designating as flycatcher critical habitat a collection of Upper Rio Grande Management Unit river segments along the Rio Grande, Rio Grande del Rancho, Coyote Creek, and Rio Fernando. We are designating a 46.8-km (29.1-mi) Rio Grande segment that extends from the Taos Junction Bridge (State Route 520) downstream to the northern boundary of the San Juan (Ohkay Ohwingeh) Pueblo, and a 1.1 km (0.4 mi) segment of the Rio Grande between the San Juan (Ohkay Ohwingeh) and Santa Clara Pueblos. We are also designating as flycatcher critical habitat an 11.9-km (7.4-mi) segment of the Rio Grande del Rancho from Sarco Canyon downstream to the Arroyo Miranda confluence, and a 10.7-km (6.6-mi) segment of Coyote Creek from above Coyote Creek State Park downstream to the second bridge on State Route 518, upstream from Los Cocas. Additionally,<PRTPAGE P="380"/>we are designating a 0.4-km (0.2-mi) segment of the Rio Fernando that is located about 3.2 km (2.0 mi) upstream from the Rio Lucero confluence.</P>
          <P>Rio Grande, Rio Grande del Rancho, and Coyote Creek were identified within this Management Unit as having substantial recovery value in the Recovery Plan (Service 2002, p. 92). These three segments, along with the essential Rio Fernando segment, are anticipated to provide flycatcher habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, these river segments and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <P>Due to the our partnership with the Santa Clara, San Juan, and San Ildefonso Pueblos and their conservation efforts on the Rio Grande, we are excluding these pueblos from the final flycatcher critical habitat designation under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <HD SOURCE="HD3">Middle Rio Grande Management Unit, New Mexico</HD>
          <P>The Recovery Plan describes a goal of 100 flycatcher territories in the Middle Rio Grande Management Unit (Service 2002, p. 85).</P>
          <P>We identified a large flycatcher nesting population on the middle Rio Grande in Valencia and Socorro Counties, New Mexico. Flycatcher territories were first detected in this Management Unit in 1993. In 2007, a high of 230 territories were detected (Sogge and Durst 2008), and since then the population has grown to about 350 territories (Moore and Ahlers 2010, p. 1). The Rio Grande is within the geographical area known to be occupied by flycatchers at the time of listing, and contains the physical or biological features essential for the conservation of the species which may require special management considerations or protection, as described above.</P>
          <P>We are designating as critical habitat a 180.4-km (112.1-mi) segment of the Rio Grande that extends from below Isleta Pueblo and the Bernalillo and Valencia County line downstream past Bosque del Apache and Sevilleta NWRs and into the upper part of Elephant Butte Reservoir ending in Socorro County about 3.2 km (2.0 mi) north of the Sierra County line, New Mexico (about 14.4 km, 9.0 mi of the upper part of Elephant Butte Reservoir, downstream of the power-line crossing is included within the designation).</P>
          <P>This Rio Grande segment was identified as having substantial recovery value in the Recovery Plan (Service 2002, p. 92). This segment of the Rio Grande is anticipated to provide flycatcher habitat for metapopulation stability, gene connectivity through this portion of the flycatcher's range, protection against catastrophic population loss, and population growth and colonization potential. As a result, this river segment and associated flycatcher habitat are anticipated to support the strategy, rationale, and science of flycatcher conservation in order to meet territory and habitat-related recovery goals.</P>
          <HD SOURCE="HD3">Lower Rio Grande Management Unit, New Mexico</HD>
          <P>The Recovery Plan describes a goal of 25 flycatcher territories in the Lower Rio Grande Management Unit (Service 2002, p. 84).</P>
          <P>There were no large flycatcher nesting populations in the lower Rio Grande Management Unit to help guide us toward a critical habitat area. Therefore, to identify the areas that would contribute to meeting recovery goals for this Management Unit, we used information based on known flycatcher territories and breeding sites, guidance from the Recovery Plan, and knowledge about stream habitat to determine critical habitat segments that may be essential for flycatcher conservation (see below). Between 1993 and 2007, three breeding sites had been detected along the lower Rio Grande in Sierra and Dona Ana Counties, New Mexico, with the first territories found in 1993 (Sogge and Durst 2008). During this time period the number of known flycatcher territories detected annually fluctuated between zero and eight (Sogge and Durst 2008). However, in 2011 the number of territories detected within the Lower Rio Grande Management Unit increased due to improved survey effort (Service 2012, p. 32) and in 2012 is believed to have reached 25 territories (Hill, D. 2012, pers. comm.). The Rio Grande is within the geographical area known to be occupied by flycatchers at the time of listing, and contains the physical or biological features essential for the conservation of the species which may require special management considerations or protection, as described above.</P>
          <P>The lower Rio Grande, from Caballo Dam to Leasburg Dam (74.2 km, 46.1 mi), was also proposed as critical habitat in this management unit. However, as a result of the commitment to comprehensively manage flycatcher habitat, through development and protection of habitat and water transaction agreements, we are excluding this segment from the final designation of revised flycatcher critical habitat under section 4(b)(2) of the Act (see Exclusions section below).</P>
          <HD SOURCE="HD1">Effects of Critical Habitat Designation</HD>
          <HD SOURCE="HD2">Section 7 Consultation</HD>
          <P>Section 7(a)(2) of the Act requires Federal agencies, including the Service, to ensure that any action they fund, authorize, or carry out is not likely to jeopardize the continued existence of any endangered species or threatened species or result in the destruction or adverse modification of designated critical habitat of such species. In addition, section 7(a)(4) of the Act requires Federal agencies to confer with the Service on any agency action which is likely to jeopardize the continued existence of any species proposed to be listed under the Act or result in the destruction or adverse modification of proposed critical habitat.</P>

          <P>Decisions by the 5th and 9th Circuit Courts of Appeals have invalidated our regulatory definition of “destruction or adverse modification” (50 CFR 402.02) (see<E T="03">Gifford Pinchot Task Force</E>v.<E T="03">U.S. Fish and Wildlife Service,</E>378 F. 3d 1059 (9th Cir. 2004) and<E T="03">Sierra Club</E>v.<E T="03">U.S. Fish and Wildlife Service et al.,</E>245 F.3d 434, 442 (5th Cir. 2001)), and we do not rely on this regulatory definition when analyzing whether an action is likely to destroy or adversely modify critical habitat. Under the statutory provisions of the Act, we determine destruction or adverse modification on the basis of whether, with implementation of the proposed Federal action, the affected critical habitat would continue to serve its intended conservation role for the species.</P>

          <P>If a Federal action may affect a listed species or its critical habitat, the responsible Federal agency (action agency) must enter into consultation with us. Examples of actions that are subject to the section 7 consultation process are actions on State, tribal, local, or private lands that require a Federal permit (such as a permit from the Corps under section 404 of the Clean Water Act (33 U.S.C. 1251<E T="03">et seq.</E>) or a permit from the Service under section 10 of the Act) or that involve some other Federal action (such as funding from the Federal Highway Administration, Federal Aviation Administration, or the Federal Emergency Management Agency). Federal actions not affecting listed species or critical habitat, and actions on State, tribal, local, or private lands that are not federally funded or<PRTPAGE P="381"/>authorized, do not require section 7 consultation.</P>
          <P>As a result of section 7 consultation, we document compliance with the requirements of section 7(a)(2) through our issuance of:</P>
          <P>(1) A concurrence letter for Federal actions that may affect, but are not likely to adversely affect, listed species or critical habitat; or</P>
          <P>(2) A biological opinion for Federal actions that may affect and are likely to adversely affect, listed species or critical habitat.</P>
          <P>When we issue a biological opinion concluding that a project is likely to jeopardize the continued existence of a listed species and/or destroy or adversely modify critical habitat, we provide reasonable and prudent alternatives to the project, if any are identifiable, that would avoid the likelihood of jeopardy and/or destruction or adverse modification of critical habitat. We define “reasonable and prudent alternatives” (at 50 CFR 402.02) as alternative actions identified during consultation that:</P>
          <P>(1) Can be implemented in a manner consistent with the intended purpose of the action,</P>
          <P>(2) Can be implemented consistent with the scope of the Federal agency's legal authority and jurisdiction,</P>
          <P>(3) Are economically and technologically feasible, and</P>
          <P>(4) Would, in the Director's opinion, avoid the likelihood of jeopardizing the continued existence of the listed species and/or avoid the likelihood of destroying or adversely modifying critical habitat.</P>
          <P>Reasonable and prudent alternatives can vary from slight project modifications to extensive redesign or relocation of the project. Costs associated with implementing a reasonable and prudent alternative are similarly variable.</P>
          <P>Regulations at 50 CFR 402.16 require Federal agencies to reinitiate consultation on previously reviewed actions in instances where we have listed a new species or subsequently designated critical habitat that may be affected and the Federal agency has retained discretionary involvement or control over the action (or the agency's discretionary involvement or control is authorized by law). Consequently, Federal agencies sometimes may need to request reinitiation of consultation with us on actions for which formal consultation has been completed, if those actions with discretionary involvement or control may affect subsequently listed species or designated critical habitat.</P>
          <HD SOURCE="HD3">Application of the “Adverse Modification” Standard</HD>
          <P>The key factor related to the adverse modification determination is whether, with implementation of the proposed Federal action, the affected critical habitat would continue to serve its intended conservation role for the species. Activities that may destroy or adversely modify critical habitat are those that alter the physical or biological features to an extent that appreciably reduces the conservation value of critical habitat for the flycatcher. As discussed above, the role of critical habitat is to support life-history needs of the species and provide for the conservation of the species.</P>
          <P>Section 4(b)(8) of the Act requires us to briefly evaluate and describe, in any proposed or final regulation that designates critical habitat, activities involving a Federal action that may destroy or adversely modify such habitat, or that may be affected by such designation.</P>
          <P>Activities that may affect critical habitat, when carried out, funded, or authorized by a Federal agency, should result in consultation for the flycatcher. These activities include, but are not limited to:</P>
          <P>(1) Actions that would remove, thin, or destroy riparian flycatcher habitat, without implementation of an effective riparian habitat management plan resulting in the development of riparian vegetation of equal or better flycatcher quality in abundance and extent. Such activities could include, but are not limited to, removing, thinning, or destroying riparian vegetation by mechanical (mowing, cutting), chemical (herbicides or burning), or biological (grazing, biocontrol agents) means. These activities could reduce the amount or extent of riparian habitat needed by flycatchers for sheltering, feeding, breeding, and migrating.</P>
          <P>(2) Actions that would appreciably diminish habitat value or quality through direct or indirect effects. Such activities could include, but are not limited to, degradation of watershed and soil characteristics; diminishing river surface and subsurface flow; negatively altering river flow regimes; introduction of exotic plants, animals, or insects; or habitat fragmentation from recreation activities. These activities could reduce or fragment the amount or extent of riparian habitat needed by flycatchers for sheltering, feeding, breeding, and migrating.</P>
          <P>(3) Actions that would negatively alter the surface or subsurface river flow. Such activities could include, but are not limited to, water diversion or impoundment, groundwater pumping, dam construction and operation, or any other activity which negatively changes the frequency, magnitude, duration, timing, or abundance of surface flow (and also subsurface groundwater elevation). These activities could permanently eliminate available riparian habitat and food availability or degrade the general suitability, quality, structure, abundance, longevity, and vigor of riparian vegetation and microhabitat components necessary for nesting, migrating, food, cover, and shelter.</P>
          <P>(4) Actions that permanently destroy or alter flycatcher habitat. Such activities could include, but are not limited to, discharge of fill material, draining, ditching, tiling, pond construction, and stream channelization (due to roads, construction of bridges, impoundments, discharge pipes, stormwater detention basins, dikes, levees, and others). These activities could permanently eliminate available riparian habitat and food availability or degrade the general suitability, quality, structure, abundance, longevity, and vigor of riparian vegetation and microhabitat components necessary for nesting, migrating, food, cover, and shelter.</P>
          <P>(5) Actions that result in alteration of flycatcher habitat from improper livestock or ungulate management. Such activities could include, but are not limited to, unrestricted ungulate access and use of riparian vegetation; excessive ungulate use of riparian vegetation during the non-growing season (i.e., leaf drop to bud break); overuse of riparian habitat and upland vegetation due to insufficient herbaceous vegetation (low-growing, non-woody plants) available to livestock; and improper herding, water development, or other livestock management actions. These activities can reduce the volume and composition of riparian vegetation, prevent regeneration of riparian plant species, physically disturb nests, alter floodplain dynamics, facilitate brood parasitism (laying eggs in flycatcher nests) by brown-headed cowbirds, alter watershed and soil characteristics, alter stream shape, and facilitate the growth of flammable exotic plant species.</P>
          <HD SOURCE="HD1">Exemptions</HD>
          <HD SOURCE="HD2">Application of Section 4(a)(3) of the Act</HD>

          <P>The Sikes Act Improvement Act of 1997 (Sikes Act) (16 U.S.C. 670a) required each military installation that includes land and water suitable for the conservation and management of natural resources to complete an INRMP by November 17, 2001. An INRMP<PRTPAGE P="382"/>integrates implementation of the military mission of the installation with stewardship of the natural resources found on the base. Each INRMP includes:</P>
          <P>(1) An assessment of the ecological needs on the installation, including the need to provide for the conservation of listed species;</P>
          <P>(2) A statement of goals and priorities;</P>
          <P>(3) A detailed description of management actions to be implemented to provide for these ecological needs; and</P>
          <P>(4) A monitoring and adaptive management plan.</P>
          <P>Among other things, each INRMP must, to the extent appropriate and applicable, provide for fish and wildlife management; fish and wildlife habitat enhancement or modification; wetland protection, enhancement, and restoration where necessary to support fish and wildlife; and enforcement of applicable natural resource laws.</P>
          <P>The National Defense Authorization Act for Fiscal Year 2004 (Pub. L. 108-136) amended the Act to limit areas eligible for designation as critical habitat. Specifically, section 4(a)(3)(B)(i) of the Act (16 U.S.C. 1533(a)(3)(B)(i)) now provides: “The Secretary shall not designate as critical habitat any lands or other geographical areas owned or controlled by the Department of Defense, or designated for its use, that are subject to an integrated natural resources management plan prepared under section 101 of the Sikes Act (16 U.S.C. 670a), if the Secretary determines in writing that such plan provides a benefit to the species for which critical habitat is proposed for designation.”</P>
          <P>We consult with the military on the development and implementation of INRMPs for installations with listed species. We analyzed INRMPs developed by military installations located within the range of the critical habitat designation for the flycatcher to determine if they meet the criteria for exemption from critical habitat under section 4(a)(3) of the Act. The following areas are Department of Defense lands with completed, Service-approved INRMPs within the proposed revised critical habitat designation.</P>
          <GPOTABLE CDEF="xs56,r125,r35,r35" COLS="4" OPTS="L2,i1">
            <TTITLE>TABLE 3—Areas Exempted From Critical Habitat Under Section 4(b)(3) of the Act by Critical Habitat Unit</TTITLE>
            <BOXHD>
              <CHED H="1">Management unit</CHED>
              <CHED H="1">Specific area</CHED>
              <CHED H="1">Areas meeting the definition of critical habitat in km (mi)</CHED>
              <CHED H="1">Areas exempted in km (mi)</CHED>
            </BOXHD>
            <ROW>
              <ENT I="01">Santa Ynez</ENT>
              <ENT>Vandenberg AFB INRMP</ENT>
              <ENT>14.7 km (9.1 mi)</ENT>
              <ENT>14.7 km (9.1 mi).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">San Diego</ENT>
              <ENT>Camp Pendleton INRMP</ENT>
              <ENT>76.1 km (47.3 mi)</ENT>
              <ENT>76.1 km (47.3 mi).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">San Diego</ENT>
              <ENT>Camp Pendleton INRMP/Fallbrook Naval Base INRMP shared boundary</ENT>
              <ENT>7.5 km (4.7 mi)</ENT>
              <ENT>7.5 km (4.7 mi).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">San Diego</ENT>
              <ENT>Fallbrook Naval Base INRMP</ENT>
              <ENT>3.2 km (2.0 mi)</ENT>
              <ENT>3.2 km (2.0 mi).</ENT>
            </ROW>
          </GPOTABLE>
          <HD SOURCE="HD3">Vandenberg AFB—Santa Ynez Management Unit, California</HD>
          <P>Vandenberg AFB has an approved INRMP. The U.S. Air Force is committed to working closely with the Service and California Department of Fish and Game to continually refine the existing INRMP as part of the Sikes Act's INRMP review process. Based on our review of the INRMP for this military installation, and in accordance with section 4(a)(3)(B)(i) of the Act, we have determined that the portion of the Santa Ynez River within this installation, identified as meeting the definition of critical habitat, is subject to the INRMP, and that conservation efforts identified in this INRMP will provide a benefit to the flycatcher. Therefore, lands within this installation are exempt from critical habitat designation under section 4(a)(3)(B) of the Act. We are not including approximately 14.7 km (9.1 mi) of riparian habitat on VAFB in this revised critical habitat designation because of this exemption.</P>
          <P>VAFB completed an INRMP in 2011, which includes benefits for flycatchers through: (1) Avoidance of flycatchers and their habitat, whenever possible, in project planning; (2) scheduling of activities that may affect flycatchers outside of the peak breeding period; (3) measures for protection of riparian zones (see Wetlands and Riparian Habitats Management Plan Section in INRMP); (4) removal of exotic plant species; and (5) implementation of brown-headed cowbird management. Further, VAFB's environmental staff reviews projects and enforces existing regulations and orders that, through their implementation, avoid and minimize impacts to natural resources, including flycatchers and their habitat. In addition, VAFB's INRMP provides protection to riparian habitats for flycatchers by excluding cattle from wetlands and riparian areas through the installation and maintenance of fencing. VAFB's INRMP specifies periodic monitoring of the distribution and abundance of flycatcher populations on the base.</P>
          <P>Habitat features essential to flycatcher conservation exist on VAFB; however, designating critical habitat on this military installation may impact its mission of launching and tracking of satellites and testing and evaluating missile systems, and therefore affect the nation's military readiness. Activities occurring on VAFB are currently being conducted in a manner that minimizes impacts to flycatchers. This military installation has an approved INRMP that provides a benefit to the flycatcher, and VAFB has committed to work closely with the Service and the State wildlife agency to continually refine their existing INRMP as part of the Sikes Act's INRMP review process.</P>
          <P>Based on the above considerations, and in accordance with section 4(a)(3)(B)(i) of the Act, we have determined that conservation efforts identified in the 2011 INRMP for VAFB provide a benefit to the flycatcher and its habitat. Therefore, lands subject to the INRMP for VAFB, which includes the lands leased from the Department of Defense by other parties, are exempt from critical habitat designation under section 4(a)(3) of the Act, and we are not including approximately 14.7 km (9.1 mi) of the Santa Ynez River in this revised critical habitat designation because of this exemption.</P>
          <HD SOURCE="HD3">Marine Corps Base Camp Pendleton (MCB Camp Pendleton)—San Diego Management Unit, California</HD>

          <P>The primary mission of Marine Corps Base Camp Pendleton (MCB Camp Pendleton) is military training. It is the Marine Corps' premier amphibious training installation and its only west coast amphibious assault training center. The installation has been conducting air, sea, and ground assault training since World War II. MCB Camp Pendleton occupies over 50,586 ha (125,000 ac) of coastal southern California in the northwest corner of San Diego County. Aside from nearly 4,047 ha (10,000 ac) that is developed, most of the installation is largely undeveloped land that is used for training. MCB Camp Pendleton is<PRTPAGE P="383"/>situated between two major metropolitan areas: Los Angeles, 132 km (82 mi) to the north; and San Diego, 61 km (38 mi) to the south. Nearby urban areas include the City of Oceanside to the south, the unincorporated community of Fallbrook to the east, and the City of San Clemente to the northwest. Aside from a portion of the MCB Camp Pendleton's border that is shared with the San Mateo Canyon Wilderness Area on the Cleveland National Forest and the Naval Weapons Station Seal Beach—Detachment Fallbrook (Fallbrook Naval Weapons Station), surrounding land use is urban development, rural residential development, and agricultural farming and ranching. In addition to military training and associated activities and infrastructure to support training, portions of MCB Camp Pendleton are leased to private and public entities and agencies. The largest single leaseholder on the installation is California State Parks, which includes a 50-year real estate lease granted on September 1, 1971, for 809 ha (2,000 ac) that encompasses San Onofre State Beach. Requirements to the lessees are to manage natural resources on leased lands in support of objectives and consistent with the philosophies of MCB Camp Pendleton's INRMP (USMC 2007, pp. 2-29).</P>
          <P>The MCB Camp Pendleton INRMP was prepared to assist installation staff and users in their efforts to rehabilitate and conserve natural resources while maintaining consistency with the use of MCB Camp Pendleton to train Marines, and sets the agenda for managing natural resources on MCB Camp Pendleton (USMC 2007, p. ES-1). The INRMP also provides ecosystem-based management to preserve, improve, and enhance ecosystem integrity on the installation (USMC 2007, pp. 1-13). MCB Camp Pendleton completed its INRMP in 2001, followed by a revised and updated version in 2007 (USMC 2007), to address conservation and management recommendations within the scope of the installation's military mission, including conservation measures for flycatchers (USMC 2007, Appendix F, Section F.1, pp. F1-F5). Additionally, Marine Corps Air Station Camp Pendleton (MCAS Camp Pendleton) is fully encompassed within MCB Camp Pendleton and recognizes itself as a separate installation with its own INRMP that also provides a benefit to the flycatcher and its habitat. MCAS Camp Pendleton and its INRMP is assumed part of this discussion within the remainder of this exemption discussion for flycatcher due to its overlapping and close association with MCB Camp Pendleton and its INRMP, and both reference and inclusion of conservation described in MCB Camp Pendleton's riparian biological opinion (1-6-95-F-02; see USMC 2006, pp. 2-4 and discussion below).</P>
          <P>The MCB Camp Pendleton INRMP incorporates measures outlined in a riparian biological opinion (Service 1995), which includes addressing the installation's Riparian Ecosystem Conservation Plan (USMC 2007, Appendix C). The Riparian Ecosystem Conservation Plan was designed to maintain and enhance the biological diversity of the riparian ecosystem on MCB Camp Pendleton, including habitat areas used by flycatchers. The conceptual approach behind this conservation plan is to sustain and restore riparian ecosystem dynamics so that natural plant and animal communities on MCB Camp Pendleton are sufficiently resilient to coexist with current and future military training activities (Service 1995, Appendix 1, p. 44). Under the reasonable and prudent measures of the riparian biological opinion, implementation of the Riparian Ecosystem Conservation Plan by the Marine Corps is nondiscretionary (Service 1995, p. 31; USMC 2007, Appendix L; USMC 2006, Appendix E, pp. 63-64). Areas or habitat containing features essential to the conservation of flycatchers addressed by the conservation plan, the Riparian BO, or MCB Camp Pendleton's INRMP include the Santa Margarita River and portions of the following creeks: Cristianitos, San Mateo, San Onofre, Los Flores, Las Pulgas, Fallbrook, Pilgrim, and DeLuz (70 FR 60886; October 19, 2005).</P>
          <P>As described in Appendix F of the MCB Camp Pendleton INRMP (USMC 2007, pp. F-58-F-67), the following management practices and conservation measures provide an indirect or direct benefit for the flycatcher:</P>
          <P>(1) Annual monitoring of population levels and distributions of the flycatcher;</P>
          <P>(2) Incorporating survey data into the GIS species distribution database to update the Environmental Operations Maps and utilize in conservation awareness and education programs;</P>
          <P>(3) Exotic vegetation control including<E T="03">Arundo donax</E>(giant reed) and<E T="03">Tamarix</E>spp. removal and control;</P>
          <P>(4) Exotic animal control (annual cowbird control activities);</P>
          <P>(5) Programmatic instructions that limit impacts to flycatcher and its habitat; and</P>
          <P>(6) Monitoring groundwater levels and basin withdrawals managed to avoid degradation and loss of habitat quality.</P>
          <P>These measures are established or ongoing aspects of existing programs, Base directives (such as the Riparian Ecosystem Conservation Plan), or measures that are being implemented as a result of previous consultations. MCB Camp Pendleton implements installation directives to avoid and minimize adverse effects to the flycatcher, such as:</P>
          <P>(1) Assuring that aircraft operations shall not be conducted lower than an altitude of 300 ft (91 m) over occupied riparian areas, to the maximum extent practical;</P>
          <P>(2) Limiting vehicle operations to existing roads in riparian areas;</P>
          <P>(3) Requiring helicopters to operate in excess of 61 m (200 ft) above ground level over riparian areas except during take-off or landing, from March 15 to August 31;</P>
          <P>(4) Restricting ground troops movement in riparian areas to existing crossings, trails, and roads; and</P>
          <P>(5) Prohibiting bivouacking in riparian areas.</P>
          <P>Current environmental regulations and restrictions apply to all endangered and threatened species on the installation (including flycatcher) and are provided to all users of ranges and training areas to guide activities and protect the species and its habitat. First, specific conservation measures are applied to flycatcher and its habitat (as outlined above). Second, MCB Camp Pendleton's environmental security staff reviews projects and enforces existing regulations and orders that, through their implementation, avoid and minimize impacts to natural resources, including the flycatcher and its habitat. Third, MCB Camp Pendleton provides training to personnel on environmental awareness for sensitive resources on the base, including the flycatcher and its habitat. As a result of these regulations and restrictions, activities occurring on MCB Camp Pendleton are currently conducted in a manner that minimizes impacts to flycatcher habitat.</P>

          <P>Based on the above considerations, and in accordance with section 4(a)(3)(B)(i) of the Act, we have determined that conservation efforts identified in the 2007<E T="03"/>INRMP for MCB Camp Pendleton (and MCAS Camp Pendleton INRMP as outlined above) will provide a benefit to the flycatcher and riparian habitat on MCB Camp Pendleton. Therefore, lands within this installation are exempt from critical habitat designation under section 4(a)(3) of the Act. We are not including approximately 76.1 km (47.3 mi) of habitat on MCB Camp Pendleton and an<PRTPAGE P="384"/>additional 7.5 km (4.7 mi) area shared with the adjacent Naval Weapons Station Seal Beach—Detachment Fallbrook (Fallbrook Naval Weapons Station) in this revised critical habitat designation because of this exemption.</P>
          <P>Naval Weapons Station Seal Beach-Detachment Fallbrook (Fallbrook Naval Weapons Station)—San Diego Management Unit, California</P>
          <P>Fallbrook Naval Weapons is the primary west coast supply point of ordnance for the U.S. Marine Corps and the large deck amphibious assault ships of the Pacific Fleet. Fallbrook Naval Weapons Station also has the only west coast maintenance facility for air-launched missiles for the Pacific Fleet. The installation encompasses approximately 3,582 ha (8,852 ac) and is located within the southern foothills of the Santa Ana Mountains of northern San Diego County, adjacent to the unincorporated community of Fallbrook, California. It is bounded to the north, west, and much of the south by MCB Camp Pendleton, with the Santa Margarita River forming the common border on the north between the two properties. Other than training lands on MCB Camp Pendleton, surrounding land use includes semi-rural agricultural lands that include plant nurseries, avocado and citrus groves, vineyards, and limited urban development.</P>
          <P>In the previous final critical habitat designation for flycatcher, we exempted Fallbrook Naval Weapons Station from the designation under section 4(a)(3)(B) of the Act because it was subject to an INRMP prepared under section 101 of the Sikes Act (16 U.S.C. 670a) that we determined to provide a benefit to the flycatcher (70 FR 60886; October 19, 2005). The INRMP was prepared to assist installation staff and users in their efforts to support mission operations and accommodate increased military mission requirements for national security and emergency homeland security, while meeting all environmental compliance responsibilities. The INRMP also provides ecosystem-based management to preserve, protect, and enhance natural resources on the installation, and provides the organizational support and communication links necessary for effective planning, implementation, and administration of the installation's natural resources. The Fallbrook Naval Weapons Station completed its INRMP in 2006 (which was updated from an INRMP developed by the Naval Ordnance Center Pacific Division in 1996) to address conservation and management of its natural resources, including conservation measures for the flycatcher (Navy 2006, Chapter 3, pp. 110-112). Areas or habitat containing features essential to the conservation of flycatchers within the boundaries of Fallbrook Naval Weapons Station occur along portions of Pilgrim Creek and the Santa Margarita River.</P>

          <P>The flycatcher primarily receives protection from activities at Fallbrook Naval Weapons Station because no training occurs on the installation. The INRMP's management and conservation measures for the flycatcher consist of avoidance and minimization measures, applied to infrastructure development and maintenance to protect the flycatcher, that are part of the NEPA (42 U.S.C. 4321<E T="03">et seq.</E>) approval process (Navy 2006, Chapter 3, pp. 110-112). The flycatcher also receives indirect protection through management and conservation measures for the least Bell's vireo such as: (1) Protection of flycatcher habitat through protection of a subset of least Bell's vireo priority management areas; (2) fencing that protects priority areas from cattle grazing; (3) a Fire Management Plan that provides a higher priority protection for riparian habitat, due to the limited amount of riparian habitat on Fallbrook Naval Weapons Station, such as core areas of least Bell's vireo and flycatcher habitat; (4) consideration of prescribed burns and livestock grazing as tools for the establishment of a buffer area between riparian habitat and shrublands; (5) timing and location protections associated with prescribed burns; (6) assessment and mapping of riparian habitat to determine suitability for least Bell's vireo occupation; and (7) implementation of nonnative vegetation control measures, including removal of<E T="03">Arundo donax</E>(giant reed) (Navy 2006, pp. 3-118).</P>
          <P>Based on the above considerations, and in accordance with section 4(a)(3)(B)(i) of the Act, we have determined that conservation efforts identified in the 2006 INRMP for Fallbrook Naval Weapons Station provide a benefit to the flycatcher and riparian habitat on the installation. Therefore, lands subject to the INRMP for the Fallbrook Naval Weapons Station are exempt from critical habitat designation under section 4(a)(3) of the Act. We are not including approximately 3.2 km (2.0 mi) of habitat on Pilgrim Creek and portions of the Santa Margarita River that lie within the boundaries of the Fallbrook Naval Weapons Station in this revised critical habitat designation because of this exemption.</P>
          <HD SOURCE="HD1">Exclusions</HD>
          <HD SOURCE="HD2">Application of Section 4(b)(2) of the Act</HD>
          <P>Section 4(b)(2) of the Act states that the Secretary shall designate and make revisions to critical habitat on the basis of the best available scientific data after taking into consideration the economic impact, national security impact, and any other relevant impact of specifying any particular area as critical habitat. The Secretary may exclude an area from critical habitat if he determines that the benefits of such exclusion outweigh the benefits of specifying such area as part of the critical habitat, unless he determines, based on the best scientific data available, that the failure to designate such area as critical habitat will result in the extinction of the species. In making that determination, the statute on its face, as well as the legislative history are clear that the Secretary has broad discretion regarding which factor(s) to use and how much weight to give to any factor.</P>
          <P>In considering whether to exclude a particular area from the designation, we identify the benefits of including the area in the designation, identify the benefits of excluding the area from the designation, and evaluate whether the benefits of exclusion outweigh the benefits of inclusion. If the analysis indicates that the benefits of exclusion outweigh the benefits of inclusion, the Secretary may exercise his discretion to exclude the area only if such exclusion would not result in the extinction of the species.</P>
          <P>When identifying 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; the educational benefits of mapping essential habitat for recovery of the listed species; and any benefits that may result from a designation due to State or Federal laws that may apply to critical habitat.</P>

          <P>The principal benefit of including an area in a critical habitat designation is the requirement for Federal agencies to ensure actions they fund, authorize, or carry out are not likely to result in the destruction or adverse modification of any designated critical habitat, the regulatory standard of section 7(a)(2) of the Act under which consultation is completed. Federal agencies must also consult with us on actions that may affect a listed species to ensure their proposed actions are not likely to jeopardize the continued existence of such species. The analysis of effects to critical habitat is a separate step and different standard from that of the<PRTPAGE P="385"/>effects to the species. Therefore, the difference in outcomes of these two analyses represents the regulatory benefit of critical habitat.</P>
          <P>The two regulatory standards are different and, significantly, the factors that are reviewed under each standard are different as well. The jeopardy analysis investigates the action's impact to survival and recovery of the species with a focus on how the action affects attributes such as numbers, distribution, and reproduction of the species. On the other hand, the adverse-modification analysis investigates the action's effects to the designated habitat's contribution to recovery with a focus on the conservation role the habitat plays for the listed species. This difference in the two consultation standards and focus of review, in some instances, will lead to different conclusions. Thus, critical habitat designations may provide greater benefits to the recovery of a species than would listing alone because it will provide another and alternative focus on factors affecting listed species. Nonetheless, for many species (in at least some locations) the outcome of these analyses in terms of any required habitat protections will be similar because effects to habitat will often also result in effects to the species.</P>
          <P>When identifying 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 that provides equal to or more conservation than a critical habitat designation would provide.</P>
          <P>In the case of the flycatcher, the benefits of critical habitat include public awareness of flycatcher presence and the importance of habitat protection. Where a Federal nexus exists, the designation of critical habitat may also increase habitat protection for the flycatcher, which may, in some cases, allow the species to move into currently unoccupied areas.</P>
          <P>In practice, a Federal nexus exists primarily on Federal lands or for projects undertaken by Federal agencies or permits issued by Federal agencies. Since the flycatcher was listed in 1995, we have been consulting with Federal agencies on their effects to the flycatcher both for projects on Federal lands, and for projects on privately owned lands that had a Federal nexus to trigger consultation under section 7 of the Act. These consultations have, in some instances, resulted in comprehensive conservation planning for specific areas across the species' range (i.e., Sprague Ranch in Kern Management Unit). These plans can provide sufficient flycatcher habitat protection for recovery of the species.</P>
          <P>When we evaluate the existence of a conservation plan when considering the benefits of exclusion, we consider a variety of factors, including but not limited to, whether the plan is finalized; how it provides for the conservation of the essential physical or biological features; whether there is a reasonable expectation that the conservation management strategies and actions contained in a management plan will be implemented into the future; whether the conservation strategies in the plan are likely to be effective; and whether the plan contains a monitoring program or adaptive management to ensure that the conservation measures are effective and can be adapted in the future in response to new information.</P>
          <P>After identifying the benefits of inclusion and the benefits of exclusion, we carefully weigh the two sides to evaluate whether the benefits of exclusion outweigh those of inclusion. If our analysis indicates that the benefits of exclusion outweigh the benefits of inclusion, we then determine whether exclusion would result in extinction. If exclusion of an area from critical habitat will result in extinction, we will not exclude it from the designation.</P>
          <P>Based on the information provided by entities seeking exclusion, as well as any additional public comments we received, we evaluated whether certain lands in the proposed critical habitat were appropriate for exclusion from this final designation pursuant to section 4(b)(2) of the Act. Table 4 below provides the areas, streams, and approximate stream lengths (km, mi) of lands that meet the definition of critical habitat but are being excluded under section 4(b)(2) of the Act from the final critical habitat rule. An explanation of the basis for each exclusion is provided below.</P>
          <GPOTABLE CDEF="s60,r60,13" COLS="3" OPTS="L2,i1">

            <TTITLE>Table 4—Plan Type, Stream Segments, and Approximate Stream Length Excluded From Flycatcher Critical Habitat Under Section 4(<E T="01">b</E>)(2) of the Act by Management Unit</TTITLE>
            <BOXHD>
              <CHED H="1">Management unit and basis for exclusion</CHED>
              <CHED H="1">Streams segments excluded</CHED>
              <CHED H="1">Approximate stream length excluded in km (mi)</CHED>
            </BOXHD>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">Santa Clara Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00" RUL="s">
              <ENT I="01">Newhall Land and Farm Conservation Easement</ENT>
              <ENT>Santa Clara River</ENT>
              <ENT>4.4 (2.7)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">Santa Ana Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Western Riverside County Multiple Species HCP</ENT>
              <ENT>Santa Ana River</ENT>
              <ENT>30.0 (18.6)</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>San Timoteo Creek</ENT>
              <ENT>21.4 (13.3)</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Bautista Creek (two segments)</ENT>
              <ENT>3.1 (1.9)</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Temecula Creek (see San Diego Management Unit)</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="01">Ramona Band of Cahuilla Partnership</ENT>
              <ENT>Bautista Creek</ENT>
              <ENT>0.4 (0.3)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">San Diego Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">San Diego County Multiple Species HCP</ENT>
              <ENT>San Dieguito River</ENT>
              <ENT>9.2 (5.7)</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>San Diego River</ENT>
              <ENT>9.6 (6.0)</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Santa Ysabel Creek (upper)</ENT>
              <ENT>2.4 (1.5)</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Santa Ysabel Creek (lower)</ENT>
              <ENT>1.1 (0.7)</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Sweetwater River</ENT>
              <ENT>2.1 (1.3)</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Western Riverside County Multiple Species HCP</ENT>
              <ENT>Temecula Creek (including Vail Lake)</ENT>
              <ENT>18.7 (11.6)</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Orange County Southern Subregional HCP</ENT>
              <ENT>Cañada Gobernadora Creek</ENT>
              <ENT>4.7 (2.9)</ENT>
            </ROW>
            <ROW>
              <ENT I="01">City of Carlsbad Habitat Management Plan</ENT>
              <ENT>Agua Hedionda Creek (two segments)</ENT>
              <ENT>3.2 (2.0)<LI>2.1 (1.3)</LI>
              </ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="386"/>
              <ENT I="01">La Jolla Band of Luiseño Indians Management Plan</ENT>
              <ENT>San Luis Rey River</ENT>
              <ENT>11.6 (7.2)</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Rincon Band of Luiseño Mission Indians Management Plan</ENT>
              <ENT>San Luis Rey River</ENT>
              <ENT>4.3 (2.7)</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Pala Band of Luiseño Mission Indians Partnership</ENT>
              <ENT>San Luis Rey River 6.9 km (4.3 mi) segment plus four separate nearby parcels totaling an additional 1.4 km (0.9 mi)</ENT>
              <ENT>8.3 (5.2)</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="01">The Barona and Viejas Groups of Capitan Grande Band of Diegueno Mission Indians Partnership</ENT>
              <ENT>San Diego River</ENT>
              <ENT>0.9 (0.6)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">Owens Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00" RUL="s">
              <ENT I="01">Los Angeles Department of Water and Power Management Plan</ENT>
              <ENT>Owens River</ENT>
              <ENT>128.5 (79.8)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">Kern Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Sprague Ranch Management Plan</ENT>
              <ENT>South Fork Kern River (north side)</ENT>
              <ENT>4.0 (2.5)</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="01">Hafenfeld Ranch Management Plan</ENT>
              <ENT>South Fork Kern River (south side)</ENT>
              <ENT>0.30 (0.20)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">Salton Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00" RUL="s">
              <ENT I="01">Iipay Nation of Santa Ysabel Partnership</ENT>
              <ENT>San Felipe Creek</ENT>
              <ENT>1.6 (1.0)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">Little Colorado Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Zuni Pueblo Management Plan</ENT>
              <ENT>Rio Nutria</ENT>
              <ENT>35.8 (22.2)</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22"/>
              <ENT>Zuni River</ENT>
              <ENT>55.4 (34.4)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">Middle Colorado Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00" RUL="s">
              <ENT I="01">LCR MSCP, including Hualapai Nation</ENT>
              <ENT>Colorado River, including upper Lake Mead</ENT>
              <ENT>74.1 (46.0)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">Pahranagat Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Key Pittman State Wildlife Area Management Plan</ENT>
              <ENT>Pahranagat River (two segments)</ENT>
              <ENT>2.5 (1.6)<LI>1.4 (0.9)</LI>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="01">Overton State Wildlife Area Management Plan</ENT>
              <ENT>Muddy River</ENT>
              <ENT>3.1 (1.9)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">Bill Williams Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00" RUL="s">
              <ENT I="01">LCR MSCP</ENT>
              <ENT>Bill Williams River</ENT>
              <ENT>8.9 (5.6)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">Hoover to Parker Dam Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">LCR MSCP, including Fort Mojave and Chemehuevi Tribes</ENT>
              <ENT>Colorado River</ENT>
              <ENT>107.0 (66.4)</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="01">LCR MSCP</ENT>
              <ENT>Bill Williams River</ENT>
              <ENT>1.7 (1.0)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">Parker Dam to Southerly International Border Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00" RUL="s">
              <ENT I="01">LCR MSCP, including Colorado River Indian Tribes and Quechan (Fort Yuma) Indian Tribe</ENT>
              <ENT>Colorado River (two segments)</ENT>
              <ENT>65.0 (40.4)<LI>148.0 (92.0)</LI>
              </ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">San Juan Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Navajo Nation Management Plan</ENT>
              <ENT>San Juan River (New Mexico)</ENT>
              <ENT>3.5 (2.2)</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>San Juan River, (Utah)—43.5 km (27.0 mi) of south bank plus 8.1 km (5.1 mi) of both banks on eastern most portion of segment</ENT>
              <ENT>51.6 (32.1)</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="01">Southern Ute Tribe Management Plan</ENT>
              <ENT>Los Pinos River</ENT>
              <ENT>25.9 (16.1)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">Verde Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Salt River Project Horseshoe and Bartlett Dams HCP</ENT>
              <ENT>Verde River (Horseshoe Lake)</ENT>
              <ENT>9.6 (6.0)</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="01">Yavapai-Apache Management Plan</ENT>
              <ENT>Verde River (two segments)</ENT>
              <ENT>2.1 (1.3)<LI>0.7 (0.4)</LI>
              </ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">Roosevelt Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Salt River Project Roosevelt Lake HCP</ENT>
              <ENT>Tonto Creek (Roosevelt Lake)</ENT>
              <ENT>12.8 (7.9)</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Salt River (Roosevelt Lake)</ENT>
              <ENT>16.3 (10.1)</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="01">Freeport McMoRan Pinal Creek Management Plan</ENT>
              <ENT>Pinal Creek</ENT>
              <ENT>5.8 (3.6)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <PRTPAGE P="387"/>
              <ENT I="21">
                <E T="02">Middle Gila and San Pedro Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00" RUL="s">
              <ENT I="01">San Carlos Apache Tribal Management Plan</ENT>
              <ENT>San Pedro River (dispersed parcels)</ENT>
              <ENT>0.9 (0.6)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">Upper Gila Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">U-Bar Ranch Management Plan</ENT>
              <ENT>Gila River (dispersed parcels)</ENT>
              <ENT>13.8 (8.6)</ENT>
            </ROW>
            <ROW>
              <ENT I="01">San Carlos Apache Tribal Management Plan</ENT>
              <ENT>Gila River</ENT>
              <ENT>31.3 (19.5)</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="01">San Carlos Reservoir</ENT>
              <ENT>Gila River (San Carlos Reservoir)</ENT>
              <ENT>26.8 (16.6)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">Hassayampa and Agua Fria Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00" RUL="s">
              <ENT I="01">Tres Rios Safe Harbor Agreement</ENT>
              <ENT>Gila River</ENT>
              <ENT>8.7 (5.4)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">San Luis Valley Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">San Luis Valley Partnership</ENT>
              <ENT>Rio Grande</ENT>
              <ENT>119.5 (74.3)</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22"/>
              <ENT>Conejos River</ENT>
              <ENT>64.9 (40.4)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">Upper Rio Grande Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">San Ildefonso Pueblo Management Plan</ENT>
              <ENT>Rio Grande</ENT>
              <ENT>7.7 (4.8)</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Santa Clara Pueblo Partnership</ENT>
              <ENT>Rio Grande</ENT>
              <ENT>10.2 (6.4)</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="01">San Juan Pueblo (Ohkay Owingeh) Partnership</ENT>
              <ENT>Rio Grande</ENT>
              <ENT>9.3 (5.8)</ENT>
            </ROW>
            <ROW EXPSTB="02" RUL="s">
              <ENT I="21">
                <E T="02">Lower Rio Grande Management Unit</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00" RUL="n,s">
              <ENT I="01">Elephant Butte Irrigation District Canalization and Conservation Project</ENT>
              <ENT>Rio Grande</ENT>
              <ENT>74.2 (46.1)</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Total</ENT>
              <ENT>1,270.4 (789.6)</ENT>
            </ROW>
            <TNOTE>
              <E T="02">Note:</E>Because of the odd shape of some properties excluded, the exclusion of just the south bank of a portion of the San Juan River, and other areas adjusted described in the Summary of Changes section, this total will not, when added to the amount of designated critical habitat, equal the total overall amount of stream length proposed as critical habitat.</TNOTE>
          </GPOTABLE>
          <P>Please note that we identified some areas within our proposed rule and subsequent July 12, 2012, publication that we considered for exclusion under section 4(b)(2) of the Act, but after further analysis, we did not exclude from this flycatcher critical habitat revision. In some instances, we did not exclude an entire area we considered (Clark County HCP-Virgin River; Alamo Lake State Wildlife Area-Big Sandy, Santa Maria, and Bill Williams River; South Fork Kern River Wildlife Area-Kern River, including upper Lake Isabella; and Elephant Butte Reservoir-Rio Grande) and in others, we did not exclude a portion of the lands we identified for consideration (Overton Wildlife Area-Virgin River, and Newhall Farm and Land-Santa Clara River and Castaic Creek). Explanations for our conclusions can be found in the Summary of Comments and Recommendations section of this final rule.</P>
          <HD SOURCE="HD3">Exclusions Based on Economic Impacts</HD>
          <P>Under section 4(b)(2) of the Act, we consider the economic impacts of specifying any particular area as critical habitat. In order to consider economic impacts, we prepared a draft economic analysis of the entire proposed critical habitat designation (which include areas we were considering for exclusion) and related factors (Industrial Economics 2012, entire).</P>
          <P>The intent of the final economic analysis (FEA) is to quantify the economic impacts of all potential conservation efforts for the flycatcher; some of these costs will likely be incurred regardless of whether we designate critical habitat (baseline). The economic impact of the final 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. The incremental conservation efforts and associated impacts are those not expected to occur absent the designation of critical habitat for the species. In other words, the incremental costs are those attributable solely to the designation of critical habitat above and beyond the baseline costs; these are the costs we consider in the final designation of critical habitat. The analysis looks retrospectively at baseline impacts incurred since the species was listed, and forecasts both baseline and incremental impacts likely to occur with the designation of critical habitat. For a further description of the methodology of the analysis, see Chapter 2, “Framework for the Analysis,” of the economic analysis.</P>

          <P>The FEA also addresses how potential economic impacts are likely to be distributed, including an assessment of any local or regional impacts of habitat conservation and the potential effects of conservation activities on government agencies, private businesses, and individuals. The FEA measures lost<PRTPAGE P="388"/>economic efficiency associated with residential and commercial development and public projects and activities, such as economic impacts on water management and transportation projects, Federal lands, small entities, and the energy industry. Decision-makers can use this information to assess whether the effects of the designation might unduly burden a particular group or economic sector. The economic analysis provides estimated costs of the foreseeable potential economic impacts of the critical habitat designation for the flycatcher over the next 20 years (2012-2031), which, for most parts of the analysis, was determined to be the appropriate period for analysis. This is because limited planning information is available for most activities to forecast activity levels for projects beyond a 20-year timeframe. The economic analysis estimates impacts to water management activities, however, over a 30-year period (2012-2041).</P>
          <P>The FEA quantifies economic impacts of flycatcher conservation efforts associated with the following categories of economic activity: (1) Water management activities; (2) livestock grazing; (3) residential and related development; (4) tribal activities; (5) transportation; (6) mining and oil and gas development; and (7) recreation activities. The total potential incremental economic impacts for all of the categories in areas proposed as revised critical habitat over the next 20 years range from $11 million to $19 million ($950,000 to $1.7 million annualized), assuming a 7 percent discount rate. A very brief summary of the estimated impacts within each category is provided below. Please refer to the draft economic analysis for a comprehensive discussion of the potential impacts.</P>
          <HD SOURCE="HD3">Transportation</HD>
          <P>Our analysis suggests that transportation activities, such as road and bridge construction and maintenance, may experience the largest impacts. Transportation projects were more difficult to forecast, resulting in potential overstatement of the impacts. Our impact estimates were based on an increased level of consultation activity (and resulting project modifications for flycatcher conservation efforts) that is higher than the historical record of past activities. Transportation agencies at the Federal, State, and local level could incur costs associated with monitoring and education activities, fencing, habitat management and creation, timing restrictions, and administrative activities. Incremental impacts may reach $5.8 million over 20 years.</P>
          <HD SOURCE="HD3">Water Management</HD>
          <P>Impacts to water management activities may be the next largest of any of the affected economic activities; however, the majority of the impact of conservation efforts to protect flycatcher will occur even if critical habitat is not designated (they are baseline impacts). All but two of the major dams and reservoirs within flycatcher proposed revised critical habitat, the Hansen Dam and the Mojave Dam, are located along river segments where the species' presence is either currently addressed, or otherwise well known to project proponents and managing agencies. Associated impacts in these areas are therefore assumed to be baseline, where most conservation activities and associated costs will occur regardless of whether critical habitat is designated.</P>
          <P>Incremental impacts over the next 30 years (assuming a 7 percent discount rate) range from $1.4 million to $9.6 million. These incremental impacts include the costs of conservation efforts associated with section 7 consultations or the development of HCPs, as well as administrative efforts to consider potential adverse modification of habitat as part of future section 7 consultations.</P>
          <HD SOURCE="HD3">Livestock Grazing</HD>
          <P>Impacts to grazing activities are likely to be smaller relative to water and transportation activities, but are anticipated to affect a broader geographic area. Grazing currently occurs in nearly all of the Management Units that are included in this final critical habitat revision. As a result, some impacts may be experienced in most units. On Federal lands, reductions in grazing allotments are possible depending on the specific conditions within the unit. The estimated potential, present value incremental costs range from $2.2 million to $3.5 million over the 20-year time period of the analysis. Impacts include the administrative costs of consultation with the Service, the lost value of grazing permits associated with reductions in authorized Animal Unit-Months, costs of constructing and maintaining fencing, and costs of cowbird trapping.</P>
          <HD SOURCE="HD3">Residential and Commercial Development</HD>
          <P>Residential and related development activities are likely to be smaller in magnitude than grazing impacts; however estimated impacts are concentrated over a smaller geographic area. Nearly all impacts to development activities are estimated to occur in the California Management Units. Areas likely to see the greatest development pressure include Santa Barbara, Ventura, Los Angeles, Riverside, San Bernardino, and San Diego Counties, California, and Mohave County, Arizona.</P>
          <P>Because the revised critical habitat is located within the 100-year floodplain, the Federal Emergency Management Agency will regulate real estate development in any critical habitat we eventually designate. As a result, additional restrictions may be imposed by individual or local jurisdictions. The restrictions or regulations may require flood control facilities or other special engineering, often making development in floodways impractical and prohibitively expensive. Due to existing development restrictions, lands within critical habitat that can be feasibly developed will be limited to areas where real estate demand is high enough to justify the costs associated with developing the floodplain.</P>

          <P>Incremental impacts to residential development are estimated at $810,000 over 20 years. These are related to reduced land value associated with the need to set aside land on-site for the flycatcher; the need to implement additional project modifications, such as cowbird trapping, fencing, monitoring, and habitat management; time delays; and administrative costs. Because of the availability of alternative lands that are not designated as critical habitat in these regions, these costs are likely to be borne by existing landowners in the form of reduced value for their existing properties. The estimated impacts would be felt immediately, in 2012, upon the effective date of this final rule (see<E T="02">DATES</E>), and reflect the change in the future, productive use of the properties.</P>
          <HD SOURCE="HD3">Tribal Activities</HD>

          <P>Incremental impacts to tribal activities of approximately $660,000 are estimated to be associated with administrative impacts over the 20-year time frame of the analysis. However, tribal concerns focus on the potential impact that the designation could have on their ability to make use of natural resources, including water rights, on their sovereign lands. The absence of some cost information related to potential impacts of flycatcher critical habitat on tribal lands results in a probable underestimate of future costs to tribal entities. Lands belonging to 19 tribes included within the boundaries of proposed revised critical habitat under consideration for exclusion from the final designation, are subsequently<PRTPAGE P="389"/>excluded under section 4(b)(2) of the Act (see Exclusions section).</P>
          <HD SOURCE="HD3">Mining, and Oil and Gas Development</HD>
          <P>In 2005, potential impacts to oil and gas development were not identified as a significant issue and thus were not considered in the previous economic analysis. However, proposed revised critical habitat in the San Juan Management Unit in San Juan County, Utah, and La Plata County, Colorado, generated concern, because this area serves as a highly developed source of oil and natural gas, with hundreds of existing wells. Due to the level of existing protections in riparian areas required by, or agreed to by, oil and gas developers and land and resource managers, no project modification costs are expected as a result of the designation of revised flycatcher critical habitat. However, baseline administrative costs of $33,000 for one formal and six informal consultations are expected due to limited oil and gas activities, including seismic studies and pipeline construction and maintenance. In addition to baseline costs, the analysis forecasts $11,000 in incremental administrative costs to consider adverse modification as part of these consultations.</P>
          <P>While few active mineral mining activities occur within revised critical habitat, the mining industry has expressed concern that water use by existing or potential mining operations could be affected by flycatcher conservation activities, particularly the designation of critical habitat. There are currently no data that indicate whether existing or future diversions of water for mining act