<?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>77</VOL>
  <NO>250</NO>
  <DATE>Monday, December 31, 2012</DATE>
  <UNITNAME>Contents</UNITNAME>
  <CNTNTS>
    <AGCY>
      <EAR>Agriculture</EAR>
      <PRTPAGE P="iii"/>
      <HD>Agriculture Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Animal and Plant Health Inspection Service</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Food Safety and Inspection Service</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Forest Service</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Institute of Food and Agriculture</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Office of Advocacy and Outreach</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Air Force</EAR>
      <HD>Air Force Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>77048-77049</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31351</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Privacy Act; Systems of Records,</DOC>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31352</FRDOCBP>
          <PGS>77049-77050</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31353</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Animal</EAR>
      <HD>Animal and Plant Health Inspection Service</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Contingency Plans:</SJ>
        <SJDENT>
          <SJDOC>Handling of Animals,</SJDOC>
          <PGS>76815-76824</PGS>
          <FRDOCBP D="9" T="31DER1.sgm">2012-31422</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Submission of Itineraries,</DOC>
          <PGS>76809-76815</PGS>
          <FRDOCBP D="6" T="31DER1.sgm">2012-31417</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Animal Disease Traceability Information Systems, Agreements, and Reports,</SJDOC>
          <PGS>77003-77004</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31346</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Data Standards for Electronic Interstate Certificates of Veterinary Inspection,</DOC>
          <PGS>77004-77005</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31401</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Antitrust Division</EAR>
      <HD>Antitrust Division</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Proposed Final Judgments and Competitive Impact Statements:</SJ>
        <SJDENT>
          <SJDOC>United States v. Apple, Inc., Hachette Book Group, Inc., Harpercollins Publishers LLC, et al.,</SJDOC>
          <PGS>77094-77111</PGS>
          <FRDOCBP D="17" T="31DEN1.sgm">2012-31339</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR/>
      <HD>Antitrust</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Antitrust Division</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR/>
      <HD>Blind or Severely Disabled, Committee for Purchase From  People Who Are</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Committee for Purchase From People Who Are Blind or Severely Disabled</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Consumer Financial Protection</EAR>
      <HD>Bureau of Consumer Financial Protection</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Home Mortgage Disclosure (Regulation C):</SJ>
        <SJDENT>
          <SJDOC>Adjustment To Asset-Size Exemption Threshold,</SJDOC>
          <PGS>76839-76840</PGS>
          <FRDOCBP D="1" T="31DER1.sgm">2012-31311</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Electronic Fund Transfers Regulation E,</DOC>
          <PGS>77188-77215</PGS>
          <FRDOCBP D="27" T="31DEP2.sgm">2012-31170</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Centers Disease</EAR>
      <HD>Centers for Disease Control and Prevention</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Charter Renewal:</SJ>
        <SJDENT>
          <SJDOC>Mine Safety and Health Research Advisory Committee,</SJDOC>
          <PGS>77078-77079</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31366</FRDOCBP>
        </SJDENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Interagency Committee on Smoking and Health,</SJDOC>
          <PGS>77079</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31371</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Commerce</EAR>
      <HD>Commerce Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Economic Development Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Foreign-Trade Zones Board</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>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>77015-77016</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31226</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Committee for Purchase</EAR>
      <HD>Committee for Purchase From People Who Are Blind or Severely Disabled</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Procurement List; Additions and Deletions,</DOC>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31379</FRDOCBP>
          <PGS>77037-77038</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31380</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Commodity Futures</EAR>
      <HD>Commodity Futures Trading Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>77038-77039</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31252</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Comptroller</EAR>
      <HD>Comptroller of the Currency</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Lending Limits,</DOC>
          <PGS>76841-76842</PGS>
          <FRDOCBP D="1" T="31DER1.sgm">2012-31267</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Minimum Capital Ratios; Issuance of Directives,</DOC>
          <PGS>76840-76841</PGS>
          <FRDOCBP D="1" T="31DER1.sgm">2012-31485</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Corporation</EAR>
      <HD>Corporation for National and Community Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>77039-77040</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31404</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Defense Acquisition</EAR>
      <HD>Defense Acquisition Regulations System</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Defense Federal Acquisition Regulation Supplement:</SJ>
        <SJDENT>
          <SJDOC>Contracting Activity Updates,</SJDOC>
          <PGS>76938-76939</PGS>
          <FRDOCBP D="1" T="31DER1.sgm">2012-31086</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Definition of Cost or Pricing Data,</SJDOC>
          <PGS>76939-76941</PGS>
          <FRDOCBP D="2" T="31DER1.sgm">2012-31088</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>New Qualifying Country—Poland,</SJDOC>
          <PGS>76941-76942</PGS>
          <FRDOCBP D="1" T="31DER1.sgm">2012-31083</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Technical Amendments,</SJDOC>
          <PGS>76937-76938</PGS>
          <FRDOCBP D="1" T="31DER1.sgm">2012-31092</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Defense Department</EAR>
      <HD>Defense Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Air Force Department</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Defense Acquisition Regulations System</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Arms Sales,</DOC>
          <PGS>77040-77045</PGS>
          <FRDOCBP D="3" T="31DEN1.sgm">2012-31420</FRDOCBP>
          <FRDOCBP D="2" T="31DEN1.sgm">2012-31429</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Establishment of Department of Defense Federal Advisory Committees,</DOC>
          <PGS>77045-77046</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31222</FRDOCBP>
        </DOCENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Defense Business Board,</SJDOC>
          <PGS>77046-77047</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31378</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Privacy Act; Systems of Records,</DOC>
          <PGS>77047-77048</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31354</FRDOCBP>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31355</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Economic Development</EAR>
      <HD>Economic Development Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Fiscal Year 2012 Annual Report to Congress:</SJ>
        <SJDENT>
          <SJDOC>Trade Adjustment Assistance for Firms Program,</SJDOC>
          <PGS>77218-77246</PGS>
          <FRDOCBP D="28" T="31DEN2.sgm">2012-31377</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Education Department</EAR>
      <HD>Education Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Part 601 Preferred Lender Arrangements,</SJDOC>
          <PGS>77050-77051</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31459</FRDOCBP>
        </SJDENT>
        <SJ>Applications for New Awards:</SJ>
        <SJDENT>
          <SJDOC>Magnet Schools Assistance Program,</SJDOC>
          <PGS>77056-77062</PGS>
          <FRDOCBP D="6" T="31DEN1.sgm">2012-31434</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Institute on Disability and Rehabilitation Research—Small Business Innovation Research Program., Phase I,</SJDOC>
          <PGS>77051-77056</PGS>
          <FRDOCBP D="5" T="31DEN1.sgm">2012-31437</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>List of Correspondence From April 1, 2012, Through June 30, 2012,</DOC>
          <PGS>77063-77064</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31435</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Employment and Training</EAR>
      <PRTPAGE P="iv"/>
      <HD>Employment and Training Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Removal of Job Training Partnership Act Implementing Regulations,</DOC>
          <PGS>76861-76862</PGS>
          <FRDOCBP D="1" T="31DER1.sgm">2012-31029</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Energy Department</EAR>
      <HD>Energy Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Energy Efficiency and Renewable Energy Office</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Energy Regulatory Commission</P>
      </SEE>
      <CAT>
        <HD>RULES</HD>
        <SJ>Energy Conservation Program for Consumer Products:</SJ>
        <SJDENT>
          <SJDOC>Test Procedures for Residential Furnaces and Boilers (Standby Mode and Off Mode),</SJDOC>
          <PGS>76831-76839</PGS>
          <FRDOCBP D="8" T="31DER1.sgm">2012-31175</FRDOCBP>
        </SJDENT>
        <SJ>Energy Conservation Program:</SJ>
        <SJDENT>
          <SJDOC>Certification of Commercial and Industrial HVAC, Refrigeration and Water Heating Equipment,</SJDOC>
          <PGS>76825-76831</PGS>
          <FRDOCBP D="6" T="31DER1.sgm">2012-31373</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Energy Conservation Program for Consumer Products and Certain Commercial and Industrial Equipment:</SJ>
        <SJDENT>
          <SJDOC>Proposed Determination of Commercial and Industrial Compressors as Covered Equipment,</SJDOC>
          <PGS>76972-76976</PGS>
          <FRDOCBP D="4" T="31DEP1.sgm">2012-31393</FRDOCBP>
        </SJDENT>
        <SJ>Energy Conservation Program for Consumer Products:</SJ>
        <SJDENT>
          <SJDOC>Association of Home Appliance Manufacturers Petition for Reconsideration,</SJDOC>
          <PGS>76952-76959</PGS>
          <FRDOCBP D="7" T="31DEP1.sgm">2012-31392</FRDOCBP>
        </SJDENT>
        <SJ>Energy Conservation Program:</SJ>
        <SJDENT>
          <SJDOC>Request for Exclusion of 100 Watt R20 Short Incandescent Reflector Lamp From Energy Conservation Standards,</SJDOC>
          <PGS>76959-76972</PGS>
          <FRDOCBP D="13" T="31DEP1.sgm">2012-31396</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Energy Efficiency</EAR>
      <HD>Energy Efficiency and Renewable Energy Office</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Petitions for Waiver From Residential Dishwasher Test Procedure:</SJ>
        <SJDENT>
          <SJDOC>BSH Corp.,</SJDOC>
          <PGS>77064-77067</PGS>
          <FRDOCBP D="3" T="31DEN1.sgm">2012-31395</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Environmental Protection</EAR>
      <HD>Environmental Protection Agency</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Approvals and Promulgations of Air Quality Implementation Plans:</SJ>
        <SJDENT>
          <SJDOC>New York, New Jersey, and Connecticut; Determination of Attainment of the 2006 Fine Particle Standard,</SJDOC>
          <PGS>76867-76871</PGS>
          <FRDOCBP D="4" T="31DER1.sgm">2012-31214</FRDOCBP>
        </SJDENT>
        <SJ>Approvals and Promulgations of Implementation Plans:</SJ>
        <SJDENT>
          <SJDOC>Colorado; Regional Haze State Implementation Plan,</SJDOC>
          <PGS>76871-76883</PGS>
          <FRDOCBP D="12" T="31DER1.sgm">2012-31192</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Designation of Areas for Air Quality Planning Purposes; Ohio; et al.,</SJDOC>
          <PGS>76884-76897</PGS>
          <FRDOCBP D="13" T="31DER1.sgm">2012-31276</FRDOCBP>
        </SJDENT>
        <SJ>Removal of Significant New Use Rules:</SJ>
        <SJDENT>
          <SJDOC>Significant New Use Rule on Certain Chemical Substances,</SJDOC>
          <PGS>76897-76898</PGS>
          <FRDOCBP D="1" T="31DER1.sgm">2012-31403</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Lead; Renovation, Repair, and Painting Program for Public and Commercial Buildings,</SJDOC>
          <PGS>76996-76998</PGS>
          <FRDOCBP D="2" T="31DEP1.sgm">2012-31532</FRDOCBP>
        </SJDENT>
        <SJ>Pesticides:</SJ>
        <SJDENT>
          <SJDOC>Minimum Risk Exemptions,</SJDOC>
          <PGS>76979-76996</PGS>
          <FRDOCBP D="17" T="31DEP1.sgm">2012-31188</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>NSPS for Fossil Fuel Fired Steam Generating Units; Renewal,</SJDOC>
          <PGS>77073-77074</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31405</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>NSPS for Industrial/Commercial/Institutional Steam Generating Units; Renewal,</SJDOC>
          <PGS>77074-77075</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31406</FRDOCBP>
        </SJDENT>
        <SJ>Environmental Assessments; Availability, etc.:</SJ>
        <SJDENT>
          <SJDOC>Designation of Expanded Ocean Dredged Material Disposal Site; Charleston, SC,</SJDOC>
          <PGS>77076</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31460</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Environmental Impact Statements; Weekly Receipt; Availability,</DOC>
          <PGS>77076</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31461</FRDOCBP>
        </DOCENT>
        <SJ>Pesticide Product Registrations:</SJ>
        <SJDENT>
          <SJDOC>Receipt of Applications for New Uses,</SJDOC>
          <PGS>77077-77078</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31375</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR/>
      <HD>Executive Office of the President</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Presidential Documents</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Trade Representative, Office of United States</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Export Import</EAR>
      <HD>Export-Import Bank</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Economic Impact Policy,</DOC>
          <PGS>77078</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31376</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Aviation</EAR>
      <HD>Federal Aviation Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Exhaust Emissions Standards:</SJ>
        <SJDENT>
          <SJDOC>New Aircraft Gas Turbine Engines and Identification Plate for Aircraft Engines,</SJDOC>
          <PGS>76842-76854</PGS>
          <FRDOCBP D="12" T="31DER1.sgm">2012-31109</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Airworthiness Directives:</SJ>
        <SJDENT>
          <SJDOC>General Electric Company Turbofan Engines,</SJDOC>
          <PGS>76977-76979</PGS>
          <FRDOCBP D="2" T="31DEP1.sgm">2012-31362</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>Tignall, GA,</SJDOC>
          <PGS>76936</PGS>
          <FRDOCBP D="0" T="31DER1.sgm">2012-31408</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Comprehensive Review of Licensing and Operating Rules for Satellite Services,</DOC>
          <PGS>77001-77002</PGS>
          <FRDOCBP D="1" T="31DEP1.sgm">2012-31391</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Emergency</EAR>
      <HD>Federal Emergency Management Agency</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Changes in Flood Elevation Determinations,</DOC>
          <PGS>76915-76916</PGS>
          <FRDOCBP D="1" T="31DER1.sgm">2012-31348</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Final Flood Elevation Determinations,</DOC>
          <PGS>76916-76936</PGS>
          <FRDOCBP D="13" T="31DER1.sgm">2012-31349</FRDOCBP>
          <FRDOCBP D="7" T="31DER1.sgm">2012-31394</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Proposed Flood Elevation Determinations:</SJ>
        <SJDENT>
          <SJDOC>Correction,</SJDOC>
          <PGS>76998-77001</PGS>
          <FRDOCBP D="3" T="31DEP1.sgm">2012-31409</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Nobles County, MN, and Incorporated Areas; Withdrawal,</SJDOC>
          <PGS>76998</PGS>
          <FRDOCBP D="0" T="31DEP1.sgm">2012-31340</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Changes in Flood Hazard Determinations,</DOC>
          <FRDOCBP D="2" T="31DEN1.sgm">2012-31344</FRDOCBP>
          <PGS>77081-77089</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31345</FRDOCBP>
          <FRDOCBP D="2" T="31DEN1.sgm">2012-31374</FRDOCBP>
          <FRDOCBP D="3" T="31DEN1.sgm">2012-31387</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Energy</EAR>
      <HD>Federal Energy Regulatory Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>77067-77070</PGS>
          <FRDOCBP D="2" T="31DEN1.sgm">2012-31264</FRDOCBP>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31265</FRDOCBP>
        </DOCENT>
        <SJ>Applications:</SJ>
        <SJDENT>
          <SJDOC>Black Bear Hydro Partners, LLC,</SJDOC>
          <PGS>77070-77071</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31262</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Combined Filings,</DOC>
          <PGS>77071-77073</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31368</FRDOCBP>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31369</FRDOCBP>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31381</FRDOCBP>
        </DOCENT>
        <SJ>Filings:</SJ>
        <SJDENT>
          <SJDOC>Banning, CA,</SJDOC>
          <PGS>77073</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31266</FRDOCBP>
        </SJDENT>
        <SJ>Initial Market-Based Rate Filings Including Requests for Blanket Section 204 Authorization:</SJ>
        <SJDENT>
          <SJDOC>Carson Cogeneration Co.,</SJDOC>
          <PGS>77073</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31367</FRDOCBP>
        </SJDENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>York Haven Power Company, LLC,</SJDOC>
          <PGS>77073</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31263</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Railroad</EAR>
      <HD>Federal Railroad Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>77181-77183</PGS>
          <FRDOCBP D="2" T="31DEN1.sgm">2012-31382</FRDOCBP>
        </DOCENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Railroad Safety Advisory Committee; Postponement,</SJDOC>
          <PGS>77183</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31383</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Reserve</EAR>
      <HD>Federal Reserve System</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Formations of, Acquisitions by, and Mergers of Bank Holding Companies,</DOC>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31213</FRDOCBP>
          <PGS>77078</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31421</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Fish</EAR>
      <PRTPAGE P="v"/>
      <HD>Fish and Wildlife Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Subsistence Management Program for Public Lands in Alaska; Rural Determination Process,</DOC>
          <PGS>77005-77007</PGS>
          <FRDOCBP D="2" T="31DEN1.sgm">2012-31359</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Food and Drug</EAR>
      <HD>Food and Drug Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>New Animal Drugs:</SJ>
        <SJDENT>
          <SJDOC>Enrofloxacin; Melengestrol; Meloxicam; Pradofloxacin; Tylosin,</SJDOC>
          <PGS>76862-76864</PGS>
          <FRDOCBP D="2" T="31DER1.sgm">2012-31397</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Food Safety</EAR>
      <HD>Food Safety and Inspection Service</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Uniform Compliance Date for Food Labeling Regulations,</DOC>
          <PGS>76824-76825</PGS>
          <FRDOCBP D="1" T="31DER1.sgm">2012-31398</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Foreign Trade</EAR>
      <HD>Foreign-Trade Zones Board</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Authorization of Production Activity:</SJ>
        <SJDENT>
          <SJDOC>Foreign-Trade Zone 230; Sonoco Corrflex; Rural Hall and Winston-Salem, NC,</SJDOC>
          <PGS>77016</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31443</FRDOCBP>
        </SJDENT>
        <SJ>Proposed Export Production Activity:</SJ>
        <SJDENT>
          <SJDOC>Foreign-Trade Zone 33; Pittsburgh, PA, Tsudis Chocolate Co.,</SJDOC>
          <PGS>77016</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31445</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Forest</EAR>
      <HD>Forest Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Subsistence Management Program for Public Lands in Alaska; Rural Determination Process,</DOC>
          <PGS>77005-77007</PGS>
          <FRDOCBP D="2" T="31DEN1.sgm">2012-31359</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Transfer of Land to the Department of Interior,</DOC>
          <PGS>77007-77008</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31342</FRDOCBP>
        </DOCENT>
      </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>Food and Drug Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Health Resources and Services Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Institutes of Health</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Health Resources</EAR>
      <HD>Health Resources and Services Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>77079-77080</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31399</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Homeland</EAR>
      <HD>Homeland Security Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Emergency Management Agency</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Interior</EAR>
      <HD>Interior Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Fish and Wildlife Service</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Land Management Bureau</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Park Service</P>
      </SEE>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Freedom of Information Act Regulations,</DOC>
          <PGS>76898-76915</PGS>
          <FRDOCBP D="17" T="31DER1.sgm">2012-31117</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>International Trade Adm</EAR>
      <HD>International Trade Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Administrative Reviews; Results, Extensions, Amendments, etc.:</SJ>
        <SJDENT>
          <SJDOC>Certain Orange Juice From Brazil,</SJDOC>
          <PGS>77017</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31446</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Antidumping and Countervailing Duty Administrative Reviews; Results, Extensions, Amendments, etc.,</DOC>
          <PGS>77017-77029</PGS>
          <FRDOCBP D="12" T="31DEN1.sgm">2012-31448</FRDOCBP>
        </DOCENT>
        <SJ>Antidumping and Countervailing Duty Administrative Reviews; Results, Extensions, Amendments, etc.:</SJ>
        <SJDENT>
          <SJDOC>Honey From Argentina,</SJDOC>
          <PGS>77029-77031</PGS>
          <FRDOCBP D="2" T="31DEN1.sgm">2012-31436</FRDOCBP>
        </SJDENT>
        <SJ>Antidumping Duty Administrative Reviews; Results, Extensions, Amendments, etc.:</SJ>
        <SJDENT>
          <SJDOC>Honey From Argentina,</SJDOC>
          <PGS>77031-77032</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31450</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Healthcare Trade Mission to Russia, June 3-7, 2013,</DOC>
          <PGS>77032-77035</PGS>
          <FRDOCBP D="3" T="31DEN1.sgm">2012-31425</FRDOCBP>
        </DOCENT>
        <SJ>U.S. Infrastructure Trade Mission to Colombia and Panama:</SJ>
        <SJDENT>
          <SJDOC>Bogota, Columbia and Panama City, Panama, May 13-16, 2012; Correction,</SJDOC>
          <PGS>77035</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31426</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>International Trade Com</EAR>
      <HD>International Trade Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Complaints,</DOC>
          <PGS>77091-77092</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31332</FRDOCBP>
        </DOCENT>
        <SJ>Investigations:</SJ>
        <SJDENT>
          <SJDOC>Certain Computer Forensic Devices and Products Containing Same,</SJDOC>
          <PGS>77093-77094</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31331</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Certain Devices for Improving Uniformity Used in a Backlight Module and Components Thereof and Products Containing Same,</SJDOC>
          <PGS>77092-77093</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31330</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Judicial Conference</EAR>
      <HD>Judicial Conference of the United States</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Hearings:</SJ>
        <SJDENT>
          <SJDOC>Advisory Committee on Rules of Evidence; Cancellation,</SJDOC>
          <PGS>77094</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31449</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Justice Department</EAR>
      <HD>Justice Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Antitrust Division</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Labor Department</EAR>
      <HD>Labor Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Employment and Training Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Mine Safety and Health Administration</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>National Farmworker Jobs Program,</SJDOC>
          <PGS>77111-77112</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31389</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Workforce Investment Act Management Information and Reporting System,</SJDOC>
          <PGS>77112-77113</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31390</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Land</EAR>
      <HD>Land Management Bureau</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Filing of Plats of Survey:</SJ>
        <SJDENT>
          <SJDOC>Idaho,</SJDOC>
          <PGS>77089</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31402</FRDOCBP>
        </SJDENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Las Cruces District Resource Advisory Council, New Mexico,</SJDOC>
          <PGS>77090</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31370</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Resource Advisory Council to the Boise District,</SJDOC>
          <PGS>77090</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31416</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Mine</EAR>
      <HD>Mine Safety and Health Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Petitions for Modification of Application of Existing Mandatory Safety Standards,</DOC>
          <PGS>77113-77117</PGS>
          <FRDOCBP D="4" T="31DEN1.sgm">2012-31233</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Institute Food</EAR>
      <HD>National Institute of Food and Agriculture</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Solicitation of Veterinary Shortage Situation Nominations for Veterinary Medicine Loan Repayment Program,</DOC>
          <PGS>77008-77015</PGS>
          <FRDOCBP D="7" T="31DEN1.sgm">2012-31407</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Institute</EAR>
      <HD>National Institute of Standards and Technology</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Malcolm Baldrige National Quality Award and Examiner Applications,</SJDOC>
          <PGS>77035-77036</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31227</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>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31210</FRDOCBP>
          <PGS>77080-77081</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31212</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Oceanic</EAR>
      <PRTPAGE P="vi"/>
      <HD>National Oceanic and Atmospheric Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>2013-2014 Summer Flounder and Scup Specifications:</SJ>
        <SJDENT>
          <SJDOC>2013 Black Sea Bass Specifications; Preliminary 2013 Quota Adjustments; 2013 Summer Flounder Quota for Delaware,</SJDOC>
          <PGS>76942-76950</PGS>
          <FRDOCBP D="8" T="31DER1.sgm">2012-31424</FRDOCBP>
        </SJDENT>
        <SJ>Fisheries of the Northeastern United States:</SJ>
        <SJDENT>
          <SJDOC>Summer Flounder, Scup, and Black Sea Bass Fisheries; 2012 Summer Flounder, Scup, and Black Sea Bass Specifications; Correction,</SJDOC>
          <PGS>76950-76951</PGS>
          <FRDOCBP D="1" T="31DER1.sgm">2012-31423</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Fisheries of the South Atlantic; South Atlantic Fishery Management Council,</SJDOC>
          <PGS>77037</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31357</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Mid-Atlantic Fishery Management Council,</SJDOC>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31356</FRDOCBP>
          <PGS>77036-77037</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31358</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Park</EAR>
      <HD>National Park Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Big Cypress National Preserve Off-Road Vehicle Advisory Committee,</SJDOC>
          <PGS>77090-77091</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31427</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Na Hoa Pili O Kaloko-Honokohau National Historical Park Advisory Commission,</SJDOC>
          <PGS>77091</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31430</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Nuclear Regulatory</EAR>
      <HD>Nuclear Regulatory Commission</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Rescinding Spent Fuel Pool Exclusion Regulations,</DOC>
          <PGS>76952</PGS>
          <FRDOCBP D="0" T="31DEP1.sgm">2012-31132</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Access Authorization—Operational Program; Proposed Revisions,</DOC>
          <PGS>77117-77118</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31419</FRDOCBP>
        </DOCENT>
        <SJ>Environmental Assessments; Availability, etc.:</SJ>
        <SJDENT>
          <SJDOC>License Amendment for Department of Agriculture, Beltsville, MD,</SJDOC>
          <PGS>77118-77121</PGS>
          <FRDOCBP D="3" T="31DEN1.sgm">2012-31418</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Advocacy Outreach</EAR>
      <HD>Office of Advocacy and Outreach</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Advisory Committee on Beginning Farmers and Ranchers Request for Nominations,</DOC>
          <PGS>77015</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31343</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR/>
      <HD>Office of United States Trade Representative</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Trade Representative, Office of United States</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Personnel</EAR>
      <HD>Personnel Management Office</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Hispanic Council on Federal Employment,</DOC>
          <PGS>77121</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31337</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Postal Service</EAR>
      <HD>Postal Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Product Changes:</SJ>
        <SJDENT>
          <SJDOC>Priority Mail Negotiated Service Agreement,</SJDOC>
          <PGS>77121-77122</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31335</FRDOCBP>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31338</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Presidential Documents</EAR>
      <HD>Presidential Documents</HD>
      <CAT>
        <HD>EXECUTIVE ORDERS</HD>
        <SJ>Committees; Establishment, Renewal, Termination, etc.:</SJ>
        <SJDENT>
          <SJDOC>Educational Excellence for Hispanics Advisory Commission; Reestablishment (EO 13634),</SJDOC>
          <PGS>77247-77249</PGS>
          <FRDOCBP D="2" T="31DEE0.sgm">2012-31574</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Securities</EAR>
      <HD>Securities and Exchange Commission</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Principal Trades With Certain Advisory Clients,</DOC>
          <PGS>76854-76860</PGS>
          <FRDOCBP D="6" T="31DER1.sgm">2012-31221</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Applications:</SJ>
        <SJDENT>
          <SJDOC>Pyxis Capital, LP, et al.,</SJDOC>
          <PGS>77122-77128</PGS>
          <FRDOCBP D="6" T="31DEN1.sgm">2012-31235</FRDOCBP>
        </SJDENT>
        <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
        <SJDENT>
          <SJDOC>BATS Exchange, Inc.,</SJDOC>
          <PGS>77176-77177</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31254</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Chicago Mercantile Exchange Inc.,</SJDOC>
          <PGS>77160-77162</PGS>
          <FRDOCBP D="2" T="31DEN1.sgm">2012-31241</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Financial Industry Regulatory Authority, Inc.,</SJDOC>
          <PGS>77162-77165</PGS>
          <FRDOCBP D="3" T="31DEN1.sgm">2012-31256</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>ICE Clear Credit LLC,</SJDOC>
          <PGS>77156-77157</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31257</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>ICE Clear Europe Ltd,</SJDOC>
          <PGS>77159-77160</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31253</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>NASDAQ OMX BX, Inc.,</SJDOC>
          <PGS>77137-77141, 77152-77154</PGS>
          <FRDOCBP D="4" T="31DEN1.sgm">2012-31245</FRDOCBP>
          <FRDOCBP D="2" T="31DEN1.sgm">2012-31411</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>NASDAQ OMX PHLX LLC,</SJDOC>
          <PGS>77134-77137</PGS>
          <FRDOCBP D="3" T="31DEN1.sgm">2012-31246</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>NASDAQ OMX PHLX, LLC,</SJDOC>
          <PGS>77129-77132, 77174-77176</PGS>
          <FRDOCBP D="3" T="31DEN1.sgm">2012-31238</FRDOCBP>
          <FRDOCBP D="2" T="31DEN1.sgm">2012-31415</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>New York Stock Exchange LLC,</SJDOC>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31240</FRDOCBP>
          <PGS>77160, 77166-77167</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31260</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>NYSE Arca, Inc.,</SJDOC>
          <PGS>77151-77152</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31223</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>NYSE MKT LLC,</SJDOC>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31239</FRDOCBP>
          <PGS>77152, 77154-77156, 77172-77174</PGS>
          <FRDOCBP D="2" T="31DEN1.sgm">2012-31247</FRDOCBP>
          <FRDOCBP D="2" T="31DEN1.sgm">2012-31412</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Options Clearing Corp.,</SJDOC>
          <PGS>77133-77134, 77157-77158</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31258</FRDOCBP>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31259</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>The NASDAQ Stock Market LLC,</SJDOC>
          <FRDOCBP D="3" T="31DEN1.sgm">2012-31236</FRDOCBP>
          <PGS>77141-77151, 77165-77166, 77168-77171</PGS>
          <FRDOCBP D="10" T="31DEN1.sgm">2012-31410</FRDOCBP>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31413</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Social</EAR>
      <HD>Social Security Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Rate for Assessment on Direct Payment of Fees to Representatives in 2013,</DOC>
          <PGS>77177-77178</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31372</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>State Department</EAR>
      <HD>State Department</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Amendment to the International Traffic in Arms Regulations:</SJ>
        <SJDENT>
          <SJDOC>Afghanistan and Change to Policy on Prohibited Exports,</SJDOC>
          <PGS>76864-76865</PGS>
          <FRDOCBP D="1" T="31DER1.sgm">2012-31217</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Culturally Significant Objects Imported for Exhibition Determinations:</SJ>
        <SJDENT>
          <SJDOC>Pre-Raphaelites; Victorian Art and Design, 1848-1900,</SJDOC>
          <PGS>77178</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31440</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Surface Transportation</EAR>
      <HD>Surface Transportation Board</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Abandonment of Freight Easement Exemption:</SJ>
        <SJDENT>
          <SJDOC>Union Pacific Railroad Company in Alameda County, Cal. (San Jose Industrial Lead),</SJDOC>
          <PGS>77183-77184</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31386</FRDOCBP>
        </SJDENT>
        <SJ>Corporate Family Transactions:</SJ>
        <SJDENT>
          <SJDOC>Hotard Coaches, Inc. and Calco Travel, Inc.,</SJDOC>
          <PGS>77184</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31414</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Trade Representative</EAR>
      <HD>Trade Representative, Office of United States</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>2013 Special 301 Review; Public Hearing:</SJ>
        <SJDENT>
          <SJDOC>Identification of Countries Under Section 182 of the Trade Act,</SJDOC>
          <PGS>77178-77180</PGS>
          <FRDOCBP D="2" T="31DEN1.sgm">2012-31336</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Transportation Department</EAR>
      <HD>Transportation Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Aviation Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Railroad Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Surface Transportation Board</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Return of Excess Transit Benefits,</DOC>
          <PGS>77180-77181</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31384</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Treasury</EAR>
      <HD>Treasury Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Comptroller of the Currency</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31237</FRDOCBP>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31385</FRDOCBP>
          <PGS>77184-77185</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31388</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Veteran Affairs</EAR>
      <HD>Veterans Affairs Department</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Copayments for Medications in 2013,</DOC>
          <PGS>76865-76867</PGS>
          <FRDOCBP D="2" T="31DER1.sgm">2012-31432</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Advisory Committee on Disability Compensation,</SJDOC>
          <PGS>77186</PGS>
          <FRDOCBP D="0" T="31DEN1.sgm">2012-31334</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Veterans' Rural Health Advisory Committee,</SJDOC>
          <PGS>77185-77186</PGS>
          <FRDOCBP D="1" T="31DEN1.sgm">2012-31333</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <PTS>
      <PRTPAGE P="vii"/>
      <HD SOURCE="HED">Separate Parts In This Issue</HD>
      <HD>Part II</HD>
      <DOCENT>
        <DOC>Bureau of Consumer Financial Protection,</DOC>
        <PGS>77188-77215</PGS>
        <FRDOCBP D="27" T="31DEP2.sgm">2012-31170</FRDOCBP>
      </DOCENT>
      <HD>Part III</HD>
      <DOCENT>
        <DOC>Commerce Department, Economic Development Administration,</DOC>
        <PGS>77218-77246</PGS>
        <FRDOCBP D="28" T="31DEN2.sgm">2012-31377</FRDOCBP>
      </DOCENT>
      <HD>Part IV</HD>
      <DOCENT>
        <DOC>Presidential Documents,</DOC>
        <PGS>77247-77249</PGS>
        <FRDOCBP D="2" T="31DEE0.sgm">2012-31574</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>77</VOL>
  <NO>250</NO>
  <DATE>Monday, December 31, 2012</DATE>
  <UNITNAME>Rules and Regulations</UNITNAME>
  <RULES>
    <RULE>
      <PREAMB>
        <PRTPAGE P="76809"/>
        <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Animal and Plant Health Inspection Service</SUBAGY>
        <CFR>9 CFR Part 2</CFR>
        <DEPDOC>[Docket No. APHIS-2006-0023]</DEPDOC>
        <RIN>RIN 0579-AD03</RIN>
        <SUBJECT>Submission of Itineraries</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Animal and Plant Health Inspection Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>We are amending the Animal Welfare Act regulations to include more specific requirements in the regulations concerning the submission of itineraries by any person who is subject to the Animal Welfare Act regulations and who intends to exhibit any animal at any location other than the person's approved site when travel will extend overnight. APHIS inspectors need access to animals, facilities, and records for unannounced inspections when animals are exhibited at a location other than at a regulated person's approved site to improve compliance with the regulations and the Animal Welfare Act.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>January 30, 2013.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Dr. Barbara Kohn, Senior Staff Veterinarian, Animal Care, APHIS, 4700 River Road, Unit 84, Riverdale, MD 20737-1234; (301) 851-3751.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Background</HD>
        <HD SOURCE="HD1">Executive Summary</HD>
        <HD SOURCE="HD1">I. Purpose of the Regulatory Action</HD>
        <P>The rule will facilitate enforcement of the Animal Welfare Act regulations for traveling exhibitors and thereby help to ensure the humane handling, housing, treatment, and transportation of the animals in their care.</P>
        <HD SOURCE="HD1">II. Summary of the Major Provisions of the Regulatory Action in Question</HD>
        <P>This rule will require the advance submission of itineraries by any person who is subject to the Animal Welfare Act regulations and who intends to exhibit any animal at any location other than the person's approved site when travel will extend overnight.</P>
        <HD SOURCE="HD1">III. Costs and Benefits</HD>
        <P>Costs of the rule for exhibitors are expected to be small. The estimated time needed to prepare and submit an itinerary once arrangements have been made is about 15 minutes. Many traveling animal exhibitors are already submitting itineraries in a timely manner in accordance with existing Agency policy when a regulated animal is exhibited away from its approved site for 4 days or more. This rule is expected to cost the estimated affected 425 exhibitors a total of about $15,375 per year to prepare and submit itineraries.</P>
        <P>The rule is expected to eliminate costs APHIS incurs in attempting to inspect animals that are not at locations where APHIS expected them to be, and to reduce some costs associated with responding to inquiries and complaints about traveling exhibitors alleged to have violated Animal Welfare Act regulations and standards. Money saved on these activities can be put toward inspections and other activities that will benefit animal welfare.</P>
        <HD SOURCE="HD2">The Final Rule</HD>
        <P>The Animal Welfare Act (Act) (7 U.S.C. 2131-2159) authorizes the Secretary of Agriculture to promulgate rules and standards and other requirements governing the humane handling, housing, care, treatment, and transportation of certain animals by dealers, exhibitors, and other regulated entities. The Secretary of Agriculture has delegated the responsibility for enforcing the Act to the Administrator of the U.S. Department of Agriculture's Animal and Plant Health Inspection Service (APHIS). Regulations and standards established under the Act are contained in title 9 of the Code of Federal Regulations (CFR), parts 1, 2, and 3. The APHIS Animal Care (AC) program ensures compliance with the Act regulations and standards by conducting unannounced inspections of premises with regulated animals.</P>
        <P>The regulations contained in 9 CFR part 2 establish certain responsibilities of regulated persons under the Act. These responsibilities include requirements for the licensing and registration of dealers, exhibitors, and research facilities, and standards for veterinary care, identification of animals, and recordkeeping.</P>
        <P>On October 1, 2009, we published in the<E T="04">Federal Register</E>(74 FR 50738-50740, Docket No. APHIS-2006-0023) a proposal<SU>1</SU>
          <FTREF/>to amend the regulations to include more specific requirements in the regulations concerning the submission of itineraries by any person who is subject to the Act regulations and who intends to exhibit any animal at any location other than the person's approved site. We proposed to require that such itineraries be submitted to the AC Regional Director no fewer than 2 days in advance of any travel.</P>
        <FTNT>
          <P>

            <SU>1</SU>To view the proposed rule and the comments we received, go to<E T="03">http://www.regulations.gov/#!docketDetail;D=APHIS-2006-0023.</E>
          </P>
        </FTNT>
        <P>We proposed that the itinerary include:</P>
        <P>• The name and license or registration number under the Act of the person who will exhibit the animals, and if any animals are leased, borrowed, loaned, or under some similar arrangement, the name of the person who owns the animals;</P>
        <P>• The name, identification number or identifying characteristics, species (common or scientific name), sex and age of each animal; and</P>
        <P>• The names, dates, and locations where the animals will travel, be housed, and be exhibited, including all anticipated dates and locations for any stops and layovers.</P>
        <P>We proposed to require that the itinerary be revised as necessary and the AC Regional Director notified of any changes.</P>
        <P>We explained that our reason for proposing to require such itineraries to be submitted no fewer than 2 days before the start of travel was to ensure that AC inspectors have advance notice of the locations where animals will be exhibited so that they can make unannounced inspections to ensure compliance with regulations and standards for animal welfare.</P>

        <P>We solicited comments concerning our proposal for 60 days ending November 30, 2009. We received 790 comments by that date. They were from<PRTPAGE P="76810"/>animal welfare organizations, exhibitor and trade associations, exhibitors, and private citizens. We have considered all issues raised by the commenters and discuss below those issues that were within the scope of the proposed rule.</P>
        <P>A large number of commenters supported the proposed rule as written. Among the reasons provided for their support, commenters stated that the proposed provisions would make it easier for APHIS to monitor adherence to the regulations and that the rule would have little impact on the majority of exhibitors who already submit itineraries in a timely manner. One commenter expressed the hope that the proposed provisions would allow APHIS to ensure that animals are afforded the minimum space requirements for primary enclosures when not in actual transport and to better monitor the time animals spend in an exercise pen or its equivalent.</P>
        <P>
          <E T="03">Issue:</E>Some commenters stated that the proposed rule is unnecessary because exhibitors already submit itineraries in accordance with a policy that APHIS implemented in 1997, titled “Policy 2,” which states:</P>
        
        <EXTRACT>
          <P>Exhibitors who are in continuous travel status shall update their itinerary as often as necessary to ensure AC [Animal Care] knows their whereabouts at all times.</P>
          <P>Circuses, petting zoos, and acts with an established route shall notify AC in advance of departing their home facility and update travel information as needed.</P>
          <P>Exhibitors who take animals from their facilities from time to time shall notify AC when any animal is gone more than four (4) consecutive days. Upon request, a licensee shall provide an itinerary of absences of less than four (4) days.</P>
          <P>Providing notification ensures the opportunity for access for an unannounced inspection, eliminates unnecessary AC visits when a licensee has been inspected recently, and minimizes resources needed to locate the exhibitor.</P>
          <P>The itinerary should provide the following:</P>
          <P>1. Dates away from the home facility.</P>
          <P>2. City and State for all stops.</P>
          <P>3. Site name or location of all stops.</P>
          <P>Similar information must be provided for all periods of “lay-over” while traveling.</P>
        </EXTRACT>
        
        <P>
          <E T="03">Response:</E>Federal regulations are codified in the CFR and carry the force of law. The regulations that APHIS has promulgated in accordance with the Act are set forth in 9 CFR parts 1 through 4. Additionally, we sometimes issue policy statements to provide the guidance to the public regarding our interpretation of what is necessary for regulated entities to meet the requirements of the regulations. Policy 2 was issued for guidance regarding the requirements of the regulations in § 2.126, which specify that APHIS must have access to regulated facilities in order to conduct inspections that effectively enforce the Act. Although regulated entities are subject to the Act no matter where their animals might be located, the regulations in § 2.126 have not included specific provisions on what APHIS considers necessary for effective enforcement of the regulations when animals have temporarily been moved from an approved site. Although Policy 2 has been useful in conveying APHIS' intent and expectations in such situations, we consider it necessary to codify in § 2.126 more specific responsibilities of a regulated entity.</P>
        <P>
          <E T="03">Issue:</E>A number of commenters stated that if APHIS does replace Policy 2 with regulations in the CFR, the regulations should be consistent with Policy 2 in requiring itineraries to be submitted only if the animals are away from the approved site for 4 days or more. Commenters stated that exhibitors sometimes take animals offsite for several short engagements during the same week or even the same day. Commenters expressed concern that being required to submit an itinerary for every movement from the approved site would impose a large and unnecessary paperwork burden on both exhibitors and APHIS. One commenter recommended that if APHIS concludes there is a need for additional reporting of offsite engagements, the regulations require that all exhibitors who move animals offsite for more than 48 hours notify APHIS of their route, exhibit locations, and anticipated time of return. One commenter recommended that, instead of requiring reporting of all travel from an approved site, APHIS require that exhibitors have on file with APHIS current contact information for the person in charge of the traveling unit. Another commenter recommended that, instead of requiring that all travel from a home facility be reported, APHIS should require that regulated facilities keep in their own records information identifying the animals taken offsite, the location to which the animals have been taken, the date and time of travel, and the date and time when the animals were returned to the facility. The commenter stated that such information would enable APHIS inspectors to know the location of animals that are taken from the approved site for short periods of time.</P>
        <P>
          <E T="03">Response:</E>Based on our experience enforcing the regulations, we consider 4 days too long a time for APHIS to be unaware of the location of animals covered by the Act. As we stated in our October 2009 proposed rule, we need to ensure that AC inspectors have advance notice of the locations where animals will be exhibited so that they can make unannounced inspections to ensure compliance with regulations and standards for animal welfare. Knowing which exhibitor showed animals at a particular location on a particular date will also help AC inspectors follow up on complaints that APHIS receives about alleged violations of the regulations and standards by traveling exhibitors. Such complaints are often received after an exhibitor has left a location, and the person submitting the complaint often does not know the name of the exhibitor. However, based on the information supplied by commenters, we agree that the benefit of APHIS' knowing the location of animals that are taken offsite for exhibition for less than a day may not be commensurate with the reporting that would be required under the proposed provisions. Therefore, in this final rule, we are providing that the reporting requirement under new § 2.126(c) applies only if animals are absent from the approved site overnight.</P>
        <P>
          <E T="03">Issue:</E>One commenter stated that if a complaint were filed while an animal were offsite for less than 4 days, the animal would likely be returned to its approved site before an inspector could reach the offsite location.</P>
        <P>
          <E T="03">Response:</E>We are making no changes based on the comment. Complaints regarding potential violations of the Act are made at various times in relation to the incident or observation. Some are made several weeks or months later. In order for APHIS to effectively follow up on any information received, it is imperative that the Agency know the location of the licensee or registrant and animals at the time of the incident or observation that prompted the complaint.</P>
        <P>
          <E T="03">Issue:</E>As noted above, the proposed rule would have required that itineraries submitted by exhibitors be received by the AC Regional Director no fewer than 2 days in advance of any travel to another location for exhibition, regardless of the length of time. A number of commenters expressed concern that having to give such advance notice would prohibit some exhibitors from accepting certain engagements and requested that the regulations provide for situations where 2 days' notice is not practical. Commenters stated that many requests for animal exhibits, including those for educational purposes, occur within 2 days of the requested exhibit date and that some requests are received on the day of the requested exhibition. Conversely, one commenter recommended that the regulations require that a detailed itinerary be<PRTPAGE P="76811"/>submitted to APHIS no less than 2 months before travel. Another commenter stated that engagements accepted with little advance notice may be subject to less careful planning than those scheduled ahead of time, making it more important for APHIS to ensure that the regulations and the standards of the Act are met.</P>
        <P>
          <E T="03">Response:</E>We expect that some of the concerns expressed by the commenters will be addressed by the change we are making to the proposed provisions that will exempt exhibitors from the submission requirement if the animals are taken offsite for exhibition and returned the same day. Movements of animals offsite for exhibition for longer periods of time requires preparation with regard to logistics such as housing, security, food, water, employees, and public barriers and perimeter fences. Such arrangements are typically made well in advance of travel. AC needs the itineraries before the travel begins to ensure that inspectors know where the animals will be on specific dates so that they can make unannounced inspections at the travel sites. Requiring itineraries to be submitted at least 48 hours in advance will give AC sufficient notice and will be close enough to the time of travel for travel plans and logistics to be firm in most instances. Nevertheless, we recognize the need for some flexibility regarding this requirement. If an exhibitor does accept an engagement for which travel will begin with less than 48 hours' notice, the exhibitor must contact the APHIS AC Regional Director immediately in writing with the information listed in § 2.126(c). Facsimiles or emails are acceptable. We expect such notifications on shortened notice to be infrequent, however, and exhibitors who repeatedly provide less than 48 hours' notice will be subject to increased scrutiny under the Act. We do not consider it practical to set a specific threshold for what constitutes “repeatedly,” due to the wide range of number of submissions by exhibitors. Whereas some exhibitors make only several submissions a year that cover multiple pre-scheduled exhibitions, others submit more numerous submissions on a job-by-job basis. If APHIS considers an exhibitor to be submitting itineraries with less than 48 hours' notice with a high frequency, we may monitor the exhibitor more closely.</P>
        <P>
          <E T="03">Issue:</E>Several commenters stated that the information on itineraries submitted in a timely fashion frequently becomes outdated by the time the animals actually begin their travel. Commenters stated that, due to factors such as illness, behavior, client requests, or shedding, animals listed on the itinerary sometimes cannot travel. Additionally, said some commenters, illness or scheduling conflicts may require that staff members other than those listed on the itinerary travel with the animals. The commenters expressed concern that having to report all such last-minute changes to APHIS would become unduly burdensome for exhibitors.</P>
        <P>
          <E T="03">Response:</E>Although exhibitors are free to submit itineraries well in advance of intended travel, this rule only requires submission of an itinerary no less than 2 days before the travel. Although we recognize that even during that amount of time, it may sometimes become necessary to change the plans indicated on the itinerary, based on our experience dealing with the regulated industry, we do not expect such changes to happen frequently enough that reporting them to APHIS will create an undue burden on exhibitors. Requirements for notifying APHIS of itinerary changes are discussed below.</P>
        <P>
          <E T="03">Issue:</E>Some commenters expressed concern that the proposed rule included a requirement that an itinerary include all anticipated dates and locations (with addresses) for any stops and layovers, and that the itinerary be promptly revised, as necessary, to account for any changes. Commenters stated that it would be unreasonably burdensome on the exhibitor and APHIS to require notification of every minor deviation from a previously filed itinerary. One commenter asked whether APHIS is contemplating requiring specific information regarding rest stops and meal breaks. Commenters stated that a variety of factors determine where and when exhibitors stop on the road for animal care checks and that events that delay or interrupt travel sometimes occur with little or no advance warning. The commenters gave as examples problems with weather, mechanical breakdowns, road conditions, uncooperative animals, and delays from a home facility or stop/layover. Other factors cited included access to water spigots and adequate parking. One commenter stated that train travel is sometimes interrupted due to track or equipment issues or for crew changes, the filling of water tanks, or to allow other traffic to proceed. During longer delays, stated the commenter, animals might be offloaded for exercise and cleaning of railcars.</P>
        <P>
          <E T="03">Response:</E>It is not the intent of this final rule, nor is it the intent of Policy 2 and § 2.126 of the regulations, to require that APHIS be advised regarding every minute of a journey. The required itinerary must indicate where the licensee or registrant and animals will be on which dates. If there is an anticipated layover of a length of time sufficient to allow/require removal of the animals from the transport enclosures, that layover should be indicated on the itinerary. Unanticipated delays of such length must be reported to the appropriate APHIS AC Regional Director the next APHIS business day.<SU>2</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>2</SU>APHIS Regional offices are available each weekday, except on Federal holidays, from 8 a.m. to 5 p.m.</P>
        </FTNT>
        <P>
          <E T="03">Issue:</E>As noted above, the proposed rule included the requirement that the information on a submitted itinerary be promptly revised to account for any changes. Several commenters asked what APHIS' intent is regarding the term “promptly,” whether APHIS personnel would be available to receive notification of changes that occur overnight, and what process APHIS had in mind for editing an itinerary.</P>
        <P>
          <E T="03">Response:</E>This final rule requires notification of itinerary changes in written form. Emails and facsimile notifications can be sent at any hour. We are providing in this final rule that, if initial notification in an emergency is made other than by email or facsimile, it must be followed up with written documentation at the earliest possible time. For changes that occur after normal business hours, the change must be conveyed to the appropriate APHIS AC Regional Director no later than the following APHIS business day.<SU>3</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>3</SU>See footnote 2.</P>
        </FTNT>
        <P>
          <E T="03">Issue:</E>A number of commenters expressed concern that if detailed information about their stops became public knowledge, it could compromise the safety of animals and caretakers. The commenters stated that such information could be used by special interest groups to plan disruptions or conduct acts of violence against exhibitors. Other commenters stated that having advance notice of an exhibitor's itinerary would give competitors an advantage in competing for business. The commenters stated that itineraries should be made available only to APHIS and its inspectors.</P>
        <P>
          <E T="03">Response:</E>We are cognizant of the concerns of persons subject to the Act regarding the release of itinerary information. We note, however, that the type of information required in this rule is already required in accordance with Policy 2 and § 2.126 of the regulations and we are not aware of any problems that have been caused by it to date. Further, a number of licensees and registrants already inform the public of their exhibit dates and locations through Web sites and other means. A person<PRTPAGE P="76812"/>seeking information submitted to APHIS would need to request such information under the Freedom of Information Act, which exempts from release commercial or financial information that is privileged or confidential.</P>
        <P>
          <E T="03">Issue:</E>One commenter recommended that loans for a stated period of time between Association of Zoos and Aquariums (AZA) member zoos and aquariums for exhibit or breeding be exempt from the provisions of the proposal.</P>
        <P>
          <E T="03">Response:</E>We agree that movements of animals from one zoological facility to another for the purposes described by the commenter are of a different nature than the types of movement contemplated by § 2.126(c). Such transfers, which are generally made on a long-term basis, do not fall under the intent or requirements of this final rule. When one zoological facility loans an animal to another zoological facility for purposes such as exhibit or breeding, the facilities generally enter into a legal agreement that transfers responsibility for the animal to the recipient facility for the loan period. The recipient facility is responsibility for meeting the requirements of the Act with regard to that animal during the duration of the loan period.</P>
        <P>
          <E T="03">Issue:</E>One commenter stated that there is no need to apply the regulation as proposed to zoos. The commenter stated that the clear intent of Policy 2 and § 2.126 of the regulations is to ensure that true traveling exhibitors such as carnivals, circuses, animal acts, traveling educational exhibits, and petting zoos are available for inspection. The commenter stated that because zoos are not traveling exhibitors, there is no need to apply the proposed requirements to them.</P>
        <P>
          <E T="03">Response:</E>We agree that zoos are generally not considered traveling exhibitors. As indicated above, those licensees and registrants who take animals offsite and return them the same day will not need to submit an itinerary to APHIS for those movements. However, APHIS needs to know the location of animals moved from zoos overnight for exhibition, just as the Agency needs to know the whereabouts of animals taken offsite overnight for exhibition by other exhibitors. With the exception discussed above for loans between zoological facilities, the provisions of § 2.126(c) will apply to zoological facilities, just as Policy 2 has applied to permanent facilities such as zoos.</P>
        <P>
          <E T="03">Issue:</E>The proposed rule included the requirement that an itinerary contain the following information:</P>
        <P>• The name(s) of the person(s) who intends to exhibit the animal(s) and transport the animal(s) for exhibition purposes, including any business name(s) and current Act license or registration number(s) and, in the event that any animal is leased, borrowed, loaned, or under some similar arrangement, the name of the person who owns such animal;</P>
        <P>• The name, identification number or identifying characteristics, species (common or scientific name), sex and age of each animal; and</P>
        <P>• The names, dates, and locations (with addresses) where the animals will travel, be housed, and be exhibited, including all anticipated dates and locations (with addresses) for any stops and layovers.</P>
        <P>Several commenters stated the required information is duplicative of information the exhibitor is already required to file. Several commenters stated that all animals already must be accompanied by a valid, current health certification, which indicates the animal's age, sex, species, and identification number where applicable. One commenter stated that the proposed requirements would be duplicative of information the exhibitor already files each year as part of its license renewal. The commenter stated that the information already submitted includes a complete list of cities and precise engagement dates and venues.</P>
        <P>
          <E T="03">Response:</E>We are making no changes based on these comments. This rule requires information beyond that collected by other programs and agencies regarding the movement of animals. The information provided in a health certificate does not encompass all the information required under Policy 2 and the more specific requirements of § 2.126 of this rule. Additionally, it is important that this information be submitted and distributed to our field inspectors in a timely manner. Having to rely on incomplete information collected by other parties would not allow efficient and effective use of APHIS resources. We do not expect that there will be a significant increase in reporting requirements for exhibitors who already comply with the regulations and Policy 2. Exhibitors who submit a yearly itinerary that does not change would not need to submit further itineraries under this rule. However, any changes to that yearly submission would need to be reported to APHIS.</P>
        <P>
          <E T="03">Issue:</E>As part of the proposed rule, in accordance with the requirements of the Paperwork Reduction Act (44 U.S.C. 3501<E T="03">et seq.</E>), APHIS provided an estimate of the public reporting burden for the collection of information that would occur under the provisions of the proposal. We estimated that the number of respondents who would provide information to APHIS if the proposed rule were made final would be 300, and that each respondent would provide an average of 8.66 responses per year, for a total of approximately 2,600 responses per year. We estimated that each response would take an average of 0.25 hours to complete.</P>
        <P>One commenter, a representative of the AZA, estimated that because many AZA-accredited zoos and aquariums conduct offsite outreach programs at locations such as schools and nursing homes, the AZA's 221 accredited zoos and aquariums alone would make a total of at least 50,000 to 70,000 submissions annually. Another commenter stated that adjustments to itineraries would require more than 15 minutes each.</P>
        <P>
          <E T="03">Response:</E>Based on comments we received from the public and upon review of our estimate of potential reporting burden for this rule, we agree that submissions by permanently based zoological facilities were underrepresented in our estimate. However, we disagree with the commenter who estimated that AZA-accredited zoos and aquariums would submit at least 50,000 to 70,000 itineraries annually. To arrive at that total, each zoo would need to submit from 225 to 320 itineraries per year, which we consider unlikely, particularly in light of the change we are making in this rule that will not require submission of itineraries for trips that do not extend overnight.</P>

        <P>We have revised our estimates of the number of exhibitors who will be affected by this rule. Our original estimate that 300 exhibitors would be affected by the rule was based on the number of active licensees that had inspections at traveling sites. We have increased that number by 125, based on our estimate that approximately 6 percent of nontraveling exhibitors may occasionally take animals away from their facility overnight for exhibition. We further estimate that those 425 exhibitors would provide a total of about 4,100 responses each year. We derived this number through discussion with AC regional offices and after looking at the size and histories of traveling exhibitors. For example, large circuses usually have itineraries planned a year or more in advance. Some smaller exhibitors may not know their schedules until a week before a performance. Thus, we estimated that about 100 of the affected exhibitors would submit itineraries about twice a year (200 submissions), and that the<PRTPAGE P="76813"/>remainder would submit itineraries monthly (3,900 submissions). We continue to consider our estimate of 0.25 hours per response to be reasonable. In each case where animals are to be moved, the facility or promoter would already have arranged the necessary booking and trip logistics. The 0.25 hours represents the time needed to type or write out the itinerary and send it by email or facsimile to APHIS.</P>
        <P>
          <E T="03">Issue:</E>Several commenters stated that APHIS did not make clear in its proposal why the Agency considers the proposed regulations to be necessary. One commenter requested that APHIS indicate the types of problems its inspectors are experiencing. One commenter stated that, in place of the expanded requirements, APHIS should work with regulated entities to develop methods of ensuring that APHIS maintains reasonable access to facilities and animals. One commenter questioned why APHIS has decided to take on the extra burden of requiring itinerary submissions for all traveling exhibits.</P>
        <P>
          <E T="03">Response:</E>As we stated in our October 2009 proposed rule, AC inspectors need to know the location and dates of traveling exhibits in advance of the travel so that they can conduct unannounced inspections of the animals at those sites. Currently, if an exhibitor has not provided AC with an accurate itinerary in advance of travel, an inspector may arrive at a facility only to find that some or all of the animals are elsewhere. Additionally, if AC receives a complaint about an alleged violation of the regulations and standards by an exhibitor at a certain location on a certain date, having a record of the itineraries will enable us to determine which exhibitor and which animals were at the location on that date so that we can look into the complaint. Currently, if there is no itinerary on file for an exhibition at a location and date cited in a complaint, and the exhibitor is not identified, APHIS must conduct an investigation to try to determine which exhibitor was there, which can be difficult and time consuming, and sometimes unsuccessful. We anticipate that this rule will enable APHIS to make more efficient use of its personnel. While we welcome recommendations from regulated entities on how to ensure that APHIS has reasonable access, we consider this rule a reasonable way to achieve that end.</P>
        <P>
          <E T="03">Issue:</E>Several commenters stated that the administrative burden on APHIS could be reduced by applying the proposed provisions to those exhibitors who have shown a reason to be of concern to APHIS and waiving the requirements for exhibitors who have demonstrated to APHIS that they provide their animals with quality care. One commenter stated that perhaps APHIS should limit the itinerary requirements to offsite exhibit of big cats.</P>
        <P>
          <E T="03">Response:</E>We are making no changes based on the comments. We do not expect an undue administrative burden on APHIS due to this rule. The intent of this rule is to ensure that APHIS has access to all regulated animals for inspections and enforcement activities at all times. Application of the rule to selected licensees and registrants could be construed as arbitrary and capricious enforcement of the regulations.</P>
        <P>
          <E T="03">Issue:</E>Several commenters recommended that the proposal be changed to require automated delivery of itineraries to APHIS. One commenter stated that submission of an itinerary by email would take about 15 minutes and would address the problem of paper copies of itineraries becoming outdated before APHIS receives them.</P>
        <P>
          <E T="03">Response:</E>While we agree that there are advantages to submitting itineraries electronically, we are not requiring submission by that means. Some persons subject to the Act may not have access to that technology, especially while traveling. Because paper copies will need to arrive at APHIS no later than 2 days before the scheduled travel, in the great majority of cases we do not expect them to be out of date by the time the travel begins. As noted above, in those cases where changes need to be made to itineraries at the last minute, those changes will need to be submitted to APHIS in some expedited fashion (e.g., by phone, facsimile, or email), followed by a written submission if the change is not initially in writing.</P>
        <P>
          <E T="03">Issue:</E>One commenter asked how APHIS intends to inform newly affected parties of any updates to the regulations.</P>
        <P>
          <E T="03">Response:</E>Exhibitors will be notified of the regulatory changes in a variety of ways. All proposed and final rules are made available to the public in the<E T="04">Federal Register</E>. Additionally, a press release will be issued when this rule is published and an announcement will be posted to APHIS' Web site. APHIS inspectors will also discuss the rule with licensees and registrants during inspections of regulated facilities.</P>
        <P>
          <E T="03">Issue:</E>One commenter asked what types of animals will be covered by this rule.</P>
        <P>
          <E T="03">Response:</E>This rule applies to all animals covered by the Act that are exhibited anywhere other than the person's approved site.</P>
        <P>
          <E T="03">Issue:</E>One commenter questioned whether the proposed provisions were within APHIS' authority.</P>
        <P>
          <E T="03">Response:</E>Section 2151 of the Act authorizes the Secretary to promulgate such rules, regulations, and orders as the Secretary may deem necessary to govern the humane handling, housing, care, treatment, and transportation of certain animals by dealers, exhibitors, and other regulated entities. Section 2146 of the Act provides that the Secretary shall, at all reasonable times, have access to the places of business and the facilities, animals, and those records required to be kept pursuant to the Act. The Secretary has delegated the responsibility for enforcing the Act to the APHIS Administrator. This final rule merely adds more specific requirements to § 2.126 of the Animal Welfare Act regulations.</P>
        <HD SOURCE="HD2">Miscellaneous</HD>
        <P>In this final rule, we are making several nonsubstantive editorial changes to what appeared in the proposed rule. Instead of making joint references to the singular and plural as, e.g., “animal(s),” we are using the singular to signify also the plural. This is consistent with the style used in the definitions in § 1.1 of the regulations. In the regulatory text of this rule, when referring to the AC Regional Director, we use the term “AC Regional Director,” which is consistent with usage elsewhere in the regulations.</P>
        <P>Therefore, for the reasons given in the proposed rule and in this document, we are adopting the proposed rule as a final rule, with the changes discussed in this document.</P>
        <HD SOURCE="HD2">Executive Orders 12866 and 13563 and Regulatory Flexibility Act</HD>
        <P>This final rule has been determined to be significant for the purposes of Executive Order 12866 and, therefore, has been reviewed by the Office of Management and Budget.</P>

        <P>We have prepared an economic analysis for this rule. The economic analysis provides a cost-benefit analysis, as required by Executive Orders 12866 and 13563, which direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, and equity). Executive Order 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. The economic analysis also examines the potential economic effects of this rule on small entities, as required by the<PRTPAGE P="76814"/>Regulatory Flexibility Act. The economic analysis is summarized below. Copies of the full analysis are available by contacting the person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>or on the Regulations.gov Web site (see<E T="02">ADDRESSES</E>above for instructions for accessing Regulations.gov).</P>
        <P>APHIS is amending the Animal Welfare Act (AWA) regulations to require a person who intends to exhibit regulated animals at any location other than the person's approved site to submit an itinerary at least 2 days in advance when travel extends overnight. In those instances when exhibitors are offered engagements with less than 2 days' notice, APHIS will accept itineraries less than 48 hours in advance of travel.</P>
        <P>The rule will facilitate enforcement of the AWA regulations for traveling exhibitors, and thereby help to ensure the humane handling, housing, treatment, and transportation of the animals in their care.</P>
        <P>Costs of the rule for exhibitors are expected to be small. The AC program has estimated that preparation and submission of an itinerary takes about 15 minutes. Many traveling animal exhibitors are already submitting itineraries in a timely manner in accordance with existing Agency policy when a regulated animal is exhibited away from its approved site for 4 days or more.</P>
        <P>The time required to prepare the estimated 4,100 itineraries that will be required because of this rule is expected to cost the approximately 425 affected exhibitors a total of $15,375 per year.</P>
        <P>Most of the traveling exhibitors affected by the rule are small entities. Regardless of size, we do not expect the exhibitors to be significantly affected.</P>
        <P>The rule is expected eliminate costs APHIS incurs in attempting to inspect animals that are not at locations where APHIS expected them to be, and to reduce some costs associated with responding to inquiries and complaints about traveling exhibitors alleged to have violated Animal Welfare regulations and standards. Money saved on these activities can be put toward inspections and other activities that will benefit animal welfare.</P>
        <P>Under these circumstances, the Administrator of the Animal and Plant Health Inspection Service has determined that this action will not have a significant economic impact on a substantial number of small entities.</P>
        <HD SOURCE="HD2">Executive Order 12372</HD>
        <P>This program/activity is listed in the Catalog of Federal Domestic Assistance under No. 10.025 and is subject to Executive Order 12372, which requires intergovernmental consultation with State and local officials. (See 7 CFR part 3015, subpart V.)</P>
        <HD SOURCE="HD2">Executive Order 12988</HD>
        <P>This final rule has been reviewed under Executive Order 12988, Civil Justice Reform. It is not intended to have retroactive effect. The Act does not provide administrative procedures which must be exhausted prior to a judicial challenge to the provisions of this rule.</P>
        <HD SOURCE="HD2">Paperwork Reduction Act</HD>

        <P>In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. 3501<E T="03">et seq.</E>), the information collection or recordkeeping requirements included in this rule have been approved by the Office of Management and Budget (OMB) under OMB control number 0579-0361.</P>
        <HD SOURCE="HD2">E-Government Act Compliance</HD>
        <P>The Animal and Plant Health Inspection Service is committed to compliance with the E-Government Act to promote the use of the Internet and other information technologies, to provide increased opportunities for citizen access to Government information and services, and for other purposes. For information pertinent to E-Government Act compliance related to this rule, please contact Mrs. Celeste Sickles, APHIS' Information Collection Coordinator, at (301) 851-2908.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 9 CFR Part 2</HD>
          <P>Animal welfare, Pets, Reporting and recordkeeping requirements, Research.</P>
        </LSTSUB>
        
        <P>Accordingly, we are amending 9 CFR part 2 as follows:</P>
        <REGTEXT PART="2" TITLE="9">
          <PART>
            <HD SOURCE="HED">PART 2—REGULATIONS</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 2 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>7 U.S.C. 2131-2159; 7 CFR 2.22, 2.80, and 371.7.</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="2" TITLE="9">
          <AMDPAR>2. In § 2.126, the section heading is revised and a new paragraph (c) and OMB citation at the end of the section are added to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 2.126</SECTNO>
            <SUBJECT>Access and inspection of records and property; submission of itineraries.</SUBJECT>
            <STARS/>
            <P>(c) Any person who is subject to the Animal Welfare regulations and who intends to exhibit any animal at any location other than the person's approved site (including, but not limited to, circuses, traveling educational exhibits, animal acts, and petting zoos), except for travel that does not extend overnight, shall submit a written itinerary to the AC Regional Director. The itinerary shall be received by the AC Regional Director no fewer than 2 days in advance of any travel and shall contain complete and accurate information concerning the whereabouts of any animal intended for exhibition at any location other than the person's approved site. If the exhibitor accepts an engagement for which travel will begin with less than 48 hours' notice, the exhibitor shall immediately contact the AC Regional Director in writing with the required information. APHIS expects such situations to occur infrequently, and exhibitors who repeatedly provide less than 48 hours' notice will, after notice by APHIS, be subject to increased scrutiny under the Act.</P>
            <P>(1) The itinerary shall include the following:</P>
            <P>(i) The name of the person who intends to exhibit the animal and transport the animal for exhibition purposes, including any business name and current Act license or registration number and, in the event that any animal is leased, borrowed, loaned, or under some similar arrangement, the name of the person who owns such animal;</P>
            <P>(ii) The name, identification number or identifying characteristics, species (common or scientific name), sex and age of each animal; and</P>
            <P>(iii) The names, dates, and locations (with addresses) where the animals will travel, be housed, and be exhibited, including all anticipated dates and locations (with addresses) for any stops and layovers that allow or require removal of the animals from the transport enclosures. Unanticipated delays of such length shall be reported to the AC Regional Director the next APHIS business day. APHIS Regional offices are available each weekday, except on Federal holidays, from 8 a.m. to 5 p.m.</P>
            <P>(2) The itinerary shall be revised as necessary, and the AC Regional Director shall be notified of any changes. If initial notification of a change due to an emergency is made by a means other than email or facsimile, it shall be followed by written documentation at the earliest possible time. For changes that occur after normal APHIS business hours, the change shall be conveyed to the AC Regional Director no later than the following APHIS business day. APHIS Regional offices are available each weekday, except on Federal holidays, from 8 a.m. to 5 p.m.</P>
            
            <EXTRACT>
              <FP>(Approved by the Office of Management and Budget under control number 0579-0361)</FP>
            </EXTRACT>
          </SECTION>
        </REGTEXT>
        <SIG>
          <PRTPAGE P="76815"/>
          <DATED>Done in Washington, DC, this 20th day of December, 2012.</DATED>
          <NAME>Rebecca Blue,</NAME>
          <TITLE>Deputy Under Secretary for Marketing and Regulatory Programs.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31417 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-34-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Animal and Plant Health Inspection Service</SUBAGY>
        <CFR>9 CFR Parts 2 and 3</CFR>
        <DEPDOC>[Docket No. APHIS-2006-0159]</DEPDOC>
        <RIN>RIN 0579-AC69</RIN>
        <SUBJECT>Handling of Animals; Contingency Plans</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Animal and Plant Health Inspection Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>We are amending the Animal Welfare Act regulations to add requirements for contingency planning and training of personnel by research facilities and by dealers, exhibitors, intermediate handlers, and carriers. We are taking this action because we believe all licensees and registrants should develop a contingency plan for all animals regulated under the Animal Welfare Act in an effort to better prepare for potential disasters. This action will heighten the awareness of licensees and registrants regarding their responsibilities and help ensure a timely and appropriate response should an emergency or disaster occur.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>January 30, 2013.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Dr. Jeanie Lin, Eastern Region Emergency Programs Manager, Animal Care, APHIS, 920 Main Campus Drive, Raleigh NC 27606; (919) 855-7100.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Background</HD>
        <P>Under the Animal Welfare Act (AWA) (7 U.S.C. 2131<E T="03">et seq.</E>), the Secretary of Agriculture is authorized to promulgate standards and other requirements governing the humane handling, care, treatment, and transportation of certain animals by dealers, research facilities, exhibitors, carriers, and intermediate handlers. Regulations established under the AWA are contained in the Code of Federal Regulations (CFR) in 9 CFR parts 1 and 2, and 9 CFR part 3 contains standards for the humane handling, care, treatment, and transportation of animals covered by the AWA. Currently, part 3 consists of subparts A through E, which contain specific standards for dogs and cats, guinea pigs and hamsters, rabbits, nonhuman primates, and marine mammals, respectively, and subpart F, which sets forth general standards for warmblooded animals not otherwise specified.</P>
        <P>The only requirement for contingency planning by licensees and registrants in the regulations has been in § 3.101(b), which covers water and power supply requirements at facilities housing marine mammals. Specifically, this section requires such facilities to submit written contingency plans to the Deputy Administrator of Animal Care (AC) regarding emergency sources of water and electric power should primary sources fail. Among other things, the plans must include evacuation plans in the event of a disaster and a description of backup systems and/or arrangements for relocating marine mammals requiring artificially cooled or heated water.</P>

        <P>Following the events experienced during the 2005 hurricane season, a Federal document, “The Federal Response to Katrina: Lessons Learned,” which can be found on the Internet at<E T="03">http://georgewbush-whitehouse.archives.gov/reports/katrina-lessons-learned/</E>, was published that highlighted the need for planning to minimize the impact of disasters. AC's experience indicates that, although contingency planning would benefit the health and welfare of animals covered by the AWA, at least some entities responsible for regulated animals have not undertaken such planning. We believe all licensees and registrants should be required to develop a contingency plan for all animals regulated under the AWA in an effort to better prepare for potential disasters. Therefore, on October 23, 2008, we published in the<E T="04">Federal Register</E>(73 FR 63085-63090, Docket No. APHIS-2006-0159) a proposal<SU>1</SU>
          <FTREF/>to amend the AWA regulations to add requirements for contingency planning and training of personnel by research facilities and by dealers, exhibitors, intermediate handlers, and carriers.</P>
        <FTNT>
          <P>

            <SU>1</SU>To view the proposed rule and the comments we received, go to<E T="03">http://www.regulations.gov/#!docketDetail;D=APHIS-2006-0159.</E>
          </P>
        </FTNT>

        <P>We solicited comments concerning our proposal for 60 days ending on December 22, 2008. On December 19, 2008, we published a notice in the<E T="04">Federal Register</E>(73 FR 77554) that extended the comment period an additional 60 days until February 20, 2009. We received 997 comments by that date. They were from private citizens, breeders, dealers, animal welfare organizations, research facilities, Government agencies, pharmaceutical companies, universities and colleges, research associations, exhibitors, carriers, kennels, and medical associations. Fifty commenters supported the rule as it was proposed. The issues raised by the remaining commenters are discussed below by topic.</P>
        <P>Many commenters had comments or questions that were not germane to the proposed rule, such as asking the Animal and Plant Health Inspection Service (APHIS) to end the trade of exotic animals. We are not addressing those comments in this final rule because they are outside of its scope.</P>
        <HD SOURCE="HD2">Objections to Mandating Contingency Plans</HD>
        <P>Many commenters objected to APHIS mandating contingency plans. One commenter stated that, since no plan can be 100 percent successful, it does not make sense to mandate plans. One commenter stated that the AWA has language prohibiting prescribing methods of research and that the proposed rule violates this by prescribing emergency planning methods.</P>
        <P>As stated in the proposed rule, the events experienced during the 2005 hurricane season highlighted the need for planning to minimize the impact of disasters on the health and welfare of all animals covered by the AWA. The intent of the proposed rule was to safeguard the health and welfare of animals in emergency situations. We understand that contingency plans may not be 100 percent successful. However, we do not agree that plans should not be mandated because, to promote animal welfare, entities should be able to demonstrate a reasonable effort to address emergency situations. The rule does not prescribe emergency planning methods. In addition, we do not consider a contingency plan to be a research method.</P>
        <P>One commenter suggested that instead of mandated plans, APHIS should provide guidance materials, training videos, or classes, as it would be cheaper for both APHIS and the regulated entities.</P>

        <P>APHIS plans to provide guidance materials, which may include videos and classes. However, this does not replace a need for contingency plans as contingency plans are more adaptable to the unique circumstances of each licensee and registrant and will determine what training is needed. In addition, as facilities have widely varying needs, allowing licensees and registrants to determine and implement their own unique training allows<PRTPAGE P="76816"/>flexibility and will potentially keep training costs down. We have prepared guidance materials that are being made available concurrently with this final rule on our Web site<SU>2</SU>
          <FTREF/>and will provide additional guidance to licensees and registrants for drafting appropriate contingency plans upon request.</P>
        <FTNT>
          <P>
            <SU>2</SU>
            <E T="03">http://www.aphis.usda.gov/animal_welfare/awa_contingency_plan.shtml.</E>
          </P>
        </FTNT>
        <P>Several commenters stated that they already had contingency plans in place or followed other accreditation standards (e.g., Association of Zoos and Aquariums standards), which they stated were sufficient to address the contingency plan components we proposed to require. Some of these commenters asked that they be exempt from the requirements of the rule because they already had plans in place or that APHIS work with other organizations that have accreditation standards to draft a standard document so that the regulations are not redundant. One commenter stated that APHIS should have done a better job of talking to facilities that already have contingency plans in place.</P>
        <P>We recognize that many AWA licensees and registrants may already have contingency plans in place. Although many of these plans may be sufficient to satisfy the new contingency plan requirements in this final rule, exemption is not practical as those nongovernmental accreditation standards are not mandatory, nor are they linked by regulatory processes to the AWA. However, before developing the proposed rule, we gathered information on regulated entities that currently have contingency plans in place. This information was used as a basis for the proposed criteria for developing contingency plans.</P>
        <HD SOURCE="HD2">Submission of Contingency Plans</HD>
        <P>Many commenters asked how APHIS will review the contingency plans, and in particular whether we will require submission of contingency plans to APHIS. Many commenters objected to submitting contingency plans because they were concerned that the plans would be subject to the Freedom of Information Act (FOIA) and that disclosure of contingency plans would put at risk the safety and security of facilities, employees, and animals by giving animal rights extremists important information. Many other commenters supported submitting contingency plans to APHIS or other agencies or making them available to the public or making relevant portions of plans available to local services identified by facilities as potentially important to the execution of their contingency plan. One commenter suggested posting contingency plans online while another suggested electronic submission. Several commenters stated that licenses should be revoked or not renewed if contingency plans are not submitted to APHIS or that plans that have been modified due to personnel changes or updates should be submitted to APHIS.</P>
        <P>We do not intend to require submission of contingency plans. As stated in the analysis of significant alternatives to the rule in the proposed rule, there are over 10,000 licensees and registrants and requiring each of them to submit plans to APHIS for review would take an enormous amount of resources for the Agency to process, review, and store. Therefore, we proposed that each research facility, dealer, exhibitor, intermediate handler, or carrier will be required to review their contingency plan on at least an annual basis. We would expect that each licensee and registrant would maintain documentation of their annual reviews, including documenting any amendments or changes made to their plan since the previous year's review, such as changes made as a result of recently predicted, but historically unforeseen, circumstances (e.g., weather extremes). We are making this clarification in § 2.38(l)(2) and § 2.134(b). We are also clarifying that APHIS will have the opportunity to review annual review documentation and training records, as well as contingency plans, as a part of our routine inspection process. It is the regulated facility's decision whether or not to share its plan with outside entities. The AWA does not require licensees and registrants to disclose documentation to outside entities. However, if a contingency plan details coordination with other government entities, an inspector may check for evidence supporting this coordination.</P>
        <HD SOURCE="HD2">Expertise</HD>
        <P>Several commenters stated that there is no evidence that APHIS has more expertise in contingency planning than other organizations, such as universities. One commenter stated that APHIS should consult with other agencies such as the Federal Emergency Management Agency (FEMA) in the development of requirements for contingency plans or in the implementation of contingency plans.</P>
        <P>APHIS already has the technical expertise to ensure that regulated entities protect the health and well-being of animals in accordance with the AWA. Further, in 2008, APHIS launched an Animal Care Emergency Programs unit, which is a full-time unit dedicated to collaborating with other organizations to support the safety and well-being of animals during emergencies and disasters. As required by the AWA, APHIS consults and cooperates with other Federal agencies concerned with the welfare of animals used for research, experimentation, or exhibition. APHIS also routinely works closely with FEMA and other organizations on animal welfare issues prior to and during disasters and emergencies.</P>
        <P>Several commenters stated that the facility and not the Government should decide what should be in contingency plans.</P>
        <P>As stated in the proposed rule, because we recognize that individual circumstances for regulated entities may be different, it is difficult to go into specific detail as to what elements must be included in all contingency plans. Therefore, we have not sought to develop a one-size-fits-all plan but have instead provided a framework of four criteria, in § 2.38(l)(1) for research facilities and § 2.134 for dealers, exhibitors, intermediate handlers, and carriers, that we believe are the minimum criteria necessary to ensure a successful contingency plan. We have largely left to the discretion of each regulated entity how best to develop contingency plans that:</P>
        <P>• Identify common emergencies such as electrical outages, faulty HVAC systems, fires, animal escapes, and natural disasters the facility is most likely to experience.</P>
        <P>• Outline specific tasks required to be carried out in response to the identified emergencies including, but not limited to, specific animal evacuation plans or shelter-in-place plans and provisions for providing backup sources of food and water as well as sanitation, ventilation, bedding, veterinary care, etc.</P>
        <P>• Identify a chain of command and who (by name or by position title) will be responsible for fulfilling these tasks.</P>
        <P>• Address how response and recovery will be handled in terms of materials, resources, and training needed.</P>

        <P>We believe that fulfilling these criteria is essential to the success of a contingency plan. In addition, we believe that these criteria provide an adequate degree of flexibility to allow all regulated entities to comply with the provisions of this final rule. These criteria are essential because they form a framework of what potential events to address, who has responsibility, and how to mitigate the potential events. These criteria form the basis of FEMA's “Ready Business” campaign, which<PRTPAGE P="76817"/>provides information to businesses on how to plan for emergencies. We have modified that information to address animal welfare concerns.</P>
        <HD SOURCE="HD2">Specific Criteria</HD>
        <P>One commenter stated that the contingency plan should identify and evaluate the location of the facility and the probable specific emergency situations that location is likely to experience. The commenter further stated that any facility-specific vulnerability should be identified and addressed. One commenter stated that facility grounds should be in areas not prone to flooding or earthquakes and that it is preferable to provide onsite care during an emergency.</P>
        <P>One of the proposed criteria for development of contingency plans is that the plan identify situations, such as emergencies and natural disasters, that a regulated entity is most likely to experience that would trigger the need for the measures identified in a contingency plan to be put into action. We expect that, if a facility-specific vulnerability would impact the humane handling and care of AWA-regulated animals during an emergency, the vulnerability would be addressed within the regulated entity's contingency plan. While we agree that ideally a regulated entity would not be located in an area prone to flooding or earthquakes, we realize that is not always feasible to ensure. As stated in the proposed rule, such disasters, if likely to be encountered by a particular regulated entity, would be expected to be addressed in that regulated entity's contingency plan.</P>
        <P>Several commenters stated that euthanasia should be considered a viable option in the event of a disaster. Several commenters stated that marine mammals should be microchipped to facilitate recovery in the event they are released into the wild. One commenter stated that all tasks necessary for ensuring the welfare of animals should be itemized and the time required for each task estimated. Several commenters recommended providing criteria for development of contingency plans by animal group or by species and, for marine mammals, criteria by geographic location. Several commenters stated that agreements with alternative facilities for evacuation should be part of the contingency plan.</P>
        <P>Since each regulated entity has different needs, we have largely left to the discretion of each regulated entity how best to fulfill the criteria of this final rule. Details about elements to include in a contingency plan, such as whether to use microchip identification methods or euthanasia or whether to itemize and time tasks, are to be decided upon by the regulated entity. In addition, as long as a regulated entity addresses each of the elements required for contingency plans, it may divide its plan according to criteria such as animal group, species, or geographic location. While we encourage regulated entities to explore cost-efficient options such as entering into mutual aid agreements with nearby similar entities, we are not requiring them to do so, as long as their contingency plans are adequate to protect the animals' welfare.</P>
        <P>As noted previously, the only contingency planning currently required for licensees and registrants are those requirements in § 3.101(b) which cover water and power supply requirements for facilities housing marine mammals. One commenter suggested that the requirements in § 3.101(b) be revised to require that contingency plans submitted for marine mammals include the proposed criteria for contingency plans included in § 2.134.</P>
        <P>The regulations added in this final rule in § 2.134 for developing contingency plans apply to all dealers, exhibitors, intermediate handlers, and carriers, including those that handle marine mammals. We are amending § 3.101(b) in this final rule to make it clear that facilities housing marine mammals must comply with the contingency planning requirements in § 2.134.</P>
        <HD SOURCE="HD2">Transportation</HD>
        <P>Several commenters stated that carriers and intermediate handlers should not have to develop contingency plans because it would be costly for them, because the number of animals lost or harmed in transit is miniscule, or because they have limited resources to respond to emergency situations. Given this, several commenters expressed concern that, if forced to comply with the proposed rule, carriers may not want to do business with research facilities.</P>
        <P>We believe that all research facilities, dealers, exhibitors, intermediate handlers, and carriers should be required to develop a contingency plan for all animals regulated under the AWA. Although there may be costs associated with developing contingency plans, we expect such costs to be reasonable given that we have largely left it up to the discretion of regulated entities to determine the best way to fulfill the contingency plan criteria provided in this final rule for their own unique circumstances (i.e., size, type of entity, location, etc.). Therefore, we do not expect that developing contingency plans will cause a significant financial burden on carriers and intermediate handlers. At a minimum, we would expect that carriers, intermediate handlers, and traveling exhibitors would have provisions in place to respond to weather-related problems and animal escapes, as well as other problems, such as mechanical failures, most likely to be experienced during transit. We do not necessarily expect carriers and intermediate handlers to have backup sources of food and water on hand when traveling, but we would expect that their contingency plan would document how and where to get them if needed. In addition, we are clarifying in § 2.134(b) that all traveling entities must carry a copy of their contingency plan with them at all times and make it available for inspection while in travel status. Having a copy of their contingency plan on hand will allow regulated entities to refer directly to their plan in the event of an emergency while traveling. We believe this will result in preventing the loss or harm of regulated animals.</P>
        <P>Several commenters stated that facilities should have backup carriers if their plans require evacuation. Also, the commenters stated that carriers should include in their plans which facility to service first in the event that a major disaster happens and multiple facilities are impacted.</P>
        <P>While we do not require regulated entities to employ backup carriers, if a regulated entity's contingency plan includes a backup carrier, we expect that the regulated entity will ensure that the carrier is compliant with the elements of the contingency plan. In addition, we believe that carriers should coordinate with the facilities they serve.</P>
        <P>Because we realize that some dealers, exhibitors, intermediate handlers, and carriers do not have stationary facilities, we are making a change to the requirements in § 2.134(a)(1) by removing the word “facility” and replacing it with the more inclusive words “licensees and registrants.” In addition, we are adding “mechanical breakdowns” to the list of likely emergencies that may be addressed in a contingency plan.</P>

        <P>Several commenters stated that licensees who travel with animals should be required to submit contingency plans both for at home and on the road. Several commenters stated that travel as part of contingency plans for dangerous animals or for marine mammals should be prohibited unless necessary for the welfare of the animals because of the risks to public safety and animal welfare, particularly in emergency situations. One commenter asked how animals that cannot be<PRTPAGE P="76818"/>evacuated will be cared for and stated that there needs to be a requirement for securing a facility in the event animals cannot be evacuated. One commenter stated that the contingency plan must document how and by whom animals would be moved and what efforts will be made to ensure the relocation of animals is done in the most humane or least stressful manner possible.</P>
        <P>The intent of the proposed rule was to safeguard the welfare of animals in emergency situations. There is no requirement to travel with animals unless it is part of a facility's contingency plan. As stated in the proposed rule, the contingency plan would have to provide detailed instructions for evacuation or shelter-in-place. Therefore, if a contingency plan includes provisions for evacuation, we expect that the plan will also include details on how and by whom the animals would be moved in a way that would be as humane as possible given the disaster circumstances a facility may be facing.</P>
        <P>One commenter asked whether an outside carrier's equipment, if called upon, would have to comply with AWA requirements.</P>
        <P>Regulated entities are expected to ensure that their routine and back-up carriers are compliant with all AWA requirements.</P>
        <HD SOURCE="HD2">Disasters</HD>
        <P>Several commenters stated that detailed evacuation or shelter-in-place plans may be possible for emergencies, but are impractical for natural disasters because regulated entities rarely have advance notice of disasters and because there are so many variations in facilities and disasters that it does not make sense to have a one-size-fits-all plan. The commenters further stated that the rule should acknowledge this and allow for a “best efforts” approach when making contingency plans for unpredictable natural disasters. Several commenters expressed concern that the proposal seemed to require that all potential disasters be addressed no matter how likely they are to occur. However, one commenter stated that all potential disasters that might occur should be addressed in the contingency plan.</P>
        <P>We recognize that it is not practical to prescribe detailed contingency plans for all situations. Therefore, we have not sought to develop a one-size-fits-all plan, but have largely left to the discretion of each regulated entity how best to fulfill the criteria described in the proposed rule. This rule intends to set the minimum criteria necessary to ensure a successful contingency plan. We believe this provides an adequate degree of flexibility to allow all regulated entities to comply with the provisions of the rule. As stated in the proposal, we would require that regulated entities address those emergencies and disasters most likely to occur, rather than requiring them to address all possible disasters and emergencies regardless of likelihood. We encourage regulated entities to consider all scales of emergencies, but recognize that highly localized events such as power disruptions and road closures (e.g., from a vehicular accident) are most likely. APHIS encourages the regulated communities to address these more routine events in their contingency plans, and to work with their local emergency management organization. APHIS understands that disaster and emergency events may be unpredictable and that it is impossible for every possible event to be addressed in a contingency plan.</P>
        <P>One commenter stated that the contingency planning requirements are inconsistent with Homeland Security Presidential Directive 8: National Preparedness (HSPD-8) because terms used in the rule, such as “major disaster” and “emergency,” are not consistent with those used in the directive.</P>

        <P>HSPD-8 establishes policy for dealing with terrorist attacks, major disasters, and other events of national scope. Section 2(e) of the directive states that the terms “major disaster” and “emergency” are defined in section 102 of the Robert T. Stafford Disaster Relief and Emergency Assistance Act. Under that Act, “emergency” is defined as any occasion or instance, as determined by the President, where Federal assistance is needed to save lives, protect property and public health and safety, or to lessen or avert a catastrophe. A “major disaster” is defined as any natural catastrophe, as determined by the President, which causes damage of sufficient severity and magnitude to warrant major disaster assistance in order to supplement the efforts and available resources of States, local governments, and disaster relief organizations in alleviating the damage, loss, hardship, or suffering caused by the catastrophe. The Stafford Act is largely a framework for Federal assistance to State and local governments for disaster relief, and these terms require Presidential involvement. The scope of this rule is broader, and thus we use the terms “disaster” and “emergency” in more general terms. This rule considers “disaster” and “emergency” to mean those events which disrupt the ability of a licensee or registrant to continue with normal business routine and which are expected to be detrimental to the good health and well-being of the animals in the licensee's or registrant's care. A core concept of emergency management is that emergencies are managed at the most local level possible. The National Incident Management System, December 2008, supports this in stating that “incidents typically begin and end locally, and are managed on a daily basis at the lowest possible geographical, organizational, and jurisdictional level.” The document is available from the FEMA Web site at<E T="03">http://www.fema.gov/pdf/emergency/nims/NIMS_core.pdf.</E>While emergencies and disasters may be Statewide or even national in scope, we expect that most often they will be events that do not generally involve disaster declarations and that remain localized, such as power outages, facility fires, or ice storms.</P>
        <P>One commenter stated that contingency plans should be integrated into the overall hazard response plan for facilities.</P>
        <P>Although we do not require regulated entities to integrate animal contingency plans into their business continuity plans, we encourage them to do so. APHIS believes that having a business continuity plan supports animal health and welfare as well as overall good business practices.</P>
        <HD SOURCE="HD2">Backups</HD>
        <P>The proposed requirements in §§ 2.38(l)(1)(ii) and 2.134(a)(2) stated that regulated entities must include in their contingency plans provisions for providing backup sources of food and water as well as sanitation, ventilation, bedding, veterinary care, etc. Several commenters recommended that we remove the words “backup sources of” from this provision and insert the words “as described in the contingency plan” after the phrase “as well as sanitation, ventilation, bedding, veterinary care, etc.” These commenters stated that it may not be possible to maintain all of the veterinary care provisions listed in § 2.33(b) during a disaster.</P>

        <P>While it may not be possible to provide the same level of veterinary care during an emergency or disaster as during normal business operations, APHIS believes that the veterinary care requirements in § 2.33(b) are the minimum requirements necessary to ensure the health and welfare of regulated animals. As with the contingency plan criteria, these veterinary care requirements are general rather than specific to allow regulated entities the discretion to determine how best to fulfill the requirements based on<PRTPAGE P="76819"/>their own unique situations. In addition, as backup veterinary care is an element that must be addressed within the contingency plan, APHIS will be able to assess the adequacy of the backup veterinary care as it assesses the adequacy of veterinary care overall during routine inspections.</P>
        <HD SOURCE="HD2">Review and Enforcement</HD>
        <P>Several commenters expressed concern regarding APHIS' ability to provide adequate inspection and review of plans, stating that the review of plans would present an excessive burden to APHIS. One commenter suggested that APHIS could reduce the inspection burden by reviewing a random sampling of plans. Two commenters suggested that, at a minimum, APHIS should review the contingency plans of facilities with dangerous animals such as elephants, nonhuman primates, or large carnivores. One commenter asked who APHIS would pay to obtain the extra staff to enforce the rule. One commenter suggested that licensing fees be increased to fund additional inspectors or that APHIS stop issuing licenses until numbers of facilities drop to a manageable level.</P>
        <P>We do not believe that our review of contingency plans would present an excessive burden on APHIS. As noted above, we would review contingency plans as a part of the routine inspection process, similar to the process for our review of dog exercise and nonhuman primate environment enhancement plans. We believe in this way we will be able to provide adequate review of the contingency plans for all regulated entities. We do not anticipate that additional APHIS staff will need to be hired as a result of this rule. Neither do we anticipate needing to contract out to other organizations to obtain additional staff.</P>
        <P>Many commenters were concerned that there were not enough specifics about what would make a contingency plan acceptable and that facilities could be cited for failing to include certain items in their plans or for not following their plans exactly. Several commenters suggested punishments for facilities that either do not submit their plans or whose plans are inadequate. One commenter asked whether the judgment of noncompliance will be affected by whether animals were harmed in any way.</P>
        <P>We have issued a guidance document along with this final rule that will assist licensees and registrants in determining what elements to include in their contingency plans. The guidance document is intended only to provide suggestions for how regulated entities may satisfy the criteria in the regulations rather than to prescribe specific measures that must be undertaken or equipment that must be purchased. For example, a regulated entity has multiple options to mitigate the potential failure of an HVAC system besides purchasing a backup generator, some of which are no-cost solutions. These no-cost solutions might include the use of a borrowed generator, opening windows, using existing fans, and/or moving the animals to a cooler location. Any of these actions could be considered adequate ways of responding to the potential failure of an HVAC system and could therefore be included in a contingency plan as long as the action listed is actually feasible. For instance, if a regulated entity's contingency plan calls for opening windows, but the facility's windows are incapable of opening, opening windows would not be a valid mitigation measure. We wish to emphasize that compliance with this final rule will be achieved through the development of an appropriate contingency plan and the training of facility personnel with respect to that plan. Nothing in this rule should be construed as requiring affected entities to make capital expenditures—for example, purchasing backup generators or making structural changes to a facility—in order to comply with the rule. As we do currently when enforcing the regulations, APHIS will assess the adequacy of a regulated entity's contingency plan using the Animal Welfare Act and Animal Welfare Regulations. This may be demonstrated by the plan itself, training records, the presence of materials and resources mentioned in the plan, or a documented history of responses to similar situations. An adequate contingency plan is one in which the minimum criteria considered necessary for a successful contingency plan have been addressed. Enforcement action may be taken on a case-by-case basis.</P>
        <P>One commenter asked if missing the training deadline by a few days would result in noncompliance with the training requirements in the regulations regarding the contingency plan.</P>
        <P>All noncompliant items, including failure to train employees on the components of the contingency plan, found during inspection would be documented on the inspection report and may be subject to enforcement action on a case-by-case basis. Enforcement actions may include issuance of official warnings, civil monetary penalties, license suspension, or license revocation. Licensees and registrants are expected to comply with all requirements of the regulations and standards, including training deadlines.</P>
        <P>Several commenters asked who would be determining the adequacy of plans and what training they would have.</P>
        <P>APHIS inspectors will review and determine the adequacy of contingency plans. We will provide training to the inspection personnel on evaluating contingency plans pursuant to the criteria set forth in this rule.</P>
        <P>One commenter asked on what basis regulated entities would be expected to determine what natural disasters they may face and whether and how this determination will be evaluated by inspectors.</P>
        <P>In the proposed rule we provided links to the U.S. Geological Survey “Hazards” Web site and the Weather Channel “WeatherREADY” Web site. These Web sites are good resources for determining the natural disasters facilities are most likely to encounter in their location. We would largely leave it up to the regulated entity to determine which natural disasters they may face. However, if it is apparent the regulated entity is likely to encounter a disaster that the contingency plan does not address (e.g., a facility in Florida that has experienced hurricanes in the past), APHIS inspectors will notify the entity and give the entity time to add provisions for responding to the disaster in the contingency plan. We anticipate that inspectors, who are typically stationed in the local area surrounding the facility, will be able to provide further guidance on potential natural disasters.</P>
        <P>One commenter stated that the rule should be revised to include language relieving a regulated facility of responsibility if a higher emergency response authority steps in.</P>
        <P>We expect that most emergencies will be of a local nature, such as facility fires or water main breaks. For emergencies or disasters of a larger scale, APHIS will consider the roles of jurisdictional emergency response authorities with respect to contingency plan implementation. It is not the intent of the rule to interfere with local, State, or Federal jurisdictional emergency response activities.</P>
        <HD SOURCE="HD2">Training</HD>

        <P>As stated in the proposed rule, training of personnel could be developed and offered by the research facility, dealer, exhibitor, intermediate handler, or carrier or provided by an outside entity. Several commenters stated that training requirements should be identified, including how facilities will document training. One commenter stated that a checklist should be<PRTPAGE P="76820"/>implemented with staff signing off that they have read the standard operating procedures and completed training. Two commenters stated that there should be requirements for training and availability of backup personnel or for ensuring intermediate personnel replacement and training. Several commenters stated that trial runs of the contingency plan must be carried out.</P>
        <P>As stated previously, because we recognize that individual circumstances for regulated entities may be different, it is difficult to go into specific detail as to what elements must be included in all contingency plans. Therefore, we do not believe it appropriate to provide technical and tactical requirements, such as protocols for personnel replacement and training, in the regulations. We anticipate that inspectors may confirm that contingency plan training is delivered in a similar manner to their current process for confirming that other required training has been delivered (e.g., for husbandry practices and veterinary care protocols). Such confirmation may include reviewing training documentation maintained by the regulated entity or asking involved employees questions about facility practices. While we have not specifically mandated trial runs of contingency plans, training may include trial runs in order to prepare licensees and registrants adequately in the event of a disaster or emergency.</P>
        <P>One commenter stated that both position title and name of employees who play a part in implementing the contingency plan should be included in the contingency plan.</P>
        <P>As stated in the proposed rule, regulated entities would need to identify a chain of command and who (by name or position title) will be responsible for fulfilling required tasks. We would leave it up to the regulated entity whether to include both position title and name or whether to include one or the other.</P>
        <P>Several commenters stated that training should only apply to individuals who have a role to play within the contingency plan.</P>
        <P>We believe the decision of which individuals should be trained is a decision best left up to the discretion of the regulated entity. However, we would expect all personnel who may be involved in or impacted by an emergency or disaster to be trained at an appropriate level.</P>
        <HD SOURCE="HD2">Dates</HD>
        <P>In the proposed rule, we proposed to require that contingency plans be in place 180 days after the effective date of this final rule. In addition, we proposed that training of personnel would have to take place within 60 days following the adoption of a contingency plan by the research facility, dealer, exhibitor, intermediate handler, or carrier. Employees hired within 30 days or less after adoption of the contingency plan would have to be trained in that 60-day period while employees hired more than 30 days after adoption of the contingency plan would have to be trained within 30 days of their start date.</P>
        <P>Several commenters asked that we further push back the effective date of the regulations to allow time to finalize contingency plans. One commenter stated that it was unclear whether the adoption date mentioned in the proposed rule is the date the rule is adopted or the date plans must be in place and that, if it is the former, the rule needs to be revised since this would require training to be completed before the contingency plan, which will guide the training, is in place. The commenter further stated that the 180-day period for having plans in place should begin at the later of either the effective date of the final rule or the date of issuance of guidance documents by APHIS. Two commenters asked whether the 180-day timeframe for having contingency plans in place includes procuring all necessary materials and resources for implementing the contingency plan. The commenters stated that if such is the case, it is too short of a timeframe to gather materials and resources that are not currently available within a facility.</P>
        <P>As stated in the proposed rule, the adoption date is the date the contingency plan must be in place. For current licensees and registrants, this date is 180 days after the effective date of this final rule. For future licensees and registrants, we expect the licensee or registrant to have a contingency plan in place prior to conducting regulated activities. We are making changes to paragraphs (l)(2) and (l)(3) in § 2.38 and paragraphs (b) and (c) in § 2.134(b) in order to make it clearer that the adoption date is the date the contingency plans must be finalized. Training of personnel must take place within 60 days after the adoption date. We believe 180 days is a sufficient length of time to ensure that contingency plans are in place and to procure any necessary materials and resources for implementing contingency plans.</P>
        <P>Several commenters stated that the 30-day training requirement for newly hired personnel is unnecessary and not in keeping with the lack of specificity for the rest of the plan.</P>
        <P>We believe that it is important to ensure that employees of a regulated entity are familiar with the regulated entity's contingency plan. Therefore, it is appropriate to require that training occur within 30 days.</P>
        <HD SOURCE="HD2">Guidance</HD>
        <P>One commenter stated that guidance documents for developing contingency plans should be developed by a lead organization with expertise in collaboration with outside organizations. One commenter stated that guidance documents should not be developed by entities outside of APHIS but that stakeholders/licensees should have input. Several commenters objected to guidance documents or other means for providing criteria outside of the regulations at all. Several commenters stated that the guidance document should be made available via the Internet, and released with the final rule.</P>
        <P>APHIS has expertise in collaborating with outside organizations and is also responsible for enforcing the AWA. Therefore, it is appropriate for us to take the lead role in developing guidance documents to support contingency planning. As stated previously, we are providing a guidance document with this final rule. During the comment period for the proposed rule, we asked for public comment, including comment from stakeholders and licensees, on what elements should be included in the guidance document. To reiterate, APHIS will assess the adequacy of a regulated entity's contingency plan using the Animal Welfare Act and Animal Welfare Regulations. The guidance document provides suggestions for how regulated entities may satisfy the criteria in the regulations.</P>
        <P>One commenter said that USDA should provide guidance on how contingency plans might address elements unique to each facility. One commenter suggested that APHIS create a Web site with more information that includes guidelines, checklists, and templates. Several commenters supplied examples of contingency plans, links to contingency plans, or resources for drafting contingency plans.</P>

        <P>We are issuing a guidance document that may assist regulated entities in addressing the circumstances unique to their location or facility. We also reviewed the information provided by the commenters and will make a list of helpful resources available on our Web site (see footnote 2). The guidance document is intended to be only a tool<PRTPAGE P="76821"/>when considering how a facility might meet the regulatory requirements, and does not provide a new set of criteria.</P>
        <HD SOURCE="HD2">Economic and Paperwork Concerns</HD>
        <P>Many commenters stated that the proposed rule will cause a serious financial impact, especially on small businesses, which make up the majority of those affected. Several commenters stated that a cost-benefit study has not been conducted and asked that APHIS withdraw the rule until one has been conducted or until APHIS has evaluated whether the rule is truly necessary.</P>

        <P>A preliminary regulatory impact analysis was conducted for the proposed rule and a final regulatory impact analysis has been conducted for this rule. A summary of the final regulatory impact analysis appears in this document under the heading “Executive Orders 12866 and 13563 and Regulatory Flexibility Act.” The full analysis may be viewed on the Regulations.gov Web site (see footnote 1) or obtained by contacting the person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>. One of the components of the preliminary regulatory impact analysis is a cost-benefit analysis. APHIS has estimated that about 5 hours, on average, will be required by a facility to develop a contingency plan, using guides provided and recommended by APHIS. Depending on the size and type of regulated entity and its circumstances, this cost, in terms of the time needed to develop a contingency plan, will vary; some facilities will require less than 5 hours to develop their plans and other entities will require more time. APHIS estimates that it will take 4 to 6 hours to develop and document a contingency plan. We note that many large regulated entities, in particular, already have contingency plans. In addition to the costs associated with the development of a contingency plan, there may also be certain expenditures necessitated by the regulated entity's plan itself. As an example, a particular regulated entity's plan may call for a backup generator to supply electricity in case of a power outage. We expect such costs to total within a reasonable range given that we have largely left it up to the discretion of facilities to determine the best way to fulfill the contingency plan criteria provided in the proposed rule for their own unique circumstances (i.e., size, type of entity, location, etc.). The costs of developing a plan and related equipment purchases should be viewed in terms of the benefits of reduced risk of harm to the animals under a regulated entity's care when there is an emergency or disaster. A reasonably scaled contingency plan that has identified potential emergencies and natural disasters therefore contributes to a regulated entity's long-term operational strength and financial security. To the extent to which the animals held by a licensee or registrant represent a capital asset or business investment, we do not believe it is unreasonable to expect that entities will have already put in place measures to ensure the continued well-being of those animals. Thus, the actual amount of new costs incurred by regulated entities due solely to the identification of a need during the development of a contingency plan should not be significant.</P>
        <P>One commenter stated that the rule does not comply with the Regulatory Flexibility Act because it shifts the burden of investigating what would be required for a contingency plan to businesses. One commenter expressed concern that the Small Business Administration was not consulted when developing the proposed rule.</P>
        <P>The Regulatory Flexibility Act requires that Federal agencies endeavor to fit regulatory and informational requirements to the scale of the businesses, organizations, and governmental jurisdictions subject to regulation. To achieve this principle, agencies are required to solicit and consider flexible regulatory proposals and to explain the rationale for their actions to assure that such proposals are given serious consideration. APHIS recognizes that each regulated entity is the best judge of the particular measures that should be included in its contingency plan. APHIS is minimizing the burden of the rule for small entities by allowing each one to determine for itself how best to meet the requirements in accordance with the general criteria and guidance documents. APHIS also consulted with the Small Business Administration in the preparation of the proposed rule and this final rule.</P>
        <P>One commenter stated that since the rule is significant and an Initial Regulatory Flexibility Analysis was prepared that APHIS is required to publish a compliance guide which will help regulated industries comply with the regulation.</P>
        <P>The guidance document that we are making available concurrently with this rule will assist licensees and registrants in complying with the regulation. Any additional compliance guides will be posted on the APHIS Web site (see footnote 2) and made available to the public to further assist small entities in complying with this rule.</P>
        <P>Two commenters asked whether they would have to build additional alternative facilities, or, if not, what shelter would be acceptable on a temporary basis, and whether USDA is ready to help shoulder some of the costs until a facility can be repaired. One commenter expressed concern that they would need to purchase disaster insurance.</P>
        <P>We do not intend to require the building of alternative facilities. While the costs for development and execution of the plan are expected to be borne by the regulated entity, they will be determined based on the emergencies and potential natural disasters most likely to be experienced by the regulated entity. As stated previously, we expect that these costs will be reasonable. The purpose of a contingency plan is to help ensure that licensees and registrants are able to respond in a timely and appropriate manner should an emergency or disaster occur. Disaster insurance is not required by this rule, and promoting the purchase of disaster insurance is not an objective of this rule.</P>
        <P>Three commenters expressed concern that the number of animals lost during Hurricane Katrina as stated in the economic analysis of the proposed rule is greater than the total number of regulated animals in Louisiana.</P>
        <P>In the preliminary regulatory impact analysis, APHIS may have inadvertently implied that the number of animals covered under the Animal Welfare Act that were harmed or killed as a result of Hurricane Katrina was comparable to the 50,000 pets that reportedly were negatively impacted by the disaster. This is incorrect. There is a difference in scale between the number of animals for which pet owners are responsible versus the number of animals for which research facilities and other licensed and registered facilities are responsible. Therefore, AWA licensees and registrants caring for large numbers of animals who did not have contingency plans in place likely found it difficult to evacuate or otherwise ensure the animals' safety during Hurricane Katrina. Our intent in the proposed rule was to illustrate this fact rather than to compare the number of regulated animals negatively impacted to the number of pets that were negatively impacted. We have reexamined the available data and we present our findings in the full final regulatory flexibility analysis, which can be viewed on the Regulations.gov Web site (see the address listed in footnote 1).</P>
        <P>One commenter suggested that a tiered contingency plan system be implemented to accommodate small businesses.</P>

        <P>As a practical matter, one would expect that the smaller the business, the smaller the scale of the contingency<PRTPAGE P="76822"/>plan that the business would be expected to prepare, just as a large entity with numerous animals would require a larger scale, more complex contingency plan. Because we recognize that individual circumstances may be different between research facilities, dealers, exhibitors, carriers, and intermediate handlers, we have provided general contingency plan criteria and largely left it up to the discretion of regulated facilities to determine how best to fulfill the criteria. Because the response to each criterion will be appropriate to the size of each individual entity, it is reasonable to describe the contingency plan system provided for by this rule as tiered.</P>
        <P>Several commenters expressed concern regarding the costs of and time for drafting a contingency plan. One commenter stated that the rule may be imposing redundant paperwork requirements because of similar requirements at the State and local levels.</P>
        <P>Many regulated facilities are currently required to have contingency plans by other organizations (e.g., accrediting institutions, State and local regulators). Many of these plans will meet the proposed contingency plan requirements, and paperwork redundancies for entities with such plans should be minimal. Those regulated facilities that do not already have plans in place may incur an additional burden to develop contingency plans. However, we believe that having an established contingency plan promotes animal welfare and will aid in business continuity, therefore reducing the burden on facilities and regulated animals in the event of a natural disaster or emergency.</P>
        <P>Therefore, for the reasons given in the proposed rule and in this document, we are adopting the proposed rule as a final rule, with the changes discussed in this document.</P>
        <HD SOURCE="HD1">Executive Orders 12866 and 13563 and Regulatory Flexibility Act</HD>
        <P>This proposed rule has been determined to be significant/economically significant for the purposes of Executive Order 12866 and, therefore, has been reviewed by the Office of Management and Budget.</P>

        <P>We have prepared an economic analysis for this rule. The economic analysis provides a cost-benefit analysis, as required by Executive Orders 12866 and 13563, which direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, and equity). Executive Order 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. The economic analysis also examines the potential economic effects of this rule on small entities, as required by the Regulatory Flexibility Act. The economic analysis is summarized below. Copies of the full analysis are available on the Regulations.gov Web site (see footnote 1 in this document for a link to Regulations.gov) or by contacting the person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>.</P>
        <P>Preparedness for emergencies and disasters can reduce the harm to animals and their loss of life. The devastating impact of the 2005 hurricane season underscores the need for contingency planning for all animals covered under the Animal Welfare Act. Currently, only facilities that house marine mammals are required under 9 CFR 3.101 to develop contingency plans. The final rule requires that all of the more than 10,000 licensees and registrants develop and document contingency plans for all other animals covered under the Act. In addition, training to carry out contingency plans will be required of a regulated entity's employees. The majority of establishments that will be affected by this rule are small, based on industry estimates obtained from the Economic Census and the Census of Agriculture.</P>
        <P>The full final regulatory flexibility analysis identifies breeders, wholesale dealers, licensed and registered exhibitors, registered research facilities, and registered transport carriers and handlers as those entities most likely to be impacted by the requirement for the development of contingency plans. While no economic data are available on business size for the specific entities, we may assume the majority of the potentially impacted establishments are small, based on the industry estimates obtained from the Economic Census and the Census of Agriculture.</P>
        <P>The final rule will impose certain costs to develop and document the contingency plans and provide employee training, but these costs are not expected to be excessive. The cost of training personnel will vary depending on the type and size of business. However, many organizations offer training courses on general disaster planning specific to the type of animals at the particular facility or operation. FEMA offers free training, while some organizations offer courses with prices ranging from $50 to $300. These courses cover the development and implementation of contingency plans. In addition, many of the larger facilities, in particular, already have contingency plans in place. APHIS recognizes that each entity is the best judge of the particular measures that should be included in its contingency plan, and will provide general criteria and guidance documents to minimize compliance costs. Each entity will determine for itself how best to meet the rule's requirements.</P>
        <HD SOURCE="HD1">Executive Order 12372</HD>
        <P>This program/activity is listed in the Catalog of Federal Domestic Assistance under No. 10.025 and is subject to Executive Order 12372, which requires intergovernmental consultation with State and local officials. (See 7 CFR part 3015, subpart V.)</P>
        <HD SOURCE="HD1">Executive Order 12988</HD>
        <P>This final rule has been reviewed under Executive Order 12988, Civil Justice Reform. It is not intended to have retroactive effect. The Act does not provide administrative procedures which must be exhausted prior to a judicial challenge to the provisions of this rule.</P>
        <HD SOURCE="HD1">Paperwork Reduction Act</HD>

        <P>In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. 3501<E T="03">et seq.</E>), the information collection or recordkeeping requirements included in this rule have been approved by the Office of Management and Budget (OMB) under OMB control number 0579-0352.</P>
        <HD SOURCE="HD1">E-Government Act Compliance</HD>
        <P>The Animal and Plant Health Inspection Service is committed to compliance with the E-Government Act to promote the use of the Internet and other information technologies, to provide increased opportunities for citizen access to Government information and services, and for other purposes. For information pertinent to E-Government Act compliance related to this rule, please contact Mrs. Celeste Sickles, APHIS' Information Collection Coordinator, at (301) 851-2908.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <CFR>9 CFR Part 2</CFR>
          <P>Animal welfare, Pets, Reporting and recordkeeping requirements, Research.</P>
          <CFR>9 CFR Part 3</CFR>
          <P>Animal welfare, Marine mammals, Pets, Reporting and recordkeeping requirements, Research, Transportation.</P>
        </LSTSUB>
        
        <P>Accordingly, we are amending 9 CFR chapter I, subchapter A, as follows:</P>
        <REGTEXT PART="2" TITLE="9">
          <PART>
            <PRTPAGE P="76823"/>
            <HD SOURCE="HED">PART 2—REGULATIONS</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 2 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>7 U.S.C. 2131-2159; 7 CFR 2.22, 2.80, and 371.7.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="2" TITLE="9">
          <AMDPAR>2. Section 2.38 is amended by adding new paragraphs (i)(4) and (l) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 2.38</SECTNO>
            <SUBJECT>Miscellaneous.</SUBJECT>
            <STARS/>
            <P>(i) * * *</P>
            <P>(4) The other person or premises must either be directly included in the research facility's contingency plan required under paragraph (l) of this section or must develop its own contingency plan in accordance with paragraph (l) of this section.</P>
            <STARS/>
            <P>(l)<E T="03">Contingency planning.</E>(1) Research facilities must develop, document, and follow an appropriate plan to provide for the humane handling, treatment, transportation, housing, and care of their animals in the event of an emergency or disaster (one which could reasonably be anticipated and expected to be detrimental to the good health and well-being of the animals in their possession). Such contingency plans must:</P>
            <P>(i) Identify situations the facility might experience that would trigger the need for the measures identified in a contingency plan to be put into action including, but not limited to, emergencies such as electrical outages, faulty HVAC systems, fires, and animal escapes, as well as natural disasters the facility is most likely to experience.</P>
            <P>(ii) Outline specific tasks required to be carried out in response to the identified emergencies or disasters including, but not limited to, detailed animal evacuation instructions or shelter-in-place instructions and provisions for providing backup sources of food and water as well as sanitation, ventilation, bedding, veterinary care, etc.;</P>
            <P>(iii) Identify a chain of command and who (by name or by position title) will be responsible for fulfilling these tasks; and</P>
            <P>(iv) Address how response and recovery will be handled in terms of materials, resources, and training needed.</P>
            <P>(2) For current registrants, the contingency plan must be in place by July 29, 2013. For research facilities registered after this date, the contingency plan must be in place prior to conducting regulated activities. The plan must be reviewed by the research facility on at least an annual basis to ensure that it adequately addresses the criteria listed in paragraph (l)(1) of this section. Each registrant must maintain documentation of their annual reviews, including documenting any amendments or changes made to their plan since the previous year's review, such as changes made as a result of recently predicted, but historically unforeseen, circumstances (e.g., weather extremes). Contingency plans, as well as all annual review documentation and training records, must be made available to APHIS and any funding Federal agency representatives upon request. Facilities maintaining or otherwise handling marine mammals in captivity must also comply with the requirements of § 3.101(b) of this subchapter.</P>
            <P>(3) The facility must provide and document participation in and successful completion of training for its personnel regarding their roles and responsibilities as outlined in the plan. For current registrants, training of facility personnel must be completed by September 27, 2013; for research facilities registered after July 29, 2013, training of facility personnel must be completed within 60 days of the facility putting its contingency plan in place. Employees hired 30 days or more before the contingency plan is put in place must also be trained by that date. For employees hired less than 30 days before that date or after that date, training must be conducted within 30 days of their start date. Any changes to the plan as a result of the annual review must be communicated to employees through training which must be conducted within 30 days of making the changes.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="2" TITLE="9">
          <AMDPAR>3. Section 2.102 is amended by adding new paragraphs (a)(4) and (b)(3) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 2.102</SECTNO>
            <SUBJECT>Holding facility.</SUBJECT>
            <P>(a) * * *</P>
            <P>(4) The other person or premises must either be directly included in the dealer's or exhibitor's contingency plan required under § 2.134 or must develop its own contingency plan in accordance with § 2.134.</P>
            <P>(b) * * *</P>
            <P>(3) The other person or premises must either be directly included in the intermediate handler's contingency plan required under § 2.134 or must develop its own contingency plan in accordance with § 2.134.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="2" TITLE="9">
          <AMDPAR>4. A new section § 2.134 is added to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 2.134</SECTNO>
            <SUBJECT>Contingency planning.</SUBJECT>
            <P>(a) Dealers, exhibitors, intermediate handlers, and carriers must develop, document, and follow an appropriate plan to provide for the humane handling, treatment, transportation, housing, and care of their animals in the event of an emergency or disaster (one which could reasonably be anticipated and expected to be detrimental to the good health and well-being of the animals in their possession). Such contingency plans must:</P>
            <P>(1) Identify situations the licensee or registrant might experience that would trigger the need for the measures identified in a contingency plan to be put into action including, but not limited to, emergencies such as electrical outages, faulty HVAC systems, fires, mechanical breakdowns, and animal escapes, as well as natural disasters most likely to be experienced;</P>
            <P>(2) Outline specific tasks required to be carried out in response to the identified emergencies or disasters including, but not limited to, detailed animal evacuation instructions or shelter-in-place instructions and provisions for providing backup sources of food and water as well as sanitation, ventilation, bedding, veterinary care, etc.;</P>
            <P>(3) Identify a chain of command and who (by name or by position title) will be responsible for fulfilling these tasks; and</P>
            <P>(4) Address how response and recovery will be handled in terms of materials, resources, and training needed.</P>

            <P>(b) For current licensees and registrants, the contingency plan must be in place by July 29, 2013. For new dealers, exhibitors, intermediate handlers, and carriers licensed or registered after this date, the contingency plan must be in place prior to conducting regulated activities. The plan must be reviewed by the dealer, exhibitor, intermediate handler, or carrier on at least an annual basis to ensure that it adequately addresses the criteria listed in paragraph (a) of this section. Each licensee and registrant must maintain documentation of their annual reviews, including documenting any amendments or changes made to their plan since the previous year's review, such as changes made as a result of recently predicted, but historically unforeseen, circumstances (e.g., weather extremes). Contingency plans, as well as all annual review documentation and training records, must be made available to APHIS upon request. Traveling entities must carry a copy of their contingency plan with them at all times and make it available for APHIS inspection while in travel status. Dealers, exhibitors, intermediate handlers, and carriers maintaining or otherwise handling marine mammals in<PRTPAGE P="76824"/>captivity must also comply with the requirements of § 3.101(b) of this subchapter.</P>
            <P>(c) Dealers, exhibitors, intermediate handlers, and carriers must provide and document participation in and successful completion of training for personnel regarding their roles and responsibilities as outlined in the plan. For current licensees and registrants, training of dealer, exhibitor, intermediate handler, and carrier personnel must be completed by September 27, 2013. For new dealers, exhibitors, intermediate handlers, or carriers licensed or registered after July 29, 2013, training of personnel must be completed within 60 days of the dealer, exhibitor, intermediate handler, or carrier putting their contingency plan in place. Employees hired 30 days or more before their contingency plan is put in place must also be trained by that date. For employees hired less than 30 days before that date or after that date, training must be conducted within 30 days of their start date. Any changes to the plan as a result of the annual review must be communicated to employees through training which must be conducted within 30 days of making the changes.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="3" TITLE="9">
          <PART>
            <HD SOURCE="HED">PART 3—STANDARDS</HD>
          </PART>
          <AMDPAR>5. The authority citation for part 3 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>7 U.S.C. 2131-2159; 7 CFR 2.22, 2.80, and 371.7.</P>
          </AUTH>
          
          <AMDPAR>6. In § 3.101, paragraph (b) is amended by adding a new sentence at the end of the paragraph to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 3.101</SECTNO>
            <SUBJECT>Facilities, general.</SUBJECT>
            <STARS/>
            <P>(b) * * * Facilities handling marine mammals must also comply with the requirements of § 2.134 of this subchapter.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Done in Washington, DC, this 20th day of December 2012.</DATED>
          <NAME>Rebecca Blue,</NAME>
          <TITLE>Deputy Under Secretary for Marketing and Regulatory Programs.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31422 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-34-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Food Safety and Inspection Service</SUBAGY>
        <CFR>9 CFR Parts 317 and 381</CFR>
        <DEPDOC>[Docket No. FSIS-2012-0039]</DEPDOC>
        <RIN>RIN 0583-AD05</RIN>
        <SUBJECT>Uniform Compliance Date for Food Labeling Regulations</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Food Safety and Inspection Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Food Safety and Inspection Service (FSIS) is establishing January 1, 2016, as the uniform compliance date for new meat and poultry product labeling regulations that are issued between January 1, 2013, and December 31, 2014. FSIS periodically announces uniform compliance dates for new meat and poultry product labeling regulations to minimize the economic impact of label changes.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective December 31, 2012. Comments on this final rule must be received on or before January 30, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>FSIS invites interested persons to submit relevant comments on this proposed rule. Comments may be submitted by either of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal:</E>This Web site provides the ability to type short comments directly into the comment field on this Web page or attach a file for lengthier comments. Go to<E T="03">http://www.regulations.gov/.</E>Follow the online instructions at that site for submitting comments.</P>
          <P>•<E T="03">Mail, including CD-ROMs:</E>Send to Docket Clerk, U.S. Department of Agriculture (USDA), FSIS, OPPD, Patriots Plaza 3, 1400 Independence Avenue SW., Mailstop 3782, 8-163A, Washington, DC 20250-3700.</P>
          <P>•<E T="03">Hand- or courier-delivered items:</E>Send to Docket Clerk, U.S. Department of Agriculture (USDA), FSIS, OPPD, Patriots Plaza 3, 355 E. Street SW., 8-163A, Washington, DC 20250-3700.</P>
          <P>
            <E T="03">Instructions:</E>All items submitted by mail or electronic mail must include the Agency name and docket number FSIS-2012-0039. Comments received in response to this docket will be made available for public inspection and posted without change, including any personal information, to<E T="03">http://www.regulations.gov/.</E>
          </P>
          <P>
            <E T="03">Docket:</E>For access to background documents or comments received, go to the FSIS Docket Room at the address listed above between 8 a.m. and 4:30 p.m., Monday through Friday.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Rosalyn Murphy-Jenkins, Director, Labeling and Program Delivery Division, Office of Policy and Program Development, Food Safety and Inspection Service, U.S. Department of Agriculture, Telephone: 301-504-0879.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Background</HD>
        <P>FSIS periodically issues regulations that require changes in the labeling of meat and poultry food products. Many meat and poultry establishments also produce non-meat and non-poultry food products that are subject to the jurisdiction of the Food and Drug Administration (FDA). FDA also periodically issues regulations that require changes in the labeling of products under its jurisdiction.</P>
        <P>On December 14, 2004, FSIS issued a final rule that established January 1, 2008, as the uniform compliance date for new meat and poultry labeling regulations issued between January 1, 2005, and December 31, 2006. The 2004 final rule also provided that the Agency would set uniform compliance dates for new labeling regulations in 2-year increments and periodically issue final rules announcing those dates. Consistent with that final rule, the Agency has published three final rules establishing the uniform compliance dates of January 1, 2010, January 1, 2012, and January 1, 2014 (72 FR 9651, 73 FR 75564, and 75 FR 71344).</P>
        <HD SOURCE="HD1">The Final Rule</HD>
        <P>This final rule establishes January 1, 2016, as the uniform compliance date for new meat and poultry product labeling regulations that are issued between January 1, 2013 and December 31, 2014, and is consistent with the previous final rules that established uniform compliance dates. In addition, FSIS' approach for establishing uniform compliance dates for new food labeling regulations is consistent with FDA's approach. FDA is also planning to publish a final rule establishing a new compliance date.</P>
        <P>Two-year increments enhance the industry's ability to make orderly adjustments to new labeling requirements without unduly exposing consumers to outdated labels. With this approach, the meat and poultry industry is able to plan for use of label inventories and to develop new labeling materials that meet the requirements of all labeling regulations made within the two year period, thereby minimizing the economic impact of labeling changes.</P>

        <P>This compliance approach also serves consumers' interests because the cost of multiple short-term label revisions that<PRTPAGE P="76825"/>would otherwise occur would likely be passed on to consumers in the form of higher prices.</P>
        <P>FSIS encourages meat and poultry companies to comply with new labeling regulations as soon as it is feasible. If companies initiate voluntary label changes, they should consider incorporating any new requirements that have been published as final regulations.</P>
        <P>The new uniform compliance date will apply only to final FSIS regulations that require changes in the labeling of meat and poultry products and that are published after January 1, 2013, and before December 31, 2014. For each final rule that requires changes in labeling, FSIS will specifically identify January 1, 2016, as the compliance date. All meat and poultry food products that are subject to labeling regulations promulgated between January 1, 2013 and December 31, 2014, will be required to comply with these regulations when introduced into commerce on or after January 1, 2016. If any food labeling regulation involves special circumstances that justify a compliance date other than January 1, 2016, the Agency will determine an appropriate compliance date and will publish that compliance date in the rulemaking.</P>
        <P>In rulemaking that began with the May 4, 2004, proposed rule, FSIS provided notice and solicited comment on the concept of establishing uniform compliance dates for labeling requirements (69 FR 24539). In the March 5, 2007, final rule, FSIS noted that the Agency received only four comments in response to the proposal, all fully supportive of the policy to set uniform compliance dates. Therefore, in the March 5, 2007, final rule, FSIS determined that further rulemaking for the establishment of uniform compliance dates for labeling requirements is unnecessary (72 FR 9651). The Agency did not receive comments on the final rule. Consistent with its statement in 2007, FSIS finds at this time that further rulemaking on this matter is unnecessary. However, FSIS is providing an opportunity for comment on the uniform compliance date established in this final rule.</P>
        <HD SOURCE="HD1">Executive Order 12988</HD>
        <P>This final rule has been reviewed under the Executive Order 12988, Civil Justice Reform. Under this final rule: (1) All state and local laws and regulations that are inconsistent with this rule will be preempted; (2) no retroactive effect will be given to this rule; and (3) no retroactive proceedings will be required before parties may file suit in court challenging this rule.</P>
        <HD SOURCE="HD1">Executive Orders 12866 and 13563 and the Regulatory Flexibility Act</HD>
        <P>Executive Orders 12866 and 13563 direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). Executive Order (E.O.) 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. This final rule has been reviewed under E.O. 12866. The Office of Management and Budget (OMB) has determined that it is not a significant regulatory action under section 3(f) of E.O. 12866 and, therefore, it has not been reviewed by OMB.</P>
        <P>This rule does not have a significant economic impact on a substantial number of small entities; consequently, a regulatory flexibility analysis is not required (5 U.S.C. 601-612).</P>
        <HD SOURCE="HD1">Paperwork Requirements</HD>
        <P>There are no paperwork or recordkeeping requirements associated with this policy under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
        <HD SOURCE="HD1">E-Government Act Compliance</HD>

        <P>FSIS and USDA are committed to achieving the purposes of the E-Government Act (44 U.S.C. 3601,<E T="03">et seq.</E>) by, among other things, promoting the use of the Internet and other information technologies and providing increased opportunities for citizen access to Government information and services, and for other purposes.</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).</P>
        <HD SOURCE="HD1">Additional Public Notification</HD>

        <P>FSIS will announce this rule online through the FSIS Web page located at<E T="03">http://www.fsis.usda.gov/regulations_&amp;_policies/Interim_&amp;_Final_Rules/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 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>
        <SIG>
          <DATED>Done at Washington, DC, on: December 21, 2012.</DATED>
          <NAME>Alfred V. Almanza,</NAME>
          <TITLE>Administrator.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31398 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-DM-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
        <CFR>10 CFR Parts 429 and 431</CFR>
        <DEPDOC>[Docket Number EERE-2012-BT-CE-0048]</DEPDOC>
        <RIN>RIN 1904-AC90</RIN>
        <SUBJECT>Energy Conservation Program: Certification of Commercial and Industrial HVAC, Refrigeration and Water Heating Equipment</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of Energy Efficiency and Renewable Energy, Department of Energy.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The U.S. Department of Energy (DOE or the “Department”) is adopting amendments to the compliance dates for manufacturers to submit certification reports for certain commercial and industrial equipment covered under the Energy Policy and<PRTPAGE P="76826"/>Conservation Act of 1975, as amended (EPCA or the “Act”). Specifically, DOE is extending the compliance date for the certification provisions for commercial refrigeration equipment; commercial heating, ventilating, air-conditioning (HVAC) equipment; and commercial water heating (WH) equipment to December 31, 2013. DOE is extending the certification date for automatic commercial ice makers to August 1, 2013. Lastly, DOE is adopting a correction to the packaged terminal equipment standards table, which would impact standard-size packaged terminal air conditioners and packaged terminal heat pumps with a cooling capacity of 15,000 Btu/h.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective December 31, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>This rulemaking can be identified by docket number EERE-2012-BT-CE-0048 and/or RIN number 1904-AC90.</P>
          <P>
            <E T="03">Docket:</E>The docket is available for review at<E T="03">http://www.regulations.gov,</E>including<E T="04">Federal Register</E>notices, public meetings attendee lists, transcripts, comments, and other supporting documents/materials. All documents in the docket are listed in the<E T="03">http://www.regulations.gov</E>index. However, not all documents listed in the index may be publicly available, such as information that is exempt from public disclosure.</P>

          <P>For further information on how to submit or review public comments or view hard copies of the docket in the Resource Room, contact Ms. Brenda Edwards at (202) 586-2945 or email:<E T="03">Brenda.Edwards@ee.doe.gov.</E>
          </P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Ms. Ashley Armstrong, U.S. Department of Energy, Office of Energy Efficiency and Renewable Energy, Building Technologies Program, EE-2J, 1000 Independence Avenue SW., Washington, DC 20585-0121. Email:<E T="03">Ashley.Armstrong@ee.doe.gov;</E>and Ms. Laura Barhydt, U.S. Department of Energy, Office of the General Counsel, Forrestal Building, GC-32, 1000 Independence Avenue SW., Washington, DC 20585. Telephone: (202) 287-5772. Email:<E T="03">Laura.Barhydt@hq.doe.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Introduction</HD>
        <HD SOURCE="HD2">A. Authority</HD>
        <P>Title III of the Energy Policy and Conservation Act of 1975, as amended (“EPCA” or “the Act”) sets forth a variety of provisions designed to improve energy efficiency. Part A of Title III (42 U.S.C. 6291-6309) provides for the Energy Conservation Program for Consumer Products Other Than Automobiles. The National Energy Conservation Policy Act (NECPA), Public Law 95-619, amended EPCA to add Part A-1 of Title III, which established an energy conservation program for certain industrial equipment. (42 U.S.C. 6311-6317)<SU>1</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>1</SU>For editorial reasons, Parts B (consumer products) and C (commercial equipment) of Title III of EPCA were re-designated as parts A and A-1, respectively, in the United States Code.</P>
        </FTNT>

        <P>Sections 6299-6305, and 6316 of EPCA authorize DOE to enforce compliance with the energy and water conservation standards (all non-product specific references herein referring to energy use and consumption include water use and consumption; all references to energy efficiency include water efficiency) established for certain consumer products and commercial equipment. (42 U.S.C. 6299-6305 (consumer products), 6316 (commercial equipment)) DOE has promulgated enforcement regulations that include specific certification and compliance requirements.<E T="03">See</E>10 CFR part 429; 10 CFR part 431, subparts B, U, and V.</P>
        <HD SOURCE="HD2">B. Background</HD>
        <P>On March 7, 2011, DOE published a final rule in the<E T="04">Federal Register</E>that, among other things, modified the requirements regarding manufacturer submission of compliance statements and certification reports to DOE (March 2011 Final Rule). 76 FR 12421. This rule was largely procedural in nature; it did not amend pre-existing sampling provisions, test procedures, or conservation standard levels for any covered products or equipment. It did, however, impose new or revised reporting requirements for some types of covered products and equipment, including a requirement that manufacturers submit annual reports to the Department certifying compliance of their basic models with applicable standards. Finally, the Department emphasized that manufacturers could use their discretion in grouping individual models as a “basic model” such that the certified rating for the basic model matched the represented rating for all included models.<E T="03">See</E>76 FR 12428-12429 for more information. This reflected a basic requirement of the Department's longstanding self-certification compliance regime—that efficiency certifications and representations must be supported by either testing or an approved alternative method of estimating efficiency.</P>
        <P>The March 2011 Final Rule provided for the revised certification provisions to be effective on July 5, 2011. Certain manufacturers of particular types of commercial and industrial equipment<SU>2</SU>
          <FTREF/>stated that, for a variety of reasons, they would be unable to meet that deadline. As a result in a final rule published June 30, 2011, the Department extended the compliance date for certification of commercial refrigeration equipment; commercial HVAC equipment; commercial WH equipment; and walk-in coolers and freezers (June 30 Final Rule). 76 FR 38287 (June 30, 2011). DOE also acknowledged in the June 30 Final Rule that numerous manufacturers for certain types of commercial equipment appear to have been making representations of efficiency and determining compliance with the applicable energy conservation standards without testing products in accordance with all of the provisions of the DOE test procedures, which include sampling plans and certification testing tolerances.</P>
        <FTNT>
          <P>
            <SU>2</SU>These products included commercial warm air furnaces, commercial packaged boilers, and commercial air conditioners and heat pumps (collectively referred to as commercial HVAC equipment); commercial refrigeration equipment; commercial water heaters, commercial hot water supply boilers, and unfired hot water storage tanks (collectively referred to as commercial WH equipment); walk-in coolers; walk-in freezers; and automatic commercial ice makers.</P>
        </FTNT>
        <P>In the June 30 Final Rule, DOE stated that it believed 18 months would be sufficient to provide manufacturers with the time necessary to develop the data and supporting documentation needed to populate the certification reports and certify compliance with DOE's regulations, including the existing testing and sampling procedures. DOE also emphasized that all covered equipment must meet the applicable energy conservation standard and that all testing procedures and sampling provisions were unaffected by the final rule.</P>

        <P>On May 31, 2012, DOE published a proposed rule to revise and expand its regulations regarding alternative efficiency determination methods (AEDMs). (77 FR 32038). AEDMs reduce testing burdens by allowing manufacturers to use computer simulations, mathematical models, and other alternative methods to determine the amount of energy used or efficiency by a particular basic model. AEDM provisions for commercial HVAC equipment and commercial WH equipment already exist, but DOE has proposed to revise those regulations and to allow manufacturers of commercial refrigeration equipment to use AEDMs. DOE has not yet finalized the AEDM rulemaking.<E T="03">See</E>Docket EERE-2011-BT-TP-0024. The Department is also<PRTPAGE P="76827"/>reviewing recommendations regarding the feasibility of a negotiated rulemaking to revise the certification requirements for commercial HVAC equipment and commercial refrigeration equipment.<SU>3</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>3</SU>The U.S. Department of Energy Convening Report on the Feasibility of a Negotiated Rulemaking to Revise the Certification Program for Commercial Heating, Ventilating, Air Conditioning, and Commercial Refrigeration Equipment can be found at<E T="03">http://www.eere.energy.gov/buildings/appliance_standards/pdfs/convening_report_hvac_cre.pdf.</E>
          </P>
        </FTNT>
        <P>In an October 2012 letter to the Secretary of Energy, the Air Conditioning, Heating and Refrigeration Institute (AHRI) requested another certification compliance date extension. (AHRI, No. 1 at pp. 1-2). Specifically, AHRI requested that the compliance date for certification be extended a minimum of 18 months from the date of publication of the AEDM final rule.</P>
        <P>On December 6, 2012, the Department proposed to extend compliance date an additional 12 months for commercial refrigeration equipment; commercial HVAC equipment; and commercial WH equipment (December 2012 NOPR). 77 FR 72763. DOE requested comment on its assumption regarding the existence of test data and on whether a longer or shorter period of time would be more appropriate. DOE also proposed to modify the regulatory text to reflect that the compliance dates for certification requirements for walk-in coolers and freezers, distribution transformers, and metal halide lamp ballasts have passed by removing the delayed compliance dates.</P>
        <P>Lastly, the Department proposed to correct a technical drafting error for packaged terminal air conditioners and heat pumps that was implemented in the reprinting of Table 5 in 10 CFR 431.97 in a final rule published on May 16, 2012. 77 FR 28994. More specifically, DOE adopted changes to the applicable energy conservation standards for standard size and non-standard size packaged terminal air conditioners and heat pumps with a cooling capacity of 15,000 Btu/h. DOE proposed to correct this error and adopt the original standards for standard size and non-standard size packaged terminal air conditioners and heat pumps with a cooling capacity of 15,000 Btu/h as presented in a final rule evaluating and originally adopting the amended energy conservation for this equipment published on April 7, 2008. 73 FR 18915.</P>
        <HD SOURCE="HD1">II. Discussion of Comments</HD>
        <P>The Department received 14 written comments on the NOPR from a number of interested commenters, including various manufacturers, trade associations, and advocacy groups. The following parties submitted comments for this rule:</P>
        <GPOTABLE CDEF="s100,xs100,xs120" COLS="3" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Commenter name</CHED>
            <CHED H="1">Short name</CHED>
            <CHED H="1">Docket ID</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Air-Conditioning, Heating and Refrigeration Institute</ENT>
            <ENT>AHRI</ENT>
            <ENT>EERE-2012-BT-CE-0048-0001<LI>EERE-2012-BT-CE-0048-0014</LI>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="01">Seasons 4, Incorporated</ENT>
            <ENT>Seasons</ENT>
            <ENT>EERE-2012-BT-CE-0048-0004</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Scotsman Ice Systems</ENT>
            <ENT>Scotsman</ENT>
            <ENT>EERE-2012-BT-CE-0048-0005</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Hoshizaki America, Inc</ENT>
            <ENT>Hoshizaki</ENT>
            <ENT>EERE-2012-BT-CE-0048-0006</ENT>
          </ROW>
          <ROW>
            <ENT I="01">UTC Climate, Controls &amp; Security</ENT>
            <ENT>UTC</ENT>
            <ENT>EERE-2012-BT-CE-0048-0008</ENT>
          </ROW>
          <ROW>
            <ENT I="01">AAON, Inc</ENT>
            <ENT>AAON</ENT>
            <ENT>EERE-2012-BT-CE-0048-0009</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Ingersoll Rand</ENT>
            <ENT>Ingersoll Rand</ENT>
            <ENT>EERE-2012-BT-CE-0048-0010</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Lennox International, Inc</ENT>
            <ENT>Lennox</ENT>
            <ENT>EERE-2012-BT-CE-0048-0011</ENT>
          </ROW>
          <ROW>
            <ENT I="01">ASAP, ACEEE, ASE, and NRDC</ENT>
            <ENT>Joint Comment</ENT>
            <ENT>EERE-2012-BT-CE-0048-0012</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Rheem Manufacturing Company</ENT>
            <ENT>Rheem</ENT>
            <ENT>EERE-2012-BT-CE-0048-0013</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Traulsen &amp; Company</ENT>
            <ENT>Traulsen</ENT>
            <ENT>EERE-2012-BT-CE-0048-0015</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Burnham Commercial</ENT>
            <ENT>Burnham</ENT>
            <ENT>EERE-2012-BT-CE-0048-0016</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Goodman Manufacturing</ENT>
            <ENT>Goodman</ENT>
            <ENT>EERE-2012-BT-CE-0048-0017</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Mitsubishi Electric Cooling and Heating</ENT>
            <ENT>Mitsubishi</ENT>
            <ENT>EERE-2012-BT-CE-0048-0018</ENT>
          </ROW>
        </GPOTABLE>
        <HD SOURCE="HD2">A. Extension of Certification Deadline for Commercial Refrigeration Equipment; HVAC Equipment; and Commercial WH Equipment</HD>
        <P>As stated above, DOE proposed an additional 12-month extension to the compliance date for filing complete certification reports for manufacturers of commercial refrigeration equipment; commercial HVAC equipment; and commercial WH equipment. 77 FR 72763. Most commenters supported an extension of at least twelve months. (Seasons, No. 4 at p. 1; UTC, No. 8 at pp. 1-2; AAON, No. 9 at pp. 1-2; Ingersoll Rand, No. 10 at pp. 1-2; Lennox, No. 11 at pp. 1-2; Joint Comment, No. 12 at pp. 1-2; Rheem, No. 13 at p. 3; AHRI, No. 14 at p. 1; Traulsen, No. 15 at pp. 2-3, Burnham, No. 16 at p. 1; Goodman, No. 17 at pp. 1-2; and Mitsubishi, No. 18 at pp. 1-2)</P>

        <P>Many commenters believed that the compliance date should be tied to the completion of the AEDM rule. (Seasons, No. 4 at p. 1; UTC, No. 8 at pp 1-2; Lennox, No. 11 at p.2; Rheem, No. 13 at p. 3; AHRI, No. 14 at pp. 1-2, Traulsen, No. 15 at p. 2-3; Goodman, No. 17 at pp. 1-2; and Mitsubishi, No. 18 at pp. 1-2) Similarly, AAON commented that the AEDM rule would impact the length of the extension needed. (AAON, No. 9 at p. 2) In addition, AAON, Lennox AHRI, Goodman, and Mitsubishi commented that they believe that the compliance date should be extended a minimum of 18 months from the publication of the AEDM final rule. (AAON, No. 9 at p.2; Lennox, No. 11 at p.2; AHRI, No. 14 at p. 2; Goodman, No. 17 at pp. 1-2; and Mitsubishi, No. 18 at pp. 1-2) Goodman detailed a view shared by Seasons, UTC, AAON, Lennox, and AHRI that the length of the extension required would depend upon the actual results of the testing (due to measurement uncertainties, variances in testing set-ups and product variances) and the tolerances allowed by DOE (for both individual test-to-simulation results as well as average test-to-simulation results), additional testing or a significant amount of effort in development/specification of the internal AEDM procedure may be required. (Goodman, 17 at p. 1; Seasons, No. 4 at p. 1; UTC, No. 8 at pp. 1-2; AAON, No. 9 at p. 2; Lennox, No. 11 at p. 2 and AHRI, No. 14 at p. 2) Ingersoll Rand commented that it was concerned that a December 31, 2013 compliance date may not be sufficient to permit the Department to conduct a negotiated rulemaking and allow manufacturers to develop a means to comply with any modified requirements. (Ingersoll Rand, No. 10 at p. 1-2) In particular, Ingersoll Rand stated that it “hope[s] the Department recognizes [the December 2013 date] is only a stopgap measure, not truly a feasible date for future<PRTPAGE P="76828"/>compliance.” (Ingersoll Rand, No. 10 at p.2) Lennox also suggested that the compliance date should be aligned with the annual certification date for each product. (Lennox, No. 11 at pp. 2-3) Traulsen also supported extending the certification deadline stating that the commercial refrigeration industry may have collected energy consumption performance data for some base model of commercial refrigeration equipment, which may not be appropriate in all circumstances. (Traulsen, No. 15 at p. 2) Traulsen also noted that for certain low volume models of commercial refrigeration equipment current data may not be available because of previously conflicting priorities. (Id.) Mitsubishi also supported an 18-month extension from publication of the AEDM final rule and offered a specific path forward for the Department's consideration: (1) Finalize the AEDM rulemaking; (2) extend the certification compliance deadline for at least 18 months from the date of the AEDM final rule; (3) In the alternative, issue a written DOE Guidance Document regarding the delay of enforcement of commercial certification compliance until the AEDM rulemaking and accompanying extension are finalized; (4) begin the negotiated rulemaking process, which has already provided MEUS an opportunity to clarify the central issues and which is consistent with AHRI's proposed direction; and (5) develop a “basic model” definition that aligns with AHRI's definition—a basic model should be defined by the unit rather than levels of efficiency. (Id.)</P>
        <P>One commenter supported the 12-month extension as proposed by the Department without modification. Specifically, Burnham commented in favor of a compliance extension similar to that proposed by the AHRI organization regarding the publication of the AEDM final rule. However, Burmham also clarified that a shorter timeframe would be feasible as well. (Burnham, No. 16 at p. 1)</P>
        <P>Several commenters suggested that a significantly longer extension was needed. UTC noted that it believes an additional 12 to 36 months will be necessary after the issuance of a final AEDM rule prior to manufacturers being in a position to submit certification reports. (UTC, No. 8 at p.2) Hoshizaki requested a two-year extension for certification of commercial refrigeration equipment as it has not completed testing of its basic models and is waiting for DOE action on the AEDM rulemaking. (Hoshizaki, No. 6 at p. 1)</P>
        <P>In light of the comments above, DOE is extending the compliance date for the certification provisions for commercial refrigeration equipment; commercial warm air furnaces, commercial packaged boilers, and commercial air conditioners and heat pumps (collectively referred to as commercial HVAC equipment); and commercial water heaters, commercial hot water supply boilers, and unfired hot water storage tanks (collectively referred to as commercial WH equipment) to December 31, 2013. DOE believes 12 months is a reasonable extension and will allow DOE time to complete the AEDM rulemaking and allow manufacturers to develop ratings in accordance with any revised AEDM provisions.</P>
        <P>As noted above, the Department is reviewing the feasibility of a negotiated rulemaking to revise the certification requirements for commercial HVAC equipment and commercial refrigeration equipment. DOE is also considering the formation of an advisory committee in conjunction with such a rulemaking. Whether DOE proceeds with a negotiated rulemaking, and the outcome of a negotiated rulemaking, however, is uncertain. DOE believes that, should it proceed with a negotiated rulemaking, the process would, of its nature, involve discussion of any need to extend the new deadline further. Moreover, DOE believes that interested parties would raise the extension issue well in advance of December 31, 2013. Accordingly, DOE believes the 12-month extension is sufficient.</P>
        <P>Many commenters submitted additional thoughts regarding the AEDM rulemaking, about the definition of “basic model” and about the potential for a negotiated rulemaking. (AAON, No. 9 at p.1; Ingersoll Rand, No. 10 at p. 1-2; Joint Comment, No. 12 at pp. 1-2; Rheem, No. 13 at pp. 1-3; AHRI, No. 14 at pp. 1-2, Goodman, No. 17 at pp. 1-2, and Mitsubishi, No. 18 at p. 2) DOE appreciates the information provided by parties on these matters. The substance of these comments is the subject of other rulemakings and should be raised in those proceedings. This rulemaking is limited to an extension of the compliance date for the March 2011 certification provisions for commercial HVAC equipment, commercial WH equipment, and commercial refrigeration equipment.</P>
        <P>DOE emphasizes that the testing and sampling requirements for commercial refrigeration equipment; commercial HVAC equipment; and commercial WH equipment are unchanged by this extension. These regulations can be found on a per product basis in subpart B to part 429 (sampling plans for testing) and 10 CFR 431.64, 431.76, 431.86, 431.96, 431.106, and 431.134 (uniform test methods).</P>
        <HD SOURCE="HD2">B. Extension of Certification Deadline for Automatic Commercial Ice Makers</HD>
        <P>In the December 2012 NOPR, DOE initially proposed to retain the December 31, 2012 deadline to certify compliance but sought comment on whether an extension was needed. Several commenters requested a six-month extension of time for submitting certification reports for automatic commercial ice makers (ACIM). (Scotsman, No. 5 at p. 1; Hoshizaki, No. 6 at p. 1; AHRI, No. 14 at p. 2) Scotsman requested additional time to work with AHRI so that AHRI could build a database to collect the required information and submit the certification reports on Scotsman's behalf. (Scotsman, No. 5 at p. 1) Hoshizaki explained that it has the required test reports but that AHRI's portal for reporting test data is not ready. (Id.) Scotsman, however, indicated that it will need to conduct additional testing prior to submitting certification reports. (Scotsman, No. 5 at p. 1) AHRI requested a six-month extension to allow manufacturers time to complete testing. (AHRI, No. 14 at p. 2)</P>
        <P>Scotsman and Hoshizaki commented that DOE released the templates for certification of ACIM in December 2012 and stated that they did not have an automated process to provide many of the data elements contained in the templates. (Scotsman, No. 5 at p. 1; Hoshizaki, No. 6 at p. 1)</P>
        <P>Traulsen, on the other hand, noted that it did not have a concern with the Department's proposed certification deadline of December 31, 2012 for ACIMs even though it does not manufacture or supply this type of equipment. (Traulsen, No. 15 at p. 3)</P>

        <P>DOE expresses no view regarding an automated process that a regulated entity may develop to provide its certification reports. DOE notes that the data elements required for certification have been public since March 2011 and the CCMS templates for certification are available to manufacturers online. Given the concerns expressed by manufacturers, DOE is extending the compliance date for ACIM to align the compliance date with the next annual certification reporting date. Manufacturers would be required to submit only one certification report in 2013 for current basic models unless they implement design changes to those models resulting in lower efficiency or increased consumption. Consequently, DOE is adopting a compliance date of August 1, 2013, for submission of certification reports for ACIM.<PRTPAGE P="76829"/>
        </P>
        <HD SOURCE="HD2">C. Compliance and Enforcement</HD>
        <P>DOE emphasizes that all covered equipment must meet the applicable energy conservation standard. ASAP, ACEEE, ASE, and NRDC also noted in their joint comment that parties are not absolved of their obligations to comply with current standards and encouraged DOE to enforce those standards effectively. (Joint Comment, No. 12 at pp. 1-2) Furthermore, all testing procedures and sampling provisions are unaffected by this final rule. DOE is adopting a 12-month extension to the compliance date for certification only for the commercial refrigeration equipment; commercial HVAC equipment; and commercial WH equipment reporting requirements in the March 2011 final rule. DOE is adopting an 8-month extension to the compliance date for certification only for the ACIM reporting requirements in the March 2011 final rule.</P>
        <P>DOE encourages manufacturers to become familiar with the CCMS prior to the certification deadline. The CCMS has templates currently available for all covered equipment available for manufacturers to use when submitting certification data to DOE.</P>
        <P>DOE conducts assessment testing of products available for purchase in the United States, pursuant to 10 CFR 429.104. While certification is not required for commercial refrigeration equipment; commercial HVAC equipment; and commercial WH equipment until December 31, 2013, and for ACIM until August 1, 2013, DOE encourages manufacturers to submit to CCMS certification reports to DOE voluntarily prior to the compliance date required for certification. The Department will refrain from selecting models for assessment testing for which the manufacturer has submitted a valid certification report in CCMS. Specifically, in 2013, DOE will, in its enforcement discretion, limit any assessment testing of commercial refrigeration equipment, commercial HVAC equipment, commercial WH equipment, and automatic commercial ice makers to those models for which DOE does not have a valid certification report on file. If DOE purchases a unit for assessment testing prior to a manufacturer submitting a valid certification report, DOE will continue with the assessment test. A valid certification report is one that meets the requirements of 10 CFR part 429, including the manufacturer's determination of compliance being based either on testing in accordance with DOE sampling and test procedures (parts 429 and 431) or on the AEDM procedures in part 429.</P>
        <P>DOE will continue to conduct enforcement testing when it has a reason to believe that products do not meet the applicable standard. In addition, DOE will continue to conduct limited testing in support of its rulemaking activities for these equipment types. DOE will also continue to conduct verification testing in support of the ENERGY STAR program.</P>
        <P>AHRI commented that it supports DOE's enforcement policy. (AHRI, No. 14 at p. 2-3) DOE appreciates AHRI's support and notes that the enforcement policy is not tied to participation in a voluntary industry certification program and is based upon the voluntary submittal of a valid CCMS certification report to DOE in advance of the compliance date required for certification of the applicable equipment.</P>
        <HD SOURCE="HD2">D. Other Compliance Dates</HD>
        <P>DOE proposed to modify the regulatory text to reflect that the compliance dates for walk-in coolers and freezers, distribution transformers, and metal halide lamp ballasts have passed. DOE did not receive any comments on this proposal. Thus, DOE is adopting these amendments to 10 CFR 429.12(i).</P>
        <HD SOURCE="HD2">E. Technical Correction</HD>
        <P>The Department proposed to correct a technical drafting error for packaged terminal air conditioners and heat pumps that was implemented in the reprinting of Table 5 in 10 CFR 431.97 in a final rule published on May 16, 2012. 77 FR 28994. More specifically, DOE adopted changes to the applicable energy conservation standards for standard size and non-standard size packaged terminal air conditioners and heat pumps with a cooling capacity of 15,000 Btu/h. DOE did not receive any comments on this proposal.</P>
        <P>Consequently, DOE is correcting this error in today's final rule by adopting the original standards for standard size and non-standard size packaged terminal air conditioners and heat pumps with a cooling capacity of 15,000 Btu/h as presented in a final rule evaluating and originally adopting the amended energy conservation for this equipment published on April 7, 2008. 73 FR 18915.</P>
        <HD SOURCE="HD1">III. Procedural Issues and Regulatory Review</HD>
        <HD SOURCE="HD2">A. Review Under Executive Order 12866</HD>
        <P>Today's regulatory action is not a “significant regulatory action” under section 3(f) of Executive Order 12866. Accordingly, this action was not subject to review under the Executive Order by the Office of Information and Regulatory Affairs (OIRA) in the Office of Management and Budget (OMB).</P>
        <HD SOURCE="HD2">B. Administrative Procedure Act</HD>
        <P>DOE has determined, pursuant to authority at 5 U.S.C. 553(d)(1), that this final rule is not subject to a 30-day delay in effective date because this rule extending the compliance date for a requirement relieves a restriction.</P>
        <HD SOURCE="HD2">C. Review Under the Regulatory Flexibility Act</HD>
        <P>The Regulatory Flexibility Act (5 U.S.C. 601<E T="03">et seq.</E>) requires preparation of an initial regulatory flexibility analysis (IFRA) for any rule that by law must be proposed for public comment, unless the agency certifies that the rule, if promulgated, will not have a significant economic impact on a substantial number of small entities. As required by Executive Order 13272, “Proper Consideration of Small Entities in Agency Rulemaking,” 67 FR 53461 (August 16, 2002), DOE published procedures and policies on February 19, 2003, to ensure that the potential impacts of its rules on small entities are properly considered during the DOE rulemaking process. 68 FR 7990. DOE has made its procedures and policies available on the Office of the General Counsel's Web site:<E T="03">http://energy.gov/gc/office-general-counsel</E>.</P>
        <P>DOE reviewed this rule under the provisions of the Regulatory Flexibility Act and the procedures and policies published on February 19, 2003. This rule merely extends the compliance date of a rulemaking already promulgated. To the extent such action has any economic impact it would be positive in that it would allow regulated parties additional time to come into compliance. DOE did undertake a full regulatory flexibility analysis of the original Certification, Compliance, and Enforcement for Consumer Products and Commercial and Industrial Equipment rulemaking. That analysis considered the impacts of that rulemaking on small entities. As a result, DOE certifies that this rule will not have a significant economic impact on a substantial number of small entities.</P>
        <HD SOURCE="HD2">D. Review Under the National Environmental Policy Act</HD>

        <P>DOE has determined that this rule falls into a class of actions that are categorically excluded from review under the National Environmental Policy Act of 1969 (42 U.S.C. 4321<E T="03">et seq.</E>) and DOE's implementing<PRTPAGE P="76830"/>regulations at 10 CFR part 1021. Specifically, this rule amends an existing rule without changing its environmental effect and, therefore, is covered by the Categorical Exclusion in 10 CFR part 1021, subpart D, paragraph A5. Accordingly, neither an environmental assessment nor an environmental impact statement is required</P>
        <HD SOURCE="HD1">IV. Approval of the Office of the Secretary</HD>
        <P>The Secretary of Energy has approved publication of today's final rule.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <CFR>10 CFR Part 429</CFR>
          <P>Administrative practice and procedure, Energy conservation, Commercial equipment, Reporting and recordkeeping requirements.</P>
          <CFR>10 CFR Part 431</CFR>
          <P>Administrative practice and procedure, Energy conservation, Commercial equipment, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        <SIG>
          <DATED>Issued in Washington, DC, on December 26, 2012.</DATED>
          <NAME>Kathleen B. Hogan,</NAME>
          <TITLE>Deputy Assistant Secretary for Energy Efficiency, Energy Efficiency and Renewable Energy.</TITLE>
        </SIG>
        <P>For the reasons set forth in the preamble, DOE amends chapter II, subchapter D, of Title 10 of the Code of Federal Regulations to read as follows:</P>
        
        <REGTEXT PART="429" TITLE="10">
          <PART>
            <HD SOURCE="HED">PART 429—CERTIFICATION, COMPLIANCE, AND ENFORCEMENT FOR CONSUMER PRODUCTS AND COMMERCIAL AND INDUSTRIAL EQUIPMENT</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 429 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 6291-6317.</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="429" TITLE="10">
          <AMDPAR>2. Revise § 429.12 paragraph (i) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 429.12</SECTNO>
            <SUBJECT>General requirements applicable to certification reports.</SUBJECT>
            <STARS/>
            <P>(i)<E T="03">Compliance dates.</E>For any product subject to an applicable energy conservation standard for which the compliance date has not yet occurred, a certification report must be submitted not later than the compliance date for the applicable energy conservation standard. The covered products enumerated below are subject to the stated compliance dates for certification:</P>
            <P>(1) Automatic commercial ice makers, August 1, 2013;</P>
            <P>(2) Commercial refrigeration equipment, December 31, 2013;</P>
            <P>(3) Commercial heating, ventilating, and air-conditioning equipment, December 31, 2013; and</P>
            <P>(4) Commercial water heating equipment, December 31, 2013.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="431" TITLE="10">
          <PART>
            <HD SOURCE="HED">PART 431—ENERGY EFFICIENCY PROGRAM FOR CERTAIN COMMERCIAL AND INDUSTRIAL EQUIPMENT</HD>
          </PART>
          <AMDPAR>3. The authority citation for part 431 continues to read as follows:</AMDPAR>
          
        </REGTEXT>
        <REGTEXT PART="431" TITLE="10">
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 6291-6317.</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="431" TITLE="10">
          <AMDPAR>4. Revise Table 5 to § 431.97 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 431.97</SECTNO>
            <SUBJECT>Energy efficiency standards and their compliance dates.</SUBJECT>
            <STARS/>
            <GPOTABLE CDEF="xs40,xs72,r50,r50,xs72" COLS="05" OPTS="L2,i1">
              <TTITLE>Table 5 to § 431.97—Updated Minimum Efficiency Standards for PTAC and PTHP</TTITLE>
              <BOXHD>
                <CHED H="1">Equipment type</CHED>
                <CHED H="1">Cooling capacity</CHED>
                <CHED H="1">Sub-category</CHED>
                <CHED H="1">Efficiency level</CHED>
                <CHED H="1">Compliance date: Products manufactured on and after . . .</CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">PTAC</ENT>
                <ENT>Standard Size</ENT>
                <ENT>&lt;7,000 Btu/h</ENT>
                <ENT>EER = 11.7</ENT>
                <ENT>October 8, 2012.</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
                <ENT O="xl"/>
                <ENT>≥7,000 Btu/h and ≤15,000 Btu/h</ENT>
                <ENT>EER = 13.8 − (0.3 × Cap<SU>1</SU>)</ENT>
                <ENT>October 8, 2012.</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
                <ENT O="xl"/>
                <ENT>&gt;15,000 Btu/h</ENT>
                <ENT>EER = 9.3</ENT>
                <ENT>October 8, 2012.</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
                <ENT>Non-Standard Size</ENT>
                <ENT>&lt;7,000 Btu/h</ENT>
                <ENT>EER = 9.4</ENT>
                <ENT>October 7, 2010.</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
                <ENT O="xl"/>
                <ENT>≥7,000 Btu/h and ≤15,000 Btu/h</ENT>
                <ENT>EER = 10.9 − (0.213 × Cap<SU>1</SU>)</ENT>
                <ENT>October 7, 2010.</ENT>
              </ROW>
              <ROW RUL="s">
                <ENT I="22"/>
                <ENT O="xl"/>
                <ENT>&gt;15,000 Btu/h</ENT>
                <ENT>EER = 7.7</ENT>
                <ENT>October 7, 2010.</ENT>
              </ROW>
              <ROW>
                <ENT I="01">PTHP</ENT>
                <ENT>Standard Size</ENT>
                <ENT>&lt;7,000 Btu/h</ENT>
                <ENT>EER = 11.9<LI>COP = 3.3</LI>
                </ENT>
                <ENT>October 8, 2012.</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
                <ENT O="xl"/>
                <ENT>≥7,000 Btu/h and≤15,000 Btu/h</ENT>
                <ENT>EER = 14.0 − (0.3 × Cap<SU>1</SU>)<LI>COP = 3.7 − (0.052 × Cap<SU>1</SU>)</LI>
                </ENT>
                <ENT>October 8, 2012.</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
                <ENT O="xl"/>
                <ENT>&gt;15,000 Btu/h</ENT>
                <ENT>EER = 9.5<LI>COP = 2.9</LI>
                </ENT>
                <ENT>October 8, 2012.</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
                <ENT>Non-Standard Size</ENT>
                <ENT>&lt;7,000 Btu/h</ENT>
                <ENT>EER = 9.3<LI>COP = 2.7</LI>
                </ENT>
                <ENT>October 7, 2010.</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
                <ENT O="xl"/>
                <ENT>≥7,000 Btu/h and≤15,000 Btu/h</ENT>
                <ENT>EER = 10.8 − (0.213 × Cap<SU>1</SU>)<LI>COP = 2.9 − (0.026 × Cap<SU>1</SU>)</LI>
                </ENT>
                <ENT>October 7, 2010.</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
                <ENT O="xl"/>
                <ENT>&gt;15,000 Btu/h</ENT>
                <ENT>EER = 7.6<LI>COP = 2.5</LI>
                </ENT>
                <ENT>October 7, 2010.</ENT>
              </ROW>
              <TNOTE>
                <SU>1</SU>“Cap” means cooling capacity in thousand Btu/h at 95 °F outdoor dry-bulb temperature.</TNOTE>
            </GPOTABLE>
            <PRTPAGE P="76831"/>
            <STARS/>
          </SECTION>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31373 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6450-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
        <CFR>10 CFR Part 430</CFR>
        <DEPDOC>[Docket No. EERE-2011-BT-TP-0007]</DEPDOC>
        <RIN>RIN 1904-AC44</RIN>
        <SUBJECT>Energy Conservation Program for Consumer Products: Test Procedures for Residential Furnaces and Boilers (Standby Mode and Off Mode)</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of Energy Efficiency and Renewable Energy, Department of Energy.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In an earlier final rule, the U.S. Department of Energy (DOE) prescribed amendments to its test procedures for residential furnaces and boilers to include provisions for measuring the standby mode and off mode energy consumption of those products, as required by the Energy Independence and Security Act of 2007. These test procedure amendments were primarily based on provisions incorporated by reference from the International Electrotechnical Commission (IEC) Standard 62301 (First Edition), “Household electrical appliances—Measurement of standby power.” In this current final rule, DOE further amends its test procedure to incorporate by reference the latest edition of the IEC Standard, specifically IEC Standard 62301 (Second Edition). The new version of this IEC standard includes a number of methodological changes designed to increase accuracy while reducing testing burden. This final rule also clarifies the rounding guidance and sampling provisions for the new measurement of standby mode and off mode wattage.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective January 30, 2013. The incorporation by reference of certain publications listed in the rule is approved by the Director of the Federal Register on January 30, 2013.</P>
          <P>For purposes of compliance with energy conservation standards, compliance with the amended test procedures is required on and after May 1, 2013 (for non-weatherized gas and oil furnaces including mobile home furnaces, and all electric furnaces). The compliance date for any representations relating to standby mode and off mode of residential furnaces and boilers is July 1, 2013; on and after this date, any such representations must be based upon results generated under these test procedures and sampling plans.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The docket for this rulemaking is available for review at<E T="03">www.regulations.gov,</E>including<E T="04">Federal Register</E>notices, public meeting attendee lists and transcripts, comments, and other supporting documents/materials. All documents in the docket are listed in the<E T="03">www.regulations.gov</E>index. However, not all documents listed in the index may be publically available, such as information that is exempt from public disclosure.</P>
          <P>A link to the docket Web page can be found at:<E T="03">http://www.regulations.gov/#!docketDetail;dct=FR%252BPR%252BN%252BO%252BSR;rpp=25;po=0;D=EERE-2011-BT-TP-0007.</E>The<E T="03">www.regulations.gov</E>Web page contains simple instructions on how to access all documents, including public comments, in the docket.</P>

          <P>For further information on how to review the docket, contact Ms. Brenda Edwards at (202) 586-2945 or by email:<E T="03">Brenda.Edwards@ee.doe.gov.</E>
          </P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Mr. Mohammed Khan, U.S. Department of Energy, Office of Energy Efficiency and Renewable Energy, Building Technologies Program, EE-2J, 1000 Independence Avenue SW., Washington, DC, 20585-0121. Telephone: (202) 586-7892. Email:<E T="03">Mohammed.Khan@ee.doe.gov.</E>
          </P>

          <P>Mr. Eric Stas, U.S. Department of Energy, Office of the General Counsel, GC-71, 1000 Independence Avenue SW., Washington, DC, 20585-0121. Telephone: (202) 586-9507. Email:<E T="03">Eric.Stas@hq.doe.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Table of Contents</HD>
        <EXTRACT>
          <FP SOURCE="FP-2">I. Background and Authority</FP>
          <FP SOURCE="FP-2">II. Summary of the Final Rule</FP>
          <FP SOURCE="FP-2">III. Discussion</FP>
          <FP SOURCE="FP1-2">A. The September 2011 Proposed Rule</FP>
          <FP SOURCE="FP1-2">B. Public Comments on DOE's September 2011 Proposed Rule</FP>
          <FP SOURCE="FP1-2">1. Crown Boiler Comments</FP>
          <FP SOURCE="FP1-2">2. Air-Conditioning, Heating, and Refrigeration Institute Comments</FP>
          <FP SOURCE="FP-2">IV. Effective Date and Compliance Dates</FP>
          <FP SOURCE="FP-2">V. Compliance With Other EPCA Requirements</FP>
          <FP SOURCE="FP-2">VI. Procedural Issues and Regulatory Review</FP>
          <FP SOURCE="FP1-2">A. Review Under Executive Order 12866</FP>
          <FP SOURCE="FP1-2">B. Review Under the Regulatory Flexibility Act</FP>
          <FP SOURCE="FP1-2">C. Review Under the Paperwork Reduction Act of 1995</FP>
          <FP SOURCE="FP1-2">D. Review Under the National Environmental Policy Act of 1969</FP>
          <FP SOURCE="FP1-2">E. Review Under Executive Order 13132</FP>
          <FP SOURCE="FP1-2">F. Review Under Executive Order 12988</FP>
          <FP SOURCE="FP1-2">G. Review Under the Unfunded Mandates Reform Act of 1995</FP>
          <FP SOURCE="FP1-2">H. Review Under the Treasury and General Government Appropriations Act, 1999</FP>
          <FP SOURCE="FP1-2">I. Review Under Executive Order 12630</FP>
          <FP SOURCE="FP1-2">J. Review Under the Treasury and General Government Appropriations Act, 2001</FP>
          <FP SOURCE="FP1-2">K. Review Under Executive Order 13211</FP>
          <FP SOURCE="FP1-2">L. Review Under Section 32 of the Federal Energy Administration Act of 1974</FP>
          <FP SOURCE="FP1-2">M. Congressional Notification</FP>
          <FP SOURCE="FP-2">VII. Approval of the Office of the Secretary</FP>
        </EXTRACT>
        <HD SOURCE="HD1">I. Background and Authority</HD>
        <P>Title III, Part B<SU>1</SU>
          <FTREF/>of the Energy Policy and Conservation Act of 1975 (EPCA or the Act), Public Law 94-163 (42 U.S.C. 6291-6309, as codified) sets forth a variety of provisions designed to improve energy efficiency and established the Energy Conservation Program for Consumer Products Other Than Automobiles, a program covering most major household appliances, including residential furnaces and boilers (referenced below as one of the “covered products”).<SU>2</SU>
          <FTREF/>(42 U.S.C. 6292(a)(5) and 6295(f))</P>
        <FTNT>
          <P>
            <SU>1</SU>For editorial reasons, upon codification in the U.S. Code, Part B was redesignated Part A.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>2</SU>All references to EPCA in this rulemaking refer to the statute as amended through the Energy Independence and Security Act of 2007, Public Law 110-140.</P>
        </FTNT>
        <P>Under the Act, this program consists essentially of four parts: (1) Testing; (2) labeling; (3) Federal energy conservation standards; and (4) certification and enforcement procedures. The testing requirements consist of test procedures that manufacturers of covered products must use as the basis for certifying to DOE that their products comply with applicable energy conservation standards adopted pursuant to EPCA and for making representations about the efficiency of those products. (42 U.S.C. 6293(c); 42 U.S.C. 6295(s)) Similarly, DOE must use these test procedures in any enforcement action to determine whether covered products comply with these energy conservation standards. (42 U.S.C. 6295(s))</P>

        <P>Under 42 U.S.C. 6293, EPCA sets forth criteria and procedures for DOE's adoption and amendment of such test procedures. Specifically, EPCA provides that “[a]ny test procedures prescribed or amended under this section shall be reasonably designed to produce test results which measure energy efficiency, energy use * * * or estimated annual operating cost of a covered product during a representative average use cycle or period of use, as determined by the Secretary [of Energy], and shall not be unduly burdensome to conduct.” (42 U.S.C. 6293(b)(3)) In addition, if DOE determines that a test procedure amendment is warranted, it must publish proposed test procedures and offer the public an opportunity to present oral and written comments on them. (42 U.S.C. 6293(b)(2)) Finally, in<PRTPAGE P="76832"/>any rulemaking to amend a test procedure, DOE must determine “to what extent, if any, the proposed test procedure would alter the measured energy efficiency * * * of any covered product as determined under the existing test procedure.” (42 U.S.C. 6293(e)(1)) If DOE determines that the amended test procedure would alter the measured efficiency of a covered product, DOE must amend the applicable energy conservation standard accordingly. (42 U.S.C. 6293(e)(2))</P>
        <P>On December 19, 2007, the Energy Independence and Security Act of 2007 (EISA 2007), Public Law 110-140, was enacted. The EISA 2007 amendments to EPCA, in relevant part, require DOE to amend the test procedures for all covered products to include measures of standby mode and off mode energy consumption. Specifically, section 310 of EISA 2007 provides definitions of “standby mode” and “off mode” (42 U.S.C. 6295(gg)(1)(A)) and permits DOE to amend these definitions in the context of a given product (42 U.S.C. 6295(gg)(1)(B)). The statute requires integration of such energy consumption into the overall energy efficiency, energy consumption, or other energy descriptor for each covered product, unless the Secretary determines that: (1) The current test procedures for a covered product already fully account for and incorporate the standby mode and off mode energy consumption of the covered product; or (2) such an integrated test procedure is technically infeasible for a particular covered product, in which case the Secretary shall prescribe a separate standby mode and off mode energy use test procedure for the covered product, if technically feasible. (42 U.S.C. 6295(gg)(2)(A))</P>

        <P>Under the statutory provisions adopted by EISA 2007, any such amendment must consider the most current versions of IEC Standard 62301,<E T="03">Household electrical appliances—Measurement of standby power,</E>and IEC Standard 62087,<E T="03">Methods of measurement for the power consumption of audio, video, and related equipment</E>.<SU>3</SU>
          <FTREF/>
          <E T="03">Id.</E>At the time of enactment of EISA 2007, the most current versions of these standards were IEC Standard 62301 (First Edition 2005-06) and IEC Standard 62087 (First Edition 2002).</P>
        <FTNT>
          <P>

            <SU>3</SU>EISA 2007 directs DOE to also consider IEC Standard 62087 when amending its test procedures to include standby mode and off mode energy consumption.<E T="03">See</E>42 U.S.C. 6295(gg)(2)(A). However, IEC Standard 62087 addresses the methods of measuring the power consumption of audio, video, and related equipment. Accordingly, the narrow scope of this particular IEC standard reduces its relevance to today's final rule.</P>
        </FTNT>

        <P>DOE's current test procedure for residential furnaces and boilers is found at 10 CFR part 430, subpart B, appendix N,<E T="03">Uniform Test Method for Measuring the Energy Consumption of Furnaces and Boilers.</E>This procedure establishes a means for determining annual energy efficiency and annual energy consumption of these products. On October 20, 2010, DOE published a final rule in the<E T="04">Federal Register</E>(hereafter called the October 2010 final rule) amending the test procedures for residential furnaces and boilers to account for the standby mode and off mode energy consumption of these products, as required by EISA 2007. 75 FR 64621. For a more detailed procedural history of the test procedure rulemaking to address standby mode and off mode energy consumption of residential furnaces and boilers, please consult the October 2010 final rule.<E T="03">Id.</E>at 64622.</P>
        <HD SOURCE="HD1">II. Summary of the Final Rule</HD>

        <P>As discussed above, EISA 2007 amended EPCA to require that DOE test procedures for covered products include provisions for measuring standby mode and off mode energy consumption. (42 U.S.C. 6295(gg)(2)(A)) In establishing test procedures to address standby mode and off mode energy consumption, EISA 2007 requires consideration of the most current version of IEC Standard 62301 to support the added measurement provisions.<E T="03">Id.</E>In the October 2010 final rule, DOE amended its test procedures to prescribe the use of IEC Standard 62301, “Household electrical appliances—Measurement of standby power,” Publication 62301 First Edition 2005-06, which was the most current version of this standard at the time of its incorporation into the DOE regulations. This final rule fulfilled DOE's obligation under EISA 2007.</P>
        <P>However, since that time, DOE has continued to address the requirements of EISA 2007 as it relates to standby mode and off mode for other products. For example, DOE has issued similar test procedure amendments for other heating products (water heaters, direct heating equipment, and pool heaters), and during that rulemaking, commenters identified improvements to IEC Standard 62301 that were under development and nearly finalized. These commenters, representing both manufacturers and energy conservation advocacy groups, are presumably the same as those that would comment on the proposals for furnaces and boilers, and they supported the draft revisions to IEC Standard 62301 as applied to the other heating products. The second edition of IEC Standard 62301 has now been finalized. In the abstract of its January 27, 2011 publication, the IEC reports that the second edition provides practical improvement and possible reduction in testing burden. DOE has reviewed IEC Standard 62301 (Second Edition) and agrees that the second edition does provide for improvement in terms of measurement accuracy and, in addition, provides for possible reduced testing burden by allowing for direct meter reading techniques, where appropriate. DOE believes these improvements would be applicable to a variety of heating products, including furnaces and boilers, as well as the other heating products discussed above. Accordingly, after careful review, in a notice of proposed rulemaking (NOPR) published on September 13, 2011 (76 FR 56339; “the September 2011 NOPR”). DOE decided to exercise its discretion to consider incorporation of the revised version of the industry standard into the DOE test procedure for residential furnaces and boilers. (42 U.S.C. 6293(b)(2)) In the September 2011 NOPR, DOE proposed to incorporate by reference the second edition of the IEC Standard 62301 standard in its entirety, calling out the appropriate provisions of that standard in DOE's test procedure regulations for residential furnaces and boilers. 76 FR 56339, 56341 (Sept. 13, 2011). This proposal also clarified the rounding guidance and sampling provisions for the new measurements of standby mode and off mode wattage. A public meeting was held on October 3, 2011 to discuss and receive comments on the issues presented in the September 2011 NOPR. The comment period ended on November 28, 2011.</P>
        <HD SOURCE="HD1">III. Discussion</HD>
        <HD SOURCE="HD2">A. The September 2011 Proposed Rule</HD>

        <P>The September 2011 proposed rule was part of the continued efforts of DOE to address the requirements of EISA 2007 as it relates to standby mode and off mode for all covered products. In particular, after the standby mode and off mode amendments were developed for furnaces and boilers, DOE considered similar test procedure amendments for other heating products (water heaters, direct heating equipment, and pool heaters), and during that rulemaking, commenters identified improvements to IEC Standard 62301 that were under development and nearly finalized. These commenters, which are largely the same as those that would comment on the proposals for furnaces and boilers, supported the draft revisions to<PRTPAGE P="76833"/>IEC Standard 62301. The second edition of the standard has now been finalized. In the abstract of that finalized publication, the IEC reported that the second edition would provide practical improvement and possible reduction in testing burden. DOE reviewed IEC Standard 62301 (Second Edition) and agrees that the second edition does provide for improvement in terms of measurement accuracy and, in addition, provides for possible reduced testing burden by allowing for direct meter reading techniques where appropriate. DOE believes these improvements are applicable to a variety of heating products, including furnaces and boilers, as well as the other heating products mentioned above. Accordingly, after careful review, DOE decided to exercise its discretion to consider incorporation by reference of the revised version of the industry standard into the DOE test procedure for residential furnaces and boilers. (42 U.S.C. 6293(b)(2)) Thus, in the September 2011 NOPR, DOE proposed to incorporate into DOE's test procedure regulations the second edition of IEC Standard 62301 in its entirety, and call out the appropriate provisions of that standard in DOE's test procedure regulations for residential furnaces and boilers.</P>
        <P>More specifically, DOE's technical review of IEC Standard 62301 (Second Edition) determined that some improvement to the current DOE test procedure is possible with the incorporation of the second edition of the IEC standard as it applies to residential furnaces and boilers. First, a more comprehensive specification of required accuracy is provided in IEC Standard 62301 (Second Edition) that depends upon the characteristics of the power being measured. DOE believes that this most recent revision to the IEC standard provides improved and realistic accuracy provisions for a range of electricity consumption patterns, thereby making the updated test method appropriate for the variety of electricity-consuming devices that form part of residential furnaces and boilers. The new specification can be met by typical, commercially-available test equipment, whereas requirements in the first version may have necessitated specialized instrumentation that is not readily available.</P>
        <P>Another important change in IEC Standard 62301 (Second Edition) that relates to the measurement of standby mode and off mode power consumption in residential furnaces and boilers involves the specification of the stability criteria required to measure that power. IEC Standard 62301 (Second Edition) contains more detailed techniques to evaluate the stability of the power consumption and to measure the power consumption for loads with different stability characteristics. In IEC Standard 62301 (First Edition), the stability of the system is determined by measuring the power consumption over a 5-minute period. If the variation over that period is less than 5 percent, the signal is considered to be stable. There are potential operational modes, however, that could show variation over longer time frames. For example, an electronic component could go into a sleep mode after a 10-minute period. This change in power consumption would not be captured in the 5-minute stability test. IEC Standard 62301 (Second Edition) acknowledges the existence of these different types of modes by creating stability tests for these variable power modes. For constant power modes, the test method specified in the second edition of IEC Standard 62301 matches that specified in the first edition. For cyclical power consumption, the second edition of IEC Standard 62301 adds measurement provisions for situations in which the variation in the signal might not be constant over a 5-minute period. The power measurements would take at least 60 minutes; a test period of this duration is required to accurately capture standby mode and off mode energy consumption for equipment with varying power consumption and is an improvement introduced by IEC Standard 62301 (Second Edition) compared to IEC Standard 62301 (First Edition). These techniques will result in more complete and accurate measures of standby mode and off mode energy consumption over a variety of operational modes. The manufacturer is given a choice of measurement procedures, including less burdensome methods such as direct meter reading methods if certain clearly-described stability conditions are met. DOE believes that the changes incorporated in IEC Standard 62301 (Second Edition) will allow for use of less burdensome methods when appropriate and will ensure accurate measures of standby energy consumption over a range of operating conditions that may be present in residential furnaces and boilers.</P>
        <P>Accordingly, for the reasons discussed above, DOE proposed to incorporate IEC Standard 62301 (Second Edition) in its entirety into the overall list of incorporated references in 10 CFR 430.3 and to call out the appropriate provisions of that standard in DOE's test procedure regulations for residential furnaces and boilers.</P>

        <P>In addition, the September 2011 NOPR clarified that the rounding guidance in the IEC Standard 62301 (Second Edition) should be used for the new proposed wattage measurements. Specifically, it was proposed that the following sentence be added to the measurement provisions in sections 8.6.1 and 8.6.2: “The recorded standby power (P<E T="52">W,SB</E>) (or P<E T="52">W,OFF</E>where appropriate) shall be rounded to the second decimal place, and for loads greater than or equal to 10W, at least three significant figures shall be reported.” 76 FR 56339, 56342 (Sept. 13, 2011).</P>

        <P>Finally, DOE proposed to apply the existing DOE sampling plans used by residential furnace and boiler manufacturers to determine the representative values for annual energy consumption to the newly proposed standby mode and off mode ratings (P<E T="52">W,SB</E>and P<E T="52">W,OFF</E>).<E T="03">Id.</E>at 56342-43. For a more complete discussion of DOE's analysis of IEC Standard 62301 (Second Edition), see sections III.A through III.C of the September 2011 NOPR. 76 FR 56339, 56341-43 (Sept. 13, 2011).</P>
        <HD SOURCE="HD2">B. Public Comments on DOE's September 2011 Proposed Rule</HD>
        <P>In response to the September 2011 NOPR, DOE received very little in the way of comment on this matter. In particular, there was no objection expressed as to the use of the updated version of the IEC standard. Only two comments were received from Crown Boiler and the Air-Conditioning, Heating, and Refrigeration Institute (Crown, No. 5 and AHRI, No. 7, respectively), and they are discussed in detail below. In overview, these comments dealt with the overall burden of measuring standby mode and off mode energy consumption and the associated rounding guidance. No comments were received on the added clarification provisions related to sampling.</P>
        <HD SOURCE="HD3">1. Crown Boiler Comments</HD>

        <P>Comments from Crown Boiler were supportive of the September 2011 NOPR, in that the company agreed that the use of the second edition of IEC Standard 62301 in lieu of the first edition would result in reduced cost of testing. However, despite this reduction in cost, Crown Boiler opposed testing provisions for standby mode and off mode energy consumption generally, applying to both the current rulemaking and the October 2010 final rule, stating,<E T="03">“…[T]he rule imposes an undue regulatory burden on boiler manufacturers, given the fact that it is unlikely to result in any significant<PRTPAGE P="76834"/>reduction in energy use. In light is this, and in light of Executive Order 13563 (“Improving Regulations and Regulatory Review”), we believe that DOE should modify this rule</E>[in this case, the provisions prescribed by the October 2010 final rule]<E T="03">so that the burden it imposes is commensurate with the real-world benefit it provides (essentially none).”</E>(emphasis added) (Crown, No. 5 at p.1-2)</P>
        <P>Initially, DOE notes that most of Crown Boiler's comment involves provisions prescribed by the October 2010 final rule rather than those proposed in the September 2011 NOPR, which are matters beyond the scope of the current rulemaking. However, DOE is addressing the concerns of Crown Boiler here because of the interrelationship between these rules. Crown Boiler maintained that the energy savings potential associated with limiting the standby mode and off mode power consumption of residential boilers would be insignificant because of the small magnitude of energy consumption in these modes. In support of this position, Crown Boiler estimated that most residential boilers would consume less than 5W of standby mode and off mode power and that the annual shipments are only 400,000 units. In response, as summarized in the September 2011 NOPR and as Crown Boiler acknowledges, the EISA 2007 amendments to EPCA, in relevant part, statutorily require DOE to amend the test procedures for all covered products (including furnaces and boilers) to include measures of standby mode and off mode energy consumption. 76 FR 56339, 56341 (Sept. 13, 2011). Specifically, the statute requires integration of such energy consumption into the overall energy efficiency, energy consumption, or other energy descriptor for each covered product, unless the Secretary determines that: (1) The current test procedures for a covered product already fully account for and incorporate the standby mode and off mode energy consumption of the covered product; or (2) such an integrated test procedure is technically infeasible for a particular covered product, in which case the Secretary shall prescribe a separate standby mode and off mode energy use test procedure for the covered product, if technically feasible. (42 U.S.C. 6295(gg)(2)(A))</P>
        <P>Furthermore, although DOE realizes that, as pointed out by Crown Boiler, the level of standby mode and off mode energy consumption of boilers is inherently smaller than that of other products, such as forced air furnaces, it nevertheless represents a significant level of energy consumption when viewed in the aggregate. For example, the cost of annual standby mode and off mode energy consumption for the commenter's estimate of annual shipments (400,000 units) and wattage would be nearly $2 million each year for a single year's shipments of boilers (400,000 × 8000 hours × 5W × .00012 $/whr = $1.92 million). Some amount of this energy consumption could be limited by an applicable energy conservation standard in the future. This energy saving potential would be part of the analysis in support of such a standard. Accordingly, for these reasons, DOE cannot eliminate the integration of standby mode and off mode into the residential furnaces and boilers test procedures on the basis of insignificant energy savings potential.</P>
        <P>Crown Boiler also argued that the overall burden of conducting the additional tests for standby mode and off mode is significant for small businesses. The commenter specifically stated that the purchase cost of equipment needed to run the IEC Standard 62301 test is significant for small boiler manufacturers. On this matter, DOE certified in the October 2010 final rule that the added provisions to address standby mode and off mode energy consumption will not a have a significant economic impact on a significant number of small entities. 75 FR 64621, 64628-29 (Oct. 20, 2010). Furthermore, in the September 2011 NOPR, DOE tentatively certified that the possible additional burden represented by the adoption of the second edition of IEC Standard 62301 also would not have a significant economic impact on a substantial number of small entities. 76 FR 56339, 56343-44 (Sept. 13, 2011). In today's final rule, DOE affirms its certification, because it has concluded that the possible additional equipment cost for affected manufacturers is a small investment compared to manufacturers' overall financial investment needed to undertake the business enterprise of testing consumer products, including residential boilers.</P>

        <P>Crown Boiler also commented on the additional testing time that IEC Standard 62301 (Second Edition) may require on units with unstable readings. DOE analyzed this issue in the September 2011 NOPR and tentatively concluded that in the worst case, the labor costs associated with wait time during testing would result in a small additional cost of $30 per test unit.<E T="03">Id.</E>at 56344. Crown Boiler maintained that in addition to the possible labor cost, the waiting time would result in less availability for the test stand. In response, DOE does not view this as additional burden, since there is no provision in the rule that requires the standby mode and off mode measurements to be made on a particular test stand. Typically, a test stand for full efficiency testing of boilers would require fossil fuel and electricity connections, as well as venting arrangements. If such test stands are in demand, the standby mode and off mode testing could be done in a more convenient place where only an electrical connection is needed.</P>

        <P>In its comments, Crown Boiler argued that a second testing burden would arise from the need to separately test different controls systems on various boiler models for standby mode and off mode energy consumption. If, in fact, the energy consumption is different for each type of control system and there are numerous control system options applied to a given basic model, additional testing may be required for those basic models. However, this situation is not unlike any other design feature of a covered product that affects energy consumption. DOE believes this possible difference between control systems, and its potential additional testing costs, could be mitigated by the existing rules regarding conservative ratings, while still satisfying the requirement in EISA 2007 for incorporation into the DOE test procedures. In a recent rulemaking on certification, compliance, and enforcement, DOE clarified the conservative ratings concept within that final rule's discussion of the concept of “basic model.” 76 FR 12422, 12428-29 (March 7, 2011). Specifically, that discussion elaborated on the permitted flexibility in determining how manufacturers choose to group individual models into a basic model with essentially identical energy consumption characteristics. Generally, characteristics, such as different control systems, that have a small effect on overall energy consumption or efficiency need not constitute different basic models and, therefore, would not require additional separate testing. Rather, at the manufacturer's discretion, a basic model could include a variety of control systems, provided that the resulting rated energy consumption would be sufficiently conservative to account for the least-efficient model within the basic model. DOE believes it is reasonable to assume that the manufacturer can determine which control system would be likely to have the highest energy consumption, thereby allowing the manufacturer to avail itself of the conservative ratings in lieu of additional testing, if it so chooses.<PRTPAGE P="76835"/>
        </P>
        <P>Finally, Crown Boiler mentioned as a burden the differences in ambient air specifications between IEC Standard 62301 and the existing DOE test procedure. This is not a valid point, because the October 2010 final rule specifies, expressly to eliminate unnecessary burden, that the existing test procedure specification for ambient air is to be used for all testing. 75 FR 64621, 64623-25 (Oct. 20, 2010). Today's final rule does nothing to alter DOE's existing specifications for ambient temperature.</P>
        <P>In sum, the concerns raised by Crown Boiler have not demonstrated an undue burden associated with DOE's proposed standby mode and off mode measurement provisions, which have been adopted pursuant to DOE's mandate in EISA 2007.</P>

        <P>Although Crown Boiler would prefer the elimination of standby mode and off mode measurements for residential boilers, in the alternative, it requested consideration of some simplification of the measurement procedures. Specifically, Crown Boiler asked that in lieu of requiring the IEC Standard 62301 measurements, that manufacturers could be allowed, as an option, to assess the standby mode and off mode wattage with a preliminary and less sophisticated measurement procedure. More specifically, Crown Boiler suggested that if that value is below some threshold, the manufacturer would be allowed to report a conservative default value (<E T="03">i.e.,</E>a value greater than the measured value). If the preliminary value is above the relevant threshold, Crown Boiler suggested that the IEC Standard 62301 provisions must be used. Crown Boiler mentioned 7.5 watts and 10 watts as the threshold and default values respectively. This concept could have merit, in that it may reduce testing burden; however, it may not, in effect, be significantly different than the conservative rating concept discussed above. Specifically, the manufacturer, in its discretion, may assess the magnitude of the standby mode/off mode loss through limited testing and choose to make a conservative rating. Therefore, DOE believes the conservative rating allowance is a reasonable pathway for the commenter to use to reduce testing burden. Accordingly, DOE has concluded that there is not a compelling need to modify the test procedure to assign specific threshold and default values along with a defined, less-accurate test measurement procedure as the commenter suggested.</P>
        <HD SOURCE="HD3">2. Air-Conditioning, Heating, and Refrigeration Institute Comments</HD>

        <P>In addition to proposing the use of the second edition of IEC Standard 62301, the September 2011 NOPR provided rounding guidance applicable to the new measures of energy consumption for furnaces and boilers (<E T="03">i.e.,</E>P<E T="52">W,SB</E>and P<E T="52">W,OFF</E>). For these values, the September 2011 NOPR clarified that the rounding guidance provided in IEC Standard 62301 (Second Edition) would apply. 76 FR 56339, 56342, 56347 (Sept. 13, 2011). Specifically, DOE proposed to add the following sentence to the measurement provisions of the proposed regulatory text, where appropriate: “The recorded standby power (P<E T="52">W,SB</E>) (or off mode power P<E T="52">W,OFF</E>, where appropriate) shall be rounded to the second decimal place, and for loads greater than or equal to 10W, at least three significant figures shall be reported.”<E T="03">Id.</E>at 56342. DOE requested comments as to the adequacy and appropriateness of this clarification. Here, it is important to note that DOE has established energy conservation standards utilizing these power measurements (<E T="03">see</E>76 FR 37408 (June 27, 2011); 76 FR 67037 (Oct. 31, 2011)). These standards are expressed to two significant figures (<E T="03">i.e.,</E>10 watts P<E T="52">W,SB</E>(or off mode power P<E T="52">W,OFF</E>, where appropriate) for gas-fired and electric furnaces and 11 watts P<E T="52">W,SB</E>(or off mode power P<E T="52">W,OFF</E>, where appropriate) for oil-fired furnaces). Therefore, certification to these standards, utilizing the IEC rounding guidance, would likely require reporting to the second decimal place (<E T="03">i.e.,</E>values below the 10 watt level where the IEC rounding guidance requires three significant figures or the second decimal place). Only reported values between 11 watts and 10 watts for oil-fired and electric furnaces would be allowed a single decimal place report using the IEC rounding guidance. AHRI, in its comments, opined that the second decimal place rounding represents an unnecessary rounding burden on manufacturers without adding any value when one considers the annualized accounting of total electrical energy consumption as represented in the term E<E T="52">SO</E>. (AHRI No. 7 at p. 1-2)</P>

        <P>DOE believes that the IEC rounding provisions for wattage measurements are appropriate and within the capabilities of the instrumentation specified in the IEC standard. Specifically, DOE's review of IEC Standard 62301-compliant instrumentation has determined that one can easily support this level of reporting. Moreover, the test procedures for other DOE covered products already utilize IEC Standard 62301 for the wattage measurements, and DOE believes there is benefit in measuring the standby mode and off mode energy consumption of various covered products in a consistent manner for the various DOE requirements (<E T="03">i.e.,</E>annual consumption representations or standards compliance reports). In sum, carrying the IEC level of precision (three significant figures) through the annualized consumption calculations does not represent any additional burden, because it is simply a matter of running a calculation and reporting the result. Accordingly, DOE has concluded that this comment does not justify a departure from the IEC provisions, so DOE is adopting the rounding guidance as proposed.</P>
        <HD SOURCE="HD1">IV. Effective Date and Compliance Dates</HD>

        <P>The effective date for these amendments is January 30, 2013. At that time, representations may be made using the new metrics P<E T="52">W,SB</E>and P<E T="52">W,OFF</E>and any other measure of energy consumption which depends on P<E T="52">W,SB</E>and P<E T="52">W,OFF</E>, which were adopted pursuant to these amendments. The compliance date for any representations relating to standby mode and off mode energy consumption of residential furnaces and boilers is July 1, 2013; on and after this date, any such representations must be based upon results generated under these test procedures and sampling plans.</P>
        <P>However, DOE is clarifying here that use of these test procedure amendments related to standby mode and off mode energy consumption are not required for purposes of energy conservation standards compliance until May 1, 2013 (for non-weatherized gas and oil furnaces including mobile home furnaces, and all electric furnaces); this is the compliance date of the recently amended energy conservation standards for residential furnaces, which include standards for standby mode and off mode energy consumption. 76 FR 37408 (June 27, 2011); 76 FR 67037 (Oct. 31, 2011). Again, DOE makes this statement with the caveat that the amended standards only apply to furnaces and not boilers. Amended energy conservation standards addressing standby mode and off mode for boilers will be addressed and apply on the compliance date for the next energy conservation standards rulemaking for those products.</P>
        <HD SOURCE="HD1">V. Compliance With Other EPCA Requirements</HD>

        <P>EPCA requires that any test procedures prescribed or amended must<PRTPAGE P="76836"/>be reasonably designed to produce test results which measure energy efficiency, energy use, or estimated annual operating cost of a covered product during a representative average use cycle or period of use, and it must not be unduly burdensome to conduct. (42 U.S.C. 6293(b)(3)) If DOE amends its test procedures, it must determine to what extent, if any, the proposed test procedure would alter the measured energy efficiency or energy use of the covered product, as determined under the existing test procedure. (42 U.S.C. 6293(e)(1)) If DOE determines that the amended test procedure would alter the measured energy efficiency or energy use, it must amend the applicable energy conservation standard to reflect the average energy efficiency or energy use, as determined using the amended test procedure. (42 U.S.C. 6293(e)(2))</P>
        <P>Today's amendments to the DOE test procedure for residential furnaces and boilers incorporates the most current version of IEC Standard 62301 in lieu of the previous version. DOE has concluded that these new provisions will continue to produce valid test results, while reducing testing burden. Accordingly, this final rule meets the requirements of 42 U.S.C. 6293(b)(3).</P>

        <P>In addition, DOE has determined that these amendments will not alter the measured efficiency or energy use when determining compliance with the current energy conservation standards for these products or with future standards related to standby mode and off mode for furnaces. Accordingly, no modifications to the currently applicable energy conservation standards are required. This is because the currently applicable energy conservation standard is based on the annual fuel utilization efficiency (AFUE) metric which does not include or depend on the new measures of energy consumption regarding standby mode and off mode. In addition, consistent with its mandate pursuant to EISA 2007, DOE is further clarifying here that use of these test procedure amendments related to standby mode and off mode energy consumption are not required for purposes of energy conservation standards compliance,<E T="03">until the compliance date of the next standards final rule that addresses standby mode and off mode.</E>As noted above, DOE has adopted amended energy efficiency standards, as well as standby mode and off mode energy conservation standards, for residential furnaces (but not boilers). 76 FR 37408 (June 27, 2011); 76 FR 67037 (Oct. 31, 2011).</P>
        <P>Lastly, DOE does not believe that these test procedure amendments, which adopt a revised version of the IEC test procedure, would significantly alter the energy consumption as measured by the existing DOE test procedure provisions related to standby mode and off mode for residential furnaces and boilers, because the test procedure provisions of IEC Standard 62301 (Second Edition) are limited to providing additional accuracy for the measurements and clarification on the test method. Consequently, DOE does not believe that potential adoption of amendments pertaining to these clarifications and additions would alter any estimates of energy consumption under either DOE's current energy conservation standards or the recently promulgated amended standards.</P>
        <HD SOURCE="HD1">VI. Procedural Issues and Regulatory Review</HD>
        <HD SOURCE="HD2">A. Review Under Executive Order 12866</HD>
        <P>The Office of Management and Budget has determined that test procedure rulemakings do not constitute “significant regulatory actions” under section 3(f) of Executive Order 12866, “Regulatory Planning and Review.” 58 FR 51735 (Oct. 4, 1993). Accordingly, this regulatory action was not subject to review under the Executive Order by the Office of Information and Regulatory Affairs (OIRA) in the Office of Management and Budget (OMB).</P>
        <HD SOURCE="HD2">B. Review Under the Regulatory Flexibility Act</HD>
        <P>The Regulatory Flexibility Act (5 U.S.C. 601<E T="03">et seq.,</E>as amended by the Small Business Regulatory Enforcement Fairness Act of 1996) requires preparation of an initial regulatory flexibility analysis for any rule that, by law, must be proposed for public comment, unless the agency certifies that the rule, if promulgated, will not have a significant economic impact on a substantial number of small entities. A regulatory flexibility analysis examines the impact of the rule on small entities and considers alternative ways of reducing negative effects. Also, as required by Executive Order 13272, “Proper Consideration of Small Entities in Agency Rulemaking,” 67 FR 53461 (August 16, 2002), DOE published procedures and policies on February 19, 2003, to ensure that the potential impacts of its rules on small entities are properly considered during the DOE rulemaking process. 68 FR 7990. DOE has made its procedures and policies available on the Office of the General Counsel's Web site at<E T="03">www.gc.doe.gov/gc/office-general-counsel.</E>
        </P>
        <P>Today's final rule adopts test procedure provisions to measure standby mode and off mode energy consumption of residential furnaces and boilers, generally through the incorporation by reference of IEC Standard 62301 (Second Edition). DOE reviewed today's final rule under the provisions of the Regulatory Flexibility Act and the policies and procedures published on February 19, 2003. For the reasons explained below, DOE certifies that the final rule will not have a significant impact on a substantial number of small entities.</P>
        <P>As noted above, the test procedure incorporates by reference provisions from IEC Standard 62301 for the measurement of standby mode and off mode energy consumption. IEC Standard 62301 is widely accepted and used internationally to measure electric power in standby mode and off mode.</P>
        <P>Based on its analysis of IEC Standard 62301 (Second Edition), DOE has determined that the only possible additional burden represented by the adoption of IEC Standard 62301 (Second Edition) is associated with the testing time. For measurements of power consumption that are determined to be stable, test time would not change. Test time would increase under IEC Standard 62301 (Second Edition), as compared to IEC Standard 62301 (First Edition), should the stability test indicate that the power is being used in a variable manner. For these cases, the revised procedure would increase the time of measurement from the current 15 minutes to up to 60 minutes. No additional setup time would be required for these tests. This possible increase in test time does not necessarily require active labor, because no additional set up is required, and the additional time essentially amounts to a waiting period to determine stability. Nonetheless, assuming the 45 minutes additional test time does incur additional labor cost, the worst-case estimate of an additional $30 per test unit is a small incremental change compared to the overall financial investment needed to undertake the business enterprise of testing consumer products. For these reasons, DOE does not believe that this final rule adds significant costs nor requires any significant investment in test facilities or new equipment.</P>

        <P>The Small Business Administration (SBA) considers an entity to be a small business if, together with its affiliates, it employs fewer than a threshold number of workers specified in 13 CFR part 121, which relies on size standards and codes established by the North American Industry Classification System (NAICS). The threshold number for NAICS classification 333415, which applies to Air-Conditioning and Warm<PRTPAGE P="76837"/>Air Heating Equipment and Commercial and Industrial Refrigeration Equipment Manufacturing (including residential furnaces and boilers), is 750 employees.<SU>4</SU>
          <FTREF/>DOE reviewed the Air-Conditioning, Heating, and Refrigeration Institute's Directory of Certified Product Performance for Residential Furnaces and Boilers (June 7, 2010),<SU>5</SU>
          <FTREF/>the ENERGY STAR Product Databases for Gas and Oil Furnaces (Jan. 4, 2010),<SU>6</SU>
          <FTREF/>the California Energy Commission's Appliance Database for Residential Furnaces and Boilers,<SU>7</SU>
          <FTREF/>and the Consortium for Energy Efficiency's Qualifying Furnace and Boiler List (2010).<SU>8</SU>
          <FTREF/>From this review, DOE found that there are approximately 14 small businesses in the furnace and boiler industry. Even though there are a significant number of small businesses within the furnace and boiler industry, DOE has concluded that the test procedure amendments contained in this final rule would not represent a substantial burden to any manufacturer, including small manufacturers, as explained above.</P>
        <FTNT>
          <P>

            <SU>4</SU>U.S. Small Business Administration, Table of Small Business Size Standards (Nov. 5, 2010) (Available at:<E T="03">http://www.sba.gov/sites/default/files/Size_Standards_Table.pdf)</E>.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>5</SU>The Air-Conditioning, Heating and Refrigeration Institute, Directory of Certified Product Performance (June 7, 2010) (Available at:<E T="03">http://www.ahridirectory.org/ahridirectory/pages/home.aspx)</E>.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>6</SU>The U.S. Environmental Protection Agency and the U.S. Department of Commerce, ENERGY STAR Furnaces—Product Databases for Gas and Oil Furnaces (Jan. 4, 2010) (Available at:<E T="03">http://www.energystar.gov/index.cfm?c=furnaces.pr_furnaces)</E>.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>7</SU>The California Energy Commission, Appliance Database for Residential Furnaces and Boilers (2010) (Available at:<E T="03">http://www.appliances.energy.ca.gov/QuickSearch.aspx)</E>.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>8</SU>Consortium of Energy Efficiency, Qualifying Furnace and Boiler List (2010) (Available at:<E T="03">http://www.cee1.org/gas/gs-ht/gs-ht-main.php3)</E>.</P>
        </FTNT>
        <P>Accordingly, DOE has not prepared a regulatory flexibility analysis for this rulemaking. DOE's certification and supporting statement of factual basis were provided to the Chief Counsel for Advocacy of the SBA for review under 5 U.S.C. 605(b). DOE did not receive any comments demonstrating a significant economic impact on any small entities. Thus, DOE reaffirms and certifies that this rule will not have a significant economic impact on a substantial number of small entities.</P>
        <HD SOURCE="HD2">C. Review Under the Paperwork Reduction Act of 1995</HD>

        <P>Today's final rule would impose no new information or recordkeeping requirements. Accordingly, OMB clearance is not required under the Paperwork Reduction Act. (44 U.S.C. 3501<E T="03">et seq.</E>)</P>
        <HD SOURCE="HD2">D. Review Under the National Environmental Policy Act</HD>

        <P>In this rule, DOE is amending the test procedure for residential furnaces and boilers to address measurement of the standby mode and off mode energy consumption of these products. DOE has determined that this final rule falls into a class of actions that are categorically excluded from review under the National Environmental Policy Act of 1969 (Pub. L. 91-190, codified at 42 U.S.C. 4321<E T="03">et seq.</E>), and DOE's implementing regulations at 10 CFR part 1021. Specifically, this final rule, which adopts an industry standard for measurement of standby mode and off mode energy consumption, amends an existing rule without changing its environmental effect, and, therefore, is covered by Categorical Exclusion A5 found in 10 CFR part 1021, subpart D, appendix A. Today's final rule does not affect the amount, quality, or distribution of energy usage, and, therefore, does not result in any environmental impacts.<SU>9</SU>
          <FTREF/>Accordingly, neither an environmental assessment nor an environmental impact statement is required.</P>
        <FTNT>
          <P>
            <SU>9</SU>Categorical Exclusion A5 provides: “Rulemaking interpreting or amending an existing rule or regulation that does not change the environmental effect of the rule or regulation being amended.”</P>
        </FTNT>
        <HD SOURCE="HD2">E. Review Under Executive Order 13132</HD>
        <P>Executive Order 13132, “Federalism,” imposes certain requirements on agencies formulating and implementing policies or regulations that preempt State law or that have Federalism implications. 64 FR 43255 (August 10, 1999). The Executive Order requires agencies to examine the constitutional and statutory authority supporting any action that would limit the policymaking discretion of the States, and to carefully assess the necessity for such actions. The Executive Order also requires agencies to have an accountable process to ensure meaningful and timely input by State and local officials in the development of regulatory policies that have Federalism implications. On March 14, 2000, DOE published a statement of policy describing the intergovernmental consultation process that it will follow in developing such regulations. 65 FR 13735. DOE has examined this final rule and has determined that it does not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. EPCA governs and prescribes Federal preemption of State regulations as to energy conservation for the products that are the subject of today's final rule. States can petition DOE for exemption from such preemption to the extent, and based on criteria, set forth in EPCA. (42 U.S.C. 6297(d)) Therefore, Executive Order 13132 requires no further action.</P>
        <HD SOURCE="HD2">F. Review Under Executive Order 12988</HD>
        <P>Regarding the review of existing regulations and the promulgation of new regulations, section 3(a) of Executive Order 12988, “Civil Justice Reform,” 61 FR 4729 (Feb. 7, 1996), imposes on Federal agencies the general duty to adhere to the following requirements: (1) eliminate drafting errors and ambiguity; (2) write regulations to minimize litigation; (3) provide a clear legal standard for affected conduct rather than a general standard; and (4) promote simplification and burden reduction. Regarding the review required by section 3(a), section 3(b) of Executive Order 12988 specifically requires that Executive agencies make every reasonable effort to ensure that the regulation: (1) Clearly specifies the preemptive effect, if any; (2) clearly specifies any effect on existing Federal law or regulation; (3) provides a clear legal standard for affected conduct while promoting simplification and burden reduction; (4) specifies the retroactive effect, if any; (5) adequately defines key terms; and (6) addresses other important issues affecting clarity and general draftsmanship under any guidelines issued by the Attorney General. Section 3(c) of Executive Order 12988 requires Executive agencies to review regulations in light of applicable standards in sections 3(a) and 3(b) to determine whether they are met or it is unreasonable to meet one or more of them. DOE has completed the required review and determined that, to the extent permitted by law, this rule meets the relevant standards of Executive Order 12988.</P>
        <HD SOURCE="HD2">G. Review Under the Unfunded Mandates Reform Act of 1995</HD>

        <P>Title II of the Unfunded Mandates Reform Act of 1995 (UMRA) (Pub. L. 104-4, codified at 2 U.S.C. 1501<E T="03">et seq.</E>) requires each Federal agency to assess the effects of Federal regulatory actions on State, local, and Tribal governments and the private sector. For regulatory actions likely to result in a rule that may cause expenditures by State, local, and Tribal governments, in the aggregate, or by the private sector, of $100 million or more in any one year (adjusted annually for inflation), section 202 of UMRA<PRTPAGE P="76838"/>requires a Federal agency to publish a written statement that estimates the resulting costs, benefits, and other effects on the national economy. (2 U.S.C. 1532(a) and (b)) Section 204 of UMRA also requires a Federal agency to develop an effective process to permit timely input by elected officers of State, local, and Tribal governments on a proposed “significant intergovernmental mandate.” UMRA also requires an agency plan for giving notice and opportunity for timely input to small governments that may be potentially affected before establishing any requirement that might significantly or uniquely affect them. On March 18, 1997, DOE published a statement of policy on its process for intergovernmental consultation under UMRA. 62 FR 12820. (This policy is also available at<E T="03">http://www.gc.doe.gov/gc/office-general-counsel</E>). Today's final rule, which modifies the current test procedures for residential furnaces and boilers, contains neither an intergovernmental mandate, nor a mandate that may result in the expenditure by State, local, and Tribal governments, or by the private sector, of $100 million or more in any year. Accordingly, no further assessment or analysis is required under the Unfunded Mandates Reform Act of 1995.</P>
        <HD SOURCE="HD2">H. Review Under the Treasury and General Government Appropriations Act, 1999</HD>
        <P>Section 654 of the Treasury and General Government Appropriations Act, 1999 (Pub. L. 105-277) requires Federal agencies to issue a Family Policymaking Assessment for any rule that may affect family well-being. Today's final rule amending DOE test procedures would not have any impact on the autonomy or integrity of the family as an institution. Accordingly, DOE has concluded that it is not necessary to prepare a Family Policymaking Assessment.</P>
        <HD SOURCE="HD2">I. Review Under Executive Order 12630</HD>
        <P>Pursuant to Executive Order 12630, “Governmental Actions and Interference with Constitutionally Protected Property Rights,” 53 FR 8859 (March 15, 1988), DOE has determined that this final rule will not result in any takings that might require compensation under the Fifth Amendment to the United States Constitution.</P>
        <HD SOURCE="HD2">J. Review Under the Treasury and General Government Appropriations Act, 2001</HD>
        <P>The Treasury and General Government Appropriations Act, 2001 (Pub. L. 106-554, codified at 44 U.S.C. 3516 note) provides for agencies to review most disseminations of information to the public under information quality guidelines established by each agency pursuant to general guidelines issued by OMB. OMB's guidelines were published at 67 FR 8452 (Feb. 22, 2002), and DOE's guidelines were published at 67 FR 62446 (Oct. 7, 2002). DOE has reviewed today's final rule under the OMB and DOE guidelines and has concluded that it is consistent with applicable policies in those guidelines.</P>
        <HD SOURCE="HD2">K. Review Under Executive Order 13211</HD>
        <P>Executive Order 13211, “Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use,” 66 FR 28355 (May 22, 2001), requires Federal agencies to prepare and submit to OMB a Statement of Energy Effects for any proposed significant energy action. A “significant energy action” is defined as any action by an agency that promulgated or is expected to lead to promulgation of a final rule, and that: (1) is a significant regulatory action under Executive Order 12866, or any successor order; and (2) is likely to have a significant adverse effect on the supply, distribution, or use of energy; or (3) is designated by the Administrator of OIRA as a significant energy action. For any proposed significant energy action, the agency must give a detailed statement of any adverse effects on energy supply, distribution, or use should the proposal be implemented, and of reasonable alternatives to the action and their expected benefits on energy supply, distribution, and use. Today's final rule is not a significant regulatory action under Executive Order 12866 or any successor order; will not have a significant adverse effect on the supply, distribution, or use of energy; and has not been designated by the Administrator of OIRA as a significant energy action. Therefore, DOE has determined that this rule is not a significant energy action. Accordingly, DOE has not prepared a Statement of Energy Effects for this rulemaking.</P>
        <HD SOURCE="HD2">L. Review Under Section 32 of the Federal Energy Administration Act of 1974</HD>

        <P>Under section 301 of the Department of Energy Organization Act (Pub. L. 95-91; 42 U.S.C. 7101<E T="03">et seq.</E>), DOE must comply with all laws applicable to the former Federal Energy Administration, including section 32 of the Federal Energy Administration Act of 1974 (Pub. L. 93-275), as amended by the Federal Energy Administration Authorization Act of 1977 (Pub. L. 95-70). (15 U.S.C. 788) Section 32 provides that where a proposed rule authorizes or requires use of commercial standards, the notice of proposed rulemaking must inform the public of the use and background of such standards. In addition, section 32(c) requires DOE to consult with the Attorney General and the Federal Trade Commission (FTC) concerning the impact of commercial or industry standards on competition.</P>

        <P>Certain of the amendments and revisions in this final rule incorporate testing methods contained in the following commercial standard, the International Electrotechnical Commission (IEC) Standard 62301, “Household electrical appliances—Measurement of standby power” (Second Edition 2011). DOE has evaluated this standard and is unable to conclude whether it fully complies with the requirements of section 32(b) of the Federal Energy Administration Act (<E T="03">i.e.,</E>that it was developed in a manner that fully provides for public participation, comment, and review). DOE has consulted with the Attorney General and the Chairman of the FTC concerning the impact on competition of requiring manufacturers to use the test methods contained in this standard, and neither recommended against incorporation of this standard.</P>
        <HD SOURCE="HD2">M. Congressional Notification</HD>
        <P>As required by 5 U.S.C. 801, DOE will report to Congress on the promulgation of today's final rule before its effective date. The report will state that it has been determined that the rule is not a “major rule” as defined by 5 U.S.C. 804(2).</P>
        <HD SOURCE="HD1">VII. Approval of the Office of the Secretary</HD>
        <P>The Secretary of Energy has approved publication of this final rule.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 10 CFR Part 430</HD>
          <P>Administrative practice and procedure, Confidential business information, Energy conservation, Household appliances, Imports, Incorporation by reference, Intergovernmental relations, Small businesses.</P>
        </LSTSUB>
        <SIG>
          <DATED>Issued in Washington, DC, on November 16, 2012.</DATED>
          <NAME>Kathleen B. Hogan,</NAME>
          <TITLE>Deputy Assistant Secretary for Energy Efficiency,Energy Efficiency and Renewable Energy.</TITLE>
        </SIG>
        <P>For the reasons stated in the preamble, DOE is amending part 430 of Chapter II, Subchapter D of Title 10 of the Code of Federal Regulations, as set forth below:</P>
        <REGTEXT PART="430" TITLE="10">
          <PART>
            <PRTPAGE P="76839"/>
            <HD SOURCE="HED">PART 430—ENERGY CONSERVATION PROGRAM FOR CONSUMER PRODUCTS</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 430 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 6291-6309; 28 U.S.C. 2461 note.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="430" TITLE="10">
          <SECTION>
            <SECTNO>§ 430.3</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. Section 430.3 is amended by:</AMDPAR>
          <AMDPAR>a. Removing, in paragraph (m)(1), the words “appendix I, and appendix N” and adding in its place “and appendix I”;</AMDPAR>
          <AMDPAR>b. Adding after “J2,” in paragraph (m)(2), “N,”.</AMDPAR>
          <AMDPAR>3. Appendix N to subpart B of part 430 is amended:</AMDPAR>
          <AMDPAR>a. By revising the second sentence of the introductory note.</AMDPAR>
          <AMDPAR>b. In section 2.4., by removing the phrase “(First Edition 2005-06)” and adding in its place “(Edition 2.0 2011-01)”;</AMDPAR>

          <AMDPAR>c. In section 8.6.1, by removing in the third sentence, the phrase “4.5<E T="03">Power measurement accuracy”</E>and adding in its place, the phrase “4.4<E T="03">Power measurement instruments”</E>and by adding a sentence at the end of the section.</AMDPAR>

          <AMDPAR>d. In section 8.6.2, by removing in the third sentence, the phrase “4.5<E T="03">Power measurement accuracy”</E>and adding in its place the phrase “<E T="03">4.4 Power measurement instruments”,</E>and by adding a sentence at the end of the section.</AMDPAR>
          <P>The additions and revisions read as follows:</P>
          <HD SOURCE="HD1">Appendix N to Subpart B of Part 430—Uniform Test Method for Measuring the Energy Consumption of Furnaces and Boilers</HD>
          
          <EXTRACT>
            <NOTE>
              <HD SOURCE="HED">Note:</HD>
              <P>* * * However, any representation related to standby mode and off mode energy consumption of these products made after July 1, 2013 must be based upon results generated under this test procedure, consistent with the requirements of 42 U.S.C. 6293(c)(2). * * *</P>
            </NOTE>
            <STARS/>
            <P>
              <E T="03">8.6.1Standby power measurement.</E>* * * The recorded standby power (P<E T="52">W,SB</E>) shall be rounded to the second decimal place, and for loads greater than or equal to 10W, at least three significant figures shall be reported.</P>
            <P>
              <E T="03">8.6.2.Off mode power measurement.</E>* * * The recorded off mode power (P<E T="52">W,OFF</E>) shall be rounded to the second decimal place, and for loads greater than or equal to 10W, at least three significant figures shall be reported.</P>
            <STARS/>
          </EXTRACT>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31175 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6450-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">BUREAU OF CONSUMER FINANCIAL PROTECTION</AGENCY>
        <CFR>12 CFR Part 1003</CFR>
        <DEPDOC>[Docket No. CFPB-2012-0049]</DEPDOC>
        <SUBJECT>Home Mortgage Disclosure (Regulation C): Adjustment To Asset-Size Exemption Threshold</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Bureau of Consumer Financial Protection.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule; official commentary.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Bureau of Consumer Financial Protection (Bureau) is publishing a final rule amending the official commentary that interprets the requirements of the Bureau's Regulation C (Home Mortgage Disclosure) to reflect a change in the asset-size exemption threshold for banks, savings associations, and credit unions based on the annual percentage change in the Consumer Price Index for Urban Wage Earners and Clerical Workers (CPI-W). The exemption threshold is adjusted to increase to $42 million from $41 million. The adjustment is based on the 2.23 percent increase in the average of the CPI-W for the 12-month period ending in November 2012. Therefore, banks, savings associations, and credit unions with assets of $42 million or less as of December 31, 2012, are exempt from collecting data in 2013.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This final rule is effective December 31, 2012.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Joan Kayagil, Senior Counsel, Office of Regulations, at (202) 435-7700.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background</HD>
        <P>The Home Mortgage Disclosure Act of 1975 (HMDA) (12 U.S.C. 2801-2810) requires most mortgage lenders located in metropolitan areas to collect data about their housing-related lending activity. Annually, lenders must report those data to the appropriate Federal agencies and make the data available to the public. The Bureau's Regulation C (12 CFR part 1003) implements HMDA.</P>

        <P>Prior to 1997, HMDA exempted certain depository institutions as defined in HMDA (<E T="03">i.e.,</E>banks, savings associations, and credit unions) with assets totaling $10 million or less as of the preceding year-end. In 1996, HMDA was amended to expand the asset-size exemption for these depository institutions. 12 U.S.C. 2808(b). The amendment increased the dollar amount of the asset-size exemption threshold by requiring a one-time adjustment of the $10 million figure based on the percentage by which the CPI-W for 1996 exceeded the CPI-W for 1975, and it provided for annual adjustments thereafter based on the annual percentage increase in the CPI-W, rounded to the nearest multiple of $1 million dollars.</P>
        <P>The definition of “financial institution” in Regulation C provides that the Bureau will adjust the asset threshold based on the year-to-year change in the average of the CPI-W, not seasonally adjusted, for each 12-month period ending in November, rounded to the nearest million. 12 CFR 1003.2. For 2012, the threshold was $41 million. During the 12-month period ending in November 2012, the CPI-W increased by 2.23 percent. As a result, the exemption threshold is increased to $42 million. Thus, banks, savings associations, and credit unions with assets of $42 million or less as of December 31, 2012, are exempt from collecting data in 2013. An institution's exemption from collecting data in 2013 does not affect its responsibility to report data it was required to collect in 2012.</P>
        <HD SOURCE="HD1">II. Procedural Requirements</HD>
        <HD SOURCE="HD2">Administrative Procedure Act</HD>
        <P>Under the Administrative Procedure Act (APA), notice and opportunity for public comment are not required if the Bureau finds that notice and public comment are impracticable, unnecessary, or contrary to the public interest. 5 U.S.C. 553(b)(B). Pursuant to this final rule, comment 1003.2 (Financial institution)-2 in Regulation C, supplement I, is amended to update the exemption threshold. The amendment in this final rule is technical and nondiscretionary, and it merely applies the formula established by Regulation C for determining any adjustments to the exemption threshold. For these reasons, the Bureau has determined that publishing a notice of proposed rulemaking and providing opportunity for public comment are unnecessary and the amendment is adopted in final form.</P>

        <P>Under section 553(d) of the APA, the required publication or service of a substantive rule shall be made not less than 30 days before its effective date except for certain instances, including when a substantive rule grants or recognizes an exemption or relieves a restriction. 5 U.S.C. 553(d). As this rule increases the exemption threshold, and is therefore a substantive rule that grants or recognizes an exemption or relieves a restriction, the Bureau is publishing this final rule less than 30 days before its effective date. Additionally, as it is in the public interest to make the<PRTPAGE P="76840"/>updated threshold for the asset-size exemption available publicly as soon as possible after all data needed for the calculation are available, the Bureau is making the final rule effective immediately upon publication in the<E T="04">Federal Register</E>.</P>
        <HD SOURCE="HD2">Regulatory Flexibility Act</HD>
        <P>The Regulatory Flexibility Act (RFA) does not apply to a rulemaking where general notice of proposed rulemaking is not required. 5 U.S.C. 603 and 604. As noted previously, the Bureau has determined that it is unnecessary to publish a general notice of proposed rulemaking for this final rule. Accordingly the RFA's requirements relating to an initial and final regulatory flexibility analysis do not apply.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 12 CFR Part 1003</HD>
          <P>Banks, Banking, Credit unions, Mortgages, National banks, Savings associations, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        <HD SOURCE="HD1">Authority and Issuance</HD>
        <P>For the reasons set forth in the preamble, the Bureau of Consumer Financial Protection amends 12 CFR part 1003 as follows:</P>
        <REGTEXT PART="1003" TITLE="12">
          <PART>
            <HD SOURCE="HED">PART 1003—HOME MORTGAGE DISCLOSURE (REGULATION C)</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 1003 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>12 U.S.C. 2803, 2804, 2805, 5512, 5581.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="1003" TITLE="12">
          <AMDPAR>2. In Supplement I to part 1003, under<E T="03">Section 1003.2—</E>
            <E T="03">Definitions,</E>under the definition “<E T="03">Financial institution”,</E>paragraph 2 is revised to read as follows:</AMDPAR>
          <HD SOURCE="HD1">Supplement I to Part 1003—Staff Commentary</HD>
          <EXTRACT>
            <STARS/>
            <HD SOURCE="HD2">Section 1003.2—Definitions</HD>
            <STARS/>
            <P>Financial institution.</P>
            <STARS/>
            <P>2.<E T="03">Adjustment of exemption threshold for banks, savings associations, and credit unions.</E>For data collection in 2013, the asset-size exemption threshold is $42 million. Banks, savings associations, and credit unions with assets at or below $42 million as of December 31, 2012, are exempt from collecting data for 2013.</P>
            <STARS/>
          </EXTRACT>
        </REGTEXT>
        <SIG>
          <DATED>Dated: December 21, 2012.</DATED>
          <NAME>Richard Cordray,</NAME>
          <TITLE>Director, Consumer Financial Protection Bureau.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31311 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4810-AM-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
        <SUBAGY>Comptroller of the Currency</SUBAGY>
        <CFR>12 CFR Part 3</CFR>
        <SUBJECT>Minimum Capital Ratios; Issuance of Directives</SUBJECT>
        <HD SOURCE="HD2">CFR Correction</HD>
        <P>In Title 12 of the Code of Federal Regulations, Parts 1 to 199, revised as of January 1, 2012, on page 52, in appendix C to Part 3, Part I, Section 1 is revised to read as follows:</P>
        <REGTEXT PART="3" TITLE="12">
          <APPENDIX>
            <HD SOURCE="HED">Appendix C to Part 3—Capital Adequacy Guidelines for Banks: Internal-Ratings-Based and Advanced Measurement Approaches</HD>
            <STARS/>
            <HD SOURCE="HD1">Part I. General Provisions</HD>
            <HD SOURCE="HD2">Section 1. Purpose, Applicability, Reservation of Authority, and Principle of Conservatism</HD>
            <P>(a)<E T="03">Purpose.</E>This appendix establishes:</P>
            <P>(1) Minimum qualifying criteria for banks using bank-specific internal risk measurement and management processes for calculating risk-based capital requirements;</P>
            <P>(2) Methodologies for such banks to calculate their risk-based capital requirements; and</P>
            <P>(3) Public disclosure requirements for such banks.</P>
            <P>(b)<E T="03">Applicability.</E>(1) This appendix applies to a bank that:</P>
            <P>(i) Has consolidated assets, as reported on the most recent year-end Consolidated Report of Condition and Income (Call Report) equal to $250 billion or more;</P>
            <P>(ii) Has consolidated total on-balance sheet foreign exposure at the most recent year-end equal to $10 billion or more (where total on-balance sheet foreign exposure equals total cross-border claims less claims with head office or guarantor located in another country plus redistributed guaranteed amounts to the country of head office or guarantor plus local country claims on local residents plus revaluation gains on foreign exchange and derivative products, calculated in accordance with the Federal Financial Institutions Examination Council (FFIEC) 009 Country Exposure Report);</P>
            <P>(iii) Is a subsidiary of a depository institution that uses 12 CFR part 3, appendix C, 12 CFR part 208, appendix F, 12 CFR part 325, appendix D, or 12 CFR part 567, appendix C, to calculate its risk-based capital requirements; or</P>
            <P>(iv) Is a subsidiary of a bank holding company that uses 12 CFR part 225, appendix G, to calculate its risk-based capital requirements.</P>
            <P>(2) Any bank may elect to use this appendix to calculate its risk-based capital requirements.</P>
            <P>(3) A bank that is subject to this appendix must use this appendix unless the OCC determines in writing that application of this appendix is not appropriate in light of the bank's asset size, level of complexity, risk profile, or scope of operations. In making a determination under this paragraph, the OCC will apply notice and response procedures in the same manner and to the same extent as the notice and response procedures in 12 CFR 3.12.</P>
            <P>(c)<E T="03">Reservation of authority</E>—(1)<E T="03">Additional capital in the aggregate.</E>The OCC may require a bank to hold an amount of capital greater than otherwise required under this appendix if the OCC determines that the bank's risk-based capital requirement under this appendix is not commensurate with the bank's credit, market, operational, or other risks. In making a determination under this paragraph, the OCC will apply notice and response procedures in the same manner and to the same extent as the notice and response procedures in 12 CFR 3.12.</P>
            <P>(2)<E T="03">Specific risk-weighted asset amounts.</E>(i) If the OCC determines that the risk-weighted asset amount calculated under this appendix by the bank for one or more exposures is not commensurate with the risks associated with those exposures, the OCC may require the bank to assign a different risk-weighted asset amount to the exposures, to assign different risk parameters to the exposures (if the exposures are wholesale or retail exposures), or to use different model assumptions for the exposures (if relevant), all as specified by the OCC.</P>
            <P>(ii) If the OCC determines that the risk-weighted asset amount for operational risk produced by the bank under this appendix is not commensurate with the operational risks of the bank, the OCC may require the bank to assign a different risk-weighted asset amount for operational risk, to change elements of its operational risk analytical framework, including distributional and dependence assumptions, or to make other changes to the bank's operational risk management processes, data and assessment systems, or quantification systems, all as specified by the OCC.</P>
            <P>(3)<E T="03">Regulatory capital treatment of unconsolidated entities.</E>If the OCC determines that the capital treatment for a bank's exposure or other relationship to an entity not consolidated on the bank's balance sheet is not commensurate with the actual risk relationship of the bank to the entity, for risk-based capital purposes, it may require the bank to treat the entity as if it were consolidated onto the bank's balance sheet and require the bank to hold capital against the entity's exposures. The OCC will look to the substance of and risk associated with the transaction as well as other relevant factors the OCC deems appropriate in determining whether to require such treatment and in determining the bank's compliance with minimum risk-based capital requirements. In making a determination under this paragraph, the OCC will apply notice and response procedures in the same manner and to the same extent as the notice and response procedures in 12 CFR 3.12.</P>
            <P>(4)<E T="03">Other supervisory authority.</E>Nothing in this appendix limits the authority of the OCC under any other provision of law or regulation to take supervisory or enforcement action, including action to address unsafe or unsound practices or conditions, deficient capital levels, or violations of law.<PRTPAGE P="76841"/>
            </P>
            <P>(d)<E T="03">Principle of conservatism.</E>Notwithstanding the requirements of this appendix, a bank may choose not to apply a provision of this appendix to one or more exposures, provided that:</P>
            <P>(1) The bank can demonstrate on an ongoing basis to the satisfaction of the OCC that not applying the provision would, in all circumstances, unambiguously generate a risk-based capital requirement for each such exposure greater than that which would otherwise be required under this appendix;</P>
            <P>(2) The bank appropriately manages the risk of each such exposure;</P>
            <P>(3) The bank notifies the OCC in writing prior to applying this principle to each such exposure; and</P>
            <P>(4) The exposures to which the bank applies this principle are not, in the aggregate, material to the bank.</P>
            <STARS/>
          </APPENDIX>
        </REGTEXT>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31485 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 1505-01-D</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
        <SUBAGY>Office of the Comptroller of the Currency</SUBAGY>
        <CFR>12 CFR Part 32</CFR>
        <DEPDOC>[Docket ID OCC-2012-0007]</DEPDOC>
        <RIN>RIN 1557-AD59</RIN>
        <SUBJECT>Lending Limits</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of the Comptroller of the Currency, Treasury.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Office of the Comptroller of the Currency (OCC) is amending its lending limits rule to extend the rule's temporary exception for credit exposures arising from a derivative transaction or securities financing transaction from January 1, 2013 to July 1, 2013.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This final rule is effective December 31, 2012. The effective date of amendatory instruction 3a of the interim final rule published on June 21, 2012, 77 FR 37277, is delayed from January 1, 2013 to July 1, 2013.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Jonathan Fink, Assistant Director, Bank Activities and Structure Division, (202) 649-5593; Heidi M. Thomas, Special Counsel, Legislative and Regulatory Activities Division, (202) 649-5490; or Kurt Wilhelm, Director for Financial Markets, (202) 649-6437, Office of the Comptroller of the Currency, Washington, DC 20219.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Description of Final Rule</HD>
        <P>Section 5200 of the Revised Statutes, 12 U.S.C. 84, provides that the total loans and extensions of credit by a national bank to a person outstanding at one time shall not exceed 15 percent of the unimpaired capital and unimpaired surplus of the bank if the loan or extension of credit is not fully secured, plus an additional 10 percent of unimpaired capital and unimpaired surplus if the loan is fully secured. Section 5(u)(1) of the Home Owners' Loan Act (HOLA), 12 U.S.C. 1464(u)(1), provides that section 5200 of the Revised Statutes “shall apply to savings associations in the same manner and to the same extent as it applies to national banks.” In addition, section 5(u)(2) of HOLA, 12 U.S.C. 1464(u)(2), includes exceptions to the lending limits for certain loans made by savings associations. These HOLA provisions apply to both Federal and state-chartered savings associations.</P>
        <P>Section 610 of the Dodd-Frank Wall Street Reform and Consumer Protection Act<SU>1</SU>
          <FTREF/>(Dodd-Frank Act) amended section 5200 of the Revised Statutes to provide that the definition of “loans and extensions of credit” includes any credit exposure to a person arising from a derivative transaction, repurchase agreement, reverse repurchase agreement, securities lending transaction, or securities borrowing transaction between a national bank and that person. This amendment was effective July 21, 2012. By virtue of section 5(u)(1) of the HOLA, this new definition of “loans and extensions of credit” applies to all savings associations as well as to national banks.</P>
        <FTNT>
          <P>
            <SU>1</SU>Public Law 111-203, 124 Stat. 1376 (2010).</P>
        </FTNT>
        <P>On June 21, 2012, the OCC published in the<E T="04">Federal Register</E>an interim final rule that, among other things, amended the OCC's lending limits regulation, 12 CFR part 32, by implementing section 610 of the Dodd-Frank Act.<SU>2</SU>
          <FTREF/>Specifically, the interim final rule amended part 32 to provide national banks and savings associations with different options for measuring the appropriate credit exposures of derivatives transactions and securities financing transactions, including an internal model option. The interim final rule was effective on July 21, 2012. Because the OCC recognized that national banks and savings associations would need additional time to comply with these new provisions, the interim final rule provided at 12 CFR 32.1(d) that the requirements of part 32 only apply to a credit exposure arising from a derivative transaction or securities financing transaction on or after January 1, 2013.<SU>3</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>2</SU>77 FR 37265 (June 21, 2012).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>3</SU>The interim final rule also removed from the lending limits rule the securities reverse repurchase provision, redesignated as § 32.2(q)(1)(vii), on January 1, 2013 to correspond to the expiration of the exception for the section 610-related provisions. This final rule changes the date of this removal to July 1, 2013 as a conforming change.</P>
        </FTNT>
        <P>Based on the public comments received on the interim final rule, the OCC concludes that institutions that wish to use an internal model method to determine credit exposure for derivative transactions and securities financing transactions may not have sufficient time to develop a model, receive approval for its use, and implement the model before the January 1, 2013 expiration of the temporary exception. Moreover, for many institutions with large portfolios, the other non-model methods to measure credit exposure provided by the rule often would not be optimal. For the foregoing reasons, the OCC is extending this exception to July 1, 2013,<SU>4</SU>
          <FTREF/>in advance of finalizing the interim final rule. As indicated in the preamble to the interim final rule, notwithstanding this extension, the OCC retains full authority to address credit exposures that present undue concentrations on a case-by-case basis through our existing safety and soundness authorities.</P>
        <FTNT>
          <P>
            <SU>4</SU>The OCC issued OCC Bulletin 2012-36 on November 16, 2012, to provide notice prior to finalizing the interim final rule of its intention to extend the exception to April 1, 2013 so that national banks and savings associations could adjust their preparations for compliance accordingly. Since then, the OCC has determined that it is more appropriate to extend the exception to July 1, 2013.</P>
        </FTNT>
        <HD SOURCE="HD1">II. Notice and Comment</HD>
        <P>This final rule is effective on December 31, 2012. Pursuant to the Administrative Procedure Act (APA), at 5 U.S.C. 553(b)(B), notice and comment are not required prior to the issuance of a final rule if an agency, for good cause, finds that “notice and public procedure thereon are impracticable, unnecessary, or contrary to the public interest.”</P>
        <P>This final rule extends the temporary exception from the lending limits rules for extensions of credit arising from derivative transactions or securities financing transactions from January 1, 2013 to July 1, 2013 in order to provide national banks and savings associations with additional time to comply with these provisions. The rule makes no substantive changes to the lending limits rule. Furthermore, on November 16, 2012, the OCC announced its intention to extend this temporary exception,<SU>5</SU>
          <FTREF/>thereby giving notice to<PRTPAGE P="76842"/>interested parties that the January 1, 2013 date would likely be extended. For these reasons, the OCC finds that prior notice and comment are unnecessary.</P>
        <FTNT>
          <P>
            <SU>5</SU>
            <E T="03">See</E>OCC Bulletin 2012-36.</P>
        </FTNT>
        <HD SOURCE="HD1">III. Effective Date</HD>

        <P>This interim final rule is effective on December 31, 2012. A final rule may be effective without 30 days advance publication in the<E T="04">Federal Register</E>if an agency finds good cause and publishes such with the final rule.<SU>6</SU>
          <FTREF/>The purpose of a delayed effective date is to permit regulated entities to adjust their behavior before the final rule takes effect. As described above, national banks and savings associations are currently excepted from the lending limits rules for extensions of credit arising from derivative transactions or securities financing transactions until January 1, 2013. This final rule extends this exception through July 1, 2013 in order to provide national banks and savings associations with additional time to comply with these provisions. The rule makes no substantive changes to the lending limits rule. Because the current exception will expire less than 30 days from the date of this rule's publication, it is necessary to make this rule effective immediately. Not doing so would result in national banks and savings associations having to comply with these provisions for a limited amount of time before the July 1, 2013 exception is effective. For these reasons, the OCC finds good cause to dispense with a delayed effective date.</P>
        <FTNT>
          <P>
            <SU>6</SU>5 U.S.C. 553(d)(3).</P>
        </FTNT>
        <HD SOURCE="HD1">IV. Regulatory Analysis</HD>
        <HD SOURCE="HD2">Regulatory Flexibility Act</HD>
        <P>Pursuant to the Regulatory Flexibility Act (RFA),<SU>7</SU>
          <FTREF/>5 U.S.C. 603, an agency must prepare a regulatory flexibility analysis for all proposed and final rules that describe the impact of the rule on small entities, unless the head of an agency certifies that the rule will not have “a significant economic impact on a substantial number of small entities.” However, the RFA applies only to rules for which an agency publishes a general notice of proposed rulemaking pursuant to 5 U.S.C. 553(b).<SU>8</SU>
          <FTREF/>Pursuant to the APA at 5 U.S.C. 553(b)(B), general notice and an opportunity for public comment are not required prior to the issuance of a final rule when an agency, for good cause, finds that “notice and public procedure thereon are impracticable, unnecessary, or contrary to the public interest.” For the reasons discussed above, the OCC did not publish a notice of proposed rulemaking. Therefore, the RFA does not apply to this final rule.</P>
        <FTNT>
          <P>
            <SU>7</SU>Public Law 96-354, Sept. 19, 1980.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>8</SU>5 U.S.C. 603(a), 604(a).</P>
        </FTNT>
        <HD SOURCE="HD2">Unfunded Mandates Reform Act</HD>
        <P>Section 202 of the Unfunded Mandates Reform Act of 1995, Public Law 104-4 (2 U.S.C. 1532) (Unfunded Mandates Act), requires that an agency prepare a budgetary impact statement before promulgating any rule likely to result in a Federal mandate that may result in the expenditure by state, local, and tribal governments, in the aggregate, or by the private sector, of $100 million or more in any one year. If a budgetary impact statement is required, § 205 of the Unfunded Mandates Act also requires an agency to identify and consider a reasonable number of regulatory alternatives before promulgating a rule. The OCC has determined that there is no Federal mandate imposed by this rulemaking that may result in the expenditure by state, local, and tribal governments, in the aggregate, or by the private sector, of $100 million or more in any one year. Accordingly, final rule is not subject to § 202 of the Unfunded Mandates Act.</P>
        <HD SOURCE="HD2">Paperwork Reduction Act</HD>
        <P>In accordance with the requirements of the Paperwork Reduction Act (PRA) of 1995 (44 U.S.C. 3501-3521), the OCC may not conduct or sponsor, and a respondent is not required to respond to, an information collection unless it displays a currently valid Office of Management and Budget (OMB) control number. This rule amends rules, which contain information collection requirements under the PRA, that have been previously approved by OMB under OMB Control No. 1557-0221. The amendments in this final rule do not introduce any new collections of information into the rules, nor do they amend the rules in a way that modifies the collection of information that OMB has previously approved for part 32. Therefore, no Paperwork Reduction Act submission to OMB is required.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 12 CFR Part 32</HD>
          <P>National banks, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        
        <P>For the reasons set forth in the preamble, 12 CFR part 32 is amended as follows:</P>
        <REGTEXT PART="32" TITLE="12">
          <PART>
            <HD SOURCE="HED">PART 32—LENDING LIMITS</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 32 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>12 U.S.C. 1<E T="03">et seq.,</E>84, 93a, 1462a, 1463, 1464(u), and 5412(b)(2)(B).</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="32" TITLE="12">
          <SECTION>
            <SECTNO>§ 32.1</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. Section 32.1(d) is amended by removing “January 1, 2013” and adding in its place “July 1, 2013”.</AMDPAR>
        </REGTEXT>
        <SIG>
          <DATED>Dated: December 21, 2012.</DATED>
          <NAME>Thomas J. Curry,</NAME>
          <TITLE>Comptroller of the Currency.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31267 Filed 12-26-12; 11:15 am]</FRDOC>
      <BILCOD>BILLING CODE 4810-33-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Federal Aviation Administration</SUBAGY>
        <CFR>14 CFR Parts 34 and 45</CFR>
        <DEPDOC>[Docket No.: FAA-2012-1333; Amendment Nos. 34-5 and 45-28]</DEPDOC>
        <RIN>RIN 2120-AK15</RIN>
        <SUBJECT>Exhaust Emissions Standards for New Aircraft Gas Turbine Engines and Identification Plate for Aircraft Engines</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Aviation Administration (FAA), DOT.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule; request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This action amends the emission standards for turbine engine powered airplanes to incorporate the standards promulgated by the United States Environmental Protection Agency (EPA) on June 18, 2012. This amendment fulfills the FAA's requirements under the Clean Air Act Amendments of 1970 to issue regulations ensuring compliance with the EPA standards. This action revises the standards for oxides of nitrogen and test procedures for exhaust emissions based on International Civil Aviation Organization standards, and for the identification and marking requirements for engines.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>

          <P>Effective December 31, 2012. Affected parties, however, are not required to comply with the information collection requirement in § 45.11 until the Office of Management and Budget (OMB) approves the collection and assigns a control number under the Paperwork Reduction Act of 1995. The FAA will publish in the<E T="04">Federal Register</E>a notice of the control number assigned by the Office of Management and Budget (OMB) for this information collection requirement.</P>
          <P>The incorporation by reference of certain publications listed in the rule is approved by the Director of the Federal Register as of December 31, 2012.</P>
          <P>Submit comments on or before March 1, 2013.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>You may send comments identified by Docket Number FAA-<PRTPAGE P="76843"/>2012-1333 using any of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal:</E>Go to<E T="03">www.regulations.gov</E>and follow the instructions for sending your comments electronically.</P>
          <P>•<E T="03">Mail:</E>Send comments to Docket Operations, U.S. Department of Transportation, 1200 New Jersey Avenue SE., West Building Ground Floor, Room W12-140, Washington, DC 20590.</P>
          <P>•<E T="03">Fax:</E>Fax comments to Docket Operations at 202-493-2251.</P>
          <P>•<E T="03">Hand Delivery:</E>Take comments to Docket Operations in Room W12-140 of the West Building Ground Floor at 1200 New Jersey Avenue SE., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holiday.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>For technical questions concerning this action, contact Aimee Fisher, Emissions Division (AEE-300), Office of Environment and Energy, Federal Aviation Administration, 800 Independence Avenue SW., Washington, DC 20591; telephone (202) 267-7705; email<E T="03">Aimee.Fisher@faa.gov.</E>
          </P>

          <P>For legal questions concerning this rule contact Karen Petronis, International Law, Legislation and Regulations Division (AGC-200), Office of the Chief Counsel, Federal Aviation Administration, 800 Independence Avenue SW., Washington, DC 20591; telephone (202) 267-3073, email<E T="03">Karen.Petronis@faa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Good Cause for Immediate Adoption</HD>

        <P>Section 553(b)(3)(B) of the Administrative Procedure Act (APA) (5 U.S.C. 551<E T="03">et seq.</E>) authorizes agencies to dispense with notice and comment procedures for rules when the agency for “good cause” finds that those procedures are “impracticable, unnecessary, or contrary to the public interest.” Under this section, an agency, upon finding good cause, may issue a final rule without seeking comment prior to the rulemaking.</P>

        <P>In July 2011, the United States Environmental Protection Agency (EPA) proposed new aircraft engine emission standards for oxides of nitrogen (NO<E T="52">X</E>), compliance flexibilities, and other regulatory requirements applicable to aircraft turbofan or turbojet engines with rated thrusts greater than 26.7 kilonewtons (kN) (76 FR 45012, July 27, 2011). The final rule adopting these proposals was published in the<E T="04">Federal Register</E>on June 18, 2012 (77 FR 36342). The public had an opportunity to comment on the EPA's proposed rule, and the comments received were addressed in the EPA's final rule.</P>
        <P>Section 232 of the Clean Air Act Amendments of 1970 (CAA) (42 U.S.C. 7572) directs the FAA to prescribe regulations to ensure compliance with the EPA's aircraft emission standards. The FAA is amending 14 CFR parts 34 and 45 to incorporate the changes promulgated by the EPA in the emission standards and the associated engine marking requirements. The FAA is not adopting any standards or requirements different from those promulgated by the EPA. Accordingly, the FAA finds that further public comment on these standards prior to promulgation is unnecessary, and that further delay in making the regulations consistent would be contrary to the public interest.</P>
        <P>Section 553(d)(3) of the Administrative Procedure Act requires that agencies publish a rule not less than 30 days before its effective date, except as otherwise provided by the agency for good cause found and published with the rule.</P>
        <P>This rule, as previously adopted by the EPA, contains a production cutoff date of December 31, 2012. In addition, it contains a new production marking requirement that is effective on aircraft engines produced after December 31. In order to give manufacturers the maximum amount of time to adjust their processes to these requirements, the FAA finds that good cause exists to make this rule effective in less than 30 days.</P>
        <HD SOURCE="HD1">Authority for This Rulemaking</HD>
        <P>The FAA's authority to issue rules on aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106, describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart III. Under Section 232 of the CAA (42 U.S.C. 7571), the FAA is directed to prescribe regulations to ensure compliance with the standards prescribed by the EPA under § 7571, including making such standards applicable in the issuance, amendment, modification, suspension, or revocation of any certificate authorized by part A of subtitle VII of title 49. These regulations are within the scope of that authority, as the FAA is adopting the standards promulgated by the EPA and making them applicable to aircraft engine type certificates issued under the FAA's Title 49 authority.</P>
        <HD SOURCE="HD1">Comments Invited</HD>
        <P>For the reasons noted above, the FAA is adopting this final rule without prior notice and public comment. The Regulatory Policies and Procedures of the Department of Transportation (DOT) (44 FR 1134; February 26, 1979) provide that, to the maximum extent possible, operating administrations for the DOT should provide an opportunity for public comment on regulations issued without prior notice.</P>
        <P>The FAA invites interested persons to participate in this rulemaking by submitting written comments, data, or views. The agency also invites comments relating to the economic, environmental, energy, or federalism impacts that might result from adopting the changes. The most helpful comments reference a specific portion of this rule, explain the reason for any recommended change, and include supporting data. To ensure the docket does not contain duplicate comments, please send only one copy of written comments, or if you are filing comments electronically, please submit your comments only one time.</P>

        <P>The FAA will file in the docket all comments we receive, as well as a report summarizing each substantive public contact with FAA personnel concerning this rulemaking. Once the comment period closes, the FAA will review and dispose of the comments filed in the rulemaking docket. Because this is a final rule, the FAA will publish a disposition of comments in the<E T="04">Federal Register</E>. Based on the comments received, the FAA will state whether it has decided that (i) no action is necessary other than publishing the disposition of comments in the<E T="04">Federal Register</E>, or (ii) the FAA should prepare a revised final rule.</P>
        <P>
          <E T="03">Privacy:</E>We will post all comments we receive, without change to<E T="03">www.regulations.gov,</E>including any personal information you provide. Using the search function of our docket Web site, anyone can find and read the comments received into any of our dockets, including the name of the individual sending the comment (or signing the comment for an association, business, labor union, etc.). You may review DOT's complete Privacy Act Statement in the<E T="04">Federal Register</E>published on April 11, 2000 (65 FR 19477-78) or you may visit<E T="03">DocketsInfo.dot.gov.</E>
        </P>
        <P>
          <E T="03">Docket:</E>To read background documents or comments received, go to<E T="03">regulations.gov</E>at any time or to Docket Operations in Room W12-140 of the West Building Ground Floor at 1200 New Jersey Avenue SE., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.<PRTPAGE P="76844"/>
        </P>
        <HD SOURCE="HD1">Proprietary or Confidential Business Information</HD>

        <P>Do not file in the docket information that you consider to be proprietary or confidential business information. Send or deliver this information directly to the person identified in the<E T="02">FOR FURTHER INFORMATION CONTACT</E>section of this document. Mark the information that is considered proprietary or confidential. If the information is on a disk or CD ROM, mark the outside of the disk or CD ROM and also identify electronically within the disk or CD ROM the specific information that is proprietary or confidential.</P>
        <P>Under § 11.35(b), when the FAA is aware of proprietary information filed with a comment, the agency does not place it in the docket. The FAA holds it in a separate file to which the public does not have access, and the agency places a note in the docket that it has received it. If the FAA receives a request to examine or copy this information, the FAA treats it as any other request under the Freedom of Information Act, 5 U.S.C. 552. The FAA processes such a request under the DOT procedures found in 49 CFR part 7.</P>
        <HD SOURCE="HD1">Availability of Rulemaking Documents</HD>
        <P>You can get an electronic copy of rulemaking documents using the Internet by:</P>
        <P>(1) Searching the Federal eRulemaking portal at<E T="03">http://www.regulations.gov;</E>
        </P>
        <P>(2) Visiting the FAA's Regulations and Policies Web page at<E T="03">http://www.faa.gov/regulations_policies/;</E>or</P>
        <P>(3) Accessing the Government Printing Office's Web page at<E T="03">http://www.gpo.gov/fdsys/browse/collection.action?collectionCode=FR.</E>
        </P>
        <P>You can also get a copy by sending a request to the Federal Aviation Administration, Office of Rulemaking, ARM-1, 800 Independence Avenue SW., Washington, DC 20591, or by calling (202) 267-9680. Make sure to identify the docket and amendment numbers of this rulemaking.</P>
        <HD SOURCE="HD2">I. Background</HD>
        <P>Section 231(a)(2)(A) of the CAA (42 U.S.C. 7571) directs the Administrator of the EPA to propose aircraft emission standards applicable to the emission of any air pollutant from classes of aircraft engines which in the EPA Administrator's judgment causes or contributes to air pollution that may reasonably be anticipated to endanger public health or welfare. These emission standards have been promulgated by the EPA in 40 CFR part 87.</P>
        <P>Section 232 of the CAA (42 U.S.C. 7572) then directs the FAA to prescribe regulations to ensure compliance with the EPA's standards. The FAA has promulgated these emission standards in 14 CFR part 34, and the engine marking requirements in part 45.</P>
        <P>The EPA initially regulated gaseous exhaust emissions, smoke and fuel venting from aircraft in 1973, with occasional revision. Since the EPA's adoption of the initial regulations, the FAA has taken subsequent action to ensure that the regulations in 14 CFR are kept current with the EPA's standards. This final rule continues the revisions to the regulations in 14 CFR.</P>

        <P>On July 27, 2011, the EPA proposed new aircraft engine emission standards for NO<E T="52">X</E>, compliance flexibilities, and other regulatory requirements for aircraft turbofan or turbojet engines with rated thrusts greater than 26.7 kilonewtons (kN) (76 FR 45012). The EPA also proposed adopting the gas turbine engine test procedures of ICAO. The final rule adopting these proposals was published on June 18, 2012 (77 FR 36342), and was effective July 18, 2012.</P>
        <HD SOURCE="HD2">II. Summary of the Costs and Benefits of the Final Rule</HD>
        <P>Department of Transportation Order DOT 2100.5 prescribes policies and procedures for simplification, analysis, and review of regulations. If the expected cost impact is so minimal that a proposed or final rule does not warrant a full evaluation, this order permits that a statement to that effect and the basis for it to be included in the preamble if a full regulatory evaluation of the cost and benefits is not prepared. Such a determination has been made for this final rule.</P>
        <HD SOURCE="HD2">III. Discussion of This Final Rule</HD>
        <HD SOURCE="HD3">1. New Naming Convention</HD>

        <P>The EPA has adopted a new naming convention, “tier,” in 40 CFR part 87. The tier numbers distinguish levels of increased stringency in the NO<E T="52">X</E>emission standards. This convention is consistent with the numeric identifier that the Committee on Aviation Environmental Protection (CAEP) of ICAO uses to differentiate the CAEP work cycles that produce new standards. For example, the standards that correspond to CAEP's sixth meeting (CAEP/6) are identified by the EPA as Tier 6, while the standards that correspond to CAEP/8 are called Tier 8. The naming convention is also being applied to previously effective less stringent standards, i.e., Tier 0, Tier 2, and Tier 4. None of the previous standards have been changed, only the tier designation has been added in the regulations for comparison and consistency. The following table identifies the various CAEP cycles and corresponding tier naming convention.</P>
        <P>The tier designation departs from the previous FAA practice that described aircraft engine emission standards as amendments. The new designation is a valuable tool that provides a consistent reference to individual standards. The FAA is adopting this naming convention in the emission standards contained in this final rule; the designations appear in §§ 34.21 and 34.23.</P>
        <GPOTABLE CDEF="s50,r50,r50,r50,xs50" COLS="5" OPTS="L2,i1">
          <TTITLE>Table 1—Naming Conventions Comparison</TTITLE>
          <BOXHD>
            <CHED H="1">CAEP meeting no. and Annex 16 amendment</CHED>
            <CHED H="1">Date CAEP adopted, effective, and applicable</CHED>
            <CHED H="1">FAA part 34 amendments</CHED>
            <CHED H="1">14 CFR part 34 rule promulgation</CHED>
            <CHED H="1">40 CFR part 87 tier</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">CAEP/1 Annex 16 Vol II, Amendment 1</ENT>
            <ENT>03/4/1988, 07/31/1998, 11/17/1988</ENT>
            <ENT>1. NPRM cancel SFAR 27 and add FAR 34-1;</ENT>
            <ENT>1. 08/10/1990</ENT>
            <ENT>Tier 0.</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT>2. 14 CFR Part 34 Amendment 2</ENT>
            <ENT>2. 09/10/1990</ENT>
            <ENT O="xl"/>
          </ROW>
          <ROW>
            <ENT I="01">CAEP/2 Annex 16 Vol II, Amendment 2</ENT>
            <ENT>03/24/1993, 07/26/1993, 11/11/1993</ENT>
            <ENT>14 CFR Part 34 Amendment 3</ENT>
            <ENT>3/3/1999</ENT>
            <ENT>Tier 2.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">CAEP/4 Annex 16 Vol II, Amendment 4</ENT>
            <ENT>02/26/1999, 07/19/1999, 11/4/1999</ENT>
            <ENT>14 CFR Part 34 Amendment 4</ENT>
            <ENT>4/29/2009</ENT>
            <ENT>Tier 4.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">CAEP/6 Annex 16 Vol II, Amendment 5</ENT>
            <ENT>02/23/2005, 07/11/2005, 11/24/2005</ENT>
            <ENT>14 CFR Part 34 Amendment 5</ENT>
            <ENT>TBD (40 CFR Part 87 Effective July 18, 2012)</ENT>
            <ENT>Tier 6.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">CAEP/8 Annex 16 Vol II, Amendment 7</ENT>
            <ENT>03/4/2011, 07/18/2011, 11/17/2011</ENT>
            <ENT O="xl"/>
            <ENT O="xl"/>
            <ENT>Tier 8.</ENT>
          </ROW>
          <TNOTE>
            <E T="02">Note:</E>The NO<E T="52">X</E>standards were not amended during CAEP/3, CAEP/5, and CAEP/7 meetings and are not included in the tier designations.</TNOTE>
        </GPOTABLE>
        <PRTPAGE P="76845"/>
        <HD SOURCE="HD3">2. Changes to Part 34</HD>
        <P>This final rule adopts the same emissions standards in part 34 as the EPA promulgated for 40 CFR part 87. Any differences between the appearance of the regulations is the result of different regulatory formats between the two titles. No difference in the standards or the meaning of any term is implied nor should any difference be presumed. In the event that a substantive difference is identified, the regulation in 40 CFR part 87 is considered controlling and will be enforced.</P>
        <P>The FAA is not changing any of its procedures for exemption requests submitted under part 34. The FAA intends to continue to work together with the EPA to jointly consider all exemption requests as we have in the past.</P>
        <P>In this document we are revising paragraph 34.7(b) to add an additional sentence limiting the applicability to the requirements of § 34.21 (maintaining the current scope after § 34.23 is added).</P>
        <HD SOURCE="HD3">3. NO<E T="52">X</E>Standards for Newly Certificated Engines</HD>
        <P>Table 2 below summarizes the NO<E T="52">X</E>standards for newly certificated engines that are adopted in this final rule, in § 34.23. The regulation establishes two levels of increasingly stringent NO<E T="52">X</E>emission standards for gas turbofan engines with maximum rated thrusts greater than 26.7 kN. The standard applicable to a particular engine is based on its type certification date. Newly certificated aircraft engines are those that receive a new type certificate after the effective date of the applicable standard. The two new standards are:</P>
        <HD SOURCE="HD3">a. Tier 6/CAEP 6 NO<E T="52">X</E>Standards</HD>
        <P>The first set of standards is equivalent to the NO<E T="52">X</E>limits established at the CAEP/6 meeting. This level was originally adopted by ICAO and became internationally applicable after December 31, 2007. Engine manufacturers have been producing engines that meet Tier 6 standards even though the standard and the marking designation had not yet been adopted in the United States.</P>

        <P>Overall, Tier 6 represents an approximate 12 percent reduction in NO<E T="52">X</E>emissions from Tier 4, § 34.21(d)(1)(vi). Tier 4 standards were adopted by ICAO in 2005 with an implementation date in 2008. The Tier 6 standard is incorporated in § 34.23(a).</P>
        <P>Under the EPA rule, the Tier 6 standard was effective for engines produced on and after July 18, 2012, unless otherwise covered by an exception or exemption. These exceptions include:</P>
        <P>1. The production of Tier 4 engines introduced before July 18, 2012, (including their derivatives) through December 31, 2012 (§ 34.23(c) and 40 CFR § 87.23(d)(1)); and</P>
        <P>2. Up to six engines per manufacturer produced on and after July 18, 2012 and before August 31, 2013 (§ 34.9(b) and 40 CFR § 87.23(d)(3)). This exception is described more fully in section 4 below.</P>
        <P>Exemptions to the standards of part 34 must be filed under the regulatory exemption process discussed in § 34.7 and part 11.</P>
        <HD SOURCE="HD3">b. Tier 8/CAEP 8 NO<E T="52">X</E>Standards</HD>

        <P>The second set of new standards is equivalent to the CAEP/8 NO<E T="52">X</E>limits that were recommended at the February 2010 CAEP/8 meeting and applicable as ICAO standards and recommended practices in November 2011. These Tier 8 standards will be mandatory in the United States for engines for which the first individual production model is manufactured after December 31, 2013. Overall, Tier 8 represents an approximate 15 percent reduction in NO<E T="52">X</E>emissions from Tier 6. The Tier 8 standard is incorporated in § 34.23(b).</P>
        <GPOTABLE CDEF="xs40,r50,xs48,xs80,xs80,r50" COLS="6" OPTS="L2,i1">
          <TTITLE>Table 2—Tier 6 and Tier 8 Standards for NO<E T="52">X</E>
          </TTITLE>
          <BOXHD>
            <CHED H="1">Tier</CHED>
            <CHED H="1">Date</CHED>
            <CHED H="1">Class</CHED>
            <CHED H="1">Rated pressure ratio—rPR</CHED>
            <CHED H="1">Rated output<LI>rO (kN)</LI>
            </CHED>
            <CHED H="1">NO<E T="52">X</E>
              <LI>(g/kN)</LI>
            </CHED>
          </BOXHD>
          <ROW RUL="n,n,n,n,s">
            <ENT I="01">Tier 6</ENT>
            <ENT>Manufactured on and after July 18, 2012 and for which the first individual production model is manufactured on or before December 31, 2013 (subject to regulatory exceptions)</ENT>
            <ENT>TF, T3, T8</ENT>
            <ENT>rPR ≤ 30</ENT>
            <ENT>26.7 &lt; rO &lt; 89.0</ENT>
            <ENT>38.5486 + 1.6823 (rPR) − 0.2453 (rO) − (0.00308 (rPR) (rO))</ENT>
          </ROW>
          <ROW RUL="n,n,n,n,s">
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT O="xl"/>
            <ENT O="xl"/>
            <ENT>rO &gt; 89.0</ENT>
            <ENT>16.72 + 1.4080 (rPR)</ENT>
          </ROW>
          <ROW RUL="n,n,n,n,s">
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT O="xl"/>
            <ENT>30 &lt; rPR &lt; 82.6</ENT>
            <ENT>26.7 &lt; rO ≤ 89.0</ENT>
            <ENT>46.1600 + 1.4286 (rPR) − 0.5303 (rO) + (0.00642 (rPR) (rO))</ENT>
          </ROW>
          <ROW RUL="n,n,n,n,s">
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT O="xl"/>
            <ENT O="xl"/>
            <ENT>rO &gt; 89.0</ENT>
            <ENT>−1.04 + 2.0 (rPR)</ENT>
          </ROW>
          <ROW RUL="s">
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT O="xl"/>
            <ENT>rPR ≥ 82.6</ENT>
            <ENT>All</ENT>
            <ENT>32 + 1.6 (rPR)</ENT>
          </ROW>
          <ROW RUL="n,n,n,n,s">
            <ENT I="01">Tier 8</ENT>
            <ENT>First individual production model manufactured after December 31, 2013</ENT>
            <ENT>TF, T3, T8</ENT>
            <ENT>rPR ≤ 30</ENT>
            <ENT>26.7 &lt; rO &lt; 89.0</ENT>
            <ENT>40.052 + 1.5681 (rPR) − 0.3615 (rO) − (0.0018 (rPR) (rO))</ENT>
          </ROW>
          <ROW RUL="n,n,n,n,s">
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT O="xl"/>
            <ENT O="xl"/>
            <ENT>rO &gt; 89.0</ENT>
            <ENT>7.88 + 1.4080 (rPR)</ENT>
          </ROW>
          <ROW RUL="n,n,n,n,s">
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT O="xl"/>
            <ENT>30 &lt; rPR &lt; 104.7</ENT>
            <ENT>26.7 &lt; rO &lt; 89.0</ENT>
            <ENT>41.9435 + 1.505 (rPR) − 0.5823 (rO) + (0.005562 (rPR) (rO))</ENT>
          </ROW>
          <ROW RUL="n,n,n,n,s">
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT O="xl"/>
            <ENT O="xl"/>
            <ENT>rO &gt; 89.0</ENT>
            <ENT>−9.88 + 2.0 (rPR)</ENT>
          </ROW>
          <ROW>
            <ENT I="22"/>
            <ENT O="xl"/>
            <ENT O="xl"/>
            <ENT>rPR ≥ 104.7</ENT>
            <ENT>All</ENT>
            <ENT>32 + 1.6 (rPR)</ENT>
          </ROW>
        </GPOTABLE>
        <PRTPAGE P="76846"/>
        <HD SOURCE="HD3">4. Standards for Engines Manufactured On and After July 18, 2012</HD>
        <P>This final rule applies to engines that are to be manufactured on and after July 18, 2012, the effective date for Tier 6 standards in the United States. However, Tier 4 engines introduced before July 18, 2012 (and their derivatives) may continue to be produced through December 31, 2012 without further action by the manufacturer. In addition, § 34.9(b) incorporates an exception that allows each engine manufacturer to produce up to six Tier 4 compliant engines with a date of manufacture on and after July 18, 2012 and before August 31, 2013 that do not meet the Tier 6 standards without further action by the manufacturer. Engines produced under this exception are required to meet Tier 4 standards.</P>
        <P>The primary purpose of allowing limited continued production of Tier 4 engines is to provide for an orderly transition to Tier 6 standards as Tier 4 engines reach the end of their production cycles.</P>
        <HD SOURCE="HD3">5. Spare Engines</HD>
        <P>This final rule allows for the production of a “spare” engine that is newly produced but meets the Tier 4 emission standard under which it was certificated rather than a more stringent standard that may be in place at the time of production. A spare engine may be produced as a replacement for an engine in service, whether installed temporarily during a repair or for permanent use. A spare engine may not be installed on a new aircraft. A spare engine may have different emission levels for individual pollutants than the engine being replaced, as long as the spare remains in overall compliance with the levels required for the original engine's type certificate.</P>
        <P>The standard is incorporated in § 34.9(a). Spare engines must be marked in accordance with § 45.13(a)(7)(v).</P>
        <HD SOURCE="HD3">6. Standards for Supersonic Aircraft Turbine Engines</HD>
        <P>This final rule contains carbon monoxide (CO) and NO<E T="52">X</E>emission standards for turbine engines that are used to propel aircraft at sustained supersonic speeds (i.e., supersonic aircraft). While emission standards for these aircraft were originally adopted by ICAO in the 1980s, the original U.S. adoption of emission standards for supersonic aircraft did not include CO or NO<E T="52">X</E>. The absence of U.S. standards for these pollutants has no practical effect because supersonic aircraft are not allowed to fly over the continental U.S. and no supersonic engines have been certificated since the Olympus 593 Mk. 610-14-28 installed on the Concorde. This certification has since been surrendered and the engines are no longer in production. We are adopting CO and NO<E T="52">X</E>standards that will apply to future engine designs used on supersonic aircraft and for harmonization with ICAO standards.</P>
        <GPOTABLE CDEF="s50,r50,xs80,xs80" COLS="4" OPTS="L2,i1">
          <TTITLE>Table 3—Gaseous Emission Standards for Supersonic Engines</TTITLE>
          <BOXHD>
            <CHED H="1">Class</CHED>
            <CHED H="1">Rated output<LI>rO<SU>1</SU>(kN)</LI>
            </CHED>
            <CHED H="1">NO<E T="52">X</E>
              <LI>(g/kN)</LI>
            </CHED>
            <CHED H="1">CO<LI>(g/kN)</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">TSS</ENT>
            <ENT>All</ENT>
            <ENT>36 + 2.42 (rPR)</ENT>
            <ENT>4,550 (rPR)<E T="51">−1.03</E>
            </ENT>
          </ROW>
          <TNOTE>
            <SU>1</SU>rO is the rated output with afterburning applied.</TNOTE>
        </GPOTABLE>
        <HD SOURCE="HD3">7. Test Procedures</HD>
        <P>The amended test procedures adopted in § 34.60 are based on ICAO Annex 16, Volume II. The amendments to Annex 16 Volume II include clarifications and add flexibilities for engine manufacturers. They are:</P>
        <P>• Standardizing the terminology relating to engine thrust/power.</P>
        <P>• Clarifying the need to correct measured results to standard reference day and reference engine conditions.</P>
        <P>• Allowing a certificating authority to approve the use of test fuels other than those specified during certification testing.</P>
        <P>• Allowing materials other than stainless steel in the sample collection equipment.</P>
        <P>• Clarifying the appropriate value of fuel flow to be used at each LTO test point.</P>
        <P>• Clarifying exhaust nozzle terminology for exhaust emissions sampling.</P>
        <P>• Allowing an equivalent procedure for gaseous emission and smoke measurement if approved by the certificating authority.</P>
        <P>Many manufacturers are already voluntarily complying with these changes. The U.S. adoption of these test procedure amendments is unlikely to require new action by manufacturers. To accomplish the above changes, we have revised § 34.60 and removed §§ 34.61 through 34.64, and 34.71. This action eliminates subpart H of part 34, and we have removed cross references to subpart H in the affected sections where they appear.</P>
        <HD SOURCE="HD3">8. Definitions</HD>
        <P>In promulgating the new standards, the EPA adopted several new definitions for terms in its regulations. The FAA is including seven of these definitions in § 34.1 to avoid any uncertainty about their meaning and application. These definitions are consistent with CAEP/8 usage, and the common understanding of these terms as used by industry. The terms and definitions have the same scope and meaning as they have in 40 CFR part 87. Since the regulation includes the terms and their definitions, they are not being repeated here.</P>
        <HD SOURCE="HD3">9. Derivative Engines</HD>
        <P>Often manufacturers will make changes to a type certificated engine that is in production while keeping the same basic engine core and combustor design. In some cases, these modifications may affect emissions. We are adopting the term “derivative engine for emissions certification purposes” to distinguish an engine model for which the emission characteristics vary from the original type certificated engine design, but remain within the criteria specified in § 34.48.</P>
        <P>The FAA has adopted the EPA's rule text in § 34.48 that uses the phrase “similar in design to a previously certificated (original) engine for purposes of compliance” with the emissions standards. The FAA understands the “original” to be a previously type certificated engine for which there is test data. That test data will be used in determining whether the new engine may be considered a derivative using the criteria in § 34.48.</P>

        <P>To qualify as a derivative engine for emissions certification purposes, an engine must comply with the emission standards associated with the original type certificated engine. The derivative engine must have the same or similar emission characteristics as the original type certificated engine; the original engine must be listed on a U.S. type certificate issued under part 33. The FAA will make the following determinations regarding derivatives:<PRTPAGE P="76847"/>
        </P>
        <P>• Whether the emission characteristics of the modified design are significantly different from the original type certificated engine's emissions such that a demonstration of compliance with more recent emission standards is necessary;</P>
        <P>• Whether the changes are minor relative to the original type certificated engine's emissions, such that it may be considered a derivative version of the original type certificated engine model with no emissions changes;</P>
        <P>• Whether iterative changes made over time resulted in a cumulative change that reaches the point at which a new demonstration of compliance is warranted.</P>
        <P>In the past, these determinations were made for turbofan engines by an engineering evaluation that was performed by the engine manufacturer and then reviewed by the FAA. The definition of “derivative engines for emissions certification purposes,” along with the criteria for making this determination, will provide engine manufacturers and the FAA with more certainty regarding emission standard requirements for future modifications made to certificated models. The FAA will continue its existing practices for determining derivatives for part 33 engine certification, expanding those practices to make “derivative engines for emissions certification” determinations under the criteria promulgated by the EPA and adopted here into § 34.48.</P>
        <P>If a derivative engine is sufficiently similar to its original type certificated engine so as to meet the criteria established in § 34.48, the manufacturer may demonstrate certification compliance and continue production of the engine model to the same extent as allowed for the original engine model. However, if a derivative engine is determined to be significantly different than the original type certificated engine, the manufacturer would be required to demonstrate compliance with the most recent emission standards. This determination will be made using numerical criteria consistent with ICAO provisions. An engine model may be considered a derivative only if:</P>
        <P>1. It is a modification of an engine that received a U.S. type certificate;</P>
        <P>2. The engine was certificated under 14 CFR part 33; and</P>
        <P>3. One of the following conditions is met:</P>
        <P>• If the FAA determines that a safety issue exists that requires an engine modification; or</P>
        <P>• If emissions from the derivative engines are equivalent to or lower than the original type certificated engine.</P>
        <P>This final rule provides that an engine manufacturer may show emissions equivalency by demonstrating that the difference between emission rates of a derivative engine and the original type certificated engine are within the following allowable ranges (unless otherwise adjusted using good engineering judgment as determined by the FAA):</P>
        <P>• ± 3.0 g/kN for NO<E T="52">X</E>,</P>
        <P>• ± 1.0 g/kN for HC,</P>
        <P>• ± 5.0 g/kN for CO, and</P>
        <P>• ± 2.0 SN for smoke.</P>
        <P>This final rule also provides that an engine model whose characteristic level is at least 5 percent below all applicable standards would be allowed to demonstrate equivalency by engineering analysis. In all other cases, the manufacturer is required to test the new engine model to show emission equivalency.</P>
        <HD SOURCE="HD3">10. Abbreviations</HD>
        <P>Similar to the new terms being defined in § 34.1, certain abbreviations have been added or corrected in § 34.2. No separate discussion of them is included here. We are amending the text of §§ 34.10(a) and (b), 34.21(b) and (d), and 34.31(b) to include the correct notation of these abbreviations.</P>
        <HD SOURCE="HD3">11. Miscellaneous</HD>
        <P>In § 34.21(b) of the current regulation, there is a printing error. The formula for smoke number should have included “−0.274” as a superscript notation. Instead, it was printed in regular size text, implying a very different mathematical calculation. Since all other instances of the notation in paragraphs (d) and (e) of that section are correct, we are not aware that there has been any misunderstanding from this printing error, but we are correcting it here.</P>
        <P>The FAA is revising §§ 34.3(c) and (d), General requirements, to eliminate the use of the term Federal Aviation Regulation and its abbreviation, FAR. Neither term is correct. As regulations are amended, the FAA is removing these terms.</P>
        <P>In addition, the FAA is revising § 34.3(d) to remove the reference to 40 CFR 87.1(c) and replacing it with a reference to 40 CFR 87.1 as the EPA regulation no longer uses subparagraph designations in that section.</P>
        <HD SOURCE="HD3">12. Part 45—Identification Data</HD>
        <P>The new emission standards require the addition of new designations to identify the status of engines at manufacture. Section 45.13(a)(7) is being added to include the new designations EXEMPT NEW and EXCEPTED SPARE. Engines are already required to carry certain production markings, and this amendment merely adds the two new designations adopted in this final rule. The use of these new terms is required under §§ 34.7(h) and 34.9(a)(6).</P>
        <HD SOURCE="HD2">IV. Regulatory Notices and Analyses</HD>
        <HD SOURCE="HD3">A. Paperwork Reduction Act</HD>
        <P>The Paperwork Reduction Act of 1995 (44 U.S.C. 3507(d)) requires that the FAA consider the impact of paperwork and other information collection burdens imposed on the public. According to the 1995 amendments to the Paperwork Reduction Act (5 CFR 1320.8(b)(2)(vi)), an agency may not collect or sponsor the collection of information, nor may it impose an information collection requirement unless it displays a currently valid Office of Management and Budget (OMB) control number.</P>
        <P>This action contains an existing collection in use without an OMB control number. As required by the Paperwork Reduction Act of 1995 (44 U.S.C. 3507(d)), the FAA has submitted these information collection amendments to OMB for its review.</P>
        <P>
          <E T="03">Summary:</E>Under § 45.11, manufacturers of engines are required to mark each engine produced under a type certificate or production certificate by attaching a fireproof identification plate that contains the information specified in § 45.13. As part of the information required, § 45.13(a)(7) states that one of three designations (comply, exempt and non U.S.) that indicates compliance with the applicable exhaust emission provisions of part 34 and 40 CFR part 87 must be included. Under this final rule, the number of possible designations is being increased to five (comply, exempt, non U.S., excepted spare and exempt new), with the new designations having been adopted from the determinations made at ICAO CAEP/8.</P>
        <P>
          <E T="03">Use:</E>The information will be used by purchasers, owners, operators and FAA inspectors, periodically, to confirm that an engine meets the exhaust emission provisions of part 34 and 40 CFR part 87.</P>
        <P>
          <E T="03">Respondents (including number of):</E>There are currently 10 engine manufacturers that will be impacted by this requirement.</P>
        <P>
          <E T="03">Frequency:</E>This is a one time burden for each engine. The information required will be stamped on the<PRTPAGE P="76848"/>identification plate at the time of manufacture.</P>
        <P>
          <E T="03">Annual Burden Estimate:</E>We estimate that approximately 1,200 engines will be manufactured each year by 10 engine manufacturers and that stamping each identification plate will require 5 minutes. The annual burden is estimated to be 100 hours. We estimate that it will take 5 minutes to label each engine for an average cost of $3.75 for labor and materials for each engine. The total annual cost to respondents is estimated to be $4,500.</P>
        <P>The agency is soliciting comments to—</P>
        <P>(1) Evaluate whether the proposed information requirement is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
        <P>(2) Evaluate the accuracy of the agency's estimate of the burden;</P>
        <P>(3) Enhance the quality, utility, and clarity of the information to be collected; and</P>
        <P>(4) Minimize the burden of collecting information on those who are to respond, including by using appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology.</P>

        <P>Individuals and organizations may send comments on the information collection requirement to the address listed in the<E T="02">ADDRESSES</E>section at the beginning of this preamble by March 1, 2013. Comments also should be submitted to the Office of Management and Budget, Office of Information and Regulatory Affairs, Attention: Desk Officer for FAA, New Executive Building, Room 10202, 725 17th Street NW., Washington, DC 20503.</P>
        <HD SOURCE="HD3">B. Regulatory Evaluation</HD>
        <P>Changes to Federal regulations must undergo several economic analyses. First, Executive Order 12866 and Executive Order 13563 direct that each Federal agency shall propose or adopt a regulation only upon a reasoned determination that the benefits of the intended regulation justify its costs. Second, the Regulatory Flexibility Act of 1980 (Pub. L. 96-354) requires agencies to analyze the economic impact of regulatory changes on small entities. Third, the Trade Agreements Act (Pub. L. 96-39) prohibits agencies from setting standards that create unnecessary obstacles to the foreign commerce of the United States. In developing U.S. standards, the Trade Act requires agencies to consider international standards and, where appropriate, that they be the basis of U.S. standards. Fourth, the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4) requires agencies to prepare a written assessment of the costs, benefits, and other effects of proposed or final rules that include a Federal mandate likely to result in the expenditure by State, local, or tribal governments, in the aggregate, or by the private sector, of $100 million or more annually (adjusted for inflation with base year of 1995). This portion of the preamble summarizes the FAA's analysis of the economic impacts of this final rule.</P>
        <P>Department of Transportation Order DOT 2100.5 prescribes policies and procedures for simplification, analysis, and review of regulations. If the expected cost impact is so minimal that a proposed or final rule does not warrant a full evaluation, this order permits that a statement to that effect and the basis for it to be included in the preamble if a full regulatory evaluation of the cost and benefits is not prepared. Such a determination has been made for this final rule. The reasoning for this determination follows:</P>
        <P>Rulemaking actions by the FAA usually trigger a full regulatory evaluation of the potential monetary costs that would be imposed and benefits generated (including separate analyses for regulatory flexibility, international trade impact, and unfunded mandates). However, this regulation brings the regulations in 14 CFR into conformity with the existing EPA regulations. A full regulatory evaluation is unwarranted because the FAA is not imposing any new standards on the aviation industry for engine emissions or test procedures. The EPA concluded (77 FR 36342, 36386, June 18, 2012) that its rule would impose minimal costs to manufacturers because the affected engines are designed for and marketed internationally, and thus are already being manufactured using the ICAO standards adopted in this rule.</P>
        <P>The FAA has made one addition to the standards adopted by the EPA. Previously, each affected engine had to be marked pursuant to 14 CFR part 45 as falling under one of three engine categories. The rule now requires that each affected engine has to be marked as falling under one of five engine categories. As all affected engines had to be marked under the previous rule, increasing the number of categories from three to five will not change the number of engines that need to be marked. The EPA rule required these markings be effective, but the requirement that controls engine marking exists only in 14 CFR part 45. Accordingly, the FAA is simply implementing the EPA requirement. The FAA has, therefore, determined that this final rule is not a “significant regulatory action” as defined in section 3(f) of Executive Order 12866, and is not “significant” as defined in DOT's Regulatory Policies and Procedures.</P>
        <HD SOURCE="HD3">C. Regulatory Flexibility Determination</HD>
        <P>The Regulatory Flexibility Act of 1980 (Pub. L. 96-354) (RFA) establishes “as a principle of regulatory issuance that agencies shall endeavor, consistent with the objectives of the rule and of applicable statutes, to fit regulatory and informational requirements to the scale of the businesses, organizations, and governmental jurisdictions subject to regulation.” To achieve this principle, agencies are required to solicit and consider flexible regulatory proposals and to explain the rationale for their actions to assure that such proposals are given serious consideration.” The RFA covers a wide-range of small entities, including small businesses, not-for-profit organizations, and small governmental jurisdictions.</P>
        <P>Agencies must perform a review to determine whether a rule will have a significant economic impact on a substantial number of small entities. If the agency determines that it will, the agency must prepare a regulatory flexibility analysis as described in the RFA.</P>
        <P>However, if an agency determines that a rule is not expected to have a significant economic impact on a substantial number of small entities, section 605(b) of the RFA provides that the head of the agency may so certify and a regulatory flexibility analysis is not required. The certification must include a statement providing the factual basis for this determination, and the reasoning should be clear.</P>
        <P>This final rule revises the emission standards for turbine engine airplanes, the test procedures for gaseous emissions, and the different engine categories for marking purposes. Other than the FAA marking requirement that involves minimal cost changes to engine manufacturers, all of the costs associated with this rule have been addressed by the EPA in its rulemaking. The EPA determined that its rule would impose minimal costs to manufacturers because the affected engines are designed for and marketed internationally, and thus are already being manufactured using the ICAO standards adopted in the EPA rule. Thus, this rule has a minimal economic impact.</P>

        <P>Therefore, as the FAA Acting Administrator, I certify that this rule will not have a significant economic impact on a substantial number of small entities.<PRTPAGE P="76849"/>
        </P>
        <HD SOURCE="HD3">D. International Trade Impact Assessment</HD>
        <P>The Trade Agreements Act of 1979 (Pub. L. 96-39), as amended by the Uruguay Round Agreements Act (Pub. L. 103-465), prohibits Federal agencies from establishing standards or engaging in related activities that create unnecessary obstacles to the foreign commerce of the United States. Pursuant to these Acts, the establishment of standards is not considered an unnecessary obstacle to the foreign commerce of the United States, so long as the standard has a legitimate domestic objective, such as the protection of safety, and does not operate in a manner that excludes imports that meet this objective. The statute also requires consideration of international standards and, where appropriate, that they be the basis for U.S. standards. The FAA has assessed the potential effect of this final rule and determined that it is in accord with the Trade Agreements Act, as the rule uses the ICAO international standards as the basis for the U.S. regulation.</P>
        <HD SOURCE="HD3">E. Unfunded Mandates Assessment</HD>
        <P>Title II of the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4) requires each Federal agency to prepare a written statement assessing the effects of any Federal mandate in a proposed or final agency rule that may result in an expenditure of $100 million or more (in 1995 dollars) in any one year by State, local, and tribal governments, in the aggregate, or by the private sector; such a mandate is deemed to be a “significant regulatory action.” The FAA currently uses an inflation-adjusted value of $143.1 million in lieu of $100 million. This final rule does not contain such a mandate; therefore, the requirements of Title II of the Act do not apply.</P>
        <HD SOURCE="HD3">F. International Compatibility and Cooperation</HD>
        <P>(1) In keeping with U.S. obligations under the Convention on International Civil Aviation, it is FAA policy to conform to International Civil Aviation Organization (ICAO) Standards and Recommended Practices to the maximum extent practicable. The FAA has reviewed the corresponding ICAO Standards and Recommended Practices and has identified no differences with these regulations.</P>
        <P>(2) Executive Order 13609, Promoting International Regulatory Cooperation, promotes international regulatory cooperation to meet shared challenges involving health, safety, labor, security, environmental, and other issues and to reduce, eliminate, or prevent unnecessary differences in regulatory requirements. The FAA has analyzed this action under the policies and agency responsibilities of Executive Order 13609, and has determined that this action would have no effect on international regulatory cooperation.</P>
        <HD SOURCE="HD3">G. Environmental Analysis</HD>

        <P>In accordance with FAA Order 1050.1E, the FAA has determined that this action is categorically excluded from environmental review under section 103(2)(c) of the National Environmental Policy Act (NEPA). This action is categorically excluded under FAA Order 1050.1E, Chapter 3, paragraph 312a, which covers “all FAA actions to ensure compliance with EPA aircraft emission standards.” This rule amends the emission standards for turbine engine powered airplanes and certain marking requirements for engines, to incorporate the standards adopted by EPA based on the ICAO standards for gaseous emissions of NO<E T="52">X</E>.</P>
        <HD SOURCE="HD1">Executive Order Determinations</HD>
        <HD SOURCE="HD1">Executive Order 13132, Federalism</HD>
        <P>The FAA has analyzed this final rule under the principles and criteria of Executive Order 13132, Federalism. We determined that this action will not have a substantial direct effect on the States, or the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, we determined that this final rule does not have federalism implications.</P>
        <HD SOURCE="HD1">Executive Order 13211, Regulations that Significantly Affect Energy Supply, Distribution, or Use</HD>
        <P>The FAA has analyzed this final rule under Executive Order 13211, Actions Concerning Regulations that Significantly Affect Energy Supply, Distribution, or Use, 66 FR 28355 (May 18, 2001). We have determined that it is not a “significant energy action” under the executive order because it is not a “significant regulatory action” under Executive Order 12866, and it is not likely to have a significant adverse effect on the supply, distribution, or use of energy.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <CFR>14 CFR Part 34</CFR>
          <P>Air pollution control, Aircraft, Incorporation by reference.</P>
          <CFR>14 CFR Part 45</CFR>
          <P>Aircraft, marking, identification data.</P>
        </LSTSUB>
        <HD SOURCE="HD1">The Amendments</HD>
        <P>In consideration of the foregoing, the Federal Aviation Administration amends Chapter I of Title 14 Code of Federal Regulations as follows:</P>
        <REGTEXT PART="34" TITLE="14">
          <PART>
            <HD SOURCE="HED">PART 34—FUEL VENTING AND EXHAUST EMISSION REQUIREMENTS FOR TURBINE ENGINE POWERED AIRPLANES</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 34 is revised to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C 4321<E T="03">et seq.,</E>7572l 49 U.S.C. 106(g), 40113, 44701-44702, 44704, 44714</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="34" TITLE="14">
          <SUBPART>
            <HD SOURCE="HED">Subpart A—[Amended]</HD>
          </SUBPART>
          <AMDPAR>2. In § 34.1, add in alphabetical order, the definitions for the terms “Characteristic level”, “Derivative engine for emissions certification purposes”, “Excepted”, “Exempt”, “Introduction date”, and “Tier”, and revise the definitions of “Commercial aircraft engine”, “Rated output (rO),” and “Rated pressure ratio (rPR)” to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 34.1</SECTNO>
            <SUBJECT>Definitions.</SUBJECT>
            <STARS/>
            <P>
              <E T="03">Characteristic level</E>has the meaning given in Appendix 6 of ICAO Annex 16 as of July 2008. The characteristic level is a calculated emission level for each pollutant based on a statistical assessment of measured emissions from multiple tests.<SU>1</SU>
              <FTREF/>
            </P>
            <FTNT>
              <P>

                <SU>1</SU>This incorporation by reference was approved by the Director of the Federal Register in accordance with 5 U.S.C. 552(a) and 1 CFR part 51. This document can be obtained from the ICAO, Document Sales Unit, 999 University Street, Montreal, Quebec H3C 5H7, Canada, phone +1 514-954-8022, or<E T="03">www.icao.int</E>or<E T="03">sales@icao.int.</E>Copies can be reviewed at the FAA New England Regional Office, 12 New England Executive Park, Burlington, Massachusetts, 781-238-7101, or at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to:<E T="03">http://www.archives.gov/federal_register/code_of_federal_regulations/ibr_locations.html.</E>
              </P>
            </FTNT>
            <STARS/>
            <P>
              <E T="03">Commercial aircraft engine</E>means any aircraft engine used or intended for use by an “air carrier” (including those engaged in “intrastate air transportation”) or a “commercial operator” (including those engaged in “intrastate air transportation”) as these terms are defined in Title 49 of the United States Code and Title 14 of the Code of Federal Regulations.</P>
            <STARS/>
            <P>
              <E T="03">Derivative engine for emissions certification purposes</E>means an engine that has the same or similar emissions characteristics as an engine covered by a U.S. type certificate issued under 14<PRTPAGE P="76850"/>CFR part 33. These characteristics are specified in § 34.48.</P>
            <STARS/>
            <P>
              <E T="03">Excepted,</E>as used in § 34.9, means an engine that may be produced and sold that does not meet otherwise applicable standards. Excepted engines must conform to regulatory conditions specified for an exception in § 34.9. Excepted engines are subject to the standards of this part even though they are not required to comply with the otherwise applicable requirements. Engines excepted with respect to certain standards must comply with other standards from which they are not specifically excepted.</P>
            <P>
              <E T="03">Exempt</E>means an engine that does not meet certain applicable standards but may be produced and sold under the terms allowed by a grant of exemption issued pursuant to § 34.7 of this part and part 11 of this chapter. Exempted engines must conform to regulatory conditions specified in the exemption as well as other applicable regulations. Exempted engines are subject to the standards of this part even though they are not required to comply with the otherwise applicable requirements. Engines exempted with respect to certain standards must comply with other standards as a condition of the exemption.</P>
            <STARS/>
            <P>
              <E T="03">Introduction date</E>means the date of manufacture of the first individual production engine of a given engine model or engine type certificate family to be certificated. Neither test engines nor engines not placed into service affect this date.</P>
            <STARS/>
            <P>
              <E T="03">Rated output (rO)</E>means the maximum power/thrust available for takeoff at standard day conditions as approved for the engine by the Federal Aviation Administration, including reheat contribution where applicable, but excluding any contribution due to water injection, expressed in kilowatts or kilonewtons (as applicable), rounded to at least three significant figures.</P>
            <P>
              <E T="03">Rated pressure ratio (rPR)</E>means the ratio between the combustor inlet pressure and the engine inlet pressure achieved by an engine operation at rated output, rounded to at least three significant figures.</P>
            <STARS/>
            <P>
              <E T="03">Tier,</E>as used in this part, is a designation related to the NO<E T="52">X</E>emission standard for the engine as specified in § 34.21 or § 34.23 of this part (e.g., Tier 0).</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="34" TITLE="14">
          <AMDPAR>3. In § 34.2, remove the abbreviation for the term “W Watt(s)” and add the abbreviations for the terms “Carbon dioxide”, “Gram(s)”, “Kilonewton(s)”, “Kilowatt(s)”, and “Pound(s)” to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 34.2</SECTNO>
            <SUBJECT>Abbreviations.</SUBJECT>
            <STARS/>
            <P>CO<E T="52">2</E>Carbon dioxide</P>
            <STARS/>
            <P>g Gram(s)</P>
            <STARS/>
            <P>kN Kilonewton(s)</P>
            <P>kW Kilowatt(s)</P>
            <P>lb Pound(s)</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="34" TITLE="14">
          <AMDPAR>4. In § 34.3, revise paragraphs (c) and (d) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 34.3</SECTNO>
            <SUBJECT>General requirements.</SUBJECT>
            <STARS/>
            <P>(c)<E T="03">U.S. airplanes.</E>This part applies to civil airplanes that are powered by aircraft gas turbine engines of the classes specified herein and that have U.S. standard airworthiness certificates.</P>
            <P>(d)<E T="03">Foreign airplanes.</E>Pursuant to the definition of “aircraft” in 40 CFR 87.1, this regulation applies to civil airplanes that are powered by aircraft gas turbine engines of the classes specified herein and that have foreign airworthiness certificates that are equivalent to U.S. standard airworthiness certificates. This regulation applies only to those foreign civil airplanes that, if registered in the United States, would be required by applicable regulations to have a U.S. standard airworthiness certificate in order to conduct the operations intended for the airplane. Pursuant to 40 CFR 87.3(c), this regulation does not apply where it would be inconsistent with an obligation assumed by the United States to a foreign country in a treaty, convention, or agreement.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="34" TITLE="14">
          <AMDPAR>5. In § 34.7, amend paragraph (b) by adding a sentence at the end of the paragraph and by revising paragraph (d) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 34.7</SECTNO>
            <SUBJECT>Exemptions.</SUBJECT>
            <STARS/>
            <P>(b) * * * This exemption is limited to the requirements of § 34.21 only.</P>
            <STARS/>
            <P>(d)<E T="03">Applicants seeking exemption from other emissions standards of this part and 40 CFR part 87.</E>Applicants must request exemption from both the FAA and the EPA, even where the underlying regulatory requirements are the same. The FAA and EPA will jointly consider such exemption requests, and will assure consistency in the respective agency determinations.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="34" TITLE="14">
          <AMDPAR>6. Add § 34.9 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 34.9</SECTNO>
            <SUBJECT>Exceptions.</SUBJECT>
            <P>(a)<E T="03">Spare engines.</E>Certain engines that meet the following description are excepted:</P>
            <P>(1) This exception allows production of an engine for installation on an in-service aircraft. A spare engine may not be installed on a new aircraft.</P>
            <P>(2) Each spare engine must be identical to a sub-model previously certificated to meet all applicable requirements.</P>
            <P>(3) A spare engine may be used only when the emissions of the spare do not exceed the certification requirements of the original engine, for all regulated pollutants.</P>
            <P>(4) No separate approval is required to produce spare engines.</P>
            <P>(5) The record for each engine excepted under this paragraph (c) must indicate that the engine was produced as an excepted spare engine.</P>
            <P>(6) Engines produced under this exception must be labeled “EXCEPTED SPARE” in accordance with § 45.13 of this chapter.</P>

            <P>(b) On and after July 18, 2012, and before August 31, 2013, a manufacturer may produce up to six Tier 4 compliant engines that meet the NO<E T="52">X</E>standards of paragraph (d)(1)(vi) of this section rather than § 34.23(a)(2). No separate approval is required to produce these engines. Engines produced under this exception are to be labeled “COMPLY” in accordance with § 45.13 of this chapter.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="34" TITLE="14">
          <SUBPART>
            <HD SOURCE="HED">Subpart B—Engine Fuel Venting Emissions (New and In-Use Aircraft Gas Turbine Engines)</HD>
          </SUBPART>
          <AMDPAR>7. Revise § 34.10 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 34.10</SECTNO>
            <SUBJECT>Applicability.</SUBJECT>
            <P>(a) The provisions of this subpart are applicable to all new aircraft gas turbine engines of classes T3, T8, TSS, and TF equal to or greater than 36 kN (8,090 lb) rated output, manufactured on or after January 1, 1974, and to all in-use aircraft gas turbine engines of classes T3, T8, TSS, and TF equal to or greater than 36 kN (8,090 lb) rated output manufactured after February 1, 1974.</P>
            <P>(b) The provisions of this subpart are also applicable to all new aircraft gas turbine engines of class TF less than 36 kN (8,090 lb) rated output and class TP manufactured on or after January 1, 1975, and to all in-use aircraft gas turbine engines of class TF less than 36 kN (8,090 lb) rated output and class TP manufactured after January 1, 1975.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="34" TITLE="14">
          <SUBPART>
            <PRTPAGE P="76851"/>
            <HD SOURCE="HED">Subpart C—Exhaust Emissions (New Aircraft Gas Turbine Engines)</HD>
          </SUBPART>
          <AMDPAR>8. In § 34.21, revise paragraphs (b), (d), (e), and (f), and add paragraph (g) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 34.21</SECTNO>
            <SUBJECT>Standards for exhaust emission.</SUBJECT>
            <STARS/>
            <P>(b) Exhaust emissions of smoke from each new aircraft gas turbine engine of class TF and of rated output of 129 kN (29,000 lb) thrust or greater, manufactured on or after January 1, 1976, shall not exceed</P>
            
            <FP SOURCE="FP-2">SN = 83.6 (rO)<E T="51">−0.274</E>(rO is in kN).</FP>
            
            <STARS/>
            <P>(d) Gaseous exhaust emissions from each new aircraft gas turbine engine shall not exceed:</P>
            <P>(1) For Classes TF, T3, T8 engines greater than 26.7 kN (6,000 lb) rated output:</P>
            <P>(i) Engines manufactured on or after January 1, 1984:</P>
            
            <FP SOURCE="FP-2">Hydrocarbons: 19.6 g/kN rO.</FP>
            
            <P>(ii) Engines manufactured on or after July 7, 1997:</P>
            
            <FP SOURCE="FP-2">Carbon Monoxide: 118 g/kN rO.</FP>
            
            <P>(iii) Engines of a type or model of which the date of manufacture of the first individual production model was on or before December 31, 1995, and for which the date of manufacture of the individual engine was on or before December 31, 1999 (Tier 2):</P>
            
            <FP SOURCE="FP-2">Oxides of Nitrogen: (40+2(rPR)) g/kN rO.</FP>
            
            <P>(iv) Engines of a type or model of which the date of manufacture of the first individual production model was after December 31, 1995, or for which the date of manufacture of the individual engine was after December 31, 1999 (Tier 2):</P>
            
            <FP SOURCE="FP-2">Oxides of Nitrogen: (32+1.6(rPR)) g/kN rO.</FP>
            
            <P>(v) The emission standards prescribed in paragraphs (d)(1)(iii) and (iv) of this section apply as prescribed beginning July 7, 1997.</P>
            <P>(vi) The emission standards of this paragraph apply as prescribed after December 18, 2005. For engines of a type or model of which the first individual production model was manufactured after December 31, 2003 (Tier 4):</P>
            <P>(A) That have a rated pressure ratio of 30 or less and a maximum rated output greater than 89 kN:</P>
            
            <FP SOURCE="FP-2">Oxides of Nitrogen: (19 + 1.6(rPR)) g/kN rO.</FP>
            
            <P>(B) That have a rated pressure ratio of 30 or less and a maximum rated output greater than 26.7 kN but not greater than 89 kN:</P>
            
            <FP SOURCE="FP-2">Oxides of Nitrogen: (37.572 + 1.6(rPR) − 0.2087(rO)) g/kN rO.</FP>
            
            <P>(C) That have a rated pressure ratio greater than 30 but less than 62.5, and a maximum rated output greater than 89 kN:</P>
            
            <FP SOURCE="FP-2">Oxides of Nitrogen: (7 + 2(rPR)) g/kN rO.</FP>
            
            <P>(D) That have a rated pressure ratio greater than 30 but less than 62.5, and a maximum rated output greater than 26.7 kN but not greater than 89 kN:</P>
            
            <FP SOURCE="FP-2">Oxides of Nitrogen: (42.71 + 1.4286(rPR) − 0.4013(rO) + 0.00642(rPR × rO)) g/kN rO.</FP>
            
            <P>(E) That have a rated pressure ratio of 62.5 or more:</P>
            
            <FP SOURCE="FP-2">Oxides of Nitrogen: (32 + 1.6(rPR)) g/kN rO.</FP>
            
            <P>(2) For Class TSS Engines manufactured on or after January 1, 1984:</P>
            
            <FP SOURCE="FP-2">Hydrocarbons: 140 (0.92)<SU>rPR</SU>g/kN rO.</FP>
            
            <P>(e) Smoke exhaust emissions from each gas turbine engine of the classes specified below shall not exceed:</P>
            <P>(1) For Class TF of rated output less than 26.7 kN (6,000 lb) manufactured on or after August 9, 1985:</P>
            
            <FP SOURCE="FP-2">SN = 83.6(rO)<E T="51">−0.274</E>(rO is in kN) not to exceed a maximum of SN = 50.</FP>
            
            <P>(2) For Classes T3, T8, TSS, and TF of rated output equal to or greater than 26.7 kN (6,000 lb) manufactured on or after January 1, 1984:</P>
            
            <FP SOURCE="FP-2">SN = 83.6(rO)<E T="51">−0.274</E>(rO is in kN) not to exceed a maximum of SN = 50.</FP>
            
            <P>(3) For Class TP of rated output equal to or greater than 1,000 kW manufactured on or after January 1, 1984:</P>
            
            <FP SOURCE="FP-2">SN = 187(rO)<E T="51">−0.168</E>(rO is in kW).</FP>
            
            <P>(f) The standards set forth in paragraphs (a), (b), (c), (d), and (e) of this section refer to a composite gaseous emission sample representing the operation cycles and exhaust smoke emission emitted during operation of the engine as specified in the applicable sections of subpart G of this part, and measured and calculated in accordance with the procedures set forth in subpart G.</P>
            <P>(g) Where a gaseous emission standard is specified by a formula, calculate and round the standard to three significant figures or to the nearest 0.1 g/kN (for standards at or above 100 g/kN). Where a smoke standard is specified by a formula, calculate and round the standard to the nearest 0.1 SN. Engines comply with an applicable standard if the testing results show that the engine type certificate family's characteristic level does not exceed the numerical level of that standard, as described in § 34.60.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="34" TITLE="14">
          <AMDPAR>9. Add § 34.23 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 34.23</SECTNO>
            <SUBJECT>Exhaust Emission Standards for Engines Manufactured On and After July 18, 2012.</SUBJECT>
            <P>The standards of this section apply to aircraft engines manufactured on and after July 18, 2012, unless otherwise exempted or excepted. Where a gaseous emission standard is specified by a formula, calculate and round the standard to three significant figures or to the nearest 0.1 g/kN (for standards at or above 100 g/kN). Where a smoke standard is specified by a formula, calculate and round the standard to the nearest 0.1 SN. Engines comply with an applicable standard if the testing results show that the engine type certificate family's characteristic level does not exceed the numerical level of that standard, as described in § 34.60.</P>
            <P>(a) Gaseous exhaust emissions from each new aircraft gas turbine engine shall not exceed:</P>
            <P>(1) For Classes TF, T3 and T8 of rated output less than 26.7 kN (6,000 lb) manufactured on and after July 18, 2012:</P>
            
            <FP SOURCE="FP-2">SN = 83.6(rO)<E T="51">−0.274</E>or 50.0, whichever is smaller</FP>
            
            <P>(2) Except as provided in §§ 34.9(b) and 34.21(c), for Classes TF, T3 and T8 engines manufactured on and after July 18, 2012, and for which the first individual production model was manufactured on or before December 31, 2013 (Tier 6):</P>
            <GPOTABLE CDEF="xs56,r50,r50,r100" COLS="4" OPTS="L2,i1">
              <TTITLE>Tier 6 Oxides of Nitrogen Emission Standards for Subsonic Engines</TTITLE>
              <BOXHD>
                <CHED H="1">Class</CHED>
                <CHED H="1">Rated pressure ratio—rPR</CHED>
                <CHED H="1">Rated output rO (kN)</CHED>
                <CHED H="1">NO<E T="52">X</E>(g/kN)</CHED>
              </BOXHD>
              <ROW RUL="n,n,s">
                <ENT I="01">TF, T3, T8</ENT>
                <ENT>rPR ≤ 30</ENT>
                <ENT>26.7 &lt; rO &lt; 89.0</ENT>
                <ENT>38.5486 + 1.6823 (rPR) − 0.2453 (rO) − (0.00308 (rPR) (rO))</ENT>
              </ROW>
              <ROW RUL="n,s">
                <ENT I="22"/>
                <ENT O="xl"/>
                <ENT>rO &gt; 89.0</ENT>
                <ENT>16.72 + 1.4080 (rPR)</ENT>
              </ROW>
              <ROW RUL="n,n,s">
                <PRTPAGE P="76852"/>
                <ENT I="22"/>
                <ENT>30 &lt; rPR &lt; 82.6</ENT>
                <ENT>26.7 &lt; rO ≤ 89.0</ENT>
                <ENT>46.1600 + 1.4286 (rPR) − 0.5303 (rO) + (0.00642 (rPR) (rO))</ENT>
              </ROW>
              <ROW RUL="n,s">
                <ENT I="22"/>
                <ENT O="xl"/>
                <ENT>rO &gt; 89.0</ENT>
                <ENT>−1.04 + 2.0 (rPR)</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
                <ENT>rPR ≥ 82.6</ENT>
                <ENT>All</ENT>
                <ENT>32 + 1.6 (rPR)</ENT>
              </ROW>
            </GPOTABLE>
            <P>(3) Engines exempted from paragraph (a)(2) of this section produced on or before December 31, 2016 must be labeled “EXEMPT NEW” in accordance with § 45.13 of this chapter. No exemptions to the requirements of paragraph (a)(2) of this section will be granted after December 31, 2016.</P>
            <P>(4) For Class TSS Engines manufactured on and after July 18, 2012:</P>
            <GPOTABLE CDEF="s50,r50,xs80,xs80" COLS="4" OPTS="L2,i1">
              <TTITLE>Gaseous Emission Standards for Supersonic Engines</TTITLE>
              <BOXHD>
                <CHED H="1">Class</CHED>
                <CHED H="1">Rated output<LI>rO<SU>1</SU>(kN)</LI>
                </CHED>
                <CHED H="1">NO<E T="52">X</E>
                  <LI>(g/kN)</LI>
                </CHED>
                <CHED H="1">CO<LI>(g/kN)</LI>
                </CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">TSS</ENT>
                <ENT>All</ENT>
                <ENT>36 + 2.42 (rPR)</ENT>
                <ENT>4,550 (rPR)<E T="51">−1.03</E>
                </ENT>
              </ROW>
              <TNOTE>
                <SU>1</SU>rO is the rated output with afterburning applied.</TNOTE>
            </GPOTABLE>
            <P>(b) Gaseous exhaust emissions from each new aircraft gas turbine engine shall not exceed:</P>
            <P>(1) For Classes TF, T3 and T8 engines of a type or model of which the first individual production model was manufactured after December 31, 2013 (Tier 8):</P>
            <GPOTABLE CDEF="xs56,r50,r50,r100" COLS="4" OPTS="L2,i1">
              <TTITLE>Tier 8 Oxides of Nitrogen Emission Standards for Subsonic Engines</TTITLE>
              <BOXHD>
                <CHED H="1">Class</CHED>
                <CHED H="1">Rated pressure ratio—rPR</CHED>
                <CHED H="1">Rated output<LI>rO (kN)</LI>
                </CHED>
                <CHED H="1">NOx<LI>(g/kN)</LI>
                </CHED>
              </BOXHD>
              <ROW RUL="n,n,s">
                <ENT I="01">TF, T3, T8</ENT>
                <ENT>rPR ≤ 30</ENT>
                <ENT>26.7 &lt; rO &lt; 89.0</ENT>
                <ENT>40.052 + 1.5681 (rPR) − 0.3615 (rO) − (0.0018 (rPR) (rO))</ENT>
              </ROW>
              <ROW RUL="n,s">
                <ENT I="22"/>
                <ENT O="xl"/>
                <ENT>rO &gt; 89.0</ENT>
                <ENT>7.88 + 1.4080 (rPR)</ENT>
              </ROW>
              <ROW RUL="n,n,s">
                <ENT I="22"/>
                <ENT>30 &lt; rPR &lt; 104.7</ENT>
                <ENT>26.7 &lt; rO &lt; 89.0</ENT>
                <ENT>41.9435 + 1.505 (rPR) − 0.5823 (rO) + (0.005562 (rPR) (rO))</ENT>
              </ROW>
              <ROW RUL="n,s">
                <ENT I="22"/>
                <ENT O="xl"/>
                <ENT>rO &gt; 89.0</ENT>
                <ENT>−9.88 + 2.0 (rPR)</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
                <ENT>rPR ≥ 104.7</ENT>
                <ENT>All</ENT>
                <ENT>32 + 1.6 (rPR)</ENT>
              </ROW>
            </GPOTABLE>

            <P>(c) Engines (including engines that are determined to be derivative engines for the purposes of emission certification) type certificated with characteristic levels at or below the NO<E T="52">X</E>standards of § 34.21(d)(1)(vi) of this part (as applicable based on rated output and rated pressure ratio) and introduced before July 18, 2012, may be produced through December 31, 2012, without meeting the NO<E T="52">X</E>standard of paragraph (a)(2) of this section.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="34" TITLE="14">
          <AMDPAR>10. In § 34.31, revise paragraphs (b) and (c) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 34.31</SECTNO>
            <SUBJECT>Standards for exhaust emissions.</SUBJECT>
            <STARS/>
            <P>(b) Exhaust emissions of smoke from each in-use aircraft gas turbine engine of Class TF and of rated output of 129 kN (29,000 lb) thrust or greater, beginning January l, 1976, shall not exceed</P>
            
            <FP SOURCE="FP-2">SN=83.6(rO)<E T="51">−0.274</E>(rO is in kN).</FP>
            
            <P>(c) The standards set forth in paragraphs (a) and (b) of this section refer to exhaust smoke emission emitted during operation of the engine as specified in the applicable sections of subpart G of this part, and measured and calculated in accordance with the procedures set forth in subpart G.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="34" TITLE="14">
          <SUBPART>
            <HD SOURCE="HED">Subpart E—Certification Provisions</HD>
          </SUBPART>
          <AMDPAR>11. Add § 34.48 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 34.48</SECTNO>
            <SUBJECT>Derivative engines for emissions certification purposes.</SUBJECT>
            <P>(a)<E T="03">General.</E>A derivative engine for emissions certification purposes is an engine configuration that is determined to be similar in design to a previously certificated (original) engine for purposes of compliance with exhaust emissions standards (gaseous and smoke). A type certificate holder may request from the FAA a determination that an engine configuration is considered a derivative engine for emissions certification purposes. To be considered a derivative engine for emission purposes under this part, the configuration must have been derived from the original engine that was certificated to the requirements of part 33 of this chapter and one of the following:</P>
            <P>(1) The FAA has determined that a safety issue exists that requires an engine modification.</P>
            <P>(2) Emissions from the derivative engines are determined to be similar. In general, this means the emissions must meet the criteria specified in paragraph (b) of this section. The FAA may amend the criteria of paragraph (b) in unusual circumstances, for individual cases, consistent with good engineering judgment.</P>

            <P>(3) All of the regulated emissions from the derivative engine are lower than the original engine.<PRTPAGE P="76853"/>
            </P>
            <P>(b)<E T="03">Emissions similarity.</E>(1) The type certificate holder must demonstrate that the proposed derivative engine model's emissions meet the applicable standards and differ from the original model's emission rates only within the following ranges:</P>
            <P>(i) ± 3.0 g/kN for NO<E T="52">X</E>.</P>
            <P>(ii) ± 1.0 g/kN for HC.</P>
            <P>(iii) ± 5.0 g/kN for CO.</P>
            <P>(iv) ± 2.0 SN for smoke.</P>
            <P>(2) If the characteristic level of the original certificated engine model (or any other sub-models within the emission type certificate family tested for certification) before modification is at or above 95% of the applicable standard for any pollutant, an applicant must measure the proposed derivative engine model's emissions for all pollutants to demonstrate that the derivative engine's resulting characteristic levels will not exceed the applicable emission standards. If the characteristic levels of the originally certificated engine model (and all other sub-models within the emission type certificate family tested for certification) are below 95% of the applicable standard for each pollutant, the applicant may use engineering analysis consistent with good engineering judgment to demonstrate that the derivative engine will not exceed the applicable emission standards. The engineering analysis must address all modifications from the original engine, including those approved for previous derivative engines.</P>
            <P>(c)<E T="03">Continued production allowance.</E>Derivative engines for emissions certification purposes may continue to be produced after the applicability date for new emissions standards when the engines conform to the specifications of this section.</P>
            <P>(d)<E T="03">Non-derivative engines.</E>If the FAA determines that an engine model does not meet the requirements for a derivative engine for emissions certification purposes, the type certificate holder is required to demonstrate that the engine complies with the emissions standards applicable to a new engine type.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="34" TITLE="14">
          <SUBPART>
            <HD SOURCE="HED">Subpart G—Test Procedures for Engine Exhaust Gaseous Emissions (Aircraft and Aircraft Gas Turbine Engines)</HD>
          </SUBPART>
          <AMDPAR>12. Revise § 34.60 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 34.60</SECTNO>
            <SUBJECT>Introduction.</SUBJECT>
            <P>(a) Use the equipment and procedures specified in Appendix 3, Appendix 5, and Appendix 6 of ICAO Annex 16, as applicable, to demonstrate whether engines meet the applicable gaseous emission standards specified in subpart C of this part. Measure the emissions of all regulated gaseous pollutants. Use the equipment and procedures specified in Appendix 2 and Appendix 6 of ICAO Annex 16 to determine whether engines meet the applicable smoke standard specified in subpart C of this part. The compliance demonstration consists of establishing a mean value from testing the specified number of engines, then calculating a “characteristic level” by applying a set of statistical factors that take into account the number of engines tested. Round each characteristic level to the same number of decimal places as the corresponding emission standard. For turboprop engines, use the procedures specified for turbofan engines, consistent with good engineering judgment.</P>
            <P>(b) Use a test fuel that meets the specifications described in Appendix 4 of ICAO Annex 16. The test fuel must not have additives whose purpose is to suppress smoke, such as organometallic compounds.</P>
            <P>(c) Prepare test engines by including accessories that are available with production engines if they can reasonably be expected to influence emissions. The test engine may not extract shaft power or bleed service air to provide power to auxiliary gearbox-mounted components required to drive aircraft systems.</P>
            <P>(d) Test engines must reach a steady operating temperature before the start of emission measurements.</P>
            <P>(e) In consultation with the EPA, the FAA may approve alternative procedures for measuring emissions, including testing and sampling methods, analytical techniques, and equipment specifications that differ from those specified in this part. Manufacturers and operators may request approval of alternative procedures by written request with supporting justification to the FAA Aircraft Certification Office and to the Designated EPA Program Officer. To be approved, one of the following conditions must be met:</P>
            <P>(1) The engine cannot be tested using the specified procedures; or</P>
            <P>(2) The alternative procedure is shown to be equivalent to, or more accurate or precise than, the specified procedure.</P>
            <P>(f) The following landing and takeoff (LTO) cycles apply for emissions testing and for calculating weighted LTO values:</P>
            <GPOTABLE CDEF="s25,10,10,10,10,10,10" COLS="7" OPTS="L2,i1">
              <TTITLE>LTO Test Cycles and Time in Mode</TTITLE>
              <BOXHD>
                <CHED H="1">Mode</CHED>
                <CHED H="1">Class</CHED>
                <CHED H="2">TP</CHED>
                <CHED H="3">TIM (min)</CHED>
                <CHED H="3">% of rO</CHED>
                <CHED H="2">TF, T3, T8</CHED>
                <CHED H="3">TIM (min)</CHED>
                <CHED H="3">% of rO</CHED>
                <CHED H="2">TSS</CHED>
                <CHED H="3">TIM (min)</CHED>
                <CHED H="3">% of rO</CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">Taxi/idle</ENT>
                <ENT>26.0</ENT>
                <ENT>7</ENT>
                <ENT>26.0</ENT>
                <ENT>7</ENT>
                <ENT>26.0</ENT>
                <ENT>5.8</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Takeoff</ENT>
                <ENT>0.5</ENT>
                <ENT>100</ENT>
                <ENT>0.7</ENT>
                <ENT>100</ENT>
                <ENT>1.2</ENT>
                <ENT>100</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Climbout</ENT>
                <ENT>2.5</ENT>
                <ENT>90</ENT>
                <ENT>2.2</ENT>
                <ENT>85</ENT>
                <ENT>2.0</ENT>
                <ENT>65</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Descent</ENT>
                <ENT>NA</ENT>
                <ENT>NA</ENT>
                <ENT>NA</ENT>
                <ENT>NA</ENT>
                <ENT>1.2</ENT>
                <ENT>15</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Approach</ENT>
                <ENT>4.5</ENT>
                <ENT>30</ENT>
                <ENT>4.0</ENT>
                <ENT>30</ENT>
                <ENT>2.3</ENT>
                <ENT>34</ENT>
              </ROW>
            </GPOTABLE>
            <P>(g) Engines comply with an applicable standard if the testing results show that the engine type certificate family's characteristic level does not exceed the numerical level of that standard, as described in the applicable appendix of Annex 16.</P>

            <P>(h) The system and procedure for sampling and measurement of gaseous emissions shall be as specified by in Appendices 2, 3, 4, 5 and 6 to the International Civil Aviation Organization (ICAO) Annex 16, Environmental Protection, Volume II, Aircraft Engine Emissions, Third Edition, July 2008. This incorporation by reference was approved by the Director of the Federal Register in accordance with 5 U.S.C. 552(a) and 1 CFR part 51. This document can be obtained from the ICAO, Document Sales Unit, 999 University Street, Montreal, Quebec H3C 5H7, Canada, phone +1 514-954-8022, or<E T="03">www.icao.int</E>or<E T="03">sales@icao.int.</E>Copies can be reviewed at the FAA New England Regional Office, 12 New<PRTPAGE P="76854"/>England Executive Park, Burlington, Massachusetts, 781-238-7101, or at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to:<E T="03">http://www.archives.gov/federal_register/code_of_federal_regulations/ibr_locations.html.</E>
            </P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="34" TITLE="14">
          <SECTION>
            <SECTNO>§§ 34.61-34.64</SECTNO>
            <SUBJECT>[Reserved]</SUBJECT>
          </SECTION>
          <AMDPAR>13. Remove and reserve §§ 34.61-34.64.</AMDPAR>
          <SECTION>
            <SECTNO>§ 34.71</SECTNO>
            <SUBJECT>[Reserved]</SUBJECT>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="34" TITLE="14">
          <AMDPAR>14. Remove and reserve § 34.71.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="34" TITLE="14">
          <SUBPART>
            <HD SOURCE="HED">Subpart H—[Removed]</HD>
          </SUBPART>
          <AMDPAR>15. Remove subpart H, consisting of §§ 34.80 through 34.89.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="45" TITLE="14">
          <PART>
            <HD SOURCE="HED">PART 45—IDENTIFICATION AND REGISTRATION MARKING</HD>
          </PART>
          <AMDPAR>16. The authority citation for part 45 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 106(g), 40103, 40113-40114, 44101-44105, 44107-44111, 44504, 44701, 44708-44709, 44711-44713, 44725, 45302-45303, 46104, 46304, 46306, 47122.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="45" TITLE="14">
          <SUBPART>
            <HD SOURCE="HED">Subpart B—Identification of Aircraft and Related Products</HD>
          </SUBPART>
          <AMDPAR>17. In § 45.13, revise paragraph (a)(7) introductory text and add paragraphs (a)(7)(iv) and (a)(7)(v) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 45.13</SECTNO>
            <SUBJECT>Identification data.</SUBJECT>
            <P>(a) * * *</P>
            <P>(7) On or after January 1, 1984, for aircraft engines specified in part 34 of this chapter, the date of manufacture as defined in § 34.1 of this chapter, and a designation, approved by the FAA, that indicates compliance with the applicable exhaust emission provisions of part 34 of this chapter and 40 CFR part 87. Approved designations include COMPLY, EXEMPT, and NON-US, as appropriate. After December 31, 2012, approved designations also include EXEMPT NEW, and EXCEPTED SPARE, as appropriate.</P>
            <STARS/>
            <P>(iv) The designation EXEMPT NEW indicates that the engine has been granted an exemption pursuant to the applicable provision of § 34.7(h) of this chapter; the designation must be noted in the permanent powerplant record that accompanies the engine from the time of its manufacture.</P>
            <P>(v) The designation EXCEPTED SPARE indicates that the engine has been excepted pursuant to the applicable provision of § 34.9(b) of this chapter; the designation must be noted in the permanent powerplant record that accompanies the engine from the time of its manufacture.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Issued in Washington, DC, on December 14, 2012.</DATED>
          <NAME>Michael P. Huerta,</NAME>
          <TITLE>Acting Administrator.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31109 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-13-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
        <CFR>17 CFR Part 275</CFR>
        <DEPDOC>[Release No. IA-3522; File No. S7-23-07]</DEPDOC>
        <RIN>RIN 3235-AL28</RIN>
        <SUBJECT>Temporary Rule Regarding Principal Trades With Certain Advisory Clients</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Securities and Exchange Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Securities and Exchange Commission is amending rule 206(3)-3T under the Investment Advisers Act of 1940, a temporary rule that establishes an alternative means for investment advisers who are registered with the Commission as broker-dealers to meet the requirements of section 206(3) of the Investment Advisers Act when they act in a principal capacity in transactions with certain of their advisory clients. The amendment extends the date on which rule 206(3)-3T will sunset from December 31, 2012 to December 31, 2014.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>The amendments in this document are effective December 28, 2012 and the expiration date for 17 CFR 275.206(3)-3T is extended to December 31, 2014.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Melissa S. Gainor, Attorney-Adviser, Vanessa M. Meeks, Attorney-Adviser, Sarah A. Buescher, Branch Chief, or Daniel S. Kahl, Assistant Director, at (202) 551-6787 or<E T="03">IArules@sec.gov,</E>Office of Investment Adviser Regulation, Division of Investment Management, U.S. Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-8549.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>The Securities and Exchange Commission is adopting an amendment to temporary rule 206(3)-3T [17 CFR 275.206(3)-3T] under the Investment Advisers Act of 1940 [15 U.S.C. 80b] that extends the date on which the rule will sunset from December 31, 2012 to December 31, 2014. Note that previous related releases used RIN 3235-AJ96. (<E T="03">See Temporary Rule Regarding Principal Trades with Certain Advisory Clients,</E>Investment Advisers Act Release No. 2653 (Sep. 24, 2007) [72 FR 55022 (Sep. 28, 2007)];<E T="03">Temporary Rule Regarding Principal Trades with Certain Advisory Clients,</E>Investment Advisers Act Release No. 2965 (Dec. 23, 2009) [74 FR 69009 (Dec. 30, 2009)];<E T="03">Temporary Rule Regarding Principal Trades with Certain Advisory Clients,</E>Investment Advisers Act Release No. 2965A (Dec. 31, 2009) [75 FR 742 (Jan. 6, 2010)];<E T="03">Temporary Rule Regarding Principal Trades with Certain Advisory Clients,</E>Investment Advisers Act Release No. 3118 (Dec. 1, 2010) [75 FR 75650 (Dec. 6, 2010)];<E T="03">Temporary Rule Regarding Principal Trades with Certain Advisory Clients,</E>Investment Advisers Act Release No. 3128 (Dec. 28, 2010) [75 FR 82236 (Dec. 30, 2010)];<E T="03">Temporary Rule Regarding Principal Trades with Certain Advisory Clients,</E>Investment Advisers Act Release No. 3483 (October 9, 2012), [77 FR 62185 (October 12, 2012)].)</P>
        <HD SOURCE="HD1">I. Background</HD>
        <P>On September 24, 2007, we adopted, on an interim final basis, rule 206(3)-3T, a temporary rule under the Investment Advisers Act of 1940 (the “Advisers Act”) that provides an alternative means for investment advisers that are registered with us as broker-dealers to meet the requirements of section 206(3) of the Advisers Act when they act in a principal capacity in transactions with certain of their advisory clients.<SU>1</SU>
          <FTREF/>In December 2009, we extended the rule's sunset date by one year to December 31, 2010.<SU>2</SU>
          <FTREF/>In December 2010, we further extended the rule's sunset date by two years to December 31, 2012.<SU>3</SU>

          <FTREF/>We deferred final action on rule 206(3)-3T at that time in<PRTPAGE P="76855"/>order to complete a study required by section 913 of the Dodd-Frank Wall Street Reform and Consumer Protection Act (the “Dodd-Frank Act”)<SU>4</SU>
          <FTREF/>and to consider more broadly the regulatory requirements applicable to broker-dealers and investment advisers, including whether rule 206(3)-3T should be substantively modified, supplanted, or permitted to sunset.<SU>5</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>1</SU>Rule 206(3)-3T [17 CFR 275.206(3)-3T]. All references to rule 206(3)-3T and the various sections thereof in this release are to 17 CFR 275.206(3)-3T and its corresponding sections.<E T="03">See also Temporary Rule Regarding Principal Trades with Certain Advisory Clients,</E>Investment Advisers Act Release No. 2653 (Sep. 24, 2007) [72 FR 55022 (Sep. 28, 2007)] (“2007 Principal Trade Rule Release”).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>2</SU>
            <E T="03">See Temporary Rule Regarding Principal Trades with Certain Advisory Clients,</E>Investment Advisers Act Release No. 2965 (Dec. 23, 2009) [74 FR 69009 (Dec. 30, 2009)] (“2009 Extension Release”);<E T="03">Temporary Rule Regarding Principal Trades with Certain Advisory Clients,</E>Investment Advisers Act Release No. 2965A (Dec. 31, 2009) [75 FR 742 (Jan. 6, 2010)] (making a technical correction to the 2009 Extension Release).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>3</SU>See<E T="03">Temporary Rule Regarding Principal Trades with Certain Advisory Clients,</E>Investment Advisers Act Release No. 3118 (Dec. 1, 2010) [75 FR 75650 (Dec. 6, 2010)] (proposing a two-year extension of rule 206(3)-3T's sunset date) (“2010 Extension Proposing Release”);<E T="03">Temporary Rule Regarding Principal Trades with Certain Advisory Clients,</E>Investment Advisers Act Release No. 3128 (Dec. 28, 2010) [75 FR 82236 (Dec. 30, 2010)] (“2010 Extension Release”).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>4</SU>Public Law 111-203, 124 Stat. 1376 (2010). Under section 913 of the Dodd-Frank Act, we were required to conduct a study and provide a report to Congress concerning the obligations of broker-dealers and investment advisers, including standards of care applicable to those intermediaries and their associated persons. Section 913 also provides that we may commence a rulemaking concerning the legal or regulatory standards of care for broker-dealers, investment advisers, and persons associated with these intermediaries for providing personalized investment advice about securities to retail customers, taking into account the findings, conclusions, and recommendations of the study.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>5</SU>
            <E T="03">See</E>2010 Extension Release, Section II.</P>
        </FTNT>
        <P>The study mandated by section 913 of the Dodd-Frank Act was prepared by the staff and delivered to Congress on January 21, 2011.<SU>6</SU>
          <FTREF/>Since that time, we have considered the findings, conclusions, and recommendations of the 913 Study in order to determine whether to promulgate rules concerning the legal or regulatory standards of care for broker-dealers and investment advisers. In addition, since issuing the 913 Study, Commissioners and the staff have held numerous meetings with interested parties on the study and related matters.<SU>7</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>6</SU>
            <E T="03">See Study on Investment Advisers and Broker-Dealers</E>(“913 Study”) (Jan. 21, 2011), available at<E T="03">http://www.sec.gov/news/studies/2011/913studyfinal.pdf</E>. For a discussion regarding principal trading,<E T="03">see</E>section IV.C.1.(b) of the 913 Study.<E T="03">See also</E>Commissioners Kathleen L. Casey and Troy A. Paredes,<E T="03">Statement by SEC Commissioners: Statement Regarding Study on Investment Advisers and Broker-Dealers</E>(Jan. 21, 2011), available at<E T="03">http://www.sec.gov/news/speech/2011/spch012211klctap.htm</E>.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>7</SU>
            <E T="03">See Comments on Study Regarding Obligations of Brokers, Dealers, and Investment Advisers,</E>File No. 4-606, available at<E T="03">http://sec.gov/comments/4-606/4-606.shtml</E>.</P>
        </FTNT>
        <P>On October 9, 2012, we proposed to extend the date on which rule 206(3)-3T will sunset for a limited amount of time, from December 31, 2012 to December 31, 2014.<SU>8</SU>
          <FTREF/>We received five comment letters addressing our proposal.<SU>9</SU>
          <FTREF/>Four of these commenters generally supported extending rule 206(3)-3T for at least two years,<SU>10</SU>
          <FTREF/>and one opposed a two-year extension.<SU>11</SU>
          <FTREF/>The comments we received on our proposal are discussed below. After considering each of the comments, we are extending the rule's sunset date by two years to December 31, 2014, as proposed.</P>
        <FTNT>
          <P>
            <SU>8</SU>
            <E T="03">See Temporary Rule Regarding Principal Trades with Certain Advisory Clients,</E>Investment Advisers Act Release No. 3483 (October 9, 2012), [77 FR 62185 (October 12, 2012)] (“Proposing Release”).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>9</SU>
            <E T="03">See</E>Comment Letter of Chris Barnard (Oct. 26, 2012) (“Barnard Letter”); Comment Letter of fi360, Inc. (Nov. 13, 2012) (“fi360 Letter”); Comment Letter of the Financial Services Institute (Nov. 5, 2012) (“FSI Letter”); Comment Letter of the Securities Industry and Financial Markets Association (Nov. 13, 2012) (“SIFMA Letter”); Comment Letter of Wells Fargo Advisors (Nov. 13, 2012) (“Wells Fargo Letter”).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>10</SU>
            <E T="03">See</E>Barnard Letter; FSI Letter; SIFMA Letter; Wells Fargo Letter.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>11</SU>
            <E T="03">See</E>fi360 Letter.</P>
        </FTNT>
        <HD SOURCE="HD1">II. Discussion</HD>
        <P>We are amending rule 206(3)-3T only to extend the rule's sunset date by two additional years.<SU>12</SU>
          <FTREF/>We are not adopting any substantive amendments to the rule at this time. Absent further action by the Commission, the rule would sunset on December 31, 2012. We are adopting this extension because, as we discussed in the Proposing Release, we continue to believe that the issues raised by principal trading, including the restrictions in section 206(3) of the Advisers Act and our experiences with, and observations regarding, the operation of rule 206(3)-3T, should be considered as part of our broader consideration of the regulatory requirements applicable to broker-dealers and investment advisers in connection with the Dodd-Frank Act.<SU>13</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>12</SU>The rule includes a reference to an “investment grade debt security,” which is defined as “a non-convertible debt security that, at the time of sale, is rated in one of the four highest rating categories of at least two nationally recognized statistical rating organizations (as defined in section 3(a)(62) of the Exchange Act).” Rule 206(3)-3T(a)(2) and (c). Section 939A of the Dodd-Frank Act requires that we “review any regulation issued by [us] that requires the use of an assessment of the credit-worthiness of a security or money market instrument; and any references to or requirements in such regulations regarding credit ratings.” Once we have completed that review, the statute provides that we modify any regulations identified in our review to “remove any reference to or requirement of reliance on credit ratings and to substitute in such regulations such standard of credit-worthiness” as we determine appropriate. We believe that the credit rating requirement in the temporary rule would be better addressed after the Commission completes its review of the regulatory standards of care that apply to broker-dealers and investment advisers. One commenter addressed credit ratings and agreed with us that the issue would be better addressed after the Commission completes its review.<E T="03">See</E>SIFMA Letter. We are not adopting any substantive amendments to the rule at this time.<E T="03">See generally Report on Review of Reliance on Credit Ratings</E>(July 21, 2011), available at<E T="03">http://www.sec.gov/news/studies/2011/939astudy.pdf</E>(staff study reviewing the use of credit ratings in Commission regulations).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>13</SU>
            <E T="03">See</E>Proposing Release, Section II. The 913 Study is one of several studies relevant to the regulation of broker-dealers and investment advisers mandated by the Dodd-Frank Act.<E T="03">See, e.g., Study on Enhancing Investment Adviser Examinations</E>(Jan. 19, 2011), available at<E T="03">http://sec.gov/news/studies/2011/914studyfinal.pdf</E>(staff study required by section 914 of the Dodd-Frank Act, which directed the Commission to review and analyze the need for enhanced examination and enforcement resources for investment advisers); Commissioner Elisse B. Walter,<E T="03">Statement on Study Enhancing Investment Adviser Examinations</E>(<E T="03">Required by Section 914 of Title IV of the Dodd-Frank Wall Street Reform and Consumer Protection Act</E>) (Jan. 19, 2011), available at<E T="03">http://sec.gov/news/speech/2011/spch011911ebw.pdf. See also Study and Recommendations on Improved Investor Access to Registration Information About Investment Advisers and Broker-Dealers</E>(Jan. 26, 2011), available at<E T="03">http://sec.gov/news/studies/2011/919bstudy.pdf</E>(staff study required by section 919B of the Dodd-Frank Act that directed the Commission to complete a study, including recommendations (some of which have been implemented) of ways to improve investor access to registration information about investment advisers and broker-dealers, and their associated persons);<E T="03">United States Government Accountability Office Report to Congressional Committees on Private Fund Advisers</E>(July 11, 2011), available at<E T="03">http://www.gao.gov/new.items/d11623.pdf</E>(study required by section 416 of the Dodd-Frank Act, which directed the Comptroller General of the United States to study the feasibility of forming a self-regulatory organization to oversee private funds).</P>
        </FTNT>
        <P>Section 913 of the Dodd-Frank Act provides that we may commence a rulemaking concerning, among other things, the legal or regulatory standards of care for broker-dealers, investment advisers, and persons associated with these intermediaries when providing personalized investment advice about securities to retail customers. Since the completion of the 913 Study in 2011, we have been considering the findings, conclusions, and recommendations of the study and the comments we have received from interested parties.<SU>14</SU>
          <FTREF/>In addition, our staff has been working to obtain data and economic analysis related to standards of conduct and enhanced regulatory harmonization of broker-dealers and investment advisers to inform the Commission as it considers any future rulemaking. At this time, our consideration of the regulatory requirements applicable to broker-dealers and investment advisers and the recommendations from the 913 Study is ongoing. We will not complete our consideration of these issues before December 31, 2012, the current sunset date for rule 206(3)-3T.</P>
        <FTNT>
          <P>

            <SU>14</SU>Section 913(f) of the Dodd-Frank Act requires us to consider the 913 Study in any rulemaking authorized by that section of the Dodd-Frank Act.<E T="03">See also Comments on Study Regarding Obligations of Brokers, Dealers, and Investment Advisers,</E>File No. 4-606, available at<E T="03">http://sec.gov/comments/4-606/4-606.shtml</E>.</P>
        </FTNT>

        <P>If we permit rule 206(3)-3T to sunset on December 31, 2012, after that date investment advisers registered with us as broker-dealers that currently rely on rule 206(3)-3T would be required to comply with section 206(3)'s transaction-by-transaction written disclosure and consent requirements without the benefit of the alternative means of complying with these requirements currently provided by rule 206(3)-3T. This could limit the access of non-discretionary advisory clients of<PRTPAGE P="76856"/>advisory firms that are registered with us as broker-dealers to certain securities.<SU>15</SU>
          <FTREF/>In addition, firms would be required to make substantial changes to their disclosure documents, client agreements, procedures, and systems.</P>
        <FTNT>
          <P>

            <SU>15</SU>For a discussion of the costs and benefits underlying rule 206(3)-3T,<E T="03">see</E>2007 Principal Trade Rule Release, Section VI.C.</P>
        </FTNT>
        <P>As noted above, four commenters generally supported our proposal to amend rule 206(3)-3T to extend it,<SU>16</SU>
          <FTREF/>and one commenter opposed the two-year extension.<SU>17</SU>
          <FTREF/>Commenters who supported the extension cited the disruption to investors that would occur if the rule expired at this time, asserting that investors would lose access to the securities currently offered through principal trades, receive less favorable pricing on such securities, or be forced to buy such securities through brokerage accounts.<SU>18</SU>
          <FTREF/>These commenters further explained that, if the rule were allowed to expire, firms relying on the rule would be required to make considerable changes to their operations, client relationships, systems, policies and procedures at substantial expense, without substantial benefits to investors.<SU>19</SU>
          <FTREF/>One commenter described a recent survey it conducted that indicated reliance on rule 206(3)-3T by dual registrants in order to engage in principal trades.<SU>20</SU>
          <FTREF/>In addition, two commenters specifically addressed Commission consideration of requests for exemptive orders as an alternative means of compliance with section 206(3). Both commenters strongly supported the two-year extension instead of Commission consideration of requests for exemptive orders.<SU>21</SU>
          <FTREF/>One commenter expressed concern about the potential inefficiency and uncertainty created by the need to submit individual requests for exemptive relief.<SU>22</SU>
          <FTREF/>Commenters supporting the extension agreed that extending the rule while the Commission conducted its review of the obligations of broker-dealers and investment advisers, as mandated by the Dodd-Frank Act, would be the least disruptive option.<SU>23</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>16</SU>
            <E T="03">See</E>Barnard Letter; FSI Letter; SIFMA Letter; Wells Fargo Letter.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>17</SU>
            <E T="03">See</E>fi360 Letter.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>18</SU>
            <E T="03">See</E>FSI Letter; SIFMA Letter (noting that of seven advisory firms that responded to a recent SIFMA survey, two firms indicated that they would not be able to elicit customer consent in accordance with section 206(3) of the Advisers Act, and the other five firms indicated that although they would be able to elicit customer consent in accordance with section 206(3), they would nonetheless significantly limit their volume of principal trading); Wells Fargo Letter.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>19</SU>
            <E T="03">See</E>FSI Letter; SIFMA Letter; Wells Fargo Letter.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>20</SU>
            <E T="03">See</E>SIFMA Letter (SIFMA noted responses from seven dual-registrant firms that, in the aggregate, manage over $325 billion of assets in over 1.1 million non-discretionary advisory accounts. The firms indicated that 459,507 of these accounts with aggregate assets of over $125 billion are eligible to engage in principal trading in reliance on rule 206(3)-3T. These firms also indicated that, during the previous two years, they engaged in principal trades in reliance on rule 206(3)-3T with 106,682 accounts and executed an average of 12,009 principal trades per month in reliance on the rule.)</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>21</SU>
            <E T="03">See</E>SIFMA Letter; Wells Fargo Letter.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>22</SU>
            <E T="03">See</E>SIFMA Letter.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>23</SU>
            <E T="03">See</E>Barnard Letter; SIFMA Letter; Wells Fargo Letter.</P>
        </FTNT>
        <P>One commenter opposed extending the rule for more than a limited period of time (no more than six months) and questioned maintaining investor choice as a rationale for extending rule 206(3)-3T.<SU>24</SU>
          <FTREF/>This commenter also noted that although instances of “dumping” have not been discovered, the staff has observed related compliance problems in the past. The commenter asserted that a more detailed analysis of principal trades executed in reliance on rule 206(3)-3T, including spreads paid by investors and investment returns, be conducted and suggested that the Commission extend rule 206(3)-3T for no more than six months to conduct such an assessment.<SU>25</SU>
          <FTREF/>The commenter also expressed concern about the open-ended nature of extending this temporary rule.<SU>26</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>24</SU>
            <E T="03">See</E>fi360 Letter. This commenter also raised concerns regarding the effectiveness of disclosure generally, including the disclosures required by the temporary rule. Such concerns are beyond the scope of this rulemaking.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>25</SU>
            <E T="03">See</E>fi360 Letter.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>26</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <P>On balance, and after careful consideration of these comments, we conclude that extending the rule for two years is the most appropriate course of action at this time. First, with respect to investors, we agree with commenters that permitting the rule to sunset before we complete our consideration of the regulatory requirements applicable to broker-dealers and investment advisers could produce substantial disruption for investors with advisory accounts serviced by firms relying on the rule.<SU>27</SU>
          <FTREF/>These investors might lose access to securities available through principal transactions and be forced to convert their accounts in the interim, only to face the possibility of future change—and the costs and uncertainty such additional change may entail.<SU>28</SU>
          <FTREF/>We believe that the rule benefits investors because it provides them with greater access to a wider range of securities and includes provisions designed to protect them.</P>
        <FTNT>
          <P>
            <SU>27</SU>
            <E T="03">See</E>Barnard Letter; SIFMA Letter; Wells Fargo Letter.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>28</SU>As discussed in each of the 2007 Principal Trade Rule Release, 2009 Extension Release and 2010 Extension Release, firms have explained that they may refrain from engaging in principal trading with their advisory clients in the absence of the rule given the practical difficulties of complying with section 206(3), and thus may not offer principal trades through advisory accounts.<E T="03">See</E>2007 Principal Trade Rule Release, Section I.B; 2009 Extension Release, Section I; 2010 Extension Release, Section II.<E T="03">See also</E>SIFMA Letter.</P>
        </FTNT>
        <P>Second, with respect to firms, the letters submitted by three commenters demonstrate that firms in fact do rely on the rule, and that those firms will be faced with uncertainty and disruption of operations should the rule expire just as the Commission is engaging in a comprehensive review process that may ultimately produce different regulatory requirements.<SU>29</SU>
          <FTREF/>One commenter that represents securities firms provided data showing that a substantial number of accounts and volume of trades would be affected by a change in the rule.<SU>30</SU>
          <FTREF/>This disruption will be avoided if the rule remains available while we engage in our broader consideration of the regulatory requirements applicable to broker-dealers and investment advisers.</P>
        <FTNT>
          <P>
            <SU>29</SU>
            <E T="03">See</E>FSI Letter; SIFMA Letter; Wells Fargo Letter.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>30</SU>
            <E T="03">See</E>SIFMA Letter.</P>
        </FTNT>
        <P>We believe that the requirements of rule 206(3)-3T, coupled with regulatory oversight, will adequately protect advisory clients for an additional limited period of time while we consider more broadly the regulatory requirements applicable to broker-dealers and investment advisers.<SU>31</SU>
          <FTREF/>In the 2010 Extension Proposing Release, we discussed certain compliance issues identified by the Office of Compliance, Inspections and Examinations.<SU>32</SU>
          <FTREF/>One matter identified in the staff's review resulted in a settlement of an enforcement proceeding and other matters continue to be reviewed by the staff.<SU>33</SU>
          <FTREF/>We are sensitive to the concerns regarding compliance issues with respect to rule 206(3)-3T raised by one commenter.<SU>34</SU>

          <FTREF/>Since 2010 and throughout the period of the extension,<PRTPAGE P="76857"/>the staff has and will continue to examine firms that engage in principal transactions and will take appropriate action to help ensure that firms are complying with section 206(3) or rule 206(3)-3T (as applicable), including possible enforcement action.</P>
        <FTNT>
          <P>
            <SU>31</SU>In addition, rule 206(3)-3T(b) provides that the rule does not relieve an investment adviser from acting in the best interests of its clients, or from any obligation that may be imposed by sections 206(1) or (2) of the Advisers Act or any other applicable provisions of the federal securities laws.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>32</SU>
            <E T="03">See</E>2010 Extension Proposing Release, Section II (discussing certain compliance issues identified by the Office of Compliance Inspections and Examinations with respect to the requirements of section 206(3) or rule 206(3)-3T and noting that the staff did not identify any instances of “dumping” as part of its review).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>33</SU>
            <E T="03">See In the Matter of Feltl &amp; Company, Inc.,</E>Investment Advisers Act Release No. 3325 (Nov. 28, 2011) (settled order finding, among other things, violations of section 206(3) of the Advisers Act for certain principal transactions and section 206(4) of the Advisers Act and rule 206(4)-7 thereunder for failure to adopt written policies and procedures reasonably designed to prevent violations of the Advisers Act and its rules).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>34</SU>
            <E T="03">See</E>fi360 Letter.</P>
        </FTNT>
        <P>We received four comment letters specifically addressing the duration of our proposed extension of rule 206(3)-3T.<SU>35</SU>
          <FTREF/>Three of these commenters expressed support for extending the rule for an additional two years, although two of these commenters suggested that an extension of five years would be more appropriate.<SU>36</SU>
          <FTREF/>One commenter opposed extending the rule for more than a six-month period, during which the rule's effectiveness could be further assessed.<SU>37</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>35</SU>
            <E T="03">See</E>fi360 Letter; FSI Letter; SIFMA Letter; Wells Fargo Letter.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>36</SU>
            <E T="03">See</E>FSI Letter; SIFMA Letter; Wells Fargo Letter. Two of these commenters also recommended that the rule should ultimately be made permanent.<E T="03">See</E>FSI Letter; SIFMA Letter.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>37</SU>
            <E T="03">See</E>fi360 Letter.</P>
        </FTNT>
        <P>As we noted in the Proposing Release, we believe that the rule's sunset date should be extended only for a limited amount of time.<SU>38</SU>
          <FTREF/>That period of time, however, must be long enough to permit us to engage in any rulemaking prompted by our broader review of regulatory requirements applicable to investment advisers and broker-dealers. We do not believe that six months is long enough to engage in this process, and we do not believe that it is appropriate at this time to extend the temporary rule for an additional five years. We are sensitive to comments regarding the duration of the extension and the uncertainty caused by extending a temporary rule, but we believe that a two-year extension is necessary to provide investors uninterrupted access to securities available through principal trades and to provide us adequate time to engage in any rulemaking or other process.</P>
        <FTNT>
          <P>
            <SU>38</SU>
            <E T="03">See</E>Proposing Release, Section II.</P>
        </FTNT>
        <P>Three commenters addressed the question of whether we should consider changing the requirements for adviser disclosures to have registered advisers provide more information to us and their clients about whether they are relying on rule 206(3)-3T.<SU>39</SU>
          <FTREF/>Each of these commenters asserted that additional requirements for adviser disclosures are unnecessary, noting that certain additional disclosures may be redundant, and that current disclosures appear to be adequate.<SU>40</SU>
          <FTREF/>We are not adopting amendments requiring additional adviser disclosures at this time, but will consider the need for such disclosures in future rulemakings or other processes as necessary.<SU>41</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>39</SU>
            <E T="03">See</E>FSI Letter; SIFMA Letter; Wells Fargo Letter.<E T="03">See also</E>Proposing Release, Section III (requesting comment on whether we should consider changing the requirements in Form ADV for adviser disclosures to have registered advisers provide more information to us and their clients about whether they are relying on the rule).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>40</SU>
            <E T="03">See</E>FSI Letter; SIFMA Letter; Wells Fargo Letter.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>41</SU>
            <E T="03">See supra</E>note 25.</P>
        </FTNT>
        <P>As noted above, one commenter suggested that there be a more detailed analysis of data, including spreads paid and investor returns.<SU>42</SU>
          <FTREF/>These factors are relevant to principal trades in general, and are not specific to rule 206(3)-3T. This commenter also raised the concern that the Commission may ultimately apply a “uniform” fiduciary standard to broker-dealers and investment advisers in two different ways.<SU>43</SU>
          <FTREF/>These comments pertain to our broader consideration of the regulatory requirements applicable to broker-dealers and investment advisers, and we will consider these comments in conducting this broader review.</P>
        <FTNT>
          <P>
            <SU>42</SU>
            <E T="03">See</E>fi360 Letter.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>43</SU>
            <E T="03">See</E>fi360 Letter. We note that the standard of care to which advisers are subject and the duties they owe clients are in no way diminished by their reliance on rule 206(3)-3T.<E T="03">See supra</E>note 30.</P>
        </FTNT>
        <HD SOURCE="HD1">III. Certain Administrative Law Matters</HD>

        <P>The amendment to rule 206(3)-3T is effective on December 28, 2012. The Administrative Procedure Act generally requires that an agency publish a final rule in the<E T="04">Federal Register</E>not less than 30 days before its effective date.<SU>44</SU>
          <FTREF/>However, this requirement does not apply if the rule is a substantive rule which grants or recognizes an exemption or relieves a restriction, or if the rule is interpretive.<SU>45</SU>
          <FTREF/>Rule 206(3)-3T is a rule that recognizes an exemption and relieves a restriction and in part has interpretive aspects.</P>
        <FTNT>
          <P>
            <SU>44</SU>5 U.S.C. 553(d).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>45</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD1">IV. Paperwork Reduction Act</HD>
        <P>Rule 206(3)-3T contains “collection of information” requirements within the meaning of the Paperwork Reduction Act of 1995.<SU>46</SU>
          <FTREF/>The Office of Management and Budget (“OMB”) last approved the collection of information with an expiration date of May 31, 2014. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB control number. The title for the collection of information is: “Temporary rule for principal trades with certain advisory clients, rule 206(3)-3T” and the OMB control number for the collection of information is 3235-0630. The Proposing Release solicited comments on our PRA estimates, but we did not receive comment on them.<SU>47</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>46</SU>44 U.S.C. 3501 et seq.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>47</SU>
            <E T="03">See</E>Proposing Release, Section IV.</P>
        </FTNT>
        <P>The amendment to the rule we are adopting today—to extend rule 206(3)-3T's sunset date for two years—does not affect the current annual aggregate estimated hour burden of 378,992 hours.<SU>48</SU>
          <FTREF/>Therefore, we are not revising the Paperwork Reduction Act burden and cost estimates submitted to OMB as a result of this amendment.</P>
        <FTNT>
          <P>
            <SU>48</SU>
            <E T="03">See Proposed Collection; Comment Request,</E>75 FR 82416 (Dec. 30, 2010);<E T="03">Submission for OMB Review; Comment Request,</E>76 FR 13002 (Mar. 9, 2011).</P>
        </FTNT>
        <HD SOURCE="HD1">V. Economic Analysis</HD>
        <HD SOURCE="HD2">A. Introduction</HD>
        <P>We are sensitive to the costs and benefits of our rules. The discussion below addresses the costs and benefits of extending rule 206(3)-3T's sunset date for two years, as well as the effect of the extension on the promotion of efficiency, competition, and capital formation as required by section 202(c) of the Advisers Act.<SU>49</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>49</SU>15 U.S.C. 80b-2(c). Section 202(c) of the Advisers Act mandates that the Commission, when engaging in rulemaking that requires it to consider or determine whether an action is necessary or appropriate in the public interest, consider, in addition to the protection of investors, whether the action will promote efficiency, competition, and capital formation.</P>
        </FTNT>
        <P>Rule 206(3)-3T provides an alternative means for investment advisers that are registered with the Commission as broker-dealers to meet the requirements of section 206(3) of the Advisers Act when they act in a principal capacity in transactions with their non-discretionary advisory clients. Other than extending the rule's sunset date for two additional years, we are not modifying the rule from its current form. We previously considered and discussed the economic analysis of rule 206(3)-3T in its current form in the 2007 Principal Trade Rule Release, the 2009 Extension Release, and the 2010 Extension Release.<SU>50</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>50</SU>
            <E T="03">See</E>2007 Principal Trade Rule Release, Sections VI-VII; 2009 Extension Release, Sections V-VI; 2010 Extension Release, Sections V-VI.</P>
        </FTNT>

        <P>The baseline for the following analysis of the benefits and costs of the amendment is the situation in existence today, in which investment advisers that are registered with us as broker-dealers can choose to use rule 206(3)-3T as an alternative means to comply with section 206(3) of the Advisers Act when engaging in principal transactions with their non-discretionary advisory clients. The amendment, which will extend rule 206(3)-3T's sunset date by<PRTPAGE P="76858"/>two additional years, will affect investment advisers that are registered with us as broker-dealers and engage in, or may consider engaging in, principal transactions with non-discretionary advisory clients, as well as the non-discretionary advisory clients of these firms that engage in, or may consider engaging in, principal transactions. The extent to which firms currently rely on the rule is unknown.<SU>51</SU>
          <FTREF/>Past comment letters have indicated that since its implementation in 2007, both large and small advisers have relied upon the rule.<SU>52</SU>
          <FTREF/>A recent letter submitted by one commenter describes survey results of several of its members that rely on the rule.<SU>53</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>51</SU>As of November 1, 2012, we estimate that there are 491registered investment advisers that also are registered broker-dealers. Based on IARD data as of November 1, 2012, we estimate that there are approximately 100 registered advisers that also are registered as broker-dealers that have non-discretionary advisory accounts and that engage in principal transactions.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>52</SU>
            <E T="03">See</E>Comment Letter of Securities Industry and Financial Markets Association (Dec. 20, 2010); Comment Letter of Winslow, Evans &amp; Crocker (Dec. 8, 2009) (“Winslow, Evans &amp; Crocker Letter”); Comment Letter of Bank of America Corporation (Dec. 20, 2010) (“Bank of America Letter”).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>53</SU>
            <E T="03">See supra</E>notes 18, 20.</P>
        </FTNT>
        <HD SOURCE="HD2">B. Benefits and Costs of Rule 206(3)-3T</HD>
        <P>As stated in previous releases, we believe the principal benefit of rule 206(3)-3T is that it maintains investor choice among different types of accounts and protects the interests of investors. Rule 206(3)-3T also provides a lower cost and more efficient alternative for an adviser that is registered with us as a broker-dealer to comply with the requirements of section 206(3) of the Advisers Act. This, in turn, may provide non-discretionary advisory clients greater access to a wider range of securities. Non-discretionary advisory clients also benefit from the protections of the sales practice rules of the Securities Exchange Act of 1934 (the “Exchange Act”) and the relevant self-regulatory organization(s) and the fiduciary duties and other obligations imposed by the Advisers Act. Greater access to a wider range of securities may also allow non-discretionary advisory clients to better allocate capital. In the long term, the more efficient allocation of capital may lead to an increase in capital formation.</P>
        <P>We received one comment on our economic analysis.<SU>54</SU>
          <FTREF/>The commenter questioned the importance of investor choice as the principal benefit of rule 206(3)-3T.<SU>55</SU>
          <FTREF/>We continue to believe that providing non-discretionary advisory clients with greater access to a wider range of securities is beneficial. As we have previously stated, many clients wish to access the securities inventory of a diversified broker-dealer through their non-discretionary advisory accounts.<SU>56</SU>
          <FTREF/>We believe that it is appropriate to preserve investors' access to the securities available through principal transactions made in reliance on rule 206(3)-3T while consideration of the regulatory requirements applicable to broker-dealers and investment advisers is ongoing.</P>
        <FTNT>
          <P>
            <SU>54</SU>
            <E T="03">See</E>fi360 Letter.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>55</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>56</SU>
            <E T="03">See</E>2007 Principal Trade Rule Release, Section I.B.</P>
        </FTNT>
        <P>Also, in connection with the 2010 extension of the rule, one commenter had disagreed with a number of the benefits of rule 206(3)-3T described above, but did not provide any specific data, analysis, or other information in support of its comment.<SU>57</SU>
          <FTREF/>That commenter argued that rule 206(3)-3T would impede, rather than promote, capital formation because it would lead to “more numerous and more severe violations * * * of the trust placed by individual investors in their trusted investment adviser.”<SU>58</SU>
          <FTREF/>While we understand the view that numerous and severe violations of trust could impede capital formation, we have not seen any evidence that rule 206(3)-3T has caused this result. The staff has not identified instances where an adviser has used the temporary rule to “dump” unmarketable securities or securities that the adviser believes may decline in value into an advisory account, a harm that section 206(3) and the conditions and limitations of rule 206(3)-3T are designed to redress.<SU>59</SU>
          <FTREF/>No commenter provided any substantive or specific evidence to contradict our previous conclusion that the rule benefits investors, and we continue to believe that the rule provides those benefits.<SU>60</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>57</SU>
            <E T="03">See</E>Comment Letter of the National Association of Personal Financial Advisors (Dec. 20, 2010) (“NAPFA Letter”) (questioning the benefits of the rule in: (1) Providing protections of the sales practice rules of the Exchange Act and the relevant self-regulatory organizations; (2) allowing non-discretionary advisory clients of advisory firms that are also registered as broker-dealers to have easier access to a wider range of securities which, in turn, should continue to lead to increased liquidity in the markets for these securities; (3) maintaining investor choice; and (4) promoting capital formation).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>58</SU>
            <E T="03">See id.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>59</SU>
            <E T="03">See supra</E>note 32.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>60</SU>
            <E T="03">See</E>2007 Principal Trade Rule Release, Section VI.C; 2009 Extension Release, Section V; 2010 Extension Release, Section V.</P>
        </FTNT>
        <P>We also received comments on the 2007 Principal Trade Rule Release from commenters who opposed the limitation of the temporary rule to investment advisers that are registered with us as broker-dealers, as well as to accounts that are subject to both the Advisers Act and Exchange Act as providing a competitive advantage to investment advisers that are registered with us as broker-dealers.<SU>61</SU>
          <FTREF/>Based on our experience with the rule to date, and as we noted in previous releases, we have no reason to believe that broker-dealers (or affiliated but separate investment advisers and broker-dealers) are put at a competitive disadvantage to advisers that are themselves also registered as broker-dealers.<SU>62</SU>
          <FTREF/>Commenters on the Proposing Release did not address this specific issue, but we intend to continue to evaluate the effects of the rule on efficiency, competition, and capital formation in connection with our broader consideration of the regulatory requirements applicable to broker-dealers and investment advisers.</P>
        <FTNT>
          <P>
            <SU>61</SU>
            <E T="03">See</E>Comment Letter of the Financial Planning Association (Nov. 30, 2007); Comment Letter of the American Bar Association, section of Business Law's Committee on Federal Regulation of Securities (Apr. 18, 2008).<E T="03">See also</E>2009 Extension Release, Section VI.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>62</SU>
            <E T="03">See</E>2009 Extension Release, Section VI; 2010 Extension Release, Section VI.</P>
        </FTNT>
        <P>As we discussed in previous releases, there are also several costs associated with rule 206(3)-3T, including the operational costs associated with complying with the rule.<SU>63</SU>
          <FTREF/>In the 2007 Principal Trade Rule Release, we presented estimates of the costs of each of the rule's disclosure elements, including: prospective disclosure and consent; transaction-by-transaction disclosure and consent; transaction-by-transaction confirmations; and the annual report of principal transactions. We also provided estimates for the following related costs of compliance with rule 206(3)-3T: (i) The initial distribution of prospective disclosure and collection of consents; (ii) systems programming costs to ensure that trade confirmations contain all of the information required by the rule; and (iii) systems programming costs to aggregate already-collected information to generate compliant principal transactions reports. Although one commenter noted that the Commission's cost analysis had remained unchanged, we do not believe the extension we are adopting today materially affects the cost estimates associated with the rule.<SU>64</SU>

          <FTREF/>The commenter did not provide supporting data discrediting the cost<PRTPAGE P="76859"/>analysis we presented in the 2007 Principal Trade Rule Release.<SU>65</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>63</SU>
            <E T="03">See supra</E>note 50.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>64</SU>
            <E T="03">See</E>2007 Principal Trade Rule Release, Section VI.D. In the 2007 Principal Trade Rule Release, we estimated the total overall costs, including estimated costs for all eligible advisers and eligible accounts, relating to compliance with rule 206(3)-3T to be $37,205,569.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>65</SU>
            <E T="03">See</E>fi360 Letter.</P>
        </FTNT>
        <HD SOURCE="HD2">C. Benefits and Costs of the Extension</HD>
        <P>In addition to the benefits of rule 206(3)-3T described above and in previous releases, we believe there are benefits to extending the rule's sunset date for an additional two years. The temporary extension of rule 206(3)-3T will have the benefit of providing the Commission with additional time to consider principal trading as part of the broader consideration of the regulatory requirements applicable to broker-dealers and investment advisers without causing disruption to the firms and clients relying on the rule.</P>
        <P>One alternative to the extension of the rule's sunset date would be to let the temporary rule sunset on its current sunset date, and so preclude investment advisers from engaging in principal transactions with their advisory clients unless in compliance with the requirements of section 206(3) of the Advisers Act. As explained in the 2010 Extension Release, if we did not extend rule 206(3)-3T's sunset date, firms currently relying on the rule would be required to restructure their operations and client relationships on or before the rule's current expiration date—potentially only to have to do so again later (first when the rule sunsets or is modified, and again if we adopt a new approach in connection with our broader consideration of the regulatory requirements applicable to broker-dealers and investment advisers).<SU>66</SU>
          <FTREF/>As a result of the two-year extension of the rule's sunset date, firms relying on the rule will continue to be able to offer clients and prospective clients the same level of access to certain securities on a principal basis and will not need to incur the cost of adjusting to a new set of rules or abandoning the systems established to comply with the current rule during this two-year period. The extension of the rule will also permit non-discretionary advisory clients who have had greater access to certain securities because of their advisers' reliance on the rule to trade on a principal basis to continue to have the same level of access to those securities without disruption.</P>
        <FTNT>
          <P>
            <SU>66</SU>
            <E T="03">See</E>2010 Extension Release, Section V.</P>
        </FTNT>
        <P>Although we did not receive any comments on the rule's compliance costs, we recognize that, as a result of our amendment, firms relying on the rule will incur the costs associated with complying with the rule for two additional years. We also recognize that a temporary rule, by nature, creates long-term uncertainty, which in turn, may result in a reduced ability of firms to coordinate and plan future business activities.<SU>67</SU>
          <FTREF/>However, we believe that it would be premature to allow the rule to sunset or to adopt the rule on a permanent basis while consideration of the regulatory requirements applicable to broker-dealers and investment advisers is ongoing. We also considered extending the rule's sunset date for a period other than two years. Two commenters suggested an extension of five years, noting that this period of time would provide greater certainty for firms and more ample time for the Commission to consider its broader regulation of broker-dealers and investment advisers.<SU>68</SU>
          <FTREF/>Another commenter stated that the rule should be extended for no more than six months.<SU>69</SU>
          <FTREF/>We do not believe that six months is long enough to engage in a review of the regulatory obligations of broker-dealers and investment advisers, and we do not believe that it is appropriate at this time to extend the temporary rule for an additional five years. Should our consideration of the fiduciary obligations and other regulatory requirements applicable to broker-dealers and investment advisers extend beyond the sunset date of the temporary rule, a longer period may be appropriate. On balance, however, we continue to believe that the two-year extension of rule 206(3)-3T appropriately addresses the needs of firms and clients relying on the rule while preserving the Commission's ability to address principal trading as part of its broader consideration of the standards applicable to investment advisers and broker-dealers. We will continue to assess the rule's operation and impact along with intervening developments during the period of the extension.</P>
        <FTNT>
          <P>

            <SU>67</SU>One of the two commenters who argued that the rule should eventually be made permanent specifically noted the uncertainty caused by the need for additional extensions in the future.<E T="03">See</E>SIFMA Letter. We also received several comments in connection with prior extensions of the rule urging us to make the rule permanent to avoid such uncertainty.<E T="03">See e.g.,</E>Winslow, Evans &amp; Crocker Letter; Bank of America Letter.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>68</SU>
            <E T="03">See</E>SIFMA Letter; Wells Fargo Letter.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>69</SU>
            <E T="03">See</E>fi360 Letter.</P>
        </FTNT>
        <HD SOURCE="HD1">VI. Final Regulatory Flexibility Act Analysis</HD>
        <P>The Commission has prepared the following Final Regulatory Flexibility Analysis (“FRFA”) regarding the amendment to rule 206(3)-3T in accordance with 5 U.S.C. 604. We prepared and included an Initial Regulatory Flexibility Analysis (“IRFA”) in the Proposing Release.<SU>70</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>70</SU>
            <E T="03">See</E>Proposing Release, Section VII.</P>
        </FTNT>
        <HD SOURCE="HD2">A. Need for the Rule Amendment</HD>
        <P>We are adopting an amendment to extend rule 206(3)-3T's sunset date for two years because we believe that it would be premature to require firms relying on the rule to restructure their operations and client relationships before we complete our broader consideration of the regulatory requirements applicable to broker-dealers and investment advisers. The objective of the amendment to rule 206(3)-3T, as discussed above, is to permit firms currently relying on rule 206(3)-3T to limit the need to modify their operations and relationships on multiple occasions before we complete our broader consideration of the regulatory requirements applicable to broker-dealers and investment advisers. Absent further action by the Commission, the rule will sunset on December 31, 2012.</P>
        <P>We are amending rule 206(3)-3T pursuant to sections 206A and 211(a) of the Advisers Act [15 U.S.C. 80b-6a and 15 U.S.C. 80b-11(a)].</P>
        <HD SOURCE="HD2">B. Significant Issues Raised by Public Comments</HD>
        <P>We did not receive any comment letters related to our IRFA.</P>
        <HD SOURCE="HD2">C. Small Entities Subject to the Rule</HD>
        <P>Rule 206(3)-3T is an alternative method of complying with Advisers Act section 206(3) and is available to all investment advisers that: (i) Are registered as broker-dealers under the Exchange Act; and (ii) effect trades with clients directly or indirectly through a broker-dealer controlling, controlled by or under common control with the investment adviser, including small entities. Under Advisers Act rule 0-7, for purposes of the Regulatory Flexibility Act an investment adviser generally is a small entity if it: (i) Has assets under management of less than $25 million; (ii) did not have total assets of $5 million or more on the last day of its most recent fiscal year; and (iii) does not control, is not controlled by, and is not under common control with another investment adviser that has assets under management of $25 million or more, or any person (other than a natural person) that had total assets of $5 million or more on the last day of its most recent fiscal year.<SU>71</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>71</SU>
            <E T="03">See</E>17 CFR 275.0-7.</P>
        </FTNT>

        <P>As noted in the Proposing Release, we estimated that as of August 1, 2012, 547 SEC-registered investment advisers were<PRTPAGE P="76860"/>small entities.<SU>72</SU>
          <FTREF/>As discussed in the 2007 Principal Trade Rule Release, we opted not to make the relief provided by rule 206(3)-3T available to all investment advisers, and instead have restricted it to investment advisers that also are registered as broker-dealers under the Exchange Act.<SU>73</SU>
          <FTREF/>We therefore estimated for purposes of the IRFA that 7 of these small entities (those that are both investment advisers and registered broker-dealers) could rely on rule 206(3)-3T.<SU>74</SU>
          <FTREF/>We did not receive any comments on these estimates.</P>
        <FTNT>
          <P>
            <SU>72</SU>IARD data as of August 1, 2012. As of November 1, 2012, based on IARD data, we estimate that 502 SEC-registered investment advisers were small entities.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>73</SU>
            <E T="03">See</E>2007 Principal Trade Rule Release, Section VIII.B.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>74</SU>IARD data as of August 1, 2012. As of November 1, 2012, based on IARD data, we estimate that 6 of these small entities could rely on rule 206(3)-3T.</P>
        </FTNT>
        <HD SOURCE="HD2">D. Projected Reporting, Recordkeeping, and other Compliance Requirements</HD>
        <P>The provisions of rule 206(3)-3T impose certain reporting or recordkeeping requirements and our amendment will extend the imposition of these requirements for an additional two years. The two-year extension will not alter these requirements.</P>
        <P>Rule 206(3)-3T is designed to provide an alternative means of compliance with the requirements of section 206(3) of the Advisers Act. Investment advisers taking advantage of the rule with respect to non-discretionary advisory accounts are required to make certain disclosures to clients on a prospective, transaction-by-transaction and annual basis.</P>
        <P>Specifically, rule 206(3)-3T permits an adviser, with respect to a non-discretionary advisory account, to comply with section 206(3) of the Advisers Act by, among other things: (i) Making certain written disclosures; (ii) obtaining written, revocable consent from the client prospectively authorizing the adviser to enter into principal trades; (iii) making oral or written disclosure and obtaining the client's consent orally or in writing prior to the execution of each principal transaction; (iv) sending to the client a confirmation statement for each principal trade that discloses the capacity in which the adviser has acted and indicating that the client consented to the transaction; and (v) delivering to the client an annual report itemizing the principal transactions. Advisers are already required to communicate the content of many of the disclosures pursuant to their fiduciary obligations to clients. Other disclosures are already required by rules applicable to broker-dealers.</P>
        <P>Our amendment will only extend the rule's sunset date for two years in its current form. Advisers currently relying on the rule already should be making the disclosures described above.</P>
        <HD SOURCE="HD2">E. Agency Action To Minimize Effect on Small Entities</HD>
        <P>The Regulatory Flexibility Act directs us to consider significant alternatives that would accomplish our stated objective, while minimizing any significant adverse impact on small entities.<SU>75</SU>
          <FTREF/>Alternatives in this category would include: (i) Establishing different compliance or reporting standards or timetables that take into account the resources available to small entities; (ii) clarifying, consolidating, or simplifying compliance requirements under the rule for small entities; (iii) using performance rather than design standards; and (iv) exempting small entities from coverage of the rule, or any part of the rule.</P>
        <FTNT>
          <P>
            <SU>75</SU>
            <E T="03">See</E>5 U.S.C. 603(c).</P>
        </FTNT>
        <P>We believe that special compliance or reporting requirements or timetables for small entities, or an exemption from coverage for small entities, may create the risk that the investors who are advised by and effect securities transactions through such small entities would not receive adequate disclosure. Moreover, different disclosure requirements could create investor confusion if it creates the impression that small investment advisers have different conflicts of interest with their advisory clients in connection with principal trading than larger investment advisers. We believe, therefore, that it is important for the disclosure protections required by the rule to be provided to advisory clients by all advisers, not just those that are not considered small entities. Further consolidation or simplification of the proposals for investment advisers that are small entities would be inconsistent with our goal of fostering investor protection.</P>
        <P>We have endeavored through rule 206(3)-3T to minimize the regulatory burden on all investment advisers eligible to rely on the rule, including small entities, while meeting our regulatory objectives. It was our goal to ensure that eligible small entities may benefit from our approach to the rule to the same degree as other eligible advisers. The condition that advisers seeking to rely on the rule must also be registered with us as broker-dealers and that each account with respect to which an adviser seeks to rely on the rule must be a brokerage account subject to the Exchange Act, and the rules thereunder, and the rules of the self-regulatory organization(s) of which the broker dealer is a member, reflect what we believe is an important element of our balancing between easing regulatory burdens (by affording advisers an alternative means of compliance with section 206(3) of the Act) and meeting our investor protection objectives.<SU>76</SU>
          <FTREF/>Finally, we do not consider using performance rather than design standards to be consistent with our statutory mandate of investor protection in the present context.</P>
        <FTNT>
          <P>
            <SU>76</SU>
            <E T="03">See</E>2007 Principal Trade Rule Release, Section II.B.7 (noting commenters that objected to this condition as disadvantaging small broker-dealers (or affiliated but separate investment advisers and broker-dealers)).</P>
        </FTNT>
        <HD SOURCE="HD1">VII. Statutory Authority</HD>
        <P>The Commission is amending rule 206(3)-3T pursuant to sections 206A and 211(a) of the Advisers Act [15 U.S.C. 80b-6a and 80b-11(a)].</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 17 CFR Part 275</HD>
          <P>Investment advisers, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        <HD SOURCE="HD1">Text of Rule Amendment</HD>
        <P>For the reasons set out in the preamble, Title 17, Chapter II of the Code of Federal Regulations is amended as follows.</P>
        <REGTEXT PART="275" TITLE="17">
          <PART>
            <HD SOURCE="HED">PART 275—RULES AND REGULATIONS, INVESTMENT ADVISERS ACT OF 1940</HD>
          </PART>
          <AMDPAR>1. The authority citation for Part 275 continues to read in part as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>15 U.S.C. 80b-2(a)(11)(G), 80b-2(a)(11)(H), 80b-2(a)(17), 80b-3, 80b-4, 80b-4a, 80b-6(4), 80b-6a, and 80b-11, unless otherwise noted.</P>
          </AUTH>
          <STARS/>
        </REGTEXT>
        <REGTEXT PART="275" TITLE="17">
          <SECTION>
            <SECTNO>§ 275.206(3)-3T</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. In § 275.206(3)-3T, amend paragraph (d) by removing the words “December 31, 2012” and adding in their place “December 31, 2014.”</AMDPAR>
        </REGTEXT>
        <SIG>
          <DATED>Dated: December 20, 2012.</DATED>
          
          <P>By the Commission.</P>
          
          <NAME>Elizabeth M. Murphy,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31221 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 8011-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <PRTPAGE P="76861"/>
        <AGENCY TYPE="N">DEPARTMENT OF LABOR</AGENCY>
        <SUBAGY>Employment and Training Administration</SUBAGY>
        <CFR>20 CFR Parts 626, 627, 628, 631, 632, 633, 634, 636, 637, and 638</CFR>
        <RIN>RIN 1205-AB68</RIN>
        <SUBJECT>Removal of Job Training Partnership Act Implementing Regulations</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Employment and Training Administration, Labor.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Direct final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Employment and Training Administration (ETA) of the Department of Labor (Department) is removing the regulations at 20 CFR parts 626, 627, 628, 631, 632, 633, 634, 636, 637, and 638, which implemented the Job Training Partnership Act (JTPA or the Act). These regulations were designed to improve the employment status of disadvantaged youth, adults, dislocated workers, and other individuals facing barriers to employment. In 1998, Congress passed the Workforce Investment Act (WIA), which required the Secretary of Labor to transition any authority under the JTPA to the system created by WIA. Therefore, the Department is taking this action to remove regulations for a program that is no longer operative.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>

          <P>This Direct Final Rule is effective April 1, 2013 without further action, unless significant adverse comment is received by January 30, 2013. If significant adverse comment is received, the Department of Labor will publish a timely withdrawal of the rule in the<E T="04">Federal Register.</E>
          </P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by RIN 1205-AB68, by one of the following methods:</P>
          <P>
            <E T="03">Federal e-Rulemaking Portal: http://www.regulations.gov.</E>Follow the Web site instructions for submitting comments.</P>
          <P>
            <E T="03">Mail and hand delivery/courier:</E>Written comments, disk, and CD-ROM submissions may be mailed to Michael S. Jones, Acting Administrator, Office of Policy Development and Research, U.S. Department of Labor, 200 Constitution Avenue NW., Room N-5641, Washington, DC 20210.</P>
          <P>
            <E T="03">Instructions:</E>Label all submissions with “RIN 1205-AB68.”</P>

          <P>Please submit your comments by only one method. Please be advised that the Department will post all comments on this Direct Final Rule on<E T="03">http://www.regulations.gov</E>without making any change to the comments or redacting any information. The<E T="03">http://www.regulations.gov</E>Web site is the Federal e-rulemaking portal and all comments posted there are available and accessible to the public. Therefore, the Department recommends that commenters remove personal information such as Social Security Numbers, personal addresses, telephone numbers, and email addresses included in their comments as such information may become easily available to the public via the<E T="03">http://www.regulations.gov</E>Web site. It is the responsibility of the commenter to safeguard their personal information.</P>

          <P>Also, please note that due to security concerns, postal mail delivery in Washington, DC may be delayed. Therefore, the Department encourages the public to submit comments on<E T="03">http://www.regulations.gov.</E>
          </P>
          <P>
            <E T="03">Docket:</E>All comments on this Direct Final Rule will be available on the<E T="03">http://www.regulations.gov</E>Web site, posted without change, and can be found using RIN 1205-AB68. The Department also will make all the comments it receives available for public inspection by appointment during normal business hours at the above address. If you need assistance to review the comments, the Department will provide you with appropriate aids such as readers or print magnifiers. The Department will make copies of the rule available, upon request, in large print and electronic file on computer disk. To schedule an appointment to review the comments and/or obtain the rule in an alternative format, contact the Office of Policy Development and Research at (202) 693-3700 (this is not a toll-free number). You may also contact this office at the address listed below.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Michael S. Jones, Acting Administrator, Office of Policy Development and Research, Employment and Training Administration, U.S. Department of Labor, Room N-5641, 200 Constitution Avenue NW, Washington, DC 20210; telephone: (202) 693-3700 (this is not a toll-free number). This notice is available through the printed<E T="04">Federal Register,</E>and electronically at<E T="03">http://www.gpo.gov/fdsys/browse/collection.action?collectionCode=FR.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Direct Final Rule Procedure</HD>
        <P>Since removal of the Job Training Partnership Act implementing regulations is not controversial, and the authorizing legislation for these regulations has been repealed, these regulations govern a program that is no longer in operation. The Department therefore has determined that good cause exists to remove these regulations using a Direct Final Rule. No significant adverse comments are anticipated. All interested parties should comment at this time because we will not initiate an additional comment period.</P>

        <P>If significant adverse comments are received, we will publish a timely notice in the<E T="04">Federal Register</E>withdrawing this Direct Final Rule. For purposes of withdrawing this Direct Final Rule, a significant adverse comment is one that explains: (1) why the Direct Final Rule is inappropriate, including challenges to the rule's underlying premise or approach; or (2) why the Direct Final Rule will be ineffective or unacceptable without a change. In determining whether a significant adverse comment necessitates withdrawal of this Direct Final Rule, we will consider whether the comment raises an issue serious enough to warrant a substantive response through the notice and comment process.</P>
        <HD SOURCE="HD1">II. Background</HD>

        <P>Through this Direct Final Rule, the Department is removing and reserving the JTPA regulations at 20 CFR parts 626, 627, 628, 631, 632, 633, 634, 636, 637, and 638, which were designed to improve the employment status of disadvantaged young adults, dislocated workers, and individuals facing barriers to employment. These regulations have been superseded by the regulations promulgated under the Workforce Investment Act of 1998 (WIA), 29 U.S.C. 2801<E T="03">et seq.</E>
        </P>

        <P>The statutory purpose of the JTPA was to establish programs that prepared disadvantaged youth and adults who faced serious barriers to employment for participation in the labor force by providing job training and other services that would result in increased employment and earnings, increased educational and occupational skills, and decreased welfare dependency.<E T="03">See</E>20 CFR part 626. To carry out this purpose, the Department published regulations that implemented adult and youth training programs, summer youth employment and training programs, provided employment and training assistance for dislocated workers, and authorized programs for other individuals facing barriers to employment.<E T="03">See</E>20 CFR parts 628, 631. The JTPA regulations also established corrective action and sanctions for instances of noncompliance, provided procedures for hearings, and established standards and expectations for the programs authorized under the Act.<E T="03">See</E>20 CFR part 627.<PRTPAGE P="76862"/>
        </P>

        <P>On August 7, 1998, Congress passed WIA. Under WIA, which superseded the JTPA, Congress required the Secretary of Labor to develop and publish interim final regulations (IFR) to implement this transition no later than 180 days after WIA's enactment date.<E T="03">See</E>20 U.S.C. 9276(c)(1). The Department published the WIA IFR on April 15, 1999.<E T="03">See</E>64 FR 18662. In that IFR, the Department explicitly provided for the phased transition of the JTPA programs to WIA, to be fully completed by July 1, 2000.<E T="03">See</E>64 FR 18662, 18663 (Apr. 15, 1999). The final rule implementing WIA was published on August 11, 2000.<E T="03">See</E>65 FR 49293 (Aug. 11, 2000).</P>
        <P>Initially, although the JTPA authorizing legislation was repealed, the Department retained the JTPA regulations in the Code of Federal Regulations for grant closeout and auditing purposes. However, now that the JTPA programs have been transitioned to WIA for over a decade, the Department finds no reason to retain the JTPA regulations. Furthermore, the Department has previously removed several other JTPA regulatory provisions. Parts 629 and 630 were removed at 57 FR 62004 (Dec. 29, 1992). Part 635 was re-designated as 20 CFR part 1005 at 54 FR 39352 (Sept. 26, 1989), and the Department later removed part 1005 at 59 FR 26601 (May 23, 1994). Finally, the Department notes that it re-designated part 684 as part 638 at 55 FR 12992 (Apr. 6, 1990). Those JTPA regulatory provisions that remain are subject to this removal notice.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <CFR>20 CFR Parts 626, 627, 628, 631 and 637</CFR>
          <P>Accounting, Administrative practice and procedure, Disaster assistance, Grant programs—Labor, Manpower training programs, Reporting and recordkeeping requirements, Youth.</P>
          <CFR>20 CFR Part 632</CFR>
          <P>Administrative practice and procedure, Fraud, Grant programs—Indians, Grant programs—labor, Hawaiian Natives, Manpower training programs, Reporting and recordkeeping requirements Youth.</P>
          <CFR>20 CFR Part 633</CFR>
          <P>Grant programs—labor, Manpower training programs, Migrant labor, Recording and record keeping requirements.</P>
          <CFR>20 CFR Part 634</CFR>
          <P>Grant Programs—labor, Manpower training programs, Statistics.</P>
          <CFR>20 CFR Part 636</CFR>
          <P>Administrative practice and procedure, Grant programs—labor, Manpower training programs.</P>
          <CFR>20 CFR Part 638</CFR>
          <P>Grant programs—labor, Job Corps, Lobbying, Manpower training programs, Recording and record keeping requirements, Youth.</P>
        </LSTSUB>
        <P>Accordingly, under the authority of the Workforce Investment Act of 1998 (WIA), 29 U.S.C. 9276(a), and for the reasons discussed in the preamble, the Department amends 20 CFR Chapter V by removing Parts 626, 627, 628, 631, 632, 633, 634, 636, 637, and 638 as follows:</P>
        <REGTEXT PART="626" TITLE="20">
          <PART>
            <HD SOURCE="HED">PART 626—[REMOVED AND RESERVED]</HD>
          </PART>
          <AMDPAR>1. Remove and reserve part 626, consisting of §§ 626.1 through 626.5.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="627" TITLE="20">
          <PART>
            <HD SOURCE="HED">PART 627—[REMOVED AND RESERVED]</HD>
          </PART>
          <AMDPAR>2. Remove and reserve part 627, consisting of §§ 627.100 through 627.906.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="628" TITLE="20">
          <PART>
            <HD SOURCE="HED">PART 628—[REMOVED AND RESERVED]</HD>
          </PART>
          <AMDPAR>3. Remove and reserve part 628, consisting of §§ 628.100 through 628.804.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="631" TITLE="20">
          <PART>
            <HD SOURCE="HED">PART 631—[REMOVED AND RESERVED]</HD>
          </PART>
          <AMDPAR>4. Remove and reserve part 631, consisting of §§ 631.1 through 631.87.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="632" TITLE="20">
          <PART>
            <HD SOURCE="HED">PART 632—[REMOVED AND RESERVED]</HD>
          </PART>
          <AMDPAR>5. Remove and reserve part 632, consisting of §§ 632.1 through 632.263.</AMDPAR>
          <PART>
            <HD SOURCE="HED">PART 633—[REMOVED AND RESERVED]</HD>
          </PART>
          <AMDPAR>6. Remove and reserve part 633, consisting of §§ 633.102 through 633.322.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="634" TITLE="20">
          <PART>
            <HD SOURCE="HED">PART 634—[REMOVED AND RESERVED]</HD>
          </PART>
          <AMDPAR>7. Remove and reserve part 634, consisting of §§ 634.1 through 634.5.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="636" TITLE="20">
          <PART>
            <HD SOURCE="HED">PART 636—[REMOVED AND RESERVED]</HD>
          </PART>
          <AMDPAR>8. Remove and reserve part 636, consisting of §§ 636.1 through 636.11.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="637" TITLE="20">
          <PART>
            <HD SOURCE="HED">PART 637—[REMOVED AND RESERVED]</HD>
          </PART>
          <AMDPAR>9. Remove and reserve part 637, consisting of §§ 637.100 through 637.310.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="638" TITLE="20">
          <PART>
            <HD SOURCE="HED">PART 638—[REMOVED AND RESERVED]</HD>
          </PART>
          <AMDPAR>10. Remove and reserve part 638, consisting of §§ 638.100 through 638.815.</AMDPAR>
        </REGTEXT>
        <SIG>
          <DATED>Signed at Washington, DC, this 18th day of December, 2012.</DATED>
          <NAME>Jane Oates</NAME>
          <TITLE>Assistant Secretary, Employment and Training Administration.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31029 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4510-FN-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Food and Drug Administration</SUBAGY>
        <CFR>21 CFR Parts 520, 522, 529, and 558</CFR>
        <DEPDOC>[Docket No. FDA-2012-N-0002]</DEPDOC>
        <SUBJECT>New Animal Drugs; Enrofloxacin; Melengestrol; Meloxicam; Pradofloxacin; Tylosin</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Food and Drug Administration, HHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Food and Drug Administration (FDA) is amending the animal drug regulations to reflect approval actions for new animal drug applications (NADAs) and abbreviated new animal drug applications (ANADAs) during November 2012. FDA is also informing the public of the availability of summaries the basis of approval and of environmental review documents, where applicable.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective December 31, 2012.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>George K. Haibel, Center for Veterinary Medicine (HFV-6), Food and Drug Administration, 7519 Standish Pl., Rockville, MD 20855, 240-276-9019, email:<E T="03">george.haibel@fda.hhs.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>FDA is amending the animal drug regulations to reflect original and supplemental approval actions during November 2012, as listed in table 1 of this document. In addition, FDA is informing the public of the availability, where applicable, of documentation of environmental review required under the National Environmental Policy Act (NEPA) and, for actions requiring<PRTPAGE P="76863"/>review of safety or effectiveness data, summaries of the basis of approval (FOI Summaries) under the Freedom of Information Act (FOIA). These public documents may be seen in the Division of Dockets Management (HFA-305), Food and Drug Administration, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852, between 9 a.m. and 4 p.m., Monday through Friday. Persons with access to the Internet may obtain these documents at the Center for Veterinary Medicine FOIA Electronic Reading Room:<E T="03">http://www.fda.gov/AboutFDA/CentersOffices/OfficeofFoods/CVM/CVMFOIAElectronicReadingRoom/default.htm.</E>
        </P>
        <P>This rule does not meet the definition of “rule” in 5 U.S.C. 804(3)(A) because it is a rule of “particular applicability.” Therefore, it is not subject to the congressional review requirements in 5 U.S.C. 801-808.</P>
        <GPOTABLE CDEF="s50,r50,r50,r100,25,10,xs25" COLS="7" OPTS="L2,p7,7/8,i1">
          <TTITLE>Table 1—Original and Supplemental NADAs and ANADAs Approved During November 2012</TTITLE>
          <BOXHD>
            <CHED H="1">NADA/<LI>ANADA</LI>
            </CHED>
            <CHED H="1">Sponsor</CHED>
            <CHED H="1">New animal drug product name</CHED>
            <CHED H="1">Action</CHED>
            <CHED H="1">21 CFR Section</CHED>
            <CHED H="1">FOIA<LI>summary</LI>
            </CHED>
            <CHED H="1">NEPA review</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">141-344</ENT>
            <ENT>Bayer HealthCare LLC, Animal Health Division, P.O. Box 390, Shawnee Mission, KS 66201</ENT>
            <ENT>VERAFLOX (pradofloxacin) Oral Suspension for Cats</ENT>

            <ENT>Original approval for the treatment of skin infections (wounds and abscesses) in cats caused by susceptible strains of<E T="03">Pasteurella multocida, Streptococcus canis,</E>
              <E T="03">S. aureus, S. felis,</E>and<E T="03">S. pseudintermedius</E>
            </ENT>
            <ENT>520.1860</ENT>
            <ENT>Yes</ENT>
            <ENT>CE<SU>1</SU>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="01">141-346</ENT>
            <ENT>Abbott Laboratories, Inc., North Chicago, IL 60064</ENT>
            <ENT>OROCAM (meloxicam) Transmucosal Oral Spray</ENT>
            <ENT>Original approval for the control of pain and inflammation associated with osteoarthritis in dogs</ENT>
            <ENT>529.1350</ENT>
            <ENT>Yes</ENT>
            <ENT>CE<SU>1</SU>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="01">141-068</ENT>
            <ENT>Bayer HealthCare LLC, Animal Health Division, P.O. Box 390, Shawnee Mission, KS 66201</ENT>
            <ENT>BAYTRIL 100 (enrofloxacin) Injectable Solution</ENT>

            <ENT>Supplemental approval adding treatment and control of swine respiratory disease associated with<E T="03">Bordetella bronchiseptica</E>and<E T="03">Mycoplasma hyopneumoniae</E>
            </ENT>
            <ENT>522.812</ENT>
            <ENT>Yes</ENT>
            <ENT>CE<SU>1</SU>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="01">200-534</ENT>
            <ENT>Huvepharma AD, 5th Floor, 3A Nikolay Haitov St., 1113 Sophia, Bulgaria</ENT>
            <ENT>TYLOVET 100 (tylosin phosphate) and RUMENSIN (monensin) and MGA (melengestrone acetate) liquid and dry, combination drug Type C medicated feeds</ENT>
            <ENT>Original approval as a generic copy of NADA 138-870</ENT>
            <ENT>558.342</ENT>
            <ENT>Yes</ENT>
            <ENT>CE<SU>1</SU>
            </ENT>
          </ROW>
          <TNOTE>
            <SU>1</SU>The Agency has determined under 21 CFR 25.33 that this action is categorically excluded (CE) from the requirement to submit an environmental assessment or an environmental impact statement because it is of a type that does not individually or cumulatively have a significant effect on the human environment.</TNOTE>
        </GPOTABLE>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <CFR>
            <E T="03">21 CFR Parts 520, 522, and 529</E>
          </CFR>
          <P>Animal drugs.</P>
          <CFR>
            <E T="03">21 CFR Part 558</E>
          </CFR>
          <P>Animal drugs, animal feeds.</P>
        </LSTSUB>
        
        <P>Therefore, under the Federal Food, Drug, and Cosmetic Act and under authority delegated to the Commissioner of Food and Drugs and redelegated to the Center for Veterinary Medicine, 21 CFR parts 520, 522, 529, and 558 are amended as follows:</P>
        <REGTEXT PART="520" TITLE="21">
          <PART>
            <HD SOURCE="HED">PART 520—ORAL DOSAGE FORM NEW ANIMAL DRUGS</HD>
          </PART>
        </REGTEXT>
        
        <REGTEXT PART="520" TITLE="21">
          <AMDPAR>1. The authority citation for 21 CFR part 520 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>21 U.S.C. 360b.</P>
          </AUTH>
          
          <AMDPAR>2. Add § 520.1860 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 520.1860</SECTNO>
            <SUBJECT>Pradofloxacin.</SUBJECT>
            <P>(a)<E T="03">Specifications.</E>Each milliliter of suspension contains 25 milligrams (mg) pradofloxacin.</P>
            <P>(b)<E T="03">Sponsor.</E>See No. 000859 in § 510.600(c) of this chapter.</P>
            <P>(c)<E T="03">Special considerations.</E>Federal law restricts this drug to use by or on the order of a licensed veterinarian. Federal law prohibits the extralabel use of this drug in food-producing animals.</P>
            <P>(d)<E T="03">Conditions of use in cats</E>—(1)<E T="03">Amount.</E>Administer 3.4 mg/lb (7.5 mg/kg) body weight once daily for 7 consecutive days.</P>
            <P>(2)<E T="03">Indications for use.</E>For the treatment of skin infections (wounds and abscesses) in cats caused by susceptible strains of<E T="03">Pasteurella multocida, Streptococcus canis,</E>
              <E T="03">Staphylococcus aureus, Staphylococcus felis,</E>and<E T="03">Staphylococcus pseudintermedius.</E>
            </P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="522" TITLE="21">
          <PART>
            <HD SOURCE="HED">PART 522—IMPLANTATION OR INJECTABLE DOSAGE FORM NEW ANIMAL DRUGS</HD>
          </PART>
          <AMDPAR>3. The authority citation for 21 CFR part 522 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>21 U.S.C. 360b.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="522" TITLE="21">
          <AMDPAR>4. In § 522.812, revise paragraph (e)(3)(ii) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 522.812</SECTNO>
            <SUBJECT>Enrofloxacin.</SUBJECT>
            <STARS/>
            <P>(e) * * *</P>
            <P>(3) * * *</P>
            <P>(ii)<E T="03">Indications for use.</E>For the treatment and control of swine respiratory disease (SRD) associated with<E T="03">Actinobacillus pleuropneumoniae, Pasteurella multocida,</E>
              <E T="03">Haemophilus parasuis, Streptococcus suis,</E>
              <E T="03">Bordetella bronchiseptica,</E>and<E T="03">Mycoplasma hyopneumoniae.</E>
            </P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        
        <REGTEXT PART="529" TITLE="21">
          <PART>
            <HD SOURCE="HED">PART 529—CERTAIN OTHER DOSAGE FORM NEW ANIMAL DRUGS</HD>
          </PART>
          <AMDPAR>5. The authority citation for 21 CFR part 529 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>21 U.S.C. 360b.</P>
          </AUTH>
          
          <AMDPAR>6. Add § 529.1350 to read as follows:</AMDPAR>
        </REGTEXT>
        
        <REGTEXT PART="529" TITLE="21">
          <SECTION>
            <SECTNO>§ 529.1350</SECTNO>
            <SUBJECT>Meloxicam.</SUBJECT>
            <P>(a)<E T="03">Specifications.</E>Each milliliter of solution contains 5 milligrams (mg) meloxicam.</P>
            <P>(b)<E T="03">Sponsor.</E>See No. 000074 in § 510.600(c) of this chapter.<PRTPAGE P="76864"/>
            </P>
            <P>(c)<E T="03">Conditions of use in dogs</E>—(1)<E T="03">Amount.</E>Administer 0.1 mg per kilogram of body weight once daily using the metered dose pump.</P>
            <P>(2)<E T="03">Indications for use.</E>For the control of pain and inflammation associated with osteoarthritis in dogs.</P>
            <P>(3)<E T="03">Limitations.</E>Federal law restricts this drug to use by or on the order of a licensed veterinarian.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="558" TITLE="21">
          <PART>
            <HD SOURCE="HED">PART 558—NEW ANIMAL DRUGS FOR USE IN ANIMAL FEEDS</HD>
          </PART>
          <AMDPAR>7. The authority citation for 21 CFR part 558 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>21 U.S.C. 360b, 371.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="558" TITLE="21">
          <SECTION>
            <SECTNO>§ 558.342</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>8. In § 558.342, in the table, in paragraph (e)(1)(xi), in the “Limitations” column, revise the last sentence to read “Monensin provided by No. 000986 and tylosin provided by Nos. 000986 and 016592 in § 510.600(c) of this chapter.”; and in the “Sponsor” column, add “016592”.</AMDPAR>
        </REGTEXT>
        <SIG>
          <DATED>Dated: December 26, 2012.</DATED>
          <NAME>Bernadette Dunham,</NAME>
          <TITLE>Director, Center for Veterinary Medicine.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31397 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4160-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF STATE</AGENCY>
        <CFR>22 CFR Parts 120 and 126</CFR>
        <DEPDOC>[Public Notice 8135]</DEPDOC>
        <RIN>RIN 1400-AD26</RIN>
        <SUBJECT>Amendment to the International Traffic in Arms Regulations: Afghanistan and Change to Policy on Prohibited Exports</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Department of State.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Department of State is amending the International Traffic in Arms Regulations (ITAR) to list Afghanistan as a major non-NATO ally, and to make available the use of two additional defense export license exemptions for proscribed destinations.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>This rule is effective December 31, 2012.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Ms. Candace M. J. Goforth, Director, Office of Defense Trade Controls Policy, U.S. Department of State, telephone (202) 663-2792, or email<E T="03">DDTCResponseTeam@state.gov.</E>ATTN: Regulatory Change, Afghanistan and 126.1.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>On July 6, 2012, President Obama exercised his authority under section 517 of the Foreign Assistance Act of 1961 (FAA) to designate the Islamic Republic of Afghanistan as a major non-NATO ally (MNNA) for purposes of the FAA and the Arms Export Control Act. This final rule amends ITAR § 120.32, which lists major non-NATO allies, to account for this designation. Section 126.1 is amended to except the exemptions at ITAR §§ 126.4 and 126.6 from the prohibitions therein and the text is further amended to clarify the requirements therein. Additionally, § 126.1(g) is amended to clarify references to United Nations Security Council resolutions.</P>
        <HD SOURCE="HD1">Regulatory Analysis and Notices</HD>
        <HD SOURCE="HD2">Administrative Procedure Act</HD>
        <P>The Department of State is of the opinion that controlling the import and export of defense articles and services is a foreign affairs function of the United States Government and that rules implementing this function are exempt from sections 553 (rulemaking) and 554 (adjudications) of the Administrative Procedure Act. Since the Department is of the opinion that this rule is exempt from 5 U.S.C. 553, it is the view of the Department that the provisions of section 553(d) do not apply to this rulemaking. Therefore, this rule is effective upon publication. The Department also finds that, given the national security issues surrounding U.S. policy towards Afghanistan, notice and public procedure on this rule would be impracticable, unnecessary, or contrary to the public interest; for the same reason, the rule will be effective immediately.</P>
        <HD SOURCE="HD2">Regulatory Flexibility Act</HD>
        <P>Since the Department is of the opinion that this rule is exempt from the rulemaking provisions of 5 U.S.C. 553, it does not require analysis under the Regulatory Flexibility Act.</P>
        <HD SOURCE="HD2">Unfunded Mandates Act of 1995</HD>
        <P>This rulemaking does not involve a mandate that will result in the expenditure by state, local, and tribal governments, in the aggregate, or by the private sector, of $100 million or more in any year and it will not significantly or uniquely affect small governments. Therefore, no actions were deemed necessary under the provisions of the Unfunded Mandates Reform Act of 1995.</P>
        <HD SOURCE="HD2">Small Business Regulatory Enforcement Fairness Act of 1996</HD>
        <P>This rulemaking has been found not to be a major rule within the meaning of the Small Business Regulatory Enforcement Fairness Act of 1996.</P>
        <HD SOURCE="HD2">Executive Orders 12372 and 13132</HD>
        <P>This rulemaking will not have substantial direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, in accordance with Executive Order 13132, it is determined that this rulemaking does not have sufficient federalism implications to require consultations or warrant the preparation of a federalism summary impact statement. The regulations implementing Executive Order 12372 regarding intergovernmental consultation on Federal programs and activities do not apply to this rulemaking.</P>
        <HD SOURCE="HD2">Executive Orders 12866 and 13563</HD>
        <P>Executive Orders 13563 and 12866 direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributed impacts, and equity). These Executive Orders stress the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. This rule has been designated “significant regulatory actions,” although not economically significant, under section 3(f) of Executive Order 12866. Accordingly, this rule has been reviewed by the Office of Management and Budget (OMB).</P>
        <HD SOURCE="HD2">Executive Order 12988</HD>
        <P>The Department of State has reviewed this rulemaking in light of sections 3(a) and 3(b)(2) of Executive Order 12988 to eliminate ambiguity, minimize litigation, establish clear legal standards, and reduce burden.</P>
        <HD SOURCE="HD2">Executive Order 13175</HD>
        <P>The Department of State has determined that this rulemaking will not have tribal implications, will not impose substantial direct compliance costs on Indian tribal governments, and will not pre-empt tribal law. Accordingly, the requirement of Executive Order 13175 does not apply to this rulemaking.</P>
        <HD SOURCE="HD2">Paperwork Reduction Act</HD>

        <P>This rule does not impose any new reporting or recordkeeping requirements<PRTPAGE P="76865"/>subject to the Paperwork Reduction Act, 44 U.S.C. Chapter 35.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 22 CFR Parts 120 and 126</HD>
          <P>Arms and munitions, Exports.</P>
        </LSTSUB>
        
        <P>Accordingly, for the reasons set forth above, Title 22, Chapter I, Subchapter M, parts 120 and 126 are amended as follows:</P>
        <REGTEXT PART="120" TITLE="22">
          <PART>
            <HD SOURCE="HED">PART 120—PURPOSE AND DEFINITIONS</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 120 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>Secs. 2, 38, and 71, Pub. L. 90-629, 90 Stat. 744 (22 U.S.C. 2752, 2778, 2797); 22 U.S.C. 2794; E.O. 11958, 42 FR 4311; E.O. 13284, 68 FR 4075; 3 CFR, 1977 Comp. p. 79; 22 U.S.C. 2651a; Pub. L. 105-261, 112 Stat. 1920; Pub. L. 111-266.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="120" TITLE="22">
          <AMDPAR>2. Section 120.32 is revised to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 120.32</SECTNO>
            <SUBJECT>Major non-NATO ally.</SUBJECT>
            <P>
              <E T="03">Major non-NATO ally,</E>as defined in section 644(q) of the Foreign Assistance Act of 1961 (22 U.S.C. 2403(q)), means a country that is designated in accordance with section 517 of the Foreign Assistance Act of 1961 (22 U.S.C. 2321(k)) as a major non-NATO ally for purposes of the Foreign Assistance Act of 1961 and the Arms Export Control Act (22 U.S.C. 2151<E T="03">et seq.</E>and 22 U.S.C. 2751<E T="03">et seq.</E>). The following countries are designated as major non-NATO allies: Afghanistan (<E T="03">see</E>§ 126.1(g) of this subchapter), Argentina, Australia, Bahrain, Egypt, Israel, Japan, Jordan, Kuwait, Morocco, New Zealand, Pakistan, the Philippines, Thailand, and Republic of Korea. Taiwan shall be treated as though it were designated a major non-NATO ally.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="126" TITLE="22">
          <PART>
            <HD SOURCE="HED">PART 126—GENERAL POLICIES AND PROVISIONS</HD>
          </PART>
          <AMDPAR>3. The authority citation for part 126 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>Secs. 2, 38, 40, 42, and 71, Pub. L. 90-629, 90 Stat. 744 (22 U.S.C. 2752, 2778, 2780, 2791, and 2797); E.O. 11958, 42 FR 4311; 3 CFR, 1977 Comp., p. 79; 22 U.S.C. 2651a; 22 U.S.C. 287c; E.O. 12918, 59 FR 28205; 3 CFR, 1994 Comp., p. 899; Sec. 1225, Pub. L. 108-375; Sec. 7089, Pub. L. 111-117; Pub. L. 111-266; Section 7045, Pub. L. 112-74; Section 7046, Pub. L. 112-74.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="126" TITLE="22">
          <AMDPAR>4. Section 126.1 is amended by revising paragraphs (a) and (g) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 126.1</SECTNO>
            <SUBJECT>Prohibited exports, imports, and sales to or from certain countries.</SUBJECT>
            <P>(a)<E T="03">General.</E>It is the policy of the United States to deny licenses and other approvals for exports and imports of defense articles and defense services destined for or originating in certain countries. This policy applies to Belarus, Cuba, Eritrea, Iran, North Korea, Syria, and Venezuela. This policy also applies to countries with respect to which the United States maintains an arms embargo (<E T="03">e.g.,</E>Burma, China, and the Republic of the Sudan) or whenever an export would not otherwise be in furtherance of world peace and the security and foreign policy of the United States. Information regarding certain other embargoes appears elsewhere in this section. Comprehensive arms embargoes are normally the subject of a State Department notice published in the<E T="04">Federal Register</E>. The exemptions provided in this subchapter, except §§ 123.17, 126.4, and 126.6 of this subchapter or when the recipient is a U.S. Government department or agency, do not apply with respect to defense articles or defense services originating in or for export to any proscribed countries, areas, or persons identified in this section.</P>
            <STARS/>
            <P>(g)<E T="03">Afghanistan.</E>It is the policy of the United States to deny licenses or other approvals for exports and imports of defense articles and defense services, destined for or originating in Afghanistan, except that a license or other approval may be issued, on a case-by-case basis, for the Government of Afghanistan or coalition forces. In addition, the names of individuals, groups, undertakings, and entities subject to arms embargoes, due to their affiliation with the Taliban, Al-Qaida, or those associated with them, are published in lists maintained by the United Nations Security Council's Sanctions Committees (established pursuant to United Nations Security Council resolutions (UNSCR) 1267, 1988, and 1989).</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: December 18, 2012.</DATED>
          <NAME>Rose E. Gottemoeller,</NAME>
          <TITLE>Acting Under Secretary, Arms Control and International Security,  Department of State.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31217 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4710-25-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
        <CFR>38 CFR Part 17</CFR>
        <RIN>RIN 2900-AO58</RIN>
        <SUBJECT>Copayments for Medications in 2013</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Department of Veterans Affairs.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Interim final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Department of Veterans Affairs (VA) amends its medical regulations concerning the copayment required for certain medications. But for this rulemaking, beginning on January 1, 2013, the copayment amount would increase based on a formula set forth in regulation. The maximum annual copayment amount payable by veterans would also increase. For 2012, VA “froze” the copayment amount for veterans in VA's health care system enrollment priority categories 2 through 6, but allowed copayments to increase based on the regulatory formula for veterans in priority categories 7 and 8. However, that formula did not trigger an increase in the copayment amount for veterans in priority categories 7 and 8. This rulemaking freezes copayments at the current rate for veterans in priority categories 2 through 8 for 2013, and thereafter resumes increasing copayments in accordance with the regulatory formula.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>This rule is effective on December 31, 2012.</P>
          <P>Comments must be received on or before March 1, 2013.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Written comments may be submitted by email through<E T="03">http://www.regulations.gov;</E>by mail or hand-delivery to Director, Regulation Policy and Management (02REG), Department of Veterans Affairs, 810 Vermont Avenue NW., Room 1068, Washington, DC 20420; or by fax to (202) 273-9026. (This is not a toll-free number.) Comments should indicate that they are submitted in response to “RIN 2900-AO58, Copayments for Medications in 2013.” Copies of comments received will be available for public inspection in the Office of Regulation Policy and Management, Room 1063B, between the hours of 8:00 a.m. and 4:30 p.m. Monday through Friday (except holidays). Please call (202) 461-4902 for an appointment. (This is not a toll-free number.) In addition, during the comment period, comments may be viewed online through the Federal Docket Management System (FDMS) at<E T="03">http://www.regulations.gov</E>.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Kristin Cunningham, Director, Business Policy, Chief Business Office, 810 Vermont Avenue NW., Washington, DC 20420, (202) 461-1599. (This is not a toll-free number.)</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>Under 38 U.S.C. 1722A(a), VA must require veterans to pay a $2 copayment for each 30-day supply of medication furnished on an outpatient basis for the treatment of a non-service-connected disability or<PRTPAGE P="76866"/>condition unless a veteran has a service-connected disability rated 50 percent or more, is a former prisoner of war, or has an annual income at or below the maximum annual rate of VA pension that would be payable if the veteran were eligible for pension. Under 38 U.S.C. 1722A(b), VA “may,” by regulation, increase that copayment amount and establish a maximum annual copayment amount (a “cap”). We have consistently interpreted section 1722A(b) to mean that VA has discretion to determine the appropriate copayment amount and annual cap amount for medication furnished on an outpatient basis for covered treatment, provided that any decision by VA to increase the copayment amount or annual cap amount is the subject of a rulemaking proceeding. We have implemented this statute in 38 CFR 17.110.</P>
        <P>Under 38 CFR 17.110(b)(1), veterans are obligated to pay VA a copayment for each 30-day or less supply of medication provided by VA on an outpatient basis (other than medication administered during treatment). Under the current regulation, for the period from July 1, 2010, through December 31, 2012, the copayment amount for veterans in priority categories 2 through 6 of VA's health care system is $8. 38 CFR 17.110(b)(1)(ii). Thereafter, the copayment amount for all affected veterans is to be established using a formula based on the prescription drug component of the Medical Consumer Price Index (CPI-P), set forth in 38 CFR 17.110(b)(1)(iv). For veterans in priority categories 7 and 8, the copayment amount from July 1, 2010, through December 31, 2011, was $9. 38 CFR 17.110(b)(1)(iii). After December 31, 2011, copayments for veterans in priority categories 7 and 8 were subject to the regulatory formula; however, that formula did not trigger an increase in the copayment amount, so it remains $9.</P>
        <P>Current § 17.110(b)(2) also includes a “cap” on the total amount of copayments in a calendar year for a veteran enrolled in one of VA's health care enrollment system priority categories 2 through 6. Through December 31, 2012, the annual cap is set at $960. Thereafter, the cap is to increase “by $120 for each $1 increase in the copayment amount” applicable to veterans enrolled in one of VA's health care enrollment system priority categories 2 through 6.</P>
        <P>On December 20, 2011, we published a final rulemaking that “froze” copayments for veterans in priority categories 2 through 6 at $8, through December 31, 2012. 76 FR 78824, Dec. 20, 2011. In that rulemaking, we stated that this freeze was appropriate because this group would be impacted more by the increase due to their likely greater need for medical care as a result of their service-connected disabilities or conditions. This continues to be true, and therefore we are continuing to freeze copayments for these veterans for the next 12 months.</P>
        <P>We also believe that a freeze of the copayment rate is now appropriate for veterans enrolled in priority categories 7 and 8. Prior rulemakings justified freezing copayment rates on the basis that higher copayments reduced the utilization of VA pharmacy benefits. The ability to ensure that medications are taken as prescribed is essential to effective health care management. VA can monitor whether its patients are refilling prescriptions at regular intervals while also checking for medications that may conflict with each other when these prescriptions are filled by VA. When non-VA providers are also issuing prescriptions, there is a greater risk of adverse interactions and harm to the patient because it is more difficult for each provider to know if the patient is taking any other medications.</P>

        <P>At the end of calendar year 2013, unless additional rulemaking is initiated, VA will once again utilize the CPI-P methodology in § 17.110(b)(1)(iv) to determine whether to increase copayments and calculate any mandated increase in the copayment amount for veterans in priority categories 2 through 8. At that time, the CPI-P as of September 30, 2013, will be divided by the index as of September 30, 2001, which was 304.8. The ratio will then be multiplied by the original copayment amount of $7. The copayment amount of the new calendar year will be rounded down to the whole dollar amount. As mandated by current  § 17.110(b)(2), the annual cap will be calculated by increasing the cap by $120 for each $1 increase in the copayment amount. Any change in the copayment amount and cap, along with the associated calculations explaining the basis for the increase, will be published in a<E T="04">Federal Register</E>notice. Thus, the intended effect of this rule is to temporarily prevent increases in copayment amounts and the copayment cap for veterans in priority categories 2 through 8, following which copayments and the copayment cap will increase as prescribed in current § 17.110(b).</P>
        <HD SOURCE="HD1">Administrative Procedure Act</HD>
        <P>In accordance with 5 U.S.C. 553(b)(B) and (d)(3), the Secretary of Veterans Affairs finds that there is good cause to dispense with the opportunity for advance notice and opportunity for public comment and good cause to publish this rule with an immediate effective date. As stated above, this rule freezes at current rates the prescription drug copayment that VA charges certain veterans. The Secretary finds that it is impracticable and contrary to the public interest to delay this rule for the purpose of soliciting advance public comment or to have a delayed effective date. Increasing the copayment amount on January 1, 2013, might cause a significant financial hardship for some veterans.</P>

        <P>For the above reasons, the Secretary issues this rule as an interim final rule. VA will consider and address comments that are received within 60 days of the date this interim final rule is published in the<E T="04">Federal Register</E>.</P>
        <HD SOURCE="HD1">Effect of Rulemaking</HD>
        <P>Title 38 of the Code of Federal Regulations, as revised by this interim final rulemaking, represents VA's implementation of its legal authority on this subject. Other than future amendments to this regulation or governing statutes, no contrary guidance or procedures are authorized. All existing or subsequent VA guidance must be read to conform with this rulemaking if possible or, if not possible, such guidance is superseded by this rulemaking.</P>
        <HD SOURCE="HD1">Paperwork Reduction Act</HD>
        <P>This interim final rule contains no provisions constituting a collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3521).</P>
        <HD SOURCE="HD1">Executive Orders 12866 and 13563</HD>

        <P>Executive Orders 12866 and 13563 direct agencies to assess the costs and benefits of available regulatory alternatives and, when regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, and other advantages; distributive impacts; and equity). Executive Order 13563 (Improving Regulation and Regulatory Review) emphasizes the importance of quantifying both costs and benefits, reducing costs, harmonizing rules, and promoting flexibility. Executive Order 12866 (Regulatory Planning and Review) defines a “significant regulatory action,” which requires review by the Office of Management and Budget (OMB), as “any regulatory action that is likely to result in a rule that may: (1) Have an annual effect on the economy of $100 million or more or adversely affect in a material way the<PRTPAGE P="76867"/>economy, a sector of the economy, productivity, competition, jobs, the environment, public health or safety, or State, local, or tribal governments or communities; (2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another agency; (3) Materially alter the budgetary impact of entitlements, grants, user fees, or loan programs or the rights and obligations of recipients thereof; or (4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in this Executive Order.”</P>
        <P>The economic, interagency, budgetary, legal, and policy implications of this regulatory action have been examined, and it has been determined to be a significant regulatory action under Executive Order 12866.</P>
        <HD SOURCE="HD1">Unfunded Mandates</HD>
        <P>The Unfunded Mandates Reform Act of 1995 requires, at 2 U.S.C. 1532, that agencies prepare an assessment of anticipated costs and benefits before issuing any rule that may result in an expenditure by State, local, and tribal governments, in the aggregate, or by the private sector, of $100 million or more (adjusted annually for inflation) in any given year. This rule will have no such effect on State, local, and tribal governments, or on the private sector.</P>
        <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
        <P>The Secretary hereby certifies that this interim final rule will not have a significant economic impact on a substantial number of small entities as they are defined in the Regulatory Flexibility Act, 5 U.S.C. 601-612. This interim final rule will temporarily freeze the copayments that certain veterans are required to pay for prescription drugs furnished by VA. The interim final rule affects individuals and has no impact on any small entities. Therefore, pursuant to 5 U.S.C. 605(b), this rulemaking is exempt from the initial and final regulatory flexibility analysis requirements of sections 603 and 604.</P>
        <HD SOURCE="HD1">Catalog of Federal Domestic Assistance</HD>
        <P>The Catalog of Federal Domestic Assistance program number and title for this rule are as follows: 64.005, Grants to States for Construction of State Home Facilities; 64.007, Blind Rehabilitation Centers; 64.008, Veterans Domiciliary Care; 64.009, Veterans Medical Care Benefits; 64.010, Veterans Nursing Home Care; 64.011, Veterans Dental Care; 64.012, Veterans Prescription Service; 64.013, Veterans Prosthetic Appliances; 64.014, Veterans State Domiciliary Care; 64.015, Veterans State Nursing Home Care; 64.016, Veterans State Hospital Care; 64.018, Sharing Specialized Medical Resources; 64.019, Veterans Rehabilitation Alcohol and Drug Dependence; 64.022, Veterans Home Based Primary Care; and 64.024, VA Homeless Providers Grant and Per Diem Program.</P>
        <HD SOURCE="HD1">Signing Authority</HD>
        <P>The Secretary of Veterans Affairs, or designee, approved this document and authorized the undersigned to sign and submit the document to the Office of the Federal Register for publication electronically as an official document of the Department of Veterans Affairs. John R. Gingrich, Chief of Staff, Department of Veterans Affairs, approved this document on December 7, 2012, for publication.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 38 CFR Part 17</HD>
          <P>Administrative practice and procedure, Alcohol abuse, Alcoholism, Claims, Day care, Dental health, Drug abuse, Foreign relations, Government contracts, Grant programs-health, Grant programs-veterans, Health care, Health facilities, Health professions, Health records, Homeless, Medical and dental schools, Medical devices, Medical research, Mental health programs, Nursing homes, Philippines, Reporting and recordkeeping requirements, Scholarships and fellowships, Travel and transportation expenses, Veterans.</P>
        </LSTSUB>
        <SIG>
          <DATED>Approved: December 7, 2012.</DATED>
          <NAME>John R. Gingrich,</NAME>
          <TITLE>Chief of Staff, Department of Veterans Affairs.</TITLE>
        </SIG>
        <P>For the reasons set forth in the preamble, VA amends 38 CFR part 17 as follows:</P>
        <REGTEXT PART="17" TITLE="38">
          <PART>
            <HD SOURCE="HED">PART 17—MEDICAL</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 17 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>38 U.S.C. 501(a), and as noted in specific sections.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="17" TITLE="38">
          <SECTION>
            <SECTNO>§ 17.110</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. Amend § 17.110 as follows:</AMDPAR>
          <AMDPAR>a. In paragraphs (b)(1)(ii) and (b)(2), remove “December 31, 2012” each place it appears and add, in each place, “December 31, 2013”.</AMDPAR>
          <AMDPAR>b. In paragraphs (b)(1)(iii) and (b)(1)(iv), remove “December 31, 2011” each place it appears and add, in each place, “December 31, 2013”.</AMDPAR>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31432 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 8320-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <CFR>40 CFR Part 52</CFR>
        <DEPDOC>[Docket No. EPA-R02-OAR-2012-0504; FRL-9763-6]</DEPDOC>
        <SUBJECT>Approval and Promulgation of Air Quality Implementation Plans; New York, New Jersey, and Connecticut; Determination of Attainment of the 2006 Fine Particle Standard</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The Environmental Protection Agency (EPA) is determining that the New York-N. New Jersey-Long Island, NY-NJ-CT fine particle (PM<E T="52">2.5</E>) nonattainment area for the 2006 24-hour PM<E T="52">2.5</E>National Ambient Air Quality Standard (NAAQS) has attained the 2006 24-hour PM<E T="52">2.5</E>NAAQS. The determination of attainment will suspend the requirements for the New York-N. New Jersey-Long Island, NY-NJ-CT PM<E T="52">2.5</E>nonattainment area to submit an attainment demonstration, associated reasonably available control measures, reasonable further progress, contingency measures, and other planning state implementation plans (SIPs) related to attainment of the 2006 24-hour PM<E T="52">2.5</E>NAAQS for so long as the area continues to attain the 2006 24-hour PM<E T="52">2.5</E>NAAQS.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>This rule is effective on December 31, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>EPA has established a docket for this action under Docket ID Number EPA-R02-OAR-2012-0504. All documents in the docket are listed in the<E T="03">http://www.regulations.gov</E>web site. Although listed in the electronic docket, some information is not publicly available, i.e., confidential business information (CBI) or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, is not placed on the Internet and will be publicly available only in hard copy form. Publicly available docket materials are available either electronically through<E T="03">http://www.regulations.gov</E>or in hard copy for public inspection during normal business hours at the Air Programs Branch, U.S. Environmental Protection Agency, Region II, 290 Broadway, New York, New York 10007.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Gavin Lau, (212) 637-3708, or by email at<E T="03">lau.gavin@epa.gov</E>if you have questions related to New York or New Jersey. If you have questions related to Connecticut, please contact Alison C.<PRTPAGE P="76868"/>Simcox, (617) 918-1684, or by email at<E T="03">simcox.alison@epa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Throughout this document whenever “we,” “us,” or “our” is used, we mean EPA.</P>
        <P>The<E T="02">SUPPLEMENTARY INFORMATION</E>section is arranged as follows:</P>
        <EXTRACT>
          <FP SOURCE="FP-2">I. What action Is EPA taking?</FP>
          <FP SOURCE="FP-2">II. What is the background for EPA's action?</FP>
          <FP SOURCE="FP-2">III. What comments did EPA receive on its proposal and what is EPA's response?</FP>
          <FP SOURCE="FP-2">IV. What Is the effect of this action?</FP>
          <FP SOURCE="FP-2">V. What is EPA's final action?</FP>
          <FP SOURCE="FP-2">VI. Statutory and executive order reviews</FP>
        </EXTRACT>
        <HD SOURCE="HD1">I. What action Is EPA taking?</HD>

        <P>EPA is determining that the New York-N. New Jersey-Long Island, NY-NJ-CT fine particle (PM<E T="52">2.5</E>) nonattainment area for the 2006 24-hour PM<E T="52">2.5</E>NAAQS, referred to from this point forward as the NY-NJ-CT PM<E T="52">2.5</E>nonattainment area, has attained the 2006 24-hour PM<E T="52">2.5</E>NAAQS. This determination is based upon quality-assured, quality-controlled and certified ambient air monitoring data that show the area has monitored attainment of the 2006 24-hour PM<E T="52">2.5</E>NAAQS for the 2007-2009, 2008-2010, and 2009-2011 monitoring periods. Specific details regarding the determination and the rationale for EPA's action are explained in the proposed rulemaking published in the<E T="04">Federal Register</E>(FR) on August 30, 2012 (77 FR 52626).</P>
        <HD SOURCE="HD1">II. What is the background for EPA's action?</HD>

        <P>EPA's determination is being made in accordance with its longstanding interpretation under the Clean Data Policy, and with previously issued rules and determinations of attainment. A brief description of the Clean Data Policy with respect to the 2006 PM<E T="52">2.5</E>standard is set forth below. In addition, the docket for this rulemaking includes documentation providing more detail regarding the application of EPA's Clean Data Policy to determinations of attainment for the 2006 PM<E T="52">2.5</E>NAAQS.</P>
        <P>In April 2007, EPA issued its PM<E T="52">2.5</E>Implementation Rule for the 1997 PM<E T="52">2.5</E>standard. 72 FR 20586; (April 25, 2007). In March, 2012, EPA published implementation guidance for the 2006 PM<E T="52">2.5</E>standard.<E T="03">See</E>Memorandum from Stephen D. Page, Director, Office of Air Quality Planning and Standards, “Implementation Guidance for the 2006 24-Hour Final Particle (PM<E T="52">2.5</E>) National Ambient Air Quality Standards (NAAQS)” (March 2, 2012). In that guidance, EPA stated its view “that the overall framework and policy approach of the 2007 PM<E T="52">2.5</E>Implementation Rule continues to provide effective and appropriate guidance on the EPA's interpretation of the general statutory requirements that states should address in their SIPs. In general, the EPA believes that the interpretations of the statute in the framework of the 2007 PM<E T="52">2.5</E>Implementation Rule are relevant to the statutory requirements for the 2006 24-hour PM<E T="52">2.5</E>NAAQS * * *”<E T="03">Id.,</E>page 1. With respect to the statutory provisions applicable to 2006 PM<E T="52">2.5</E>implementation, the guidance emphasized that “EPA outlined its interpretation of many of these provisions in the 2007 PM<E T="52">2.5</E>Implementation Rule. In addition to regulatory provisions, the EPA provided substantial general guidance for attainment plans for PM<E T="52">2.5</E>in the preamble to the final the [<E T="03">sic</E>] 2007 PM<E T="52">2.5</E>Implementation Rule.”<E T="03">Id.,</E>page 2. In keeping with the principles set forth in the guidance, and with respect to the effect of a determination of attainment for the 2006 PM<E T="52">2.5</E>standard, EPA is applying the same interpretation here with respect to the implications of clean data determinations that it set forth in the preamble to the 1997 PM<E T="52">2.5</E>standard and in the regulation that embodies this interpretation. 40 CFR 51.1004(c).<SU>1</SU>
          <FTREF/>EPA has long applied this interpretation in regulations and individual rulemakings for the 1-hour ozone and 1997 8-hour ozone standards, the PM-10 standard, and the lead standard.</P>
        <FTNT>
          <P>

            <SU>1</SU>While EPA recognizes that 40 CFR 51.1004(c) does not itself expressly apply to the 2006 PM<E T="52">2.5</E>standard, the statutory interpretation that it embodies is identical and is applicable to both the 1997 and 2006 PM<E T="52">2.5</E>standards.</P>
        </FTNT>

        <P>In 1995, based on the interpretation of Clean Air Act (CAA) sections 171 and 172, and section 182 in the General Preamble, EPA set forth what has become known as its “Clean Data Policy” for the 1-hour ozone NAAQS.<E T="03">See</E>Memorandum from John S. Seitz, Director, Office of Air Quality Planning and Standards, “Reasonable Further Progress, Attainment Demonstration, and Related Requirements for Ozone Nonattainment Areas Meeting the Ozone National Ambient Air Quality Standard” (May 10, 1995). In 2004, EPA indicated its intention to extend the Clean Data Policy to the PM<E T="52">2.5</E>NAAQS.<E T="03">See</E>Memorandum from Steve Page, Director, EPA Office of Air Quality Planning and Standards, “Clean Data Policy for the Fine Particle National Ambient Air Quality Standards” (December 14, 2004).</P>
        <P>The Clean Data Policy represents EPA's interpretation that certain requirements of subpart 1 of part D of the Act are by their terms not applicable to areas that are currently attaining the NAAQS.<SU>2</SU>
          <FTREF/>The specific requirements that are inapplicable to an area attaining the standard are the requirements to submit a SIP that provides for: attainment of the NAAQS; implementation of all reasonably available control measures; reasonable further progress (RFP); and implementation of contingency measures for failure to meet deadlines for RFP and attainment.</P>
        <FTNT>
          <P>

            <SU>2</SU>This discussion refers to subpart 1 because subpart 1 contains the requirements relating to attainment of the 2006 PM<E T="52">2.5</E>NAAQS.</P>
        </FTNT>

        <P>It is important to note that the obligation of a State with respect to an area which attains the 2006 PM<E T="52">2.5</E>standard based on three years of data, to submit an attainment demonstration and related planning submissions is suspended only for so long as the area continues to attain the standard. If EPA subsequently determines, after notice-and-comment rulemaking, that the area has violated the NAAQS, the requirements for the State to submit a SIP to meet the previously suspended requirements would be reinstated. It is likewise important to note that the area remains designated nonattainment pending a further redesignation action.</P>
        <HD SOURCE="HD1">III. What comments did EPA receive on its proposal and what is EPA's response?</HD>
        <P>EPA received one adverse comment on the proposal, from a pseudonymous commenter. A summary of the comment submitted and EPA's response is provided below.</P>
        <P>
          <E T="03">Comment:</E>The commenter alleges that the determination of attainment for the NY-NJ-CT PM<E T="52">2.5</E>nonattainment area is inappropriate due to particulate matter released from burning and allegedly inadequate air quality monitoring. The commenter also questioned the interaction between the New Jersey Department of Environmental Protection and EPA.</P>
        <P>
          <E T="03">Response:</E>In this rulemaking, EPA is making the determination that the NY-NJ-CT PM<E T="52">2.5</E>nonattainment area has attained the 2006 PM<E T="52">2.5</E>NAAQS. EPA is finalizing its determination only after conducting notice and comment rulemaking, through a transparent process in which the information on which the determination is based has been made available in the docket and also placed in the Technical Support Document for this rulemaking. EPA's determination of attainment is based on quality-assured, quality-controlled, and certified ambient air monitoring data. These data establish that, for 2007-2009, 2008-2010, and 2009-2011 the NY-NJ-CT PM<E T="52">2.5</E>nonattainment area<PRTPAGE P="76869"/>meets the 2006 24-hour PM<E T="52">2.5</E>NAAQS. Air monitoring data available for 2012 also indicate that the NY-NJ-CT PM<E T="52">2.5</E>nonattainment area is continuing to meet the 2006 24-hour PM<E T="52">2.5</E>NAAQS. Contrary to the commenter's contention, the air monitoring networks for Connecticut, New Jersey, and New York are adequate, and meet the requirements for monitoring as specified in 40 CFR Part 58. EPA meets annually with the states to determine the adequateness of the monitoring networks. Air monitoring network approval letters are included in the Technical Support Document and docket for the proposed rule. In conclusion, the determination of attainment is being made based on quality-assured air quality data from approved monitoring networks. The suspension of requirements for this area to submit attainment-related planning SIP submission requirements lasts only as long as the area continues to meet that standard. No other requirements are suspended and no control measures in the SIP are being relaxed. This action does not change the implementation of control measures, or air quality, in the area.</P>

        <P>Table 1 shows the design values by county (i.e., the 3-year average of 98th percentile 24-hour PM<E T="52">2.5</E>concentrations) for the 2006 24-hour PM<E T="52">2.5</E>NAAQS for the NY-NJ-CT PM<E T="52">2.5</E>nonattainment area monitors for the years 2007 through 2011 based on complete (except where otherwise noted), quality-assured and certified air quality monitoring data. As shown in Table 1, none of the design values for the periods of 2007-2009, 2008-2010, and 2009-2011 in the NY-NJ-CT PM<E T="52">2.5</E>nonattainment area exceeds<FTREF/>the 2006 24-hour PM<E T="52">2.5</E>NAAQS of 35.0 micrograms per cubic meter (μg/m<SU>3</SU>).</P>
        <FTNT>
          <P>
            <SU>3</SU>PM<E T="52">2.5</E>Design Values can be found at:<E T="03">http://www.epa.gov/airtrends/values.html.</E>
          </P>
          <P>
            <SU>4</SU>The monitor located in Nassau County had incomplete data for 2007 which led to inability to calculate design values for the period of 2007-2009. The monitor did not show previous violations and therefore it was deemed that determining the design values though alternative procedures was not necessary.</P>
          <P>

            <SU>5</SU>The monitor in New York County located at Public School 59 was the highest reading monitor in the County at the time EPA made designations for the 2006 PM<E T="52">2.5</E>NAAQS. Midway through 2008, the monitor at PS 59 was shut down due to the demolition of the building site. Since missing 2008 data affected calculation of the design value for the 24-hour standard, EPA used an alternative procedure to determine the design value for the 24-hour standard. Detailed information on this alternative procedure can be found in the Technical Support Document for this rulemaking.</P>
          <P>
            <SU>6</SU>Design Value was calculated using the alternative procedure described in the Technical Support Document for this rulemaking.</P>
          <P>

            <SU>7</SU>The air monitor at the Newark Willis Center station in Essex County was discontinued on July 24, 2008 due to an unexpected loss of access, and replaced with a new monitor at the Newark Firehouse. PM<E T="52">2.5</E>monitoring was established at the firehouse on May 13, 2009. EPA used an alternative procedure to determine the design value for the 24-hour standard for 2007-2009 and 2008-2010. The monitor did not show any violations in 2009 and 2010, therefore it was deemed that determining the design value for 2009-2011 through alternative procedures was not necessary. For 2009 and 2010, the 98th percentile value for the new monitor was 24 µg/m<SU>3</SU>. Detailed information on this alternative procedure can be found in the Technical Support Document for this rulemaking.</P>
        </FTNT>
        <GPOTABLE CDEF="s40,14,14,14" COLS="4" OPTS="L2,i1">

          <TTITLE>Table 1—Design Values<SU>3</SU>by County for the 2006 24-Hour PM<E T="52">2.5</E>NAAQS for the NY-NJ-CT Monitors in Micrograms per Cubic Meter (μg/m<SU>3</SU>). The Standard for the 2006 24-Hour PM<E T="52">2.5</E>NAAQS Is 35.0 μg/m<SU>3</SU>
          </TTITLE>
          <BOXHD>
            <CHED H="1">County</CHED>
            <CHED H="1">2007-2009<LI>PM<E T="52">2.5</E>Design</LI>
              <LI>Values</LI>
            </CHED>
            <CHED H="1">2008-2010<LI>PM<E T="52">2.5</E>Design</LI>
              <LI>Values</LI>
            </CHED>
            <CHED H="1">2009-2011<LI>PM<E T="52">2.5</E>Design</LI>
              <LI>Values</LI>
            </CHED>
          </BOXHD>
          <ROW EXPSTB="03" RUL="s">
            <ENT I="21">
              <E T="02">New York</E>
            </ENT>
          </ROW>
          <ROW EXPSTB="00">
            <ENT I="01">Bronx</ENT>
            <ENT>33</ENT>
            <ENT>29</ENT>
            <ENT>28</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Kings</ENT>
            <ENT>30</ENT>
            <ENT>27</ENT>
            <ENT>25</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Nassau<SU>4</SU>
            </ENT>
            <ENT>INC</ENT>
            <ENT>25</ENT>
            <ENT>23</ENT>
          </ROW>
          <ROW>
            <ENT I="01">New York<SU>5</SU>
            </ENT>
            <ENT>
              <SU>6</SU>33</ENT>
            <ENT>
              <SU>6</SU>31</ENT>
            <ENT>28</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Orange</ENT>
            <ENT>26</ENT>
            <ENT>24</ENT>
            <ENT>23</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Queens</ENT>
            <ENT>30</ENT>
            <ENT>28</ENT>
            <ENT>26</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Richmond</ENT>
            <ENT>29</ENT>
            <ENT>26</ENT>
            <ENT>24</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Rockland</ENT>
            <ENT>NM</ENT>
            <ENT>NM</ENT>
            <ENT>NM</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Suffolk</ENT>
            <ENT>26</ENT>
            <ENT>25</ENT>
            <ENT>23</ENT>
          </ROW>
          <ROW RUL="s">
            <ENT I="01">Westchester</ENT>
            <ENT>29</ENT>
            <ENT>28</ENT>
            <ENT>25</ENT>
          </ROW>
          <ROW EXPSTB="03" RUL="s">
            <ENT I="21">
              <E T="02">NJ</E>
            </ENT>
          </ROW>
          <ROW EXPSTB="00">
            <ENT I="01">Bergen</ENT>
            <ENT>31</ENT>
            <ENT>28</ENT>
            <ENT>25</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Essex<SU>7</SU>
            </ENT>
            <ENT>
              <SU>6</SU>30</ENT>
            <ENT>
              <SU>6</SU>26</ENT>
            <ENT>INC</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Hudson</ENT>
            <ENT>32</ENT>
            <ENT>29</ENT>
            <ENT>28</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Mercer</ENT>
            <ENT>29</ENT>
            <ENT>27</ENT>
            <ENT>26</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Middlesex</ENT>
            <ENT>27</ENT>
            <ENT>23</ENT>
            <ENT>20</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Monmouth</ENT>
            <ENT>NM</ENT>
            <ENT>NM</ENT>
            <ENT>NM</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Morris</ENT>
            <ENT>26</ENT>
            <ENT>23</ENT>
            <ENT>23</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Passaic</ENT>
            <ENT>30</ENT>
            <ENT>INC</ENT>
            <ENT>25</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Somerset</ENT>
            <ENT>NM</ENT>
            <ENT>NM</ENT>
            <ENT>NM</ENT>
          </ROW>
          <ROW RUL="s">
            <ENT I="01">Union</ENT>
            <ENT>
              <SU>6</SU>32</ENT>
            <ENT>30</ENT>
            <ENT>30</ENT>
          </ROW>
          <ROW EXPSTB="03" RUL="s">
            <ENT I="21">
              <E T="02">Connecticut</E>
            </ENT>
          </ROW>
          <ROW EXPSTB="00">
            <ENT I="01">Fairfield</ENT>
            <ENT>31</ENT>
            <ENT>28</ENT>
            <ENT>26</ENT>
          </ROW>
          <ROW>
            <ENT I="01">New Haven</ENT>
            <ENT>31</ENT>
            <ENT>29</ENT>
            <ENT>28</ENT>
          </ROW>
          <TNOTE>NM—No monitor located in county.</TNOTE>
          <TNOTE>INC—Counties listed as INC did not meet 75 percent data completeness requirement for the relevant time period.</TNOTE>
        </GPOTABLE>
        <PRTPAGE P="76870"/>
        <HD SOURCE="HD1">IV. What is the effect of this action?</HD>

        <P>This final action, in accordance with the Clean Data Policy, which is reflected in 40 CFR 51.1004(c), suspends the requirements for the States of Connecticut, New Jersey, and New York, to submit an attainment demonstration, associated reasonably available control measures, RFP, contingency measures, and other planning SIPs related to attainment of the 2006 24-hour PM<E T="52">2.5</E>NAAQS for the NY-NJ-CT PM<E T="52">2.5</E>nonattainment area for so long as the area continues to attain the 2006 PM<E T="52">2.5</E>NAAQS.</P>

        <P>This action does not constitute a redesignation to attainment under section 107(d)(3) of the CAA, because the area does not have an approved maintenance plan as required under section 175A of the CAA. Nor is it a determination that the area has met the other requirements for redesignation. The designation status of the area remains nonattainment for the 2006 24-hour PM<E T="52">2.5</E>NAAQS until such time as EPA determines that the area, and/or a State portion thereof, meets the CAA requirements for redesignation to attainment.</P>
        <HD SOURCE="HD1">V. What is EPA's final action?</HD>
        <P>EPA is determining that the NY-NJ-CT PM<E T="52">2.5</E>nonattainment area for the 2006 24-hour PM<E T="52">2.5</E>NAAQS has attained the 2006 24-hour PM<E T="52">2.5</E>NAAQS. This determination is based upon quality-assured, quality-controlled, and certified ambient air monitoring data that show that the area has monitored attainment of the 2006 24-hour PM<E T="52">2.5</E>NAAQS for the 2007-2009 and 2008-2010 and 2009-2011 monitoring periods. Preliminary air monitoring data available for 2012 are consistent with the determination that the NY-NJ-CT PM<E T="52">2.5</E>nonattainment area is continuing to meet the 2006 24-hour PM<E T="52">2.5</E>NAAQS. This final action, in accordance with the Clean Data Policy, suspends the requirements for the States of New York, New Jersey and Connecticut to submit, for the NY-NJ-CT PM<E T="52">2.5</E>nonattainment area, an attainment demonstration, associated reasonably available control measures, RFP, contingency measures, and other planning SIPs related to attainment of the 2006 24-hour PM<E T="52">2.5</E>NAAQS in the area for so long as the area continues to attain the 2006 24-hour PM<E T="52">2.5</E>NAAQS. If EPA subsequently determines, after notice-and-comment rulemaking in the<E T="04">Federal Register</E>, that the NY-NJ-CT PM<E T="52">2.5</E>nonattainment area has violated the 2006 24-hour PM<E T="52">2.5</E>NAAQS, the basis for the suspension of the specific requirements would no longer exist for the area, and the affected States would thereafter have to address the applicable requirements for the 2006 24-hour PM<E T="52">2.5</E>NAAQS.</P>

        <P>In accordance with 5 U.S.C. 553(d), EPA finds there is good cause for this action to become effective immediately upon publication. A delayed effective date is unnecessary due to the nature of a determination of attainment, which suspends the obligation to submit certain attainment-related CAA planning requirements that would otherwise apply. The immediate effective date for this action is authorized under both 5 U.S.C. 553(d)(1), which provides that rulemaking actions may become effective less than 30 days after publication if the rule “grants or recognizes an exemption or relieves a restriction,” and section 553(d)(3), which allows an effective date less than 30 days after publication “as otherwise provided by the agency for good cause found and published with the rule.” The purpose of the 30-day waiting period prescribed in section 553(d) is to give affected parties a reasonable time to adjust their behavior and prepare before the final rule takes effect. Today's rule, however, does not create any new regulatory requirements such that affected parties would need time to prepare before the rule takes effect. Rather, today's rule relieves the affected States of the obligation to submit certain attainment-related planning requirements for this PM<E T="52">2.5</E>nonattainment area. For these reasons, EPA finds good cause under 5 U.S.C. 553(d)(3) for this action to become effective on the date of publication of this notice.</P>
        <HD SOURCE="HD1">VI. Statutory and Executive Order Reviews</HD>
        <P>This action makes an attainment determination based on air quality and results in the suspension of certain Federal requirements, and it does not impose additional requirements beyond those imposed by state law.</P>
        <P>For these reasons, this action:</P>
        <P>• Is not a “significant regulatory action” subject to review by the Office of Management and Budget under Executive Order 12866 (58 FR 51735, October 4, 1993);</P>

        <P>• Does not impose an information collection burden under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501<E T="03">et seq.</E>);</P>

        <P>• Is certified as not having a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601<E T="03">et seq.</E>);</P>
        <P>• Does not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4);</P>
        <P>• Does not have Federalism implications as specified in Executive Order 13132 (64 FR 43255, August 10, 1999);</P>
        <P>• Is not an economically significant regulatory action based on health or safety risks subject to Executive Order 13045 (62 FR 19885, April 23, 1997);</P>
        <P>• Is not a significant regulatory action subject to Executive Order 13211 (66 FR 28355, May 22, 2001);</P>
        <P>• Is not subject to requirements of Section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) because application of those requirements would be inconsistent with the CAA; and</P>
        <P>• Does not provide EPA with the discretionary authority to address, as appropriate, disproportionate human health or environmental effects, using practicable and legally permissible methods, under Executive Order 12898 (59 FR 7629, February 16, 1994).</P>
        <P>In addition, this rule does not have tribal implications as specified by Executive Order 13175 (65 FR 67249, November 9, 2000), because the SIP is not approved to apply in Indian country located in the state, and EPA notes that it will not impose substantial direct costs on tribal governments or preempt tribal law.</P>
        <P>The Congressional Review Act, 5 U.S.C. 801<E T="03">et seq.,</E>as added by the Small Business Regulatory Enforcement Fairness Act of 1996, generally provides that before a rule may take effect, the agency promulgating the rule must submit a rule report, which includes a copy of the rule, to each House of the Congress and to the Comptroller General of the United States. EPA will submit a report containing this action and other required information to the U.S. Senate, the U.S. House of Representatives, and the Comptroller General of the United States prior to publication of the rule in the<E T="04">Federal Register</E>. A major rule cannot take effect until 60 days after it is published in the<E T="04">Federal Register</E>. This action is not a “major rule” as defined by 5 U.S.C. 804(2).</P>

        <P>Under section 307(b)(1) of the Clean Air Act, petitions for judicial review of this action must be filed in the United States Court of Appeals for the appropriate circuit by March 1, 2013. Filing a petition for reconsideration by the Administrator of this final rule does not affect the finality of this action for the purposes of judicial review nor does it extend the time within which a petition for judicial review may be filed,<PRTPAGE P="76871"/>and shall not postpone the effectiveness of such rule or action.</P>
        <P>This action may not be challenged later in proceedings to enforce its requirements. (See section 307(b)(2).)</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 40 CFR Part 52</HD>
          <P>Environmental protection, Air pollution control, Incorporation by reference, Particulate matter.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: November 28, 2012.</DATED>
          <NAME>Judith A. Enck,</NAME>
          <TITLE>Regional Administrator, Region II.</TITLE>
          
          <DATED>Dated: December 11, 2012.</DATED>
          <NAME>H. Curtis Spalding,</NAME>
          <TITLE>Regional Administrator, Region I.</TITLE>
          
        </SIG>
        <P>Part 52, chapter I, title 40 of the Code of Federal Regulations is amended as follows:</P>
        <REGTEXT PART="52" TITLE="40">
          <PART>
            <HD SOURCE="HED">PART 52—APPROVAL AND PROMULGATION OF IMPLEMENTATION PLANS</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 52 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 7401 et seq.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">
          <SUBPART>
            <HD SOURCE="HED">Subpart H—Connecticut</HD>
          </SUBPART>
          <AMDPAR>2. Section 52.379 is amended by adding paragraph (g) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 52.379</SECTNO>
            <SUBJECT>Control strategy: PM<E T="52">2.5</E>.</SUBJECT>
            <STARS/>
            <P>(g)<E T="03">Determination of Attainment.</E>EPA has determined, as of December 31, 2012, that the New York-N. New Jersey-Long Island, NY-NJ-CT fine particle (PM<E T="52">2.5</E>) nonattainment area has attained the 2006 PM<E T="52">2.5</E>National Ambient Air Quality Standard. This determination suspends the requirements for this area to submit an attainment demonstration, associated reasonably available control measures, a reasonable further progress plan, contingency measures, and other planning SIPs related to attainment of the standard for as long as the area continues to attain the 2006 PM<E T="52">2.5</E>NAAQS.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">
          <SUBPART>
            <HD SOURCE="HED">Subpart FF—New Jersey</HD>
          </SUBPART>
          <AMDPAR>3. Section 52.1602 is amended by adding paragraph (e) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 52.1602</SECTNO>
            <SUBJECT>Control strategy and regulations: PM<E T="52">2.5</E>.</SUBJECT>
            <STARS/>
            <P>(e)<E T="03">Determination of Attainment.</E>EPA has determined, as of December 31, 2012, that the New York-N. New Jersey-Long Island, NY-NJ-CT fine particle (PM<E T="52">2.5</E>) nonattainment area has attained the 2006 PM<E T="52">2.5</E>National Ambient Air Quality Standard. This determination suspends the requirements for this area to submit an attainment demonstration, associated reasonably available control measures, a reasonable further progress plan, contingency measures, and other planning SIPs related to attainment of the standard for as long as the area continues to attain the 2006 PM<E T="52">2.5</E>NAAQS.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">
          <SUBPART>
            <HD SOURCE="HED">Subpart HH—New York</HD>
          </SUBPART>
          <AMDPAR>4. Section 52.1678 is amended by adding paragraph (f) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 52.1678</SECTNO>
            <SUBJECT>Control strategy and regulations: Particulate matter.</SUBJECT>
            <STARS/>
          </SECTION>
          <AMDPAR>(f)<E T="03">Determination of Attainment.</E>EPA has determined, as of December 31, 2012, that the New York-N. New Jersey-Long Island, NY-NJ-CT fine particle (PM<E T="52">2.5</E>) nonattainment area has attained the 2006 PM<E T="52">2.5</E>National Ambient Air Quality Standard. This determination suspends the requirements for this area to submit an attainment demonstration, associated reasonably control available measures, a reasonable further progress plan, contingency measures, and other planning SIPs related to attainment of the standard for as long as the area continues to attain the 2006 PM<E T="52">2.5</E>NAAQS.</AMDPAR>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31214 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <CFR>40 CFR Part 52</CFR>
        <DEPDOC>[EPA-R08-OAR-2011-0770, FRL-9734-8]</DEPDOC>
        <SUBJECT>Approval and Promulgation of Implementation Plans; State of Colorado; Regional Haze State Implementation Plan</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>EPA is approving a State Implementation Plan (SIP) revision submitted by the State of Colorado on May 25, 2011 that addresses regional haze. Colorado submitted this SIP revision to meet the requirements of the Clean Air Act (CAA or “the Act”) and our rules that require states to prevent any future and remedy any existing man-made impairment of visibility in mandatory Class I areas caused by emissions of air pollutants from numerous sources located over a wide geographic area (also referred to as the “regional haze program”). EPA is taking this action pursuant to section 110 of the CAA.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This final rule is effective January 30, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>EPA has established a docket for this action under Docket ID No. EPA-R08-OAR-2011-0770. All documents in the docket are listed on the<E T="03">www.regulations.gov</E>Web site.</P>

          <P>Publicly available docket materials are available either electronically through<E T="03">www.regulations.gov</E>, or in hard copy at the Air Program, Environmental Protection Agency (EPA), Region 8, 1595 Wynkoop Street, Denver, Colorado 80202-1129. EPA requests that if, at all possible, you contact the individual listed in the<E T="02">FOR FURTHER INFORMATION CONTACT</E>section to view the hard copy of the docket. You may view the hard copy of the docket Monday through Friday, 8 a.m. to 4 p.m., excluding Federal holidays.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Laurel Dygowski, Air Program, Mailcode 8P-AR, Environmental Protection Agency, Region 8, 1595 Wynkoop Street, Denver, Colorado 80202-1129, (303) 312-6144,<E T="03">dygowski.laurel@epa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Table of Contents</HD>
        
        <EXTRACT>
          <FP SOURCE="FP-2">I. Background</FP>
          <FP SOURCE="FP1-2">A. Regional Haze</FP>
          <FP SOURCE="FP1-2">B. Lawsuits</FP>
          <FP SOURCE="FP1-2">C. Our Proposal</FP>
          <FP SOURCE="FP1-2">D. Public Participation</FP>
          <FP SOURCE="FP-2">II. Final Action</FP>
          <FP SOURCE="FP-2">III. Basis for Our Final Action</FP>
          <FP SOURCE="FP-2">IV. Issues Raised by Commenters and EPA's Response</FP>
          <FP SOURCE="FP1-2">A. NO<E T="52">X</E>BART for Tri-State Craig Unit 1 and Unit 2</FP>
          <FP SOURCE="FP1-2">B. NO<E T="52">X</E>BART Determination for Martin Drake Units 5, 6, and 7</FP>
          <FP SOURCE="FP1-2">C. BART Determination for Colorado Energy Nations (CENC) Unit 4 and Unit 5</FP>
          <FP SOURCE="FP1-2">D. NO<E T="52">X</E>BART Determination for Cemex Lyons Kiln</FP>
          <FP SOURCE="FP1-2">E. NO<E T="52">X</E>BART Determination for Comanche Unit 1 and Unit 2</FP>
          <FP SOURCE="FP1-2">F. NO<E T="52">X</E>Reasonable Progress Determination for Craig Unit 3</FP>
          <FP SOURCE="FP1-2">G. NO<E T="52">X</E>Reasonable Progress Determination for Nucla</FP>
          <FP SOURCE="FP1-2">H. Reasonable Progress for Rio Grande Cement Company (GCC)</FP>
          <FP SOURCE="FP1-2">I. Legal Issues</FP>
          <FP SOURCE="FP1-2">1. Public Service Company of Colorado (PSCO) BART Alternative</FP>
          <FP SOURCE="FP1-2">2. Timing of Implementation</FP>
          <FP SOURCE="FP1-2">3. Compliance With Section 110(l)</FP>
          <FP SOURCE="FP1-2">J. Comments Generally in Favor of Our Proposal</FP>
          <FP SOURCE="FP-2">V. Statutory and Executive Order Reviews</FP>
        </EXTRACT>
        
        <HD SOURCE="HD1">Definitions</HD>
        <P>For the purpose of this document, we are giving meaning to certain words or initials as follows:</P>
        
        <EXTRACT>
          <P>i. The words or initials<E T="03">Act</E>or<E T="03">CAA</E>mean or refer to the Clean Air Act, unless the context indicates otherwise.<PRTPAGE P="76872"/>
          </P>
          <P>ii. The initials<E T="03">APEN</E>mean or refer to Air Pollution Emissions Notice.</P>
          <P>iii. The initials<E T="03">AQCC</E>mean or refer to the Air Quality Control Commission.</P>
          <P>iv. The initials<E T="03">BACT</E>mean or refer to Best Available Control Technology.</P>
          <P>v. The initials<E T="03">BART</E>mean or refer to Best Available Retrofit Technology.</P>
          <P>vi. The initials<E T="03">CMA</E>mean or refer to the Colorado Mining Association.</P>
          <P>vii. The words<E T="03">Colorado</E>and<E T="03">the State</E>mean the State of Colorado.</P>
          <P>viii. The initials<E T="03">EGUs</E>mean or refer to Electric Generating Units.</P>
          <P>ix. The words<E T="03">EPA, we,</E>
            <E T="03">us, our,</E>or<E T="03">the Agency</E>mean or refer to the United States Environmental Protection Agency.</P>
          <P>x. The initials<E T="03">LNB</E>mean or refer to low NO<E T="52">X</E>burner.</P>
          <P>xi. The initials<E T="03">NAAQS</E>mean or refer to the National Ambient Air Quality Standards.</P>
          <P>xii. The initials<E T="03">NO</E>
            <E T="52">X</E>mean or refer to nitrogen oxides.</P>
          <P>xiii. The initials<E T="03">NPS</E>mean or refer to National Park Service.</P>
          <P>xiv. The initials<E T="03">PM</E>
            <E T="52">2.5</E>mean or refer to particulate matter with an aerodynamic diameter of less than 2.5 micrometers.</P>
          <P>xv. The initials<E T="03">SCR</E>mean or refer to selective catalytic reduction.</P>
          <P>xvi. The initials<E T="03">SIP</E>mean or refer to State Implementation Plan.</P>
          <P>xvii. The initials<E T="03">SNCR</E>mean or refer to selective non-catalytic reduction.</P>
          <P>xviii. The initials<E T="03">SO</E>
            <E T="52">2</E>mean or refer to sulfur dioxide.</P>
          <P>xix. The initials<E T="03">TSD</E>mean or refer to Technical Support Document.</P>
        </EXTRACT>
        <HD SOURCE="HD1">I. Background</HD>
        <P>The CAA requires each state to develop plans, referred to as SIPs, to meet various air quality requirements. A state must submit its SIPs and SIP revisions to us for approval. Once approved, a SIP is enforceable by EPA and citizens under the CAA, also known as being federally enforceable. This action addresses the requirement that states have SIPs that address regional haze.</P>
        <HD SOURCE="HD2">A. Regional Haze</HD>
        <P>In 1990, Congress added section 169B to the CAA to address regional haze issues, and we promulgated regulations addressing regional haze in 1999 (64 FR 35714, July 1, 1999, codified at 40 CFR part 51, subpart P). The requirements for regional haze, found at 40 CFR 51.308 and 51.309, are included in our visibility protection regulations at 40 CFR 51.300-309. The requirement to submit a regional haze SIP applies to all 50 states, the District of Columbia and the Virgin Islands. States were required to submit a SIP addressing regional haze visibility impairment no later than December 17, 2007 (40 CFR 51.308(b)).</P>
        <P>Few states submitted a regional haze SIP prior to the December 17, 2007, deadline, and on January 15, 2009, EPA found that 37 states, including Colorado, the District of Columbia, and the Virgin Islands, had failed to submit SIPs addressing the regional haze requirements (74 FR 2392). Once EPA has found that a state has failed to make a required submission, EPA is required to promulgate a Federal Implementation Plan (FIP) within 2 years unless the state submits a SIP and the Agency approves it within the 2-year period. CAA section 110(c)(1).</P>
        <P>Colorado submitted a SIP addressing regional haze on May 25, 2011.</P>
        <HD SOURCE="HD2">B. Lawsuits</HD>
        <P>In a lawsuit in the U.S. District Court for the District of Colorado, environmental groups sued us for our failure to take timely action with respect to the regional haze requirements of the CAA and our regulations. In particular, the lawsuits alleged that we had failed to promulgate FIPs for these requirements within the 2-year period allowed by CAA section 110(c) or, in the alternative, fully approve SIPs addressing these requirements.</P>
        <P>As a result of these lawsuits, we entered into a consent decree. The consent decree requires that we sign a notice of final rulemaking addressing the regional haze requirements for Colorado by September 10, 2012. We are meeting that requirement with the signing of this notice of final rulemaking.</P>
        <HD SOURCE="HD2">C. Our Proposal</HD>

        <P>We signed our notice of proposed rulemaking on March 15, 2012, and it was published in the<E T="04">Federal Register</E>on March 26, 2012 (77 FR 18052). In that notice, we provided a detailed description of the various regional haze requirements. We are not repeating that description here; instead, the reader should refer to our notice of proposed rulemaking for further detail.<SU>1</SU>
          <FTREF/>In our proposal, we proposed to approve Colorado's May 25, 2011, regional haze SIP.</P>
        <FTNT>
          <P>
            <SU>1</SU>We note that our proposed rule contained certain errors, as follows: (1) In Table 2, at 77 FR 18060, “Tri-State Generation and Transmission, Inc.” should have read “Tri-State Generation and Transmission Association, Inc.;” (2) In Table 13, at 77 FR 18068, the visibility improvement for SCR for Craig Unit 2 should have read 0.98 deciviews instead of 1.01 deciviews; and (3) In Table 38, at 77 FR 18085, the annualized costs for the limestone injection improvements (LII) option should have read $2,188,595 instead of $914,290. None of these errors impact our analysis or decision. In particular, the cost effectiveness value for the LII option in Table 38 already accounted for the correct annualized cost value.</P>
        </FTNT>
        <HD SOURCE="HD2">D. Public Participation</HD>
        <P>We requested comments on all aspects of our proposed action and provided a 60-day comment period, with the comment period closing on May 25, 2012. We received comments on our proposed rule that generally supported our proposed action and comments that were critical of certain aspects of our proposed action. In this action, we are responding to the comments we have received, taking final rulemaking action, and explaining the bases for our action.</P>
        <HD SOURCE="HD1">II. Final Action</HD>
        <P>With this action, EPA is approving a SIP revision submitted by the State of Colorado on May 25, 2011, that addresses regional haze. We are approving the State's regional haze SIP, including revisions submitted as part of the regional haze SIP to:</P>
        <P>• Regulation No. 3, Part F, Section VI and Section VII.</P>
        <P>• Regulation No. 3, Part D, Section XIV.F.</P>
        <P>• Regulation No. 7, Section XVII.E.3.a.</P>
        <HD SOURCE="HD1">III. Basis for Our Final Action</HD>
        <P>We have fully considered all significant comments on our proposal and have concluded that no changes from our proposal are warranted. Our action is based on an evaluation of Colorado's regional haze SIP submittal against the regional haze requirements at 40 CFR 51.300-51.309 and CAA sections 169A and 169B. All general SIP requirements contained in CAA section 110, other provisions of the CAA, and our regulations applicable to this action were also evaluated. The purpose of this action is to ensure compliance with these requirements. Our authority for action on Colorado's SIP submittal is based on CAA section 110(k).</P>
        <P>We are approving the State's regional haze SIP provisions because they meet the relevant regional haze requirements. Most of the adverse comments we received concerning our proposed approval of the regional haze SIP pertained to the State's best available retrofit technology (BART) and reasonable progress determinations. With respect to the BART determinations, we understand that there is room for disagreement about certain aspects of the State's analyses. Furthermore, we may have reached different conclusions had we been performing the determinations in the first instance. However, the comments have not convinced us that the State, conducting specific case-by-case analyses for the relevant units, acted unreasonably or that we should disapprove the State's BART determinations.</P>

        <P>With respect to the State's reasonable progress determinations, the State<PRTPAGE P="76873"/>included emission limits in the SIP that reflect reasonable levels of control for reasonable progress for this initial planning period. Here again, we understand that there is room for disagreement about the State's analyses and appropriate limits. And, again, we may have reached different conclusions had we been performing the determinations. However, the comments have not convinced us that the State, conducting specific case-by-case analyses for the relevant units, made unreasonable determinations for this initial planning period or that we should disapprove the State's SIP.</P>
        <HD SOURCE="HD1">IV. Issues Raised by Commenters and EPA's Response</HD>
        <HD SOURCE="HD2">A. NO<E T="52">X</E>BART for Tri-State Craig Unit 1 and Unit 2</HD>
        <P>
          <E T="03">Comment:</E>We received comments that the State and EPA did not follow the BART guidelines or otherwise meet the intent of the BART requirements because the State and we did not evaluate the most stringent control efficiencies associated with operating selective catalytic reduction (SCR). The commenters pointed out that State and EPA evaluations assumed that SCR is capable of achieving 0.07 lb/MMBtu on an annual average and 0.07-0.08 lb/MMBtu on a 30-day rolling average. Commenters stated that this level reflects 74-75% reduction from baseline emissions from these units, and SCR is well known to be capable of control efficiencies greater than 90% and limits of 0.05 lb/MMBtu or less on a 30-day rolling average. One commenter pointed out that in a November 2010 report, Tri-State's own consultants evaluated a 0.05 lb/MMBtu design emission rate for SCR. One commenter also pointed out that previous statements by EPA and the National Park Service (NPS) to the State about the Colorado regional haze plan reflect this.<E T="51">2 3</E>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>2</SU>Letter from Callie A. Videtich, Director, Air Program, EPA Region 8, to Paul Tourangeau, Air Director, Colorado Department of Public Health and the Environment, October 26, 2010, Re: Regional Haze State Implementation Plan. (October 26, 2010 letter).</P>
          <P>
            <SU>3</SU>NPS Comments on Best Available Retrofit Technology (BART) Analysis of Control Options for Tri-State Generation &amp; Transmission Association, Inc.—Craig Station Units 1 &amp; 2, December 1, 2010.</P>
        </FTNT>

        <P>One commenter went on to say that if an emission rate of 0.05 lb/MMBtu had been used to assess the cost of SCR, the State would have found the cost to be $5,879 per ton of NO<E T="52">X</E>reduced for Unit 1 and $5,728 per ton of NO<E T="52">X</E>reduced for Unit 2. Commenters provided numerous examples of electric generating units (EGUs) that are achieving or will be required to achieve a NO<E T="52">X</E>emission rate of 0.05 lb/MMBtu or less on an annual and 30-day rolling average.</P>
        <P>
          <E T="03">Response:</E>We agree that SCR in some cases can achieve annual NO<E T="52">X</E>emission rates as low as 0.05 lb/MMBtu. However, the annual emission rate assumed by Colorado, 0.07 lb/MMBtu, is within the range of actual emission rates demonstrated at similar facilities in EPA's Clean Air Markets Division (CAMD) emission database.</P>
        <P>
          <E T="03">Comment:</E>The proposed emission limit of 0.27 lb/MMBtu for selective non-catalytic reduction (SNCR) does not reflect what is achievable for that control technology. The State's technical support document (TSD) shows that Craig Unit 1 is already meeting an emission rate of 0.27 lb/MMBtu, even without SNCR. Furthermore, as noted by EPA in its October 26, 2010, letter, SNCR is capable of achieving emission reductions of 20-30% below baseline. This would mean that SNCR would actually be capable of achieving an emission rate of around 0.20 lb/MMBtu or lower at Units 1 and 2, not 0.27 lb/MMBtu.</P>
        <P>
          <E T="03">Response:</E>We disagree that the State's TSD shows that Craig 1 is already achieving a 30-day rolling average emission rate of 0.27 lb/MMBtu, even without SNCR. The commenter has confused actual average annual emission rates that Colorado used for cost calculations with 30-day rolling average emission rates. Colorado's TSD shows that the maximum actual 30-day rolling average emission rate during this period was 0.304 lb/MMBtu. Therefore, Craig 1 is currently operating above, not below, the BART emission limit. However, we understand that the commenter's larger point is that the emission limit for Craig Unit 1 does not reflect the level of control that can be achieved with SNCR.</P>
        <P>As noted by the commenter, SNCR can typically achieve a 20-30% reduction after combustion controls. By contrast, Colorado assumed that at Craig SNCR could achieve a 15% reduction after combustion controls. This in turn was based on Tri-State's assertion that the Craig BART units can only meet this level of control since the effectiveness of SNCR is lower for wall-fired boilers similar to those at Craig. Under the circumstances, we do not find that the State's conclusion was unreasonable.</P>
        <P>
          <E T="03">Comment:</E>EPA provided no insight as to what it considers presumptive BART to be for Craig Units 1 and 2. Presumptive BART for the Craig units should be based on the primary type of coal burned there, which is sub-bituminous. EPA should establish the presumptive BART limit for Craig at 0.23 lb/MMBtu. On this basis, the limits proposed by EPA exceed presumptive BART.</P>
        <P>
          <E T="03">Response:</E>The presumptive limits for EGUs, which are reflective of combustion controls for all but cyclone boilers, are clearly stated in the BART guidelines. The presumptive limit for dry-bottom wall-fired EGUs firing sub-bituminous coal, such as the Craig BART units, is 0.23 lb/MMBtu (70 FR 39172, July 6, 2005).</P>

        <P>Colorado has stated that the Craig BART units fire sub-bituminous coal that is “bituminous-like” with respect to NO<E T="52">X</E>formation.<SU>4</SU>
          <FTREF/>That is, they exhibit relatively higher NO<E T="52">X</E>emissions. This is supported by actual emissions data, which show that the units fail to achieve the presumptive limit with the existing ultra low-NO<E T="52">X</E>burners and overfire air, the same combustion controls that EPA assumed for sources when it established the presumptive limit. The State's analysis of CEMs data in EPA's CAMD emissions database shows an actual maximum 30-day rolling average emission rate of 0.304 lb/MMBtu at each unit (2006-2008). Thus, we conclude that the presumptive limit that applies to Craig—0.23 lb/MMBtu—does not provide a meaningful benchmark for evaluating the State selected limits at Craig. Furthermore, our BART guidelines are clear that the BART analysis may result in a limit that differs from the presumptive limit.</P>
        <FTNT>
          <P>
            <SU>4</SU>The presumptive limit for dry-bottom wall-fired EGUs firing bituminous coal is 0.39 lb/MMBtu (70 FR 39172).</P>
        </FTNT>
        <P>
          <E T="03">Comment:</E>One of the options suggested by the BART Guidelines to evaluate cost effectiveness is cost/deciview. Applying the cost/deciview metric to SCR at Craig yields about $10 million/deciview for Mt. Zirkel and $2.6 million/deciview on a cumulative basis. Both values are reasonable when compared to the national average of $14-$18 million/deciview.</P>
        <P>
          <E T="03">Response:</E>The BART Guidelines require that cost effectiveness be calculated in terms of annualized dollars per ton of pollutant removed, or $/ton (70 FR 39167). The commenters are correct in that the BART Guidelines list the $/deciview ratio as an additional cost effectiveness metric that can be employed along with $/ton for use in a BART evaluation. However, the State was not required to use this metric. We do not generally recommend the use of this metric as it can be complicated to use and the results can be difficult to assess. We also note that the $/deciview metric has not been widely used as a comparative tool. It is sufficient to analyze the cost effectiveness of<PRTPAGE P="76874"/>potential BART controls using $/ton, in conjunction with an assessment of the modeled visibility benefits of the BART control.</P>
        <P>
          <E T="03">Comment:</E>Because the control efficiency for SCR was underestimated, the visibility benefits from SCR are underestimated by the modeling.</P>
        <P>
          <E T="03">Response:</E>We disagree with this comment. As stated above, while we recognize that lower annual emission rates for SCR have been demonstrated at some facilities, the annual emission rate of 0.07 lb/MMBtu assumed by Colorado in estimating the costs and benefits of SCR is within the overall range for similar facilities in EPA's CAMD emission database. Given this, we find that it was not unreasonable for Colorado to use 0.07 lb/MMBtu to model the predicted visibility improvement from SCR.</P>
        <P>
          <E T="03">Other Comments:</E>A number of commenters objected to our proposed approval of the State's BART determination for Craig Unit 1 on other grounds and asserted that the State should have selected SCR as BART. These commenters articulated several bases for their comments. The comments fall into four main categories, as follows:</P>
        <HD SOURCE="HD3">(1) Costs</HD>
        <P>We received numerous comments that the State, relying on Tri-State's cost analysis, significantly overestimated capital costs for SCR at Craig Unit 1 and Unit 2, and that EPA did not conduct a detailed review of Tri-State's cost analysis. Commenters cited numerous sources to show that the expected capital costs for SCR at Unit 1 and Unit 2 should be lower than what Tri-State assumed in its cost estimates. Commenters noted limited or missing information, such as lack of vendor quotes or detailed cost estimates. According to a commenter, this type of information is necessary for the public or other agencies to be able to thoroughly review and comment on the proposed determinations. According to commenters, the absence of this underlying information renders EPA's proposed approval of the BART determinations for these sources arbitrary. Commenters said that, to the extent that the State or EPA relied on such information, failure to include it in the docket further illegally impaired and deprived the public of its notice and comment rights, by concealing important grounds for the proposed action and preventing the public from examining and offering meaningful comment thereon.</P>
        <P>Commenters noted several items in Tri-State's and the State's cost analyses that are not allowed by or are inconsistent with EPA's Control Cost Manual (CCM). According to commenters, Tri-State and the State: (1) Disregarded EPA's cost method, often referred to as the “overnight cost method;”<SU>5</SU>
          <FTREF/>(2) included Allowance for Funds During Construction (AFUDC);<SU>6</SU>
          <FTREF/>(3) used escalation, which is inappropriate and generally not allowed; (4) included lost generation costs with no support or justification for the costs, the duration of outages needed, and why time beyond normal scheduled outages would be necessary; (5) provided no justification for the inclusion of owner's costs as 10% of the direct cost; (6) included a 50-hour workweek in their cost estimate without any justification; (6) included no consideration of the cost savings when controls like SCR are applied to multiple units at the same facility; and (7) used an unrealistic equipment life and interest rate.</P>
        <FTNT>
          <P>
            <SU>5</SU>The overnight cost method represents the cost of building the plant as if all the supplies could be purchased and all the labor paid within a very short period of time. In contrast, when forecasting revenue requirements for environmental retrofits, utilities typically attempt to estimate the costs that would actually be reflected in their future rate cases as a result of the retrofits in what is known as the “all in” method. According to commenters, the results from these two cost calculating methods cannot and should not be compared. Commenters also asserted the following: (1) Relative to the EPA CCM, the utility method typically overstates the cost of control per ton of avoided emissions by about 36%; and (2) National consistency in cost allocation method is necessary to ensure that no company or state receives an economic advantage by using a different cost method.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>6</SU>According to commenters, this cost is not allowed because Tri-State is not a rate-regulated utility and the AFUDC cost is not already included in the base case, as per a utility commission decision.</P>
        </FTNT>
        <P>Commenters provided revised cost analyses for SCR at Craig Units 1 and 2. One commenter calculated that a more accurate cost effectiveness value would be no higher than $3,460/ton and $3,370/ton at Unit 1 and Unit 2, respectively. Another commenter calculated that average costs would be $2,209/ton for Unit 1 and $1,962/ton for Unit 2. Commenters pointed out that these costs were below the threshold established by the State for choosing SCR.</P>
        <HD SOURCE="HD3">(2) Visibility Improvement</HD>
        <P>Commenters point out that EPA only provides the impacts to the most impacted Class I area, Mt. Zirkel, and that the cumulative impact of a source's emissions on visibility, as well as the cumulative benefit of emission reductions, is a necessary consideration as part of the fifth step in the BART analysis. Commenters provided examples where other EPA regions (Region 6 and Region 9) have considered cumulative visibility benefits. The NPS performed modeling and submitted the results as part of its comments. NPS modeling shows that the cumulative visibility impact from Craig Units 1 and 2 is 17.61 deciviews, while SCR at both units would provide a cumulative visibility improvement of 8.99 deciviews. The modeling also shows that SCR at both units would achieve at least a 0.5 deciview improvement at each of five Class I areas.</P>
        <HD SOURCE="HD3">(3) Determination of BART</HD>

        <P>Commenters identified numerous issues with the State's determination of BART and consideration of the five factors. First, commenters pointed out that the State relied on a predetermined set of thresholds applicable only to post-combustion NO<E T="52">X</E>controls for determining what is BART,<SU>7</SU>
          <FTREF/>and that the State attempted to justify this by a short discussion of its belief that “the costs of control should have a relationship to visibility improvement.” According to commenters, the State articulated no governing principle or rational explanation for how it considered the five factors within the context of this threshold.</P>
        <FTNT>
          <P>
            <SU>7</SU>For the highest-performing NO<E T="52">X</E>post-combustion control options (<E T="03">i.e.,</E>SCR systems for EGUs) that do not exceed $5,000/ton of pollutant reduced by the State's calculation, and which provide a modeled visibility benefit of 0.5 deciview or greater at the primary Class I Area affected, the State views that level of control as generally reasonable. For lesser-performing NO<E T="52">X</E>post-combustion control options (<E T="03">e.g.,</E>SNCR technologies for EGUs) that do not exceed $5,000/ton of pollutant reduced by the State's calculation, and which provide a modeled visibility benefit of 0.2 deciview or greater at the primary Class I Area affected, the State views that level of control as generally reasonable.</P>
        </FTNT>
        <P>Commenters asserted that EPA, in its October 26, 2010, comment letter to Colorado, anticipated some of the reasons the State's threshold is untenable. One commenter went on to say that in the unlikely scenario that the appropriate cost of SCR at Craig Units 1 and 2 is in fact above $5,000/ton, the State's criteria “preclude a reasonable weighing of the five factors,” as EPA had foretold. Commenters indicated that EPA relied on the State's vague and unsubstantiated criteria without resolving or even discussing its prior concerns.</P>

        <P>Commenters noted that the Craig analysis presented data for each of the five BART factors, but pointed out that when it came to the crux of the BART determination, the actual weighing of the factors, EPA's proposed rulemaking failed to explain how EPA determined<PRTPAGE P="76875"/>that costs were unjustified in light of anticipated visibility benefits and the other considerations. As such, commenters said that EPA had failed to require a reasoned basis for weighing the five factors in the Craig BART analysis and determination. One commenter went on to say that to comply with the Administrative Procedure Act, the Agency must provide a reasoned basis for its BART determination, including a reasonable explanation why certain benefits do not justify certain costs, why EPA's chosen methods for evaluating costs and benefits are appropriate, and what significance the Agency has accorded to each of the five BART factors. The commenter argued that EPA's failure to identify its method of decision making amounts to an arbitrary decision.</P>

        <P>One commenter stated that it was concerned that, although the State found SCR to be reasonable as BART for Craig Unit 2, it found the control technology to be unreasonable for Unit 1, even though according to the five factors, it would meet the same reasonability threshold as for Unit 2. Notably, the State found the cost of SCR for Unit 2, $5,728 per ton of NO<E T="52">X</E>reduced, to be reasonable as it was ultimately adopted as BART.</P>
        <HD SOURCE="HD3">(4) BART Alternative</HD>
        <P>Commenters pointed out that the Craig BART alternative fails to provide for greater reasonable progress than would be achieved if an adequate source-specific BART limit were required of both subject-to-BART Craig units. Commenters went on to say that BART should have been SCR on both Craig units and thus, the BART alternative of SNCR on Unit 1 and SCR on Unit 2 is not better than BART. According to commenters, given that 40 CFR 51.308(e)(2)(C) requires states to make a BART determination for any source subject to an alternative to BART, the State's flawed BART analysis fails to support an alternative to BART pursuant to EPA regulations.</P>
        <P>
          <E T="03">Response:</E>While we agree with some aspects of the commenters' assertions in these four categories, we disagree with others and ultimately conclude that Colorado's plan achieves a reasonable result overall. We acknowledged in our October 26, 2010, comment letter to the State that the cost analysis was not conducted by Colorado in accordance with EPA's Control Cost Manual, and we agreed that the costs for SCR at Craig Units 1 and 2 appeared to be substantially overestimated, which the commenters also pointed out. In addition, as we suggested during the State's public comment period, the State should have more thoroughly considered the visibility impacts of controlling emissions from Craig 1 on the various impacted Class I areas and not just have focused on the most impacted Class I area.</P>
        <P>EPA acknowledges that Colorado's approach appears to be a novel and comprehensive strategy for addressing regional haze requirements and other air quality goals. In 2010, the Colorado General Assembly adopted legislation authorizing the Air Quality Control Commission and the Public Utilities Commission to develop a comprehensive plan for coal-fired electric generating units in the state that would address not only regional haze but also potential new ozone standards and mercury standards, as well as other requirements that, in the State's view, could apply to coal-fired electric generation units in the foreseeable future. The State desired to address these issues in a coordinated way in order to achieve the most cost-effective strategy that accounted for not only current, but other imminent regulatory requirements. This approach appears to be unique and, as noted below, will yield significant emissions reductions not only of pollutants that affect visibility in Class I areas, but also significant reductions in pollutants that contribute to ozone formation, nitrogen deposition, and mercury emissions and deposition. The State spent considerable time and conducted sequential and extended hearings to develop a plan which seeks to balance a number of variables beyond those that would be involved in a simpler and narrower regional haze determination.</P>
        <P>Colorado's BART requirements for the Craig units reflect a balance struck by Tri-State Generation &amp; Transmission Association, Inc. and several environmental groups before the Colorado Air Quality Control Commission during an extensive and formal proceeding; at the conclusion of the proceeding, the Commission adopted the agreement reached by Tri-State and those environmental groups as part of Colorado's regional haze plan. As a result, the plan requires installation of SCR at one of the two Craig BART-eligible units even though the Commission previously had concluded that installation of SCR was not warranted at either unit. In addition, we note that Colorado has imposed SCR as BART on two other EGUs in western Colorado—Hayden Units 1 and 2—and at the Pawnee plant in eastern Colorado. Moreover, Colorado has exceeded the minimum requirements for BART and reasonable progress for sources included in the PSCO BART Alternative (as described in our notice of proposed rulemaking, 77 FR 18073-18075), and has imposed substantial and meaningful controls, that go beyond what EPA's regulations otherwise might have required, to address reasonable progress sources for the initial planning period.</P>
        <P>Under the unique circumstances discussed above, EPA concludes that Colorado's plan achieves a reasonable result overall. Based on this, we are approving the entirety of the Colorado regional haze SIP, even though the State's BART analysis for Craig 1 only analyzed visibility impacts at the most impacted Class I area and appears to overestimate the costs of SCR controls. We expect Colorado to revisit the appropriateness of SCR controls on Craig Unit 1 in the next reasonable progress planning period.</P>
        <P>Finally, we note that the State's plan will result in NO<E T="52">X</E>emission reductions of 34,774 tons per year, SO<E T="52">2</E>emission reductions of 35,776 tons per year, and PM reductions of 532 tons per year. As many of the NO<E T="52">X</E>emission reductions will occur along Colorado's Front Range, the State's plan should help reduce ozone levels in Colorado's ozone non-attainment area and nitrogen deposition in Rocky Mountain National Park. In addition, portions of Colorado's plan includes retirement and fuel-switching of existing coal-fired units, resulting in significant reductions of emissions of mercury into the atmosphere at levels that exceed what a straightforward application of emission reduction technology to satisfy BART and reasonable progress would have conferred on sources throughout the state.</P>
        <HD SOURCE="HD2">B. NO<E T="52">X</E>BART Determination for Martin Drake Units 5, 6, and 7</HD>
        <P>
          <E T="03">Comment:</E>The NO<E T="52">X</E>BART determination for Martin Drake underestimates the control efficiency of SCR. A conservative, but more appropriate control efficiency would be an annual average of 0.05 lb/MMBtu. This would result in additional reductions of 41, 69, and 105 tons of NO<E T="52">X</E>per year at Units 5, 6, and 7, respectively. This would also result in larger modeled visibility benefits.</P>
        <P>
          <E T="03">Response:</E>We agree that at some facilities, SCR has achieved annual NO<E T="52">X</E>emission rates as low as 0.05 lb/MMBtu; however, the annual emission rate of 0.07 lb/MMBtu assumed by Colorado in estimating the costs and benefits of SCR is within the range of actual emission rates demonstrated at similar facilities in EPA's CAMD emission database. Given this, we find that it was not unreasonable for Colorado to use 0.07 lb/MMBtu to model the predicted<PRTPAGE P="76876"/>visibility improvement from SCR. Moreover, while we do agree that assuming a control efficiency of 0.05 lb/MMBtu would have resulted in greater modeled visibility benefits, we do not agree that the difference in visibility benefits would have led Colorado to a different conclusion given the magnitude of the benefits associated with SCR.</P>
        <P>
          <E T="03">Comment:</E>The costs of SCR were overestimated in the Martin Drake analysis in the following ways: (1) The SCR costs were estimated using the Integrated Emissions Control Cost (IECCOST) model, not the CCM as required by the BART Guidelines; (2) the calculated costs included items that are expressly disallowed or typically excluded when following the CCM methodology, including royalties, initial catalyst and chemicals, and escalation. These costs add millions of dollars to the total amount attributed to SCR; (3) the $/kW costs were extremely high. While SCR retrofits typically range from $83—$300/kW, including the most complex and space constrained projects, the costs for the Martin Drake units were $558/kW, $448/kW, and $325/kW, for Units 5, 6, and 7, respectively; and (4) the analysis did not consider the cost savings when controls like SCR are applied to multiple units at the same facility. This discount is on the order of 4-10%.</P>
        <P>
          <E T="03">Response:</E>We agree with several points in this comment. In fact, we raised many of the same issues related to cost analysis in our October 26, 2010, comment letter to the State. However, we note that Colorado eliminated SCR from consideration for the Martin Drake BART units primarily on the basis of the level of visibility improvement. The visibility improvement associated with SCR at Units 5, 6, and 7, is 0.12, 0.27, and 0.37 deciviews, respectively. In addition, as the State noted, the incremental visibility improvement from SCR versus ultra-low NO<E T="52">X</E>burners and overfire air (the control technology upon which the State's NO<E T="52">X</E>BART limits are based) is even lower—0.04, 0.07, and 0.11 deciview, respectively, at Units 5, 6, and 7. The State concluded that lower costs would not change its BART determination. Based on these visibility improvement values and the expectation that cost effectiveness values for SCR calculated in accordance with the CCM would still be relatively high compared to the selected control option, we find that the State's NO<E T="52">X</E>BART determination for Martin Drake Units 5, 6, and 7 was reasonable.</P>
        <P>
          <E T="03">Comment:</E>A cost analysis consistent with the CCM would indicate that SCR is cost effective for the Martin Drake units. A revised costs analysis would show that the revised cost effectiveness for SCR is under the State's $5000/ton threshold.</P>
        <P>
          <E T="03">Response:</E>The commenter did not provide sufficient data or analysis to support this assertion regarding a revised cost analysis. Regardless, for the reasons stated above, we conclude that the State's BART determination was reasonable. Even if a control technology is arguably cost-effective on a dollar per ton basis, a State may conclude that the control technology is not warranted based on a consideration of all BART factors.</P>
        <P>
          <E T="03">Comment:</E>EPA failed to consider the cumulative visibility benefits on all of the impacted Class I areas. Additionally, the predicted improvement for SCR at the most affected Class I area, at least 0.12 deciview, 0.27 deciview, and 0.37 deciview, for Units 5, 6, and 7, respectively, are not insignificant.</P>
        <P>
          <E T="03">Response:</E>While we agree that Colorado should have considered impacts to the various impacted Class I areas, we have no reason to believe that the cumulative visibility benefits would warrant a change in our approval of the State's NO<E T="52">X</E>BART determination for Martin Drake Units 5, 6, and 7. Regarding the predicted improvement at the most affected Class I area, while we agree that the levels are not insignificant, they are not significant enough for us to conclude that the State's BART determination was unreasonable, particularly when the incremental visibility improvement and expected costs of SCR are considered.</P>
        <P>
          <E T="03">Comment:</E>Cost-effective visibility benefits were rejected as a result of Colorado's criteria that holds post-combustion controls and SCR in particular to a higher standard of visibility benefits. As EPA itself previously pointed out in its October 26, 2010, letter: “* * * the criteria appear to discriminate against SCR as a potential control option. Under the criteria, if the cost of SCR is under $5,000/ton and the modeled visibility benefit is 0.20 delta-deciview or greater but less than 0.50 delta-deciview, the State would reject SCR. Using the State's criteria, the State would find SNCR reasonable with the same $/ton and delta-deciview values. We are not aware of a valid basis for applying different criteria to the two control options.”</P>
        <P>This example proves EPA's point. By this logic, if the evaluated technology in this instance were SNCR instead of SCR, it would be BART for at least Units 6 and 7, and possibly Unit 5. We concur with EPA's previous critique: this distinction has no basis and is untenable.</P>
        <P>
          <E T="03">Response:</E>While we do not necessarily agree with the State's criteria for post-combustion controls, we find the State's NO<E T="52">X</E>BART determination for Martin Drake Units 5, 6, and 7 to be reasonable within the context of the five factors for the reasons stated above.</P>
        <HD SOURCE="HD2">C. BART Determination for Colorado Energy Nations (CENC) Unit 4 and Unit 5</HD>
        <P>
          <E T="03">Comment:</E>In determining BART for Units 4 and 5, the State failed to identify and analyze alternative fueling scenarios that would lead to greater reductions in NO<E T="52">X</E>, sulfur dioxide (SO<E T="52">2</E>), and particulate matter. The proposed rule notes, and the underlying record clearly explains, that Units 4 and 5 are capable of burning (and do in fact burn) fuels other than coal. In particular, the proposed rule states that Unit 4 can and does burn natural gas or fuel oil and that Unit 5 can and does burn fuel oil. Both boilers may fire ethanol or sludge from the Coors Brewery.</P>

        <P>Despite this, the State did not assess whether alternative fueling scenarios, such as a full or partial shift from coal to natural gas or fuel oil at Units 4 and 5 would represent BART. This is a concern because according to the CAA Title V Operating Permit for the facility, both Units 4 and 5 could meet stronger SO<E T="52">2</E>and NO<E T="52">X</E>emission rates than have been proposed by the State as BART. The operating permit shows that the permitted emission rates for Units 4 and 5, when firing natural gas and/or fuel oil, are already lower than the proposed BART emission rates.<SU>8</SU>

          <FTREF/>Given that permitted emission rates are higher than actual emissions, this means that the facility is most likely capable of achieving far greater emission reductions under an alternative fueling scenario. Indeed, for Unit 4, whether firing natural gas or fuel oil, both permitted SO<E T="52">2</E>and NO<E T="52">X</E>emission rates are lower than the proposed BART limits. For Unit 5, when firing fuel oil, the permitted SO<E T="52">2</E>emission rate is lower than proposed BART. Furthermore, although the permitted NO<E T="52">X</E>emission rate for Unit 5 when firing fuel oil is higher than the proposed BART, it is based on a 3-hour average (as opposed to a 30-day average) and even then, actual emissions are likely to be lower than the proposed BART</P>
        <FTNT>
          <P>
            <SU>8</SU>
            <E T="03">See</E>Colorado Department of Public Health and Environment, Operating Permit, Trigen-Colorado Energy Corporation Golden Facility (Feb. 1, 2003). Attached as Exhibit 1 to the comment.</P>
        </FTNT>

        <P>Here, alternative fueling scenarios, such as a full or partial shift away from<PRTPAGE P="76877"/>coal to fuels that are already being burned in Units 4 and 5 (including natural gas and fuel oil) both seem to represent the “best system of continuous emission control technology” and seem entirely reasonable when considering the five factors required to be assessed by states when determining BART. The State failed to analyze alternative fueling in its SIP. Alternative fueling is an available technology that should have been analyzed by the State given that the visibility benefits to Class I areas could be tremendous. Although the State purported to identify “all available technologies” in its BART analysis, clearly it did not identify all available technologies.</P>

        <P>The failure to analyze alternative fueling scenarios is especially confusing because the State did, apparently, identify in its TSD for the CENC facility a fuel switch to natural gas as an available technology and in analyzing “SO<E T="52">2</E>Emissions Management” as potential BART, noted that an option to reduce emissions could involve a “dispatch [of] natural gas-fired capacity.” There is, however, no explanation in the TSD as to why “fuel switching,” or otherwise increased reliance on natural gas, would not constitute BART or would be contrary to the five factors required to be considered in establishing BART under the CAA.</P>

        <P>The failure to analyze alternative fueling scenarios is further confusing because the EPA's BART guidelines indicate that alternative fueling scenarios should be analyzed by states when determining BART. The guidelines specifically state that “potentially applicable retrofit control alternatives” can include the “use of inherently lower-emitting processes/practices” or “combinations of inherently lower-emitting processes and add-on controls.” Appendix Y at Section IV.D.3. Above all, states should “identify potentially applicable retrofit technologies that represent the full range of demonstrated alternatives.”<E T="03">Id.</E>The guidelines clearly indicate that inherently “lower-emitting processes,” such as alternative fueling, are squarely within the realm of what may be considered BART.</P>
        <P>Given the State's failure to take into consideration an available technology, the EPA must disapprove the BART determinations for CENC Units 4 and 5 and in accordance with the CAA promulgate a FIP that establishes BART limits based on a full consideration of alternative fueling scenarios.</P>
        <P>
          <E T="03">Response:</E>Although the State did not present the information in the SIP and was not required to analyze such scenarios, the State in fact analyzed alternative fueling scenarios for Unit 4 and Unit 5.<SU>9</SU>
          <FTREF/>The State examined fuel switching to a number of different fuels. The State determined that Units 4 and 5 are not capable of burning wood or other biomass fuels and the use of sludge as the primary fuel is not technically feasible due to handling and storage issues. The State determined residual oil, distillate oil, ethanol, and natural gas were technically feasible options.</P>
        <FTNT>
          <P>
            <SU>9</SU>The State sent an email to EPA Region 8 on July 16, 2012 containing its cost estimates for fuel switching. The cost analysis can be found in the docket.</P>
        </FTNT>
        <P>The State determined residual oil would not result in pollutant reductions, and that distillate oil, ethanol, and biodiesel are high cost fuels for boilers of this size, with prices about two to three times the cost of natural gas, and six to seven times the cost of coal (at the time of analysis—December 2009) and highly volatile. Thus, the State eliminated these fuels from further consideration.</P>

        <P>Furthermore, the State determined the cost effectiveness of fuel-switching to natural gas for SO<E T="52">2</E>and NO<E T="52">X</E>control for Units 4 and 5. The State determined the costs for fuel switching to natural gas for SO<E T="52">2</E>would be $29,985/ton removed for Unit 4 and $30,945/ton removed for Unit 5. The State determined the costs for fuel switching to natural gas for NO<E T="52">X</E>would be $64,102/ton removed for Unit 4 and $82,834/ton removed for Unit 5. Because of the high cost effectiveness values, the State did not perform any visibility modeling for fuel switching to natural gas and the State eliminated it from further consideration for BART. We have reviewed the State's cost calculations and find them reasonable.</P>
        <P>Based on the above statement from our BART guidelines, and based on the State's analysis, we agree with the State's conclusion that fuel switching to natural gas is not BART at CENC Units 4 and 5.</P>
        <HD SOURCE="HD2">D. NO<E T="52">X</E>BART Determination for Cemex Lyons Kiln</HD>
        <P>
          <E T="03">Comment:</E>Colorado did not appropriately analyze whether SCR was reasonable as BART for the kiln at the Cemex Lyons cement plant. In particular, the State rejected SCR as not an available technology. EPA itself did not agree with this finding. Despite this, EPA allowed the State to reject SCR due to perceived uncertainty over its cost effectiveness. However, because the State rejected SCR as an available technology, no analysis of the costs of SCR was actually undertaken and therefore, EPA's claims are baseless.</P>

        <P>SCR has been an available emission control technology for NO<E T="52">X</E>emissions for many years. Although its use on cement kilns has come about recently, several sources indicate that the technology is available and cost-effective, contrary to claims by the State. A report commissioned by Rocky Mountain Clean Air Action, which later merged with WildEarth Guardians, found that SCR “is an effective and proven technology to reduce nitrogen oxide emissions from cement kilns.”<SU>10</SU>

          <FTREF/>The report concluded that: “The installation of SCR on the [Cemex] Lyons Cement Plant could be expected to achieve substantial reductions (85-95%) in emissions of NO<E T="52">X</E>.” The report also found that the cost effectiveness of utilizing SCR ranges between $1,500 and $3,800 per ton of NO<E T="52">X</E>reduced, which is “easily within regulatory cost thresholds for many NO<E T="52">X</E>control programs.” Follow up correspondence from the author of the report, Dr. Armendariz to the State further confirmed that SCR was available and cost-effective.<SU>11</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>10</SU>See Armendariz, A, The Costs and Benefits of Selective Catalytic Reduction on Cement Kilns for Multi-Pollutant Control and the Applicability to the CEMEX Lyons Cement Plant (February 15, 2008) at 19. This report is attached as Exhibit 2 to this comment.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>11</SU>See Letter from Armendariz, A. to Dann, C. in re: SCR and Cement Kilns (July 22, 2008). This letter is attached as Exhibit 3 to this comment.</P>
        </FTNT>
        <P>EPA cannot come to conclusions on the cost effectiveness of SCR without analytical support, and there is no support for approving the State BART determination for the Cemex Lyons cement kiln. We request the EPA promulgate a FIP that objectively and thoroughly analyzes SCR as an available technology for purposes of establishing BART limits for the Cemex Lyons cement kiln.</P>
        <P>
          <E T="03">Response:</E>We disagree with this comment and stand by the rationale presented in our proposal (77 FR 18062). As we said there, we accept the State's decision, not to analyze SCR further for the purposes of regional haze. EPA has acknowledged, in the context of establishing the New Source Performance Standards (NSPS) for Portland Cement Plants, substantial uncertainty regarding the cost effectiveness associated with the use of SCR at such plants (75 FR 54995). In particular, while EPA noted that SCR had been used at three cement kilns in Europe, and had been agreed to by one domestic cement kiln as part of a settlement, EPA also noted the potential for dust buildup on the catalyst, “which<PRTPAGE P="76878"/>[could] be influenced by site specific raw material characteristics present in the facility's proprietary quarry, such as trace contaminants that may produce a stickier particulate than is experienced at sites where the technology has been installed.”<E T="03">Id.</E>at 54994, 54995. EPA went on to state in the NSPS rulemaking that “[t]his buildup could reduce the effectiveness of the SCR technology, and make cleaning of the catalyst difficult resulting in kiln downtime and significant costs.”<E T="03">Id.</E>Because of the uncertainty, EPA was unable to estimate these costs.<E T="03">Id.</E>For the reasons stated in our NSPS rulemaking and in the State's regional haze SIP, there is also substantial uncertainty regarding the costs and control effectiveness of SCR at Cemex. We are not convinced that cost and control effectiveness information from the European plants or from SCR applications at other types of sources is sufficiently reliable to guide a BART determination for Cemex.<SU>12</SU>
          <FTREF/>Under the circumstances, we find that Colorado reasonably eliminated SCR as a potential BART control technology. As we stated in our proposal, we expect the State to reevaluate SCR technology in subsequent reasonable progress planning periods as more information regarding the use of SCR at cement kilns becomes available.</P>
        <FTNT>
          <P>
            <SU>12</SU>The State indicated that CEMEX consulted four potential SCR vendors but was unable to obtain meaningful quotes from any of them.</P>
        </FTNT>
        <HD SOURCE="HD2">E. NO<E T="52">X</E>BART Determination for Comanche Unit 1 and Unit 2</HD>
        <P>
          <E T="03">Comment:</E>Comanche Units 1 and 2 are currently meeting lower NO<E T="52">X</E>emission rates than the emission limits the State proposed for BART. With regard to the proposed BART limits, the State has proposed, and EPA has proposed to approve, a 30-day emission rate for Units 1 and 2 of 0.20 lb/MMBtu and a combined annual average emission rate of 0.15 lb/MMBtu for Units 1 and 2. According to the State, these limits will be met with no additional controls on Unit 1 or Unit 2.</P>
        <P>The State's own BART analysis notes that currently Unit 1 is emitting at an average annual rate of 0.124 lb/MMBtu and Unit 2 is emitting at an average annual rate of 0.165 lb/MMBtu. This means that both on a 30-day rolling average basis and on an annual average basis, both units are capable of emitting, and indeed do emit, at rates below the proposed BART limits of 0.20 lb/MMBtu on a 30-day rolling average and 0.15 lb/MMBtu on an annual basis. In essence, Colorado's BART proposal actually allows Comanche Units 1 and 2 to emit more pollution than what they currently emit.</P>

        <P>Under the State's proposed BART, emissions will be allowed to increase on an annual basis. Using annual heat input totals from the baseline year of 2009 obtained from the EPA's Air Markets Program Data Web site (24,247,113.27 MMBtu for unit 1 and 27,423,612.26 MMBtu for unit 2) and using the proposed annual combined average BART limits, it appears that under the annual BART limits, NO<E T="52">X</E>emissions will be allowed to increase by at least 14 tons per year (tpy).</P>

        <P>Concerning the 30-day rolling average limits, there will definitely be allowed emission increases. During the baseline year of 2009, both Comanche Unit 1 and Unit 2 emitted far lower than the proposed BART limit of 0.20 lb/MMBtu. During the baseline year of 2009, 30-day rolling average NO<E T="52">X</E>emissions were consistently far below 0.20 lb/MMBtu for the year. Even the peak 30-day rolling averages of 0.142 and 0.179 lb/MMBtu for Units 1 and 2, respectively, are below the proposed limit. Based on this, the proposed BART would actually allow Unit 1 to emit at least 40% more NO<E T="52">X</E>than the baseline 30-day rolling average peak and Unit 2 to emit 12% more NO<E T="52">X</E>. However, this is just in the context of the baseline peak 30-day rolling average. In all reality, actual 30-day rolling average emission will remain even further below the proposed BART limit of 0.20 lb/MMBtu.</P>

        <P>Clearly, Comanche Units 1 and 2 could easily meet lower emission limits as BART. We do not suggest that the State was required to set the emission limits exactly at the levels emitted, but clearly when the data demonstrates that Unit 1 could meet a 30-day rolling average NO<E T="52">X</E>emission limit of 0.15 lb/MMBtu and Unit 2 could meet a limit of 0.18 lb/MMBtu without any trouble, the BART limits should reflect what is achievable.</P>
        <P>Although the State and the EPA may claim the proposed limits are necessary to provide a margin or cushion of compliance, nothing in the CAA or the EPA's regulations suggests that it is appropriate to build in such margins or cushions into BART limits, especially given that BART must represent that “best system of continuous emission reduction.” If Comanche Units 1 and 2 can do better, than clearly, the proposed BART limits are not the best. Nothing in the CAA or the EPA's regulations implementing the regional haze program suggest or remotely imply that a state could allow emission increases as BART.</P>
        <P>Accordingly, EPA must disapprove of Colorado's NO<E T="52">X</E>BART determinations for Comanche Unit 1 and Unit 2 and adopt a FIP that establishes BART limits that are consistent with the CAA and that represent actual emission reductions.</P>
        <P>
          <E T="03">Response:</E>In our October 26, 2010, comment letter to Colorado, we asked Colorado to evaluate tightening Comanche's NO<E T="52">X</E>limits as potential BART. As discussed in Colorado's BART analysis for the Comanche units, Colorado did in fact evaluate emission limit tightening in response to our concerns. Colorado subsequently concluded that a 0.20 lb/MMBtu 30-day rolling average emission limit was necessary to account for uncertainty regarding load fluctuations, cold-weather operating, start-up, and cycling for renewable energy. Colorado noted that greater future reliance on renewable energy will lead to increased cycling of the Comanche units and more frequent start-ups. This in turn may lead to increased emissions over shorter averaging periods compared to past actual emissions. Colorado also noted the limited amount of actual emissions data for the two units since controls were installed for SO<E T="52">2,</E>and the same is true for NO<E T="52">X</E>. Thus, while Colorado established an annual NO<E T="52">X</E>BART limit of 0.15 lb/MMBtu that is lower than the average actual emissions of 0.16 lb/MMBtu for Units 1 and 2 between January and October 2010, Colorado allowed greater leeway in the 30-day rolling average limit than would result from the strict application of a 15% buffer to 0.16 lb/MMBtu (0.20 lb/MMBtu versus 0.184 lb/MMBtu). Given some of the uncertainties regarding future operations and emissions, we have determined that the State acted reasonably in setting the emission limits for Comanche Units 1 and 2. We also note that commenter's own analysis suggests that the difference in annual emissions between maximum emissions under the BART limit using 2009 heat inputs and 2009 actuals would only be 14 tons per year. This is not significant when compared to Comanche's annual NO<E T="52">X</E>emissions of approximately 3,860 tons; it does not warrant disapproval and a subsequent FIP.</P>

        <P>In addition, Comanche's actual emissions following the installation of low NO<E T="52">X</E>burners and over-fire air occurred under permit limits that are identical to those the State selected as BART. The commenter has provided no evidence that the State's adoption of the same limits as BART limits will cause an increase in actual emissions.</P>
        <P>
          <E T="03">Comment:</E>The State failed to assess appropriately the cost of SCR. In particular, the State assumed that SCR would achieve an emission rate of 0.07<PRTPAGE P="76879"/>lb/MMBtu. However, as EPA itself noted in its October 26, 2010, comment letter to the State, SCR does achieve emission rates as low as 0.04 lb/MMBtu on an annual basis, and a 0.05 lb/MMBtu emission rate is a more appropriate benchmark from which to assess the cost effectiveness of SCR.</P>
        <P>In this case, the State did not assess the cost effectiveness of SCR based on a rate of 0.05 lb/MMBtu. Thus, it did not reasonably take into account the cost of compliance with SCR in accordance with the CAA. Without an adequate case-specific cost analysis, there is simply no support for concluding SCR, particularly for Unit 2, is unreasonable.</P>
        <P>
          <E T="03">Response:</E>As stated above, we agree that SCR has in some cases achieved annual NO<E T="52">X</E>emission rates as low as 0.05 lb/MMBtu, the emission rate that commenters suggest would have been a more appropriate benchmark in assessing the costs of SCR at Commanche; however, the 0.07 lb/MMBtu annual emission rate assumed by Colorado in estimating the costs and visibility benefits associated with SCR is within the range of actual emission rates demonstrated at similar facilities in EPA's CAMD emission database. Moreover, as with Martin Drake, we do not believe that if Colorado had used a more stringent emission rate that the impact on the BART analysis would have led Colorado to a different conclusion given the magnitude of the benefits associated with SCR. Given this, we conclude that the State's use of 0.07 lb/MMBtu to evaluate the cost effectiveness of SCR at Comanche was not unreasonable.</P>
        <P>
          <E T="03">Comment:</E>The State appears to have overestimated the capital cost of SCR. Both the EPA and the NPS previously commented to the State that the State should have used the EPA's CCM and noted that the CUECost model relied upon by the State is not appropriate. Nowhere in the record does the State explain why CUECost was reasonable, particularly in light of the concerns expressed by the EPA and the NPS. It appears that the reliance on CUECost led to artificially inflated capital costs, which in turn overestimated the true cost of SCR.</P>
        <P>
          <E T="03">Response:</E>We agree that there were flaws in Colorado's approach to estimating the costs of SCR for the Comanche BART units. However, we find that the State's NO<E T="52">X</E>BART determination to be reasonable within the context of the five factors, particularly based on the relatively modest visibility improvement associated with SCR—0.14 deciviews at Unit 1, and 0.17 deciviews at Unit 2—and the expectation that cost effectiveness values for SCR calculated in accordance with the CCM would still be relatively high compared to the selected control option.</P>
        <P>
          <E T="03">Comment:</E>Although the State and EPA may claim that, even if the costs were accurately assessed, the visibility benefits of SCR would not be significant, even for Unit 2, there is no support for this assertion. In particular, it appears as if the State's assessment of visibility improvements is based on an assumption that the proposed BART limits (<E T="03">i.e.,</E>the “do nothing” BART) would actually improve visibility. Given that the proposed BART limits would allow increased emissions, it would not actually improve visibility. When compared to the real impacts of the State's proposed BART for Comanche unit 1, SCR would appear to provide significant visibility improvements because, as opposed to the proposed BART, SCR would actually achieve improvements. For Unit 2, this is especially significant because SCR was the only available technology analyzed for BART. Thus, by all indications, SCR is the only means of actually achieving visibility improvements at Comanche Unit 2.</P>
        <P>
          <E T="03">Response:</E>We disagree with this comment. As shown in Colorado's visibility impact analysis for the Comanche BART units, Colorado assessed the benefit of control options relative to both the subject-to-BART baseline and to the installation of new LNB in 2007 and 2008. In addition, the subject-to-BART modeling emission rates were based on the maximum 24-hr rate consistent with the BART guidelines. Colorado's analysis shows visibility benefits for all of the control options considered, not just SCR. Moreover, relative to the subject-to-BART baseline, Colorado's BART selection (combustion controls), does in fact show visibility improvement (0.16 deciview and 0.31 deciview for Units 1 and 2, respectively). Therefore, EPA finds that no changes to the BART determinations or to the SIP are needed in response to this comment.</P>
        <P>
          <E T="03">Comment:</E>It is unclear why the State rejected SNCR for Comanche Unit 1, particularly given that the proposed BART limit for Unit 1 is less stringent than Unit 1's current actual emissions. Under an SNCR scenario, Unit 1 would meet a 30-day rolling average emission rate of 0.10 lb/MMBtu according to the EPA. According to the State, the cost, coupled with the State's perceived “low visibility improvement” warranted a determination that SNCR was not reasonable. However, according to the State's analysis, SNCR is cost effective at Unit 1, costing $3,644 per ton of NO<E T="52">X</E>reduced, which is squarely within the range of what the State considers to be cost-effective.</P>
        <P>
          <E T="03">Response:</E>We find that the State's rejection of SNCR was reasonable based on its weighing of the BART factors. The State reasonably concluded that the cost of SNCR was not warranted given the relatively modest visibility improvement that would result—0.11 deciviews. Even if a control technology is arguably cost-effective on a dollar per ton basis, a State may conclude that the control technology is not warranted based on a reasonable consideration of all BART factors.</P>
        <P>
          <E T="03">Comment:</E>With regard to visibility benefits, the State's analysis also indicates that SNCR would achieve greater improvement than an emission rate of 0.20 lb/MMBtu on a 30-day rolling average. Although the State asserts that the improvement would amount to 0.11 deciviews, it is unclear why such improvements are not reasonable or are otherwise insignificant, particularly given that the purpose of BART is to reduce or eliminate visibility impairment, and indeed there is no explanation in the record supporting the State's assertion. It also appears as if the State's assessment of visibility improvements is based on an assumption that the proposed BART limits would actually improve visibility. Given that the proposed BART allows increased emissions, it would not improve visibility. When compared to the real impacts of the State's proposed BART for Comanche Unit 1, SNCR appears to provide significant visibility improvements because, as opposed to the proposed BART, SNCR would actually achieve improvements. This further underscores why the State's BART determination for Comanche Unit 1 is flawed and why EPA must promulgate a FIP that establishes appropriate NO<E T="52">X</E>BART limits.</P>
        <P>
          <E T="03">Response:</E>The commenter is correct that the State predicted that SNCR would result in additional improvement in visibility over the control technology the State selected as BART. However, this does not mean the CAA or our regulations required the State to select SNCR as BART. For the reasons stated above, we find that it was reasonable for the State to reject SNCR based on consideration of all the BART factors. Regarding the commenter's suggestion that the State's selected limits will lead to an increase in emissions, as noted above, the commenter has presented no evidence that this will occur. Moreover, as indicated in a separate response to comments, above, Colorado assessed the benefit of control options relative to<PRTPAGE P="76880"/>both the subject-to-BART baseline and to the installation of new LNB in 2007 and 2008. Relative to the subject-to-BART baseline, Colorado's BART determination does in fact result in visibility benefits. The installation of LNB resulted in a visibility improvement of 0.16 deciview and 0.31 deciview for Comanche Units 1 and 2, respectively.</P>
        <HD SOURCE="HD2">F. NO<E T="52">X</E>Reasonable Progress Determination for Craig Unit 3</HD>
        <P>
          <E T="03">Comment:</E>We received comments that the reasonable progress evaluation of Craig Unit 3 includes the same flaws as for Units 1 and 2 (see comments in section IV.A.1—4 above). One commenter indicated that the estimated cost effectiveness is no higher than $3,190/ton, and likely lower, considering the conservative $300/kW starting point for their analysis. Another commenter estimated the cost effectiveness of SCR at Unit 3 as $2,385/ton.</P>
        <P>Based on visibility modeling from the NPS, commenters pointed out that the visibility benefits of adding SCR to Unit 3 are similar to those at Units 1 and 2—over 0.5 deciview at five Class I areas, and additional benefits at several more. The commenters asserted that, cumulatively, Unit 3 has an 8.39 deciview impact, with SCR providing a cumulative visibility improvement of 4.56 deciviews. Commenters went on to say that SCR at a limit of 0.05 lb/MMBtu should be required as reasonable progress for Craig Unit 3.</P>
        <P>
          <E T="03">Response:</E>We agree that the State likely overestimated the cost associated with SCR at Unit 3, but we are not prepared to disapprove the State's reasonable progress determination for Craig Unit 3. Assuming the commenters' assessments of the cost effectiveness of SCR are reasonably accurate, the values are not so low that it is clear that the State would have been unreasonable to reject SCR, especially given the State's requirement that Craig Unit 3 install SNCR and the resulting visibility benefits. We expect the State to re-evaluate SCR for Unit 3 in the next planning period.</P>
        <HD SOURCE="HD2">G. NO<E T="52">X</E>Reasonable Progress Determination for Nucla</HD>
        <P>
          <E T="03">Comment:</E>The State's proposed SIP appears to allow increased emissions from the Nucla coal fired power plant under the reasonable progress aspect of the proposed SIP. In light of this, it is unclear how the proposed emission limits for NO<E T="52">X</E>and SO<E T="52">2</E>actually meet the State's reasonable progress goals. Under the reasonable progress prong of the regional haze requirements of the CAA, the State determined that additional controls at the Nucla plant were reasonable to protect Class I areas. Accordingly, the State proposed to require the power plant to achieve a NO<E T="52">X</E>emission limit of 0.5 lb/MMBtu and an SO<E T="52">2</E>limit of 0.4 lb/MMBtu, both over a 30-day rolling average period. However, according to data from EPA's Air Markets Program Database, Nucla has been meeting emission rates far below these proposed reasonable progress limits.</P>

        <P>Indeed, data from the EPA demonstrates that between January 1, 2009, and December 31, 2011, Nucla has been meeting an average monthly NO<E T="52">X</E>emission rate of 0.367 lb/MMBtu and an average monthly SO<E T="52">2</E>emission rate of 0.301 lb/MMBtu. These rates indicate that Nucla is able to meet more stringent emission rates at no additional cost. The monthly SO<E T="52">2</E>and NO<E T="52">X</E>emission rates actually achieved by Nucla in the past 3 years clearly demonstrate that the power plant has consistently emitted at rates below the reasonable progress limits proposed by the State. Nucla is capable of achieving NO<E T="52">X</E>and SO<E T="52">2</E>emission rates lower than 0.30 lb/MMBtu on a 30-day basis.</P>
        <P>More importantly though, these rates indicate that the State's proposed reasonable progress limits actually allow more air pollution to be emitted from Nucla than is currently emitted. An increase in emissions would not appear to ensure reasonable progress in restoring visibility in Colorado's Class I areas. Thus, the State's proposed SIP is not approvable by EPA because it fails to ensure reasonable progress in accordance with 42 U.S.C. 7491(g)(1) and 40 CFR 51.308(d)(1)(i). At the least, the proposed reasonable progress emission limits for Nucla demonstrate that the State failed to appropriately assess the costs of compliance in accordance with the CAA. Indeed, if the State had appropriately assessed the costs of compliance, it would have found that lower emission rates would be equally cost-effective and more protective of visibility. Such a flawed analysis of reasonable progress in relation to the Nucla plant cannot be approved by EPA.</P>

        <P>The EPA must promulgate a FIP that establishes reasonable progress limits at the Nucla plant that actually achieve cost-effective emissions reductions. To this end, we request EPA adopt reasonable progress limits that limit NO<E T="52">X</E>emissions to no more than 0.25 lb/MMBtu and SO<E T="52">2</E>emissions to no more than 0.28 lb/MMBtu. Such limits are achievable and appear to be very cost-effective given that they would cost nothing.</P>
        <P>
          <E T="03">Response:</E>We disagree with this comment. Colorado based the SO<E T="52">2</E>emission limit of 0.4 lb/MMBtu on the existing limestone injection system for SO<E T="52">2</E>, and it based the NO<E T="52">X</E>limit of 0.5 lb/MMBtu on the inherent low-NO<E T="52">X</E>nature of the circulating fluidized bed boiler. A review of recent (2008-2010) monthly data in EPA's CAMD emissions database shows monthly NO<E T="52">X</E>emission rates as high as 0.45 lb/MMBtu and monthly SO<E T="52">2</E>emission rates as high as 0.33 lb/MMBtu. These rates are commensurate with the reasonable progress emission limits established by Colorado. Based on its reasonable progress analysis, Colorado concluded that no additional controls were reasonable. We concur with that conclusion.</P>
        <HD SOURCE="HD2">H. Reasonable Progress for Rio Grande Cement Company (GCC)</HD>
        <P>
          <E T="03">Comment:</E>The State should have analyzed visibility impacts due to GCC, as either a permit modification or as a reasonable progress source. To date, the State has not considered the impacts of the source under either program. Had the State compared GCC's emissions (Q) as a function of distance (d) to the threshold Q/d &gt; 20 used to determine whether a source would be included in the reasonable progress analysis, GCC would have qualified for reasonable progress review. The State contends that GCC was not included in the reasonable progress review because the State used 2007 emissions to determine which sources were subject to reasonable progress review, and GCC did not begin normal operations until 2009. However, in its analysis of the proposed permit modification, the State asserts that GCC's actual emissions should be based upon the current permit limits, not zero emissions. In that case, GCC's permit emissions should have been used to trigger inclusion in the Colorado reasonable progress analysis.</P>

        <P>It is essential that any regulatory program try to maintain a “level playing field.” There are two other cement plants in Colorado, and additional NO<E T="52">X</E>controls are being required on both under Colorado's regional haze SIP.</P>

        <P>GCC has installed SNCR but the current permit does not require these controls to be operated. We believe that, because the GCC permit allows emissions that exceed the State's threshold for determining which sources are subject to a reasonable progress analysis, GCC should have been included as a reasonable progress source. It is likely, based on the State's actions regarding the other two cement plants that the State would have required continuous operation of SNCR.<PRTPAGE P="76881"/>EPA should require GCC to reduce NO<E T="52">X</E>emissions by 45% on a continuous basis.</P>
        <P>
          <E T="03">Response:</E>The State based its evaluation of potential reasonable progress sources on stationary sources with actual emissions of 100 tpy or greater of PM, NO<E T="52">X,</E>and SO<E T="52">2</E>based on Air Pollution Emissions Notice (APEN) reports from 2007. The APEN reports for 2007 are based on data reported to the State by April 30, 2007, which is based on the previous full year of production (2006). The State formalized its reasonable progress analysis process in 2009. At that time, the APEN report data the State had (that had undergone full quality assurance and quality control) were the 2007 APEN reports based on the source reported 2006 data.</P>
        <P>In 2006, Rio Grande Cement reported zero emissions because it did not operate. In 2007, Rio Grande Cement did report APEN emissions (based on permitted limits) resulting in a Q/d&gt;20, but those emissions were not actual emissions because the source did not actually begin producing cement until April 2008. Because the State based its reasonable progress evaluation on 2006 actual emissions, we find it reasonable that the State did not further evaluate GCC for purposes of reasonable progress. We expect the State to do so for the next reasonable progress planning period.</P>
        <HD SOURCE="HD2">I. Legal Issues</HD>
        <HD SOURCE="HD3">1. Public Service Company of Colorado (PSCO) BART Alternative</HD>
        <P>
          <E T="03">Comment:</E>Phase III of the SIP Rulemaking (at which the PSCO BART Alternative was adopted), to which Colorado Mining Association (CMA) was a party, was based upon numerous irregularities and violations of the Colorado Administrative Procedures Act, the Colorado Air Pollution Prevention and Control Act, and H. B. 10-1365. CMA filed a complaint challenging the Air Quality Control Commission's (AQCC) SIP Rulemaking on March 16, 2011, in Denver District Court. The CMA case is pending review by the District Court. The issues before the court are numerous and establish the AQCC's Phase III rulemaking was improper and that the PSCO BART Alternative should be stricken from the Colorado regional haze SIP. If the Court determines that the Phase III rulemaking was improper, and therefore, portions of the proposed Colorado SIP were invalid under State law, those same portions of the proposed Colorado SIP would be unenforceable under federal law.</P>
        <P>As a result of the AQCC's egregious failures in Phase III of the SIP Rulemaking, the PSCO BART Alternative should not be included in the Colorado regional haze SIP. Until the Court has completed its review, EPA should not act to include the PSCO BART Alternative in the State's regional haze SIP.</P>
        <P>
          <E T="03">Response:</E>Once a state has submitted a SIP revision to us, we must approve it if it meets the CAA's minimum requirements. One of the relevant requirements is that the State have adequate authority under State law to carry out the plan. See CAA section 110(a)(2)(E). Absent a stay or determination by a court that a plan is invalid, or some other clear indication that the State lacks authority to implement the plan, we have no basis to disapprove it under 110(a)(2)(E). Here, there is no indication that Colorado lacks authority to implement the PSCO BART Alternative. Indeed, it is our understanding that CMA's lawsuit has been dismissed by the Denver District Court as moot. We have included a copy of the court's June 6, 2012 order in the docket for this action. If a court subsequently invalidates the PSCO BART Alternative, we will need to evaluate the Colorado SIP at that time, but the possibility of future invalidation does not provide a basis for us to disapprove the PSCO BART Alternative.</P>
        <HD SOURCE="HD3">2. Timing of Implementation</HD>
        <P>
          <E T="03">Comment:</E>Colorado's proposed SIP appears to contain a blanket schedule of BART compliance that states, “sources must comply as expeditiously as practicable, but no later than 5 years from EPA approval of the SIP.” This blanket schedule of compliance, which applies to all subject-to-BART sources under the proposed Colorado SIP, is contrary to the CAA. It is true that the CAA requires that subject-to-BART sources “procure, install, and operate, as expeditiously as practicable” any additional controls that may represent BART. However, simply stating verbatim in the SIP that “sources must comply as expeditiously as practicable” fails to give force and effect to this statutory provision. In this case, it is unclear what “as expeditiously as practicable” means, particularly in the context of individual subject-to-BART sources. The lack of any specificity renders this provision unenforceable, which further undermines the adequacy of the SIP under CAA section 110 and frustrates the statutory mandate set forth under the CAA.</P>
        <P>Additionally, the CAA is clear that in mandating “expeditious” compliance, SIPs must ensure that subject-to-BART sources comply as soon as possible. In this case, Colorado's SIP simply fails to ensure compliance with BART as soon as possible. It lacks any concrete dates by which subject-to-BART sources must comply, other than to state that sources must comply within the statutory maximum compliance date of 5 years. However, the CAA is clear that if a source can comply with BART before 5 years, it must comply by that earlier date. See 42 U.S.C. 7491(g)(4). Simply deferring to the 5-year deadline undermines the Congressional intent behind the “as expeditiously as practicable” provision.</P>
        <P>It is notable that in other situations, the EPA has proposed to require concrete compliance dates to satisfy the CAA's “as expeditiously as practicable” provisions under the regional haze program. For example, in proposing a FIP for BART for the San Juan Generating Station in New Mexico, the EPA proposed a 3-year compliance date, finding it to be “as expeditiously as practicable” (76 FR 504). Although EPA ultimately concluded that a 5-year schedule of compliance was appropriate, the Agency's proposed action clearly signaled that a concrete date is needed to satisfy the CAA.</P>
        <P>The EPA must therefore disapprove of Colorado's blanket schedule of BART compliance. In its place, the Agency must promulgate a FIP that sets forth concrete dates by which all subject-to-BART sources must “procure, install, and operate” BART that represent the most expeditious dates practicable.</P>
        <P>
          <E T="03">Response:</E>We have reviewed the compliance dates for meeting BART limits that are contained in the SIP. These dates are reasonable given the magnitude of the retrofits being undertaken. We note that the State's Regulation Number 3—<E T="03">Stationary Source Permitting And Air Pollutant Emission Notice Requirements</E>that we are approving as part of this action provides for compliance as expeditiously as practicable, but in no event later than 5 years from EPA final approval of the SIP.</P>
        <HD SOURCE="HD3">3. Compliance With Section 110(l)</HD>
        <P>
          <E T="03">Comment:</E>The EPA is duty-bound to ensure the proposed SIP does not interfere with attainment and maintenance of the National Ambient Air Quality Standards (NAAQS), in accordance with section 110(l) of the CAA. Thus, the EPA must ensure that the proposed SIP adequately limits air pollution in order to safeguard public health.</P>

        <P>In this case, we are concerned that in proposing to approve Colorado's regional haze plan that the EPA has not demonstrated that the proposal<PRTPAGE P="76882"/>adequately safeguards the 2008 8-hour ozone NAAQS, the newly promulgated 1-hour nitrogen dioxide NAAQS, the newly promulgated 1-hour SO<E T="52">2</E>NAAQS, and the 2006 fine particulate matter (PM<E T="52">2.5</E>) NAAQS. Thus, EPA has not shown the extent to which public health is likely to be protected under the proposed SIP.</P>

        <P>We are particularly concerned that the EPA overlooked its 110(l) obligations under the CAA given that, although the proposed rule may lead to emission reductions, no analysis or assessment has been prepared to demonstrate that even after these emission reductions, the recently promulgated NAAQS will be met. In this case, we are particularly concerned that the recently promulgated 1-hour NO<E T="52">2</E>and SO<E T="52">2</E>NAAQS could be jeopardized. Indeed, many, if not most, of the proposed emission rates are based on 30-day rolling averages. There is no indication that meeting emission rates on a 30-day rolling average will ensure that 1-hour NAAQS will be sufficiently protected. Indeed, a source could comply with a 30-day rolling average limit, yet still emit enough pollution on an hourly basis to cause or contribute to violations of the NAAQS, thereby interfering with attainment or maintenance.</P>

        <P>We are further concerned over the fact that several BART limits allow for increased emissions. For example, the proposed NO<E T="52">X</E>BART determinations for Comanche Units 1 and 2 allow for greater emissions than are currently released by the units. This raises concerns over the impacts to the NAAQS. These impacts must be addressed by EPA.</P>
        <P>In this case, the EPA must either disapprove of the Colorado SIP over the State's failure to perform a 110(l) analysis or prepare its own 110(l) analysis to demonstrate that the SIP will effectively protect public health and not interfere with attainment or maintenance of the NAAQS.</P>
        <P>
          <E T="03">Response:</E>CAA section 110(l) provides that EPA “shall not approve a revision of a plan if the revision would interfere with any applicable requirement concerning attainment and reasonable further progress * * *, or any other applicable requirement of” the CAA. It is not clear that the regional haze SIP submitted by Colorado is a “revision of a plan” within the meaning of CAA section 110(l) as it is the first implementation plan due under the regional haze program. See,<E T="03">e.g.,</E>§ 51.308(b). However, even if such an analysis were required, the commenter has not provided any evidence that the Colorado regional haze SIP will interfere with any applicable requirement concerning attainment and reasonable progress or any other applicable requirement of the CAA, or that further analysis under 110(l) is necessary.</P>

        <P>Although the Colorado regional haze SIP will lead to emission reductions, the commenter asserts that that even so EPA must determine that the SIP revision will ensure the NAAQS are met. We disagree with this interpretation of CAA section 110(l). The Act and EPA's regulations require the regional haze SIP to address visibility impairment in mandatory Class I areas—attainment of the NAAQS is provided for through a separate SIP process. It is EPA's consistent interpretation of section 110(l) that a SIP revision does not interfere with attainment and maintenance of the NAAQS if the revision at least preserves the status quo air quality by not relaxing or removing any existing emissions limitation or other SIP requirement. EPA does not interpret section 110(l) to require a full attainment or maintenance demonstration for each NAAQS for every SIP revision.<E T="03">See, e.g., Kentucky Resources Council, Inc.,</E>v.<E T="03">EPA,</E>467 F.3d 986 (6th Cir. 2006);<E T="03">see also,</E>61 FR 16050, 16051 (April 11, 1996) (actions on which the<E T="03">Kentucky Resources Council</E>case were based).</P>
        <P>Thus, in this action, we need not determine whether a 30-day limit is adequate to protect a shorter-term NAAQS because the regional haze SIP is not required to ensure attainment of the NAAQS. The fact that the regional haze SIP specifies 30-day limits will not preclude Colorado from adopting limits with a shorter averaging time, if at some future date such limits are found to be necessary and required by the CAA to protect the NAAQS.</P>

        <P>The commenter also alleges that “several BART limits allow for increased emissions” over current actual source emissions and cites as an example the NO<E T="52">X</E>BART limits for Comanche Units 1 and 2. The commenter claims this raises concerns over impacts to the NAAQS. However, the Colorado regional haze SIP imposes new emissions limits on a number of existing sources, and it does not relax any existing emissions limits or other SIP requirements. In fact, the regional haze SIP makes violations of the NAAQS less likely because without the BART limits, actual emissions could increase even more. And, the regional haze SIP does not prevent the State from adopting lower limits in the future as necessary to protect the NAAQS. Thus, the regional haze SIP revision and its BART limits will not interfere with “any applicable requirement concerning attainment and reasonable further progress * * *, or any other applicable requirement of” the CAA.</P>
        <HD SOURCE="HD2">J. Comments Generally in Favor of our Proposal</HD>
        <P>
          <E T="03">Comment:</E>We received comment letters fully in support of our rulemaking from Xcel Energy, Tri-State Generation, and a letter on behalf of Colorado Environmental Coalition, Environment Colorado, Environmental Defense Fund, and Western Resource Advocates. We received 84 comments from members of National Parks Conservation Association generally in support of our action. These comments from National Parks Conservation Association members also urged EPA to finalize stricter NO<E T="52">X</E>controls on Tri-State Craig Unit 1, which we have addressed above. We also received comments from National Parks Conservation Association, the NPS, and WildEarth Guardians that supported the majority of our action, but pointed out some concerns, to which we have responded above.</P>
        <P>
          <E T="03">Response:</E>We acknowledge the support of these commenters for part or all of our proposed action.</P>
        <HD SOURCE="HD1">V. Statutory and Executive Order Reviews</HD>
        <P>Under the Clean Air Act, the Administrator is required to approve a SIP submission that complies with the provisions of the Act and applicable Federal regulations. 42 U.S.C. 7410(k); 40 CFR 52.02(a). Thus, in reviewing SIP submissions, EPA's role is to approve state choices, provided that they meet the criteria of the Clean Air Act. Accordingly, this action merely approves state law as meeting Federal requirements and does not impose additional requirements beyond those imposed by state law. For that reason, this action:</P>
        <P>• Is not a “significant regulatory action” subject to review by the Office of Management and Budget under Executive Order 12866 (58 FR 51735, October 4, 1993);</P>

        <P>• Does not impose an information collection burden under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501<E T="03">et seq.</E>);</P>

        <P>• Is certified as not having a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601<E T="03">et seq.</E>);</P>
        <P>• Does not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4);</P>

        <P>• Does not have Federalism implications as specified in Executive<PRTPAGE P="76883"/>Order 13132 (64 FR 43255, August 10, 1999);</P>
        <P>• Is not an economically significant regulatory action based on health or safety risks subject to Executive Order 13045 (62 FR 19885, April 23, 1997);</P>
        <P>• Is not a significant regulatory action subject to Executive Order 13211 (66 FR 28355, May 22, 2001);</P>
        <P>• Is not subject to requirements of Section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) because application of those requirements would be inconsistent with the Clean Air Act; and</P>
        <P>• Does not provide EPA with the discretionary authority to address, as appropriate, disproportionate human health or environmental effects, using practicable and legally permissible methods, under Executive Order 12898 (59 FR 7629, February 16, 1994).</P>
        <P>In addition, this rule does not have tribal implications as specified by Executive Order 13175 (65 FR 67249, November 9, 2000), because the SIP is not approved to apply in Indian country located in the state, and EPA notes that it will not impose substantial direct costs on tribal governments or preempt tribal law.</P>
        <P>The Congressional Review Act, 5 U.S.C. 801<E T="03">et seq.,</E>as added by the Small Business Regulatory Enforcement Fairness Act of 1996, generally provides that before a rule may take effect, the agency promulgating the rule must submit a rule report, which includes a copy of the rule, to each House of the Congress and to the Comptroller General of the United States. EPA will submit a report containing this action and other required information to the U.S. Senate, the U.S. House of Representatives, and the Comptroller General of the United States prior to publication of the rule in the<E T="04">Federal Register</E>. A major rule cannot take effect until 60 days after it is published in the<E T="04">Federal Register</E>. This action is not a “major rule” as defined by 5 U.S.C. 804(2).</P>
        <P>Under section 307(b)(1) of the Clean Air Act, petitions for judicial review of this action must be filed in the United States Court of Appeals for the appropriate circuit by March 1, 2013. Filing a petition for reconsideration by the Administrator of this final rule does not affect the finality of this action for the purposes of judicial review nor does it extend the time within which a petition for judicial review may be filed, and shall not postpone the effectiveness of such rule or action. This action may not be challenged later in proceedings to enforce its requirements. (See CAA section 307(b)(2).)</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 40 CFR Part 52</HD>
          <P>Environmental protection, Air pollution control, Incorporation by reference, Nitrogen dioxide, Ozone, Particulate matter, Sulfur oxides.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: September 10, 2012.</DATED>
          <NAME>James B. Martin,</NAME>
          <TITLE>Regional Administrator, Region 8.</TITLE>
        </SIG>
        <P>For the reasons discussed in the preamble, 40 CFR chapter I is amended as follows:</P>
        <REGTEXT PART="52" TITLE="40">
          <PART>
            <HD SOURCE="HED">PART 52—APPROVAL AND PROMULGATION OF IMPLEMENTATION PLANS</HD>
          </PART>
          <AMDPAR>1. The authority citation for Part 52 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 7401<E T="03">et seq.</E>
            </P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">
          <SUBPART>
            <HD SOURCE="HED">Subpart G—Colorado</HD>
          </SUBPART>
          <AMDPAR>2. Section 52.320 is amended by adding paragraph (c)(108)(i)(C) and adding paragraph (c)(124) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 52.320</SECTNO>
            <SUBJECT>Identification of plan.</SUBJECT>
            <STARS/>
            <P>(c) * * *</P>
            <P>(108) * * *</P>
            <P>(i) * * *</P>

            <P>(C) Colorado Air Quality Control Commission, Regulation Number 3, 5 CCR 1001-5,<E T="03">Stationary Source Permitting and Air Pollutant Emission Notice Requirements,</E>Part D,<E T="03">Concerning Major Stationary Source New Source Review and Prevention of Significant Deterioration,</E>Section XIV.F,<E T="03">Long Term Strategy,</E>subsection XIV.F.1. introductory text and XIV.F.1.c; adopted January 7, 2011; effective February 14, 2011.</P>
            <STARS/>
            <P>(124) On May 25, 2011 the State of Colorado submitted revisions to its State Implementation Plan to address the requirements of EPA's regional haze rule.</P>
            <P>(i) Incorporation by reference.</P>

            <P>(A) Colorado Air Quality Control Commission, Regulation Number 3, 5 CCR 1001-5,<E T="03">Stationary Source Permitting and Air Pollutant Emission Notice Requirements,</E>Part F,<E T="03">Regional Haze Limits—Best Available Retrofit Technology (BART) and Reasonable Progress (RP),</E>Section VI,<E T="03">Regional Haze Determinations,</E>and Section VII,<E T="03">Monitoring, Recordkeeping, and Reporting for Regional Haze Limits;</E>adopted January 7, 2011; effective February 14, 2011.</P>

            <P>(B) Colorado Air Quality Control Commission, Regulation Number 7, 5 CCR 1001-9,<E T="03">Control of Ozone via Ozone Precursors (Emissions of Volatile Organic Compounds and Nitrogen Oxides),</E>Section XVII,<E T="03">(State Only, except Section XVII.E.3.a. which was submitted as part of the Regional Haze SIP) Statewide Controls for Oil and Gas Operations and Natural Gas-Fired Reciprocating Internal Combustion Engines,</E>subsection E.3.a,<E T="03">(Regional Haze SIP) Rich Burn Reciprocating Internal Combustion Engines;</E>adopted January 7, 2011; effective February 14, 2011.</P>
          </SECTION>
        </REGTEXT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31192 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <CFR>40 CFR Parts 52 and 81</CFR>
        <DEPDOC>[EPA-R05-OAR-2011-0468; FRL-9764-9]</DEPDOC>
        <SUBJECT>Approval and Promulgation of Implementation Plans and Designation of Areas for Air Quality Planning Purposes; Ohio; Redesignation of the Ohio Portion of the Huntington-Ashland 1997 Annual Fine Particulate Matter Nonattainment Area to Attainment</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>EPA is approving, under the Clean Air Act (CAA), the state of Ohio's request to redesignate the Ohio portion of the Huntington-Ashland (OH-WV-KY) nonattainment area (Lawrence, Scioto, and portions of Adams and Gallia Counties) to attainment for the 1997 annual National Ambient Air Quality Standard (NAAQS or standard) for fine particulate matter (PM<E T="52">2.5</E>). The Ohio Environmental Protection Agency (Ohio EPA) submitted its request on May 4, 2011. EPA determined that the entire Huntington-Ashland area has attained the 1997 annual PM<E T="52">2.5</E>standard, and proposed to approve Ohio's request to redesignate the Ohio portion of the area on December 22, 2011. EPA's final rulemaking involves several related actions. EPA has determined that the entire Huntington-Ashland area continues to attain the 1997 annual PM<E T="52">2.5</E>standard. EPA is approving, as a revision to the Ohio State Implementation Plan (SIP), the state's plan for maintaining the 1997 annual PM<E T="52">2.5</E>NAAQS in the area through 2022. EPA is also approving the 2005 and 2008 emissions inventories for the Ohio portion of the Huntington-Ashland area as meeting the comprehensive emissions inventory requirement of the CAA. EPA finds adequate and is making a finding of<PRTPAGE P="76884"/>insignificance for Ohio motor vehicle emissions of nitrogen oxides (NO<E T="52">X</E>) and direct PM<E T="52">2.5</E>for the Huntington-Ashland area. EPA, therefore, grants Ohio's request to redesignate the Ohio portion of the Huntington-Ashland area to attainment for the 1997 PM<E T="52">2.5</E>annual standard.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>This rule will be effective December 31, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>EPA has established a docket for this action under Docket Identification EPA-R05-OAR-2011-0468. All documents in these dockets are listed on the<E T="03">www.regulations.gov</E>Web site. 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 U.S. Environmental Protection Agency, Region 5, Air and Radiation Division, 77 West Jackson Boulevard, Chicago, Illinois 60604. This facility is open from 8:30 a.m. to 4:30 p.m., Monday through Friday, excluding Federal holidays. We recommend that you telephone Carolyn Persoon at (312) 353-8290 before visiting the Region 5 office.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Carolyn Persoon, Environmental Engineer, Control Strategies Section, Air Programs Branch (AR-18J), Environmental Protection Agency, Region 5, 77 West Jackson Boulevard, Chicago, Illinois 60604, (312) 353-8290, persoon.carolyn@epa.gov.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Throughout this document whenever “we,” “us,” or “our” is used, we mean EPA. This supplementary information section is arranged as follows:</P>
        
        <EXTRACT>
          <FP SOURCE="FP-2">I. What is the background for the actions?</FP>
          <FP SOURCE="FP-2">II. What actions is EPA taking?</FP>
          <FP SOURCE="FP-2">III. What is EPA's response to comments?</FP>
          <FP SOURCE="FP-2">IV. Why is EPA taking these actions?</FP>
          <FP SOURCE="FP-2">V. Final action</FP>
          <FP SOURCE="FP-2">VI. Statutory and executive order reviews</FP>
        </EXTRACT>
        <HD SOURCE="HD1">I. What is the background for the actions?</HD>

        <P>On May 4, 2011 the Ohio EPA submitted its request to redesignate the Ohio portion of the Huntington-Ashland nonattainment area to attainment for the 1997 annual PM<E T="52">2.5</E>NAAQS, and for EPA approval of the state's SIP revision containing an emissions inventory and a maintenance plan for the area. On December 22, 2011 (76 FR 79593), EPA proposed approval of Ohio's redesignation request, emissions inventories and plan for maintaining the 1997 annual PM<E T="52">2.5</E>NAAQS. EPA also proposed approval of Ohio's determination that on-road emissions of PM<E T="52">2.5</E>and NO<E T="52">X</E>are insignificant contributors to PM<E T="52">2.5</E>concentrations in the area. Additional background for today's action is set forth in EPA's December 22, 2011, proposed rulemaking.</P>

        <P>In the proposed redesignation of the Huntington-Ashland area, EPA proposed to determine that the emission reduction requirements that contributed to attainment of the 1997 annual PM<E T="52">2.5</E>standard in the nonattainment area could be considered permanent and enforceable. At the time of proposal, EPA noted that the Clean Air Interstate Rule (CAIR), which had been in place through 2011, had been replaced by the recently promulgated Cross-State Air Pollution Rule (CSAPR). 76 FR 48208, August 8, 2011. CSAPR included regulatory changes to sunset (i.e., discontinue) CAIR and the CAIR Federal Implementation Plans (FIPs) for control periods in 2012 and beyond.<E T="03">See</E>76 FR 48322. Although Ohio's redesignation request and maintenance plan relied on reductions associated with CAIR, EPA proposed to approve the request based in part on the fact that CSAPR achieved “similar or greater reductions in the relevant areas in 2012 and beyond.” 76 FR 79598. On December 30, 2011, eight days after the proposed redesignation, the U.S. Court of Appeals for the D.C. Circuit (referred to as D.C. Circuit or court hereafter) issued an order addressing the status of CSAPR and CAIR in response to motions filed by numerous parties seeking a stay of CSAPR pending judicial review. In that order, the court stayed CSAPR pending resolution of the petitions for review of that rule in<E T="03">EME Homer Generation, L.P.</E>v.<E T="03">EPA</E>(No. 11-1302 and consolidated cases). The court also indicated that EPA was expected to continue to administer CAIR in the interim until judicial review of CSAPR was completed.</P>
        <P>On August 21, 2012, the D.C. Circuit issued a decision in<E T="03">EME Homer Generation, L.P.</E>v.<E T="03">EPA,</E>to vacate and remand CSAPR and ordered EPA to continue administering CAIR pending the promulgation of a valid replacement. That judgment is not yet final as the mandate has not been issued by the court and on October 5, 2012, EPA filed a petition for rehearing<E T="03">en banc</E>asking the full court to reconsider that decision. EPA has determined that it is appropriate to move forward with final approval of this redesignation action, even though the emission reductions associated with CSAPR that EPA referenced in the proposal notice may not be relied upon at this time given the rule's legal status. As discussed in greater detail in this notice, the submission received from the state relied on reductions achieved from CAIR and demonstrated that the Huntington-Ashland area achieved attainment due in part to emission reductions required by CAIR. The D.C. Circuit's order that EPA continue administering CAIR until a valid replacement rule is developed ensures that the reductions that led to attainment are sufficiently permanent and enforceable to meet the requirements of CAA section 107(d)(3)(E)(iii).</P>
        <HD SOURCE="HD1">II. What actions is EPA taking?</HD>

        <P>EPA has determined that the entire Huntington-Ashland area has attained and continues to attain the 1997 annual PM<E T="52">2.5</E>standard<SU>1</SU>

          <FTREF/>(76 FR 55542) and that the Ohio portion of the area meets the requirements for redesignation under section 107(d)(3)(E) of the CAA. On September 7, 2011, at 76 FR 55542, EPA finalized its determinations that the Huntington-Ashland area attained the 1997 PM<E T="52">2.5</E>NAAQS and that the area attained the 1997 PM<E T="52">2.5</E>NAAQS by the applicable attainment date of April 5, 2010. Subsequent to EPA's final determination of attainment and proposed redesignation of the Ohio portion of the Huntington-Ashland area, additional monitoring data have become available, quality-assured, and certified. Table 1 below sets forth design values for 2007-2009, 2008-2010, and 2009-2011, last of which is based on the most current 3-years of data, which shows that the area continues to attain. Preliminary data available for 2012 also are consistent with continued attainment.</P>
        <FTNT>
          <P>

            <SU>1</SU>On September 7, 2011 EPA published a final determination that the Huntington-Ashland area has attained the 1997 annual PM<E T="52">2.5</E>standard. 76 FR 55542, September 7, 2011.</P>
        </FTNT>
        <PRTPAGE P="76885"/>
        <GPOTABLE CDEF="s50,r25,15,15,15,15" COLS="6" OPTS="L2,i1">

          <TTITLE>Table 1—Design Value Concentrations for the Huntington-Ashland Area for the 1997 Annual PM<E T="52">2.5</E>NAAQS Microgram per Cubic meter (μg/m<SU>3</SU>)</TTITLE>
          <BOXHD>
            <CHED H="1">Location</CHED>
            <CHED H="1">County, State</CHED>
            <CHED H="1">Monitor ID</CHED>
            <CHED H="1">3-Year Design Values</CHED>
            <CHED H="2">2007-2009</CHED>
            <CHED H="2">2008-2010</CHED>
            <CHED H="2">2009-2011</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Huntington</ENT>
            <ENT>Cabell, WV</ENT>
            <ENT>54-011-0006</ENT>
            <ENT>14.3</ENT>
            <ENT>13.1</ENT>
            <ENT>12.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Ashland Primary (FIVCO)</ENT>
            <ENT>Boyd, KY</ENT>
            <ENT>21-019-0017</ENT>
            <ENT>12.4</ENT>
            <ENT>11.4</ENT>
            <ENT>10.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Lawrence County Hospital (LCH)<SU>2</SU>
            </ENT>
            <ENT>Lawrence, OH</ENT>
            <ENT>39-087-0010</ENT>
            <ENT>13.3</ENT>
            <ENT>NA</ENT>
            <ENT>NA</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Ironton Department of Transportation (DOT)<SU>3</SU>
            </ENT>
            <ENT>Lawrence, OH</ENT>
            <ENT>39-087-0012</ENT>
            <ENT>12.2</ENT>
            <ENT>12.2</ENT>
            <ENT>11.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Portsmouth</ENT>
            <ENT>Scioto, OH</ENT>
            <ENT>39-145-0013</ENT>
            <ENT>12.3</ENT>
            <ENT>11.6</ENT>
            <ENT>10.9</ENT>
          </ROW>
          <TNOTE>
            <SU>2</SU>The Lawrence County Hospital Site was shut down in February 2008. The Ironton DOT site began operation on the same day the Lawrence County Hospital Site ceased monitoring.</TNOTE>
          <TNOTE>
            <SU>3</SU>The Ironton DOT site did not begin operation until February 2008; however, an analysis of air quality data at this location, as provided for in 40 CFR part 50 appendix N, was done showing that the area would attain the standard for the 2007-2009 and 2008-2010 monitoring periods.</TNOTE>
        </GPOTABLE>

        <P>Because the area continues to attain and meets all other requirements for redesignation under CAA section 107(d)(3)(E), EPA is approving the request from the state of Ohio to change the legal designation of the Ohio portion of the Huntington-Ashland area from nonattainment to attainment for the 1997 annual PM<E T="52">2.5</E>NAAQS.<SU>4</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>4</SU>EPA in this notice is not addressing the requests of Kentucky and West Virginia for redesignation of those states' portions of the Huntington-Ashland area.</P>
        </FTNT>
        <P>EPA is taking several actions related to Ohio's PM<E T="52">2.5</E>redesignation request, as discussed below.</P>

        <P>EPA is approving, pursuant to CAA section 175A, Ohio's 1997 annual PM<E T="52">2.5</E>maintenance plan for the Huntington-Ashland area as a revision to the Ohio SIP (such approval being one of the CAA criteria for redesignation to attainment status). The maintenance plan is designed to keep the Huntington-Ashland area in attainment of the 1997 annual PM<E T="52">2.5</E>NAAQS through 2022.</P>

        <P>EPA is approving, pursuant to CAA section 172(c)(3), both the 2005 and 2008 emission inventories for primary PM<E T="52">2.5</E>,<SU>5</SU>
          <FTREF/>NO<E T="52">X</E>, and SO<E T="52">2</E>,<SU>6</SU>
          <FTREF/>documented in Ohio's PM<E T="52">2.5</E>redesignation request submittal. These emission inventories satisfy the requirement in section 172(c)(3) of the CAA for a comprehensive, current emission inventory.</P>
        <FTNT>
          <P>
            <SU>5</SU>Fine particulates directly emitted by sources and not formed in a secondary manner through chemical reactions or other processes in the atmosphere.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>6</SU>NO<E T="52">X</E>and SO<E T="52">2</E>are precursors for fine particulates through chemical reactions and other related processes in the atmosphere.</P>
        </FTNT>

        <P>Finally, for transportation conformity purposes EPA is approving Ohio's determination that on-road emissions of PM<E T="52">2.5</E>and NO<E T="52">X</E>are insignificant contributors to PM<E T="52">2.5</E>concentrations in the area. Further discussion of the basis for these actions was provided in the proposed rulemaking on December 22, 2011 (76 FR 79593).</P>
        <HD SOURCE="HD1">III. What is EPA's Response to Comments?</HD>
        <P>EPA received two sets of comments on its proposed rulemaking. The Ohio Utilities Group submitted comments in support of the redesignation of the Ohio portion of the Huntington-Ashland area, and on behalf of Sierra Club, Robert Ukeiley submitted adverse comments. A summary of Sierra Club's comments and EPA's responses are provided below.</P>
        <P>
          <E T="03">Comment 1a:</E>The Commenter contends that EPA cannot rely on reductions associated with the NO<E T="52">X</E>SIP Call,<SU>7</SU>

          <FTREF/>CAIR, and CSAPR in order to redesignate the Huntington-Ashland area because reductions from these programs are not permanent and enforceable. The Commenter points out that EPA noted that the area is impacted by pollution from electric generating units (EGUs) and that the Ohio submittal “credits reductions” to three rules that reduce SO<E T="52">2</E>and NO<E T="52">X</E>emissions from power plants, the NO<E T="52">X</E>SIP Call, CAIR, and CSAPR.</P>
        <FTNT>
          <P>

            <SU>7</SU>The Commenter mentions that EPA may not rely on emission reductions associated with the NO<E T="52">X</E>SIP Call but does not provide any specific arguments to support this contention.</P>
        </FTNT>

        <P>Specifically, the Commenter argues that CAIR reductions are not permanent and enforceable because EPA stated in the proposal that CAIR emission reductions only run through 2011. The Commenter also cites statements by EPA made in the context of other rules indicating that CAIR is legally deficient, remanded, and therefore temporary, in both the regional haze proposed rulemakings (76 FR 78194, 78200, December 16, 2011), as well as a redesignation proposal for Cincinnati (76 FR 65458, 65460, October 21, 2011). The Commenter argues that EPA cannot rely on CAIR because it is a cap-and-trade program. The Commenter cites to<E T="03">NRDC</E>v.<E T="03">EPA,</E>571 F.3d 1245, 1257 (D.C. Cir. 2009) for support of the proposition that, because EPA cannot predict which sources will reduce emissions, EPA cannot rely on cap-and-trade programs for future reductions. The Commenter states that any source could decide at any time in the future to purchase emissions credits and increase its emissions and impacts to the Huntington-Ashland area. The Commenter adds that emissions banking can also lead to violations of the NAAQS and prevents CAIR emission budgets from being permanent and enforceable emission limits.</P>
        <P>
          <E T="03">Response 1a:</E>EPA disagrees with Commenter that it must disapprove Ohio's redesignation request because the submittal relies on CAIR. First, although Ohio's redesignation request references CAIR and includes emission reductions associated with CAIR, EPA's modeling indicates that the area would attain and maintain the 1997 PM<E T="52">2.5</E>NAAQS even in the absence of CAIR. Second, the EPA statements cited by the Commenter regarding the status of CAIR were made prior to the D.C. Circuit's decision to vacate CSAPR and to leave CAIR in place. Third, EPA disagrees with the Commenter's assertion that reductions may not be relied upon for redesignation purposes if those reductions stem from an emissions trading program. Finally, EPA believes that the area meets all the requirements for redesignation regardless of the status of CAIR, because the area has other measures, such as consent decrees on EGUs.</P>

        <P>As an initial matter, EPA notes that the modeling EPA conducted during the rulemaking for the CSAPR rulemaking demonstrates that the Huntington-Ashland area would attain and maintain the 1997 PM<E T="52">2.5</E>NAAQS even without CAIR or a rule to replace CAIR. Nothing in the<E T="03">EME Homer</E>decision undermines that conclusion or suggests that the air quality modeling conducted during the rulemaking was flawed. As such, there<PRTPAGE P="76886"/>is no basis to conclude that it would be improper to redesignate the area even in the absence of CAIR. Moreover, the commenter's assertions regarding the status of CAIR and the extent to which emission reductions associated with CAIR may be relied upon in redesignations are flawed for the reasons described below.</P>
        <P>The Commenter points out that EPA made statements that CAIR reductions were expiring in 2011 (76 FR 79593, December 22, 2011) and were temporary (76 FR 78194, 78200, December 16, 2011; 76 FR 65458, 65460, October 21, 2011). However, these statements should be viewed in light of changes in the legal context of CAIR and CSAPR, which occurred subsequent to those statements and had a significant effect on the status of CAIR.</P>

        <P>On May 12, 2005, EPA published CAIR, which requires significant reductions in emissions of SO<E T="52">2</E>and NO<E T="52">X</E>from electric generating units to limit the interstate transport of these pollutants and the ozone and fine particulate matter they form in the atmosphere.<E T="03">See</E>76 FR 70093. The D.C. Circuit initially vacated CAIR,<E T="03">North Carolina</E>v.<E T="03">EPA,</E>531 F.3d 896 (D.C. Cir. 2008), but ultimately remanded the rule to EPA without vacatur to preserve the environmental benefits provided by CAIR,<E T="03">North Carolina</E>v.<E T="03">EPA,</E>550 F.3d 1176, 1178 (D.C. Cir. 2008). In response to the court's decision, EPA issued CSAPR, to address interstate transport of NO<E T="52">X</E>and SO<E T="52">2</E>in the eastern United States.<E T="03">See</E>76 FR 48208 (August 8, 2011). On August 21, 2012, the D.C. Circuit issued a decision to vacate CSAPR. In that decision, it also ordered EPA to continue administering CAIR “pending * * * development of a valid replacement.”<E T="03">EME Homer City Generation, L.P.</E>v.<E T="03">EPA,</E>696 F.3d 7, 38 (D.C. Cir. 2012).<SU>8</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>8</SU>The court's judgment is not yet final as the mandate has not issued and on October 5, 2012, EPA filed a petition asking for rehearing<E T="03">en banc.</E>
          </P>
        </FTNT>

        <P>The agency's statements cited by the Commenter must be viewed in context: They were made after CSAPR had been promulgated to sunset and replace CAIR, and before the D.C. Circuit stayed CSAPR and issued its decision in<E T="03">EME Homer</E>to vacate the rule. In that decision, the court ordered EPA to continue implementing CAIR until a valid replacement rule is promulgated. The decision thus had a significant impact on the CAIR programs and EPA's evaluation of the status of emission reductions achieved pursuant to those programs. In light of these unique circumstances and for the reasons explained below, EPA is finalizing the redesignation and the related SIP revision for the Huntington-Ashland area, including Ohio's plan for maintaining attainment of the PM<E T="52">2.5</E>standard. The air quality modeling analysis conducted for CSAPR demonstrates that the Huntington-Ashland area would be able to attain the PM<E T="52">2.5</E>standard even in the absence of either CAIR or CSAPR.<E T="03">See</E>“Air Quality Modeling Final Rule Technical Support Document,” appendix B, B-55 to B-56. This modeling is available in the docket for this proposed redesignation action. Nothing in the D.C. Circuit's August 2012 decision disturbs or calls into question that conclusion or the validity of the air quality analysis on which it is based.</P>

        <P>In addition, CAIR remains in place and enforceable until substituted by a “valid” replacement rule. Ohio's CAIR provisions can be found in Ohio Administrative Code Chapter 3745-109. On February 1, 2008, at 73 FR 6034, EPA approved an “abbreviated SIP” covering several of Ohio's CAIR provisions, including CAIR NO<E T="52">X</E>allocations. On September 25, 2009 (74 FR 48857), EPA approved a full CAIR SIP for Ohio incorporating all of Ohio's CAIR provisions. These SIP provisions remain in place and are federally enforceable. And, because CAIR has been in force since 2005, the monitoring data used to demonstrate the area's attainment of the 1997 annual PM<E T="52">2.5</E>NAAQS by the April 2010 attainment deadline were impacted by CAIR. CAIR reductions began as early as 2007, with full program requirements beginning in 2009. However, to the extent that Ohio's redesignation request and maintenance plan rely on CAIR, the recent directive from the D.C. Circuit in<E T="03">EME Homer</E>ensures that the reductions associated with CAIR will be permanent and enforceable for the necessary time period. EPA has been ordered by the court to develop a new rule and the opinion makes clear that after promulgating that new rule EPA must provide states an opportunity to draft and submit SIPs to implement that rule. CAIR thus cannot be replaced until EPA has promulgated a final rule through a notice-and-comment rulemaking process, states have had an opportunity to draft and submit SIPs, EPA has reviewed the SIPs to determine if they can be approved, and EPA has taken action on the SIPs, including promulgating a FIP if appropriate. These steps alone will take many years, even with EPA and the states acting expeditiously. The court's clear instruction to EPA that it must continue to administer CAIR until a “valid replacement” exists provides an additional backstop; by definition, any rule that replaces CAIR and meets the court's direction would require upwind states to have SIPs that eliminate significant contributions to downwind nonattainment and prevent interference with maintenance in downwind areas.</P>

        <P>Further, in vacating CSAPR and requiring EPA to continue administering CAIR, the D.C. Circuit emphasized that the consequences of vacating CAIR “might be more severe now in light of the reliance interests accumulated over the intervening four years.”<E T="03">EME Homer,</E>696 F.3d at 38. The accumulated reliance interests include the interests of states who reasonably assumed they could rely on reductions associated with CAIR which brought certain nonattainment areas into attainment with the NAAQS. If EPA were prevented from relying on reductions associated with CAIR in redesignation actions, states would be forced to impose additional, redundant reductions on top of those achieved by CAIR. EPA believes this is precisely the type of irrational result the court sought to avoid by ordering EPA to continue administering CAIR. For these reasons also, EPA believes it is appropriate to allow states to rely on CAIR, and the existing emissions reductions achieved by CAIR, as sufficiently permanent and enforceable for purposes such as redesignation. Following promulgation of the replacement rule, EPA will review SIPs as appropriate to identify whether there are any issues that need to be addressed.</P>

        <P>EPA also disagrees with the Commenter that emission reductions occurring within the relevant nonattainment area cannot be relied upon for the purpose of redesignations if they are associated with the emissions trading programs established in CAIR. The case cited by the Commenter,<E T="03">NRDC</E>v.<E T="03">EPA,</E>571 F.3d 1245 (D.C. Cir. 2009), does not support the Commenter's position and is entirely consistent with EPA's position here. That case addressed EPA's determination that the nonattainment Reasonably Available Control Technology (RACT) requirement was satisfied by the NO<E T="52">X</E>SIP Call trading program. The court emphasized that reductions outside the nonattainment area do not satisfy the RACT requirement and thus held that because EPA had not shown the trading program would result in sufficient reductions<E T="03">in a nonattainment area,</E>its determination that the program satisfied RACT was not supported.<SU>9</SU>
          <FTREF/>
          <E T="03">Id.</E>at 1256-<PRTPAGE P="76887"/>58. The court did not hold, as Commenter suggests, that emissions trading programs must be ignored when evaluating redesignation requests.</P>
        <FTNT>
          <P>

            <SU>9</SU>The court specifically elected not to vacate the RACT provision and left open the possibility that<PRTPAGE/>EPA may be able to reinstate the provision for particular nonattainment areas if, upon conducting a technical analysis, it finds the NO<E T="52">X</E>SIP Call results in greater emissions reductions in a nonattainment area than would be achieved if RACT-level controls were installed in that area.<E T="03">Id.</E>at 1258.</P>
        </FTNT>

        <P>There is simply no support for the Commenter's argument that, in determining whether to redesignate an area, EPA must ignore all emission reductions achieved by CAIR simply because the mechanism used to achieve the reductions is an emissions trading program. As a general matter, trading programs require total mass emission reductions by establishing mandatory caps on total emissions to permanently reduce the total mass emissions allowed by sources subject to the programs, validated through rigorous continuous emission monitoring and reporting regimens. The emission caps and associated controls are enforced through the associated SIP rules or FIPs. Any purchase of allowances and increase in emissions by one source necessitates a corresponding sale of allowances and reduction in emissions by another covered source. Given the regional nature of PM<E T="52">2.5</E>, the corresponding emission reduction will have an air quality benefit that will compensate, at least in part, for the impact of any emission increase. In contrast, emission rate limits serve a different purpose and do not limit total mass emissions. Total mass emissions can vary greatly under emission rate programs as demand and production vary from year to year.</P>

        <P>There is no support for the Commenter's contention that the presence of allowance banking in a program somehow renders those programs' emission reduction requirements impermanent or unenforceable, such that EPA must ignore reductions associated with any trading program that allows banking. In general, banking provides economic incentives for early reductions in emissions and encourages sources to install controls earlier than required for compliance with future caps on emissions. As Commenter points out, Ohio's submittal states that “companies installed more controls” during the time period that CAIR was being developed and promulgated. The flexibility under a cap and trade system is not about whether to reduce emissions. Rather, it is about how to reduce them at the lowest possible cost. The fact that companies anticipate the economic benefits of installing controls earlier, and reductions thus may occur more quickly than required (freeing up allowances that may then be banked and providing earlier health and environmental benefits to the public) does not, in any way, undermine the permanence or enforceability of the requirements in the underlying rule. The bank itself was factored into the CAIR cap levels that were chosen. The bank allows for a “glide path” to final cap levels (70 FR 25194, May 12, 2005). Further, evaluations have been made to see whether banking and trading have created emissions “hot spots.” For example, since the beginning of the Acid Rain Program, there have been no emissions hot spots identified or created as a result of the program (see “The Acid Rain Program Experience: Should We Be Concerned About SO<E T="52">2</E>Emissions Hotspots?” at<E T="03">http://epa.gov/airmarkets/resource/acidrain-resource.html</E>).</P>
        <P>Additionally, states and localities may impose stricter limits on sources to address specific local air quality concerns. These limits must be met regardless of a source's accumulated allowances.</P>

        <P>In sum, contrary to Commenter's contention, the decision of the D.C. Circuit in<E T="03">NRDC</E>v.<E T="03">EPA</E>does not establish that emission reductions from cap-and-trade programs, or emission reductions from cap-and-trade programs that allow banking, may not be relied upon for redesignations. For the reasons explained above, EPA disagrees that the Commenter has identified a basis on which EPA should disapprove Ohio's redesignation request.</P>
        <P>EPA also notes that CAIR is not the only permanent and enforceable measure affecting EGU emission reductions in the Huntington-Ashland area. There have been several consent decrees in the area affecting EGUs. First, in the Kentucky portion of the Huntington-Ashland Area, the Big Sandy Power Station was required by a federally enforceable consent decree<SU>10</SU>

          <FTREF/>and 2007 settlement agreement to install and continuously operate selective catalytic reduction (SCR) to reduce NO<E T="52">X</E>emissions from Unit 2 beginning January 1, 2009. The plant is also required to install and continuously operate flue gas desulfurization (FGD) to reduce SO<E T="52">2</E>emissions from Unit 2 beginning December 31, 2015. Operation of FGD controls has a co-benefit of reducing direct PM<E T="52">2.5</E>emissions as well. In the Ohio and West Virginia portions of the Area, a federally enforceable consent decree<SU>11</SU>
          <FTREF/>and 2007 settlement agreement require the General James M. Gavin Power Plant (Ohio) and Mountaineer Power Plant (West Virginia) to install and continuously operate SCR and FGD on specified units and the Philip Sporn Plant (West Virginia) to retire, retrofit, or re-power one unit. Another consent decree,<SU>12</SU>
          <FTREF/>to which EPA was not a party, requires the J.M. Stuart Power Plant (Ohio) to install and continuously operate SCR on all of its units. To the extent that power plant emission reductions contributed to attainment in the Huntington-Ashland Area, these reductions are permanent and enforceable.</P>
        <FTNT>
          <P>

            <SU>10</SU>Entered with the United States District Court For The Southern District Of Ohio Eastern Division (United States of America and State Of New York,<E T="03">et al.,</E>v. American Electric Power Service Corp.,<E T="03">et al.,</E>No. C2-99-1250 and 1182 (consolidated)).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>11</SU>
            <E T="03">Id.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>

            <SU>12</SU>Entered with the United States District Court For The Southern District Of Ohio, Eastern Division (<E T="03">Sierra Club and Marilyn Wall</E>v.<E T="03">The Dayton Power and Light Company, Duke Energy Ohio, Inc., and Columbus Southern Power Co.,</E>Civil Action No. 2: 04-cv-905).</P>
        </FTNT>
        <P>
          <E T="03">Comment 1b:</E>The Commenter claims that “EPA's proposal indicates that is relying heavily on CSAPR to justify its redesignation of the Huntington-Ashland area.” The Commenter argues that EPA cannot rely on CSAPR, because it has been stayed,<SU>13</SU>
          <FTREF/>thus imposing no emission reductions or emission limits, and therefore cannot be found to impose permanent and enforceable emission reductions. The Commenter also notes that EPA's proposal of revisions to CSAPR undermines EPA's ability to analyze whether reductions required by CSAPR will achieve attainment in the Huntington-Ashland area. Furthermore, Commenter argues that CSAPR cannot be relied upon to redesignate the Huntington-Ashland area into attainment unless the D.C. Circuit affirms the rule. The Commenter also objects to reliance on CSAPR because CSAPR, as a trading program, does not impose emission limits on the sources impacting air quality in the Huntington-Ashland area that are at least as stringent as those sources' actual 2008 emission rates. Specifically, the Commenter argues that CSAPR does not result in permanent and enforceable reductions because individual sources that impact the area can comply with the rule by either meeting their emission budgets or by obtaining emission credits from other sources that do not impact the air quality in the Huntington-Ashland area; and because under CSAPR, sources can bank emissions.</P>
        <FTNT>
          <P>

            <SU>13</SU>The rule was stayed as of the time of submission of comments; it has since been vacated by the D.C. Circuit and petitions for rehearing<E T="03">en banc</E>are pending.</P>
        </FTNT>
        <P>
          <E T="03">Response 1b:</E>Contrary to Commenter's contention, EPA's<PRTPAGE P="76888"/>conclusion that the area has met the requirements for redesignation does not rely on and is not dependent on CSAPR being in place. Ohio's maintenance plan does not rely on future emission reductions from CSAPR, and thus EPA's basis for redesignation of the area from nonattainment to attainment is unaffected by the status of CSAPR. Instead, Ohio relied on CAIR in its maintenance plan, and as discussed in EPA's response to comment 1a, such reliance is appropriate in this context. EPA did not rely on CSAPR to provide a basis for redesignating the area from nonattainment to attainment. Rather, EPA's statements about CSAPR in the proposal were made in the context of CAIR's imminent replacement by CSAPR. The Huntington-Ashland area has attained the 1997 annual PM<E T="52">2.5,</E>and continues to attain the standard as shown in the monitoring data provided above. The state of Ohio has shown that the emission reductions that led to the monitored attainment were due to many permanent and enforceable measures, including federal mobile vehicle standards, CAIR and consent decrees. At proposal, EPA noted that CSAPR had been promulgated to replace CAIR but that redesignation of Huntington-Ashland was still appropriate, because reductions achieved by CSAPR in this area would be equivalent to or greater than those achieved by CAIR. Since the proposal, the D.C. Circuit has issued a decision to vacate CSAPR; thus in this action EPA is evaluating Ohio's maintenance plan as submitted, including the emission reductions associated with CAIR. The redesignation of the Ohio portion of the Huntington-Ashland area meets the requirements under section 107(d)(3)(iii) without any reductions associated with CSAPR.</P>
        <P>
          <E T="03">Comment 1c:</E>The Commenter states that it is arbitrary for EPA to use only one year in determining whether permanent and enforceable emission reductions led to air quality improvements, because cap-and-trade programs allow for varied emissions year to year. Moreover, the Commenter states that analyzing the year 2008 poses further problems, because it marked the beginning of a major economic downturn and EPA provided no analysis of whether the recession was a factor in the improvements in air quality.</P>
        <P>
          <E T="03">Response 1c:</E>EPA's conclusion here is fully supported by the facts and applicable legal criteria. EPA's longstanding practice and policy<SU>14</SU>

          <FTREF/>provides for states to demonstrate permanent and enforceable emissions reductions by comparing nonattainment area emissions occurring during the nonattainment period (represented by emissions during one of the years during the 3-year nonattainment period, in this case 2005) with emissions in the area during the attainment period (represented by emissions during one of the three attainment years, in this case 2008, which is included in the 3-year period, 2007-2009, that the State used to show attainment with the 1997 annual PM<E T="52">2.5</E>standard). A determination that an area has attained the 1997 annual PM<E T="52">2.5</E>standard is based on an objective review of air quality data in accordance with 40 CFR 50.13 and Appendix N of part 50, based on 3 complete, consecutive calendar years of quality-assured air quality monitoring data. In the State's redesignation request, Ohio considered data for the 2007-2009 time period to demonstrate attainment. In EPA's determination of attainment and proposed approval of the redesignation request, EPA considered data for the 2008-2010 time period, which was the most recent quality-assured, certified data available. See 76 FR 55542 (September 7, 2011), 76 FR 79593 (December 22, 2011). In this final rulemaking, EPA is also considering the area's continued attainment based on complete, quality-assured certified data for 2009-2011. EPA has also considered preliminary data showing the area has continued to monitor attainment through 2012. Therefore, selecting 2008 as a representative attainment year, and comparing emissions for this year to those for a representative year during the nonattainment period, 2005, is an appropriate and long-established approach that demonstrates improvements in air quality as a result of the imposition of emission reductions in the area between the years of nonattainment and attainment. For example, see recent redesignations such as Indianapolis PM<E T="52">2.5</E>annual standard (76 FR 59512), Lake and Porter 8-hour ozone standard (75 FR 12090), and Northwest Indiana PM<E T="52">2.5</E>annual standard (76 FR 59600).</P>
        <FTNT>
          <P>
            <SU>14</SU>See September 4, 1992 memorandum from John Calcagni entitled “Procedures for Processing Requests to Redesignate Areas to Attainment,” pp. 4 and 8-9.</P>
        </FTNT>
        <P>EPA disagrees with the Commenter's contention that using a single attainment year is arbitrary due to year to year variations in emission levels resulting from cap-and-trade programs, and that 2008 was a “problematic” year to select for analysis. As noted above, data for 2008-2010 and 2009-2011 as well as preliminary data for 2012 show continued attainment of the standard. Although the Commenter points out one monitor's reading that approached the threshold in 2010, the fact remains that Huntington-Ashland is in attainment and has been in attainment.</P>

        <P>With respect to the Commenter's assertion that EPA has conducted no analyses to prove that emission reductions between 2005 and 2008 led to reduced PM<E T="52">2.5</E>concentrations, as noted above, comparing emissions for a representative nonattainment year to emissions for a representative attainment year is consistent with longstanding practice and EPA policy for making such a demonstration. The CAA does not specifically require the use of modeling in making any such demonstration and it has not been the general practice to do so. While the Commenter expressed concerns that an economic downturn was responsible for the improvement in air quality, the Commenter has made no demonstration that the reduction in emissions and observed improvement in air quality is due to an economic recession, changes in meteorology, or temporary or voluntary emissions reductions.</P>

        <P>In contrast, in EPA's proposed redesignation of the Kentucky portion of the Huntington-Ashland area 77 FR 69409 (November 19,2012), EPA provided a technical analysis showing that emission reductions from EGUs in the Huntington-Ashland area exceed average emission reductions seen in EGUs subject to decreased electrical demand, i.e., the economic recession. A summary of the emission changes from 2005 to 2011 for the entire Huntington-Ashland Area is provided in Table 2 below. Table 3 summarizes EPA's analysis showing reductions of SO<E T="52">2</E>and NO<E T="52">X</E>emissions, in tons per year (tpy) across the Huntington-Ashland area for 2005-2011 for all the coal-fired EGUs in the area. There were reductions in SO<E T="52">2</E>and NO<E T="52">X</E>emissions for all facilities with two exceptions. At the General J.M. Gavin facility, the 2011 SO<E T="52">2</E>emission rate was nearly the same as the 2005 rate, but production was higher in 2011 than in 2005. Thus the slight increase in emissions was in no way related to the fact that CAIR is an emissions trading program. As stated earlier, limitations on emission rates do not ensure total mass emissions are limited. And at the Kyger Creek facility, the 2011 emission rate was slightly higher than the 2005 rate; however, the slight increase was directly related to the facility's strategy to reduce emissions. The facility installed a scrubber to control SO<E T="52">2</E>in 2012. The company originally planned to install the controls by 2011 and therefore switched to higher sulfur coal<PRTPAGE P="76889"/>then. Now that the scrubber is installed, 2012 emission reductions are on track to be as much as 65,000 tons lower than in 2005 putting Ohio reductions for 2012 around 169,000 tons,<SU>15</SU>

          <FTREF/>as compared to 2005 emissions. Emission reductions have been greater than decreases in emissions that could be attributed to any decrease in electrical demand in the Huntington-Ashland Area. While the average SO<E T="52">2</E>and NO<E T="52">X</E>emission reductions from coal fired power plants in the Huntington-Ashland Area for the period 2005-2011 were 31 percent and 68 percent, respectively, the average facility power production in terms of heat input decreased by only about 5 percent during the same period. EPA finds that Ohio's 2008 inventory is a suitable representation of emissions during the period when the Huntington-Ashland area came to attain the standard.<FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>15</SU>Final 2012 emission reductions will not be known until early 2013 when fourth quarter emissions data is submitted by the facilities.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>16</SU>Data reflects reported actual emissions from the Clean Air Markets Division Database at<E T="03">http://ampd.epa.gov/ampd/</E>.</P>
        </FTNT>
        <GPOTABLE CDEF="s40,10,10,10,10" COLS="5" OPTS="L2,i1">
          <TTITLE>Table 2—Actual Emission Reductions From Coal Fired EGUs in the Huntington-Ashland Area for the Period 2005-2011<SU>16</SU>
          </TTITLE>
          <BOXHD>
            <CHED H="1">Facility—county</CHED>
            <CHED H="1">Emissions differences from 2005 to 2011 (tpy)</CHED>
            <CHED H="2">SO<E T="52">2</E>
            </CHED>
            <CHED H="2">Percent<LI>reduction</LI>
            </CHED>
            <CHED H="2">NO<E T="52">X</E>
            </CHED>
            <CHED H="2">Percent<LI>reduction</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">KY: Big Sandy—Lawrence County</ENT>
            <ENT>7,958</ENT>
            <ENT>16</ENT>
            <ENT>5,862</ENT>
            <ENT>47</ENT>
          </ROW>
          <ROW>
            <ENT I="22">WV:</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Mountaineer—Mason County</ENT>
            <ENT>40,972</ENT>
            <ENT>95</ENT>
            <ENT>10,395</ENT>
            <ENT>82</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Phil Sporn—Mason County</ENT>
            <ENT>28,334</ENT>
            <ENT>72</ENT>
            <ENT>6,896</ENT>
            <ENT>77</ENT>
          </ROW>
          <ROW>
            <ENT I="22">OH:</ENT>
          </ROW>
          <ROW>
            <ENT I="03">JM Stuart—Adams County</ENT>
            <ENT>97,784</ENT>
            <ENT>92</ENT>
            <ENT>16,662</ENT>
            <ENT>68</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Killen Station—Adams County</ENT>
            <ENT>11,845</ENT>
            <ENT>61</ENT>
            <ENT>2,353</ENT>
            <ENT>39</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Gen J M Gavin—Gallia County</ENT>
            <ENT>−5,299</ENT>
            <ENT>−19</ENT>
            <ENT>31,720</ENT>
            <ENT>82</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Kyger Creek—Gallia County</ENT>
            <ENT>−70,497</ENT>
            <ENT>−97</ENT>
            <ENT>9,144</ENT>
            <ENT>50</ENT>
          </ROW>
        </GPOTABLE>
        <GPOTABLE CDEF="s40,10,10,10,10" COLS="5" OPTS="L2,i1">
          <TTITLE>Table 3—Actual Emission Reductions From Coal Fired EGUs in the Huntington-Ashland Area for the Period 2005-2011, by State</TTITLE>
          <TDESC>[Emissions differences from 2005 to 2011 (tpy)]</TDESC>
          <BOXHD>
            <CHED H="1">State</CHED>
            <CHED H="1">SO<E T="52">2</E>
            </CHED>
            <CHED H="1">Percent<LI>reduction</LI>
            </CHED>
            <CHED H="1">NO<E T="52">X</E>
            </CHED>
            <CHED H="1">Percent<LI>reduction</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">KY</ENT>
            <ENT>7,958</ENT>
            <ENT>16</ENT>
            <ENT>5,862</ENT>
            <ENT>47</ENT>
          </ROW>
          <ROW>
            <ENT I="01">WV</ENT>
            <ENT>69,306</ENT>
            <ENT>84</ENT>
            <ENT>17,291</ENT>
            <ENT>80</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">OH</ENT>
            <ENT>33,833</ENT>
            <ENT>15</ENT>
            <ENT>59,878</ENT>
            <ENT>68</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Total</ENT>
            <ENT>111,097</ENT>
            <ENT>31</ENT>
            <ENT>83,030</ENT>
            <ENT>68</ENT>
          </ROW>
        </GPOTABLE>
        <P>
          <E T="03">Comment 1d:</E>The Commenter observes that Ohio cites the availability of cheap natural gas as one of the causes of attainment. The Commenter asserts that cheap natural gas is not a permanent and enforceable emissions limit, and states that because EPA has not determined whether the improvement in air quality was dependent on the presence of cheap natural gas, EPA must disapprove the redesignation request.</P>
        <P>
          <E T="03">Response 1d:</E>In determining that the improvement in air quality was due to permanent and enforceable emissions reductions, EPA did not cite or rely upon cheap natural gas as a permanent and enforceable limit. In its proposed rulemaking, EPA identified multiple permanent and enforceable measures (76 FR 79593), including, but not limited to Tier 2 vehicle standards, heavy-duty gasoline and diesel highway vehicle standards, nonroad spark-ignition engines and recreational engines standards, large nonroad diesel engine standards, consent decrees, CAIR, and the NO<E T="52">X</E>SIP Call. Permanent and enforceable measures set an enforceable limit, and the emission standard that must be met is independent of the choice of fuel. Further, as mentioned above, the large coal-fired electric generating units continued to run at or near the same amount over the years evaluated.</P>
        <P>
          <E T="03">Comment 2a:</E>The Commenter claims that “EPA has failed to conduct an adequate analysis under CAA section 110(l) on what effect redesignation will have on the 2006 24-hour PM<E T="52">2.5</E>NAAQS, the 1-hour NO<E T="52">X</E>NAAQS, the 1-hour SO<E T="52">2</E>NAAQS and the 1997 and 2008 75 parts per billion ozone NAAQS.” In subsequent comments, the Commenter also states, “EPA has not conducted an adequate analysis of the effect redesignation will have on other National Ambient Air Quality Standards”.</P>
        <P>
          <E T="03">Response 2a:</E>Section 110(l) provides in part: “the Administrator shall not approve a revision of a plan if the revision would interfere with any applicable requirement concerning attainment and reasonable further progress * * *, or any other applicable requirement of this chapter.” As a general matter, EPA is obligated under section 110(l) to consider whether a revision would “interfere with” attainment or applicable requirements. For example, 70 FR 53, 57 (January 3, 2005); 70 FR 17029, 17033 (April 4, 2005); 70 FR 28429, 28431 (May 18, 2005); and 70 FR 58119, 58134 (October 5, 2005). In its review, EPA has indeed considered its obligations under section 110(l). In acting on Ohio's redesignation request and maintenance plan for the 1997 annual PM<E T="52">2.5</E>NAAQS, Ohio did not revise or remove any existing emissions limit for any NAAQS, nor do they alter any existing control requirements. Thus, EPA concludes that<PRTPAGE P="76890"/>the redesignation will not interfere with attainment or maintenance of any other air quality standard. The Commenter provides no information in its comment to indicate that redesignation would have any impact on the area's ability to comply with the 2006 24-hour PM<E T="52">2.5</E>NAAQS, the 1-hour NO<E T="52">2</E>NAAQS, the 1-hour SO<E T="52">2</E>NAAQS or the 1997 8-hour ozone NAAQS and 2008 75 parts per billion ozone NAAQS. The redesignation does not relax any existing rules or limits, nor will it adversely alter the status quo air quality.<SU>17</SU>

          <FTREF/>In fact, the maintenance plan submitted by Ohio demonstrates a decline in the direct PM<E T="52">2.5</E>and PM<E T="52">2.5</E>precursor emissions over the timeframe of the maintenance period. EPA therefore concludes that there is no basis for concluding that the redesignation might interfere with attainment of any standard or with satisfaction of any other requirement, and thus EPA finds that section 110(l) does not prohibit EPA from approving the redesignation request and the maintenance SIP revision.</P>
        <FTNT>
          <P>

            <SU>17</SU>EPA notes that the Huntington-Ashland Area does not have violating monitors for the 2006 24-hour PM<E T="52">2.5</E>NAAQS, the 1-hour NO<E T="52">X</E>NAAQS, or the 1-hour SO<E T="52">2</E>NAAQS, the 1-hour and 8-hour ozone NAAQS, and that this Area has never been designated nonattainment for 2006 24-hour PM<E T="52">2.5</E>NAAQS, the 1-hour NO<E T="52">X</E>NAAQS, or the 1-hour SO<E T="52">2</E>NAAQS.</P>
        </FTNT>
        <P>
          <E T="03">Comment 2b:</E>The Commenter states that the Ohio SIP does not currently have RACT standards in place for PM<E T="52">2.5</E>, and that implementation of such standards would have reduced NO<E T="52">X</E>and SO<E T="52">2</E>, and helped with the 2006 24-hour PM<E T="52">2.5</E>NAAQS, the 1-hour NO<E T="52">X</E>NAAQS, the 1-hour SO<E T="52">2</E>NAAQS, and the 1997 and 2008 ozone NAAQS as well as visibility. The Commenter contends that EPA should demonstrate that the absence of this alleged co-benefit will not interfere with attainment, reasonable further progress and any other applicable requirement.”</P>
        <P>
          <E T="03">Response 2b:</E>EPA disagrees with the Commenter that the Ohio SIP does not comply with the applicable RACT requirements. EPA has previously set forth its interpretation of RACT for PM<E T="52">2.5</E>as linked to attainment needs of the area. If an area is attaining the PM<E T="52">2.5</E>standard, it clearly does not need further measures to reach attainment. Therefore, under EPA's interpretation of the RACT requirement, as it applies to PM<E T="52">2.5</E>, Ohio has satisfied the RACT requirement without need for further measures. EPA's memorandum of May 22, 2008, clarified and fully explained EPA's view of the relationship between PM<E T="52">2.5</E>attainment and RACT requirements. Memorandum from William T. Harnett, Director, Air Quality Policy Division to Regional Air Division Directors, entitled, “PM<E T="52">2.5</E>Clean Data Policy Clarification.”</P>

        <P>This memorandum explained that 40 CFR 51.1004(c) provides that a determination that an area has attained the PM<E T="52">2.5</E>standard suspends the requirements to submit RACT and Reasonably Achieved Control Measures (RACM) requirements.</P>
        <P>40 CFR 51.1010 provides in part: “For each PM<E T="52">2.5</E>nonattainment area, the state shall submit with the attainment  demonstration a SIP revision demonstrating that it has adopted all reasonably available control measures (including RACT for stationary sources) necessary to demonstrate attainment as expeditiously as practicable and to meet any Reasonable Further Progress (RFP) requirements.”</P>

        <P>Thus the regulatory text itself defines RACT as included in RACM, and provides that it is required only insofar as it is necessary to advance attainment. See also section 51.1010(b). Thus, EPA is correct in its conclusion here that the RACT requirement has been satisfied, and it does not result in interference with attainment or with other applicable requirements. The mere fact that EPA has correctly determined that the area meets the RACT requirements for the 1997 PM<E T="52">2.5</E>standard, and that thus no more is required under that standard, does not result in interference with attainment of other standards.</P>
        <P>The Commenter claims that<E T="03">Wall</E>v.<E T="03">EPA,</E>265 F.3d 426, 442 (6th Cir. 2001), establishes that fully adopted RACT is nonetheless required. The Wall case, however, is not applicable to RACT requirements for the PM<E T="52">2.5</E>standard. The Wall decision addressed entirely different statutory provisions for ozone RACT under CAA part D subpart 2, which do not apply or pertain to the subpart 1 RACT requirements for PM<E T="52">2.5</E>.</P>
        <P>
          <E T="03">Comment 2c:</E>The Commenter contends that it is inappropriate for EPA to redesignate the area to attainment at this time, claiming that EPA is illegally delaying issuing a final rule to revise the annual PM<E T="52">2.5</E>NAAQS, and that EPA's Clean Air Science Advisory Committee has recommended adoption of a lower NAAQS. The Commenter alleges that EPA is removing the protection of the 1997 NAAQS, while not adopting a more protective standard.</P>
        <P>
          <E T="03">Response 2c:</E>EPA finds that the concerns expressed by the Commenter are unfounded here. First, this redesignation does not remove the protection of the 1997 annual PM<E T="52">2.5</E>NAAQS; it does not relax control requirements or implementation for the 1997 NAAQS. Nor does the redesignation in any way address or affect the area's obligations under the new NAAQS. Its purpose and function is to focus solely on the 1997 annual PM<E T="52">2.5</E>NAAQS, and it has no impact on EPA's position with respect to requirements for the area under a revised NAAQS.</P>

        <P>Also, on December 14, 2012, EPA finalized a rule revising the PM<E T="52">2.5</E>annual standard to 12 μg/m<SU>3</SU>based on current scientific evidence regarding the protection of public health. EPA notes that the newly proposed standard is independent of this action, and the newly proposed standard does not affect the redesignation of the Huntington-Ashland area for the 1997 annual PM<E T="52">2.5</E>standard.</P>
        <P>
          <E T="03">Comment 3:</E>The Commenter asserts that “Emissions calculations for on-road mobile sources fail to consider 15% ethanol in gasoline (E15).”</P>
        <P>
          <E T="03">Response 3:</E>In 2010 and 2011, EPA granted partial waivers for use of E15 in model year (MY) 2001 and newer light-duty motor vehicles (75 FR 68094 and 76 FR 4662). As discussed in the waiver decisions, there may be some small emission impacts from the use of E15. E15 is expected to cause a small immediate emissions increase in NO<E T="52">X</E>emissions. However, due to its lower volatility than the 10% ethanol gasoline currently in-use, its use is also expected to result in lower evaporative emissions. Other possible emissions impacts may be from the misfueling of E15 in vehicles or engines for which its use is not approved, i.e., MY2000 and older motor vehicles, heavy-duty engines and vehicles, motorcycles and all nonroad engines, vehicles and equipment. EPA has promulgated a separate rule dealing specifically with the mitigation of misfueling to reduce the potential emissions impacts from misfueling (76 FR 44406).</P>
        <P>However, the E15 partial waivers do not require that E15 be made or sold and it is unclear if and to what extent E15 may even be used in Ohio. Even if E15 is introduced into commerce in Ohio, considering the likely small and offsetting direction of the emission impacts, the limited set of motor vehicles approved for its use, and the measures required to mitigate misfueling, EPA believes that any potential emission impacts of E15 will be less than the maintenance plan safety margin by which Ohio shows maintenance.</P>
        <P>
          <E T="03">Commment 4a:</E>The Commenter asserts that the Ohio maintenance plan is deficient in part because the contingency measures it includes provide for their implementation within 18 months of a monitored violation, if<PRTPAGE P="76891"/>one occurs. The Commenter claims that as a consequence, the “contingency measures do not provide for prompt correction of violations.”</P>
        <P>
          <E T="03">Response 4a:</E>The Commenter overlooks the provisions of the CAA applicable to contingency measures. Section 175A(d) provides that “[e]ach plan revision submitted under this section shall contain such contingency provisions as<E T="03">the Administrator deems necessary</E>to assure that the state will promptly correct any violation of the standard which occurs after the redesignation of the area as an attainment area.” (emphasis added). Thus Congress gave EPA discretion to evaluate and determine the contingency measures EPA “deems necessary” to assure that the state will promptly correct any subsequent violation. EPA has long exercised this discretion in its rulemakings on section 175A contingency measures in redesignation maintenance plans, allowing as contingency measures commitments to adopt and implement in lieu of fully adopted contingency measures, and finding that implementation<E T="03">within</E>18 months of a violation complies with the requirements of section 175A.<SU>18</SU>

          <FTREF/>See recent redesignations, e.g. Lake and Porter 8-hour ozone standard (75 FR 12090), and Northwest Indiana PM<E T="52">2.5</E>annual standard (76 FR 59600). Section 175A does not establish any deadlines for implementation of contingency measures after redesignation to attainment. It also provides far more latitude than does section 172(c)(9), which applies to a different set of contingency measures applicable to nonattainment areas. Section 172(c)(9) contingency measures must “take effect * * * without further action by the state or [EPA].” By contrast, section 175A confers upon EPA the discretion to determine what constitutes adequate assurance, and thus permits EPA to take into account the need of a state to assess, adopt implement contingency measures if and when a violation occurs after an area's redesignation to attainment. Therefore, in accordance with the discretion accorded it by statute, EPA may allow reasonable time for states to analyze data and address the causes and appropriate means of remedying a violation. In assessing what “promptly” means in this context, EPA also may take into account time for adopting and implementation of the appropriate measure. In the case of the Huntington-Ashland area, EPA reasonably concluded that 18 months constitutes a timeline consistent with prompt correction of a potential monitored violation. This timeframe also conforms with EPA's many prior rulemakings on acceptable schedules for implementing section 175A contingency measures.</P>
        <FTNT>
          <P>

            <SU>18</SU>See examples in recent redesignations, e.g. Lake and Porter County portion of Chicago 1997 8-hour ozone nonattainment area 75 FR 12090 May 11, 2010, and Lake and Porter County portion of Chicago 1997 PM<E T="52">2.5</E>annual standard 76 FR 59600, September 27, 2011.</P>
        </FTNT>
        <P>
          <E T="03">Comment 4b:</E>The Commenter asserts the maintenance plan does not demonstrate maintenance because EPA cannot rely on CSAPR to ensure maintenance in the Huntington-Ashland area.</P>
        <P>
          <E T="03">Response 4b:</E>EPA disagrees with the Commenter's assertion that the Huntington-Ashland area relies on CSAPR for maintenance. Ohio has used future emission reduction projects to meet the maintenance plan requirement under section 175A of the CAA, and has submitted a maintenance plan that extends 10 years past the redesignation. The Commenter improperly interprets EPA's references to CSAPR reductions in the proposal redesignation notice (found in Tables 5 and 6). EPA referred to CSAPR because Ohio had incorporated CAIR reductions in the emissions inventory, and that EPA believed at the time of proposal that CSAPR (which at the time had not yet been stayed) would allow for greater emission reductions both regionally and from local implementation than CAIR had provided. EPA therefore concluded in the proposal that the emission projections cited in Ohio's submittal were conservative, and still well below attainment year emissions. Since the proposal, CSAPR has been stayed; however, the emission reductions projected by Ohio, which were based on continued implementation of CAIR, in Ohio's maintenance plan are still valid and are significantly less than attainment year emissions. Ohio has met the requirements of 175A, without CSAPR in place.</P>

        <P>EPA also has modeling, included in the docket for this rulemaking, which projects that the Huntington-Ashland area will maintain the 1997 annual PM<E T="52">2.5</E>NAAQS without CSAPR or CAIR.<E T="03">See</E>appendix B to the Air Quality Modeling Final Rule Technical Support Document for CSAPR. The modeling analysis was a rigorous analysis using CAMx, a photochemical grid model which models PM<E T="52">2.5</E>concentrations arising both from direct PM<E T="52">2.5</E>emissions, as well as from formation from precursors (NO<E T="52">X</E>and SO<E T="52">2</E>) on a regional scale level. Extensive quality assurance and control measures, such as model calibration and sensitivity were taken into account. An in-depth discussion of the modeling is found in the docket. The analysis projected concentrations at current monitor locations for the Huntington-Ashland area using emissions inventories without CAIR and CSAPR for 2012 and 2014. Modeled results projected maximum concentrations of PM<E T="52">2.5</E>at 13.92 μg/m<SU>3</SU>(Lawrence County), and 13.26 μg/m<SU>3</SU>(Scioto County) for 2012. Those sites have current design values 2-3 μ/m<SU>3</SU>lower than the conservative modeled results. For the year 2014, EPA modeled maximum concentrations at these two sites as 13.32 and 12.71 μg/m<SU>3</SU>, respectively, without CAIR or CSAPR emission reductions.</P>

        <P>Further, Ohio's maintenance plan provides for verification of continued attainment by performing future reviews of triennial emissions inventories. It also includes contingency measures to ensure that the NAAQS is maintained into the future if monitored increases in ambient PM<E T="52">2.5</E>concentrations occur (76 FR 79593, December 22, 2012). For these reasons, EPA finds that Ohio has submitted a maintenance plan that meets the requirements of 107(d)(3)(E)(iv) and 175A.</P>
        <P>
          <E T="03">Comment 5:</E>The Commenter argues that due to certain start-up, shutdown and malfunction (SSM) provisions contained in the Ohio SIP, emission reductions in Ohio cannot be due to “permanent and enforceable reductions in emissions resulting from implementation of applicable implementation plan and Federal air pollutant control regulations and other permanent and enforceable reductions;” and the state cannot have met “all requirements applicable to the area under section 7410 of this title and part D of this subchapter,” citing 42 U.S.C. 7407(d)(3)(E). The Commenter points out that excess emissions from sources during SSM events may be subject to automatic or discretionary `exemption' under the Ohio SIP as currently constituted. The Commenter urges that Ohio's SSM regulations should be revised to “clearly comply” with the CAA and with EPA guidance (providing citations) such that all excess emissions are violations of the CAA, and to preserve the authority of EPA and citizens to enforce the SIP standards and limitations. The Commenter argues that these existing provisions in the Ohio SIP preclude redesignation of this area to attainment for the 1997 PM<E T="52">2.5</E>standards.</P>
        <P>
          <E T="03">Response 5:</E>EPA does not agree that the SSM provisions in the Ohio SIP provide a basis for disapproving the redesignation request for this area at this time. The provisions that the Commenter objects to are approved provisions of the Ohio SIP. As such, the<PRTPAGE P="76892"/>emission limits that contain the SSM provisions objected to by the Commenter are “permanent and enforceable” SIP provisions. The Commenter expresses concerns about certain exemptions for excess emissions within those existing provisions, but that does not affect whether the provisions are permanent and enforceable for purposes of redesignations. Similarly, the Commenter expresses concern that these existing provisions are not consistent with other requirements of the CAA, but as of this time those provisions are part of the approved Ohio SIP. EPA is in the process of addressing SSM provisions in the Ohio SIP through an on-going nationwide process, and in the event that EPA determines the provisions to be problematic, EPA can address them in that more appropriate context.</P>

        <P>The CAA sets forth the general criteria for redesignation of an area from nonattainment to attainment in section 107(d)(3)(E). These criteria include that the Administrator has fully approved the implementation plan for area for applicable requirements, 42 U.S.C. 7407(d)(3)(E)(ii)and (v). EPA must also determine that the improvement in air quality is due to reductions that are “permanent and enforceable” (iii), and that the area has an approved maintenance plan under section 175A. EPA has fully addressed all these criteria in its proposed and final rulemakings on the redesignation of the Ohio portion of the Huntington-Ashland Area. The SSM-related SIP provisions identified in the Commenter's letter are already approved, portions of the Ohio SIP, and EPA is not required to re-evaluate or revise them as part of this redesignation. EPA's review here is limited to whether the already approved SSM provisions impact any redesignation requirement in section 107(d)(3)(E), so as to preclude EPA from approving the redesignation request. There is no basis for EPA to conclude that these provisions have such effect. First, it has long been established that in approving a redesignation request EPA may rely on prior SIP approvals plus any additional measures it may approve in conjunction with a redesignation action. See John Calcagni Memorandum (September 4, 1992 at 3);<E T="03">Southwestern Pennsylvania Growth Alliance</E>v.<E T="03">Browner</E>, 144 F.3d 984, 989-990 (6th Cir. 1998);<E T="03">Wall</E>v.<E T="03">EPA</E>, 265 F.3d 426 (6th Cir. 2001); 68 FR 25413, 25426 (May 12, 2003).</P>
        <P>While the Commenter takes the position that specific SSM provisions in the Ohio rules result in a “regulatory structure that is inconsistent with the fundamental requirement that all excess emissions be considered violations,” the Commenter does not link this concern with any specific deficiencies in Ohio's redesignation submittal for the Huntington-Ashland Area.<SU>19</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>19</SU>The Commenter also cites the EPA action on a Utah SIP at 75 FR 70888, 70892 (Nov. 19, 2010) as a redesignation that was disapproved due to SSM provisions. However, this action was not a redesignation disapproval. That rulemaking was in fact a “Finding of Substantial Inadequacy of Implementation Plan; Call for Utah State Implementation Plan Revision”, otherwise known as a “SIP Call,” and not a redesignation.</P>
        </FTNT>
        <P>The Commenter expressed concerns that some specific existing SIP provisions contain exemptions for excess emissions such that the emission limits are not “permanent and enforceable” for purposes of section 107(d)(3)(E)(iii). EPA disagrees with this conclusion because the provisions are contained within the existing approved SIP and thus, in the context of 107(d)(3), are both “permanent and enforceable”. The Commenter may take issue with some features of those provisions, which contain automatic and discretionary exemptions for excess emissions, but these provisions, in the form in which they exist, are currently approved in the SIP and thus considered “permanent and enforceable”.</P>
        <P>EPA is in the process of evaluating SSM provisions in a separate context. While EPA understands that the Commenter wishes to raise concerns that about Ohio's existing SIP provisions with SSM exemptions, in the context of a redesignation action, EPA is not required to re-evaluate the validity of previously approved SIP provisions. In the context of a redesignation action, that generally a state has met the requirements of section 107(d)(3)(E)(ii) and (v), because the provisions have been previously approved into the SIP by EPA. If these provisions are later or separately determined to be deficient, such as compliance with other relevant requirements of the CAA, then EPA will be able to evaluate those concerns in the appropriate context. EPA notes that, in another, separate proceeding, EPA is in the process of evaluating similar comments relating to other SSM provisions.</P>

        <P>On June 30, 2011, Sierra Club filed a “Petition to Find Inadequate and Correct Several State Implementation Plans under section 110 of the Clean Air Act Due to Startup, Shutdown, Malfunction, and/or Maintenance Provisions”. As part of settlement of a lawsuit, EPA has agreed to take action in response to this petition. See<E T="03">Sierra Club et al.</E>v.<E T="03">Jackson,</E>No. 3:10-cv-04060-CRB (N.D. Cal). The comments regarding Ohio SSM provisions submitted in this redesignation action raise similar concerns to those identified by the petitioner in the Ohio-specific portion of the above-referenced petition. EPA is currently reviewing these Ohio SSM provisions as part of EPA's evaluation of the petition, and of other SSM provisions across the nation. Thus, EPA will be addressing those concerns in that separate action. EPA's redesignation of the Ohio portion Huntington-Ashland area to attainment for 1997 annual PM<E T="52">2.5</E>does not affect or preclude EPA from taking appropriate action on the from requiring the State of Ohio and other states to address excess emissions during SSM events correctly for purposes of CAA requirements in both nonattainment and attainment areas.</P>

        <P>At this time, with regard to the redesignation of the Ohio portion of the Huntington-Ashland area, Ohio has a fully approved SIP. The provisions to which the Commenter objects are permanent and enforceable, as those terms are meant in section 107(d)(3). In addition, the area has attained the annual PM<E T="52">2.5</E>standard since 2009, and has demonstrated that it can maintain the standard for at least ten years. EPA notes, moreover, that it is approving contingency measures under section 175A(d), as part of the area's maintenance plan. These measures provide assurance that the area can promptly correct a violation that might occur after redesignation. Finally, if, in the future, EPA concludes the provisions identified by the Commenter are problematic, EPA will be able to address that concern in a separate action.</P>
        <P>
          <E T="03">Comment 6a:</E>The Commenter contends that the Ohio SIP lacks required SIP provisions, asserting that section 172(c) of the CAA requires SIPs to include a RFP plan, a PM<E T="52">2.5</E>attainment demonstration, contingency measures, nonattainment New Source Review (NSR) rules, and RACM/RACT rules and that EPA has not approved these items into the Ohio SIP.</P>
        <P>
          <E T="03">Response 6a:</E>For a number of reasons, EPA disagrees with the Commenter's contentions that approvals of the cited measures is required for purposes of redesignation. First, pursuant to 40 CFR 51.1004(c), EPA's final determination that the Huntington-Ashland area has attained the PM<E T="52">2.5</E>standard suspended Ohio's obligation to submit attainment-related planning requirements that would otherwise apply, including an attainment demonstration, RFP, RACM/RACT, and contingency measures under section 172(c). The substance and legal basis of 40 CFR 51.1004(c), which<PRTPAGE P="76893"/>embodies EPA's interpretation under its “Clean Data Policy,” has been upheld by the D.C. Circuit Court.<E T="03">NRDC</E>v.<E T="03">EPA,</E>571 F.3d 1245 (D.C. Cir. 2009).<SU>20</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>20</SU>See also<E T="03">Sierra Club</E>v.<E T="03">EPA,</E>99 F. 3d 1551 (10th Cir. 1996);<E T="03">Sierra Club</E>v.<E T="03">EPA,</E>375 F.3d 537 (7th Cir. 2004); and<E T="03">Our Children's Earth Foundation</E>v.<E T="03">EPA,</E>No. 04-73032 (9th Cir. June 28, 2005) (memorandum opinion).</P>
        </FTNT>
        <P>Moreover, prior to the promulgation of 40 CFR 51.1004(c) the General Preamble for Implementation of Title I (57 FR 13498, April 16, 1992) addressed the role of attainment-related planning requirements in the specific context of EPA's consideration of a redesignation request. The General Preamble sets forth EPA's view of applicable requirements for purposes of evaluating redesignation requests when an area is attaining a standard (General Preamble for Implementation of Title I (57 FR 13498, April 16, 1992)).</P>
        <P>In the context of redesignations, EPA has interpreted requirements related to attainment as not applicable for purposes of redesignation.</P>
        <P>The General Preamble explains that, in the context of a redesignation to attainment, when EPA determines that attainment has been reached, no additional measures are needed to provide for attainment. Thus section 172(c)(1) requirements for an attainment demonstration and RACM are no longer considered to be applicable for purposes of redesignation as long as the area continues to attain the standard until redesignation. The RFP requirement under section 172(c)(2) and contingency measures requirement under section 172(c)(9) are similarly not relevant for purposes of redesignation. The General Preamble stated:</P>
        <EXTRACT>
          
          <P>[t]he section 172(c)(9) requirements are directed at ensuring RFP and attainment by the applicable date. These requirements no longer apply when an area has attained the standard and is eligible for redesignation. Furthermore, section 175A for maintenance plans * * * provides specific requirements for contingency measures that effectively supersede the requirements of section 172(c)(9) for these areas. “General Preamble for the Interpretation of Title I of the Clean Air Act Amendments of 1990,” (General Preamble) 57 FR 13498, 13564 (April 16, 1992).</P>
        </EXTRACT>
        
        <P>See also Calcagni memorandum at 6 (“The requirements for reasonable further progress and other measures needed for attainment will not apply for redesignations because they only have meaning for areas not attaining the standard.”). With respect to nonattainment NSR requirements, see EPA's response to Comment 6c, below.</P>
        <P>
          <E T="03">Comment 6b:</E>The Commenter contends that the Ohio SIP lacks approved contingency measures. The Commenter asserts that contingency measures must be in place so that, if an area monitor shows a violation of the NAAQS in the future, that violation of the NAAQS is quickly addressed, minimizing the number of people that will be harmed by air quality levels above the NAAQS.</P>
        <P>
          <E T="03">Response 6b:</E>As explained in the response to the previous comment (6a), the nonattainment area contingency measure requirements of section 172(c)(9) are directed at ensuring RFP and attainment by the applicable date. These nonattainment area requirements no longer apply after an area has attained the standard and after the area has been redesignated to attainment. Under section 175A of the CAA, a maintenance plan must contain contingency provisions, “as deemed necessary by the Administrator,” and it is these contingency measures that apply to the area after redesignation to attainment. Ohio has included such provisions in its maintenance plan, which EPA is approving in this action.</P>
        <P>Ohio has committed to remedy a future violation that may occur after redesignation, and has included measures to address potential violations from a range of sources, as well as a timeline for promptly completing adoption and implementation. The state has identified measures that are sufficiently specific but which allow for latitude in potential scope. EPA believes that the contingency measures set forth in the submittal, combined with the state's commitment to an expeditious timeline and process for implementation, provide assurance that the State will promptly correct a future potential violation. The contingency measures, as part of the maintenance plan, are codified into the state's SIP at the time the area is redesignated to attainment effective upon publication.</P>
        <P>
          <E T="03">Comment 6c:</E>The Commenter asserts that the Ohio SIP lacks a PM<E T="52">2.5</E>nonattainment NSR program. The Commenter also contends that the prevention of significant deterioration (PSD) program that is part of the SIP that an area being redesignated needs to ensure that the area will stay in attainment. The Commenter takes the position that EPA cannot approve the redesignation request because Ohio does not have an adequate PM<E T="52">2.5</E>PSD program. The Commenter bases his conclusion that Ohio's PSD program is inadequate for PM<E T="52">2.5</E>on the contention that the programs do not contain significant emission rates for PM<E T="52">2.5</E>and its precursors, and that the programs do not include PM<E T="52">2.5</E>increments.</P>
        <P>
          <E T="03">Response 6c:</E>Ohio has an approved nonattainment NSR program in its SIP. EPA approved Ohio's current NSR program on January 10, 2003 (68 FR 1366). Nonetheless, for purposes of evaluating a request for redesignation to attainment, because PSD requirements will apply after redesignation, EPA's longstanding view is that the area need not have a fully-approved nonattainment NSR program, provided that the area demonstrates maintenance of the NAAQS without part D NSR. A detailed rationale for this view is described in a memorandum from Mary Nichols, Assistant Administrator for Air and Radiation, dated October 14, 1994, entitled, “Part D New Source Review Requirements for Areas Requesting Redesignation to Attainment.” The memo states, “nonattainment areas may be redesignated to attainment notwithstanding the lack of a fully-approved part D NSR program, provided the program is not relied upon for maintenance.” In this case, Ohio has not relied upon NSR to maintain the standard.</P>

        <P>Congress used the undefined term “measure” differently in various provisions of the CAA, which indicates that the term is susceptible to more than one interpretation and that EPA has the discretion to interpret it in a reasonable manner in the context of section 175A. See<E T="03">Greenbaum</E>v.<E T="03">United States EPA,</E>370 F. 3d 527, 535-38 (6th Cir. 2004). (court “find[s] persuasive the EPA's argument that the very nature of the NSR permit program supports its interpretation that it is not intended to be a contingency measure pursuant to section 175A(d).”) It is reasonable to interpret “measure” to exclude part D NSR in this context because PSD, a program that is the corollary of part D NSR for attainment areas, goes into effect in lieu of part D NSR upon redesignation. PSD requires that new sources demonstrate that emissions from their construction and operation will not cause or contribute to a violation of any NAAQS or PSD increment. The state has demonstrated that the area will be able to maintain the standard without part D NSR in effect, and the state's PSD program will become effective in the area upon redesignation to attainment. See the rationale set forth at length in the Nichols Memorandum. For other explanations of why full approval and retention of NSR is not required in redesignation actions, see the following redesignation rulemakings: 60 FR 12459, 12467-12468 (March 7, 1995)(Redesignation of Detroit, MI); 61 FR 20458, 20469-20470 (May 7,<PRTPAGE P="76894"/>1996)(Cleveland-Akron-Lorrain, OH); 66 FR 53665, 53669 (October 23, 2001) (Louisville, KY); 61 FR 31831, 31836-31837 (June 21, 1996) (Grand Rapids, MI). Contrary to the Commenter's assertion, the<E T="03">Greenbaum</E>court declined to reach the issue of whether full approval of a part D NSR program is required prior to redesignation. See<E T="03">Greenbaum,</E>370 F. 3d at 534-35.</P>
        <P>Ohio also has an EPA approved PSD program that includes PM<E T="52">2.5</E>as a NSR pollutant. While the Commenter is correct in stating that both Ohio approved PSD SIPs do not include specific significant emissions rates for PM<E T="52">2.5</E>or its precursors, the Ohio SIP does include a provision that sets “any emission rate” as the significant emission rate for any regulated NSR pollutant that does not have a specific significant emission rate listed in the state rule.</P>
        <P>Therefore, any increase in direct PM<E T="52">2.5</E>emissions or emissions of its precursors (SO<E T="52">2</E>and NO<E T="52">X</E>) will trigger the requirements to obtain a PSD permit; to perform an air quality analysis that demonstrates that the proposed source or modification will not cause or contribute to a violation of the PM<E T="52">2.5</E>NAAQS; and to apply best available control technology for direct PM<E T="52">2.5</E>and/or the pertinent precursor.</P>
        <P>In addition, the fact that Ohio's approved PSD SIPs lack PM<E T="52">2.5</E>increments does not prevent the program from addressing and helping to assure maintenance of the PM<E T="52">2.5</E>standard in accordance with CAA section 175A. A PSD increment is the maximum increase in concentration that is allowed to occur above a baseline concentration for a pollutant. Even in the absence of an approved PSD increment, the approved PSD program prohibits air quality from deteriorating beyond the concentration allowed by the applicable NAAQS. Thus Ohio's approved PSD program is adequate for purposes of assuring maintenance of the 1997 annual PM<E T="52">2.5</E>standard as required by section 175A.</P>
        <P>
          <E T="03">Comment 6d:</E>The Commenter contends that the Ohio SIP does not have approved RACT rules.</P>
        <P>
          <E T="03">Response 6d:</E>This comment has been addressed above, in response 2b.</P>
        <P>
          <E T="03">Comment 6e:</E>The Commenter claims that 42 U.S.C. 7502(c)(7) requires that the nonattainment SIP meet all the requirements of 42 U.S.C. 7410(a)(2). EPA interprets this to mean only the Infrastructure elements that are linked to the nonattainment area. EPA's position contradicts the plain language of the statute. The Commenter also states that EPA says that it disapproved the Section 110(a)(2)(D)(i) portion of the Ohio Infrastructure submittal but did not take action on the rest of the September 4, 2009, submittal. 76 FR 79595. However, EPA did not explain what is included in the September 4, 2009, submittal and did not provide the September 4, 2009, submittal in the docket.</P>
        <P>
          <E T="03">Response 6e:</E>For a number of reasons, the concerns expressed by the Commenter are unfounded. First, EPA has issued final approvals of Ohio's infrastructure SIP for 1997 ozone and PM standards for all portions of 110(a) 2 requirements (76 FR 23757, April 28, 2011). EPA also acted on Ohio's submittal of the 2006 PM infrastructure SIP (proposed 76 FR 6376, February 4, 2011, finalized 76 FR 43175, July 20, 2011) where EPA disapproved the state's use of CAIR to fulfill the requirements of 110(a)2(D). EPA notes that there was an editorial error in the<E T="04">Federal Register</E>citation (but not the date of publication) of the 2006 infrastructure disapproval in the proposed redesignation; however, this has been fixed in the reference above, and a full submittal can be found in that docket. Even with this disapproval on February 4, 2011, the approval of the 1997 PM infrastructure elements on April 28, 2011, fulfills the “fully approved” SIP elements associated with redesignation, with exceptions unrelated to the requirements for redesignation.</P>

        <P>The requirements applicable for purposes of redesignation are those which at a minimum are linked to the attainment status of the area being redesignated. As noted in the proposal (76 FR 23757, April 28, 2011), all areas, regardless of their designation as attainment or nonattainment, are subject to section 110(a)(2)(D). The applicability of this provision is not connected with nonattainment plan submissions or with the attainment status of an area. A nonattainment area remains subject to the requirements of section 110(a)(2)(D) after it has been redesignated to attainment. Therefore EPA has long interpreted the 110(a)(2)(D) requirements as a not applicable requirement for purposes of redesignation. EPA has leeway to determine what constitutes an “applicable” requirement under section 107(d)(3)(E), and EPA's interpretation is entitled to deference.<E T="03">Sierra Club</E>v.<E T="03">EPA,</E>375 F.3d 537 (7th Cir. 2004). EPA has consistently interpreted only those section 110 requirements that are linked with a particular area's designation as the requirements to be considered in evaluating a redesignation request. See, e.g., EPA's position on the applicability of conformity, oxygenated fuels requirements for purposes of redesignations. See Reading, Pennsylvania, proposed and final rulemakings (61 FR 53174-53176, October 10, 1996, and 62 FR 24826, May 7, 1997); Cleveland-Akron-Lorain, Ohio, final rulemaking (61 FR 20458, May 7, 1996); and Tampa, Florida, final rulemaking (60 FR 62748, December 7, 1995). See also the discussion on this issue in the Cincinnati, Ohio 1-hour ozone redesignation (65 FR 37890, June 19, 2000), and in the Pittsburgh, Pennsylvania 1-hour ozone redesignation (66 FR 50399, October 19, 2001).</P>
        <P>
          <E T="03">Comment 7:</E>The Commenter contends that Ohio must restore an ambient air monitor to Lawrence County, in order to meet the monitoring network requirements.</P>
        <P>
          <E T="03">Response 7:</E>EPA disagrees with the Commenter that the monitoring network must restore a monitor in Lawrence County. Currently, Ohio operates a monitor in Lawrence County, the Ironton Department of Transportation (DOT) site monitor, and the monitoring network for the area has met and continues to meet monitoring network requirements. The Ironton DOT site address for the monitor in Lawrence County was moved to a location within 1.5 miles of the former site location (Lawrence County Hospital). The Lawrence County Hospital site was demolished on February 12, 2008, and a new site in the Lawrence County, Ohio portion of the Huntington-Ashland area, known as the Ironton DOT site, began operation on the same day. To date the Ironton DOT site has collected a complete design value for the monitoring period 2009-2011, which shows that the area continues to attain the 1997 annual standard. A full discussion of this aspect of the monitoring history is contained in the proposed determination of attainment for the Huntington-Ashland area (76 FR 27290, May 11, 2011).</P>
        <P>
          <E T="03">Comment 8:</E>The Commenter asserts that the 2005 emissions inventory that EPA is proposing to approve as meeting the emission inventory requirement of section 172(c)(3) of the CAA is inadequate and EPA cannot approve this emissions inventory. The Commenter notes that the emissions inventory is 6 years old. In addition, the commenter contends that portions of the emissions inventory were estimated, as opposed to being actual emissions, and claims that EPA has included in the docket only a summary of the emissions inventory. The Commenter asserts that EPA must place in the docket a comprehensive emissions inventory, including information for each point<PRTPAGE P="76895"/>source, so as to allow the public to review the inventory and comment on it.</P>
        <P>
          <E T="03">Response 8:</E>Ohio developed a 2005 comprehensive inventory to meet the requirement of section 172(c)(3) of the CAA in accordance with EPA's November 18, 2002, policy memorandum from Lydia N. Wegman entitled “2002 Base Year Emission Inventory SIP Planning: 8-hr Ozone, PM<E T="52">2.5</E>and Regional Haze Programs,”.</P>
        <P>The Commenter observes that portions of the emissions inventory were estimated. This method is entirely consistent with accepted EPA procedures for emissions inventory development procedures. It is common practice, and consistent with EPA emissions inventory guidance, for states to estimate emissions for any given year using related activity factors or to project emissions based on information from prior years and associated activity growth factors. See “Emissions Inventory Guidance for Implementation of Ozone and Particulate Matter National Ambient Air Quality Standards (NAAQS) and Regional Haze Regulations,” dated August 2005. For mobile sources, it is standard and accepted practice for states to estimate emissions using an EPA- approved emissions model coupled with the output of a transportation model, which provides traffic levels by roadway and activity type. The Commenter provided no information or specific details that show that the 2005 inventory was inaccurate.</P>
        <P>While we believe the 2005 inventory submitted by the state meets the inventory requirements section 172(c)(3) of the CAA, EPA notes that Ohio also submitted a comprehensive 2008 emissions inventory to serve as the attainment year inventory as part of the maintenance plan. EPA's longstanding view, as set forth in the September 4, 1992, Calcagni memorandum is that the “requirements for an emission inventory [under section 172(c)] will be satisfied by the inventory requirements of the maintenance plan.” See Calcagni memorandum at 6.</P>
        <P>When preparing the comprehensive 2008 emissions inventory, Ohio compiled point source information from the 2008 annual emissions reports submitted to Ohio EPA by sources and EPA's Clean Air Markets Division database for electric utilities. Area source emissions were calculated using the most recently available methodologies and emissions factors from EPA along with activity data (population, employment, fuel use, etc.) specific to 2008. Nonroad mobile source emissions were calculated using EPA's NONROAD emissions model. In addition, emissions estimates were calculated for commercial marine vessels, aircraft, and railroads, three non-road categories not included in the NONROAD model. On-road mobile source emissions were calculated using EPA's MOVES emissions model with 2008 Vehicle Miles Traveled data provided by the Tri-state planning agency KYOVA.</P>
        <P>Therefore, the state has satisfied the CAA inventory requirements by its submittal of two inventories that meet the applicable emissions inventory requirement.</P>

        <P>The docket associated with the proposal contained Ohio's submittal including appendix B, which contains the state's method and analysis of sources for the 2005 inventory year. The Clean Air Fine Particle Implementation Rule (72 FR 20586) states that the 3-year emissions inventory that fulfills the SIP requirement under 172(c)(3) must provide documentation on the development of the SIP inventory (appendix B of the proposal docket). The rule also states that all source types must be reported, but does not specify the resolution of the data reporting as a source by source report. Ohio has interpreted the source type reporting requirement as reported by county, which they have provided in their submittal. EPA also believes that its summary provided in the notice of proposed rulemaking, along with appendix B description of development, provides an adequate basis for the public to identify pertinent issues and evaluate EPA's analysis and conclusions regarding satisfaction of section 172(c)(3). Much of the information in Ohio's inventory also was used in EPA's National Emissions Inventory, which can be examined in considerable detail at<E T="03">http://www.epa.gov/ttn/chief/net/2008inventory.html</E>. EPA acknowledges that an in-depth inventory was unintentionally omitted from the electronic docket at<E T="03">www.regulations.gov</E>. However, the document was available to the public in hard copy at the EPA Region 5 office, and had the Commenter contacted the Region, the inventory could have been provided. The facility-specific inventory has since been added to the electronic docket.</P>
        <HD SOURCE="HD1">IV. Why is EPA taking these actions?</HD>

        <P>EPA has determined that the Huntington-Ashland area has continued to attain the 1997 annual PM<E T="52">2.5</E>NAAQS. EPA has also determined that all other criteria have been met for the redesignation of the Ohio portion of the Huntington-Ashland area from nonattainment to attainment of the 1997 annual PM<E T="52">2.5</E>NAAQS and for approval of Ohio's maintenance plan for the area.<E T="03">See</E>CAA sections 107(d)(3)(E) and 175A. The detailed rationale for EPA's findings and actions is set forth in the proposed rulemaking of December 22, 2011 (76 FR 79593) and in this final rulemaking.</P>
        <HD SOURCE="HD1">V. Final Action</HD>

        <P>EPA has previously made the determination that the Huntington-Ashland area has attained the 1997 annual PM<E T="52">2.5</E>standard (76 FR 55541). EPA is determining that the area continues to attain the standard and that the Ohio portion of the area meets the requirements for redesignation to attainment of that standard under sections 107(d)(3)(E) and 175A of the CAA. Thus, EPA is granting the request from Ohio to change the legal designation of its portion of the Huntington-Ashland area from nonattainment to attainment for the 1997 annual PM<E T="52">2.5</E>NAAQS. EPA is also approving Ohio's 1997 annual PM<E T="52">2.5</E>maintenance plan for the Huntington-Ashland area as a revision to the SIP because the plan meets the requirements of section 175A of the CAA. EPA is approving the 2005 and 2008 emissions inventories for primary PM<E T="52">2.5</E>, NO<E T="52">X</E>, and SO<E T="52">2</E>, documented in Ohio's May 4, 2011, submittals as satisfying the requirement in section 172(c)(3) of the CAA for a comprehensive, current emission inventory. Finally, for transportation conformity purposes, EPA is approving Ohio's determination that on-road emissions of PM<E T="52">2.5</E>and NO<E T="52">X</E>are insignificant contributors to PM<E T="52">2.5</E>concentrations in the area.</P>

        <P>In accordance with 5 U.S.C. 553(d), EPA finds there is good cause for this action to become effective immediately upon publication. This is because a delayed effective date is unnecessary due to the nature of a redesignation to attainment, which relieves the area from certain CAA requirements that would otherwise apply to it. The immediate effective date for this action is authorized under both 5 U.S.C. 553(d)(1), which provides that rulemaking actions may become effective less than 30 days after publication if the rule—grants or recognizes an exemption or relieves a restriction, and section 553(d)(3), which allows an effective date less than 30 days after publication—as otherwise provided by the agency for good cause found and published with the rule. The purpose of the 30-day waiting period prescribed in section 553(d) is to give affected parties a reasonable time to adjust their behavior and prepare before<PRTPAGE P="76896"/>the final rule takes effect. Today's rule, however, does not create any new regulatory requirements such that affected parties would need time to prepare before the rule takes effect. Rather, today's rule relieves the Ohio of various requirements for the Ohio portion of the Huntington-Ashland area. For these reasons, EPA finds good cause under 5 U.S. C. 553(d)(3) for this action to become effective on the date of publication of this action.</P>
        <HD SOURCE="HD1">VI. Statutory and Executive Order Reviews</HD>
        <P>Under the CAA, redesignation of an area to attainment and the accompanying approval of the maintenance plan under CAA section 107(d)(3)(E) are actions that affect the status of geographical area and do not impose any additional regulatory requirements on sources beyond those required by state law. A redesignation to attainment does not in and of itself impose any new requirements, but rather results in the application of requirements contained in the CAA for areas that have been redesignated to attainment. Moreover, the Administrator is required to approve a SIP submission that complies with the provisions of the Act and applicable Federal regulations. 42 U.S.C. 7410(k); 40 CFR 52.02(a). Thus, in reviewing SIP submissions, EPA's role is to approve state choices, provided that they meet the criteria of the CAA. Accordingly, this action merely approves state law as meeting Federal requirements and does not impose additional requirements beyond those imposed by state law. For these reasons, these actions:</P>
        <P>• Are not a “significant regulatory action” subject to review by the Office of Management and Budget under Executive Order 12866 (58 FR 51735, October 4, 1993);</P>

        <P>• Do not impose an information collection burden under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501<E T="03">et seq.</E>);</P>

        <P>• Are certified as not having a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601<E T="03">et seq.</E>);</P>
        <P>• Do not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4);</P>
        <P>• Do not have Federalism implications as specified in Executive Order 13132 (64 FR 43255, August 10, 1999);</P>
        <P>• Are not an economically significant regulatory action based on health or safety risks subject to Executive Order 13045 (62 FR 19885, April 23, 1997);</P>
        <P>• Are not significant regulatory action subject to Executive Order 13211 (66 FR 28355, May 22, 2001);</P>
        <P>• Are not subject to requirements of Section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) because application of those requirements would be inconsistent with the CAA; and,</P>
        <P>• Do not provide EPA with the discretionary authority to address, as appropriate, disproportionate human health or environmental effects, using practicable and legally permissible methods, under Executive Order 12898 (59 FR 7629, February 16, 1994).</P>
        <P>In addition, this final rule does not have tribal implications as specified by Executive Order 13175 (65 FR 67249, November 9, 2000), because the SIP is not approved to apply in Indian country located in the Commonwealth, and EPA notes that it will not impose substantial direct costs on tribal governments or preempt tribal law.</P>
        <P>The Congressional Review Act, 5 U.S.C. 801<E T="03">et seq.,</E>as added by the Small Business Regulatory Enforcement Fairness Act of 1996, generally provides that before a rule may take effect, the agency promulgating the rule must submit a rule report, which includes a copy of the rule, to each House of the Congress and to the Comptroller General of the United States. EPA will submit a report containing this action and other required information to the U.S. Senate, the U.S. House of Representatives, and the Comptroller General of the United States prior to publication of the rule in the<E T="04">Federal Register</E>. A major rule cannot take effect until 60 days after it is published in the<E T="04">Federal Register</E>. This action is not a “major rule” as defined by 5 U.S.C. 804(2).</P>

        <P>Under section 307(b)(1) of the CAA, petitions for judicial review of this action must be filed in the United States Court of Appeals for the appropriate circuit by March 1, 2013. Filing a petition for reconsideration by the Administrator of this final rule does not affect the finality of this action for the purposes of judicial review nor does it extend the time within which a petition for judicial review may be filed, and shall not postpone the effectiveness of such rule or action. This action may not be challenged later in proceedings to enforce its requirements. (<E T="03">See</E>section 307(b)(2).</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <CFR>40 CFR Part 52</CFR>
          <P>Environmental protection, Air pollution control, Incorporation by reference, Intergovernmental relations, Particulate matter.</P>
          <CFR>40 CFR Part 81</CFR>
          <P>Environmental protection, Air pollution control, National parks.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: December 18, 2012.</DATED>
          <NAME>Susan Hedman,</NAME>
          <TITLE>Regional Administrator, Region 5.</TITLE>
        </SIG>
        <P>40 CFR parts 52 and 81 are amended as follows:</P>
        <REGTEXT PART="52" TITLE="40">
          <PART>
            <HD SOURCE="HED">PART 52—[AMENDED]</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 52 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 7401<E T="03">et seq.</E>
            </P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">
          <AMDPAR>2. Section 52.1880 is amended by adding paragraphs (p)(2) and (q)(2) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 52.1880</SECTNO>
            <SUBJECT>Control strategy: Particulate matter.</SUBJECT>
            <STARS/>
            <P>(p) * * *</P>

            <P>(2) The Ohio portion of the Huntington-Ashland nonattainment area (Lawrence and Scioto Counties and portions of Adams and Gallia Counties). The maintenance plan establishes a determination of insignificance for both NO<E T="52">X</E>and primary PM<E T="52">2.5</E>for conformity purposes.</P>
            <P>(q) * * *</P>
            <P>(2) Ohio's 2005 and 2008 NO<E T="52">X</E>, directly emitted PM<E T="52">2.5</E>, and SO<E T="52">2</E>emissions inventory satisfies the emission inventory requirements of section 172(c)(3) for the Huntington-Ashland area.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="81" TITLE="40">
          <PART>
            <HD SOURCE="HED">PART 81—[AMENDED]</HD>
          </PART>
          <AMDPAR>3. The authority citation for part 81 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 7401<E T="03">et seq.</E>
            </P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="81" TITLE="40">

          <AMDPAR>4. Section 81.336 is amended by removing the entry for Huntington-Ashland, WV-KY-OH and adding in its place an entry for Huntington-Ashland, OH in the table entitled “Ohio PM<E T="52">2.5</E>(Annual NAAQS)” to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 81.336</SECTNO>
            <SUBJECT>Ohio.</SUBJECT>
            <STARS/>
            <PRTPAGE P="76897"/>
            <GPOTABLE CDEF="s75,12,12" COLS="3" OPTS="L2,i1">
              <TTITLE>Ohio PM<E T="52">2.5</E>(Annual NAAQS)</TTITLE>
              <BOXHD>
                <CHED H="1">Designated area</CHED>
                <CHED H="1">Designation<SU>a</SU>
                </CHED>
                <CHED H="2">Date<SU>1</SU>
                </CHED>
                <CHED H="2">Type</CHED>
              </BOXHD>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*******</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Huntington-Ashland, OH</ENT>
              </ROW>
              <ROW>
                <ENT I="03">Adams County (part)</ENT>
              </ROW>
              <ROW>
                <ENT I="05">Monroe Township</ENT>
              </ROW>
              <ROW>
                <ENT I="05">Sprigg Township</ENT>
              </ROW>
              <ROW>
                <ENT I="03">Gallia County (part)</ENT>
              </ROW>
              <ROW>
                <ENT I="05">Addison Township</ENT>
              </ROW>
              <ROW>
                <ENT I="05">Cheshire Township</ENT>
              </ROW>
              <ROW>
                <ENT I="03">Lawrence County</ENT>
              </ROW>
              <ROW>
                <ENT I="03">Scioto County</ENT>
                <ENT>12/31/12</ENT>
                <ENT>Attainment.</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*******</ENT>
              </ROW>
              <TNOTE>
                <SU>a</SU>Includes Indian Country located in each county or area, except as otherwise specified.</TNOTE>
              <TNOTE>
                <SU>1</SU>This date is 90 days after January 5, 2005, unless otherwise noted.</TNOTE>
            </GPOTABLE>
            <STARS/>
          </SECTION>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31276 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <CFR>40 CFR Parts 9 and 721</CFR>
        <DEPDOC>[EPA-HQ-OPPT-2011-0941; FRL-9369-8]</DEPDOC>
        <RIN>RIN 2070-AB27</RIN>
        <SUBJECT>Significant New Use Rule on Certain Chemical Substances; Removal of Significant New Use Rules</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>EPA is removing significant new use rules (SNURs) promulgated under the Toxic Substances Control Act (TSCA) for four chemical substances which were the subject of premanufacture notices (PMNs). EPA published these SNURs using direct final rulemaking procedures. EPA received notice of intent to submit adverse comments on these rules. Therefore, the Agency is removing these SNURs, as required under the expedited SNUR rulemaking process. EPA intends to publish in the near future proposed SNURs for these four chemical substances under separate notice and comment procedures.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This final rule is effective December 31, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>
            <E T="03">For technical information contact:</E>Kenneth Moss, Chemical Control Division (7405M), Office of Pollution Prevention and Toxics, Environmental Protection Agency, 1200 Pennsylvania Ave. NW., Washington, DC 20460-0001; telephone number: (202) 564-9232; email address:<E T="03">Moss.Kenneth@epa.gov.</E>
          </P>
          <P>
            <E T="03">For general information contact:</E>The TSCA-Hotline, ABVI-Goodwill, 422 South Clinton Ave. Rochester, NY 14620; telephone number: (202) 554-1404; email address:<E T="03">TSCA-Hotline@epa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Does this action apply to me?</HD>
        <P>A list of potentially affected entities is provided in the<E T="04">Federal Register</E>of September 21, 2012 (77 FR 58666) (FRL-9357-2). If you have questions regarding the applicability of this action to a particular entity, consult the technical person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>.</P>
        <HD SOURCE="HD1">II. What rules are being removed?</HD>
        <P>In the<E T="04">Federal Register</E>of September 21, 2012 (77 FR 58666), EPA issued several direct final SNURs, including SNURs for the chemical substances that are the subject of this removal. These direct final rules were issued pursuant to the procedures in 40 CFR part 721, subpart D. In accordance with § 721.160(c)(3)(ii), EPA is removing these rules issued for four chemical substances which were the subject of PMNs P-07-204, P-10-58, P-10-59, and P-10-60, because the Agency received notice of intent to submit adverse comments without sufficient time to respond prior to the effective date of the rules. EPA intends to publish proposed SNURs for these chemical substances under separate notice and comment procedures.</P>

        <P>For further information regarding EPA's expedited process for issuing SNURs, interested parties are directed to 40 CFR part 721, subpart D, and the<E T="04">Federal Register</E>of July 27, 1989 (54 FR 31314). The record for the direct final SNURs for the chemical substances that are being removed was established at EPA-HQ-OPPT-2011-0941. That record includes information considered by the Agency in developing this rule and the notice of intent to submit adverse comments.</P>
        <HD SOURCE="HD1">III. How do I access the docket?</HD>
        <P>To access the electronic docket, please go to<E T="03">http://www.regulations.gov</E>and follow the online instructions to access docket ID number EPA-HQ-OPPT-2011-0941. Additional information about the Docket Facility is provided under<E T="02">ADDRESSES</E>in the<E T="04">Federal Register</E>of September 21, 2012 (77 FR 58666). If you have questions, consult the technical person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>.</P>
        <HD SOURCE="HD1">IV. Statutory and Executive Order Reviews</HD>

        <P>This final rule removes existing regulatory requirement and does not contain any new or amended requirements. As such, the Agency has determined that this removal will not have any adverse impacts, economic or otherwise. The statutory and executive order review requirements applicable to the direct final rule were discussed in the<E T="04">Federal Register</E>of September 21, 2012 (77 FR 58666). Those review requirements do not apply to this action because it is a removal and does not contain any new or amended requirements.</P>
        <HD SOURCE="HD1">V. Congressional Review Act (CRA)</HD>
        <P>The Congressional Review Act, 5 U.S.C. 801<E T="03">et seq.,</E>generally provides that before a rule may take effect, the agency promulgating the rule must submit a rule report, which includes a copy of the rule, to each House of the Congress and to the Comptroller General<PRTPAGE P="76898"/>of the United States. EPA will submit a report containing this rule and other required information to the U.S. Senate, the U.S. House of Representatives, and the Comptroller General of the United States prior to publication of the rule in the<E T="04">Federal Register</E>. This rule is not a “major rule” as defined by 5 U.S.C. 804(2).</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <CFR>40 CFR Part 9</CFR>
          <P>Environmental protection, Reporting and recordkeeping requirements.</P>
          <CFR>40 CFR Part 721</CFR>
          <P>Environmental protection, Chemicals, Hazardous substances, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: December 17, 2012.</DATED>
          <NAME>Maria J. Doa,</NAME>
          <TITLE>Director, Chemical Control Division, Office of Pollution Prevention and Toxics.</TITLE>
        </SIG>
        <P>Therefore, 40 CFR parts 9 and 721 are amended as follows:</P>
        <REGTEXT PART="9" TITLE="40">
          <PART>
            <HD SOURCE="HED">PART 9—[AMENDED]</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 9 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>7 U.S.C. 135<E T="03">et seq.,</E>136-136y; 15 U.S.C. 2001, 2003, 2005, 2006, 2601-2671; 21 U.S.C. 331j, 346a, 348; 31 U.S.C. 9701; 33 U.S.C. 1251<E T="03">et seq.,</E>1311, 1313d, 1314, 1318, 1321, 1326, 1330, 1342, 1344, 1345(d) and (e), 1361; E.O. 11735, 38 FR 21243, 3 CFR, 1971-1975 Comp. p. 973; 42 U.S.C. 241, 242b, 243, 246, 300f, 300g, 300g-1, 300g-2, 300g-3, 300g-4, 300g-5, 300g-6, 300j-1, 300j-2, 300j-3, 300j-4, 300j-9, 1857<E T="03">et seq.,</E>6901-6992k, 7401-7671q, 7542, 9601-9657, 11023, 11048.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="9" TITLE="40">
          <SECTION>
            <SECTNO>§ 9.1</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. The table in § 9.1 is amended by removing the entries “§ 721.10509” and “§ 721.10515” under the undesignated center heading “Significant New Uses of Chemical Substances.”</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <PART>
            <HD SOURCE="HED">PART 721—[AMENDED]</HD>
          </PART>
          <AMDPAR>3. The authority citation for part 721 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>15 U.S.C. 2604, 2607, and 2625(c).</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <SECTION>
            <SECTNO>§ 721.10509</SECTNO>
            <SUBJECT>[Removed]</SUBJECT>
          </SECTION>
          <AMDPAR>4. Remove § 721.10509.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="721" TITLE="40">
          <SECTION>
            <SECTNO>§ 721.10515</SECTNO>
            <SUBJECT>[Removed]</SUBJECT>
          </SECTION>
          <AMDPAR>5. Remove § 721.10515.</AMDPAR>
        </REGTEXT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31403 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <CFR>43 CFR Part 2</CFR>
        <RIN>RIN 1093-AA15</RIN>
        <SUBJECT>Freedom of Information Act Regulations</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of the Secretary, Interior.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This rule revises the regulations that the Department of the Interior (the “Department”) follows in processing records under the Freedom of Information Act (“FOIA”). The revisions clarify and update procedures for requesting information from the Department and procedures that the Department follows in responding to requests from the public. The revisions also incorporate clarifications and updates resulting from changes to the FOIA and case law. Finally, the revisions include current cost figures to be used in calculating and charging fees and increase the amount of information that members of the public may receive from the Department without being charged processing fees.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Effective January 30, 2013.</P>
        </DATES>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Why We're Publishing This Rule and What It Does</HD>
        <HD SOURCE="HD2">A. Introduction</HD>
        <P>The regulations are being revised to update, clarify, and streamline the language of procedural provisions, and to incorporate certain changes brought about by the amendments to the FOIA under the OPEN Government Act of 2007, Public Law 110-175, 121 Stat. 2524. Additionally, the regulations are being updated to reflect developments in the case law and to include current cost figures to be used in calculating and charging fees.</P>
        <P>The revisions also incorporate changes to the language and structure of the FOIA regulations in order to improve the Department's FOIA performance. More nuanced multitrack processing can be found at § 2.15. Partial fee waivers are expressly permitted under § 2.45. Revisions of the Department's fee schedule can be found at §§ 2.42, 2.49(a)(1), and Appendix A. The duplication charge for physical records or scanning records increased from thirteen to fifteen cents a page. The amount at or below which the Department will not charge a fee increased from $30.00 to $50.00.</P>

        <P>On September 13, 2012, the Department published a proposed rule in the<E T="04">Federal Register</E>(77 FR 56592) and requested comments over a 60-day period ending on November 13, 2012. All comments received were considered in drafting this final rule.</P>
        <HD SOURCE="HD2">B. Discussion of Comments</HD>
        <P>Six commenters responded to the invitation for comments, including one commenter from a subcomponent of a Federal agency and five commenters from non-Federal sources. While most of the commenters generally supported the proposed changes, they identified thirty specific issues or recommendations, which the Department addressed as follows:</P>
        <HD SOURCE="HD3">The Final Rule Should Include More Information in Its Introductory Section</HD>
        <P>One commenter suggested that § 2.1 discuss how to submit a FOIA request (and also expressed concern that the regulations might only allow FOIA requests to be submitted to the Department electronically). Because § 2.3 directly addresses where to send a FOIA request (and specifically discusses where to find the physical and email addresses of each bureau's FOIA Officer), the Department has not adopted this suggestion.</P>
        <HD SOURCE="HD3">The Final Rule Should Not Create Unnecessary Burdens for Requesters</HD>
        <P>One commenter suggested that requiring requesters to “write directly to the bureau that you believe maintains those records” in § 2.3(b) was overly burdensome and creates barriers to access, because requesters may not know where the records are maintained. However, § 2.3(d) specifically notes that “[q]uestions about where to send a FOIA request should be directed to the bureau that manages the underlying program or to the appropriate FOIA Public Liaison, as discussed in § 2.66.” Therefore, the Department does not believe § 2.3 is unduly burdensome and has not amended it.</P>
        <HD SOURCE="HD3">The Final Rule Should Provide Examples of How Requesters Can Reasonably Describe the Records They Seek</HD>
        <P>One commenter suggested that examples of how requesters can reasonably describe the records they seek be added to § 2.5(b), and the Department has adopted this suggestion.</P>
        <HD SOURCE="HD3">The Final Rule Should Not Use the Ambiguous Phrase “Does Not Hear From You”</HD>

        <P>One commenter suggested, in the context of § 2.5, that the use of “does not hear from you” was ambiguous. The Department has adopted this suggestion<PRTPAGE P="76899"/>by replacing the ambiguous phrase with “does not receive a written response from you” everywhere it occurred (§§ 2.5, 2.6, and 2.51).</P>
        <HD SOURCE="HD3">The Final Rule Should Allow Requesters More Time To Respond to the Department's Communications and Make Advance Payments</HD>
        <P>One commenter suggested that the time for requesters to respond to the Department in §§ 2.5(c), 2.6(c), and 2.50(e) be expanded from 20 workdays (the time period in the draft version of the final rule, as well as in the Department's previous version of the final rule) to 30 workdays. As the commenter notes, the Department does “expend[] numerous resources to produce documents pursuant to the FOIA, and the agency has an interest in resolving FOIA matters in an organized and timely fashion.” Although the commenter believes the 20 workday deadline is “unreasonable and arbitrary,” it has been the standard for the Department for over a decade and the Department believes that it is reasonable and comports with the statutory FOIA processing deadlines. The Department therefore declines to adopt this suggestion.</P>
        <HD SOURCE="HD3">The Final Rule Should Require the Department To Notify Requesters in Advance Before Charging Them the Direct Costs of Converting Records to the Format They Request</HD>
        <P>One commenter suggested § 2.8(b) be revised to require a bureau to inform requesters in advance if it intends to charge the requester any direct costs for converting the requested records into a requested format. The Department has adopted this suggestion by adding a cross reference to § 2.44 and adding this scenario to the examples given in § 2.44(b).</P>
        <HD SOURCE="HD3">The Final Rule Should Not Confuse Expedited Processing Requests and FOIA Requests</HD>
        <P>One commenter suggested that the juxtaposition of §§ 2.10 and 2.11 could lead to confusion about what kinds of “requests” were being referenced in these sections. The Department agrees and has adopted this suggestion by amending § 2.10.</P>
        <HD SOURCE="HD3">The Final Rule Should Elaborate on the Department's Consultation and Referral Process</HD>
        <P>One commenter suggested that, in § 2.13(c) and (e), the Department notify requesters of whether part of the request or entire request has been referred, and the Department has adopted this suggestion. The same commenter also suggested that the Department provide the requester with the contact information (in addition to the name) of the person the request had been referred to, and the Department has adopted this suggestion. Another commenter expressed concerns about § 2.13, stating that portions of it were “ambiguous and have no legal basis.” This commenter specified that § 2.13(e) permitted the Department to withhold the identity of outside agencies to which the Department refers FOIA requests, under limited circumstances, and §§ 2.13(f)(2) and 2.13(f)(4) did not have concrete examples. The Department has carefully reviewed § 2.13(e) and finds it to be unambiguous and consistent with law and policy. The Department has also concluded that adding examples to §§ 2.13(f)(2) and 2.13(f)(4) would not be beneficial, as the situations that will arise under these sections are highly fact specific and general examples would be bulky and would not be illuminating. However, the Department agrees that the previous versions of §§ 2.13(a) and 2.13(h) were unintentionally confusing. The Department therefore has adopted this suggestion in part and revised these sections for clarity.</P>
        <HD SOURCE="HD3">The Final Rule Should Not Expand the Time Period for Determining Whether the Department Will Comply With a Request</HD>
        <P>One commenter suggested that the multiple tracks for processing FOIA requests outlined in § 2.15 violated FOIA's requirement that agencies “determine within 20 days [or longer in unusual circumstances] * * * after the receipt of any [FOIA] request whether to comply with such request * * * ” 5 U.S.C. 552(a)(6)(A). However, § 2.15 does not alter the statutory requirement for a bureau to determine whether it will comply with a request. To the contrary, it implements 5 U.S.C. 552(a)(6)(D)(i), which specifically permits agencies to promulgate regulations “providing for multitrack processing of requests for records based on the amount of work or time (or both) involved in processing requests.” This provision of the FOIA recognizes that a bureau exercising due diligence can determine whether it will comply with a request within the statutory timeframe, but may need additional time to search for and process the records in question. It also recognizes that simple requests should not have to wait for long periods of time while more complex requests are processed. To clarify this point, the Department has added paragraph (f) to this section. (The Department has also corrected a typographical error in § 2.15(c)(3) that may have created confusion about processing times.) The same commenter also suggested the definition of “review” in § 2.70 would violate FOIA's mandated time limits. However, the definition addresses when fees will be charged to a requester, not how long a bureau has to respond to a FOIA request. Neither § 2.15 nor § 2.70 expands the time period for determining whether to comply with a request and therefore neither have been amended.</P>
        <HD SOURCE="HD3">The Final Rule Should Help Set Requesters' Expectations of When To Expect a Response</HD>
        <P>One commenter suggested a clause and a sentence be added to § 2.16(a) referring to the potential of a 10-day extension, to help set the requester's expectations of when to expect a response. The Department has adopted the suggestion to refer to the potential extension, but consolidated the suggested language. The final rule already has a provision discussing when the bureau may extend the basic time limit (§ 2.19) and a cross reference to it has been added to § 2.16(a). The Department has also amended § 2.16(a) to more exactly track the language of 5 U.S.C. 552(a)(6)(A)(i).</P>
        <HD SOURCE="HD3">The Final Rule Should Not Exceed the FOIA's Temporary Suspension Authority</HD>
        <P>One commenter expressed concern that the provisions in § 2.18(b) exceeded the FOIA's provisions for temporarily suspending the statutory response period because a temporary suspension was allowed to occur more than once if the bureau needed to clarify issues regarding fee assessments. However, 5 U.S.C. 552(a)(6)(A) makes it clear that, although a temporary suspension can occur only once when a bureau is reasonably asking for clarifying information unrelated to fee assessments (and the temporary suspension ends with a requester's response), temporary suspensions of the statutory response period can occur as many times as is necessary when a bureau needs clarifying information regarding a fee assessment. This section therefore does not exceed FOIA's temporary suspension authority and has not been amended.</P>
        <HD SOURCE="HD3">The Final Rule Should Require the Department To Include a Brief Description of the Subject of the Request in Acknowledgement Letters</HD>

        <P>One commenter suggested that the Department add a clause to § 2.21(b) requiring bureaus to provide a brief description of the subject of the request in its acknowledgment letter. The<PRTPAGE P="76900"/>Department declines to adopt the portion of the suggestion about making this description mandatory, due to the increased burden it would place on bureaus (especially those with a high rate of FOIA requests) and the dampening effect this would have on experimenting with new forms of written acknowledgments that could more quickly serve requesters (such as post cards). The Department has, however, added a sentence to § 2.21(b) noting this information may be included.</P>
        <HD SOURCE="HD3">The Final Rule Should Clarify When Procedural Benefits Are Denied Versus When Records Are Denied</HD>
        <P>A commenter suggested modifying § 2.23 to clarify when a request is being denied as opposed to the denial of procedural benefits under FOIA. The Department agrees this would be helpful and has made the suggested modifications, along with a few minor clarifications. The Department also made a minor change to paragraph (a)(3) of this section because a some material that had previously been included in § 2.13(h), amendments to which were discussed above, made more sense in this context.</P>
        <HD SOURCE="HD3">The Final Rule Should Require the Department to State the Precise Volume of Denied Material and Provide a Detailed Justification of Its Withholdings</HD>
        <P>One commenter suggested § 2.24 be amended to state that, where possible, the requester will be provided with the precise volume of denied material, rather than an estimated volume. Although the Department has declined to adopt this exact suggestion (because it believes the change would have a significant negative impact on the Department's processing and response times while providing the requester with very little, if any, additional, meaningful information), it has amended § 2.25 to more exactly track the language of 5 U.S.C. 552(b), which the commenter referenced. Another commenter suggested § 2.24 be amended to require “a detailed justification for [a] denial,” citing case law requiring detailed justifications in a litigation context. The Department has considered this suggestion, but declined to adopt it because it is not required at an administrative level and would have a tremendous negative impact on the Department's processing and response times.</P>
        <HD SOURCE="HD3">The Final Rule Should Correctly State What Types of Information Can Be Protected Under the Trade Secrets Act</HD>

        <P>One commenter suggested that § 2.36 be amended to state that only trade secrets can be withheld under the Trade Secrets Act, 18 U.S.C. 1905. However, the Trade Secrets Act is a broadly worded criminal statute that prohibits the unauthorized disclosure of more than simply “trade secrets.”<E T="03">See, e.g., Bartholdi Cable Co.</E>v.<E T="03">FCC,</E>114 F.3d 274, 281 (D.C. Cir. 1997) (citing<E T="03">CAN Fin. Corp</E>v.<E T="03">Donovan,</E>830 F.2d 1132, 1140 (D.C. Cir. 1987) and declaring: “[W]e have held that information falling within Exemption 4 of FOIA also comes within the Trade Secrets Act.”);<E T="03">Parker</E>v.<E T="03">Bureau of Land Mgmt.,</E>141 F. Supp. 2d 71, 77 n.5 (D.D.C. 2001) (“Although FOIA exemptions are normally permissive rather than mandatory, the D.C. Circuit has held that the disclosure of material which is exempted under [Exemption 4 of the FOIA] is prohibited under the Trade Secrets Act”). This section therefore has not been amended.</P>
        <HD SOURCE="HD3">The Final Rule Should Reflect Three Fee Categories, Rather Than Four</HD>
        <P>One commenter suggested that §§ 2.38 and 2.70 be amended to reflect that the FOIA provides for three fee categories, not four. While the Department agrees that only three categories are referred to in the FOIA, it has found over many years that requesters appreciate and benefit from the additional clarity provided by having one of the broader categories split in two. The Department therefore has not adopted this suggestion.</P>
        <HD SOURCE="HD3">The Final Rule Should Use Individualized Local Locality Payments</HD>
        <P>One commenter suggested that § 2.41(b) be amended from “the fees will be the average hourly General Schedule (“GS”) base salary, plus the District of Columbia locality payment” to “the fees will be the average hourly General Schedule (“GS”) base salary, plus any applicable locality payment.” The Department utilized the District of Columbia (“DC”) locality payments as its standardized locality payment in its previous version of the final rule and found it to be both efficient and reasonable. It allows the Department to create a standard chart that all bureaus can use to calculate fees, rather than each bureau calculating different amounts for different employees (in the Department, it is not unusual for people who work on the same request to be in multiple geographic locations) and requesters being confused by widely varying charges for the same work. It makes sense to use the DC locality as the standard, given the large numbers of the Department's FOIA professionals and processors that are based in DC The Department therefore has not adopted this suggestion.</P>
        <HD SOURCE="HD3">The Final Rule Should Not Unduly Limit Agency Decisions on Fee Waivers and Appeals</HD>
        <P>One commenter suggested that § 2.45(c) unduly limits bureau decisions on fee waivers and this would negatively impact appeal decisions under § 2.57. However, § 2.45(c) merely allows a bureau to make fee waiver decisions based on what is submitted to it by the requester, rather than being required to seek additional information (although it is free to do so, at its discretion). The Department therefore has not amended these sections.</P>
        <HD SOURCE="HD3">The Final Rule Should Further Clarify When Fees May Be Waived</HD>
        <P>One commenter suggested adding the following sentence to § 2.45(d) in order to further assist the Department in setting expectations for requesters regarding fee waivers: “A fee waiver is tied to the subject of the request in addition to the identity of the requester.” The Department is concerned that adopting this suggestion would give the mistaken impression that only these two criteria are at issue in fee waiver determinations. But, in response to this comment, § 2.45(d) now includes two cross references. These cross references, to the fee waiver criteria in §§ 2.45(a) and 2.48, will help set requesters' expectations regarding fee waivers.</P>
        <HD SOURCE="HD3">The Final Rule Should Say More About Where and How To File a Fee Waiver</HD>
        <P>One commenter suggested that § 2.46 discuss where and how to file a fee waiver request. Because § 2.6 directly addresses where and how to file fee waiver requests (and § 2.46 already cross references § 2.6), the Department believes adopting this suggestion is not necessary.</P>
        <HD SOURCE="HD3">The Final Rule Should Not Be Narrower than FOIA's Fee Waiver Standards</HD>

        <P>One commenter expressed concern that § 2.48(a)(4), which outlines one of the four criteria bureaus are asked to consider when evaluating a fee waiver request, was narrower than FOIA's fee waiver standards. However, this provision does not narrow the scope of 5 U.S.C. 552(a)(4)(A)(iii), it simply helps the Department analyze whether the disclosure of the information is likely to contribute significantly to public understanding of the operations or<PRTPAGE P="76901"/>activities of the government. Because § 2.48(a)(4) is not narrower than FOIA's fee waiver standards, the Department has not adopted this suggestion. The same commenter also expressed concern about a change of phrasing in § 2.48(a)(3)(iv) from the parallel provision in the previous version of the final rule. The Department did not intend to change the provision's meaning. Therefore, in accordance with the commenter's suggestion, the word “unlikely” has been removed and the phrase “less likely” restored.</P>
        <HD SOURCE="HD3">The Final Rule Should Require the Department to Allow Requesters To Pay in Installments</HD>
        <P>One commenter suggested that § 2.50(e) be amended to require the Department to “collaborate with FOIA requesters to establish a payment schedule that would permit requesters to pay [advance payments] in installments instead of closing out requests.” As the commenter notes, this provision mirrors the applicable provision in the previous version of the final rule. Changing it would greatly add to the complexity, uncertainty, and time spent processing advance fee payments, impairing the Department's FOIA processing. The Department therefore declines to adopt this suggestion.</P>
        <HD SOURCE="HD3">The Final Rule Should Clearly Articulate its Rationale for Combining or Aggregating Requests</HD>
        <P>One commenter suggested the Department should articulate its rationale for combining or aggregating requests more clearly in § 2.54. The Department agrees the previous version of this section was unintentionally confusing. The lettering/numbering therefore has been amended. Additionally, a “will” in § 2.54(a)(2) has been amended to “may.”</P>
        <HD SOURCE="HD3">The Final Rule Should Provide Examples of Types of Records the Department May Charge Fees for Outside the Scope of FOIA</HD>
        <P>One commenter suggested it may be helpful to include examples of the particular types of records that a bureau may charge fees for outside of the scope of the FOIA in § 2.55. The Department has carefully considered this suggestion and has concluded that examples in this area would be so specific and narrow that they would be more distracting than illuminating. The Department therefore has not adopted this suggestion.</P>
        <HD SOURCE="HD3">The Final Rule Should Allow Bureaus Not Only To Waive Fees Discretionarily, But Also To Reduce them Discretionarily</HD>
        <P>One commenter suggested that § 2.56 be amended to allow for the discretionary reduction of fees (in addition to the discretionary waiver of fees) and the Department has adopted this suggestion. The same commenter also suggested that new language be added to give Department employees additional, broader discretion for waiving or reducing fees, for example, whenever “the interest of the United States Government would be served.” The Department has declined to adopt this suggestion, because it is concerned that it would create unrealistic expectations on the part of requesters, undercut FOIA's statutory fee requirements, and provide Department employees with an unacceptably vague standard.</P>
        <HD SOURCE="HD3">The Final Rule Should Strengthen the Regulations to Expand Online Disclosures</HD>
        <P>One commenter suggested that the Department require all responses to FOIA requests be posted online (except those that implicate the Privacy Act) and that it adopt a policy to proactively disclose information to the greatest extent possible. The Department has carefully considered this suggestion, but declines to adopt it because it believes the final rule reflects the appropriate balance between providing useful information and an appropriate use of the Department's resources.</P>
        <HD SOURCE="HD3">The Final Rule Should Specifically Discuss Working With the Office of Government Information Services (“OGIS”)</HD>
        <P>Two commenters suggested the final rule discuss the services offered by OGIS. The Department agrees that OGIS's role in the FOIA process should be noted in the final rule. Rather than waiting until after an appeal decision has been made to introduce this information (as one of the commenters suggested), the Department has adopted this suggestion by requiring bureaus to provide information on OGIS in letters taking final action on a request, which will ensure maximum dissemination of the information at the most appropriate stage of the process. The revised § 2.21(a) both clarifies the provision and requires the Department to provide notice of the services offered by OGIS to all of the Department's FOIA requesters, rather than just the ones that file appeals.</P>
        <HD SOURCE="HD3">The Final Rule Should Include Procedures for Confidential Business Information</HD>
        <P>One commenter suggested the Department require submitters of older records to provide additional information to explain why the information is still confidential and its release would still be harmful after the passage of time. However, § 2.28(g) already requires this, so the Department believes adopting this suggestion is not necessary.</P>
        <HD SOURCE="HD3">The Final Rule Should Not Contravene Transparency Goals</HD>
        <P>One commenter asserted, in addition to a number of specific comments, that the final rule directly contravenes transparency goals. The Department has carefully considered this assertion, but believes the final rule improves overall processing and increases transparency, so no changes have been made based on this comment.</P>
        <HD SOURCE="HD3">The Final Rule Should Not Change the FOIA, Exceed the Scope of the Department's Rulemaking Authority, or Be Contrary to Law</HD>
        <P>One commenter's entire comment was: “NO.Do not change the freedom of info act.” As noted above, this rule consists of the regulations that the Department follows in processing records under the FOIA. It does not change the FOIA itself in any way. Another commenter asserted, in addition to a number of specific comments, that the final rule exceeded the scope of the Department's rulemaking authority and was “contrary to law.” The Department has carefully considered these assertions, but believes the final rule was fully within the scope of the Department's rulemaking authority and completely consistent with all applicable laws, so no changes have been made based on this comment.</P>
        <HD SOURCE="HD2">C. Technical and Procedural Comments</HD>

        <P>A number of commenters made suggestions related to minor word choices, minor clarifications, and additional citations, many of which have been adopted without further comment. The Department has also fixed a few minor typographical errors. Additionally, the Department added cross references, and/or made very minor clarifications in the following sections: 2.7(a) and (b), 2.15(a), 2.17, 2.19(c), 2.20(c), 2.22(c), 2.33, 2.41(a) and (c), 2.42(a), 2.43(a), and 2.60(b). Finally, in the interests of clarity, the Department also added phrases to §§ 2.31(a) and 2.63(c) and a second paragraph to § 2.37(f).<PRTPAGE P="76902"/>
        </P>
        <HD SOURCE="HD1">II. Compliance With Laws and Executive Orders</HD>
        <HD SOURCE="HD2">1. Regulatory Planning and Review (Executive Orders 12866 and 13563)</HD>
        <P>Executive Order 12866 provides that the Office of Information and Regulatory Affairs will review all significant rules. The Office of Information and Regulatory Affairs has determined that this rule is not significant.</P>
        <P>Executive Order 13563 reaffirms the principles of E.O. 12866 while calling for improvements in the nation's regulatory system to promote predictability, to reduce uncertainty, and to use the best, most innovative, and least burdensome tools for achieving regulatory ends. The executive order directs agencies to consider regulatory approaches that reduce burdens and maintain flexibility and freedom of choice for the public where these approaches are relevant, feasible, and consistent with regulatory objectives. E.O. 13563 emphasizes further that regulations must be based on the best available science and that the rulemaking process must allow for public participation and an open exchange of ideas. We have developed this rule in a manner consistent with these requirements.</P>
        <HD SOURCE="HD2">2. Regulatory Flexibility Act</HD>

        <P>The Department of the Interior certifies that this rule will not have a significant economic effect on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601<E T="03">et seq.</E>).</P>
        <HD SOURCE="HD2">3. Small Business Regulatory Enforcement Fairness Act (SBREFA)</HD>
        <P>This is not a major rule under 5 U.S.C. 804(2), the Small Business Regulatory Enforcement Fairness Act. This rule:</P>
        <P>a. Does not have an annual effect on the economy of $100 million or more.</P>
        <P>b. Will not cause a major increase in costs or prices for consumers, individual industries, Federal, State, or local government agencies, or geographic regions.</P>
        <P>c. Does not have significant adverse effects on competition, employment, investment, productivity, innovation, or the ability of U.S.-based enterprises to compete with foreign-based enterprises.</P>
        <HD SOURCE="HD2">4. Unfunded Mandates Reform Act</HD>

        <P>This rule does not impose an unfunded mandate on State, local, or tribal governments or the private sector of more than $100 million per year. This rule does not have a significant or unique effect on State, local or tribal governments or the private sector. A statement containing the information required by the Unfunded Mandates Reform Act (2 U.S.C. 1531<E T="03">et seq.</E>) is not required.</P>
        <HD SOURCE="HD2">5. Takings (E.O. 12630)</HD>
        <P>In accordance with Executive Order 12630, this rule does not have significant takings implications. A takings implication assessment is not required.</P>
        <HD SOURCE="HD2">6. Federalism (E.O. 13132)</HD>
        <P>In accordance with Executive Order 13132, this rule does not have sufficient federalism implications to warrant the preparation of a Federalism Assessment. It would not substantially and directly affect the relationship between the Federal and state governments. A Federalism Assessment is not required.</P>
        <HD SOURCE="HD2">7. Civil Justice Reform (E.O. 12988)</HD>
        <P>In accordance with Executive Order 12988, the Office of the Solicitor has determined that this rule does not unduly burden the judicial system and meets the requirements of sections 3(a) and 3(b)(2) of the Order.</P>
        <HD SOURCE="HD2">8. Consultation With Indian Tribes (E.O. 13175)</HD>
        <P>Under the criteria in Executive Order 13175, we have evaluated this rule and determined that it has no potential effects on federally recognized Indian tribes. This rule does not have tribal implications that impose substantial direct compliance costs on Indian Tribal governments.</P>
        <HD SOURCE="HD2">9. Paperwork Reduction Act</HD>
        <P>This rule does not contain information collection requirements, and a submission to the Office of Management and Budget under the Paperwork Reduction Act is not required.</P>
        <HD SOURCE="HD2">9. National Environmental Policy Act</HD>
        <P>This rule does not constitute a major Federal action significantly affecting the quality of the human environment. A detailed statement under the National Environmental Policy Act of 1969 is not required. Pursuant to Department Manual 516 DM 2.3A(2), Section 1.10 of 516 DM 2, Appendix 1 excludes from documentation in an environmental assessment or impact statement “policies, directives, regulations and guidelines of an administrative, financial, legal, technical or procedural nature; or the environmental effects of which are too broad, speculative or conjectural to lend themselves to meaningful analysis and will be subject late to the NEPA process, either collectively or case-by-case.”</P>
        <HD SOURCE="HD2">10. Effects on the Energy Supply (E.O. 13211)</HD>
        <P>This rule is not a significant energy action under the definition in Executive Order 13211. A Statement of Energy Effects is not required. This rule will not have a significant effect on the nation's energy supply, distribution, or use.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 43 CFR Part 2</HD>
          <P>Freedom of information.</P>
        </LSTSUB>
        <SIG>
          <NAME>David J. Hayes,</NAME>
          <TITLE>Deputy Secretary of the Interior.</TITLE>
        </SIG>
        <P>For the reasons stated in the preamble, the Department of the Interior amends 43 CFR subtitle A as follows:</P>
        <REGTEXT PART="2" TITLE="43">
          <PART>
            <HD SOURCE="HED">PART 2—FREEDOM OF INFORMATION ACT; RECORDS AND TESTIMONY</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 2 is revised to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>5 U.S.C. 301, 552, 552a, 553; 31 U.S.C. 3717; 43 U.S.C. 1460, 1461.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="2" TITLE="43">
          <AMDPAR>2. The heading of part 2 is revised to read as set forth above.</AMDPAR>
          <SUBPART>
            <HD SOURCE="HED">Subparts F through H [Redesignated as Subparts J through L]</HD>
          </SUBPART>
        </REGTEXT>
        <REGTEXT PART="2" TITLE="43">
          <AMDPAR>3. Subpart F (consisting of § 2.41), subpart G (consisting of §§ 2.45 through 2.79), and subpart H (consisting of §§ 2.80 through 2.90) are redesignated as subpart J, subpart K, and subpart L.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="2" TITLE="43">
          <AMDPAR>4. Subparts A through E are revised to read as follows:</AMDPAR>
          <CONTENTS>
            <SUBPART>
              <HD SOURCE="HED">Subpart A—Introduction</HD>
              <SECHD>Sec.</SECHD>
              <SECTNO>2.1</SECTNO>
              <SUBJECT>What should you know up front?</SUBJECT>
              <SECTNO>2.2</SECTNO>
              <SUBJECT>What kinds of records are not covered by the regulations in subparts A through I of this part?</SUBJECT>
            </SUBPART>
            <SUBPART>
              <HD SOURCE="HED">Subpart B—How to Make a Request</HD>
              <SECTNO>2.3</SECTNO>
              <SUBJECT>Where should you send a FOIA request?</SUBJECT>
              <SECTNO>2.4</SECTNO>
              <SUBJECT>Does where you send your request affect its processing?</SUBJECT>
              <SECTNO>2.5</SECTNO>
              <SUBJECT>How should you describe the records you seek?</SUBJECT>
              <SECTNO>2.6</SECTNO>
              <SUBJECT>How will fee information affect the processing of your request?</SUBJECT>
              <SECTNO>2.7</SECTNO>
              <SUBJECT>What information should you include about your fee category?</SUBJECT>
              <SECTNO>2.8</SECTNO>
              <SUBJECT>Can you ask for records to be disclosed in a particular form or format?</SUBJECT>
              <SECTNO>2.9</SECTNO>
              <SUBJECT>What if your request seeks records about another person?</SUBJECT>
              <SECTNO>2.10</SECTNO>
              <SUBJECT>May you ask for the processing of your request to be expedited?</SUBJECT>
              <SECTNO>2.11</SECTNO>
              <SUBJECT>What contact information should your request include?</SUBJECT>
            </SUBPART>
            <SUBPART>
              <HD SOURCE="HED">Subpart C—Processing Requests</HD>
              <SECTNO>2.12</SECTNO>
              <SUBJECT>What should you know about how bureaus process requests?</SUBJECT>
              <SECTNO>2.13</SECTNO>
              <SUBJECT>How do consultations and referrals work?</SUBJECT>
            </SUBPART>
            <SUBPART>
              <PRTPAGE P="76903"/>
              <HD SOURCE="HED">Subpart D—Timing of Responses to Requests</HD>
              <SECTNO>2.14</SECTNO>
              <SUBJECT>In what order are responses usually made?</SUBJECT>
              <SECTNO>2.15</SECTNO>
              <SUBJECT>What is multitrack processing and how does it affect your request?</SUBJECT>
              <SECTNO>2.16</SECTNO>
              <SUBJECT>What is the basic time limit for responding to a request?</SUBJECT>
              <SECTNO>2.17</SECTNO>
              <SUBJECT>When does the basic time limit begin for misdirected FOIA requests?</SUBJECT>
              <SECTNO>2.18</SECTNO>
              <SUBJECT>When can the bureau suspend the basic time limit?</SUBJECT>
              <SECTNO>2.19</SECTNO>
              <SUBJECT>When may the bureau extend the basic time limit?</SUBJECT>
              <SECTNO>2.20</SECTNO>
              <SUBJECT>When will expedited processing be provided and how will it affect your request?</SUBJECT>
            </SUBPART>
            <SUBPART>
              <HD SOURCE="HED">Subpart E—Responses to Requests</HD>
              <SECTNO>2.21</SECTNO>
              <SUBJECT>How will the bureau respond to requests?</SUBJECT>
              <SECTNO>2.22</SECTNO>
              <SUBJECT>How will the bureau grant requests?</SUBJECT>
              <SECTNO>2.23</SECTNO>
              <SUBJECT>When will the bureau deny a request or procedural benefits?</SUBJECT>
              <SECTNO>2.24</SECTNO>
              <SUBJECT>How will the bureau deny requests?</SUBJECT>
              <SECTNO>2.25</SECTNO>
              <SUBJECT>What if the requested records contain both exempt and nonexempt material?</SUBJECT>
            </SUBPART>
          </CONTENTS>
          <SUBPART>
            <HD SOURCE="HED">Subpart A—Introduction</HD>
            <SECTION>
              <SECTNO>§ 2.1</SECTNO>
              <SUBJECT>What should you know up front?</SUBJECT>
              <P>(a) Subparts A through I of this part contain the rules that the Department follows in processing records under the Freedom of Information Act (FOIA), 5 U.S.C. 552.</P>
              <P>(b) Definitions of terms used in Subparts A through I of this part are found at § 2.70.</P>
              <P>(c) Subparts A through I of this part should be read in conjunction with the text of the FOIA and the OMB Fee Guidelines.</P>

              <P>(d) The Department's FOIA Handbook and its attachments contain detailed information about Department procedures for making FOIA requests and descriptions of the types of records maintained by different Department bureaus or offices. This resource is available at<E T="03">http://www.doi.gov/foia/guidance.cfm.</E>
              </P>
              <P>(e) Requests made by individuals for records about themselves under the Privacy Act of 1974, 5 U.S.C. 552a, are processed under subparts A through I and subpart K of this part.</P>
              <P>(f) Part 2 does not entitle any person to any service or to the disclosure of any record that is not required under the FOIA.</P>

              <P>(g) Before you file a FOIA request, you are encouraged to review the Department's electronic FOIA libraries at<E T="03">http://www.doi.gov/foia/libraries.cfm.</E>The material you seek may be immediately available electronically at no cost.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.2</SECTNO>
              <SUBJECT>What kinds of records are not covered by the regulations in subparts A through I of this part?</SUBJECT>
              <P>Subparts A through I of this part do not apply to records that fall under the law enforcement exclusions in 5 U.S.C. 552(c)(1)-(3). These exclusions may be used only in the limited circumstances delineated by the statute and require both prior approval from the Office of the Solicitor and the recording of their use and approval process.</P>
            </SECTION>
          </SUBPART>
          <SUBPART>
            <HD SOURCE="HED">Subpart B—How To Make a Request</HD>
            <SECTION>
              <SECTNO>§ 2.3</SECTNO>
              <SUBJECT>Where should you send a FOIA request?</SUBJECT>
              <P>(a) The Department does not have a central location for submitting FOIA requests and it does not maintain a central index or database of records in its possession. Instead, the Department's records are decentralized and maintained by various bureaus and offices throughout the country.</P>
              <P>(b) To make a request for Department records, you must write directly to the bureau that you believe maintains those records.</P>

              <P>(c) Address requests to the appropriate FOIA contact in the bureau that maintains the requested records. The Department's FOIA Web site,<E T="03">http://www.doi.gov/foia/index.cfm</E>, lists the physical and email addresses of each bureau's FOIA Officer, along with other appropriate FOIA contacts at<E T="03">http://www.doi.gov/foia/contacts.cfm.</E>
              </P>
              <P>(d) Questions about where to send a FOIA request should be directed to the bureau that manages the underlying program or to the appropriate FOIA Public Liaison, as discussed in § 2.66 of this part.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.4</SECTNO>
              <SUBJECT>Does where you send your request affect its processing?</SUBJECT>
              <P>(a) A request to a particular bureau component (for example, a request addressed to a regional or field office) will be presumed to seek only records from that particular component.</P>
              <P>(b) If you seek records from an entire bureau, submit your request to the bureau FOIA Officer. The bureau FOIA Officer will forward it to the bureau component(s) that he or she believes has or are likely to have responsive records.</P>
              <P>(c) If a request to a bureau states that it seeks records located at another specific component of the same bureau, the appropriate FOIA contact will forward the request to the other component.</P>
              <P>(d) If a request to a bureau states that it seeks records from other unspecified components within the same bureau, the appropriate FOIA contact will send the request to the Bureau FOIA Officer. He or she will forward it to the components that the bureau FOIA Officer believes have or are likely to have responsive records.</P>
              <P>(e) If a request to a bureau states that it seeks records of another specified bureau, the bureau will route the misdirected request to the specified bureau for response.</P>
              <P>(f) If a request to a bureau states that it seeks records from other unspecified bureaus, the bureau's FOIA Officer may forward the request to those bureaus which he or she believes have or are likely to have responsive records. If the bureau FOIA Officer forwards the request, they will notify you in writing and provide the name of a contact in the other bureau(s). If it does not forward the request, the bureau will return it to you, advise you to submit the request directly to the other bureaus, notify you that it cannot comply with the request, and close the request.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.5</SECTNO>
              <SUBJECT>How should you describe the records you seek?</SUBJECT>
              <P>(a) You must reasonably describe the records sought. A reasonable description contains sufficient detail to enable bureau personnel familiar with the subject matter of the request to locate the records with a reasonable amount of effort.</P>
              <P>(b) You should include as much detail as possible about the specific records or types of records that you are seeking. This will assist the bureau in identifying the requested records (for example, time frames involved or specific personnel who may have the requested records). For example, whenever possible, identify:</P>
              <P>(1) The date, title or name, author, recipient, and subject of any particular records you seek;</P>
              <P>(2) The office that created the records you seek;</P>
              <P>(3) The timeframe for which you are seeking records; and</P>
              <P>(4) Any other information that will assist the bureau in locating the records.</P>
              <P>(c) The bureau's FOIA Public Liaison can assist you in formulating or reformulating a request in an effort to better identify the records you seek.</P>

              <P>(d) If the request does not reasonably describe the records sought, the bureau will inform you what additional information is needed. It will also notify you that it will not be able to comply with your FOIA request unless you provide the additional information requested within 20 workdays. If you receive this sort of response, you may wish to discuss it with the bureau's designated FOIA contact or its FOIA Public Liaison (see § 2.66 of this part). If the bureau does not hear from you within 20 workdays after asking for<PRTPAGE P="76904"/>additional information, it will presume that you are no longer interested in the records and will close the file on the request.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.6</SECTNO>
              <SUBJECT>How will fee information affect the processing of your request?</SUBJECT>
              <P>(a) Your request must explicitly state that you will pay all fees associated with processing the request, that you will pay fees up to a specified amount, and/or that you are seeking a fee waiver.</P>
              <P>(b) If the bureau anticipates that the fees for processing the request will exceed the amount you have agreed to pay, or if you did not agree in writing to pay processing fees and the bureau anticipates the processing costs will exceed your entitlements, the bureau will notify you:</P>
              <P>(1) Of the estimated processing fees;</P>
              <P>(2) Of its need for either an advance payment (see § 2.50 of this part) or your written assurance that you will pay the anticipated fees (or fees up to a specified amount); and</P>
              <P>(3) That it will not be able to fully comply with your FOIA request unless you provide the written assurance or advance payment requested.</P>
              <P>(c) If the bureau does not receive a written response from you within 20 workdays after requesting the information in paragraph (b) of this section, it will presume that you are no longer interested in the records and will close the file on the request.</P>
              <P>(d) If you are seeking a fee waiver, your request must include sufficient justification (see the criteria in §§ 2.45, 2.48, and 2.56 of this part). Failure to provide sufficient justification will result in a denial of the fee waiver request. If you are seeking a fee waiver, you may also indicate the amount you are willing to pay if the fee waiver is denied. This allows the bureau to process the request for records while it considers your fee waiver request.</P>
              <P>(e) The bureau will begin processing the request only after the fee issues are resolved.</P>
              <P>(f) If you are required to pay a fee and it is later determined on appeal that you were entitled to a full or partial fee waiver, you will receive an appropriate refund.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.7</SECTNO>
              <SUBJECT>What information should you include about your fee category?</SUBJECT>
              <P>(a) A request should indicate your fee category (that is, whether you are a commercial-use requester, news media, educational or noncommercial scientific institution, or other requester as described in §§ 2.38 and 2.39 of this part).</P>
              <P>(b) If you submit a FOIA request on behalf of another person or organization (for example, if you are an attorney submitting a request on behalf of a client), the bureau will determine the fee category by considering the underlying requester's identity and intended use of the information.</P>
              <P>(c) If your fee category is unclear, the bureau may ask you for additional information (see § 2.51 of this part).</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.8</SECTNO>
              <SUBJECT>Can you ask for records to be disclosed in a particular form or format?</SUBJECT>
              <P>(a) Generally, you may choose the form or format of disclosure for records requested. The bureau must provide the records in the requested form or format if the bureau can readily reproduce the record in that form or format.</P>
              <P>(b) The bureau may charge you the direct costs involved in converting records to the requested format if the bureau does not normally maintain the records in that format (see § 2.44 of this part).</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.9</SECTNO>
              <SUBJECT>What if your request seeks records about another person?</SUBJECT>
              <P>(a) When a request seeks records about another person, you may receive greater access by submitting proof that the person either:</P>
              <P>(1) Consents to the release of the records to you (for example, a notarized authorization signed by that person); or</P>
              <P>(2) Is deceased (for example, a copy of a death certificate or an obituary).</P>
              <P>(b) At its discretion, the bureau can require you to supply additional information if necessary to verify that a particular person has consented to disclosure or is deceased.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.10</SECTNO>
              <SUBJECT>May you ask for the processing of your request to be expedited?</SUBJECT>
              <P>You may ask for the processing of your request to be expedited. The bureau will determine whether to expedite the processing of your request using the criteria outlined in § 2.20.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.11</SECTNO>
              <SUBJECT>What contact information should your request include?</SUBJECT>
              <P>A request should include your name, mailing address, daytime telephone number (or the name and telephone number of an appropriate contact), email address, and fax number (if available) in case the bureau needs additional information or clarification of your request.</P>
            </SECTION>
          </SUBPART>
          <SUBPART>
            <HD SOURCE="HED">Subpart C—Processing Requests</HD>
            <SECTION>
              <SECTNO>§ 2.12</SECTNO>
              <SUBJECT>What should you know about how bureaus process requests?</SUBJECT>
              <P>(a) Except as described in §§ 2.4 and 2.13 of this part, the bureau to which the request is addressed is responsible for responding to the request and for making a reasonable effort to search for responsive records.</P>
              <P>(b) In determining which records are responsive to a request, the bureau will include only records in its possession and control on the date that it begins its search.</P>
              <P>(c) The bureau will make reasonable efforts to search for the requested records in electronic form or format, except when these efforts would significantly interfere with the operation of the bureau's automated information system.</P>
              <P>(d) If a bureau receives a request for records in its possession that it did not create or that another bureau or a Federal agency is substantially concerned with, it may undertake consultations and/or referrals as described in § 2.13.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.13</SECTNO>
              <SUBJECT>How do consultations and referrals work?</SUBJECT>
              <P>(a) Consultations and referrals can occur within the Department or outside the Department.</P>
              <P>(1) Paragraphs (b) and (c) of this section addresses consultations and referrals that occur within the Department when the bureau has responsive records.</P>
              <P>(2) Paragraphs (d) through (g) of this section address consultations and referrals that occur outside the Department when the bureau has responsive records.</P>
              <P>(3) Paragraph (h) of this section addresses what happens when the bureau has no responsive records but believes responsive records may be in the possession of a Federal agency outside the Department.</P>
              <P>(b) If a bureau (other than the Office of Inspector General) receives a request for records in its possession that another bureau created or is substantially concerned with, it will either:</P>
              <P>(1) Consult with the other bureau before deciding whether to release or withhold the records; or</P>
              <P>(2) Refer the request, along with the records, to that other bureau for direct response.</P>
              <P>(c) The bureau that originally received the request will notify you of the referral in writing. When the bureau notifies you of the referral, it will tell you whether the referral was for part or all of your request and provide the name and contact information for the other bureau.</P>
              <P>(d) If, while responding to a request, the bureau locates records that originated with another Federal agency, it usually will refer the request and any responsive records to that other agency for a release determination and direct response.</P>

              <P>(e) If the bureau refers records to another agency, it will document the<PRTPAGE P="76905"/>referral and maintain a copy of the records that it refers and notify you of the referral in writing, unless the notification will itself disclose a sensitive, exempt fact. When the bureau notifies you of the referral, it will tell you whether the referral was for part or all of your request and provide the name and contact information for the other agency. You may treat such a response as a denial of records and file an appeal, in accordance with the procedures in § 2.59 of this part.</P>
              <P>(f) If the bureau locates records that originated with another Federal agency while responding to a request, the bureau will make the release determination itself (after consulting with the originating agency) when:</P>
              <P>(1) The record is of primary interest to the Department (for example, a record may be of primary interest to the Department if it was developed or prepared according to the Department's regulations or directives, or in response to a Departmental request);</P>
              <P>(2) The Department is in a better position than the originating agency to assess whether the record is exempt from disclosure;</P>
              <P>(3) The originating agency is not subject to the FOIA; or</P>
              <P>(4) It is more efficient or practical depending on the circumstances.</P>
              <P>(g) If the bureau receives a request for records that another Federal agency has classified under any applicable executive order concerning record classification, it must refer the request to that agency for response.</P>
              <P>(h) If the bureau receives a request for records not in its possession, but that the bureau believes may be in the possession of a Federal agency outside the Department, the bureau will return the request to you, may advise you to submit it directly to the agency, will notify you that the bureau cannot comply with the request, and will close the request.</P>
            </SECTION>
          </SUBPART>
          <SUBPART>
            <HD SOURCE="HED">Subpart D—Timing of Responses to Requests</HD>
            <SECTION>
              <SECTNO>§ 2.14</SECTNO>
              <SUBJECT>In what order are responses usually made?</SUBJECT>
              <P>The bureau ordinarily will respond to requests according to their order of receipt within their processing track.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.15</SECTNO>
              <SUBJECT>What is multitrack processing and how does it affect your request?</SUBJECT>
              <P>(a) Bureaus use processing tracks to distinguish simple requests from more complex ones on the basis of the estimated number of workdays needed to process the request.</P>
              <P>(b) In determining the number of workdays needed to process the request, the bureau considers factors such as the number of pages involved in processing the request or the need for consultations.</P>
              <P>(c) The basic processing tracks are designated as follows:</P>
              <P>(1) Simple: requests in this track will take between one to five workdays to process;</P>
              <P>(2) Normal: requests in this track will take between six to twenty workdays to process;</P>
              <P>(3) Complex: requests in this track will take between twenty-one workdays and sixty workdays to process; or</P>
              <P>(4) Exceptional/Voluminous: requests in this track involve very complex processing challenges, which may include a large number of potentially responsive records, and will take over sixty workdays to process.</P>
              <P>(d) Bureaus also have a specific processing track for requests that are granted expedited processing under the standards in § 2.20 of this part. These requests will be processed as soon as practicable.</P>
              <P>(e) Bureaus must advise you of the track into which your request falls and, when appropriate, will offer you an opportunity to narrow your request so that it can be placed in a different processing track.</P>
              <P>(f) The use of multitrack processing does not alter the statutory deadline for a bureau to determine whether to comply with your FOIA request (see § 2.16 of this part).</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.16</SECTNO>
              <SUBJECT>What is the basic time limit for responding to a request?</SUBJECT>
              <P>(a) Ordinarily, the bureau has 20 workdays after the date of receipt to determine whether to comply with (for example, grant, partially grant, or deny) a FOIA request, but unusual circumstances may allow the bureau to take longer than 20 workdays (see § 2.19).</P>
              <P>(b) A consultation or referral under § 2.13 of this part does not restart the statutory time limit for responding to a request.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.17</SECTNO>
              <SUBJECT>When does the basic time limit begin for misdirected FOIA requests?</SUBJECT>
              <P>The basic time limit for a misdirected FOIA request (see § 2.4(e) of this part) begins no later than ten workdays after the request is first received by any component of the Department that is designated to receive FOIA requests.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.18</SECTNO>
              <SUBJECT>When can the bureau suspend the basic time limit?</SUBJECT>
              <P>(a) The basic time limit in § 2.16 of this part may be temporarily suspended for the time it takes you to respond to one written communication from the bureau reasonably asking for clarifying information.</P>
              <P>(b) The basic time limit in § 2.16 may also repeatedly be temporarily suspended for the time it takes you to respond to written communications from the bureau that are necessary to clarify issues regarding fee assessment (see § 2.51 of this part).</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.19</SECTNO>
              <SUBJECT>When may the bureau extend the basic time limit?</SUBJECT>
              <P>(a) The bureau may extend the basic time limit if unusual circumstances exist. Before the expiration of the basic 20 workday time limit to respond, the bureau will notify you in writing of:</P>
              <P>(1) The unusual circumstances involved; and</P>
              <P>(2) The date by which it expects to complete processing the request.</P>
              <P>(b) If the processing time will extend beyond a total of 30 workdays, the bureau will:</P>
              <P>(1) Give you an opportunity to limit the scope of the request or agree to an alternative time period for processing; and</P>
              <P>(2) Make available its FOIA Public Liaison (see § 2.66 of this part) to assist in resolving any disputes between you and the bureau.</P>
              <P>(c) If the bureau extends the time limit under this section and you do not receive a response in accordance with § 2.16(a) in that time period, you may consider the request denied and file an appeal in accordance with the procedures in § 2.59.</P>
              <P>(d) Your refusal to reasonably modify the scope of a request or arrange an alternative time frame for processing a request after being given the opportunity to do so may be considered for litigation purposes as a factor when determining whether exceptional circumstances exist.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.20</SECTNO>
              <SUBJECT>When will expedited processing be provided and how will it affect your request?</SUBJECT>
              <P>(a) The bureau will provide expedited processing upon request if you demonstrate to the satisfaction of the bureau that there is a compelling need for the records. The following circumstances demonstrate a compelling need:</P>
              <P>(1) Where failure to expedite the request could reasonably be expected to pose an imminent threat to the life or physical safety of an individual; or</P>
              <P>(2) Where there is an urgency to inform the public about an actual or alleged Federal Government activity and the request is made by a person primarily engaged in disseminating information.</P>

              <P>(i) In most situations, a person primarily engaged in disseminating<PRTPAGE P="76906"/>information will be a representative of the news media.</P>
              <P>(ii) If you are not a full time member of the news media, to qualify for expedited processing here, you must establish that your main professional activity or occupation is information dissemination, although it need not be your sole occupation.</P>
              <P>(iii) The requested information must be the type of information which has particular value that will be lost if not disseminated quickly; this ordinarily refers to a breaking news story of general public interest.</P>
              <P>(iv) Information of historical interest only or information sought for litigation or commercial activities would not qualify, nor would a news media deadline unrelated to breaking news.</P>
              <P>(b) If you seek expedited processing, you must submit a statement that:</P>
              <P>(1) Explains in detail how your request meets one or both of the criteria in paragraph (a) of this section; and</P>
              <P>(2) Certifies that your explanation is true and correct to the best of your knowledge and belief.</P>
              <P>(c) You may ask for expedited processing at any time by writing to the appropriate FOIA contact in the bureau that maintains the records requested. When making a request for expedited processing of an administrative appeal, submit the request to the FOIA Appeals Officer.</P>
              <P>(d) The bureau must notify you of its decision to grant or deny expedited processing within 10 calendar days of receiving an expedited processing request.</P>
              <P>(e) If expedited processing is granted, the request will be given priority, placed in the processing track for expedited requests, and be processed as soon as practicable.</P>
              <P>(f) If expedited processing is denied, the bureau will notify you of the right to appeal the decision on expedited processing in accordance with the procedures in subpart H of this part.</P>
              <P>(g) If you appeal the decision on expedited processing, your appeal (if it is properly formatted under § 2.59 of this part) will be processed ahead of other appeals.</P>
              <P>(h) If the bureau has not responded to the request for expedited processing within 10 calendar days, you may file an appeal (for nonresponse in accordance with § 2.57(a)(8) of this part).</P>
            </SECTION>
          </SUBPART>
          <SUBPART>
            <HD SOURCE="HED">Subpart E—Responses to Requests</HD>
            <SECTION>
              <SECTNO>§ 2.21</SECTNO>
              <SUBJECT>How will the bureau respond to requests?</SUBJECT>

              <P>(a) When the bureau informs you of its decision to comply with a request by granting, partially granting, or denying the request, it will do so in writing and in accordance with the deadlines in subpart D of this part. The bureau's written response will include a statement about the services offered by the Office of Government Information Services (OGIS), using standard language that can be found at:<E T="03">http://www.doi.gov/foia/news/guidance/index.cfm</E>.</P>
              <P>(b) If the bureau determines that your request will take longer than 10 workdays to process, the bureau immediately will send you a written acknowledgment that includes the request's individualized tracking number and processing track (see § 2.15(e)). The acknowledgement may also include a brief description of the subject of your request.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.22</SECTNO>
              <SUBJECT>How will the bureau grant requests?</SUBJECT>
              <P>(a) Once the bureau makes a determination to grant a request in full or in part, it must notify you in writing.</P>
              <P>(b) The notification will inform you of any fees charged under subpart G of this part.</P>
              <P>(c) The bureau will release records (or portions of records) to you promptly upon payment of any applicable fees (or before then, in accordance with § 2.37(c) of this part).</P>
              <P>(d) If the records (or portions of records) are not included with the bureau's notification, the bureau will advise you how, when, and where the records will be made available.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.23</SECTNO>
              <SUBJECT>When will the bureau deny a request or procedural benefits?</SUBJECT>
              <P>(a) A bureau denies a request when it makes a decision that:</P>
              <P>(1) A requested record is exempt, in full or in part;</P>
              <P>(2) The request does not reasonably describe the records sought;</P>
              <P>(3) A requested record does not exist, cannot be located, or is not in the bureau's possession; or</P>
              <P>(4) A requested record is not readily reproducible in the form or format you seek.</P>
              <P>(b) A bureau denies a procedural benefit only, and not access to the underlying records, when it makes a decision that:</P>
              <P>(1) A fee waiver, or another fee-related issue, will not be granted; or</P>
              <P>(2) Expedited processing will not be provided.</P>
              <P>(c) The bureau must consult with the Office of the Solicitor before it denies a fee waiver request or withholds all or part of a requested record.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.24</SECTNO>
              <SUBJECT>How will the bureau deny requests?</SUBJECT>
              <P>(a)The bureau must notify you in writing of any denial of your request.</P>
              <P>(b) The denial notification must include:</P>
              <P>(1) The name and title or position of the person responsible for the denial;</P>
              <P>(2) A brief statement of the reasons for the denial, including a reference to any FOIA exemption(s) applied by the bureau to withhold records in full or in part;</P>
              <P>(3) An estimate of the volume of any records or information withheld, for example, by providing the number of pages or some other reasonable form of estimation, unless such an estimate would harm an interest protected by the exemption(s) used to withhold the records or information;</P>
              <P>(4) The name and title of the Office of the Solicitor attorney consulted (if the bureau is denying a fee waiver request or withholding all or part of a requested record); and</P>
              <P>(5) A statement that the denial may be appealed under subpart H of this part and a description of the requirements set forth therein.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.25</SECTNO>
              <SUBJECT>What if the requested records contain both exempt and nonexempt material?</SUBJECT>
              <P>If responsive records contain both exempt and nonexempt material, the bureau will consult with the Office of the Solicitor, as discussed in § 2.23(c). After consultation, the bureau will partially grant and partially deny the request by:</P>
              <P>(a) Segregating and releasing the nonexempt information, unless the nonexempt material is so intertwined with the exempt material that disclosure of it would leave only meaningless words and phrases;</P>
              <P>(b) Indicating on the released portion of the record the amount of information deleted and the FOIA exemption under which the deletion was made, unless doing so would harm an interest protected by the FOIA exemption used to withhold the information; and</P>
              <P>(c) If technically feasible, placing the information required by paragraph (b) of this section at the place in the record where the deletion was made.</P>
            </SECTION>
          </SUBPART>
        </REGTEXT>
        <REGTEXT PART="2" TITLE="43">
          <AMDPAR>5. Subparts F through I are added to read as follows:</AMDPAR>
          <CONTENTS>
            <SUBPART>
              <HD SOURCE="HED">Subpart F—Handling Confidential Information</HD>
              <SECHD>Sec.</SECHD>
              <SECTNO>2.26</SECTNO>
              <SUBJECT>How will the bureau interact with the submitter of possibly confidential information?</SUBJECT>
              <SECTNO>2.27</SECTNO>
              <SUBJECT>When will the bureau notify a submitter of a request for their possibly confidential information?</SUBJECT>
              <SECTNO>2.28</SECTNO>

              <SUBJECT>What information will the bureau include when it notifies a submitter of a request for their possibly confidential information?<PRTPAGE P="76907"/>
              </SUBJECT>
              <SECTNO>2.29</SECTNO>
              <SUBJECT>When will the bureau not notify a submitter of a request for their possibly confidential information?</SUBJECT>
              <SECTNO>2.30</SECTNO>
              <SUBJECT>How and when may a submitter object to disclosure of confidential information?</SUBJECT>
              <SECTNO>2.31</SECTNO>
              <SUBJECT>What must a submitter include in a detailed Exemption 4 objection statement?</SUBJECT>
              <SECTNO>2.32</SECTNO>
              <SUBJECT>How will the bureau consider the submitter's objections?</SUBJECT>
              <SECTNO>2.33</SECTNO>
              <SUBJECT>What if the bureau determines it will disclose information over the submitter's objections?</SUBJECT>
              <SECTNO>2.34</SECTNO>
              <SUBJECT>Will a submitter be notified of a FOIA lawsuit?</SUBJECT>
              <SECTNO>2.35</SECTNO>
              <SUBJECT>Will you receive notification of activities involving the submitter?</SUBJECT>
              <SECTNO>2.36</SECTNO>
              <SUBJECT>Can a bureau release information protected by Exemption 4?</SUBJECT>
            </SUBPART>
            <SUBPART>
              <HD SOURCE="HED">Subpart G—Fees</HD>
              <SECTNO>2.37</SECTNO>
              <SUBJECT>What general principles govern fees?</SUBJECT>
              <SECTNO>2.38</SECTNO>
              <SUBJECT>What are the requester fee categories?</SUBJECT>
              <SECTNO>2.39</SECTNO>
              <SUBJECT>Does your requester category affect the fees you are charged?</SUBJECT>
              <SECTNO>2.40</SECTNO>
              <SUBJECT>How will fee amounts be determined?</SUBJECT>
              <SECTNO>2.41</SECTNO>
              <SUBJECT>What search fees will you have to pay?</SUBJECT>
              <SECTNO>2.42</SECTNO>
              <SUBJECT>What duplication fees will you have to pay?</SUBJECT>
              <SECTNO>2.43</SECTNO>
              <SUBJECT>What review fees will you have to pay?</SUBJECT>
              <SECTNO>2.44</SECTNO>
              <SUBJECT>What fees for other services will you have to pay?</SUBJECT>
              <SECTNO>2.45</SECTNO>
              <SUBJECT>When will the bureau waive fees?</SUBJECT>
              <SECTNO>2.46</SECTNO>
              <SUBJECT>When may you ask the bureau for a fee waiver?</SUBJECT>
              <SECTNO>2.47</SECTNO>
              <SUBJECT>How will the bureau notify you if it denies your fee waiver request?</SUBJECT>
              <SECTNO>2.48</SECTNO>
              <SUBJECT>How will the bureau evaluate your fee waiver request?</SUBJECT>
              <SECTNO>2.49</SECTNO>
              <SUBJECT>When will you be notified of anticipated fees?</SUBJECT>
              <SECTNO>2.50</SECTNO>
              <SUBJECT>When will the bureau require advance payment?</SUBJECT>
              <SECTNO>2.51</SECTNO>
              <SUBJECT>What if the bureau needs clarification about fee issues?</SUBJECT>
              <SECTNO>2.52</SECTNO>
              <SUBJECT>How will you be billed?</SUBJECT>
              <SECTNO>2.53</SECTNO>
              <SUBJECT>How will the bureau collect fees owed?</SUBJECT>
              <SECTNO>2.54</SECTNO>
              <SUBJECT>When will the bureau combine or aggregate requests?</SUBJECT>
              <SECTNO>2.55</SECTNO>
              <SUBJECT>What if other statutes require the bureau to charge fees?</SUBJECT>
              <SECTNO>2.56</SECTNO>
              <SUBJECT>May the bureau waive or reduce your fees at its discretion?</SUBJECT>
            </SUBPART>
            <SUBPART>
              <HD SOURCE="HED">Subpart H—Administrative Appeals</HD>
              <SECTNO>2.57</SECTNO>
              <SUBJECT>When may you file an appeal?</SUBJECT>
              <SECTNO>2.58</SECTNO>
              <SUBJECT>How long do you have to file an appeal?</SUBJECT>
              <SECTNO>2.59</SECTNO>
              <SUBJECT>How do you file an appeal?</SUBJECT>
              <SECTNO>2.60</SECTNO>
              <SUBJECT>Who makes decisions on appeals?</SUBJECT>
              <SECTNO>2.61</SECTNO>
              <SUBJECT>How are decisions on appeals issued?</SUBJECT>
              <SECTNO>2.62</SECTNO>
              <SUBJECT>When can you expect a decision on your appeal?</SUBJECT>
              <SECTNO>2.63</SECTNO>
              <SUBJECT>Can you receive expedited processing of appeals?</SUBJECT>
              <SECTNO>2.64</SECTNO>
              <SUBJECT>Must you submit an appeal before seeking judicial review?</SUBJECT>
            </SUBPART>
            <SUBPART>
              <HD SOURCE="HED">Subpart I—General Information</HD>
              <SECTNO>2.65</SECTNO>
              <SUBJECT>Where are records made available?</SUBJECT>
              <SECTNO>2.66</SECTNO>
              <SUBJECT>What are public liaisons?</SUBJECT>
              <SECTNO>2.67</SECTNO>
              <SUBJECT>When will the Department make records available without a FOIA request?</SUBJECT>
              <SECTNO>2.68</SECTNO>
              <SUBJECT>How will FOIA materials be preserved?</SUBJECT>
              <SECTNO>2.69</SECTNO>
              <SUBJECT>How will a bureau handle a request for federally-funded research data?</SUBJECT>
              <SECTNO>2.70</SECTNO>
              <SUBJECT>What definitions apply to subparts A through I of this part?</SUBJECT>
            </SUBPART>
          </CONTENTS>
          <SUBPART>
            <HD SOURCE="HED">Subpart F—Handling Confidential Information</HD>
            <SECTION>
              <SECTNO>§ 2.26</SECTNO>
              <SUBJECT>How will the bureau interact with the submitter of possibly confidential information?</SUBJECT>
              <P>(a) The Department encourages, but does not require, submitters to designate confidential information in good faith at the time of submission. Such designations assist the bureau in determining whether information obtained from the submitter is confidential information, but will not always be determinative.</P>
              <P>(b) If, in the course of responding to a FOIA request, a bureau cannot readily determine whether information is confidential information, the bureau will:</P>
              <P>(1) Consult with the submitter under §§ 2.27 and 2.28; and</P>
              <P>(2) Provide the submitter an opportunity to object to a decision to disclose the information under §§ 2.30 and 2.31 of this subpart.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.27</SECTNO>
              <SUBJECT>When will the bureau notify a submitter of a request for their possibly confidential information?</SUBJECT>
              <P>(a) Except as outlined in § 2.29 of this subpart, a bureau must promptly notify a submitter in writing when it receives a FOIA request if either:</P>
              <P>(1) The requested information has been designated in good faith by the submitter as information considered protected from disclosure under Exemption 4 of the FOIA, found at 5 U.S.C. 552(b)(4); or</P>
              <P>(2) The bureau believes that requested information may be protected from disclosure under Exemption 4.</P>

              <P>(b) If a large number of submitters are involved, the bureau may publish a notice in a manner reasonably calculated to reach the attention of the submitters (for example, in newspapers or newsletters, the bureau's Web site, or the<E T="04">Federal Register</E>) instead of providing a written notice to each submitter.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.28</SECTNO>
              <SUBJECT>What information will the bureau include when it notifies a submitter of a request for their possibly confidential information?</SUBJECT>
              <P>A notice to a submitter must include:</P>
              <P>(a) Either a copy of the FOIA request or the exact language of the request;</P>
              <P>(b) Either a description of the possibly confidential information located in response to the request or a copy of the responsive records, or portions of records, containing the information;</P>
              <P>(c) A description of the procedures for objecting to the release of the possibly confidential information under §§ 2.30 and 2.31 of this subpart;</P>
              <P>(d) A time limit for responding to the bureau—no less than 10 workdays from receipt or publication of the notice (as set forth in § 2.27(b) of this subpart)—to object to the release and to explain the basis for the objection;</P>
              <P>(e) Notice that information contained in the submitter's objections may itself be subject to disclosure under the FOIA;</P>
              <P>(f) Notice that the bureau, not the submitter, is responsible for deciding whether the information will be released or withheld;</P>
              <P>(g) A request for the submitter's views on whether they still consider the information to be confidential if the submitter designated the material as confidential commercial or financial information 10 or more years before the request; and</P>
              <P>(h) Notice that failing to respond within the time frame specified under § 2.28(d) of this subpart will create a presumption that the submitter has no objection to the disclosure of the information in question.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.29</SECTNO>
              <SUBJECT>When will the bureau not notify a submitter of a request for their possibly confidential information?</SUBJECT>
              <P>The notice requirements of § 2.28 of this subpart will not apply if:</P>
              <P>(a) The information has been lawfully published or officially made available to the public; or</P>
              <P>(b) Disclosure of the information is required by a statute other than the FOIA or by a regulation (other than this part) issued in accordance with the requirements of Executive Order 12600.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.30</SECTNO>
              <SUBJECT>How and when may a submitter object to the disclosure of confidential information?</SUBJECT>
              <P>(a) If a submitter has any objections to the disclosure of confidential information, the submitter should provide a detailed written statement to the bureau that specifies all grounds for withholding the particular information under any FOIA exemption (see § 2.31 of this subpart for further discussion of Exemption 4 objection statements).</P>
              <P>(b) A submitter who does not respond within the time period specified under § 2.28(d) of this subpart will be considered to have no objection to disclosure of the information. Responses received by the bureau after this time period will not be considered by the bureau unless the appropriate bureau FOIA contact determines, in his or her sole discretion, that good cause exists to accept the late response.</P>
            </SECTION>
            <SECTION>
              <PRTPAGE P="76908"/>
              <SECTNO>§ 2.31</SECTNO>
              <SUBJECT>What must a submitter include in a detailed Exemption 4 objection statement?</SUBJECT>
              <P>(a) To rely on Exemption 4 as basis for nondisclosure, the submitter must explain why the information is confidential information. To do this, the submitter must give the bureau a detailed written statement. This statement must include a specific and detailed discussion of why the information is a trade secret or, if the information is not a trade secret, the following three categories must be addressed (unless the bureau informs the submitter that a response to one of the first two categories will not be necessary):</P>
              <P>(1) Whether the Government required the information to be submitted, and if so, how substantial competitive or other business harm would likely result from release;</P>
              <P>(2) Whether the submitter provided the information voluntarily and, if so, how the information fits into a category of information that the submitter does not customarily release to the public; and</P>
              <P>(3) A certification that the information is confidential, has not been disclosed to the public by the submitter, and is not routinely available to the public from other sources.</P>
              <P>(b) If not already provided, the submitter must include a daytime telephone number, an email and mailing address, and a fax number (if available).</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.32</SECTNO>
              <SUBJECT>How will the bureau consider the submitter's objections?</SUBJECT>
              <P>(a) The bureau must carefully consider a submitter's objections and specific grounds for nondisclosure in deciding whether to disclose the requested information.</P>
              <P>(b) The bureau, not the submitter, is responsible for deciding whether the information will be released or withheld.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.33</SECTNO>
              <SUBJECT>What if the bureau determines it will disclose information over the submitter's objections?</SUBJECT>
              <P>If the bureau decides to disclose information over the objection of a submitter, the bureau must notify the submitter by certified mail or other traceable mail, return receipt requested. The notification must be sent to the submitter's last known address and must include:</P>
              <P>(a) The specific reasons why the bureau determined that the submitter's disclosure objections do not support withholding the information;</P>
              <P>(b) Copies of the records or information the bureau intends to release; and</P>
              <P>(c) Notice that the bureau intends to release the records or information no less than 10 workdays after receipt of the notice by the submitter.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.34</SECTNO>
              <SUBJECT>Will a submitter be notified of a FOIA lawsuit?</SUBJECT>
              <P>If you file a lawsuit seeking to compel the disclosure of confidential information, the bureau must promptly notify the submitter.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.35</SECTNO>
              <SUBJECT>Will you receive notification of activities involving the submitter?</SUBJECT>
              <P>If any of the following occur, the bureau will notify you:</P>
              <P>(a) The bureau provides the submitter with notice and an opportunity to object to disclosure;</P>
              <P>(b) The bureau notifies the submitter of its intent to disclose the requested information; or</P>
              <P>(c) A submitter files a lawsuit to prevent the disclosure of the information.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.36</SECTNO>
              <SUBJECT>Can a bureau release information protected by Exemption 4?</SUBJECT>
              <P>If a bureau determines that the requested information is protected from release by Exemption 4 of the FOIA, the bureau has no discretion to release the information. Release of information protected from release by Exemption 4 is prohibited by the Trade Secrets Act, a criminal provision found at 18 U.S.C. 1905.</P>
            </SECTION>
          </SUBPART>
          <SUBPART>
            <HD SOURCE="HED">Subpart G—Fees</HD>
            <SECTION>
              <SECTNO>§ 2.37</SECTNO>
              <SUBJECT>What general principles govern fees?</SUBJECT>
              <P>(a) The bureau will charge for processing requests under the FOIA in accordance with this subpart and with the OMB Fee Guidelines.</P>
              <P>(b) The bureau may contact you for additional information to resolve fee issues.</P>
              <P>(c) The bureau ordinarily will collect all applicable fees before sending copies of records to you.</P>
              <P>(d) You may usually pay fees by check, certified check, or money order made payable to the “Department of the Interior” or the bureau.</P>
              <P>(1) Where appropriate, the bureau may require that your payment be made in the form of a certified check.</P>
              <P>(2) You may also be able to pay your fees by credit card. You may contact the bureau to determine what forms of payment it accepts.</P>
              <P>(e) The bureau should ensure that it conducts searches, review, and duplication in the most efficient and the least expensive manner so as to minimize costs for both you and the bureau.</P>
              <P>(f) If the Department does not comply with any of the FOIA's statutory time limits:</P>
              <P>(1) The bureau cannot assess search fees for your FOIA request, unless unusual or exceptional circumstances apply; and</P>
              <P>(2) Depending on your fee category, the bureau may not be able to assess duplication fees for your FOIA request, as discussed in § 2.39(b) of this subpart.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.38</SECTNO>
              <SUBJECT>What are the requester fee categories?</SUBJECT>
              <P>(a) There are four categories of requesters for the purposes of determining fees—commercial-use, educational and noncommercial scientific institutions, representatives of news media, and all others.</P>
              <P>(b) The bureau's decision to place you in a particular fee category will be made on a case-by-case basis based on your intended use of the information and, in most cases, your identity. If you do not submit sufficient information in your FOIA request for the bureau to determine your proper fee category, the bureau may ask you to provide additional information (see § 2.51 of this subpart).</P>
              <P>(c) See § 2.70 of this part for the definitions of each of these fee categories.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.39</SECTNO>
              <SUBJECT>How does your requester category affect the fees you are charged?</SUBJECT>
              <P>(a) You will be charged as shown in the following table:</P>
              <GPOTABLE CDEF="s100,r50,r50,r50" COLS="4" OPTS="L2,tp0,i1">
                <TTITLE/>
                <BOXHD>
                  <CHED H="1">Requester Category</CHED>
                  <CHED H="1">Search fees</CHED>
                  <CHED H="1">Review fees</CHED>
                  <CHED H="1">Duplication fees</CHED>
                </BOXHD>
                <ROW>
                  <ENT I="01">Commercial use requester</ENT>
                  <ENT>Yes</ENT>
                  <ENT>Yes</ENT>
                  <ENT>Yes.</ENT>
                </ROW>
                <ROW>
                  <ENT I="01">Educational and non-commercial scientific institutions</ENT>
                  <ENT>No</ENT>
                  <ENT>No</ENT>
                  <ENT>Yes (first 100 pages, or equivalent volume, free).</ENT>
                </ROW>
                <ROW>
                  <ENT I="01">Representative of news media requester</ENT>
                  <ENT>No</ENT>
                  <ENT>No</ENT>
                  <ENT>Yes (first 100 pages, or equivalent volume, free).</ENT>
                </ROW>
                <ROW>
                  <ENT I="01">All other requesters</ENT>
                  <ENT>Yes (first 2 hours free)</ENT>
                  <ENT>No</ENT>
                  <ENT>Yes (first 100 pages, or equivalent volume, free).</ENT>
                </ROW>
              </GPOTABLE>
              <PRTPAGE P="76909"/>
              <P>(b) If you are in the fee category of a representative of the news media or an educational and noncommercial scientific institution and the Department does not comply with any of the FOIA's statutory time limits, the Department cannot assess duplication fees for the FOIA request in question, unless unusual or exceptional circumstances apply to the processing of the request.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.40</SECTNO>
              <SUBJECT>How will fee amounts be determined?</SUBJECT>
              <P>(a) The bureau will charge the types of fees discussed below unless a waiver of fees is required under § 2.39 of this subpart or has been granted under § 2.45 or § 2.56.</P>
              <P>(b) Because the types of fees discussed below already account for the overhead costs associated with a given fee type, the bureau should not add any additional costs to those charges.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.41</SECTNO>
              <SUBJECT>What search fees will you have to pay?</SUBJECT>
              <P>(a) The bureau will charge search fees for all requests, subject to the restrictions of §§ 2.37(f), 2.39, and 2.40(a) of this subpart. The bureau may charge you for time spent searching even if it does not locate any responsive records or if it determines that the records are entirely exempt from disclosure.</P>
              <P>(b) For each quarter hour spent by personnel searching for requested records, including electronic searches that do not require new programming, the fees will be the average hourly General Schedule (GS) base salary, plus the District of Columbia locality payment, plus 16 percent for benefits, of employees in the following three categories, as applicable:</P>
              <P>(1) Clerical—Based on GS-6, Step 5, pay (all employees at GS-7 and below are classified as clerical for this purpose);</P>
              <P>(2) Professional—Based on GS-11, Step 7, pay (all employees at GS-8 through GS-12 are classified as professional for this purpose); and</P>
              <P>(3) Managerial—Based on GS-14, Step 2, pay (all employees at GS-13 and above are classified as managerial for this purpose).</P>

              <P>(c) You can review the current fee schedule for the categories discussed above in paragraph (b) of this section at<E T="03">http://www.doi.gov/foia/fees-waivers.cfm.</E>
              </P>
              <P>(d) Some requests may require retrieval of records stored at a Federal records center operated by the National Archives and Records Administration. For these requests, bureaus will charge additional costs in accordance with the Transactional Billing Rate Schedule established by the National Archives and Records Administration.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.42</SECTNO>
              <SUBJECT>What duplication fees will you have to pay?</SUBJECT>
              <P>(a) The bureau will charge duplication fees, subject to the restrictions of §§ 2.37(f), 2.39, and 2.40(a) of this subpart.</P>
              <P>(b) If photocopies or scans are supplied, the bureau will provide one copy per request at the cost determined by the table in appendix A to this part.</P>
              <P>(c) For other forms of duplication, the bureau will charge the actual costs of producing the copy, including the time spent by personnel duplicating the requested records. For each quarter hour spent by personnel duplicating the requested records, the fees will be the same as those charged for a search under § 2.41(b) of this subpart.</P>
              <P>(d) If the bureau must scan paper records to accommodate your preference to receive records in an electronic format, you will pay both the per page amount noted in Appendix A to this part and the time spent by personnel scanning the requested records. For each quarter hour spent by personnel scanning the requested records, the fees will be the same as those charged for a search under § 2.41(b) of this subpart.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.43</SECTNO>
              <SUBJECT>What review fees will you have to pay?</SUBJECT>
              <P>(a) The bureau will charge review fees if you make a commercial-use request, subject to the restrictions of §§ 2.37(f), 2.39, and 2.40(a) of this subpart.</P>
              <P>(b) The bureau will assess review fees in connection with the initial review of the record (the review conducted by the bureau to determine whether an exemption applies to a particular record or portion of a record).</P>
              <P>(c) The Department will not charge for reviews at the administrative appeal stage of exemptions applied at the initial review stage. However, if the appellate authority determines that an exemption no longer applies, any costs associated with the bureau's re-review of the records to consider the use of other exemptions may be assessed as review fees.</P>
              <P>(d) The bureau will charge review fees at the same rates as those charged for a search under § 2.41(b) of this subpart.</P>
              <P>(e) The bureau can charge review fees even if the record(s) reviewed ultimately is not disclosed.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.44</SECTNO>
              <SUBJECT>What fees for other services will you have to pay?</SUBJECT>
              <P>(a) Although not required to provide special services, if the bureau chooses to do so as a matter of administrative discretion, it will charge you the direct costs of providing the service.</P>
              <P>(b) Examples of these services include certifying that records are true copies under subpart L of this part, providing multiple copies of the same record, converting records to a requested format, obtaining research data under § 2.69 of this part, or sending records by means other than first class mail.</P>
              <P>(c) The bureau will notify you of these fees before they accrue and will obtain your written assurance of payment or an advance payment before proceeding. See §§ 2.49 and 2.50 of this subpart.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.45</SECTNO>
              <SUBJECT>When will the bureau waive fees?</SUBJECT>
              <P>(a) The bureau will release records responsive to a request without charge (in other words, it will give you a full fee waiver) or at a reduced charge (in other words, it will give you a partial fee waiver, as discussed further in paragraph (b) of this section) if the bureau determines, based on all available information, that you have demonstrated (under the factors listed in § 2.48 of this subpart) that disclosing the information is:</P>
              <P>(1) In the public interest because it is likely to contribute significantly to public understanding of government operations or activities, and</P>
              <P>(2) Not primarily in your commercial interest.</P>
              <P>(b) A partial fee waiver may be appropriate if some but not all of the requested records are likely to contribute significantly to public understanding of the operations and activities of the government.</P>
              <P>(c) When deciding whether to waive or reduce fees, the bureau will rely on the fee waiver justification submitted in your request letter. If the letter does not include sufficient justification, the bureau will deny the fee waiver request. The bureau may, at its discretion, request additional information from you (see § 2.51 of this subpart).</P>
              <P>(d) The burden is on you to justify entitlement to a fee waiver. Requests for fee waivers are decided on a case-by-case basis under the criteria discussed above in paragraph (a) of this section and § 2.48 of this subpart. If you have received a fee waiver in the past, that does not mean you are automatically entitled to a fee waiver for every request submitted.</P>
              <P>(e) Discretionary fee waivers are addressed in § 2.56 of this subpart.</P>
              <P>(f) The bureau must not make value judgments about whether the information at issue is “important” enough to be made public; it is not the bureau's role to attempt to determine the level of public interest in requested information.</P>
            </SECTION>
            <SECTION>
              <PRTPAGE P="76910"/>
              <SECTNO>§ 2.46</SECTNO>
              <SUBJECT>When may you ask the bureau for a fee waiver?</SUBJECT>
              <P>(a) You should request a fee waiver when your request is first submitted to the bureau (see § 2.6 of this part).</P>
              <P>(b) You may submit a fee waiver request at a later time if the underlying record request is still either pending or on administrative appeal.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.47</SECTNO>
              <SUBJECT>How will the bureau notify you if it denies your fee waiver request?</SUBJECT>
              <P>If the bureau denies your request for a fee waiver, it will notify you, in writing, of the following:</P>
              <P>(a) The basis for the denial, including a full explanation of why the fee waiver request does not meet the Department's fee waiver criteria in § 2.48 of this subpart.</P>
              <P>(b) The name and title or position of each person responsible for the denial;</P>
              <P>(c) The name and title of the Office of the Solicitor attorney consulted; and</P>
              <P>(d) Your right to appeal the denial to the FOIA Appeals Officer, under the procedures in § 2.57 of this part, within 30 workdays after the date of the fee waiver denial letter.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.48</SECTNO>
              <SUBJECT>How will the bureau evaluate your fee waiver request?</SUBJECT>
              <P>(a) In deciding whether your fee waiver request meets the requirements of § 2.45(a)(1) of this subpart, the bureau will consider the criteria listed in paragraphs one through four below. You must address each of these criteria.</P>
              <P>(1) How the records concern the operations or activities of the Federal government.</P>
              <P>(2) How disclosure is likely to contribute to public understanding of those operations or activities, including:</P>
              <P>(i) How the contents of the records are meaningfully informative;</P>
              <P>(ii) The logical connection between the content of the records and the operations or activities;</P>
              <P>(iii) How disclosure will contribute to the understanding of a reasonably broad audience of persons interested in the subject, as opposed to your individual understanding;</P>
              <P>(iv) Your identity, vocation, qualifications, and expertise regarding the requested information and information that explains how you plan to disclose the information in a manner that will be informative to the understanding of a reasonably broad audience of persons interested in the subject, as opposed to your individual understanding</P>
              <P>(v) Your ability and intent to disseminate the information to a reasonably broad audience of persons interested in the subject (for example, how and to whom do you intend to disseminate the information).</P>
              <P>(3) How disclosure is likely to significantly contribute to the understanding of a reasonably broad audience of persons interested in the subject, as opposed to your individual understanding, including:</P>
              <P>(i) Whether the information being requested is new;</P>
              <P>(ii) Whether the information would confirm or clarify data that has been released previously;</P>
              <P>(iii) How disclosure will increase the level of public understanding of the operations or activities of the Department or a bureau that existed prior to disclosure; and</P>
              <P>(iv) Whether the information is already publicly available. If the Government previously has published the information you are seeking or it is routinely available to the public in a library, reading room, through the Internet, or as part of the administrative record for a particular issue, it is less likely that there will be a significant contribution from release.</P>
              <P>(4) How the public's understanding of the subject in question will be enhanced to a significant extent by the disclosure.</P>
              <P>(b) In deciding whether the fee waiver meets the requirements in § 2.45(a)(2) of this subpart, the bureau will consider any commercial interest of yours that would be furthered by the requested disclosure.</P>
              <P>(1) You are encouraged to provide explanatory information regarding this consideration.</P>
              <P>(2) The bureau will not find that disclosing the requested information will be primarily in your commercial interest where the public interest is greater than any identified commercial interest in disclosure.</P>
              <P>(3) If you do have a commercial interest that would be furthered by disclosure, explain how the public interest in disclosure would be greater than any commercial interest you or your organization may have in the documents.</P>
              <P>(i) Your identity, vocation, and intended use of the requested records are all factors to be considered in determining whether disclosure would be primarily in your commercial interest.</P>
              <P>(ii) If you are a representative of a news media organization seeking information as part of the news gathering process, we will presume that the public interest outweighs your commercial interest.</P>
              <P>(iii) If you represent a business/corporation/association or you are an attorney representing such an organization, we will presume that your commercial interest outweighs the public interest unless you demonstrate otherwise.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.49</SECTNO>
              <SUBJECT>When will you be notified of anticipated fees?</SUBJECT>
              <P>(a) The bureau will notify you under this section unless:</P>
              <P>(1) The anticipated fee is less than $50 (you will not be charged if the fee for processing your request is less than $50, unless multiple requests are aggregated under § 2.54 of this subpart).</P>
              <P>(2) You have been granted a full fee waiver; or</P>
              <P>(3) You have previously agreed to pay all the fees associated with the request.</P>
              <P>(b) If none of the above exceptions apply, the bureau will:</P>
              <P>(1) Promptly notify you of the estimated costs for search, review, and/or duplication;</P>
              <P>(2) Ask you to provide written assurance within 20 workdays that you will pay all fees or fees up to a designated amount;</P>
              <P>(3) Notify you that it will not be able to comply with your FOIA request unless you provide the written assurance requested; and</P>
              <P>(4) Give you an opportunity to reduce the fee by modifying the request.</P>
              <P>(c) If the bureau does not receive your written assurance of payment under paragraph (b)(2) of this section within 20 workdays, the request will be closed.</P>
              <P>(d) After the bureau begins processing a request, if it finds that the actual cost will exceed the amount you previously agreed to pay, the bureau will:</P>
              <P>(1) Stop processing the request;</P>
              <P>(2) Promptly notify you of the higher amount and ask you to provide written assurance of payment; and</P>
              <P>(3) Notify you that it will not be able to fully comply with your FOIA request unless you provide the written assurance requested; and</P>
              <P>(4) Give you an opportunity to reduce the fee by modifying the request.</P>
              <P>(e) If you wish to modify your request in an effort to reduce fees, the bureau's FOIA Public Liaison can assist you.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.50</SECTNO>
              <SUBJECT>When will the bureau require advance payment?</SUBJECT>
              <P>(a) The bureau will require advance payment before starting further work when it finds the estimated fee is over $250 and:</P>
              <P>(1) You have never made a FOIA request to the Department requiring the payment of fees; or</P>
              <P>(2) You did not pay a previous FOIA fee within 30 calendar days of the date of billing.</P>

              <P>(b) If the bureau believes that you did not pay a previous FOIA fee within 30 calendar days of the date of billing, the bureau will require you to either:<PRTPAGE P="76911"/>
              </P>
              <P>(1) Demonstrate you paid prior fee within 30 calendar days of the date of billing; or</P>
              <P>(2) Pay any unpaid amount of the previous fee, plus any applicable interest penalties (see § 2.53 of this subpart), and pay in advance the estimated fee for the new request.</P>
              <P>(c) When the bureau notifies you that an advance payment is due, it will give you an opportunity to reduce the fee by modifying the request.</P>
              <P>(d) The bureau may require payment before records are sent to you; such a payment is not considered an “advance payment” under § 2.50(a) of this subpart.</P>
              <P>(e) If the bureau requires advance payment, it will start further work only after receiving the advance payment. It will also notify you that it will not be able to comply with your FOIA request unless you provide the advance payment. Unless you pay the advance payment within 20 workdays after the date of the bureau's fee letter, the bureau will presume that you are no longer interested and will close the file on the request.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.51</SECTNO>
              <SUBJECT>What if the bureau needs clarification about fee issues?</SUBJECT>
              <P>(a) If your FOIA request does not contain sufficient information for the bureau to determine your proper fee category or leaves another fee issue unclear, the bureau may ask you to provide additional clarification. If it does so, the bureau will notify you that it will not be able to comply with your FOIA request unless you provide the clarification requested.</P>
              <P>(b) If the bureau asks you to provide clarification, the 20-workday statutory time limit for the bureau to respond to the request is temporarily suspended.</P>
              <P>(1) If the bureau hears from you within 20 workdays, the 20-workday statutory time limit for processing the request will resume (see § 2.16 of this part).</P>
              <P>(2) If you still have not provided sufficient information to resolve the fee issue, the bureau may ask you again to provide additional clarification and notify you that it will not be able to comply with your FOIA request unless you provide the additional information requested within 20 workdays.</P>
              <P>(3) If the bureau asks you again for additional clarification, the statutory time limit for response will be temporarily suspended again and will resume again if the bureau hears from you within 20 workdays.</P>
              <P>(c) If the bureau asks for clarification about a fee issue and does not receive a written response from you within 20 workdays, it will presume that you are no longer interested and will close the file on the request.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.52</SECTNO>
              <SUBJECT>How will you be billed?</SUBJECT>
              <P>If you are required to pay a fee associated with a FOIA request, the bureau processing the request will send a bill for collection.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.53</SECTNO>
              <SUBJECT>How will the bureau collect fees owed?</SUBJECT>
              <P>(a) The bureau may charge interest on any unpaid bill starting on the 31st day following the billing date.</P>
              <P>(b) The bureau will assess interest charges at the rate provided in 31 U.S.C. 3717 and implementing regulations and interest will accrue from the billing date until the bureau receives payment.</P>
              <P>(c) The bureau will follow the provisions of the Debt Collection Act of 1982 (Public Law 97-365, 96 Stat. 1749), as amended, and its administrative procedures, including the use of consumer reporting agencies, collection agencies, and offset to collect overdue amounts and interest.</P>
              <P>(d) This section does not apply if you are a state, local, or tribal government.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.54</SECTNO>
              <SUBJECT>When will the bureau combine or aggregate requests?</SUBJECT>
              <P>(a) The bureau may aggregate requests and charge accordingly when it reasonably believes that you, or a group of requesters acting in concert with you, are attempting to avoid fees by dividing a single request into a series of requests on a single subject or related subjects.</P>
              <P>(1) The bureau may presume that multiple requests of this type made within a 30-day period have been made to avoid fees.</P>
              <P>(2) The bureau may aggregate requests separated by a longer period only where there is a reasonable basis for determining that aggregation is warranted in view of all the circumstances involved.</P>
              <P>(b) The bureau will not aggregate multiple requests involving unrelated matters.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.55</SECTNO>
              <SUBJECT>What if other statutes require the bureau to charge fees?</SUBJECT>
              <P>(a) The fee schedule in appendix A to this part does not apply to fees charged under any statute that specifically requires the bureau to set and collect fees for particular types of records.</P>
              <P>(b) If records otherwise responsive to a request are subject to a statutorily-based fee schedule, the bureau will inform you whom to contact to obtain the records.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.56</SECTNO>
              <SUBJECT>May the bureau waive or reduce your fees at its discretion?</SUBJECT>
              <P>(a) The bureau may waive or reduce fees at its discretion if a request involves furnishing:</P>
              <P>(1) A copy of a record that the bureau has reproduced for free distribution;</P>
              <P>(2) One copy of a personal document (for example, a birth certificate) to a person who has been required to furnish it for retention by the Department;</P>
              <P>(3) One copy of the transcript of a hearing before a hearing officer in a grievance or similar proceeding to the employee for whom the hearing was held;</P>
              <P>(4) Records to donors with respect to their gifts;</P>
              <P>(5) Records to individuals or private nonprofit organizations having an official, voluntary, or cooperative relationship with the Department if it will assist their work with the Department;</P>
              <P>(6) A reasonable number of records to members of the U.S. Congress; state, local, and foreign governments; public international organizations; or Indian tribes, when to do so is an appropriate courtesy, or when the recipient is carrying on a function related to a Departmental function and the waiver will help accomplish the Department's work;</P>
              <P>(7) Records in conformance with generally established business custom (for example, furnishing personal reference data to prospective employers of current or former Department employees); or</P>
              <P>(8) One copy of a single record to assist you in obtaining financial benefits to which you may be entitled (for example, veterans or their dependents, employees with Government employee compensation claims).</P>
              <P>(b) You cannot appeal the denial of a discretionary fee waiver or reduction.</P>
            </SECTION>
          </SUBPART>
          <SUBPART>
            <HD SOURCE="HED">Subpart H—Administrative Appeals</HD>
            <SECTION>
              <SECTNO>§ 2.57</SECTNO>
              <SUBJECT>When may you file an appeal?</SUBJECT>
              <P>(a) You may file an appeal when:</P>
              <P>(1) The bureau withholds records, or parts of records;</P>
              <P>(2) The bureau informs you that your request has not adequately described the records sought;</P>
              <P>(3) The bureau informs you that it does not possess or cannot locate responsive records and you have reason to believe this is incorrect or that the search was inadequate;</P>
              <P>(4) The bureau did not address all aspects of the request for records;</P>
              <P>(5) You believe there is a procedural deficiency (for example, fees are improperly calculated);</P>
              <P>(6) The bureau denied a fee waiver;</P>
              <P>(7) The bureau did not make a decision within the time limits in § 2.16 or, if applicable, § 2.18; or</P>

              <P>(8) The bureau denied, or was late in responding to, a request for expedited<PRTPAGE P="76912"/>processing filed under the procedures in § 2.20 of this part.</P>
              <P>(b) An appeal under paragraph (a)(8) of this section relates only to the request for expedited processing and does not constitute an appeal of the underlying request for records. Special procedures apply to requests for expedited processing of an appeal (see § 2.63 of this subpart).</P>
              <P>(c) Before filing an appeal, you may wish to communicate with the contact person listed in the FOIA response, the bureau's FOIA Officer, and/or the FOIA Public Liaison to see if the issue can be resolved informally. However, appeals must be received by the FOIA Appeals Officer within the time limits in § 2.58 of this subpart or they will not be processed.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.58</SECTNO>
              <SUBJECT>How long do you have to file an appeal?</SUBJECT>
              <P>(a) Appeals covered by § 2.57(a)(1) through (5) of this subpart must be received by the FOIA Appeals Officer no later than 30 workdays from the date of the final response.</P>
              <P>(b) Appeals covered by § 2.57(a)(6) of this subpart must be received by the FOIA Appeals Officer no later than 30 workdays from the date of the letter denying the fee waiver.</P>
              <P>(c) Appeals covered by § 2.57(a)(7) of this subpart may be filed any time after the time limit for responding to the request has passed.</P>
              <P>(d) Appeals covered by § 2.57(a)(8) of this subpart should be filed as soon as possible.</P>
              <P>(e) Appeals arriving or delivered after 5 p.m. Eastern Time, Monday through Friday, will be deemed received on the next workday.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.59</SECTNO>
              <SUBJECT>How do you file an appeal?</SUBJECT>

              <P>(a) You must submit the appeal in writing by mail, fax or email to the FOIA Appeals Officer (using the address available at<E T="03">http://www.doi.gov/foia/appeals.cfm)</E>. Your failure to send an appeal directly to the FOIA Appeals Officer may delay processing.</P>
              <P>(b) The appeal must include:</P>
              <P>(1) Copies of all correspondence between you and the bureau concerning the FOIA request, including the request and the bureau's response (if there is one); and</P>
              <P>(2) An explanation of why you believe the bureau's response was in error.</P>
              <P>(c) The appeal should include your name, mailing address, daytime telephone number (or the name and telephone number of an appropriate contact), email address, and fax number (if available) in case the Department needs additional information or clarification.</P>
              <P>(d) An appeal concerning a denial of expedited processing or a fee waiver denial should also demonstrate fully how the criteria in § 2.20 or §§ 2.45 and 2.48 of this part are met.</P>
              <P>(e) All communications concerning an appeal should be clearly marked with the words: “FREEDOM OF INFORMATION APPEAL.”</P>
              <P>(f) The Department will reject an appeal that does not attach all correspondence required by paragraph (b)(1) of this section, unless the FOIA Appeals Officer determines, in his or her sole discretion, that good cause exists to accept the defective appeal. The time limits for responding to an appeal will not begin to run until the correspondence is received.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.60</SECTNO>
              <SUBJECT>Who makes decisions on appeals?</SUBJECT>
              <P>(a) The FOIA Appeals Officer is the deciding official for FOIA appeals.</P>
              <P>(b) When necessary, the FOIA Appeals Officer will consult other appropriate offices, including the Office of the Solicitor for denials of records and fee waivers.</P>
              <P>(c) The FOIA Appeals Officer normally will not make a decision on an appeal if the request becomes a matter of FOIA litigation.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.61</SECTNO>
              <SUBJECT>How are decisions on appeals issued?</SUBJECT>
              <P>(a) A decision on an appeal must be made in writing.</P>
              <P>(b) A decision that upholds the bureau's determination will notify you of the decision and your statutory right to file a lawsuit.</P>
              <P>(c) A decision that overturns, remands, or modifies the bureau's determination will notify you of the decision. The bureau then must further process the request in accordance with the appeal determination.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.62</SECTNO>
              <SUBJECT>When can you expect a decision on your appeal?</SUBJECT>
              <P>(a) The basic time limit for responding to an appeal is 20 workdays after receipt of an appeal meeting the requirements of § 2.59 of this subpart.</P>
              <P>(b) The FOIA Appeals Officer may extend the basic time limit, if unusual circumstances exist. Before the expiration of the basic 20-workday time limit to respond, the FOIA Appeals Officer will notify you in writing of the unusual circumstances involved and of the date by which he or she expects to complete processing of the appeal.</P>
              <P>(c) If the Department is unable to reach a decision on your appeal within the given time limit for response, the FOIA Appeals Officer will notify you of:</P>
              <P>(1) The reason for the delay; and</P>
              <P>(2) Your statutory right to seek review in a United States District Court.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.63</SECTNO>
              <SUBJECT>Can you receive expedited processing of appeals?</SUBJECT>
              <P>(a) To receive expedited processing of an appeal, you must demonstrate to the Department's satisfaction that the appeal meets one of the criteria under § 2.20 of this part and include a statement that the need for expedited processing is true and correct to the best of your knowledge and belief.</P>
              <P>(b) The FOIA Appeals Officer will advise you whether the Department will grant expedited processing within 10 calendar days of receiving the appeal.</P>
              <P>(c) If the FOIA Appeals Officer decides to grant expedited processing, he or she will give the appeal priority over other pending appeals and process it as soon as practicable.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.64</SECTNO>
              <SUBJECT>Must you submit an appeal before seeking judicial review?</SUBJECT>
              <P>Before seeking review by a court of the bureau's adverse determination, you generally must first submit a timely administrative appeal.</P>
            </SECTION>
          </SUBPART>
          <SUBPART>
            <HD SOURCE="HED">Subpart I—General Information</HD>
            <SECTION>
              <SECTNO>§ 2.65</SECTNO>
              <SUBJECT>Where are records made available?</SUBJECT>

              <P>Records that are required by the FOIA to be made proactively available for public inspection and copying are accessible on the Department's Web site,<E T="03">http://www.doi.gov/foia/libraries.cfm</E>. They may also be available at bureau office locations.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.66</SECTNO>
              <SUBJECT>What are public liaisons?</SUBJECT>
              <P>(a) Each bureau has a FOIA Public Liaison that can assist individuals in locating bureau records.</P>
              <P>(b) FOIA Public Liaisons report to the Department's Chief FOIA Officer and you can raise concerns to them about the service you have received.</P>
              <P>(c) FOIA Public Liaisons are responsible for assisting in reducing delays, increasing transparency and understanding of the status of requests, and assisting in resolving disputes.</P>

              <P>(d) A list of the Department's FOIA Public Liaisons is available at<E T="03">http://doi.gov/foia/servicecenters.cfm</E>.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.67</SECTNO>
              <SUBJECT>When will the Department make records available without a FOIA request?</SUBJECT>
              <P>(a) Each bureau must:</P>
              <P>(1) Determine which of its records must be made publicly available under the FOIA (for example, certain frequently requested records);</P>
              <P>(2) Identify additional records of interest to the public that are appropriate for public disclosure; and</P>
              <P>(3) Post those records in FOIA libraries.</P>

              <P>(b) Because of these proactive disclosures, you are encouraged to review the Department's FOIA libraries<PRTPAGE P="76913"/>before filing a FOIA request. The material you seek may be immediately available electronically at no cost.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.68</SECTNO>
              <SUBJECT>How will FOIA materials be preserved?</SUBJECT>
              <P>(a) Each bureau must preserve all correspondence pertaining to the requests that it receives under subpart B of this part, as well as copies of all requested records, until disposition or destruction is authorized by the General Records Schedule 14 of the National Archives and Records Administration (NARA) or another NARA-approved records schedule.</P>
              <P>(b) Materials that are identified as responsive to a FOIA request will not be disposed of or destroyed while the request or a related appeal or lawsuit is pending. This is true even if they would otherwise be authorized for disposition or destruction under the General Records Schedule 14 of NARA or another NARA-approved records schedule.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.69</SECTNO>
              <SUBJECT>How will a bureau handle a request for federally-funded research data?</SUBJECT>
              <P>(a) If you request research data that were used by the Federal Government in developing certain kinds of agency actions, and the research data relate to published research findings produced under an award, in accordance with OMB Circular A-110:</P>
              <P>(1) If the bureau was the awarding agency, it will request the research data from the recipient;</P>
              <P>(2) The recipient must provide the research data within a reasonable time; and</P>
              <P>(3) The bureau will review the research data to see if it can be released under the FOIA.</P>
              <P>(b) If the bureau obtains the research data solely in response to your FOIA request, the bureau may charge you a reasonable fee equaling the full incremental cost of obtaining the research data.</P>
              <P>(1) This fee should reflect costs incurred by the agency, the recipient, and applicable subrecipients.</P>
              <P>(2) This fee is in addition to any fees the agency may assess under the FOIA.</P>
              <P>(c) The bureau will forward a copy of the request to the recipient, who is responsible for searching for and reviewing the requested information in accordance with these FOIA regulations. The recipient will forward a copy of any responsive records that are located, along with any recommendations concerning the releasability of the data, and the total cost incurred in searching for, reviewing, and providing the data.</P>
              <P>(d) The bureau will review and consider the recommendations of the recipient regarding the releasability of the requested research data. However, the bureau, not the recipient, is responsible for deciding whether the research data will be released or withheld.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 2.70</SECTNO>
              <SUBJECT>What definitions apply to subparts A through I of this part?</SUBJECT>
              <P>For the purposes of subparts A through I of this part, the following definitions apply:</P>
              <P>
                <E T="03">Bureau</E>means any major component of the Department administering its own FOIA program. A list of these components is available at:<E T="03">http://www.doi.gov/foia/contacts.cfm.</E>
              </P>
              <P>
                <E T="03">Commercial interest</E>means a commercial, trade, or profit interest as these terms are commonly understood. Your status as profitmaking or non-profitmaking is not the deciding factor in determining whether you have a commercial interest.</P>
              <P>
                <E T="03">Commercial use</E>means a use that furthers your commercial, trade or profit interests or that of the person on whose behalf the request is made.</P>
              <P>
                <E T="03">Confidential information</E>means trade secrets or commercial or financial information (that is privileged or confidential and obtained by the Department from a person) that may be protected from disclosure under Exemption 4 of the FOIA.</P>
              <P>
                <E T="03">Department</E>means the Department of the Interior.</P>
              <P>
                <E T="03">Direct costs</E>means those resources that the bureau expends in searching for and duplicating (and, in the case of commercial-use requests, reviewing) records to respond to a FOIA request. For example, direct costs include the salary of the employee performing the work (the basic rate of pay for the employee plus 16 percent of that rate to cover benefits) and the cost of operating duplicating machinery, such as photocopiers and scanners. Direct costs do not include overhead expenses such as the costs of space and of heating or lighting a facility.</P>
              <P>
                <E T="03">Duplication</E>means reproducing a copy of a record or of the information contained in it necessary to respond to a FOIA request. Copies can take the form of paper, audiovisual materials, or electronic records, among others.</P>
              <P>
                <E T="03">Educational institution</E>means any school that operates a program of scholarly research. In order to fall within this category, you must show that the request is authorized by and made under the auspices of, a qualifying institution and that the records are not sought for a commercial use, but rather are sought to further scholarly research.</P>
              <P>
                <E T="03">Exceptional circumstances</E>means a delay that does not result from a predictable workload of requests (unless the bureau demonstrates reasonable progress in reducing its backlog of pending requests).</P>
              <P>
                <E T="03">Exempt</E>means the record in question, or a portion thereof, is not subject to disclosure due to one or more of the FOIA's nine statutory exemptions, found at 5 U.S.C. 552(b)(1)-(9).</P>
              <P>
                <E T="03">Exemption</E>means one or more of the FOIA's nine statutory exemptions, found at 5 U.S.C. 552(b)(1)-(9).</P>
              <P>
                <E T="03">Expedited processing</E>means giving a FOIA request priority and processing it ahead of other requests pending in the bureau because you have shown a compelling need for the records.</P>
              <P>
                <E T="03">Fee category</E>means one of the four categories, discussed in §§ 2.38 and 2.39, that agencies place you in for the purpose of determining whether you will be charged fees for search, review, and duplication.</P>
              <P>
                <E T="03">FOIA</E>means the Freedom of Information Act, 5 U.S.C. 552, as amended.</P>
              <P>
                <E T="03">FOIA libraries</E>means a physical or electronic compilation of records required to be made available to the public for inspection and copying under 5 U.S.C. 552(a)(2). It also includes a physical or electronic compilation of records that the bureau, at its discretion, makes available to the public for inspection and copying.</P>
              <P>
                <E T="03">Frequently requested records</E>means records that have been released to any person in response to a FOIA request and that have been requested, or that the bureau anticipates will be requested, at least two more times under the FOIA.</P>
              <P>
                <E T="03">Multitrack processing</E>means placing simple requests, requiring relatively minimal review, in one processing track and more voluminous and complex requests in one or more other tracks. Requests in each track are processed on a first-in/first-out basis.</P>
              <P>
                <E T="03">Noncommercial scientific institution</E>means an institution that is not operated for commerce, trade or profit, and that is operated solely for the purpose of conducting scientific research the results of which are not intended to promote any particular product or industry. To be in this category, you must show that the request is authorized by and is made under the auspices of a qualifying institution and that the records are not sought for a commercial use but are sought to further scientific research.</P>
              <P>
                <E T="03">OMB Fee Guidelines</E>means the Uniform Freedom of Information Fee Schedule and Guidelines published by the Office of Management and Budget at 52 FR 10012 (Mar. 27, 1987).</P>
              <P>
                <E T="03">Published</E>means, for the purposes of § 2.69 of this subpart only, when:<PRTPAGE P="76914"/>
              </P>
              <P>(1) Research findings are published in a peer-reviewed scientific or technical journal; or</P>
              <P>(2) A Federal agency publicly and officially cites the research findings in support of an agency action that has the force and effect of law.</P>
              <P>
                <E T="03">Recipient</E>means, for the purposes of § 2.69 of this subpart only, an organization receiving financial assistance directly from Federal awarding agencies to carry out a project or program. The term includes public and private institutions of higher education, public and private hospitals, and other quasi-public and private non-profit organizations. The term may include commercial organizations, foreign or international organizations (such as agencies of the United Nations) which are recipients, subrecipients, or contractors or subcontractors of recipients or subrecipients at the discretion of the Federal awarding agency. The term does not include government-owned contractor-operated facilities or research centers providing continued support for mission-oriented, large-scale programs that are government-owned or controlled, or are designated as federally-funded research and development centers.</P>
              <P>
                <E T="03">Record</E>means an agency record that is either created or obtained by an agency and is under agency possession and control at the time of the FOIA request, or is maintained by an entity under Government contract for the purposes of records management.</P>
              <P>
                <E T="03">Representative of the news media</E>means any person or entity that gathers information of potential interest to a segment of the public, uses its editorial skills to turn the raw materials into a distinct work, and distributes that work to an audience. The term<E T="03">news</E>as used in this definition means information that is about current events or that would be of current interest to the public. Examples of news media entities are newspapers, television, Web sites, or radio stations broadcasting to the public at large, and publishers of periodicals (but only if such entities qualify as disseminators of news) who make their products available for purchase by or subscription by or free distribution to the general public. These examples are not all inclusive. As methods of news delivery evolve, alternative representatives of news media may come into being. A freelance journalist will qualify as a news-media entity if he or she can demonstrate a solid basis for expecting publication through that entity, whether or not the journalist is actually employed by that entity (for example, a publication contract would present a solid basis for such an expectation).</P>
              <P>
                <E T="03">Research data</E>means, for the purposes of § 2.69 of this subpart only, the recorded factual material commonly accepted in the scientific community as necessary to validate research findings, but not any of the following: preliminary analyses, drafts of scientific papers, plans for future research, peer reviews, or communications with colleagues. The term<E T="03">recorded</E>as used in this definition excludes physical objects (e.g., laboratory samples). Research data also do not include:</P>
              <P>(1) Trade secrets, commercial information, materials necessary to be held confidential by a researcher until they are published, or similar information which is protected under law; and</P>
              <P>(2) Personnel and medical information and similar information the disclosure of which would constitute a clearly unwarranted invasion of personal privacy, such as information that could be used to identify a particular person in a research study.</P>
              <P>
                <E T="03">Review</E>means the examination of a record located in response to a request to determine whether any portion of it is exempt from disclosure. Review time includes processing any record for disclosure, such as doing all that is necessary to prepare the record for disclosure, including the process of redacting the record and marking the appropriate exemptions. Review time also includes time spent both obtaining and considering any formal objection to disclosure made by a confidential information submitter under subpart G of this part, but it excludes time spent resolving general legal or policy issues regarding the application of FOIA exemptions.</P>
              <P>
                <E T="03">Search</E>means the process of looking for and retrieving records responsive to a request. Search time includes page-by-page or line-by-line identification of information within records; and the reasonable efforts expended to locate and retrieve electronic records.</P>
              <P>
                <E T="03">Submitter</E>means any person or entity outside the Federal Government from whom the Department obtains confidential information, directly or indirectly. The term includes, but is not limited to individuals, corporations, and state, local, tribal, and foreign governments.</P>
              <P>
                <E T="03">Unusual circumstances</E>means the need to search for and collect requested records from field facilities or other establishments that are separate from the office processing the request; the need to search for, collect, and examine a voluminous amount of separate and distinct records which are demanded in a single request; or the need for consultation, which shall be conducted with all practicable speed, with another agency, or among two or more components of the Department, having a substantial interest in the determination of the request.</P>
              <P>
                <E T="03">Workday</E>means a regular Federal workday. It excludes Saturdays, Sundays, or Federal legal public holidays. Items arriving or delivered after 5 p.m. Eastern Time will be deemed received on the next workday.</P>
              <P>
                <E T="03">You</E>means a person requesting records, or filing an appeal, under the FOIA.</P>
            </SECTION>
          </SUBPART>
        </REGTEXT>
        <HD SOURCE="HD1">Appendix A to Part 2 [Removed]</HD>
        <REGTEXT PART="2" TITLE="43">
          <AMDPAR>6. Appendix A to Part 2 is removed.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="2" TITLE="43">
          <HD SOURCE="HD1">Appendix B to Part 2 [Removed]</HD>
        </REGTEXT>
        <REGTEXT PART="2" TITLE="43">
          <AMDPAR>7. Appendix B to Part 2 is removed.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="2" TITLE="43">
          <HD SOURCE="HD1">Appendix C to Part 2 [Redesignated as Appendix A to Part 2]</HD>
        </REGTEXT>
        <REGTEXT PART="2" TITLE="43">
          <AMDPAR>8. Appendix C to Part 2 is redesignated as Appendix A to Part 2 and revised to read as follows.</AMDPAR>
          <HD SOURCE="HD1">Appendix A to Part 2—Fee Schedule</HD>
          <GPOTABLE CDEF="s100,r100" COLS="2" OPTS="L2,tp0,i1">
            <TTITLE/>
            <BOXHD>
              <CHED H="1">Types of Records</CHED>
              <CHED H="1">Fee</CHED>
            </BOXHD>
            <ROW>
              <ENT I="22">(1) Physical records:</ENT>
              <ENT/>
            </ROW>
            <ROW>
              <ENT I="22">Pages no larger than 8.5 × 14 inches, when reproduced by standard office copying machines or scanned into an electronic format</ENT>
              <ENT>$.15 per page ($.30 for double-sided copying).</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Color copies of pages no larger than 8.5 × 11 inches</ENT>
              <ENT>$.90 per page.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Pages larger than 8.5 × 14 inches</ENT>
              <ENT>Direct cost to DOI.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Color copies of pages no larger than 11 × 17 inches</ENT>
              <ENT>$1.50 per page.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Photographs and records requiring special handling (for example, because of age, size, or format)</ENT>
              <ENT>Direct cost to DOI.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">(2) Electronic records:</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Charges for services related to processing requests for electronic records</ENT>
              <ENT>Direct cost to DOI.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="76915"/>
              <ENT I="22">(3) Certification</ENT>
              <ENT>Fee.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Each certificate of verification attached to authenticate copies of records</ENT>
              <ENT>$.25</ENT>
            </ROW>
            <ROW>
              <ENT I="22">(4) Postage:</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Charges that exceed the cost of first class postage, such as express mail or overnight delivery</ENT>
              <ENT>Postage or delivery charge.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">(5) Other Services:</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cost of special services or materials, other than those provided for by this fee schedule, when requester is notified of such costs in advance and agrees to pay them</ENT>
              <ENT>Direct cost to DOI.</ENT>
            </ROW>
          </GPOTABLE>
        </REGTEXT>
        <REGTEXT PART="2" TITLE="43">
          <HD SOURCE="HD1">Appendix D to Part 2 [Removed]</HD>
          <AMDPAR>9. Appendix D to Part 2 is removed.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="2" TITLE="43">
          <HD SOURCE="HD1">Appendix E to Part 2 [Removed]</HD>
          <AMDPAR>10. Appendix E to Part 2 is removed.</AMDPAR>
        </REGTEXT>
        <REGTEXT PART="2" TITLE="43">
          <HD SOURCE="HD1">Appendix F to Part 2 [Redesignated as Appendix B to Part 2]</HD>
          <AMDPAR>11. Appendix F to Part 2 is redesignated as Appendix B to Part 2.</AMDPAR>
        </REGTEXT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31117 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4310-10-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Federal Emergency Management Agency</SUBAGY>
        <CFR>44 CFR Part 65</CFR>
        <DEPDOC>[Docket ID FEMA-2012-0003]</DEPDOC>
        <SUBJECT>Changes in Flood Elevation Determinations</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Emergency Management Agency, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Modified Base (1% annual-chance) Flood Elevations (BFEs) are finalized for the communities listed below. These modified BFEs will be used to calculate flood insurance premium rates for new buildings and their contents.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The effective dates for these modified BFEs are indicated on the following table and revise the Flood Insurance Rate Maps (FIRMs) in effect for the listed communities prior to this date.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The modified BFEs for each community are available for inspection at the office of the Chief Executive Officer of each community. The respective addresses are listed in the table below.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal Emergency Management Agency, 500 C Street SW., Washington, DC 20472, (202) 646-4064, or (email)<E T="03">Luis.Rodriguez3@fema.dhs.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The Federal Emergency Management Agency (FEMA) makes the final determinations listed below of the modified BFEs for each community listed. These modified BFEs have been published in newspapers of local circulation and ninety (90) days have elapsed since that publication. The Deputy Associate Administrator for Mitigation has resolved any appeals resulting from this notification.</P>
        <P>The modified BFEs are not listed for each community in this notice. However, this final rule includes the address of the Chief Executive Officer of the community where the modified BFE determinations are available for inspection.</P>

        <P>The modified BFEs are made pursuant to section 206 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4105, and are in accordance with the National Flood Insurance Act of 1968, 42 U.S.C. 4001<E T="03">et seq.,</E>and with 44 CFR part 65.</P>
        <P>For rating purposes, the currently effective community number is shown and must be used for all new policies and renewals.</P>
        <P>The modified BFEs are the basis for the floodplain management measures that the community is required either to adopt or to show evidence of being already in effect in order to qualify or to remain qualified for participation in the National Flood Insurance Program (NFIP).</P>
        <P>These modified BFEs, together with the floodplain management criteria required by 44 CFR 60.3, are the minimum that are required. They should not be construed to mean that the community must change any existing ordinances that are more stringent in their floodplain management requirements. The community may at any time enact stricter requirements of its own or pursuant to policies established by other Federal, State, or regional entities.</P>
        <P>These modified BFEs are used to meet the floodplain management requirements of the NFIP and also are used to calculate the appropriate flood insurance premium rates for new buildings built after these elevations are made final, and for the contents in those buildings. The changes in BFEs are in accordance with 44 CFR 65.4.</P>
        <P>
          <E T="03">National Environmental Policy Act.</E>This final rule is categorically excluded from the requirements of 44 CFR part 10, Environmental Consideration. An environmental impact assessment has not been prepared.</P>
        <P>
          <E T="03">Regulatory Flexibility Act.</E>As flood elevation determinations are not within the scope of the Regulatory Flexibility Act, 5 U.S.C. 601-612, a regulatory flexibility analysis is not required.</P>
        <P>
          <E T="03">Regulatory Classification.</E>This final rule is not a significant regulatory action under the criteria of section 3(f) of Executive Order 12866 of September 30, 1993, Regulatory Planning and Review, 58 FR 51735.</P>
        <P>
          <E T="03">Executive Order 13132, Federalism.</E>This final rule involves no policies that have federalism implications under Executive Order 13132, Federalism.</P>
        <P>
          <E T="03">Executive Order 12988, Civil Justice Reform.</E>This final rule meets the applicable standards of Executive Order 12988.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 44 CFR Part 65</HD>
          <P>Flood insurance, Floodplains, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        
        <P>Accordingly, 44 CFR part 65 is amended to read as follows:</P>
        <REGTEXT PART="65" TITLE="44">
          <PART>
            <HD SOURCE="HED">PART 65—[AMENDED]</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 65 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 4001<E T="03">et seq.;</E>Reorganization Plan No. 3 of 1978, 3 CFR, 1978 Comp., p. 329; E.O. 12127, 44 FR 19367, 3 CFR, 1979 Comp., p.376.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="65" TITLE="44">
          <SECTION>
            <SECTNO>§ 65.4</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>

          <AMDPAR>2. The tables published under the authority of § 65.4 are amended as follows:<PRTPAGE P="76916"/>
          </AMDPAR>
          <GPOTABLE CDEF="s50,r50,r75,r100,xs80,10" COLS="6" OPTS="L2,tp0,p7,7/8,i1">
            <TTITLE/>
            <BOXHD>
              <CHED H="1">State and county</CHED>
              <CHED H="1">Location and case No.</CHED>
              <CHED H="1">Date and name of newspaper where notice was published</CHED>
              <CHED H="1">Chief executive officer of community</CHED>
              <CHED H="1">Effective date of<LI>modification</LI>
              </CHED>
              <CHED H="1">Community No.</CHED>
            </BOXHD>
            <ROW>
              <ENT I="01">Texas: Tarrant (FEMA Docket No.: B-1225)</ENT>
              <ENT>City of Keller (11-06-2181P)</ENT>
              <ENT>June 24, 2011, July 1, 2011,<E T="03">The Fort Worth Star-Telegram</E>
              </ENT>
              <ENT>The Honorable Pat McGrail, Mayor, City of Keller, 1100 Bear Creek Parkway, Keller, TX 76248</ENT>
              <ENT>October 31, 2011</ENT>
              <ENT>480602</ENT>
            </ROW>
          </GPOTABLE>
        </REGTEXT>
        
        <EXTRACT>
          <FP>(Catalog of Federal Domestic Assistance No. 97.022, “Flood Insurance.”)</FP>
        </EXTRACT>
        
        <SIG>
          <NAME>James A. Walke,</NAME>
          <TITLE>Acting Deputy Associate Administrator for Mitigation, Department of Homeland Security,Federal Emergency Management Agency.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31348 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-12-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Federal Emergency Management Agency</SUBAGY>
        <CFR>44 CFR Part 67</CFR>
        <DEPDOC>[Docket ID FEMA-2012-0003]</DEPDOC>
        <SUBJECT>Final Flood Elevation Determinations</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Emergency Management Agency, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Base (1% annual-chance) Flood Elevations (BFEs) and modified BFEs are made final for the communities listed below. The BFEs and modified BFEs are the basis for the floodplain management measures that each community is required either to adopt or to show evidence of being already in effect in order to qualify or remain qualified for participation in the National Flood Insurance Program (NFIP).</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The date of issuance of the Flood Insurance Rate Map (FIRM) showing BFEs and modified BFEs for each community. This date may be obtained by contacting the office where the maps are available for inspection as indicated in the table below.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The final BFEs for each community are available for inspection at the office of the Chief Executive Officer of each community. The respective addresses are listed in the table below.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal Emergency Management Agency, 500 C Street SW., Washington, DC 20472, (202) 646-4064, or (email)<E T="03">Luis.Rodriguez3@fema.dhs.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The Federal Emergency Management Agency (FEMA) makes the final determinations listed below for the modified BFEs for each community listed. These modified elevations have been published in newspapers of local circulation and ninety (90) days have elapsed since that publication. The Deputy Associate Administrator for Mitigation has resolved any appeals resulting from this notification.</P>
        <P>This final rule is issued in accordance with section 110 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4104, and 44 CFR part 67. FEMA has developed criteria for floodplain management in floodprone areas in accordance with 44 CFR part 60.</P>
        <P>Interested lessees and owners of real property are encouraged to review the proof Flood Insurance Study and FIRM available at the address cited below for each community. The BFEs and modified BFEs are made final in the communities listed below. Elevations at selected locations in each community are shown.</P>
        <P>
          <E T="03">National Environmental Policy Act.</E>This final rule is categorically excluded from the requirements of 44 CFR part 10, Environmental Consideration. An environmental impact assessment has not been prepared.</P>
        <P>
          <E T="03">Regulatory Flexibility Act.</E>As flood elevation determinations are not within the scope of the Regulatory Flexibility Act, 5 U.S.C. 601-612, a regulatory flexibility analysis is not required.</P>
        <P>
          <E T="03">Regulatory Classification.</E>This final rule is not a significant regulatory action under the criteria of section 3(f) of Executive Order 12866 of September 30, 1993, Regulatory Planning and Review, 58 FR 51735.</P>
        <P>
          <E T="03">Executive Order 13132, Federalism.</E>This final rule involves no policies that have federalism implications under Executive Order 13132.</P>
        <P>
          <E T="03">Executive Order 12988, Civil Justice Reform.</E>This final rule meets the applicable standards of Executive Order 12988.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 44 CFR Part 67</HD>
          <P>Administrative practice and procedure, Flood insurance, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        
        <P>Accordingly, 44 CFR part 67 is amended as follows:</P>
        <REGTEXT PART="67" TITLE="44">
          <PART>
            <HD SOURCE="HED">PART 67—[AMENDED]</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 67 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 4001<E T="03">et seq.;</E>Reorganization Plan No. 3 of 1978, 3 CFR, 1978 Comp., p. 329; E.O. 12127, 44 FR 19367, 3 CFR, 1979 Comp., p. 376.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="67" TITLE="44">
          <SECTION>
            <SECTNO>§ 67.11</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. The tables published under the authority of § 67.11 are amended as follows:</AMDPAR>
          <GPOTABLE CDEF="s25,r50,15,r25" COLS="4" OPTS="L2,tp0,i1">
            <TTITLE/>
            <BOXHD>
              <CHED H="1">Flooding source(s)</CHED>
              <CHED H="1">Location of referenced elevation</CHED>
              <CHED H="1">* Elevation in feet (NGVD)<LI>+ Elevation in feet (NAVD)</LI>
                <LI># Depth in feet above ground</LI>
                <LI>⁁ Elevation in meters (MSL)</LI>
                <LI>modified</LI>
              </CHED>
              <CHED H="1">Communities affected</CHED>
            </BOXHD>
            <ROW EXPSTB="03">
              <ENT I="21">
                <E T="02">Cobb County, Georgia, and Incorporated Areas</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03" RUL="s">
              <ENT I="21">
                <E T="02">Docket No.: FEMA-B-1233</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Buttermilk Creek</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+892</ENT>
              <ENT>City of Austell, Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="76917"/>
              <ENT I="22"/>
              <ENT>Approximately 1.0 mile upstream of the Sweetwater Creek confluence</ENT>
              <ENT>+892</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Chattahoochee River</ENT>
              <ENT>Approximately 2.9 miles downstream of I-20</ENT>
              <ENT>+760</ENT>
              <ENT>City of Smyrna, Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.8 miles upstream of Morgan Falls Dam</ENT>
              <ENT>+861</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Concord Creek</ENT>
              <ENT>At the Nickajack Creek confluence</ENT>
              <ENT>+894</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 720 feet upstream of Auldyn Drive</ENT>
              <ENT>+999</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cooper Lake Creek</ENT>
              <ENT>Approximately 1,200 feet upstream of the Nickajack Creek confluence</ENT>
              <ENT>+825</ENT>
              <ENT>City of Smyrna, Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the upstream side of Gann Road Southeast</ENT>
              <ENT>+892</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Favor Creek</ENT>
              <ENT>At the Nickajack Creek confluence</ENT>
              <ENT>+913</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.55 miles upstream of the Nickajack Creek confluence</ENT>
              <ENT>+1001</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gilmore Creek</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+774</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.64 mile upstream of the Chattahoochee River confluence</ENT>
              <ENT>+774</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+905</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the Douglas County boundary</ENT>
              <ENT>+905</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Harmony Grove Creek</ENT>
              <ENT>At the Willeo Creek confluence</ENT>
              <ENT>+898</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the upstream side of Johnson Ferry Road</ENT>
              <ENT>+1052</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Laurel Creek</ENT>
              <ENT>At the Nickajack Creek confluence</ENT>
              <ENT>+802</ENT>
              <ENT>City of Smyrna, Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 500 feet upstream of Lee Street Southeast</ENT>
              <ENT>+984</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Liberty Hill Branch</ENT>
              <ENT>At the Queen Creek confluence</ENT>
              <ENT>+774</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.95 mile upstream of the Queen Creek confluence</ENT>
              <ENT>+911</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Noonday Creek</ENT>
              <ENT>At the Noonday Creek confluence</ENT>
              <ENT>+905</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.5 mile upstream of the Noonday Creek confluence</ENT>
              <ENT>+905</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Lost Mountain Creek</ENT>
              <ENT>At the Wildhorse Creek confluence</ENT>
              <ENT>+903</ENT>
              <ENT>City of Powder Springs, Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,250 feet upstream of Macedonia Road Southwest</ENT>
              <ENT>+943</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Milam Branch</ENT>
              <ENT>At the Queen Creek confluence</ENT>
              <ENT>+904</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 200 feet upstream of Francis Circle Southwest</ENT>
              <ENT>+1013</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Mill Creek No. 2</ENT>
              <ENT>At the Nickajack Creek confluence</ENT>
              <ENT>+902</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 150 feet upstream of Hicks Road Southwest</ENT>
              <ENT>+963</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Mud Creek</ENT>
              <ENT>At the Noses Creek confluence</ENT>
              <ENT>+908</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.4 mile upstream of the Noses Creek confluence</ENT>
              <ENT>+911</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Nickajack Creek</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+764</ENT>
              <ENT>City of Smyrna, Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 200 feet upstream of South Cobb Drive</ENT>
              <ENT>+1049</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Noonday Creek</ENT>
              <ENT>At the Cherokee County boundary</ENT>
              <ENT>+895</ENT>
              <ENT>City of Kennesaw, City of Marietta, Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 350 feet upstream of New Salem Road</ENT>
              <ENT>+1023</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Noonday Creek Tributary No. 4</ENT>
              <ENT>At the Noonday Creek confluence</ENT>
              <ENT>+927</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="76918"/>
              <ENT I="22"/>
              <ENT>Approximately 1,800 feet upstream of the Noonday Creek confluence</ENT>
              <ENT>+928</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Noses Creek</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+895</ENT>
              <ENT>City of Austell, City of Marietta, City of Powder Springs, Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 450 feet upstream of Kennesaw Avenue</ENT>
              <ENT>+1081</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Olley Creek</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+895</ENT>
              <ENT>City of Austell, Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the upstream side of Clay Road Southwest</ENT>
              <ENT>+895</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Powder Springs Creek</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+901</ENT>
              <ENT>City of Austell, City of Powder Springs, Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,750 feet upstream of Oglesby Road</ENT>
              <ENT>+901</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Powers Branch</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+795</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,060 feet upstream of the Chattahoochee River confluence</ENT>
              <ENT>+795</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Queen Creek</ENT>
              <ENT>At the Nickajack Creek confluence</ENT>
              <ENT>+764</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the upstream side of Mableton Parkway</ENT>
              <ENT>+999</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Rottenwood Creek</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+781</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,300 feet upstream of the Chattahoochee River confluence</ENT>
              <ENT>+781</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Smyrna Branch</ENT>
              <ENT>At the Theater Branch confluence</ENT>
              <ENT>+930</ENT>
              <ENT>City of Smyrna.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 200 feet upstream of Powder Springs Street Southeast</ENT>
              <ENT>+998</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweat Mountain Creek</ENT>
              <ENT>At the Willeo Creek confluence</ENT>
              <ENT>+941</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 950 feet upstream of Wesley Chapel Road</ENT>
              <ENT>+1000</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek</ENT>
              <ENT>Approximately 200 feet downstream of Old Alabama Road</ENT>
              <ENT>+891</ENT>
              <ENT>City of Austell, Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the Paulding County boundary</ENT>
              <ENT>+909</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Theater Branch</ENT>
              <ENT>At the Nickajack Creek confluence</ENT>
              <ENT>+923</ENT>
              <ENT>City of Smyrna, Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the downstream side of Parkway Drive Southeast</ENT>
              <ENT>+975</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Timber Ridge Branch</ENT>
              <ENT>At the Willeo Creek confluence</ENT>
              <ENT>+863</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.22 miles upstream of the Willeo Creek confluence</ENT>
              <ENT>+879</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ward Creek</ENT>
              <ENT>At the Noses Creek confluence</ENT>
              <ENT>+924</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.4 mile upstream of the Noses Creek confluence</ENT>
              <ENT>+925</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Wildhorse Creek</ENT>
              <ENT>At the Noses Creek confluence</ENT>
              <ENT>+903</ENT>
              <ENT>City of Powder Springs, Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 700 feet upstream of Arapaho Drive</ENT>
              <ENT>+953</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Willeo Creek</ENT>
              <ENT>Approximately 1,000 feet upstream of the Chattahoochee River confluence</ENT>
              <ENT>+863</ENT>
              <ENT>Unincorporated Areas of Cobb County.</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22"/>
              <ENT>Approximately 400 feet upstream of the Sweat Mountain Creek confluence</ENT>
              <ENT>+942</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">* National Geodetic Vertical Datum.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">+ North American Vertical Datum.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22"># Depth in feet above ground.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">⁁ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="21">
                <E T="02">ADDRESSES</E>
              </ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="22">
                <E T="02">City of Austell</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">Maps are available for inspection at City Hall, 2716 Broad Street Southwest, Austell, GA 30106.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="22">
                <E T="02">City of Kennesaw</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <PRTPAGE P="76919"/>
              <ENT I="22">Maps are available for inspection at City Hall, 2529 J.O. Stephenson Avenue, Kennesaw, GA 30144.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="22">
                <E T="02">City of Marietta</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">Maps are available for inspection at the Public Works Department, 205 Lawrence Street, Marietta, GA 30060.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="22">
                <E T="02">City of Powder Springs</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">Maps are available for inspection at City Hall, 4484 Marietta Street, Powder Springs, GA 30127.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="22">
                <E T="02">City of Smyrna</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">Maps are available for inspection at the Engineer's Office, 2800 King Street, Smyrna, GA 30080.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="21">
                <E T="02">Unincorporated Areas of Cobb County</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03" RUL="s">
              <ENT I="22">Maps are available for inspection at the Cobb County Development and Inspection Department, 205 Lawrence Street, Marietta, GA 30060.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="21">
                <E T="02">Douglas County, Georgia, and Incorporated Areas</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03" RUL="s">
              <ENT I="21">
                <E T="02">Docket No.: FEMA-B-1233</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Anneewakee Creek</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+749</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,900 feet upstream of the Anneewakee Creek Tributary B confluence</ENT>
              <ENT>+749</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Anneewakee Creek Tributary A</ENT>
              <ENT>At the Anneewakee Creek confluence</ENT>
              <ENT>+749</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 910 feet upstream of the Anneewakee Creek confluence</ENT>
              <ENT>+749</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Anneewakee Creek Tributary B</ENT>
              <ENT>At the Anneewakee Creek confluence</ENT>
              <ENT>+749</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 500 feet upstream of the Anneewakee Creek confluence</ENT>
              <ENT>+749</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Bear Creek</ENT>
              <ENT>At the upstream side of the Chattahoochee River confluence</ENT>
              <ENT>+740</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 2,000 feet upstream of State Route 166</ENT>
              <ENT>+740</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Beaver Creek</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+871</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 500 feet upstream of Patty Court</ENT>
              <ENT>+1006</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Beaver Creek Tributary A</ENT>
              <ENT>At the Beaver Creek confluence</ENT>
              <ENT>+914</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.52 mile upstream of the Beaver Creek confluence</ENT>
              <ENT>+953</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Camp Branch</ENT>
              <ENT>At the Hurricane Creek confluence</ENT>
              <ENT>+975</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,200 feet upstream of the Camp Branch Tributary A confluence</ENT>
              <ENT>+1062</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Camp Branch Tributary A</ENT>
              <ENT>At the Camp Branch confluence</ENT>
              <ENT>+1043</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 750 feet upstream of the Camp Branch confluence</ENT>
              <ENT>+1066</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Chattahoochee River</ENT>
              <ENT>At the Carroll County boundary</ENT>
              <ENT>+730</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the Cobb County boundary</ENT>
              <ENT>+760</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Dog River</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+736</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,200 feet upstream of the Chattahoochee River confluence</ENT>
              <ENT>+736</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Dry Creek</ENT>
              <ENT>At the Beaver Creek confluence</ENT>
              <ENT>+891</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,050 feet upstream of Lee Road</ENT>
              <ENT>+988</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Dry Creek Tributary A</ENT>
              <ENT>At the Dry Creek confluence</ENT>
              <ENT>+898</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.53 mile upstream of the Dry Creek confluence</ENT>
              <ENT>+925</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Dry Creek Tributary B</ENT>
              <ENT>At the Dry Creek confluence</ENT>
              <ENT>+928</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,170 feet upstream of the Dry Creek confluence</ENT>
              <ENT>+944</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Dry Creek Tributary C</ENT>
              <ENT>At the Dry Creek confluence</ENT>
              <ENT>+943</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,900 feet upstream of the Dry Creek confluence</ENT>
              <ENT>+969</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="76920"/>
              <ENT I="01">Gordon Creek</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+881</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the Cobb County boundary</ENT>
              <ENT>+898</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek</ENT>
              <ENT>At the Cobb County boundary</ENT>
              <ENT>+905</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.35 miles upstream of Cedar Mountain Road</ENT>
              <ENT>+1042</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 1</ENT>
              <ENT>At the Gothards Creek confluence</ENT>
              <ENT>+906</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,040 feet upstream of the Gothards Creek confluence</ENT>
              <ENT>+908</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 10</ENT>
              <ENT>At the Gothards Creek confluence</ENT>
              <ENT>+946</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.68 mile upstream of the Gothards Creek confluence</ENT>
              <ENT>+970</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 11</ENT>
              <ENT>Approximately 250 feet upstream of the Gothards Creek confluence</ENT>
              <ENT>+948</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.03 miles upstream of the Gothards Creek Tributary 11.3 confluence</ENT>
              <ENT>+1063</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 11.1</ENT>
              <ENT>At the Gothards Creek Tributary 11 confluence</ENT>
              <ENT>+972</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 200 feet upstream of Cedar Mountain Road</ENT>
              <ENT>+987</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 11.2</ENT>
              <ENT>At the Gothards Creek Tributary 11 confluence</ENT>
              <ENT>+985</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.05 miles upstream of the Gothards Creek Tributary 11 confluence</ENT>
              <ENT>+1100</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 11.3</ENT>
              <ENT>At the Gothards Creek Tributary 11 confluence</ENT>
              <ENT>+1006</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.49 mile upstream of the Gothards Creek Tributary 11 confluence</ENT>
              <ENT>+1042</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 12</ENT>
              <ENT>At the Gothards Creek confluence</ENT>
              <ENT>+961</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.60 mile upstream of the Gothards Creek confluence</ENT>
              <ENT>+1000</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 15</ENT>
              <ENT>At the Gothards Creek confluence</ENT>
              <ENT>+980</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 350 feet upstream of County Services Road</ENT>
              <ENT>+1013</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 2</ENT>
              <ENT>At the Gothards Creek confluence</ENT>
              <ENT>+909</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.78 mile upstream of the Gothards Creek confluence</ENT>
              <ENT>+995</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 2.1</ENT>
              <ENT>At the Gothards Creek confluence</ENT>
              <ENT>+907</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the Gothards Creek Tributary 2 divergence</ENT>
              <ENT>+966</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 3</ENT>
              <ENT>At the Gothards Creek confluence</ENT>
              <ENT>+910</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,100 feet upstream of Boyd Road</ENT>
              <ENT>+1095</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 3.1</ENT>
              <ENT>At the Gothards Creek Tributary 3</ENT>
              <ENT>+917</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 640 feet upstream of Greystone Lane</ENT>
              <ENT>+1057</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 3.2</ENT>
              <ENT>At the Gothards Creek Tributary 3 confluence</ENT>
              <ENT>+928</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the upstream side of Cody Lane</ENT>
              <ENT>+951</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 4</ENT>
              <ENT>At the Paulding County boundary</ENT>
              <ENT>+935</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,650 feet upstream of the Paulding County boundary</ENT>
              <ENT>+961</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 4.1</ENT>
              <ENT>At the Paulding County boundary</ENT>
              <ENT>+938</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.39 mile upstream of the Paulding County boundary</ENT>
              <ENT>+980</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 4.1.1</ENT>
              <ENT>At the Paulding County boundary</ENT>
              <ENT>+933</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="76921"/>
              <ENT I="22"/>
              <ENT>Approximately 650 feet upstream of Bearden Road</ENT>
              <ENT>+972</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 6</ENT>
              <ENT>At the Gothards Creek confluence</ENT>
              <ENT>+926</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 300 feet upstream of Maroney Mill Road</ENT>
              <ENT>+941</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 8</ENT>
              <ENT>At the Gothards Creek confluence</ENT>
              <ENT>+940</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.95 mile upstream of the Gothards Creek Tributary 8.1 confluence</ENT>
              <ENT>+1084</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 8.1</ENT>
              <ENT>At the Gothards Creek Tributary 8 confluence</ENT>
              <ENT>+977</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.67 mile upstream of the Gothards Creek Tributary 8 confluence</ENT>
              <ENT>+1030</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Gothards Creek Tributary 9</ENT>
              <ENT>At the Gothards Creek confluence</ENT>
              <ENT>+945</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.46 mile upstream of the Gothards Creek confluence</ENT>
              <ENT>+962</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hickory Creek</ENT>
              <ENT>At the Beaver Creek confluence</ENT>
              <ENT>+926</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.52 mile upstream of Burnt Hickory Road</ENT>
              <ENT>+1043</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hickory Creek Tributary A</ENT>
              <ENT>At the Hickory Creek confluence</ENT>
              <ENT>+958</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,650 feet upstream of U.S. Route 20</ENT>
              <ENT>+999</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hickory Creek Tributary B</ENT>
              <ENT>At the Hickory Creek confluence</ENT>
              <ENT>+959</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 650 feet upstream of September Way</ENT>
              <ENT>+1036</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hickory Creek Tributary C</ENT>
              <ENT>At the Hickory Creek confluence</ENT>
              <ENT>+983</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 350 feet upstream of Magnolia Trail</ENT>
              <ENT>+1036</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hickory Creek Tributary D</ENT>
              <ENT>At the Hickory Creek confluence</ENT>
              <ENT>+999</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,250 feet upstream of Lakeland Hills Drive</ENT>
              <ENT>+1046</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hickory Creek Tributary E</ENT>
              <ENT>At the Hickory Creek confluence</ENT>
              <ENT>+1007</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.47 mile upstream of the Hickory Creek confluence</ENT>
              <ENT>+1056</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Huey Creek</ENT>
              <ENT>At the Paulding County boundary</ENT>
              <ENT>+931</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,150 feet upstream of Brown Street</ENT>
              <ENT>+1083</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Huey Creek Tributary 1</ENT>
              <ENT>At the Huey Creek confluence</ENT>
              <ENT>+940</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.91 mile upstream of the Huey Creek Tributary 1.1 confluence</ENT>
              <ENT>+1095</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Huey Creek Tributary 1.1</ENT>
              <ENT>At the Huey Creek Tributary 1 confluence</ENT>
              <ENT>+1004</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,550 feet upstream of the Huey Creek Tributary 1 confluence</ENT>
              <ENT>+1067</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Huey Creek Tributary 2</ENT>
              <ENT>At the Huey Creek confluence</ENT>
              <ENT>+976</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 350 feet upstream of Huey Road</ENT>
              <ENT>+1017</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Huey Creek Tributary 3</ENT>
              <ENT>At the Huey Creek confluence</ENT>
              <ENT>+976</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 300 feet upstream of Pirkle Road</ENT>
              <ENT>+1038</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hurricane Creek</ENT>
              <ENT>At the Carroll County boundary</ENT>
              <ENT>+727</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.10 miles upstream of the Tyree Branch confluence</ENT>
              <ENT>+1201</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hurricane Creek Tributary A</ENT>
              <ENT>At the Hurricane Creek confluence</ENT>
              <ENT>+747</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="76922"/>
              <ENT I="22"/>
              <ENT>Approximately 0.66 mile upstream of the Hurricane Creek confluence</ENT>
              <ENT>+796</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hurricane Creek Tributary B</ENT>
              <ENT>At the Hurricane Creek confluence</ENT>
              <ENT>+784</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,450 feet upstream of the Hurricane Creek confluence</ENT>
              <ENT>+832</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hurricane Creek Tributary C</ENT>
              <ENT>At the Hurricane Creek confluence</ENT>
              <ENT>+940</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.38 mile upstream of the Hurricane Creek confluence</ENT>
              <ENT>+980</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hurricane Creek Tributary D</ENT>
              <ENT>At the Hurricane Creek confluence</ENT>
              <ENT>+958</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.53 mile upstream of the Hurricane Creek confluence</ENT>
              <ENT>+1012</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hurricane Creek Tributary E</ENT>
              <ENT>At the Hurricane Creek confluence</ENT>
              <ENT>+976</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,921 feet upstream of Tweeddale Drive</ENT>
              <ENT>+1022</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Kraft Creek</ENT>
              <ENT>At the Hurricane Creek confluence</ENT>
              <ENT>+1019</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 450 feet upstream of Kraft Drive</ENT>
              <ENT>+1045</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Kraft Creek Tributary A</ENT>
              <ENT>At the Kraft Creek confluence</ENT>
              <ENT>+1031</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 950 feet upstream of the Kraft Creek confluence</ENT>
              <ENT>+1057</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Lion Branch</ENT>
              <ENT>At the Beaver Creek confluence</ENT>
              <ENT>+900</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 200 feet upstream of East Melissa Lane</ENT>
              <ENT>+1060</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Lion Branch Tributary A</ENT>
              <ENT>At the Lion Branch confluence</ENT>
              <ENT>+932</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.50 mile upstream of Trail Creek Drive</ENT>
              <ENT>+992</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Lion Branch Tributary B</ENT>
              <ENT>At the Lion Branch confluence</ENT>
              <ENT>+962</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 250 feet upstream of Bottlebrush Drive</ENT>
              <ENT>+987</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Hurricane Creek</ENT>
              <ENT>At the Hurricane Creek confluence</ENT>
              <ENT>+866</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 450 feet upstream of Summer Hill Drive</ENT>
              <ENT>+1066</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Hurricane Creek Tributary A</ENT>
              <ENT>At the Little Hurricane Creek confluence</ENT>
              <ENT>+927</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.73 mile upstream of Gable Drive</ENT>
              <ENT>+990</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Margie Branch</ENT>
              <ENT>At the Beaver Creek confluence</ENT>
              <ENT>+942</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.45 mile upstream of the Margie Branch Tributary A confluence</ENT>
              <ENT>+1074</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Margie Branch Tributary A</ENT>
              <ENT>At the Margie Branch confluence</ENT>
              <ENT>+1028</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,800 feet upstream of the Margie Branch confluence</ENT>
              <ENT>+1079</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Mill Creek</ENT>
              <ENT>At the Gothards Creek confluence</ENT>
              <ENT>+931</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 200 feet upstream of Crystal Creek Place</ENT>
              <ENT>+1091</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Mill Creek Tributary 1</ENT>
              <ENT>At the Mill Creek confluence</ENT>
              <ENT>+972</ENT>
              <ENT>City of Douglasville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.85 mile upstream of the Mill Creek confluence</ENT>
              <ENT>+1061</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Miller Creek</ENT>
              <ENT>At the Beaver Creek confluence</ENT>
              <ENT>+927</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 600 feet upstream of Miller Street</ENT>
              <ENT>+969</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Miller Creek Tributary A</ENT>
              <ENT>At the Miller Creek confluence</ENT>
              <ENT>+927</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,450 feet upstream of the Miller Creek confluence</ENT>
              <ENT>+983</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Palmer Branch</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+757</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.56 mile upstream of the Palmer Branch Tributary C confluence</ENT>
              <ENT>+900</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="76923"/>
              <ENT I="01">Palmer Branch Tributary A</ENT>
              <ENT>At the Palmer Branch confluence</ENT>
              <ENT>+789</ENT>
              <ENT>City of Douglasville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.55 mile upstream of the Palmer Branch confluence</ENT>
              <ENT>+935</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Palmer Branch Tributary B</ENT>
              <ENT>At the Palmer Branch confluence</ENT>
              <ENT>+807</ENT>
              <ENT>City of Douglasville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.53 mile upstream of the Palmer Branch confluence</ENT>
              <ENT>+882</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Palmer Branch Tributary C</ENT>
              <ENT>At the Palmer Branch confluence</ENT>
              <ENT>+855</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,850 feet upstream of Washington Drive</ENT>
              <ENT>+1005</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Park Creek</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+885</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 800 feet upstream of Sinyard Road</ENT>
              <ENT>+968</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Pine Creek</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+889</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the Cobb County boundary</ENT>
              <ENT>+890</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Pinewood Branch</ENT>
              <ENT>At the Park Creek confluence</ENT>
              <ENT>+885</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 600 feet upstream of Paces Drive</ENT>
              <ENT>+949</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Pinewood Branch Tributary A</ENT>
              <ENT>At the Pinewood Branch confluence</ENT>
              <ENT>+900</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,100 feet upstream of Plantation Drive</ENT>
              <ENT>+987</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Shell Creek</ENT>
              <ENT>At the Hurricane Creek confluence</ENT>
              <ENT>+994</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.78 mile upstream of Shell Road</ENT>
              <ENT>+1099</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Shoals Branch</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+768</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.27 miles upstream of the Shoals Branch Tributary B confluence</ENT>
              <ENT>+975</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Shoals Branch Tributary A</ENT>
              <ENT>At the Shoals Branch confluence</ENT>
              <ENT>+827</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.44 mile upstream of the Shoals Branch confluence</ENT>
              <ENT>+923</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Shoals Branch Tributary B</ENT>
              <ENT>At the Shoals Branch confluence</ENT>
              <ENT>+842</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,100 feet upstream of the Shoals Branch confluence</ENT>
              <ENT>+877</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Spivey Branch</ENT>
              <ENT>At the Hickory Creek confluence</ENT>
              <ENT>+944</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.82 mile upstream of the Spivey Branch Tributary B confluence</ENT>
              <ENT>+1086</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Spivey Branch Tributary A</ENT>
              <ENT>At the Spivey Branch confluence</ENT>
              <ENT>+965</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 550 feet upstream of Ivy Brooke Drive</ENT>
              <ENT>+1040</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Spivey Branch Tributary B</ENT>
              <ENT>At the Spivey Branch confluence</ENT>
              <ENT>+978</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.38 mile upstream of the Spivey Branch confluence</ENT>
              <ENT>+1007</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek</ENT>
              <ENT>Approximately 85 feet downstream of the Palmer Branch confluence</ENT>
              <ENT>+757</ENT>
              <ENT>City of Austell, City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 450 feet upstream of the Cobb County boundary</ENT>
              <ENT>+892</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek Tributary A</ENT>
              <ENT>Approximately 1,450 feet upstream of the Sweetwater Creek confluence</ENT>
              <ENT>+758</ENT>
              <ENT>City of Douglasville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,000 feet upstream of Riverside Parkway</ENT>
              <ENT>+799</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek Tributary B</ENT>
              <ENT>Approximately 1,400 feet upstream of the Sweetwater Creek confluence</ENT>
              <ENT>+757</ENT>
              <ENT>City of Douglasville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.47 mile upstream of the Sweetwater Creek confluence</ENT>
              <ENT>+788</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek Tributary C</ENT>
              <ENT>Approximately 1,800 feet upstream of the Sweetwater Creek confluence</ENT>
              <ENT>+758</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="76924"/>
              <ENT I="22"/>
              <ENT>Approximately 0.77 mile upstream of the Sweetwater Creek confluence</ENT>
              <ENT>+797</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek Tributary D</ENT>
              <ENT>Approximately 0.48 mile upstream of the Sweetwater Creek confluence</ENT>
              <ENT>+758</ENT>
              <ENT>City of Douglasville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.52 miles upstream of the Sweetwater Creek confluence</ENT>
              <ENT>+856</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek Tributary E</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+778</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.88 mile upstream of the Sweetwater Creek confluence</ENT>
              <ENT>+900</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek Tributary F</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+876</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 750 feet upstream of Factory Shoals Road</ENT>
              <ENT>+964</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek Tributary G</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+878</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 800 feet upstream of Trae Lane</ENT>
              <ENT>+1002</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek Tributary H</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+879</ENT>
              <ENT>City of Douglasville, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the Cobb County boundary</ENT>
              <ENT>+911</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek Tributary I</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+882</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 250 feet upstream of White Flag Trail</ENT>
              <ENT>+918</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek Tributary J</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+887</ENT>
              <ENT>City of Austell, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,200 feet upstream of State Route 6 (Thornton Road)</ENT>
              <ENT>+946</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek Tributary K</ENT>
              <ENT>At the Sweetwater Creek confluence</ENT>
              <ENT>+887</ENT>
              <ENT>City of Austell, Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.51 mile upstream of U.S. Route 78 (Bankhead Highway)</ENT>
              <ENT>+921</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek Tributary L</ENT>
              <ENT>At the Cobb County boundary</ENT>
              <ENT>+906</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,250 feet upstream of Brownsville Road</ENT>
              <ENT>+1057</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek Tributary L.2</ENT>
              <ENT>At the Sweetwater Creek Tributary L confluence</ENT>
              <ENT>+907</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 750 feet upstream of North Sweetwater Road</ENT>
              <ENT>+966</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek Tributary L.3</ENT>
              <ENT>At the Sweetwater Creek Tributary L confluence</ENT>
              <ENT>+934</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,500 feet upstream of Union Grove Road</ENT>
              <ENT>+990</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sweetwater Creek Tributary L.3.1</ENT>
              <ENT>At the Sweetwater Creek Tributary L.3 confluence</ENT>
              <ENT>+955</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,600 feet upstream of the Sweetwater Creek Tributary L.3 confluence</ENT>
              <ENT>+999</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Tyree Branch</ENT>
              <ENT>At the Hurricane Creek confluence</ENT>
              <ENT>+1044</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.10 miles upstream of the Hurricane Creek confluence</ENT>
              <ENT>+1171</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Zion Branch</ENT>
              <ENT>At the Hurricane Creek confluence</ENT>
              <ENT>+736</ENT>
              <ENT>Unincorporated Areas of Douglas County.</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22"/>
              <ENT>Approximately 0.53 mile upstream of State Route 5</ENT>
              <ENT>+988</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">* National Geodetic Vertical Datum.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">+ North American Vertical Datum.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22"># Depth in feet above ground.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">⁁ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="21">
                <E T="02">ADDRESSES</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">
                <E T="02">City of Austell</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">Maps are available for inspection at the City of Austell-Threadmill Complex, 5000 Austell-Powder Springs Road, Austell, GA 30106.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="22">
                <E T="02">City of Douglasville</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">Maps are available for inspection at City Hall, 6695 Church Street, Douglasville, GA 30134.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <PRTPAGE P="76925"/>
              <ENT I="21">
                <E T="02">Unincorporated Areas of Douglas County</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03" RUL="s">
              <ENT I="22">Maps are available for inspection at the Douglas County Courthouse, 8700 Hospital Drive, Douglasville, GA 30134.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="21">
                <E T="02">Forsyth County, Georgia, and Incorporated Areas</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03" RUL="s">
              <ENT I="21">
                <E T="02">Docket No.: FEMA-B-1233</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Baldridge Creek</ENT>
              <ENT>At Pilgrim Mill Road</ENT>
              <ENT>+1088</ENT>
              <ENT>Unincorporated Areas of Forsyth County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.75 mile upstream of U.S. Route 19 (State Route 400)</ENT>
              <ENT>+1299</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Bentley Creek</ENT>
              <ENT>Approximately 1,460 feet upstream of the Big Creek confluence</ENT>
              <ENT>+1025</ENT>
              <ENT>Unincorporated Areas of Forsyth County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,800 feet upstream of Bentley Road</ENT>
              <ENT>+1047</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Big Creek</ENT>
              <ENT>At the Fulton County boundary</ENT>
              <ENT>+1000</ENT>
              <ENT>City of Cumming, Unincorporated Areas of Forsyth County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,490 feet upstream of Canton Road (State Route 20)</ENT>
              <ENT>+1142</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Camp Creek Tributary</ENT>
              <ENT>At the Fulton County boundary</ENT>
              <ENT>+1012</ENT>
              <ENT>Unincorporated Areas of Forsyth County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 350 feet upstream of James Road</ENT>
              <ENT>+1062</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Chattahoochee River</ENT>
              <ENT>At the Fulton County boundary</ENT>
              <ENT>+904</ENT>
              <ENT>Unincorporated Areas of Forsyth County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the Buford Dam</ENT>
              <ENT>+920</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Cheatam Creek</ENT>
              <ENT>At the Big Creek confluence</ENT>
              <ENT>+1029</ENT>
              <ENT>Unincorporated Areas of Forsyth County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,250 feet upstream of Kelly Mill Road</ENT>
              <ENT>+1056</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Daves Creek</ENT>
              <ENT>At the James Creek confluence</ENT>
              <ENT>+946</ENT>
              <ENT>Unincorporated Areas of Forsyth County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,070 feet upstream of Northside Forsyth Drive</ENT>
              <ENT>+1203</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Dick Creek</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+906</ENT>
              <ENT>Unincorporated Areas of Forsyth County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At Mathis Airport Parkway</ENT>
              <ENT>+1042</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Haw Creek</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+919</ENT>
              <ENT>Unincorporated Areas of Forsyth County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 400 feet upstream of Habersham Gate Drive</ENT>
              <ENT>+1179</ENT>
            </ROW>
            <ROW>
              <ENT I="01">James Creek</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+912</ENT>
              <ENT>Unincorporated Areas of Forsyth County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 700 feet upstream of Oak Industrial Lane</ENT>
              <ENT>+1204</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Johns Creek</ENT>
              <ENT>At the upstream side of McGinnis Ferry Road</ENT>
              <ENT>+1023</ENT>
              <ENT>Unincorporated Areas of Forsyth County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the Fulton County boundary</ENT>
              <ENT>+1041</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sawnee Creek</ENT>
              <ENT>At the downstream side of the Sawnee Creek Tributary 2 confluence</ENT>
              <ENT>+1085</ENT>
              <ENT>Unincorporated Areas of Forsyth County.</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22"/>
              <ENT>Approximately 1,050 feet upstream of Jackson Court</ENT>
              <ENT>+1261</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">* National Geodetic Vertical Datum.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">+ North American Vertical Datum.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22"># Depth in feet above ground.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">⁁ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="21">
                <E T="02">ADDRESSES</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">
                <E T="02">City of Cumming</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">Maps are available for inspection at City Hall, 100 Main Street, Cumming, GA 30040.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="21">
                <E T="02">Unincorporated Areas of Forsyth County:</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03" RUL="s">
              <ENT I="22">Maps are available for inspection at the Forsyth County Administration Building, Department of Engineering, 110 East Main Street, Suite 120, Cumming, GA 30040.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="21">
                <E T="02">Gwinnett County, Georgia, and Incorporated Areas</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03" RUL="s">
              <ENT I="21">
                <E T="02">Docket No.: FEMA-B-1233</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Brushy Creek</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+904</ENT>
              <ENT>City of Suwanee, Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 100 feet upstream of Suwanee Dam Road</ENT>
              <ENT>+1010</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="76926"/>
              <ENT I="01">Chattahoochee River</ENT>
              <ENT>Approximately 800 feet upstream of Holcomb Bridge Road (at the Fulton County boundary)</ENT>
              <ENT>+884</ENT>
              <ENT>City of Berkeley Lake, City of Duluth, City of Sugar Hill, City of Suwanee, Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.6 mile upstream of the Chattahoochee River (Bowmans East) divergence</ENT>
              <ENT>+920</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Chattahoochee River (Bowmans East)</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+915</ENT>
              <ENT>City of Sugar Hill, Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.71 mile upstream of the Chattahoochee River confluence</ENT>
              <ENT>+917</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Duncan Creek</ENT>
              <ENT>Approximately 1.14 miles downstream of Crimson King Drive</ENT>
              <ENT>+817</ENT>
              <ENT>Town of Braselton, Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.43 mile upstream of East Rock Quarry Road</ENT>
              <ENT>+1082</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Level Creek</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+907</ENT>
              <ENT>City of Sugar Hill, City of Suwanee, Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 250 feet upstream of Peachtree Industrial Boulevard</ENT>
              <ENT>+1045</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Level Creek Tributary No. 1</ENT>
              <ENT>At the Level Creek confluence</ENT>
              <ENT>+951</ENT>
              <ENT>City of Suwanee, Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the downstream side of Suwanee Dam Road</ENT>
              <ENT>+995</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Level Creek Tributary No. 2</ENT>
              <ENT>At the upstream side of Whitehead Road</ENT>
              <ENT>+976</ENT>
              <ENT>City of Sugar Hill, Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 160 feet upstream of Sugar Ridge Drive</ENT>
              <ENT>+1021</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Mulberry River</ENT>
              <ENT>Approximately 0.47 mile downstream of Mount Moriah Road</ENT>
              <ENT>+836</ENT>
              <ENT>Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 550 feet upstream of Millwater Crossing</ENT>
              <ENT>+995</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Mulberry River Tributary A</ENT>
              <ENT>At the Little Mulberry River confluence</ENT>
              <ENT>+846</ENT>
              <ENT>Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 175 feet upstream of Mineral Springs Road</ENT>
              <ENT>+986</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Mulberry River Tributary B</ENT>
              <ENT>At the Little Mulberry River confluence</ENT>
              <ENT>+849</ENT>
              <ENT>Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 125 feet upstream of Hog Mountain Road</ENT>
              <ENT>+929</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Mulberry River Tributary C</ENT>
              <ENT>At the Little Mulberry River confluence</ENT>
              <ENT>+858</ENT>
              <ENT>Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 125 feet upstream of the private driveway</ENT>
              <ENT>+889</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Mulberry River Tributary D</ENT>
              <ENT>At the upstream side of Hog Mountain Road</ENT>
              <ENT>+896</ENT>
              <ENT>Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 270 feet upstream of Hog Mountain Road</ENT>
              <ENT>+896</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Little Mulberry River Tributary E</ENT>
              <ENT>Approximately 100 feet upstream of Hog Mountain Road</ENT>
              <ENT>+908</ENT>
              <ENT>Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 100 feet downstream of Patrick Road</ENT>
              <ENT>+908</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Mill Creek (Stream 6)</ENT>
              <ENT>Approximately 950 feet upstream of the Mill Creek Tributary (Stream 6.1) confluence</ENT>
              <ENT>+896</ENT>
              <ENT>City of Berkeley Lake, Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the upstream side of Bush Road</ENT>
              <ENT>+926</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Mill Creek Tributary (Stream 6.1)</ENT>
              <ENT>At the Mill Creek (Stream 6) confluence</ENT>
              <ENT>+895</ENT>
              <ENT>City of Berkeley Lake, Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 270 feet upstream of Bayway Circle</ENT>
              <ENT>+976</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Mitchell Creek</ENT>
              <ENT>Approximately 1.34 miles downstream of Thompson Mill Road</ENT>
              <ENT>+1015</ENT>
              <ENT>Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 850 feet upstream of South Puckett Lane</ENT>
              <ENT>+1136</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Richland Creek</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+914</ENT>
              <ENT>City of Buford, City of Sugar Hill, Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 80 feet upstream of Cole Road Northeast</ENT>
              <ENT>+1096</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Richland Creek Tributary No. 1</ENT>
              <ENT>At the Richland Creek confluence</ENT>
              <ENT>+951</ENT>
              <ENT>City of Sugar Hill, Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="76927"/>
              <ENT I="22"/>
              <ENT>Approximately 100 feet upstream of Stewart Road Northeast</ENT>
              <ENT>+1010</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Richland Creek Tributary No. 2</ENT>
              <ENT>At the Richland Creek confluence</ENT>
              <ENT>+1010</ENT>
              <ENT>City of Buford, Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 450 feet upstream of Pine Hollow Way</ENT>
              <ENT>+1055</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Rock Creek</ENT>
              <ENT>Approximately 950 feet downstream of Bailey Road</ENT>
              <ENT>+961</ENT>
              <ENT>Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.68 miles upstream of Bailey Road</ENT>
              <ENT>+999</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Rogers Creek</ENT>
              <ENT>Approximately 1,160 feet upstream of the Chattahoochee River confluence</ENT>
              <ENT>+899</ENT>
              <ENT>City of Duluth, Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.83 mile upstream of Bridlewood Drive</ENT>
              <ENT>+1039</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Sherwood Creek</ENT>
              <ENT>Approximately 0.66 mile downstream of Old Thompson Mill Road</ENT>
              <ENT>+922</ENT>
              <ENT>Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,950 feet upstream of Rock Quarry Road</ENT>
              <ENT>+964</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Stream 1</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+887</ENT>
              <ENT>Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 450 feet upstream of Allenhurst Drive</ENT>
              <ENT>+932</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Stream 10</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+902</ENT>
              <ENT>City of Duluth, Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.47 mile upstream of Buford Highway</ENT>
              <ENT>+1031</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Stream 2</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+888</ENT>
              <ENT>Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,650 feet upstream of the pedestrian bridge</ENT>
              <ENT>+947</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Stream 3</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+890</ENT>
              <ENT>Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.55 mile upstream of Edgerton Drive</ENT>
              <ENT>+948</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Stream 4</ENT>
              <ENT>Approximately 950 feet upstream of the Chattahoochee River confluence</ENT>
              <ENT>+891</ENT>
              <ENT>Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 100 feet upstream of the Detention Pond</ENT>
              <ENT>+950</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Stream 5</ENT>
              <ENT>Approximately 1,150 feet upstream of the Chattahoochee River confluence</ENT>
              <ENT>+895</ENT>
              <ENT>Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 275 feet upstream of Bush Road</ENT>
              <ENT>+920</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Stream 8</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+898</ENT>
              <ENT>City of Duluth.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the upstream side of Howell Springs Drive</ENT>
              <ENT>+972</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Suwanee Creek</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+903</ENT>
              <ENT>Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.91 mile upstream of the Chattahoochee River confluence</ENT>
              <ENT>+909</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Swilling Creek</ENT>
              <ENT>At the Chattahoochee River confluence</ENT>
              <ENT>+897</ENT>
              <ENT>City of Duluth.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,680 feet upstream of Tree Summit Parkway</ENT>
              <ENT>+977</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Swilling Creek Tributary</ENT>
              <ENT>At the Swilling Creek confluence</ENT>
              <ENT>+928</ENT>
              <ENT>City of Duluth.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 100 feet downstream of Whippoorwill Drive</ENT>
              <ENT>+966</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Wheeler Creek</ENT>
              <ENT>Approximately 1.2 miles downstream of Wheeler Road</ENT>
              <ENT>+838</ENT>
              <ENT>Unincorporated Areas of Gwinnett County.</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22"/>
              <ENT>Approximately 435 feet upstream of Flowery Branch Road</ENT>
              <ENT>+931</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">* National Geodetic Vertical Datum.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">+ North American Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"># Depth in feet above ground.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">⁁ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="21">
                <E T="02">ADDRESSES</E>
              </ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">City of Berkeley Lake</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at City Hall, 4040 Berkeley Lake Road, Berkeley Lake, GA 30096.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">City of Buford</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at City Hall, 95 Scott Street, Buford, GA 30518.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">City of Duluth</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the Department of Planning and Development, 3578 West Lawrenceville Street, Duluth, GA 30096.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">City of Sugar Hill</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at City Hall, Planning and Zoning Department, 4988 West Broad Street, Sugar Hill, GA 30518.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="22">
                <E T="02">City of Suwanee</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the Crossroads Center, 323 Buford Highway, Suwanee, GA 30024.</ENT>
            </ROW>
            
            <ROW>
              <PRTPAGE P="76928"/>
              <ENT I="22">
                <E T="02">Town of Braselton</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at the Town Hall, 4982 State Route 53, Braselton, GA 30517.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="21">
                <E T="02">Unincorporated Areas of Gwinnett County</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22">Maps are available for inspection at the Gwinnett County Office, 75 Langley Drive, Lawrenceville, GA 30045.</ENT>
            </ROW>
            <ROW>
              <ENT I="21">
                <E T="02">Mille Lacs County, Minnesota, and Incorporated Areas</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="21">
                <E T="02">Docket No.: FEMA-B-1161</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Mille Lacs Lake</ENT>
              <ENT>Entire shoreline within community</ENT>
              <ENT>+1254</ENT>
              <ENT>City of Wahkon, Unincorporated Areas of Mille Lacs County.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Rum River (Lower Reach)</ENT>
              <ENT>Approximately 2.25 miles downstream of State Highway 95</ENT>
              <ENT>+962</ENT>
              <ENT>Unincorporated Areas of Mille Lacs County.</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22"/>
              <ENT>Approximately 0.82 mile upstream of State Highway 95</ENT>
              <ENT>+967</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">* National Geodetic Vertical Datum.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">+ North American Vertical Datum.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"># Depth in feet above ground.</ENT>
            </ROW>
            <ROW>
              <ENT I="22">⁁ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="21">
                <E T="02">ADDRESSES</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">
                <E T="02">City of Wahkon</E>
              </ENT>
            </ROW>
            <ROW>
              <ENT I="22">Maps are available for inspection at City Hall, 151 2nd Street East, Wahkon, MN 56386.</ENT>
            </ROW>
            
            <ROW>
              <ENT I="21">
                <E T="02">Unincorporated Areas of Mille Lacs County</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22">Maps are available for inspection at the Mille Lacs County Courthouse Annex, 246 6th Avenue Southeast, Milaca, MN 56353.</ENT>
            </ROW>
            <ROW>
              <ENT I="21">
                <E T="02">Putnam County, New York (All Jurisdictions)</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="21">
                <E T="02">Docket No.: FEMA-B-1137</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Barrett Pond</ENT>
              <ENT>At the confluence with Clove Creek</ENT>
              <ENT>+361</ENT>
              <ENT>Town of Philipstown.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 2,741 feet upstream of Fishkill Road</ENT>
              <ENT>+378</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Clove Creek</ENT>
              <ENT>Approximately 50 feet downstream of U.S. Route 9</ENT>
              <ENT>+259</ENT>
              <ENT>Town of Philipstown.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1.6 miles upstream of Briars Road</ENT>
              <ENT>+517</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Croton Falls Diverting Reservoir</ENT>
              <ENT>Entire shoreline within the Town of Southeast</ENT>
              <ENT>+310</ENT>
              <ENT>Town of Southeast</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Croton Falls Reservoir</ENT>
              <ENT>Entire shoreline</ENT>
              <ENT>+311</ENT>
              <ENT>Town of Carmel, Town of Southeast.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">East Branch Croton River Reach 1</ENT>
              <ENT>At the confluence with the Croton Falls Diverting Reservoir</ENT>
              <ENT>+310</ENT>
              <ENT>Town of Southeast, Village of Brewster.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 777 feet upstream of State Route 22</ENT>
              <ENT>+359</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Foundry Brook</ENT>
              <ENT>Approximately 1,320 feet downstream of State Route 9D</ENT>
              <ENT>+8</ENT>
              <ENT>Town of Philipstown, Village of Cold Spring, Village of Nelsonville.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 852 feet upstream of Fishkill Road</ENT>
              <ENT>+369</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Holly Stream</ENT>
              <ENT>Approximately 1,099 feet downstream of State Route 22</ENT>
              <ENT>+273</ENT>
              <ENT>Town of Southeast.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 854 feet upstream of I-684</ENT>
              <ENT>+312</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Lake Mahopac</ENT>
              <ENT>Entire shoreline within the Town of Carmel</ENT>
              <ENT>+660</ENT>
              <ENT>Town of Carmel.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Lost Lake</ENT>
              <ENT>Entire shoreline</ENT>
              <ENT>+466</ENT>
              <ENT>Town of Patterson.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Michael Brook</ENT>
              <ENT>At the confluence with the Croton Falls Reservoir</ENT>
              <ENT>+311</ENT>
              <ENT>Town of Carmel, Town of Kent.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.9 mile upstream of Fair Street</ENT>
              <ENT>+593</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Middle Branch Croton River</ENT>
              <ENT>At confluence with the Middle Branch Reservoir</ENT>
              <ENT>+371</ENT>
              <ENT>Town of Carmel, Town of Kent, Town of Southeast.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 101 feet upstream of Lakeshore Drive</ENT>
              <ENT>+620</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Middle Branch Reservoir</ENT>
              <ENT>Entire shoreline within the Town of Southeast</ENT>
              <ENT>+371</ENT>
              <ENT>Town of Southeast.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Muscoot River</ENT>
              <ENT>At the county boundary</ENT>
              <ENT>+509</ENT>
              <ENT>Town of Carmel.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,009 feet upstream of Stillwater Road</ENT>
              <ENT>+511</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Oscawana Brook</ENT>
              <ENT>At the county boundary</ENT>
              <ENT>+115</ENT>
              <ENT>Town of Putnam Valley.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,550 feet upstream of Oscawana Lake Road</ENT>
              <ENT>+516</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Putnam Lake</ENT>
              <ENT>Entire shoreline</ENT>
              <ENT>+494</ENT>
              <ENT>Town of Patterson.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Secor Brook</ENT>
              <ENT>At the confluence with the Muscoot River</ENT>
              <ENT>+511</ENT>
              <ENT>Town of Carmel.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,396 feet upstream of Secor Road</ENT>
              <ENT>+566</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Shrub Oak Brook</ENT>
              <ENT>Approximately 500 feet upstream of the confluence with Peekskill Hollow Creek</ENT>
              <ENT>+219</ENT>
              <ENT>Town of Putnam Valley.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>At the county boundary</ENT>
              <ENT>+393</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Stephens Brook</ENT>
              <ENT>Approximately 250 feet upstream of the confluence with East Branch Croton River Reach 2</ENT>
              <ENT>+433</ENT>
              <ENT>Town of Patterson.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 31 feet upstream of Thunder Ridge Road</ENT>
              <ENT>+473</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="76929"/>
              <ENT I="01">Tonetta Brook</ENT>
              <ENT>At the confluence with East Branch Croton River Reach 1</ENT>
              <ENT>+313</ENT>
              <ENT>Town of Southeast, Village of Brewster.</ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="22"/>
              <ENT>Approximately 351 feet upstream of Pumphouse Road</ENT>
              <ENT>+444</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">* National Geodetic Vertical Datum.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">+ North American Vertical Datum.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22"># Depth in feet above ground.</ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">⁁ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="21">
                <E T="02">ADDRESSES</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">
                <E T="02">Town of Carmel</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">Maps are available for inspection at the Carmel Town Hall, 60 McAlpin Avenue, Mahopac, NY 10541.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="22">
                <E T="02">Town of Kent</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">Maps are available for inspection at the Town of Kent Administration Office, 25 Sybils Crossing, Kent Lakes, NY 10512.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="22">
                <E T="02">Town of Patterson</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">Maps are available for inspection at the Town Hall, 1142 Route 311, Patterson, NY 12563.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="22">
                <E T="02">Town of Philipstown</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">Maps are available for inspection at the Philipstown Town Hall, 238 Main Street, Cold Spring, NY 10516.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="22">
                <E T="02">Town of Putnam Valley</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">Maps are available for inspection at the Town Hall, 265 Oscawana Lake Road, Putnam Valley, NY 10579.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="22">
                <E T="02">Town of Southeast</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">Maps are available for inspection at the Southeast Town Building Department, 1 Main Street, Brewster, NY 10509.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="22">
                <E T="02">Village of Brewster</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">Maps are available for inspection at the Village Hall, Larry T. Jewell Municipal Building, 50 Main Street, Brewster, NY 10509.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="22">
                <E T="02">Village of Cold Spring</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">Maps are available for inspection at the Village Hall, 85 Main Street, Cold Spring, NY 10516.</ENT>
            </ROW>
            
            <ROW EXPSTB="03">
              <ENT I="22">
                <E T="02">Village of Nelsonville</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="03">
              <ENT I="22">Maps are available for inspection at the Village Hall, 258 Main Street, Nelsonville, NY 10516.</ENT>
            </ROW>
          </GPOTABLE>
        </REGTEXT>
        <EXTRACT>
          <FP>(Catalog of Federal Domestic Assistance No. 97.022, “Flood Insurance.”)</FP>
        </EXTRACT>
        <SIG>
          <NAME>James A. Walke,</NAME>
          <TITLE>Acting Deputy Associate Administrator for Mitigation, Department of Homeland Security, Federal Emergency Management Agency.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31349 Filed 12-28-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-12-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Federal Emergency Management Agency</SUBAGY>
        <CFR>44 CFR Part 67</CFR>
        <DEPDOC>[Docket ID FEMA-2012-0003]</DEPDOC>
        <SUBJECT>Final Flood Elevation Determinations</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Emergency Management Agency, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Base (1% annual-chance) Flood Elevations (BFEs) and modified BFEs are made final for the communities listed below. The BFEs and modified BFEs are the basis for the floodplain management measures that each community is required either to adopt or to show evidence of being already in effect in order to qualify or remain qualified for participation in the National Flood Insurance Program (NFIP).</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The date of issuance of the Flood Insurance Rate Map (FIRM) showing BFEs and modified BFEs for each community. This date may be obtained by contacting the office where the maps are available for inspection as indicated in the table below.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The final BFEs for each community are available for inspection at the office of the Chief Executive Officer of each community. The respective addresses are listed in the table below.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal Emergency Management Agency, 500 C Street SW., Washington, DC 20472, (202) 646-4064, or (email)<E T="03">Luis.Rodriguez3@fema.dhs.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The Federal Emergency Management Agency (FEMA) makes the final determinations listed below for the modified BFEs for each community listed. These modified elevations have been published in newspapers of local circulation and ninety (90) days have elapsed since that publication. The Deputy Associate Administrator for Mitigation has resolved any appeals resulting from this notification.</P>
        <P>This final rule is issued in accordance with section 110 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4104, and 44 CFR part 67. FEMA has developed criteria for floodplain management in floodprone areas in accordance with 44 CFR part 60.</P>
        <P>Interested lessees and owners of real property are encouraged to review the proof Flood Insurance Study and FIRM available at the address cited below for each community.</P>
        <P>The BFEs and modified BFEs are made final in the communities listed below. Elevations at selected locations in each community are shown.</P>
        <P>
          <E T="03">National Environmental Policy Act.</E>This final rule is categorically excluded from the requirements of 44 CFR part 10, Environmental Consideration. An environmental impact assessment has not been prepared.<PRTPAGE P="76930"/>
        </P>
        <P>
          <E T="03">Regulatory Flexibility Act.</E>As flood elevation determinations are not within the scope of the Regulatory Flexibility Act, 5 U.S.C. 601-612, a regulatory flexibility analysis is not required.</P>
        <P>
          <E T="03">Regulatory Classification.</E>This final rule is not a significant regulatory action under the criteria of section 3(f) of Executive Order 12866 of September 30, 1993, Regulatory Planning and Review, 58 FR 51735.</P>
        <P>
          <E T="03">Executive Order 13132, Federalism.</E>This final rule involves no policies that have federalism implications under Executive Order 13132.</P>
        <P>
          <E T="03">Executive Order 12988, Civil Justice Reform.</E>This final rule meets the applicable standards of Executive Order 12988.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 44 CFR Part 67</HD>
          <P>Administrative practice and procedure, Flood insurance, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        
        <P>Accordingly, 44 CFR part 67 is amended as follows:</P>
        <REGTEXT PART="67" TITLE="44">
          <PART>
            <HD SOURCE="HED">PART 67—[AMENDED]</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 67 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 4001<E T="03">et seq.;</E>Reorganization Plan No. 3 of 1978, 3 CFR, 1978 Comp., p. 329; E.O. 12127, 44 FR 19367, 3 CFR, 1979 Comp., p. 376.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="67" TITLE="44">
          <SECTION>
            <SECTNO>§ 67.11</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. The tables published under the authority of § 67.11 are amended as follows:</AMDPAR>
          <GPOTABLE CDEF="s25,r50,15,r25" COLS="4" OPTS="L2,tp0,i1">
            <TTITLE/>
            <BOXHD>
              <CHED H="1">Flooding source(s)</CHED>
              <CHED H="1">Location of referenced elevation</CHED>
              <CHED H="1">* Elevation in feet (NGVD)<LI>+ Elevation in feet</LI>
                <LI>(NAVD)</LI>
                <LI># Depth in feet</LI>
                <LI>above ground</LI>
                <LI>⁁ Elevation in meters (MSL)</LI>
                <LI>modified</LI>
              </CHED>
              <CHED H="1">Communities affected</CHED>
            </BOXHD>
            <ROW EXPSTB="03">
              <ENT I="21">
                <E T="02">Shelby County, Alabama, and Incorporated Areas</E>
              </ENT>
            </ROW>
            <ROW RUL="s">
              <ENT I="21">
                <E T="02">Docket No.: FEMA-B-1233</E>
              </ENT>
            </ROW>
            <ROW EXPSTB="00">
              <ENT I="01">Acton Creek</ENT>
              <ENT>Approximately 0.78 mile downstream of Indian Valley Road</ENT>
              <ENT>+428</ENT>
              <ENT>City of Hoover, Unincorporated Areas of Shelby County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximate 595 feet upstream of Caldwell Mill Road</ENT>
              <ENT>+472</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Beaverdam Creek</ENT>
              <ENT>At the Cahaba River confluence</ENT>
              <ENT>+394</ENT>
              <ENT>City of Helena, Unincorporated Areas of Shelby County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 775 feet downstream of County Road 17</ENT>
              <ENT>+424</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Bishop Creek</ENT>
              <ENT>At the downstream side of Industrial Park Drive</ENT>
              <ENT>+423</ENT>
              <ENT>City of Helena, City of Pelham, Town of Indian Springs Village, Unincorporated Areas of Shelby County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 483 feet upstream of Surrey Lane</ENT>
              <ENT>+525</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Buck Creek</ENT>
              <ENT>Approximately 800 feet upstream of U.S. Route 261</ENT>
              <ENT>+412</ENT>
              <ENT>City of Alabaster, City of Helena, City of Pelham, Unincorporated Areas of Shelby County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.9 mile upstream of County Road 340</ENT>
              <ENT>+567</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Camp Creek (backwater effects from Kelly Creek)</ENT>
              <ENT>Approximately 841 feet upstream of the Kelly Creek confluence</ENT>
              <ENT>+439</ENT>
              <ENT>Unincorporated Areas of Shelby County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 0.7 mile upstream of the Kelly Creek confluence</ENT>
              <ENT>+439</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Coales Branch</ENT>
              <ENT>At the upstream side of CSX Railroad Bridge</ENT>
              <ENT>+444</ENT>
              <ENT>City of Pelham.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,350 feet upstream of Dow Street</ENT>
              <ENT>+494</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Dodd Branch</ENT>
              <ENT>Approximately 174 feet upstream of Lake Forest Circle</ENT>
              <ENT>+421</ENT>
              <ENT>City of Hoover, City of Pelham, Unincorporated Areas of Shelby County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 730 feet upstream of Indian Lake Lane</ENT>
              <ENT>+499</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Dodd Branch Tributary 1</ENT>
              <ENT>Approximately 908 feet downstream of Baneberry Drive</ENT>
              <ENT>+445</ENT>
              <ENT>City of Hoover, City of Pelham, Unincorporated Areas of Shelby County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,670 feet upstream of Indian Lake Way</ENT>
              <ENT>+487</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Dodd Branch Tributary 1.1</ENT>
              <ENT>At the downstream side of Stratshire Lane</ENT>
              <ENT>+453</ENT>
              <ENT>City of Helena, City of Pelham.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 413 feet upstream of Aaron Road</ENT>
              <ENT>+485</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Dry Creek I</ENT>
              <ENT>Approximately 0.47 mile downstream of Fox Valley Farms Road</ENT>
              <ENT>+422</ENT>
              <ENT>City of Alabaster, City of Helena, Unincorporated Areas of Shelby County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 531 feet downstream of Fox Valley Farms Road</ENT>
              <ENT>+423</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hogpen Creek</ENT>
              <ENT>At the upstream side of the railroad</ENT>
              <ENT>+452</ENT>
              <ENT>City of Pelham, Unincorporated Areas of Shelby County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 1,390 feet upstream of Berry Lane</ENT>
              <ENT>+510</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hurricane Creek (backwater effects from Cahaba River)</ENT>
              <ENT>Approximately 0.75 mile downstream of County Road 13</ENT>
              <ENT>+381</ENT>
              <ENT>City of Helena, Unincorporated Areas of Shelby County.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="76931"/>
              <ENT I="22"/>
              <ENT>Approximately 0.8 mile upstream of County Road 13</ENT>
              <ENT>+381</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Hurricane Creek I (backwater effects from Bear Creek)</ENT>
              <ENT>Approximately 1,365 feet downstream of Rocky Hollow Lane</ENT>
              <ENT>+464</ENT>
              <ENT>Unincorporated Areas of Shelby County.</ENT>
            </ROW>
            <ROW>
              <ENT I="22"/>
              <ENT>Approximately 416 feet upstream of Rocky Hollow Lane</ENT>
              <ENT>+464</ENT>
            </ROW>
            <ROW>
              <ENT I="01">Ivy Branch (backwater effects from North Fork Yellowleaf Creek)</ENT>
              <ENT>At the downstream side of County Road 