<?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>52</NO>
  <DATE>Friday, March 16, 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>Rural Utilities Service</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Animal</EAR>
      <HD>Animal and Plant Health Inspection Service</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Bovine Spongiform Encephalopathy; Importation of Bovines and Bovine Products,</DOC>
          <PGS>15848-15913</PGS>
          <FRDOCBP D="65" T="16MRP2.sgm">2012-6151</FRDOCBP>
        </DOCENT>
      </CAT>
    </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>Centers Disease</EAR>
      <HD>Centers for Disease Control and Prevention</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Subcommittee on Procedures Review, Advisory Board on Radiation and Worker Health, NIOSH,</SJDOC>
          <PGS>15761-15762</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6475</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Civil Rights</EAR>
      <HD>Civil Rights Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>District of Columbia Advisory Committee,</SJDOC>
          <PGS>15717-15718</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6376</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Nevada Advisory Committee,</SJDOC>
          <PGS>15717</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6360</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>North Dakota Advisory Committee,</SJDOC>
          <PGS>15717</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6353</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Coast Guard</EAR>
      <HD>Coast Guard</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Special Local Regulations:</SJ>
        <SJDENT>
          <SJDOC>Annual Marine Events in Eighth Coast Guard District,</SJDOC>
          <PGS>15604-15605</PGS>
          <FRDOCBP D="1" T="16MRR1.sgm">2012-6379</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Emerald Coast Super Boat Grand Prix; Saint Andrew Bay, Panama City, FL,</SJDOC>
          <PGS>15600-15602</PGS>
          <FRDOCBP D="2" T="16MRR1.sgm">2012-6377</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Spa Creek and Annapolis Harbor, Annapolis, MD,</SJDOC>
          <PGS>15602-15604</PGS>
          <FRDOCBP D="2" T="16MRR1.sgm">2012-6382</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>USAT Triathlon / Race Rowing Competition, Black Warrior River, Tuscaloosa, AL,</SJDOC>
          <PGS>15597-15600</PGS>
          <FRDOCBP D="3" T="16MRR1.sgm">2012-6381</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Special Local Regulations:</SJ>
        <SJDENT>
          <SJDOC>Temporary Change of Dates for Recurring Events in Fifth Coast Guard District, Ocean City, MD,</SJDOC>
          <PGS>15647-15650</PGS>
          <FRDOCBP D="3" T="16MRP1.sgm">2012-6380</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Requests For Applications:</SJ>
        <SJDENT>
          <SJDOC>Navigation Safety Advisory Council,</SJDOC>
          <PGS>15784-15785</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6378</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Commerce</EAR>
      <HD>Commerce Department</HD>
      <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>15718</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6416</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>
          <PGS>15736-15737</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6441</FRDOCBP>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6442</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Commodity Futures</EAR>
      <HD>Commodity Futures Trading Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Technology Advisory Committee,</SJDOC>
          <PGS>15737</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6369</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Consumer Product</EAR>
      <HD>Consumer Product Safety Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Meetings; Sunshine Act,</DOC>
          <PGS>15737</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6539</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>15737-15739</PGS>
          <FRDOCBP D="2" T="16MRN1.sgm">2012-6364</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Defense Acquisition</EAR>
      <HD>Defense Acquisition Regulations System</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>15739</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6255</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Defense Department</EAR>
      <HD>Defense Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Defense Acquisition Regulations System</P>
      </SEE>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Privacy Act; Implementation,</DOC>
          <PGS>15585-15597</PGS>
          <FRDOCBP D="1" T="16MRR1.sgm">2012-6167</FRDOCBP>
          <FRDOCBP D="2" T="16MRR1.sgm">2012-6168</FRDOCBP>
          <FRDOCBP D="2" T="16MRR1.sgm">2012-6169</FRDOCBP>
          <FRDOCBP D="1" T="16MRR1.sgm">2012-6170</FRDOCBP>
          <FRDOCBP D="1" T="16MRR1.sgm">2012-6171</FRDOCBP>
          <FRDOCBP D="1" T="16MRR1.sgm">2012-6172</FRDOCBP>
          <FRDOCBP D="1" T="16MRR1.sgm">2012-6173</FRDOCBP>
          <FRDOCBP D="1" T="16MRR1.sgm">2012-6174</FRDOCBP>
          <FRDOCBP D="1" T="16MRR1.sgm">2012-6175</FRDOCBP>
          <FRDOCBP D="1" T="16MRR1.sgm">2012-6176</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Education Department</EAR>
      <HD>Education Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>15739-15740</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6458</FRDOCBP>
        </DOCENT>
        <SJ>Applications for New Awards:</SJ>
        <SJDENT>
          <SJDOC>Alaska Native Education Program,</SJDOC>
          <PGS>15740-15745</PGS>
          <FRDOCBP D="5" T="16MRN1.sgm">2012-6459</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Employment and Training</EAR>
      <HD>Employment and Training Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Funding Availabilities:</SJ>
        <SJDENT>
          <SJDOC>Indian and Native American Employment and Training Programs,</SJDOC>
          <PGS>15811-15812</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6287</FRDOCBP>
        </SJDENT>
        <SJ>Funding Opportunities:</SJ>
        <SJDENT>
          <SJDOC>Serving Juvenile Offenders in High-Poverty, High-Crime Communities,</SJDOC>
          <PGS>15812</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6283</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Energy Department</EAR>
      <HD>Energy Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Energy Efficiency and Renewable Energy Office</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Energy Regulatory Commission</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Energy Efficiency</EAR>
      <HD>Energy Efficiency and Renewable Energy Office</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Appliance Standards and Rulemaking Federal Advisory Committee:</SJ>
        <SJDENT>
          <SJDOC>Establishment and Solicitation of Nominations for Membership; Correction,</SJDOC>
          <PGS>15745-15746</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6415</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>Connecticut; Determination of Attainment of One-hour Ozone Standard,</SJDOC>
          <PGS>15607-15608</PGS>
          <FRDOCBP D="1" T="16MRR1.sgm">2012-6424</FRDOCBP>
        </SJDENT>
        <SJ>Revisions to Final Response to Petition from New Jersey; Withdrawal</SJ>
        <SJDENT>
          <SJDOC>SO<E T="52">2</E>Emissions from the Portland Generating Station,</SJDOC>
          <PGS>15608-15609</PGS>
          <FRDOCBP D="1" T="16MRR1.sgm">2012-6427</FRDOCBP>
        </SJDENT>
        <SJ>Revocation of TSCA Section 4 Testing Requirements:</SJ>
        <SJDENT>
          <SJDOC>Certain High Production Volume Chemical Substances,</SJDOC>
          <PGS>15609-15617</PGS>
          <FRDOCBP D="8" T="16MRR1.sgm">2012-6430</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <PRTPAGE P="iv"/>
        <HD>PROPOSED RULES</HD>
        <SJ>Implementation of the New Source Review Program for Particulate Matter Less Than 2.5 Micrometers (PM2.5):</SJ>
        <SJDENT>
          <SJDOC>Amendment to the Definition Regulated NSR Pollutant Concerning Condensable Particulate Matter,</SJDOC>
          <PGS>15656-15664</PGS>
          <FRDOCBP D="8" T="16MRP1.sgm">2012-6429</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
        <SJDENT>
          <SJDOC>Weekly Receipt,</SJDOC>
          <PGS>15750</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6431</FRDOCBP>
        </SJDENT>
        <SJ>Final Test Guidelines; Availability:</SJ>
        <SJDENT>
          <SJDOC>Office of Chemical Safety and Pollution Prevention 810 Series,</SJDOC>
          <PGS>15750-15751</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6432</FRDOCBP>
        </SJDENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Local Government Advisory Committee and Small Communities Advisory Subcommittee,</SJDOC>
          <PGS>15751-15752</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6423</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Proposed Prospective Purchaser Agreement Amendment, etc.,</DOC>
          <PGS>15752-15753</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6425</FRDOCBP>
        </DOCENT>
        <SJ>Requests For Nominations:</SJ>
        <SJDENT>
          <SJDOC>Experts for Science Advisory Board Panel to Review EPA's Web-based Report on Environment,</SJDOC>
          <PGS>15753-15754</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6422</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR/>
      <HD>Executive Office of the President</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Trade Representative, Office of United States</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Federal Aviation</EAR>
      <HD>Federal Aviation Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Modifications of Class E Airspace:</SJ>
        <SJDENT>
          <SJDOC>Sheridan, WY,</SJDOC>
          <PGS>15575-15576</PGS>
          <FRDOCBP D="1" T="16MRR1.sgm">2012-6341</FRDOCBP>
        </SJDENT>
        <SJ>Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures:</SJ>
        <SJDENT>
          <SJDOC>Miscellaneous Amendments,</SJDOC>
          <PGS>15576-15585</PGS>
          <FRDOCBP D="8" T="16MRR1.sgm">2012-6006</FRDOCBP>
          <FRDOCBP D="1" T="16MRR1.sgm">2012-6010</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Airworthiness Directives:</SJ>
        <SJDENT>
          <SJDOC>Airbus Airplanes,</SJDOC>
          <PGS>15636-15638, 15644-15646</PGS>
          <FRDOCBP D="2" T="16MRP1.sgm">2012-6461</FRDOCBP>
          <FRDOCBP D="2" T="16MRP1.sgm">2012-6465</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Boeing Co. Airplanes,</SJDOC>
          <PGS>15638-15644</PGS>
          <FRDOCBP D="2" T="16MRP1.sgm">2012-6468</FRDOCBP>
          <FRDOCBP D="4" T="16MRP1.sgm">2012-6470</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Passenger Facility Charge Approvals and Disapprovals,</DOC>
          <PGS>15841-15843</PGS>
          <FRDOCBP D="2" T="16MRN1.sgm">2012-6315</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Communications</EAR>
      <HD>Federal Communications Commission</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Cellular Service:</SJ>
        <SJDENT>
          <SJDOC>Changes in Licensing of Unserved Areas; Interim Restrictions and Procedures for Applications,</SJDOC>
          <PGS>15665-15681</PGS>
          <FRDOCBP D="16" T="16MRP1.sgm">2012-5689</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Deposit</EAR>
      <HD>Federal Deposit Insurance Corporation</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Meetings; Sunshine Act,</DOC>
          <PGS>15754</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6515</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Update Listings of Financial Institutions in Liquidation,</DOC>
          <PGS>15755</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6417</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Emergency</EAR>
      <HD>Federal Emergency Management Agency</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Proposed Flood Elevation Determinations,</DOC>
          <PGS>15664-15665</PGS>
          <FRDOCBP D="1" T="16MRP1.sgm">2012-6356</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Emergency Declarations:</SJ>
        <SJDENT>
          <SJDOC>Connecticut, Amendment No. 2,</SJDOC>
          <PGS>15785</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6357</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Connecticut; Amendment No. 4,</SJDOC>
          <PGS>15785-15786</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6368</FRDOCBP>
        </SJDENT>
        <SJ>Major Disaster Declarations:</SJ>
        <SJDENT>
          <SJDOC>Connecticut; Amendment No. 1,</SJDOC>
          <PGS>15786</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6358</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Connecticut; Amendment No. 5,</SJDOC>
          <PGS>15786</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6362</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Kentucky; Amendment No. 1,</SJDOC>
          <PGS>15785</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6361</FRDOCBP>
        </SJDENT>
        <SJ>Major Disasters and Related Determinations:</SJ>
        <SJDENT>
          <SJDOC>Kentucky,</SJDOC>
          <PGS>15786-15787</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6355</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Washington,</SJDOC>
          <PGS>15787</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6370</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Energy</EAR>
      <HD>Federal Energy Regulatory Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Applications:</SJ>
        <SJDENT>
          <SJDOC>Dominion Transmission, Inc.; Clarification,</SJDOC>
          <PGS>15747</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6366</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Merced Irrigation District,</SJDOC>
          <PGS>15746</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6402</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Combined Filings,</DOC>
          <PGS>15747-15748</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6394</FRDOCBP>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6395</FRDOCBP>
        </DOCENT>
        <SJ>Motions for Extensions of Rate Case Filing Deadlines:</SJ>
        <SJDENT>
          <SJDOC>Atmos Energy Corp., Atmos Energy - Kentucky/Mid-States Division,</SJDOC>
          <PGS>15748-15749</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6401</FRDOCBP>
        </SJDENT>
        <SJ>Preliminary Permit Applications:</SJ>
        <SJDENT>
          <SJDOC>Peak Hour Power, LLC,</SJDOC>
          <PGS>15749</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6365</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Twin Lakes Canal Co.,</SJDOC>
          <PGS>15749-15750</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6367</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Housing Finance Agency</EAR>
      <HD>Federal Housing Finance Agency</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Private Transfer Fees,</DOC>
          <PGS>15566-15575</PGS>
          <FRDOCBP D="9" T="16MRR1.sgm">2012-6414</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Reserve</EAR>
      <HD>Federal Reserve System</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>15755-15757</PGS>
          <FRDOCBP D="2" T="16MRN1.sgm">2012-6332</FRDOCBP>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6347</FRDOCBP>
        </DOCENT>
        <SJ>Changes in Bank Control:</SJ>
        <SJDENT>
          <SJDOC>Acquisitions of Shares of Bank or Bank Holding Company,</SJDOC>
          <PGS>15757</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6436</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Trade</EAR>
      <HD>Federal Trade Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>15757-15759</PGS>
          <FRDOCBP D="2" T="16MRN1.sgm">2012-6400</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Fish</EAR>
      <HD>Fish and Wildlife Service</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Endangered and Threatened Wildlife and Plants:</SJ>
        <SJDENT>
          <SJDOC>Establishing Manatee Refuge in Kings Bay, Citrus County, FL,</SJDOC>
          <PGS>15617-15635</PGS>
          <FRDOCBP D="18" T="16MRR1.sgm">2012-6055</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Food and Drug</EAR>
      <HD>Food and Drug Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Citizen Petitions; Petition for Reconsideration or Stay of Action; Advisory Opinions,</SJDOC>
          <PGS>15762-15763</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6392</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Filing Objections and Requests for Hearing on Regulation or Order,</SJDOC>
          <PGS>15763-15764</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6393</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Waiver of In Vivo Demonstration of Bioequivalence of Animal Drugs in Soluble Powder Oral Dosage Form Products and Type A Medicated Articles,</SJDOC>
          <PGS>15764-15765</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6391</FRDOCBP>
        </SJDENT>
        <SJ>Food and Drug Administration Modernization Act of 1997:</SJ>
        <SJDENT>
          <SJDOC>Modifications to the List of Recognized Standards, Recognition List Number 028,</SJDOC>
          <PGS>15765-15779</PGS>
          <FRDOCBP D="14" T="16MRN1.sgm">2012-6389</FRDOCBP>
        </SJDENT>
        <SJ>Medical Devices:</SJ>
        <SJDENT>
          <SJDOC>Availability of Safety and Effectiveness Summaries for Premarket Approval Applications,</SJDOC>
          <PGS>15779-15780</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6390</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>General Services</EAR>
      <HD>General Services Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>State Agency Monthly Donation Report of Surplus Property,</SJDOC>
          <PGS>15759</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6405</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Health and Human</EAR>
      <HD>Health and Human Services Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Centers for Disease Control and Prevention</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Food and Drug Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Institutes of Health</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Final Effect of Designation of a Class of Employees for Addition to the Special Exposure Cohort,</DOC>
          <PGS>15759-15760</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6473</FRDOCBP>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6474</FRDOCBP>
        </DOCENT>
        <PRTPAGE P="v"/>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Health Information Technology Policy Advisory Committee,</SJDOC>
          <PGS>15760-15761</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6437</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Health Information Technology Standards Advisory Committee,</SJDOC>
          <PGS>15760</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6433</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Statements of Organization, Functions, and Delegation of Authority,</DOC>
          <PGS>15761</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6466</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Homeland</EAR>
      <HD>Homeland Security Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Coast Guard</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Emergency Management Agency</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>U.S. Citizenship and Immigration Services</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Housing</EAR>
      <HD>Housing and Urban Development Department</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Amendments to the HUD Acquisition Regulation,</DOC>
          <PGS>15681-15701</PGS>
          <FRDOCBP D="20" T="16MRP1.sgm">2012-6165</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Federal Properties Suitable as Facilities to Assist Homeless,</DOC>
          <PGS>15788-15794</PGS>
          <FRDOCBP D="6" T="16MRN1.sgm">2012-6053</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Indian Affairs</EAR>
      <HD>Indian Affairs Bureau</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
        <SJDENT>
          <SJDOC>Proposed KRoad Moapa Solar Generation Facility, Clark County, NE,</SJDOC>
          <PGS>15794-15795</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6203</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Interior</EAR>
      <HD>Interior Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Fish and Wildlife Service</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Indian Affairs Bureau</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>
    </AGCY>
    <AGCY>
      <EAR>Internal Revenue</EAR>
      <HD>Internal Revenue Service</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Guidance Regarding Deduction and Capitalization of Expenditures Related to Tangible Property,</DOC>
          <PGS>15646</PGS>
          <FRDOCBP D="0" T="16MRP1.sgm">2012-6371</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>International Trade Adm</EAR>
      <HD>International Trade Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Antidumping Duty Administrative Reviews; Results, Extensions, Amendments, etc.:</SJ>
        <SJDENT>
          <SJDOC>Circular Welded Carbon-Quality Steel Pipe from India, Sultanate of Oman, et al.; Postponement,</SJDOC>
          <PGS>15718</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6462</FRDOCBP>
        </SJDENT>
        <SJ>Countervailing Duty Administrative Reviews; Results, Extensions, Amendments, etc.:</SJ>
        <SJDENT>
          <SJDOC>Certain Pasta from Italy,</SJDOC>
          <PGS>15718-15719</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6463</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Justice Department</EAR>
      <HD>Justice Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Lodgings of Modified Consent Orders:</SJ>
        <SJDENT>
          <SJDOC>United States v. Kentucky Utilities Co.; Clean Air Act,</SJDOC>
          <PGS>15803</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6385</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Labor Department</EAR>
      <HD>Labor Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Employment and Training Administration</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Reintegration of Ex-Offenders, Adult Reporting System,</SJDOC>
          <PGS>15803-15804</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6435</FRDOCBP>
        </SJDENT>
        <SJ>Program Year 2012 Workforce Investment Act Allotments:</SJ>
        <SJDENT>
          <SJDOC>Wagner-Peyser Act Final Allotments and Workforce Information Grants,</SJDOC>
          <PGS>15804-15811</PGS>
          <FRDOCBP D="7" T="16MRN1.sgm">2012-6446</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Land</EAR>
      <HD>Land Management Bureau</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
        <SJDENT>
          <SJDOC>Gasco Energy Inc. Uinta Basin Natural Gas Development Project, Uintah County, UT,</SJDOC>
          <PGS>15795-15796</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6324</FRDOCBP>
        </SJDENT>
        <SJ>Filings of Plats of Surveys:</SJ>
        <SJDENT>
          <SJDOC>Oregon/Washington,</SJDOC>
          <PGS>15796</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6471</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Highway</EAR>
      <HD>National Highway Traffic Safety Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Petitions For Exemptions:</SJ>
        <SJDENT>
          <SJDOC>Nissan; Vehicle Theft Prevention Standard,</SJDOC>
          <PGS>15843-15845</PGS>
          <FRDOCBP D="2" T="16MRN1.sgm">2012-6411</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Institute</EAR>
      <HD>National Institute of Standards and Technology</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Workshops:</SJ>
        <SJDENT>
          <SJDOC>Federal Conformity Assessment Guidance,</SJDOC>
          <PGS>15719</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6373</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Institute</EAR>
      <HD>National Institutes of Health</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Child Health Disparities Measurement for the National Children's Study,</SJDOC>
          <PGS>15780-15782</PGS>
          <FRDOCBP D="2" T="16MRN1.sgm">2012-6354</FRDOCBP>
        </SJDENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Center For Scientific Review,</SJDOC>
          <PGS>15783</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6342</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Cancer Institute,</SJDOC>
          <PGS>15782-15783</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6337</FRDOCBP>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6345</FRDOCBP>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6352</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Institute of Diabetes and Digestive and Kidney Diseases,</SJDOC>
          <PGS>15784</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6340</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Institute of General Medical Sciences,</SJDOC>
          <PGS>15783-15784</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6336</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Oceanic</EAR>
      <HD>National Oceanic and Atmospheric Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Fisheries of Caribbean, Gulf of Mexico, and South Atlantic:</SJ>
        <SJDENT>
          <SJDOC>Comprehensive Annual Catch Limit Amendment for South Atlantic,</SJDOC>
          <PGS>15916-15932</PGS>
          <FRDOCBP D="16" T="16MRR2.sgm">2012-6450</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Atlantic Highly Migratory Species:</SJ>
        <SJDENT>
          <SJDOC>2012 Atlantic Bluefin Tuna Quota Specifications,</SJDOC>
          <PGS>15712-15716</PGS>
          <FRDOCBP D="4" T="16MRP1.sgm">2012-6453</FRDOCBP>
        </SJDENT>
        <SJ>Highly Migratory Species:</SJ>
        <SJDENT>
          <SJDOC>2006 Consolidated Highly Migratory Species Fishery Management Plan; Amendment 4,</SJDOC>
          <PGS>15701-15712</PGS>
          <FRDOCBP D="11" T="16MRP1.sgm">2012-6455</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Endangered and Threatened Species:</SJ>
        <SJDENT>
          <SJDOC>Take of Anadromous Fish,</SJDOC>
          <PGS>15719-15720</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6451</FRDOCBP>
        </SJDENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>New England Fishery Management Council,</SJDOC>
          <PGS>15720-15721</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6398</FRDOCBP>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6404</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>North Pacific Fishery Management Council,</SJDOC>
          <PGS>15722</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6399</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>South Atlantic Fishery Management Council,</SJDOC>
          <PGS>15721</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6448</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Southern California Hook and Line Survey,</SJDOC>
          <PGS>15722</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6403</FRDOCBP>
        </SJDENT>
        <SJ>Takes of Marine Mammals Incidental to Specified Activities:</SJ>
        <SJDENT>
          <SJDOC>Russian River Estuary Management Activities,</SJDOC>
          <PGS>15722-15735</PGS>
          <FRDOCBP D="13" T="16MRN1.sgm">2012-6452</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Park</EAR>
      <HD>National Park Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Intents to Repatriate Cultural Items:</SJ>
        <SJDENT>
          <SJDOC>Bureau of Indian Affairs, Washington, DC, and Arizona State Museum, University of Arizona, Tucson, AZ,</SJDOC>
          <PGS>15796-15798</PGS>
          <FRDOCBP D="2" T="16MRN1.sgm">2012-6334</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Colorado College, Colorado Springs, CO,</SJDOC>
          <PGS>15798</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6330</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>San Francisco State University, San Francisco, CA,</SJDOC>
          <PGS>15798-15800</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6325</FRDOCBP>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6326</FRDOCBP>
        </SJDENT>
        <SJ>Inventory Completions:</SJ>
        <SJDENT>
          <SJDOC>California Department of Parks and Recreation, Sacramento, CA,</SJDOC>
          <PGS>15801-15802</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6321</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <PRTPAGE P="vi"/>
          <SJDOC>Central Washington University Department of Anthropology, Ellensburg, WA,</SJDOC>
          <PGS>15802-15803</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6322</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Fish and Wildlife Service, Southwest Regional Office, Albuquerque, NM,</SJDOC>
          <PGS>15800-15801</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6323</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Nuclear Regulatory</EAR>
      <HD>Nuclear Regulatory Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Draft Regulatory Guides:</SJ>
        <SJDENT>
          <SJDOC>Initial Test Program of Condensate and Feedwater Systems for Light-Water Reactors,</SJDOC>
          <PGS>15812-15813</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6410</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Preoperational Testing of Instrument and Control Air Systems,</SJDOC>
          <PGS>15813-15814</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6413</FRDOCBP>
        </SJDENT>
        <SJ>Facility Operating Licenses:</SJ>
        <SJDENT>
          <SJDOC>PPL Susquehanna, LLC,</SJDOC>
          <PGS>15814-15818</PGS>
          <FRDOCBP D="4" T="16MRN1.sgm">2012-6407</FRDOCBP>
        </SJDENT>
        <SJ>Interim Staff Guidance; Availability:</SJ>
        <SJDENT>
          <SJDOC>License Renewal, Ongoing Review of Operating Experience,</SJDOC>
          <PGS>15818-15819</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6409</FRDOCBP>
        </SJDENT>
      </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>Postal Service</EAR>
      <HD>Postal Service</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Mobile Commerce and Personalization Promotion,</DOC>
          <PGS>15605-15607</PGS>
          <FRDOCBP D="2" T="16MRR1.sgm">2012-6086</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Rural Utilities</EAR>
      <HD>Rural Utilities Service</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Expansion of 911 Access Loans and Loan Guarantees,</DOC>
          <PGS>15564-15565</PGS>
          <FRDOCBP D="1" T="16MRR1.sgm">2012-6420</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Securities</EAR>
      <HD>Securities and Exchange Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
        <SJDENT>
          <SJDOC>Financial Industry Regulatory Authority, Inc.,</SJDOC>
          <PGS>15824-15833</PGS>
          <FRDOCBP D="2" T="16MRN1.sgm">2012-6386</FRDOCBP>
          <FRDOCBP D="6" T="16MRN1.sgm">2012-6444</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Fixed Income Clearing Corp.,</SJDOC>
          <PGS>15822-15824</PGS>
          <FRDOCBP D="2" T="16MRN1.sgm">2012-6384</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>New York Stock Exchange LLC,</SJDOC>
          <PGS>15826-15827</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6387</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>NYSE Arca, Inc.,</SJDOC>
          <PGS>15819-15822</PGS>
          <FRDOCBP D="3" T="16MRN1.sgm">2012-6383</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Options Price Reporting Authority,</SJDOC>
          <PGS>15833-15834</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6388</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Small Business</EAR>
      <HD>Small Business Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Exemption Requests,</DOC>
          <PGS>15834-15835</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6464</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Privacy Act; Systems of Records,</DOC>
          <PGS>15835-15839</PGS>
          <FRDOCBP D="4" T="16MRN1.sgm">2012-6467</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Special Inspector</EAR>
      <HD>Special Inspector General for Afghanistan Reconstruction</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Freedom of Information Act and Privacy Act Procedures,</DOC>
          <PGS>15555-15561</PGS>
          <FRDOCBP D="6" T="16MRR1.sgm">2012-6335</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Requests for Testimony or Production of Records in Court or Other Proceedings in Which U.S. is Not a Party,</DOC>
          <PGS>15561-15564</PGS>
          <FRDOCBP D="3" T="16MRR1.sgm">2012-6306</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>State Department</EAR>
      <HD>State Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Culturally Significant Objects Imported for Exhibition Determinations:</SJ>
        <SJDENT>
          <SJDOC>Joan Miro - the Ladder of Escape,</SJDOC>
          <PGS>15839</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6460</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Making a Presence - F. Holland Day in Artistic Photography,</SJDOC>
          <PGS>15839</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6457</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Trade Representative</EAR>
      <HD>Trade Representative, Office of United States</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>2011 Generalized System of Preferences Product Review:</SJ>
        <SJDENT>
          <SJDOC>Possible Actions Related to Competitive Need Limitations,</SJDOC>
          <PGS>15839-15841</PGS>
          <FRDOCBP D="2" T="16MRN1.sgm">2012-6349</FRDOCBP>
        </SJDENT>
        <SJ>Generalized System of Preferences:</SJ>
        <SJDENT>
          <SJDOC>Change in Hearing Date for the 2011 Annual GSP Product Review,</SJDOC>
          <PGS>15841</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6454</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>National Highway Traffic Safety Administration</P>
      </SEE>
    </AGCY>
    <AGCY>
      <EAR>Treasury</EAR>
      <HD>Treasury Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Internal Revenue Service</P>
      </SEE>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>15845</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6396</FRDOCBP>
        </DOCENT>
        <SJ>State Small Business Credit Initiative National Standards; Availability:</SJ>
        <SJDENT>
          <SJDOC>Compliance and Oversight for Participating States,</SJDOC>
          <PGS>15845-15846</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6412</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>U.S. Citizenship</EAR>
      <HD>U.S. Citizenship and Immigration Services</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Application for Travel Document,</SJDOC>
          <PGS>15787-15788</PGS>
          <FRDOCBP D="1" T="16MRN1.sgm">2012-6418</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Veteran Affairs</EAR>
      <HD>Veterans Affairs Department</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Fisher House and Other Temporary Lodging,</DOC>
          <PGS>15650-15656</PGS>
          <FRDOCBP D="6" T="16MRP1.sgm">2012-6397</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Advisory Committee on Minority Veterans,</SJDOC>
          <PGS>15846</PGS>
          <FRDOCBP D="0" T="16MRN1.sgm">2012-6469</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <PTS>
      <HD SOURCE="HED">Separate Parts In This Issue</HD>
      <HD>Part II</HD>
      <DOCENT>
        <DOC>Agriculture Department, Animal and Plant Health Inspection Service,</DOC>
        <PGS>15848-15913</PGS>
        <FRDOCBP D="65" T="16MRP2.sgm">2012-6151</FRDOCBP>
      </DOCENT>
      <HD>Part III</HD>
      <DOCENT>
        <DOC>Commerce Department, National Oceanic and Atmospheric Administration,</DOC>
        <PGS>15916-15932</PGS>
        <FRDOCBP D="16" T="16MRR2.sgm">2012-6450</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>52</NO>
  <DATE>Friday, March 16, 2012</DATE>
  <UNITNAME>Rules and Regulations</UNITNAME>
  <RULES>
    <RULE>
      <PREAMB>
        <PRTPAGE P="15555"/>
        <AGENCY TYPE="F">SPECIAL INSPECTOR GENERAL FOR AFGHANISTAN RECONSTRUCTION</AGENCY>
        <CFR>5 CFR Chapter LXXXIII and Part 9301</CFR>
        <RIN>RIN 3460-AA00</RIN>
        <SUBJECT>Freedom of Information Act and Privacy Act Procedures</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Special Inspector General for Afghanistan Reconstruction.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Interim final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This interim final rule establishes procedures for the public to obtain information from the Special Inspector General for Afghanistan Reconstruction under the Freedom of Information Act (FOIA) and the Privacy Act of 1974. These procedures will facilitate public interaction with SIGAR.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This interim final rule is effective March 16, 2012. Written comments may be submitted by April 16, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>You may submit comments, identified by RIN 3460-AA00 in the subject line to Mr. Hugo Teufel, Acting General Counsel, Special Inspector General for Afghanistan Reconstruction, 2530 Crystal Drive, Arlington, VA 22202-3940, email:<E T="03">hugo.teufel.civ@mail.mil</E>, phone (703) 545-5990, fax (703) 601-3804.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Kate Gastner, Public Information Manager, at (703) 545-5993, email:<E T="03">mary.k.gastner.civ@mail.mil</E>.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Background</HD>
        <P>On January 28, 2008, the President signed into law the National Defense Authorization Act for Fiscal Year 2008 (Pub. L. 110-181), whichcreated the Special Inspector General for Afghanistan Reconstruction (SIGAR). In order to establish procedures to facilitate public interaction with SIGAR, the agency is issuing interim final regulations under the FOIA and the Privacy Act.</P>
        <HD SOURCE="HD1">II. The Interim Final Rule</HD>
        <P>This interim final rule establishes procedures for SIGAR necessary to implement the FOIA (5 U.S.C. 552) and the Privacy Act (5 U.S.C. 552a). The provisions of this subpart shall apply to all components of SIGAR.</P>
        <P>The FOIA provides for the disclosure of agency records and information to the public, unless that information is exempted under delineatedstatutory exemptions under the FOIA. The Privacy Act serves to safeguard public interest in informational privacy by delineating the duties andresponsibilities of federal agencies that collect, store, and disseminate personal information about individuals. The procedures established here are intended to ensure that SIGAR fully satisfies its responsibility to the public to disclose agency information while simultaneouslysafeguarding individual privacy.</P>
        <P>The Privacy Act serves to balance the Government's need to maintaininformation about individuals with the rights of individuals to beprotected against unwarranted invasions of their privacy stemming from federal agencies' collection, maintenance, use, and disclosure of personal information about them. Agencies are required to issue regulationsoutlining the agency's rules and procedures for implementation of thePrivacy Act and its provisions within the agency. This includes procedures on how individuals may request access to information about themselves,request amendment or correction of those records, and request anaccounting of disclosures of their records by SIGAR.</P>
        <HD SOURCE="HD1">III. Procedural Requirements</HD>
        <P>These regulations establish procedures under the FOIA and the Privacy Act to facilitate the interaction of the public with SIGAR. SIGAR's policy of disclosure follows the Presidential Memorandum of January 21, 2009, “Transparency and Openness,” 74 FR 4685, and the Attorney General's March 19, 2009 FOIA policy guidance, advising Federal agencies to apply apresumption of disclosure in FOIA decision making. This Interim Final Rule parallels the procedures currently used by other agencies toimplement the FOIA and the Privacy Act. SIGAR has determined that good cause exists to publish these regulations as an interim final rule. These rules establish procedures to facilitate SIGAR's interactions with the public and the public's right to gain access to information about SIGAR and about themselves that SIGAR maintains. The absence of Privacy Actregulations could impair the confidentiality and privacy rights of those who submit sensitive information to SIGAR as well as the ability of SIGAR to use that information to carry out its statutory mission. SIGAR hasdetermined that this interim rule should be issued without a delayedeffective date pursuant to 5 U.S.C. 553(d)(3).</P>
        <P>Because no notice of proposed rulemaking is required, the provisions of the Regulatory Flexibility Act (5 U.S.C. Chapter 6) do not apply. It has been determined that this rulemaking is not a significant regulatoryaction for the purposes of Executive Order 12866. Accordingly, a regulatory impact analysis is not required.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 5 CFR Part 9301</HD>
          <P>Administrative practice and procedure, Freedom of information, Privacy.</P>
        </LSTSUB>
        <HD SOURCE="HD1">Authority and Issuance</HD>
        <P>For the reasons set forth above, SIGAR establishes 5 CFR Chapter LXXXIII, consisting of part 9301 to read as set forth below.</P>
        <REGTEXT PART="9301" TITLE="5">
          <HD SOURCE="HD1">Title 5—Administrative Personnel</HD>
          <HD SOURCE="HD1">CHAPTER LXXXIII—SPECIAL INSPECTOR GENERAL FOR AFGHANISTAN RECONSTRUCTION</HD>
          <PART>
            <HD SOURCE="HED">PART 9301—DISCLOSURE OF RECORDS AND INFORMATION</HD>
            <CONTENTS>
              <SECHD>Sec.</SECHD>
              <SUBPART>
                <HD SOURCE="HED">Subpart A—Freedom of Information Act</HD>
                <HD SOURCE="HD1">Procedures for Disclosure of Materials or Information</HD>
                <SECTNO>9301.1</SECTNO>
                <SUBJECT>In general.</SUBJECT>
                <SECTNO>9301.2</SECTNO>
                <SUBJECT>Authority and functions.</SUBJECT>
                <SECTNO>9301.3</SECTNO>
                <SUBJECT>Organization.</SUBJECT>
                <HD SOURCE="HD1">Procedures</HD>
                <SECTNO>9301.4</SECTNO>
                <SUBJECT>Availability of records.</SUBJECT>
                <SECTNO>9301.5</SECTNO>
                <SUBJECT>Accessing records without request.</SUBJECT>
                <SECTNO>9301.6</SECTNO>
                <SUBJECT>Requesting records.</SUBJECT>
                <HD SOURCE="HD1">Costs</HD>
                <SECTNO>9301.7</SECTNO>
                <SUBJECT>Definitions.</SUBJECT>
                <SECTNO>9301.8</SECTNO>
                <SUBJECT>Fees in general.</SUBJECT>
                <SECTNO>9301.9</SECTNO>
                <SUBJECT>Fees for categories of requesters.<PRTPAGE P="15556"/>
                </SUBJECT>
                <SECTNO>9301.10</SECTNO>
                <SUBJECT>Other charges.</SUBJECT>
                <SECTNO>9301.11</SECTNO>
                <SUBJECT>Payment and waiver.</SUBJECT>
              </SUBPART>
              <SUBPART>
                <HD SOURCE="HED">Subpart B—Privacy Act</HD>
                <SECTNO>9301.12</SECTNO>
                <SUBJECT>Purpose and scope.</SUBJECT>
                <SECTNO>9301.13</SECTNO>
                <SUBJECT>Rules for determining if an individual is the subject of arecord.</SUBJECT>
                <SECTNO>9301.14</SECTNO>
                <SUBJECT>Requests for access.</SUBJECT>
                <SECTNO>9301.15</SECTNO>
                <SUBJECT>Access to the accounting of disclosures from records.</SUBJECT>
                <SECTNO>9301.16</SECTNO>
                <SUBJECT>Requests for copies of records.</SUBJECT>
                <SECTNO>9301.17</SECTNO>
                <SUBJECT>Requests to amend records.</SUBJECT>
                <SECTNO>9301.18</SECTNO>
                <SUBJECT>Request for review.</SUBJECT>
                <SECTNO>9301.19</SECTNO>
                <SUBJECT>Schedule of fees.</SUBJECT>
              </SUBPART>
            </CONTENTS>
            <SUBPART>
              <HD SOURCE="HED">Subpart A—Freedom of Information Act</HD>
              <AUTH>
                <HD SOURCE="HED">Authority:</HD>
                <P>5 U.S.C. 552; Pub. L. No. 110-175, 121 Stat. 2524 (2007); 5 U.S.C. 301 and 552; Exec. Order 12600, 52 FR 23781, 3 CFR, 1987 Comp., p. 235; Exec. Order No. 13392, 70 FR 75373-75377, 3 CFR, 2006 Comp., pp. 216-200.</P>
              </AUTH>
              <HD SOURCE="HD1">Procedures for Disclosure of Records Under the Freedom of Information Act</HD>
              <SECTION>
                <SECTNO>§ 9301.1</SECTNO>
                <SUBJECT>In general.</SUBJECT>
                <P>This information is furnished for the guidance of the public and in compliance with the requirements of the Freedom of Information Act (FOIA), 5 U.S.C. 552, as amended. This subpart should be read in conjunction with the FOIA.</P>
              </SECTION>
              <SECTION>
                <SECTNO>§ 9301.2</SECTNO>
                <SUBJECT>Authority and functions.</SUBJECT>
                <P>Section 1229 of the National Defense Authorization Act for Fiscal Year 2008, Public Law 110-181, established the Special Inspector General for Afghanistan Reconstruction (SIGAR). SIGAR's mission under Sections 1229 and 842 of Public Law 110-181, is to provide independent oversight of the treatment, handling, and expenditure of funds appropriated or otherwise made available for the reconstruction of Afghanistan; detect and deter fraud, waste, and abuse of U.S. funds; and promote actions to increase program economy, efficiency, and effectiveness.</P>
              </SECTION>
              <SECTION>
                <SECTNO>§ 9301.3</SECTNO>
                <SUBJECT>Organization.</SUBJECT>
                <P>SIGAR maintains its headquarters in Arlington, Virginia, and field offices in Kabul and elsewhere in Afghanistan.</P>
                <HD SOURCE="HD1">Procedures</HD>
              </SECTION>
              <SECTION>
                <SECTNO>§ 9301.4</SECTNO>
                <SUBJECT>Availability of records.</SUBJECT>
                <P>SIGAR's publicly accessible records are available through SIGAR's Electronic Reading Room on its Web site. SIGAR also provides records to individual requesters in response to FOIA requests. SIGAR generally withholds predecisional, deliberative documents, investigatory materials and sensitive policy documents under 5 U.S.C. 552(b).</P>
              </SECTION>
              <SECTION>
                <SECTNO>§ 9301.5</SECTNO>
                <SUBJECT>Accessing records without request.</SUBJECT>

                <P>Certain SIGAR records, including the agency's Quarterly Report, audit reports, testimony, oversight plans, press releases and other public issuances, are available electronically from SIGAR's homepage at<E T="03">http://www.sigar.mil._ SIGAR</E>encourages requesters to visit its Web site before making a request for records under § 9301.6.</P>
              </SECTION>
              <SECTION>
                <SECTNO>§ 9301.6</SECTNO>
                <SUBJECT>Requesting records.</SUBJECT>
                <P>(a)<E T="03">Written requests required.</E>For records not available as described under § 9301.5, requesters wishing to obtain information from SIGAR should submit a written request to SIGAR's FOIA Officer. Requests should be addressed to FOIA Officer, Office of the Special Inspector General for Afghanistan Reconstruction, 2530 Crystal Drive, Arlington, VA 22202. As there may be delays in mail delivery, it is advisable to send the request via facsimile to (703) 601-3804 or by email to<E T="03">sigar.pentagon.gen-coun.mbx.foia@mail.mil.</E>
                </P>
                <P>(b)<E T="03">Contents of requests.</E>Requests should be as specific as possible and should reasonably specify the records sought so that the records can be located with a reasonable amount of effort. The request should identify the desired record or describe it, and include information such as the date, title or name, author, recipient, and subject matter of the record, where possible. The request should also include a statement of the requester's willingness to pay fees, or request a fee waiver. The words “FOIA REQUEST” or “REQUEST FOR RECORDS” should be clearly marked on the cover letter, letter, and/or envelope.</P>
                <P>(c)<E T="03">Response to requests</E>—(1)<E T="03">Processing.</E>The FOIA Officer shall determine within 20 days (except Saturdays, Sundays, and federal holidays) after receiving a request for records, whether it is appropriate to grant or deny the request. The 20-day period may be tolled once if the FOIA Officer requests information from the requestor or if additional time is necessary to clarify issues with the requestor regarding a fee assessment.</P>
                <P>(i)<E T="03">Request granted.</E>If the FOIA Officer decides to grant the request, the FOIA Officer shall promptly provide the requester written notice of the decision. The FOIA Officer shall include with the notice both the requested records and a copy of the decision. The notice shall also describe the procedure for filing an appeal.</P>
                <P>(ii)<E T="03">Request denied.</E>If the FOIA Officer denies the request, in full or part, the FOIA Officer shall provide the requester written notice of the denial together with the approximate number of pages of information withheld and the exemption under which the information was withheld. The notice shall also describe the procedure for filing an appeal.</P>
                <P>(2)(i)<E T="03">Expedited processing.</E>At the time a requester submits an initial request for records the requester may ask the FOIA Officer in writing to expedite processing of the request. The request for expedited processing must be accompanied by a written statement, which shall state that it is true and correct to the best of the requester's knowledge and belief, explaining why expedited processing is warranted. The FOIA Officer shall generally grant requests for expedited processing of requests for records, and appeals of denials under paragraph (d)(2) of this section, whenever the FOIA Officer determines that:</P>
                <P>(A) Failure to obtain the requested records on an expedited basis could reasonably pose a threat to a person's life or physical safety; or</P>
                <P>(B) With respect to a request made by a person primarily engaged in disseminating information, there is an urgency to inform the public about Government activity that is the specific subject of the FOIA request.</P>
                <P>(ii) The FOIA Officer shall ordinarily decide within ten calendar days after receiving a request for expedited processing whether to grant it and shall notify the requester of the decision. If the FOIA Officer grants a request for expedited processing, the FOIA Officer shall process the request as soon as practicable. If the FOIA Officer denies a request for expedited processing, SIGAR shall act expeditiously on any appeal of that denial.</P>
                <P>(3) Extension for unusual circumstances—(i) In general. If the FOIA Officer determines that unusual circumstances exist, the FOIA Officer may extend for no more than ten days (except Saturdays, Sundays and Federal holidays) the time limits described in paragraph (c)(1) of this section by providing written notice of the extension to the requester. The FOIA Officer shall include with the notice a brief statement of the reason for the extension and the date the FOIA Officer expects to make the determination.</P>
                <P>(ii)<E T="03">Additional procedures.</E>The FOIA Officer shall provide written notice to the requester if the FOIA Officer decides that the determination cannot be made within the time limit described in paragraph (c)(3)(i) of this section. The notice shall afford the requester an opportunity to limit the scope of the request to the extent necessary for the<PRTPAGE P="15557"/>FOIA Officer to process it within that time limit or an opportunity to arrange a longer period for processing the request.</P>
                <P>(d)<E T="03">Appeals</E>—(1)<E T="03">Initiating appeals.</E>Requesters not satisfied with the FOIA Officer's written decision may request SIGAR's FOIA Appellate Authority to review the decision. Appeals must be delivered in writing within 60 days of the date of the decision and shall be addressed to the FOIA Appellate Authority, Office of Privacy, Records &amp; Disclosure, Special Inspector General for Afghanistan Reconstruction, 2530 Crystal Drive, Arlington, VA 22202. As there may be delays in mail delivery, it is advisable to Fax appeals to (703) 601-3804 or email to<E T="03">sigar.pentagon.gen-coun.mbx.foia@mail.mil.</E>An appeal shall include a statement specifying the records that are the subject of the appeal and explaining why the Appellate Authority should grant the appeal.</P>
                <P>(2)<E T="03">Appeal decisions.</E>The Appellate Authority shall ordinarily decide the appeal within 20 days (except Saturdays, Sundays and federal holidays) from the date it receives the appeal. If the Appellate Authority denies the appeal in full or part, the Appellate Authority shall promptly notify the requester in writing of the Appellate Authority's decision and the provisions for judicial review. If the Appellate Authority grants the appeal, the FOIA Officer shall notify the requester in writing and shall make available to the requester copies of the releasable records once the requester pays any fees that SIGAR assesses under §§ 9301.8 through 9301.10.</P>
                <HD SOURCE="HD1">Costs</HD>
              </SECTION>
              <SECTION>
                <SECTNO>§ 9301.7</SECTNO>
                <SUBJECT>Definitions.</SUBJECT>
                <P>For purposes of this subpart:</P>
                <P>(a)<E T="03">Commercial use request</E>means a request from or on behalf of a person who seeks information for a use or purpose that furthers the requester's or other person's commercial, trade, or profit interests.</P>
                <P>(b)<E T="03">Direct costs</E>means those costs incurred in searching for and duplicating (and, in the case of commercial use requests, reviewing) documents to respond to a FOIA request. Direct costs include, for example, salaries of employees who perform the work and costs of conducting large-scale computer searches.</P>
                <P>(c)<E T="03">Duplicate</E>means to copy records to respond to a FOIA request. Copies can take the form of paper, audio-visual materials, or electronic records, among others.</P>
                <P>(d)<E T="03">Educational institution</E>means a preschool, a public or private elementary or secondary school, an institution of graduate higher education, an institution of undergraduate higher education, an institution of professional education, and an institution of vocational education, that operates a program or programs of scholarly research.</P>
                <P>(e)<E T="03">Non-commercial scientific institution</E>means an institution that is not operated on a commercial basis and that operates solely for the purpose of conducting scientific research the results of which are not intended to promote any particular product or industry.</P>
                <P>(f)<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.</P>
                <P>(g)<E T="03">Review</E>means to examine a record to determine whether any portion of the record may be withheld and to process a record for disclosure, including by redacting it.</P>
                <P>(h)<E T="03">Search for</E>means look for and retrieve records covered by a FOIA request, including by looking page-by-page or line-by-line to identify responsive material within individual records.</P>
              </SECTION>
              <SECTION>
                <SECTNO>§ 9301.8</SECTNO>
                <SUBJECT>Fees in general.</SUBJECT>
                <P>SIGAR shall charge reasonable fees that recoup the full allowable direct costs it incurs in responding to FOIA requests. SIGAR may assess charges for time spent searching for records even if SIGAR is unable to locate the records or if the records are located and determined to be exempt from disclosure. In general, SIGAR shall apply the following fee schedule, subject to §§ 9301.9 through 9301.11:</P>
                <P>(a)<E T="03">Manual searches.</E>Time devoted to manual searches shall be charged on the basis of the salary of the employee(s) conducting the search (basic hourly rate(s) of pay for the employee).</P>
                <P>(b)<E T="03">Electronic searches.</E>Fees shall reflect the direct cost of conducting the search. This will include the cost of operating the central processing unit for that portion of operating time that is directly attributable to searching for and printing records responsive to the FOIA request and operator/programmer salary attributable to the search.</P>
                <P>(c)<E T="03">Record reviews.</E>Time devoted to reviewing records shall be charged on the same basis as under paragraph (a) of this section, but shall only be applicable to the initial review of records located in response to commercial use requests.</P>
                <P>(d)<E T="03">Duplication.</E>Fees for copying paper records or for printing electronic records shall be assessed at a rate of $.10 per page. For other types of copies such as disks or audio visual tapes, SIGAR shall charge the direct cost of producing the document(s). If duplication charges are expected to exceed $25, the FOIA Officer shall notify the requester, unless the requester has indicated in advance a willingness to pay fees as high as those anticipated. If a requester wishes to limit costs, the FOIA Officer shall provide the requester an opportunity to reformulate the request in order to reduce costs. If the requester reformulates a request, it shall be considered a new request and the 20-day period described in § 9301.6(c)(1) shall be deemed to begin when the FOIA Officer receives the revised request.</P>
                <P>(e)<E T="03">Advance payments required.</E>(1)<E T="03"/>The FOIA Officer may require a requester to make an advance deposit of up to the amount of the entire anticipated fee before the FOIA Officer begins to process the request if:</P>
                <P>(i) The FOIA Officer estimates that the fee will exceed $250; or</P>
                <P>(ii) The requester has previously failed to pay a fee in a timely fashion.</P>
                <P>(2) When the FOIA Officer requires a requester to make an advance payment, the 20-day period described in § 9301.6(c)(1) shall begin when the FOIA Officer receives the payment.</P>
                <P>(f)<E T="03">No assessment of fee.</E>SIGAR shall not charge a fee to any requester if:</P>
                <P>(1) The cost of collecting the fee would be equal to or greater than the fee itself; or</P>
                <P>(2) SIGAR fails to comply with any time limit under the FOIA for responding to a request for records where no unusual or exceptional circumstances apply.</P>
              </SECTION>
              <SECTION>
                <SECTNO>§ 9301.9</SECTNO>
                <SUBJECT>Fees for categories of requesters.</SUBJECT>
                <P>SIGAR shall assess fees for certain categories of requesters as follows:</P>
                <P>(a)<E T="03">Commercial use requesters.</E>In responding to commercial use requests, SIGAR shall assess fees that recover the full direct costs of searching for, reviewing and duplicating records.</P>
                <P>(b)<E T="03">Educational institutions.</E>SIGAR shall provide records to requesters in this category for the cost of duplication alone, excluding charges for the first 100 pages. To qualify for inclusion in this fee category, a requester must show that the request is authorized by and is made under the auspices of a qualifying institution and that the records are sought to further scholarly research, not an individual goal.</P>
                <P>(c)<E T="03">Representatives of the news media.</E>SIGAR shall provide records to requesters in this category for the cost<PRTPAGE P="15558"/>of duplication alone, excluding charges for the first 100 pages.</P>
                <P>(d)<E T="03">All other requesters.</E>SIGAR shall charge requesters who do not fall within paragraphs (a) through (c) of this section fees that recover the full direct cost of searching for and duplicating records, excluding charges for the first 100 pages of reproduction and the first two hours of search time.</P>
              </SECTION>
              <SECTION>
                <SECTNO>§ 9301.10</SECTNO>
                <SUBJECT>Other charges.</SUBJECT>
                <P>SIGAR may apply other charges, including the following:</P>
                <P>(a)<E T="03">Special charges.</E>SIGAR shall recover the full cost of providing special services, such as sending records by an overnight delivery service, to the extent that SIGAR elects to provide them.</P>
                <P>(b)<E T="03">Interest charges.</E>SIGAR may begin assessing interest charges on an unpaid bill starting on the 31st day following the day on which the FOIA Officer sent the billing. Interest shall be charged at the rate prescribed in 31 U.S.C. 3717 and will accrue from the date of billing.</P>
                <P>(c)<E T="03">Aggregating requests.</E>When the FOIA Officer reasonably believes that a requester or a group of requesters acting in concert is attempting to divide a request into a series of requests for the purpose of avoiding fees, the FOIA Officer shall aggregate those requests and charge accordingly.</P>
              </SECTION>
              <SECTION>
                <SECTNO>§ 9301.11</SECTNO>
                <SUBJECT>Payment and waiver.</SUBJECT>
                <P>(a)<E T="03">Remittances.</E>Payment shall be made in the form of check or money order made payable to the Treasury of the United States. At the time the FOIA Officer notifies a requestor of the applicable fees, the Officer shall inform the requestor of where to send the payment.</P>
                <P>(b)<E T="03">Waiver.</E>SIGAR may waive all or part of any fee provided for in §§ 9301.8 through 9301.9 when the FOIA Officer deems that disclosure of the information is in the general public's interest because it is likely to contribute significantly to public understanding of the operations or activities of the Government and is not primarily in the commercial interest of the requester. Requesters may request a waiver in their initial FOIA request letter. Requests for a fee waiver should explain how the information requested contributes to the public's understanding of the operations or activities of the government. In determining whether a fee should be waived, the FOIA Officer may consider whether:</P>
                <P>(1) The subject matter specifically concerns identifiable operations or activities of the government;</P>
                <P>(2) The information is already in the public domain;</P>
                <P>(3) Disclosure of the information would contribute to the understanding of the public-at-large as opposed to a narrow segment of the population;</P>
                <P>(4) Disclosure of the information would significantly enhance the public's understanding of the subject matter;</P>
                <P>(5) Disclosure of the information would further a commercial interest of the requester; and</P>
                <P>(6) The public's interest is greater than any commercial interest of the requester.</P>
              </SECTION>
            </SUBPART>
            <SUBPART>
              <HD SOURCE="HED">Subpart B—Privacy Act</HD>
              <AUTH>
                <HD SOURCE="HED">Authority:</HD>
                <P>Privacy Act of 1974, Pub. L. 93-579, 88 Stat. 1896, codified at 5 U.S.C. 552a(f).</P>
              </AUTH>
              <SECTION>
                <SECTNO>§ 9301.12</SECTNO>
                <SUBJECT>Purpose and scope.</SUBJECT>
                <P>The purpose of this subpart is to provide certain safeguards for an individual against the invasion of his or her personal privacy by SIGAR. This subpart is promulgated pursuant to the requirements applicable to all federal agencies contained in 5 U.S.C. 552a(f).</P>
              </SECTION>
              <SECTION>
                <SECTNO>§ 9301.13</SECTNO>
                <SUBJECT>Rules for determining if an individual is the subject of a record.</SUBJECT>

                <P>(a) Individuals desiring to know if a specific system of records maintained by SIGAR contains a record pertaining to them should address their inquiries to the Privacy Officer, Special Inspector General for Afghanistan Reconstruction, 2530 Crystal Drive, Arlington, VA 22202. As there may be delays in mail delivery, it is advisable to send the request via facsimile to (703) 601-3804 or by email to<E T="03">sigar.pentagon.gen-coun.mbx.privacy@mail.mil.</E>The written inquiry should contain a specific reference to the system of records maintained by the SIGAR listed in the SIGAR Notice of Systems of Records, or it should describe the type of record in sufficient detail reasonably to identify the system of records. Notice of SIGAR systems of records subject to the Privacy Act will be published in the<E T="04">Federal Register</E>, posted on the SIGAR public facing Web site, and copies of the notices will be available upon request to the Privacy Officer when so published. A compilation of such notices will also be made and published by the Office of the Federal Register, in accordance with 5 U.S.C. 552a(f).</P>
                <P>(b) At a minimum, the request should contain sufficient identifying information to allow SIGAR to determine if there is a record pertaining to the individual making the request in a particular system of records. In instances when the requester's identification is insufficient to ensure disclosure to the individual to whom the information pertains in view of the sensitivity of the information, SIGAR reserves the right to solicit from the person requesting access to a record additional identifying information.</P>
                <P>(c) Ordinarily the person requesting will be informed whether the named system of records contains a record pertaining to such person within 10 days of such a request (excluding Saturdays, Sundays and legal Federal holidays). Such a response will also contain or reference the procedures which must be followed by the individual making the request in order to gain access to the record.</P>
                <P>(d) Whenever a response cannot be made within the 10 days, the Privacy Officer will inform the person making the request the reasons for the delay and the date on which a response may be anticipated.</P>
              </SECTION>
              <SECTION>
                <SECTNO>§ 9301.14</SECTNO>
                <SUBJECT>Requests for access.</SUBJECT>
                <P>(a)<E T="03">Requirement for written requests.</E>An individual desiring to gain access to a record pertaining to him or her in a system of records maintained by SIGAR must submit his or her request in writing in accordance with the procedures set forth in paragraph (b) of this section. Individuals employed by the SIGAR may make their requests on a regularly scheduled workday (Monday through Friday, excluding legal Federal holidays) between the hours of 9 a.m. and 5:30 p.m. Such requests for access by individuals employed by SIGAR need not be made in writing.</P>
                <P>(b)<E T="03">Procedures</E>—(1)<E T="03">Content of the request.</E>The request for access to a record in a system of records shall be addressed to the Privacy Officer at the address cited above, and shall name the system of records or contain a concise description of such system of records. The request should state that the request is pursuant to the Privacy Act of 1974. In the absence of such a statement, if the request is for a record pertaining to the person requesting access which is maintained by SIGAR in a system of records, the request will be considered under both the Privacy Act of 1974 and the Freedom of Information Act, depending on which would allow greater access to the records requested. The request should contain necessary information to verify the identity of the person requesting access (see paragraph (b)(2)(vi) of this section). In addition, such person should include any other information which may assist in the rapid identification of the record for which access is being requested (<E T="03">e.g.,</E>maiden name, dates of employment, etc.) as well as any other identifying information contained in and required<PRTPAGE P="15559"/>by the SIGAR Notice of Systems of Records.</P>
                <P>(i) If the request for access follows a prior request under § 9301.1, the same identifying information need not be included in the request for access if a reference is made to that prior correspondence or a copy of the SIGAR response to that request is attached. If the individual specifically desires a copy of the record, the request should so specify under § 9301.4.</P>
                <P>(ii) [Reserved]</P>
                <P>(2)<E T="03">SIGAR action on request.</E>A request for access will ordinarily be answered within 10 days, except when the Privacy Officer determines otherwise, in which case the person making the request will be informed of the reasons for the delay and an estimated date by which the request will be answered. When the request can be answered within 10 days, it shall include the following:</P>
                <P>(i) A statement that there is a record as requested or a statement that there is not a record in the systems of records maintained by SIGAR;</P>
                <P>(ii) A statement as to whether access will be granted only by providing a copy of the record through the mail; or the address of the location and the date and time at which the record may be examined. In the event the person requesting access is unable to meet the specified date and time, alternative arrangements may be made with the Privacy Officer;</P>
                <P>(iii) A statement, when appropriate, that examination in person will be the sole means of granting access only when the Privacy Officer has determined that it would not unduly impede the right of access of the person making the request.</P>
                <P>(iv) The amount of fees charged, if any (see §§ 9301.6 and 9301.7). (Fees are applicable only to requests for copies);</P>
                <P>(v) The name, title, and telephone number of the SIGAR official having operational control over the record; and</P>
                <P>(vi) The documentation required by SIGAR to verify the identity of the person making the request. At a minimum, SIGAR verification standards include the following:</P>
                <P>(A)<E T="03">Current or former SIGAR Employees.</E>Current or former SIGAR employees requesting access to a record pertaining to them in a system of records maintained by SIGAR may, in addition to the other requirements of this section, and at the sole discretion of the official having operational control over the record, have his or her identity verified by visual observation. If the current or former SIGAR employee cannot be so identified by the official having operational control over the records, identification documentation will be required. The employee's common access card, annuitant identification, driver licenses, or the “employee copy” of any official personnel document in the record are examples of acceptable identification validation.</P>
                <P>(B)<E T="03">Other than current or former SIGAR employees.</E>Individuals other than current or former SIGAR employees requesting access to a record pertaining to them in a system of records maintained by SIGAR must produce identification documentation of the type described in paragraph (b)(2)(vi)(A) of this section, prior to being granted access. The extent of the identification documentation required will depend on the type of record for which access is requested. In most cases, identification verification will be accomplished by the presentation of two forms of identification. Any additional requirements will be specified in the system of records notices published by SIGAR pursuant to 5 U.S.C. 552a(e)(4).</P>
                <P>(C)<E T="03">Access granted by mail.</E>For records to be made accessible by mail, the Privacy Officer shall, to the extent possible, establish identity by a comparison of signatures in situations where the data in the record is not so sensitive that unauthorized access could cause harm or embarrassment to the individual to whom they pertain. No identification documentation will be required for the disclosure to a person making a request of information under the FOIA, 5 U.S.C. 552. When, in the opinion of the Privacy Officer the granting of access through the mail could reasonably be expected to result in harm or embarrassment if disclosed to a person other than the individual to whom the record pertains, a notarized statement of identity or some similar assurance of identity will be required.</P>
                <P>(D)<E T="03">Unavailability of identification documentation.</E>If an individual is unable to produce adequate identification documentation the individual will be required to sign a statement asserting identity and acknowledging that knowingly or willfully seeking or obtaining access to records about another person under false pretenses may result in a fine of up to $5,000. In addition, depending upon the sensitivity of the records to which access is sought, the official having operational control over the records may require such further reasonable assurances as may be considered appropriate;<E T="03">e.g.,</E>statements of other individuals who can attest to the identity of the person making the request.</P>
                <P>(E)<E T="03">Access by the parent of a minor, or by a legal guardian.</E>A parent of a minor, upon presenting suitable personal identification, may act on behalf of the minor to gain access to any record pertaining to the minor maintained by SIGAR in a system of records. A legal guardian may similarly act on behalf of an individual declared to be incompetent due to physical or mental incapacity or age by a court of competent jurisdiction, upon the presentation of the documents authorizing the legal guardian to so act, and upon suitable personal identification of the guardian.</P>
                <P>(F) Granting access when accompanied by another individual. When an individual requesting access to his or her record in a system of records maintained by SIGAR wishes to be accompanied by another individual during the course of the examination of the record, the individual making the request shall submit to the official having operational control of the  record, a signed statement authorizing that person access to the record.</P>
                <P>(G)<E T="03">Granting access to individuals other than the subject of the record.</E>SIGAR will not disclose any record which is contained in a system of records by any means of communication to any person, or to another agency, except pursuant to a written request by, or with the prior written consent of, the individual to whom the record pertains, pursuant to the Privacy Act of 1974.</P>
                <P>(H)<E T="03">Denial of access for inadequate identification documentation.</E>If the official having operation control over the records in a system of records maintained by SIGAR determines that an individual seeking access has not provided sufficient identification documentation to permit access, the official shall consult with the Privacy Officer prior to finally denying the individual access.</P>
                <P>(vii)<E T="03">Medical records.</E>The records in a system of records which are medical records shall be disclosed to the individual to whom they pertain in such manner and following such procedures as the Privacy Officer shall direct. When SIGAR in consultation with a physician, determines that the disclosure of medical information could have an adverse effect upon the individual to whom it pertains, SIGAR may transmit such information to a physician named by the individual.</P>
                <P>(viii)<E T="03">Exceptions.</E>Nothing in this section shall be construed to entitle an individual the right to access to any information compiled in reasonable anticipation of litigation.</P>
              </SECTION>
              <SECTION>
                <PRTPAGE P="15560"/>
                <SECTNO>§ 9301.15</SECTNO>
                <SUBJECT>Access to the accounting of disclosures from records.</SUBJECT>
                <P>Rules governing the granting of access to the accounting of disclosures are the same as those for granting access to the records (including verification of identity) outlined in § 9301.14.</P>
              </SECTION>
              <SECTION>
                <SECTNO>§ 9301.16</SECTNO>
                <SUBJECT>Requests for copies of records.</SUBJECT>
                <P>Rules governing requests for copies of records are the same as those for the granting of access to the records (including verification of identity) outlined in § 9301.14. (See also § 9301.19 for rules regarding fees.)</P>
              </SECTION>
              <SECTION>
                <SECTNO>§ 9301.17</SECTNO>
                <SUBJECT>Requests to amend records.</SUBJECT>
                <P>(a)<E T="03">Requirement for written requests.</E>Individuals desiring to amend a record that pertains to them in a system of records maintained by SIGAR must submit their request in writing in accordance with the procedures set forth herein unless this requirement is waived by the official having responsibility for the system of records. Records not subject to the Privacy Act of 1974 will not be amended in accordance with these provisions. However, individuals who believe that such records are inaccurate may bring this to the attention of SIGAR.</P>
                <P>(b)<E T="03">Procedures.</E>(1)(i) The request to amend a record in a system of records shall be addressed to the Privacy Officer. Included in the request shall be the name of the system and a brief description of the record proposed for amendment. In the event the request to amend the record is the result of the individual's having gained access to the record in accordance with the provisions concerning access to records as set forth in this paragraph, copies of previous correspondence between the individual and SIGAR will serve in lieu of a separate description of the record.</P>
                <P>(ii) When the individual's identity has been previously verified pursuant to § 9301.14(b)(2)(vi), further verification of identity is not required as long as the communication does not suggest that a need for verification has reappeared. If the individual's identity has not been previously verified, SIGAR may require identification validation as described in § 9301.14(b)(2)(vi). Individuals desiring assistance in the preparation of a request to amend a record should contact the Privacy Officer at the address cited above.</P>
                <P>(iii) The exact portion of the record the individual seeks to have amended should be clearly indicated. If possible, the desired proposed alternative language should also be set forth, or at a minimum, the facts which the individual believes are not accurate, relevant, timely, or complete should be set forth with such particularity as to permit SIGAR to understand the basis for the request and to make an appropriate amendment to the record.</P>
                <P>(iv) The request should also set forth the reasons why the individual believes his record is not accurate, relevant, timely, or complete. In order to avoid the retention by SIGAR of personal information merely to permit verification of records, the burden of persuading SIGAR to amend a record will be upon the individual. The individual must furnish sufficient facts or credible documentation to persuade the official in charge of the system of the inaccuracy, irrelevancy, untimeliness, or incompleteness of the record.</P>
                <P>(2)<E T="03">SIGAR action on the request.</E>To the extent possible, a decision upon a request to amend a record will be made within 10 days, excluding Saturdays, Sundays, and legal Federal holidays. In the event a decision cannot be made within this timeframe, the individual making the request will be informed within 10 days of the expected date for a decision. The decision upon a request for amendment will include the following:</P>
                <P>(i) The decision of SIGAR whether to grant in whole, or deny any part of the request to amend the record.</P>
                <P>(ii) The reasons for the determination for any portion of the request which is denied.</P>
                <P>(iii) The name and address of the official with whom an appeal of the denial may be lodged.</P>
                <P>(iv) The name and address of the official designated to assist, as necessary, and upon request of, the individual making the request in the preparation of the appeal.</P>
                <P>(v) A description of the review of the appeal within SIGAR (see § 9301.18).</P>
                <P>(vi) A description of any other procedures which may be required of the individual in order to process the appeal.</P>
              </SECTION>
              <SECTION>
                <SECTNO>§ 9301.18</SECTNO>
                <SUBJECT>Request for review.</SUBJECT>
                <P>(a) Individuals wishing to request a review of the decision by SIGAR with regard to an initial request to amend a record in accordance with the provisions of § 9301.17, should submit the request for review in writing and, to the extent possible, include the information specified in § 9301.17(a). Individuals desiring assistance in the preparation of their request for review should contact the Privacy Officer at the address provided herein.</P>
                <P>(b) The request for review should contain a brief description of the record involved or in lieu thereof, copies of the correspondence from SIGAR in which the request to amend was denied, and also should state the reasons why the individual believes that the disputed information should be amended. The request for review should make reference to the information furnished by the individual in support of his claim and the reasons, as required by § 9301.17, set forth by SIGAR in its decision denying the amendment. In order to avoid the unnecessary retention of personal information, SIGAR reserves the right to dispose of the material concerning the request to amend a record if no request for review in accordance with this section is received by SIGAR within 180 days of the mailing by SIGAR of its decision upon an initial request. A request for review received after the 180-day period may, at the discretion of the Privacy Officer, be treated as an initial request to amend a record.</P>

                <P>(c) The request for review should be addressed to the Appellate Authority, Office of the Special Inspector General for Afghanistan Reconstruction, 2530 Crystal Drive, Arlington, VA 22202. As there may be delays in mail delivery, it is advisable to send the request via facsimile to (703) 601-3804 or by email to<E T="03">sigar.pentagon.gen-coun.mbx.privacy@mail.mil.</E>
                </P>
                <P>(d) Final determinations on requests for reviews within SIGAR will be made by the Appellate Authority. Additional information may be requested by the Appellate Authority from the person requesting a review if necessary to make a determination.</P>

                <P>(e) The Appellate Authority will inform the person making the request in writing of the decision on the request for review within 30 days (excluding Saturdays, Sundays and legal Federal holidays) from the date of receipt by SIGAR of the individual's request for review, unless the Appellate Authority extends the 30-day period for good cause. The extension and the reasons therefore will be sent by SIGAR to the individual within the initial 30-day period. Included in the notice of a decision being reviewed, if the decision does not grant in full the request for review, will be a description of the steps the individual may take to obtain judicial review of such a decision, and a statement that the individual may file a concise statement with SIGAR setting forth the individual's reasons for his disagreement with the decision upon the request for review. The SIGAR Privacy Officer has the authority to determine the “conciseness” of the statement, taking into account the scope of the disagreement and the complexity of the issues. Upon the filing of a proper concise statement by the individual, any subsequent disclosure of the<PRTPAGE P="15561"/>information in dispute will have the information in dispute clearly noted and a copy of the concise statement furnished, setting forth its reasons for not making the requested changes, if SIGAR chooses to file such a statement. A copy of the individual's statement, and if it chooses, SIGAR's statement, will be sent to any prior transferee of the disputed information who is listed on the accounting required by 5 U.S.C. 552a(c).</P>
              </SECTION>
              <SECTION>
                <SECTNO>§ 9301.19</SECTNO>
                <SUBJECT>Schedule of fees.</SUBJECT>
                <P>(a)<E T="03">Prohibitions against charging fees.</E>Individuals will not be charged for:</P>
                <P>(1) The search and review of the record;</P>
                <P>(2) Any copies of the record produced as a necessary part of the process of making the record available for access; or</P>
                <P>(3) Any copies of the requested record when it has been determined that access can only be accomplished by providing a copy of the record through the mail.</P>
                <P>(b)<E T="03">Waiver.</E>The Privacy Officer may, at no charge, provide copies of a record if it is determined that the production of the copies is in the interest of the Government.</P>
                <P>(c)<E T="03">Fee schedule and method of payment.</E>Fees will be charged as provided below except as provided in paragraphs (a) and (b) of this section.</P>
                <P>(1) Duplication of records. Records will be duplicated at a rate of $.10 per page for copying of 4 pages or more. There is no charge for copying fewer pages.</P>
                <P>(2) Where it is anticipated that the fees chargeable under this section will amount to more than $25, the person making the request shall be notified of the amount of the anticipated fee or such portion thereof as can readily be estimated. In instances where the estimated fees will greatly exceed $25, an advance deposit may be required. The notice or request for an advance deposit shall extend an offer to the person requesting to consult with the Privacy Officer in order to reformulate the request in a manner which will reduce the fees, yet still meet the needs of individuals making the request.</P>
                <P>(3) Fees must be paid in full prior to issuance of requested copies. In the event the person requesting is in arrears for previous requests copies will not be provided for any subsequent request until the arrears have been paid in full.</P>
                <P>(4) Remittances shall be in the form either of a personal check or bank draft drawn on a bank in the United States, or a postal money order. Remittances shall be made payable to the order of the Treasury of the United States and mailed or delivered to the Privacy Officer, Office of the Special Inspector General for Afghanistan Reconstruction, 2530 Crystal Drive, Arlington, VA 22202.</P>
                <P>(5) A receipt for fees paid will be given upon request.</P>
              </SECTION>
            </SUBPART>
          </PART>
        </REGTEXT>
        <SIG>
          <DATED>Dated: March 12, 2012.</DATED>
          <NAME>Steven J Trent,</NAME>
          <TITLE>Acting Inspector General, Special Inspector General for Afghanistan Reconstruction.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6335 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3710-L9-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">SPECIAL INSPECTOR GENERAL FOR AFGHANISTAN RECONSTRUCTION</AGENCY>
        <CFR>5 Part 9302</CFR>
        <RIN>RIN 3460-AA02</RIN>
        <SUBJECT>Requests for Testimony or the Production of Records in a Court or Other Proceedings in Which the United States Is Not a Party</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Special Inspector General for Afghanistan Reconstruction.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Interim final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This interim final rule establishes procedures for the public to obtain the production or disclosure of information and documents of Special Inspector General for Afghanistan Reconstruction (SIGAR) in connection with legal proceedings in which neither the United States nor the SIGAR is a party. It sets forth the procedures used when determining whether SIGAR employees will be permitted to testify or provide records relating to their official duties when they are subpoenaed or otherwise requested to testify. The rule also specifies the criteria that SIGAR officials are to use when deciding whether to allow an employee to testify or provide records.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This interim final rule is effective March 16, 2012. Written comments may be submitted by April 16, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Submit written comments to Hugo Teufel, Acting General Counsel, email:<E T="03">hugo.teufel.civ@mail.mil,</E>Special Inspector General for Afghanistan Reconstruction, Arlington, Virginia.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Hugo Teufel, Acting General Counsel, at (703) 703-545-5990, email:<E T="03">hugo.teufel.civ@mail.mil.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background</HD>
        <P>On January 28, 2008, the President signed into law the National Defense Authorization Act for Fiscal Year 2008 (Pub. L. 110-181), which created the Special Inspector General for Afghanistan Reconstruction (SIGAR). Under 5 U.S.C. 301, heads of Executive or military departments may prescribe regulations governing the conduct of its employees and the custody, use, and preservation of the department's records, papers, and property. Many departments and agencies have promulgated such regulations to provide procedures for the disclosure of official records and information.</P>
        <P>Generally, these are termed<E T="03">Touhy</E>regulations, after the Supreme Court's decision in<E T="03">United States ex rel. Touhy</E>v.<E T="03">Regan, 340 U.S. 462 (1951).</E>In that case, the Supreme Court held that an agency employee could not be held in contempt for refusing to disclose agency records or information when following instructions of his or her supervisor regarding the disclosure that were issued pursuant to agency regulations. As such, an agency's<E T="03">Touhy</E>regulations are the instructions agency employees are to follow when those employees receive requests or demands to testify or otherwise disclose agency records or information.</P>
        <P>SIGAR's proposed<E T="03">Touhy</E>regulations provide generally that employees of SIGAR may not disclose documents or information in response to a demand or order of a court or any other authority without first being authorized by the agency to do so. The purpose of these regulations is to conserve valuable agency resources, protect SIGAR employees from becoming enmeshed in litigation, and to protect sensitive Government information and decision making processes within the confines of the law. In order to establish procedures to facilitate public interaction with SIGAR, SIGAR is issuing proposed and interim final regulations.</P>
        <HD SOURCE="HD1">II. The Interim Final Rule</HD>
        <P>This interim final rule establishes procedures governing the disclosure of information and records in connection with court litigation and certain other types of proceedings.</P>
        <HD SOURCE="HD1">III. Procedural Requirements</HD>
        <P>This interim final rule is generally similar to the<E T="03">Touhy</E>procedures concerning the disclosure of information in litigation that have been adopted by other agencies. Further, this rule relates to agency management and personnel. Accordingly, SIGAR has determined that notice and public procedure thereon are impracticable, unnecessary and contrary to the public interest pursuant to 5 U.S.C. 553(b)(3)(B). For the same reasons, SIGAR has determined that this interim rule should be issued without a delayed effective date pursuant to 5 U.S.C.<PRTPAGE P="15562"/>553(d)(3). Nevertheless, SIGAR will consider any public comments on this interim final rule before issuing its final rule.</P>
        <P>Because no notice of proposed rulemaking is required, the provisions of the Regulatory Flexibility Act (5 U.S.C. chapter 6) do not apply.</P>
        <P>It has been determined that this rulemaking is not a significant regulatory action for the purposes of Executive Order 12866. Accordingly, a regulatory impact analysis is not required.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 5 CFR Part 9302</HD>
          <P>Courts, Government employees, Freedom of information, Government employees.</P>
        </LSTSUB>
        <HD SOURCE="HD1">Authority and Issuance</HD>
        <REGTEXT PART="9302" TITLE="5">
          <AMDPAR>For the reasons set forth above, 5 CFR chapter LXXXIII is amended to add part 9302 to read as follows:</AMDPAR>
          <PART>
            <HD SOURCE="HED">PART 9302—REQUESTS FOR TESTIMONY OR THE PRODUCTION OF RECORDS IN A COURT OR OTHER PROCEEDINGS IN WHICH THE UNITED STATES IS NOT A PARTY</HD>
            <AUTH>
              <HD SOURCE="HED">Authority:</HD>
              <P>Pub. L. 110-181 (Jan. 28, 2008), Section 1229 (122 Stat. 378-85), as amended, and Section 842 (122 Stat. 234-36), 10 U.S.C. 2302 note; and 5 U.S.C. 301.</P>
            </AUTH>
            <SECTION>
              <SECTNO>§ 9302.1</SECTNO>
              <SUBJECT>SIGAR Touhy regulations.</SUBJECT>
              <P>(a)<E T="03">Applicability.</E>(1) This section sets forth the policies and procedures of the Special Inspector General for Afghanistan Reconstruction (SIGAR or the agency) regarding the testimony of employees and former employees as witnesses and the production or disclosure of SIGAR documents or information for use in legal proceedings in which the United States is not a party and where the demand is pursuant to a subpoena, order or request (collectively referred to in this section as a “demand”).</P>
              <P>(2) This section does not apply to any legal proceeding in which an employee is to testify while on leave status regarding facts or events that are unrelated to the official business of SIGAR.</P>
              <P>(3)(i) Nothing in this section affects the rights and procedures governing public access to agency records pursuant to the Freedom of Information Act (5 U.S.C. 552) or the Privacy Act (5 U.S.C. 552a).</P>
              <P>(ii) Demands in legal proceedings in which the United States is not a party for the production of SIGAR records or information, or for the testimony of SIGAR employees, regarding information or documents that are protected by the Privacy Act (5 U.S.C. 552a), the Trade Secrets Act (18 U.S.C. 1905) or other statutes, must satisfy the requirements for disclosure set forth in those statutes and the applicable regulations of this part, before the records may be provided or testimony given.</P>
              <P>(4) This section is intended to provide guidance for the internal operations of SIGAR and to inform the public about SIGAR procedures concerning service of process upon SIGAR and its responses to demands. The procedures specified in this section, or the failure of any SIGAR employee to follow the procedures specified in this section, are not intended to, do not, and may not be relied upon to create a right or benefit, substantive or procedural, enforceable at law by a party against the United States.</P>
              <P>(b)<E T="03">Definitions.</E>For purposes of this section:</P>
              <P>
                <E T="03">Agency counsel</E>means: SIGAR's General Counsel or his or her designee.</P>
              <P>
                <E T="03">Demand</E>means a subpoena, order or request for testimony, documents or information related to, or for possible use in, a legal proceeding in which the United States is not a party.</P>
              <P>
                <E T="03">Document</E>means any record or other property, no matter what media, and including copies thereof, held by SIGAR, including without limitation, letters, Emails, telegrams, memoranda, facsimiles, reports, studies, calendar and diary entries, maps, graphs, pamphlets, notes, charts, tabulations, analyses, statistical or informational accumulations, summaries of meetings and conversations, film impressions, magnetic tapes and sound or mechanical reproductions.</P>
              <P>
                <E T="03">Employee</E>means all employees or officers of SIGAR, including (for the purpose of this section only) contractors and any other individuals who have been appointed by, or are subject to the supervision, jurisdiction or control of SIGAR. The procedures established within this subpart also apply to former employees of SIGAR where specifically stated in this section.</P>
              <P>
                <E T="03">General Counsel</E>means the General Counsel of SIGAR.</P>
              <P>
                <E T="03">Legal proceeding</E>means all pretrial, trial and post-trial stages of all judicial or administrative actions, hearings, investigations, arbitrations or similar proceedings before courts, commissions, boards, grand juries, or other tribunals, foreign or domestic. This term includes all phases of discovery as well as responses to informal requests by attorneys or others involved in legal proceedings seeking interviews or the like.</P>
              <P>
                <E T="03">Official business</E>means the authorized business of SIGAR as stated in the “National Defense Authorization Act for Fiscal Year 2008,” Pub. L. 110-181 (Jan. 28, 2008), Section 1229 (122 Stat. 378-85), as amended, and Section 842 (122 Stat. 234-36), 10 U.S.C. 2302 note.</P>
              <P>
                <E T="03">Testimony</E>means an employee's statement in any form, including testifying before a court or other tribunal or board, giving depositions, interviews, telephonic, televised, videoconference or videotaped statements, and providing written responses to interrogatories, admission requests or other discovery.</P>
              <P>(c)<E T="03">SIGAR policy.</E>(1) SIGAR was established by Section 1229 of the National Defense Authorization Act for Fiscal Year 2008, Public Law 110-181 (January 28, 2008), as a wartime or overseas contingency operation oversight agency of the United States Government's Executive Branch. SIGAR's Inspector General is appointed by the President of the United States. See Pub. L. 110-181, Section 1229(c). SIGAR performs oversight of Afghanistan reconstruction and security programs, operations and contracts to prevent and detect waste, fraud and abuse pursuant to Sections 1229 and 842 of Public Law 110-181. The records of an inspector general frequently contain sensitive law enforcement information that is protected from disclosure or obtained under guarantees of confidentiality.</P>
              <P>(2) In appropriate cases, the agency counsel shall notify the United States Department of Justice (DOJ) of the demand and coordinate with the DOJ to file any appropriate motions or other pleadings.</P>

              <P>(3) No current or former employee shall, in response to a demand, produce any SIGAR documents, provide testimony regarding any information relating to or based upon SIGAR documents, or disclose any information or produce materials acquired as part of the performance of that employee's official duties or official status, in a legal proceeding in which the United States is not a party, without the prior written authorization of the General Counsel.<E T="03">See United States ex rel. Touhy</E>v.<E T="03">Ragen,</E>340 U.S. 462 (1951); and 5 U.S.C. 301 (“The head of an Executive department or military department may prescribe regulations for the government of his department, the conduct of its employees, the distribution and performance of its business, and the custody, use, and preservation of its records, papers, and property. This section does not authorize withholding information from the public or limiting the availability of records to the public.”)<PRTPAGE P="15563"/>
              </P>
              <P>(d)<E T="03">Procedures for demand for testimony or production of documents.</E>
              </P>
              <P>(1) A written demand directed to SIGAR for the testimony of a SIGAR employee or for the production of documents shall be served in accordance with the requirements of the Federal Rules of Civil Procedure, Federal Rules of Criminal Procedure, or applicable state procedures, as appropriate. If the demand is served by the U.S. mails, it should be addressed to the General Counsel, Special Inspector General for Afghanistan Reconstruction, 2530 Crystal Drive, Arlington, VA 22202-3940. If the demand is served by overnight delivery service or courier, it should be directed to the General Counsel, Special Inspector General for Afghanistan Reconstruction, 2530 Crystal Drive, Arlington, VA 22202-3940. SIGAR's acceptance of a demand shall not constitute an admission or waiver of any objection with respect to the propriety of jurisdiction, service of process, venue, or any other defense in law or equity available under applicable law.</P>
              <P>(2) A subpoena or other demand for testimony directed to an employee or former employee shall be served in accordance with the Federal Rules of Civil or Criminal Procedure or applicable State procedure; and a copy of the subpoena or demand shall be delivered to the General Counsel.</P>
              <P>(3)(i)<E T="03">Touhy</E>Request. In court cases in which the United States or SIGAR is not a party, where the giving of testimony or the production of documents by SIGAR, or a current or former employee is desired, a verified statement (declaration under penalty of perjury) by the litigant or his counsel, setting forth the information with respect to which the testimony or production is desired (“<E T="03">Touhy</E>Request”), must be submitted in order to obtain a decision concerning whether such testimony or production will be authorized by SIGAR. The<E T="03">Touhy</E>Request should include: the title of the legal proceeding, the court or other forum, the requesting party's interest in the legal proceeding, a statement whether other evidence reasonably suited to the requester's needs is not otherwise available, and, if testimony is requested, the subject matter and intended use of the testimony, a statement whether document(s) could be provided in lieu of testimony to satisfy the request, and a statement that the requester will submit a check for costs of duplication at commercially reasonable rates to SIGAR if the request is granted. The purpose of these requirements is to assist the General Counsel in making a fair and informed decision under governing law regarding whether testimony or the production of document should be authorized and under what conditions, if any. Permission to testify or produce documents will be limited to the areas of proposed testimony described in the<E T="03">Touhy</E>Request.</P>

              <P>(ii) Agency counsel may consult or negotiate with an attorney for a party or the party, if not represented by an attorney, to refine or limit a demand so that compliance is less burdensome or to obtain information necessary to make the determination required by paragraph (e) of this section. Failure of the requester to cooperate in good faith to enable the General Counsel to make an informed determination under this subpart may serve as a basis for denying the<E T="03">Touhy</E>Request.</P>

              <P>(iii) A determination under this section to comply or not to comply with the<E T="03">Touhy</E>Request is without prejudice to the agency's assertion of privilege, lack of relevance, technical deficiency, or any other objection to the demand.</P>
              <P>(4)(i) Employees shall immediately refer all inquiries and demands made to SIGAR or its employees to the General Counsel.</P>
              <P>(ii) An employee who receives a demand shall forward the demand to the General Counsel, who will determine the agency's response to the demand under this section.</P>
              <P>(e)<E T="03">Factors to be considered by the General Counsel with respect to a Touhy Request.</E>(1) In deciding whether to authorize the release of official information or the testimony of SIGAR personnel concerning official information (hereafter referred to as the “disclosure”), the General Counsel shall consider the following factors:</P>
              <P>(i) Whether the demand is unduly burdensome to the agency or otherwise inappropriate under the applicable rules of discovery, evidence and procedure governing the litigation in which the demand arose, balanced against the need for the specific testimony or documents sought;</P>
              <P>(ii) Whether the demand is appropriate under the relevant substantive law of privilege and disclosure of Government information, or seeks information or documents protected from disclosure under the Freedom of Information Act, 5 U.S.C. 552(b), the Privacy Act, 5 U.S.C. 552a, or the Inspector General Act of 1978, as amended, 5 U.S.C. App.;</P>
              <P>(iii) Whether the demand would interfere with SIGAR's statutory mandate stated in the “National Defense Authorization Act for Fiscal Year 2008,” Pub. L. 110-181 (Jan. 28, 2008), Section 1229 (122 Stat. 378-85), as amended; Pub. L. 110-181, Section 842 (122 Stat. 234-36), 10 U.S.C. 2302 note; or the Inspector General Act of 1978, as amended, 5 U.S.C. App.;</P>
              <P>(iv) Whether the demand would be in the public interest;</P>
              <P>(v) The extent to which the time of employees for conducting official agency business would be compromised;</P>
              <P>(vi) Whether the request demonstrates that the information requested is relevant and material to the action pending, genuinely necessary to the proceeding, unavailable from other sources, and reasonable in scope; and</P>
              <P>(vii) Whether other similar requests are likely to have a deleterious cumulative effect on the expenditure of agency time and resources.</P>
              <P>(2) Among those demands and requests in response to which compliance will ordinarily not be authorized are those with respect to which any of the following factors exists:</P>
              <P>(i) The requested disclosure elicits information or documents protected by a statute, Executive Order or regulation, including but not limited to Section 7(b) of the Inspector General Act of 1978, as amended, 5 U.S.C. App. 3, section 7(b), or other prohibition from disclosure;</P>
              <P>(ii) The requested disclosure would interfere with ongoing enforcement proceedings, compromise constitutional rights, reveal the identity of an intelligence source, confidential informant or undercover agent, or disclose trade secrets or similar confidential commercial or financial information.</P>
              <P>(iii) The integrity of the administrative and deliberative processes of SIGAR would be jeopardized;</P>
              <P>(iv) The requested disclosure would not be appropriate under the rules of procedure governing the pending litigation or matter in which the demand arose;</P>
              <P>(v) The requested disclosure is not appropriate under the relevant substantive law concerning privilege; or</P>
              <P>(vi) The requested disclosure, except when production is in camera, would reveal information properly classified or other matters exempt from unrestricted disclosure.</P>
              <P>(3) All decisions granting or denying a<E T="03">Touhy</E>Request must be in writing and, if a denial, provide the grounds for the decision in summary form based on one or more of the factors listed above.</P>
              <P>(f)<E T="03">Requests for opinion or expert testimony.</E>(1) Pursuant to 5 CFR 2635.805, an employee shall not provide, with or without compensation, opinion or expert testimony in any<PRTPAGE P="15564"/>proceeding before a court or agency of the United States in which the United States is a party or has a direct and substantial interest, except on behalf of the United States or a party represented by the Department of Justice, without written approval of agency counsel.</P>
              <P>(2) Upon a showing by the requestor of exceptional need or unique circumstances, the General Counsel may, in writing, grant authorization for an employee, or former employee, to appear and testify.</P>
              <P>(3) Any expert or opinion testimony by a former employee of SIGAR shall be excepted from the restriction under 5 CFR 2635.805 where the testimony involves only general expertise gained while employed at SIGAR.</P>
              <P>(g)<E T="03">Procedures when agency counsel directs an employee not to testify or provide documents.</E>(1) If agency counsel determines that an employee or former employee should not comply with a subpoena or other request for testimony or the production of documents, agency counsel will so inform the employee and the requesting party who submitted the demand.</P>
              <P>(2) If, despite the determination of the agency counsel that testimony should not be given or documents not be produced, a court of competent jurisdiction or other tribunal orders the employee or former employee to testify and/or produce documents, the employee shall promptly notify the General Counsel of such Order.</P>
              <P>(i) If agency counsel determines that no further legal review of, appeal from, or challenge to, the Order will be sought, agency counsel shall promptly inform the employee or former employee of said determination.</P>

              <P>(ii) If SIGAR determines to challenge an Order directing testimony or the production of documents in litigation in which the United States is not a party, the employee should not comply with the Order. The employee should appear at the time and place as commanded in the order or subpoena. If legal counsel cannot appear on behalf of the employee, the employee should produce a copy of this section and respectfully inform the Court or other legal tribunal that he/she has been advised by the General Counsel not to provide the requested testimony or documents pursuant to the decision of the United States Supreme Court in<E T="03">United States ex rel. Touhy</E>v.<E T="03">Ragen,</E>340 U.S. 462 (1951), and this section. Agency counsel will coordinate with the DOJ to file such motions or other pleadings that may be deemed appropriate in the circumstances, such as, for example, a notice to remove the case from state court to Federal court, or a motion to quash or modify the subpoena, or a motion for a protective order.</P>
              <P>(h)<E T="03">Fees.</E>In the event that a Touhy Request is granted, SIGAR may charge reasonable fees to parties seeking official information or records. Such fees are calculated to reimburse the Government for the expense of providing such information or records, and may include the costs of time expended by SIGAR employees to process and respond to the request; attorney time for reviewing the request and any responsive records and for related legal work in connection with the request; and reasonable expenses generated by materials and equipment used to search for, produce, and copy the responsive information or records.</P>
            </SECTION>
          </PART>
        </REGTEXT>
        <SIG>
          <DATED>Dated: March 12, 2012.</DATED>
          <NAME>Steven J Trent,</NAME>
          <TITLE>Acting Inspector General, Special Inspector General for Afghanistan Reconstruction.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6306 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3710-L9-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Rural Utilities Service</SUBAGY>
        <CFR>7 CFR Part 1735</CFR>
        <RIN>RIN 0572-AC24</RIN>
        <SUBJECT>Expansion of 911 Access Loans and Loan Guarantees</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Rural Utilities Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Affirmation of interim rule as final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Rural Utilities Service (RUS) is adopting as a final rule, without change, an interim rule to implement the Expansion of 911 as authorized by Section 315 of the Rural Electrification Act of 1936 (RE Act) as provided for in Section 6107 of the Food, Conservation, and Energy Act of 2008 (2008 Farm Bill). The interim rule codified the Secretary's authority to make loans in five areas of eligibility to expand or improve 911 access and integrated emergency communications systems in rural areas for the Telecommunications Loan Program.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Effective on March 16, 2012, we are adopting as a final rule the interim rule published at 76 FR 56091-56094 on September 12, 2011.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>David Villano, Assistant Administrator, Telecommunications Program, USDA—Rural Utilities Service, 1400 Independence Avenue SW., STOP 1590, Room 5151-S, Washington, DC 20250-1590. Telephone number: (202) 720-9554, Facsimile: (202) 720-0810.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Background</HD>
        <HD SOURCE="HD2">A. Introduction</HD>
        <P>The Agency improves the quality of life in rural America by providing investment capital for deployment of rural telecommunications infrastructure. Financial assistance is provided to rural utilities; municipalities; commercial corporations; limited liability companies; public utility districts; Indian tribes; and cooperative, nonprofit, limited-dividend, or mutual associations. In order to achieve the goal of increasing economic opportunity in rural America, the Agency finances infrastructure that enables access to a seamless, nationwide telecommunications network. With access to the same advanced telecommunications networks as its urban counterparts, especially broadband networks designed to accommodate distance learning, telework, and telemedicine, rural America will eventually see improving educational opportunities, health care, economies, safety and security, and ultimately higher employment. The Agency shares the assessment of Congress, State and local officials, industry representatives, and rural residents that broadband service is a critical component to the future of rural America and modern emergency communications capabilities are critical to the safety and security of all Americans. The Agency is committed to ensuring that rural America will have access to affordable, reliable, telecommunications and broadband services and to provide a healthy, safe, and prosperous place to live and work.</P>
        <HD SOURCE="HD2">B. Regulatory History</HD>
        <P>Following the September 11, 2001, attacks on the United States, significant Congressional attention was placed on weaknesses in the nation's emergency communications capabilities. The ability of rural communities, carriers and emergency responders to keep up with changing communications technologies was and continues to be a concern of emergency response professionals. Interoperability; or the ability of emergency responders from various agencies and jurisdictions to communicate with each other is also a pressing national need.</P>

        <P>In 2002, the Congress gave the RUS statutory authority to “to expand or improve 911 access and integrated emergency communications systems in rural areas” in section 315 of the RE Act (6102 of the 2002 Farm Security and Rural Investment Act of 2002). No<PRTPAGE P="15565"/>regulations were ever proposed to implement that section.</P>
        <P>In 2008, the Congress re-authorized section 315 of the RE Act and added language to further define eligible loan purposes. It also clarified that projects could be funded from appropriations made to the RUS telecommunications program.</P>
        <P>In 2011, the President launched a major initiative to use wireless 4G technology to create a nation-wide interoperable emergency communications network. The plan contemplates using dual-use 4G wireless technologies in rural areas to address public safety and private sector communications needs.</P>

        <P>Rural areas face significant challenges in deploying emergency communications systems. The 911 Program Office housed within the National Transportation Safety Administration specifically noted that “(r)ural and tribal 911 centers face special challenges. They typically serve areas that are large geographically but less-densely populated than urban areas. Because it may take first responders longer to reach the scene of an emergency, call-takers in public safety answering points (PSAPs) serving rural areas may be required to stay on the phone longer with callers or provide more extensive emergency instruction to callers until help arrives. And in medical emergencies, hospitals are often farther away which results in extended transport times, making the ambulance unavailable for other calls in its response area—in areas that may have very limited coverage to begin with. The limited responder resources typical of rural areas can be more quickly overwhelmed in disasters or large-scale incidents.” The program office went on to observe that “supporting rural PSAPs is vitally important, particularly because it may take longer for help to arrive in rural areas, and the call-taker may make an even bigger difference in the outcome of an emergency situation.” (see<E T="03">http://www.911.gov/911-issues/challenges.html</E>).</P>
        <P>The sixty-minute period immediately following a traumatic injury, like an injury resulting from a car crash is known as the “golden hour.” The risks of death or permanent injury increase dramatically if medical attention is not given within that first hour. In rural America, distance and sparse population work against the quick discovery and treatment of injuries resulting from an individual or mass emergency. In rural areas the ability to reach a person in distress can be the difference between life and death or recovery and disability.</P>
        <P>Congress twice enacted section 315 to give the RUS flexible financial tools to help rural communities, service providers and governmental entities address their emergency communications needs. By giving clear loan authority to the agency, RUS would have the tools to leverage public and private resources to speed the rural deployment of a dual-use public safety/commercial wireless network, address homeland security communications needs along America's rural international borders; finance enhanced 911 capabilities for carriers and communities to precisely locate a rural wireless call to 911 or to finance next-gen 911 upgrades which would allow citizens to contact 911 via text message or send to emergency responders cell phone photos or short videos of a crime scene or accident location. E911 location accuracy requirements pose unique challenges for rural wireless carriers. The new authority would give the agency clear authority to finance wireless upgrades which relate to public safety and security, even if it does not finance the entire wireless communications systems.</P>
        <P>Without this authority, RUS would be very limited in its ability to make financing available to address specific rural emergency communications needs. Without this authority, the RUS telecommunications statute would generally prohibit the agency from financing municipal investments.</P>
        <P>As a loan program which must meet the rigorous financial and engineering feasibility requirements, the agency expects no impact on its subsidy rate.</P>
        <P>RUS has conducted extensive tribal consultations in 2010 and 2011 related to implementation of new authorities for substantially underserved trust areas. Through those consultations, the agency had discussions with tribal leaders on the entire portfolio of RUS programs. This authority could be useful in addressing some of the emergency communications needs raised by tribal leaders in some of those discussions. Tribal areas are among the regions of the United States with the least connectivity to 911 and other emergency communications systems.</P>
        <P>The regulation would simply codify the authority contained in section 315 of the RE Act.</P>
        <HD SOURCE="HD2">C. Rule Changes</HD>
        <P>The amendment to 7 CFR part 1735 implements Section 315 of the Rural Electrification Act of 1936 (RE Act) as provided in Section 6107 of the Food, Conservation, and Energy Act of 2008 by clarifying that the expansion of 911 access &amp; integrated interoperable emergency communications systems are eligible purposes of the RE Act.</P>
        <P>Section 6107 of the Food, Conservation, and Energy Act of 2008 added Section 315 of RE Act to clearly authorize the RUS to make loans for the following purposes:</P>
        <P>(1) 911 access;</P>
        <P>(2) Integrated interoperable emergency communications, including multiuse networks that provide commercial or transportation information services in addition to emergency communications services;</P>
        <P>(3) Homeland security communications;</P>
        <P>(4) Transportation safety communications; or</P>
        <P>(5) Location technologies used outside an urbanized area.</P>
        <P>The provision also clarified that the Agency could consider State or local 911 fees to be security for a loan under this section and that loans may be made in certain circumstances to an emergency communication equipment provider to accomplish the purposes of this section where a State or municipality may be prohibited from incurring debt.</P>
        <P>Comments on the interim rule were required to be received on or before November 14, 2011. We received one comment supporting the amendments to 7 CFR part 1735 by that date. Therefore, for the reasons given in the interim rule, we are adopting the interim rule as a final rule without change.</P>
        <P>This action also affirms information contained in the interim rule concerning Executive Order 12866 and the Regulatory Flexibility Act, Executive Order 12988, and the Paperwork Reduction Act. Further, for this action, the Office of Management and Budget has waived its review under Executive Order 12866.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 7 CFR Part 1735</HD>
          <P>Loan programs—communications, Reporting and recordkeeping requirements, Rural areas, Telephone.</P>
        </LSTSUB>
        <PART>
          <HD SOURCE="HED">PART 1735—GENERAL POLICIES, TYPES OF LOANS, LOAN REQUIREMENTS—TELECOMMUNICATIONS PROGRAM</HD>
          <P>Accordingly, we are adopting as a final rule, without change, the interim rule that amended  7 CFR part 1735 and that was published at 76 FR 56091 on September 12, 2011.</P>
          <SIG>
            <DATED>Dated: February 24, 2012.</DATED>
            <NAME>James R. Newby,</NAME>
            <TITLE>Acting Administrator,  Rural Utilities Service.</TITLE>
          </SIG>
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6420 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <PRTPAGE P="15566"/>
        <AGENCY TYPE="N">FEDERAL HOUSING FINANCE AGENCY</AGENCY>
        <CFR>12 CFR Part 1228</CFR>
        <RIN>RIN 2590-AA41</RIN>
        <SUBJECT>Private Transfer Fees</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Housing Finance Agency.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Federal Housing Finance Agency (FHFA) is issuing a final rule to restrict the regulated entities—the Federal National Mortgage Association (Fannie Mae), the Federal Home Loan Mortgage Corporation (Freddie Mac) (collectively, the Enterprises), and the Federal Home Loan Banks (Banks)—from dealing in mortgages on properties encumbered by certain types of private transfer fee covenants and in certain related securities. This final rule is intended to protect the regulated entities from exposure to mortgages with certain features that may impair their value and increase risk to the financial safety and soundness of the entities. FHFA intends that the regulated entities develop reasonable means and appropriate methods to implement the rule in consultation with FHFA.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This final rule is effective July 16, 2012.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Mark D. Laponsky, Deputy General Counsel, (202) 649-3054 or Christopher T. Curtis, Senior Deputy General Counsel, (202) 649-3051 (not toll-free numbers), Federal Housing Finance Agency, Eighth Floor, 400 Seventh Street SW., Washington, DC 20024. The telephone number for the Telecommunications Device for the Hearing Impaired is (800) 877-8339.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Background</HD>
        <HD SOURCE="HD2">Establishment of FHFA</HD>
        <P>FHFA is an independent agency of the federal government and was established by the Housing and Economic Recovery Act of 2008 (HERA), Public Law 110-289, 122 Stat. 2654, to regulate and oversee the regulated entities.<SU>1</SU>

          <FTREF/>HERA amended the Federal Housing Enterprises Financial Safety and Soundness Act of 1992 (12 U.S.C. 4501<E T="03">et seq.</E>) (“Safety and Soundness Act”) and the Federal Home Loan Bank Act (12 U.S.C. 1421 through 1449) (Bank Act) to enhance the authorities and responsibilities of the new agency.</P>
        <FTNT>
          <P>
            <SU>1</SU>
            <E T="03">See</E>Division A, titled the Federal Housing Finance Regulatory Reform Act of 2008, Title I, section 1101<E T="03">et seq.</E>of HERA.</P>
        </FTNT>
        <P>FHFA's regulatory mission is to ensure, among other things, that each of the regulated entities “operates in a safe and sound manner” and that their “operations and activities * * * foster liquid, efficient, competitive, and resilient national housing finance markets.” (12 U.S.C. 4513(a)(1)(B)). HERA authorizes FHFA to “issue any regulations * * * necessary to carry out” that mission and “to ensure that the purposes of this chapter and the authorizing statutes are accomplished.” (12 U.S.C. 4526(a)). This same grant of rulemaking authority also enables FHFA to draw on its cease-and-desist powers (12 U.S.C. 4631) to prohibit by general rule the same types of unsafe and unsound practices it would be empowered to address through case-by-case adjudications.<SU>2</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>2</SU>
            <E T="03">See Lincoln Savings &amp; Loan Ass'n</E>v.<E T="03">Federal Home Loan Bank Board,</E>856 F.2d 1558, 1562-63 (D.C. Cir. 1988) (upholding FHLBB regulation prohibiting certain unsafe and unsound practices based on cease-and-desist powers);<E T="03">Independent Bankers Ass'n of America</E>v.<E T="03">Heimann,</E>613 F.2d 1164, 1168-69 (D.C. Cir. 1980) (upholding OCC regulation prohibiting certain unsafe and unsound practices based on cease-and-desist powers). As further discussed below, FHFA has found that it constitutes an unsafe and unsound practice to participate in any market for mortgages on property encumbered by certain private transfer fees. To allow full public participation and for the sake of efficiency, FHFA has elected to require the regulated entities to cease and desist from these practices by issuing a rule of general applicability rather than by instituting individual proceedings.</P>
        </FTNT>
        <HD SOURCE="HD2">Private Transfer Fee Covenants and FHFA's Proposed Guidance</HD>
        <P>On August 16, 2010, FHFA published for comment a notice of proposed guidance that would have advised the Enterprises and the Banks not to purchase, or accept as collateral for advances, mortgages on property subject to any private transfer fee covenants. (75 FR 49932).</P>
        <P>As described in the proposed guidance, private transfer fee covenants may be attached to real property by the owner or another private party—frequently, the property developer—and provide for a transfer fee to be paid to an identified third party—such as the developer or its trustee—upon each resale of the property. The fee typically is stated as a fixed amount or as a percentage, such as one percent of the property's sales price, and often exists for a period of 99 years.</P>
        <P>Many states have enacted legislation to address private transfer fee covenants. State legislative solutions are diverse and include permitting the covenants subject to recordation and disclosure requirements<SU>3</SU>
          <FTREF/>and prohibiting them when fees are paid to private third parties, with exceptions for homeowners' associations, condominiums, cooperatives, and similar organizations that use the fees to directly benefit the properties encumbered by the covenants.<SU>4</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>3</SU>
            <E T="03">E.g.,</E>Cal. Civ. Code §§ 1098 and 1098.5 (2010).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>4</SU>
            <E T="03">E.g.,</E>Del. Code Ann. Tit. 25, § 319 (2010); Minn. Stat. §§ 513.73 to 513.76 (2010); N.C. Gen. Stat. §§ 39A-1 to 39A-3 (2010).</P>
        </FTNT>
        <P>In the proposed guidance and the proposed rule that followed, FHFA expressed concerns that private transfer fees may be used to fund purely private continuous streams of income for select market participants either directly or through securitized investment vehicles, may not benefit homeowners or the properties involved, and, therefore, could impair the safety and soundness of the regulated entities that invest in or purchase mortgages secured by such properties as collateral. Another concern expressed about private transfer fees is the adequacy of disclosure of these covenants which, in turn, may impede the marketability and valuation of the encumbered property. Consumers may also be unaware that a fee applies even if the resale price of their home drops below the original purchase price.</P>
        <HD SOURCE="HD2">History of the Rule</HD>

        <P>FHFA's proposed rule grew out of its consideration of over 4,200 comments received on the proposed guidance. Commenters included the Community Associations Institute (CAI), American Land Title Association (ALTA), National Association of Realtors (NAR), Freehold Capital Partners (Freehold), American College of Real Estate Lawyers, Institute of Real Estate Management, Coalition to Stop Wall Street Home Resale Fees, Sierra Club numerous state and regional real estate agent associations, real estate companies, numerous homeowners', cooperative, and condominium associations and individuals living within such associations, community associations and other nonprofit organizations, conservation funds and land trusts and foundations, housing and conservation boards, state housing and community development agencies, state natural resources agencies, developers, builders, appraisers, accountants, title companies, several Federal Home Loan Banks, members of the U.S. House of Representatives, State Governors, law firms (writing on their own behalf and on behalf of their clients), and other individuals and organizations who wrote to express a wide range of views on private transfer fee covenants. After receiving and reviewing the comments, FHFA<PRTPAGE P="15567"/>determined to address the subject through regulation rather than through guidance.</P>
        <P>On February 8, 2011, FHFA published a Notice of Proposed Rulemaking (76 FR 6702) inviting comments on a proposal that incorporated a number of changes to the substance of the former proposed guidance. The proposed rule reflected a narrower focus than the guidance and limited the private transfer fees to which it would be applicable. Among other things, the proposed rule sought comment on an approach to refine the definition of transfer fees eligible for regulated entity investment to include those that provided a direct benefit to the property of the homeowner through maintenance or enhancement of common areas or the structures of multifamily units or the property of the homeowner through support, for instance, of homeowners' or community associations. FHFA also proposed to make the rule prospective in effect, and apply it only to private transfer fee covenants created after the publication date of the proposed rule (February 8, 2011). FHFA proposed further to allow an implementation period of 120 days for the regulated entities within which they might use reasonable means to achieve compliance. FHFA received over one thousand comments on the proposed rule, discussed in more detail below.</P>
        <P>In developing the final rule, FHFA reviewed the comments received on the proposed rule as well as, again, the comments received on the previously proposed guidance. In addition to making the intuitive objection that it is wrong to impose a fee on homeowners for exercising the right to sell their own homes, commenters criticized private transfer fees for many reasons in both rounds of comment:</P>
        <P>(1) That the impact of transfer fees on property values is uncertain and potentially adverse because of uncertainty over how often the property will be sold during the duration of the covenant; and that, for that reason as well as because property values go up and down, and therefore the fee as well (in the majority of cases in which it is a percentage of property value), the fees paid are likely to not be aligned with the value received in return, if any.</P>
        <P>(2) That there is no price transparency because buyers are not offered a choice between a property encumbered by the transfer fee covenant and the same property at a different price without the covenant, or between comparable properties with and without the covenant.</P>
        <P>(3) That in many cases the transfer fee is not assessed on the first buyer, making the covenant less likely to be reflected in the initial sale price but more likely to be a surprise upon attempted resale. Similarly, that it is difficult for a buyer to predict the effect of the covenant on the property's value upon resale to subsequent buyers.</P>
        <P>(4) That private transfer fees exploit the lack of transparency of complex real estate transactions; further, that they are not normally discoverable until well after the sale contract is executed, when a title search is performed prior to closing, with unpredictable effects on whether the sale will close or whether the price will be renegotiated.</P>
        <P>(5) That private transfer fee covenants present questions of legal enforceability, especially if they are not associated with provision of a direct benefit to the burdened property.</P>
        <P>These criticisms contribute to FHFA's concerns about the reliability with which properties subject to such encumbrances may be valued, posing safety and soundness risk to FHFA's regulated entities. Many of these concerns are lessened when the fees provide a direct benefit to the burdened properties, and, as described in more detail below, the final rule follows the approach of the proposed rule in excepting defined classes of fee covenants that are associated with a direct benefit.</P>
        <P>This rule does not prohibit any private transfer fees. Rather, pursuant to FHFA's safety and soundness authorities under the Safety and Soundness Act and the Bank Act, as augmented with respect to the Enterprises by its additional plenary powers as Conservator, it prospectively instructs the regulated entities that participating in any market for mortgages on property encumbered by certain private transfer fees is an unsafe and unsound practice in which they shall not engage. The rule also identifies the types of private transfer fee covenants that will not disqualify a mortgage for investment.</P>
        <HD SOURCE="HD1">II. Public Comments on the Proposed Rule</HD>
        <P>The public comment period on the proposed rule closed on April 11, 2011. FHFA received over 1,000 comments on all aspects of the proposed rule. Many of the organizations and constituencies that commented on the proposed guidance also commented on the proposed rule. However, the comments differed from those received on the proposed guidance. A very small minority of commenters preferred the more restrictive approach in the proposed guidance. The majority of comments supported the proposed rule because, unlike the guidance, it would not apply to existing transfer fees and because those fees that directly benefit the property on which they are assessed would not disqualify a mortgage for regulated entity investment.</P>
        <P>Most comments centered on refinements to the proposed rule to assure it would not inadvertently disqualify certain fee arrangements through omission from the definitions in the proposed rule; on changes to expand parties and activities covered by the “direct benefit” test; and on objections to the proposed rule either because it deviated from the original proposal to disqualify mortgages on property encumbered by any private transfer fee covenant or because it continued to make ineligible for investment mortgages encumbered by fees affecting certain interest groups or business entities.</P>
        <P>The comments can be generally characterized as falling into four categories: (1) Comments endorsing the proposed rule; (2) comments generally supporting the proposal, but suggesting specific changes; (3) comments opposed to core elements of the proposed rule; and, (4) comments asserting that the rule lacks prerequisites to proper promulgation. FHFA has accepted suggestions from a number of commenters and made adjustments to the rule to address these comments.</P>
        <HD SOURCE="HD1">III. Discussion of Public Comments</HD>
        <HD SOURCE="HD2">Supporting the Rule as Proposed</HD>
        <P>Commenters such as ALTA, the Coalition to Stop Wall Street Home Resale Fees, and the Conference of State Bank Supervisors (CSBS) endorsed the proposed rule's ban on investing in mortgages encumbered with private transfer fee covenants and FHFA's adoption of a “direct benefit” test for permissible covenants. ALTA did note that how the regulated entities would enforce the rule would be of interest, as the title search and examination process would occur late in the home-buying process and that transfer fees often are difficult to detect, if not recorded.</P>

        <P>With respect to implementation, ALTA's concern was echoed by other commenters, including the Federal Home Loan Banks as regulated entities. FHFA intends that the regulated entities develop reasonable means for implementation of the regulation in consultation with FHFA. Possible methods include incorporating appropriate restrictions in the seller-servicer guides of the Enterprises; using representations and warranties; or, in the case of the Federal Home Loan Banks, perhaps requiring mortgages to<PRTPAGE P="15568"/>conform to Enterprise purchase standards. The regulated entities have a great deal of experience in developing methods of segregating mortgages in which investment is permissible and those in which investment is not.</P>
        <P>The CSBS supported the proposed rule as establishing a “regulatory floor” for the regulated entities. CSBS stated that this “floor” will ensure that the states can continue to enact practical regulations affecting private transfer fees; and that state level supervision of these fees ensures that the regulators are accessible to those they regulate, understand the applicable state laws and are in tune with the local economy. The Joint Editorial Board for Uniform Real Property Acts (JEBURPA) and CSBS were among the commenters urging FHFA to respect state law and avoid preemption of state laws regulating these fees. FHFA believes that § 1228.4 of the final rule adequately addresses this issue.</P>
        <HD SOURCE="HD2">Support With Modifications</HD>
        <P>Many commenters expressed support for the proposed rule, but requested modifications primarily to definitions that would clarify its application.</P>
        <HD SOURCE="HD2">One Thousand Yards</HD>
        <P>Hyatt &amp; Stubblefield (H&amp;S) and Sproul Trost (Sproul), two real estate law firms, along with CAI, the National Association of Homebuilders (NAHB), the Mortgage Bankers' Association (MBA), JEBURPA, and others criticized the proposal's “adjacent or contiguous property” requirement as ambiguous when considered with other definitions, unworkable, and too restrictive, particularly the requirement that property be located within 1,000 yards of the burdened community in order to be considered “adjacent or contiguous.” As described below, FHFA has decided to delete the 1,000-yard limitation. The rule does address the issue of properties that may not be adjacent or contiguous, but with a test of direct benefit rather than location.</P>
        <HD SOURCE="HD2">Breadth of “Direct Benefit,” “Private Transfer Fees,” and Exceptions</HD>
        <P>A significant number of commenters, including NAHB, echoed the CAI comment to broaden the definition of “direct benefit” to embrace all duties and responsibilities that residents ordinarily expect, or choose to require, community or homeowner associations to fulfill. FHFA intends to encompass routine functions of property management and ordinary obligations of governing associations. However, to automatically include any activity that such associations may engage in as a “direct benefit” may not meet the prudential need that the financial burden of such fees be balanced by value actually added to the encumbered property.</P>
        <P>Similarly, JEBURPA, noting that the proposed definition of “private transfer fee” contains only four exclusions (fees imposed by court decree; fees payable to the Federal government or a State or local government; fees arising out of a mechanic's lien; and fees arising from an option to purchase land), suggested that the definition should be expanded to exclude loan assumption fees; loan prepayment fees; and deferred purchase price payments or appreciation sharing contracts. Other comments also sought various expansions to the definition, and FHFA has reviewed these comments and state laws with diverse exceptions. CAI recommended using the term “community transfer fee covenant” rather than “excepted transfer fee covenant.” CAI stated that this would more clearly define the fees that FHFA seeks to disqualify by specifically outlining fees FHFA does not seek to restrict.</P>
        <P>Patton Boggs, a law firm writing on behalf of its client, Associations, Inc. (Associa), explained that Associa's members support property owners by providing various services, including closing services, to homeowners' associations. While Associa believed these services fall outside the scope of the proposed rule, Patton Boggs suggested adding a fifth exclusion to the private transfer fee definition to codify its understanding. The H&amp;S law firm stated its general support for the proposed rule as an improvement over the proposed guidance, but also objected to the definition of “direct benefit.” H&amp;S argued alternatively that the definition should be expanded to include a number of additional qualifying uses or deleted in favor of revising the definition of “excepted transfer fee covenant” to be more inclusive.</P>
        <P>FHFA has made changes in the proposed rule, described below, in response to these comments.</P>
        <HD SOURCE="HD2">Internal Revenue Code and Sections 501(c)(3) and 501(c)(4) Charitable Status</HD>
        <P>Among others, the Natural Resources Defense Council (NRDC), Coalition to Save Community Benefits (CSCB), the Sierra Club, H&amp;S, Sproul, Endangered Habitats League (EHL), and Shute, Mihaly &amp; Weinberger, LLP, a law firm writing on behalf of several environmental groups, objected to the requirement for covenants to directly and exclusively benefit encumbered property, and the reference to usage fee charges in the event of general public use, as well as the limited definition of “covered association.” The principal theme common to these objections is an assertion that the definitions taken together, and particularly in view of requirements for exclusivity of benefits and possible charges for public use, are too restrictive to benefit charitable organizations. These commenters urge a broader exception for not-for-profit organizations that allows their covenants special treatment, asserting that FHFA's proposal is inconsistent with charitable purposes, which require non-exclusivity of benefits in order to meet the public purposes requirement for tax exempt status under sections 501(c)(3) and 501(c)(4) of the Internal Revenue Code (IRC).</P>
        <P>The California Building Industry Association (CBIA) proposed a revision that embraced the concept of a “community benefits covenant” approach to accommodate nonprofit organizations that administer transfer fees. According to CBIA, this approach would allow non-profits to meet the Internal Revenue Service requirements for nonprofit organizations to engage in charitable and public purposes.</P>
        <P>In response to the comments questioning the consistency between the direct benefit requirement and requirements for certain types of tax-exempt status under the IRC, FHFA has made certain changes to the section of the rule on direct benefit that may address some concerns expressed in the comments. FHFA takes no position, however, with respect to potential tax consequences for a nonprofit organization that may result from the administration of transfer fees or that otherwise may be associated with the encumbrance of a property with a private transfer fee covenant.</P>
        <HD SOURCE="HD2">Recording, Disclosures, and Implementation</HD>

        <P>Recording and pre-purchase and pre-foreclosure disclosure requirements were among significant suggestions offered by many commenters including MBA, EHL, CSCB, and the Consumer Mortgage Coalition. Commenters recommended recording and disclosure of private transfer fee covenants as additional measures to protect homebuyers and consumers; as ameliorating implementation difficulties for the regulated entities; and a complete alternative to the rule's method of identifying fees that disqualify mortgages for investment. FHFA views recording and disclosure as valuable adjuncts to consumer and lender awareness of fees and perhaps a “best practice” that might be considered<PRTPAGE P="15569"/>by appropriate state or federal authorities. However, adopting such requirements for real estate transactions potentially injects FHFA into issues of state policy and matters of consumer protection. FHFA's core role is as prudential and mission supervisor of its regulated entities, not as a general regulator of real estate markets and practices. The provisions of the rule focus on those aspects of private transfer fee practice that may affect the value of property underlying mortgages held by the regulated entities. FHFA recognizes that future action might be required to revise the rule. FHFA will assess the effectiveness of this rule, deferring consideration of specific transaction requirements to allow state or other federal policymakers to address these issues in the first instance.</P>
        <P>With respect to implementation, although recording and disclosure may make it easier for the regulated entities, FHFA does not intend to establish by rule detailed instructions for how regulated entities will implement the rule. However, all regulated entities have experience in establishing controls to segregate mortgages in which they can invest from those which are disqualified. As stated by FHFA when publishing the proposed rule, acceptable compliance with the final rule may be achieved through a Federal Home Loan Bank's quality control review process or through the Banks' collateral review process, coupled with appropriate direction to their members, as well as robust representations, warranties, or certifications. The Enterprises would be expected to use similar compliance tools such as appropriate provisions in seller-servicer guides, representations and warranties, and quality-control processes. FHFA does not expect that the Federal Home Loan Banks must use such compliance tools with respect to Enterprise securities, because Enterprise securities issued prospectively should comply with the provisions of the final rule. FHFA will work with the regulated entities to develop appropriate methods to implement the rule.</P>
        <P>The suggestion offered by some commenters that recording and disclosure are an alternative to the rule's description of covenants that qualify for investment is misplaced. The rule is not directed at controlling private transfer fee covenants. It is instead directed at limiting the risk to regulated entities when investing in property with values that may be compromised by such covenants. Recording and disclosure requirements do not distinguish among levels of risk, but only make identification of an existing covenant easier. Those details, as noted above, are matters best left to state law or other appropriate federal consumer-focused regulation.</P>
        <HD SOURCE="HD2">Prospective Application</HD>
        <P>A variety of commenters, including Federal Home Loan Banks, law firms, and non-profit organizations, expressed concerns over the date on which the rule would apply. The proposed rule provided that regulated entity compliance was not required until after publication of the final rule. To comply with the rule, regulated entities cannot trade in disqualified “mortgages on properties encumbered by private transfer fee covenants created on or after” February 8, 2011. The obligation on the regulated entities is unequivocally prospective—“The regulated entities shall comply with this part not later than 120 days” after publication of the final rule. The date—February 8, 2011—identifies the private transfer fee covenants to which the regulated entities are to apply the rule's qualification and disqualification tests.</P>
        <P>The structure of the proposed rule is clear that the language “created on or after” refers to the date on which the covenant that encumbers the land was created. Covenants that encumbered land before February 8, 2011 do not disqualify mortgages. It is FHFA's intention that the date of creation is the date on which the covenant became legally enforceable with respect to the specific encumbered property that is the subject of a mortgage, whether under state law that is the date of recording or some other date.</P>
        <P>The only obligations that the proposed rule would impose are forward looking, and they apply only to the regulated entities. The rule regulates neither private transfer fee covenants nor market participants who create or use them.</P>
        <P>
          <E T="03">National Cable &amp; Telecommunications Association</E>v.<E T="03">Federal Communications Commission,</E>567 F.3d 659 (D.C. Cir. 2009), is instructive with respect to applying retroactivity principles to this rule. In that case, the Federal Communications Commission (FCC) promulgated a rule that prohibited the enforcement of pre-existing exclusivity contracts between cable operators and multi-unit developments, like apartment buildings. The court upheld the rule and determined that it was not an impermissibly retroactive regulation.<E T="03">Id.</E>at 671-72.</P>
        <P>In<E T="03">National Cable,</E>the petitioners asserted that applying the rule to existing contracts violated the presumption against retroactivity contained in the Administrative Procedure Act's “future effect” requirement and was impermissible because of the rule's so-called “secondary retroactivity”; that is, secondary effects of the rule that the FCC failed to consider. The court first emphasized that “[w]e have thus repeatedly made clear that an agency order that only `upsets expectations based on prior law is not retroactive,'<E T="03">Mobile Relay Associates</E>v.<E T="03">FCC,</E>457 F.3d [1, 11 (D.C. Cir. 2006)].” 567 F.3d at 670.</P>

        <P>Even if the proposed rule affects the value of private transfer fee covenants entered between February 8, 2011 and the date of the regulation, it has “not rendered [those covenants] illegal or otherwise sanctionable. ‘It is often the case that a business will undertake a certain course of conduct based on the current law, and will then find its expectations frustrated when the law changes.'<E T="03">Chemical Waste Management, Inc.</E>v.<E T="03">U.S. Environmental Protection Agency</E>(EPA), 869 F.2d 1526, 1536 (D.C. Cir. 1989). Such expectations, however legitimate, cannot furnish a sufficient basis for identifying impermissibly retroactive rules.” 567 F.3d at 670.<E T="03">See also, Landgraf</E>v.<E T="03">USI Film Products,</E>511 U.S. 244, 269 (1994);<E T="03">Arkema, Inc.</E>v.<E T="03">EPA,</E>618 F.3d 1, 7 (D.C. Cir. 2010) (“A rule operates retroactively if it takes away or impairs vested rights.”). A retroactive rule “alter[s] the<E T="03">past</E>legal consequences of past actions.”<E T="03">Bowen</E>v.<E T="03">Georgetown University Hospital,</E>488 U.S. 204, 219 (Scalia, J., concurring) (emphasis in original). If a vested right is not impaired, the rule is not retroactive.<E T="03">See Arkema,</E>518 F.3d at 7.</P>
        <P>This rule might frustrate an assumption that an encumbered mortgage would be eligible for purchase by a regulated entity, but it does not extinguish any third-party right to have a regulated entity trade in that mortgage, because there is no such right. At any time in the past, regulated entities could refuse to make such purchases; no one possessed a right to require them to be purchased and no regulated entity had any obligation to purchase, invest or otherwise trade in them. Since the rule does not impair a vested right, the rule is not retroactive.</P>

        <P>“Secondary retroactivity” exists where a rule “affects a regulated entity's investment made in reliance on the regulatory status quo before the rule's promulgation.”<E T="03">Mobile Relay,</E>457 F.3d at 11. It invalidates a rule only if the rule is arbitrary or capricious.<E T="03">See Bowen,</E>488 U.S. at 219 (Scalia, J. concurring);<E T="03">Mobile Relay,</E>457 F.3d at 11. An assessment and balancing of<PRTPAGE P="15570"/>benefits and burdens is required if a rule creates such secondary effects.<E T="03">National Cable,</E>567 F.3d at 671-72.</P>
        <P>Through this rule, FHFA is protecting regulated entities from investments with certain features that impair their value and pose unacceptable levels of risk to the financial safety and soundness of the entities. The regulation is supported by the proliferating use of private transfer fees for purposes unrelated to the encumbered property and proposals to securitize streams of income from them that will never be returned to the property or property owner. By strengthening the safety and soundness of the regulated entities, the rule furthers the central mission of FHFA. It is abundantly clear that FHFA has considered secondary effects. Despite the fact that the rule does not prohibit covenants, it contains a grandfathering provision to allow the regulated entities to trade in mortgages encumbered by otherwise disqualifying covenants if the covenants were created before a date certain. The date certain of February 8, 2011, is the date on which the rule was proposed. It was chosen as a rational date at which markets and market participants could adjust their behavior in case a rule unfavorable to them was eventually adopted and as a means to avoid market disruption that would occur if developers and others attempted to anticipate the forthcoming rule by placing disqualifying covenants on large numbers of previously unencumbered properties during the time that a final rule was being considered. This is an acceptable practice among regulatory agencies.</P>
        <P>In<E T="03">National Cable</E>the court upheld the rule despite the fact that “by significantly altering the bargained-for benefits of now unenforceable exclusivity agreements, the Commission has undoubtedly created the kinds of secondary retroactive effects that require agency attention and balancing” because the FCC in fact conducted the balancing analysis and concluded that “banning enforcement of existing contracts was essential.” 567 F.3d at 671. Like FHFA, the FCC concluded that the public interest required it to “prevent the harms from existing contracts `to continue for years,' or `to continue indefinitely in the cases of exclusivity clauses that last in perpetuity.”<E T="03">Id.</E>The court noted that, as FHFA has done here, the FCC considered legitimate expectations and felt they were relatively undisturbed because states and the FCC had been scrutinizing the prohibited arrangements for some time.<E T="03">Id.</E>
        </P>
        <P>FHFA has fully considered the benefits and burdens and primary and secondary effects of the rule. FHFA concludes that this rule is not impermissibly retroactive and that this conclusion is supported by applicable precedent.</P>
        <HD SOURCE="HD2">Opposition to Core Elements of the Rule</HD>
        <P>Some comments opposed elements so fundamental to the proposed rule that changing or eliminating them as requested would vitiate the purpose of the regulation itself. FHFA considered all comments and assessed whether to issue this rule as a regulation, guidance, or not at all. FHFA determined that the concerns, risks, and issues leading it to propose guidance in the first place have not abated and the comments to the proposed rule reinforce that the housing finance system and its participants are better served by the certainty of a rule on this subject. Consequently, FHFA has not accepted suggestions that would serve to make the rule ineffective and undermine its core principles.</P>
        <P>One of the principal objectors to the fundamental underpinnings of the proposed rule is Freehold, joined by law firms, developers, and some builders. These commenters claim that private, profit-motivated entities can use private transfer fees (characterized by them as “capital recovery fees,” although the fees are not tied to any particular capital investment) to provide financial benefits to homeowners and communities by distributing development and infrastructure costs to “future” homeowners, rather than embedding all of these costs in the sales price to the initial homebuyer. They generally liken these benefits to those provided by homeowner associations and similar entities that provide ongoing support to encumbered properties. This view is far from universal, as many builders and the NAHB oppose private transfer fee covenants of this sort.</P>
        <P>Freehold and other proponents of private transfer fees contend that creating a right for the developer to receive a future stream of transfer fee payments from successive homebuyers allows the developer to recover investment costs more quickly, enabling more capital investment in new development. This is to be accomplished by securitizing that revenue stream, and selling the security to investors who have no connection to the encumbered property. The developer receives the sale proceeds of the security irrespective of the subsequent market value of the developed property. If the stream of income is not securitized and sold to investors, or otherwise assigned, the developer receives it over the life of the covenant, usually 99 years. Advocates for this model argue that the fees allow developers to pursue or complete projects not otherwise viable due to a housing market downturn. As new developments are completed, they assert, jobs are created and the economy in general benefits. Additionally, proponents claim that by spreading costs into the future, each homebuyer benefits from a price that is lower than if the full costs of the development were recovered from the initial purchaser. However, another commenter, the Center for Regulatory Effectiveness (CRE), challenged Freehold's analysis, finding that private transfer fees paid to developers or to unrelated third parties (as opposed to those directly benefiting owners of burdened property) produce negligible benefits for homeowners, while imposing additional costs and burdens, such as increased difficulty of selling a home encumbered by a private transfer fee. FHFA has carefully considered both analyses and finds CRE's comments more persuasive.</P>

        <P>Freehold argues that the purpose of the private transfer fee revenue stream is to fund infrastructure investments. However, FHFA has determined that these arrangements do not require that the revenue stream be spent on infrastructure improvements. To the contrary, Freehold's marketing literature to developers, available on its Web site and cited in CRE's comment on the proposed rule, describes private transfer fees as a means to “extract more value from your real estate projects.”<E T="03">See  http://freeholdcapitalpartners.com/forms/freehold_brochure.pdf.</E>That “value” is not used to fund any part of the development, precisely because it is a future revenue stream and not cash in hand to the developer. To FHFA's knowledge, no securities based on these revenue streams have ever been sold, so the asserted benefits of this arrangement to developers as a means of funding projects are speculative.</P>

        <P>Even as a matter of principle, the arrangement that Freehold markets to developers cannot work to the benefit of both developers and homebuyers as Freehold argues. In a fully informed, freely functioning marketplace, the initial sale price of a property subject to the covenants should be reduced by the present value of the expected future stream of transfer fee payments with which the property is burdened. The price of the security that the developer sells should also reflect the present value of the expected future stream of transfer fee payments, so there is no net creation of value to the developer. In fact, because the financial intermediaries who would manage the transaction would extract a fee, and<PRTPAGE P="15571"/>because Freehold also would extract a fee, the amount received by the developer would actually be<E T="03">less</E>than the amount the developer loses because of the reduction in the sale price of the burdened properties. The developer gains a benefit only if the home buyers<E T="03">do not</E>reduce the price they are willing to pay by the present value of the future transfer fee burden or even close to it.<SU>5</SU>
          <FTREF/>The arrangement does not work to the benefit of both developers and homebuyers.</P>
        <FTNT>
          <P>

            <SU>5</SU>Why might developers and Freehold expect this to be the case? There are at least two possible explanations. First, behavioral economists argue that consumers discount future negative outcomes at excessively high rates, a phenomenon that they call “hyperbolic discounting.”<E T="03">See</E>Bar-Gill,<E T="03">Seduction by Plastic,</E>98 Nw. U. L. Rev. 1373, 1396-99 (2004); Heidhues &amp; Koszegi, “Exploiting Naïvete About Self-Control in the Credit Market” (Institute for Behavioral Economics, Sept. 2009). Second, a substantial number of commenters argue that transfer fees are inadequately disclosed, both as a matter of clarity and as a matter of timing in the real estate purchase transaction, and urge FHFA to establish disclosure standards. This phenomenon could be reinforced by the fact that Freehold's fees—as well as most of those supporting environmental and conservation projects, discussed below—are not charged to the initial buyer of the burdened property, but only to subsequent buyers. That is, the arrangement is structured to ensure that the fees are paid only by parties who are remote from the creation of the covenants and least likely to be aware of them or appreciative of their impact. As explained above, FHFA does not believe that it is its role to fashion or to mandate appropriate disclosures, nor does FHFA take a position on behavioral economics or any of its theories. It is enough for FHFA to recognize that the effect of transfer fee covenants on property values is uncertain, and that the Freehold arrangement extracts value from property that is not returned to it.</P>
        </FTNT>
        <P>FHFA has carefully reviewed and considered Freehold's analysis and has concluded that Freehold's assertion that private transfer fees are economically beneficial to homebuyers and to the economy is based on assumptions that are not verifiable and lack empirical data. In particular, Freehold's present value assertions rest on assumptions about cash flow streams and appropriate discount rates that are unidentified, unexplained, and lack validation.</P>
        <P>FHFA does not agree that private transfer fees appropriately and equitably spread initial developer costs across future homeowners. Development costs ostensibly recovered by these fees do not have a value that extends to the typical 99-year life of the covenant. Initial improvements by a developer depreciate in value over a much shorter period of time. In a traditional development, the initial home price captures the value of the developer's investment. Resale prices capture remaining value of the improvement. This method of capital recovery is more equitable and less disruptive to home resale markets than charging future generations of homeowners for capital investments and residual values of the improvements funded by those investments. Instead, FHFA finds that the core purpose behind the Freehold model is reflected in Freehold's own marketing material heralding the returns to developers and remote investors from generations-long extraction of value from land at the expense of successive homebuyers. Nothing in the Freehold model demonstrates that any benefit is ever returned to the property burdened by private transfer fee covenants in exchange for repeated and potentially escalating charges.</P>
        <P>A variety of non-profit environmental groups asserted that private transfer fee covenants can be used to promote environmental protections and resource conservation, which they claim inures to the benefit of encumbered property and to society at large. The benefits are argued to transcend the property and property owners and therefore, the commenters assert, the covenants have indirect and non-exclusive benefits that should not cause a mortgage to be ineligible for investment. Commenters opposed to such use of private transfer fees argue that developers are willing to impose private transfer fee covenants on properties in settlement of environmental and similar litigation, because the resulting fees are not paid by the developer but shifted to the homeowners; a phenomenon exacerbated by the fact that the initial sale from developer to first buyer is typically exempt from the fee.</P>
        <P>FHFA does not take a position on the merits of the environmental, conservation, or similar projects that are funded by private transfer fees. Instead, in its capacity as the safety and soundness regulator of Fannie Mae, Freddie Mac, and the Federal Home Loan Banks and as the Conservator of the Enterprises, FHFA addresses the subject from the perspective of the valuation issues that such use of private transfer fees may cause for the reasons enumerated above: Unpredictability of future sales and, therefore, the magnitude of the financial burden on the encumbered properties;<SU>6</SU>
          <FTREF/>lack of transparency to sellers and purchasers; and the practice of shifting the payment obligation to future buyers who are not privy to the settlement with environmental groups or to the initial transaction with the developer.<SU>7</SU>

          <FTREF/>As a result, FHFA declines to recognize such private transfer fee covenants as excepted from disqualification unless the activities they fund provide a direct benefit to the burdened properties, as defined in the rule and discussed further below. The environmental commenters' reliance on the National Environmental Policy Act of 1969, as amended (NEPA), (42 U.S.C. 4321<E T="03">et seq.</E>), is also discussed below.</P>
        <FTNT>
          <P>

            <SU>6</SU>“If the fee has a 20-year term, for example, one house may be sold three times and assessed three fees while another house is not sold and, consequently, has no fee.” “Using Real Estate Transfer Fees to Deliver Community Projects,” in<E T="03">Conservation Frontiers: Reports from the California Council of Land Trusts</E>(Feb. 2008), p. 3,<E T="03">at  http://www.calandtrusts.org/download.cfm?ID=24427.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>

            <SU>7</SU>“[T]he original sale of a house has not been assessed in most cases, but the fee does apply to all subsequent sales.”<E T="03">Id.</E>
          </P>
        </FTNT>
        <HD SOURCE="HD2">Regulatory Prerequisites</HD>
        <P>A number of commenters asserted that FHFA failed to satisfy prerequisites for rulemaking. Through counsel, a variety of environmental groups, including the NRDC, claimed that FHFA is required to prepare either an Environmental Impact Statement (EIS) or an Environmental Assessment (EA) under NEPA before proceeding with the rule. Freehold contended that FHFA is not complying with the Regulatory Flexibility Act (RFA), 5 U.S.C. 601through 612, because the regulation impacts small business entities and the RFA requires FHFA to undertake a detailed analysis and to adopt the least restrictive means for accomplishing the agency's objectives while minimizing the economic impact on small entities.</P>
        <P>For reasons explained below, FHFA disagrees with both of these comments. Neither an EIS nor an EA is required for this rule. The RFA was satisfied by the certification contained in the proposed rule and repeated in this final rule.</P>
        <HD SOURCE="HD2">National Environmental Policy Act</HD>
        <P>Before addressing the commenters' legal arguments, it is useful to review the background in which their private transfer fee practices have arisen. As described above, certain private transfer fees have been put in place to resolve claims of adverse environmental or other impacts that are asserted to result from proposed real estate developments—claims that would otherwise be resolved in court, or before government permitting bodies. Specifically, particular arrangements that commenters have held up as examples of how they would like to continue using private transfer fees have resulted from settlement of litigation or as a negotiated means to obtain government approval.<SU>8</SU>
          <FTREF/>In response to<PRTPAGE P="15572"/>those environmental and other concerns, various possible tools and outcomes are possible in such cases: a development may be blocked; restricted in other ways; or mitigating measures may be funded using means other than private transfer fees, such as by regular assessments that are more transparent and more readily translatable into property valuation than private transfer fees,<SU>9</SU>
          <FTREF/>or by a lump sum from sale of part of the subject property. Other tools may be available as well and, in some cases, the deciding authority would conclude that the development does not pose the concerns that are claimed and can proceed without restriction. Not one of the letters FHFA received raising environmental concerns about the proposed rule has explained why, or even asserted that, private transfer fees are the only or even a specially valuable tool for dealing with the concerns that have been asserted in comparison with other tools, or why they are the tool of preference, if they are.<SU>10</SU>
          <FTREF/>In each case, the environmental and other impacts that are asserted do not result from FHFA's proposed rule on private transfer fees, but from the real estate development to which the commenters object. That federal regulations may make one or another financing tool that the commenters might wish to use less attractive does not mean that those regulations cause environmental impacts.</P>
        <FTNT>
          <P>
            <SU>8</SU>
            <E T="03">See</E>“Using Real Estate Transfer Fees to Deliver Community Projects,” in<E T="03">Conservation Frontiers: Reports from the California Council of Land Trusts</E>

            <PRTPAGE/>(Feb. 2008), describing the litigation origin of the Roseville and Martis Valley private transfer fee arrangements in Placer County, California. Both of those arrangements are discussed in the comment letters FHFA has received. One comment letter described the Plum Creek development in Maine, in which private transfer fees feature prominently in an arrangement arrived at after five years of negotiations and hearings and approved by Maine's Land Use Regulation Commission. That arrangement, however, appears to be currently on hold as a result of subsequent litigation by a subset of the environmental groups,<E T="03">see</E>“Plum Creek's Maine Development Set Aside by Judge” (Associated Press, April 7, 2011).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>9</SU>
            <E T="03">See</E>Quang Do &amp; Sirmans, “Residential Property Tax Capitalization: Discount Rate Evidence from California,” 47 Nat'l Tax J. 341 (1994) (analyzing a data-set from a tax district in San Diego to argue that homebuyers capitalize real property taxes into purchase prices, discounting the future tax payments at a rate of about 4 percent).</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>10</SU>Perhaps developers show less resistance to private transfer fees than to other types of restrictions or funding mechanisms.<E T="03">See</E>supra n. 5. That certainly is the perspective of the commenters who are adverse to this use of private transfer fees.</P>
        </FTNT>
        <P>Even focusing only on private transfer fees, contrary to a commenter's assertion that FHFA “proposed [the] elimination of private transfer fees,” the rule does not restrict or ban them, but restricts its regulated entities from buying mortgages backed by real estate subject to certain types of covenants. Mortgages held in portfolio or securitized in private secondary markets are not affected by the rule.</P>

        <P>For these reasons, for purposes of the NEPA, FHFA's rule is financial and economic; it is not “a major Federal action[]<E T="03">significantly affecting the quality of the human environment.”</E>42 U.S.C. 4332. NEPA does not require the analysis commenters assert without an “injury to the environment; an economic injury will not suffice.”<E T="03">Ranchers Cattlemen Action Legal Fund United Stockgrowers of America, ICA</E>v.<E T="03">United States Department of Agriculture,</E>415 F.3d 1078, 1103 (9th Cir. 2005) (emphasis added). There must be some causal connection between the rule and the environmental injury. The environmental injury the commenters appear to assert is not caused by FHFA's rule; at best it has a tenuous and speculative nexus to the rule.</P>
        <P>The commenters assume that without unrestricted access to a federally supported secondary mortgage market for private transfer fee encumbered mortgages, their environmental protection activities will not just be inconvenienced, but subverted and permanently stopped. The agency recognized that some private transfer fees are used to fund desirable ends, some of which are environmental, social, or cultural. They still can be used for those purposes, but mortgages on property encumbered by them may not qualify for the federally supported secondary mortgage market unless they contain the features required by the rule. Considering all private transfer fee covenants, the rule allows regulated entity investment when property is encumbered by a grandfathered covenant, and also when the covenant creates a direct benefit to the encumbered property. In these circumstances, the regulated entities may invest in encumbered property. That leaves, as the asserted environmental injury, the inability to trade in the secondary mortgage market mortgages on property encumbered by those private transfer fees that do not return a benefit to the encumbered property, and that are not grandfathered as related to a pre-existing litigation settlement or government-approved agreement. No explanation has been offered why regulation of the mortgage market will result in developments with detrimental environmental impacts or that cannot be remedied by other means that do not pose risks to the safety and soundness of the regulated entities.</P>

        <P>FHFA is fundamentally responsible for the safety and soundness of the regulated entities. Its statutory command is to ensure their financial safety and soundness. FHFA cannot allow speculative considerations such as those offered by the commenters to interrupt or subordinate its statutory obligation to prohibit the regulated entities from engaging in unsafe and unsound practices. Congress did not condition FHFA's safety and soundness determinations on assessments of their environmental impact. Like the Federal Energy Regulatory Commission in<E T="03">Grand Council of the Crees</E>v.<E T="03">Federal Energy Regulatory Commission</E>(FERC), even if the proposed rule had an environmental impact, when acting to fulfill its independent statutory command to ensure safety and soundness, FHFA would not be required to conduct an EIS or an EA. 198 F.3d 950, 953-54, 956 (D.C. Cir. 2000) (when setting “just and reasonable rates” as commanded by statute, FERC was not required to conduct an EIS or EA, despite the environmental consequences of the action).</P>
        <HD SOURCE="HD2">Regulatory Flexibility Act</HD>

        <P>Both the proposed rule and this final rule comply with the RFA, 5 U.S.C. 601 through 612, because they contain FHFA's certification that the rule will not have a significant economic impact on a substantial number of small entities. This certification obviates the need for the detailed analysis commenters seek.<E T="03">See</E>5 U.S.C. 605(b).</P>

        <P>The only impacts that require an RFA analysis are the direct impacts of the rule on small entities that are subject to the rule.<E T="03">See, e.g.,</E>
          <E T="03">Cement Kiln Recycling Coalition</E>v.<E T="03">EPA,</E>255 F.3d 855, 869 (D.C. Cir. 2001) (citing cases “consistently reject[ing] the contention that the [RFA] applies to small businesses indirectly affected by the regulation of other entities”);<E T="03">Mid-Tex Electric Cooperative, Inc.</E>v.<E T="03">FERC,</E>773 F.2d 327, 343 (D.C. Cir. 1985) (where rule directly regulated utilities, agency did not have to analyze economic impact on wholesale customers of utilities);<E T="03">National Women, Infants, and Children Grocers Association</E>v.<E T="03">Food and Nutrition Service,</E>416 F. Supp. 2d 92, 108-10 (D.D.C. 2006) (where rule regulated state agencies, agency did not have to analyze impact on vendors that did business with state agencies). The only entities subject to this rule, and the only entities on which the rule will have direct impact, are the FHFA regulated entities—Fannie Mae, Freddie Mac, and the Federal Home Loan Banks—none of which is small. Therefore, an analysis under the RFA is not required. FHFA's certification is sufficient.<PRTPAGE P="15573"/>
        </P>
        <HD SOURCE="HD1">IV. FHFA Response to Public Comments in the Proposed Rule</HD>
        <P>FHFA has decided to adopt the rule largely as proposed. However, in response to comments received, FHFA is making a number of changes to the text of the regulation.</P>
        <P>Section 1228.2 is changed to ensure no doubt that any activity dealing in mortgages on property encumbered by private transfer fee covenants, including guaranteeing them as well as purchasing or investing in them, is restricted. The new language broadens the proposed phrase “purchase or invest in” to “purchase invest, or otherwise deal in.” The remainder of that section remains unchanged.</P>
        <P>A number of commenters criticized the definition of “adjacent or contiguous property,” and particularly the requirement that it be located within 1,000 yards of the burdened community, arguing that some commonly held facilities, such as marinas, beach access, or golf courses, often cannot feasibly be located within that distance, but yet are for the common benefit of the members of the community and contribute to the value of their property to the same extent as if they were closer. In response to that concern, FHFA has removed the proposed 1,000-yard requirement from the regulation.</P>
        <P>At the same time, some commenters pointed out that the restrictions on public access that the proposed regulation contemplated as part of the definition of “direct benefit” would be problematic in situations where the covered association uses transfer fees to fund parks or trails that interconnect with a larger municipal park or trail system which is open to the public. In that situation, although the covered association makes the adjacent property open to the public, the community members (and hence their property) receive fair value in exchange, in the form of convenient access to the larger trail or park system. To address this situation, as well as that described above of common facilities located some distance from the burdened community, FHFA is adopting a two-part approach to the use of transfer fees to fund activities or property outside the burdened community. First, the fees may fund property that is open to the public that is actually adjacent, meaning that it borders the burdened community.<SU>11</SU>

          <FTREF/>Second, transfer fees may fund amenities that are more distant, if the amenities are primarily for the benefit of the covered association's members. In light of these revisions, FHFA has deleted the proposed provisions regarding public access for a fee or<E T="03">de minimis</E>use, as adding unnecessary complexity.</P>
        <FTNT>
          <P>
            <SU>11</SU>The rule allows the properties to be separated by a public right of way, because a public right of way is not inconsistent with public access across the properties.</P>
        </FTNT>
        <P>Several commenters noted that some planned communities include both master associations and sub-associations, such that all residents are members of both a master association and a sub-association, but not of the same sub-association. The final regulation specifically recognizes that possibility.</P>
        <P>Some commenters observed that some payments or charges are secured by a covenant to pay upon the next transfer, but do not impose a continuing obligation to pay whenever the property is transferred. FHFA does not regard such obligations as posing the same valuation problem as continuing transfer fee covenants, and has clarified the regulation to define a private transfer fee as one that is payable on a continuing basis whenever the property is transferred. This clarification makes it unnecessary to except from the definition of “private transfer fee” payments arising from an option to purchase or waiver of the right to purchase the encumbered real property (an exception in the proposed definition which FHFA has removed from the final rule) and other exception items suggested by commenters, such as deferred purchase price payments. Other suggested exceptions are unnecessary; for example, loan prepayment fees need not be excepted because they are not paid “in connection with or as a result of transfer of title to real estate,” but rather because of prepayment of the loan and, therefore, are not covered by the definition of “private transfer fee” as proposed.</P>
        <P>In response to some comments and a review of state private transfer fee legislation, FHFA has added to the final rule an exception to the definition of “private transfer fee” for fees and payments that defray actual costs of the transfer, such as new keys, mailboxes, and other features that benefit the new owner.</P>
        <P>Some commenters urged that private transfer fees should be used to support local services such as schools, libraries, and fire departments. FHFA has not added an exception for such uses, which normally would fall within the proposed exception for fees paid to government entities. FHFA retains that exception in the final rule. If a particular use of transfer fee covenants would not fall within that exception, FHFA is reluctant to specifically sanction it in the final rule, because such a rule is likely to raise the concern about property valuation in the absence of a direct benefit, which motivates the rule as a whole.</P>
        <P>The proposed rule's definition of “private transfer fee” included an exception for fees that are imposed by court judgment, order, or decree. FHFA removes that exception in the final rule. A survey of existing state laws on private transfer fees reveals that most do not contain that exception. Further, review of the many comments discussing the use of private transfer fees to fund preservation or environmental projects that, though they may be meritorious from the perspective of society as a whole, do not contribute directly to the value of the burdened property, raising the valuation concerns that underlie this regulation when funded by private transfer fees, shows that such arrangements often result from settlement of litigation or threatened litigation, and therefore could be structured to escape the effect of this rule by moving to have them embodied in a court decree.</P>
        <P>A review of those state statutes on private transfer fees also shows that most of them do not contain the proposed rule's exception for mechanic's liens, plausibly because those liens do not secure an obligation to pay specifically upon transfer (though as a practical matter that obligation, and any other secured obligation, may have to be satisfied in order to clear the title and make the transfer) and are not private transfer fee covenants to begin with. Therefore, FHFA has removed that exception.</P>
        <P>Many commenters reacted favorably to FHFA's proposal that the regulation have prospective effect and not apply to private transfer fee covenants created before a date certain. A number of commenters, however, described projects currently underway that are funded by private transfer fees, which could be disrupted to the extent that covenants have not yet been attached to particular parcels that are part of the overall plan. FHFA has clarified the prospective scope of the rule, so that it will not apply to private transfer fee covenants if they are imposed pursuant to a litigation settlement agreement or an agreement approved by a government body before the date certain specified in the rule, February 8, 2011.</P>

        <P>Some commenters suggested that the proposed § 1228.4, “State restrictions unaffected,” be revised to state that such state restrictions might include restrictions on validity and enforceability as well as with respect to disclosures or duration, the two<PRTPAGE P="15574"/>examples given in the proposed rule. In cases where a state law restricts the validity or enforceability of private transfer fees, it was not the intention of FHFA to override those restrictions, but rather to provide a framework to protect the regulated entities in the event that private transfer fees could be imposed consistently with state law. For example, one commenter stated that California law does not permit community associations to fund themselves using private transfer fees. That result is not affected by FHFA's rule permitting the regulated entities to buy mortgages that are secured by properties encumbered by such association transfer fees.</P>
        <P>And finally, various commenters suggested technical revisions to the proposed regulation in the interest of clarity, and FHFA adopts a number of those suggestions in the final rule.</P>
        <HD SOURCE="HD1">V. Paperwork Reduction Act</HD>

        <P>The rule does not contain any collections of information pursuant to the Paperwork Reduction Act of 1995 (44 U.S.C. 3501<E T="03">et seq.</E>). Therefore, FHFA has not submitted any information to the Office of Management and Budget for review.</P>
        <HD SOURCE="HD1">VI. Regulatory Flexibility Act</HD>
        <P>The rule applies only to the regulated entities, which do not come within the meaning of small entities as defined in section 601(6) of the RFA. In accordance with section 605(b) of the RFA, FHFA certifies that this rule will not have a significant economic impact on a substantial number of small entities.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 12 CFR Part 1228</HD>
          <P>Asset-backed securities, Builders, Condominium associations, Cooperative associations, Developers, Federal Home Loan Banks, Government-sponsored enterprises, Homeowners' associations, Housing, Mortgages, Mortgage-backed securities, Nonprofit organizations, Private transfer fees.</P>
        </LSTSUB>
        
        <P>For the reasons stated in the Supplementary Information, and under the authority of 12 U.S.C. 4526, the Federal Housing Finance Agency amends Chapter XII of Title 12 of the Code of Federal Regulations by adding new part 1228 to subchapter B to read as follows:</P>
        <REGTEXT PART="1228" TITLE="12">
          <PART>
            <HD SOURCE="HED">PART 1228—RESTRICTIONS ON THE ACQUISITION OF, OR TAKING SECURITY INTERESTS IN, MORTGAGES ON PROPERTIES ENCUMBERED BY CERTAIN PRIVATE TRANSFER FEE COVENANTS AND RELATED SECURITIES</HD>
            
            <CONTENTS>
              <SECHD>Sec.</SECHD>
              <SECTNO>1228.1</SECTNO>
              <SUBJECT>Definitions.</SUBJECT>
              <SECTNO>1228.2</SECTNO>
              <SUBJECT>Restrictions.</SUBJECT>
              <SECTNO>1228.3</SECTNO>
              <SUBJECT>Prospective application and effective date.</SUBJECT>
              <SECTNO>1228.4</SECTNO>
              <SUBJECT>State restrictions unaffected.</SUBJECT>
            </CONTENTS>
            
            <AUTH>
              <HD SOURCE="HED">Authority:</HD>
              <P>12 U.S.C. 4511, 4513, 4526, 4616, 4617, 4631.</P>
            </AUTH>
            <SECTION>
              <SECTNO>§ 1228.1</SECTNO>
              <SUBJECT>Definitions.</SUBJECT>
              <P>For the purposes of this part, the following definitions apply:</P>
              <P>
                <E T="03">Adjacent or contiguous property</E>means property that borders the burdened community,<E T="03">provided that</E>such adjacent or contiguous property may be separated from the burdened community by public right of way.</P>
              <P>
                <E T="03">Burdened community</E>means a community comprising all of the parcels or interests in real property encumbered by a single private transfer fee covenant or a series of separate private transfer fee covenants that require payment of private transfer fees to the same entity to be used for the same purposes.</P>
              <P>
                <E T="03">Covered association</E>means a nonprofit mandatory membership organization comprising owners of homes, condominiums, cooperatives, manufactured homes, or any interest in real property, created pursuant to a declaration, covenant or other applicable law; or an organization described in section 501(c)(3) or section 501(c)(4) of the Internal Revenue Code. A covered association may include master and sub-associations, each of which is also a covered association.</P>
              <P>
                <E T="03">Direct benefit</E>means that the proceeds of a private transfer fee are used exclusively to support maintenance and improvements to encumbered properties, and acquisition, improvement, administration, and maintenance of property owned by the covered association of which the owners of the burdened property are members and used primarily for their benefit.<E T="03">Direct benefit</E>also includes cultural, educational, charitable, recreational, environmental, conservation or other similar activities that—</P>
              <P>(1) Are conducted in or protect the burdened community or adjacent or contiguous property, or</P>
              <P>(2) Are conducted on other property that is used primarily by residents of the burdened community.</P>
              <P>
                <E T="03">Enterprises</E>means, collectively, the Federal National Mortgage Association and the Federal Home Loan Mortgage Corporation.</P>
              <P>
                <E T="03">Excepted transfer fee covenant</E>means a private transfer fee covenant that requires payment of a private transfer fee to a covered association and limits the use of such transfer fees exclusively to purposes which provide a direct benefit to the real property encumbered by the private transfer fee covenants.</P>
              <P>
                <E T="03">Federal Home Loan Banks</E>or<E T="03">Banks</E>mean the Federal Home Loan Banks established under section 12 of the Federal Home Loan Bank Act (12 U.S.C. 1432).</P>
              <P>
                <E T="03">Private transfer fee</E>means a transfer fee, including a charge or payment, imposed by a covenant, restriction, or other similar document and required to be paid in connection with or as a result of a transfer of title to real estate, and payable on a continuing basis each time a property is transferred (except for transfers specifically excepted) for a period of time or indefinitely. A<E T="03">private transfer fee</E>does not include fees, charges, payments, or other obligations—</P>
              <P>(1) Imposed by or payable to the Federal government or a State or local government; or</P>
              <P>(2) That defray actual costs of the transfer of the property, including transfer of membership in the relevant covered association.</P>
              <P>
                <E T="03">Private transfer fee covenant</E>means a covenant that:</P>
              <P>(1) Purports to run with the land or to bind current owners of, and successors in title to, such real property; and</P>
              <P>(2) Obligates a transferee or transferor of all or part of the property to pay a private transfer fee upon transfer of an interest in all or part of the property, or in consideration for permitting such transfer.</P>
              <P>
                <E T="03">Regulated entities</E>means the Federal National Mortgage Association, the Federal Home Loan Mortgage Corporation, and the Federal Home Loan Banks.</P>
              <P>
                <E T="03">Transfer</E>means, with respect to real property, the sale, gift, grant, conveyance, assignment, inheritance, or other transfer of an interest in the real property.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1228.2</SECTNO>
              <SUBJECT>Restrictions.</SUBJECT>

              <P>The regulated entities shall not purchase, invest or otherwise deal in any mortgages on properties encumbered by private transfer fee covenants, securities backed by such mortgages, or securities backed by the income stream from such covenants, unless such covenants are excepted transfer fee covenants. The Federal Home Loan Banks shall not accept such mortgages or securities as collateral,<PRTPAGE P="15575"/>unless such covenants are excepted transfer fee covenants.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1228.3</SECTNO>
              <SUBJECT>Prospective application and effective date.</SUBJECT>
              <P>This part shall apply only to mortgages on properties encumbered by private transfer fee covenants if those covenants are created on or after February 8, 2011. This part shall not apply to mortgages on properties encumbered by private transfer fee covenants if those covenants are created pursuant to an agreement entered into before February 8, 2011, applicable to land that is identified in the agreement, and the agreement was in settlement of litigation or approved by a government agency or body. This part also applies to securities backed by mortgages to which this part applies, and to securities issued after February 8, 2011, backed by revenue from private transfer fees regardless of when the covenants were created. The regulated entities shall comply with this part not later July 16, 2012.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 1228.4</SECTNO>
              <SUBJECT>State restrictions unaffected.</SUBJECT>
              <P>This part does not affect state restrictions or requirements with respect to private transfer fee covenants, such as with respect to validity, enforceability, disclosures, or duration.</P>
            </SECTION>
          </PART>
        </REGTEXT>
        <SIG>
          <DATED>Dated: March 12, 2012.</DATED>
          <NAME>Edward J. DeMarco,</NAME>
          <TITLE>Acting Director, Federal Housing Finance Agency.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6414 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 8070-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Federal Aviation Administration</SUBAGY>
        <CFR>14 CFR Part 71</CFR>
        <DEPDOC>[Docket No. FAA-2011-1192; Airspace Docket No. 11-ANM-22]</DEPDOC>
        <SUBJECT>Modification of Class E Airspace; Sheridan, WY</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Aviation Administration (FAA), DOT.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This action amends Class E airspace at Sheridan County Airport, Sheridan, WY. Decommissioning of the Sheridan Tactical Air Navigation System (TACAN) has made this action necessary for the safety and management of Instrument Flight Rules (IFR) operations at the airport.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Effective date, 0901 UTC, May 31, 2012. The Director of the Federal Register approves this incorporation by reference action under 1 CFR part 51, subject to the annual revision of FAA Order 7400.9 and publication of conforming amendments.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Eldon Taylor, Federal Aviation Administration, Operations Support Group, Western Service Center, 1601 Lind Avenue SW., Renton, WA 98057; telephone (425) 203-4537.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">History</HD>
        <P>On December 22, 2011, the FAA published in the<E T="04">Federal Register</E>a notice of proposed rulemaking to amend controlled airspace at Sheridan, WY (76 FR 79563). Interested parties were invited to participate in this rulemaking effort by submitting written comments on the proposal to the FAA. No comments were received.</P>
        <P>Class E airspace designations are published in paragraph 6002, of FAA Order 7400.9V dated August 9, 2011, and effective September 15, 2011, which is incorporated by reference in 14 CFR Part 71.1. The Class E airspace designations listed in this document will be published subsequently in that Order.</P>
        <HD SOURCE="HD1">The Rule</HD>
        <P>This action amends Title 14 Code of Federal Regulations (14 CFR) Part 71 by amending Class E surface airspace at Sheridan County Airport, Sheridan, WY. Airspace reconfiguration is necessary due to the decommissioning of the Sheridan TACAN. This action is necessary for the safety and management of IFR operations.</P>
        <P>The FAA has determined this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. Therefore, this regulation: (1) Is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. Since this is a routine matter that will only affect air traffic procedures and air navigation, it is certified this rule, when promulgated, will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act. The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the U.S. Code. Subtitle 1, Section 106 discusses 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 I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of airspace necessary to ensure the safety of aircraft and the efficient use of airspace. This regulation is within the scope of that authority as it amends controlled airspace at Sheridan County Airport, Sheridan WY.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 14 CFR Part 71</HD>
          <P>Airspace, Incorporation by reference, Navigation (air).</P>
        </LSTSUB>
        <HD SOURCE="HD1">Adoption of the Amendment</HD>
        <P>In consideration of the foregoing, the Federal Aviation Administration amends 14 CFR part 71 as follows:</P>
        <REGTEXT PART="71" TITLE="14">
          <PART>
            <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, B, C, D AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS</HD>
          </PART>
          <AMDPAR>1. The authority citation for 14 CFR Part 71 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 106(g), 40103, 40113, 40120; E. O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="71" TITLE="14">
          <SECTION>
            <SECTNO>§ 71.1</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. The incorporation by reference in 14 CFR Part 71.1 of the Federal Aviation Administration Order 7400.9V, Airspace Designations and Reporting Points, dated August 9, 2011, and effective September 15, 2011 is amended as follows:</AMDPAR>
          <EXTRACT>
            <HD SOURCE="HD2">Paragraph 6002Class E airspace designated as surface areas.</HD>
            <STARS/>
            <HD SOURCE="HD1">ANM WY E2Sheridan WY [Amended]</HD>
            <FP SOURCE="FP-2">Sheridan County Airport, WY</FP>
            <FP SOURCE="FP1-2">(Lat. 44°46′09″ N., long. 106°58′49″ W.)</FP>
            
            <P>That airspace extending upward from the surface within a 4.5-mile radius of the Sheridan County Airport, and within 4.5 miles each side of the 157° bearing of the airport, extending from the 4.5-mile radius to 17.6 miles southeast of the airport, and within 3.5 miles each side of the Sheridan County Airport 316° bearing extending from the 4.5-mile radius to 15.5 miles northwest of the airport, and within 3.5 miles each side of the Sheridan County Airport 325° bearing extending from the 4.5-mile radius to 16 miles northwest of the airport, and 4 miles each side of the 336° bearing of the Sheridan County Airport extending from the 4.5-mile radius to 15.4 miles northwest of the airport, and within 3.5 miles each side of the Sheridan County Airport 140° bearing extending from the 4.5-mile radius to 15.5 miles southeast of the airport.</P>
            
          </EXTRACT>
        </REGTEXT>
        <SIG>
          <PRTPAGE P="15576"/>
          <DATED>Issued in Seattle, Washington, on March 7, 2012.</DATED>
          <NAME>John Warner,</NAME>
          <TITLE>Manager, Operations Support Group, Western Service Center.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6341 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-13-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Federal Aviation Administration</SUBAGY>
        <CFR>14 CFR Part 97</CFR>
        <DEPDOC>[Docket No. 30831; Amdt. No. 3468]</DEPDOC>
        <SUBJECT>Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures; Miscellaneous Amendments</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Aviation Administration (FAA), DOT.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This rule establishes, amends, suspends, or revokes Standard Instrument Approach Procedures (SIAPs) and associated Takeoff Minimums and Obstacle Departure Procedures for operations at certain airports. These regulatory actions are needed because of the adoption of new or revised criteria, or because of changes occurring in the National Airspace System, such as the commissioning of new navigational facilities, adding new obstacles, or changing air traffic requirements. These changes are designed to provide safe and efficient use of the navigable airspace and to promote safe flight operations under instrument flight rules at the affected airports.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective March 16, 2012. The compliance date for each SIAP, associated Takeoff Minimums, and ODP is specified in the amendatory provisions.</P>
          <P>The incorporation by reference of certain publications listed in the regulations is approved by the Director of the Federal Register as of March 16, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Availability of matters incorporated by reference in the amendment is as follows:</P>
          <P>
            <E T="03">For Examination—</E>
          </P>
          <P>1. FAA Rules Docket, FAA Headquarters Building, 800 Independence Avenue SW., Washington, DC 20591;</P>
          <P>2. The FAA Regional Office of the region in which the affected airport is located;</P>
          <P>3. The National Flight Procedures Office, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 or</P>

          <P>4. The National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to:<E T="03">http://www.archives.gov/federal_register/code_of_federal_regulations/ibr_locations.html.</E>
          </P>
          <P>
            <E T="03">Availability</E>—All SIAPs and Takeoff Minimums and ODPs are available online free of charge. Visit<E T="03">http://www.nfdc.faa.gov</E>to register. Additionally, individual SIAP and Takeoff Minimums and ODP copies may be obtained from:</P>
          <P>1. FAA Public Inquiry Center (APA-200), FAA Headquarters Building, 800 Independence Avenue SW., Washington, DC 20591; or</P>
          <P>2. The FAA Regional Office of the region in which the affected airport is located.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Richard A. Dunham III, Flight Procedure Standards Branch (AFS-420), Flight Technologies and Programs Divisions, Flight Standards Service, Federal Aviation Administration, Mike Monroney Aeronautical Center, 6500 South MacArthur Blvd. Oklahoma City, OK 73169 (Mail Address: P.O. Box 25082, Oklahoma City, OK 73125) Telephone: (405) 954-4164.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>This rule amends Title 14 of the Code of Federal Regulations, Part 97 (14 CFR part 97), by establishing, amending, suspending, or revoking SIAPS, Takeoff Minimums and/or ODPS. The complete regulators description of each SIAP and its associated Takeoff Minimums or ODP for an identified airport is listed on FAA form documents which are incorporated by reference in this amendment under 5 U.S.C. 552(a), 1 CFR part 51, and 14 CFR part 97.20. The applicable FAA Forms are FAA Forms 8260-3, 8260-4, 8260-5, 8260-15A, and 8260-15B when required by an entry on 8260-15A.</P>

        <P>The large number of SIAPs, Takeoff Minimums and ODPs, in addition to their complex nature and the need for a special format make publication in the<E T="04">Federal Register</E>expensive and impractical. Furthermore, airmen do not use the regulatory text of the SIAPs, Takeoff Minimums or ODPs, but instead refer to their depiction on charts printed by publishers of aeronautical materials. The advantages of incorporation by reference are realized and publication of the complete description of each SIAP, Takeoff Minimums and ODP listed on FAA forms is unnecessary. This amendment provides the affected CFR sections and specifies the types of SIAPs and the effective dates of the, associated Takeoff Minimums and ODPs. This amendment also identifies the airport and its location, the procedure, and the amendment number.</P>
        <HD SOURCE="HD1">The Rule</HD>
        <P>This amendment to 14 CFR part 97 is effective upon publication of each separate SIAP, Takeoff Minimums and ODP as contained in the transmittal. Some SIAP and Takeoff Minimums and textual ODP amendments may have been issued previously by the FAA in a Flight Data Center (FDC) Notice to Airmen (NOTAM) as an emergency action of immediate flight safety relating directly to published aeronautical charts. The circumstances which created the need for some SIAP and Takeoff Minimums and ODP amendments may require making them effective in less than 30 days. For the remaining SIAPS and Takeoff Minimums and ODPS, an effective date at least 30 days after publication is provided.</P>
        <P>Further, the SIAPs and Takeoff Minimums and ODPS contained in this amendment are based on the criteria contained in the U.S. Standard for Terminal Instrument Procedures (TERPS). In developing these SIAPS and Takeoff Minimums and ODPs, the TERPS criteria were applied to the conditions existing or anticipated at the affected airports. Because of the close and immediate relationship between these SIAPs, Takeoff Minimums and ODPs, and safety in air commerce, I find that notice and public procedures before adopting these SIAPS, Takeoff Minimums and ODPs are impracticable and contrary to the public interest and, where applicable, that good cause exists for making some SIAPs effective in less than 30 days.</P>
        <HD SOURCE="HD1">Conclusion</HD>
        <P>The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore—(1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule ” under DOT Regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. For the same reason, the FAA certifies that this amendment will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
        <LSTSUB>
          <PRTPAGE P="15577"/>
          <HD SOURCE="HED">List of Subjects in 14 CFR Part 97</HD>
          <P>Air traffic control, Airports, Incorporation by reference, and Navigation (air).</P>
        </LSTSUB>
        <SIG>
          <DATED>Issued in Washington, DC on March 2, 2012.</DATED>
          <NAME>John McGraw,,</NAME>
          <TITLE>Deputy Director, Flight Standards Service.</TITLE>
        </SIG>
        <HD SOURCE="HD1">Adoption of the Amendment</HD>
        <P>Accordingly, pursuant to the authority delegated to me, Title 14, Code of Federal Regulations, Part 97 (14 CFR part 97) is amended by establishing, amending, suspending, or revoking Standard Instrument Approach Procedures and/or Takeoff Minimums and/or Obstacle Departure Procedures effective at 0902 UTC on the dates specified, as follows:</P>
        <REGTEXT PART="97" TITLE="14">
          <PART>
            <HD SOURCE="HED">PART 97—STANDARD INSTRUMENT APPROACH PROCEDURES</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 97 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 106(g), 40103, 40106, 40113, 40114, 40120, 44502, 44514, 44701, 44719, 44721-44722.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="97" TITLE="14">
          <AMDPAR>2. Part 97 is amended to read as follows:</AMDPAR>
          <HD SOURCE="HD1">Effective 5 APR 2012</HD>
          <FP SOURCE="FP-1">Bethel, AK, Bethel, ILS OR LOC/DME Y RWY 19R, Orig</FP>
          <FP SOURCE="FP-1">Bethel, AK, Bethel, ILS OR LOC/DME Z RWY 19R, Amdt 7</FP>
          <FP SOURCE="FP-1">Bethel, AK, Bethel, RNAV (GPS) RWY 19R, Amdt 2</FP>
          <FP SOURCE="FP-1">Jasper, AL, Walker County-Bevill Field, RNAV (GPS) RWY 9, Orig</FP>
          <FP SOURCE="FP-1">Scottsdale, AZ, Scottsdale, RNAV (GPS)-D, Amdt 1</FP>
          <FP SOURCE="FP-1">Scottsdale, AZ, Scottsdale, RNAV (GPS)-E, Amdt 1</FP>
          <FP SOURCE="FP-1">Scottsdale, AZ, Scottsdale, VOR-C, Amdt 2</FP>
          <FP SOURCE="FP-1">Scottsdale, AZ, Scottsdale, VOR/DME-A, Amdt 3</FP>
          <FP SOURCE="FP-1">Georgetown, DE, Sussex County, Takeoff Minimums and Obstacle DP, Amdt 3</FP>
          <FP SOURCE="FP-1">Laurel, DE, Laurel, GPS-A, Orig-A, CANCELLED</FP>
          <FP SOURCE="FP-1">Laurel, DE, Laurel, RNAV (GPS)-A, Orig</FP>
          <FP SOURCE="FP-1">Laurel, DE, Laurel, Takeoff Minimums and Obstacle DP, Amdt 2</FP>
          <FP SOURCE="FP-1">Miami, FL, Kendall-Tamiami Executive, ILS OR LOC RWY 9R, Amdt 11</FP>
          <FP SOURCE="FP-1">Orlando, FL, Executive, ILS OR LOC/DME RWY 25, Orig</FP>
          <FP SOURCE="FP-1">Orlando, FL, Executive, LOC BC RWY 25, Amdt 21B, CANCELLED</FP>
          <FP SOURCE="FP-1">Orlando, FL, Executive, LOC RWY 25, Orig</FP>
          <FP SOURCE="FP-1">Orlando, FL, Executive, RNAV (GPS) RWY 25, Amdt 1</FP>
          <FP SOURCE="FP-1">Ormond Beach, FL, Ormond Beach Muni, GPS RWY 8, Orig-A, CANCELLED</FP>
          <FP SOURCE="FP-1">Ormond Beach, FL, Ormond Beach Muni, RADAR 1, Amdt 2C, CANCELLED</FP>
          <FP SOURCE="FP-1">Ormond Beach, FL, Ormond Beach Muni, RNAV (GPS) RWY 8, Orig</FP>
          <FP SOURCE="FP-1">Ormond Beach, FL, Ormond Beach Muni, RNAV (GPS) RWY 17, Orig</FP>
          <FP SOURCE="FP-1">Ormond Beach, FL, Ormond Beach Muni, RNAV (GPS) RWY 26, Orig</FP>
          <FP SOURCE="FP-1">Ormond Beach, FL, Ormond Beach Muni, VOR RWY 17, Amdt 2</FP>
          <FP SOURCE="FP-1">Honolulu, HI, Honolulu Intl, ILS Y RWY 4R, Amdt 1</FP>
          <FP SOURCE="FP-1">Honolulu, HI, Honolulu Intl, ILS Z RWY 4R, Amdt 1</FP>
          <FP SOURCE="FP-1">Honolulu, HI, Honolulu Intl, LOC/DME RWY 4R, Amdt 1</FP>
          <FP SOURCE="FP-1">Honolulu, HI, Honolulu Intl, RNAV (GPS) Y RWY 4R, Amdt 2</FP>
          <FP SOURCE="FP-1">Honolulu, HI, Honolulu Intl, RNAV (RNP) Z RWY 4R, Amdt 1</FP>
          <FP SOURCE="FP-1">Honolulu, HI, Honolulu Intl, RNAV (RNP) Z RWY 8L, Amdt 1</FP>
          <FP SOURCE="FP-1">Chariton, IA, Chariton Muni, RNAV (GPS) RWY 17, Amdt 1</FP>
          <FP SOURCE="FP-1">Chariton, IA, Chariton Muni, VOR OR GPS RWY 17, Amdt 1A, CANCELLED</FP>
          <FP SOURCE="FP-1">Independence, IA, Independence Muni, NDB RWY 18, Amdt 3</FP>
          <FP SOURCE="FP-1">Independence, IA, Independence Muni, RNAV (GPS) RWY 18, Orig</FP>
          <FP SOURCE="FP-1">Independence, IA, Independence Muni, RNAV (GPS) RWY 36, Orig</FP>
          <FP SOURCE="FP-1">Red Oak, IA, Red Oak Muni, NDB RWY 17, Amdt 9, CANCELLED</FP>
          <FP SOURCE="FP-1">Red Oak, IA, Red Oak Muni, RNAV (GPS) RWY 5, Amdt 1</FP>
          <FP SOURCE="FP-1">Carmi, IL, Carmi Muni, NDB RWY 36, Amdt 1A, CANCELLED</FP>
          <FP SOURCE="FP-1">Bar Harbor, ME, Hancock County-Bar Harbor, ILS OR LOC RWY 22, Amdt 6A</FP>
          <FP SOURCE="FP-1">Fayetteville, NC, Fayetteville Rgnl/Grannis Field, ILS OR LOC/DME RWY 4, Amdt 16A</FP>
          <FP SOURCE="FP-1">Fayetteville, NC, Fayetteville Rgnl/Grannis Field, LOC BC RWY 22, Amdt 8</FP>
          <FP SOURCE="FP-1">Fayetteville, NC, Fayetteville Rgnl/Grannis Field, RNAV (GPS) RWY 4, Amdt 2</FP>
          <FP SOURCE="FP-1">Fayetteville, NC, Fayetteville Rgnl/Grannis Field, RNAV (GPS) RWY 22, Amdt 4</FP>
          <FP SOURCE="FP-1">Pinehurst/Southern Pines, NC, Moore County, ILS OR LOC RWY 5, Amdt 1</FP>
          <FP SOURCE="FP-1">Pinehurst/Southern Pines, NC, Moore County, RNAV (GPS) RWY 23, Amdt 1</FP>
          <FP SOURCE="FP-1">Chadron, NE, Chadron Muni, ILS OR LOC RWY 2, Amdt 2A</FP>
          <FP SOURCE="FP-1">Chadron, NE, Chadron Muni, NDB RWY 20, Amdt 12A</FP>
          <FP SOURCE="FP-1">Chadron, NE, Chadron Muni, RNAV (GPS) RWY 2, Amdt 1</FP>
          <FP SOURCE="FP-1">Chadron, NE, Chadron Muni, RNAV (GPS) RWY 20, Amdt 2</FP>
          <FP SOURCE="FP-1">Lincoln, NE, Lincoln, ILS OR LOC RWY 18, Amdt 7</FP>
          <FP SOURCE="FP-1">Lincoln, NE, Lincoln, ILS OR LOC RWY 36, Amdt 11G</FP>
          <FP SOURCE="FP-1">Findlay, OH, Findlay, VOR RWY 25, Amdt 5A, CANCELLED</FP>
          <FP SOURCE="FP-1">Findlay, OH, Findlay, VOR RWY 36, Amdt 6B, CANCELLED</FP>
          <FP SOURCE="FP-1">Bloomsburg, PA, Bloomsburg Muni, Takeoff Minimums and Obstacle DP, Amdt 1</FP>
          <FP SOURCE="FP-1">Reedsville, PA, Mifflin County, LOC RWY 6, Amdt 8A</FP>
          <FP SOURCE="FP-1">Nashville, TN, Nashville Intl, RNAV (GPS) RWY 20C, Orig</FP>
          <FP SOURCE="FP-1">Smithville, TN, Smithville Muni, RNAV (GPS) RWY 6, Amdt 2</FP>
          <FP SOURCE="FP-1">Smithville, TN, Smithville Muni, RNAV (GPS) RWY 24, Amdt 2</FP>
          <FP SOURCE="FP-1">Houston, TX, Ellington Field, RNAV (GPS) RWY 17R, Amdt 1</FP>
          <FP SOURCE="FP-1">Houston, TX, Ellington Field, RNAV (GPS) RWY 22, Amdt 1A</FP>
          <FP SOURCE="FP-1">Kerrville, TX, Kerrville Muni/Louis Schreiner Field, LOC RWY 30, Amdt 4A</FP>
          <FP SOURCE="FP-1">Kerrville, TX, Kerrville Muni/Louis Schreiner Field, RNAV (GPS) RWY 12, Amdt 1</FP>
          <FP SOURCE="FP-1">Kerrville, TX, Kerrville Muni/Louis Schreiner Field, RNAV (GPS) RWY 30, Orig-A</FP>
          
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6010 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-13-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Federal Aviation Administration</SUBAGY>
        <CFR>14 CFR Part 97</CFR>
        <DEPDOC>[Docket No. 30832; Amdt. No. 3469]</DEPDOC>
        <SUBJECT>Standard Instrument Approach Procedures, and Takeoff Minimums and Obstacle Departure Procedures; Miscellaneous Amendments</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Aviation Administration (FAA), DOT.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>This rule establishes, amends, suspends, or revokes Standard Instrument Approach Procedures (SIAPs) and associated Takeoff Minimums and Obstacle Departure Procedures for operations at certain airports. These regulatory actions are needed because of the adoption of new or revised criteria, or because of changes occurring in the National Airspace System, such as the commissioning of new navigational facilities, adding new obstacles, or changing air traffic requirements. These changes are designed to provide safe and efficient use of the navigable airspace and to promote safe flight operations under<PRTPAGE P="15578"/>instrument flight rules at the affected airports.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective March 16, 2012. The compliance date for each SIAP, associated Takeoff Minimums, and ODP is specified in the amendatory provisions.</P>
          <P>The incorporation by reference of certain publications listed in the regulations is approved by the Director of the Federal Register as of March 16, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Availability of matter incorporated by reference in the amendment is as follows:</P>
          <P>
            <E T="03">For Examination</E>—</P>
          <P>1. FAA Rules Docket, FAA Headquarters Building, 800 Independence Avenue SW., Washington, DC 20591;</P>
          <P>2. The FAA Regional Office of the region in which the affected airport is located;</P>
          <P>3. The National Flight Procedures Office, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 or</P>

          <P>4. The National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to:<E T="03">http://www.archives.gov/federal_register/code_of_federal_regulations/ibr_locations.html.</E>
          </P>
          <P>
            <E T="03">Availability</E>—All SIAPs are available online free of charge. Visit nfdc.faa.gov to register. Additionally, individual SIAP and Takeoff Minimums and ODP copies may be obtained from:</P>
          <P>1. FAA Public Inquiry Center (APA-200), FAA Headquarters Building, 800 Independence Avenue SW., Washington, DC 20591; or</P>
          <P>2. The FAA Regional Office of the region in which the affected airport is located.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Richard A. Dunham III, Flight Procedure Standards Branch (AFS-420) Flight Technologies and Programs Division, Flight Standards Service, Federal Aviation Administration, Mike Monroney Aeronautical Center, 6500 South MacArthur Blvd., Oklahoma City, OK 73169 (Mail Address: P.O. Box 25082 Oklahoma City, OK. 73125) telephone: (405) 954-4164.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>This rule amends Title 14, Code of Federal Regulations, Part 97 (14 CFR part 97) by amending the referenced SIAPs. The complete regulatory description of each SIAP is listed on the appropriate FAA Form 8260, as modified by the National Flight Data Center (FDC)/Permanent Notice to Airmen (P-NOTAM), and is incorporated by reference in the amendment under 5 U.S.C. 552(a), 1 CFR part 51, and § 97.20 of Title 14 of the Code of Federal Regulations.</P>

        <P>The large number of SIAPs, their complex nature, and the need for a special format make their verbatim publication in the<E T="04">Federal Register</E>expensive and impractical. Further, airmen do not use the regulatory text of the SIAPs, but refer to their graphic depiction on charts printed by publishers of aeronautical materials. Thus, the advantages of incorporation by reference are realized and publication of the complete description of each SIAP contained in FAA form documents is unnecessary. This amendment provides the affected CFR sections and specifies the types of SIAP and the corresponding effective dates. This amendment also identifies the airport and its location, the procedure and the amendment number.</P>
        <HD SOURCE="HD1">The Rule</HD>
        <P>This amendment to 14 CFR part 97 is effective upon publication of each separate SIAP as amended in the transmittal. For safety and timeliness of change considerations, this amendment incorporates only specific changes contained for each SIAP as modified by FDC/P-NOTAMs.</P>
        <P>The SIAPs, as modified by FDC P-NOTAM, and contained in this amendment are based on the criteria contained in the U.S. Standard for Terminal Instrument Procedures (TERPS). In developing these changes to SIAPs, the TERPS criteria were applied only to specific conditions existing at the affected airports. All SIAP amendments in this rule have been previously issued by the FAA in a FDC NOTAM as an emergency action of immediate flight safety relating directly to published aeronautical charts. The circumstances which created the need for all these SIAP amendments requires making them effective in less than 30 days.</P>
        <P>Because of the close and immediate relationship between these SIAPs and safety in air commerce, I find that notice and public procedure before adopting these SIAPs are impracticable and contrary to the public interest and, where applicable, that good cause exists for making these SIAPs effective in less than 30 days.</P>
        <HD SOURCE="HD1">Conclusion</HD>
        <P>The FAA has determined that this regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore—(1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT regulatory Policies and Procedures (44 FR 11034; February 26, 1979); and (3) does not warrant preparation of a regulatory evaluation as the anticipated impact is so minimal. For the same reason, the FAA certifies that this amendment will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 14 CFR Part 97</HD>
          <P>Air traffic control, Airports, Incorporation by reference, and Navigation (air).</P>
        </LSTSUB>
        <SIG>
          <DATED>Issued in Washington, DC, on March 2, 2012.</DATED>
          <NAME>John McGraw,</NAME>
          <TITLE>Deputy Director, Flight Standards Service.</TITLE>
        </SIG>
        <HD SOURCE="HD1">Adoption of the Amendment</HD>
        <P>Accordingly, pursuant to the authority delegated to me, Title 14, Code of Federal regulations, Part 97, 14 CFR part 97, is amended by amending Standard Instrument Approach Procedures, effective at 0901 UTC on the dates specified, as follows:</P>
        <REGTEXT PART="97" TITLE="14">
          <PART>
            <HD SOURCE="HED">PART 97—STANDARD INSTRUMENT APPROACH PROCEDURES</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 97 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 106(g), 40103, 40106, 40113, 40114, 40120, 44502, 44514, 44701, 44719, 44721-44722.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="97" TITLE="14">
          <AMDPAR>2. Part 97 is amended to read as follows:</AMDPAR>
          <P>By amending: § 97.23 VOR, VOR/DME, VOR or TACAN, and VOR/DME or TACAN; § 97.25 LOC, LOC/DME, LDA, LDA/DME, SDF, SDF/DME; § 97.27 NDB, NDB/DME; § 97.29 ILS, ILS/DME, MLS, MLS/DME, MLS/RNAV; § 97.31 RADAR SIAPs; § 97.33 RNAV SIAPs; and § 97.35 COPTER SIAPs, Identified as follows:</P>
          <EXTRACT>
            <HD SOURCE="HD2">* * * Effective Upon Publication</HD>
          </EXTRACT>
          <GPOTABLE CDEF="xs48,xls32,r50,r50,10,10,r50" COLS="7" OPTS="L2,tp0,i1">
            <TTITLE/>
            <BOXHD>
              <CHED H="1">AIRAC date</CHED>
              <CHED H="1">State</CHED>
              <CHED H="1">City</CHED>
              <CHED H="1">Airport</CHED>
              <CHED H="1">FDC</CHED>
              <CHED H="1">FDC date</CHED>
              <CHED H="1">Subject</CHED>
            </BOXHD>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Bristol-Johnson-Kingsport</ENT>
              <ENT>Bristol/Tri-Cities Rgnl</ENT>
              <ENT>2/0280</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS RWY 23, ILS RWY 23 (CAT II), Amdt 24D.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>AK</ENT>
              <ENT>Soldotna</ENT>
              <ENT>Soldotna</ENT>
              <ENT>2/0793</ENT>
              <ENT>2/23/12</ENT>
              <ENT>NDB RWY 07, Amdt 2.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="15579"/>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>AK</ENT>
              <ENT>Soldotna</ENT>
              <ENT>Soldotna</ENT>
              <ENT>2/1292</ENT>
              <ENT>2/23/12</ENT>
              <ENT>VOR-A, Amdt 7.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TX</ENT>
              <ENT>Van Horn</ENT>
              <ENT>Culberson County</ENT>
              <ENT>2/2701</ENT>
              <ENT>2/13/12</ENT>
              <ENT>NDB RWY 21, Amdt 2A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>St Louis</ENT>
              <ENT>Lambert-St Louis Intl</ENT>
              <ENT>2/2720</ENT>
              <ENT>2/27/12</ENT>
              <ENT>ILS OR LOC RWY 11, ILS RWY 11 (CAT II), ILS RWY 11 (CAT III), Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>St Louis</ENT>
              <ENT>Lambert-St Louis Intl</ENT>
              <ENT>2/2721</ENT>
              <ENT>2/27/12</ENT>
              <ENT>ILS OR LOC RWY 12L, ILS RWY 12L (CAT II), ILS RWY 12L (CAT III), Amdt 6.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>Kansas City</ENT>
              <ENT>Kansas City Intl</ENT>
              <ENT>2/2722</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 1R, ILS RWY 1R (CAT II), ILS RWY 1R (CAT III), Amdt 3A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>Kansas City</ENT>
              <ENT>Kansas City Intl</ENT>
              <ENT>2/2723</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 19R, ILS RWY 19R (CAT II), ILS RWY 19R (CAT III), Amdt 10A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>St Louis</ENT>
              <ENT>Lambert-St Louis Intl</ENT>
              <ENT>2/2724</ENT>
              <ENT>2/27/12</ENT>
              <ENT>ILS OR LOC RWY 30R, ILS RWY 30R (CAT II), ILS RWY 30R (CAT III), Amdt 10.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Dayton</ENT>
              <ENT>James M Cox Dayton Intl</ENT>
              <ENT>2/2725</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 6L, ILS RWY 6L (CAT II), ILS RWY 6L (CAT III), Amdt 9.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>AR</ENT>
              <ENT>Little Rock</ENT>
              <ENT>Adams Field</ENT>
              <ENT>2/2727</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 22R, ILS RWY 22R (CAT II), ILS RWY 22R (CAT III), Amdt 2A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MI</ENT>
              <ENT>Detroit</ENT>
              <ENT>Detroit Metropolitan Wayne County</ENT>
              <ENT>2/2732</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 3R, ILS RWY 3R (CAT II), ILS RWY 3R (CAT III), Amdt 15A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Cleveland</ENT>
              <ENT>Cleveland-Hopkins Intl</ENT>
              <ENT>2/2733</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 6L, ILS RWY 6L (CAT II), ILS RWY 6L (CAT III), Amdt 2B.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Cleveland</ENT>
              <ENT>Cleveland-Hopkins Intl</ENT>
              <ENT>2/2734</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC/DME RWY 24R, ILS RWY 24R (SA CAT I), ILS RWY 24R (CAT II), ILS RWY 24R (CAT III), Amdt 5.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Cleveland</ENT>
              <ENT>Cleveland-Hopkins Intl</ENT>
              <ENT>2/2735</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 24L, ILS RWY 24L (SA CAT II), Amdt 22.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MI</ENT>
              <ENT>Detroit</ENT>
              <ENT>Detroit Metropolitan Wayne County</ENT>
              <ENT>2/2740</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 4R, ILS RWY 4R (CAT II), ILS RWY 4R (CAT III), Amdt 16.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>Kansas City</ENT>
              <ENT>Kansas City Intl</ENT>
              <ENT>2/2743</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) Y RWY 1R, Amdt 1A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>Kansas City</ENT>
              <ENT>Kansas City Intl</ENT>
              <ENT>2/2744</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) Y RWY 19L, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>AR</ENT>
              <ENT>Little Rock</ENT>
              <ENT>Adams Field</ENT>
              <ENT>2/2746</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 4R, Amdt 2A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Cleveland</ENT>
              <ENT>Cleveland-Hopkins Intl</ENT>
              <ENT>2/2751</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 6R, ILS RWY 6R (SA CAT II), Amdt 21.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KS</ENT>
              <ENT>Wichita</ENT>
              <ENT>Wichita Mid-Continent</ENT>
              <ENT>2/2752</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 1R, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KS</ENT>
              <ENT>Wichita</ENT>
              <ENT>Wichita Mid-Continent</ENT>
              <ENT>2/2754</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (RNP) Z RWY 19L, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MI</ENT>
              <ENT>Detroit</ENT>
              <ENT>Detroit Metropolitan Wayne County</ENT>
              <ENT>2/2758</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 4L, Amdt 2.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>Kansas City</ENT>
              <ENT>Kansas City Intl</ENT>
              <ENT>2/2759</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (RNP) Z RWY 1R, Orig-B.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>St Louis</ENT>
              <ENT>Lambert-St Louis Intl</ENT>
              <ENT>2/2760</ENT>
              <ENT>2/27/12</ENT>
              <ENT>RNAV (GPS) RWY 11, Orig.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>AR</ENT>
              <ENT>Little Rock</ENT>
              <ENT>Adams Field</ENT>
              <ENT>2/2768</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 4L, Amdt 25D.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>AR</ENT>
              <ENT>Little Rock</ENT>
              <ENT>Adams Field</ENT>
              <ENT>2/2770</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 4R, Amdt 1A.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="15580"/>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>AR</ENT>
              <ENT>Little Rock</ENT>
              <ENT>Adams Field</ENT>
              <ENT>2/2771</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 22L, Amdt 1A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>AR</ENT>
              <ENT>Little Rock</ENT>
              <ENT>Adams Field</ENT>
              <ENT>2/2772</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 4L, Amdt 1A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KS</ENT>
              <ENT>Wichita</ENT>
              <ENT>Wichita Mid-Continent</ENT>
              <ENT>2/2780</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 19R, Amdt 5C.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OK</ENT>
              <ENT>Oklahoma City</ENT>
              <ENT>Will Rogers World</ENT>
              <ENT>2/2781</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (RNP) Z RWY 17L, Amdt 2.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>Kansas City</ENT>
              <ENT>Kansas City Intl</ENT>
              <ENT>2/2783</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (RNP) Z RWY 19R, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>St Louis</ENT>
              <ENT>Lambert-St Louis Intl</ENT>
              <ENT>2/2784</ENT>
              <ENT>2/27/12</ENT>
              <ENT>ILS OR LOC RWY 29, Amdt 1B.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OK</ENT>
              <ENT>Oklahoma City</ENT>
              <ENT>Will Rogers World</ENT>
              <ENT>2/2786</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (RNP) Z RWY 35R, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OK</ENT>
              <ENT>Oklahoma City</ENT>
              <ENT>Will Rogers World</ENT>
              <ENT>2/2790</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) Y RWY 35R, Amdt 2.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>Kansas City</ENT>
              <ENT>Kansas City Intl</ENT>
              <ENT>2/2792</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 1L, Amdt 14.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>St Louis</ENT>
              <ENT>Lambert-St Louis Intl</ENT>
              <ENT>2/2793</ENT>
              <ENT>2/27/12</ENT>
              <ENT>RNAV (GPS) RWY 12L, Amdt 2.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>St Louis</ENT>
              <ENT>Lambert-St Louis Intl</ENT>
              <ENT>2/2795</ENT>
              <ENT>2/27/12</ENT>
              <ENT>ILS OR LOC RWY 12R, Admt 21E.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OK</ENT>
              <ENT>Oklahoma City</ENT>
              <ENT>Will Rogers World</ENT>
              <ENT>2/2797</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) Y RWY 17L, Amdt 2.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OK</ENT>
              <ENT>Oklahoma City</ENT>
              <ENT>Will Rogers World</ENT>
              <ENT>2/2799</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 17R, Amdt 11.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OK</ENT>
              <ENT>Oklahoma City</ENT>
              <ENT>Will Rogers World</ENT>
              <ENT>2/2800</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC/DME RWY 35L, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>Kansas City</ENT>
              <ENT>Kansas City Intl</ENT>
              <ENT>2/2802</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (RNP) Z RWY 1L, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>Kansas City</ENT>
              <ENT>Kansas City Intl</ENT>
              <ENT>2/2805</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) Y RWY 19R, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>St Louis</ENT>
              <ENT>Lambert-St Louis Intl</ENT>
              <ENT>2/2806</ENT>
              <ENT>2/27/12</ENT>
              <ENT>RNAV (GPS) RWY 30R, Amdt 1B.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MI</ENT>
              <ENT>Detroit</ENT>
              <ENT>Detroit Metropolitan Wayne County</ENT>
              <ENT>2/2807</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 22R, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Dayton</ENT>
              <ENT>James M Cox Dayton Intl</ENT>
              <ENT>2/2810</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) RWY 24R, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MI</ENT>
              <ENT>Detroit</ENT>
              <ENT>Detroit Metropolitan Wayne County</ENT>
              <ENT>2/2811</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 22L, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>St Louis</ENT>
              <ENT>Lambert-St Louis Intl</ENT>
              <ENT>2/2818</ENT>
              <ENT>2/27/12</ENT>
              <ENT>RNAV (GPS) RWY 30L, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>St Louis</ENT>
              <ENT>Lambert-St Louis Intl</ENT>
              <ENT>2/2823</ENT>
              <ENT>2/27/12</ENT>
              <ENT>ILS OR LOC RWY 30L, Amdt 12.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>St Louis</ENT>
              <ENT>Lambert-St Louis Intl</ENT>
              <ENT>2/2825</ENT>
              <ENT>2/27/12</ENT>
              <ENT>RNAV (GPS) RWY 12R, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>Kansas City</ENT>
              <ENT>Kansas City Intl</ENT>
              <ENT>2/2826</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (RNP) Z RWY 19L, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>St Louis</ENT>
              <ENT>Lambert-St Louis Intl</ENT>
              <ENT>2/2827</ENT>
              <ENT>2/27/12</ENT>
              <ENT>RNAV (GPS) RWY 29, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Cleveland</ENT>
              <ENT>Cleveland-Hopkins Intl</ENT>
              <ENT>2/2828</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 6L, Amdt 1A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Cleveland</ENT>
              <ENT>Cleveland-Hopkins Intl</ENT>
              <ENT>2/2830</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 24R, Amdt 3.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Cleveland</ENT>
              <ENT>Cleveland-Hopkins Intl</ENT>
              <ENT>2/2831</ENT>
              <ENT>2/22/12</ENT>
              <ENT>LDA/DME RWY 6R, Amdt 1A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>Kansas City</ENT>
              <ENT>Kansas City Intl</ENT>
              <ENT>2/2832</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 19L, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Cleveland</ENT>
              <ENT>Cleveland-Hopkins Intl</ENT>
              <ENT>2/2833</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 24L, Amdt 3.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KS</ENT>
              <ENT>Wichita</ENT>
              <ENT>Wichita Mid-Continent</ENT>
              <ENT>2/2834</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (RNP) Z RWY 1L, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Cleveland</ENT>
              <ENT>Cleveland-Hopkins Intl</ENT>
              <ENT>2/2835</ENT>
              <ENT>2/22/12</ENT>
              <ENT>LDA/DME RWY 24L, Amdt 1A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MO</ENT>
              <ENT>Kansas City</ENT>
              <ENT>Kansas City Intl</ENT>
              <ENT>2/2836</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) Y RWY 1L, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KS</ENT>
              <ENT>Wichita</ENT>
              <ENT>Wichita Mid-Continent</ENT>
              <ENT>2/2837</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 1R, Amdt 17A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KS</ENT>
              <ENT>Wichita</ENT>
              <ENT>Wichita Mid-Continent</ENT>
              <ENT>2/2839</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) Y RWY 1L, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Dayton</ENT>
              <ENT>James M Cox Dayton Intl</ENT>
              <ENT>2/2840</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) RWY 24L, Amdt 1A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Cleveland</ENT>
              <ENT>Cleveland-Hopkins Intl</ENT>
              <ENT>2/2844</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 6R, Amdt 2A.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="15581"/>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KS</ENT>
              <ENT>Wichita</ENT>
              <ENT>Wichita Mid-Continent</ENT>
              <ENT>2/2846</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) Y RWY 19L, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KS</ENT>
              <ENT>Wichita</ENT>
              <ENT>Wichita Mid-Continent</ENT>
              <ENT>2/2847</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 19L, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Dayton</ENT>
              <ENT>James M Cox Dayton Intl</ENT>
              <ENT>2/2850</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) RWY 6R, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Dayton</ENT>
              <ENT>James M Cox Dayton Intl</ENT>
              <ENT>2/2854</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 24R, Amdt 9.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Dayton</ENT>
              <ENT>James M Cox Dayton Intl</ENT>
              <ENT>2/2858</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) RWY 6L, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>AR</ENT>
              <ENT>Little Rock</ENT>
              <ENT>Adams Field</ENT>
              <ENT>2/2859</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 22L, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Dayton</ENT>
              <ENT>James M Cox Dayton Intl</ENT>
              <ENT>2/2860</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 24L, Amdt 9.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MI</ENT>
              <ENT>Detroit</ENT>
              <ENT>Detroit Metropolitan Wayne County</ENT>
              <ENT>2/2864</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS Y RWY 22R, Orig.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MI</ENT>
              <ENT>Detroit</ENT>
              <ENT>Detroit Metropolitan Wayne County</ENT>
              <ENT>2/2865</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS Z OR LOC RWY 22R, Amdt 2A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MI</ENT>
              <ENT>Detroit</ENT>
              <ENT>Detroit Metropolitan Wayne County</ENT>
              <ENT>2/2868</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 3R, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MI</ENT>
              <ENT>Detroit</ENT>
              <ENT>Detroit Metropolitan Wayne County</ENT>
              <ENT>2/2869</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 4R, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MI</ENT>
              <ENT>Detroit</ENT>
              <ENT>Detroit Metropolitan Wayne County</ENT>
              <ENT>2/2871</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 27R, Amdt 2.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2893</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 20R, Amdt 10.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2894</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) Y RWY 20R, Amdt 2.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2895</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (RNP) Z RWY 20R, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2896</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) Y RWY 20L, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2897</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 2R, Amdt 7.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2898</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS RWY 2R (CAT II), Amdt 7.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2899</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) Y RWY 2R, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2900</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (RNP) Z RWY 2R, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2901</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) Y RWY 2L, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2902</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) Y RWY 2C, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2903</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (RNP) Z RWY 2C, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2904</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 20L, Amdt 5.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2905</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (RNP) Z RWY 20L, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2906</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 2C, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2907</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 2L, Amdt 9.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2908</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS RWY 2L (CAT II), Amdt 9.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2909</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS RWY 2L (CAT III), Amdt 9.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2910</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS RWY 2R (CAT III), Amdt 7.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Nashville</ENT>
              <ENT>Nashville Intl</ENT>
              <ENT>2/2911</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (RNP) Z RWY 2L, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NC</ENT>
              <ENT>Charlotte</ENT>
              <ENT>Charlotte/Douglas Intl</ENT>
              <ENT>2/2920</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 18C, Amdt 10A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NC</ENT>
              <ENT>Charlotte</ENT>
              <ENT>Charlotte/Douglas Intl</ENT>
              <ENT>2/2921</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) Y RWY 18C, Amdt 3A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NC</ENT>
              <ENT>Charlotte</ENT>
              <ENT>Charlotte/Douglas Intl</ENT>
              <ENT>2/2922</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (RNP) Z RWY 18C, Orig-B.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NC</ENT>
              <ENT>Charlotte</ENT>
              <ENT>Charlotte/Douglas Intl</ENT>
              <ENT>2/2933</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS RWY 36C (CAT II), Amdt 16A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NC</ENT>
              <ENT>Charlotte</ENT>
              <ENT>Charlotte/Douglas Intl</ENT>
              <ENT>2/2934</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) Y RWY 36C, Amdt 3A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NC</ENT>
              <ENT>Charlotte</ENT>
              <ENT>Charlotte/Douglas Intl</ENT>
              <ENT>2/2941</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 36C, Amdt 16A.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="15582"/>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NC</ENT>
              <ENT>Charlotte</ENT>
              <ENT>Charlotte/Douglas Intl</ENT>
              <ENT>2/2942</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS RWY 36C (CAT III), Amdt 16A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NC</ENT>
              <ENT>Charlotte</ENT>
              <ENT>Charlotte/Douglas Intl</ENT>
              <ENT>2/2943</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (RNP) Z RWY 36C, Orig-C.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2946</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (RNP) Z RWY 18L, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2947</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS RWY 36C (CAT III), Amdt 41.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2948</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS OR LOC RWY 36L, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2949</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS OR LOC RWY 18C, Amdt 22.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2950</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (GPS) Y RWY 18C, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2951</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (GPS) Y RWY 18L, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2952</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS OR LOC RWY 18R, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2953</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS OR LOC RWY 36C, Amdt 41.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2954</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS OR LOC RWY 18L, Amdt 7.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2955</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (GPS) RWY 36C, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2956</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS OR LOC RWY 36R, Amdt 8.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2957</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS RWY 36R (CAT II), Amdt 8.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2958</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (RNP) Z RWY 36R, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2959</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (GPS) Y RWY 36L, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2960</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (RNP) Z RWY 36L, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2961</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (RNP) Z RWY 18C, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2962</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS RWY 18R (CAT II), Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2963</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS RWY 36C (CAT II), Amdt 41.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2964</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS RWY 36L (CAT II), Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2965</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (GPS) Y RWY 36R, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2966</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS RWY 36R (CAT III), Amdt 8.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2967</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (GPS) Y RWY 36C, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2968</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (RNP) Z RWY 36C, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2969</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (RNP) Z RWY 18R, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KY</ENT>
              <ENT>Covington</ENT>
              <ENT>Cincinnati/Northern Kentucky Intl</ENT>
              <ENT>2/2970</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (GPS) Y RWY 18R, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3079</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 17L, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3081</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS RWY 17L (CAT II), Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3082</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS RWY 17R (CAT II), Amdt 5.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3084</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS RWY 35L (CAT II), Amdt 6A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3085</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (RNP) Z RWY 35L, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3086</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 17R, Amdt 5.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3087</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS RWY 35R (CAT II), Amdt 1A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3088</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS RWY 36R (CAT II), Amdt 1A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3090</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 18R, Amdt 9.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3091</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 36R, Amdt 9A.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="15583"/>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3092</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 35L, Amdt 6A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3093</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) Y RWY 36L, Orig.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3094</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS RWY 35L (CAT III), Amdt 6A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3095</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 35R, Amdt 1A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3096</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) Y RWY 35L, Orig.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3097</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (RNP) Z RWY 36L, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3098</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (RNP) Z RWY 35R, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3099</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) Y RWY 36R, Orig.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3100</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) Y RWY 35R, Orig.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3101</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS RWY 36R (CAT III), Amdt 9A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Orlando</ENT>
              <ENT>Orlando Intl</ENT>
              <ENT>2/3104</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (RNP) Z RWY 36R, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Miami</ENT>
              <ENT>Miami Intl</ENT>
              <ENT>2/3113</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 9, Orig-C.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3114</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS OR LOC RWY 28R, Amdt 9.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Miami</ENT>
              <ENT>Miami Intl</ENT>
              <ENT>2/3116</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 26L, Amdt 15A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Miami</ENT>
              <ENT>Miami Intl</ENT>
              <ENT>2/3118</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 9, Amdt 9B.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Miami</ENT>
              <ENT>Miami Intl</ENT>
              <ENT>2/3119</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 27, Amdt 25.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3124</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (RNP) Z RWY 28L, Orig-B.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3126</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS RWY 28R (CAT II), Amdt 9.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3127</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS OR LOC RWY 28L, Amdt 10.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3128</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (GPS) Y RWY 28L, Amdt 4A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3129</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (GPS) Y RWY 28C, Amdt 4.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3130</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (RNP) Z RWY 28C, Orig-B.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3131</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS RWY 10L, Amdt 25A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3132</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS RWY 10L (CAT II), Amdt 25A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3133</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS RWY 10L (CAT III), Amdt 25A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3134</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (GPS) RWY 10L, Amdt 3.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3135</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (RNP) Z RWY 10C, Orig-B.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3136</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (GPS) Y RWY 10C, Amdt 4.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3137</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS RWY 10R (CAT II), Amdt 10D.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3138</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS OR LOC RWY 10R, Amdt 10D.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3139</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (GPS) Y RWY 10R, Amdt 3A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3140</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS RWY 10R (CAT III), Amdt 10D.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>PA</ENT>
              <ENT>Pittsburgh</ENT>
              <ENT>Pittsburgh Intl</ENT>
              <ENT>2/3141</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (RNP) Z RWY 10R, Orig-B.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Tampa</ENT>
              <ENT>Tampa Intl</ENT>
              <ENT>2/3163</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS OR LOC RWY 19L, Amdt 40.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Tampa</ENT>
              <ENT>Tampa Intl</ENT>
              <ENT>2/3165</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS RWY 1L (CAT III), Amdt 16A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Tampa</ENT>
              <ENT>Tampa Intl</ENT>
              <ENT>2/3166</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS RWY 1L (CAT II), Amdt 16A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Tampa</ENT>
              <ENT>Tampa Intl</ENT>
              <ENT>2/3167</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (GPS) RWY 1R, Amdt 2.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="15584"/>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Tampa</ENT>
              <ENT>Tampa Intl</ENT>
              <ENT>2/3168</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS RWY 19L (CAT II), Amdt 40.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Tampa</ENT>
              <ENT>Tampa Intl</ENT>
              <ENT>2/3169</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (GPS) Z RWY 19L, Amdt 2.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Tampa</ENT>
              <ENT>Tampa Intl</ENT>
              <ENT>2/3170</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS OR LOC RWY 19R, Amdt 5.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Tampa</ENT>
              <ENT>Tampa Intl</ENT>
              <ENT>2/3171</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS RWY 19L (SA CAT I), Amdt 40.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Tampa</ENT>
              <ENT>Tampa Intl</ENT>
              <ENT>2/3172</ENT>
              <ENT>2/6/12</ENT>
              <ENT>RNAV (RNP) Y RWY 19L, Amdt 1A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Tampa</ENT>
              <ENT>Tampa Intl</ENT>
              <ENT>2/3173</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS RWY 1L (SA CAT I), Amdt 16A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>FL</ENT>
              <ENT>Tampa</ENT>
              <ENT>Tampa Intl</ENT>
              <ENT>2/3174</ENT>
              <ENT>2/6/12</ENT>
              <ENT>ILS OR LOC RWY 1L, Amdt 16A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>UT</ENT>
              <ENT>Logan</ENT>
              <ENT>Logan-Cache</ENT>
              <ENT>2/3187</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) RWY 17, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>VT</ENT>
              <ENT>Lyndonville</ENT>
              <ENT>Caledonia County</ENT>
              <ENT>2/4811</ENT>
              <ENT>2/22/12</ENT>
              <ENT>NDB RWY 2, Amdt 4A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>VT</ENT>
              <ENT>Lyndonville</ENT>
              <ENT>Caledonia County</ENT>
              <ENT>2/4812</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 2, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TX</ENT>
              <ENT>Dallas</ENT>
              <ENT>Dallas Executive</ENT>
              <ENT>2/5875</ENT>
              <ENT>2/13/12</ENT>
              <ENT>ILS OR LOC RWY 31, Amdt 8B.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TX</ENT>
              <ENT>San Antonio</ENT>
              <ENT>San Antonio Intl</ENT>
              <ENT>2/6055</ENT>
              <ENT>2/13/12</ENT>
              <ENT>ILS OR LOC RWY 12R, ILS RWY 12R (CAT II), Amdt 14A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TX</ENT>
              <ENT>San Antonio</ENT>
              <ENT>San Antonio Intl</ENT>
              <ENT>2/6056</ENT>
              <ENT>2/13/12</ENT>
              <ENT>ILS OR LOC RWY 30L, Amdt 10A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>KS</ENT>
              <ENT>Wichita</ENT>
              <ENT>Wichita Mid-Continent</ENT>
              <ENT>2/6416</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 1L, ILS RWY 1L (CAT II), Amdt 3A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OK</ENT>
              <ENT>Tulsa</ENT>
              <ENT>Tulsa Intl</ENT>
              <ENT>2/6417</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 36R, ILS RWY 36R (CAT II), Amdt 39A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MN</ENT>
              <ENT>Minneapolis</ENT>
              <ENT>Minneapolis-St Paul Intl/Wold-Chamberlain</ENT>
              <ENT>2/6418</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 30L, ILS RWY 30L (CAT II), Amdt 44A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MN</ENT>
              <ENT>Minneapolis</ENT>
              <ENT>Minneapolis-St Paul Intl/Wold-Chamberlain</ENT>
              <ENT>2/6419</ENT>
              <ENT>2/23/12</ENT>
              <ENT>CONVERGING ILS RWY 30L, Orig.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MN</ENT>
              <ENT>Duluth</ENT>
              <ENT>Duluth Intl</ENT>
              <ENT>2/6423</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 9, ILS RWY 9 (CAT II), Amdt 21.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Wilmington</ENT>
              <ENT>Wilmington Air Park</ENT>
              <ENT>2/6427</ENT>
              <ENT>2/23/12</ENT>
              <ENT>NDB RWY 22R, Amdt 7D.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NE</ENT>
              <ENT>Omaha</ENT>
              <ENT>Eppley Airfield</ENT>
              <ENT>2/6429</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 32R, ILS RWY 32R (CAT II), ILS RWY 32R (CAT III), Orig-B.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Wilmington</ENT>
              <ENT>Wilmington Air Park</ENT>
              <ENT>2/6432</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS RWY 22L, ILS RWY 22L (CAT II), Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>OH</ENT>
              <ENT>Wilmington</ENT>
              <ENT>Wilmington Air Park</ENT>
              <ENT>2/6435</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 22R, ILS RWY 22R (CAT II), ILS RWY 22R (CAT III), Amdt 5.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MN</ENT>
              <ENT>Duluth</ENT>
              <ENT>Duluth Intl</ENT>
              <ENT>2/6442</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 27, Amdt 9A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MN</ENT>
              <ENT>Duluth</ENT>
              <ENT>Duluth Intl</ENT>
              <ENT>2/6443</ENT>
              <ENT>2/22/12</ENT>
              <ENT>COPTER ILS OR LOC RWY 27, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NE</ENT>
              <ENT>Omaha</ENT>
              <ENT>Eppley Airfield</ENT>
              <ENT>2/6444</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC/DME RWY 14R, ILS RWY 14R (CAT II), ILS RWY 14R (CAT III), Amdt 4A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MN</ENT>
              <ENT>Duluth</ENT>
              <ENT>Duluth Intl</ENT>
              <ENT>2/6445</ENT>
              <ENT>2/22/12</ENT>
              <ENT>COPTER ILS RWY 9, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>WI</ENT>
              <ENT>Milwaukee</ENT>
              <ENT>General Mitchell Intl</ENT>
              <ENT>2/6638</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 1L, ILS RWY 1L (CAT II), ILS RWY 1L (CAT III), Amdt 9.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TX</ENT>
              <ENT>Fort Worth</ENT>
              <ENT>Fort Worth Alliance</ENT>
              <ENT>2/6942</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 16L, ILS RWY 16L (CAT II), ILS RWY 16L (CAT III), Amdt 6.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TX</ENT>
              <ENT>Houston</ENT>
              <ENT>Houston/William P. Hobby</ENT>
              <ENT>2/6943</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 4, ILS RWY 4 (CAT II), ILS RWY 4 (CAT III), Amdt 40A.</ENT>
            </ROW>
            <ROW>
              <PRTPAGE P="15585"/>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>ME</ENT>
              <ENT>Bangor</ENT>
              <ENT>Bangor Intl</ENT>
              <ENT>2/7098</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 15, ILS RWY 15 (CAT II), ILS RWY 15 (CAT III), Amdt 6A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>IL</ENT>
              <ENT>Chicago/Lake In The Hills</ENT>
              <ENT>Lake In The Hills</ENT>
              <ENT>2/7102</ENT>
              <ENT>2/23/12</ENT>
              <ENT>Takeoff Minimums and Obstacle DP, Orig.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>AL</ENT>
              <ENT>Huntsville</ENT>
              <ENT>Huntsville Intl—Carl T Jones Field</ENT>
              <ENT>2/7139</ENT>
              <ENT>2/23/12</ENT>
              <ENT>VOR A, Amdt 12A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TX</ENT>
              <ENT>Dallas-Fort Worth</ENT>
              <ENT>Dallas-Fort Worth Intl</ENT>
              <ENT>2/7608</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS RWY 13R (SA CAT II), Amdt 8.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TN</ENT>
              <ENT>Knoxville</ENT>
              <ENT>McGhee Tyson</ENT>
              <ENT>2/7680</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) RWY 5L, Amdt 1A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TX</ENT>
              <ENT>Waco</ENT>
              <ENT>Waco Rgnl</ENT>
              <ENT>2/7711</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 32, Orig.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TX</ENT>
              <ENT>Port Aransas</ENT>
              <ENT>Mustang Beach</ENT>
              <ENT>2/7820</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) RWY 12, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TX</ENT>
              <ENT>Port Aransas</ENT>
              <ENT>Mustang Beach</ENT>
              <ENT>2/7821</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) RWY 30, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>TX</ENT>
              <ENT>Houston</ENT>
              <ENT>Ellington Field</ENT>
              <ENT>2/8123</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) RWY 35L, Orig-B.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NC</ENT>
              <ENT>Greensboro</ENT>
              <ENT>Piedmont Triad Intl</ENT>
              <ENT>2/8139</ENT>
              <ENT>2/27/12</ENT>
              <ENT>ILS RWY 5R (CAT II), Amdt 7A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NC</ENT>
              <ENT>Greensboro</ENT>
              <ENT>Piedmont Triad Intl</ENT>
              <ENT>2/8140</ENT>
              <ENT>2/27/12</ENT>
              <ENT>ILS RWY 5L (CAT III), Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NC</ENT>
              <ENT>Greensboro</ENT>
              <ENT>Piedmont Triad Intl</ENT>
              <ENT>2/8141</ENT>
              <ENT>2/27/12</ENT>
              <ENT>ILS OR LOC RWY 23R, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NC</ENT>
              <ENT>Greensboro</ENT>
              <ENT>Piedmont Triad Intl</ENT>
              <ENT>2/8142</ENT>
              <ENT>2/27/12</ENT>
              <ENT>RNAV (GPS) RWY 5L, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NC</ENT>
              <ENT>Greensboro</ENT>
              <ENT>Piedmont Triad Intl</ENT>
              <ENT>2/8143</ENT>
              <ENT>2/27/12</ENT>
              <ENT>ILS OR LOC RWY 5L, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NC</ENT>
              <ENT>Greensboro</ENT>
              <ENT>Piedmont Triad Intl</ENT>
              <ENT>2/8144</ENT>
              <ENT>2/27/12</ENT>
              <ENT>ILS RWY 5L (CAT II), Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NC</ENT>
              <ENT>Greensboro</ENT>
              <ENT>Piedmont Triad Intl</ENT>
              <ENT>2/8146</ENT>
              <ENT>2/27/12</ENT>
              <ENT>ILS OR LOC RWY 5R, Amdt 7A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NC</ENT>
              <ENT>Greensboro</ENT>
              <ENT>Piedmont Triad Intl</ENT>
              <ENT>2/8148</ENT>
              <ENT>2/27/12</ENT>
              <ENT>RNAV (GPS) RWY 23R, Orig-A.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>AZ</ENT>
              <ENT>Phoenix</ENT>
              <ENT>Phoenix Sky Harbor Intl</ENT>
              <ENT>2/8151</ENT>
              <ENT>2/27/12</ENT>
              <ENT>ILS OR LOC RWY 25L, Amdt 1E.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>AZ</ENT>
              <ENT>Phoenix</ENT>
              <ENT>Phoenix Sky Harbor Intl</ENT>
              <ENT>2/8152</ENT>
              <ENT>2/27/12</ENT>
              <ENT>ILS OR LOC RWY 7R, Amdt 2.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>UT</ENT>
              <ENT>Vernal</ENT>
              <ENT>Vernal Rgnl</ENT>
              <ENT>2/8182</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) RWY 34, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>SC</ENT>
              <ENT>Aiken</ENT>
              <ENT>Aiken Muni</ENT>
              <ENT>2/8273</ENT>
              <ENT>2/23/12</ENT>
              <ENT>RNAV (GPS) RWY 7, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>SC</ENT>
              <ENT>Aiken</ENT>
              <ENT>Aiken Muni</ENT>
              <ENT>2/8274</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC/DME RWY 7, Orig.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>IN</ENT>
              <ENT>Jeffersonville</ENT>
              <ENT>Clark Rgnl</ENT>
              <ENT>2/8287</ENT>
              <ENT>2/22/12</ENT>
              <ENT>NDB RWY 18, Amdt 1.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>IN</ENT>
              <ENT>Jeffersonville</ENT>
              <ENT>Clark Rgnl</ENT>
              <ENT>2/8288</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC RWY 18, Amdt 2.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>IN</ENT>
              <ENT>Auburn</ENT>
              <ENT>De Kalb County</ENT>
              <ENT>2/8896</ENT>
              <ENT>2/22/12</ENT>
              <ENT>VOR RWY 9, Amdt 7B.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>ND</ENT>
              <ENT>Bismarck</ENT>
              <ENT>Bismarck Muni</ENT>
              <ENT>2/8897</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC RWY 31, Amdt 33.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>MN</ENT>
              <ENT>Bemidji</ENT>
              <ENT>Bemidji Rgnl</ENT>
              <ENT>2/9058</ENT>
              <ENT>2/22/12</ENT>
              <ENT>RNAV (GPS) RWY 25, Orig.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>NH</ENT>
              <ENT>Portsmouth</ENT>
              <ENT>Portsmouth Intl at Peasea</ENT>
              <ENT>2/9382</ENT>
              <ENT>2/23/12</ENT>
              <ENT>Takeoff Minimums and Obstacle DP, Orig.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>AK</ENT>
              <ENT>Kodiak</ENT>
              <ENT>Kodiak</ENT>
              <ENT>2/9393</ENT>
              <ENT>2/22/12</ENT>
              <ENT>ILS OR LOC/DME Y RWY 25, Amdt 2.</ENT>
            </ROW>
            <ROW>
              <ENT I="01">5-Apr-12</ENT>
              <ENT>ME</ENT>
              <ENT>Brunswick</ENT>
              <ENT>Brunswick Executive</ENT>
              <ENT>2/9657</ENT>
              <ENT>2/23/12</ENT>
              <ENT>ILS OR LOC/DME RWY 1R, Orig.</ENT>
            </ROW>
          </GPOTABLE>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6006 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-13-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <DEPDOC>[Docket ID DoD-2010-OS-0183]</DEPDOC>
        <CFR>32 CFR Part 311</CFR>
        <SUBJECT>Privacy Act; Implementation</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of the Secretary, DoD.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The Office of the Secretary of Defense is exempting those records contained in DMDC 15 DoD, entitled “Armed Services Military Accession Testing” when the record includes the specific answers submitted and the answer key. Releasing this information to the individual will compromise the<PRTPAGE P="15586"/>objectivity or fairness of the test if the correct or incorrect answers are released.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective March 16, 2012.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Mrs. Cindy Allard at (703) 588-6830.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The Proposed Rule was published on January 3, 2011, in the<E T="04">Federal Register</E>(76 FR 56-57). During the comment period, two public comments were received.</P>
        <P>The first commenter asserted that the proposed Privacy Act exemption rule “could possibly be viewed as a violation of [the] constitutional rights * * * [of] U.S. citizen[s],” making reference to the Third, Fifth, Sixth, and Fourteenth Amendments of the Constitution. Also the first commenter commented that the provision “of the answers and/or answer keys should be at the discretion of the test taker, i.e., U.S. citizens.”</P>
        <P>The Privacy Act exemption rule addresses an individual's answers to the Armed Services Vocational Aptitude Battery (ASVAB) and the appropriate answer key, allowing the Department of Defense to exempt an individual's ASVAB answers and the answer key from the access provisions of the Privacy Act of 1974.</P>
        <P>The exemption rule is intended to ensure that individuals will not compromise the purpose of the ASVAB—to ascertain the skills and abilities of individuals joining the military or seeking to join the military. If individuals were allowed to have the specific responses to the questions as well as the correct answers, the Department of Defense would be unable to ensure that individuals were placed in jobs for which they had an aptitude, or more importantly, placed in jobs for which they had no aptitude. If individuals were allowed to have their individual responses as well as the correct answers, the integrity and scoring of the battery would be compromised rendering the testing worthless.</P>
        <P>Individuals taking the test are provided a copy of their scores along with an explanation of what the given scores indicate.</P>
        <P>The exemption rule is consistent with the Privacy Act, its underlying purposes, and the U.S. Constitution. Further, the rules published at 32 CFR part 311, The OSD Privacy Program, provide individuals an opportunity to appeal the denial of access to their records, which could include the consideration of alleged constitutional rights violations arising out of the denial of access to requested records.</P>
        <P>The second commenter did not address the proposed exemption rule but addressed the first commenter's comments.</P>
        <HD SOURCE="HD1">Executive Order 12866, “Regulatory Planning and Review” and Executive Order 13563, “Improving Regulation and Regulatory Review”</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense are not significant rules. The rules do not (1) Have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy; a sector of the economy; productivity; competition; jobs; the environment; public health or safety; or State, local, or tribal governments or communities; (2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another Agency; (3) Materially alter the budgetary impact of entitlements, grants, user fees, or loan programs, or the rights and obligations of recipients thereof; or (4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in these Executive orders.</P>
        <HD SOURCE="HD1">Public Law 96-354, “Regulatory Flexibility Act” (5 U.S.C. Chapter 6)</HD>
        <P>It has been determined that this Privacy Act rule for the Department of Defense does not have significant economic impact on a substantial number of small entities because it is concerned only with the administration of Privacy Act systems of records within the Department of Defense.</P>
        <HD SOURCE="HD1">Public Law 95-511, “Paperwork Reduction Act” (44 U.S.C. Chapter 35)</HD>
        <P>It has been determined that this Privacy Act rule for the Department of Defense imposes no information requirements beyond the Department of Defense and that the information collected within the Department of Defense is necessary and consistent with 5 U.S.C. 552a, known as the Privacy Act of 1974.</P>
        <HD SOURCE="HD1">Section 202, Public Law 104-4, “Unfunded Mandates Reform Act”</HD>
        <P>It has been determined that this Privacy Act rulemaking for the Department of Defense does not involve a Federal mandate that may result in the expenditure by State, local and tribal governments, in the aggregate, or by the private sector, of $100 million or more and that such rulemaking will not significantly or uniquely affect small governments.</P>
        <HD SOURCE="HD1">Executive Order 13132, “Federalism”</HD>
        <P>It has been determined that the Privacy Act rules for the Department of Defense do not have federalism implications. The rule does not have substantial direct effects on the States, on the relationship between the National Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 32 CFR Part 311</HD>
          <P>Privacy.</P>
        </LSTSUB>
        
        <P>Accordingly, 32 CFR part 311 is amended to read as follows:</P>
        
        <REGTEXT PART="311" TITLE="32">
          <PART>
            <HD SOURCE="HED">PART 311—OFFICE OF THE SECRETARY OF DEFENSE AND JOINT STAFF PRIVACY PROGRAM</HD>
          </PART>
          <AMDPAR>1. The authority citation for 32 CFR part 311 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>Pub. L. 93-579, 88 Stat. 1986 (5 U.S.C. 522a).</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="311" TITLE="32">
          <AMDPAR>2. Section 311.8 is amended by adding paragraph (c)(16) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 311.8</SECTNO>
            <SUBJECT>Procedures for exemptions.</SUBJECT>
            <STARS/>
            <P>(c) * * *</P>
            <P>(16)<E T="03">System identifier and name:</E>DMDC 15 DoD, Armed Services Military Accession Testing.</P>
            <P>(i)<E T="03">Exemption:</E>Testing or examination material used solely to determine individual qualifications for appointment or promotion in the Federal service or military service may be exempt pursuant to 5 U.S.C. 552a(k)(6), if the disclosure would compromise the objectivity or fairness of the test or examination process. Therefore, portions of the system of records may be exempt pursuant to 5 U.S.C. 552a(d).</P>
            <P>(ii)<E T="03">Authority:</E>5 U.S.C. 552a(k)(6).</P>
            <P>(iii)<E T="03">Reasons:</E>(A) An exemption is required for those portions of the Skill Qualification Test system pertaining to individual item responses and scoring keys to preclude compromise of the test and to ensure fairness and objectivity of the evaluation system.</P>
            <P>(B) From subsection (d)(1) when access to those portions of the Skill Qualification Test records would reveal the individual item responses and scoring keys. Disclosure of the individual item responses and scoring keys will compromise the objectivity and fairness of the test as well as the validity of future tests resulting in the Department being unable to use the testing battery as an individual assessment tool.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <SIG>
          <PRTPAGE P="15587"/>
          <DATED>Dated: February 28, 2012.</DATED>
          <NAME>Patricia L. Toppings,</NAME>
          <TITLE>OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6169 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <DEPDOC>[Docket ID DoD-2012-OS-0027]</DEPDOC>
        <CFR>32 CFR Part 311</CFR>
        <SUBJECT>Privacy Act of 1974; Implementation</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of the Secretary, DoD.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Direct final rule with request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Office of the Secretary of Defense is exempting those records contained in DMDC 11, entitled “Investigative Records Repository”, when investigatory material is compiled solely for the purpose of determining suitability, eligibility, or qualifications for Federal civilian employment, military service, Federal contracts, or access to classified information, but only to the extent that such material would reveal the identity of a confidential source. This direct final rule makes nonsubstantive changes to the Office of the Secretary Privacy Program rules. These changes will allow the Department to add an exemption rule to the Office of the Secretary of Defense Privacy Program rules that will exempt applicable Department records and/or material from certain portions of the Privacy Act. This change will allow the Department to move part of the Department's personnel security program records from the Defense Security Service Privacy Program to the Office of the Secretary of Defense Privacy Program. This will improve the efficiency and effectiveness of DoD's program by preserving the exempt status of the applicable records and/or material when the purposes underlying the exemption(s) are valid and necessary. This rule is being published as a direct final rule as the Department of Defense does not expect to receive any adverse comments, and so a proposed rule is unnecessary.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>

          <P>The rule is effective on May 25, 2012 unless comments are received that would result in a contrary determination. Comments will be accepted on or before May 15, 2012. If DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by docket number and title, by any of the following methods:</P>
          <P>•<E T="03">Federal Rulemaking Portal: http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Mail:</E>Federal Docket Management System Office, 4800 Mark Center Drive, East Tower, Suite 02G09, Alexandria, VA 22350-3100.</P>
          <P>
            <E T="03">Instructions:</E>All submissions received must include the agency name and docket number for this<E T="04">Federal Register</E>document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the Internet at<E T="03">http://www.regulations.gov</E>as they are received without change, including any personal identifiers or contact information.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ms. Cindy Allard at (703) 588-6830.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Direct Final Rule and Significant Adverse Comments</HD>

        <P>DoD has determined this rulemaking meets the criteria for a direct final rule because it involves nonsubstantive changes dealing with DoD's management of its Privacy Programs. DoD expects no opposition to the changes and no significant adverse comments. However, if DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>. 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 comment necessitates withdrawal of this direct final rule, DoD will consider whether it warrants a substantive response in a notice and comment process.</P>
        <HD SOURCE="HD1">Executive Order 12866, “Regulatory Planning and Review” and Executive Order 13563, “Improving Regulation and Regulatory Review”</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense are not significant rules. The rules do not (1) have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy; a sector of the economy; productivity; competition; jobs; the environment; public health or safety; or State, local, or tribal governments or communities; (2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another Agency; (3) Materially alter the budgetary impact of entitlements, grants, user fees, or loan programs, or the rights and obligations of recipients thereof; or (4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in these Executive orders.</P>
        <HD SOURCE="HD1">Public Law 96-354, “Regulatory Flexibility Act” (5 U.S.C. Chapter 6)</HD>
        <P>It has been determined that this Privacy Act rule for the Department of Defense does not have significant economic impact on a substantial number of small entities because it is concerned only with the administration of Privacy Act systems of records within the Department of Defense.</P>
        <HD SOURCE="HD1">Public Law 95-511, “Paperwork Reduction Act” (44 U.S.C. Chapter 35)</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense impose no additional information collection requirements on the public under the Paperwork Reduction Act of 1995.</P>
        <HD SOURCE="HD1">Section 202, Public Law 104-4, “Unfunded Mandates Reform Act”</HD>
        <P>It has been determined that this Privacy Act rulemaking for the Department of Defense does not involve a Federal mandate that may result in the expenditure by State, local and tribal governments, in the aggregate, or by the private sector, of $100 million or more and that such rulemaking will not significantly or uniquely affect small governments.</P>
        <HD SOURCE="HD1">Executive Order 13132, “Federalism”</HD>
        <P>It has been determined that the Privacy Act rules for the Department of Defense do not have federalism implications. The rule does not have substantial direct effects on the States, on the relationship between the National Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 32 CFR Part 311</HD>
          <P>Privacy.</P>
        </LSTSUB>
        
        <P>Accordingly, 32 CFR part 311 is amended as follows:</P>
        <REGTEXT PART="311" TITLE="32">
          <PART>
            <HD SOURCE="HED">PART 311—OFFICE OF THE SECRETARY OF DEFENSE AND JOINT STAFF PRIVACY PROGRAM</HD>
          </PART>
          <AMDPAR>1. The authority citation for 32 CFR part 311 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>Pub. L. 93-579, 88 Stat. 1986 (5 U.S.C. 522a).</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="311" TITLE="32">
          <PRTPAGE P="15588"/>
          <AMDPAR>2. Section 311.8 is amended by revising paragraph (c)(17) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 311.8</SECTNO>
            <SUBJECT>Procedures for exemptions.</SUBJECT>
            <STARS/>
            <P>(c) * * *</P>
            <P>(17)<E T="03">System identifier and name:</E>DMDC 13, Investigative Records Repository.</P>
            <P>(i)<E T="03">Exemptions:</E>(A) Investigatory material compiled for law enforcement purposes may be exempt pursuant to 5 U.S.C. 552a(k)(2). However, if an individual is denied any right, privilege, or benefit for which he would otherwise be entitled by Federal law or for which he would otherwise be eligible, as a result of the maintenance of such information, the individual will be provided access to such information except to the extent that disclosure would reveal the identity of a confidential source.</P>
            <P>(B) Records maintained in connection with providing protective services to the President and other individuals under 18 U.S.C. 3506, may be exempt pursuant to 5 U.S.C. 552a(k)(3).</P>
            <P>(C) Investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for Federal civilian employment, military service, Federal contracts, or access to classified information may be exempt pursuant to 5 U.S.C. 552a(k)(5), but only to the extent that such material would reveal the identity of a confidential source.</P>
            <P>(D) Any portion of this system that falls under the provisions of 5 U.S.C. 552a(k)(2), (k)(3), or (k)(5) may be exempt from the following subsections of 5 U.S.C. 552(c)(3), (d), (e)(1), (e)(4)(G), (H), and (I), and (f).</P>
            <P>(ii)<E T="03">Authority:</E>5 U.S.C. 552a(k)(2), (k)(3), or (k)(5).</P>
            <P>(iii)<E T="03">Reasons:</E>(A) From subsection (c)(3) because it will enable the Department to conduct certain investigations and relay law enforcement information without compromise of the information, protection of investigative techniques and efforts employed, and identities of confidential sources who might not otherwise come forward and who furnished information under an express promise that the sources' identity would be held in confidence (or prior to the effective date of the Act, under an implied promise).</P>
            <P>(B) From subsections (e)(1), (e)(4(G), (H), and (I) because it will provide protection against notification of investigatory material including certain reciprocal investigations and counterintelligence information, which might alert a subject to the fact that an investigation of that individual is taking place, and the disclosure of which would weaken the on-going investigation, reveal investigatory techniques, and place confidential informants in jeopardy who furnished information under an express promise that the source's identity would be held in confidence (or prior to the effective date of the Act, under an implied promise).</P>
            <P>(C) From subsections (d) and (f) because requiring OSD to grant access to records and agency rules for access and amendment of records would unfairly impede the agency's investigation of allegations of unlawful activities. To require OSD to confirm or deny the existence of a record pertaining to a requesting individual may in itself provide an answer to that individual relating to an on-going investigation. The investigation of possible unlawful activities would be jeopardized by agency rules requiring verification of record, disclosure of the record to the subject, and record amendment procedures.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: February 28, 2012.</DATED>
          <NAME>Patricia L. Toppings,</NAME>
          <TITLE>OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6167 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <DEPDOC>[Docket ID DoD-2012-OS-0028]</DEPDOC>
        <CFR>32 CFR Part 311</CFR>
        <SUBJECT>Privacy Act of 1974; Implementation</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of the Secretary, DoD.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Direct final rule with request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Office of the Secretary of Defense is exempting those records contained in DMDC 13 DoD, entitled “Defense Clearance and Investigations Index (DCII),” pertaining to investigatory material compiled for law enforcement purposes to enable OSD components to conduct certain investigations and relay law enforcement information without compromise of the information, protect investigative techniques and efforts employed, and identities of confidential sources who might not otherwise come forward and who furnished information under an express promise that the sources' identity would be held in confidence. The exemption will allow DoD to provide protection against notification of investigatory material including certain reciprocal investigations and counterintelligence information, which might alert a subject to the fact that an investigation of that individual is taking place, and the disclosure of which would weaken the on-going investigation, reveal investigatory techniques, and place confidential informants in jeopardy who furnished information under an express promise that the sources' identity would be held in confidence. Further, requiring OSD to grant access to records and agency rules for access and amendment of records would unfairly impede the investigation of allegations of unlawful activities. To require OSD to confirm or deny the existence of a record pertaining to a requesting individual may in itself provide an answer to that individual relating to an on-going investigation. The investigation of possible unlawful activities would be jeopardized by agency rules requiring verification of record, disclosure of the record to the subject, and record amendment procedures. This direct final rule makes nonsubstantive changes to the Office of the Secretary Privacy Program rules. These changes will allow the Department to add an exemption rule to the Office of the Secretary of Defense Privacy Program rules that will exempt applicable Department records and/or material from certain portions of the Privacy Act. This change will allow the Department to move part of the Department's personnel security program records from the Defense Security Service Privacy Program to the Office of the Secretary of Defense Privacy Program. This will improve the efficiency and effectiveness of DoD's program by preserving the exempt status of the applicable records and/or material when the purposes underlying the exemption(s) are valid and necessary. This rule is being published as a direct final rule as the Department of Defense does not expect to receive any adverse comments, and so a proposed rule is unnecessary.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>

          <P>The rule is effective on May 25, 2012 unless comments are received that would result in a contrary determination. Comments will be accepted on or before May 15, 2012. If DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>You may submit comments, identified by docket number and title, by any of the following methods:<PRTPAGE P="15589"/>
          </P>
          <P>•<E T="03">Federal Rulemaking Portal: http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Mail:</E>Federal Docket Management System Office, Mark Center Drive, East Tower, Suite 02G09, Alexandria, VA 22350-3100.</P>
          <P>
            <E T="03">Instructions:</E>All submissions received must include the agency name and docket number for this<E T="04">Federal Register</E>document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the Internet at<E T="03">http://www.regulations.gov</E>as they are received without change, including any personal identifiers or contact information.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ms. Cindy Allard at (703) 588-6830.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>This direct final rule is consistent with the rule previously published at 32 CFR part 321.13(h) and another rule is being published to remove and reserve 321.13(h).</P>
        <HD SOURCE="HD1">Direct Final Rule and Significant Adverse Comments</HD>

        <P>DoD has determined this rulemaking meets the criteria for a direct final rule because it involves nonsubstantive changes dealing with DoD's management of its Privacy Programs. DoD expects no opposition to the changes and no significant adverse comments. However, if DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>. 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 comment necessitates withdrawal of this direct final rule, DoD will consider whether it warrants a substantive response in a notice and comment process.</P>
        <HD SOURCE="HD1">Executive Order 12866, “Regulatory Planning and Review” and Executive Order 13563, “Improving Regulation and Regulatory Review”</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense are not significant rules. The rules do not (1) Have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy; a sector of the economy; productivity; competition; jobs; the environment; public health or safety; or State, local, or tribal governments or communities; (2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another Agency; (3) Materially alter the budgetary impact of entitlements, grants, user fees, or loan programs, or the rights and obligations of recipients thereof; or (4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in these Executive orders.</P>
        <HD SOURCE="HD1">Public Law 96-354, “Regulatory Flexibility Act” (5 U.S.C. Chapter 6)</HD>
        <P>It has been determined that this Privacy Act rule for the Department of Defense does not have significant economic impact on a substantial number of small entities because it is concerned only with the administration of Privacy Act systems of records within the Department of Defense.</P>
        <HD SOURCE="HD1">Public Law 95-511, “Paperwork Reduction Act” (44 U.S.C. Chapter 35)</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense impose no additional information collection requirements on the public under the Paperwork Reduction Act of 1995.</P>
        <HD SOURCE="HD1">Section 202, Public Law 104-4, “Unfunded Mandates Reform Act”</HD>
        <P>It has been determined that this Privacy Act rulemaking for the Department of Defense does not involve a Federal mandate that may result in the expenditure by State, local and tribal governments, in the aggregate, or by the private sector, of $100 million or more and that such rulemaking will not significantly or uniquely affect small governments.</P>
        <HD SOURCE="HD1">Executive Order 13132, “Federalism”</HD>
        <P>It has been determined that the Privacy Act rules for the Department of Defense do not have federalism implications. The rule does not have substantial direct effects on the States, on the relationship between the National Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 32 CFR Part 311</HD>
          <P>Privacy.</P>
        </LSTSUB>
        
        <P>Accordingly, 32 CFR part 311 is amended as follows:</P>
        <REGTEXT PART="311" TITLE="32">
          <PART>
            <HD SOURCE="HED">PART 311—OFFICE OF THE SECRETARY OF DEFENSE AND JOINT STAFF PRIVACY PROGRAM</HD>
          </PART>
          <AMDPAR>1. The authority citation for 32 CFR part 311 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>Pub. L. 93-579, 88 Stat. 1986 (5 U.S.C. 522a).</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="311" TITLE="32">
          <AMDPAR>2. Section 311.8 is amended by revising paragraph (c)(20) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 311.8</SECTNO>
            <SUBJECT>Procedures for exemptions.</SUBJECT>
            <STARS/>
            <P>(c) * * *</P>
            <P>(20)<E T="03">System identifier and name:</E>DMDC 13 DoD, Defense Clearance and Investigations Index.</P>
            <P>(i)<E T="03">Exemptions:</E>Investigatory material compiled for law enforcement purposes may be exempt pursuant to 5 U.S.C. 552a(k)(2). However, if an individual is denied any right, privilege, or benefit for which he would otherwise be entitled by Federal law or for which he would otherwise be eligible, as a result of the maintenance of such information, the individual will be provided access to such information except to the extent that disclosure would reveal the identity of a confidential source. Any portion of this system that falls under the provisions of 5 U.S.C. 552a(k)(2) may be exempt from the following subjections of 5 U.S.C. 552a(c)(3); (d); (e)(1); (e)(4)(G), (H), and (I) and (f).</P>
            <P>(ii)<E T="03">Authority:</E>5 U.S.C. 552a(k)(2).</P>
            <P>(iii)<E T="03">Reasons:</E>(A) From subsection (c)(3) because it will enable OSD components to conduct certain investigations and relay law enforcement information without compromise of the information, protection of investigative techniques and efforts employed, and identities of confidential sources who might not otherwise come forward and who furnished information under an express promise that the sources' identity would be held in confidence (or prior to the effective date of the Act, under an implied promise).</P>
            <P>(B) From subsections (e)(1), (e)(4)(G), (H), and (I) because it will provide protection against notification of investigatory material including certain reciprocal investigations and counterintelligence information, which might alert a subject to the fact that an investigation of that individual is taking place, and the disclosure of which would weaken the on-going investigation, reveal investigatory techniques, and place confidential informants in jeopardy who furnished information under an express promise that the sources' identity would be held in confidence (or prior to the effective date of the Act, under an implied promise).</P>

            <P>(C) From subsections (d) and (f) because requiring OSD to grant access to records and agency rules for access and amendment of records would unfairly impede the investigation of allegations<PRTPAGE P="15590"/>of unlawful activities. To require OSD to confirm or deny the existence of a record pertaining to a requesting individual may in itself provide an answer to that individual relating to an on-going investigation. The investigation of possible unlawful activities would be jeopardized by agency rules requiring verification of record, disclosure of the record to the subject, and record amendment procedures.</P>
          </SECTION>
        </REGTEXT>
        <STARS/>
        <SIG>
          <DATED>Dated: February 28, 2012.</DATED>
          <NAME>Patricia L. Toppings,</NAME>
          <TITLE>OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6168 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <DEPDOC>[Docket ID DoD-2012-OS-0035]</DEPDOC>
        <CFR>32 CFR Part 319</CFR>
        <SUBJECT>Privacy Act; Implementation</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Defense Intelligence Agency, DoD.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Direct final rule with request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Defense Intelligence Agency (DIA) is proposing to update the DIA Privacy Act Program by adding an exemption to accurately describe the basis for exempting the records in the system of records notice LDIA 0660, Security and Counterintelligence Records. This direct final rule makes nonsubstantive changes to the Defense Intelligence Agency (DIA) Privacy Program rules. These changes will allow the Department to add an exemption rule to the DIA Privacy Program rules that will exempt applicable Department records and/or material from certain portions of the Privacy Act. This will improve the efficiency and effectiveness of DoD's program by preserving the exempt status of the applicable records and/or material when the purposes underlying the exemption(s) are valid and necessary. This rule is being published as a direct final rule as the Department of Defense does not expect to receive any adverse comments, and so a proposed rule is unnecessary.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>

          <P>The rule is effective on May 25, 2012 unless comments are received that would result in a contrary determination. Comments will be accepted on or before May 15, 2012. If DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by docket number and title, by any of the following methods:</P>
          <P>•<E T="03">Federal Rulemaking Portal: http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Mail:</E>Federal Docket Management System Office, 4800 Mark Center Drive, 2nd Floor, East Tower, Suite 02G09, Alexandria, VA 22350-3100.</P>
          <P>
            <E T="03">Instructions:</E>All submissions received must include the agency name and docket number for this<E T="04">Federal Register</E>document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the Internet at<E T="03">http://www.regulations.gov</E>as they are received without change, including any personal identifiers or contact information.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ms. Theresa Lowery at (202) 231-1193.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Direct Final Rule and Significant Adverse Comments</HD>

        <P>DoD has determined this rulemaking meets the criteria for a direct final rule because it involves nonsubstantive changes dealing with DoD's management of its Privacy Progams. DoD expects no opposition to the changes and no significant adverse comments. However, if DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>. 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 comment necessitates withdrawal of this direct final rule, DoD will consider whether it warrants a substantive response in a notice and comment process.</P>
        <HD SOURCE="HD1">Executive Order 12866, “Regulatory Planning and Review” and Executive Order 13563, “Improving Regulation and Regulatory Review”</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense are not significant rules. The rules do not (1) have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy; a sector of the economy; productivity; competition; jobs; the environment; public health or safety; or State, local, or tribal governments or communities; (2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another Agency; (3) Materially alter the budgetary impact of entitlements, grants, user fees, or loan programs, or the rights and obligations of recipients thereof; or (4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in these Executive orders.</P>
        <HD SOURCE="HD1">Public Law 96-354, “Regulatory Flexibility Act” (5 U.S.C. Chapter 6)</HD>
        <P>It has been determined that this Privacy Act rule for the Department of Defense does not have significant economic impact on a substantial number of small entities because it is concerned only with the administration of Privacy Act systems of records within the Department of Defense.</P>
        <HD SOURCE="HD1">Public Law 95-511, “Paperwork Reduction Act” (44 U.S.C. Chapter 35)</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense impose no additional information collection requirements on the public under the Paperwork Reduction Act of 1995.</P>
        <HD SOURCE="HD1">Section 202, Public Law 104-4, “Unfunded Mandates Reform Act”</HD>
        <P>It has been determined that this Privacy Act rulemaking for the Department of Defense does not involve a Federal mandate that may result in the expenditure by State, local and tribal governments, in the aggregate, or by the private sector, of $100 million or more and that such rulemaking will not significantly or uniquely affect small governments.</P>
        <HD SOURCE="HD1">Executive Order 13132, “Federalism”</HD>
        <P>It has been determined that the Privacy Act rules for the Department of Defense do not have federalism implications. The rule does not have substantial direct effects on the States, on the relationship between the National Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 32 CFR Part 319</HD>
          <P>Privacy.</P>
        </LSTSUB>
        
        <P>Accordingly, 32 CFR part 319 is amended as follows:</P>
        <REGTEXT PART="319" TITLE="32">
          <PART>
            <HD SOURCE="HED">PART 319—DEFENSE INTELLIGENCE AGENCY PRIVACY PROGRAM</HD>
          </PART>
          <AMDPAR>1. The authority citation for 32 CFR Part 319.13 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>Pub. L. 93-579, 88 Stat. 1896 (5 U.S.C. 552a).</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="319" TITLE="32">
          <PRTPAGE P="15591"/>
          <AMDPAR>2. Section 319.13 is amended by revising paragraph (e) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 319.13</SECTNO>
            <SUBJECT>Specific exemptions.</SUBJECT>
            <STARS/>
            <P>(e)<E T="03">System identifier and name:</E>LDIA 0660, Security and Counterintelligence Files.</P>
            <P>(1)<E T="03">Exemption:</E>Any portion of this record system which falls within the provisions of 5 U.S.C. 552a(k)(2), (k)(5) and (k)(6) may be exempt from the following subsections of 5 U.S.C. 552a: (c)(3), (d), (e)(1), (e)(4)(G), (e)(4)(H), and (e)(4)(I).</P>
            <P>(2)<E T="03">Authority:</E>5 U.S.C. 552a(k)(2), (k)(5) and (k)(6).</P>
            <P>(3)<E T="03">Reasons:</E>The reasons for asserting these exemptions are to ensure the integrity of the adjudication process used by the Agency to determine the suitability, eligibility or qualification for Federal service with the Agency and to make determinations concerning the questions of access to classified materials and activities. The proper execution of this function requires that the Agency have the ability to obtain candid and necessary information in order to fully develop or resolve pertinent information developed in the process. Potential sources, out of fear or retaliation, exposure or other action, may be unwilling to provide needed information or may not be sufficiently frank to be a value in personnel screening, thereby seriously interfering with the proper conduct and adjudication of such matters; and protects information used for medical, psychological evaluations, security questionnaires and polygraph testing.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: February 28, 2012.</DATED>
          <NAME>Patricia L. Toppings,</NAME>
          <TITLE>OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6176 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <DEPDOC>[Docket ID DOD-2012-OS-0034]</DEPDOC>
        <CFR>32 CFR Part 319</CFR>
        <SUBJECT>Privacy Act; Implementation</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Defense Intelligence Agency, DoD.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Direct final rule with request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Defense Intelligence Agency is deleting an exemption rule for LDIA 0275, “DoD Hotline Referrals” in its entirety. This direct final rule makes nonsubstantive changes to the Defense Intelligence Agency Privacy Program rules. These changes will allow the Department to transfer these records to another system of records, LDIA 0271.This will improve the efficiency and effectiveness of DoD's program by preserving the exempt status of the records when the purposes underlying the exemption are valid and necessary to protect the contents of the records. This rule is being published as a direct final rule as the Department of Defense does not expect to receive any adverse comments, and so a proposed rule is unnecessary.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>

          <P>The rule is effective on May 25, 2012 unless comments are received that would result in a contrary determination. Comments will be accepted on or before May 15, 2012. If DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by docket number and title, by any of the following methods.</P>
          <P>•<E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Mail:</E>Federal Docket management System Office, 4800 Mark Center Drive, 2nd Floor, East Tower, Suite 02G09, Alexandria, VA 22350-3100.</P>
          <P>
            <E T="03">Instructions:</E>All submissions received must include the agency name and docket number or Regulatory Information Number (RIN) for this<E T="04">Federal Register</E>document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the Internet at<E T="03">http://www.regulations.gov</E>as they are received without change, including any personal identifiers or contact information.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ms. Theresa Lowery at (202) 231-1193.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Direct Final Rule and Significant Adverse Comments</HD>

        <P>DoD has determined this rulemaking meets the criteria for a direct final rule because it involves nonsubstantive changes dealing with DoD's management of its Privacy Programs. DoD expects no opposition to the changes and no significant adverse comments. However, if DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>. 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 comment necessitates withdrawal of this direct final rule, DoD will consider whether it warrants a substantive response in a notice and comment process.</P>
        <HD SOURCE="HD1">Executive Order 12866, “Regulatory Planning and Review” and Executive Order 13563, “Improving Regulation and Regulatory Review”</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense are not significant rules. The rules do not (1) Have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy; a sector of the economy; productivity; competition; jobs; the environment; public health or safety; or State, local, or tribal governments or communities; (2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another Agency; (3) Materially alter the budgetary impact of entitlements, grants, user fees, or loan programs, or the rights and obligations of recipients thereof; or (4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in these Executive orders.</P>
        <HD SOURCE="HD1">Public Law 96-354, “Regulatory Flexibility Act” (5 U.S.C. Chapter 6)</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense do not have significant economic impact on a substantial number of small entities because they are concerned only with the administration of Privacy Act systems of records within the Department of Defense.</P>
        <HD SOURCE="HD1">Public Law 96-511, “Paperwork Reduction Act” (44 U.S.C. Chapter 35)</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense impose no additional information collection requirements on the public under the Paperwork Reduction Act of 1995.</P>
        <HD SOURCE="HD1">Section 202, Public Law 104-4, “Unfunded Mandates Reform Act”</HD>

        <P>It has been determined that the Privacy Act rulemaking for the Department of Defense does not involve a Federal mandate that may result in the expenditure by State, local and tribal governments, in the aggregate, or by the private sector, of $100 million or more and that such rulemaking will not significantly or uniquely affect small governments.<PRTPAGE P="15592"/>
        </P>
        <HD SOURCE="HD1">Executive Order 13132, “Federalism”</HD>
        <P>It has been determined that the Privacy Act rules for the Department of Defense do not have federalism implications. The rules do not have substantial direct effects on the States, on the relationship between the National Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 32 CFR Part 319</HD>
          <P>Privacy.</P>
        </LSTSUB>
        
        <P>Accordingly, 32 CFR part 319 is amended as follows:</P>
        <REGTEXT PART="319" TITLE="32">
          <PART>
            <HD SOURCE="HED">PART 319—DEFENSE INTELLIGENCE AGENCY PRIVACY PROGRAM</HD>
          </PART>
          <AMDPAR>1. The authority citation for 32 CFR part 319 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>Pub. L. 93-579, 5 U.S.C. 552a(f) and (k).</P>
          </AUTH>
          <SECTION>
            <SECTNO>§ 319.13</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. In § 319.13, remove and reserve paragraph (d).</AMDPAR>
        </REGTEXT>
        <SIG>
          <DATED>Dated: February 28, 2012.</DATED>
          <NAME>Patricia L. Toppings,</NAME>
          <TITLE>OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6174 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <DEPDOC>[Docket ID DoD-2012-OS-0029]</DEPDOC>
        <CFR>32 CFR Part 319</CFR>
        <SUBJECT>Privacy Act; Implementation</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Defense Intelligence Agency, DoD.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Direct final rule with request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Defense Intelligence Agency (DIA) is adding a new exemption rule for LDIA 0010, entitled “Information Requests-Freedom of Information Act (FOIA) and Privacy Act” to exempt those records that have been previously claimed for the records in another Privacy Act system of records. To the extent that copies of exempt records from those other systems of records are entered into these case records, DIA hereby claims the same exemptions for the records as claimed in the original primary system of records of which they are a part. This direct final rule makes nonsubstantive changes to the Defense Intelligence Agency Program rules. This will improve the efficiency and effectiveness of DoD's program by allowing those records that are only exempt from pertinent provisions of law, to the extent such provisions have been identified and an exemption claimed for the original record and the purposes underlying the exemption for the original record, to still pertain to the record which is now contained in this system of records. This rule is being published as a direct final rule as the Department of Defense does not expect to receive any adverse comments, and so a proposed rule is unnecessary.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>

          <P>The rule is effective on May 25, 2012 unless comments are received that would result in a contrary determination. Comments will be accepted on or before May 15, 2012. If DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by docket number and title, by any of the following methods.</P>
          <P>•<E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Mail:</E>Federal Docket Management System Office, 4800 Mark Center Drive, 2nd Floor, East Tower, Suite 02G09, Alexandria, VA 22350-3100.</P>
          <P>
            <E T="03">Instructions:</E>All submissions received must include the agency name and docket number or Regulatory Information Number (RIN) for this<E T="04">Federal Register</E>document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the Internet at<E T="03">http://www.regulations.gov</E>as they are received without change, including any personal identifiers or contact information.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ms. Theresa Lowery at (202)231-1193.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Direct Final Rule and Significant Adverse Comments</HD>

        <P>DoD has determined this rulemaking meets the criteria for a direct final rule because it involves nonsubstantive changes dealing with DoD's management of its Privacy Progams. DoD expects no opposition to the changes and no significant adverse comments. However, if DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>. 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 comment necessitates withdrawal of this direct final rule, DoD will consider whether it warrants a substantive response in a notice and comment process.</P>
        <HD SOURCE="HD2">Executive Order 12866, “Regulatory Planning and Review” and Executive Order 13563, “Improving Regulation and Regulatory Review”</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense are not significant rules. The rules do not (1) have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy; a sector of the economy; productivity; competition; jobs; the environment; public health or safety; or State, local, or tribal governments or communities; (2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another Agency; (3) Materially alter the budgetary impact of entitlements, grants, user fees, or loan programs, or the rights and obligations of recipients thereof; or (4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in these Executive orders.</P>
        <HD SOURCE="HD2">Public Law 96-354, “Regulatory Flexibility Act” (5 U.S.C. Chapter 6)</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense do not have significant economic impact on a substantial number of small entities because they are concerned only with the administration of Privacy Act systems of records within the Department of Defense.</P>
        <HD SOURCE="HD2">Public Law 96-511, “Paperwork Reduction Act” (44 U.S.C. Chapter 35)</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense impose no additional information collection requirements on the public under the Paperwork Reduction Act of 1995.</P>
        <HD SOURCE="HD2">Section 202, Public Law 104-4, “Unfunded Mandates Reform Act”</HD>

        <P>It has been determined that the Privacy Act rulemaking for the Department of Defense does not involve a Federal mandate that may result in the expenditure by State, local and tribal governments, in the aggregate, or by the private sector, of $100 million or more and that such rulemaking will not significantly or uniquely affect small governments.<PRTPAGE P="15593"/>
        </P>
        <HD SOURCE="HD2">Executive Order 13132, “Federalism”</HD>
        <P>It has been determined that the Privacy Act rules for the Department of Defense do not have federalism implications. The rules do not have substantial direct effects on the States, on the relationship between the National Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 32 CFR Part 319</HD>
          <P>Privacy.</P>
        </LSTSUB>
        
        <P>Accordingly, 32 CFR part 319 amended as follows:</P>
        <REGTEXT PART="319" TITLE="32">
          <PART>
            <HD SOURCE="HED">PART 319—DEFENSE INTELLIGENCE AGENCY PRIVACY PROGRAM</HD>
          </PART>
          <AMDPAR>1. The authority citation for 32 CFR part 319 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>Pub. L. 93-579, 5 U.S.C. 552a(f) and (k).</P>
          </AUTH>
        </REGTEXT>
        
        <AMDPAR>2. Section 319.13 is amended by adding paragraph (j) to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 319.13</SECTNO>
          <SUBJECT>Specific exemptions.</SUBJECT>
          <STARS/>
          <P>(j)<E T="03">System identifier and name:</E>LDIA 0010, Information Requests-Freedom of Information Act (FOIA) and Privacy Act.</P>
          <P>(1)<E T="03">Exemption:</E>During the course of information requests-FOIA and Privacy Act actions, exempt records/material from other systems of records may become part of this system of records. For such records/material, DIA hereby claims the same exemptions as is claimed for the systems from which such records/material are derived.</P>
          <P>(2)<E T="03">Authority:</E>5 U.S.C. 552a(k)(2) through (k)(7).</P>
          <P>(3)<E T="03">Reasons:</E>Records in a system of records are only exempted from pertinent provisions of 5 U.S.C. 552a to the extent such provisions are identified and an exemption claimed. In general, exemptions claimed protect properly classified information relating to national defense and foreign policy; avoid interference during the conduct of criminal, civil, or administrative actions or investigations; ensure protective services provided the President and others are not compromised; protect the identity of confidential sources incident to Federal employment, military service, contract, and security clearance determinations; preserve the confidentiality and integrity of Federal testing materials; and safeguard evaluation materials used for military promotions when furnished by a confidential source. The exemption rule(s) for the systems of records from which the records/materials was derived will identify the specific reasons why the records/materials are exempt from provisions of 5 U.S.C. 552a.</P>
        </SECTION>
        <SIG>
          <DATED>Dated: February 28, 2012.</DATED>
          <NAME>Patricia L. Toppings,</NAME>
          <TITLE>OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6172 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <DEPDOC>[Docket ID DOD-2012-OS-0033]</DEPDOC>
        <CFR>32 CFR Part 319</CFR>
        <SUBJECT>Privacy Act; Implementation</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Defense Intelligence Agency, DoD.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Direct final rule with request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Defense Intelligence Agency (DIA) is adding a new exemption rule for LDIA 0900, entitled “Accounts Receivable, Indebtedness and Claims” to exempt those records that have been previously claimed for the records in another Privacy Act system of records. To the extent that copies of exempt records from those other systems of records are entered into these case records, DIA hereby claims the same exemptions for the records as claimed in the original primary system of records of which they are a part. This direct final rule makes nonsubstantive changes to the Defense Intelligence Agency Program rules. These changes will allow the Department to exempt records from certain portions of the Privacy Act. This will improve the efficiency and effectiveness of DoD's program by preserving the exempt status of the records when the purposes underlying the exemption for the original records are still valid and necessary to protect the contents of the records. This rule is being published as a direct final rule as the Department of Defense does not expect to receive any adverse comments, and so a proposed rule is unnecessary.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>

          <P>The rule is effective on May 25, 2012 unless comments are received that would result in a contrary determination. Comments will be accepted on or before May 15, 2012. If DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by docket number and title, by any of the following methods.</P>
          <P>•<E T="03">Federal eRulemaking Portal:  http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Mail:</E>Federal Docket management System Office, 4800 Mark Center Drive, 2nd Floor, East Tower, Suite 02G09, Alexandria, VA 22350-3100.</P>
          <P>
            <E T="03">Instructions:</E>All submissions received must include the agency name and docket number or Regulatory Information Number (RIN) for this<E T="04">Federal Register</E>document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the Internet at<E T="03">http://www.regulations.gov</E>as they are received without change, including any personal identifiers or contact information.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ms. Theresa Lowery at (202) 231-1193.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Direct Final Rule and Significant Adverse Comments</HD>

        <P>DoD has determined this rulemaking meets the criteria for a direct final rule because it involves nonsubstantive changes dealing with DoD's management of its Privacy Progams. DoD expects no opposition to the changes and no significant adverse comments. However, if DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>. 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 comment necessitates withdrawal of this direct final rule, DoD will consider whether it warrants a substantive response in a notice and comment process.</P>
        <HD SOURCE="HD2">Executive Order 12866, “Regulatory Planning and Review” and Executive Order 13563, “Improving Regulation and Regulatory Review”</HD>

        <P>It has been determined that Privacy Act rules for the Department of Defense are not significant rules. The rules do not (1) have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy; a sector of the economy; productivity; competition; jobs; the environment; public health or safety; or State, local, or tribal governments or communities; (2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another Agency; (3) Materially alter the<PRTPAGE P="15594"/>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 these Executive orders.</P>
        <HD SOURCE="HD2">Public Law 96-354, “Regulatory Flexibility Act” (5 U.S.C. Chapter 6)</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense do not have significant economic impact on a substantial number of small entities because they are concerned only with the administration of Privacy Act systems of records within the Department of Defense.</P>
        <HD SOURCE="HD2">Public Law 96-511, “Paperwork Reduction Act” (44 U.S.C. Chapter 35)</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense impose no additional information collection requirements on the public under the Paperwork Reduction Act of 1995.</P>
        <HD SOURCE="HD2">Section 202, Public Law 104-4, “Unfunded Mandates Reform Act”</HD>
        <P>It has been determined that the Privacy Act rulemaking for the Department of Defense does not involve a Federal mandate that may result in the expenditure by State, local and tribal governments, in the aggregate, or by the private sector, of $100 million or more and that such rulemaking will not significantly or uniquely affect small governments.</P>
        <HD SOURCE="HD2">Executive Order 13132, “Federalism”</HD>
        <P>It has been determined that the Privacy Act rules for the Department of Defense do not have federalism implications. The rules do not have substantial direct effects on the States, on the relationship between the National Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 32 CFR Part 319</HD>
          <P>Privacy.</P>
        </LSTSUB>
        
        <P>Accordingly, 32 CFR part 319 amended as follows:</P>
        <REGTEXT PART="319" TITLE="32">
          <PART>
            <HD SOURCE="HED">PART 319—DEFENSE INTELLIGENCE AGENCY PRIVACY PROGRAM</HD>
          </PART>
          <AMDPAR>1. The authority citation for 32 CFR part 319 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>Pub. L. 93-579, 5 U.S.C. 552a(f) and (k).</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="319" TITLE="32">
          <AMDPAR>2. Section 319.13 is amended by revising paragraph (i) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 319.13</SECTNO>
            <SUBJECT>Specific exemptions.</SUBJECT>
            <STARS/>
            <P>(i)<E T="03">System identifier and name:</E>LDIA 0900, Accounts Receivable, Indebtedness and Claims.</P>
            <P>(1)<E T="03">Exemption:</E>During the course of accounts receivable, indebtedness or claims actions, exempt materials from other systems of records may in turn become part of the case record in this system. To the extent that copies of exempt records from those “other” systems of records are entered into this system, the DIA hereby claims the same exemptions for the records from those “other” systems that are entered into this system, as claimed for the original primary system of which they are a part.</P>
            <P>(2)<E T="03">Authority:</E>5 U.S.C. 552a(k)(2) through (k)(7).</P>
            <P>(3)<E T="03">Reasons:</E>Records are only exempt from pertinent provisions of 5 U.S.C. 552a to the extent such provisions have been identified and an exemption claimed for the original record and the purposes underlying the exemption for the original record still pertain to the record which is now contained in this system of records. In general, the exemptions were claimed in order to protect properly classified information relating to national defense and foreign policy, to avoid interference during the conduct of criminal, civil, or administrative actions or investigations, to ensure protective services provided the President and others are not compromised, to protect the identity of confidential sources incident to Federal employment, military service, contract, and security clearance determinations, to preserve the confidentiality and integrity of Federal testing materials, and to safeguard evaluation materials used for military promotions when furnished by a confidential source. The exemption rule for the original records will identify the specific reasons why the records are exempt from specific provisions of 5 U.S.C. 552a.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: February 28, 2012.</DATED>
          <NAME>Patricia L. Toppings,</NAME>
          <TITLE>OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6173 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <DEPDOC>[Docket ID DoD-2012-OS-0030]</DEPDOC>
        <CFR>32 CFR Part 319</CFR>
        <SUBJECT>Privacy Act; Implementation</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Defense Intelligence Agency, DoD.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Direct final rule with request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Defense Intelligence Agency is deleting an exemption rule for LDIA 0800, “Operation Record System” in its entirety. This direct final rule makes nonsubstantive changes to the Defense Intelligence Agency Privacy Program rules. These changes will allow the Department to transfer these records to another system of records, LDIA 10-0002, “Foreign Intelligence and Counterintelligence Operation Records” (June 15, 2010, 75 FR 33791). This will improve the efficiency and effectiveness of DoD's program by preserving the exempt status of the records when the purposes underlying the exemption are valid and necessary to protect the contents of the records. This rule is being published as a direct final rule as the Department of Defense does not expect to receive any adverse comments, and so a proposed rule is unnecessary.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>

          <P>The rule is effective on May 25, 2012 unless comments are received that would result in a contrary determination. Comments will be accepted on or before May 15, 2012. If DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by docket number and title, by any of the following methods.</P>
          <P>•<E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Mail:</E>Federal Docket management System Office, 4800 Mark Center Drive, 2nd Floor, East Tower, Suite 02G09, Alexandria, VA 22350-3100.</P>
          <P>
            <E T="03">Instructions:</E>All submissions received must include the agency name and docket number or Regulatory Information Number (RIN) for this<E T="04">Federal Register</E>document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the Internet at<E T="03">http://www.regulations.gov</E>as they are received without change, including any personal identifiers or contact information.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ms. Theresa Lowery at (202) 231-1193.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Direct Final Rule and Significant Adverse Comments</HD>

        <P>DoD has determined this rulemaking meets the criteria for a direct final rule because it involves nonsubstantive changes dealing with DoD's<PRTPAGE P="15595"/>management of its Privacy Progams. DoD expects no opposition to the changes and no significant adverse comments. However, if DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>. 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 comment necessitates withdrawal of this direct final rule, DoD will consider whether it warrants a substantive response in a notice and comment process.</P>
        <HD SOURCE="HD2">Executive Order 12866, “Regulatory Planning and Review” and Executive Order 13563, “Improving Regulation and Regulatory Review”</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense are not significant rules. The rules do not (1) Have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy; a sector of the economy; productivity; competition; jobs; the environment; public health or safety; or State, local, or tribal governments or communities; (2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another Agency; (3) Materially alter the budgetary impact of entitlements, grants, user fees, or loan programs, or the rights and obligations of recipients thereof; or (4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in these Executive orders.</P>
        <HD SOURCE="HD2">Public Law 96-354, “Regulatory Flexibility Act” (5 U.S.C. Chapter 6)</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense do not have significant economic impact on a substantial number of small entities because they are concerned only with the administration of Privacy Act systems of records within the Department of Defense.</P>
        <HD SOURCE="HD2">Public Law 96-511, “Paperwork Reduction Act” (44 U.S.C. Chapter 35)</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense impose no additional information collection requirements on the public under the Paperwork Reduction Act of 1995.</P>
        <HD SOURCE="HD2">Section 202, Public Law 104-4, “Unfunded Mandates Reform Act”</HD>
        <P>It has been determined that the Privacy Act rulemaking for the Department of Defense does not involve a Federal mandate that may result in the expenditure by State, local and tribal governments, in the aggregate, or by the private sector, of $100 million or more and that such rulemaking will not significantly or uniquely affect small governments.</P>
        <HD SOURCE="HD2">Executive Order 13132, “Federalism”</HD>
        <P>It has been determined that the Privacy Act rules for the Department of Defense do not have federalism implications. The rules do not have substantial direct effects on the States, on the relationship between the National Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 32 CFR Part 319</HD>
          <P>Privacy.</P>
        </LSTSUB>
        
        <P>Accordingly, 32 CFR 319 is amended as follows:</P>
        <REGTEXT PART="319" TITLE="32">
          <PART>
            <HD SOURCE="HED">PART 319—DEFENSE INTELLIGENCE AGENCY PRIVACY PROGRAM</HD>
          </PART>
          <AMDPAR>1. The authority citation for 32 CFR part 319 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>Pub. L. 93-579, 5 U.S.C. 552a(f) and (k).</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="319" TITLE="32">
          <SECTION>
            <SECTNO>§ 319.13</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. In § 319.13 remove and reserve paragraph (f).</AMDPAR>
        </REGTEXT>
        <SIG>
          <DATED>Dated: February 28, 2012.</DATED>
          <NAME>Patricia L. Toppings,</NAME>
          <TITLE>OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6175 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <DEPDOC>[Docket ID DoD-2012-OS-0031]</DEPDOC>
        <CFR>32 CFR Part 322</CFR>
        <SUBJECT>Privacy Act; Implementation</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>National Security Agency/Central Security Service, DoD.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Direct final rule with request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The National Security Agency/Central Security Service (NSA/CSS) is adding a new exemption rule for GNSA 29 to exempt those records that are presently exempt from certain requirements of the Privacy Act. This direct final rule makes nonsubstantive changes to the National Security Agency/Central Security Service Privacy Program rules. These changes will allow the Department to exempt records from certain portions of the Privacy Act. This will improve the efficiency and effectiveness of DoD's program by preserving the exempt status of the records when the purposes underlying the exemption are valid and necessary to protect the contents of the records.</P>
          <P>This rule is being published as a direct final rule as the Department of Defense does not expect to receive any adverse comments, and so a proposed rule is unnecessary.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>

          <P>The rule is effective on May 25, 2012 unless comments are received that would result in a contrary determination. Comments will be accepted on or before May 15, 2012. If DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by docket number and title, by any of the following methods:</P>
          <P>•<E T="03">Federal Rulemaking Portal: http://www.regulations.gov</E>. Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Mail:</E>Federal Docket Management System Office, 4800 Mark Center Drive, 2nd Floor, East Tower, Suite 02G09, Alexandria, VA 22350-3100.</P>
          <P>
            <E T="03">Instructions:</E>All submissions received must include the agency name and docket number or Regulatory Information Number (RIN) for this<E T="04">Federal Register</E>document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the Internet at<E T="03">http://www.regulations.gov</E>as they are received without change, including any personal identifiers or contact information.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ms. Anne Hill at (301) 688-6527.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Direct Final Rule and Significant Adverse Comments</HD>

        <P>DoD has determined this rulemaking meets the criteria for a direct final rule because it involves nonsubstantive changes dealing with DoD's management of its Privacy Progams. DoD expects no opposition to the changes and no significant adverse comments. However, if DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>. A significant adverse comment is one that explains: (1) Why the direct<PRTPAGE P="15596"/>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 comment necessitates withdrawal of this direct final rule, DoD will consider whether it warrants a substantive response in a notice and comment process.</P>
        <HD SOURCE="HD2">Executive Order 12866, “Regulatory Planning and Review” and Executive Order 13563, “Improving Regulation and Regulatory Review”</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense are not significant rules. The rules do not (1) have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy; a sector of the economy; productivity; competition; jobs; the environment; public health or safety; or State, local, or tribal governments or communities; (2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another Agency; (3) Materially alter the budgetary impact of entitlements, grants, user fees, or loan programs, or the rights and obligations of recipients thereof; or (4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in these Executive orders.</P>
        <HD SOURCE="HD2">Public Law 96-354, “Regulatory Flexibility Act” (5 U.S.C. Chapter 6)</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense do not have significant economic impact on a substantial number of small entities because they are concerned only with the administration of Privacy Act systems of records within the Department of Defense.</P>
        <HD SOURCE="HD2">Public Law 96-511, “Paperwork Reduction Act” (44 U.S.C. Chapter 35)</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense impose no additional information collection requirements on the public under the Paperwork Reduction Act of 1995.</P>
        <HD SOURCE="HD2">Section 202, Public Law 104-4, “Unfunded Mandates Reform Act”</HD>
        <P>It has been determined that the Privacy Act rulemaking for the Department of Defense does not involve a Federal mandate that may result in the expenditure by State, local and tribal governments, in the aggregate, or by the private sector, of $100 million or more and that such rulemaking will not significantly or uniquely affect small governments.</P>
        <HD SOURCE="HD2">Executive Order 13132, “Federalism”</HD>
        <P>It has been determined that the Privacy Act rules for the Department of Defense do not have federalism implications. The rules do not have substantial direct effects on the States, on the relationship between the National Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 32 CFR Part 322</HD>
          <P>Privacy.</P>
        </LSTSUB>
        
        <P>Accordingly, 32 CFR part 322 is amended as follows:</P>
        <REGTEXT PART="322" TITLE="32">
          <PART>
            <HD SOURCE="HED">PART 322—NATIONAL SECURITY AGENCY/CENTRAL SECURITY SERVICE PROGRAM</HD>
          </PART>
          <AMDPAR>1. The authority citation for 32 CFR part 322 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>Privacy Act of 1974, Pub. L. 93-579, Stat. 1896 (5 U.S.C. 552a).</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="322" TITLE="32">
          <AMDPAR>2. Section 322.7 is amended by adding paragraph (l) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 322.7</SECTNO>
            <SUBJECT>Exempt systems of records.</SUBJECT>
            <STARS/>
            <P>(l)<E T="03">ID:</E>GNSA 29 (General Exemption)</P>
            <P>(2)<E T="03">System name:</E>NSA/CSS Office of Inspector General Investigations and Complaints.</P>
            <P>(3)<E T="03">Exemption:</E>Investigatory material compiled for law enforcement purposes, other than material within the scope of subsection 5 U.S.C. 552a(j)(2), may be exempt pursuant to 5 U.S.C. 552a(k)(2). However, if any individual is denied any right, privilege, or benefit for which he would otherwise be entitled by Federal law or for which he would otherwise be eligible, as a result of the maintenance of the information, the individual will be provided access to the information except to the extent that disclosure would reveal the identity of a confidential source.<E T="04">Note:</E>When claimed, this exemption allows limited protection of investigative reports maintained in a system of records used in personnel or administrative actions.</P>
            <P>Investigatory material compiled solely for the purpose of determining suitability, eligibility, or qualifications for Federal civilian employment, military service, federal contracts, or access to classified information may be exempt pursuant to 5 U.S.C. 552a(k)(5), but only to the extent that such material would reveal the identity of a confidential source.</P>
            <P>(4)<E T="03">Authority:</E>5 U.S.C. 552a(k)(2) through (k)(5).</P>
            <P>(5)<E T="03">Reasons:</E>(i) From subsection (c)(3) and (d) when access to accounting disclosures and access to or amendment of records would cause the identity of a confidential source to be revealed. Disclosure of the source's identity not only will result in the Department breaching the promise of confidentiality made to the source but it will impair the Department's future ability to compile investigatory material for the purpose of determining suitability, eligibility, or qualifications for Federal civilian employment, Federal contracts, or access to classified information. Unless sources can be assured that a promise of confidentiality will be honored, they will be less likely to provide information considered essential to the Department in making the required determinations.</P>
            <P>(ii) From (e)(1) because in the collection of information for investigatory purposes, it is not always possible to determine the relevance and necessity of particular information in the early stages of the investigation. In some cases, it is only after the information is evaluated in light of other information that its relevance and necessity becomes clear. Such information permits more informed decision-making by the Department when making required suitability, eligibility, and qualification determinations</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: February 28, 2012.</DATED>
          <NAME>Patricia L. Toppings,</NAME>
          <TITLE>OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6170 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Office of the Secretary</SUBAGY>
        <DEPDOC>[Docket ID DoD-2012-OS-0032]</DEPDOC>
        <CFR>32 CFR Part 322</CFR>
        <SUBJECT>Privacy Act; Implementation</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>National Security Agency/Central Security Service, DoD.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Direct final rule with request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The National Security Agency/Central Security Service is removing an exemption rule for GNSA 23, NSA/CSS Operations Security Support Program and Training Files. This direct final rule makes nonsubstantive changes to the National Security Agency/Central Security Service Program rules. These changes will remove the exemption rule for the system of records GNSA 23, NSA/CSS Operations Security Support Program and Training Files, which has been<PRTPAGE P="15597"/>deleted in its entirety. This rule is being published as a direct final rule as the Department of Defense does not expect to receive any adverse comments, and so a proposed rule is unnecessary.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>

          <P>The rule is effective on May 25, 2012 unless comments are received that would result in a contrary determination. Comments will be accepted on or before May 15, 2012. If DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by docket number and title, by any of the following methods.</P>
          <P>•<E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Mail:</E>Federal Docket Management System Office, 4800 Mark Center Drive, Suite 02G09, Alexandria, VA 22350-3100.</P>
          <P>
            <E T="03">Instructions:</E>All submissions received must include the agency name and docket number or Regulatory Information Number (RIN) for this<E T="04">Federal Register</E>document. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing on the Internet at<E T="03">http://www.regulations.gov</E>as they are received without change, including any personal identifiers or contact information.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ms. Anne Hill at (301) 688-6527.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Direct Final Rule and Significant Adverse Comments</HD>

        <P>DoD has determined this rulemaking meets the criteria for a direct final rule because it involves nonsubstantive changes dealing with DoD's management of its Privacy Progams. DoD expects no opposition to the changes and no significant adverse comments. However, if DoD receives a significant adverse comment, the Department will publish a withdrawal of this direct final rule in the<E T="04">Federal Register</E>. 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 comment necessitates withdrawal of this direct final rule, DoD will consider whether it warrants a substantive response in a notice and comment process.</P>
        <HD SOURCE="HD1">Executive Order 12866, “Regulatory Planning and Review” and Executive Order 13563, “Improving Regulation and Regulatory Review”</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense are not significant rules. The rules do not (1) Have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy; a sector of the economy; productivity; competition; jobs; the environment; public health or safety; or State, local, or tribal governments or communities; (2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another Agency; (3) Materially alter the budgetary impact of entitlements, grants, user fees, or loan programs, or the rights and obligations of recipients thereof; or (4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in these Executive orders.</P>
        <HD SOURCE="HD1">Public Law 96-354, “Regulatory Flexibility Act” (5 U.S.C. Chapter 6)</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense do not have significant economic impact on a substantial number of small entities because they are concerned only with the administration of Privacy Act systems of records within the Department of Defense.</P>
        <HD SOURCE="HD1">Public Law 96-511, “Paperwork Reduction Act” (44 U.S.C. Chapter 35)</HD>
        <P>It has been determined that Privacy Act rules for the Department of Defense impose no additional information collection requirements on the public under the Paperwork Reduction Act of 1995.</P>
        <HD SOURCE="HD1">Section 202, Public Law 104-4, “Unfunded Mandates Reform Act”</HD>
        <P>It has been determined that the Privacy Act rulemaking for the Department of Defense does not involve a Federal mandate that may result in the expenditure by State, local and tribal governments, in the aggregate, or by the private sector, of $100 million or more and that such rulemaking will not significantly or uniquely affect small governments.</P>
        <HD SOURCE="HD1">Executive Order 13132, “Federalism”</HD>
        <P>It has been determined that the Privacy Act rules for the Department of Defense do not have federalism implications. The rules do not have substantial direct effects on the States, on the relationship between the National Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 32 CFR Part 322</HD>
          <P>Privacy.</P>
        </LSTSUB>
        
        <P>Accordingly, 32 CFR part 322 is amended as follows:</P>
        <REGTEXT PART="322" TITLE="32">
          <PART>
            <HD SOURCE="HED">PART 322—NATIONAL SECURITY AGENCY/CENTRAL SECURITY SERVICE</HD>
          </PART>
          <AMDPAR>1. The authority citation for 32 CFR part 322 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>Pub. L. 93-579, 88 Stat. 1896 (5 U.S.C. 552a).</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="322" TITLE="32">
          <SECTION>
            <SECTNO>§ 322.7</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. In § 322.7 remove and reserve paragraph (r).</AMDPAR>
        </REGTEXT>
        <SIG>
          <DATED>Dated: February 28, 2012.</DATED>
          <NAME>Patricia L. Toppings,</NAME>
          <TITLE>OSD Federal Register Liaison Officer, Department of Defense.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6171 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 5001-06-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Coast Guard</SUBAGY>
        <CFR>33 CFR Part 100</CFR>
        <DEPDOC>[Docket No. USCG-2012-0088]</DEPDOC>
        <RIN>RIN 1625-AA08</RIN>
        <SUBJECT>Special Local Regulation; USAT Triathlon/Race Rowing Competition; Black Warrior River; Tuscaloosa, AL</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Coast Guard, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Temporary final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Coast Guard is establishing a temporary special local regulation for a portion of the Black Warrior River, from mile 338.5 to mile 341.5, Tuscaloosa, AL. This action is necessary for the safeguard of participants and spectators, including all crews, vessels, and persons on navigable waters during the USAT Triathlon/Race Rowing Competition. Entry into, transiting in or anchoring in this area is prohibited to all vessels not registered with the sponsor as participants or not part of the regatta patrol, unless specifically authorized by the Captain of the Port (COTP) Mobile or a designated representative.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective and enforceable with actual notice from 7 a.m. until 6 p.m. on April 21, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Documents indicated in this preamble as being available in the docket are part of docket USCG-2012-<PRTPAGE P="15598"/>0088 and are available online by going to<E T="03">http://www.regulations.gov</E>, inserting USCG-2012-0088 in the “Search” box, and then clicking “Search.” They are also available for inspection or copying at the Docket Management Facility (M-30), U.S. Department of Transportation, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays; and U.S. Coast Guard Sector Mobile (spw), Building 102, Brookley Complex South Broad Street, Mobile, AL 36615, between 8 a.m. and 3:30 p.m., Monday through Friday, except Federal holidays.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>If you have questions on this temporary rule, call or email Lt. Lenell J. Carson, Coast Guard Sector Mobile, Waterways Division; telephone 251-441-5940 or email<E T="03">Lenell.J.Carson@uscg.mil</E>. If you have questions on viewing the docket, call Renee V. Wright, Program Manager, Docket Operations, telephone 202-366-9826.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Regulatory Information</HD>
        <P>The Coast Guard is issuing this temporary final rule without prior notice and opportunity to comment pursuant to authority under section 4(a) of the Administrative Procedure Act (APA) (5 U.S.C. 553(b)). This provision authorizes an agency to issue a rule without prior notice and opportunity to comment when the agency for good cause finds that those procedures are “impracticable, unnecessary, or contrary to the public interest.” This rule provides proper notice; however, under 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) which would provide a comment period with respect to this rule. The Coast Guard received applications for Marine Event Permits on February 2, 2012, and February 6, 2012, from the University of Alabama and the Tuscaloosa Tourism and Sports Commission to conduct their events on April 21, 2012. After reviewing the details of the events and the permit applications, the Coast Guard determined that a special local regulation is needed and delaying or foregoing this safety measure to provide a comment period would be contrary to the public interest. The special local regulation is needed to safeguard persons and vessels from safety hazards associated with the USAT Triathlon and Race Rowing Competition.</P>
        <HD SOURCE="HD1">Basis and Purpose</HD>
        <P>The University of Alabama Women's rowing team is sponsoring a Race Rowing Competition between the University of Alabama and the University of Iowa on the Black Warrior River. The Tuscaloosa Tourism and Sports Commission is sponsoring the USAT National Collegiate Championship Triathlon, and the swimming portion of the race is to take place in the Black Warrior River. The introduction of rowing vessels and swimmers into a commercially transited river system poses significant safety hazards to both swimmers and rowing vessels. The COTP Mobile is establishing a temporary special local regulation for a portion of the Black Warrior River, Tuscaloosa, AL, to safeguard persons and vessels during the two events.</P>
        <P>The COTP anticipates minimal impact on vessel traffic due to this regulation. However, this special local regulation is deemed necessary for the safeguard of life and property within the COTP Mobile zone.</P>
        <HD SOURCE="HD1">Discussion of Rule</HD>
        <P>The Coast Guard is establishing a temporary special local regulation for a portion of the Black Warrior River from mile 338.5 to mile 341.5, Tuscaloosa, AL. This temporary rule will safeguard life and property in this area. Entry into, transiting in or anchoring in this zone is prohibited to all vessels not registered with the sponsor as participants or not part of the regatta patrol, unless specifically authorized by the COTP Mobile or a designated representative. They may be contacted on VHF-FM Channel 16 or through Coast Guard Sector Mobile at 251-441-5976.</P>
        <P>The COTP Mobile or a designated representative will inform the public through broadcast notice to mariners of changes in the effective period for the special local regulation. This rule is effective from 7 a.m. until 6 p.m. on April 21, 2012.</P>
        <HD SOURCE="HD1">Regulatory Analyses</HD>
        <P>We developed this rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on 13 of these statutes or executive orders.</P>
        <HD SOURCE="HD1">Regulatory Planning and Review</HD>
        <P>This rule is not a significant regulatory action under section 3(f) of Executive Order 12866, Regulatory Planning and Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Order. The Office of Management and Budget has not reviewed it under that Order.</P>
        <P>The special local regulation listed in this rule will only restrict vessel traffic from entering, transiting, or anchoring within a small portion of the Black Warrior River, Tuscaloosa, AL. The effect of this regulation will not be significant for several reasons: (1) This rule will only affect vessel traffic for a short duration; (2) vessels may request permission from the COTP to transit through the regulated area; and (3) the impacts on routine navigation are expected to be minimal. Notifications to the marine community will be made through broadcast notice to mariners. These notifications will allow the public to plan operations around the regulated area.</P>
        <HD SOURCE="HD1">Small Entities</HD>
        <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
        <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities. This rule will affect the following entities, some of which may be small entities: The owners or operators of vessels intending to transit or anchor in affected portions of the Black Warrior River, Tuscaloosa, AL, during the two events. This special local regulation will not have a significant economic impact on a substantial number of small entities for the following reasons. The zone is limited in size, is of short duration, and vessel traffic may request permission from the COTP Mobile or a designated representative to enter or transit through the regulated area.</P>
        <HD SOURCE="HD1">Assistance for Small Entities</HD>
        <P>Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we offer to assist small entities in understanding the rule so that they can better evaluate its effects on them and participate in the rulemaking process.</P>

        <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business<PRTPAGE P="15599"/>Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.</P>
        <HD SOURCE="HD1">Collection of Information</HD>
        <P>This calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
        <HD SOURCE="HD1">Federalism</HD>
        <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. We have analyzed this rule under that Order and determined that this rule does not have implications for federalism.</P>
        <HD SOURCE="HD1">Unfunded Mandates Reform Act</HD>
        <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or more in any one year. Though this rule will not result in such expenditure, we do discuss the effects of this rule elsewhere in this preamble.</P>
        <HD SOURCE="HD1">Taking of Private Property</HD>
        <P>This rule will not affect a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.</P>
        <HD SOURCE="HD1">Civil Justice Reform</HD>
        <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.</P>
        <HD SOURCE="HD1">Protection of Children</HD>
        <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or risk to safety that may disproportionately affect children.</P>
        <HD SOURCE="HD1">Indian Tribal Governments</HD>
        <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
        <HD SOURCE="HD1">Energy Effects</HD>
        <P>We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. The Administrator of the Office of Information and Regulatory Affairs has not designated it as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211.</P>
        <HD SOURCE="HD1">Technical Standards</HD>
        <P>The National Technology Transfer and Advancement Act (NTTAA) (15 U.S.C. 272 note) directs agencies to use voluntary consensus standards in their regulatory activities unless the agency provides Congress, through the Office of Management and Budget, with an explanation of why using these standards would be inconsistent with applicable law or otherwise impractical. Voluntary consensus standards are technical standards (e.g., specifications of materials, performance, design, or operation; test methods; sampling procedures; and related management systems practices) that are developed or adopted by voluntary consensus standards bodies. This rule does not use technical standards. Therefore, we did not consider the use of voluntary consensus standards.</P>
        <HD SOURCE="HD1">Environment</HD>
        <P>We have analyzed this rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA) (42 U.S.C. 4321-4370f), and have concluded this action is one of a category of actions which do not individually or cumulatively have a significant effect on the human environment. This rule is categorically excluded, under figure 2-1, paragraph (34)(h), of the Instruction. This rule involves establishing a special local regulation, requiring a permit wherein an analysis of the environmental impact of the regulations was performed. Under figure 2-1, paragraph (34)(h.), of the Instruction, an environmental analysis checklist and a categorical exclusion determination are not required for this rule.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects 33 CFR Part 100</HD>
          <P>Marine safety, Navigation (water), Reporting and recordkeeping requirements, Waterways.</P>
        </LSTSUB>
        
        <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 100 as follows:</P>
        <REGTEXT PART="100" TITLE="33">
          <PART>
            <HD SOURCE="HED">PART 100-SAFETY OF LIFE ON NAVIGABLE WATERS</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 100 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>33 U.S.C. 1233.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="100" TITLE="33">
          <AMDPAR>2. Add § 100.35T08-0088 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 100.35T08-0088</SECTNO>
            <SUBJECT>Special Local Regulation; Black Warrior River; Tuscaloosa, AL.</SUBJECT>
            <P>(a)<E T="03">Regulated Area.</E>The following area is a regulated area: a portion of the Black Warrior River, from mile 338.5 to mile 341.5, Tuscaloosa, AL.</P>
            <P>(b)<E T="03">Enforcement dates.</E>This rule will be enforced from 7 a.m. until 6 p.m. on April 21, 2012.</P>
            <P>(c)<E T="03">Special Local Regulations.</E>(1) The Coast Guard will patrol the regulated area under the direction of a designated Coast Guard Patrol Commander. The Patrol Commander may be contacted on Channel 16 VHF-FM (156.8 MHz) by the call sign “PATCOM”.</P>
            <P>(2) All Persons and vessels not registered with the sponsor as participants or official patrol vessels are considered spectators. The “official patrol vessels” consist of any Coast Guard, state, or local law enforcement and sponsor provided vessels assigned or approved by the Captain of the Port Mobile to patrol the regulated area.</P>
            <P>(3) Spectator vessels desiring to transit the regulated area may do so only with prior approval of the Patrol Commander and when so directed by that officer and will be operated at a minimum safe navigation speed in a manner which will not endanger participants in the regulated area or any other vessels.</P>

            <P>(4) No spectator shall anchor, block, loiter, or impede the through transit of<PRTPAGE P="15600"/>participants or official patrol vessels in the regulated area during the effective dates and times, unless cleared for entry by or through an official patrol vessel.</P>
            <P>(5) The patrol commander may forbid and control the movement of all vessels in the regulated area. When hailed or signaled by an official patrol vessel, a vessel shall come to an immediate stop and comply with the directions given. Failure to do so may result in expulsion from the area, citation for failure to comply, or both.</P>
            <P>(6) Any spectator vessel may anchor outside the regulated area, but may not anchor in, block, or loiter in a navigable channel. Spectator vessels may be moored to a waterfront facility within the regulated area in such a way that they shall not interfere with the progress of the event. Such mooring must be complete at least 30 minutes prior to the establishment of the regulated area and remain moored through the duration of the event.</P>
            <P>(7) The Patrol Commander may terminate the event or the operation of any vessel at any time it is deemed necessary for the protection of life or property.</P>
            <P>(8) The Patrol Commander will terminate enforcement of the special local regulations at the conclusion of the event.</P>
            <P>(d)<E T="03">Informational Broadcasts.</E>The Captain of the Port or a designated representative will inform the public through broadcast notices to mariners of the enforcement period for the regulated area as well as any changes in the planned schedule.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: February 21, 2012.</DATED>
          <NAME>D.J. Rose,</NAME>
          <TITLE>Captain, U.S. Coast Guard, Captain of the Port Mobile.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6381 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-04-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Coast Guard</SUBAGY>
        <CFR>33 CFR Part 100</CFR>
        <DEPDOC>[Docket No. USCG-2012-0085]</DEPDOC>
        <RIN>RIN 1625-AA08</RIN>
        <SUBJECT>Special Local Regulation; Emerald Coast Super Boat Grand Prix; Saint Andrew Bay; Panama City, FL</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Coast Guard, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Temporary final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Coast Guard is establishing a temporary special local regulation for a portion of Saint Andrew Bay, Panama City, FL. This action is necessary for the safeguard of participants and spectators, including all crews, vessels, and persons on navigable waters during the Emerald Coast Super Boat Grand Prix high speed boat races. Entry into, transiting in or anchoring in this area is prohibited to all vessels not registered with the sponsor as participants or not part of the regatta patrol, unless specifically authorized by the Captain of the Port (COTP) Mobile or a designated representative.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective from 10 a.m. until 4 p.m. on May 6, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Documents indicated in this preamble as being available in the docket are part of docket USCG-2012-0085 and are available online by going to<E T="03">http://www.regulations.gov,</E>inserting USCG-2012-0085 in the “Search” box, and then clicking “Search.” They are also available for inspection or copying at the Docket Management Facility (M-30), U.S. Department of Transportation, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays and U.S. Coast Guard Sector Mobile (spw), Building 102, Brookley Complex South Broad Street Mobile, AL 36615, between 8 a.m. and 3:30 p.m., Monday through Friday, except Federal holidays.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>If you have questions on this temporary rule, call or email Lt. Lenell J. Carson, Coast Guard Sector Mobile, Waterways Division; telephone 251-441-5940 or email<E T="03">Lenell.J.Carson@uscg.mil.</E>If you have questions on viewing the docket, call Renee V. Wright, Program Manager, Docket Operations, telephone 202-366-9826.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Regulatory Information</HD>
        <P>The Coast Guard is issuing this temporary final rule without prior notice and opportunity to comment pursuant to authority under section 4(a) of the Administrative Procedure Act (APA) (5 U.S.C. 553(b)). This provision authorizes an agency to issue a rule without prior notice and opportunity to comment when the agency for good cause finds that those procedures are “impracticable, unnecessary, or contrary to the public interest.” This rule provides proper notice; however, under 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) which would provide a comment period with respect to this rule. The Coast Guard received an application for a Marine Event Permit on January 31, 2011 from Super Boat International, Inc. to conduct a high speed boat race on May 6, 2012. After reviewing the details of the event and the permit application, the Coast Guard determined that a special local regulation is needed and delaying or foregoing this safety measure to provide a comment period would be contrary to the public interest. The special local regulation is needed to safeguard persons and vessels from safety hazards associated with the Emerald Coast Super Boat Grand Prix high speed boat races.</P>
        <HD SOURCE="HD1">Basis and Purpose</HD>
        <P>On January 31, 2012, Super Boat International, Inc. applied for a Marine Event Permit to conduct a high speed boat race on Saint Andrew Bay, Panama City, FL on May 6, 2012. This event will draw in a large number of pleasure craft and the high speed boats pose a significant safety hazard to both vessels and mariners operating in or near the area. The COTP Mobile is establishing a temporary special local regulation for a portion of Saint Andrew Bay, Panama City, FL, to safeguard persons and vessels during the high speed boat races.</P>
        <P>The COTP anticipates minimal impact on vessel traffic due to this regulation. However, this special local regulation is deemed necessary for the safeguard of life and property within the COTP Mobile zone.</P>
        <HD SOURCE="HD1">Discussion of Rule</HD>
        <P>The Coast Guard is establishing a temporary special local regulation for a portion of Saint Andrew Bay, Panama City, FL, enclosed by a bounded area starting at a point on the shore at approximately 30°09′55.62″ N, 085°41′46.30″ W, then east following the shore line to 30°08′39.18″ N, 085°39′27.89″ W, then southwest to30°08′34.24″ N, 085°39′40.68″ W, then west to 30°09′34.35″ N, 085°41′46.30″ W, then north to the starting point at 30°09′55.62″ N, 085°41′46.30″ W. This temporary rule will safeguard life and property in this area. Entry into, transiting in or anchoring in this zone is prohibited to all vessels not registered with the sponsor as participants or not part of the regatta patrol, unless specifically authorized by the COTP Mobile or a designated representative. They may be contacted on VHF-FM Channel 16 or through Coast Guard Sector Mobile at 251-441-5976.</P>

        <P>The COTP Mobile or a designated representative will inform the public through broadcast notice to mariners of changes in the effective period for the special local regulation. This rule will<PRTPAGE P="15601"/>be effective and enforced from 10 a.m. until 4 p.m. on May 6, 2012.</P>
        <HD SOURCE="HD1">Regulatory Analyses</HD>
        <P>We developed this rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on 13 of these statutes or executive orders.</P>
        <HD SOURCE="HD1">Regulatory Planning and Review</HD>
        <P>This rule is not a significant regulatory action under section 3(f) of Executive Order 12866, Regulatory Planning and Review, as supplemented by Executive Order 13563, Improving Regulation and Regulatory Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of Executive Order 12866 or under section 1 of Executive Order 13563. The Office of Management and Budget has not reviewed it under those Orders.</P>
        <P>The special local regulation listed in this rule will only restrict vessel traffic from entering, transiting, or anchoring within a small portion of Saint Andrew Bay, Panama City, FL. The effect of this regulation will not be significant for several reasons: (1) This rule will only affect vessel traffic for a short duration; (2) vessels may request permission from the COTP to transit through the regulated area; and (3) the impacts on routine navigation are expected to be minimal. Notifications to the marine community will be made through broadcast notice to mariners. These notifications will allow the public to plan operations around the regulated area.</P>
        <HD SOURCE="HD1">Small Entities</HD>
        <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
        <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities. This rule will affect the following entities, some of which may be small entities: The owners or operators of vessels intending to transit or anchor in affected portions of Saint Andrew Bay during the high speed boat races. This special local regulation will not have a significant economic impact on a substantial number of small entities for the following reasons. The zone is limited in size, is of short duration and vessel traffic may request permission from the COTP Mobile or a designated representative to enter or transit through the regulated area.</P>
        <HD SOURCE="HD1">Assistance for Small Entities</HD>
        <P>Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we offer to assist small entities in understanding the rule so that they can better evaluate its effects on them and participate in the rulemaking process.</P>
        <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.</P>
        <HD SOURCE="HD1">Collection of Information</HD>
        <P>This calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
        <HD SOURCE="HD1">Federalism</HD>
        <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. We have analyzed this rule under that Order and determined that this rule does not have implications for federalism.</P>
        <HD SOURCE="HD1">Unfunded Mandates Reform Act</HD>
        <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or more in any one year. Though this rule will not result in such expenditure, we do discuss the effects of this rule elsewhere in this preamble.</P>
        <HD SOURCE="HD1">Taking of Private Property</HD>
        <P>This rule will not affect a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.</P>
        <HD SOURCE="HD1">Civil Justice Reform</HD>
        <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.</P>
        <HD SOURCE="HD1">Protection of Children</HD>
        <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or risk to safety that may disproportionately affect children.</P>
        <HD SOURCE="HD1">Indian Tribal Governments</HD>
        <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
        <HD SOURCE="HD1">Energy Effects</HD>
        <P>We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. The Administrator of the Office of Information and Regulatory Affairs has not designated it as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211.</P>
        <HD SOURCE="HD1">Technical Standards</HD>

        <P>The National Technology Transfer and Advancement Act (NTTAA) (15 U.S.C. 272 note) directs agencies to use voluntary consensus standards in their regulatory activities unless the agency provides Congress, through the Office of Management and Budget, with an explanation of why using these standards would be inconsistent with applicable law or otherwise impractical. Voluntary consensus standards are<PRTPAGE P="15602"/>technical standards (e.g., specifications of materials, performance, design, or operation; test methods; sampling procedures; and related management systems practices) that are developed or adopted by voluntary consensus standards bodies.</P>
        <P>This rule does not use technical standards. Therefore, we did not consider the use of voluntary consensus standards.</P>
        <HD SOURCE="HD1">Environment</HD>
        <P>We have analyzed this rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA) (42 U.S.C. 4321-4370f), and have concluded this action is one of a category of actions which do not individually or cumulatively have a significant effect on the human environment. This rule is categorically excluded, under figure 2-1, paragraph (34)(h), of the Instruction. This rule involves establishing a special local regulation, requiring a permit wherein an analysis of the environmental impact of the regulations was performed. Under figure 2-1, paragraph (34)(h.), of the Instruction, an environmental analysis checklist and a categorical exclusion determination are not required for this rule.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 33 CFR Part 100</HD>
          <P>Marine safety, Navigation (water), Reporting and recordkeeping requirements, Waterways.</P>
        </LSTSUB>
        
        <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 100 as follows:</P>
        <REGTEXT PART="100" TITLE="33">
          <PART>
            <HD SOURCE="HED">PART 100—SAFETY OF LIFE ON NAVIGABLE WATERS</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 100 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>33 U.S.C. 1233.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="100" TITLE="33">
          <AMDPAR>2. Add § 100.T08-0085 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 100.T08-0085</SECTNO>
            <SUBJECT>Special Local Regulation; Saint Andrew Bay; Panama City, FL.</SUBJECT>
            <P>(a)<E T="03">Regulated Area.</E>The following area is a regulated area: A portion of Saint Andrew Bay, Panama City, FL, enclosed by a bounded area starting at a point on the shore at approximately 30°09′55.62″ N, 085°41′46.30″ W, then east following the shore line to 30°08′39.18″ N, 085°39′27.89″ W, then southwest to 30°08′34.24″ N, 085°39′40.68″ W, then west to 30°09′34.35″ N, 085°41′46.30″  W, then north to the starting point at 30°09′55.62″  N, 085°41′46.30″ W.</P>
            <P>(b)<E T="03">Enforcement dates.</E>This rule will be enforced from 10 a.m. until 4 p.m. on May 6, 2012.</P>
            <P>(c)<E T="03">Special Local Regulations.</E>(1) The Coast Guard will patrol the regulated area under the direction of a designated Coast Guard Patrol Commander. The Patrol Commander may be contacted on Channel 16 VHF-FM (156.8 MHz) by the call sign “PATCOM”.</P>
            <P>(2) All Persons and vessels not registered with the sponsor as participants or official patrol vessels are considered spectators. The “official patrol vessels” consist of any Coast Guard, state, or local law enforcement and sponsor provided vessels assigned or approved by the Captain of the Port Mobile to patrol the regulated area.</P>
            <P>(3) Spectator vessels desiring to transit the regulated area may do so only with prior approval of the Patrol Commander and when so directed by that officer and will be operated at a minimum safe navigation speed in a manner which will not endanger participants in the regulated area or any other vessels.</P>
            <P>(4) No spectator shall anchor, block, loiter, or impede the through transit of participants or official patrol vessels in the regulated area during the effective dates and times, unless cleared for entry by or through an official patrol vessel.</P>
            <P>(5) The patrol commander may forbid and control the movement of all vessels in the regulated area. When hailed or signaled by an official patrol vessel, a vessel shall come to an immediate stop and comply with the directions given. Failure to do so may result in expulsion from the area, citation for failure to comply, or both.</P>
            <P>(6) Any spectator vessel may anchor outside the regulated area, but may not anchor in, block, or loiter in a navigable channel. Spectator vessels may be moored to a waterfront facility within the regulated area in such a way that they shall not interfere with the progress of the event. Such mooring must be complete at least 30 minutes prior to the establishment of the regulated area and remain moored through the duration of the event.</P>
            <P>(7) The Patrol Commander may terminate the event or the operation of any vessel at any time it is deemed necessary for the protection of life or property.</P>
            <P>(8) The Patrol Commander will terminate enforcement of the special local regulations at the conclusion of the event.</P>
            <P>(d)<E T="03">Informational Broadcasts.</E>The Captain of the Port or a designated representative will inform the public through broadcast notices to mariners of the enforcement period for the regulated area as well as any changes in the planned schedule.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: February 21, 2012.</DATED>
          <NAME>D.J. Rose,</NAME>
          <TITLE>Captain, U.S. Coast Guard, Captain of the Port Mobile.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6377 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-04-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Coast Guard</SUBAGY>
        <CFR>33 CFR Part 100</CFR>
        <DEPDOC>[Docket No. USCG-2011-1120]</DEPDOC>
        <RIN>RIN 1625-AA08</RIN>
        <SUBJECT>Special Local Regulations for Marine Events; Spa Creek and Annapolis Harbor, Annapolis, MD</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Coast Guard, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Temporary final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Coast Guard is establishing special local regulations during the swim segment of the “TriRock Triathlon Series”, a marine event to be held on the waters of Spa Creek and Annapolis Harbor on May 12, 2012. These special local regulations are necessary to provide for the safety of life on navigable waters during the event. This action is intended to temporarily restrict vessel traffic in a portion of the Spa Creek and Annapolis Harbor during the event.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective and will be enforced from 6 a.m. to 9:45 a.m. on May 12, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Comments and material received from the public, as well as documents mentioned in this preamble as being available in the docket, are part of docket USCG-2011-1120 and are available online by going to<E T="03">http://www.regulations.gov,</E>inserting USCG-2011-1120 in the “Search” box, and then clicking “Search.” This material is also available for inspection or copying at the Docket Management Facility (M-30), U.S. Department of Transportation, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>If you have questions on this temporary rule, call or email Mr. Ronald Houck, U.S. Coast Guard Sector Baltimore, MD; telephone 410-576-2674, email<E T="03">Ronald.L.Houck@uscg.mil.</E>If you have questions on viewing the docket, call Renee V. Wright, Program Manager,<PRTPAGE P="15603"/>Docket Operations, telephone 202-366-9826.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Regulatory Information</HD>

        <P>On January 18, 2012, we published a notice of proposed rulemaking (NPRM) entitled “Special Local Regulations for Marine Events; Spa Creek and Annapolis Harbor, Annapolis, MD” in the<E T="04">Federal Register</E>(77 FR 11). We received no comments on the proposed rule. No public meeting was requested, and none was held.</P>
        <HD SOURCE="HD1">Background and Purpose</HD>
        <P>On Saturday, May 12, 2012, Competitor Group Inc. of San Diego, California, will sponsor the “TriRock Triathlon Series” in Annapolis, Maryland. The swim segment of the event will occur from 6:30 a.m. to 9:15 a.m. and will be located in Spa Creek and Annapolis Harbor. Up to 300 swimmers will operate on a 500-meter course located between the Annapolis City Dock and the confluence of the Spa Creek with the Severn River. The swimmers will be supported by sponsor-provided watercraft. The start and finish will be located at the Annapolis City Dock. A portion of the swim course will impede the federal navigation channel. Due to the need for vessel control during the event, the Coast Guard will temporarily restrict vessel traffic in the event area to provide for the safety of participants, spectators and other transiting vessels.</P>
        <HD SOURCE="HD1">Discussion of Comments and Changes</HD>
        <P>The Coast Guard received no comments in response to the NPRM. No public meeting was requested and none was held.</P>
        <HD SOURCE="HD1">Regulatory Analyses</HD>
        <P>We developed this rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on 13 of these statutes or executive orders.</P>
        <HD SOURCE="HD1">Regulatory Planning and Review</HD>
        <P>This rule is not a significant regulatory action under section 3(f) of Executive Order 12866, Regulatory Planning and Review, as supplemented by Executive Order 13563, Improving Regulation and Regulatory Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of Executive Order 12866 or under section 1 of Executive Order 13563. The Office of Management and Budget has not reviewed it under those Orders. We expect the economic impact of this rule to be so minimal that a full Regulatory Evaluation under the regulatory policies and procedures of DHS is unnecessary. Although this regulation will prevent traffic from transiting a portion of Spa Creek and Annapolis Harbor during the event, the effect of this regulation will not be significant due to the limited duration that the regulated area will be in effect and the extensive advance notifications that will be made to the maritime community via the Local Notice to Mariners and marine information broadcasts, so mariners can adjust their plans accordingly.</P>
        <HD SOURCE="HD1">Small Entities</HD>
        <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
        <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities. This rule would affect the following entities, some of which might be small entities: The owners or operators of vessels intending to transit or anchor in the effected portions of Spa Creek and Annapolis Harbor during the event.</P>
        <P>Although this regulation prevents traffic from transiting a portion of the Spa Creek and Annapolis Harbor during the event, this rule will not have a significant economic impact on a substantial number of small entities for the following reasons: Though the regulated area extends across the entire width of the waterway, this rule would be in effect for only a limited period; and before the enforcement period, we will issue maritime advisories so mariners can adjust their plans accordingly. All Coast Guard vessels enforcing this regulated area can be contacted at telephone number 410-576-2693 or on marine band radio VHF-FM channel 16 (156.8 MHz).</P>
        <HD SOURCE="HD1">Assistance for Small Entities</HD>
        <P>Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), in the NPRM we offered to assist small entities in understanding the rule so that they could better evaluate its effects on them and participate in the rulemaking process.</P>
        <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.</P>
        <HD SOURCE="HD1">Collection of Information</HD>
        <P>This rule calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
        <HD SOURCE="HD1">Federalism</HD>
        <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. We have analyzed this rule under that Order and determined that this rule does not have implications for federalism.</P>
        <HD SOURCE="HD1">Unfunded Mandates Reform Act</HD>
        <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 or more in any one year. Though this rule will not result in such an expenditure, we do discuss the effects of this rule elsewhere in this preamble.</P>
        <HD SOURCE="HD1">Taking of Private Property</HD>
        <P>This rule will not effect a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.</P>
        <HD SOURCE="HD1">Civil Justice Reform</HD>
        <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.</P>
        <HD SOURCE="HD1">Protection of Children</HD>

        <P>We have analyzed this rule under Executive Order 13045, Protection of<PRTPAGE P="15604"/>Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or risk to safety that may disproportionately affect children.</P>
        <HD SOURCE="HD1">Indian Tribal Governments</HD>
        <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
        <HD SOURCE="HD1">Energy Effects</HD>
        <P>We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. The Administrator of the Office of Information and Regulatory Affairs has not designated it as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211.</P>
        <HD SOURCE="HD1">Technical Standards</HD>
        <P>The National Technology Transfer and Advancement Act (NTTAA) (15 U.S.C. 272 note) directs agencies to use voluntary consensus standards in their regulatory activities unless the agency provides Congress, through the Office of Management and Budget, with an explanation of why using these standards would be inconsistent with applicable law or otherwise impractical. Voluntary consensus standards are technical standards (e.g., specifications of materials, performance, design, or operation; test methods; sampling procedures; and related management systems practices) that are developed or adopted by voluntary consensus standards bodies. This rule does not use technical standards. Therefore, we did not consider the use of voluntary consensus standards.</P>
        <HD SOURCE="HD1">Environment</HD>

        <P>We have analyzed this rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA) (42 U.S.C. 4321-4370f), and have concluded this action is one of a category of actions which do not individually or cumulatively have a significant effect on the human environment. This rule is categorically excluded, under figure 2-1, paragraph (34)(h), of the Instruction. This rule involves implementation of regulations within 33 CFR Part 100 applicable to organized marine events on the navigable waters of the United States that could negatively impact the safety of waterway users and shore side activities in the event area. The category of water activities includes but is not limited to sail boat regattas, boat parades, power boat racing, swimming events, crew racing, canoe and sail board racing. An environmental analysis checklist and a categorical exclusion determination are available in the docket where indicated under<E T="02">ADDRESSES</E>.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 33 CFR Part 100</HD>
          <P>Marine safety, Navigation (water), Reporting and recordkeeping requirements, Waterways.</P>
        </LSTSUB>
        
        <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 100 as follows:</P>
        <REGTEXT PART="100" TITLE="33">
          <PART>
            <HD SOURCE="HED">PART 100—SAFETY OF LIFE ON NAVIGABLE WATERS</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 100 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>33 U.S.C. 1233.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="100" TITLE="33">
          <AMDPAR>2. Add a temporary section, § 100.35T05-1120 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 100.35T05-1120</SECTNO>
            <SUBJECT>Special Local Regulations for Marine Events; Spa Creek and Annapolis Harbor, Annapolis, MD.</SUBJECT>
            <P>(a)<E T="03">Regulated area.</E>The following location is a regulated area: All waters of the Spa Creek and Annapolis Harbor, within lines connecting the following positions: from position latitude 38°58′34″ N, longitude 076°29′05″ W, thence to position latitude 38°58′27″ N, longitude 076°28′55″ W, and from position latitude 38°58′40″ N, longitude 076°28′49″ W to position latitude 38°58′32″ N, longitude 076°28′45″ W. All coordinates reference Datum NAD 1983.</P>
            <P>(b)<E T="03">Definitions.</E>(1)<E T="03">Coast Guard Patrol Commander</E>means a commissioned, warrant, or petty officer of the U.S. Coast Guard who has been designated by the Commander, Coast Guard Sector Baltimore.</P>
            <P>(2)<E T="03">Official Patrol</E>means any vessel assigned or approved by Commander, Coast Guard Sector Baltimore with a commissioned, warrant, or petty officer on board and displaying a Coast Guard ensign.</P>
            <P>(c)<E T="03">Special local regulations.</E>(1) The Coast Guard Patrol Commander may forbid and control the movement of all vessels and persons in the regulated area. When hailed or signaled by an official patrol vessel, a vessel or person in the regulated area shall immediately comply with the directions given. Failure to do so may result in expulsion from the area, citation for failure to comply, or both.</P>
            <P>(2) All Coast Guard vessels enforcing this regulated area can be contacted at telephone number 410-576-2693 or on marine band radio VHF-FM channel 16 (156.8 MHz).</P>
            <P>(3) The Coast Guard will publish a notice in the Fifth Coast Guard District Local Notice to Mariners and issue a marine information broadcast on VHF-FM marine band radio announcing specific event date and times.</P>
            <P>(d) Enforcement period: This section will be enforced from 6 a.m. to 9:45 a.m. on May 12, 2012.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: February 23, 2012.</DATED>
          <NAME>Mark P. O'Malley,</NAME>
          <TITLE>Captain, U.S. Coast Guard, Captain of the Port Baltimore.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6382 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-04-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Coast Guard</SUBAGY>
        <CFR>33 CFR Part 100</CFR>
        <DEPDOC>[Docket No. USCG-2012-0134]</DEPDOC>
        <SUBJECT>Annual Marine Events in the Eighth Coast Guard District</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Coast Guard, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of enforcement of regulation.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Coast Guard will enforce Special Local Regulations for the Neches River Festival boat races in Port Neches, TX from 3 p.m. on May 4, 2012 through 6 p.m. on May 6, 2012. This action is necessary to provide for the safety of the race participants, crew, spectators, participating vessels, non-participating vessels and other users of the waterway. During the enforcement period no person or vessel may enter the zone established by the special local regulation without permission of the Captain of the Port.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The regulation in 33 CFR 100.801 (Table 1, paragraph 118) will be enforced from 3 p.m. to 6 p.m. on May 4, 2012; and from 9 a.m. to 6 p.m. on May 5 and May 6, 2012.</P>
        </DATES>
        <FURINF>
          <PRTPAGE P="15605"/>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>If you have questions on this notice of enforcement, call or email Mr. Scott Whalen, U.S. Coast Guard Marine Safety Unit Port Arthur, TX; telephone 409-719-5086, email<E T="03">scott.k.whalen@uscg.mil.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The Coast Guard will enforce Special Local Regulations for the annual Neches River Festival in 33 CFR 100.801 (Table 1, paragraph 118) on May 4, 2012, from 3 p.m. to 6 p.m. and on May 5 and May 6, 2012 from 9 a.m. to 10 p.m.</P>
        <P>Under the provisions of 33 CFR 100.801 (Table 1, paragraph 118), a vessel may not enter the regulated area, unless it receives permission from the Captain of the Port. Spectator vessels may safely transit outside the regulated area but may not anchor, block, loiter, or impede participants or official patrol vessels. The Coast Guard may be assisted by other federal, state or local law enforcement agencies in enforcing this regulation.</P>

        <P>This notice of enforcement is issued under the authority of 33 CFR 100.801 (Table 1, paragraph 118). In addition to this notification in the<E T="04">Federal Register</E>, the Coast Guard will provide the maritime community with notification of this enforcement period via Local Notice to Mariners, Marine Information Broadcasts, and Marine Safety Information Bulletins.</P>
        <P>If the Captain of the Port or his designated representative determines that the regulated area need not be enforced for the full duration stated in this notice of enforcement, he or she may use a Broadcast Notice to Mariners to grant general permission to enter the regulated area.</P>
        <SIG>
          <DATED>Dated: February 21, 2012.</DATED>
          <NAME>G.J. Paitl,</NAME>
          <TITLE>Captain, U.S. Coast Guard, Captain of the Port, Port Arthur.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6379 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-04-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">POSTAL SERVICE</AGENCY>
        <CFR>39 CFR Part 111</CFR>
        <SUBJECT>Mobile Commerce and Personalization Promotion</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Postal Service<E T="51">TM</E>.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Postal Service will revise the<E T="03">Mailing Standards of the United States Postal Service,</E>Domestic Mail Manual (DMM®) 709.3 to add a new temporary promotion in the summer of 2012 for Presorted and automation First-Class Mail® cards, letters and flats, and Standard Mail® letters and flats bearing two-dimensional mobile barcodes or equivalent print technology.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>July 1, 2012.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Krista Becker at 202-268-7345, Bill Chatfield at 202-268-7278, or<E T="03">mobilebarcode@usps.gov</E>.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>On February 21, 2012, the Postal Service filed a notice (R2012-6) with the Postal Regulatory Commission to temporarily reduce the prices for certain types of First-Class Mail and Standard Mail letters items that contain, in or on the mailpiece, a transactional two-dimensional barcode or similar print technology such as watermarks or tags (collectively “Mobile Barcode” or “Mobile Barcodes”) readable by consumer mobile devices. In recognition of the success of the mobile barcode promotion in the summer of 2011, the Postal Service offers a revised promotion from July 1, 2012, through August 31, 2012.</P>
        <P>In this final rule, the Postal Service provides a description of the conditions for eligibility for the price reduction for the mobile commerce and personalization promotion, and the revised mailing standards to implement the promotion.</P>
        <P>To be eligible, each Presorted and automation mailpiece in the mailing that is listed on the postage statement for that mailing must have a Mobile Barcode on the outside of each piece or on the contents within each piece. When scanned, the Mobile Barcode must lead the recipient of the mailpiece to either: a Web page that allows the recipient to purchase a product or service, or a personalized URL that leads to a Web page whose Web address and content are unique to the mailpiece recipient. In both cases, the Web site must remain mobile-optimized. Mobile Barcodes that direct consumers to Web pages that allow payment for prior or future purchases, or encourage enrollment in online bill payment or paperless statement services are not eligible for the discount. Mailpieces with Mobile Barcodes that convey postage information, destination, sender, or a machinable serial number for security also are not eligible for the discount.</P>
        <P>The promotion provides an upfront price reduction of 2 percent of the eligible postage for qualifying mailpieces containing Mobile Barcodes as described above. Qualifying mailings are Presorted and automation mailings of First-Class Mail cards, letters, and flats, and Standard Mail (including Nonprofit) letters and flats. Commingled, co-mailed and combined mailings are allowed, but a separate postage statement is required for mailpieces with Mobile Barcodes.</P>

        <P>Eligible mailings must be accompanied by electronic documentation. Mailings that are prepared by an entity other than the mail owner must indicate the identity of the owner in the electronic documentation. The electronic documentation must identify the mail owner and mail preparer in the “By/For” fields for all mailings, either by Customer Registration ID (CRID), Mailer ID (MID) or other account type that is assigned by USPS®. Mailings of automation letters or flats must have Intelligent Mail® barcodes. Mailpieces with POSTNET<E T="51">TM</E>barcodes will not be eligible for the price reduction.</P>
        <P>The price reduction will be taken off the postage amount due at the time of mailing, and there will be no refunds or postage credit provided under this promotion. The promotion discount does not apply to single-piece First-Class Mail pieces including residual single-piece First-Class Mail pieces on a postage statement for Presorted and automation mailings.</P>
        <HD SOURCE="HD1">Postage Payment Methods</HD>
        <P>Postage payment methods will be restricted to permit imprint, metered postage, or precancelled stamps. Pieces with metered postage must bear an exact amount of postage as stipulated by the class and shape of mail. Affixed postage values for metered mailings will be as follows:</P>
        <GPOTABLE CDEF="s25,7" COLS="02" OPTS="L0,tp0,p0,8/9,g1,t1,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1"/>
            <CHED H="1"/>
          </BOXHD>
          <ROW>
            <ENT I="01">First-Class Mail postcards</ENT>
            <ENT>$0.20</ENT>
          </ROW>
          <ROW>
            <ENT I="01">First-Class Mail automation and (PRSTD) machinable letters</ENT>
            <ENT>0.25</ENT>
          </ROW>
          <ROW>
            <ENT I="01">First-Class Mail nonmachinable letters</ENT>
            <ENT>0.45</ENT>
          </ROW>
          <ROW>
            <ENT I="01">First-Class Mail automation and Presorted flats</ENT>
            <ENT>0.35</ENT>
          </ROW>
          <ROW>
            <ENT I="01">STD Mail Regular letters</ENT>
            <ENT>0.12</ENT>
          </ROW>
          <ROW>
            <ENT I="01">STD Mail Regular flats</ENT>
            <ENT>0.13</ENT>
          </ROW>
          <ROW>
            <ENT I="01">STD Nonprofit letters</ENT>
            <ENT>0.05</ENT>
          </ROW>
          <ROW>
            <ENT I="01">STD Nonprofit flats</ENT>
            <ENT>0.06</ENT>
          </ROW>
        </GPOTABLE>
        <P>Mailings with postage paid by metered or precancelled stamp postage will have the percentage discount deducted from the additional postage due, except for Value Added Refund mailings, which may include the amount of the discount with the amount to be refunded.</P>
        <P>The mobile barcode promotion discount cannot be combined with other incentives, with the exception of the full-service Intelligent Mail barcode discount.</P>
        <HD SOURCE="HD1">Promotion Dates and More Information</HD>

        <P>To participate in the promotion, customers must register on the Business<PRTPAGE P="15606"/>Customer Gateway at<E T="03">www.gateway.usps.com</E>and specify which permits and CRIDs will participate in the promotion. Registration opens May 1, 2012, and must be completed at least 24 hours prior to the first mailing date. The Postal Service will implement the promotion and temporary price reduction for mailings made on July 1, 2012, through August 31, 2012. Plant-verified drop shipment (PVDS) mailings accepted no later than August 31, 2012, may be entered at destinations through September 15, 2012. Program requirements, including updated FAQs, are available on the RIBBS Web site at<E T="03">https://ribbs.usps.gov/index.cfm?page=mobilebarcode</E>or by email to<E T="03">mobilebarcode@usps.gov.</E>
        </P>
        <P>The Postal Service adopts the following changes to<E T="03">Mailing Standards of the United States Postal Service,</E>Domestic Mail Manual (DMM), which is incorporated by reference in the<E T="03">Code of Federal Regulations.</E>See 39 CFR 111.1.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 39 CFR Part 111</HD>
          <P>Administrative practice and procedure, Postal Service.</P>
        </LSTSUB>
        
        <P>Accordingly, 39 CFR part 111 is amended as follows:</P>
        <REGTEXT PART="111" TITLE="39">
          <PART>
            <HD SOURCE="HED">PART 111—[AMENDED]</HD>
          </PART>
          <AMDPAR>1. The authority citation for 39 CFR part 111 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>5 U.S.C. 552(a); 13 U.S.C. 301-307; 18 U.S.C. 1692-1737; 39 U.S.C. 101, 401, 403, 404, 414, 416, 3001-3011, 3201-3219, 3403-3406, 3621, 3622, 3626, 3632, 3633, and 5001.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="111" TITLE="39">
          <AMDPAR>2. Revise the following sections of the<E T="03">Mailing Standards of the United States Postal Service,</E>Domestic Mail Manual (DMM):</AMDPAR>
          <HD SOURCE="HD1">Mailing Standards of the United States Postal Service, Domestic Mail Manual (DMM):</HD>
          <STARS/>
          <HD SOURCE="HD1">700Special Standards</HD>
          <STARS/>
          <HD SOURCE="HD1">709Experimental and Temporary Classifications</HD>
          <STARS/>
          <P>
            <E T="03">[Revise the title of 3.0 as follows:]</E>
          </P>
          <HD SOURCE="HD1">3.0Mobile Commerce and Personalization Promotion</HD>
          <HD SOURCE="HD1">3.1Program Description and Scope</HD>
          <P>
            <E T="03">[Revise 3.1 by incorporating the text of current items a and b into the body of 3.1 and revising the text as follows:]</E>
          </P>
          <P>The mobile commerce and personalization promotion provides a two percent discount for pieces mailed at Presorted and automation prices in mailings of First-Class Mail cards, letters, and flats, and Standard Mail (including Nonprofit) letters and flats that include a transactional two-dimensional mobile barcode when the mailpieces meet all the conditions in these standards. Images such as watermarks and tags that, when scanned, direct consumers to mobile-optimized sites under conditions in 3.0 are also eligible. Automation pieces must bear Intelligent Mail barcodes; pieces with POSTNET barcodes are not eligible for this promotion. The promotion is valid for mailings entered from July 1, 2012 through August 31, 2012. Plant-verified drop shipment (PVDS) mailings meeting all relevant standards may be accepted at origin as late as August 31, 2012 if they are entered no later than September 15, 2012 at the destination.</P>
          <HD SOURCE="HD1">3.2Eligibility Standards</HD>
          <P>
            <E T="03">[Revise 3.2 as follows:]</E>
          </P>

          <P>To be eligible for the two percent discount, customers must register on Business Customer Gateway at<E T="03">gateway.usps.com</E>, and specify which permits and CRIDs will participate in the promotion. Registration opens May 1, 2012, and must be completed at least 24 hours prior to the first mailing date. Mailpieces must be mailed under the following conditions:</P>
          <P>a. A two-dimensional mobile barcode or similar image must be on each mailpiece, either on the outside or printed on the contents of the piece. Brief instructions or directional copy must be printed near the barcode to instruct the recipient to scan the barcode. One-dimensional barcodes do not qualify.</P>
          <P>b. The mobile barcode must be readable by a mobile device and must lead to a mobile-optimized Web site. The barcode must be relevant to the contents of the mailpiece. Scanning the barcode must lead the consumer to a Web page that allows the recipient a good or service on the mobile device, or to a personalized URL that leads to a Web page unique to an individual recipient. In either situation, the Web site must remain mobile-optimized. Barcodes with links that direct consumers to sites that allow payment for prior or future purchases or that encourage enrollment in online bill payment or paperless statement services are not eligible for the discount. Mailpieces with mobile barcodes that convey postage information, destination, sender, or a machinable serial number for security also are not eligible for the discount.</P>
          <P>c. The mailpieces with mobile barcodes must be one of the following:</P>
          <P>1. Presorted or automation First-Class Mail cards, letters, or flats. Automation pieces must bear Intelligent Mail barcodes.</P>
          <P>2. Standard Mail (including Nonprofit) letters or flats.</P>
          <P>d. Postage must be paid by permit imprint or by affixing metered postage or a precanceled stamp to each piece of mail; the postage statement and mailing documentation must be submitted electronically. Mailings that are prepared by an entity other than the mail owner must indicate the owner's identity in the electronic documentation (“eDoc”). The eDoc must identify the mail owner and mail preparer in the By/For fields, either by Customer Registration ID (CRID), Mailer ID (MID) or other account type assigned by the USPS. All Presorted and automation pieces declared on a postage statement must contain a mobile barcode that qualifies for the discount.</P>
          <P>e. Mailers must provide the USPS acceptance unit with an unaddressed sample of the mailpiece that contains a mobile barcode. If mobile personalization is used, at least two samples must be submitted, demonstrating that the web addresses are unique to each addressee. Mailers must also retain, until October 31, 2012, a sample of each mailpiece claiming a discount.</P>
          <P>f. Other than a full-service Intelligent Mail discount (see 705.24), no otherincentives apply for mailpieces claiming a discount under this promotion.</P>
          <P>g. Participants must agree to participate in a survey conducted during or afterthe promotional period.</P>
          <P>h. Federal government official mailings under OMAS are not eligible for thispromotion.</P>
          <HD SOURCE="HD1">3.3Discount</HD>
          <P>
            <E T="03">[Revise the first sentence of 3.3 and add new second and third sentences as follows:]</E>
          </P>

          <P>Mailers must claim the two percent postage discount on the postage statement at the time the statement is electronically submitted. Mailings with postage affixed will deduct the discount amount from the additional postage due, except that mail service providers authorized to submit Value Added Refund (VAR) mailings may include the refund for the incentive discount in the VAR amount. Pieces with metered postage must bear an exact amount of postage as stipulated by the class and shape of mail. Affixed postage values for metered mailings may be found in the<PRTPAGE P="15607"/>
            <E T="04">Federal Register</E>notice available at<E T="03">pe.usps.com</E>. * * *</P>
          <STARS/>
          <P>We will publish an appropriate amendment to 39 CFR part 111 to reflect these changes.</P>
          <SIG>
            <NAME>Stanley F. Mires,</NAME>
            <TITLE>Attorney, Legal Policy and Legislative Advice.</TITLE>
          </SIG>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6086 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 7710-12-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <CFR>40 CFR Part 52</CFR>
        <DEPDOC>[EPA-R01-OAR-2010-0380; A-1-FRL-9648-5 ]</DEPDOC>
        <SUBJECT>Approval and Promulgation of Air Quality Implementation Plans; Connecticut; Determination of Attainment of the One-Hour Ozone Standard for the Greater Connecticut Area</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 EPA is determining that the Greater Connecticut serious one-hour ozone nonattainment area did not meet the applicable deadline of November 15, 2007, for attaining the one-hour National Ambient Air Quality Standard (NAAQS) for ozone. This determination is based upon complete, quality-assured, certified ambient air monitoring data that show the area had an expected ozone exceedance rate above the level of the now revoked one-hour ozone NAAQS for the 2005-2007 monitoring period. Separate from and independent of this determination, EPA is also determining that the Greater Connecticut serious one-hour ozone nonattainment area currently attains the now revoked one-hour NAAQS for ozone, based upon complete, quality-assured, certified ambient air monitoring data for 2008-2010. The area first attained the one-hour NAAQS during the 2006-2008 monitoring period, and continued in attainment during the 2007-2009, and 2008-2010 monitoring periods. Quality assured and quality controlled, but not yet certified ozone data available for 2011 indicate that the area continues to attain the one-hour NAAQS. These determinations are made under the Clean Air Act.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>This rule is effective on April 16, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>EPA has established a docket for this action under Docket Identification No. EPA-R01-OAR-2011-0711. All documents in the docket are listed on the<E T="03">www.regulations.gov</E>Web site. Although listed in the index, some information is not publicly available, i.e., CBI or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, is not placed on the Internet and will be publicly available only in hard copy form. Publicly available docket materials are available either electronically through<E T="03">www.regulations.gov</E>or in hard copy at the Office of Ecosystem Protection, U.S. Environmental Protection Agency, EPA New England Regional Office, Office of Ecosystem Protection, Air Quality Planning Unit, 5 Post Office Square—Suite 100, Boston, MA 02109-3912. EPA requests that if at all possible, you contact the contact listed in the<E T="02">FOR FURTHER INFORMATION CONTACT</E>section to schedule your inspection. The Regional Office's official hours of business are Monday through Friday, 8:30 to 4:30, excluding legal holidays.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Richard P. Burkhart, Air Quality Planning Unit, U.S. Environmental Protection Agency, EPA New England Regional Office, 5 Post Office Square, Suite 100, Boston, MA 02109-3912, telephone number (617) 918-1664, fax number (617) 918-0664, email<E T="03">Burkhart.Richard@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 following outline is provided to aid in locating information in this preamble.</P>
        
        <EXTRACT>
          <FP SOURCE="FP-2">I. What actions is EPA taking?</FP>
          <FP SOURCE="FP-2">II. What is the effect of these actions?</FP>
          <FP SOURCE="FP-2">III. Final Action</FP>
          <FP SOURCE="FP-2">IV. Statutory and Executive Order Reviews</FP>
        </EXTRACT>
        <HD SOURCE="HD1">I. What actions is EPA taking?</HD>
        <P>EPA is taking two separate and independent actions for the Greater Connecticut one-hour ozone serious nonattainment area (hereafter, “the Greater Connecticut area”).</P>
        <HD SOURCE="HD2">A. Determination of Failure To Attain by Applicable Attainment Date</HD>
        <P>EPA is determining that the Greater Connecticut area did not attain the one-hour ozone National Ambient Air Quality Standard (NAAQS) by the applicable attainment date, November 15, 2007. This determination is based upon complete, quality-assured and certified air quality monitoring data for the 2005 through 2007 ozone seasons.</P>
        <HD SOURCE="HD2">B. Determination of Current Attainment</HD>
        <P>In addition, EPA is determining that the Greater Connecticut area is currently attaining the one-hour ozone NAAQS based upon complete, quality-assured and certified ambient air monitoring data showing the area currently monitored attainment of the one-hour ozone NAAQS, and that it has done so continuously since the 2006-2008 monitoring period.</P>
        <P>Other specific details related to these determinations and the rationale for EPA's action are explained in the Notice of Proposed Rulemaking (NPR) published on November 23, 2011 (76 FR 72377) and will not be restated here. No comments were received on the NPR.</P>
        <HD SOURCE="HD1">II. What is the effect of these actions?</HD>

        <P>After revocation of the one-hour ozone standard, EPA must continue to provide a mechanism to give effect to the one-hour anti-backsliding requirements. See<E T="03">SCAQMD</E>v.<E T="03">EPA,</E>47 F.3d 882, at 903. In keeping with this responsibility, EPA has determined that Greater Connecticut failed to attain the one-hour ozone standard by its applicable attainment date. Consistent with 40 CFR 51.905(e)(2), and the South Coast decision, upon revocation of the one-hour ozone NAAQS for an area, EPA is no longer obligated to determine whether an area has attained the one-hour NAAQS, except insofar as it relates to effectuating the anti-backsliding requirements that are specifically retained. EPA's determination here is linked solely to required, one-hour anti-backsliding, contingency measures. A final determination of failure to attain will not result in reclassification of the area under the revoked one-hour standard, nor is EPA identifying or determining any new one-hour reclassification for the area. EPA is no longer required to reclassify an area to a higher classification for the one-hour ozone NAAQS based upon a determination that the area failed to attain that NAAQS by its attainment date. See 40 CFR 51.905(e)(2)(i)(B). Moreover, EPA has previously approved the one-hour ozone attainment demonstration and Reasonable Further Progress (ROP) plans for this area, and in doing so noted that although there were no state implementation plan contingency measure reductions applicable to the Greater Connecticut area for failure to attain, there were federal measures the state had not accounted for in its attainment demonstration that provided more reductions than necessary to serve the purpose of contingency measures for this area. See 66 FR 634, January 3, 2001. In addition, EPA has also determined that the Greater Connecticut area attained the one-hour ozone standard in 2008, and continues to<PRTPAGE P="15608"/>attain this standard. In this context, EPA has also determined that there are not any additional obligations, including those relating to one-hour ozone contingency measures, for the Greater Connecticut area under the one-hour ozone standard.</P>
        <HD SOURCE="HD1">III. Final Action</HD>
        <P>EPA is determining that the Greater Connecticut one-hour ozone nonattainment area did not meet its applicable one-hour ozone attainment date of November 15, 2007, based on 2005-2007 quality-assured ozone monitoring data. Separate from and independent of this determination, EPA is also determining that the Greater Connecticut one-hour ozone nonattainment area is currently attaining the one-hour ozone standard, based on the most recent three years (2008-2010) of complete, quality-assured ozone monitoring data at all monitoring sites in the area. EPA's review of the data shows that the area began attaining the one-hour ozone standard in the 2006-2008 period, and has continued to attain this standard through the 2007-2009 and 2008-2010 monitoring periods. Quality assured and quality controlled, but not yet certified, ozone data available for 2011 indicate that the area continues to attain the one-hour NAAQS.</P>
        <HD SOURCE="HD1">IV. Statutory and Executive Order Reviews</HD>
        <P>These actions make determinations of attainment based on air quality, result in the suspension of certain Federal requirements, and would not impose additional requirements beyond those imposed by state law. For that reason, these actions:</P>
        <P>• Are not “significant regulatory actions” 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 economically significant regulatory actions based on health or safety risks subject to Executive Order 13045 (62 FR 19885, April 23, 1997);</P>
        <P>• Are not significant regulatory actions 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 Clean Air Act; 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, these actions do 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 these actions 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). This rule is effective on April 16, 2012.</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 May 15, 2012. 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 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, Intergovernmental relations, Nitrogen dioxide, Ozone, Reporting and recordkeeping requirements, Volatile organic compounds.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: March 8, 2012.</DATED>
          <NAME>H. Curtis Spalding,</NAME>
          <TITLE>Regional Administrator, EPA New England.</TITLE>
        </SIG>
        
        <P>Part 52 of 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—[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 et seq.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">
          <SUBPART>
            <HD SOURCE="HED">Subpart H—Connecticut</HD>
          </SUBPART>
          <AMDPAR>2. Section 52.377 is amended by adding paragraph (i) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 52.377</SECTNO>
            <SUBJECT>Control strategy: Ozone.</SUBJECT>
            <STARS/>
            <P>(i) Determination of Attainment for the One-Hour Ozone Standard. Effective April 16, 2012, EPA is determining that the Greater Connecticut one-hour ozone nonattainment area did not meet its applicable one-hour ozone attainment date of November 15, 2007, based on 2005-2007 complete, quality-assured ozone monitoring data. Separate from and independent of this determination, EPA is determining that the Greater Connecticut one-hour ozone nonattainment area met the one-hour ozone standard, based on 2008-2010 complete, quality-assured ozone monitoring data at all monitoring sites in the area. EPA's review of the ozone data shows that the area began attaining the one-hour ozone standard during the 2006-2008 monitoring period, and has continued attaining the one-hour standard through the 2007-2009 and 2008-2010 monitoring periods.</P>
          </SECTION>
        </REGTEXT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6424 Filed 3-15-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-HQ-OAR-2011-0081; FRL-9648-9]</DEPDOC>
        <RIN>RIN 2060-AR42</RIN>
        <SUBJECT>Revisions to Final Response to Petition From New Jersey Regarding SO2 Emissions From the Portland Generating Station</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <PRTPAGE P="15609"/>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Withdrawal of direct final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The EPA issued “Revisions to Final Response to Petition From New Jersey Regarding SO<E T="52">2</E>Emissions From the Portland Generating Station” as a direct final rule on December 22, 2011. Because the EPA received an adverse comment to the parallel proposal issued under the same name on December 22, 2011, we are withdrawing the direct final rule amendments to “Revisions to Final Response to Petition From New Jersey Regarding SO<E T="52">2</E>Emissions From the Portland Generating Station” published in the<E T="04">Federal Register</E>on December 22, 2011.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>

          <P>As of March 16, 2012, the EPA withdraws the direct final rule amendments published on December 22, 2011.<E T="03">See</E>76 FR 79541.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>The EPA has established a docket for this action under Docket ID No. EPA-HQ-OAR-2011-0081. All documents in the docket are listed on the<E T="03">http://www.regulations.gov</E>Web site. Although listed in the index, some information is not publicly available, e.g., confidential business information 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 at Air Docket, EPA/DC, EPA West, Room 3334, 1301 Constitution Ave., NW., Washington, DC. The Public Reading Room is open from 8:30 a.m. to 4:30 p.m., Monday through Friday, excluding legal holidays. The telephone number for the Public Reading Room is (202) 566-1744.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Mr. Todd Hawes (919) 541-5591,<E T="03">hawes.todd@epa.gov,</E>or Ms. Gobeail McKinley (919) 541-5246,<E T="03">mckinley.gobeail@epa.gov,</E>Office of Air Quality Planning and Standards, Air Quality Policy Division, Mail Code C539-04, Research Triangle Park, NC 27711.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background Information</HD>

        <P>The EPA issued “Revisions to Final Response to Petition From New Jersey Regarding SO<E T="52">2</E>Emissions From the Portland Generating Station” as a direct final rule on December 22, 2011.<E T="03">See</E>76 FR 79541. The direct final rule revised the preamble and rule text to the “Final Response to Petition From New Jersey Regarding SO<E T="52">2</E>Emissions From the Portland Generating Station” (Portland) published November 7, 2011, to clarify that Portland significantly contributes to nonattainment or interferes with maintenance of the 1-hour sulfur dioxide national ambient air quality standard in the State of New Jersey, and not in specific counties within the state.<E T="03">See</E>76 FR 69052. The revisions did not change the conclusions that the EPA made in the final rule and did not affect the emission limits, increments of progress, compliance schedules, or reporting provisions.</P>

        <P>The EPA issued a parallel proposal under the same name on December 22, 2011, that proposed to make the same revisions outlined in the direct final and solicited comment on those revisions.<E T="03">See</E>76 FR 79574. We stated in the direct final rule amendments that if we received adverse comment to the parallel proposal by February 21, 2012, we would publish a timely notice of withdrawal of the direct final rule in the<E T="04">Federal Register.</E>We received one adverse comment on the proposed amendments on February 21, 2012. We are consequently withdrawing the “Revisions to Final Response to Petition From New Jersey Regarding SO<E T="52">2</E>Emissions From the Portland Generating Station” published as a direct final rule in the<E T="04">Federal Register</E>on December 22, 2012 as of March 16, 2012.<E T="03">See</E>76 FR 79541. The EPA will address the adverse comment in a subsequent final action based on the parallel proposal also published on December 22, 2011.<E T="03">See</E>76 FR 79574. As stated in the parallel proposal, we will not institute a second comment period on this action.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 40 CFR Part 52</HD>
          <P>Approval and promulgation of implementation plans, Environmental protection, Administrative practice and procedures, Air pollution control, Incorporation by reference, Intergovernmental relations, and Reporting and recordkeeping requirements, Sulfur dioxide.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: March 12, 2012.</DATED>
          <NAME>Lisa P. Jackson,</NAME>
          <TITLE>Administrator.</TITLE>
        </SIG>
        <REGTEXT PART="52" TITLE="40">
          <PART>
            <HD SOURCE="HED">PART 52—[AMENDED]</HD>

            <P>Accordingly, the amendments to the rule published in the<E T="04">Federal Register</E>on December 22, 2011 (76 FR 79541) on pages 79541-79544 are withdrawn as of March 16, 2012.</P>
            
          </PART>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6427 Filed 3-15-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 799</CFR>
        <DEPDOC>[EPA-HQ-OPPT-2005-0033; FRL-9335-6]</DEPDOC>
        <RIN>RIN 2070-AD16</RIN>
        <SUBJECT>Revocation of TSCA Section 4 Testing Requirements for Certain High Production Volume Chemical Substances</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Direct final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>EPA is revoking certain testing requirements for six chemical substances and all the testing requirements for four chemical substances. EPA is basing its decision to take this action on information received since publication of the first test rule for certain high production volume chemical substances (HPV1). HPV1 established testing requirements for those 10 chemical substances. On the effective date of this direct final rule, persons who export or intend to export the four chemical substances for which all the testing requirements are revoked are no longer subject to section 12(b) of the Toxic Substance Control Act (TSCA) export notification requirements triggered by HPV1.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>

          <P>This direct final rule is effective May 15, 2012 without further notice, unless EPA receives adverse comment in writing, or a request to present comment orally, on or before April 16, 2012. If EPA receives adverse comment, or a written request for an opportunity to present oral comments, EPA will publish a timely withdrawal in the<E T="04">Federal Register</E>informing the public that this direct final rule, or relevant portions of this direct final rule, will not take effect. If you write EPA to request an opportunity to present oral comments on or before April 16, 2012, EPA will hold a public meeting on this direct final rule in Washington, DC. The announcement of the meeting will be published in the<E T="04">Federal Register</E>.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Submit your comments, identified by docket identification (ID) number EPA-HQ-OPPT-2005-0033, by one of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>Follow the online instructions for submitting comments.</P>
          <P>•<E T="03">Mail:</E>Document Control Office (7407M), Office of Pollution Prevention and Toxics (OPPT), Environmental Protection Agency, 1200 Pennsylvania Ave. NW., Washington, DC 20460-0001.</P>
          <P>•<E T="03">Hand Delivery:</E>OPPT Document Control Office (DCO), EPA East Bldg.,<PRTPAGE P="15610"/>Rm. 6428, 1201 Constitution Ave. NW., Washington, DC. Attention: Docket ID Number EPA-HQ-OPPT-2005-0033. The DCO is open from 8 a.m. to 4 p.m., Monday through Friday, excluding legal holidays. The telephone number for the DCO is (202) 564-8930. Such deliveries are only accepted during the DCO's normal hours of operation, and special arrangements should be made for deliveries of boxed information.</P>
          <P>
            <E T="03">Instructions:</E>Direct your comments to docket ID number EPA-HQ-OPPT-2005-0033. EPA's policy is that all comments received will be included in the docket without change and may be made available online at<E T="03">http://www.regulations.gov,</E>including any personal information provided, unless the comment includes information claimed to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Do not submit information that you consider to be CBI or otherwise protected through regulations.gov or email. The regulations.gov Web site is an “anonymous access” system, which means EPA will not know your identity or contact information unless you provide it in the body of your comment. If you send an email comment directly to EPA without going through regulations.gov, your email address will be automatically captured and included as part of the comment that is placed in the docket and made available on the Internet. If you submit an electronic comment, EPA recommends that you include your name and other contact information in the body of your comment and with any disk or CD-ROM you submit. If EPA cannot read your comment due to technical difficulties and cannot contact you for clarification, EPA may not be able to consider your comment. Electronic files should avoid the use of special characters, any form of encryption, and be free of any defects or viruses.</P>
          <P>
            <E T="03">Docket:</E>All documents in the docket are listed in the docket index available at<E T="03">http://www.regulations.gov.</E>Although listed in the index, some information is not publicly available, e.g., CBI or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, is not placed on the Internet and will be publicly available only in hard copy form. Publicly available docket materials are available in the electronic docket at<E T="03">http://www.regulations.gov,</E>or, if only available in hard copy, at the OPPT Docket. The OPPT Docket is located in the EPA Docket Center (EPA/DC) at Rm. 3334, EPA West Bldg., 1301 Constitution Ave. NW., Washington, DC. The EPA/DC Public Reading Room hours of operation are 8:30 a.m. to 4:30 p.m., Monday through Friday, excluding legal holidays. The telephone number of the EPA/DC Public Reading Room is (202) 566-1744, and the telephone number for the OPPT Docket is (202) 566-0280. Docket visitors are required to show photographic identification, pass through a metal detector, and sign the EPA visitor log. All visitor bags are processed through an X-ray machine and subject to search. Visitors will be provided an EPA/DC badge that must be visible at all times in the building and returned upon departure.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>
            <E T="03">For technical information contact:</E>Catherine Roman, Chemical Control Division, Office of Pollution Prevention and Toxics, Environmental Protection Agency, 1200 Pennsylvania Ave. NW., Washington, DC 20460-0001; telephone number: (202) 564-8157; email address:<E T="03">roman.catherine@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>
        <P/>
        <HD SOURCE="HD1">I. General Information</HD>
        <HD SOURCE="HD2">A. Does this action apply to me?</HD>

        <P>This action is directed to the public in general and may be of particular interest to those persons who manufacture (defined by statute to include import), process, or export the chemical substances identified in this direct final rule. Because other persons may also be interested, the Agency has not attempted to describe all the specific persons that may be affected by this action. If you have any 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="HD2">B. What should I consider as I prepare my comments for EPA?</HD>
        <P>1.<E T="03">Submitting CBI.</E>Do not submit this information to EPA through regulations.gov or email. Clearly mark the part or all of the information that you claim to be CBI. For CBI information in a disk or CD-ROM that you mail to EPA, mark the outside of the disk or CD-ROM that you mail to EPA, mark the outside of the disk or CD-ROM as CBI and then identify electronically within the disk or CD-ROM the specific information that is claimed as CBI. In addition to one complete version of the comment that includes information claimed as CBI, a copy of the comment that does not contain the information claimed as CBI must be submitted for inclusion in the public docket. Information so marked will not be disclosed except in accordance with procedures set forth in 40 CFR part 2.</P>
        <P>2.<E T="03">Tips for preparing your comments.</E>When submitting comments, remember to:</P>

        <P>i. Identify the document by docket ID number and other identifying information (subject heading,<E T="04">Federal Register</E>date and page number).</P>
        <P>ii. Follow directions. The Agency may ask you to respond to specific questions or organize comments by referencing a Code of Federal Regulations (CFR) part or section number.</P>
        <P>iii. Explain why you agree or disagree; suggest alternatives and substitute language for your requested changes.</P>
        <P>iv. Describe any assumptions and provide any technical information and/or data that you used.</P>
        <P>v. If you estimate potential costs or burdens, explain how you arrived at your estimate in sufficient detail to allow for it to be reproduced.</P>
        <P>vi. Provide specific examples to illustrate your concerns and suggest alternatives.</P>
        <P>vii. Explain your views as clearly as possible, avoiding the use of profanity or personal threats.</P>
        <P>viii. Make sure to submit your comments by the comment period deadline identified.</P>
        <HD SOURCE="HD1">II. Statutory Authority</HD>
        <P>Section 4(a) of TSCA authorizes EPA to require testing if certain findings are made. EPA is amending the chemical testing requirements for certain HPV chemical substances in 40 CFR 799.5085 because some of the findings that EPA made for 10 chemical substances are no longer supported. These findings were that:</P>
        <P>1. The chemical substances were produced in substantial quantities.</P>
        <P>2. There are insufficient data upon which the effects of manufacture, distribution, processing, use, or disposal of those chemical substances on health or the environment can reasonably be determined or predicted.</P>
        <P>3. Testing of the chemical substance with respect to such effects is necessary to develop such data. (See TSCA section 4(a)(1)(B)(i), (ii), and (iii); also, see Ref. 1).</P>
        <P>Unit III. discusses which findings are not supported for each specific chemical substance subject to this direct final rule.</P>
        <HD SOURCE="HD1">III. Amendment to Chemical Testing Requirements</HD>

        <P>EPA is amending the chemical testing requirements for certain HPV chemical<PRTPAGE P="15611"/>substances in 40 CFR 799.5085 by direct final rule. Specifically, this direct final rule revokes the testing requirements for the following four chemical substances: Acetyl chloride (CAS No. 75-36-5); imidodicarbonic diamide (CAS No. 108-19-0); methane, isocyanato- (CAS No. 624-83-9); and urea, reaction products with formaldehyde (CAS No. 68611-64-3). This direct final rule also revokes some of the testing requirements for the following six chemical substances: 9,10-Anthracenedione (CAS No. 84-65-1); 1-chlorododecane (CAS No. 112-52-7); phenol, 4,4′-methylenebis [2,6-bis(1,1-dimethylethyl)]- (CAS No. 118-82-1); methanesulfinic acid, hydroxyl-, monosodium salt (CAS No. 149-44-0); benzenesulfonic acid, [[4-[[4-(phenylamino)phenyl][4-(phenylimino)-2,5-cyclohexadien-1-ylidene]methyl]phenyl]amino]- (CAS No. 1324-76-1); and C.I. Solvent Black 7 (CAS No. 8005-02-5). EPA is basing its decision to revoke all testing requirements for four chemical substances and some of the testing requirements for six other chemical substances on information received since publication of HPV1 (40 CFR 799.5085), as described in this unit.</P>
        <HD SOURCE="HD2">A. Revocation of All Testing Requirements for Four Chemical Substances</HD>
        <P>1.<E T="03">Acetyl chloride.</E>EPA is revoking all testing requirements for acetyl chloride (CAS No. 75-36-5) because there is no longer support for the TSCA section 4(a)(1)(B)(i) “substantial production” finding for this chemical substance. “Substantial production” of a chemical substance under TSCA section 4(a)(1)(B)(i) is generally interpreted by EPA to be an aggregate production (including import) volume equaling or exceeding 1 million pounds per year. See EPA's TSCA section 4(a)(1)(B) Final Statement of Policy (“B” policy) (Ref. 2). The “substantial production” finding for this chemical substance was based on reports from several companies to the 2002 TSCA Inventory Update Reporting (IUR) rule. The Albemarle Corporation which manufactured and imported the largest volume of acetyl chloride, without which a finding of substantial production could not have been made, informed EPA in 2007 that its manufacture and importation of acetyl chloride at the time the test rule was promulgated were only for non-TSCA purposes (i.e., for use in pharmaceuticals) (Ref. 3), and was, therefore, not subject to HPV1.</P>
        <P>Three other companies had reported importing smaller volumes of acetyl chloride in the 2002 IUR, the sum of which would not have provided support for a finding of substantial production. Two of these companies, Tessenderlo Kerley, Inc., and a company, which claimed its name as CBI, have since ceased importation of acetyl chloride. Tessenderlo Kerley ceased importation several years ago, and the other company ceased importation over a year prior to the effective date of HPV1, April 17, 2006 (Ref. 4). Neither of these companies is, therefore, subject to HPV1. The third small importer, Chartkit Chemical Corporation, reported that it imported only a small amount of acetyl chloride after the effective date of HPV1 in 2006, but none since (Ref. 5). EPA's review of data in the 2006 IUR (which required reporting on chemical substances manufactured or imported during calendar year 2005) did not identify any companies manufacturing or importing acetyl chloride. (Chartkit Chemical Corporation did not import acetyl chloride in 2005, making a report to the 2006 IUR unnecessary.) Because the finding for substantial production for acetyl chloride was not supported when HPV1 was promulgated, the Agency is revoking all the testing requirements for acetyl chloride (CAS No. 75-36-5) by removing it from Table 2 in 40 CFR 799.5085(j).</P>
        <P>2.<E T="03">Imidodicarbonic diamide.</E>EPA is revoking all the testing requirements for imidodicarbonic diamide (CAS No. 108-19-0), also known as biuret, by removing imidodicarbonic diamide from Table 2 in 40 CFR 799.5085(j). EPA considers the test requirements for this chemical substance unnecessary at this time because sufficient data have been provided to allow the Agency to reverse its finding under TSCA section 4(a)(1)(B)(ii) for “insufficient data.” Information that satisfied HPV1's requirements was voluntarily submitted by The Fertilizer Institute (TFI) on behalf of a member company that manufactures the chemical substance as an impurity in its products. EPA considers a company that manufactures a chemical substance only as an impurity to be a Tier 2 manufacturer with regard to its obligations under HPV1. Although subject to HPV1 and responsible for providing reimbursement to persons in Tier 1, Tier 2 manufacturers do not have to respond to HPV1 with a letter of intent to test or a request for exemption, unless directed to do so by EPA through a document published in the<E T="04">Federal Register</E>. Although EPA did not publish such a document, TFI, acting on behalf of its member company, volunteered to provide information to EPA on the endpoints specified by HPV1 for that chemical substance. This information (Refs. 6-8) was provided to the Agency and found to meet the standards prescribed by EPA (Refs. 9-11) and is being made available in the docket for this direct final rule and will be added to the High Production Volume Information System (HPVIS).</P>
        <P>3.<E T="03">Methane, isocyanato.</E>EPA is revoking all the testing requirements for methane, isocyanato- (CAS No. 624-83-9) by removing it from Table 2 in 40 CFR 799.5085(j). On May 11, 2007, Bayer CropScience submitted a test plan and robust summaries of existing data for methane, isocyanato- along with a request that EPA determine if the robust summaries satisfied the Agency's need for data on physical/chemical properties (Ref. 12). In the same letter, Bayer CropScience requested a waiver for the requirement to determine an octanol-water partition coefficient and the requirement to conduct aquatic toxicity tests because of the extreme reactivity in water of methane, isocyanato-. Bayer CropScience also asked EPA to consider, as a substitute for aquatic toxicity studies of methane, isocyanato-, robust summaries of aquatic toxicity studies of dimethyl urea (CAS No. 96-31-1) (DMU), one of the two degradation products of methane, isocyanato- in water, the other being carbon dioxide. EPA concluded that the submitted data satisfied the Agency's need for data on the physical/chemical properties of boiling point, melting point, vapor pressure, and water solubility (Ref. 13). EPA also agreed that methane, isocyanato- hydrolyzes very rapidly and, as a result, an octanol-water partition coefficient is not relevant (Ref. 13). Because of the rapid hydrolysis of methane, isocyanato- to carbon dioxide and DMU, EPA is revoking the requirement to test for aquatic toxicity (fish acute toxicity,<E T="03">Daphnia</E>acute toxicity, and toxicity to algae). EPA believes that the aquatic toxicity studies of DMU, provided by Bayer CropScience, which the Agency reviewed and found adequate, provide information on the aquatic effects of methane, isocyanato- (Ref. 14). Therefore, EPA, in this direct final rule, is revoking the testing requirements for boiling point, melting point, vapor pressure, octanol-water partition coefficient, water solubility, fish acute toxicity,<E T="03">Daphnia</E>acute toxicity, and toxicity to algae for methane, isocyanato- by removing it from Table 2 in 40 CFR 799.5085(j).</P>
        <P>4.<E T="03">Urea, reaction products with formaldehyde.</E>EPA is revoking all the testing requirements for urea, reaction products with formaldehyde (CAS No. 68611-64-3) by removing it from Table<PRTPAGE P="15612"/>2 in 40 CFR 799.5085(j). EPA considers the test requirements for this chemical substance unnecessary at this time because sufficient data have been provided to allow the Agency to reverse its finding under TSCA section 4(a)(1)(B)(ii) for “insufficient data.” Information which satisfied HPV1's requirements was voluntarily submitted by TFI on behalf of its member companies that manufacture this chemical substance as an impurity in their products. EPA considers companies that manufacture a chemical substance only as an impurity to be Tier 2 manufacturers with regard to their obligations under HPV1. Although subject to HPV1 and responsible for providing reimbursement to persons in Tier 1, Tier 2 manufacturers did not have to respond to HPV1 with a letter of intent to test or a request for exemption, unless directed to do so by EPA through a document published in the<E T="04">Federal Register</E>. Despite the lack of an EPA published<E T="04">Federal Register</E>document, TFI, acting on behalf of its member companies, volunteered to provide information to EPA on the endpoints specified by HPV1 for this chemical substance. This information (Refs. 7 and 16) has been provided to the Agency and found to meet the standards for testing prescribed by EPA (Refs. 17-19) and is being made available in the docket for this direct final rule and will be added to HPVIS.</P>
        <HD SOURCE="HD2">B. Revocation of Some Test Requirements for Six Chemical Substances</HD>
        <P>1.<E T="03">9,10-Anthracenedione.</E>In a letter dated July 10, 2006, the Chemical Products Corporation (CPC) requested EPA's permission to submit the values for boiling point and vapor pressure of 9,10-anthracenedione (CAS No. 84-65-1) contained in the International Uniform Chemical Information Database (IUCLID) instead of conducting the tests required by HPV1 (Ref. 20). CPC stated that the ASTM methods specified by HPV1 would not work for 9,10-anthracenedione because the boiling point and vapor pressure listed for that chemical substance in IUCLID and the boiling point listed for that chemical substance in the “Handbook of Chemistry and Physics” (Ref. 21) fell outside the determination ranges of the ASTM methods. EPA agreed and approved CPC's request to submit IUCLID and other existing values because those values matched or were in close agreement with measured values in various literature sources (Ref. 22). CPC also requested a modification of the ASTM method E 324 to determine the melting point for 9,10-anthracenedione (Ref. 23). While evaluating this request, EPA reviewed available data on measured melting points of 9,10-anthracenedione and found the existing data to be in sufficiently close agreement that they could be used to satisfy the Agency's data need for that endpoint (Ref. 22). EPA is, therefore, revoking the requirement that the boiling point, vapor pressure, and melting point of 9,10-anthracenedione be determined by the ASTM methods specified in HPV1 and accepts the submitted existing data as sufficient to satisfy those data needs, making the testing requirements unnecessary. Therefore, EPA is revoking the testing requirements for boiling point, vapor pressure, and melting point for 9,10-anthracenedione by removing those requirements from those listed for 9,10-anthracenedione in Table 2 in 40 CFR 799.5085(j). The test requirements for 9,10-anthracenedione that are not revoked by this direct final rule include tests to determine octanol/water partition coefficient and water solubility, and to screen for reproduction/developmental toxicity. Studies responding to those test requirements have been submitted to the Agency (Ref. 24).</P>
        <P>2.<E T="03">1-Chlorododecane.</E>In a letter dated February 21, 2008, EPA informed Lonza, Inc., that the testing of 1-chlorododecane (CAS No. 112-52-7), which Lonza had committed to sponsor, did not have to include a test for melting point because, in publicly available documents, 1-chlorododecane is reported to be a liquid (Ref. 25). Therefore, EPA is revoking the testing requirement for melting point for 1-chlorododecane by removing that requirement from those listed for 1-chlorododecane in Table 2 in 40 CFR 799.5085(j). The test requirements for 1-chlorododecane that are not revoked by this direct final rule include tests for boiling point, vapor pressure, octanol/water partition coefficient, water solubility, biodegradation,<E T="03">Daphnia</E>chronic toxicity, toxicity to algae, acute mammalian toxicity, mutagenicity, chromosomal damage, and 28-day repeated-dose toxicity with a reproduction/developmental toxicity screen. Studies responding to those test requirements have been submitted to the Agency (Ref. 26).</P>
        <P>3.<E T="03">Phenol, 4,4′-methylenebis[2,6-bis(1,1-dimethylethyl)]-.</E>In letters dated May 12, 2006, July 14, 2006, May 1, 2007, and May 16, 2007 (Refs. 27-30), the Albemarle Corporation requested EPA to review existing data that it was submitting for phenol, 4,4′-methylenebis[2,6-bis(1,1-dimethylethyl)]- (CAS No. 118-82-1) to determine if they satisfied the Agency's need for data on water solubility, octanol/water partition coefficient, acute mammalian toxicity, bacterial reverse mutation, and screening level reproduction/developmental toxicity. EPA found that the data satisfied the Agency's data needs for those testing endpoints in HPV1, making the testing requirements unnecessary (Refs. 31-33). Therefore, EPA is revoking the testing requirements for water solubility, octanol/water partition coefficient, acute mammalian toxicity, bacterial reverse mutation assay, and a reproduction/developmental toxicity screen for phenol, 4,4′-methylenebis[2,6-bis(1,1-dimethylethyl)]- by removing those requirements from Table 2 in 40 CFR 799.5085(j). The test requirements for phenol, 4,4′-methylenebis[2,6-bis(1,1-dimethylethyl)]- that are not revoked by this direct final rule include tests for melting point, boiling point, vapor pressure, inherent biodegradation, and chromosomal damage. Studies responding to those test requirements have been submitted to the Agency (Ref. 34).</P>
        <P>4.<E T="03">Methanesulfinic acid, hydroxyl-, monosodium salt.</E>On May 14, 2007, the Sodium Formaldehyde Sulfoxylate Consortium (SFS Consortium) formed under the auspices of the Synthetic Organic Chemical Manufacturers Association (SOCMA) submitted existing data to satisfy some of the testing requirements for methanesulfinic acid, hydroxyl-, monosodium salt (CAS No. 149-44-0) (Ref. 35). The submitted studies used the dihydrate form of methanesulfinic acid, hydroxyl-, monosodium salt (CAS No. 6035-47-8) as the test substance to address the endpoints of inherent biodegradation, fish acute toxicity,<E T="03">Daphnia</E>acute toxicity, and toxicity to algae (Ref. 35). Although the hydrated form is identified by a different CAS number, in general, EPA does not recognize a hydrate as a separate entity from the corresponding anhydrous material for TSCA purposes, and accepts studies of the hydrated form of a chemical substance as predictive of the effects of the anhydrous chemical (Ref. 15). EPA found that the submitted study on ready biodegradation satisfied the need for information on biodegradability, making the test requirement for inherent biodegradation unnecessary (Refs. 36 and 37). The existing studies on fish acute toxicity,<E T="03">Daphnia</E>acute toxicity, and toxicity to algae were reviewed by the Agency and found to satisfy EPA's data needs for those endpoints (Ref. 38).</P>

        <P>In the test plan submitted with the May 14, 2007 letter, the SFS Consortium<PRTPAGE P="15613"/>requested that EPA revoke the requirement to determine vapor pressure because the chemical substance is an organo-metallic salt that does not volatilize (Ref. 35). The SFS Consortium also requested that EPA revoke the requirement to determine the octanol/water partition coefficient (log K<E T="52">ow</E>) because its estimated value was −6.17 and HPV1 did not require a determination of octanol/water partition coefficient if its estimated value is less than zero (Ref. 35). EPA agreed with the SFS Consortium's position that testing was not needed to determine vapor pressure (Ref. 39) and octanol/water partition coefficient (Ref. 40). Also, in the test plan submitted on May 14, 2007, (Ref. 35), the SFS Consortium reported that in a test to determine boiling point, the test substance decomposed. EPA, therefore, is waiving the test for boiling point (Ref. 41).</P>

        <P>EPA is revoking the testing requirements for boiling point, vapor pressure, octanol/water partition coefficient, biodegradation, fish acute toxicity,<E T="03">Daphnia</E>acute toxicity, and toxicity to algae for methanesulfinic acid, hydroxyl-, monosodium salt by removing those requirements from those listed for that chemical substance in Table 2 in 40 CFR 799.5085(j). The testing requirements for methanesulfinic acid, hydroxyl-, monosodium salt that are not revoked by this direct final rule include tests for melting point, water solubility, chromosomal damage, and 28-day repeated-dose toxicity with a reproduction/developmental toxicity screen. Studies responding to those test requirements, also using the dihydrate form of methanesulfinic acid, hydroxyl-, monosodium salt, were submitted to the Agency (Ref. 42).</P>
        <P>5.<E T="03">Benzenesulfonic acid, [[4-[[4-(phenylamino)phenyl][4-(phenylimino)-2,5-cyclohexadien-1-ylidene]methyl]phenyl]amino]-.</E>On July 17, 2006, the Color Pigments Manufacturers Association (CPMA) submitted a test plan for benzenesulfonic acid, [[4-[[4-(phenylamino)phenyl][4-(phenylimino)-2,5-cyclohexadien-1-ylidene]methyl]phenyl]amino]- (CAS No. 1324-76-1), also known as C.I. Pigment Blue 61. CPMA also submitted robust summaries of existing data which CPMA asked EPA to accept as satisfying some of the Agency's data needs for C.I. Pigment Blue 61. Some of the existing data described in the summaries addressed C.I. Pigment Blue 56, a close analog of C.I. Pigment Blue 61, which CPMA requested EPA to accept as satisfying the Agency's data needs for C.I. Pigment Blue 61, providing a structure-activity relationship (SAR) argument in the test plan to justify that request (Refs. 43 and 44). CPMA also asked EPA to accept results for water solubility and octanol/water partition coefficient which were obtained by using an alternative method, due to the extremely low predicted solubility of C.I. Pigment Blue 61, instead of the methods specified by the test rule (Ref. 43). Finally, CPMA asked EPA to accept that determining a melting point for C.I. Pigment Blue 61 was not relevant because the pigment thermally decomposes before it melts (Ref. 43).</P>
        <P>EPA reviewed the submitted information on physical/chemical properties and decided that melting point, boiling point, and vapor pressure determinations were not relevant because C.I. Pigment Blue 61 decomposes before it melts and the decomposition temperature had been reported (Ref. 45). EPA accepted the submitted data on water solubility as satisfying the Agency's data needs for that endpoint, but did not accept the calculated value submitted to satisfy the testing requirement for octanol/water partition coefficient (Ref. 45). EPA believes the calculated value would, most likely, underestimate the measured value (Ref. 45) required to be determined by HPV1.</P>
        <P>EPA reviewed CPMA's SAR argument concerning C.I. Pigment Blue 61 and C.I. Pigment Blue 56 and agreed that C.I. Pigment Blue 56 is an acceptable surrogate for C.I. Pigment Blue 61, thereby allowing adequate data on C.I. Pigment Blue 56 to satisfy data needs for C.I. Pigment Blue 61 (Ref. 46). As a result, a biodegradation study of C.I. Pigment Blue 56, found adequate by an EPA review, satisfies the need for biodegradation data on C.I. Pigment Blue 61 (Ref. 46). Likewise, a chromosomal damage test of C.I. Pigment Blue 56, which EPA reviewed and found adequate, will satisfy the data need for that endpoint (Ref. 47) for C.I. Pigment Blue 61. EPA's review of the existing data on C.I. Pigment Blue 61 found the studies on fish acute toxicity, mammalian acute toxicity, and bacterial mutation assay to be adequate to satisfy the data needs for those endpoints (Ref. 47). The existing study on repeated-dose toxicity, however, did not satisfy the test requirement for that endpoint (Ref. 47).</P>

        <P>Therefore, EPA is revoking the testing requirements for melting point, boiling point, vapor pressure, water solubility, biodegradation, fish acute toxicity, mammalian acute toxicity, bacterial reverse mutation, and chromosomal damage for C.I. Pigment Blue 61 by removing those requirements from those listed for that chemical substance in Table 2 in 40 CFR 799.5085(j). In order to clarify that test requirements for acute toxicity to<E T="03">Daphnia</E>and toxicity to algae had not been satisfied by existing studies, and that the fish acute toxicity test requirement had been satisfied, the test symbol C2 replaces C1 for C.I. Pigment Blue 61 in Table 2 in 40 CFR 799.5085(j). The testing requirements for C.I. Pigment Blue 61 that are not revoked by this direct final rule include tests for octanol/water partition coefficient, acute toxicity to<E T="03">Daphnia,</E>toxicity to algae, and combined 28-day repeated-dose toxicity with a reproduction/developmental toxicity screen. Studies responding to those test requirements were submitted to the Agency. The full studies were claimed to be CBI and are not available to the public, but robust summaries of those studies (Ref. 48) are in the docket.</P>
        <P>6.<E T="03">C.I. Solvent Black 7.</E>On July 29, 2006 and August 4, 2006, the Solvent Black 7 Consortium formed under the auspices of SOCMA submitted eight existing studies on C.I. Solvent Black 7 (CAS No. 8005-02-5) and requested EPA to determine if they satisfied some of the Agency's data needs specified in HPV1 (Ref. 49). EPA found that the studies satisfied the need for data on inherent biodegradation, fish acute toxicity,<E T="03">Daphnia</E>acute toxicity, toxicity to algae, acute mammalian toxicity, chromosomal damage, and repeated-dose 28-day oral toxicity in rodents, making those test requirements for C.I. Solvent Black 7 unnecessary (Ref. 50). Although the 28-day oral toxicity study in rodents was accepted, it lacked a required screening test for reproduction/developmental toxicity. Although a test for chronic toxicity to<E T="03">Daphnia</E>was not required for this chemical substance, SOCMA submitted a<E T="03">Daphnia magna</E>reproduction test because the log K<E T="52">ow</E>of C.I. solvent Black 7 is close to 4.2 and a log K<E T="52">ow</E>greater than 4.2 would have made a<E T="03">Daphnia</E>chronic toxicity test a requirement (Refs. 1 and 51). The submitted study was evaluated and was not found adequate to satisfy the objectives of a<E T="03">Daphnia</E>chronic toxicity study because the study was only 10 days long instead of 21 days, and only one concentration was tested and it was lethal, preventing observation of sub-lethal endpoints (Ref. 52).</P>

        <P>Therefore, EPA is revoking the testing requirements for inherent biodegradation, fish acute toxicity,<E T="03">Daphnia</E>acute toxicity, toxicity to algae, acute mammalian toxicity, chromosomal damage, and repeated-dose 28-day oral toxicity in rodents for C.I. Solvent Black 7 (CAS No. 8005-02-5) by removing those requirements from those listed for that chemical substance<PRTPAGE P="15614"/>in Table 2 in 40 CFR 799.5085(j). In order to clarify that the requirement for a reproduction/developmental toxicity screening test had not been satisfied, but that the requirement for a repeated-dose 28-day oral toxicity test had been satisfied, the test symbol F2 replaces F1 for C.I. Solvent Black 7 in Table 2 in 40 CFR 799.5085(j). The testing requirements not revoked by this direct final rule include the tests to determine five physical/chemical properties and to screen for reproduction/developmental toxicity. Studies responding to those test requirements have been submitted to the Agency (Refs. 51 and 53).</P>
        <HD SOURCE="HD1">IV. Economic Analysis</HD>
        <P>In the economic impact analysis of this direct final rule, the Agency estimated the total testing cost to industry to be $4.03 million for all 17 chemical substances, with an average of approximately $237,000 per chemical substance (Ref. 54). This total included an additional 25% in administrative costs. An amendment to HPV1 revoking testing requirements for Coke-Oven Light Oil (Coal) reduced the total cost to industry to an estimated $3.7 million for the remaining 16 chemical substances, with an average compliance cost of approximately $232,000 per chemical substance. This direct final rule would have the effect of further reducing the total testing cost by an estimated $1.5 million (approximately 41%), by eliminating all the testing requirements for acetyl chloride; imidodicarbonic diamide; methane, isocyanato-; and urea, reaction products with formaldehyde; as well as some of the testing requirements for 9,10-anthracenedione; 1-chlorododecane; phenol, 4,4′-methylenebis [2,6-bis (1,1-dimethylethyl)]-; methanesulfinic acid, hydroxy-, monosodium salt; benzenesulfonic acid, [[4-[[4-(phenylamino)phenyl][4-(phenylmino)-2,5-cyclohexadien-1-ylidene]methyl]phenyl]amino]-; and C.I. Solvent Black 7 (Ref. 55). In addition, the 25% administrative costs would be eliminated for these tests. The reduced total cost for the remaining 12 chemical substances with testing requirements is estimated to be $2.2 million (i.e., $3.7 million minus $1.5 million), with an average compliance cost per chemical substance of approximately $184,000 (Ref. 55).</P>
        <HD SOURCE="HD1">V. Export Notification</HD>
        <P>On the effective date of the revocations in this direct final rule of the TSCA section 4 testing requirements for acetyl chloride (CAS No. 75-36-5); imidodicarbonic diamide (CAS No. 108-19-0), methane, isocyanato- (CAS No. 624-83-9); and urea, reaction products with formaldehyde (CAS No. 68611-64-3), persons who export or intend to export those chemical substances will no longer be subject to any TSCA section 12(b) export notification requirements triggered by HPV1 (See 40 CFR part 707, subpart D). The export notification requirements remain the same for the other six chemical substances discussed in the preamble of this direct final rule that are listed as subject to the requirements of HPV1 (Ref. 1); these chemical substances are 9,10-anthracenedione (CAS No. 84-65-1); 1-chlorododecane (CAS No. 112-52-7); phenol, 4,4′-methylenebis[2,6-bis(1,1-dimethylethyl)]- (CAS No. 118-82-1); methanesulfinic acid, hydroxy-, monosodium salt (CAS No. 149-44-0); benzenesulfonic acid, [[4-[[4-(phenylamino)phenyl][4-(phenylimino)-2,5-cyclohexadien-1-ylidene]methyl]phenyl]amino]- (CAS No. 1324-76-1); and C.I. Solvent Black 7 (CAS No. 8005-02-5).</P>
        <HD SOURCE="HD1">VI. Direct Final Rule Procedures</HD>

        <P>EPA is publishing this direct final rule without prior proposal because the Agency views this as a non-controversial amendment and anticipates no adverse comment as this action simply revokes testing which is not feasible, or testing for which the substantial production finding was not supported, or testing for which EPA has adequate data at this time. This direct final rule is effective May 15, 2012 without further notice, unless EPA receives adverse comment or a written request for an opportunity to present oral comments on or before April 16, 2012. If EPA receives adverse comment or a written request for an opportunity to present oral comments on one or more distinct amendments, paragraphs, or sections of this direct final rule, the Agency will publish a timely withdrawal in the<E T="04">Federal Register</E>indicating which provisions will become effective and which provisions are being withdrawn due to adverse comment or a written request for an opportunity to present oral comments. Any distinct amendment, paragraph, or section of this direct final rule for which the Agency does not receive adverse comment or a request for an opportunity to present oral comments is effective May 15, 2012, notwithstanding any adverse comment or request on any other distinct amendment, paragraph, or section of this direct final rule. For any distinct amendment, paragraph, or section of this direct final rule that is withdrawn due to adverse comment or a request for an opportunity to present oral comments, EPA will publish a notice of proposed rulemaking in a future issue of the<E T="04">Federal Register</E>. The Agency will address the comment or request for an opportunity to present oral comments on any such distinct amendment, paragraph, or section as part of that notice of proposed rulemaking.</P>
        <HD SOURCE="HD1">VII. References</HD>

        <P>Each reference listed in this unit has a docket ID number (EPA-HQ-OPPT-2005-0033) followed by a four-digit document ID number. All document ID numbers are listed in numerical order in the docket. To access a particular document in the docket, go to<E T="03">http://www.regulations.gov</E>and follow the online instructions.</P>
        
        <EXTRACT>

          <FP SOURCE="FP-2">1. EPA. Testing of Certain High Production Volume Chemicals; Final Rule.<E T="04">Federal Register</E>(71 FR 13708, March 16, 2006) (FRL-7335-2). (Document ID number EPA-HQ-OPPT-2005-0033-0001).</FP>

          <FP SOURCE="FP-2">2. EPA. TSCA Section 4(a)(1)(B) Final Statement of Policy; Criteria for Evaluating Substantial Production, Substantial Release, and Substantial or Significant Human Exposure; Notice.<E T="04">Federal Register</E>(58 FR 28736, May 14, 1993) (FRL-4059-9). (Document ID number EPA-HQ-OPPT-2005-0033-0060).</FP>
          <FP SOURCE="FP-2">3. Albemarle Corporation. Letter from M.G. Clisby to Catherine Roman, Chemical Information and Testing Branch (CITB), Chemical Control Division (CCD), Office of Pollution Prevention and Toxics (OPPT), EPA. April 16, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0344).</FP>
          <FP SOURCE="FP-2">4. Tessenderlo Kerley, Inc. Email from Dawn Kominski to Catherine Roman, CITB, CCD, OPPT, EPA. March 23, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0342).</FP>
          <FP SOURCE="FP-2">5. Charkit Chemical Corporation. Letter from Bryant Hinnant to Document Control Office, OPPT, EPA. December 7, 2006. (Document ID number EPA-HQ-OPPT-2005-0033-0220).</FP>
          <FP SOURCE="FP-2">6. TFI. Submission for fulfillment of data requirements for biuret under TSCA section 4. July 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0343).</FP>
          <FP SOURCE="FP-2">7. Organisation for Economic Co-operation and Development (OECD). Screening Information Data Set (SIDS), Urea, CAS No.: 57-13-6. Also, a supporting document for biuret. 1994. (Document ID number EPA-HQ-OPPT-2005-0033-0360).</FP>
          <FP SOURCE="FP-2">8. IUCLID Data Set, Biuret, CAS No. 108-19-0. March 7, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0359).</FP>

          <FP SOURCE="FP-2">9. EPA. Memorandum from Tracy Williamson, Industrial Chemistry Branch (ICB), Economics, Exposure, and Technology Division (EETD), OPPT, to Greg Schweer, CITB, CCD, OPPT. Review of the physical-chemical endpoints for HPV orphan chemical biuret (CAS No.<PRTPAGE P="15615"/>108-19-0). Sept 17, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0356).</FP>
          <FP SOURCE="FP-2">10. EPA. Email from Robert Boethling, Exposure Assessment Branch (EAB), EETD, OPPT, to Greg Schweer, CITB, CCD, OPPT. Review of TFI submission on biuret. August 20, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0347).</FP>
          <FP SOURCE="FP-2">11. EPA. Email from David Brooks, High Production Volume Chemical Branch (HPVCB), Risk Assessment Division (RAD), OPPT, to Greg Schweer, CITB, CCD, OPPT. Review of biuret (CAS No. 108-19-0). October 2, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0358).</FP>
          <FP SOURCE="FP-2">12. Bayer CropScience. Letter to Document Control Office, OPPT, EPA, submitting a test plan and request for review of existing data on physical chemical properties and aquatic toxicity. May 11, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0249).</FP>
          <FP SOURCE="FP-2">13. EPA. Email from Tracy Williamson, ICB, EETD, OPPT, to Catherine Roman, CITB, CCD, OPPT. June 18, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0281).</FP>
          <FP SOURCE="FP-2">14. EPA. Email and attached review of aquatic studies of methane, isocyanato from David Brooks, HPVCB, RAD, OPPT, to Greg Schweer, CITB, CCD, OPPT. August 29, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0284).</FP>
          <FP SOURCE="FP-2">15. EPA. Emails on acceptability of studies on dihydrate form of CAS No. 149-44-0. August 18, 2009. (Document ID number EPA-HQ-OPPT-2005-0033-0357).</FP>
          <FP SOURCE="FP-2">16. TFI. Submission for Fulfillment of Data Requirements for Urea, Reaction Products with Formaldehyde under TSCA Section 4. Revised March 2008. (Document ID number EPA-HQ-OPPT-2005-0033-0361).</FP>
          <FP SOURCE="FP-2">17. EPA. Memorandum from Kathryn Schechter, ICB, EETD, OPPT, to Greg Schweer, CITB, CCD, OPPT. September 13, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0345).</FP>
          <FP SOURCE="FP-2">18. EPA. Email from David Brooks, HPVCB, RAD, OPPT, to Mike Mattheisen and Catherine Roman, CITB, CCD, OPPT. April 23, 2008. (Document ID number EPA-HQ-OPPT-2005-0033-0346).</FP>

          <FP SOURCE="FP-2">19. EPA. Email from Robert Boethling, EAB, EETD, OPPT, to Greg Schweer, CITB, CCD, OPPT. August 14, 2007. Includes copyrighted attachment: Ahapir, Nir, et al. Purification and Characterization of TrzF: Biuret Hydrolysis by Allophanate Hydrolase Supports Growth.<E T="03">Applied and Environmental Microbiology.</E>72(4):2941-2495 (2006). (Document ID number EPA-HQ-OPPT-2005-0033-0363).</FP>
          <FP SOURCE="FP-2">20. CPC. Letter from Jerry A. Cook to Document Control Office, OPPT, EPA, concerning existing data on boiling point and vapor pressure. July 10, 2006. (Document ID number EPA-HQ-OPPT-2005-0033-0182).</FP>
          <FP SOURCE="FP-2">21. CRC Handbook of Chemistry and Physics. 85th Edition. David R. Lide, ed., CRC Press. Boca Raton, FL. 2004.</FP>
          <FP SOURCE="FP-2">22. EPA. Letter from Greg Schweer, CITB, CCD, OPPT, to Jerry A. Cook, CPC, concerning acceptance of existing data on boiling point, vapor pressure, and melting point. August 30, 2006. (Document ID number EPA-HQ-OPPT-2005-0033-0211).</FP>
          <FP SOURCE="FP-2">23. CPC. Email from Jerry Cook to Catherine Roman, CITB, CCD, OPPT, EPA, concerning determination of melting point. July 24, 2006. (Document ID number EPA-HQ-OPPT-2005-0033-0348).</FP>
          <FP SOURCE="FP-2">24. CPC. Studies submitted for 9,10-anthracenedione on octanol/water partition coefficient, water solubility, and a screen for reproduction/developmental toxicity. Submitted on February 15, 2007. (Document ID numbers EPA-HQ-OPPT-2005-0033-0222.1, EPA-HQ-OPPT-2005-0033-0222.1, and EPA-HQ-OPPT-2005-0033-0222.2, respectively).</FP>
          <FP SOURCE="FP-2">25. EPA. Letter from Mike Mattheisen, CITB, CCD, OPPT, to John Van Miller, Toxicology/Regulatory Services, Charlottesville, VA. February 21, 2008. (Document ID number EPA-HQ-OPPT-2005-0033-0291).</FP>

          <FP SOURCE="FP-2">26. Lonza, Inc. Studies submitted for 1-chlorododecane on boiling point, vapor pressure, octanol/water partition coefficient, water solubility, biodegradation,<E T="03">Daphnia</E>chronic toxicity, toxicity to algae, acute mammalian toxicity, mutagenicity, chromosomal damage, and 28-day repeated-dose toxicity with a reproduction/developmental toxicity screen. Submitted on September 17, 2008. (Document ID numbers EPA-HQ-OPPT-2005-0033-0314.6, EPA-HQ-OPPT-2005-0033-314.10, EPA-HQ-OPPT-2005-0033-0314.8, EPA-HQ-OPPT-2005-0033-0314.11, EPA-HQ-OPPT-2005-0033-0314.9, EPA-HQ-OPPT-2005-0033-0314.7, EPA-HQ-OPPT-2005-0033-0314.5, EPA-HQ-OPPT-2005-0033-0314.1, EPA-HQ-OPPT-2005-0033-0314.2, EPA-HQ-OPPT-2005-0033-0314.3, and EPA-HQ-OPPT-2005-0033-0314.4, respectively).</FP>
          <FP SOURCE="FP-2">27. Albemarle Corporation. Letter from Ronald Zumstein to Document Control Office, OPPT, EPA, concerning existing data on water solubility and octanol-water partition coefficient. May 12, 2006. (Document ID number EPA-HQ-OPPT-2005-0033-0163).</FP>
          <FP SOURCE="FP-2">28. Albemarle Corporation. Letter from Kim Boudreaux to Document Control Office, OPPT, EPA, concerning existing data on acute toxicity, gene mutation, and reproductive/developmental toxicity. July 14, 2006. (Document ID numbers EPA-HQ-OPPT-2005-0033-0181, EPA-HQ-OPPT-2005-0033-0181.1, EPA-HQ-OPPT-2005-0033-0181.2, and EPA-HQ-OPPT-2005-0033-0181.3).</FP>
          <FP SOURCE="FP-2">29. Albemarle Corporation. Letter from Kim Boudreaux to Document Control Office, OPPT, EPA, concerning an existing Ames study. May 1, 2007. (Document ID numbers EPA-HQ-OPPT-2005-0033-0250, EPA-HQ-OPPT-2005-0033-0250.1, and EPA-HQ-OPPT-2005-0033-0250.2).</FP>
          <FP SOURCE="FP-2">30. Albemarle Corporation. Letter from Kim Boudreaux to Document Control Office, OPPT, EPA, concerning existing data on repeated-dose toxicity and reproduction/developmental toxicity screening. May 16, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0247).</FP>
          <FP SOURCE="FP-2">31. EPA. Letter from Greg Schweer, CITB, CCD, OPPT, to Ronald Zumstein and Kim Boudreaux, Albemarle Corporation, concerning EPA's acceptance of existing data on water solubility and octanol-water partition coefficient. August 9, 2006. (Document ID number EPA-HQ-OPPT-2005-0033-0210).</FP>
          <FP SOURCE="FP-2">32. EPA. Letter from Greg Schweer, CITB, CCD, OPPT, to Kim Boudreaux, Albemarle Corporation, concerning EPA's acceptance of existing data on mammalian acute toxicity. April 5, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0237).</FP>
          <FP SOURCE="FP-2">33. EPA. Letter from Greg Schweer, CITB, CCD, OPPT, to Kim Boudreaux, Albemarle Corporation, concerning EPA's acceptance of existing data on bacterial reverse mutation and reproductive/developmental toxicity. October 23, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0285).</FP>
          <FP SOURCE="FP-2">34. Albemarle Corporation. Studies submitted for phenol, 4,4'-methylenebis[2,6-bis(1,1-dimethylethyl)]- on melting point, boiling point, vapor pressure, inherent biodegradation, and chromosomal aberration. Submitted on October 31, 2007 and November 1, 2007. (Document ID numbers EPA-HQ-OPPT-2005-0033-0274, EPA-HQ-OPPT-2005-0033-0274, EPA-HQ-OPPT-2005-0033-0274, EPA-HQ-OPPT-2005-0033-0275.1, and EPA-HQ-OPPT-2005-0033-0257, respectively).</FP>
          <FP SOURCE="FP-2">35. SFS Consortium, SOCMA. Letter to Document Control Office, OPPT, EPA, submitting a test plan and request for review of existing data on biodegradation and aquatic toxicity. May 14, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0238).</FP>
          <FP SOURCE="FP-2">36. EPA. Memorandum from Robert Boethling, EAB, EETD, OPPT, to Greg Schweer, CITB, CCD, OPPT, concerning biodegradation test requirement. July 6, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0277).</FP>
          <FP SOURCE="FP-2">37. EPA. Memorandum from Jed Costanza, EAB, EETD, OPPT, to Mike Mattheisen,CITB, CCD, OPPT. October 9, 2008. (Document ID number EPA-HQ-OPPT-2005-0033-0352).</FP>
          <FP SOURCE="FP-2">38. EPA. Email from David Brooks, HPVCB, RAD, OPPT, to Catherine Roman, CITB, CCD, OPPT. Review of CAS No. 149-44-0. August 13, 2009. (Document ID number EPA-HQ-OPPT-2005-0033-0349).</FP>

          <FP SOURCE="FP-2">39. EPA. Memorandum from Daniel Lin, ICB, EETD, OPPT, to Greg Schweer, CITB, CCD, OPPT, concerning vapor pressure requirement. June 19, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0278).<PRTPAGE P="15616"/>
          </FP>
          <FP SOURCE="FP-2">40. EPA. Letter from Charles Auer, OPPT, to Tucker Helmes, SOCMA. May 28, 2008. (Document ID number EPA-HQ-OPPT-2005-0033-0307).</FP>
          <FP SOURCE="FP-2">41. EPA. Memorandum from Greg Fritz, ICB, EETD, OPPT, to Mike Mattheisen, CITB, CCD, OPPT. August 25, 2008. (Document ID number EPA-HQ-OPPT-2005-0033-0351).</FP>
          <FP SOURCE="FP-2">42. SOCMA. Studies submitted for methanesulfinic acid, hydroxyl-, monosodium salt on melting point, water solubility, chromosomal damage, and 28-day repeated-dose toxicity with a reproduction/developmental toxicity screen. Submitted on June 16, 2008. (Document ID number EPA-HQ-OPPT-2005-0033-0309).</FP>
          <FP SOURCE="FP-2">43. CPMA. Letter to Document Control Office, OPPT, EPA, from J. Lawrence Robinson concerning existing data and test plan. July 17, 2006. (Document ID number EPA-HQ-OPPT-2005-0033-0185).</FP>
          <FP SOURCE="FP-2">44. CPMA. Letter to Document Control Office, OPPT, EPA, from J. Lawrence Robinson concerning existing data and test plan. May 9, 2007. (Document ID EPA-HQ-OPPT-2005-0033-0246).</FP>
          <FP SOURCE="FP-2">45. EPA. Memorandum from Diana Darling, ICB, EETD, OPPT, to Greg Schweer, CITB, CCD, OPPT. Testing requirements and existing data for physical/chemical properties of the HPV test rule chemical, C.I. Pigment Blue 61 (CAS No. 1324-76-1). May 17, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0280).</FP>
          <FP SOURCE="FP-2">46. EPA. Memorandum from Robert Boethling, EAB, EETD, OPPT, to Greg Schweer, CITB, CCD, OPPT. Review of SAR argument and a biodegradation test concerning an HPV test rule chemical, C.I. Pigment Blue 61 (CAS No. 1324-76-1). May 15, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0279).</FP>
          <FP SOURCE="FP-2">47. EPA. Email and attached review from David Brooks, HPVCB, RAD, OPPT, to Greg Schweer and Catherine Roman, CITB, CCD, OPPT. Review of C.I. Pigment Blue (CAS No. 1324-76-1). August 22, 2007. (Document ID number EPA-HQ-OPPT-2005-0033-0286).</FP>

          <FP SOURCE="FP-2">48. SOCMA. Robust summaries submitted for C.I. Pigment Blue 61 on octanol/water partition coefficient, acute toxicity to<E T="03">Daphnia,</E>toxicity to algae, and combined 28-day repeated-dose toxicity with a reproduction/developmental toxicity screen. Submitted on November 14, 2008. (Document ID number EPA-HQ-OPPT-2005-0033-0318).</FP>
          <FP SOURCE="FP-2">49. SOCMA. Letters from C. Tucker Helmes to Document Control Office, OPPT, EPA. Submission of existing data on C.I. Solvent Black 7. June 29, 2006 and August 4, 2006. (Document ID numbers EPA-HQ-OPPT-2005-0033-0168, EPA-HQ-OPPT-2005-0033-0169, EPA-HQ-OPPT-2005-0033-0170, EPA-HQ-OPPT-2005-0033-0171, EPA-HQ-OPPT-2005-0033-0172, EPA-HQ-OPPT-2005-0033-0173, EPA-HQ-OPPT-2005-0033-0174, EPA-HQ-OPPT-2005-0033-0175, EPA-HQ-OPPT-2005-0033-0176, and EPA-HQ-OPPT-2005-0033-0184).</FP>
          <FP SOURCE="FP-2">50. EPA. Memorandum from Mark Townsend, HPVCB, RAD, OPPT, to Greg Schweer, CITB, CCD, OPPT. November 27, 2006. (Document ID number EPA-HQ-OPPT-2005-0033-0283).</FP>

          <FP SOURCE="FP-2">51. SOCMA. Letter from C. Tucker Helmes to Document Control Office, OPPT, EPA. Justification for providing<E T="03">Daphnia</E>reproduction study for C.I. Solvent Black 7. February 28, 2008. (Document ID number EPA-HQ-OPPT-2005-0033-0290).</FP>
          <FP SOURCE="FP-2">52. EPA. Email from David Brooks, HPVCB, RAD, OPPT, to Mike Mattheisen, CITB, CCD, OPPT. July 15, 2008. (Document ID number EPA-HQ-OPPT-2005-0033-0353).</FP>
          <FP SOURCE="FP-2">53. SOCMA. Studies submitted for C.I. Solvent Black 7 on physical/chemical properties and prenatal developmental toxicity. Submitted on February 28, 2008. (Document ID numbers EPA-HQ-OPPT-2005-0290.2 and EPA-HQ-OPPT-2005-0033-0290.4).</FP>
          <FP SOURCE="FP-2">54. EPA, EPAB, EETD, OPPT. Economic Analysis for the Final Section 4 Test Rule for High Production Volume Chemicals. October 28, 2005. (Document ID number EPA-HQ-OPPT-2005-0033-0131).</FP>
          <FP SOURCE="FP-2">55. EPA. Email from Stephanie Suazo, EPAB, EETD, OPPT, to Catherine Roman, CITB, CCD, OPPT. RE: “Revised Economic Analysis for Revocation of Testing Requirements” with attached economic analysis. December 14, 2009. (Document ID number EPA-HQ-OPPT-2005-0033-0350).</FP>
        </EXTRACT>
        <HD SOURCE="HD1">VIII. Statutory and Executive Order Reviews</HD>

        <P>This direct final rule only eliminates existing requirements; it does not otherwise impose any new or revised requirements. As such, this action is not subject to review by the Office of Management and Budget (OMB) as a “significant regulatory action” under Executive Order 12866, entitled “Regulatory Planning and Review” (58 FR 51735, October 4, 1993). Nor does it impose or change any information collection burden that requires additional review by OMB under the provisions of the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501<E T="03">et seq.</E>).</P>

        <P>Because this direct final rule eliminates existing requirements without imposing any new or revised requirements, the Agency certifies pursuant to section 605(b) of the Regulatory Flexibility Act (RFA) (5 U.S.C. 601<E T="03">et seq.</E>), that this action will not have a significant economic impact on a substantial number of small entities.</P>
        <P>For the same reasons, it is not subject to the requirements of sections 202 and 205 of the Unfunded Mandates Reform Act (UMRA) (2 U.S.C. 1531-1538), and does not significantly or uniquely affect small governments or impose a significant intergovernmental mandate, as described in sections 203 and 204 of UMRA. This direct final rule does not have tribal implications, as specified in Executive Order 13175, entitled “Consultation and Coordination with Indian Tribal Governments” (65 FR 67249, November 9, 2000), or federalism implications as specified in Executive Order 13132, entitled “Federalism” (64 FR 43255, August 10, 1999).</P>
        <P>Since this action is not economically significant under Executive Order 12866, it is not subject to Executive Order 13045, entitled “Protection of Children from Environmental Health Risks and Safety Risks” (62 FR 19885, April 23, 1997), and 13211, “Actions concerning Regulations that Significantly Affect Energy Supply, Distribution, or Use” (66 FR 28355, May 22, 2001).</P>
        <P>This action does not involve technical standards; thus, the requirements of section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) do not apply.</P>
        <P>This direct final rule does not involve special consideration of environmental justice related issues as specified in Executive Order 12898, entitled “Federal Actions to Address Environmental Justice in Minority Populations and Low-Income Populations” (59 FR 7629, February 16, 1994).</P>
        <HD SOURCE="HD1">IX. Congressional Review Act</HD>
        <P>The Congressional Review Act, 5 U.S.C. 801<E T="03">et seq.,</E>generally provides that before a rule may take effect, the agency promulgating the rule must submit a rule report to each House of the Congress and the Comptroller General of the United States. EPA will submit a report containing this rule and other required information to the U.S. Senate, the U.S. House of Representatives, and the Comptroller General of the United States prior to publication of 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 in 40 CFR Part 799</HD>
          <P>Environmental protection, Chemicals, Hazardous substances, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: March 9, 2012.</DATED>
          <NAME>James Jones,</NAME>
          <TITLE>Acting Assistant Administrator, Office of Chemical Safety and Pollution Prevention.</TITLE>
        </SIG>
        <P>Therefore, 40 CFR chapter I is amended as follows:</P>
        <REGTEXT PART="799" TITLE="40">
          <PART>
            <PRTPAGE P="15617"/>
            <HD SOURCE="HED">PART 799—[AMENDED]</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 799 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>15 U.S.C. 2603, 2611, 2625.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="799" TITLE="40">
          <AMDPAR>2. In § 799.5085, revise the section heading and Table 2 of paragraph (j) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 799.5085</SECTNO>
            <SUBJECT>Chemical testing requirements for first group of high production volume chemicals (HPV1).</SUBJECT>
            <STARS/>
            <P>(j) * * *</P>
            <GPOTABLE CDEF="xs60,r50,12,xs100" COLS="4" OPTS="L2,i1">
              <TTITLE>Table 2—Chemical Substances and Testing Requirements</TTITLE>
              <BOXHD>
                <CHED H="1">CAS No.</CHED>
                <CHED H="1">Chemical name</CHED>
                <CHED H="1">Class</CHED>
                <CHED H="1">Required tests<LI>(see table 3 of this section)</LI>
                </CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">74-95-3</ENT>
                <ENT>Methane, dibromo-</ENT>
                <ENT>1</ENT>
                <ENT>A, C1, E2, F2.</ENT>
              </ROW>
              <ROW>
                <ENT I="01">78-11-5</ENT>
                <ENT>1,3-Propanediol, 2,2-bis[(nitrooxy)methyl]-, dinitrate (ester)</ENT>
                <ENT>1</ENT>
                <ENT>A4, A5, B, C6, F2.</ENT>
              </ROW>
              <ROW>
                <ENT I="01">84-65-1</ENT>
                <ENT>9,10-Anthracenedione</ENT>
                <ENT>1</ENT>
                <ENT>A4, A5, F2.</ENT>
              </ROW>
              <ROW>
                <ENT I="01">110-44-1</ENT>
                <ENT>2,4-Hexadienoic acid, (<E T="03">E,E</E>)-</ENT>
                <ENT>1</ENT>
                <ENT>A, C4.</ENT>
              </ROW>
              <ROW>
                <ENT I="01">112-52-7</ENT>
                <ENT>1-Chlorododecane</ENT>
                <ENT>1</ENT>
                <ENT>A2, A3, A4, A5, B, C3, D, E1, E2, F1.</ENT>
              </ROW>
              <ROW>
                <ENT I="01">118-82-1</ENT>
                <ENT>Phenol, 4,4'-methylenebis[2,6bis(1,1-dimethylethyl)]-</ENT>
                <ENT>1</ENT>
                <ENT>A1, A2, A3, B, E2.</ENT>
              </ROW>
              <ROW>
                <ENT I="01">149-44-0</ENT>
                <ENT>Methanesulfinic acid, hydroxy-, monosodium salt</ENT>
                <ENT>1</ENT>
                <ENT>A1, A5, E2, F1.</ENT>
              </ROW>
              <ROW>
                <ENT I="01">409-02-9</ENT>
                <ENT>Heptenone, methyl-</ENT>
                <ENT>2</ENT>
                <ENT>A, B, C1, D, E1, E2, F1.</ENT>
              </ROW>
              <ROW>
                <ENT I="01">594-42-3</ENT>
                <ENT>Methanesulfenyl chloride, trichloro-</ENT>
                <ENT>1</ENT>
                <ENT>A, B, C1, E1, E2, F2.</ENT>
              </ROW>
              <ROW>
                <ENT I="01">1324-76-1</ENT>
                <ENT>Benzenesulfonic acid, [[4-[[4-(phenylamino)phenyl][4-(phenylimino)-2,5-cyclohexadien-1-ylidene]methyl]phenyl]amino]-</ENT>
                <ENT>2</ENT>
                <ENT>A4, C2, F1.</ENT>
              </ROW>
              <ROW>
                <ENT I="01">2941-64-2</ENT>
                <ENT>Carbonochloridothioic acid,<E T="03">S</E>-ethyl ester</ENT>
                <ENT>1</ENT>
                <ENT>A, B, C1, E2, F1.</ENT>
              </ROW>
              <ROW>
                <ENT I="01">8005-02-5</ENT>
                <ENT>C.I. Solvent Black 7</ENT>
                <ENT>2</ENT>
                <ENT>A, F2.</ENT>
              </ROW>
            </GPOTABLE>
            <STARS/>
          </SECTION>
        </REGTEXT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6430 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
        <SUBAGY>Fish and Wildlife Service</SUBAGY>
        <CFR>50 CFR Part 17</CFR>
        <DEPDOC>[Docket No. FWS-R4-ES-2010-0079; FXES11130900000C3-123-FF09E30000]</DEPDOC>
        <RIN>RIN 1018-AX27</RIN>
        <SUBJECT>Endangered and Threatened Wildlife and Plants; Establishing a Manatee Refuge in Kings Bay, Citrus County, FL</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Fish and Wildlife Service, Interior.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>We, the U.S. Fish and Wildlife Service, establish a manatee refuge in Citrus County, Florida, in the waters of Kings Bay, including its tributaries and connected waters. This action is based on our determination that there is substantial evidence showing that certain waterborne activities would result in the taking of one or more manatees and that certain waterborne activities must be restricted to prevent the taking of one or more manatees in Kings Bay. In making this rule final, we considered the biological needs of the manatee, the level of take at these sites, and the likelihood of additional take of manatees due to human activity at these sites.</P>
          <P>This final rule is modified from the proposed rule to ensure that the provisions do not compromise human safety and to clarify certain aspects. The modifications are not considered significant as they are within the scope of the proposed rule. To avoid creation of a hazard to human safety, watercraft may be operated at 25 miles per hour during daylight hours in a portion of the manatee refuge from June 1 through August 15. The portion of the rule prohibiting use of mooring and floatlines that can entangle manatees has been removed. Language regarding prohibitions on waterborne activities in Three Sisters Spring has been revised to improve clarity. We also announce the availability of a final environmental assessment and Finding of No Significant Impact for this action.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective March 16, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>This final rule, and supporting documentation, including public comments, are available on the Internet at<E T="03">http://www.regulations.gov</E>at Docket No. FWS-R4-ES-2010-0079. Comments and materials received, as well as supporting documentation used in preparing this final rule, are also available for public inspection, by appointment, during normal business hours at the U.S. Fish and Wildlife Service, North Florida Ecological Services Office, 7915 Baymeadows Way, Suite 200, Jacksonville, Florida, 32256.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Field Supervisor, U.S. Fish and Wildlife Service, North Florida Ecological Services Office, 7915 Baymeadows Way, Suite 200, Jacksonville, Florida, 32256; by telephone (904/731-3336); by facsimile (904/731-3045); by email:<E T="03">manatee@fws.gov;</E>or on-line at<E T="03">http://www.fws.gov/northflorida.</E>Persons who use a telecommunications device for the deaf (TDD) may call the Federal Information Relay Service (FIRS) at 800-877-8339.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Background</HD>
        <HD SOURCE="HD2">Previous Federal Actions</HD>
        <P>The West Indian manatee<E T="03">(Trichechus manatus)</E>was listed as an endangered species on June 2, 1970 (35 FR 8491), under the Endangered Species Conservation Act of 1969 and this status was retained under the Endangered Species Act of 1973, as amended (ESA) (16 U.S.C. 1531<E T="03">et seq.</E>), and the population is further protected as a depleted stock under the Marine Mammal Protection Act of 1972, as amended (MMPA) (16 U.S.C. 1361<E T="03">et seq.</E>). On October 22, 1979, the U.S. Fish and Wildlife Service (Service) adopted a regulatory process to provide a means for establishing manatee protection areas in waters under the jurisdiction of the United States where manatees were taken by waterborne activities (44 FR 60964). The first manatee protection areas were designated in Kings Bay on November 12, 1980, for the purpose of preventing the take of manatees by harassment from waterborne activities and included the Banana Island Sanctuary (including King Spring), the Sunset Shores Sanctuary, and the Magnolia Springs Sanctuary (45 FR 74880). The Service subsequently designated four additional manatee protection areas in Kings Bay on May 12, 1994, and on October 16, 1998, (including the Buzzard Island Sanctuary, Tarpon Springs Sanctuary, Warden Key Sanctuary, and Three<PRTPAGE P="15618"/>Sisters Springs Sanctuary, respectively) (59 FR 24654 and 63 FR 55553). To prevent the imminent take of manatees by waterborne activities, we published an emergency rule that temporarily established the Kings Bay manatee refuge in Citrus County, Florida, on November 9, 2010 (75 FR 68719). On June 22, 2011, the Service proposed to establish the manatee refuge throughout Kings Bay, while maintaining the seven existing Manatee Sanctuaries in the Bay (76 FR 36493).</P>

        <P>The West Indian manatee includes two subspecies: the Florida manatee (<E T="03">Trichechus manatus latirostris</E>) and the Antillean manatee (<E T="03">Trichechus manatus manatus</E>). Florida manatees can be found throughout the southeastern United States, with Florida at the core of its range. Extensive efforts are ongoing by the Service and the Florida Fish and Wildlife Conservation Commission (Commission or FWC) to recover this species. In particular, significant efforts are made to minimize human-related threats and to reduce the number of manatees taken by human activities.</P>
        <P>Take, as defined by section 3(19) of the ESA, means to harass, harm, pursue, hunt, shoot, wound, kill, trap, capture, collect, or to attempt to engage in any such conduct. Harm is further defined by regulation at 50 CFR 17.3 to mean an act which actually kills or injures wildlife. Harass is also defined by regulation to mean any intentional or negligent act or omission which creates the likelihood of injury to wildlife by annoying it to such an extent as to significantly disrupt normal behavioral patterns, which include, but are not limited to, breeding, feeding, or sheltering (50 CFR 17.3). Take, as defined by section 3(13) of the MMPA, means to harass, hunt, capture, or kill, or attempt to harass, hunt, capture, or kill any marine mammal. Take is further defined in 50 CFR 18.3 to include, without limitation, any of the following: The collection of dead animals or parts thereof; the restraint or detention of a marine mammal, no matter how temporary; tagging a marine mammal; or the negligent or intentional operation of an aircraft or vessel, or the doing of any other negligent or intentional act which results in the disturbing or molesting of a marine mammal. Under section 3(18) of the MMPA, harassment is defined to include any act of pursuit, torment, or annoyance, which (i) has the potential to injure a marine mammal or marine mammal stock in the wild (Level A); or (ii) has the potential to disturb a marine mammal or marine mammal stock in the wild by causing disruption of behavioral patterns, including, but not limited to, migration, breathing, nursing, breeding, feeding, or sheltering (Level B). All takings, including takings by harassment, are prohibited.</P>

        <P>The primary human-related causes of death and injury to manatees rangewide include watercraft-related strikes (impacts and/or propeller strikes), entrapment and/or crushing in water control structures (gates, locks, etc.), and entanglement in fishing lines, crab pot lines, etc. A 2005 analysis concluded that watercraft-related mortality was the leading human-related cause of death for manatees throughout Florida (MPSWG 2005, p. 5). A subsequent threats analysis concluded that watercraft strikes and the potential loss of warm-water habitat pose the greatest threats to the Florida manatee population (Runge<E T="03">et al.</E>2007, p. 17).</P>
        <P>The Service may establish manatee protection areas (in the form of a manatee refuge or a manatee sanctuary) whenever there is substantial evidence showing that such establishment is necessary to prevent the taking of one or more manatees. Regulations authorizing designation of manatee refuges and sanctuaries in areas where restrictions or prohibitions on certain waterborne activities are needed to prevent the take of manatees are codified in 50 CFR 17 subpart J. A manatee refuge is defined as an area in which the Director has determined that: (1) Certain waterborne activities would take one or more manatees; or (2) certain waterborne activities must be restricted to prevent the take of one or more manatees, including but not limited to taking by harassment. A manatee sanctuary is an area where it has been determined that any waterborne activity would result in the taking of one or more manatees, including but not limited to a taking by harassment (50 CFR 17.102). Manatee refuges and manatee sanctuaries are established under a different authority from Federal National Wildlife Refuges.</P>
        <HD SOURCE="HD2">Kings Bay</HD>
        <P>The Florida manatee's range includes Kings Bay, Florida. Kings Bay is a large embayment located at the headwaters of the Crystal River, a tidal river located on Florida's west coast. Springs are the primary water source for this estuarine system; a recent report describes 70 springs that discharge warm, artesian water (that is, water rises under pressure from a permeable stratum overlaid by impermeable rock) into Kings Bay (Vanasse, Hangen, and Brustlin, Inc., 2010, p. 1). Kings Bay is partially located within the City of Crystal River's city limits, and wholly within Citrus County, Florida. Citrus County and the City of Crystal River are an integral part of “Florida's Nature Coast,” a northwestern Florida region marketed for outdoor recreational opportunities, including opportunities for viewing manatees (Nature Coast Coalition 2010 Web site). In addition to viewing manatees, area recreationists engage in snorkeling and diving, boating, canoeing and kayaking, fishing, waterskiing, and other activities (Gold 2008, pp. 4-5). Local eco-tour operators, dive shops, marinas, hotels and motels, restaurants, and other businesses benefit from these activities (Buckingham 1990, p. 6).</P>
        <P>The Kings Bay springs constitute one of the most important natural warm-water shelters for manatees. Manatees have historically been attracted to the warm, spring-fed waters in Kings Bay where they retreat from the cold during the winter. As manatee populations have increased, year-round use of Kings Bay by manatees has increased accordingly (Figures 1 and 2). Wintering manatees have been the focus of a manatee viewing industry for many years, and bay waters are widely used by commercial and recreational waterway users for a variety of activities throughout the year. Manatees are struck and killed or injured by watercraft operating in Kings Bay. Manatees are harassed by the viewing public. The number of manatees struck and killed by watercraft in Kings Bay is increasing, as are the number of public reports of acts of manatee harassment.</P>
        <BILCOD>BILLING CODE 4310-55-P</BILCOD>
        <GPH DEEP="640" SPAN="3">
          <PRTPAGE P="15619"/>
          <GID>ER16MR12.000</GID>
        </GPH>
        <BILCOD>BILLING CODE 4310-55-C</BILCOD>
        
        <PRTPAGE P="15620"/>
        <P>Watercraft associated with recreational and commercial activities strike and kill manatees. In the State's northwestern region, where Kings Bay is located, adult manatee mortality is almost equally split between human-related and natural causes, with watercraft collisions being the leading source of human-caused mortality. According to mortality statistics compiled by the FWC, 13 manatees killed as a result of collisions with watercraft have been recovered within the boundaries of the Kings Bay manatee refuge (as established by this rule) between April 1974 and November 2010; all of these occurred since 1999 (Table 1; FWC FWRI Manatee Mortality Database 2011 Web site).</P>
        <GPOTABLE CDEF="xs48,12,xls48,xls36,10,r25,r25" COLS="7" OPTS="L2,i1">
          <TTITLE>Table 1—All Carcasses Recovered in the “Kings Bay” Region From April 1974 Through November 2010 for Which the Cause of Death Was Specifically Determined To Be Watercraft. *The Entry for 06/11/2002 Is a Carcass That Was Recovered Outside of the Boundaries of the Kings Bay Manatee Refuge (as Established by This Rule), but Considered the “Kings Bay” Region by FWC</TTITLE>
          <TDESC>[Data source: FWC FWRI Manatee Mortality Database 2011 Web site]</TDESC>
          <BOXHD>
            <CHED H="1">FL county</CHED>
            <CHED H="1">Date</CHED>
            <CHED H="1">Field ID</CHED>
            <CHED H="1">Sex</CHED>
            <CHED H="1">Size<LI>(cm)</LI>
            </CHED>
            <CHED H="1">Region</CHED>
            <CHED H="1">Probable cause of death</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Citrus</ENT>
            <ENT>10/27/1999</ENT>
            <ENT>MNW9934</ENT>
            <ENT>F</ENT>
            <ENT>268</ENT>
            <ENT>Kings Bay</ENT>
            <ENT>Watercraft.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Citrus</ENT>
            <ENT>10/12/2000</ENT>
            <ENT>MNW0029</ENT>
            <ENT>F</ENT>
            <ENT>275</ENT>
            <ENT>Kings Bay</ENT>
            <ENT>Watercraft.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Citrus</ENT>
            <ENT>06/11/2002</ENT>
            <ENT>MNW0222</ENT>
            <ENT>M</ENT>
            <ENT>207</ENT>
            <ENT>Kings Bay*</ENT>
            <ENT>Watercraft.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Citrus</ENT>
            <ENT>07/17/2002</ENT>
            <ENT>MNW0229</ENT>
            <ENT>F</ENT>
            <ENT>310</ENT>
            <ENT>Kings Bay</ENT>
            <ENT>Watercraft.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Citrus</ENT>
            <ENT>02/01/2003</ENT>
            <ENT>MNW0305</ENT>
            <ENT>F</ENT>
            <ENT>257</ENT>
            <ENT>Kings Bay</ENT>
            <ENT>Watercraft.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Citrus</ENT>
            <ENT>06/01/2004</ENT>
            <ENT>MNW0417</ENT>
            <ENT>F</ENT>
            <ENT>204</ENT>
            <ENT>Kings Bay</ENT>
            <ENT>Watercraft.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Citrus</ENT>
            <ENT>05/19/2006</ENT>
            <ENT>LPZ102120</ENT>
            <ENT>F</ENT>
            <ENT>259</ENT>
            <ENT>Kings Bay</ENT>
            <ENT>Watercraft.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Citrus</ENT>
            <ENT>05/24/2007</ENT>
            <ENT>MNW0715</ENT>
            <ENT>F</ENT>
            <ENT>227</ENT>
            <ENT>Kings Bay</ENT>
            <ENT>Watercraft.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Citrus</ENT>
            <ENT>07/04/2007</ENT>
            <ENT>MNW0721</ENT>
            <ENT>F</ENT>
            <ENT>331</ENT>
            <ENT>Kings Bay</ENT>
            <ENT>Watercraft.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Citrus</ENT>
            <ENT>08/23/2007</ENT>
            <ENT>LPZ102383</ENT>
            <ENT>M</ENT>
            <ENT>262</ENT>
            <ENT>Kings Bay</ENT>
            <ENT>Watercraft.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Citrus</ENT>
            <ENT>03/25/2008</ENT>
            <ENT>MNW0813</ENT>
            <ENT>F</ENT>
            <ENT>219</ENT>
            <ENT>Kings Bay</ENT>
            <ENT>Watercraft.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Citrus</ENT>
            <ENT>07/13/2008</ENT>
            <ENT>MNW0814</ENT>
            <ENT>M</ENT>
            <ENT>228</ENT>
            <ENT>Kings Bay</ENT>
            <ENT>Watercraft.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Citrus</ENT>
            <ENT>12/05/2008</ENT>
            <ENT>LPZ102654</ENT>
            <ENT>F</ENT>
            <ENT>261</ENT>
            <ENT>Kings Bay</ENT>
            <ENT>Watercraft.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Citrus</ENT>
            <ENT>01/03/2010</ENT>
            <ENT>MNW1002</ENT>
            <ENT>M</ENT>
            <ENT>246</ENT>
            <ENT>Kings Bay</ENT>
            <ENT>Watercraft.</ENT>
          </ROW>
        </GPOTABLE>
        <P>Manatee viewing activities provide a significant source of revenue to the local economy (Buckingham 1990, p. 6). Local eco-tour businesses bring visitors out to Kings Bay where visitors view manatees while in the water, from boats, and from other vantage points. Some manatees initiate encounters with visitors, but most manatees avoid or ignore encounters with people, preferring to frequent manatee sanctuaries where all human activities are prohibited. Some manatees are harassed by visitors, despite the fact that all forms of harassment are prohibited by law.</P>
        <P>Hartman (1979, pp. 128-131) was the first to observe and describe how manatees respond to the presence of people in the water, observing that most manatees tended to avoid people, some ignored people, a few approached people and then left, and some approached and initiated interactions with people. These observations were made in Kings Bay's warm water springs and the author correlated a reduction in the number of manatees using the Main Spring with an increasing number of people (Hartman 1979, p. 131). Concern has been expressed about manatees displaced from warm water springs for prolonged periods of time; prolonged exposure to cold can be fatal to manatees, especially for smaller animals (O'Shea 1995, p. 304). Hartman (1979, p. 126) believed that manatees in Kings Bay are harassed by people in the water and by boats.</P>

        <P>Researchers have observed and documented manatee responses to people and boats (Sorice<E T="03">et al.</E>2003, p. 324). Researchers noted increases in swimming, milling, and cavorting behaviors and decreases in resting, feeding, and nursing behaviors in the presence of increasing numbers of people and boats (Abernathy 1995, pp. 23-26; Wooding 1997, p. 1; King and Heinen 2004, pp. 230-231). They also observed that increases in numbers of boats and people prompted manatees to use other areas (Kochman<E T="03">et al.</E>1985, pp. 922-924; Buckingham<E T="03">et al.</E>1999, p. 514). However, none of these studies' observations of manatee responses to viewing participants and boats suggest that harm (killing or injuring of manatees) has occurred or is occurring (Sorice<E T="03">et al.</E>2003, p. 320). Nor have there been any significant increases in the number of cold-related injuries and mortalities in the northwestern Florida region, even in the recent extreme cold events, which killed large numbers of manatees in other portions of the winter range. For example, in the 2009-2010 winter cold event, only two deaths due to cold stress were recorded in Citrus County while to the south in Lee County, 24 manatee deaths were reported due to cold stress (FWC FWRI Manatee Mortality Database 2011 Web site). Manatee survival rates in the northwestern region are among the highest in Florida (Runge<E T="03">et al.</E>2007, p. 20).</P>
        <P>Observations of manatee harassment in Kings Bay prompted the Service to promulgate a rule in 1979 that allowed the agency to designate manatee protection areas where certain waterborne activities, including boating and swimming, could be prohibited in order to “reduce the incidence of manatee injuries and deaths” and to “lessen the likelihood that manatees will encounter boats and people” (44 FR 60964; October 22, 1979). Subsequently, three manatee sanctuaries were designated in Kings Bay in 1980 (45 FR 74880; November 12, 1980) and, in 1983, the Service purchased lands in and around Kings Bay and established the Crystal River NWR for the purpose of protecting manatees and to educate the public about manatees.</P>

        <P>In 1994, citing a doubling of the number of manatees in the area since 1980, a large increase in the number of visitors, the inability of the existing sanctuaries to provide sufficient shelter for manatees, and reports of increasing manatee harassment, the Service designated three additional sanctuaries in Kings Bay to prevent the take of manatees by harassment (59 FR 24654; May 12, 1994). This expansion was<PRTPAGE P="15621"/>followed by the addition of another sanctuary in 1998, similarly justified by reports of increasing harassment and observations of increasing numbers of manatees, increasing numbers of recreational divers and snorkelers, and insufficient space for manatees to rest, free from harassment (63 FR 55553; October 16, 1998: See Table 2.).</P>
        <GPOTABLE CDEF="s50,12,xs100,12" COLS="4" OPTS="L2,i1">
          <TTITLE>Table 2—Information Justifying Previous Manatee Sanctuary Designations in Kings Bay, Florida</TTITLE>
          <BOXHD>
            <CHED H="1">Date of Kings Bay manatee sanctuary designations</CHED>
            <CHED H="1">Approximate number of manatees using Kings Bay</CHED>
            <CHED H="1">Estimated number of<LI>people viewing manatees</LI>
            </CHED>
            <CHED H="1">Number of sanctuary<LI>designations</LI>
              <LI>new (total)</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">November 12, 1980 (45 FR 74880)</ENT>
            <ENT>100</ENT>
            <ENT>30,000 to 40,000</ENT>
            <ENT>3(3)</ENT>
          </ROW>
          <ROW>
            <ENT I="01">May 12, 1994 (59 FR 24654)</ENT>
            <ENT>240</ENT>
            <ENT>60,000 to 80,000</ENT>
            <ENT>3(6)</ENT>
          </ROW>
          <ROW>
            <ENT I="01">October 16, 1998 (63 FR 55553)</ENT>
            <ENT>250</ENT>
            <ENT>100,000</ENT>
            <ENT>1(7)</ENT>
          </ROW>
        </GPOTABLE>
        <P>Over the last 30 years (1980-2010), the Service and the State of Florida have created a network of manatee protection areas within the Kings Bay area. This network was designed to prevent the take of manatees by waterborne activities, including but not limited to, boating and manatee viewing activities, and was established to allow manatees to continue to gain access to critical warm-water areas and important resting and foraging areas. During the manatee season (November 15 through March 31), the network includes seven Federal manatee sanctuaries (which are described in our regulations at 50 CFR 17.108(a)(1)-(a)(7)) and five State manatee protection zones (as described in Chapter 68C-22, “The Florida Manatee Sanctuary Act” (2010)).</P>
        <P>The seven Federal sanctuaries are located at heavily-used winter, warm-water sites (springs) and foraging areas and preclude all waterborne activities within their boundaries, preventing take from both boating and manatee viewing within these areas. The State protection zones include year-round idle and slow-speed zones that prevent the take of manatees from high-speed watercraft collisions. Given the State's statutory responsibilities for balancing the needs of manatees with the needs of the boating community, the State designated a 35-mile per-hour (mph) (daytime)/25 mph (nighttime) watersports area (watersports area) in Kings Bay between May 1 and August 31. This area encircles Buzzard Island in the center of the bay.</P>
        <P>This network of manatee protection areas is enforced by Service, State, and local law enforcement officers. Extensive outreach and education programs support the protection area network, encouraging the public who engage in waterborne activities, including boating, manatee viewing activities, and others, to avoid taking manatees.</P>
        <HD SOURCE="HD2">Summary of Comments and Recommendations</HD>
        <P>In the June 22, 2011, proposed rule (76 FR 36493), we requested comments concerning any aspect of the proposal and the accompanying draft Environmental Assessment (EA) that might contribute to development of the final decision on the proposed rule. A 60-day comment period was provided. We sent notifications and other informational materials about the proposal to Federal and State agencies, Congressional representatives, conservation groups, local governments, local commercial diving operations, and numerous private citizens who may be affected or had expressed an interest in receiving further information on the proposal. In accordance with our policy on peer review, published on July 1, 1994 (59 FR 34270), we also provided copies of the proposed rule to three appropriate independent peer reviewers.</P>
        <P>We published a legal notice in the Citrus County Chronicle newspaper on June 24, 2011, announcing the proposal and availability of the draft EA, inviting public comment on both, and announcing the schedule for the informal open house and formal public hearing. Informational flyers were also distributed by the Crystal River National Wildlife Refuge (NWR) staff and friends group to all waterfront properties adjoining Kings Bay, as well as other nearby residences, and copies were mailed to the NWR's Comprehensive Conservation Plan development stakeholder and interested party list.</P>
        <P>We held a public informational open house and formal public hearing at the College of Central Florida—Citrus Campus, CF Conference Center in Lecanto, Florida, on July 7, 2011. The public hearing was attended by 169 people, not including Service staff. Of the 49 hearing attendees who signed up to speak, 42 provided oral comments (including 15 local officials).</P>
        <P>During the comment period, we received 415 written comments and 42 oral comments. A number of reviewers attached supporting documents such as petitions with multiple signatures or member form letters. Overall, comments came from individuals, conservation organizations, property owners, dive shop owners, tour operators, business owners, local officials, and other stakeholders. The majority of the comments expressed support for or opposition to the proposed manatee refuge without any substantive data or information provided for Service consideration.</P>
        <P>Those expressing support generally either supported the rule as proposed, with some minor modifications and suggestions for improving education, or expressed concerns that it was not extensive enough. Those expressing opposition cited a broad range of concerns including riparian property rights, lack of alternatives considered, perception that the public was not involved earlier in the process, recreational user safety, and perceived economic effects. In some cases those in opposition generally supported most of the winter aspects of the rule but not the year-round watercraft restrictions. Analysis of all comments received is summarized in the main issues that are identified and discussed below.</P>
        <HD SOURCE="HD2">Peer Review</HD>

        <P>In accordance with our peer review policy published on July 1, 1994 (59 FR 34270), we solicited expert opinion from three knowledgeable individuals with expertise in various aspects of the rule. We received responses from two of the peer reviewers. The peer reviewers generally concurred with our proposal and its content. One provided an additional economic reference, which was incorporated into the EA. Another recommended protection of an additional spring (Hunter Spring) but did not provide accompanying justification. The Service does not have<PRTPAGE P="15622"/>sufficient information to justify its inclusion at this time.</P>
        <HD SOURCE="HD2">Public Comments</HD>
        <P>In responding to public comments, the Service has grouped similar comments into a single cohesive comment/response in order to provide greater clarity to the reader. We have not addressed or included comments that were unrelated to the rule, for example, comments about critical habitat designation. Finally, there were comments that were unrelated to the mechanics or effects of the rule such as perceptions, motives, etc. These comments are not addressed in the final rule but may be addressed in outreach materials accompanying the release of the final rule.</P>
        <P>(1)<E T="03">Comment:</E>With the increased number of manatees using Kings Bay, the death of one manatee should be acceptable.</P>
        <P>
          <E T="03">Our Response:</E>The available data show that, in several years, one or more manatees have been killed or harassed; the Service is establishing the manatee refuge in Kings Bay with the intent of reducing those impacts. All take (as defined by the ESA and the MMPA) of manatees, including take by harassment, is prohibited by Federal law.</P>
        <P>(2)<E T="03">Comment:</E>The Service did not fully engage the public in the Federal rulemaking process.</P>
        <P>
          <E T="03">Our Response:</E>In accordance with 50 CFR 17.100-108, we issued an emergency rule on November 9, 2010 (75 FR 68719) to establish Kings Bay as a manatee refuge to prevent the imminent take of manatees by waterborne activities. We held four informational meetings with the community to provide the public with information on the next steps in the regulatory process as well as for the exchange of useful information. These meetings were held on November 16, 18, and 20 and December 2, 2010, at the Plantation Inn and Golf Resort, Crystal River, FL, to initiate the process of formalizing the manatee emergency regulation. On June 22, 2011 (76 FR 36493), we proposed to establish Kings Bay as a manatee refuge as defined under 50 CFR 17 subpart J and announced a public hearing on this proposed rule. A 60-day public comment period was provided. On July 7, 2011, we held the public hearing at the College of Central Florida—Citrus Campus, CF Conference Center in Lecanto, Florida. As stated above, the public hearing was well attended, and overall we received 415 written comments and 42 oral comments from interested parties. We have worked closely with the public and the State of Florida and fully engaged the public in the rulemaking process in accordance with applicable laws and regulations. We have thoroughly evaluated and considered comments received and incorporated edits to the regulation where appropriate.</P>
        <P>(3)<E T="03">Comment:</E>The establishment of Kings Bay as a manatee refuge is an expansion of the Federal Crystal River National Wildlife Refuge.</P>
        <P>
          <E T="03">Our Response:</E>The manatee protection area (manatee refuge) established in Kings Bay through this final rule does not alter the boundary of the existing Crystal River National Wildlife Refuge, although it does overlap with part of this National Wildlife Refuge. It is an area established in accordance with 50 CFR 17.100-108, subpart J, the sole purpose of which is to prevent the take of one or more manatees from waterborne activities being conducted in the area. As previously defined, “manatee refuges” are established solely to prevent the take of one or more manatees. They are protection areas designated in the water and are not land acquisitions or land parcels. No ownership of the waterways or submerged lands is transferred as a result of establishing a manatee protection area (i.e., a manatee refuge or manatee sanctuary). National Wildlife Refuges, on the other hand, are part of the Federal National Wildlife Refuge System. These are Federal lands set aside to conserve America's fish, wildlife, and plants through the National Wildlife Refuge System Improvement Act of 1997. The manatee protection area (manatee refuge) established in Kings Bay through this final rule is also<E T="03">not</E>an expansion of an existing Federal Crystal River National Wildlife Refuge. The Crystal River National Wildlife Refuge Fish and Wildlife Service staff is only associated with this manatee refuge because they will be a part of the team that implements the management activities detailed in this rule, as they currently are for the seven existing Federal seasonal manatee sanctuaries in Kings Bay.</P>
        <P>(4)<E T="03">Comment:</E>The establishment of Kings Bay as a manatee refuge will stop all boating activity and recreation.</P>
        <P>
          <E T="03">Our Response:</E>Designating Kings Bay as a manatee refuge pursuant to 50 CFR 17.100-108, subpart J, will not stop all boating and recreational activity. It provides for specific prohibitions, including speed and anchoring restrictions, time and area prohibitions, and prohibited activities such as chasing manatees, to avoid and minimize the harassment of manatees. However, boating, fishing, kayaking, and other forms of recreation are still allowed within all or portions of the manatee refuge, except in manatee sanctuaries and temporary no entry areas while they are in effect, as defined in the rule portion of this regulation.</P>
        <P>(5)<E T="03">Comment:</E>The proposed designation of Kings Bay as a manatee refuge infringes on property rights of homeowners that own property on the banks of Kings Bay. The establishment of Kings Bay as a manatee refuge will require homeowners on Kings Bay to get a permit.</P>
        <P>
          <E T="03">Our Response:</E>Manatee protection areas (manatee sanctuaries) were established in Kings Bay in 1980, 1994, and 1998. With all of these rules, exceptions were allowed for homeowners that own property on the banks of Kings Bay adjoining manatee sanctuaries or no-entry areas to continue to use waterways to go from and to their property under idle speed. They have also continually been allowed to maintain their property. Homeowners that own property as described above under these prior rules were not required to get a permit. Under these past rules, they notified the Crystal River NWR office and received a no-cost sticker to identify their watercraft. Some of these homeowners on Kings Bay already have identification stickers. When effective, this final rule for Kings Bay allows similar exceptions to all riparian property homeowners (their guests, employees, and designees including contractors and lessees) whose property adjoins a manatee sanctuary or no-entry area so they can retain their watercraft access and conduct property maintenance. This final rule also employs a similar no-cost sticker and no-cost letter of authorization program that has been used in the area for many years. The letter of authorization for contractors and designees is a process to help and protect homeowners as well. These stickers and/or letters are not required for those riparian property homeowners (their guests, employees, and designees including contractors and lessees) with Kings Bay property that does not adjoin a manatee sanctuary or no-entry area.</P>
        <P>(6)<E T="03">Comment:</E>Several comments related to the human safety aspects of the proposal. Some commenters expressed concern that, by closing the summer watersports zone, recreational watercraft operators would be forced into the narrow channel of Crystal River proper. Others expressed concern that the current watersports zone is unsafe because of the high number of users and the speed at which watercraft are being operated. Some commenters suggested that a reduced watersports zone could<PRTPAGE P="15623"/>increase safety for manatees while not forcing too much recreational activity into the river.</P>
        <P>
          <E T="03">Our Response:</E>We have fully evaluated comments shared by the public in and around Kings Bay and other concerned stakeholders in relation to actions being considered for implementation that were identified in the Services' June 2011 proposed rule. These concerns led us to seek and review Florida Fish and Wildlife Conservation Commission boating accident records in Crystal River and Kings Bay. Review of that information revealed that, since 2000, eight boating accidents have been reported in Kings Bay. Those accidents resulted in four injuries. In Crystal River, 24 accidents have been reported since 1998. Those accidents resulted in 12 injuries and 1 fatality.</P>
        <P>As part of our evaluation of comments, the Service worked with the U.S. Coast Guard (USCG) to evaluate the human safety aspects of the proposed rule. In an October 7, 2011, memorandum, the USCG (and confirmed by FWC by letter of December 8, 2011) conveyed their concern that the proposed closure of the watersports zone is likely to result in the displacement of high-speed watercraft activity into the Gulf of Mexico and the connecting waters of Crystal River, with the latter being the more likely of the two options due to the 2-hour transit time from Kings Bay to the Gulf. Crystal River has a narrow high-speed channel. In working with the USCG, we concluded that an increase in traffic such as might occur with implementation of our proposed rule is likely to result in unsafe conditions for watercraft operators by increasing the density of boaters in a smaller area and, therefore, the danger of boating safety infractions and marine accidents including vessel collisions, potentially involving serious bodily injury. We worked with the USCG to ensure that the manatee protection area designated through this rule both prevents the take of one or more manatees and alleviates the human safety issues raised in public comments.</P>
        <P>The Service examined seasonal manatee use data (i.e., numbers of manatees seen and when they were seen) in the watersports zone on a monthly basis from May through August for a period of 13 years (1999-2011); 69 surveys in all (Crystal River NWR unpublished data). Manatee use was highest during May (23.7 manatees/survey), declined in June (16.8 manatees/survey), July (17.5 manatees/survey), and the first half of August (11.0 manatees/survey), and increased in the latter half of August (19.4 manatees/survey). Coincidentally, the period of least manatee use also matched the timeframe when the least experienced boaters would be most likely to be on the water, the public school summer vacation period.</P>
        <P>The Service also examined manatee area use data (i.e., numbers of manatees seen and their locations) in various portions of the watersports zone for this same time period. Manatees are found throughout Kings Bay; however, some portions of Kings Bay appear to have less frequent use than others, such as a portion of the bay north of Buzzard Island. Manatee use during the months of May through August, was greatest (approximately 60 percent of all observations) in the waters east, west, and south of Buzzard Island. The waters along the south, west, and north shorelines in that portion of Kings Bay north of Buzzard Island combined encompassed approximately 15 percent of all observations. The remainder of the waters north of Buzzard Island encompassed approximately 25 percent of the manatee observations (Crystal River NWR unpublished data).</P>

        <P>We, therefore, considered the best available information, including manatee area and seasonal use within the Bay, and concluded that we could still meet the regulatory requirements of 50 CFR 17.100-108, subpart J, while also considering the human safety aspects by modifying the proposed rule to continue to allow some level of high speed watercraft recreation in Kings Bay. The final rule reflects these modifications that are within the scope of the proposed rule. Further, as confirmed in a memorandum to the Service dated November 8, 2011, these modifications alleviate the USCG's concerns regarding the proposed rule. Specifically, watercraft will be able to operate at high speed, not to exceed 25 mph, in a portion of Kings Bay generally north of Buzzard Island from June 1 through August 15 during daylight hours (sunrise to sunset). Slow-speed operation is required from sunset to sunrise during this period and at all times from August 16 through May 31. Manatees in Kings Bay are known to approach anchored boats for various and sometimes unknown reasons (<E T="03">e.g.,</E>to rub on the anchor line, seek cover, etc.). Therefore, we added a protection measure in the high-speed area through a prohibition against anchoring a vessel in the area (except in emergency situations) while the zone is in effect, which will avoid creating an attractive nuisance. A secondary benefit of this manatee protection measure is that it enhances the value of the area for safe waterborne recreation by precluding anchorage of vessels in the high-speed area during the defined time period. Currently, this area is a location where recreational vessels are anchored for extended periods and this effectively limits high-speed recreation in the widest portion of the Bay, causing recreationists to use the more constricted portions of the watersports area.</P>
        <P>The modifications to the rule will allow continued use of a portion of Kings Bay for high-speed recreation and, therefore, is less likely to result in additional recreational pressure in Crystal River during this peak summer recreation period. The modifications also coincide with the period of least manatee use based on available occurrence data (Crystal River NWR 2011, unpublished data). The area north of Buzzard Island provides the most open space available for watercraft operation in Kings Bay and is of less value to manatees for feeding, breeding, and sheltering (Crystal River NWR unpublished data). The waters to the east, west, and south of Buzzard Island that will become a year-round slow-speed zone generally have a greater density of manatee occurrences during the summer months, are shallower, and likely contain more submerged aquatic vegetation than the waters to the north of the island.</P>
        <P>The<E T="03">“Speed and anchoring restrictions”</E>portion of the rule provides for slow speed shoreline buffers along the south, west, and north shorelines in the portion of Kings Bay north of Buzzard Island. This provision allows the Service to protect the areas most frequented by manatees and to allow a safe operating area for recreational vessels. Based on our estimates of the location of these buffers relative to manatee observational data, we believe the final rule provides significant improvements in manatee protection over current conditions. It provides the same level of manatee protection as the June 2011 proposed rule during 47 days of May and August when the bay is slow speed throughout. During June, July, and the first half of August (76 days total), boats will be required to travel at slow speed where manatees are most likely to occur east, west, and south of Buzzard Island (approximately 60 percent of the observed locations) and along shorelines north of Buzzard Island (approximately 15 percent of the observed locations; Crystal River NWR unpublished data). As a result of the changes to the rule, which prohibits mooring and anchoring in the area north of Buzzard Island from June 1 to August 15, we also believe there will be fewer<PRTPAGE P="15624"/>manatees (currently, this area supports approximately 5 percent of observed locations; Crystal River NWR unpublished data) in the area where boats have historically anchored and moored which will also increase manatee protection in the 25 mph area. In total, we estimate that the final rule will provide at least 84 percent of the slow-speed benefits of the proposed rule (100 percent for 47 days and 75 percent for 76 days) and could reduce the potential risk of manatee mortality and injury by this fraction as the result of legal vessel operation. We believe the final rule will prevent the take of one or more manatees and resolves the safety concerns expressed by the public and confirmed by the USCG and FWC. Therefore, the Service is exercising its discretionary authority under 50 CFR subpart J to establish this manatee protection area.</P>
        <P>(7)<E T="03">Comment:</E>One reviewer commented that slowing boat speeds will not protect manatees.</P>
        <P>
          <E T="03">Our Response:</E>Slowing vessels allows increased reaction time for both boaters and manatees to avoid each other. It also minimizes the amount of force involved should a collision occur. Blunt force trauma is a significant factor in the deaths of manatees and injuries in collisions with boats.</P>
        <P>(8)<E T="03">Comment:</E>The definition of slow speed in the rule should be modified to include the aspect of “no wake” and should be modified to define a certain miles per hour.</P>
        <P>
          <E T="03">Our Response:</E>The Service uses definitions of watercraft operation speeds that are consistent with those of the State of Florida. We do not have any information to indicate that addition of “no wake” and a set miles per hour limit would offer further protection than the current definition in use.</P>
        <P>(9)<E T="03">Comment:</E>We received comments that there is not enough information to support establishing a temporary no-entry area around House and Jurassic Springs as well as comments that requested greater protection for these springs in the form of sanctuaries.</P>
        <P>
          <E T="03">Our Response:</E>As many as 20 animals have been seen in each of these sites on particularly cold days (J. Kleen, Crystal River NWR, 2010, pers. com.). Based on the best available information, including manatee use data, we believe that having the ability to establish temporary no-entry areas in House and Jurassic Springs will prevent the take, including harassment, of one or more manatees. These temporary no-entry areas will not be established in these spring areas when manatees are not present. Establishment of temporary no-entry areas will be based on aerial survey observations of manatees using the existing sanctuary sites, current weather information, and other sources of credible, relevant information. Depending on the winter season, House and Jurassic Springs may not have to be temporarily closed to entry or may only need to be closed for a time less than the duration of the winter season. In relation to greater protection, manatee use at these Springs is also expected to increase with less disturbance and future growth of the manatee population. At this time, the evidence does not support a determination that establishment of permanent sanctuaries is necessary to prevent the taking of one or more manatees. We will work closely with the local, State, and Federal officials and the local community if rule changes are considered in the future.</P>
        <P>(10)<E T="03">Comment:</E>The Service should specify specific air and water temperatures and tidal conditions that are necessary before an early or late creation of any temporary no-entry area could occur.</P>
        <P>
          <E T="03">Our Response:</E>Creation of any temporary no-entry area will be made only after an evaluation of a number of factors. The designation of temporary no-entry areas in advance of or after the regular manatee winter season will be made based on presence of manatees as identified by aerial survey observations of manatees using the existing sanctuary sites, and current weather information including air and water temperature and forecast duration of the cold event. Tidal conditions are not a factor in considering these designations.</P>
        <P>(11)<E T="03">Comment:</E>Some reviewers commented that we are only establishing the Kings Bay manatee refuge because of the threat of court action against the Service from several environmental groups.</P>
        <P>
          <E T="03">Our Response:</E>In designating the Kings Bay manatee refuge, the Service is guided by the provisions of 50 CFR 17.100-108.</P>
        <P>(12)<E T="03">Comment:</E>Some reviewers commented that, with the manatee population increasing, there is no need for establishing a Federal manatee refuge in Kings Bay, Citrus County, Florida.</P>
        <P>
          <E T="03">Our Response:</E>Both the ESA and MMPA prohibit the take, including incidental take, of manatees without appropriate authorization, which, to be obtained, must meet certain findings made under these Acts. Preventing the take of manatees as a result of watercraft collisions is a top priority in manatee recovery and management programs because of the overall value of this area to recovery, and the risk of take from harassment and watercraft. This action is consistent with prior Service rulemaking. After evaluating the best available information, we have determined that designation of this area as a manatee refuge is warranted pursuant to 50 CFR 17.100-108.</P>
        <P>(13)<E T="03">Comment:</E>Kings Bay as a whole and the channel proper that feeds into Kings Bay should be established as a manatee sanctuary.</P>
        <P>
          <E T="03">Our Response:</E>At this time, there is not substantial evidence to support the establishment of a manatee sanctuary throughout Kings Bay or the Crystal River channel proper that feeds into Kings Bay. Establishment of such a designation would unnecessarily restrict recreational opportunities within the Bay.</P>
        <P>(14)<E T="03">Comment:</E>Several reviewers commented that harassment as defined by these more specific prohibited activities should be added to 50 CFR 17.102 and that these prohibited actions that clarify take of manatees should apply everywhere it occurs and should be clarified in the rule.</P>
        <P>
          <E T="03">Our Response:</E>With the publication of this final rule, 50 CFR part 17 will be amended as noted in the Regulation Promulgation section of this rule. The Director may establish manatee protection areas whenever there is substantial evidence showing such establishment is necessary to prevent the taking of one or more manatees. Defining “harassment” under 50 CFR 17.102 is outside the scope of this rule. We have substantial evidence that the prohibited behaviors specifically identified in this rule can and have resulted in take of manatees in Kings Bay. It is not clear that extending the prohibitions beyond Kings Bay is warranted at this time, and in any case, goes beyond the scope of the rule. We will work closely with the local, State, and Federal officials and the local community if rule changes outside of Kings Bay are considered in the future.</P>
        <P>(15)<E T="03">Comment:</E>Some reviewers expressed confusion about the proposed prohibition against using mooring or float lines that can entangle manatees. Comments were also received suggesting that this line prohibition should apply everywhere the manatee occurs.</P>
        <P>
          <E T="03">Our Response:</E>The intent of the prohibition against the “use of mooring and float lines that can entangle manatees” was to prevent one or more manatees from being injured or killed from entanglement in such lines that have been abandoned or are not regularly checked and could, therefore, become an entanglement hazard. We recognize, however, that our intent was not clearly articulated in the proposed<PRTPAGE P="15625"/>rule. Entanglements are a threat to manatees in Kings Bay. In our attempts to clarify this proposed prohibition, we have recognized that this threat and solutions toward this threat need additional consideration. Implementing this provision at this time is not practical for several reasons (<E T="03">e.g.,</E>uncertainty regarding identification and availability of appropriate materials, application for different uses, and enforceability). Our goal of the proposed prohibition was the removal of derelict line sources and to encourage all operators to regularly check lines that are secured in Kings Bay. Through improved outreach, we are going to encourage all operators to help us meet this goal. We intend to work with the community and researchers to assess and evaluate equipment (line, connections, traps) solutions that are feasible and evidence suggests will help reduce manatee entanglements. Until we can accomplish that, other measures, such as fishing line recycling programs and the State of Florida's derelict crab pot removal program, are already in existence within Kings Bay to provide means for reducing the number of lines discarded in this area. Therefore, we have modified the rule to remove this proposed prohibition.</P>
        <P>(16)<E T="03">Comment:</E>Comments expressed the opinion that the Service does not have the resources to enforce the prohibitions and restrictions within the Kings Bay manatee refuge. Similarly, we received comments suggesting that enforcement should be increased in Kings Bay before additional protections are implemented.</P>
        <P>
          <E T="03">Our Response:</E>Both State and Federal law enforcement agents are authorized to enforce these regulations, and enforcement is a valuable tool to reduce take from noncompliant activity. The watercraft speed restrictions address the potential for accidental take associated with currently legal activities. Increased enforcement of existing laws would not prevent these injuries and deaths.</P>
        <P>(17)<E T="03">Comment:</E>Numerous comments stated the need to improve education for all parties who participate in waterborne activities within Kings Bay.</P>
        <P>
          <E T="03">Our Response:</E>Education and public awareness are important elements in the ongoing efforts to protect and recover manatees. In addition, our analysis of the best available information indicates that establishment of manatee protection areas and their requisite enforcement are equally important components in the comprehensive approach toward manatee protection. We will continue to work with the local community to increase education and public awareness of these regulations and restrictions.</P>
        <P>(18)<E T="03">Comment:</E>Some reviewers commented that elimination of the summer watersports zone will adversely impact the economy by reducing property values, certain forms of recreation, and tourism. Others commented that the proposal will support economic growth through increased ecotourism in the summer. One commenter pointed out the savings in costs from rescuing and caring for injured manatees.</P>
        <P>
          <E T="03">Our Response:</E>The net economic effect of the rule, whether positive or negative, is expected to be minimal. There is little debate that manatees are an economic asset to the community, but the extent to which that value may increase in summer months is unknown. The changes in the slow-speed requirements for safety purposes will have the secondary effect of buffering potential adverse economic effects through lost use. The rule will reduce the duration when certain waterborne activities may take place by 38 percent, but will maintain the opportunity for such recreation during the peak summer use period. It will remove some areas where high-speed watercraft operation can take place but improve opportunities for such recreation in other areas. It will increase and enhance the opportunities for other forms of waterborne recreation such as kayaking or canoeing, swimming, diving, and wildlife observation immediately east, south, and west of Buzzard Island. We know that the most recent annual reimbursement by the State to rehabilitation facilities for the cost of rescue and care for injured or distressed manatees is $1.15 million. Any incremental reduction in manatee injuries will represent a cost savings.</P>
        <P>(19)<E T="03">Comment:</E>One reviewer commented that the manatee mortality statistics in the rule and Environmental Assessment are inaccurate.</P>
        <P>
          <E T="03">Our Response:</E>The statistics have been reviewed and have been revised in this final rule to be current and accurate at the time of publication.</P>
        <P>(20)<E T="03">Comment:</E>One reviewer commented that the refuge establishment will prevent dredging.</P>
        <P>
          <E T="03">Our Response:</E>Manatee-safe procedures are currently required for all dredging activities in Florida where manatees are found. The rule does not impose additional restrictions on dredging.</P>
        <P>(21)<E T="03">Comment:</E>Several comments stated that the rule should incorporate additional protected areas both within and beyond the refuge and noted that the Service is not closing access to the “keyhole” in Kings Spring, a marked corridor within the Banana Island Sanctuary that currently allows access to swimmers and divers while the sanctuary is in place.</P>
        <P>
          <E T="03">Our Response:</E>The Service does not believe that additional closures are warranted within the manatee refuge and closures outside of the manatee refuge are beyond the scope of this rule. The Service believes that the rule is sufficient to prevent the take of one or more manatees and is, therefore, compliant with our discretionary authority. We believe swimming and diving can be allowed in the “keyhole” without harassing manatees. However, should swimming, diving, or both in the keyhole prove to be a problem, the Service has authority to close public access without additional rulemaking, as this area is Federally-owned and administered by the Service.</P>
        <P>(22)<E T="03">Comment:</E>Several comments suggested additional rules for in-water behavior relative to specific approach distances, touching of manatees, gear requirements or prohibitions, and passive observation.</P>
        <P>
          <E T="03">Our Response:</E>In order for the Service to implement and enforce a restriction we must be able to demonstrate substantial evidence that the activity results in “take.” As such, the rule prohibits numerous types of contact with manatees that will result in take. However, we have no evidence that simply touching a manatee, or approaching a manatee within some specific proximity, or use of some specific types of gear near a manatee will necessarily result in take. The commenter also acknowledged that “* * * interactions between certain manatees that invite contact with people may not annoy, disturb, or harm [manatees].” Adding these prohibitions would thus exceed our authority under subpart J and MMPA. Conversely, all of the prohibitions in the rule can be shown to result in take and will collectively allow us to prevent illegal take, and violations can be successfully prosecuted.</P>
        <P>(23)<E T="03">Comment:</E>Some reviewers suggested that the Service delay implementation and create a stakeholder committee to develop a solution.</P>
        <P>
          <E T="03">Our Response:</E>Prior to development of this final rule, we held four public meetings and one public hearing. No specific alternative solutions were submitted during these public meetings, subsequent to these meetings, or during the public comment period, despite the request for such information. We coordinated with Law Enforcement, FWC, and the USCG. The Service<PRTPAGE P="15626"/>considered alternative configurations for the final rule in coordination with the USCG and incorporated the changes that maximize manatee protection while addressing human safety concerns that were brought to our attention during the proposed rule comment period. Finally, the Service, as part of our mission, supports fishing, boating, and other outdoor recreation. In the future, if there is a technological means or other alternative that will protect manatees to the extent provided in the rule and allow us to lift some or all of the prohibitions, we will modify the manatee refuge and/or its prohibitions.</P>
        <HD SOURCE="HD1">Summary of Changes and Clarifications</HD>

        <P>(1) The proposed prohibition on use of mooring and float lines at paragraph (c)(14)(ix)(M) was removed. Entanglements are a threat to manatees in Kings Bay. In our attempts to clarify this proposed prohibition, we have recognized that this threat and solutions toward this threat need additional consideration. Implementing this provision at this time is not practical for several reasons (<E T="03">e.g.,</E>uncertainty regarding identification and availability of appropriate materials, application for different uses, and enforceability). Our goal of the proposed prohibition was the removal of derelict line sources and to encourage all operators to regularly check lines that are secured in Kings Bay. Through improved outreach, we are going to encourage all operators to help us meet this goal. We intend to work with the community and researchers to assess and evaluate equipment (line, connections, traps) solutions that are feasible and evidence suggests will help reduce manatee entanglements. Until we can accomplish that, other measures, such as fishing line recycling programs and the State of Florida's derelict crab pot removal program, are already in existence within Kings Bay to provide means for reducing the number of lines discarded in this area. Therefore, we have modified the rule to remove this proposed prohibition.</P>
        <P>(2) The requirement at paragraph (c)(14)(ii)(A) in reference to Three Sisters Springs was changed from “no entry” to prohibiting all waterborne activities during nighttime hours. Additionally, the timeframe was revised from specific hours to “sunset to sunrise.” The reference to “waterborne activities” is necessary to ensure that we are within our authorities under subpart J. This minor revision in hours is necessary to accomplish the intent to restrict activities during darkness when manatees cannot be seen and avoided and human activities cannot be monitored by enforcement officials.</P>
        <P>(3) As described in comment 6 and its response (above), we received numerous comments concerned that implementing a portion of the June 2011 proposed rule would result in human safety issues. The Service worked with the USCG (later confirmed by FWC) to evaluate the human safety aspects of the proposed rule and concluded that the proposed closure of the watersports zone is likely to result in the displacement of high-speed watercraft activity into the Gulf of Mexico and the connecting waters of Crystal River, with the latter being the more likely of the two options due to the 2-hour transit time from Kings Bay to the Gulf. Crystal River has a narrow high-speed channel, and we concluded that an increase in traffic such as might occur with implementation of our proposed rule is likely to result in unsafe conditions for watercraft operators by increasing the danger of boating safety infractions and marine accidents including vessel collisions, potentially involving serious bodily injury.</P>

        <P>We, therefore, reconsidered the substantial evidence showing that such establishment is necessary to prevent the taking of one or more manatees, including manatee area and seasonal use within the Bay, and concluded that we could still meet the regulatory requirements of 50 CFR 17.100-108 while also considering human safety by modifying the proposed rule to continue to allow some level of high speed watercraft recreation in Kings Bay. The final rule reflects these modifications that are within the scope of the proposed rule. Specifically, watercraft will be able to operate at high speed, not to exceed 25 mph, in a portion of Kings Bay generally north of Buzzard Island from June 1 through August 15 during daylight hours (sunrise to sunset). Slow-speed operation is required from sunset to sunrise during this period and at all times from August 16 through May 31. Manatees in Kings Bay are known to approach anchored boats for various and sometimes unknown reasons (<E T="03">e.g.,</E>to rub on the anchor line, seek cover, etc.). Therefore, we added protection measures in the high speed area through a prohibition against anchoring a vessel in the area (except in emergency situations) while the zone is in effect, which will avoid creating an attractive nuisance. A secondary benefit of this manatee protection measure is that it enhances the value of the area for safe waterborne recreation by precluding anchorage of vessels in the high-speed area during the defined time period. Currently, this area is a location where recreational vessels are anchored for extended periods and this situation effectively limits high-speed recreation in the widest portion of the Bay, causing recreationists to use the more constricted portions of the watersports area.</P>
        <P>The modifications to the rule will allow continued use of a portion of Kings Bay for recreation and, therefore, are less likely to result in additional recreational pressure in Crystal River during this peak summer recreation period. The modifications also coincide with the period of least manatee use based on available occurrence data (Crystal River NWR 2011, unpublished data). The area north of Buzzard Island provides the most open space available for watercraft operation in Kings Bay and is of less value to manatees for feeding, breeding, and sheltering (Crystal River NWR unpublished data). The waters to the east, west, and south of Buzzard Island that will become a year-round slow-speed zone generally have a greater density of manatee occurrences during the summer months, are shallower, and likely contain more submerged aquatic vegetation than the waters to the north of the island. The final rule at paragraph (c)(14)(iii) contains these changes.</P>

        <P>The rule greatly increases manatee protection over current conditions. The rule reduces the period of high-speed watercraft operation from 123 to 76 days. During the 76-day period (June 1 through August 15), it reduces the speed limit from 35 mph to 25 mph during the day and requires slow-speed operation at night. Based on aerial survey data (Crystal River NWR unpublished reports), this rule does not allow watercraft to travel at high speed where they are most likely to encounter manatees (<E T="03">e.g.,</E>shallow, grassy areas). High-speed operation is confined to a timeframe and area when and where it is least likely to impact manatees. The rule allows high-speed watercraft operation during the peak human use period to prevent exacerbating human safety risks in Crystal River. It increases human safety associated with waterborne activities in portions of the manatee refuge immediately east, south, and west of Buzzard Island, which are the more confined and shallower areas of the State-designated watersports area (and where manatee use is most concentrated).</P>

        <P>As was the case with the proposed rule, this rule does not supersede any more restrictive Federal, State, or local regulations currently in place nor does it preclude more restrictive future actions by these entities.<PRTPAGE P="15627"/>
        </P>
        <P>(4) The information standard for designating manatee protection areas is substantial evidence. As stated in 50 CFR 17.103, “The Director may * * * establish manatee protection areas whenever there is substantial evidence showing such establishment is necessary to prevent the taking of one or more manatees.” This is also the legal standard for emergency designations under section 17.106. There is no indication in the subpart J regulations that information to be considered is limited to scientific or commercial (i.e., species trade) data. The substantial evidence standard means that the Service can appropriately consider any valid, reliable evidence as long as it is relevant to the question of whether the establishment is “necessary to prevent the taking of one or more manatees.”</P>
        <P>The Service made a minor technical error in our proposed rule. In our opening summary section, we correctly stated the substantial evidence standard and shared a summary of the substantial evidence we used on page 36494 in our proposed rule. But, in the Public Comments Solicited section of the proposed rule, we incorrectly cited the use of only the best scientific and commercial data. While we certainly use up-to-date scientific data in our evaluation as part of the evidence we consider (for example, we would not establish a manatee protection area where manatees are not documented), the standard by which we designate manatee protection areas is that we have substantial evidence that designation of the area is necessary to prevent the taking of one or more manatee(s). We wanted to clarify this technical error in this final rule.</P>
        <HD SOURCE="HD1">Kings Bay—Assessment of Current Conditions</HD>
        <P>Similar to previous circumstances that warranted increases in the level of protection for manatees in Kings Bay, the number of manatees using Kings Bay more than doubled since 1998 (from 250 animals to 516 animals in December 2010, with the highest count on record of 566 in January 2010; Kleen 2011, pers. com.); the number of residents, visitors, and boats increased; and the amount of space in the existing sanctuaries became insufficient to provide this number of manatees with shelter free from harassment. In addition, the number of manatees struck and killed by boats in Kings Bay has increased since 1999.</P>

        <P>The manatee population in northwestern Florida grew at a rate of 4.0 percent per year through 2000, based on an assessment of adult survival rates (Runge<E T="03">et al.</E>2004, p. 371). Consistent with this rate of increase, the number of manatees counted in the region has increased, as well. Aerial counts were first conducted during the winter of 1983-1984, when 142 manatees were sighted in Citrus County; 124 of these animals were sighted in Kings Bay and Crystal River. In January 2010, Crystal River NWR researchers counted 646 manatees in Citrus County's coastal waters, including 566 manatees in Kings Bay. This is the highest number of manatees ever counted in this region and in Kings Bay (Kleen 2010, pers. com.). Aerial observations of manatees in Kings Bay during especially cold periods include sightings of manatees within the sanctuary areas and in smaller springs. In recent years, dozens of manatees are seen sheltering just outside of the sanctuary boundaries because the sanctuaries are overcrowded. Some animals shelter in some of Kings Bay's smaller, unprotected springs, including House Spring, Jurassic Spring, and a spring just east of the mouth of Three Sisters Springs run referred to in this rule as Idiot's Delight Number 2. As many as 20 animals have been seen in each of these sites on particularly cold days (Kleen 2010, pers. com.).</P>
        <P>The number of Citrus County residents increased by 19.8 percent (an average annual growth rate of 2.5 percent per year), from 118,085 to 141,416, between 2000 and 2008 (U.S. Census Bureau 2010 Web site). Concurrent with this increase in number of residents, the number of boats registered in Citrus County increased by 36.2 percent at an average annual growth rate of 4.0 percent per year. In 2010, there were 16,901 boats registered in Citrus County, 3,975 more than the 12,926 vessels registered there in 2000 (FDHSMV 2011 Web site). While the number of visitor-owned watercraft that are used in Citrus County waterways including Kings Bay is unknown, this number is likely increasing based on county revenue trends that describe an increasing number of visitors to the area. Revenue trends associated with businesses that cater to visitors, including Citrus County lodging and food service revenues and tourist tax revenues, have increased by 178 percent and 214 percent, respectively, over the past 10 years, suggesting an increase in the number of visitors to the area (U.S. Census Bureau 2010 Web site). Tourism surveys suggest that about half of all visitors to the area come to Citrus County to enjoy water-based activities that include manatee viewing, snorkeling, and diving (Gold 2008, pp. 4-5).</P>
        <P>From 1974 through 2010, collisions with watercraft killed 60 manatees in Citrus County waterways, including 13 manatees recovered within the boundaries of the Kings Bay manatee refuge, as established by this rule (FWC-FWRI Manatee Mortality Database 2011 Web site). All 13 deaths occurred since 1999. In 2008, FWC recorded the highest number (eight) of manatees ever killed by watercraft in Citrus County and three of these carcasses were recovered in Kings Bay (FWC-FWRI Manatee Mortality Database Web site).</P>
        <P>While watercraft-related deaths occur throughout the year in Citrus County, 7 of the 13 watercraft-related deaths that were recovered in Kings Bay since 1999 took place during those times of the year when the watersports area was in effect (May 1 through August 31). In May 2004, observers witnessed a boat striking a manatee in the watersports area; a carcass was recovered nearby the following day (FWC-FWRI Manatee Mortality Database 2011 Web site). Researchers are currently working on determining manatee scar acquisition rates for the Crystal River/Kings Bay manatee population, but preliminary findings suggest that propeller wounds continue to be acquired during their residency in the area (R. Bonde, peer review 2011).</P>

        <P>Every year, manatees are entangled in fishing line, float lines, anchor and mooring lines, and other types of gear. In extreme cases, entangled manatees can die when entangling gear cuts into their hide, causing sepsis and the occasional loss of limbs. In cases when animals are superficially entangled, entangling gear is removed and the animals are released onsite. In more severe cases, manatees are transported to rehabilitation facilities where they are treated for injuries and infections associated with entanglements. There are 30 known cases of manatee entanglements from Citrus County, including 10 from Kings Bay. Fourteen of these cases include manatees entangled in crab pot float lines, including four from Kings Bay. The remaining cases from Kings Bay include four from fishing lines and two from anchor lines. County-wide records of entanglements include 24 rescues and four deaths. More than half of these are known to have occurred during the past 15 years (U.S. Fish and Wildlife Service Manatee Rescue Rehabilitation and Release Program entanglements unpubl. data). However, measures, such as fishing line recycling programs and the State of Florida's derelict crab pot removal program, are already in existence within Kings Bay to provide<PRTPAGE P="15628"/>means for reducing the number of lines discarded in this area.</P>
        <P>Manatee harassment, largely associated with wintertime manatee viewing activities, occurs in Kings Bay; a variety of methods are being used to help prevent and minimize harassment from occurring. The Service, State, nongovernment organizations, and private companies prepare and distribute outreach materials to manatee-viewing recreationists to familiarize them with best practices to follow when in the water with manatees. Best practices include the “Manatee Viewing Guidelines,” developed by the Service and partners. Outreach materials include, among other things, handouts, kiosks, signs, and videos. The Crystal River NWR developed “Manatee Manners,” a video that dive shops and kayak outfitters are required to show their customers before they enter Kings Bay. These businesses take visitors to see manatees in Kings Bay, including Crystal River NWR. Under the National Wildlife Refuge System Improvement Act (16 U.S.C. 668dd-668ee), commercial interests conducting business within the NWR are required to obtain special-use permits (SUPs), which are conditioned to ensure that the permittees and their designees do not take manatees. Crystal River NWR also maintains a visitor center where guests are provided with outreach materials. The Crystal River Refuge's “Manatee Watch” volunteer network places volunteers in kayaks near the sanctuaries to educate visitors and report infractions when they occur.</P>
        <P>Federal regulations include 50 CFR 17.100-108, which provide for enforcement of manatee protection measures, and State regulations include provisions of the State's Florida Manatee Sanctuary Act as codified in 68 C-22 of the Florida Administrative Code. State and Federal officers have been cross-deputized and can enforce both State and Federal regulations. The Service, State, and other law enforcement agencies actively enforce harassment regulations in Citrus County and in Kings Bay. Cited acts of harassment include trespass by manatee-viewing individuals into manatee sanctuaries where the Service has determined that any waterborne activity occurring within these areas would result in take of manatees, including but not limited to take by harassment. Indirectly, the presence of large numbers of people in the vicinity of manatees may cause some animals to abandon the area, another form of harassment. Outside of these areas, the public disturbs and occasionally harasses manatees while engaged in viewing and other waterborne activities. When observed, violators are warned or cited. State violations include boaters traveling at speeds in excess of those described by law within specific areas. Given variations in enforcement practices and recordkeeping systems, these records are not used to describe trends in harassment activity.</P>
        <HD SOURCE="HD1">Summary</HD>
        <P>Based on current and historical data that document increasing numbers of manatees, waterway users, watercraft-related manatee deaths and injuries, and reports of manatee harassment in Kings Bay, we conclude that the take of manatees is occurring and increasing in this area. Sources of information include the U.S. Geological Survey, the FWC, manatee experts, the public, and peer-reviewed literature. Future take would occur without additional protection measures and we do not anticipate any alternative protection measures being enacted by other agencies in sufficient time to reduce the likelihood of take. For these reasons and based on this substantial evidence, we believe the establishment of an additional manatee protection area is needed to prevent the take of manatees. The Kings Bay manatee refuge covers the same geographical area as that defined by the November 9, 2010, emergency rule (75 FR 68719).</P>
        <P>To prevent the take of manatees, the Service and the State of Florida have designated a network of manatee protection areas at sites throughout Florida where threats to manatees have been well-documented and where manatees are known to frequently occur. This network supports our goal of providing areas of protected habitat throughout peninsular Florida, adequate to satisfy the biological needs of the species. This network is enhanced by the establishment of an additional manatee protection area, i.e., a manatee refuge in Kings Bay, a waterbody located in Crystal River, Citrus County, Florida.</P>
        <HD SOURCE="HD3">Kings Bay Manatee Refuge</HD>
        <P>Under the manatee refuge designation, specified restrictions will improve the Service's ability to address takings associated with watercraft and manatee viewing activities. Restrictions on watercraft operation will reduce the number of watercraft-related manatee deaths and injuries occurring in Kings Bay. Harassment associated with manatee viewing can be controlled through the establishment of no-entry areas not to exceed specified distances around existing manatee sanctuaries, the designation of no-entry areas at other springs when needed, and the identification of manatee refuge-specific prohibitions.</P>
        <HD SOURCE="HD2">Location</HD>
        <P>The Service designates the waters of Kings Bay as a manatee refuge. These waters include that tract of submerged land that includes all waters of Kings Bay, including all tributaries and adjoining waterbodies, upstream of the confluence of Kings Bay and Crystal River, described by a line that bears North 53°00′00″ East (True) from the northeasternmost point of an island on the southwesterly shore of Crystal River (approximate latitude 28°53′32″ North, approximate longitude 82°36′23″ West) to the southwesternmost point of a peninsula of Magnolia Shores (approximate latitude 28°53′38″ North, approximate longitude 82°36′16″ West). See Map “Kings Bay Manatee Refuge”.</P>
        <P>The manatee refuge encompasses seven existing Federal manatee sanctuaries, described in 50 CFR 17.108: The Banana Island Sanctuary (including King Spring), the Sunset Shores Sanctuary, the Magnolia Springs Sanctuary (including Gator Hole), the Buzzard Island Sanctuary, the Tarpon Springs Sanctuary, the Warden Key Sanctuary, and the Three Sisters Springs Sanctuary. The existing sanctuaries are in effect from November 15 through March 31 (referred to as the “manatee season”). The manatee refuge measures would be in effect in Kings Bay as described below.</P>
        <HD SOURCE="HD2">Manatee Refuge Measures</HD>
        <P>The manatee refuge measures, described in more detail below, include:</P>
        <P>• Maintaining the seven existing manatee sanctuaries where all waterborne activities are prohibited November 15 through March 31;</P>
        <P>• Regulating watercraft speeds throughout the manatee refuge at all times;</P>
        <P>• Prohibiting anchorage (other than emergency anchorage) of watercraft in the high-speed (25 mph) area from June 1 through August 15;</P>
        <P>• 12 specifically prohibited activities throughout the manatee refuge at all times;</P>
        <P>• Temporary `no-entry' areas adjacent to existing sanctuaries and specified additional springs during the manatee season (November 15 through March 31);</P>
        <P>• Temporary `no-entry' areas prior to or after the manatee season during unusual cold events; and</P>

        <P>• Exceptions for adjoining property owners and their designees.<PRTPAGE P="15629"/>
        </P>
        <HD SOURCE="HD3">Existing Manatee Sanctuaries</HD>
        <P>All seven currently existing manatee sanctuaries in Kings Bay, where all waterborne activities are prohibited November 15 through March 31, will remain in effect.</P>
        <HD SOURCE="HD3">Watercraft Speeds and Anchorage</HD>
        <P>To prevent the take of one or more manatees killed and injured by high-speed watercraft, operating speeds in Kings Bay are regulated throughout the year. Watercraft operation is restricted to slow speed throughout the manatee refuge unless otherwise marked. In some portions of the manatee refuge, State or local regulations require watercraft to travel at idle speed. For example, during summer holiday weekends, local ordinances and USCG regulations can require watercraft to travel at restricted speeds throughout Kings Bay due to human safety concerns regarding the high volume of watercraft activity, regardless of posted zones allowing greater speed. This rule allows watercraft to travel at speeds up to 25 mph during daylight hours (slow speed at night) in a portion of the manatee refuge from June 1 through August 15. The intent of regulating watercraft speeds and slowing all watercraft down in areas most frequented by manatees is to prevent the take of one or more manatees in Kings Bay from compliant watercraft operation. Some manatees in Kings Bay are known to approach anchored boats and, therefore, anchoring boats in the high-speed (25 mph) area is prohibited from June 1 through August 15. By prohibiting anchorage of boats in the high-speed (25 mph) area during this time period, manatees will not be attracted into harm's way by seeking cover around the boats, being attracted to the discharge of bilge water, chewing on anchor lines, etc.</P>
        <HD SOURCE="HD3">Manatee Viewing and Other Waterborne Activities</HD>
        <P>To prevent the take of one or more manatees associated with manatee viewing and other waterborne activities, we specify prohibitions that would be in effect throughout the year. Pursuant to the ESA and MMPA, all takings, including takings by harassment, are prohibited throughout the year, wherever they may occur. In regard to these prohibited activities, we consider a resting manatee to be a mostly motionless manatee that rises to breathe from the water bottom, in the water column, or on the water's surface. While resting, a manatee may make minor changes in its posture and may slightly shift its position. Minor changes in posture occur when manatees breathe or roll. Resting manatees may also make slight movements with their flippers or tail to compensate for draft, etc. (Hartman 1979, pp. 82-84). To prevent the take of manatees by individuals engaged in waterborne activities while in the water, in boats, or on-shore within the Kings Bay Manatee Refuge, we specifically identify and prohibit the following activities:</P>
        <P>(i) Chasing or pursuing a manatee(s).</P>
        <P>(ii) Disturbing or touching a resting or feeding manatee(s).</P>
        <P>(iii) Diving from the surface onto a resting or feeding manatee(s).</P>
        <P>(iv) Cornering or surrounding or attempting to corner or surround a manatee(s).</P>
        <P>(v) Riding, holding, grabbing, or pinching or attempting to ride, hold, grab, or pinch a manatee(s).</P>
        <P>(vi) Poking, prodding, or stabbing or attempting to poke, prod, or stab a manatee(s) with anything, including your hands and feet.</P>
        <P>(vii) Standing on or attempting to stand on a manatee(s).</P>
        <P>(viii) Separating a mother and calf or attempting to separate a mother and calf.</P>
        <P>(ix) Separating a manatee(s) from a group or attempting to separate a manatee(s) from a group.</P>
        <P>(x) Giving a manatee(s) anything to eat or drink or attempting to give a manatee(s) anything to eat or drink.</P>
        <P>(xi) Actively initiating contact with a belted and/or tagged manatee(s) and associated gear, including any belts, harnesses, tracking devices, or antennae.</P>
        <P>(xii) Interfering with rescue and research activities.</P>
        <P>The following activities are prohibited within Three Sisters Springs from November 15 through March 31:</P>
        <P>a. All waterborne activities in Three Sisters Springs from sunset to sunrise.</P>
        <P>b. Scuba diving.</P>
        <P>c. Fishing, including but not limited to fishing by hook and line, by cast net, and by spear.</P>
        <HD SOURCE="HD3">Prohibited Anchoring in the High-Speed Area of Kings Bay</HD>
        <P>Some manatees in Kings Bay are known to approach anchored boats. To minimize the potential for attraction (manatees seeking cover, bilge water, etc.) into harm's way, anchorage (other than emergency anchorage) of watercraft is prohibited in the high speed (25 mph) area from June 1 through August 15.</P>
        <HD SOURCE="HD3">Temporary No-Entry Areas (November 15 Through March 31)</HD>
        <P>Because there is insufficient space in the existing sanctuaries for all manatees that use Kings Bay to shelter, rest, and feed, free from harassment, we will create temporary no-entry areas outside of and adjacent to the existing sanctuaries to ensure adequate room for manatees wanting to access these sites when space is needed during the manatee season (between November 15 and March 31). This rule allows for creation of no-entry areas around one or more of the existing sanctuaries, as appropriate. The creation and removal of the temporary no-entry areas will be based on manatee usage data (such as aerial survey or on-the-water observations), current weather, and other sources of substantial information. We will also create no-entry areas around House Spring, Jurassic Spring, and Idiot's Delight Number 2 Spring when these springs are occupied by manatees in need of shelter free from harassment. With this rule, we have the ability to create temporary no-entry areas around any or all sanctuaries and specified springs for the manatee season, but we do not envision this will be necessary in all years. Temporary no-entry areas will be created at the distances specified in this rule to accommodate manatee biological needs as they use Kings Bay during cold events. The temporary no-entry areas will be posted for as long as they are necessary within the manatee season.</P>
        <HD SOURCE="HD3">Temporary No-Entry Areas (April 1 Through November 14)</HD>
        <P>To prevent the take of manatees sheltering in Kings Bay from cold weather that occurs outside of the manatee season (November 15 through March 31), temporary no-entry areas under this rule can be put in effect during early onset and protracted cold weather events that occur outside of the manatee season. Manatees that appear in Kings Bay during cold fronts that pre-date the start of the manatee season are especially vulnerable to harassment because none of the sanctuaries and no-entry areas are in effect prior to November 15. Similarly, none of these measures are in effect after March 31, during those times when cold weather continues beyond this period of time. In April 2010, the Service asked the public to voluntarily stay out of existing manatee sanctuaries after the close of the manatee season due to protracted cold weather and the continued presence of manatees at these sites. While the public generally complied with the request, some people did not and manatees were harassed.</P>

        <P>By designating temporary no-entry areas prior to November 15 and after March 31 during cold fronts when manatees are present, manatee harassment that could occur during<PRTPAGE P="15630"/>these times can be prevented. Designations would remain in effect for the duration of a cold front and only when there is regular manatee use; manatee presence at warm-water sites during unseasonal cold events typically lasts for several days or less. Temporary designations would remain in effect for no longer than 14 consecutive days.</P>
        <HD SOURCE="HD3">Exceptions for Adjoining Property Owners and Their Designees</HD>
        <P>Public and private property owners who own property that adjoins designated no-entry areas, their guests, employees, and designees (including but not limited to contractors and lessees) will continue to be able to access their property by obtaining, at no charge, an exception from the Crystal River NWR that will allow them to operate watercraft within the adjoining no-entry area for purposes of access and property maintenance. The Crystal River NWR will continue to provide adjoining property owners and their designees with a no-cost sticker or letter of authorization that identifies their watercraft as authorized to access no-entry areas. Watercraft owned by excepted owners will be required to be marked by stickers and operate at idle speed while within a designated no-entry area. Designees with a letter of authorization would be required to have a copy of the letter in their possession and required to operate at idle speed while within a designated no-entry area.</P>
        <HD SOURCE="HD1">Required Determinations</HD>
        <HD SOURCE="HD2">Regulatory Planning and Review</HD>
        <P>In accordance with the criteria in Executive Order 12866, the Office of Management and Budget (OMB) has determined that this rule is not a significant regulatory action. OMB bases its determination on the following four criteria:</P>
        <P>a. Whether the rule will have an annual economic impact of $100 million or more on the economy or adversely affect an economic sector, productivity, jobs, the environment, or other units of government.</P>
        <P>b. Whether the rule will create inconsistencies with other Federal agencies' actions.</P>
        <P>c. Whether the rule will materially affect entitlements, grants, user fees, loan programs, or the rights and obligations of their recipients.</P>
        <P>d. Whether the rule raises novel legal or policy issues.</P>
        <HD SOURCE="HD2">Regulatory Flexibility Act</HD>

        <P>Under the Regulatory Flexibility Act (as amended by the Small Business Regulatory Enforcement Fairness Act (SBREFA) of 1996), whenever a Federal agency is required to publish a notice of rulemaking for any proposed or final rule, it must prepare and make available for public comment a regulatory flexibility analysis that describes the effect of the rule on small entities (i.e., small businesses, small organizations, and small government jurisdictions) (5 U.S.C. 601<E T="03">et seq.</E>). However, no regulatory flexibility analysis is required if the head of an agency certifies that the rule would not have a significant economic impact on a substantial number of small entities. Thus, for a regulatory flexibility analysis to be required, impacts must exceed a threshold for “significant impact” and a threshold for a “substantial number of small entities.” See 5 U.S.C. 605(b). SBREFA amended the Regulatory Flexibility Act to require Federal agencies to provide a statement of the factual basis for certifying that a rule would not have a significant economic impact on a substantial number of small entities. This section presents a screening level analysis of the potential effects of the designation of a manatee protection area on small entities. We certify that this rule would not have a significant economic impact on a substantial number of small entities as defined under the Regulatory Flexibility Act (5 U.S.C. 601<E T="03">et seq.</E>). An initial/final Regulatory Flexibility Analysis is not required. Accordingly, a Small Entity Compliance Guide is not required.</P>
        <P>In order to determine whether the rule would have a significant economic impact on a substantial number of small entities, we utilize available information on the industries most likely to be affected by the designation of the manatee refuge. Small entities likely affected by the rule include entities whose businesses support high-speed recreational boating activities and commercial fishing. However, no current information is available on the specific number of small entities that would potentially be affected. This rule reduces the area and duration of high-speed activities from a previously existing summertime water-sports area and would add travel time to boating recreationists and commercial activities having to travel through the additional slow-speed zones. Because the only restrictions on recreational activity result from a reduction in time and space of the water-sports area and added travel time and alternative sites are available for all waterborne activities, we believe that the economic impact on small entities resulting from changes in recreational use patterns will not be significant. The economic impacts on small businesses resulting from this rule are likely to be indirect effects related to reduced demand for goods and services if recreationists choose to reduce their level of participation in waterborne activities. Similarly, because the only restrictions on commercial activity result from the inconvenience of added travel time, we believe that any economic impact on small commercial fishing or charter boat entities would not be significant. Also, the indirect economic impact on small businesses that may result from reduced demand for goods and services from commercial entities is likely to be insignificant.</P>
        <HD SOURCE="HD2">Small Business Regulatory Enforcement Fairness Act</HD>
        <P>This rule is not a major rule under 5 U.S.C. 804(2). This rule:</P>
        <P>a. Is not expected to have an annual effect on the economy of $100 million or more. This rule may cause some inconvenience in the form of displacement and added travel time for recreationists and commercial fishing and charter boat businesses because of speed and access restrictions in this manatee refuge, but it should not translate into any significant business reductions for the many small businesses in Citrus County. Since the only restrictions on recreational activity would result from displacement and added travel time and alternative sites are available for all waterborne activities, we believe that the economic impact on small entities resulting from changes in recreational use patterns would not be significant. The economic impacts on small business resulting from this rule are likely to be indirect effects related to reduced demand for goods and services if recreationists choose to reduce their level of participation in waterborne activities. Similarly, because the only restrictions on commercial activity result from the inconvenience of added travel time, we believe that any economic impact on small commercial fishing or charter boat entities would not be significant. Also, the indirect economic impact on small businesses that may result from reduced demand for goods and services from commercial entities is likely to be insignificant.</P>

        <P>b. Would not cause a major increase in costs or prices for consumers, individual industries, Federal, State, or local government agencies, or geographic regions. It is unlikely that there are unforeseen changes in costs or prices for consumers stemming from this rule. The recreational charter boat and commercial fishing industries may be affected by lower speed limits for<PRTPAGE P="15631"/>some areas when traveling to and from fishing grounds. However, this impact is likely to be limited.</P>
        <P>c. Would 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. As stated above, this rule may generate some level of inconvenience to recreationists due to displacement and added travel time, but the resulting economic impacts are believed to be minor and would not interfere with the normal operation of businesses in the affected county. Added travel time to traverse some areas is not expected to be a major factor that would impact business activity.</P>
        <HD SOURCE="HD2">Unfunded Mandates Reform Act</HD>

        <P>In accordance with the Unfunded Mandates Reform Act (2 U.S.C. 1501<E T="03">et seq.</E>):</P>
        <P>a. This rule will not significantly or uniquely affect small governments. A Small Government Agency Plan is not required. The designation of manatee refuges imposes no substantial new obligations on State or local governments.</P>
        <P>b. This rule will not produce a Federal mandate of $100 million or greater in any year. As such, it is not a significant regulatory action under the Unfunded Mandates Reform Act.</P>
        <HD SOURCE="HD2">Takings</HD>
        <P>In accordance with Executive Order 12630, this rule does not have significant takings implications. A takings implication assessment is not required. The manatee protection area is located over Federal-, State-, or privately-owned submerged bottoms. Any property owners in the vicinity would retain navigational access and the ability to maintain their property.</P>
        <HD SOURCE="HD2">Federalism</HD>
        <P>In accordance with Executive Order 13132, the rule does not have significant Federalism effects. A Federalism assessment is not required. This rule will not have substantial direct effects on the State, on the relationship between the Federal Government and the State, or on the distribution of power and responsibilities among the various levels of government. We coordinated with the State of Florida to the extent possible on the development of this rule.</P>
        <HD SOURCE="HD2">Civil Justice Reform</HD>
        <P>In accordance with Executive Order 12988, the Office of the Solicitor has determined that this rule would 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">Paperwork Reduction Act</HD>

        <P>This regulation does not contain new collections of information that require approval by the Office of Management and Budget under 44 U.S.C. 3501<E T="03">et seq.</E>The regulation would not impose new recordkeeping or reporting requirements on State or local governments, individuals, businesses, or organizations. OMB has reviewed and approved the information collection requirements associated with special use permits and assigned OMB Control No. 1018-0102. We may not conduct or sponsor and you are not required to respond to a collection of information unless it displays a currently valid OMB control number.</P>
        <HD SOURCE="HD2">National Environmental Policy Act</HD>

        <P>We have analyzed this rule in accordance with the criteria of the National Environmental Policy Act (42 USC 4321<E T="03">et seq.</E>). This final rule does not constitute a major Federal action significantly affecting the quality of the human environment. An environmental assessment and Finding of No Significant Impact has been prepared and is available on-line at<E T="03">http://www.regulations.gov</E>(see<E T="02">ADDRESSES</E>), or upon request (see<E T="02">FOR FURTHER INFORMATION CONTACT</E>).</P>
        <HD SOURCE="HD2">Government-to-Government Relationship With Tribes</HD>
        <P>In accordance with the President's memorandum of April 29, 1994, “Government-to-Government Relations with Native American Tribal Governments” (59 FR 22951), Executive Order 13175 and the Department of the Interior's manual at 512 DM 2, we have evaluated possible effects on Federally-recognized Indian tribes and have determined that there are no effects.</P>
        <HD SOURCE="HD2">Energy Supply, Distribution, or Use</HD>
        <P>On May 18, 2001, the President issued Executive Order 13211 on regulations that significantly affect energy supply, distribution, and use. Executive Order 13211 requires agencies to prepare Statements of Energy Effects when undertaking certain actions. Because this rule is not a significant regulatory action under Executive Order 12866, and it would only require vessels to proceed at slow or idle speeds (with the exception of a posted high-speed area available June 1 through August 15) or avoid no-entry areas in 530 acres of waterways in Florida, it is not expected to significantly affect energy supplies, distribution, and use. Therefore, this action is not a significant energy action, and no Statement of Energy Effects is required.</P>
        <HD SOURCE="HD1">References Cited</HD>

        <P>For a list of the references cited in this rule, see Docket No. FWS-R4-ES-2010-0079, available at<E T="03">http://www.regulations.gov.</E>
        </P>
        <HD SOURCE="HD1">Author</HD>

        <P>The primary author of this document is the U.S. Fish and Wildlife Service, North Florida Ecological Services Office (see<E T="02">ADDRESSES</E>).</P>
        <HD SOURCE="HD1">Authority</HD>

        <P>The statutory authority to establish manatee protection areas is provided by the Endangered Species Act of 1973, as amended (16 U.S.C. 1531<E T="03">et seq.</E>), and the Marine Mammal Protection Act of 1972, as amended (16 U.S.C. 1361<E T="03">et seq.</E>).</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 50 CFR Part 17</HD>
          <P>Endangered and threatened species, Exports, Imports, Reporting and recordkeeping requirements, Transportation.</P>
        </LSTSUB>
        <HD SOURCE="HD1">Regulation Promulgation</HD>
        <P>Accordingly, we amend part 17, subchapter B of chapter I, title 50 of the Code of Federal Regulations, as follows:</P>
        <REGTEXT PART="17" TITLE="50">
          <PART>
            <HD SOURCE="HED">PART 17—[AMENDED]</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 17 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>16 U.S.C. 1361-1407; 16 U.S.C. 1531-1544; 16 U.S.C. 4201-4245; Pub. L. 99-625, 100 Stat. 3500; unless otherwise noted.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="17" TITLE="50">
          <AMDPAR>2. Amend § 17.104 by revising paragraph (b) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 17.104</SECTNO>
            <SUBJECT>Prohibitions.</SUBJECT>
            <STARS/>
            <P>(b)<E T="03">Manatee refuge.</E>It is unlawful for any person within a particular manatee refuge to engage in any waterborne activity which has been specifically prohibited within that refuge, or to engage in any waterborne activity in a manner contrary to that permitted by regulation within that area. Any take of manatees under the Acts (see § 18.3 of this chapter for a definition of “take” in regard to marine mammals), including take by harassment, is prohibited wherever it may occur.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="17" TITLE="50">
          <AMDPAR>3. Amend § 17.108 by:</AMDPAR>
          <AMDPAR>a. In paragraph (a)(3), removing the period at the end of the paragraph and adding in its place a comma and the words “to be known as the Magnolia Springs Manatee Sanctuary.”;</AMDPAR>

          <AMDPAR>b. In paragraph (a)(4), removing the period at the end of the paragraph and<PRTPAGE P="15632"/>adding in its place a comma and the words “to be known as the Buzzard Island Manatee Sanctuary.”;</AMDPAR>
          <AMDPAR>c. In paragraph (a)(5), removing the period at the end of the paragraph and adding in its place a comma and the words “to be known as the Tarpon Springs Manatee Sanctuary.”;</AMDPAR>
          <AMDPAR>d. In paragraph (a)(6), removing the period at the end of the paragraph and adding in its place a comma and the words “to be known as the Warden Key Manatee Sanctuary.”;</AMDPAR>
          <AMDPAR>e. Revising paragraph (b) to read as set forth below; and</AMDPAR>
          <AMDPAR>f. Adding paragraph (c)(14) to read as set forth below:</AMDPAR>
          <SECTION>
            <SECTNO>§ 17.108</SECTNO>
            <SUBJECT>List of designated manatee protection areas.</SUBJECT>
            <STARS/>
            <P>(b)<E T="03">Exceptions.</E>(1) Adjoining property owners, their guests, employees, and their designees (including but not limited to contractors and lessees) may engage in watercraft access and property maintenance activities through manatee sanctuaries (set forth in paragraphs (a)(1) through (a)(11) of this section) and designated “no-entry areas” in the Kings Bay Manatee Refuge (set forth in paragraph (c)(14) of this section). Use of sanctuary and no-entry area waters is restricted to authorized individuals accessing adjoining properties, storing watercraft, and maintaining property and waterways. Maintenance activities include those actions necessary to maintain property and waterways, subject to any Federal, State, and local government permitting requirements.</P>
            <P>(2) Authorized individuals must obtain a sticker or letter of authorization from the U.S. Fish and Wildlife Service identifying them as individuals authorized to enter no-entry areas that adjoin their property. Stickers must be placed in a conspicuous location to readily identify authorized watercraft. Individuals with a letter of authorization must have a valid letter in their possession when accessing no-entry areas.</P>
            <P>(3) Authorized individuals must conduct any authorized boating activity within these areas at idle or no-wake speeds.</P>
            <P>(c) * * *</P>
            <P>(14)<E T="03">The Kings Bay Manatee Refuge.</E>A tract of submerged land that includes all waters of Kings Bay, including all tributaries and adjoining waterbodies, upstream of the confluence of Kings Bay and Crystal River, described by a line that bears North 53°00′00″ East (True) from the northeasternmost point of an island on the southwesterly shore of Crystal River (approximate latitude 28°53′32″ North, approximate longitude 82°36′23″ West) to the southwesternmost point of a peninsula of Magnolia Shores (approximate latitude 28°53′38″ North, approximate longitude 82°36′16″ West).</P>
            <P>(i)<E T="03">Area covered.</E>The Kings Bay Manatee Refuge encompasses existing manatee protection areas as described in paragraphs (a)(1) through (a)(7) of this section, and areas outside these sections as depicted on the map in paragraph (c)(14)(ii) of this section.</P>
            <P>(ii)<E T="03">Particular areas.</E>The following springs fall within the boundaries of the Kings Bay Manatee Refuge. A map showing the entire refuge, including these springs, follows:</P>
            <BILCOD>BILLING CODE 4310-55-P</BILCOD>
            <GPH DEEP="550" SPAN="3">
              <PRTPAGE P="15633"/>
              <GID>ER16MR12.001</GID>
            </GPH>
            <BILCOD>BILLING CODE 4310-55-C</BILCOD>
            <P>(A)<E T="03">Three Sisters Springs.</E>A tract of submerged land, lying in Section 28, Township 18 South, Range 17 East, Tallahassee Meridian, Citrus County, Florida, more particularly described as follows: For a point of reference, commence at the northwest corner of said Section 28 in an east southeast direction to the canal that begins on the west side of Southeast Cutler Spur Boulevard and runs west-northwest to Kings Bay. The spring is north and east of the northern terminus of Southeast Paradise Avenue along the northern shore of said canal. Three Sisters Springs includes three main and numerous smaller spring vents and a spring run that connects the vents to said canal in Crystal River, Citrus County, Florida. This area is not the same as set forth in paragraph (a)(7) of this section. This area is behind the sanctuary (north from the mouth of the channel) as set forth in paragraph (a)(7) of this section.</P>
            <P>(<E T="03">1</E>) All waterborne activities in this specific area are prohibited from sunset to sunrise from November 15 through March 31 exclusive of the provisions of paragraph (c)(14)(v) of this section.</P>
            <P>(<E T="03">2</E>) Scuba diving and fishing (including but not limited to fishing by<PRTPAGE P="15634"/>hook and line, by cast net, and by spear) are also prohibited in this specific area from November 15 through March 31 exclusive of the provisions of paragraph (c)(14)(v) of this section.</P>
            <P>(<E T="03">3</E>) If the provisions of paragraph (c)(14)(vi) of this section are put in effect, all waterborne activities are prohibited in this specific area for the duration established under paragraph (c)(14)(vi) of this section.</P>
            <P>(B)<E T="03">House Spring.</E>A tract of submerged land, lying in Section 21, Township 18 South, Range 17 East, Tallahassee Meridian, Citrus County, Florida, more particularly described as follows: For a point of reference, commence at the southwest corner of said Section 21 in an east-northeast direction to the northeasternmost corner of Hunter Spring Run. The spring is immediately west of and adjacent to Northeast 2nd Court in Crystal River, Citrus County, Florida.</P>
            <P>(C)<E T="03">Jurassic Spring.</E>A tract of submerged land, lying in Section 21, Township 18 South, Range 17 East, Tallahassee Meridian, Citrus County, Florida, more particularly described as follows: For a point of reference, commence at the southwest corner of said Section 21 in an east northeast direction to the eastern shore of Hunter Spring Run. The spring is immediately west of the western terminus of Bayshore Drive in Crystal River, Citrus County, Florida.</P>
            <P>(D)<E T="03">Idiot's Delight Number 2 Spring.</E>A tract of submerged land, lying in Section 28, Township 18 South, Range 17 East, Tallahassee Meridian, Citrus County, Florida, more particularly described as follows: For a point of reference, commence at the northwest corner of said Section 28 in an east southeast direction to the canal that begins on the west side of Southeast Cutler Spur Boulevard and runs west-northwest to Kings Bay. The spring is north and east of the northern terminus of Southeast Paradise Avenue along the northern shore of said canal just east of the southern terminus of the Three Sisters Springs run in Crystal River, Citrus County, Florida.</P>
            <P>(iii)<E T="03">Speed and anchoring restrictions.</E>(A) Throughout the entire year, watercraft speeds are restricted to slow speed throughout the manatee refuge with the following exceptions:</P>
            <P>(<E T="03">1</E>)  A posted area generally north of Buzzard Island, exclusive of shoreline slow-speed buffer zones, where watercraft may travel at speeds up to 25 miles per hour during daylight hours (sunrise to sunset) from June 1 through August 15;</P>
            <P>(<E T="03">2</E>) Those areas where access is precluded (manatee sanctuaries, no-entry areas); or</P>
            <P>(<E T="03">3</E>) Areas where more restrictive speed restrictions are in effect.</P>
            <P>(B) From June 1 through August 15, anchorage (other than emergency anchorage) of watercraft is prohibited in the posted high speed (25 miles per hour) area around Buzzard Island referenced in paragraph (c)(14)(iii)(A) of this section.</P>
            <P>(iv)<E T="03">Time and area prohibitions.</E>When the provisions of paragraphs (c)(14)(v) or (vi) of this section are in effect (November 15 through March 31 and April 1 through November 14, respectively), all waterborne activities, including swimming, diving (including skin and scuba diving), snorkeling, water skiing, surfing, fishing (including with hook and line, by cast net, or spear), and the use of water vehicles (including but not limited to boats powered by engine, wind, or other means; ships powered by engine, wind, or other means; barges, surfboards, personal watercraft, water skis, and any other devices or mechanisms capable of locomotion on, across, or underneath the surface of the water) are prohibited in areas that are adjacent to and within specified distances from the existing manatee sanctuaries located in Kings Bay (defined in paragraphs (a)(1) through (a)(7) of this section) and the springs defined in paragraph (c)(14)(ii) of this section: Three Sisters Springs, House Spring, Jurassic Spring, and Idiot's Delight Number 2 Spring.</P>
            <P>(v)<E T="03">Expanded temporary no-entry area (November 15 through March 31).</E>When manatees exceed the capacity of an existing manatee sanctuary or shift usage around an existing manatee sanctuary or shift usage to Three Sisters Springs, House Spring, Jurassic Spring, and Idiot's Delight Number 2 Spring, due to water or weather or other conditions, we will designate “no-entry” areas from November 15 through March 31 as appropriate and necessary around any of these sites. The determination to designate and subsequently remove no-entry areas around existing manatee sanctuaries and Three Sisters Springs, House Spring, Jurassic Spring, and Idiot's Delight Number 2 Spring within the Kings Bay Manatee Refuge will be based on aerial survey observations of manatees using the existing sanctuary sites, current weather information, and other sources of credible, relevant information. We will designate no-entry areas within Kings Bay Manatee Refuge and outside of existing sanctuaries as follows:</P>
            <P>(A) For the sanctuaries set forth in paragraphs (a)(1) through (a)(6) of this section, to a distance not to exceed 100 feet from the existing sanctuary boundary.</P>
            <P>(B) For the Three Sisters Springs Sanctuary, to a distance not to exceed 400 feet from the existing boundary. We do not intend to completely mark off the manmade channel. Expansions could occur directly around the existing sanctuary and north into the area locally known as Three Sisters Springs.</P>
            <P>(C) For House Spring and Jurassic Spring, an area that does not exceed 100 feet from the associated spring vents.</P>
            <P>(D) For Idiot's Delight Number 2 Spring, an area that does not exceed 25 feet from the associated spring vent. Any temporary designation will be configured to avoid the manmade channel in the canal and will not block access into Three Sisters Springs.</P>
            <P>(vi)<E T="03">Temporary no-entry areas (April 1 through November 14).</E>Temporary no-entry area designations may be made in the existing manatee sanctuaries located in Kings Bay defined in paragraphs (a)(1) through (a)(7) and paragraphs (c)(14)(v)(A) through (D) of this section prior to November 15 and after March 31 during cold fronts when manatees are present. Designations will remain in effect for the duration of a cold front and only when there is regular manatee use; temporary no-entry area designations will remain in effect for no longer than 14 consecutive days.</P>
            <P>(vii)<E T="03">Posting of temporary no-entry areas designated in accordance with paragraph (c)(14)(v) or (vi) of this section.</E>Additional temporary protection areas will be posted to distances as described in paragraph (c)(14)(v) of this section and identified by the following devices: buoys, float lines, signs, advisories from onsite Service employees and their designees, or other methods.</P>
            <P>(viii)<E T="03">Notifications of temporary no-entry areas designated in accordance with paragraph (c)(14)(v) or (vi) of this section.</E>When we determine that the provisions of paragraph (c)(14)(v) or (vi) of this section are appropriate, the temporary protection areas will be designated and posted to distances as described in paragraph (c)(14)(v) of this section. No-entry area designations will occur immediately. We will advise the public of designations through public notice(s) announcing and describing the measures in a local newspaper and other media, including but not limited to, local television and radio broadcasts, Web sites and other news outlets, as soon as time permits. Onsite Service employees and their designees, when<PRTPAGE P="15635"/>present, may also inform waterway users of designations.</P>
            <P>(ix)<E T="03">Prohibited activities (year-round).</E>We specifically identify and prohibit the activities set forth in this paragraph to prevent the take of one or more manatees by individuals engaged in waterborne activities while in the water, in boats, or on-shore within the Kings Bay Manatee Refuge. In regard to these prohibited activities, we consider a resting manatee to be a mostly motionless manatee that rises to breathe from the water bottom, in the water column, or on the water's surface. While resting, a manatee may make minor changes in its posture and may slightly shift its position. Minor changes in posture occur when resting manatees breathe or roll. Resting manatees may also make slight movements with their flippers or tail to compensate for drift, etc. Prohibited activities include:</P>
            <P>(A) Chasing or pursuing manatee(s).</P>
            <P>(B) Disturbing or touching a resting or feeding manatee(s).</P>
            <P>(C) Diving from the surface on to a resting or feeding manatee(s).</P>
            <P>(D) Cornering or surrounding or attempting to corner or surround a manatee(s).</P>
            <P>(E) Riding, holding, grabbing, or pinching or attempting to ride, hold, grab, or pinch a manatee(s).</P>
            <P>(F) Poking, prodding, or stabbing or attempting to poke, prod, or stab a manatee(s) with anything, including your hands and feet.</P>
            <P>(G) Standing on or attempting to stand on manatee(s).</P>
            <P>(H) Separating a mother and calf or attempting to separate a mother and calf.</P>
            <P>(I) Separating manatee(s) from a group or attempting to separate manatee(s) from a group.</P>
            <P>(J) Giving manatee(s) anything to eat or drink or attempting to give manatee(s) anything to eat or drink.</P>
            <P>(K) Actively initiating contact with belted or tagged manatee(s) and associated gear, including any belts, harnesses, tracking devices, or antennae.</P>
            <P>(L) Interfering with rescue and research activities.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: March 1, 2012.</DATED>
          <NAME>Rachel Jacobson,</NAME>
          <TITLE>Acting Assistant Secretary for Fish and Wildlife and Parks.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6055 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4310-55-P</BILCOD>
    </RULE>
  </RULES>
  <VOL>77</VOL>
  <NO>52</NO>
  <DATE>Friday, March 16, 2012</DATE>
  <UNITNAME>Proposed Rules</UNITNAME>
  <PRORULES>
    <PRORULE>
      <PREAMB>
        <PRTPAGE P="15636"/>
        <AGENCY TYPE="F">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Federal Aviation Administration</SUBAGY>
        <CFR>14 CFR Part 39</CFR>
        <DEPDOC>[Docket No. FAA-2012-0266; Directorate Identifier 2011-NM-061-AD]</DEPDOC>
        <RIN>RIN 2120-AA64</RIN>
        <SUBJECT>Airworthiness Directives; Airbus Airplanes</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Aviation Administration (FAA), DOT.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of proposed rulemaking (NPRM).</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>We propose to adopt a new airworthiness directive (AD) for all Airbus Model A318, A319, and A320 series airplanes. This proposed AD was prompted by reports of unsuccessful slide deployments during scheduled deployment tests, and failed functional tests of the release travel of the slide release mechanism. This proposed AD would require inspecting the off-wing slide release cables on the left- and right-hand sides to determine whether a certain part number is installed, and replacement if necessary. We are proposing this AD to prevent non-availability of left- or right-hand off-wing exit slides that could impair emergency evacuation of the passengers and flightcrew, and could result in personal injuries.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>We must receive comments on this proposed AD by April 30, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may send comments by any of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal:</E>Go to<E T="03">http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Fax:</E>(202) 493-2251.</P>
          <P>•<E T="03">Mail:</E>U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE., Washington, DC 20590.</P>
          <P>•<E T="03">Hand Delivery:</E>U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-40, 1200 New Jersey Avenue SE., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.</P>

          <P>For service information identified in this proposed AD, contact Airbus, Airworthiness Office—EAS, 1 Rond Point Maurice Bellonte, 31707 Blagnac Cedex, France; telephone +33 5 61 93 36 96; fax +33 5 61 93 44 51; email:<E T="03">account.airworth-eas@airbus.com;</E>Internet<E T="03">http://www.airbus.com.</E>You may review copies of the referenced service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, Washington. For information on the availability of this material at the FAA, call 425-227-1221.</P>
        </ADD>
        <HD SOURCE="HD1">Examining the AD Docket</HD>
        <P>You may examine the AD docket on the Internet at<E T="03">http://www.regulations.gov;</E>or in person at the Docket Operations office between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this proposed AD, the regulatory evaluation, any comments received, and other information. The street address for the Docket Operations office (telephone (800) 647-5527) is in the<E T="02">ADDRESSES</E>section. Comments will be available in the AD docket shortly after receipt.</P>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Sanjay Ralhan, Aerospace Engineer, International Branch, ANM-116, Transport Airplane Directorate, FAA, 1601 Lind Avenue SW., Renton, Washington 98057-3356; telephone (425) 227-1405; fax (425) 227-1149.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Comments Invited</HD>

        <P>We invite you to send any written relevant data, views, or arguments about this proposed AD. Send your comments to an address listed under the<E T="02">ADDRESSES</E>section. Include “Docket No. FAA-2012-0266; Directorate Identifier 2011-NM-061-AD” at the beginning of your comments. We specifically invite comments on the overall regulatory, economic, environmental, and energy aspects of this proposed AD. We will consider all comments received by the closing date and may amend this proposed AD based on those comments.</P>
        <P>We will post all comments we receive, without change, to<E T="03">http://www.regulations.gov,</E>including any personal information you provide. We will also post a report summarizing each substantive verbal contact we receive about this proposed AD.</P>
        <HD SOURCE="HD1">Discussion</HD>
        <P>The European Aviation Safety Agency (EASA), which is the Technical Agent for the Member States of the European Community, has issued EASA Airworthiness Directive 2011-0015, dated January 31, 2011 (referred to after this as “the MCAI”), to correct an unsafe condition for the specified products. The MCAI states:</P>
        
        <EXTRACT>
          <P>Several operators reported unsuccessful slide deployments during scheduled deployment tests and/or failed functional tests of the release travel of the slide release mechanism.</P>
          <P>Investigations revealed deformation of the PTFE (Teflon) ball guide strip of the release cable, Part Number (P/N) L32A319-160-001. In such a situation the travel of the cable could be insufficient to open the valve when opening the exit, thereby reducing the gas flow from the reservoir to the off-wing slide in automatic or manual mode. As a result, the aspirator will not ingest sufficient ambient air for slide inflation.</P>
          <P>This condition, if not corrected, could lead to the non-availability of LH [left-hand] and/or RH [right-hand] off-wing exit slides for evacuation that would impair emergency evacuation of the aeroplane occupants, possibly resulting in personal injuries.</P>
          <P>For the reasons described above, this [EASA] AD requires the identification [inspection] and replacement of both Left hand (LH) and Right Hand (RH) off-wing slide release cables P/N L32A319-160-001 with P/N L32A320-180, which have precise stainless steel ball bearing stripes instead of stamped PTFE stripes.</P>
        </EXTRACT>
        
        <FP>You may obtain further information by examining the MCAI in the AD docket.</FP>
        <HD SOURCE="HD1">Relevant Service Information</HD>
        <P>Airbus has issued the service bulletins listed below. The actions described in this service information are intended to correct the unsafe condition identified in the MCAI.</P>
        <P>• Airbus Service Bulletin A320-28-1118, Revision 03, including Appendix 1, dated May 12, 2009.</P>
        <P>• Airbus Service Bulletin A320-28-1132, Revision 04, including Appendices 1 and 2, dated February 1, 2010.</P>
        <P>• Airbus Service Bulletin A320-28-1145, Revision 01, including Appendix 01, dated April 27, 2007.</P>

        <P>• Airbus Service Bulletin A320-28-1154, Revision 01, dated April 7, 2008.<PRTPAGE P="15637"/>
        </P>
        <P>• Airbus Service Bulletin A320-53-1227, Revision 01, dated May 31, 2010.</P>
        <HD SOURCE="HD1">FAA's Determination and Requirements of This Proposed AD</HD>
        <P>This product has been approved by the aviation authority of another country, and is approved for operation in the United States. Pursuant to our bilateral agreement with the State of Design Authority, we have been notified of the unsafe condition described in the MCAI and service information referenced above. We are proposing this AD because we evaluated all pertinent information and determined an unsafe condition exists and is likely to exist or develop on other products of the same type design.</P>
        <HD SOURCE="HD1">Differences Between This AD and the MCAI or Service Information</HD>
        <P>This AD differs from the MCAI and/or service information as follows: Although the MCAI states that no person may install an off-wing slide release cable having P/N L32A319-160-001 on any airplane after the modifications specified in paragraphs (g) or (h) of this AD have been done, or on airplanes that do not have P/N L32A319-160-001 installed as of the effective date of the MCAI, this AD requires that, as of the effective date of this AD, no person may install an off-wing slide release cable having P/N L32A319-160-001 on any airplane.</P>
        <HD SOURCE="HD1">Costs of Compliance</HD>
        <P>Based on the service information, we estimate that this proposed AD would affect about 694 products of U.S. registry. We also estimate that it would take about 39 work-hours per product to comply with the basic requirements of this proposed AD. The average labor rate is $85 per work-hour. Required parts would cost about $5,750 per product. Where the service information lists required parts costs that are covered under warranty, we have assumed that there will be no charge for these parts. As we do not control warranty coverage for affected parties, some parties may incur costs higher than estimated here. Based on these figures, we estimate the cost of the proposed AD on U.S. operators to be $6,291,110, or $9,065 per product.</P>
        <HD SOURCE="HD1">Authority for This Rulemaking</HD>
        <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. “Subtitle VII: Aviation Programs,” describes in more detail the scope of the Agency's authority.</P>
        <P>We are issuing this rulemaking under the authority described in “Subtitle VII, Part A, Subpart III, Section 44701: General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
        <HD SOURCE="HD1">Regulatory Findings</HD>
        <P>We determined that this AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
        <P>
          <E T="03">For the reasons discussed above, I certify that this AD:</E>
        </P>
        <P>1. Is not a “significant regulatory action” under Executive Order 12866;</P>
        <P>2. Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979);</P>
        <P>3. Will not affect intrastate aviation in Alaska; and</P>
        <P>4. Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
        <P>We prepared a regulatory evaluation of the estimated costs to comply with this AD and placed it in the AD docket.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
          <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
        </LSTSUB>
        <HD SOURCE="HD1">The Proposed Amendment</HD>
        <P>Accordingly, under the authority delegated to me by the Administrator, the FAA proposes to amend 14 CFR part 39 as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
          <P>1. The authority citation for part 39 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 106(g), 40113, 44701.</P>
          </AUTH>
          <SECTION>
            <SECTNO>§ 39.13</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
            <P>2. The FAA amends § 39.13 by adding the following new AD:</P>
            
            <EXTRACT>
              <FP SOURCE="FP-2">
                <E T="04">Airbus:</E>Docket No. FAA-2012-0266; Directorate Identifier 2011-NM-061-AD.</FP>
              <HD SOURCE="HD1">(a) Comments Due Date</HD>
              <P>We must receive comments by April 30, 2012.</P>
              <HD SOURCE="HD1">(b) Affected ADs</HD>
              <P>None.</P>
              <HD SOURCE="HD1">(c) Applicability</HD>
              <P>This AD applies to all Airbus Model A318-111, -112, -121, and -122 airplanes; Model A319-111, -112, -113, -114, -115, -131, -132, and -133 airplanes; and Model A320-111, -211, -212, -214, -231, -232, and -233 airplanes; certificated in any category; all serial numbers.</P>
              <HD SOURCE="HD1">(d) Subject</HD>
              <P>Air Transport Association (ATA) of America Code 28: Fuel tanks; 53: Fuselage.</P>
              <HD SOURCE="HD1">(e) Reason</HD>
              <P>This AD was prompted by reports of unsuccessful slide deployments during scheduled deployment tests, and failed functional tests of the release travel of the slide release mechanism. We are issuing this AD to prevent non-availability of left- or right-hand off-wing exit slides that could impair emergency evacuation of the passengers and flightcrew, and could result in personal injuries.</P>
              <HD SOURCE="HD1">(f) Compliance</HD>
              <P>You are responsible for having the actions required by this AD performed within the compliance times specified, unless the actions have already been done.</P>
              <HD SOURCE="HD1">(g) Inspection and Modification</HD>
              <P>Except as provided by paragraph (l) of this AD, within 36 months after the effective date of this AD, inspect the off-wing slide release cables on the left- and right-hand sides to determine whether part number (P/N) L32A319-160-001 is installed. A review of airplane maintenance records is acceptable in lieu of this inspection if the part number of the off-wing slide release cables can be conclusively determined from that review. If any off-wing slide release cable has P/N L32A319-160-001, before further flight, replace with a new off-wing slide release cable having P/N L32A320-180, in accordance with the Accomplishment Instructions of Airbus Service Bulletin A320-53-1227, Revision 01, dated May 31, 2010.</P>
              <HD SOURCE="HD1">(h) Optional Modification</HD>
              <P>Installation of a shorter off-wing slide release cable having P/N L32A319-160-002 with relocated inflation bottle during installation of the additional center tank, in accordance with the Accomplishment Instructions of the applicable service bulletin identified in paragraphs (h)(1) through (h)(4) of this AD, is acceptable for compliance with the requirements of paragraph (g) of this AD.</P>
              <P>(1) Airbus Service Bulletin A320-28-1118, Revision 03, including Appendix 1, dated May 12, 2009.</P>
              <P>(2) Airbus Service Bulletin A320-28-1132, Revision 04, including Appendices 1 and 2, dated February 1, 2010.</P>

              <P>(3) Airbus Service Bulletin A320-28-1145, Revision 01, including Appendix 01, dated April 27, 2007.<PRTPAGE P="15638"/>
              </P>
              <P>(4) Airbus Service Bulletin A320-28-1154, Revision 01, dated April 7, 2008.</P>
              <HD SOURCE="HD1">(i) Parts Installation</HD>
              <P>As of the effective date of this AD, no person may install an off-wing slide release cable having P/N L32A319-160-001 on any airplane.</P>
              <HD SOURCE="HD1">(j) Credit for Previous Actions</HD>
              <P>This paragraph provides credit for the actions required by paragraph (g) of this AD, if installation of off-wing slide release cables having P/N L32A320-180 was done before the effective date of this AD using the applicable service bulletin identified in paragraph (j)(1) through (j)(6) of this AD.</P>
              <P>(1) Airbus Service Bulletin A320-53-1227, dated March 24, 2010.</P>
              <P>(2) Airbus Service BulletinA320-28-1132, dated October 13, 2004.</P>
              <P>(3) Airbus Service Bulletin A320-28-1132, Revision 01, dated October 12, 2006.</P>
              <P>(4) Airbus Service Bulletin A320-28-1132, Revision 02, dated November 12, 2008.</P>
              <P>(5) Airbus Service Bulletin A320-28-1132, Revision 03, dated October 5, 2009.</P>
              <P>(6) Airbus Service Bulletin A320-28-1145, dated February 28, 2006.</P>
              <HD SOURCE="HD1">(k) Exception</HD>
              <P>Provided that off-wing slide release cables have not been replaced with a slide release cable having P/N L32A319-160-001, airplanes having Airbus modification 150811, 26138, 37856, or 39673 installed in production are acceptable for compliance with the requirements of paragraph (g) of this AD.</P>
              <HD SOURCE="HD1">(l) Other FAA AD Provisions</HD>
              <P>The following provisions also apply to this AD:</P>
              <P>(1)<E T="03">Alternative Methods of Compliance (AMOCs):</E>The Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the International Branch, send it to ATTN: Sanjay Ralhan, Aerospace Engineer, International Branch, ANM-116, Transport Airplane Directorate, FAA, 1601 Lind Avenue SW., Renton, Washington 98057-3356; telephone (425) 227-1405; fax (425) 227-1149. Information may be emailed to:<E T="03">9-ANM-116-AMOC-REQUESTS@faa.gov.</E>Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office. The AMOC approval letter must specifically reference this AD.</P>
              <P>(2)<E T="03">Airworthy Product:</E>For any requirement in this AD to obtain corrective actions from a manufacturer or other source, use these actions if they are FAA-approved. Corrective actions are considered FAA-approved if they are approved by the State of Design Authority (or their delegated agent). You are required to assure the product is airworthy before it is returned to service.</P>
              <HD SOURCE="HD1">(m) Related Information</HD>
              <P>Refer to MCAI European Aviation Safety Agency (EASA) Airworthiness Directive 2011-0015, dated January 31, 2011; and the service information specified in paragraphs (m)(1) through (m)(5) of this AD; for related information:</P>
              <P>(1) Airbus Service Bulletin A320-28-1118, Revision 03, including Appendix 1, dated May 12, 2009.</P>
              <P>(2) Airbus Service Bulletin A320-28-1132, Revision 04, including Appendices 1 and 2, dated February 1, 2010.</P>
              <P>(3) Airbus Service Bulletin A320-28-1145, Revision 01, including Appendix 01, dated April 27, 2007.</P>
              <P>(4) Airbus Service Bulletin A320-28-1154, Revision 01, dated April 7, 2008.</P>
              <P>(5) Airbus Service Bulletin A320-53-1227, Revision 01, dated May 31, 2010.</P>
            </EXTRACT>
          </SECTION>
          <SIG>
            <DATED>Issued in Renton, Washington, on March 1, 2012.</DATED>
            <NAME>Jeffrey E. Duven,</NAME>
            <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
          </SIG>
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6465 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-13-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Federal Aviation Administration</SUBAGY>
        <CFR>14 CFR Part 39</CFR>
        <DEPDOC>[Docket No. FAA-2009-0288; Directorate Identifier 2008-NM-214-AD]</DEPDOC>
        <RIN>RIN 2120-AA64</RIN>
        <SUBJECT>Airworthiness Directives; The Boeing Company Airplanes</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Aviation Administration (FAA), DOT.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Supplemental notice of proposed rulemaking (NPRM); reopening of comment period.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>We are revising an earlier proposed airworthiness directive (AD) for certain The Boeing Company Model 737-600, -700, -700C, -800, -900 and -900ER series airplanes. That NPRM proposed to require modifying the fluid drain path in the wing leading edge area, forward of the wing front spar, and doing all applicable related investigative and corrective actions. That NPRM was prompted by a report of leaking fuel from the wing leading edge area at the inboard end of the number 5 leading edge slat. This action revises that NPRM by including installing new seal disks on the latches in the fuel shutoff valve access door as part of the modification and by specifying that certain inspections are detailed inspections. This action also revises the applicability to include additional airplanes. We are proposing this AD to prevent flammable fluids from accumulating in the wing leading edge, and draining inboard and onto the engine exhaust nozzle, which could result in a fire. Since these actions impose an additional burden over that proposed in the NPRM, we are reopening the comment period to allow the public the chance to comment on these proposed changes.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>We must receive comments on this supplemental NPRM by April 30, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may send comments, using the procedures found in 14 CFR 11.43 and 11.45, by any of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal:</E>Go to<E T="03">http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Fax:</E>202-493-2251.</P>
          <P>•<E T="03">Mail:</E>U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE., Washington, DC 20590.</P>
          <P>•<E T="03">Hand Delivery:</E>U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.</P>

          <P>For service information identified in this proposed AD, contact Boeing Commercial Airplanes, Attention: Data &amp; Services Management, P.O. Box 3707, MC 2H-65, Seattle, Washington 98124-2207; telephone 206-544-5000, extension 1; fax 206-766-5680; email<E T="03">me.boecom@boeing.com;</E>Internet<E T="03">https://www.myboeingfleet.com.</E>You may review copies of the referenced service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, Washington. For information on the availability of this material at the FAA, call 425-227-1221.</P>
        </ADD>
        <HD SOURCE="HD1">Examining the AD Docket</HD>
        <P>You may examine the AD docket on the Internet at<E T="03">http://www.regulations.gov;</E>or in person at the Docket Management Facility between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this proposed AD (74 FR 15683, April 7, 2009), the regulatory evaluation, any comments received, and other information. The street address for the Docket Office (phone: 800-647-5527) is in the<E T="02">ADDRESSES</E>section. Comments will be available in the AD docket shortly after receipt.</P>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Chris Parker, Aerospace Engineer, Propulsion Branch, ANM-140S, FAA, Seattle Aircraft Certification Office, 1601 Lind Avenue SW., Renton,<PRTPAGE P="15639"/>Washington 98057-3356; phone: 425-917-6496; fax: 425-917-6590; email:<E T="03">chris.r.parker@faa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Comments Invited</HD>

        <P>We invite you to send any written relevant data, views, or arguments about this proposed AD. Send your comments to an address listed under the<E T="02">ADDRESSES</E>section. Include “Docket No. FAA-2009-0288; Directorate Identifier 2008-NM-214-AD” at the beginning of your comments. We specifically invite comments on the overall regulatory, economic, environmental, and energy aspects of this proposed AD. We will consider all comments received by the closing date and may amend this proposed AD because of those comments.</P>
        <P>We will post all comments we receive, without change, to<E T="03">http://www.regulations.gov,</E>including any personal information you provide. We will also post a report summarizing each substantive verbal contact we receive about this proposed AD.</P>
        <HD SOURCE="HD1">Discussion</HD>

        <P>We issued an NPRM to amend 14 CFR part 39 to include an AD that would apply to Model 737-600, -700, -700C, -800, -900 and -900ER series airplanes. That NPRM published in the<E T="04">Federal Register</E>on April 7, 2009 (74 FR 15683). That NPRM proposed to require modifying the fluid drain path in the wing leading edge area, forward of the wing front spar, and doing all applicable related investigative and corrective actions.</P>
        <HD SOURCE="HD1">Actions Since Previous NPRM Was Issued</HD>
        <P>Since we issued the previous NPRM (74 FR 15683, April 7, 2009), Boeing issued Special Attention Service Bulletin 737-57-1293, Revision 2, dated September 28, 2011, to add actions to the modification of the fluid drain path in the wing leading edge area, forward of the wing front spar. The additional actions are installing new seal disks on the latches in the fuel shutoff valve access door. Boeing Special Attention Service Bulletin 737-57-1293, Revision 2, dated September 28, 2011, also adds airplanes with line numbers 2438 through 3833 inclusive to the effectivity. The service information also changed the general visual inspection of the countersink diameter for the bonding jumper fastener hole to a detailed inspection.</P>
        <HD SOURCE="HD1">Comments</HD>
        <P>We gave the public the opportunity to comment on the previous NPRM (74 FR 15683, April 7, 2009). The following presents the comments received on the NPRM and the FAA's response to each comment.</P>
        <HD SOURCE="HD1">Request To Extend Compliance Time</HD>
        <P>Air Transport Association, on behalf of its members American Airlines (AAL) and AirTran Airways, requested that we extend the compliance time of the proposed AD (74 FR 15683, April 7, 2009). AAL requested that the proposed compliance time of 24 months be changed to 72 months. AAL stated that the proposed compliance time of 24 months does not integrate into the current operator maintenance program without significant aircraft maintenance planning adjustments and additional costs. AAL stated that a 72-month compliance time would fit within the maintenance review board heavy C-check schedule.</P>
        <P>We do not agree with the commenter's request to extend the compliance time. Extending the compliance time to 72 months would result in an unacceptable level of risk for the Model 737-600, -700, -700C, -800, -900, and -900ER fleet. We have determined that the compliance time of 24 months represents the maximum interval of time allowable for the affected airplanes to continue to safely operate before the modification is done. Under the provisions of paragraph (h) of this supplemental NPRM, however, we may consider requests for adjustments to the compliance time if data are submitted to substantiate that such an adjustment would provide an acceptable level of safety. We have not changed the supplemental NPRM in this regard.</P>
        <HD SOURCE="HD1">Request To Refer to Revised Service Bulletin</HD>
        <P>Boeing and the Air Transport Association, on behalf of its member AAL, requested that we refer to Boeing Special Attention Service Bulletin 737-57-1293, Revision 1, dated January 11, 2010, in order to incorporate new changes and to prevent issuance of alternative methods of compliance (AMOC).</P>
        <P>We disagree with the request to refer to Boeing Special Attention Service Bulletin 737-57-1293, Revision 1, dated January 11, 2010. Since the date of the commenters' requests, Boeing has issued Special Attention Service Bulletin 737-57-1293, Revision 2, dated September 28, 2011 (described previously), which adds more new changes. We have changed paragraphs (c) and (g) of this supplemental NPRM to refer to Boeing Special Attention Service Bulletin 737-57-1293, Revision 2, dated September 28, 2011.</P>
        <HD SOURCE="HD1">FAA's Determination</HD>
        <P>We are proposing this supplemental NPRM because we evaluated all the relevant information and determined the unsafe condition described previously is likely to exist or develop in other products of these same type designs. Certain changes described above expand the scope of the original NPRM (74 FR 15683, April 7, 2009). As a result, we have determined that it is necessary to reopen the comment period to provide additional opportunity for the public to comment on this supplemental NPRM.</P>
        <HD SOURCE="HD1">Proposed Requirements of the Supplemental NPRM</HD>
        <P>This supplemental NPRM would require accomplishing the actions specified in the service information described previously.</P>
        <HD SOURCE="HD1">Costs of Compliance</HD>
        <P>We estimate that this proposed AD affects 1,072 airplanes of U.S. registry.</P>
        <P>We estimate the following costs to comply with this proposed AD:</P>
        <GPOTABLE CDEF="s100,r80,12,12,12" COLS="5" OPTS="L2,i1">
          <TTITLE>Estimated Costs</TTITLE>
          <BOXHD>
            <CHED H="1">Action</CHED>
            <CHED H="1">Labor cost</CHED>
            <CHED H="1">Parts cost</CHED>
            <CHED H="1">Cost per<LI>product</LI>
            </CHED>
            <CHED H="1">Cost on U.S. operators</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Modification, Group 1 (734 airplanes)</ENT>
            <ENT>50 work-hours × $85 per hour = $4,250</ENT>
            <ENT>$1,262</ENT>
            <ENT>$5,512</ENT>
            <ENT>$4,045,808</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Modification, Group 2 (58 airplanes)</ENT>
            <ENT>27 work-hours × $85 per hour = $2,295</ENT>
            <ENT>1,262</ENT>
            <ENT>3,557</ENT>
            <ENT>206,306</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Modification, Group 3 (280 airplanes)</ENT>
            <ENT>3 work-hours × $85 per hour = $255</ENT>
            <ENT>94</ENT>
            <ENT>349</ENT>
            <ENT>97,720</ENT>
          </ROW>
        </GPOTABLE>
        <PRTPAGE P="15640"/>
        <HD SOURCE="HD1">Authority for This Rulemaking</HD>
        <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. “Subtitle VII: Aviation Programs” describes in more detail the scope of the Agency's authority.</P>
        <P>We are issuing this rulemaking under the authority described in subtitle VII, part A, subpart III, section 44701: “General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
        <HD SOURCE="HD1">Regulatory Findings</HD>
        <P>We determined that this proposed AD would not have federalism implications under Executive Order 13132. This proposed AD would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
        <P>
          <E T="03">For the reasons discussed above, I certify this proposed regulation:</E>
        </P>
        <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
        <P>(2) Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979),</P>
        <P>(3) Will not affect intrastate aviation in Alaska, and</P>
        <P>(4) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
          <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
        </LSTSUB>
        <HD SOURCE="HD1">The Proposed Amendment</HD>
        <P>Accordingly, under the authority delegated to me by the Administrator, the FAA proposes to amend 14 CFR part 39 as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
          <P>1. The authority citation for part 39 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 106(g), 40113, 44701.</P>
          </AUTH>
          <SECTION>
            <SECTNO>§ 39.13</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
            <P>2. The FAA amends § 39.13 by adding the following new airworthiness directive (AD):</P>
            
            <EXTRACT>
              <FP SOURCE="FP-2">
                <E T="04">The Boeing Company:</E>Docket No. FAA-2009-0288; Directorate Identifier 2008-NM-214-AD.</FP>
              
              <HD SOURCE="HD1">(a) Comments Due Date</HD>
              <P>We must receive comments by April 30, 2012.</P>
              <HD SOURCE="HD1">(b) Affected ADs</HD>
              <P>None.</P>
              <HD SOURCE="HD1">(c) Applicability</HD>
              <P>This AD applies to The Boeing Company Model 737-600, -700, -700C, -800, -900 and -900ER series airplanes, certificated in any category, as identified in Boeing Special Attention Service Bulletin 737-57-1293, Revision 2, dated September 28, 2011.</P>
              <HD SOURCE="HD1">(d) Subject</HD>
              <P>Joint Aircraft System Component (JASC)/Air Transport Association (ATA) of America Code 57, Wings.</P>
              <HD SOURCE="HD1">(e) Unsafe Condition</HD>
              <P>This AD was prompted by a report of leaking fuel from the wing leading edge area at the inboard end of the number 5 leading edge slat. We are issuing this AD to prevent flammable fluids from accumulating in the wing leading edge, and draining inboard and onto the engine exhaust nozzle, which could result in a fire.</P>
              <HD SOURCE="HD1">(f) Compliance</HD>
              <P>Comply with this AD within the compliance times specified, unless already done.</P>
              <HD SOURCE="HD1">(g) Modification</HD>
              <P>Within 24 months after the effective date of this AD, modify the fluid drain path in the wing leading edge area, forward of the wing front spar, and do all applicable related investigative and corrective actions, by accomplishing all applicable actions specified in the Accomplishment Instructions of Boeing Special Attention Service Bulletin 737-57-1293, Revision 2, dated September 28, 2011. Do all applicable related investigative and corrective actions before further flight.</P>
              <HD SOURCE="HD1">(h) Alternative Methods of Compliance (AMOCs)</HD>

              <P>(1) The Manager, Seattle Aircraft Certification Office, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the manager of the ACO, send it to the attention of the person identified in the Related Information section of this AD. Information may be emailed to:<E T="03">9-ANM-Seattle-ACO-AMOC-Requests@faa.gov.</E>
              </P>
              <P>(2) Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office.</P>
              <HD SOURCE="HD1">(i) Related Information</HD>

              <P>(1) For more information about this AD, contact Chris R. Parker, Aerospace Engineer, Propulsion Branch, ANM-140S, FAA, Seattle Aircraft Certification Office, 1601 Lind Avenue SW., Renton, Washington 98057-3356; phone: 425-917-6496; fax: 425-917-6590; email:<E T="03">chris.r.parker@faa.gov.</E>
              </P>

              <P>(2) For service information identified in this AD, contact Boeing Commercial Airplanes, Attention: Data &amp; Services Management, P.O. Box 3707, MC 2H-65, Seattle, Washington 98124-2207; telephone 206-544-5000, extension 1; fax 206-766-5680; email<E T="03">me.boecom@boeing.com;</E>Internet<E T="03">https://www.myboeingfleet.com.</E>You may review copies of the referenced service information at the FAA, Transport AirplaneDirectorate, 1601 Lind Avenue SW., Renton, Washington. For information on the availability of this material at the FAA, call 425-227-1221.</P>
            </EXTRACT>
          </SECTION>
          <SIG>
            <DATED>Issued in Renton, Washington, on February 23, 2012.</DATED>
            <NAME>Ali Bahrami,</NAME>
            <TITLE>Manager,Transport Airplane Directorate,Aircraft Certification Service.</TITLE>
          </SIG>
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6468 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-13-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Federal Aviation Administration</SUBAGY>
        <CFR>14 CFR Part 39</CFR>
        <DEPDOC>[Docket No. FAA-2010-0036; Directorate Identifier 2009-NM-077-AD]</DEPDOC>
        <RIN>RIN 2120-AA64</RIN>
        <SUBJECT>Airworthiness Directives; The Boeing Company Airplanes</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Aviation Administration (FAA), DOT.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Supplemental notice of proposed rulemaking (NPRM); reopening of comment period.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>We are revising an earlier proposed airworthiness directive (AD) for certain The Boeing Company Model 737-200, -200C, -300, -400, and -500 series airplanes. That NPRM proposed to require inspections for cracking and corrosion under the number 3 very high frequency (VHF) antenna, and corrective actions if necessary; and, for certain airplanes, replacing bonded skin panels with solid skin panels if not previously accomplished. That NPRM was prompted by reports of cracks in the skin and surrounding structure under the number 3 VHF antenna on the lower external surface of the airplane at buttock line 0.0, aft of the main landing gear wheel well. This action revises that NPRM by adding an optional preventive<PRTPAGE P="15641"/>modification, which would terminate the inspection requirements for certain airplanes; changing certain repairs; and adding inspections. We are proposing this supplemental NPRM to detect and correct cracks and corrosion of the skin and surrounding structure under the number 3 VHF antenna, which could result in separation of the antenna from the airplane, and rapid depressurization of the airplane. Since these actions impose an additional burden over that proposed in the original NPRM, we are reopening the comment period to allow the public the chance to comment on these proposed changes.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>We must receive comments on this supplemental NPRM by April 30, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may send comments by any of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal:</E>Go to<E T="03">http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Fax:</E>202-493-2251.</P>
          <P>•<E T="03">Mail:</E>U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE., Washington, DC 20590.</P>
          <P>•<E T="03">Hand Delivery:</E>U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.</P>

          <P>For service information identified in this AD, contact Boeing Commercial Airplanes, Attention: Data &amp; Services Management, P.O. Box 3707, MC 2H-65, Seattle, Washington 98124-2207; telephone 206-544-5000, extension 1; fax 206-766-5680; email<E T="03">me.boecom@boeing.com;</E>Internet<E T="03">https://www.myboeingfleet.com.</E>You may review copies of the referenced service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, Washington. For information on the availability of this material at the FAA, call 425-227-1221.</P>
        </ADD>
        <HD SOURCE="HD1">Examining the AD Docket</HD>
        <P>You may examine the AD docketon the Internet at<E T="03">http://www.regulations.gov;</E>or in person at the Docket Management Facility between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this proposed AD, the regulatory evaluation, any comments received, and other information. The street address for the Docket Office (phone: 800-647-5527) is in the<E T="02">ADDRESSES</E>section. Comments will be available in the AD docket shortly after receipt.</P>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Wayne Lockett, Aerospace Engineer, Airframe Branch, ANM-120S, FAA, Seattle Aircraft Certification Office, 1601 Lind Avenue SW., Renton, Washington 98057-3356; phone: (425) 917-6447; fax: (425) 917-6590; email:<E T="03">wayne.lockett@faa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Comments Invited</HD>

        <P>We invite you to send any written relevant data, views, or arguments about this proposed AD. Send your comments to an address listed under the<E T="02">ADDRESSES</E>section. Include “Docket No. FAA-2010-0036; Directorate Identifier 2009-NM-077-AD” at the beginning of your comments. We specifically invite comments on the overall regulatory, economic, environmental, and energy aspects of this proposed AD. We will consider all comments received by the closing date and may amend this proposed AD because of those comments.</P>
        <P>We will post all comments we receive, without change, to<E T="03">http://www.regulations.gov,</E>including any personal information you provide. We will also post a report summarizing each substantive verbal contact we receive about this proposed AD.</P>
        <HD SOURCE="HD1">Discussion</HD>

        <P>We issued an NPRM to amend 14 CFR part 39 to include an airworthiness directive (AD) that would apply to certain The Boeing Company Model 737-200, -200C, -300, -400, and -500 series airplanes. That original NPRM was published in the<E T="04">Federal Register</E>on April 15, 2010 (75 FR 19564). That original NPRM proposed to require repetitive inspections for cracking and corrosion of the skin and surrounding structure under the number 3 VHF antenna, and corrective actions if necessary. Also, for certain airplanes, that original NPRM proposed to require replacing bonded skin panels with solid skin panels if not previously accomplished.</P>
        <HD SOURCE="HD1">Actions Since Previous NPRM (75 FR 19564, April 15, 2010) Was Issued</HD>
        <P>The original NPRM (75 FR 19564, April 15, 2010) referred to Boeing Special Attention Service Bulletin 737-53-1287, dated March 11, 2009. Since we issued the original NPRM, we have reviewed Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010. Among other things, this service bulletin provides the following changes:</P>
        <P>• Adds an optional preventive modification for certain airplane groups, which would eliminate the need for the repetitive inspections of those airplanes. The modification involves various high frequency eddy current (HFEC) and detailed inspections for cracking and corrosion of the skin, support channel, holes, and support structure in the area of the number 3 VHF antenna; and repair if necessary, or replacing a cracked or corroded support channel with a new or serviceable support channel, if necessary. The modification also entails installing antenna support structure.</P>
        <P>• Reassigns certain airplanes to different groups.</P>
        <P>• Gives instructions for doing repairs if a crack is found, for certain airplane groups and certain conditions.</P>
        <P>• Adds HFEC inspections (that are done along with previously specified internal detailed inspections) with the antenna removed.</P>
        <P>• Adds Group 7 airplanes (line numbers 1-291) and specifies that, for these airplanes, operators must contact Boeing for inspection, repair, and preventive modification instructions. These airplanes are subject to a prior or concurrent action of replacing bonded skin panels with solid skin panels, as specified in Part V of Boeing Service Bulletin 737-53A1042, Revision 9, dated July 25, 1991. (The actions specified in that service bulletin are already required by AD 90-06-02, Amendment 39-6489 (55 FR 8372, March 7, 1990)).</P>
        <HD SOURCE="HD1">Comments</HD>
        <P>We gave the public the opportunity to comment on the original NPRM (75 FR 19564, April 15, 2010). The following presents the comment received on the NPRM and the FAA's response to the comment.</P>
        <HD SOURCE="HD1">Request To Change Requirements for Certain Airplanes</HD>
        <P>Boeing submitted a comment related to the service information. However, the substance of the comment is addressed in Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010 as discussed above in “Actions Since Previous NPRM (75 FR 19564, April 15, 2010) Was Issued.”</P>
        <HD SOURCE="HD1">FAA's Determination</HD>

        <P>We are proposing this supplemental NPRM because we evaluated all the relevant information and determined the unsafe condition described previously is likely to exist or develop in other products of these same type designs. Certain changes described above expand the scope of the original<PRTPAGE P="15642"/>NPRM (75 FR 19564, April 15, 2010). As a result, we have determined that it is necessary to reopen the comment period to provide additional opportunity for the public to comment on this supplemental NPRM.</P>
        <HD SOURCE="HD1">Proposed Requirements of the Supplemental NPRM</HD>
        <P>This supplemental NPRM would require accomplishing the actions specified in the revised service information described previously, except as discussed under “Differences Between the Supplemental NPRM and the Service Information.”</P>
        <HD SOURCE="HD1">Differences Between the Supplemental NPRM and the Service Information</HD>
        <P>Where paragraph 1.A., “Effectivity,” of Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010, places Model 737-200 and -200C airplanes having line numbers 1-291 into group 7, for purposes of this supplemental NPRM, these airplanes would be subject to the proposed requirements for Group 2, Configuration 1, 2, or 3, as applicable. There are no configuration differences for airplanes having line numbers 1-291 from the Group 2 airplanes.</P>
        <P>Table 10 in paragraph 1.E., “Compliance,” of Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010; and Part 8 of the Accomplishment Instructions of Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010; specify post-repair/modification inspections at the number 3 VHF antenna location, which may be used in support of compliance with section 121.1109(c)(2) or 129.109(c)(2) of the Federal Aviation Regulations (14 CFR 121.1109(c)(2) or 129.109(c)(2)), but this supplemental NPRM does not propose to require those post-repair/modification inspections. This difference has been coordinated with Boeing.</P>
        <HD SOURCE="HD1">Costs of Compliance</HD>
        <P>We estimate that this proposed AD will affect 629 airplanes of U.S. registry.</P>
        <P>We estimate the following costs to comply with this proposed AD:</P>
        <GPOTABLE CDEF="s50,r50,xs48,r50,12,r50" COLS="6" OPTS="L2,i1">
          <TTITLE>Estimated Costs</TTITLE>
          <BOXHD>
            <CHED H="1">Action</CHED>
            <CHED H="1">Labor cost</CHED>
            <CHED H="1">Parts cost</CHED>
            <CHED H="1">Cost per product</CHED>
            <CHED H="1">Number of U.S.-<LI>registered</LI>
              <LI>airplanes</LI>
            </CHED>
            <CHED H="1">Cost on U.S. operators</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Inspection</ENT>
            <ENT>Up to 13 work-hours × $85 per hour = Up to $1,105 per inspection cycle</ENT>
            <ENT>None</ENT>
            <ENT>Up to $1,105 per inspection cycle</ENT>
            <ENT>629</ENT>
            <ENT>Up to $695,045 per inspection cycle.</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Concurrent Replacement for Group 2 and Group 7airplanes<SU>1</SU>
            </ENT>
            <ENT>2,112 work-hours × $85 per hour = $179,520</ENT>
            <ENT>$35,000</ENT>
            <ENT>$214,520</ENT>
            <ENT>387</ENT>
            <ENT>$83,019,240.</ENT>
          </ROW>
          <TNOTE>
            <SU>1</SU>The concurrent modification for Group 2 and Group 7 airplanes required by this proposed AD is already required by AD 90-06-02, Amendment 39-6489 (55 FR 8372, March 7, 1990). AD 90-06-02 mandated the skin replacement within 20 years of the manufacture date of the airplane. All Group 2 and Group 7 airplanes have exceeded the 20-year threshold.</TNOTE>
        </GPOTABLE>
        <P>We have received no definitive data that would enable us to provide a cost estimate for the on-condition actions specified in this AD.</P>
        <HD SOURCE="HD1">Authority for This Rulemaking</HD>
        <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. “Subtitle VII: Aviation Programs” describes in more detail the scope of the Agency's authority.</P>
        <P>We are issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701: “General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
        <HD SOURCE="HD1">Regulatory Findings</HD>
        <P>We determined that this proposed AD would not have federalism implications under Executive Order 13132. This proposed AD would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
        <P>
          <E T="03">For the reasons discussed above, I certify this proposed regulation:</E>
        </P>
        <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
        <P>(2) Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979),</P>
        <P>(3) Will not affect intrastate aviation in Alaska, and</P>
        <P>(4) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
          <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
        </LSTSUB>
        <HD SOURCE="HD1">The Proposed Amendment</HD>
        <P>Accordingly, under the authority delegated to me by the Administrator, the FAA proposes to amend 14 CFR part 39 as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
          <P>1. The authority citation for part 39 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 106(g), 40113, 44701.</P>
          </AUTH>
          <SECTION>
            <SECTNO>§ 39.13</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
            <P>2. The FAA amends § 39.13 by adding the following new airworthiness directive (AD):</P>
            
            <EXTRACT>
              
              <FP SOURCE="FP-2">
                <E T="04">The Boeing Company:</E>Docket No. FAA-2010-0036; Directorate Identifier 2009-NM-077-AD.</FP>
              <HD SOURCE="HD1">(a) Comments Due Date</HD>
              <P>We must receive comments by April 30, 2012.<PRTPAGE P="15643"/>
              </P>
              <HD SOURCE="HD1">(b) Affected ADs</HD>
              <P>AD 90-06-02, Amendment 39-6489 (55 FR 8372, March 7, 1990), affects this AD.</P>
              <HD SOURCE="HD1">(c) Applicability</HD>
              <P>This AD applies to The Boeing Company Model 737-200, -200C, -300, -400, -500 series airplanes, certificated in any category, as identified in Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010.</P>
              <HD SOURCE="HD1">(d) Subject</HD>
              <P>Joint Aircraft System Component (JASC)/Air Transport Association (ATA) of America Code 53: Fuselage.</P>
              <HD SOURCE="HD1">(e) Unsafe Condition</HD>
              <P>This AD was prompted by reports of cracks of the skin and surrounding structure under the number 3 very high frequency (VHF) antenna on the lower external surface of the airplane at buttock line 0.0, aft of the main landing gear wheel well. We are issuing this AD to detect and correct cracks and corrosion of the skin and surrounding structure under the number 3 VHF antenna, which could result in separation of the antenna from the airplane, and rapid depressurization of the airplane.</P>
              <HD SOURCE="HD1">(f) Compliance</HD>
              <P>Comply with this AD within the compliance times specified, unless already done.</P>
              <HD SOURCE="HD1">(g) Inspections</HD>
              <P>Except as required by paragraph (i)(1) of this AD, at the applicable times specified in tables 1 through 9, paragraph 1.E., “Compliance,” of Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010: Do the applicable inspections (external detailed and high frequency eddy current (HFEC), external detailed, external HFEC, or internal detailed and HFEC) for cracks or corrosion in the skin, support, frames, stringers, or antenna, as applicable. Do the inspections in accordance with Parts 1, 3, 4, and 5 of the Accomplishment Instructions of Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010, except as required by paragraphs (i)(2) and (i)(3) of this AD. Repeat the applicable inspections thereafter at the applicable times specified in tables 1 through 9, paragraph 1.E., “Compliance,” of Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010, until the actions required by paragraph (j) of this AD are done.</P>
              <HD SOURCE="HD1">(h) Repair</HD>
              <P>(1) If any crack or corrosion is found during any inspection required by paragraph (g) of this AD: Repair before further flight, in accordance with the Accomplishment Instructions of Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010, except as required by paragraphs (i)(2) and (i)(3) of this AD. Repair of any crack or corrosion terminates the repetitive inspection requirements of paragraph (g) of this AD for the repaired area only.</P>
              <P>(2) Operators must obtain an approved damage tolerance evaluation for any repair installed to comply with Section 121.1109(c)(2) or 129.109(c)(2) of the Code of Federal Regulations (14 CFR 121.1109(c)(2) or 129.109(c)(2)).</P>
              <P>Note 1 to paragraph (h)(2) of this AD: Additional guidance on damage tolerance evaluation for repairs can be found in table 10 in paragraph 1.E., “Compliance,” of Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010; and Part 8 of the Accomplishment Instructions of Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010.</P>
              <HD SOURCE="HD1">(i) Exceptions</HD>
              <P>(1) Where Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010, specifies a compliance time “after the original issue date of this service bulletin:” this AD requires compliance within the specified compliance time after the effective date of this AD.</P>
              <P>(2) Where Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010, specifies contacting Boeing for inspection or repair instructions: Do the applicable action using a method approved in accordance with the procedures specified in paragraph (m) of this AD.</P>
              <P>(3) For Group 7 airplanes, as identified in paragraph 1.A., “Effectivity,” of Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010: Use the applicable instructions for Group 2, Configuration 1, 2, or 3, as identified in Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010.</P>
              <HD SOURCE="HD1">(j) Optional Terminating Action</HD>
              <P>For Groups 1, 2, 3, 4, 6, and 7 airplanes, as identified in Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010: Except as provided by paragraphs (i)(2) and (i)(3) of this AD, accomplishment of the preventive modification, including all applicable HFEC and detailed inspections for cracking or corrosion inside or outside the repair skin cutout area, in the frame fastener holes, or in the support channel; and all applicable repairs or replacements; as specified in the Accomplishment Instructions of Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010: Terminates the repetitive inspection requirements of paragraph (g) of this AD.</P>
              <HD SOURCE="HD1">(k) Concurrent Skin Panel Replacement</HD>
              <P>For Groups 2 and 7 airplanes, as identified in Boeing Special Attention Service Bulletin 737-53-1287, Revision 1, dated November 15, 2010: Before or concurrently with accomplishing the requirements of paragraph (g) of this AD, do the replacement of the bonded skin panels with solid skin panels, in accordance with the Accomplishment Instructions of Boeing Service Bulletin 737-53A1042, Revision 9, dated July 25, 1991; except as required by paragraph (i)(3) of this AD. The actions specified in paragraph (k) of this AD are also required by AD 90-06-02, Amendment 39-6489 (55 FR 8372, March 7, 1990).</P>
              <HD SOURCE="HD1">(l) Credit for Previous Actions</HD>
              <P>(1) This paragraph gives credit for the replacement required by paragraph (k) of this AD, if the replacement of bonded skin panels with solid skin panels was accomplished before the effective date of this AD using the Accomplishment Instructions of the service information identified in paragraphs (l)(1)(i), (l)(1)(ii), (l)(1)(iii), and (l)(1)(iv) of this AD:</P>
              <P>(i) Boeing Service Bulletin 737-53A1042 Revision 5, dated October 5, 1984.</P>
              <P>(ii) Boeing Service Bulletin 737-53A1042 Revision 6, dated August 10, 1989.</P>
              <P>(iii) Boeing Service Bulletin 737-53A1042 Revision 7, dated October 19, 1989.</P>
              <P>(iv) Boeing Service Bulletin 737-53A1042 Revision 8, dated July 19, 1990.</P>
              <P>(2) This paragraph gives credit for the inspections required by paragraph (g) of this AD, if the inspections were accomplished before the effective date of this AD using the Accomplishment Instructions of Boeing Special Attention Service Bulletin 737-53-1287, dated March 11, 2009.</P>
              <HD SOURCE="HD1">(m) Alternative Methods of Compliance (AMOCs)</HD>

              <P>(1) The Manager, Seattle Aircraft Certification Office (ACO), FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the manager of the ACO, send it to the attention of the person identified in the Related Information section of this AD. Information may be emailed to<E T="03">9-ANM-Seattle-ACO-AMOC-Requests@faa.gov.</E>
              </P>
              <P>(2) Before using any approved AMOC, notify your Principal Maintenance Inspector or Principal Avionics Inspector, as appropriate, or lacking a principal inspector, your local Flight Standards District Office.</P>
              <P>(3) An AMOC that provides an acceptable level of safety may be used for any repair required by this AD if it is approved by the Boeing Commercial Airplanes Organization Designation Authorization (ODA) that has been authorized by the Manager, Seattle ACO to make those findings. For a repair method to be approved, the repair must meet the certification basis of the airplane, and the approval must specifically refer to this AD.</P>
              <HD SOURCE="HD1">(n) Related Information</HD>

              <P>(1) For more information about this AD, contact Wayne Lockett, Aerospace Engineer, Airframe Branch, ANM-120S, FAA, Seattle ACO, 1601 Lind Avenue SW., Renton, Washington 98057-3356; phone: 425-917-6447; fax: 425-917-6590; email:<E T="03">wayne.lockett@faa.gov.</E>
              </P>

              <P>(2) For service information identified in this AD, contact Boeing Commercial Airplanes, Attention: Data &amp; Services Management, P.O.  Box 3707, MC 2H-65, Seattle, Washington 98124-2207; telephone 206-544-5000, extension 1; fax 206-766-5680; email<E T="03">me.boecom@boeing.com;</E>Internet<E T="03">https://www.myboeingfleet.com.</E>You may review copies of the referenced service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, Washington. For information on the<PRTPAGE P="15644"/>availability of this material at the FAA, call 425-227-1221.</P>
            </EXTRACT>
          </SECTION>
          <SIG>
            <DATED>Issued in Renton, Washington, on March 1, 2012.</DATED>
            <NAME>Jeffrey E. Duven,</NAME>
            <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
          </SIG>
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6470 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-13-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Federal Aviation Administration</SUBAGY>
        <CFR>14 CFR Part 39</CFR>
        <DEPDOC>[Docket No. FAA-2012-0192; Directorate Identifier 2011-NM-225-AD]</DEPDOC>
        <RIN>RIN 2120-AA64</RIN>
        <SUBJECT>Airworthiness Directives; Airbus Airplanes</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Aviation Administration (FAA), DOT.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of proposed rulemaking (NPRM).</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>We propose to adopt a new airworthiness directive (AD) for certain Airbus Model A330-200 and -200 freighter series airplanes; and Model A340-200, -300, -500, and -600 series airplanes. This proposed AD was prompted by fuel system reviews conducted by the manufacturer. This proposed AD would require modification of the control circuit for the fuel pumps for the center fuel tanks for certain airplanes, and center and rear fuel tanks for certain other airplanes. We are proposing this AD to prevent the potential of ignition sources inside fuel tanks, which, in combination with flammable fuel vapors, could result in fuel tank explosions and consequent loss of the airplane.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>We must receive comments on this proposed AD by April 30, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may send comments by any of the following methods:</P>
          <P>•<E T="03">Federal eRulemaking Portal:</E>Go to<E T="03">http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Fax:</E>(202) 493-2251.</P>
          <P>•<E T="03">Mail:</E>U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE., Washington, DC 20590.</P>
          <P>•<E T="03">Hand Delivery:</E>U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.</P>

          <P>For service information identified in this proposed AD, contact Airbus SAS—Airworthiness Office—EAL, 1 Rond Point Maurice Bellonte, 31707 Blagnac Cedex, France; telephone +33 5 61 93 36 96; fax +33 5 61 93 45 80; email<E T="03">airworthiness.A330-A340@airbus.com;</E>Internet<E T="03">http://www.airbus.com.</E>You may review copies of the referenced service information at the FAA, Transport Airplane Directorate, 1601 Lind Avenue SW., Renton, Washington. For information on the availability of this material at the FAA, call 425-227-1221.</P>
        </ADD>
        <HD SOURCE="HD1">Examining the AD Docket</HD>
        <P>You may examine the AD docket on the Internet at<E T="03">http://www.regulations.gov;</E>or in person at the Docket Operations office between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this proposed AD, the regulatory evaluation, any comments received, and other information. The street address for the Docket Operations office (telephone (800) 647-5527) is in the<E T="02">ADDRESSES</E>section. Comments will be available in the AD docket shortly after receipt.</P>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Vladimir Ulyanov, Aerospace Engineer, International Branch, ANM-116, Transport Airplane Directorate, FAA, 1601 Lind Avenue SW., Renton, Washington 98057-3356; telephone 425-227-1138; fax 425-227-1149.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Comments Invited</HD>

        <P>We invite you to send any written relevant data, views, or arguments about this proposed AD. Send your comments to an address listed under the<E T="02">ADDRESSES</E>section. Include “Docket No. FAA-2012-0192; Directorate Identifier 2011-NM-225-AD” at the beginning of your comments. We specifically invite comments on the overall regulatory, economic, environmental, and energy aspects of this proposed AD. We will consider all comments received by the closing date and may amend this proposed AD based on those comments.</P>
        <P>We will post all comments we receive, without change, to<E T="03">http://www.regulations.gov,</E>including any personal information you provide. We will also post a report summarizing each substantive verbal contact we receive about this proposed AD.</P>
        <HD SOURCE="HD1">Discussion</HD>
        <P>The European Aviation Safety Agency (EASA), which is the Technical Agent for the Member States of the European Community, has issued EASA Airworthiness Directive 2011-0196, dated October 7, 2011 (referred to after this as “the MCAI”), to correct an unsafe condition for the specified products. The MCAI states:</P>
        
        <EXTRACT>
          <P>* * * [T]he FAA issued a set of new rules related to Fuel Tank Safety including Special Federal Aviation Regulation (SFAR) 88. In line with SFAR88, the JAA [Joint Aviation Authorities] issued policy JAA INT/POL 25/12 and recommended to the National Aviation Authorities (NAA) the application of a similar regulation.</P>
          <P>To ensure compliance with the requirements set by SFAR88 and JAA INT/POL 25/12, this [EASA] AD requires that Ground Fault Interrupters (GFI) are installed into the electrical power supply circuits of fuel pumps for which the canisters become uncovered during normal operation, taking into account normal fuel reserve or the fuel level, triggering the low fuel level warning.</P>
          <P>The function of this additional system protection is to electrically isolate the pump if a ground fault condition occurs downstream of the GFI. The GFI gives additional earth leakage protection to the downstream circuit.</P>
        </EXTRACT>
        
        <FP>The unsafe condition is the potential of ignition sources inside fuel tanks, which, in combination with flammable fuel vapors, could result in fuel tank explosions and consequent loss of the airplane. The corrective action is modifying the control circuits of the fuel pump for the rear and center fuel tanks. You may obtain further information by examining the MCAI in the AD docket.</FP>
        <P>The FAA has examined the underlying safety issues involved in fuel tank explosions on several large transport airplanes, including the adequacy of existing regulations, the service history of airplanes subject to those regulations, and existing maintenance practices for fuel tank systems. As a result of those findings, we issued a regulation titled “Transport Airplane Fuel Tank System Design Review, Flammability Reduction and Maintenance and Inspection Requirements” (66 FR 23086, May 7, 2001). In addition to new airworthiness standards for transport airplanes and new maintenance requirements, this rule included Special Federal Aviation Regulation No. 88 (“SFAR 88,” Amendment 21-78, and subsequent Amendments 21-82 and 21-83).</P>

        <P>Among other actions, SFAR 88 (66 FR 23086, May 7, 2001) requires certain type design (i.e., type certificate (TC) and supplemental type certificate (STC)) holders to substantiate that their fuel tank systems can prevent ignition sources in the fuel tanks. This requirement applies to type design holders for large turbine-powered transport airplanes and for subsequent modifications to those airplanes. It requires them to perform design reviews<PRTPAGE P="15645"/>and to develop design changes and maintenance procedures if their designs do not meet the new fuel tank safety standards. As explained in the preamble to the rule, we intended to adopt airworthiness directives to mandate any changes found necessary to address unsafe conditions identified as a result of these reviews.</P>
        <P>In evaluating these design reviews, we have established four criteria intended to define the unsafe conditions associated with fuel tank systems that require corrective actions. The percentage of operating time during which fuel tanks are exposed to flammable conditions is one of these criteria. The other three criteria address the failure types under evaluation: single failures, single failures in combination with a latent condition(s), and in-service failure experience. For all four criteria, the evaluations included consideration of previous actions taken that may mitigate the need for further action.</P>
        <P>The Joint Aviation Authorities (JAA) has issued a regulation that is similar to SFAR 88 (66 FR 23086, May 7, 2001). (The JAA is an associated body of the European Civil Aviation Conference (ECAC) representing the civil aviation regulatory authorities of a number of European States who have agreed to co-operate in developing and implementing common safety regulatory standards and procedures.) Under this regulation, the JAA stated that all members of the ECAC that hold type certificates for transport category airplanes are required to conduct a design review against explosion risks.</P>
        <P>We have determined that the actions identified in this proposed AD are necessary to reduce the potential of ignition sources inside fuel tanks, which, in combination with flammable fuel vapors, could result in fuel tank explosions and consequent loss of the airplane.</P>
        <HD SOURCE="HD1">Relevant Service Information</HD>
        <P>Airbus has issued the following mandatory service bulletins. The actions described in this service information are intended to correct the unsafe condition identified in the MCAI.</P>
        <P>• Airbus Mandatory Service Bulletin A330-28-3113, dated July 19, 2011 (for Model A330-200 and -200 freighter series airplanes).</P>
        <P>• Airbus Mandatory Service Bulletin A340-28-4129, dated July 19, 2011 (for Model A340-200 and -300 series airplanes).</P>
        <P>• Airbus Mandatory Service Bulletin A340-28-5051, dated September 1, 2011 (for Model A340-500 and -600 series airplanes).</P>
        <HD SOURCE="HD1">FAA's Determination and Requirements of This Proposed AD</HD>
        <P>This product has been approved by the aviation authority of another country, and is approved for operation in the United States. Pursuant to our bilateral agreement with the State of Design Authority, we have been notified of the unsafe condition described in the MCAI and service information referenced above. We are proposing this AD because we evaluated all pertinent information and determined an unsafe condition exists and is likely to exist or develop on other products of the same type design.</P>
        <HD SOURCE="HD1">Costs of Compliance</HD>
        <P>Based on the service information, we estimate that this proposed AD would affect about 29 products of U.S. registry. We also estimate that it would take about 10 work-hours per product to comply with the basic requirements of this proposed AD. The average labor rate is $85 per work-hour. Required parts would cost about $3,480 per product. Where the service information lists required parts costs that are covered under warranty, we have assumed that there will be no charge for these parts. As we do not control warranty coverage for affected parties, some parties may incur costs higher than estimated here. Based on these figures, we estimate the cost of the proposed AD on U.S. operators to be $125,570, or $4,330 per product.</P>
        <HD SOURCE="HD1">Authority for This Rulemaking</HD>
        <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. “Subtitle VII: Aviation Programs,” describes in more detail the scope of the Agency's authority.</P>
        <P>We are issuing this rulemaking under the authority described in “Subtitle VII, Part A, Subpart III, Section 44701: General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.</P>
        <HD SOURCE="HD1">Regulatory Findings</HD>
        <P>We determined that this proposed AD would not have federalism implications under Executive Order 13132. This proposed AD would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
        <P>
          <E T="03">For the reasons discussed above, I certify this proposed regulation:</E>
        </P>
        <P>1. Is not a “significant regulatory action” under Executive Order 12866;</P>
        <P>2. Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979);</P>
        <P>3. Will not affect intrastate aviation in Alaska; and</P>
        <P>4. Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
        <P>We prepared a regulatory evaluation of the estimated costs to comply with this proposed AD and placed it in the AD docket.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
          <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
        </LSTSUB>
        <HD SOURCE="HD1">The Proposed Amendment</HD>
        <P>Accordingly, under the authority delegated to me by the Administrator, the FAA proposes to amend 14 CFR part 39 as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
          <P>1. The authority citation for part 39 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>49 U.S.C. 106(g), 40113, 44701.</P>
          </AUTH>
          <SECTION>
            <SECTNO>§ 39.13</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
            <P>2. The FAA amends § 39.13 by adding the following new AD:</P>
            
            <EXTRACT>
              <FP SOURCE="FP-2">
                <E T="04">Airbus:</E>Docket No. FAA-2012-0192; Directorate Identifier 2011-NM-225-AD.</FP>
              <HD SOURCE="HD1">(a) Comments Due Date</HD>
              <P>We must receive comments by April 30, 2012.</P>
              <HD SOURCE="HD1">(b) Affected ADs</HD>
              <P>None.</P>
              <HD SOURCE="HD1">(c) Applicability</HD>
              <P>This AD applies to the airplanes specified in paragraphs (c)(1), (c)(2), and (c)(3) of this AD, certificated in any category.</P>
              <P>(1) Airbus Model A330-201, -202, -203, -223, and -243 airplanes; all serial numbers; except those on which Airbus modification 200242 has been accomplished in production.</P>

              <P>(2) Airbus Model A330-223F and -243F airplanes; all serial numbers; except airplanes on which Airbus modification 58623 has been accomplished in production and on which Airbus modification 200281 has not been accomplished in production; and airplanes on which modification 200242 has been accomplished in production.<PRTPAGE P="15646"/>
              </P>
              <P>(3) Airbus Model A340-211, -212, -213, -311, -312, -313, -541, and -642 airplanes; all serial numbers; except airplanes on which Airbus modification 200242 has been accomplished in production.</P>
              <HD SOURCE="HD1">(d) Subject</HD>
              <P>Air Transport Association (ATA) of America Code 28: Fuel.</P>
              <HD SOURCE="HD1">(e) Reason</HD>
              <P>This AD was prompted by fuel system reviews conducted by the manufacturer. We are issuing this AD to prevent the potential of ignition sources inside fuel tanks, which, in combination with flammable fuel vapors, could result in fuel tank explosions and consequent loss of the airplane.</P>
              <HD SOURCE="HD1">(f) Compliance</HD>
              <P>You are responsible for having the actions required by this AD performed within the compliance times specified, unless the actions have already been done.</P>
              <HD SOURCE="HD1">(g) Actions</HD>
              <P>Within 48 months after the effective date of this AD, do the actions specified in paragraph (g)(1) or (g)(2) of this AD, as applicable.</P>
              <P>(1) For Model A330-200 and -200F series airplanes, and Model A340-200 and -300 series airplanes: Modify the control circuit for the fuel pump for the center fuel tank, in accordance with the Accomplishment Instructions of Airbus Mandatory Service Bulletin A330-28-3113, dated July 19, 2011 (for Model A330-200 and -200 freighter series airplanes); or A340-28-4129, dated July 19, 2011 (for Model A340-200 and -300 series airplanes).</P>
              <P>(2) For Model A340-500 and -600 series airplanes: Modify the control circuit for the fuel pump for the rear and/or center fuel tanks, in accordance with the Accomplishment Instructions of Airbus Mandatory Service Bulletin A340-28-5051, dated September 1, 2011.</P>
              <HD SOURCE="HD1">(h) Other FAA AD Provisions</HD>
              <P>The following provisions also apply to this AD:</P>
              <P>(1)<E T="03">Alternative Methods of Compliance (AMOCs):</E>The Manager, International Branch, ANM-116, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. In accordance with 14 CFR 39.19, send your request to your principal inspector or local Flight Standards District Office, as appropriate. If sending information directly to the International Branch, send it to ATTN: Vladimir Ulyanov, Aerospace Engineer, International Branch, ANM-116, Transport Airplane Directorate, FAA, 1601 Lind Avenue SW., Renton, Washington 98057-3356; telephone 425-227-1138; fax 425-227-1149. Information may be emailed to:<E T="03">9-ANM-116-AMOC-REQUESTS@faa.gov.</E>Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the local flight standards district office/certificate holding district office. The AMOC approval letter must specifically reference this AD.</P>
              <P>(2)<E T="03">Airworthy Product:</E>For any requirement in this AD to obtain corrective actions from a manufacturer or other source, use these actions if they are FAA-approved. Corrective actions are considered FAA-approved if they are approved by the State of Design Authority (or their delegated agent). You are required to assure the product is airworthy before it is returned to service.</P>
              <HD SOURCE="HD1">(i) Related Information</HD>
              <P>Refer to MCAI European Aviation Safety Agency (EASA) Airworthiness Directive 2011-0196, dated October 7, 2011, and the service bulletins specified in paragraphs (i)(1), (i)(2), and (i)(3) of this AD, for related information.</P>
              <P>(1) Airbus Mandatory Service Bulletin A330-28-3113, dated July 19, 2011.</P>
              <P>(2) Airbus Mandatory Service Bulletin A340-28-4129, dated July 19, 2011.</P>
              <P>(3) Airbus Mandatory Service Bulletin A340-28-5051, dated September 1, 2011.</P>
            </EXTRACT>
          </SECTION>
          <SIG>
            <DATED>Issued in Renton, Washington, on March 1, 2012.</DATED>
            <NAME>Jeffrey E. Duven,</NAME>
            <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
          </SIG>
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6461 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-13-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
        <SUBAGY>Internal Revenue Service</SUBAGY>
        <CFR>26 CFR Part 1</CFR>
        <DEPDOC>[REG-168745-03]</DEPDOC>
        <RIN>RIN 1545-BE18</RIN>
        <SUBJECT>Guidance Regarding Deduction and Capitalization of Expenditures Related to Tangible Property; Hearing</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Internal Revenue Service (IRS), Treasury.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Change date of public hearing on proposed rulemaking.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This document changes the date of a public hearing on proposed regulations relating to the deduction and capitalization of expenditures related to tangible property.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The public hearing originally scheduled for Wednesday, April 25, 2012, at 10 a.m. is rescheduled for Wednesday, May 9, 2012, at 10 a.m. Written or electronically submitted public comments along with requests to speak and outlines of topics to be discussed at the public hearing must be received by Tuesday, April 17, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The public hearing is being held in the auditorium of the Internal Revenue Service Building, 1111 Constitution Avenue NW., Washington, DC 20224.</P>

          <P>Due to building security procedures, visitors must enter at the Constitution Avenue entrance. Send submissions to: CC:PA:LPD:PR (REG-168745-03); Room 5203, Internal Revenue Service, POB 7604, Ben Franklin Station, Washington, DC. Submissions may be hand delivered Monday through Friday between the hours of 8 a.m. and 4 p.m. to CC:PA:LPD:PR (REG-168745-03) Courier's Desk, Internal Revenue Service, 1111 Constitution Avenue NW., Washington, DC. Alternatively, comments may be transmitted electronically via the Federal eRulemaking Portal at<E T="03">www.regulations.gov.</E>(IRS-REG-168745-03).</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Funmi Taylor of the Publications and Regulations Branch, Legal Processing Division, Associate Chief Counsel (Procedures and Administration), at (202) 622-7180 (not a toll-free number).</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>A notice of change date of public hearing on proposed rulemaking appearing in the<E T="04">Federal Register</E>on Monday, January 23, 2012 (77 FR 3210), announced that a public hearing relating to the deduction and capitalization of expenditures related to tangible property, would be held on Wednesday, April 25, 2012 at 10 a.m., in the auditorium of the Internal Revenue Service Building, 1111 Constitution Avenue NW., Washington, DC.</P>
        <P>The date of the public hearing has been changed. The hearing is now scheduled for Wednesday, May 9, 2012, beginning at 10 a.m. in the auditorium of the Internal Revenue Service Building at 1111 Constitution Avenue NW., Washington, DC. Requests to speak and outlines of topics to be discussed at the public hearing must be received by Tuesday, April 17, 2012.</P>
        <SIG>
          <NAME>LaNita Van Dyke,</NAME>
          <TITLE>Chief, Publications and Regulations Branch, Legal Processing Division, Associate Chief Counsel, (Procedures and Administration).</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6371 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4830-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <PRTPAGE P="15647"/>
        <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Coast Guard</SUBAGY>
        <CFR>33 CFR Part 100</CFR>
        <DEPDOC>[Docket No. USCG-2012-0046]</DEPDOC>
        <RIN>RIN 1625-AA08</RIN>
        <SUBJECT>Special Local Regulation for Marine Events; Temporary Change of Dates for Recurring Marine Events in the Fifth Coast Guard District, Ocean City Maryland Offshore Grand Prix, Ocean City, MD</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Coast Guard, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of proposed rulemaking.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Coast Guard proposes to temporarily change the enforcement period of special local regulations for one recurring marine event in the Fifth Coast Guard District, specifically, the “Ocean City Maryland Offshore Grand Prix,” hydroplane races on the North Atlantic Ocean near Ocean City, Maryland. The event consists of approximately 50 V-hull and twin-hull inboard hydroplanes racing in heats counter-clockwise around an oval race course, this regulation is necessary to provide for the safety of life on navigable waters during the event. This action is intended to restrict vessel traffic in portions of the North Atlantic Ocean near Ocean City, Maryland during the event.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments and related material must be received by the Coast Guard on or before April 5, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments identified by docket number USCG-2012-0046 using any one of the following methods:</P>
          <P>(1)<E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>
          </P>
          <P>(2)<E T="03">Fax:</E>202-493-2251.</P>
          <P>(3)<E T="03">Mail:</E>Docket Management Facility (M-30), U.S. Department of Transportation, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE., Washington, DC 20590-0001.</P>
          <P>(4)<E T="03">Hand delivery:</E>Same as mail address above, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The telephone number is 202-366-9329.</P>

          <P>To avoid duplication, please use only one of these four methods. See the “Public Participation and Request for Comments” portion of the<E T="02">SUPPLEMENTARY INFORMATION</E>section below for instructions on submitting comments.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>If you have questions on this proposed rule, call or email. If you have questions on this temporary rule, call or email LCDR Christopher O'Neal, Waterways Management Division Chief, Sector Hampton Roads, Coast Guard; telephone 757-668-5581, email<E T="03">Christopher.A.ONeal@uscg.mil.</E>If you have questions on viewing or submitting material to the docket, call Renee V. Wright, Program Manager, Docket Operations, telephone 202-366-9826.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Public Participation and Request for Comments</HD>

        <P>We encourage you to participate in this rulemaking by submitting comments and related materials. All comments received will be posted without change to<E T="03">http://www.regulations.gov</E>and will include any personal information you have provided.</P>
        <HD SOURCE="HD1">Submitting Comments</HD>

        <P>If you submit a comment, please include the docket number for this rulemaking (USCG-2012-0046), indicate the specific section of this document to which each comment applies, and provide a reason for each suggestion or recommendation. You may submit your comments and material online (via<E T="03">http://www.regulations.gov</E>) or by fax, mail, or hand delivery, but please use only one of these means. If you submit a comment online via<E T="03">www.regulations.gov</E>, it will be considered received by the Coast Guard when you successfully transmit the comment. If you fax, hand deliver, or mail your comment, it will be considered as having been received by the Coast Guard when it is received at the Docket Management Facility. We recommend that you include your name and a mailing address, an email address, or a telephone number in the body of your document so that we can contact you if we have questions regarding your submission.</P>
        <P>To submit your comment online, go to<E T="03">http://www.regulations.gov</E>, type the docket number (USCG-2012-0046) in the “SEARCH” box and click “SEARCH.” Click on “Submit a Comment” on the line associated with this rulemaking.</P>
        <P>If you submit your comments by mail or hand delivery, submit them in an unbound format, no larger than 8<FR>1/2</FR>by 11 inches, suitable for copying and electronic filing. If you submit comments by mail and would like to know that they reached the Facility, please enclose a stamped, self-addressed postcard or envelope. We will consider all comments and material received during the comment period and may change the rule based on your comments.</P>
        <HD SOURCE="HD1">Viewing Comments and Documents</HD>

        <P>To view comments, as well as documents mentioned in this preamble as being available in the docket, go to<E T="03">http://www.regulations.gov</E>, type the docket number (USCG-2012-0046) in the “SEARCH” box and click “SEARCH.” Click on Open Docket Folder on the line associated with this rulemaking. You may also visit the Docket Management Facility in Room W12-140 on the ground floor of the Department of Transportation West Building, 1200 New Jersey Avenue SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.</P>
        <HD SOURCE="HD1">Privacy Act</HD>

        <P>Anyone can search the electronic form of comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review a Privacy Act notice regarding our public dockets in the January 17, 2008, issue of the<E T="04">Federal Register</E>(73 FR 3316).</P>
        <HD SOURCE="HD1">Public Meeting</HD>

        <P>We do not now plan to hold a public meeting, but you may submit a request for one using one of the four methods specified under<E T="02">ADDRESSES</E>. Please explain why you believe a public meeting would be beneficial. If we determine that one would aid this rulemaking, we will hold one at a time and place announced by a later notice in the<E T="04">Federal Register</E>.</P>

        <P>For information on facilities or services for individuals with disabilities or to request special assistance at the public meeting, contact LCDR Christopher O'Neal at the telephone number or email address indicated under the<E T="02">FOR FURTHER INFORMATION CONTACT</E>section of this notice.</P>
        <HD SOURCE="HD1">Basis and Purpose</HD>
        <P>Marine events are frequently held on the navigable waters within the boundary of Fifth Coast Guard District. The water activities that typically comprise marine events include sailing regattas, power boat races, swim races and holiday parades. For a description of the geographical area of each Coast Guard Sector—Captain of the Port Zone, please see 33 CFR 3.25.</P>

        <P>This regulation proposes to temporarily change the enforcement period of special local regulations for one recurring marine event within Fifth<PRTPAGE P="15648"/>Coast Guard District. This proposed regulation applies to one marine event in 33 CFR 100.501, Table to § 100.501.</P>
        <P>The Offshore Performance Association (OPA) Racing LLC annually sponsors the “Ocean City Maryland Offshore Grand Prix”, on the waters of the North Atlantic Ocean near Ocean City, Maryland. This year, the event will be held on May 13, 2012. The regulation at 33 CFR 100.501 is effective annually for Ocean City Offshore Challenge marine event. The event consists of approximately 50 V-hull and twin-hull inboard hydroplanes racing in heats counter-clockwise around an oval race course. A fleet of spectator vessels is expected to gather near the event site to view the competition. Therefore, to ensure the safety of participants, spectators, support and transiting vessels, the Coast Guard will temporarily restrict vessel traffic in the event area during the hydroplane races. The regulation at 33 CFR 100.501 would be enforced for the duration of the event. Under the provisions of 33 CFR 100.501, from 11 a.m. to 5 p.m. on May 13, 2012, vessels may not enter the regulated area unless they receive permission from the Coast Guard Patrol Commander.</P>
        <HD SOURCE="HD1">Discussion of Proposed Rule</HD>
        <P>The Coast Guard is establishing a temporary special local regulation on specified waters of the North Atlantic Ocean, in Ocean City, Maryland. The regulated area will be established in the interest of public safety during the “Ocean City Offshore Grand Prix”, and will be enforced from 11 a.m. to 5 p.m. on May 13, 2012. The Coast Guard, at its discretion, when practical will allow the passage of vessels when races are not taking place. Except for participants and vessels authorized by the Captain of the Port or his Representative, no person or vessel may enter or remain in the regulated area.</P>
        <HD SOURCE="HD1">Regulatory Analyses</HD>
        <P>We developed this proposed rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on 13 of these statutes or executive orders.</P>
        <HD SOURCE="HD1">Regulatory Planning and Review</HD>
        <P>This rulemaking is not a significant regulatory action under section 3(f) of Executive Order 12866, Regulatory Planning and Review, as supplemented by Executive Order 13563, Improving Regulation and Regulatory Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of Executive Order 12866 or under section 1 of Executive Order 13563. The Office of Management and Budget has not reviewed it under those Orders.</P>
        <P>We expect the economic impact of this proposed rule to be so minimal that a full Regulatory Evaluation is unnecessary. Although this rule prevents traffic from transiting a portion of certain waterways during specified times, the effect of this regulation will not be significant due to the limited duration that the regulated area will be in effect and the extensive advance notifications that will be made to the maritime community via marine information broadcasts, local radio stations and area newspapers so mariners can adjust their plans accordingly. Additionally, this rulemaking does not change the permanent regulated areas that have been published in 33 CFR 100.501, Table to § 100.501. In some cases vessel traffic may be able to transit the regulated area when the Coast Guard Patrol Commander deems it is safe to do so.</P>
        <HD SOURCE="HD1">Small Entities</HD>
        <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this proposed rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
        <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this proposed rule would not have a significant economic impact on a substantial number of small entities.</P>
        <P>This proposed rule would affect the following entities, some of which might be small entities: the owners or operators of vessels intending to transit this section of the North Atlantic during the event.</P>

        <P>If you think that your business, organization, or governmental jurisdiction qualifies as a small entity and that this rule would have a significant economic impact on it, please submit a comment (see<E T="02">ADDRESSES</E>) explaining why you think it qualifies and how and to what degree this rule would economically affect it. This regulation will not have a significant impact on a substantial number of small entities because: (i) It will be enforced only for a short period of time on two consecutive days; (ii) vessels may be granted the opportunity to transit the safety zone during the period of enforcement if the Patrol Commander deems it safe to do so; (iii) vessels may transit around the safety zone; and (iv) before the enforcement period, the Coast Guard will issue maritime advisories so mariners can adjust their plans accordingly.</P>
        <HD SOURCE="HD1">Assistance for Small Entities</HD>
        <P>Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we want to assist small entities in understanding this proposed rule so that they can better evaluate its effects on them and participate in the rulemaking. If the rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact LCDR Christopher O'Neal. The Coast Guard will not retaliate against small entities that question or complain about this proposed rule or any policy or action of the Coast Guard.</P>
        <HD SOURCE="HD1">Collection of Information</HD>
        <P>This proposed rule would call for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520.).</P>
        <HD SOURCE="HD1">Federalism</HD>
        <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. We have analyzed this rule under that Order and determined that this rule does not have implications for federalism.</P>
        <HD SOURCE="HD1">Unfunded Mandates Reform Act</HD>
        <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or more in any one year. Though this proposed rule would not result in such an expenditure, we do discuss the effects of this rule elsewhere in this preamble.</P>
        <HD SOURCE="HD1">Taking of Private Property</HD>

        <P>This proposed rule would not cause a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with<PRTPAGE P="15649"/>Constitutionally Protected Property Rights.</P>
        <HD SOURCE="HD1">Civil Justice Reform</HD>
        <P>This proposed rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.</P>
        <HD SOURCE="HD1">Protection of Children</HD>
        <P>We have analyzed this proposed rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and would not create an environmental risk to health or risk to safety that might disproportionately affect children.</P>
        <HD SOURCE="HD1">Indian Tribal Governments</HD>
        <P>This proposed rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it would not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
        <HD SOURCE="HD1">Energy Effects</HD>
        <P>We have analyzed this proposed rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. The Administrator of the Office of Information and Regulatory Affairs has not designated it as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211.</P>
        <HD SOURCE="HD1">Technical Standards</HD>
        <P>The National Technology Transfer and Advancement Act (NTTAA) (15 U.S.C. 272 note) directs agencies to use voluntary consensus standards in their regulatory activities unless the agency provides Congress, through the Office of Management and Budget, with an explanation of why using these standards would be inconsistent with applicable law or otherwise impractical. Voluntary consensus standards are technical standards (e.g., specifications of materials, performance, design, or operation; test methods; sampling procedures; and related management systems practices) that are developed or adopted by voluntary consensus standards bodies.</P>
        <P>This proposed rule does not use technical standards. Therefore, we did not consider the use of voluntary consensus standards.</P>
        <HD SOURCE="HD1">Environment</HD>
        <P>We have analyzed this proposed rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA) (42 U.S.C. 4321-4370f), and have made a preliminary determination that this action is one of a category of actions which do not individually or cumulatively have a significant effect on the human environment. This rule is categorically excluded, under figure 2-1, paragraph (34)(h), of the Instruction. This rule involves implementation of regulations within 33 CFR Part 100 that apply to organized marine events on the navigable waters of the United States that may have potential for negative impact on the safety or other interest of waterway users and shore side activities in the event area. The category of water activities includes but is not limited to sail boat regattas, boat parades, power boat racing, swimming events, crew racing, and sail board racing. We seek any comments or information that may lead to the discovery of a significant environmental impact from this proposed rule.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 33 CFR Part 100</HD>
          <P>Marine safety, Navigation (water), Reporting and recordkeeping requirements, Waterways.</P>
        </LSTSUB>
        
        <P>For the reasons discussed in the preamble, the Coast Guard proposes to amend 33 CFR part 100 as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 100—SAFETY OF LIFE ON NAVIGABLE WATERS</HD>
          <P>1. The authority citation for part 100 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>33 U.S.C. 1233.</P>
          </AUTH>
          
          <P>2. In § 100.501, suspend line No. 38 in the Table to § 100.501.</P>
          <P>3. In § 100.501, add line No.(c.)24 in Table to § 100.501; to read as follows:</P>
          <SECTION>
            <SECTNO>§ 100.501-35T05-0046</SECTNO>
            <SUBJECT>Special Local Regulations; Marine Events in the Fifth Coast Guard District.</SUBJECT>
            <STARS/>
            <P>Table To § 100.501.—All coordinates listed in the Table to § 100.501 reference Datum NAD 1983.</P>
            
            <PRTPAGE P="15650"/>
            <GPOTABLE CDEF="xs25,r50,r50,r50,r100" COLS="5" OPTS="L1,p7,7/8,i1">
              <TTITLE>(c.) Coast Guard Sector Hampton Roads—COTP Zone</TTITLE>
              <BOXHD>
                <CHED H="1">Number</CHED>
                <CHED H="1">Date</CHED>
                <CHED H="1">Event</CHED>
                <CHED H="1">Sponsor</CHED>
                <CHED H="1">Location</CHED>
              </BOXHD>
              <ROW>
                <ENT I="22"/>
                <ENT I="28">*******</ENT>
              </ROW>
              <ROW>
                <ENT I="01">24</ENT>
                <ENT>May 13, 2012</ENT>
                <ENT>Ocean City Maryland Offshore Grand Prix</ENT>
                <ENT>Offshore Performance Assn. Racing, LLC</ENT>
                <ENT>The waters of the Atlantic Ocean commencing at a point on the shoreline at latitude 38°25′42″ N, longitude 075°03′06″ W; thence east southeast to latitude 38°25′30″ N, longitude 075°02′12″ W, thence south southwest parallel to the Ocean City shoreline to latitude 38°19′12″ N, longitude 075°03′48″ W; thence west northwest to the shoreline at latitude 38°19′30″ N, longitude 075°05′00″ W. The waters of the Atlantic Ocean bounded by a line drawn from a position along the shoreline near Ocean City, MD at latitude 38°22′25.2″ N, longitude 075°03′49.4″ W, thence easterly to latitude 38°22′00.4″ N, longitude 075°02′34.8″ W, thence southwesterly to latitude 38°19′35.9″ N, longitude 075°03′35.4″ W, thence westerly to a position near the shoreline at latitude 38°20′05″ N, longitude 075°04′48.4″ W, thence northerly along the shoreline to the point of origin.</ENT>
              </ROW>
            </GPOTABLE>
            <STARS/>
          </SECTION>
          <SIG>
            <DATED>Dated: February 17, 2012.</DATED>
            <NAME>Mark S. Ogle,</NAME>
            <TITLE>Captain, U.S. Coast Guard, Captain of the Port Hampton Roads.</TITLE>
          </SIG>
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6380 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-04-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
        <CFR>38 CFR Part 60</CFR>
        <RIN>RIN 2900-AN79</RIN>
        <SUBJECT>Fisher House and Other Temporary Lodging</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Department of Veterans Affairs.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Department of Veterans Affairs (VA) proposes to amend its regulations concerning Fisher House and other temporary lodging furnished by VA while a veteran is experiencing an episode of care at a VA medical facility. We intend that the proposed rule would update current regulations to better describe the application process for this assistance and clarify the distinctions between Fisher House and other temporary lodging provided by VA. The proposed rule generally reflects current VA policy and practice, and conforms to industry standards and expectations.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be received by VA on or before May 15, 2012.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Written comments may be submitted through<E T="03">http://www.regulations.gov;</E>by mail or hand delivery to the Director, Regulation Policy and Management (02REG), Department of Veterans Affairs, 810 Vermont Ave. NW., Room 1068, Washington, DC 20420; or by fax to (202) 273-9026. Comments should indicate that they are submitted in response to “RIN 2900-AN79, Fisher House and Other Temporary Lodging”. Copies of comments received will be available for public inspection in the Office of Regulation Policy and Management, Room 1063B, between the hours of 8 a.m. and 4:30 p.m., Monday through Friday (except holidays). Please call (202) 461-4902 (this is not a toll-free number) for an appointment. In addition, during the comment period, comments may be viewed online through the Federal Docket Management System at<E T="03">http://www.regulations.gov.</E>
          </P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Deborah Amdur, Chief Consultant, Care Management and Social Work Service (11SW), Veterans Health Administration, Department of Veterans Affairs, 810 Vermont Avenue NW., Washington, DC 20420, (202) 461-6780. (This is not a toll free number).</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Under the provisions of 38 U.S.C. 1708, VA “may furnish [certain] persons * * * with temporary lodging in a Fisher [H]ouse or other appropriate facility in connection with the examination, treatment, or care of a veteran under [chapter 17].” This authority to provide temporary lodging assists VA in providing appropriate treatment and care to veterans. Individuals receiving such treatment or care often respond better when they are accompanied by relatives, close friends, or caregivers. Thus, the provision of temporary lodging can be an important element of the veteran's treatment. VA implemented its authority under section 1708 in current 38 CFR part 60. However, we have determined that the current rules can be improved to better distinguish between Fisher House and other types of temporary lodging, and to describe the application process in greater detail. This proposed rule would provide such clarification, adding details where necessary.</P>
        <HD SOURCE="HD1">Section 60.1Purpose and scope.</HD>
        <P>Proposed § 60.1 would state that part 60 applies to the use of Fisher House and other temporary lodging furnished by VA while a veteran is experiencing an episode of care at a VA health care facility.</P>
        <HD SOURCE="HD1">Section 60.2Definitions.</HD>
        <P>Proposed § 60.2 would set forth definitions applicable to part 60. For the purpose of receiving temporary lodging from VA, current regulations use the terms “eligible persons,” “a member of the family,” people who “provide the equivalent of family support,” and “caregivers,” to refer to individuals permitted to accompany veterans during their episode of care. However, VA Form 10-0408A, the application form for Fisher House or other temporary lodging, uses the term “accompanying individual” to refer to such persons. For consistency of terms and to eliminate any ambiguity as to whether applicants must be related to the veteran, we propose to uniformly use the term “accompanying individual.” We propose to define the term to mean “an individual seeking Fisher House or other temporary lodging, who provides familial support or the equivalent of familial support, to a veteran while the veteran is experiencing an episode of care.” The regulation would specifically explain that the term is “defined broadly to include relatives, close friends, and caregivers.” This proposed definition would therefore provide for a broader class of individuals permitted to accompany veterans during an episode of care.</P>

        <P>Current § 60.2 defines the term “C&amp;P examination.” C&amp;P is the acronym<PRTPAGE P="15651"/>commonly used to refer to VA's compensation and pension programs. We propose to use the term “compensation and pension examinations” instead of using the acronym. However, the proposed definition for “compensation and pension” examinations would be substantively identical to the definition in current § 60.2.</P>
        <P>We also propose to utilize the term “episode of care” in lieu of “VA medical or compensation and pension examinations.” We propose to define an “episode of care” as “a course of outpatient treatment, or a period of hospitalization, during which a veteran receives health care under 38 U.S.C. chapter 17, or 38 U.S.C. 8111 or 8153.” Although this would be a new term in part 60, it is well recognized in the medical community and it is generally accepted, used, and understood by the medical community and by managers working in the Fisher House and other temporary lodging programs. Further, using the term “episode of care” in our regulations would be clearer than repeatedly attempting to describe the types of care for which VA may provide lodging assistance, which is how this concept is set forth in the current regulations.</P>

        <P>For purposes of further clarification regarding the definition of “episode of care,” we propose to provide a non-exclusive list of examples of episodes of care. The first would be “[a]n appointment at a VA health care facility to receive health care or a compensation and pension examination.” This is consistent with our current regulations.<E T="03">See</E>38 CFR 60.1 (explaining that part 60 “sets forth requirements regarding the use of Fisher Houses and other temporary lodging by veterans receiving * * * [compensation and pension] examinations * * *.”);<E T="03">see also</E>38 CFR 60.3(a) (explaining that veterans with an appointment at a VA health care facility for the purpose of receiving health care or a compensation and pension examination are eligible to stay in temporary lodging).</P>
        <P>The second example would be as follows: “Extended outpatient treatment, such as treatment associated with organ transplant, chemotherapy, or radiation.” The use of Fisher House or other temporary lodging for such treatment is addressed in current § 60.7. These examples represent the most common episodes of care associated with applications for lodging, and the examples are consistent with current § 60.3.</P>
        <P>The third example concerns hospitalizations for a critical injury or where death is imminent. In such cases, it can be helpful to the veteran to have friends or family present. The example would also include hospitalization “where a veteran is unable to make medical decisions for him/herself and the accompanying individual is authorized to make such decisions on the veteran's behalf.” In such cases, VA would consider an application for lodging by an accompanying individual who is authorized to make decisions for the veteran. We note that in most cases, such hospitalizations would also be considered hospitalizations for critical injury or illness. The purpose of this last example is to clarify that lodging may be provided for compassionate reasons, as well as logistically, medically, or legally necessary reasons.</P>
        <P>We also propose to define “Fisher House” as “a housing facility that is located at or near a VA health care facility and was constructed by and donated to VA by the Fisher House Foundation (formerly the Zachary and Elizabeth M. Fisher Armed Services Foundation).” This definition would be consistent with the definition of the term in current 38 CFR 60.2. However, we would add that the term includes “a facility that is treated as if it were Fisher House lodging under § 60.3.” We discuss this proposed addition below under proposed § 60.3.</P>
        <P>The definition of “other temporary lodging” would be slightly more detailed than the definition in current § 60.2, but it would not be substantively different. The definition conforms to current usage and practice.</P>
        <P>“VA” would be defined as “the Department of Veterans Affairs.”</P>
        <HD SOURCE="HD1">Section 60.3Other donated temporary lodging.</HD>

        <P>Proposed § 60.3 would establish that “[w]henever VA receives, from a source other than the Fisher House Foundation, an undesignated donation of lodging to be used on a temporary basis, the lodging will be designated as if it were Fisher House lodging or be treated as other temporary lodging based upon the types of lodging available in the area.” Under 38 U.S.C. 8103(a)(2), the Secretary of Veterans Affairs (Secretary) may accept donations of “any facility * * * that the Secretary considers necessary for use as a medical facility.”<E T="03">See also</E>38 U.S.C. 8104(e) (authorizing VA to accept donations of medical facilities). 38 U.S.C. 8101(3) defines a “medical facility” as a facility used for the provision of health-care services and including any necessary associated buildings. We interpret this definition of “medical facility” as including lodging to be used on a temporary basis in connection with VA health care since the provision of temporary lodging can be an important element of a veteran's treatment.</P>
        <P>Under proposed § 60.3, if the Secretary accepts a gift that specifies the terms of lodging to be provided, then the lodging would be used in the manner specified by the grantor of the gift. However, if no terms are specified, the Secretary would designate, based on consideration of the types of lodging available in the area, whether the gift would be treated as “other temporary lodging” or as if it were donated by the Fisher House Foundation. This is consistent with current VA practice.</P>
        <HD SOURCE="HD1">Section 60.10Eligibility criteria for Fisher House or other temporary lodging.</HD>
        <P>Proposed § 60.10 would set forth the eligibility criteria for lodging under part 60. It would include provisions from several current regulations. However, we propose to reorganize the information for clarity.</P>
        <P>Proposed paragraph (a) would establish the general rule that “[w]hile a veteran is undergoing an episode of care, VA may provide either Fisher House or other temporary lodging, as appropriate, if the application meets the requirements of this part 60. These are the only types of lodging provided by VA under this part.” Proposed paragraph (a) is consistent with current § 60.3. We would also add a new note to paragraph (a), which would clarify that “[l]odging provided for under this part will not be used by a person participating in a VA residential treatment program, or as a substitute for participation in such a program.” This note would help ensure that temporary lodging is properly used for its intended purposes, and not as an alternative to proper residential care.</P>
        <P>There are currently active duty servicemembers who receive care at VA facilities under the authority of 38 U.S.C. 8111. Under these circumstances we provide lodging in the same manner that lodging is provided for veterans and their accompanying individuals. Servicemembers would be subject to the same rules as veterans and they would be required to meet the same eligibility requirements concerning episodes of care.</P>

        <P>Proposed paragraph (b) would set forth the general requirements for Fisher House and other temporary lodging. Further, proposed paragraph (b) would clarify the major distinction between Fisher House lodging and other temporary lodging. We have determined that current regulations lack sufficient clarity regarding these two different types of lodging. The primary<PRTPAGE P="15652"/>distinction is that Fisher House lodging is generally limited to accompanying individuals. It is not available for unaccompanied veterans.</P>
        <P>Also, we propose to add a note to paragraph (b) to clarify that “VA does not impose a general limit on the number of persons who may accompany a veteran, but VA may in specific cases provide lodging to only a specific number of persons due to space or resource limitations.” This is consistent with VA's current general practice, which is to allocate lodging on a space-available basis.</P>
        <P>Concerning the differences between Fisher House lodging and other temporary lodging provided by VA, proposed paragraph (b)(1) would clarify that Fisher House lodging is not used to lodge unaccompanied veterans or individuals in need of transitional or permanent housing. This distinction is essential to preserve the intent of the Fisher House Foundation, which is to provide support for families while a veteran experiences an episode of care. Because the purpose of Fisher House lodging is to provide a retreat for accompanying individuals from the medical care environment, Fisher House lodging is available only to accompanying individuals and, in limited circumstances of immediate need and no alternative temporary lodging, to veterans with accompanying individuals.</P>
        <P>Proposed paragraph (b)(2) would discuss other temporary lodging. We would clarify in this paragraph that for an accompanying individual to stay in other temporary lodging, the veteran must also be staying in temporary lodging. We would further specify in a note to this paragraph that VA may, due to space restrictions, impose a limit on the number of accompanying individuals.</P>
        <P>Proposed paragraph (c) would restate the requirement in current § 60.4(h) that the veteran be medically stable and capable of self-care or be accompanied by an individual who is able to provide all necessary care. The proposed rule would clearly state that this requirement applies to both Fisher House lodging and other temporary lodging. The current rule is ambiguous in this regard. The capacity for self-care is required because neither Fisher House lodging nor other temporary lodging is intended to be substitutes for, or supplements to, medical care.</P>
        <P>Proposed § 60.10(d) would restate the existing travel time/distance requirement in current § 60.5, but would clarify that the distance requirement applies to both Fisher House and other temporary lodging. The current rule is ambiguous in this regard. Proposed paragraph (d) would permit the travel time/distance requirement to be applicable to “the applicant,” allowing this requirement to be considered for an accompanying individual as well as for a veteran. This is current VA practice when considering Fisher House applications from non-veterans accompanying veterans. It would also clarify that VA may waive the time/distance requirement under exceptional circumstances that apply to either the accompanying individual or the veteran.</P>
        <P>In proposed paragraph (e) we would prescribe special consideration for organ donors and their accompanying individuals. Specifically, regarding individuals who wish to donate an organ to a veteran, we would explain that “VA may provide Fisher House or other temporary lodging for individuals who must be present on site for evaluation, donation, and care related to their status as an organ donor for a veteran. VA may also provide Fisher House or other temporary lodging for the donor's accompanying individuals at all phases of the transplant process.” This provision is based on clinical need pursuant to 38 U.S.C. 1710(a) regarding eligibility for hospital care and medical services and not on our temporary lodging authority under section 1708. Outcomes of transplantation are linked directly to the presence and competence of accompanying individuals who support the organ donor at all phases of the transplant process. In addition, this paragraph would recognize VA's obligations to living donors who give veterans the gift of life.</P>
        <HD SOURCE="HD1">Section 60.15Application process.</HD>
        <P>Proposed § 60.15 would prescribe the application process for Fisher House or other temporary lodging. Under current § 60.4, applications for lodging may be submitted by mail, telephone, facsimile, in person, or electronically. We intend to continue to provide for the same means of submissions. Proposed § 60.15(a) would simply restate a portion of current § 60.4. Under proposed § 60.15(a), we would refer to VA Form 10-0408A as the application and provide information about where to obtain the form. We would also specify where to submit the completed form. This additional information is intended to assist applicants. We do not intend any changes in the current application process.</P>
        <P>In proposed paragraph (b), which is based upon current § 60.8 and 60.9, we would describe how VA processes applications and makes decisions to grant temporary lodging. However, we propose to add detail for purposes of clarification.</P>
        <P>Paragraph (b)(1) would state that applications “are generally processed in the order that they are received by VA, and temporary lodging is then granted on a first-come, first-served basis; however, in extraordinary circumstances, such as imminent death, critical injury, or organ donation applications may be processed out of order.” The general rule that applications would be processed in the order received would be based upon the last sentence of current § 60.8, which prescribes, “[t]emporary lodging will be provided on a first-come, first-served basis.” However, the proposed exceptions for circumstances involving imminent death, critical injury, or organ donation are new and we propose the exceptions because in these circumstances, we believe that family members and loved ones should be given every opportunity to be with the veteran and, likewise, that the veteran should be accompanied by such people.</P>
        <P>Proposed paragraph (b)(2) would state that “[t]emporary lodging is granted on a space-available basis, with some consideration given to the compatibility of the applicant(s) and the room(s) available.” This general rule would be based upon current § 60.8. The proposed paragraph would provide, by way of example, that “although VA may require an applicant to share a room with another veteran's accompanying individual, VA would not do so if the persons affected are not the same gender.”</P>

        <P>Proposed paragraph (b)(3) would essentially restate the second sentence of current § 60.8. It is important that grants of temporary lodging at a VA health care facility, usually in non-utilized beds, be subject to the approval of the Director of the health care facility in order to avoid any negative impact on patient care. For example, a non-utilized bed that might not be provided to an accompanying individual could include a bed located in an intensive care unit or in an area of the hospital from which visitors are limited or barred. In addition, the proposed rule would add that “[n]on-utilized beds provided to accompanying individuals must be reassigned to VA patients when necessary.” If a patient needs to use a bed that was previously non-utilized and was provided to an accompanying individual, the patient would take priority over the accompanying individual and the bed would no longer be considered “non-utilized.” In such cases, VA would make every effort to relocate the accompanying individual into other temporary lodging.<PRTPAGE P="15653"/>
        </P>
        <P>Proposed paragraph (b)(4) would restate the funding limitation prescribed in current § 60.8, without substantive change.</P>
        <P>Proposed paragraph (b)(5) would state that “[s]ubject to all criteria provided in this part, the person responsible for coordinating the Fisher House and other temporary lodging program(s) at the VA health care facility of jurisdiction is responsible for making decisions to grant temporary lodging. These decisions are considered to be final VA decisions concerning individual medical treatment plans and the scheduling and use of VA lodging facilities, and they are not appealable to the Board of Veterans' Appeals.” This general rule would be based upon current § 60.9, and would reflect current VA policy and practice. The Fisher House program is a unique private-public partnership between The Fisher House Foundation, Inc., and the Secretary of Veterans Affairs to provide temporary lodging for individuals who accompany a veteran during the veteran's hospitalization for an illness, disease, or injury. Fisher Houses are given to the U.S. Government as gifts, and VA subsequently is responsible for the operation and maintenance of Fisher Houses. Lodging in Fisher Houses and other facilities is not a VA benefit, but rather a temporary resource made available to veterans on a first-come first-serve basis, when necessary criteria under the rule are met. Section 1708 gives VA discretion to provide such lodging when appropriate and available, but does not establish a right to such lodging as a VA “benefit.” VA does not guarantee accommodations in VA Fisher Houses or in other temporary lodging facilities, and completion of the application process as described in the rule does not ensure temporary lodging would be provided. VA's determinations in providing such lodging are based in part on medical judgment regarding the course of a veteran's treatment and in part on administrative scheduling matters concerning the availability of space. These types of determinations generally are not subject to appellate review, nor could such review ordinarily be accompanied within the timeframes relevant to administering temporary lodging. Therefore, we do not interpret section 1708 as creating any benefit entitlement within the jurisdiction of the Board of Veterans' Appeals. Rather, lodging decisions made under this proposed rule would be final VA decisions.</P>
        <P>Proposed paragraphs (b)(6) and (7) would reflect current practice not prescribed in current regulations. These paragraphs would explain that when VA cannot grant an application for one type of lodging, we would consider whether the applicant could qualify for the other type of lodging, regardless of any selection on the application. If the application cannot be granted for either type of lodging, we would send the application to a VA social worker to see if other arrangements can be made to assist the applicant.</P>
        <P>Proposed paragraph (c) would restate current § 60.10, without substantive revision.</P>
        <P>As indicated throughout this preamble, VA Form 10-0408A has been designated as the application form for Fisher House and Other Temporary Lodging. Current regulations do not refer specifically to VA Form 10-0408A. However, the form was approved by the Office of Management and Budget (OMB). Therefore, we intend to note in a parenthetical at the end of proposed § 60.15 that OMB has approved the collection of information under control number 2900-0630.</P>
        <HD SOURCE="HD1">Section 60.20Duration of Fisher House or other temporary lodging.</HD>
        <P>Proposed § 60.20 would be the final section in part 60 and it would concern the duration of lodging provided by VA under part 60. Substantively, proposed paragraphs (a) and (b) would be similar to current § 60.7, except that the proposed rule would use the term “episode of care” rather than describe specific types of medical treatment.</P>
        <P>Proposed § 60.20(c) would permit an extension of a previous period of lodging. The duration of a period of lodging would be specific to each situation set forth on the application and, therefore, would generally be defined by the terms of the granted application. However, in certain cases we might need to provide exceptions, such as when a medical emergency occurs during a scheduled episode of care or when weather changes prevent departure from the lodging provided by VA.</P>
        <P>Proposed paragraph (d) would authorize an indefinite period of lodging for individuals accompanying a veteran who is hospitalized for an indefinite period based on the treatment or rehabilitation needs of the veteran as determined by the veteran's health care team and based on the availability of Fisher House lodging or of funding for other temporary lodging. Lodging in non-utilized VA hospital beds would not be authorized for an indefinite period due to the administrative and medical needs of VA medical facilities.</P>
        <P>Proposed paragraphs (e) and (f) would be consistent with current § 60.7. These paragraphs would restrict awards of temporary lodging to veterans who are unable to arrive for a scheduled appointment at the health care facility if they left their home after 8 a.m. or who would be unable to return home before 7 p.m. We believe that travel before 8 a.m. or after 7 p.m. may be more difficult or dangerous than travel during regular daylight hours.</P>
        <HD SOURCE="HD1">Effect of Rulemaking</HD>
        <P>Title 38 of the Code of Federal Regulations, as proposed to be revised by this proposed rulemaking, would represent VA's implementation of its exclusive legal authority on this subject. Other than future amendments to this regulation or governing statutes, no contrary rules or procedures would be authorized. All existing and subsequent VA guidance would be read to conform with this proposed rulemaking if possible or, if not possible, such guidance would be superseded by this rulemaking.</P>
        <HD SOURCE="HD1">Paperwork Reduction Act</HD>
        <P>Although this document contains provisions constituting collections of information under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501-3521), no new or proposed revised collections of information are associated with this proposed rule. The information collection provisions for this section are approved by OMB and have been assigned OMB control number 2900-0630.</P>
        <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
        <P>The Secretary hereby certifies that this proposed rule would not have a significant economic impact on a substantial number of small entities as they are defined in the Regulatory Flexibility Act, 5 U.S.C. 601-612. This proposed rule would not cause a significant economic impact on health care providers, suppliers, or entities because the proposed rule would apply only to patients receiving care at VA facilities. Also, this proposed rule might have an insignificant impact on small entities involved in the lodging industry. However, any effect would be minuscule. Therefore, under 5 U.S.C. 605(b), this proposed rule is exempt from the initial and final regulatory flexibility analyses requirements of 5 U.S.C. 603 and 604.</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<PRTPAGE P="15654"/>(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) classifies a “significant regulatory action,” requiring review by OMB, unless OMB waives such review as “any regulatory action that is likely to result in a rule that may: (1) Have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy, a sector of the economy, productivity, competition, jobs, the environment, public health or safety, or State, local, or tribal governments or communities; (2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another agency; (3) Materially alter the budgetary impact of entitlements, grants, user fees, or loan programs or the rights and obligations of recipients thereof; or (4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in this Executive Order.”</P>
        <P>The economic, interagency, budgetary, legal, and policy implications of this proposed rule have been examined and it has been determined not 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 the 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 year. This proposed rule would have no such effect on State, local, and tribal governments, or on the private sector.</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.014, Veterans State Domiciliary Care; 64.015, Veterans State Nursing Home 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 March 8, 2012, for publication.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 38 CFR Part 60</HD>
          <P>Health care, Health facilities, Health records, Reporting and recordkeeping requirements, Housing, Travel, Veterans.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: March 13, 2012.</DATED>
          <NAME>Robert C. McFetridge,</NAME>
          <TITLE>Director of Regulation Policy and Management, Office of the General Counsel, Department of Veterans Affairs.</TITLE>
          
        </SIG>
        <P>For the reasons stated in the preamble, VA proposes to amend 38 CFR part 60 as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 60—FISHER HOUSES AND OTHER TEMPORARY LODGING</HD>
          <P>1. The authority citation for part 60 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>38 U.S.C. 501, 1708.</P>
          </AUTH>
          
          <P>2. Part 60 is revised to read as follows:</P>
          
          <CONTENTS>
            <SECHD>Sec.</SECHD>
            <SECTNO>60.1</SECTNO>
            <SUBJECT>Purpose and scope.</SUBJECT>
            <SECTNO>60.2</SECTNO>
            <SUBJECT>Definitions.</SUBJECT>
            <SECTNO>60.3</SECTNO>
            <SUBJECT>Other donated temporary lodging.</SUBJECT>
            <SECTNO>60.10</SECTNO>
            <SUBJECT>Eligibility criteria for Fisher House or other temporary lodging.</SUBJECT>
            <SECTNO>60.15</SECTNO>
            <SUBJECT>Application process.</SUBJECT>
            <SECTNO>60.20</SECTNO>
            <SUBJECT>Duration of Fisher House or other temporary lodging.</SUBJECT>
          </CONTENTS>
          <SECTION>
            <SECTNO>§ 60.1</SECTNO>
            <SUBJECT>Purpose and scope.</SUBJECT>
            <P>This part applies to Fisher House and other temporary lodging furnished by VA while a veteran is experiencing an episode of care at a VA health care facility.</P>
            <SECAUTH>(Authority: 38 U.S.C. 501, 1708).</SECAUTH>
          </SECTION>
          <SECTION>
            <SECTNO>§ 60.2</SECTNO>
            <SUBJECT>Definitions.</SUBJECT>
            <P>For the purposes of this part:</P>
            <P>
              <E T="03">Accompanying individual</E>means an individual seeking Fisher House or other temporary lodging, who provides familial support or the equivalent of familial support, to a veteran while the veteran is experiencing an episode of care. This term is defined broadly to include relatives, close friends, and caregivers.</P>
            <P>
              <E T="03">Compensation and pension examination</E>means an examination requested by VA's Veterans Benefits Administration to be conducted at a VA health care facility for the purpose of evaluating a veteran's claim.</P>
            <P>
              <E T="03">Episode of care</E>means a course of outpatient treatment, or a period of hospitalization, during which a veteran receives health care under 38 U.S.C. chapter 17, or 38 U.S.C. 8111 or 8153. Examples of episodes of care include (but are not limited to) the following:</P>
            <P>(1) An appointment at a VA health care facility to receive health care or a compensation and pension examination.</P>
            <P>(2) Extended outpatient treatment, such as treatment associated with organ transplant, chemotherapy, or radiation.</P>
            <P>(3) Hospitalization for a critical injury or illness; where death is imminent; or where a veteran is unable to make medical decisions for him/herself and the accompanying individual is authorized to make such decisions on the veteran's behalf.</P>
            <P>
              <E T="03">Fisher House</E>means a housing facility that is located at or near a VA health care facility and was constructed by and donated to VA by the Fisher House Foundation (formerly the Zachary and Elizabeth M. Fisher Armed Services Foundation), or a facility that is treated as if it were Fisher House lodging under § 60.3.</P>
            <P>
              <E T="03">Other temporary lodging</E>includes:</P>
            <P>(1) Lodging at a temporary lodging facility, other than a Fisher House, located at a VA health care facility (generally referred to as a “hoptel”);</P>
            <P>(2) A hotel or motel;</P>
            <P>(3) Non-utilized beds at a VA health care facility designated as lodging beds; and</P>
            <P>(4) Other donated lodging to be used on a temporary basis in accordance with 38 U.S.C. 1708.</P>
            <P>
              <E T="03">VA</E>means the Department of Veterans Affairs.</P>
            <SECAUTH>(Authority: 38 U.S.C. 501, 1708)</SECAUTH>
          </SECTION>
          <SECTION>
            <SECTNO>§ 60.3</SECTNO>
            <SUBJECT>Other donated temporary lodging.</SUBJECT>
            <P>Whenever VA receives, from a source other than the Fisher House Foundation, an undesignated donation of lodging to be used on a temporary basis, the lodging will be designated as if it were Fisher House lodging or be treated as other temporary lodging based upon the types of lodging available in the area. If VA receives a gift that specifies the terms of the lodging provided, VA will use the lodging provided in the manner specified by the donor.</P>
            <SECAUTH>(Authority: 38 U.S.C. 501, 1708, 8103, 8104)</SECAUTH>
          </SECTION>
          <SECTION>
            <PRTPAGE P="15655"/>
            <SECTNO>§ 60.10</SECTNO>
            <SUBJECT>Eligibility criteria for Fisher House or other temporary lodging.</SUBJECT>
            <P>(a)<E T="03">General.</E>While a veteran is undergoing an episode of care, VA may provide either Fisher House or other temporary lodging, as appropriate, if the application meets the requirements of this part 60. These are the only types of lodging provided by VA under this part.<E T="04">Note:</E>Lodging provided for under this part will not be used by a person participating in a VA residential treatment program, or as a substitute for participation in such a program.</P>
            <P>(b)<E T="03">Eligible persons.</E>(1)<E T="03">Fisher House.</E>VA may provide Fisher House lodging to accompanying individual(s) and, in limited circumstances of immediate need and no alternative temporary lodging, to a veteran with one or more accompanying individual(s). Fisher House lodging will not be used to lodge unaccompanied veterans or individuals in need of transitional or permanent housing.<E T="04">Note:</E>VA does not impose a general limit on the number of persons who may accompany a veteran, but VA may in specific cases provide lodging to only a specific number of persons due to space or resource limitations.</P>
            <P>(2)<E T="03">Other temporary lodging.</E>VA may provide other temporary lodging to a veteran or to a veteran and his or her accompanying individual(s). Accompanying individuals may not stay in other temporary lodging unless the veteran is also staying in temporary lodging.<E T="04">Note:</E>VA does not impose a general limit on the number of persons who may accompany a veteran, but VA may in specific cases provide lodging to only a specific number of persons due to space or resource limitations.</P>
            <P>(c)<E T="03">Condition of the veteran.</E>Fisher House or other temporary lodging will not be provided to a veteran unless the VA official reviewing the application determines, based on the application and on any necessary clinical information, that the veteran is:</P>
            <P>(1) Medically stable and capable of self-care; or</P>
            <P>(2) Accompanied by an individual who is able to provide all necessary care.</P>
            <P>(d)<E T="03">Travel time/distance requirement.</E>Fisher House or other temporary lodging may be provided only if the applicant seeking lodging must travel at least 50 miles, or for 2 hours, from his or her home to the VA health care facility. VA may waive these requirements based on exceptional circumstances, such as when the physical condition of an accompanying individual and/or the veteran, inclement weather, road conditions, or the mode of transportation, make it difficult or dangerous to travel to or return from the VA health care facility without an overnight stay.</P>
            <P>(e)<E T="03">Special authority for organ transplant cases.</E>Notwithstanding any other provision of this part, VA may provide Fisher House or other temporary lodging for individuals who must be present on site for evaluation, donation, and care related to their status as an organ donor for a veteran. VA may also provide Fisher House or other temporary lodging for the donor's accompanying individuals at all phases of the transplant process.</P>
            <SECAUTH>(Authority: 38 U.S.C. 501, 1708, 1710(a))</SECAUTH>
          </SECTION>
          <SECTION>
            <SECTNO>§ 60.15</SECTNO>
            <SUBJECT>Application process.</SUBJECT>
            <P>(a)<E T="03">Obtaining and submitting the application.</E>VA Form 10-0408A is the application for Fisher House and other temporary lodging. Applications may be submitted by mail, telephone, facsimile, in person, or electronically. VA Form 10-0408A is available from any VA medical center or may be obtained online at<E T="03">http://vaww4.va.gov/vaforms/medical/pdf/vha-10-0408A-fill.pdf.</E>The completed application must be submitted as follows:</P>
            <P>(1) For Fisher House lodging, to the Fisher House Manager at the VA medical center of jurisdiction.</P>
            <P>(2) For other temporary lodging, to the temporary lodging program coordinator at the VA medical center of jurisdiction.</P>
            <P>(b)<E T="03">Processing applications.</E>(1) Applications are generally processed in the order that they are received by VA, and temporary lodging is then granted on a first come first serve basis; however, in extraordinary circumstances, such as imminent death, critical injury, or organ donation applications may be processed out of order.</P>
            <P>(2) Temporary lodging is granted on a space-available basis, with some consideration given to the compatibility of the applicant(s) and the room(s) available. For example, although VA may require an applicant to share a room with another veteran's accompanying individual, VA would not do so if the persons affected are not the same gender.</P>
            <P>(3) Temporary lodging at a VA health care facility, such as non-utilized beds in a VA medical facility, may be made available only if not barred by law and if the Director of the medical facility determines that such action would not have a negative impact on patient care. Non-utilized beds provided to accompanying individuals must be reassigned to VA patients when necessary.</P>
            <P>(4) The Director of the VA Medical Center of jurisdiction will determine whether local funding is sufficient to allow the use of temporary lodging in hotels and motels.</P>
            <P>(5) Subject to all criteria provided in this part, the person responsible for coordinating the Fisher House and other temporary lodging program(s) at the VA health care facility of jurisdiction is responsible for making decisions to grant temporary lodging. These decisions are considered to be final VA decisions concerning individual medical treatment plans and the scheduling and use of VA lodging facilities, and they are not appealable to the Board of Veterans' Appeals.</P>
            <P>(6) If VA denies an application for one type of lodging, such as at a Fisher House, the application will be considered for other temporary lodging and vice versa, if the applicant is eligible.</P>
            <P>(7) If VA denies the application for all types of temporary lodging, VA will refer the application to a VA social worker at the VA medical center of jurisdiction to determine if other arrangements can be made.</P>
            <P>(c) Costs for Fisher House and other temporary lodging under this part are borne by VA.</P>
            <SECAUTH>(Authority: 38 U.S.C. 501, 1708)</SECAUTH>
            
            <FP>(The Office of Management and Budget has approved the information collection requirements in this section under OMB control number 2900-0630)</FP>
          </SECTION>
          <SECTION>
            <SECTNO>§ 60.20</SECTNO>
            <SUBJECT>Duration of Fisher House or other temporary lodging.</SUBJECT>
            <P>Fisher House or other temporary lodging may be awarded for the following periods:</P>
            <P>(a) While the veteran is undergoing an episode of care.</P>
            <P>(b) While the veteran is hospitalized, if the veteran is admitted to a VA medical facility while undergoing an outpatient episode of care for which temporary lodging was already provided.</P>
            <P>(c) As extended by the appropriate VA clinician or social worker based on an emergency situation or unforeseen circumstances.</P>
            <P>(d) For an indefinite period for accompanying individuals who are visiting veterans hospitalized for an indefinite period, provided that the accompanying individual is not using a VA medical facility bed. Whether a veteran is hospitalized for an indefinite period will be based upon the treatment or rehabilitation needs of the veteran as determined by the veteran's health care team.</P>

            <P>(e) Temporary lodging may be furnished the night before the day of a scheduled appointment if, the veteran leaving home after 8 a.m., would be<PRTPAGE P="15656"/>unable to arrive at the health care facility by the time of the scheduled appointment.</P>
            <P>(f) Temporary lodging may be furnished the night of the scheduled appointment if, after the appointment, the veteran would be unable to return home before 7 p.m. When a veteran is undergoing outpatient treatment or procedures the veteran and accompanying individual(s) may be furnished temporary lodging for the duration of the episode of care subject to limitations described in this section.</P>
            <SECAUTH>(Authority: 38 U.S.C. 501, 1708)</SECAUTH>
            
          </SECTION>
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6397 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 8320-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <CFR>40 CFR Parts 51 and 52</CFR>
        <DEPDOC>[EPA-HQ-OAR-2003-0062; FRL-9648-1]</DEPDOC>
        <RIN>RIN 2060-AR30</RIN>

        <SUBJECT>Implementation of the New Source Review (NSR) Program for Particulate Matter Less Than 2.5 Micrometers (PM<E T="52">2.5</E>): Amendment to the Definition “Regulated NSR Pollutant” Concerning Condensable Particulate Matter</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The EPA is proposing to revise the definition “regulated NSR pollutant” contained in two sets of Prevention of Significant Deterioration (PSD) regulations and in the EPA's Emission Offset Interpretative Ruling. This revision would correct an inadvertent error made in 2008 when the EPA issued its final rule to implement the new source review (NSR) program for fine particles with an aerodynamic diameter of less than or equal to 2.5 micrometers (PM<E T="52">2.5</E>). Effectively, this revision would reestablish the interpretation that for measurement of “particulate matter emissions” in the context of the PSD and NSR regulations there is no explicit requirement to include measurement of condensable PM. However, the condensable portion would continue to be required for emissions of particles with an aerodynamic diameter of less than or equal to 10 micrometers (PM<E T="52">10</E>) and PM<E T="52">2.5</E>.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be received on or before May 15, 2012.</P>
          <P>
            <E T="03">Public Hearing.</E>If anyone contacts the EPA requesting the opportunity to speak at a public hearing concerning the proposed regulation by March 26, 2012, the EPA will hold a public hearing approximately 30 days after publication in the<E T="04">Federal Register</E>. Additional information about the hearing would be published in a subsequent<E T="04">Federal Register</E>notice.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Submit your comments, identified by Docket ID No. EPA-HQ-OAR-2003-0062, by one of the following methods:</P>
          <P>•<E T="03">http://www.regulations.gov.</E>Follow the online instructions for submitting comments.</P>
          <P>•<E T="03">Email: a-and-r-docket@epa.gov.</E>
          </P>
          <P>•<E T="03">Mail:</E>Air and Radiation Docket, Environmental Protection Agency, Mail code 6102T, 1200 Pennsylvania Avenue NW., Washington, DC 20460. Please include a total of two copies.</P>
          <P>•<E T="03">Hand Delivery:</E>EPA Docket Center, Public Reading Room, EPA West, Room 3334, 1301 Constitution Ave. NW., Washington, DC 20460. Such deliveries are only accepted during the Docket's normal hours of operation, and special arrangements should be made for deliveries of boxed information.</P>
          <P>
            <E T="03">Instructions:</E>Direct your comments to the applicable docket. The EPA's policy is that all comments received will be included in the public docket without change and may be made available online at<E T="03">http://www.regulations.gov,</E>including any personal information provided, unless the comment includes information claimed to be confidential business information (CBI) or other information whose disclosure is restricted by statute. Do not submit information that you consider to be CBI or otherwise protected through<E T="03">www.regulations.gov</E>or email. The<E T="03">www.regulations.gov</E>Web site is an “anonymous access” system, which means the EPA will not know your identity or contact information unless you provide it in the body of your comment. If you send an email comment directly to the EPA without going through<E T="03">www.regulations.gov,</E>your email address will be automatically captured and included as part of the comment that is placed in the public docket and made available on the Internet. If you submit an electronic comment, the EPA recommends that you include your name and other contact information in the body of your comment and with any disk or CD-ROM you submit. If the EPA cannot read your comment due to technical difficulties and cannot contact you for clarification, the EPA may not be able to consider your comment. Electronic files should avoid the use of special characters, any form of encryption, and be free of any defects or viruses.</P>
          <P>
            <E T="03">Docket:</E>All documents in the docket are listed in the<E T="03">www.regulations.gov</E>index. Although listed in the index, some information is not publicly available, e.g., CBI or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, 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">www.regulations.gov</E>or in hard copy at the EPA Docket Center, Public Reading Room, EPA West, Room 3334, 1301 Constitution Ave. NW., Washington, DC 20460. The Public Reading Room is open from 8:30 a.m. to 4:30 p.m., Monday through Friday, excluding legal holidays. The telephone number for the Public Reading Room is (202) 566-1742, and the telephone number for the Air Docket is (202) 566-1744.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Mr. Dan deRoeck, Air Quality Policy Division (C504-03), U.S. Environmental Protection Agency, Research Triangle Park, NC, 27711; telephone number (919) 541-5593; fax number (919) 541-5509; or email address:<E T="03">deroeck.dan@epa.gov.</E>
          </P>

          <P>To request a public hearing or information pertaining to a public hearing on this document, contact Ms. Pamela Long, Air Quality Policy Division, Office of Air Quality Planning and Standards (C504-03), Environmental Protection Agency, Research Triangle Park, North Carolina 27711; telephone number (919) 541-0641; fax number (919) 541-5509; email address:<E T="03">long.pam@epa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. General Information</HD>
        <HD SOURCE="HD2">A. Does this action apply to me?</HD>
        <P>Entities affected by this rule include sources in all industry groups. The majority of sources potentially affected are expected to be in the following groups that emit particulate matter:</P>
        <GPOTABLE CDEF="s100,r100" COLS="2" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Industry group</CHED>
            <CHED H="1">NAICS<SU>a</SU>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Electric services</ENT>
            <ENT>221111, 221112, 221113, 221119, 221121, 221122</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Petroleum refining</ENT>
            <ENT>32411</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="15657"/>
            <ENT I="01">Industrial inorganic chemicals</ENT>
            <ENT>325181, 32512, 325131, 325182, 211112, 325998, 331311, 325188</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Industrial organic chemicals</ENT>
            <ENT>32511, 325132, 325192, 325188, 325193, 32512, 325199</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Miscellaneous chemical products</ENT>
            <ENT>32552, 32592, 32591, 325182, 32551</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Natural gas liquids</ENT>
            <ENT>211112</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Natural gas transport</ENT>
            <ENT>48621, 22121</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Pulp and paper mills</ENT>
            <ENT>32211, 322121, 322122, 32213</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Paper mills</ENT>
            <ENT>322121, 322122</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Automobile manufacturing</ENT>
            <ENT>336111, 336112, 336712, 336211, 336992, 336322, 336312, 33633, 33634, 33635, 336399, 336212, 336213</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Pharmaceuticals</ENT>
            <ENT>325411, 325412, 325413, 325414</ENT>
          </ROW>
          <TNOTE>
            <SU>a</SU>North American Industry Classification System.</TNOTE>
        </GPOTABLE>
        <P>Entities affected by this rule also include state, local, and tribal reviewing authorities responsible for implementing Clean Air Act (CAA or Act) stationary source permitting programs.</P>
        <HD SOURCE="HD2">B. What should I consider as I prepare my comments for EPA?</HD>
        <P>1.<E T="03">Submitting CBI.</E>Do not submit information containing CBI to the EPA through<E T="03">www.regulations.gov</E>or email. Send or deliver information identified as CBI only to the following address: Mr. Roberto Morales, OAQPS Document Control Officer (C404-02), U.S. EPA, Office of Air Quality Planning and Standards, Research Triangle Park, North Carolina 27711, Attention: Docket ID EPA-HQ-OAR-2003-0062. Clearly mark the part or all of the information that you claim to be CBI. For CBI information in a disk or CD-ROM that you mail to the EPA, mark the outside of the disk or CD-ROM as CBI and then identify electronically within the disk or CD-ROM the specific information that is claimed as CBI. In addition to one complete version of the comment that includes information claimed as CBI, a copy of the comment that does not contain the information claimed as CBI must be submitted for inclusion in the public docket. Information so marked will not be disclosed except in accordance with procedures set forth in 40 CFR part 2.</P>
        <P>2.<E T="03">Tips for Preparing Your Comments.</E>When submitting your comments, remember to:</P>

        <P>• Identify the rulemaking by docket number and other identifying information (subject heading,<E T="04">Federal Register</E>date and page number).</P>
        <P>• Follow directions—The Agency may ask you to respond to specific questions or organize comments by referencing a Code of Federal Regulations (CFR) part or section number.</P>
        <P>• Explain why you agree or disagree, suggest alternatives, and substitute language for your requested changes.</P>
        <P>• If you estimate potential costs or burdens, explain how you arrived at your estimate in sufficient detail to allow for it to be reproduced.</P>
        <P>• Provide specific examples to illustrate your concerns, and suggest alternatives.</P>
        <P>• Explain your views as clearly as possible, avoiding the use of profanity or personal threats.</P>
        <P>• Make sure to submit your comments by the comment period deadline identified.</P>
        <HD SOURCE="HD2">C. Where can I get a copy of this document and other related information?</HD>

        <P>In addition to being available in the docket, an electronic copy of this proposed rule will also be available on the World Wide Web. Following signature by the EPA Administrator, a copy of this proposed rule will be posted in the regulations and standards section of our NSR home page located at<E T="03">http://www.epa.gov/nsr.</E>
        </P>
        <HD SOURCE="HD2">D. How can I find information about a possible public hearing?</HD>

        <P>To request a public hearing or information pertaining to a public hearing on this document, contact Ms. Pamela Long, Air Quality Policy Division, Office of Air Quality Planning and Standards (C504-03), Environmental Protection Agency, Research Triangle Park, North Carolina 27711; telephone number (919) 541-0641; fax number (919) 541-5509; email address:<E T="03">long.pam@epa.gov.</E>
        </P>
        <HD SOURCE="HD2">E. How is this preamble organized?</HD>
        <P>The information in this Supplementary Information section of this preamble is organized as follows:</P>
        <EXTRACT>
          
          <FP SOURCE="FP-2">I. General Information</FP>
          <FP SOURCE="FP1-2">A. Does this action apply to me?</FP>
          <FP SOURCE="FP1-2">B. What should I consider as I prepare my comments for EPA?</FP>
          <FP SOURCE="FP1-2">C. Where can I get a copy of this document and other related information?</FP>
          <FP SOURCE="FP1-2">D. How can I find information about a possible public hearing?</FP>
          <FP SOURCE="FP1-2">E. How is this preamble organized?</FP>
          <FP SOURCE="FP-2">II. Purpose</FP>
          <FP SOURCE="FP-2">III. Background</FP>
          <FP SOURCE="FP1-2">A. National Ambient Air Quality Standards (NAAQS) for Particulate Matter (PM)</FP>
          <FP SOURCE="FP1-2">B. Measuring and Reporting Emissions of Pariculate Matter (PM)</FP>
          <FP SOURCE="FP1-2">C. New Source Review Program for PM</FP>
          <FP SOURCE="FP-2">IV. Why is the EPA proposing to change the definition “Regulated NSR pollutant” with regard to PM?</FP>
          <FP SOURCE="FP-2">V. Statutory and Executive Order Reviews</FP>
          <FP SOURCE="FP1-2">A. Executive Order 12866: Regulatory Planning and Review and Executive Order 13563: Improving Regulation and Regulatory Review</FP>
          <FP SOURCE="FP1-2">B. Paperwork Reduction Act</FP>
          <FP SOURCE="FP1-2">C. Regulatory Flexibility Act</FP>
          <FP SOURCE="FP1-2">D. Unfunded Mandates Reform Act</FP>
          <FP SOURCE="FP1-2">E. Executive Order 13132—Federalism</FP>
          <FP SOURCE="FP1-2">F. Executive Order 13175—Consultation and Coordination With Indian Tribal Governments</FP>
          <FP SOURCE="FP1-2">G. Executive Order 13045—Protection of Children From Environmental Health and Safety Risks</FP>
          <FP SOURCE="FP1-2">H. Executive Order 13211—Actions That Significantly Affect Energy Supply, Distribution, or Use</FP>
          <FP SOURCE="FP1-2">I. National Technology Transfer and Advancement Act</FP>
          <FP SOURCE="FP1-2">J. Executive Order 12898—Federal Actions To Address Environmental Justice in Minority Populations and Low-Income Populations</FP>
          <FP SOURCE="FP-2">VI. Statutory Authority</FP>
        </EXTRACT>
        
        <HD SOURCE="HD1">II. Purpose</HD>

        <P>The purpose of this rulemaking is to revise the definition “regulated NSR pollutant” contained in the regulations for PSD at 40 CFR 51.166 and 52.21, and in the EPA's Emission Offset Interpretative Ruling at 40 CFR part 51 Appendix S. This revision will correct an error that occurred when the regulations were revised in 2008. The existing definition was changed in 2008 to require that particulate matter emissions, PM<E T="52">10</E>emissions and PM<E T="52">2.5</E>emissions—representing three separate size ranges or indicators of particles—must include “gaseous emissions from a source or activity which condense to form particulate matter at ambient temperatures,” i.e., condensable particulate matter.<E T="03">See</E>existing 40 CFR 51.166 (b)(49)(vi) and 52.21(b)(50)(vi). Previously, EPA's regulations did not require particulate matter emissions to include condensable particulate matter; consistent with the applicable New<PRTPAGE P="15658"/>Source Performance Standards (NSPS) for PM and the corresponding compliance test method, only the filterable fraction had been considered for NSR purposes. The 2008 change therefore imposed an unintended new requirement on state and local agencies and the regulated community. As described in more detail in section IV of this preamble, in the 2008 final rule we did not intend that the term “particulate matter emissions” include the condensable PM fraction of primary PM; the EPA no longer regulates the ambient indicator, total suspended particulate (TSP), with which the indicator “particulate matter emissions” was originally associated, and there is no compelling reason for requiring that the condensable PM portion be counted toward the measure of “particulate matter emissions” from stationary sources for PSD applicability determinations and in establishing emissions limitations.</P>

        <P>If these proposed revisions are finalized, they will ensure that our approach for regulating the three indicators for particulate matter under the PSD program is codified as originally intended. This would mean that “PM<E T="52">10</E>emissions” and “PM<E T="52">2.5</E>emissions” would be regulated as criteria pollutants (that is, under the portion of the definition that refers to “[a]ny pollutant for which a national ambient air quality standard has been promulgated * * *”), and would be required to include the condensable PM fraction emitted by a source. Also, “particulate matter emissions” would be regulated as a non-criteria pollutant (that is, under the portion of the definition that refers to “[a]ny pollutant that is subject to any standard promulgated under section 111 of the Act”), without a general requirement to include the condensable PM fraction emitted by a source.</P>
        <HD SOURCE="HD1">III. Background</HD>
        <HD SOURCE="HD2">A. National Ambient Air Quality Standards (NAAQS) for Particulate Matter (PM)</HD>
        <P>Sections 108 and 109 of the CAA govern the establishment and revision of the NAAQS. Section 108 directs the Administrator to identify and list “air pollutants” that “in his judgment, may reasonably be anticipated to endanger public health and welfare” and whose “presence * * * in the ambient air results from numerous or diverse mobile or stationary sources” and to issue air quality criteria for those pollutants that are listed. Section 109 directs the Administrator to propose and promulgate primary and secondary NAAQS for pollutants listed under section 108 to protect public health and welfare, respectively. Section 109 also requires review of the NAAQS at 5-year intervals.</P>

        <P>“Particulate matter” is a term used to define an air pollutant that consists of a mixture of solid particles and liquid droplets found in the ambient air. Particulate matter occurs in many sizes and shapes and can be made up of hundreds of different chemicals. As explained further in the discussion that follows, the EPA has regulated several size ranges of particles, e.g., PM<E T="52">2.5</E>, referred to as indicators of particles<SU>1</SU>
          <FTREF/>, which has required that test methods be developed to capture the appropriate size particles that occur in the ambient air or that are being emitted directly from a source. In some cases, the EPA regulates certain species of particles as separate “air pollutants.” For example, lead, beryllium, fluorides, and sulfuric acid mist are constituents of particulate matter that are also regulated separately under New Source Performance Standards (40 CFR part 60) or National Emissions Standards for Hazardous Air Pollutants (40 CFR parts 61, 63 or 65).</P>
        <FTNT>
          <P>
            <SU>1</SU>The “indicator” of a standard defines the chemical species or mixture that is to be measured in determining whether an area (in the case of an ambient standard) or a source (in the case of an in-stack standard) attains that standard.</P>
        </FTNT>

        <P>Particles as measured in the ambient air consist of both primary and secondary particles. Primary particles are emitted directly from sources, and may include gaseous emissions, which, when emitted from the stack of a source, condense under ambient conditions to form particles. Primary particles directly emitted by a source as a solid or liquid at the stack and captured on the filter of a test train are referred to as the “filterable” PM fraction. The gaseous emissions that form particles upon condensing under ambient conditions following release from the stack are referred to as “condensable” PM. Other types of particles, known as secondary particles, are formed from precursors of PM, e.g., SO<E T="52">2</E>and NO<E T="52">X</E>, at a distance from their point of release as a result of complex reactions in the atmosphere.</P>

        <P>Initially, the EPA established NAAQS for PM on April 30, 1971, under sections 108 and 109 of the Act.<E T="03">See</E>36 FR 8186. Compliance with the original PM NAAQS was based on the measurement of particles in the ambient air using an indicator of particles measuring up to a nominal size of 25 to 45 micrometers (μm) in the ambient air. The EPA used the indicator name “total suspended particulate” or “TSP” to define the particle size range that was being measured. Total suspended particulate remained the indicator for the PM NAAQS until 1987 when the EPA revised the NAAQS in part by replacing the TSP indicator for both the primary and secondary standards with a new indicator that includes only those particles with an aerodynamic diameter smaller than or equal to a nominal 10 μm (PM<E T="52">10</E>).</P>

        <P>On July 18, 1997, the EPA made significant revisions to the PM NAAQS in several respects. While the EPA determined that the PM NAAQS should continue to focus on particles less than or equal to 10 µm in diameter, the EPA also determined that the fine and coarse fractions of PM<E T="52">10</E>should be considered separately. Accordingly, on July 18, 1997, the EPA added a new indicator for fine particles with a nominal mean aerodynamic diameter less than or equal to 2.5 μm (PM<E T="52">2.5</E>), and continued to use PM<E T="52">10</E>as the indicator for purposes of regulating the coarse fraction of PM<E T="52">10</E>.<E T="03">See</E>62 FR 38652.</P>

        <P>In the next periodic review, the EPA concluded, on October 17, 2006, that it was necessary to revise the primary and secondary NAAQS for PM to provide increased protection of public health and welfare.<E T="03">See</E>71FR 61144. The EPA retained the two separate indicators—PM<E T="52">10</E>and PM<E T="52">2.5</E>—for determining compliance with the revised standards for PM, so both continue to be regarded as criteria pollutants.</P>
        <HD SOURCE="HD2">B. Measuring and Reporting Emissions of Particulate Matter (PM)</HD>
        <P>Section 110 of the Act requires that state and local air pollution control agencies develop and submit plans, known as state implementation plans or SIPs, for the EPA approval that provide for the attainment, maintenance and enforcement of the NAAQS. An essential component of each SIP is the emissions reduction strategy, including emissions limitations and other control measures (as set forth in SIPs and in individual source permits) designed to control the emissions of pollutants that contribute to the air quality against which the NAAQS are measured. For many years, most control measures for PM were generally focused on primary PM—specifically, the filterable PM fraction. Accordingly, the early EPA test methods for quantifying amounts of PM emitted by sources generally were based on the collection of the filterable PM fraction.</P>

        <P>In support of state obligations to develop emissions reduction strategies, section 111 of the Act requires the EPA to adopt technology-based standards of performance that focus on sources that cause or contribute significantly to “air pollution which may reasonably be<PRTPAGE P="15659"/>anticipated to endanger public health and welfare.” Such standards, referred to as NSPS, are emissions standards that are intended to reflect the degree of air pollution emission limitation attainable through the application of the best system of emission reduction (taking into account the cost of achieving such reduction and any non-air quality health and energy requirements) that the Administrator determines has been adequately demonstrated. Accordingly, the EPA historically has developed NSPS (and corresponding compliance test methods) under 40 CFR part 60 to provide emissions standards that address, among other pollutants, the control of PM.</P>
        <P>When the EPA promulgated the first set of NSPS for PM in 1971, only the filterable PM fraction was regulated. The EPA simultaneously promulgated a test method, known as Method 5, as the NSPS compliance test method for PM. Once available, Method 5 was often also used for permitting purposes to quantify the in-stack PM emissions that represented the particles in the atmosphere expressed in terms of the ambient indicator, TSP—the original indicator for the PM NAAQS. Thus, the filterable PM emissions collected by Method 5 or other similar source test methods were sometimes referred to as “TSP emissions,” even though it was recognized that Method 5 actually collected particles that exceeded the TSP size range (25-45 μm), and did not include the condensable PM fraction. Today, Method 5 continues to serve as the performance testing procedure for most NSPS for PM.</P>
        <P>With the promulgation of the PM<E T="52">10</E>NAAQS in 1987, the annual source emissions reporting of “particulate matter emissions” (required under 40 CFR 51.322 and 51.323) ended with the state reporting of calendar year 1987 emissions, and the required reporting of PM<E T="52">10</E>emissions began with state reporting of calendar year 1988 emissions. In the absence of a standard reference test method, states were instructed to choose an appropriate method of determining PM<E T="52">10</E>emissions for each source. On April 17, 1990, the EPA promulgated Method 201A to provide the states with a standard means of measuring filterable PM<E T="52">10</E>emissions contained in the stack. Later in the same year, noting that condensable PM emissions form very fine particles in the PM<E T="52">10</E>size range and are considered PM<E T="52">10</E>emissions, the EPA proposed to add a test method to provide states with a means of measuring condensable PM emissions from stationary sources.<E T="03">See</E>55 FR 41546, October 12, 1990. The test method for condensable PM emissions, known as Method 202, was promulgated on December 17, 1991, in Appendix M of 40 CFR part 51. With the new focus on the PM<E T="52">10</E>indicator, the EPA also began to emphasize the relevance of condensable PM emissions,<SU>2</SU>

          <FTREF/>and encouraged states to consider the condensable PM fraction where it was considered to be a significant contributor to an area's PM<E T="52">10</E>nonattainment status. However, there were only a few nonattainment areas where control of the condensable PM portion was actually required in order to achieve attainment.</P>
        <FTNT>
          <P>

            <SU>2</SU>“Condensable particulate matter is of potential importance because it usually is quite fine and thus falls primarily within the PM<E T="52">10</E>fraction.”<E T="03">See,</E>“PM-10 SIP Development Guideline” (June 1987) at p. 5-32.</P>
        </FTNT>
        <P>Even before the EPA's introduction of the PM<E T="52">2.5</E>indicator for the PM NAAQS in 1997, the EPA published information on PM<E T="52">2.5</E>emissions in its National Emission Inventory Database (NEI).<SU>3</SU>

          <FTREF/>With the assistance of information gained through speciation analyses of PM<E T="52">2.5</E>, the EPA recognized that condensable PM could be a substantial portion of the total PM<E T="52">2.5</E>emitted by certain source categories. Beginning with the 1999 NEI, the EPA began including the condensable PM fraction of the total PM<E T="52">2.5</E>emitted by certain source categories, and encouraged states to consider the condensable PM fraction for the development of emissions inventories for PM<E T="52">2.5</E>SIPs.<SU>4</SU>
          <FTREF/>The EPA also provided condensable PM emission factors for various sources in AP-42 so that those state and local air control agencies having the responsibility to report emission inventories would have the tools needed to estimate and report those emissions to the EPA.</P>
        <FTNT>
          <P>

            <SU>3</SU>The EPA's NEI contains information about sources that emit criteria pollutants and their precursors, and hazardous pollutants. The database includes estimates of annual air pollutant emissions from point, nonpoint and mobile sources. The NEI currently contains information on PM with regard to the criteria indicators PM<E T="52">10</E>and PM<E T="52">2.5</E>.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>4</SU>“Emissions Inventory Guidance for Implementation of Ozone and Particulate Matter National Ambient Air Quality Standards (NAAQS) and Regional Haze,” EPA-454/R-99-006 (April 1999).</P>
        </FTNT>

        <P>In 2002, the EPA issued a rule known as the Consolidated Emissions Reporting Rule (CERR), which, among other things, established requirements for the reporting to the EPA of PM<E T="52">2.5</E>emissions. In conjunction with the new reporting requirements, the EPA added definitions of “primary PM,” “primary PM<E T="52">10</E>,” and “primary PM<E T="52">2.5,</E>” all of which included both the filterable and condensable PM fraction.<E T="03">See</E>67 FR 39602, June 10, 2002. The CERR required states to report emissions of primary PM<E T="52">10</E>and primary PM<E T="52">2.5,</E>and listed as optional the reporting of emissions of primary PM. However, when the EPA amended those rules in 2008, it dropped the definition “primary PM” and the listing of “primary PM” as an optional pollutant, eliminating the requirement for reporting “PM” (as opposed to PM<E T="52">10</E>and PM<E T="52">2.5</E>).<E T="03">See</E>73 FR 76539, December 17, 2008.</P>

        <P>In November 2005, the EPA proposed requirements that states must fulfill in developing their implementation plans for the attainment of PM<E T="52">2.5</E>NAAQS.<E T="03">See</E>70 FR 65984, November 1, 2005. With the historical emphasis on controlling the filterable PM fraction—even when the shift occurred to control PM<E T="52">10</E>emissions—it became apparent that in many cases it could be necessary to take a closer look at the control of the condensable PM fraction in order to attain the PM<E T="52">2.5</E>NAAQS in some areas.<SU>5</SU>

          <FTREF/>The preamble highlighted the importance in certain cases of controlling the condensable PM fraction to help ensure the attainment of the new NAAQS. It was acknowledged at that time that most stationary source test methods specified in state rules did not provide for the measurement of condensable PM emissions. Instead, it was found that most source test methods referenced in SIPs provided a measurement of only the filterable fraction of PM. The EPA further noted that “these filterable particulate matter test methods are either identical or very similar to one of the ten Federal test methods published in Appendix A of 40 CFR Part 60 and used to determine compliance with New Source Performance Standards (NSPS).” Id at 66049. The EPA indicated that states needing to adopt local control measures for primary PM<E T="52">2.5</E>in nonattainment areas would need to revise their stationary source test methods to focus on the PM<E T="52">2.5</E>indicator, including the condensable PM fraction.<SU>6</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>5</SU>“The inclusion of condensable emissions in a source's PM<E T="52">2.5</E>emissions is of increasing importance with the change in the indicator for particulate matter to PM<E T="52">2.5</E>. Condensible emissions are essentially fine particles, and thus are a larger fraction of PM<E T="52">2.5</E>than of TSP or PM<E T="52">10</E>.” 70 FR 65984 (November 1, 2005) at p. 66039.</P>
        </FTNT>
        <FTNT>
          <P>

            <SU>6</SU>The EPA did indicate that “test methodologies that measure only filterable particulate matter would be acceptable in areas where no additional reductions of primary PM<E T="52">2.5</E>and particulate precursor emissions are required to project attainment of the PM<E T="52">2.5</E>NAAQS.” Id at 66049.</P>
        </FTNT>

        <P>On March 25, 2009, the EPA proposed to modify existing Method 201A to allow for measurement of filterable PM<E T="52">2.5</E>. In fact, the proposed modification offered the ability to measure filterable PM<E T="52">10</E>, filterable PM<E T="52">2.5</E>, or both filterable PM<E T="52">10</E>and filterable PM<E T="52">2.5</E>from<PRTPAGE P="15660"/>stationary sources. At the same time, the EPA proposed amendments to Method 202 to improve the precision of the method for measuring condensable PM and to provide for more accurate overall quantification of primary emissions of PM<E T="52">10</E>and PM<E T="52">2.5</E>to the ambient air. Method 202 contained several optional procedures that were intended to accommodate the various test methods used by state and local regulatory entities at the time Method 202 was being developed. The inclusion of the optional procedures in 1991 ultimately proved problematic in that each of them resulted in a different emissions value. To address this issue, the EPA explored the influence of the optional procedures to identify the ones that would result in a biased measurement. In December 2010, the EPA promulgated an improved Method 202 eliminating options that would produce different measures of emissions.</P>
        <HD SOURCE="HD2">C. New Source Review Program for PM</HD>
        <P>The NSR program is a statutorily based preconstruction permitting program that applies when a stationary source of air pollution proposes to construct or undergo modification. The NSR program consists of three different preconstruction permit programs: (1) PSD; (2) nonattainment NSR; and (3) minor NSR. We often refer to the PSD and nonattainment NSR programs together as the major NSR program because those permit programs regulate the construction of new major stationary sources and major modifications to existing major stationary sources.</P>
        <P>The nonattainment NSR program applies in advance of construction to new major stationary sources and major modifications of sources of a pollutant that locate in an area that is designated “nonattainment” for that pollutant. As such, the nonattainment NSR program applies only with respect to criteria pollutants, i.e., pollutants (or indicators thereof) for which EPA has promulgated NAAQS. On the other hand, the PSD program is a statutorily based preconstruction review and permitting program that applies to new or modified major stationary sources proposing to locate in an area meeting the NAAQS (“attainment” areas) and areas for which there is insufficient information to classify them as either attainment or nonattainment (“unclassifiable” areas).</P>
        <P>Like the nonattainment NSR program, the applicability of the PSD program to a major stationary source or major modification must be determined in advance of construction and is pollutant-specific. However, unlike the nonattainment NSR program, the PSD requirements are applied on a pollutant-specific basis for any “air pollutant” that is “subject to regulation” under the Act. Thus, the PSD program is not restricted to criteria pollutants.<SU>7</SU>
          <FTREF/>Once a major source is determined to be subject to the PSD program (PSD source) for a particular air pollutant, among other requirements, it must undertake a series of analyses to demonstrate that it will use the best available control technology (BACT) to minimize the emissions of each affected pollutant, and that the emissions of each pollutant will not cause or contribute to a violation of any applicable NAAQS or any applicable maximum allowable increase in a pollutant concentration (PSD increment).</P>
        <FTNT>
          <P>

            <SU>7</SU>“Particulate matter emissions” are regulated under the PSD program as a regulated NSR pollutant, but not under the nonattainment NSR program because nonattainment designations apply only with regard to criteria pollutants (pollutants for which NAAQS exist, e.g., PM<E T="52">10</E>and PM<E T="52">2.5</E>) and “particulate matter emissions” are not considered a criteria pollutant.</P>
        </FTNT>

        <P>Consistent with the original NAAQS and PSD increments for PM, the PSD program established pollutant applicability requirements for PM on the basis of the TSP indicator. Accordingly, the PSD regulations defined a “significant” increase in emissions of PM as 25 tons per year (tpy). When the EPA revised the PM NAAQS in 1987, establishing a new PM<E T="52">10</E>indicator, two indicators for particles were recognized as being regulated under the Act because the statutory PSD increments for PM were still expressed in terms of TSP. The addition of the new PM<E T="52">10</E>indicator also necessitated a distinction between those emissions of PM that should be used to determine a source's compliance with the new PM<E T="52">10</E>NAAQS and those emissions of PM that should be used to determine a source's compliance with the existing TSP-based increments. Hence, in 1987, the EPA adopted the term “particulate matter emissions” to help clarify the distinction between the original TSP indicator for the NAAQS and the new PM<E T="52">10</E>indicator.<E T="03">See</E>52 FR 24672, July 1, 1987. Accordingly, the original significant emissions rate of 25 tpy was retained and applied to the newly-defined term “particulate matter emissions” (associated with the ambient TSP indicator), and simultaneously a significant emissions rate of 15 tpy was defined in association with the term “PM<E T="52">10</E>emissions.”<E T="03">See</E>40 CFR 51.166(b)(23)(i) and 52.21(b)(23)(i).</P>

        <P>In 1993, under authorization contained in the CAA Amendments of 1990, EPA adopted increments for PM that were expressed in terms of ambient concentrations of PM<E T="52">10</E>, and substituted those increments for the original statutory increments for PM based on the TSP indicator.<E T="03">See</E>58 FR 31622, June 3, 1993. As a result, both the NAAQS for PM and the PSD increments for PM were henceforth measured by the PM<E T="52">10</E>indicator and, once states revised their SIPs to incorporate the new PM<E T="52">10</E>NAAQS and PM<E T="52">10</E>increments, the TSP indicator was no longer considered a regulated indicator of particles. However, because the NSPS for PM commonly measured performance standard compliance based on emissions of PM using the indicator that was roughly associated with the original ambient TSP indicator, the EPA stated in the preamble to the 1993 final rule promulgating new PSD increments based on PM<E T="52">10</E>that the agency would continue to regulate “particulate matter emissions” (25 tpy significant emissions rate) separately from “PM<E T="52">10</E>emissions” (15 tpy significant emissions rate) for purposes of PSD applicability determinations. Id at 31629.</P>

        <P>Finally, in a final rule issued on May 16, 2008, titled, “Implementation of the New Source Review (NSR) Program for Particulate Matter Less Than 2.5 Micrometers (PM<E T="52">2.5</E>)” (73 FR 28321), the EPA identified the major source threshold and significant emissions rate for PM<E T="52">2.5</E>to reflect the indicator for the PM NAAQS that were issued in 1997.<E T="03">See</E>40 CFR 51.166(b)(23)(i) and 52.21(b)(23)(i). Hence, three separate indicators for emissions of PM are currently being regulated under the PSD program. Those indicators include PM<E T="52">10</E>and PM<E T="52">2.5,</E>both of which are indicators reflecting the way the NAAQS for PM are currently measured, and “particulate matter emissions,” which is a term that signifies the indicator of PM that is measured under various NSPS for PM (40 CFR part 60).<SU>8</SU>
          <FTREF/>All three of the indicators for PM are considered separately as regulated NSR pollutants subject to review under the PSD program, which means that proposed new and modified sources must treat each indicator of PM as a separate pollutant for applicability determinations, and must then apply the PSD requirements, as appropriate, independently for each indicator of PM.</P>
        <FTNT>
          <P>
            <SU>8</SU>In addition to the NSPS for PM, it is noted that states regulated “particulate matter emissions” for many years in their SIPs for PM, and the same indicator has been used as a surrogate for determining compliance with certain standards contained in 40 CFR part 63, regarding National Emission Standards for Hazardous Air Pollutants.</P>
        </FTNT>

        <P>The 2008 final rule also added a provision to the definition “regulated NSR pollutant” in the PSD regulations and the Emission Offset Interpretative Ruling that requires the inclusion of the<PRTPAGE P="15661"/>condensable fraction of PM for all three indicators of PM. Accordingly, the determination of the potential emissions (for permit applicability determinations), and the setting of emissions limitations and in-stack pollutant measurements (for source compliance purposes) would involve the inclusion of the condensable fraction of PM for each of the three PM indicators.</P>

        <P>For reasons to be explained, this proposed rulemaking would remove “particulate matter emissions” from that provision defining “regulated NSR pollutant” in the aforementioned regulations, so that the relevant provision would require the inclusion of the condensable fraction of PM only with regard to emissions of PM<E T="52">10</E>and PM<E T="52">2.5</E>.</P>
        <HD SOURCE="HD1">IV. Why is EPA proposing to change the definition “regulated NSR pollutant” with regard to PM?</HD>

        <P>When we proposed to amend the PSD rules to address new requirements for PM<E T="52">2.5</E>in 2005, we proposed to revise the definition “regulated NSR pollutant” to add PM<E T="52">2.5</E>as a regulated criteria pollutant and to require that, for purposes of determining PSD applicability and setting emissions limitations for a particular proposed source or modification, emissions of PM<E T="52">10</E>and PM<E T="52">2.5</E>included the condensable portion of particulate matter that could be emitted by the source or modification. Specifically, the proposed regulatory text provided that “Particulate matter (PM<E T="52">10</E>and PM<E T="52">2.5</E>) emissions include gaseous emissions from a source or activity which condense to form particulate matter at ambient temperatures.”<E T="03">See,</E>e.g., 70 FR 65984 at 66067. In that text, we had not intended to include the PM indicator referred to as “particulate matter emissions”; instead, we intended the proposed text as a “shorthand” terminology encompassing both “PM<E T="52">10</E>emissions” and “PM<E T="52">2.5</E>emissions.” Moreover, we did not receive any comments suggesting that the “PM emissions” indicator should be included in the provision requiring the inclusion of condensable PM. Nevertheless, in the final stages of preparing the 2008 final rule, the proposed text “Particulate matter (PM<E T="52">10</E>and PM<E T="52">2.5</E>) emissions,” was revised to read “Particulate matter (PM) emissions, PM<E T="52">10</E>emissions and PM<E T="52">2.5</E>emissions.” Thus, the inadvertent editorial change made in the final rule added “Particulate matter (PM) emissions” as a third indicator for PM to the sentence for which the PSD regulations would require that condensable PM be included.</P>

        <P>The preamble discussion in both the NPRM and the final rulemaking, designed to describe the new provision under the definition “regulated NSR pollutant,” supports the position that our objective was to ensure that the condensable PM fraction was included in measurements of emissions of PM<E T="52">10</E>and PM<E T="52">2.5</E>. For example, the preamble to the NPRM stated the following: “The EPA has issued guidance clarifying that PM<E T="52">10</E>includes condensable particles and that, where condensable particles are expected to be significant, States should use methods that measure condensible emissions.” 70 FR 65984 at 66039 (citing a March 31, 1994, EPA memo to the Iowa Department of Natural Resources). With regard to PM<E T="52">2.5</E>, we stated “[c]ondensible emissions are essentially fine particles, and thus are a larger fraction of PM<E T="52">2.5</E>emissions than of TSP or PM<E T="52">10</E>emissions.” Ibid. In the 2008 final rule, we clearly stated in the preamble that “EPA will require that all NSR applicability determinations for PM<E T="52">2.5</E>and PM<E T="52">10</E>address condensable emissions as applicable * * *.” 73 FR 28321 at 28335.</P>

        <P>We also note that the 2008 final rule added the term “particulate matter (PM) emissions” to the definition “regulated NSR pollutant” at 40 CFR part 51 Appendix S (the EPA's “Emission Offset Interpretative Ruling”). This was clearly a mistake because that rule pertains to new source review in nonattainment areas (and to sources locating outside nonattainment areas that impact air quality in a nonattainment area). That being the case, Appendix S is not intended to address noncriteria pollutants, since nonattainment areas apply only to criteria pollutants. To further illustrate this point, the definition “regulated NSR pollutant” under the nonattainment area NSR requirements at 40 CFR 51.165 does not include the term “particulate matter emissions.” We have already explained that “particulate matter emissions” refers to the noncriteria indicator for PM subject to regulation under various NSPS. Accordingly, EPA is also proposing to revise the definition “regulated NSR pollutant” under Appendix S to remove the term “particulate matter emissions.”<E T="03">See</E>proposed 40 CFR part 51 Appendix S, Section III.A.31(ii).</P>
        <P>It is important to note that the proposed change would not totally exempt the inclusion of the condensable PM fraction as part of “particulate matter emissions.” The proposed revision accounts for the fact that, in some cases, the condensable PM fraction should be counted. The first case is where the applicable NSPS requires that the condensable PM fraction be included in the determination of compliance with the performance standard for PM.<SU>9</SU>
          <FTREF/>The second case is where the applicable SIP already requires that the condensable PM fraction be included in the measurement of PM. Finally, in the case of any source emitting a pollutant that is regulated under section 111 of the Act, but is not itself subject to an NSPS, the reviewing authority may determine the applicable test method to be used to determine that source's compliance.</P>
        <FTNT>
          <P>

            <SU>9</SU>In developing the NSPS for Wool Fiberglass Insulation Manufacturing facilities (Subpart PPP), the EPA determined that the control device could effectively reduce both the solid particles and the condensable PM, and promulgated the PM standard based on the measurement of both filterable solid particles and condensable PM. In addition, the agency established a variant of Method 5, referred to as Method 5e, to measure the filterable PM and the total organic carbon portion of the impinger catch.<E T="03">See</E>50 FR 7694, February 25, 1985.</P>
        </FTNT>

        <P>Thus, we are also proposing to clarify the text contained in the definition “regulated NSR pollutant” to indicate that for pollutants regulated under section 111 of the Act, which includes “particulate matter emissions,” the applicability of the PSD requirements to that pollutant should be determined in a manner consistent with the test method prescribed for that particular NSPS or applicable SIP.<E T="03">See</E>proposed 40 CFR 51.166(b)(49)(ii) and 52.21(b)(50)(ii). In cases where the proposed source or modification of PM is not regulated by any NSPS, but is nevertheless required to consider its potential to emit that pollutant, we intend to require under the federal PSD requirements at 40 CFR 52.21 that the applicable measurement will be determined by the Administrator. In the case of “particulate matter emissions,” we generally intend to rely on the common practice of the NSPS to require that the applicable measure should be the filterable PM only, based on a compliance test method appropriate for such source, e.g., Method 5. Under the PSD regulations at 40 CFR 51.166, we propose that states, as the reviewing authority, may establish their own policy for applying the PSD requirements for “particulate matter emissions” to sources for which the NSPS does not apply.</P>

        <P>The primary objective of our decision to propose this revision is to ensure to the extent practicable that we are not unnecessarily imposing a new requirement on state/local agencies and the regulated community that has little if any effect on preventing significant air<PRTPAGE P="15662"/>quality deterioration or on efforts to attain the primary and secondary PM NAAQS. That is, we do not intend to require the inclusion of condensable PM in measurements of “particulate matter emissions” where that has not been a common practice in state and local control agencies and there are no ambient standards against which ”particulate matter emissions” are to be compared. Proposed new or modified stationary sources of PM typically will be subjected to the PSD requirements on the basis of their potential to emit PM<E T="52">10</E>or PM<E T="52">2.5</E>emissions and will be required to install controls for their emissions of PM<E T="52">10</E>and/or PM<E T="52">2.5</E>, both of which must consider the condensable fraction. We also recognize that in some cases, some states have chosen to regulate the condensable PM when determining the amount of a source's “particulate matter emissions.” As already explained, the proposed revision would allow states to continue that practice by providing the necessary discretion to the reviewing authority, but we do not intend to impose such a new PSD requirement where it is not otherwise being practiced by the states already.</P>
        <HD SOURCE="HD1">V. Statutory and Executive Order Reviews</HD>
        <HD SOURCE="HD2">A. Executive Order 12866: Regulatory Planning and Review and Executive Order 13563: Improving Regulation and Regulatory Review</HD>
        <P>This action is not a “significant regulatory action” under the terms of Executive Order 12866 (58 FR 51735, October 4, 1993), and is therefore not subject to review under Executive Orders 12866 and 13563 (76 FR 3821, January 21, 2011).</P>
        <HD SOURCE="HD2">B. Paperwork Reduction Act</HD>

        <P>This action does not impose an information collection burden under the provisions of the<E T="03">Paperwork Reduction Act,</E>44 U.S.C. 3501<E T="03">et seq.</E>Burden is defined at 5 CFR 1320.3(b). This proposal only removes the requirement to include condensable PM when quantifying “PM emissions” from proposed new major stationary sources and major modifications subject to the PSD program. The proposed change would eliminate a requirement that was not intended.</P>
        <HD SOURCE="HD2">C. Regulatory Flexibility Act</HD>
        <P>The Regulatory Flexibility Act (RFA) generally requires an agency to prepare a regulatory flexibility analysis of any rule subject to notice and comment rulemaking requirements under the Administrative Procedure Act or any other statute unless the Agency certifies that the rule will not have a significant economic impact on a substantial number of small entities. Small entities include small businesses, small organizations, and small governmental jurisdictions.</P>
        <P>For purposes of assessing the impacts of this rule on small entities, “small entity” is defined as: (1) A small business as defined by the Small Business Administration's regulations at 13 CFR 121.201; (2) a small governmental jurisdiction that is a government of a city, county, town, school district or special district with a population of less than 50,000; and (3) a small organization that is any not-for-profit enterprise which is independently owned and operated and is not dominant in its field.</P>
        <P>After considering the economic impacts of this proposed rule on small entities, which proposes only to remove an unintended requirement to include condensable PM when quantifying “particulate matter emissions” from proposed new major stationary sources and major modifications, I certify that this action will not have a significant economic impact on a substantial number of small entities. This proposed rule will not impose any requirements on small entities because small entities are not subject to the requirements of this rule.</P>
        <P>We continue to be interested in the potential impacts of the proposed rule on small entities and welcome comments on issues related to such impacts.</P>
        <HD SOURCE="HD2">D. Unfunded Mandates Reform Act</HD>
        <P>This proposed action contains no federal mandates under the provisions of Title II of the Unfunded Mandates Reform Act of 1995 (UMRA), 2 U.S.C. 1531-1538 for state, local, or tribal governments or the private sector. The action would not impose any enforceable duty on any state, local or tribal governments or the private sector. This action proposes only to remove an unintended requirement to include condensable PM when quantifying “particulate matter emissions” from proposed new major stationary sources and major modifications. Thus, this action is not subject to the requirements of sections 202 or 205 of UMRA.</P>
        <P>This proposed rule is also not subject to the requirements of section 203 of UMRA because it does not propose any regulatory requirements that might significantly or uniquely affect small governments. This action proposes only to remove an unintended requirement to include condensable PM when quantifying “particulate matter emissions” from proposed new major stationary sources and major modifications.</P>
        <HD SOURCE="HD2">E. Executive Order 13132—Federalism</HD>

        <P>This proposed rule does not have federalism implications. It 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, as specified in Executive Order 13132. The proposed rule proposes only to remove the unintended requirement to include condensable PM when quantifying “particulate matter emissions” from proposed new major stationary sources and major modification. The requirement was inadvertently included in the 2008 final rule for Implementation of the PM<E T="52">2.5</E>NSR Program. Thus, Executive Order 13132 does not apply to this rule. Nevertheless, in the spirit of Executive Order 13132, and consistent with EPA policy to promote communications between EPA and state and local governments, EPA plans to specifically solicit comment on the proposed rule from state and local officials.</P>
        <HD SOURCE="HD2">F. Executive Order 13175—Consultation and Coordination With Indian Tribal Governments</HD>

        <P>This action does not have tribal implications, as specified in Executive Order 13175 (65 FR 67249, November 9, 2000). The proposed rule proposes only to remove the requirement to include condensable PM when quantifying “PM emissions” from proposed new major stationary sources and major modification. The requirement was inadvertently included in the 2008 final rule for Implementation of the PM<E T="52">2.5</E>NSR Program.</P>

        <P>The Act provides for states to develop plans to regulate emissions of air pollutants within their jurisdictions. The Tribal Air Rule (TAR) under the Act gives tribes the opportunity to develop and implement Act programs to attain and maintain the PM<E T="52">2.5</E>NAAQS, but leaves to the discretion of the tribes the decision of whether to develop these programs and which programs, or appropriate elements of a program, they will adopt. Thus, Executive Order 13175 does not apply to this action.</P>
        <HD SOURCE="HD2">G. Executive Order 13045—Protection of Children From Environmental Health and Safety Risks</HD>

        <P>This proposed action is not subject to Executive Order 13045 (62 FR 19885, April 23, 1997) because it is not economically significant as defined in Executive Order 12866, and because the<PRTPAGE P="15663"/>Agency does not believe the environmental health or safety risks addressed by this action to eliminate an unintended requirement present a disproportionate risk to children. The removal of this requirement would not affect one of the basic requirements of the PSD program that new and modified major sources must demonstrate that any new emissions do not cause or contribute to air quality in violation of the NAAQS.</P>
        <HD SOURCE="HD2">H. Executive Order 13211—Actions That Significantly Affect Energy Supply, Distribution, or Use</HD>
        <P>This action is not subject to Executive Order 13211 (66 FR 28355, May 22, 2001) because it is not a significant regulatory action under Executive Order 12866.</P>
        <HD SOURCE="HD2">I. National Technology Transfer and Advancement Act</HD>
        <P>Section 12(d) of the National Technology Transfer and Advancement Act of 1995 (NTTAA), Public Law 104-113, 12(d) (15 U.S.C. 272 note) directs EPA to use voluntary consensus standards in its regulatory activities unless to do so would be inconsistent with applicable law or otherwise impractical. Voluntary consensus standards are technical standards (e.g., materials specifications, test methods, sampling procedures, and business practices) that are developed or adopted by voluntary consensus standards bodies. The NTTAA directs EPA to provide Congress, through OMB, explanations when the Agency decides not to use available and applicable voluntary consensus standards.</P>
        <P>This action does not involve technical standards. Therefore, EPA did not consider the use of any voluntary consensus standards.</P>
        <HD SOURCE="HD2">J. Executive Order 12898—Federal Actions To Address Environmental Justice in Minority Populations and Low-Income Populations</HD>
        <P>Executive Order 12898 (59 FR 7629, Feb. 16, 1994) establishes federal executive policy on environmental justice. Its main provision directs federal agencies, to the greatest extent practicable and permitted by law, to make environmental justice part of their mission by identifying and addressing, as appropriate, disproportionately high and adverse human health or environmental effects of their programs, policies, and activities on minority populations and low-income populations in the United States.</P>
        <P>The EPA has determined that this proposed rule to remove an unintended requirement will not have adverse human health or environmental effects on minority or low-income populations because it does not appreciably affect the level of protection provided to human health or the environment.</P>
        <HD SOURCE="HD1">VI. Statutory Authority</HD>
        <P>The statutory authority for this proposed action is provided by sections 101, 160, 163, 165, 166, 301, and 307(d) of the Act as amended (42 U.S.C. 7401, 7470, 7473, 7475, 7476, 7601, and 7607(d)).</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <CFR>40 CFR Part 51</CFR>
          <P>Environmental protection, Administrative practices and procedures, Air pollution control, Intergovernmental relations.</P>
          <CFR>40 CFR Part 52</CFR>
          <P>Environmental protection, Administrative practices and procedures, Air pollution control, Intergovernmental relations.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: March 12, 2012.</DATED>
          <NAME>Lisa P. Jackson,</NAME>
          <TITLE>Administrator.</TITLE>
        </SIG>
        
        <P>For the reasons stated in the preamble, title 40, chapter I of the Code of Federal Regulations is proposed to be amended as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 51—[AMENDED]</HD>
          <P>1. The authority citation for part 51 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>23 U.S.C. 101; 42 U.S.C. 7401-7671q.</P>
          </AUTH>
          <SUBPART>
            <HD SOURCE="HED">Subpart I—[Amended]</HD>
          </SUBPART>
          <P>2. Section 51.166 is amended by revising paragraphs (b)(49)(i) and (ii) and removing (b)(vi) to read as follows:</P>
          <SECTION>
            <SECTNO>§ 51.166</SECTNO>
            <SUBJECT>Prevention of significant deterioration of air quality.</SUBJECT>
            <STARS/>
            <P>(b) * * *</P>
            <P>(49) * * *</P>
            <P>(i) Any pollutant for which a national ambient air quality standard has been promulgated;</P>
            <P>(<E T="03">a</E>) PM<E T="52">2.5</E>emissions and PM<E T="52">10</E>emissions shall include gaseous emissions from a source or activity which condense to form particulate matter at ambient temperatures. On or after January 1, 2011, such condensable particulate matter shall be accounted for in applicability determinations and in establishing emissions limitations for PM<E T="52">2.5</E>and PM<E T="52">10</E>in PSD permits. Compliance with emissions limitations for PM<E T="52">2.5</E>and PM<E T="52">10</E>issued prior to this date shall not be based on condensable particular matter unless required by the terms and conditions of the permit or the applicable implementation plan. Applicability determinations made prior to this date without accounting for condensable particular matter shall not be considered in violation of this section unless the applicable implementation plan required condensable particular matter to be included;</P>
            <P>(<E T="03">b</E>) Any pollutant identified under this paragraph (b)(49)(i)(<E T="03">b</E>) as a constituent or precursor to such pollutant. Precursors identified by the Administrator for purposes of NSR are the following:</P>
            <P>(<E T="03">1</E>) Volatile organic compounds and nitrogen oxides are precursors to ozone in all attainment and unclassifiable areas.</P>
            <P>(<E T="03">2</E>) Sulfur dioxide is a precursor to PM<E T="52">2.5</E>in all attainment and unclassifiable areas.</P>
            <P>(<E T="03">3</E>) Nitrogen oxides are presumed to be precursors to PM<E T="52">2.5</E>in all attainment and unclassifiable areas, unless the State demonstrates to the Administrator's satisfaction or EPA demonstrates that emissions of nitrogen oxides from sources in a specific area are not a significant contributor to that area's ambient PM<E T="52">2.5</E>concentrations.</P>
            <P>(<E T="03">4</E>) Volatile organic compounds are presumed not to be precursors to PM<E T="52">2.5</E>in any attainment or unclassifiable area, unless the State demonstrates to the Administrator's satisfaction or EPA demonstrates that emissions of volatile organic compounds from sources in a specific area are a significant contributor to that area's ambient PM<E T="52">2.5</E>concentrations.</P>
            <P>(ii) Any pollutant that is subject to any standard promulgated under section 111 of the Act, as required to be measured by the applicable performance standard for that pollutant. For sources not currently regulated by an applicable NSPS, measurement of such pollutant shall be determined by the reviewing authority;</P>
            <STARS/>
            <P>3. Appendix S to Part 51 is amended revising paragraph II.A.31(ii) and by removing paragraphs II.A.31(iii) and (iv) to read as follows:</P>
            
            <FP>and</FP>
            <HD SOURCE="HD1">Appendix S to Part 51—Emission Offset Interpretative Ruling</HD>
            <EXTRACT>
              <STARS/>
              <P>II. * * *</P>
              <P>A. * * *</P>
              <P>31. * * *</P>
              <P>(i) * * *</P>

              <P>(ii) Any pollutant for which a national ambient air quality standard has been promulgated;<PRTPAGE P="15664"/>
              </P>
              <P>(<E T="03">1</E>) PM<E T="52">2.5</E>emissions and PM<E T="52">10</E>emissions shall include gaseous emissions from a source or activity, which condense to form particulate matter at ambient temperatures. On or after January 1, 2011, such condensable particulate matter shall be accounted for in applicability determinations and in establishing emissions limitations for PM<E T="52">2.5</E>and PM<E T="52">10</E>in permits issued under this ruling. Compliance with emissions limitations for PM<E T="52">2.5</E>and PM<E T="52">10</E>issued prior to this date shall not be based on condensable particulate matter unless required by the terms and conditions of the permit or the applicable implementation plan. Applicability determinations made prior to this date without accounting for condensable particulate matter shall not be considered in violation of this section unless the applicable implementation plan required condensable particulate matter to be included.</P>
              <P>(<E T="03">2</E>) Any pollutant that is identified under this paragraph II.A.31(ii)(<E T="03">2</E>) as a constituent or precursor of a general pollutant listed under paragraph II.A.31(i) or (ii) of this Ruling, provided that such constituent or precursor pollutant may only be regulated under NSR as part of regulation of the general pollutant. Precursors identified by the Administrator for purposes of NSR are the following:</P>
              <P>(<E T="03">a</E>) Volatile organic compounds and nitrogen oxides are precursors to ozone in all ozone nonattainment areas.</P>
              <P>(<E T="03">b</E>) Sulfur dioxide is a precursor to PM<E T="52">2.5</E>in all PM<E T="52">2.5</E>nonattainment areas.</P>
              <STARS/>
            </EXTRACT>
          </SECTION>
        </PART>
        <PART>
          <HD SOURCE="HED">PART 52—[Amended]</HD>
          <P>4. The authority citation for part 52 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 7401<E T="03">et seq.</E>
            </P>
          </AUTH>
          <SUBPART>
            <HD SOURCE="HED">Subpart A—[Amended]</HD>
          </SUBPART>
          <P>5. Section 52.21 is amended by revising paragraphs (b)(50)(i) and (ii) and removing paragraph (b)(50)(vi) to read as follows:</P>
          
          <FP>and</FP>
          <SECTION>
            <SECTNO>§ 52.21</SECTNO>
            <SUBJECT>Prevention of significant deterioration of air quality.</SUBJECT>
            <STARS/>
            <P>(b) * * *</P>
            <P>(50) * * *</P>
            <P>(i) Any pollutant for which a national ambient air quality standard has been promulgated;</P>
            <P>(<E T="03">a</E>) PM<E T="52">2.5</E>emissions and PM<E T="52">10</E>emissions shall include gaseous emissions from a source or activity, which condense to form particulate matter at ambient temperatures. On or after January 1, such condensable particulate matter shall be accounted for in applicability determinations and in establishing emissions limitations for PM<E T="52">2.5</E>and PM<E T="52">10</E>in PSD permits. Compliance with emissions limitations for PM<E T="52">2.5</E>and PM<E T="52">10</E>issued prior to this date shall not be based on condensable particular matter unless required by the terms and conditions of the permit or the applicable implementation plan. Applicability determinations made prior to this date without accounting for condensable particular matter shall not be considered in violation of this section unless the applicable implementation plan required condensable particular matter to be included.</P>
            <P>(<E T="03">b</E>) Any pollutant identified under this paragraph (b)(50)(i)(<E T="03">b</E>) as a constituent or precursor for such pollutant. Precursors identified by the Administrator for purposes of NSR are the following:</P>
            <P>(<E T="03">1</E>) Volatile organic compounds and nitrogen oxides are precursors to ozone in all attainment and unclassifiable areas.</P>
            <P>(<E T="03">2</E>) Sulfur dioxide is a precursor to PM<E T="52">2.5</E>in all attainment and unclassifiable areas.</P>
            <P>(<E T="03">3</E>) Nitrogen oxides are presumed to be precursors to PM<E T="52">2.5</E>in all attainment and unclassifiable areas, unless the State demonstrates to the Administrator's satisfaction or EPA demonstrates that emissions of nitrogen oxides from sources in a specific area are not a significant contributor to that area's ambient PM<E T="52">2.5</E>concentrations.</P>
            <P>(<E T="03">4</E>) Volatile organic compounds are presumed not to be precursors to PM<E T="52">2.5</E>in any attainment or unclassifiable area, unless the State demonstrates to the Administrator's satisfaction or EPA demonstrates that emissions of volatile organic compounds from sources in a specific area are a significant contributor to that area's ambient PM<E T="52">2.5</E>concentrations.</P>
            <P>(ii) Any pollutant that is subject to any standard promulgated under section 111 of the Act, as required to be measured by the applicable performance standard for that pollutant. For sources not currently regulated by an applicable NSPS, measurement of such pollutant shall be determined by the Administrator;</P>
            <STARS/>
          </SECTION>
        </PART>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6429 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Federal Emergency Management Agency</SUBAGY>
        <CFR>44 CFR Part 67</CFR>
        <DEPDOC>[Docket ID FEMA-2011-0002; Internal Agency Docket No. FEMA-B-1207]</DEPDOC>
        <SUBJECT>Proposed 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>Proposed rule; correction.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>On August 3, 2011, FEMA published in the<E T="04">Federal Register</E>a proposed rule that contained an erroneous table. This notice provides corrections to that table, to be used in lieu of the information published at 76 FR 46701. The table provided here represents the flooding sources, location of referenced elevations, and effective and modified elevations for the City of Cadiz, Kentucky. Specifically, it addresses the flooding sources Little River (backwater effects from Lake Barkley) and Little River Tributary 1 (backwater effects from Lake Barkley).</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments are to be submitted on or before June 14, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>You may submit comments, identified by Docket No. FEMA-B-1207, to 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>
        </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) publishes proposed determinations of Base (1% annual-chance) Flood Elevations (BFEs) and modified BFEs for communities participating in the National Flood Insurance Program (NFIP), in accordance with section 110 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4104, and 44 CFR 67.4(a).</P>

        <P>These proposed BFEs and modified BFEs, together with the floodplain management criteria required by 44 CFR 60.3, are minimum requirements. They should not be construed to mean that<PRTPAGE P="15665"/>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. These proposed elevations 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.</P>
        <HD SOURCE="HD1">Correction</HD>

        <P>In the proposed rule published at 76 FR 46701, in the August 3, 2011, issue of the<E T="04">Federal Register,</E>FEMA published a table under the authority of 44 CFR 67.4. The table, entitled “City of Cadiz, Kentucky” addressed the flooding sources Little River (backwater effects from Lake Barkley) and Little River Tributary 1 (backwater effects from Lake Barkley). That table contained inaccurate information as to the location of referenced elevation, effective and modified elevation in feet, and/or communities affected for those flooding sources.</P>
        <P>In this notice, FEMA is publishing a table containing the accurate information, to address these prior errors. The information provided below should be used in lieu of that previously published for the City of Cadiz, Kentucky.</P>
        <GPOTABLE CDEF="s25,r25,xs96,xs150,10,10" COLS="6" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">State</CHED>
            <CHED H="1">City/town/county</CHED>
            <CHED H="1">Source of flooding</CHED>
            <CHED H="1">Location **</CHED>
            <CHED H="1">* Elevation in feet<LI>(NGVD)</LI>
              <LI>+ Elevation in feet</LI>
              <LI>(NAVD)</LI>
              <LI># Depth in feet above ground</LI>
              <LI>⁁ Elevation in meters (MSL)</LI>
            </CHED>
            <CHED H="2">Existing</CHED>
            <CHED H="2">Modified</CHED>
          </BOXHD>
          <ROW EXPSTB="05" RUL="s">
            <ENT I="21">
              <E T="02">City of Cadiz, Kentucky</E>
            </ENT>
          </ROW>
          <ROW EXPSTB="00">
            <ENT I="01">Kentucky</ENT>
            <ENT>City of Cadiz</ENT>
            <ENT>Little River (backwater effects from Lake Barkley)</ENT>
            <ENT>Approximately 3.7 miles upstream of the Lake Barkley confluence to approximately 4.5 miles upstream of the Lake Barkley confluence</ENT>
            <ENT>None</ENT>
            <ENT>+375</ENT>
          </ROW>
          <ROW RUL="s">
            <ENT I="01">Kentucky</ENT>
            <ENT>City of Cadiz</ENT>
            <ENT>Little River Tributary 1 (backwater effects from Lake Barkley)</ENT>
            <ENT>Approximately 500 feet upstream of the Little River confluence to approximately 1,678 feet upstream of the Little River confluence</ENT>
            <ENT>None</ENT>
            <ENT>+375</ENT>
          </ROW>
          <ROW EXPSTB="05">
            <ENT I="22">* National Geodetic Vertical Datum.</ENT>
          </ROW>
          <ROW EXPSTB="05">
            <ENT I="22">+ North American Vertical Datum.</ENT>
          </ROW>
          <ROW EXPSTB="05">
            <ENT I="22"># Depth in feet above ground.</ENT>
          </ROW>
          <ROW EXPSTB="05">
            <ENT I="22">⁁ Mean Sea Level, rounded to the nearest 0.1 meter.</ENT>
          </ROW>
          
          <ROW>
            <ENT I="22">** BFEs to be changed include the listed downstream and upstream BFEs, and include BFEs located on the stream reach between the referenced locations above. Please refer to the revised Flood Insurance Rate Map located at the community map repository (see below) for exact locations of all BFEs to be changed.</ENT>
          </ROW>
          <ROW>
            <ENT I="22">Send comments to Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal Emergency Management Agency, 500 C Street SW., Washington, DC 20472.</ENT>
          </ROW>
          
          <ROW>
            <ENT I="21">
              <E T="02">ADDRESSES</E>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="22">
              <E T="02">City of Cadiz</E>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="22">Maps are available for inspection at 63 Main Street, Cadiz, KY 42211.</ENT>
          </ROW>
        </GPOTABLE>
        <EXTRACT>
          <FP>(Catalog of Federal Domestic Assistance No. 97.022, “Flood Insurance.”)</FP>
        </EXTRACT>
        <SIG>
          <DATED>Dated: March 1, 2012.</DATED>
          <NAME>Sandra K. Knight,</NAME>
          <TITLE>Deputy Associate Administrator for Mitigation, Department of Homeland Security, Federal Emergency Management Agency.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-6356 Filed 3-15-12; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-12-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
        <CFR>47 CFR Parts 1 and 22</CFR>
        <DEPDOC>[WT Docket No. 12-40; RM-11510; FCC 12-20]</DEPDOC>
        <SUBJECT>Cellular Service, Including Changes in Licensing of Unserved Area; Interim Restrictions and Procedures for Cellular Service Applications</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Communications Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed rule; interim procedures.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>In this document, the Federal Communications Commission (Commission) proposes to amend the rules governing the 800 MHz Cellular Radiotelephone Service (Cellular Service). In the Notice of Proposed Rulemaking (<E T="03">NPRM</E>), the Commission proposes to transition the Cellular Service from a site-based licensing model to a geographic-based model by offering an “overlay” license for every Cellular Market Area (CMA) and corresponding channel block (Block A or Block B), in two stages, via auction. The Overlay Licensees would be obligated to protect existing licensees' Cellular operations from harmful interference. The<E T="03">NPRM</E>also includes proposals to update various other Cellular Service rules. The Commission seeks comment on all its proposals as well as on alternative proposals. The companion<E T="03">Order</E>imposes certain interim procedures, including a freeze on the filing of certain Cellular applications in certain markets and<PRTPAGE P="15666"/>other interim procedures regarding currently pending applications to help ensure an orderly and efficient rulemaking proceeding while the Commission considers changes to the Cellular Service rules.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Submit comments on or before May 15, 2012, and reply comments are due on or before June 14, 2012. Written comments on the Paperwork Reduction Act proposed information collection requirements must be submitted by the public, Office of Management and Budget (OMB), and other interested parties on or before May 15, 2012.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Parties may submit comments to the Secretary of the Federal Communications Commission, identified by WT Docket No. 12-40; FCC No. 12-20, by any of the following methods:</P>
          <P>
            <E T="03">Electronic Filers:</E>Comments may be filed electronically using the Internet:<E T="03">http://fjallfoss.fcc.gov/ecfs2/.</E>
          </P>
          <P>
            <E T="03">Paper Filers:</E>Parties who choose to file by paper must file an original and one copy of each filing.</P>
          <P>
            <E T="03">People with Disabilities:</E>Contact the FCC to request reasonable accommodations (accessible format documents, sign language interpreters, CART, etc.) by email:<E T="03">FCC504@fcc.gov</E>or phone 202-418-0530 or TTY: 202-418-0432.</P>
          

          <FP>In addition to filing comments with the Secretary, a copy of any comments on the Paperwork Reduction Act information collection requirements contained herein should be submitted to the Federal Communications Commission via email to<E T="03">PRA@fcc.gov</E>and to Nicholas A. Fraser, OMB, via email to<E T="03">Nicholas_A._Fraser@omb.eop.gov</E>or via fax at 202-395-5167.For detailed instructions for submitting comments and additional information on the rulemaking process,<E T="03">see</E>the<E T="02">SUPPLEMENTARY INFORMATION</E>section of this document.</FP>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Nina Shafran, Wireless Telecommunications Bureau, Mobility Division, at 202-418-2781 or by email to<E T="03">Nina.Shafran@fcc.gov.</E>For additional information concerning Paperwork Reduction Act information collection requirements contained in this document, send an email to<E T="03">PRA@fcc.gov</E>or contact Judith B. Herman at (202) 418-0214.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>This is a summary of the Commission's Notice of Proposed Rulemaking and Order (<E T="03">NPRM and Order</E>) in WT Docket No. 12-40, FCC 12-20, adopted and released on February 15, 2012. The full text of the<E T="03">NPRM and Order,</E>including all Appendices, is available for inspection and copying during normal business hours in the FCC Reference Center, 445 12th Street SW., Washington, DC 20554. The complete text may be purchased from the Commission's copy contractor, Best Copy and Printing, Inc., 445 12th Street SW., Room CY-B402, Washington, DC 20554. The complete text of the<E T="03">NPRM and Order</E>may be downloaded at:<E T="03">http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-12-20A1.doc.</E>In addition, the complete text of the<E T="03">NPRM and Order</E>as well as links to Cellular Service coverage maps and interactive map files are available at:<E T="03">http://www.fcc.gov/rulemaking/12-40.</E>Alternative formats are available to persons with disabilities by sending an email to<E T="03">fcc504@fcc.gov</E>or by calling the Consumer &amp; Governmental Affairs Bureau at 202-418-0530 (voice), 202-418-0432 (tty).</P>
        <HD SOURCE="HD1">Paperwork Reduction Act of 1995 Analysis</HD>

        <P>This document contains potential new and modified information collection requirements. The Commission, as part of its continuing effort to reduce paperwork burdens, invites the general public and OMB to comment on the potential information collection requirements contained in this document, as required by the Paperwork Reduction Act of 1995, Public Law 104-13. In addition, pursuant to the Small Business Paperwork Relief Act of 2002, Public Law 107-198,<E T="03">see</E>44 U.S.C. 3506(c)(4), we seek specific comment on how we might “further reduce the information collection burden for small business concerns with fewer than 25 employees.”</P>
        <HD SOURCE="HD1">Synopsis of the Notice of Proposed Rulemaking</HD>
        <HD SOURCE="HD1">I. Introduction</HD>
        <P>1. Since its inception roughly 30 years ago, the Cellular Service has been instrumental in transforming the communications landscape by making mobile services broadly available to the American public. As discussed in Section III below, based on our data, only limited area not yet licensed (Unserved Area) remains outside of Alaska and certain rural markets in the western United States. At this advanced stage of the Cellular Service, the site-based aspect of this licensing model is yielding diminished returns. The significant administrative burdens on licensees associated with the site-based model no longer appear to be outweighed by the public benefits produced. In addition, the Cellular Service stands apart from virtually all other commercial wireless services by not yet transitioning to a geographic-based model, which offers greater flexibility and reduced regulatory requirements. Thus, consistent with its regulatory reform agenda, the Commission proposes to revise the Cellular licensing regime to a geographic-based approach, in two stages, through competitive bidding, as explained in detail in Section III, below.</P>

        <P>2. The Commission also proposes to update the Cellular Service rules, including, for example, streamlining application requirements and deleting certain data collection requirements that may no longer be necessary going forward. Consistent with other flexibly licensed commercial wireless services, the Commission proposes to establish a signal field strength limit. Finally, we seek comment on whether to move the part 22 Cellular rules, as well as the part 24 rules, to part 27. We seek comment on all aspects of our proposals, and on the alternative transition proposals discussed in the<E T="03">NPRM,</E>including those of CTIA—The Wireless Association (CTIA), as set forth in its initial petition for rulemaking filed in February 2008, and its revised proposal submitted in September 2010, and those of the National Telecommunications Cooperative Association (NTCA), The Rural Telecommunications Group (RTG), and others on the record. (All commenters are listed in Appendix A of the<E T="03">NPRM and Order.</E>)</P>
        <HD SOURCE="HD1">II. Background</HD>
        <P>3.<E T="03">Brief History of Cellular Service Licensing.</E>The Commission adopted initial rules governing allocation of spectrum for commercial Cellular service, including the establishment of two channel blocks (Blocks A and B), in 1981. The Commission established in phases 734 Cellular Market Areas (CMAs) for the purpose of issuing licenses to two Cellular providers per market (herein, “Original System Licensees” (OSLs)), one on each Block, without competitive bidding. Every OSL was given the exclusive right, for a five-year period from the date of grant of the initial construction authorization for that CMA Block, to build out anywhere within the CMA boundary. The area timely built out during that five-year period became the licensee's initial Cellular Geographic Service Area (CGSA), the licensed area entitled to protection from harmful interference, while any area not built out by the five-year mark was automatically relinquished for re-licensing as Unserved Area on a site-by-site basis by<PRTPAGE P="15667"/>the Commission. Under site-based licensing, any interested party may request authorization to construct at a specific transmitter location (or multiple locations) in Unserved Area, and may only construct authorized transmitters. For all CMA Blocks except one (Chambers, Texas, discussed in detail below), licenses have been issued to OSLs and the initial five-year periods have expired.</P>
        <P>4. The Commission established two phases for applicants seeking to provide Cellular service in Unserved Area for each CMA Block: Phase I and Phase II. As of late 2007, the Phase I filing window had ended in all licensed Blocks. Under current rules, Phase II lasts indefinitely. Phase II applications specify the area to be licensed and are subject to a 30-day public comment period during which petitions to deny and mutually exclusive applications may be filed. In the event that mutually exclusive applications are filed for a particular Unserved Area, they are resolved through competitive bidding in closed auctions. Licenses granted in Phase II are subject to a one-year construction deadline for the authorized site and the licensee must be providing service to subscribers by the end of the one-year period; failure to build out results in automatic termination of the authorization for that site, and the Unserved Area again is subject to the filing of site-based applications.</P>
        <P>5.<E T="03">Summary of Industry Proposals on the Record.</E>In October 2008, CTIA filed a Petition requesting that the Commission change Cellular licensing from a site-based regime to a geographic area-based regime in all markets and to assign to incumbents, without using competitive bidding, all remaining Unserved Area. The Wireless Telecommunications Bureau (Bureau) subsequently issued a Public Notice seeking comment on CTIA's Petition. (<E T="03">See</E>24 FCC Rcd 27 (WTB 2009).) Ten parties filed comments, six (including CTIA) filed reply comments, and two (including CTIA) filed<E T="03">ex parte</E>letters. In September 2010, CTIA submitted a revised proposal (CTIA Revised Plan) which it asserts “takes into account the objectives and concerns raised by commenters in this proceeding.” RTG filed comments specifically addressing the CTIA Revised Plan. In May 2011, CTIA, GCI Communication Corp. (GCI), NTCA, and RTG met with Commission staff to express their additional views regarding transition approaches for Cellular licensing and, accordingly, filed<E T="03">ex parte</E>letters. Subsequently, in February 2012, CTIA, AT&amp;T, Inc. (AT&amp;T) and Verizon Wireless met with Commission staff to express their additional views regarding transition approaches for Cellular licensing and CTIA filed<E T="03">ex parte</E>letters accordingly.</P>

        <P>6. In its Revised Plan, CTIA appears to be proposing that the Commission change the Cellular Service to geographic area-based licensing and terminate site-based access to Unserved Area on a rolling basis, as CMA Blocks become “Fully Served.” CTIA defines a Fully Served Block as one where either: (1) 90 percent of the land area is served; or (2) there is no parcel of Unserved Area measuring at least 50 contiguous square miles. Under both prongs, CTIA proposes to exclude “government lands, but not tribal areas.” All Unserved Area in Fully Served Blocks would be assigned to existing incumbents “on a proportional basis” without the use of competitive bidding. Disputes over existing CGSA boundaries and the distribution of the remaining Unserved Area to incumbents would, under CTIA's Revised Plan, need to be resolved through cooperation among licensees and in the event that such cooperative efforts fail, by referral to arbitration at the expense of the referring party. So long as a CMA Block is “under-served” (<E T="03">i.e.,</E>not Fully Served), CTIA proposes that it remain under site-based licensing rules.</P>

        <P>7. AT&amp;T and Verizon Wireless generally endorse CTIA's Petition; they have not submitted comments specifically addressing CTIA's Revised Plan. In response to the CTIA Petition, Verizon Wireless offers various additional proposals, including a staggered transition process based on regional groupings of CMA Blocks; establishment of a 40 dBµV/m median field strength limit; the provision of public notice of, and opportunity to comment on, claimed licensed area boundaries; and a plan for informal dispute resolution of boundary claims (more detailed than in CTIA's Petition), in which a<E T="03">de minimis</E>discrepancy standard would be applied.</P>
        <P>8. In contrast, commenters representing the interests of smaller and rural providers generally favor indefinite retention of the current site-based licensing regime. These commenters include Commnet Wireless, LLC (Commnet), GCI, NTCA, the Rural Independent Competitive Alliance (RICA), RTG, and United States Cellular Corporation (USCC). RTG, for example, criticizes CTIA's Revised Plan by asserting that it provides no incentive to serve areas obtained through the proposed proportional allotment and that its definition of Fully Served “could leave large areas * * *  without service indefinitely.” NTCA claims that its members are asked by their communities to ensure that hikers, hunters, and others enjoying the most rural territory can complete a call in an emergency. Commnet continues to send technicians to Unserved Area to determine if there is demand for service and claims that with most of its Unserved Area applications, the OSL could have applied for that spectrum “over at least sixteen years” but did not do so. GCI, which operates in Alaska, urges continuation of site-based licensing and is concerned it will be unable to improve (or even maintain) its network if the Commission adopts CTIA's proposal.</P>
        <P>9. The smaller and more rural providers largely reject CTIA's statistics. According to RTG, for example, CTIA's Petition misleadingly “undercounts actual use of the [site-based licensing] process” by reporting only grants, not filings, and only new applications, not modification applications. RICA, GCI, and NTCA make similar arguments. Several of these commenters are also skeptical of CTIA's proposed mechanisms for resolving disputes that may arise between adjacent licensees concerning license boundaries. USCC argues that a voluntary consultation process is unworkable for dispute resolution without legal standards.</P>

        <P>10. While preferring retention of the existing paradigm, some rural commenters state that they could accept, in the alternative, a limited transition to geographic-area licensing. Their suggestions, however, are not highly detailed and contain ambiguities. GCI, for example, indicates support for issuance of a CMA-based license if the CGSA is coterminous with the CMA boundary or if Unserved Area in the CMA Block is less than 50 square miles but does not specify how the small areas would be licensed. NTCA suggests that, if an incumbent's “actual service area” is<E T="03">not</E>coterminous with the CMA Block boundary, or if there is an Unserved Area parcel that is 50 square miles or larger, the Commission could establish a geographic license but based only on the territory “actually served by the licensee.” RTG states that Cellular licensees could “elect * * *  to transition to some form of market-based licensing,” but only where the new market-based license “would encompass the areas they actually serve.” USCC, a mid-sized carrier, states that issuance of a CMA-based license may be appropriate in limited circumstances, but argues that site-based licensing should be retained at least in any market with at least one Unserved Area Licensee (defined in the<E T="03">NPRM and Order</E>as a licensee that has established a Cellular system solely<PRTPAGE P="15668"/>through the Unserved Area application process following expiration of the OSL's exclusive five-year initial build-out period), so that OSLs and Unserved Area Licensees have equal opportunity to expand their systems.</P>

        <P>11. Commenters differ on the issue of how to assign geographic area licenses. MetroPCS Communications, Inc. (MetroPCS), another mid-sized carrier, advocates a transition to geographic-area licensing via auction. AT&amp;T states broadly that, for CMA Blocks with over 50 contiguous square miles of Unserved Area, the Commission should “license that area through an auction or some other process.” In response, USCC argues that an auction is unnecessary in light of the existing normal closed auction process for mutually exclusive Unserved Area applications. In<E T="03">Ex Parte</E>letters filed by CTIA to document various meetings with Commission staff in early 2012, which involved representatives of AT&amp;T and Verizon Wireless as well, CTIA expresses concerns of CTIA, AT&amp;T and Verizon Wireless with an overlay auction approach for markets that are not substantially served. Commnet emphasizes that the Commission used competitive bidding in prior transitions to geographic area licensing.</P>
        <HD SOURCE="HD1">III. Notice of Proposed Rulemaking</HD>
        <P>12. Based on the record, it appears that site-based licensing may unduly limit licensees' ability in many markets to adapt to technological and marketplace changes, which burdens licensees and consumes FCC staff resources, as application filings are required for even minor technical system changes. These problems can be addressed by moving to a geographic-based model, which would bring the Cellular Service into greater harmony with the more flexible licensing schemes used successfully by other similar mobile services, such as the Broadband Personal Communications Service (PCS) and the 700 MHz Service. At the same time, we propose to preserve direct access to Unserved Area through the existing site-based application process for an appropriate period in Cellular Service markets that are less substantially built out.</P>
        <P>13. In anticipation of releasing the<E T="03">NPRM,</E>the Commission undertook the task of creating a digital version of every existing CGSA based on maps accompanying Cellular applications. The data, which the Commission used to calculate licensed and Unserved Area, is available at the Commission's Web site (<E T="03">see</E>
          <E T="03">http://www.fcc.gov/rulemaking/12-40</E>). It is clear from our data that the vast majority of CMA Blocks already are substantially built out. (Maps illustrating the data are provided at Appendices B and D of the<E T="03">NPRM and Order.</E>) Licensees in these markets, which we term “Substantially Licensed” as set forth below, have faced increasing regulatory challenges, however. Among other things, they do not have the ability to modify and expand their systems without Commission filings, and must seek prior Commission approval through filings if the CGSA would be expanded, even for minor adjustments to their systems. We believe that it would serve the public interest to reduce administrative burdens for these licensees (as well as for Commission staff) by providing Cellular licensees in such markets with greater flexibility to modify their operations to respond more quickly to market conditions. Moreover, the Commission has long held that market-based licensing regimes are simpler to administer for all parties.</P>

        <P>14. We recognize that, with direct access to Unserved Area through the site-based licensing regime, licensees and prospective new entrants are free to respond to market changes by filing an application on an as-needed basis (for a filing fee) without use of competitive bidding in most cases. We believe that there are public interest benefits of preserving such direct access by all interested parties, for some defined period, to any Unserved Area in CMA Blocks that are less substantially built out (<E T="03">i.e.,</E>not Substantially Licensed under our proposed test). While site-based application filings would continue to be required for some period going forward in these markets, there is a significantly smaller volume of system modification filings in areas that are less built out.</P>

        <P>15. Additionally, in developing a new model aimed at transitioning the Cellular Service to a geographic-based model, we must keep in mind long-held Commission policies governing spectrum assignment. The Balanced Budget Act of 1997 (BBA) revised the Commission's auction authority by substantially amending sections 309(j)(1) and (2) of the Communications Act of 1934, as amended (Act). (<E T="03">See</E>47 U.S.C. 309(j)(1), (2).) Under section 309(j)(1), with limited exceptions that are not applicable here, the Commission is required to license spectrum through competitive bidding whenever it accepts mutually exclusive applications for initial licenses or permits. The Commission has determined that applications are “mutually exclusive” if the grant of one application would effectively preclude the grant of one or more of the other applications,<E T="03">i.e.,</E>when acceptable, competing applications for the same license are filed. (When, however, the Commission receives only one application that is acceptable for filing for a particular license that is otherwise subject to auction, there is no mutual exclusivity, and thus, the Commission is not required to conduct an auction for that license.) Consistent with the Commission's policy that competitive bidding places licenses in the hands of those that value the spectrum most highly, we believe that it would be in the public interest to adopt the transition described below, which allows the filing of mutually exclusive applications that would be resolved through competitive bidding.</P>

        <P>16. In light of the above-described goals and considerations, we propose to issue CMA-based Overlay Licenses for all Blocks via Stage I and Stage II auctions, thus making immediately available to the Overlay Licensee, for primary service, all Unserved Area remaining in the particular Block as of an established cut-off date. An overlay license is issued for the entire geographic area (in this case, the entire CMA Block), but requires the overlay licensee to provide interference protection to incumbent operations (in this case, Cellular Service incumbents' CGSAs existing as of a certain cut-off date). In Stage I, we would offer Overlay Licenses only for those CMA Blocks that either: (1) As of a certain cut-off date, are Substantially Licensed pursuant to certain benchmarks (described below); or (2) have Cellular service that has been authorized solely under interim operating authority (IOA) (<E T="03">i.e.,</E>for which no primary license has been issued). All other Blocks would remain subject to the current site-based Unserved Area licensing system until we implement Stage II of the transition and offer Overlay Licenses for these remaining CMA Blocks. We seek comment on whether seven years is the appropriate timeframe before initiation of Stage II. As explained below, we propose to exempt from the transition the Gulf of Mexico Service Area (GMSA).</P>

        <P>17. We invite comment on all aspects of our proposals, as well on the expected costs and benefits (to the extent applicable) of operating under our proposal. For example, would the resulting lack of data that would otherwise be collected and available to the public through the Commission's Universal Licensing System and other databases (<E T="03">i.e.,</E>data that is currently available regarding major and minor CGSA modification applications, grants, construction notifications, etc., indicating the location of Cellular<PRTPAGE P="15669"/>Service transmitter sites) constitute a detrimental cost? If so, to what extent? Would the cost be outweighed by the benefits associated with the reduction in regulatory burdens, paperwork, and other aspects of our proposal? By reducing the filing burdens on many Cellular providers, we would expect resulting lower costs for the providers, and in turn, we would expect such lower costs to have a positive effect on service to subscribers. We seek comment on these cost considerations, including quantification of expected savings (in terms of monetary and human resources, for example) resulting from no longer having to submit certain applications once fixed boundaries have been established. We also seek comment on the extent to which expected savings might be passed on to subscribers. We hope these proposals will also promote enhanced competitive options for consumers and we seek comment on any additional steps the Commission could take, in this proceeding, to promote this policy priority.</P>
        <HD SOURCE="HD2">A. Stage I Transition</HD>
        <HD SOURCE="HD3">1. Substantially Licensed CMA Blocks</HD>

        <P>18. We propose to treat a CMA Block as Substantially Licensed if<E T="03">either</E>of the following benchmarks is met: (1) At least 95 percent of the total land area is licensed; or (2) there is no unlicensed parcel within the Block at least 50 contiguous square miles in size. An analysis of Cellular licensed area by Block reflects that only about 20 percent of the 1,468 CMA Blocks are geographically licensed between less than 10 percent up to roughly 94 percent. The vast majority of all Blocks (approximately 80 percent) fall at or above the 95 percent licensed threshold, representing in our view a logical breaking point for inclusion in Stage I of the proposed transition. We also recognize, however, that a Block that has less than 95 percent of its total land area licensed might not have sufficient size parcels of Unserved Area to warrant exclusion from transition in Stage I. Our current rules prohibit a new entrant from applying to serve an area smaller than 50 contiguous square miles. We therefore propose that a Block be deemed Substantially Licensed if it does not have even one remaining unlicensed parcel that is at least 50 contiguous square miles in size, regardless of the percentage of licensed area. (The small number of CMA Blocks in this category does not affect the approximate 80 percent/20 percent split between the Stage I and Stage II Blocks under our proposal.)</P>

        <P>19. Specifically, 601 of the 734 Block A markets appear to meet the proposed test, and 596 of the 734 Block B markets appear to meet the proposed test, for a total of 1,197 of 1,468 Blocks. The maps provided in Appendix D (<E T="03">see</E>full text of the<E T="03">NPRM and Order</E>) illustrate, for each Block, which markets appear to meet the proposed test and which markets, while served, do not.</P>
        <P>20. We propose to include<E T="03">total</E>land area without exclusions in our calculation of licensed area and Unserved Area. We propose to treat government lands differently in this Cellular Service transition, compared to our treatment in the 700 MHz Service, for two reasons. First, the 700 MHz Service “government lands” exclusion was adopted in conjunction with the imposition of aggressive construction benchmarks, which for the first time included mandatory coverage of geography (rather than population). In our proposed Cellular Service transition, the calculation is not based on a consideration of compliance with future construction benchmarks but is solely for purposes of determining whether a CMA Block meets our test for inclusion in Stage I. Second, in our analysis of digitized CGSAs, we observed that Cellular licensees have frequently applied to provide service to federal lands, as the demand for Cellular service has increased in areas such as national parks. We believe that permitting the exclusion of lands that are already being served as part of a Cellular licensee's CGSA would provide inaccurate results as to which markets are in fact Substantially Licensed for purposes of inclusion in the appropriate transition stage.</P>

        <P>21. Through our proposed transition, an Overlay Licensee would not only have the flexibility to extend service into currently Unserved Area, but also would be able to do so without filing modification applications, with limited exceptions. In addition, in the event that all or a portion of an incumbent's CGSA is relinquished by that incumbent (<E T="03">e.g.,</E>through license cancellation, reduction in CGSA, permanent discontinuance of operations, or failure to renew a license), the Overlay Licensee of that CMA Block would no longer be required to protect the relinquished area and could immediately provide service on a primary basis in that area (sometimes known among industry stakeholders as “reversionary rights”). We believe that auctioning, instead, only the remaining Unserved Area in a particular Block without overlay licensing rights could result in incumbents' relinquished areas being held in the Commission's auction inventory and only accessible via a future auction. In contrast, our Overlay License proposal will facilitate prompt service to such areas through reduced administrative burdens.</P>
        <P>22. Under our proposal, just as incumbents that do not become Overlay Licensees would be assured continued protection from harmful interference within their CGSA footprint as of an established cut-off date, they would in turn be obligated to protect the Overlay Licensees from harmful interference. Non-Overlay licensees' CGSA boundaries would be permanently fixed, insofar as such licensees would not be permitted to expand their CGSAs in Blocks included in the auction, except through contractual arrangements with other licensees. To foster secondary market transactions, we propose to continue to allow licensees to partition their CGSAs and/or disaggregate their authorized spectrum, as well as enter into leasing arrangements. We seek comment on this proposal. Non-overlay licensees will also be free to modify their systems in response to market demands without Commission filings, so long as the CGSA would not be expanded (other than through contractual arrangements) or reduced as a result, and subject to any obligations imposed on all licensees. (For example, certain other filings, such as administrative updates, license renewals, and filings required under the rules implementing the National Environmental Policy Act of 1969, as amended (NEPA) would still be required for all licensees.)</P>

        <P>23. We recognize that in Substantially Licensed markets included in our Stage I transition, the new Overlay Licenses awarded in the auction will be heavily encumbered by the incumbents, whose CGSAs would continue to be entitled to protection from harmful interference. A prospective Overlay Licensee would therefore need to be familiar with incumbent operations and should take care to understand how such operations may affect its ability to execute its business plan. Under delegated authority, the Bureau will determine, prior to conducting the auctions, what procedures (if any) are warranted to resolve discrepancies and other anomalies in the licensing data in order to establish definitive boundaries of existing authorized CGSAs as of certain cut-off dates. The Bureau will also issue the appropriate Public Notice(s) regarding such procedures. We recognize that, in some Blocks, the remaining Unserved Area as of the auction date may be very small, fragmented, and/or not immediately servable.<PRTPAGE P="15670"/>
        </P>
        <HD SOURCE="HD3">2. Interim Operating Authority Block (Chambers, Texas, Block A—CMA 672A)</HD>
        <P>24. Chambers, Texas, Block A (Chambers) is the only Block for which a Cellular license has never been issued. AT&amp;T Mobility of Galveston LLC (AT&amp;T Galveston) holds an interim operating authorization and provides Cellular service to nearly all of the area in this Block under Call Sign KNKP971. Notably, neither AT&amp;T nor any other commenter has mentioned this unlicensed market thus far in this proceeding. We propose that Chambers be licensed on a geographic area (CMA Block) basis and that it be included in Stage I described above.</P>
        <P>25. For Chambers, we propose not to apply our existing rules concerning the various build-out and application phases that have been applicable to other Cellular markets. For example, we propose not to subject Chambers to the Phase I or Phase II licensing processes (and because Phase I has terminated for all other CMA Blocks, we are proposing to delete the provisions that address Phase I applications, and references thereto, throughout the part 22 subpart H rules and applicable part 1 rules). As no primary license has ever been issued for Chambers, the initial five-year build-out period that is described in § 22.947 of our rules has never commenced. We propose not to apply to Chambers this five-year build-out period (and because it has expired for all other CMA Blocks, we are proposing to delete the provisions that address the five-year period, and references thereto, throughout the part 22 subpart H rules and applicable part 1 rules). Consistent with our treatment of newly authorized markets in the 700 MHz proceeding, we propose that the Overlay License for Chambers will terminate automatically if the licensee fails to provide signal coverage and offer service over at least 35 percent of the geographic area of its license authorization within four years of initial license grant and to at least 70 percent of the geographic area of its license authorization by the end of the license term. We further propose that, after the build-out requirement has been met, the Chambers Overlay Licensee should be subject to the same rules and obligations that we apply to those that are awarded the Overlay Licenses for all Substantially Licensed Blocks. AT&amp;T Galveston does not have primary authority to operate and would not be afforded incumbent status with respect to any Overlay Licensee resulting from our proposed competitive bidding process.</P>
        <P>26. We believe this proposal provides the most efficient and effective means to foster the provision of additional advanced wireless service by a primary licensee to this Texas market. We also believe that our proposed performance obligations are appropriate given the increased regulatory flexibility afforded any Chambers Overlay Licensee under our transition proposal, including the ability to modify system parameters and expand service without application filings in most instances. In short, we believe that our proposal serves the public interest, and we seek comment on all aspects of the proposal, including any foreseeable costs. Commenters that oppose our proposed approach for Chambers should offer a detailed alternative proposal that is consistent with the goals of this proceeding and the Commission's policies as set forth herein, as well as an analysis of the costs and benefits of the alternative proposal.</P>
        <HD SOURCE="HD2">B. Stage II Transition</HD>
        <P>27. As stated above, based on our preliminary data, approximately 20 percent of all CMA Blocks currently do not meet either of the two benchmarks of our proposed Substantially Licensed test. We believe that the public interest is best served by retaining the existing site-based licensing scheme in these Blocks—primarily Alaska and rural areas out west—to preserve direct access to such area through the Commission's Unserved Area application process during a defined transition period. The reduction in administrative burdens identified above for Stage I markets is substantially smaller for these Blocks that are less built out and have relatively more Unserved Area remaining. In rural areas, service tends to become economically feasible gradually, and modification and new-system applications are filed to a much lesser extent than modification applications in the Blocks that are already substantially built out. Our proposal will allow all interested parties, including new entrants, the opportunity to identify the specific areas they wish to serve as service becomes economically feasible in such markets due to changing demographics, technologies, or other factors. Under our current site-based rules, the one-year construction requirement will ensure prompt build-out of areas in these Blocks where licensees seek authorization to provide service.</P>
        <P>28. We recognize the public interest benefits of having all CMA Blocks under a single geographic area licensing scheme, and therefore we propose to retain the site-based licensing model only for a defined period. Specifically, we propose to continue this model for a period of seven years from the date on which revised Cellular Service rules take effect in this proceeding (Effective Date). We seek comment on our Stage II proposal and specifically on our proposed seven-year transitional time period. While we wish to effectuate prompt build-out in the CMA Blocks that do not currently meet the Substantially Licensed test, we recognize that certain markets may present increased challenges to widespread deployment in the near term. We seek comment on whether seven years is the appropriate timeframe that takes into account the goal of ensuring prompt build-out of systems and economic forces that might delay deployment in certain markets or any alternate proposals commenters may have. We also ask that commenters address the costs and benefits of a seven-year transition period, or for any alternate proposals set forth.</P>
        <P>29.<E T="03">Possible Exception for Alaska.</E>It is likely to be many years before the Alaskan CMA Blocks are substantially built out. We seek comment on whether we should simply retain the<E T="03">status quo</E>site-based scheme for Alaska indefinitely, rather than including it with other Blocks in Stage II. Even if we include Alaska in the proposed transition in Stage II, we seek comment on whether it is appropriate to revise the one-year build-out requirement for Alaska so long as it remains subject to site-based licensing. In addressing these issues, we also seek feedback on the costs and benefits of including Alaska in the Stage II transition, as well as revision to the one-year build-out requirement.</P>
        <P>30.<E T="03">Possible Other Exceptions.</E>We seek comment on whether public interest considerations warrant any exception that we have not considered,<E T="03">e.g.,</E>an especially challenging rural market that might require, for example, an extended build-out period, or another kind of exception altogether. Commenters proposing an exception should include details and supporting rationale consistent with the goals of this proceeding and the Commission's policies as set forth herein.</P>
        <HD SOURCE="HD2">C. Performance Requirements</HD>

        <P>31. We are mindful of our statutory obligation and overarching policy goal of ensuring that the spectrum is used effectively and efficiently to provide valuable services to the American public, including those residing in rural areas, and that the spectrum not be warehoused when it could be deployed using new technologies and services.<PRTPAGE P="15671"/>We also recognize that the Cellular Service has, in most CMAs across the country, already resulted in significant levels of system deployment during the past few decades. Indeed, the level of build-out far exceeds even the most stringent geographic-based construction benchmarks the Commission has imposed on any wireless service to foster public interest goals. In the markets not Substantially Licensed—20 percent of the CMA Blocks—the current level of build-out varies significantly, as discussed above, with most above 70 percent geographic coverage, and a few below 10 percent geographic coverage (<E T="03">e.g.,</E>certain Alaskan CMA Blocks), with the rest somewhere in between.</P>

        <P>32. We seek comment on whether we should adopt any performance benchmarks for Overlay Licenses to promote build-out in areas covered by these licenses where spectrum is unused and the costs and benefits of doing so. If we decide to adopt performance benchmarks, what would the measures be? Would it be appropriate to establish build-out requirements that vary depending on the amount of Unserved Area remaining, or for CMA Blocks that face particular construction challenges (<E T="03">e.g.,</E>Alaska)? In seeking comment, we note that the Commission has never established performance requirements in similar services mandating 100 percent build-out of all areas or population centers in a geographic-based license.</P>
        <P>33. We also seek comment on whether, in place of or in addition to performance build-out requirements, we should require an Overlay Licensee to make unused spectrum available in the secondary market to entities that have need for it. Specifically, we request comment on various possible approaches for facilitating secondary market transactions for use of spectrum that the Overlay Licensee is not using or may not be inclined to use. As one possible approach, we seek comment on whether Overlay Licensees that continue to hold unused spectrum after a certain period of time should be required to make that information publicly available, in some readily accessible and transparent fashion, so that any party interested in using that spectrum can more easily seek to take advantage of the opportunity to gain access to the spectrum. If we were to require the licensee to provide information on unused spectrum, how should this information be made publicly available? We also seek comment on the possible costs and benefits of pursuing this secondary market transparency approach.</P>
        <P>34. As another possible approach, should Overlay Licensees be required to participate in good faith negotiations with a party expressing an interest in spectrum leasing, partitioning, or disaggregating spectrum in a CMA Block? Or, should we consider a modified version of negotiation methodologies employed in other wireless services, possibly involving phases of voluntary negotiations, followed by mandatory negotiations? What are the relative benefits and costs to such an approach in the context of Overlay Licenses?</P>
        <P>35. In considering various approaches, we request that commenters address any difficulties they may have experienced when seeking to access unused spectrum in secondary markets transactions that could inform our decision-making and could improve the workings of secondary markets with respect to unused spectrum associated with Overlay Licenses. Finally, we seek comment on any other approach that commenters may suggest that could facilitate secondary market transactions that help ensure that valuable spectrum resources do not needlessly lie fallow.</P>
        <HD SOURCE="HD2">D. Competitive Bidding Procedures</HD>
        <P>36. As stated above, consistent with the Commission's approach in prior transitions of other services from site-based to geographic area-based overlay licensing, we believe that it serves the public interest to accept competing, mutually exclusive applications in our proposed transition of Cellular licensing that will be resolved by competitive bidding. We reiterate that we are interested in reducing regulatory burdens and affording increased system flexibility (including deployment of broadband service) within fixed boundaries for Cellular licensees, but in a manner that is consistent with Commission precedent and spectrum management policies. No commenter has offered a justification for departing from a transition approach under which we accept mutually exclusive applications. Competitive bidding should place Cellular Overlay Licenses in the hands of those that value them most.</P>

        <P>37. In other competing commercial wireless services, the Commission implemented geographic-based licensing, rather than a site-based model, from the inception of the radio service, particularly in PCS, the Advanced Wireless Service (AWS), and the 700 MHz Service. In these radio services, the existing incumbents (<E T="03">e.g.,</E>microwave, government, and broadcasters) were to be relocated. In other commercial wireless services where incumbents were originally licensed on a site-by-site basis but were permitted to remain in the band, the Commission also chose to transition to geographic-based overlay licensing including, for example, the 800 MHz specialized mobile radio service, the 220 MHz private land mobile radio service, and the 929-931 MHz paging services. In each instance, the Commission determined that the geographic-area licensing model afforded licensees increased flexibility to construct and operate facilities within a larger geographic area and commence operations without prior Commission approval, thereby reducing regulatory burdens.</P>
        <P>38. In the event we adopt our proposal for a transition entailing competitive bidding, we propose to apply the general competitive bidding rules set forth in part 1, subpart Q of the Commission's rules, substantially consistent with the bidding procedures that have been employed in previous auctions. Specifically, we propose to employ the Part 1 rules governing competitive bidding design, designated entity preferences, unjust enrichment, application and payment procedures, reporting requirements, and the prohibition on certain communications between auction applicants. Under this proposal, such rules would be subject to any modifications that the Commission may adopt in the future. In addition, consistent with our long-standing approach, auction-specific matters such as the competitive bidding design and mechanisms, as well as minimum opening bids and/or reserve prices, would be determined by the Bureau pursuant to its delegated authority. We invite comment on this proposal. In particular, we request comment on whether any of our part 1 competitive bidding rules or other auction procedures would be inappropriate or should be modified for an auction of Cellular licenses in the context of this proceeding.</P>
        <P>39.<E T="03">Provisions for Designated Entities.</E>In authorizing the Commission to use competitive bidding, Congress mandated that the Commission “ensure that small businesses, rural telephone companies, and businesses owned by members of minority groups and women are given the opportunity to participate in the provision of spectrum-based services.” In addition, section 309(j)(3)(B) of the Act provides that, in establishing eligibility criteria and bidding methodologies, the Commission shall promote “economic opportunity and competition . . . by avoiding excessive concentration of licenses and by disseminating licenses among a wide<PRTPAGE P="15672"/>variety of applicants, including small businesses, rural telephone companies, and businesses owned by members of minority groups and women.” One of the principal means by which the Commission fulfills these mandates is through the award of bidding credits to small businesses. The Commission's experience with numerous auctions has demonstrated that bidding credits for designated entities afford such entities substantial opportunity to compete with larger businesses for spectrum licenses and provide spectrum-based services.</P>
        <P>40. The Commission has stated that it would define eligibility requirements for small businesses on a service-specific basis, taking into account the capital requirements and other characteristics of each particular service in establishing the appropriate threshold. Although it has standardized many of its auction rules, the Commission has determined that it will continue a service-by-service approach to defining small businesses.</P>
        <P>41. We propose to employ the following three small business definitions for auctions of these licenses. We seek comment on whether we should define an entrepreneur as an entity with average gross revenues for the preceding three years not exceeding $40 million, a small business as an entity with average gross revenues for the preceding three years not exceeding $15 million, and a very small business as an entity with average gross revenues for the preceding three years not exceeding $3 million. As provided in § 1.2110(f)(2) of our rules, we seek comment on whether we should offer entrepreneurs a bidding credit of 15 percent, small businesses a bidding credit of 25 percent, and very small businesses a bidding credit of 35 percent. Commenters are encouraged to provide feedback on the costs and benefits of these proposed definitions and bidding credit designations. We also invite input on whether alternative size standards should be established in light of the particular circumstances or requirements that may apply to the proposed Cellular Overlay Licenses. Commenters advocating alternatives should explain the basis for their proposed alternatives, including whether anything about the characteristics or capital requirements of providing Cellular service or other considerations require a different approach, as well as the costs and benefits of the alternatives.</P>
        <HD SOURCE="HD2">E. Gulf of Mexico Service Area</HD>

        <P>42. Cellular service in the Gulf of Mexico Service Area (GMSA) (CMA Blocks 306A and 306B) is subject to special licensing rules. The GMSA is divided by rule into two zones: the Coastal Zone (GMCZ) in the Eastern Gulf region and the Exclusive Zone (GMEZ). The existing Cellular licensing regime for the GMSA was carefully developed by the Commission after taking into account many prior disputes between Gulf-based and adjacent land-based carriers, multiple prior Commission decisions, court litigation and judicial rulings, as well as the unique circumstances of providing Cellular service in the Gulf region. We propose not to alter the existing regime, except that we propose to subject GMSA licensees to our proposed field strength limit, discussed below. We also believe that GMSA licensees may benefit from certain other rule changes proposed in the<E T="03">NPRM.</E>We seek comment on our proposed exemption of the GMSA from a Cellular licensing transition at this time, including comment on which (if any) individual rule changes should be applied to GMSA licensees.</P>
        <HD SOURCE="HD2">F. Signal Field Strength Limit Proposal</HD>

        <P>43. The Commission believes that a median field strength limit of 40 dBμV/m is appropriate for the Cellular Service and proposes that all Cellular licensees be subject to this limit in all CMA Blocks. With an established field strength limit applicable to all Cellular licensees, the current rule governing Service Area Boundary (SAB) extensions (<E T="03">see</E>47 CFR 22.912) would be unnecessary, even in those CMA Blocks that remain subject to the current site-based licensing rules for Unserved Area. In the latter class of CMA Blocks, however, SABs and CGSAs (for new systems and expansions of existing systems) would still be calculated under the provisions currently set forth in § 22.911. We seek comment on our proposal.</P>
        <P>44. An appropriate field strength limit allows a licensee to transmit at a signal strength sufficient to provide reliable service right up to the license boundary, while preventing the licensee from transmitting at a signal strength that is excessive for that purpose. Having a 47 dBμV/m field strength limit for PCS, for example, has worked effectively as a limit on the amount of signal incursion a licensee may have into an adjacent licensed area, and we believe that a 40 dBμV/m field strength limit will be similarly effective for the Cellular Service. We do not anticipate a notable increase in boundary disputes if we adopt our proposal. There is no evidence of a causal relationship between boundary disputes and a field strength limit if the limit applies equally to all licensees in a given service.</P>
        <P>45. We believe that co-channel licensees are in the best position to negotiate placement and parameters of facilities near the boundary of another licensee's protected area, taking into account the factors unique to their systems and the area involved, including, for example, technologies, traffic loading, topography, and location of major roads. Thus, consistent with the PCS field strength limit rules, we also propose to allow Cellular licensees to negotiate contractual agreements specifying field strength limits different from the limit established by rule. We emphasize, however, that Commission rules do not allow licensees to agree to transmit their signals at a power level that is higher than the applicable power limit set forth in the rules.</P>
        <P>46. Even with full compliance with the proposed field strength limit, licensees operating in proximity to each other will still need to coordinate channel usage in order to avoid mutually destructive interference. Section 22.907 of our rules requires that interference problems (and any possible problems with traffic capture) in the Cellular Service be avoided by coordination between or among licensees. We propose to retain the requirements for mandatory coordination that are currently set forth in § 22.907.</P>
        <P>47. We encourage parties to address all aspects of our proposal concerning a field strength limit and continued mandatory licensee coordination. Interested parties that offer a counter-proposal, whether for a different field strength limit or non-use of any signal field strength limit, should be specific and explain how their proposal better serves the public interest, including whether it would be more cost effective.</P>
        <HD SOURCE="HD2">G. Other Alternatives to the Commission's Proposed Transition</HD>
        <P>48.<E T="03">Single-stage Transition for All Blocks.</E>We seek comment on the possibility of eliminating the site-based licensing scheme and transitioning expeditiously, via a<E T="03">single</E>auction, all CMA Blocks to a geographic-based model. Commenters should address the impact of such a proposal on rural service and rural interests in particular, given that once an Overlay License is offered at auction, the Unserved Area in that particular Block would no longer be available under site-based licensing, even if the Overlay License returns to the Commission for re-licensing. For example, if there is no successful bidder at auction, or if a successful bidder is awarded the Overlay License but then, years later, fails to renew, the only methodology for re-licensing is to offer<PRTPAGE P="15673"/>the Overlay License again at a subsequent Commission auction. We seek comment on these considerations under this alternate approach.</P>
        <P>49.<E T="03">A Three-Stage Transition.</E>As another alternative, we could subdivide the Blocks that do not now meet the Substantially Licensed test into two groups, as there may be some markets that need even more time, such as those in Alaska and other very rural areas with similar construction challenges, resulting in a third stage in the Cellular licensing transition. We seek specific comment on this approach as well. For example, what benchmarks should be used to distinguish the Stage II Blocks from the Stage III Blocks, and what is the basis for choosing such benchmarks? What would be an appropriate dividing line in terms of licensed area? What should the trigger dates be for Stage II and Stage III, and what would be the rationale? We also seek comment on whether all Blocks with unique construction challenges should be subject to an extended build-out requirement while they remain under the site-based licensing regime.</P>
        <P>50.<E T="03">Other Alternatives.</E>We also welcome submission of alternatives that we have not considered herein. Commenters who oppose our two-stage proposal and advocate an alternative need to address details of implementation and should demonstrate how their alternative serves the public interest and is cost effective.</P>
        <HD SOURCE="HD2">H. Proposed Amendments to Rules and Possible Rule Relocation</HD>
        <HD SOURCE="HD3">1. Proposed Amendments</HD>
        <P>51.<E T="03">Transition-related proposed amendments.</E>Proposed new and revised rules to reflect the proposed two-stage transition of Cellular licensing are set forth in Appendix E of the<E T="03">NPRM and Order.</E>We urge all parties to review Appendix E closely and submit detailed comments. Our proposals introduce some new terminology, including for incumbent operations, and we also propose revisions and some deletions regarding the definitions in § 22.99.</P>
        <P>52.<E T="03">Other Deletions and Updates.</E>Although we are not proposing immediate fundamental changes to the rules for CMA Blocks that are not to be included in the Stage I transition (except for the proposed establishment of a signal field strength limit), we have reviewed all the subpart H rules as well as certain part 1 rules applicable to Cellular licensing in an effort to streamline or update them, and we propose certain changes. We have also reviewed these rules to determine whether any should be deleted as obsolete or, going forward, no longer necessary. For example, we believe that certain items required under §§ 22.929 and 22.953(a) of our rules will no longer be routinely of interest to the Commission's engineering staff in their review of Cellular applications in the future, and accordingly, we propose to streamline these requirements in a revised § 22.953 (and a corresponding deletion of § 22.929). In addition, we discuss below a proposal regarding § 22.901(b). The results of our review are reflected in the proposed rules set forth in Appendix E of the<E T="03">NPRM and Order.</E>We invite all commenters to review each of the proposed revisions, additions, and deletions and comment on them with specificity. If there are other rules that commenters believe should be revised, deleted or added as part of our effort to streamline and update the rules that govern Cellular licensees, we welcome suggestions regarding such revisions. Commenters should be specific in their proposals, providing proposed language for the rule itself as well as the rationale for the change.</P>
        <P>53.<E T="03">AMPS Sunset Certifications: Termination of Collection; Deletion of Section 22.901(b).</E>On June 15, 2007, the Commission released an Order declining to extend the sunset of the Cellular analog service requirement set forth in § 22.901(b) of our rules.<E T="03">See</E>22 FCC Rcd 11243 (2007). Pursuant to such<E T="03">2007 AMPS Sunset Order,</E>on November 16, 2007, the Bureau released a Public Notice (<E T="03">see</E>22 FCC Rcd 19922 (WTB 2007)) with instructions for Cellular licensees on how to file a one-time Cellular Coverage Certification (AMPS Sunset Certification), which would certify that discontinuance of analog service would not result in any loss of wireless coverage throughout the CGSA. By filing an AMPS Sunset Certification, licensees could preserve the rights associated with their previously determined CGSAs on file with the Commission as of the AMPS Sunset Certification's filing date. The overwhelming majority of Cellular licensees have opted to file an AMPS Sunset Certification. We believe that all Cellular licensees have had ample time—more than four years since the<E T="03">AMPS Instructions Notice</E>—to make their choice and file either the one-time AMPS Sunset Certification or the appropriate revised CGSA showing. Accordingly, we propose to terminate the Commission's collection of such Certifications and to delete § 22.901(b). We welcome comment on these proposals.</P>
        <HD SOURCE="HD3">2. Possible Relocation of Part 22 Cellular and Part 24 PCS Rules to Part 27</HD>
        <P>54. In light of our proposal to revise the Cellular licensing rules to bring them in line with the more flexible rules that govern other wireless services, we take this opportunity to invite comment on placement of revised rules that may ultimately be adopted in this proceeding. Specifically, in the event that we adopt a geographic area regime that includes Overlay Licenses, should the new Cellular rules be incorporated into part 27, which houses the existing rules for certain other flexible wireless services, such as AWS, rather than in subpart H of part 22? If the revised Cellular rules are to be incorporated into part 27, we believe that the rules for part 24 PCS—which is already a flexible service governed by geographic area-based licensing—should then also be moved into part 27. Should the Commission initiate a separate rulemaking to revise the part 27 rules and reserve the possible relocation of Cellular and PCS rules to that separate proceeding? We welcome comment on such relocations and the optimal timing for them.</P>
        <HD SOURCE="HD3">3. Proposed Correction of Section 1.958(d)</HD>

        <P>55. We take this opportunity to propose correction of a clerical error in the distance computation formula in § 1.958(d) of our rules. The error was introduced in the process of moving the provision containing the formula from part 22 (§ 22.157) to subpart F of part 1. The proposed correction is included in Appendix E of the<E T="03">NPRM and Order.</E>
        </P>
        <HD SOURCE="HD1">IV. Order</HD>

        <P>56. To facilitate the orderly and effective resolution of the fundamental changes and issues raised in the<E T="03">NPRM,</E>and consistent with our actions in numerous prior proceedings, the Commission adopts a companion<E T="03">Order</E>on February 15, 2012 in which it imposes an immediate freeze on the acceptance of certain Cellular applications in certain markets, as explained below, and imposes other interim procedures for certain Cellular applications, as also explained below. The Commission's decision to impose a freeze and other interim procedures is procedural and therefore not subject to the notice and comment or effective date requirements of the Administrative Procedure Act. (<E T="03">See</E>5 U.S.C. 553(b)(A), (d).<E T="03">See also, e.g., Bachow Communications, Inc.</E>v.<E T="03">FCC, 237 F.3d 683 (D.C. Cir. 2001)).</E>The tailored freeze and other interim procedures are<PRTPAGE P="15674"/>effective as of February 15, 2012 until further notice.</P>
        <HD SOURCE="HD2">A. Suspension of Certain Filings</HD>
        <P>57. Rather than imposing a freeze on all modification and new-system applications, the Commission has tailored the freeze in this proceeding to: (1) provide for the continued expansion of service to consumers during the pendency of this proceeding; and (2) help the Commission identify Unserved Area and inform potential bidders of encumbrances well in advance of the auction. A tailored freeze will facilitate much needed network changes. We conclude that the benefits described above outweigh the limited potential costs of this tailored freeze.</P>

        <P>58. As of the Adoption Date (February 15, 2012) and until further notice, we have suspended acceptance of certain Cellular applications claiming Unserved Area in “Covered” CMA Blocks. We wish to allow licensees to continue limited expansion of existing systems necessary to respond to customer needs by addressing technical changes at the periphery of their current CGSAs without facing strike applications,<E T="03">i.e.,</E>applications filed primarily to block such service during a transition to geographic area licensing. Moreover, accepting and processing all applications in the normal course under our current rules would arguably be inconsistent with our goal of changing to a less burdensome licensing system.</P>

        <P>59. Covered Blocks include: (i) Those we preliminarily determine to be Substantially Licensed under either benchmark of our proposed test (listed in Appendix C of the<E T="03">NPRM and Order</E>); and (ii) those we preliminarily determine to be more than 90 percent but less than 95 percent licensed (listed in Appendix F of the<E T="03">NPRM and Order</E>). In Covered Blocks, we prohibit the filing of applications for: (a) new-system Cellular licenses; and (b) major modifications to expand existing systems if claiming Unserved Area that is not contiguous to the existing CGSA. The prohibition applies even if a portion of the area to be claimed as CGSA lies in a non-Covered Block. Thus, for example, if a proposed new-system or major modification application proposes to claim (as CGSA) Unserved Area that straddles a CMA boundary, where the CMA Block on one side of the boundary is Covered while the Block on the other side of the boundary is non-Covered, the entire application will be treated as if solely for Unserved Area in a Covered Block. Any applications prohibited under the<E T="03">Order</E>that are received on or after the Adoption Date are to be dismissed by the Bureau as unacceptable for filing.</P>
        <P>60. We are permitting major modification applications that propose CGSA expansion in, or into, Covered Blocks only if claiming Unserved Area that is contiguous to the existing CGSA. (If an application proposes to claim (as CGSA) contiguous Unserved Area that is partially in a Covered Block and partially in a non-Covered Block, the application will be treated as if the entire claimed area is in a Covered Block.) Also, as of the Adoption Date and until further notice, we are using a “same-day filing group” for purposes of determining mutual exclusivity of permissible Cellular applications that entail Unserved Area in Covered Blocks. We will dismiss any mutually exclusive applications claiming Unserved Area in Covered Blocks that are received on or after the Adoption Date rather than conduct closed auctions to resolve such applications. We will permit major amendments to permissible major modification applications only so long as the proposed CGSA expansion in the amendment is claiming Unserved Area that is contiguous to the existing licensed CGSA. (If the amendment proposes to claim (as CGSA) contiguous Unserved Area that is partially in a Covered Block and partially in a non-Covered Block, it will be treated as if the entire claimed area is in a Covered Block.) Also, for such major amendments filed on or after the Adoption Date and until further notice, we will use a “same-day filing group” for purposes of determining mutual exclusivity, and we will dismiss any such mutually exclusive major amendments rather than conduct closed auctions to resolve them.</P>

        <P>61. These interim filing procedures do not affect applications claiming Unserved Area solely in non-Covered CMA Blocks, which we will continue to accept and process under current rules and procedures, nor do they affect any applications that do not propose a new Cellular system or a CGSA expansion (<E T="03">e.g.,</E>renewals, transfers, assignments, modifications that do not extend a CGSA boundary, administrative updates, and required notifications), no matter the Block. Applications for renewal must comply with any applicable provisions of the Notice of Proposed Rulemaking released by the Commission in the Wireless Radio Services (WRS) proceeding in May 2010. (<E T="03">See generally WRS NPRM, 25 FCC Rcd 6996 (2010).</E>
          <E T="03">See also</E>47 CFR 1.939.) We advise all parties, however, that although minor modification applications (regardless of market) are not affected by the freeze imposed under this<E T="03">Order,</E>we know from experience that staff might find on review that a purported minor modification application submitted on or after the Adoption Date is in fact a major modification application. If such an application is for Unserved Area (in whole or in part) in a Covered CMA Block, the application will be subject to the same procedures and restrictions described above (including dismissal if an impermissible filing under this<E T="03">Order</E>).</P>
        <P>62. In the following Section B, we discuss how we will process currently pending new-system and CGSA-expansion applications in Covered CMA Blocks.</P>
        <HD SOURCE="HD2">B. Currently Pending Non-Mutually Exclusive Applications in Covered CMA Blocks</HD>
        <P>63.<E T="03">New-System and Major Modification Applications.</E>Currently pending applications (<E T="03">i.e.,</E>filed prior to the Adoption Date) that propose either a new Cellular system or a modification that would expand an existing system's CGSA boundary in, or into, Covered CMA Blocks fall into one of two categories: (1) Those accepted for filing and placed on public notice at least 30 days before the Adoption Date; and (2) those for which the 30-day public comment period has not yet expired as of the Adoption Date. We will treat non-mutually exclusive applications in the first category (including pending applications that would be impermissible under this<E T="03">Order</E>if filed on or after the Adoption Date) under existing rules and will process them in the normal course as expeditiously as possible, subject to certain interim procedures regarding major amendments. Specifically, for pending modification applications proposing expansion of an existing CGSA, we will permit major amendments on or after the Adoption Date subject to the same interim procedures described above in Section IV.A. For pending new-system applications, we will permit major amendments on or after the Adoption Date only so long as the proposed new-system CGSA in the amendment is claiming Unserved Area that is contiguous to the CGSA proposed in the application that was pending as of the Adoption Date. (If an application proposes to claim (as CGSA) contiguous Unserved Area that is partially in a Covered Block and partially in a non-Covered Block, the application will be treated as if the entire claimed area is in a Covered Block.) For such amendments, we will use a “same-day filing group” for purposes of determining mutual exclusivity, and we<PRTPAGE P="15675"/>will dismiss any such mutually exclusive major amendments claiming Unserved Area in Covered Blocks that are received on or after the Adoption Date rather than conduct closed auctions to resolve them. On balance, rather than holding them in abeyance until conclusion of this proceeding, we concluded that processing pending applications in the first category under existing rules, subject to the interim procedures described herein, will not sacrifice the goals we seek to accomplish in this proceeding.</P>

        <P>64. Pending new-system and major modification applications in the second category (<E T="03">i.e.,</E>filed prior to the Adoption Date but for which the 30-day comment period has not expired) claiming any Unserved Area in Covered CMA Blocks will be deemed mutually exclusive only if a competing application was filed prior to the adoption date of the<E T="03">Order.</E>Applications in the second category that are not mutually exclusive will be processed under our current rules, except that we will only permit the filing of major amendments subject to the same interim procedures described above regarding major amendments to applications in the first category.</P>
        <P>65.<E T="03">Minor Modifications.</E>As explained above, applications submitted as minor modifications of an existing CGSA are sometimes found by staff to be major modification applications. During the pendency of this proceeding, a minor modification application submitted prior to the Adoption Date that is determined to be proposing a major modification claiming (as CGSA) Unserved Area in a Covered Block will be treated the same as a pending major modification application in accordance with the interim procedures described above.</P>
        <HD SOURCE="HD1">V. Procedural Matters</HD>
        <HD SOURCE="HD2">A. Ex Parte Rules—Permit-But-Disclose</HD>
        <P>66. The proceeding that the<E T="03">NPRM</E>initiates shall be treated as a “permit-but-disclose” proceeding in accordance with the Commission's<E T="03">ex parte</E>rules. Persons making<E T="03">ex parte</E>presentations must file a copy of any written presentation or a memorandum summarizing any oral presentation within two business days after the presentation (unless a different deadline applicable to the Sunshine Period applies). Persons making oral<E T="03">ex parte</E>presentations are reminded that memoranda summarizing the presentation must (1) list all persons attending or otherwise participating in the meeting at which the<E T="03">ex parte</E>presentation was made, and (2) summarize all data presented and arguments made during the presentation. If the presentation consisted in whole or in part of the presentation of data or arguments already reflected in the presenter's written comments, memoranda or other filings in the proceeding, the presenter may provide citations to such data or arguments in his or her prior comments, memoranda, or other filings (specifying the relevant page and/or paragraph numbers where such data or arguments can be found) in lieu of summarizing them in the memorandum. Documents shown or given to Commission staff during<E T="03">ex parte</E>meetings are deemed to be written<E T="03">ex parte</E>presentations and must be filed consistent with § 1.1206(b). In proceedings governed by § 1.49(f) or for which the Commission has made available a method of electronic filing, written<E T="03">ex parte</E>presentations and memoranda summarizing oral<E T="03">ex parte</E>presentations, and all attachments thereto, must be filed through the electronic comment filing system available for that proceeding, and must be filed in their native format (<E T="03">e.g.,</E>.doc, .xml, .ppt, searchable .pdf). Participants in this proceeding should familiarize themselves with the Commission's<E T="03">ex parte</E>rules.</P>
        <HD SOURCE="HD2">B. Comment Period and Procedures</HD>

        <P>67. Pursuant to §§ 1.415 and 1.419 of the Commission's rules, interested parties may file comments and reply comments on or before the dates indicated on the first page of this document.<E T="03">All comments and reply comments should refer to WT Docket No. 12-40.</E>Comments may be filed using the Commission's Electronic Comment Filing System (ECFS).</P>
        <P>
          <E T="03">Electronic Filers:</E>Comments may be filed electronically using the Internet by accessing the ECFS:<E T="03">http://fjallfoss.fcc.gov/ecfs2/.</E>
        </P>
        <P>
          <E T="03">Paper Filers:</E>Parties who choose to file by paper must file an original and one copy of each filing.</P>
        <P>Filings can be sent by hand or messenger delivery, by commercial overnight courier, or by first-class or overnight U.S. Postal Service mail. All filings must be addressed to the Commission's Secretary, Office of the Secretary, Federal Communications Commission.</P>

        <P>All hand-delivered or messenger-delivered paper filings for the Commission's Secretary must be delivered to FCC Headquarters at 445 12th St. SW., Room TW-A325, Washington, DC 20554. The filing hours are 8 a.m. to 7 p.m. All hand deliveries must be held together with rubber bands or fasteners. Any envelopes and boxes must be disposed of<E T="03">before</E>entering the building.</P>
        <P>Commercial overnight mail (other than U.S. Postal Service Express Mail and Priority Mail) must be sent to 9300 East Hampton Drive, Capitol Heights, MD 20743.</P>
        <P>U.S. Postal Service first-class, Express, and Priority mail must be addressed to 445 12th Street SW., Washington DC 20554.</P>

        <P>68. People with Disabilities: To request materials in accessible formats for people with disabilities (Braille, large print, electronic files, audio format), send an email to<E T="03">fcc504@fcc.gov</E>or call the Consumer &amp; Governmental Affairs Bureau at 202-418-0530 (voice), 202-418-0432 (tty).</P>
        <HD SOURCE="HD3">Initial Regulatory Flexibility Analysis of the Notice of Proposed Rulemaking and Order</HD>

        <P>69. As required by the Regulatory Flexibility Act of 1980, as amended (RFA), the Commission has prepared this Initial Regulatory Flexibility Analysis (IRFA) of the possible significant economic impact on a substantial number of small entities by the policies and rules proposed in the<E T="03">NPRM.</E>Written public comments are requested on this IRFA. Comments must be filed by the same dates as listed on the first page of the<E T="03">NPRM</E>and must have a separate and distinct heading designating them as responses to this IRFA. The Commission will send a copy of the NPRM, including this IRFA, to the Chief Counsel for Advocacy of the Small Business Administration (SBA). In addition, the<E T="03">NPRM</E>and IRFA (or summaries thereof) will be published in the<E T="04">Federal Register</E>.</P>
        <HD SOURCE="HD3">Need for, and Objectives of, the Proposed Rules</HD>
        <P>70. In the<E T="03">NPRM,</E>the Commission proposes a transition for the 800 MHz Cellular (Cellular) Service from site-based licensing to geographic-area licensing. The proposed transition would occur in two stages, via Commission auction. We believe that the current site-based paradigm is outdated and hinders carriers from being able to respond quickly to changing market conditions and consumer demands. We also believe it is contrary to the public interest to maintain a burdensome system to preserve extremely limited Unserved Area licensing opportunities. The Commission's early key goal of creating a seamless and integrated nationwide Cellular Service has been achieved throughout the vast majority of our nation. The Commission has long held that market-based licensing regimes are<PRTPAGE P="15676"/>simpler to administer for all parties concerned. The proposed transition would reduce administrative burdens for licensees as well as Commission staff. The proposed transition is consistent with the Commission's ongoing regulatory reform agenda and also supports the Commission's Data Innovation Initiative, launched in June 2010, by reducing information collection burdens under the Paperwork Reduction Act. We anticipate that, with the proposed additional flexibility provided to licensees, the regulatory and compliance costs associated with service provision would be reduced. These changes would also put Cellular licensees more on par with other wireless telecommunications licensees and further the Commission's goal of rule harmonization for the different wireless services.</P>

        <P>71. As detailed in Section III, we propose a transition in two stages. Consistent with precedent, we would accept competing applications for Overlay Licenses, and resolve them via auction, for each CMA Block. In Stage I, the Commission would offer Overlay Licenses for all CMA Blocks that are “Substantially Licensed” or authorized solely under interim operating authority (IOA). We propose the following test to determine if a CMA Block is Substantially Licensed:<E T="03">either</E>(1) at least 95 percent of the total land area in the CMA Block is licensed;<E T="03">or</E>(2) there is no parcel within the Block at least 50 contiguous square miles in size that is not licensed. We believe it is appropriate to include<E T="03">total</E>land area without exclusions in calculating the licensed area. If a CMA Block meets either benchmark as of an established date, it would be deemed Substantially Licensed and included in the Stage I transition. We propose, however, that the Gulf of Mexico Service Area (GMSA) be exempt from the transition because it is governed by a specialized licensing regime.</P>

        <P>72. All CMA Blocks that do not meet the Substantially Licensed test would remain under site-based licensing until Stage II is triggered. In Stage II, the Commission proposes to offer Overlay Licenses for all remaining CMA Blocks (except the GMSA), regardless of the percentage of total land area licensed, and terminate site-based licensing. In the<E T="03">NPRM,</E>we propose to continue the site-based model for seven years before Stage II is triggered, and we seek comment on whether this is the appropriate period of time. We believe that the public interest is best served by preserving the current scheme's direct spectrum access through site-based applications in Blocks that are not yet Substantially Licensed, primarily rural areas out west, for a defined period of time. This will allow all interested parties to have the opportunity to identify the specific areas they wish to serve as demographics change or service otherwise becomes economically feasible in such markets. Moreover, site-based licensing in such Blocks will ensure build-out within one year of authorization of such areas.</P>

        <P>73. Overlay Licensees would be obligated to protect incumbent licensees' operations from harmful interference. That obligation would cease with respect to any incumbent's licensed area relinquished for any reason in the future (<E T="03">e.g.,</E>through failure to renew the license). Such relinquished areas would not be returned to the Commission's auction inventory but, rather, could by served immediately by the Overlay Licensee on a primary basis without being subject to competitive bidding.</P>
        <P>74. The Chambers, Texas Block-A market (Chambers) is the only CMA Block for which a license has never been issued; the market is served solely under IOA. We propose to include Chambers in the Stage I auction and award an Overlay License consistent with the process described for the Substantially Licensed Blocks, but subject to specific build-out requirements for the Chambers Overlay Licensee, as explained in Section III.A.2. We believe this is the most efficient and effective way to resolve the continued lack of a licensee and help bring additional advanced service to this Texas market.</P>

        <P>75. We also propose that all Cellular licensees, regardless of Block, should be subject to a field strength limit at their respective license boundaries, similar to licensees in other flexible services such as PCS, certain AWS, etc. The<E T="03">NPRM</E>proposes a median field strength limit of 40 dBμV/m for the Cellular Service. We also propose certain other revisions in individual Cellular rules to reflect the proposed transition, and to delete provisions that we deem obsolete or unnecessary going forward, including certain application requirements and other filings, and to streamline certain other provisions. The proposed rules are set forth in Appendix E and we encourage all interested parties to review them carefully. We seek comment on how the proposals will impact the amount of information available to regulated entities and the public.</P>
        <HD SOURCE="HD3">Legal Basis</HD>
        <P>76. The proposed action is taken under sections 1, 2, 4(i), 301, 303, 307, 309, 319, 324, and 332 of the Communications Act of 1934, as amended, 47 U.S.C. 151, 152, 154(i), 301, 303, 307, 309, 319, 324, and 332.</P>
        <HD SOURCE="HD3">Description and Estimate of the Number of Small Entities to Which the Proposed Rules Will Apply</HD>
        <P>77. The RFA directs agencies to provide a description of and, where feasible, an estimate of the number of small entities that may be affected by the proposed rules, if adopted. The RFA generally defines the term “small entity” as having the same meaning as the terms “small business,” “small organization,” and “small governmental jurisdiction.” In addition, the term “small business” has the same meaning as the term “small business concern” under the Small Business Act. A small business concern is one which: (1) Is independently owned and operated; (2) is not dominant in its field of operation; and (3) satisfies any additional criteria established by the SBA.</P>
        <P>78.<E T="03">Small Businesses, Small Organizations, and Small Governmental Jurisdictions.</E>Our action may, over time, affect small entities that are not easily categorized at present. We therefore describe here, at the outset, three comprehensive, statutory small entity size standards. First, nationwide, there are a total of approximately 27.5 million small businesses, according to the SBA. In addition, a “small organization” is generally “any not-for-profit enterprise which is independently owned and operated and is not dominant in its field.” Nationwide, as of 2007, there were approximately 1,621,315 small organizations. Finally, the term “small governmental jurisdiction” is defined generally as “governments of cities, towns, townships, villages, school districts, or special districts, with a population of less than fifty thousand.” Census Bureau data for 2011 indicate that there were 89,476 local governmental jurisdictions in the United States. We estimate that, of this total, as many as 88,506 entities may qualify as “small governmental jurisdictions.” Thus, we estimate that most governmental jurisdictions are small.</P>
        <P>79.<E T="03">Wireless Telecommunications Carriers (except Satellite).</E>The appropriate size standard under SBA rules is for the category Wireless Telecommunications Carriers. The size standard for that category is that a business is small if it has 1,500 or fewer employees. Census Bureau data for 2007, which now supersede data from the 2002 Census, show that there were 3,188 firms in this category that operated for the entire year. Of this<PRTPAGE P="15677"/>total, 3,144 had employment of 999 or fewer, and 44 firms had employment of 1,000 employees or more. Thus, under this category and the associated small business size standard, the Commission estimates that the majority of wireless telecommunications carriers (except satellite) are small entities that may be affected by our proposed action. The Commission's own data—available on its Spectrum Dashboard—indicate that, as of February 9, 2012, there are 347 Cellular licensees that will be affected by this<E T="03">NPRM.</E>The Commission does not know how many of these licensees are small, as the Commission does not collect that information for these types of entities.</P>
        <HD SOURCE="HD3">Description of Projected Reporting, Recordkeeping, and Other Compliance Requirements</HD>
        <P>80. In the<E T="03">NPRM,</E>the Commission seeks to reduce filing burdens and recordkeeping for all Cellular licensees by changing from site-based to geographic area licensing. We propose that, in the Blocks for which an Overlay License is offered, the CGSA boundaries of incumbents that do not become Overlay Licensees would be permanently fixed insofar as such incumbents would not be permitted to expand their CGSAs, except through contractual arrangements with other licensees. They would, however, be free to modify their systems in response to market demands without Commission filings in most cases, so long as the CGSA would not be changed as a result, and subject to any obligations we impose on all Cellular licensees.</P>

        <P>81. Under our proposal, in most cases Overlay Licensees would be free as well to modify their systems without Commission filings, thereby minimizing their regulatory burdens. In addition, while Overlay Licensees would be obligated to protect incumbent licensees' operations from harmful interference, that obligation would cease with respect to any incumbent's licensed area (CGSA) or portion thereof that is relinquished for any reason in the future (<E T="03">e.g.,</E>through failure to renew the license). Such relinquished areas would not be returned to the Commission's auction inventory but, rather, could be served by the Overlay Licensee on a primary basis immediately, without being subject to competitive bidding.</P>

        <P>82. Once an Overlay License is granted via auction for Chambers, we propose not to subject the Licensee to the existing rules concerning the five-year build-out phase or the Phase I or Phase II license application processes that have been applicable to other CMA Blocks. Instead, we propose that the Chambers Overlay Licensee be required to demonstrate that it has built out a Cellular system that is providing signal coverage and offering service over at least 35 percent of the geographic area of its license authorization within four years of initial license grant and at least 70 percent of the geographic area of its license authorization by the end of the license term, with failure to meet these build-out deadlines resulting in automatic forfeiture of the license. We further propose that, after the build-out requirements have been met, the Chambers Overlay Licensee should be subject to the same rules and obligations that we apply to the other Overlay Licenses issued in Stage I of the transition. For example, we seek comment in the<E T="03">NPRM</E>on whether Overlay Licensees should be subject to performance requirements.</P>
        <P>83. The Commission also proposes that all Cellular licensees be subject to a field strength limit at their respective license boundaries and that a median field strength limit of 40 dBµV/m is appropriate for the Cellular Band. Coordination among co-channel licensees regarding channel usage will remain essential in actually preventing harmful interference. We therefore propose to retain the current Cellular Service rule mandating coordination in certain circumstances (§ 22.907), but we also propose to allow Cellular licensees to negotiate contractual agreements specifying different field strength limits. This will provide licensees with additional flexibility in their operations.</P>
        <P>84. In the<E T="03">NPRM,</E>we also propose various other changes in parts 1 and 22 of the Commission's rules that apply to Cellular Service licensees. For example, we propose to streamline the application requirements for site-based Unserved Area applications, notably § 22.953 (deleting certain technical data requirements that, going forward, we believe will no longer be routinely necessary). We also propose to delete provisions that we believe are obsolete going forward, such as those requiring certifications associated with cessation of analog service, often referred to as the “analog sunset.” Here too, our proposals are consistent with the Commission's regulatory reform agenda and its Data Innovation Initiative. The proposed rules are set forth in Appendix E and we encourage all interested parties to review them carefully and comment on them with specificity.</P>
        <HD SOURCE="HD3">Steps Taken To Minimize Significant Economic Impact on Small Entities, and Significant Alternatives Considered</HD>
        <P>85. The RFA requires an agency to describe any significant, specifically small business, alternatives that it has considered in reaching its proposed approach, which may include the following four alternatives (among others): (1) The establishment of differing compliance or reporting requirements or timetables that take into account the resources available to small entities; (2) the clarification, consolidation, or simplification of compliance and reporting requirements under the rule for small entities; (3) the use of performance rather than design standards; and (4) an exemption from coverage of the rule, or any part thereof for small entities.</P>
        <P>86. The<E T="03">NPRM</E>discusses several alternatives to the proposed two-stage transition. These include, for example, alternatives that would entail transition via auction in more than two stages as well as possible exemption for certain extremely rural markets such as Alaskan markets and others with special build-out challenges. The<E T="03">NPRM</E>also discusses proposals put forth by industry stakeholders thus far in this proceeding, including an approach that would not entail competitive bidding. The<E T="03">NPRM</E>specifically invites interested parties to comment on these various alternatives and to suggest other alternative proposals. At this time, the Commission has not excluded any alternative proposal from its consideration, but it would do so in this proceeding if the record indicates that a particular proposal would have a significant and unjustifiable adverse economic impact on small entities.</P>

        <P>87. The Commission believes that the proposed transition to a geographic-area licensing system for the Cellular Service in two stages via auction will benefit all Cellular incumbents and entrants, regardless of size. The proposed scheme would put Cellular licensees on a regulatory par with other wireless licensees that hold geographic area licenses, such as PCS and certain AWS licensees, thus easing the regulatory burden of compliance by eliminating discrepancies in competing services. The Commission has historically valued harmonization in the rules for wireless licensees by eliminating burdensome requirements, as appropriate. Furthermore, we anticipate that the modernized licensing scheme will encourage Cellular licensees to invest in and deploy ever more advanced technologies as they evolve. By reducing the paperwork burden on Cellular providers, we would also expect their resulting lower costs to have some positive effect on the rates paid by subscriber groups, including small businesses that rely on Cellular service.<PRTPAGE P="15678"/>
        </P>
        <HD SOURCE="HD3">Federal Rules That May Duplicate, Overlap, or Conflict With the Proposed Rules</HD>
        <P>None.</P>
        <HD SOURCE="HD2">C. Initial Paperwork Reduction Analysis</HD>

        <P>88. This document contains potential new and modified information collection requirements. The Commission, as part of its continuing effort to reduce paperwork burdens, invites the general public and OMB to comment on the potential information collection requirements contained in this document, as required by the Paperwork Reduction Act of 1995, Public Law 104-13. In addition, pursuant to the Small Business Paperwork Relief Act of 2002, Public Law 107-198,<E T="03">see</E>44 U.S.C. 3506(c)(4), we seek specific comment on how we might “further reduce the information collection burden for small business concerns with fewer than 25 employees.”</P>
        <HD SOURCE="HD1">VI. Ordering Clauses</HD>

        <P>89. Pursuant to sections 1, 2, 4(i), 301, 302, 303, 308, 309(j), and 332 of the Communications Act of 1934, as amended, 47 U.S.C. 151, 152, 154(i), 301, 302, 303, 308, 309(j), and 332, this<E T="03">Notice of Proposed Rulemaking and Order</E>are hereby<E T="03">adopted.</E>
        </P>

        <P>90. Pursuant to sections 4(i), 301, 303, 308, and 309 of the Communications Act of 1934, as amended, 47 U.S.C. 154(i), 301, 303, 308, and 309, that effective as of the date of the adoption of this<E T="03">Notice of Proposed Rule Making and Order,</E>THE FEDERAL COMMUNICATIONS COMMISSION WILL NOT ACCEPT FOR FILING ANY APPLICATIONS for licenses in the Cellular Band that are inconsistent with the terms of the application freeze discussed herein. This suspension is effective until further notice and applies to any such applications received on or after the date of adoption of this<E T="03">Notice of Proposed Rulemaking and Order.</E>
        </P>

        <P>91. NOTICE IS HEREBY GIVEN of the proposed regulatory changes described in this<E T="03">Notice of Proposed Rulemaking</E>and that comment is sought on these proposals.</P>
        <P>92. The Commission's Consumer and Governmental Affairs Bureau, Reference Information Center, SHALL SEND a copy of this Notice of Proposed Rulemaking and Order, including the Initial Regulatory Flexibility Analysis, to the Chief Counsel for Advocacy of the Small Business Administration.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <CFR>47 CFR Part 1</CFR>
          <P>Administrative practice and procedure, Communications common carriers, Radio, Reporting and recordkeeping requirements, Telecommunications.</P>
          <CFR>47 CFR Part 22</CFR>
          <P>Communications common carriers, Radio, Reporting and recordkeeping requirements, Rural areas.</P>
        </LSTSUB>
        <SIG>
          <FP>Federal Communications Commission.</FP>
          <NAME>Marlene H. Dortch,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
        
        <P>For the reasons discussed in the preamble, the Federal Communications Commission proposes to amend 47 CFR parts 1 and 22 as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 1—PRACTICE AND PROCEDURE</HD>
          <P>1. The authority citation for part 1 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>15 U.S.C. 79<E T="03">et seq.;</E>47 U.S.C. 151, 154(i), 154(j), 155, 157, 225, 227, 303(r), and 309.</P>
          </AUTH>
          <SECTION>
            <SECTNO>§ 1.919</SECTNO>
            <SUBJECT>[Amended]</SUBJECT>
            <P>2. Amend § 1.919 by removing and reserving paragraph (c).</P>
            <P>3. Amend § 1.929 by revising paragraph (b)(1), removing and reserving paragraph (b)(3), and adding paragraph (b)(4) to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 1.929</SECTNO>
            <SUBJECT>Classification of filings as major or minor.</SUBJECT>
            <STARS/>
            <P>(b) * * *</P>
            <P>(1) Request for an authorization or an amendment to a pending application that would expand the Cellular Geographic Service Area (CGSA) of an existing cellular system or, in the case of an amendment, as previously proposed in an application, in a CMA Block that has not been included in an auction for Cellular Overlay Authorizations under § 22.985.</P>
            <STARS/>
            <P>(4) Request for a Cellular Overlay Authorization.<E T="03">See</E>§ 22.985.</P>
            <STARS/>
            <P>4. Amend § 1.958 by revising paragraph (d) to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 1.958</SECTNO>
            <SUBJECT>Distance computation.</SUBJECT>
            <STARS/>
            <P>(d) Calculate the number of kilometers per degree of longitude difference for the mean geodetic latitude calculated in paragraph (b) of this section as follows:</P>
            
            <FP SOURCE="FP-2">KPD<E T="52">lon</E>= 111.41513 cos ML − 0.09455 cos 3ML + 0.00012 cos 5ML</FP>
            <STARS/>
          </SECTION>
        </PART>
        <PART>
          <HD SOURCE="HED">PART 22—PUBLIC MOBILE SERVICES</HD>
          <P>5. The authority citation for part 22 continues to read as follows:</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>47 U.S.C. 154, 222, 303, 309 and 332.</P>
          </AUTH>
          
          <P>6. Amend § 22.99 by:</P>
          <P>a. Removing the definitions “Build-out transmitters,” “Extension,” “Five year build-out period,” and “Partitioned cellular market”;</P>
          <P>b. Revising the definitions<E T="03">“Cellular Geographic Service Area,” and</E>“Cellular markets”; and</P>
          <P>c. Revising the term “Unserved areas” to read “Unserved Area” and revising the first sentence of its definition;</P>
          <P>d. Adding definitions “<E T="03">Cellular area-based authorization,” “Cellular Licensed Area,” “Cellular Overlay Authorization (COA),” “Cellular Overlay Licensee,” “Cellular site-based authorization,” “CMA Block,” and “Substantially Licensed CMA Block”.</E>
          </P>
          <P>The revisions and additions read as follows:</P>
          <SECTION>
            <SECTNO>§ 22.99</SECTNO>
            <SUBJECT>Definitions.</SUBJECT>
            <STARS/>
            <P>
              <E T="03">Cellular area-based authorization.</E>An authorization in the Cellular Radiotelephone Service where the licensed area is a specified fixed geographic area other than a CGSA (<E T="03">e.g.,</E>a CMA, as in the case of a Cellular Overlay Authorization) irrespective of the locations and technical parameters of base stations (cell sites), in a CMA Block included in an auction under § 22.985.</P>
            <P>
              <E T="03">Cellular Geographic Service Area (CGSA).</E>The licensed geographic area, determined by the specified locations and technical parameters of base stations (cell sites) pursuant to the procedures set forth in § 22.911, within which a cellular system is entitled to protection and adverse effects are recognized, for the purpose of determining whether a petitioner has standing, in the Cellular Radiotelephone Service.</P>
            <P>
              <E T="03">Cellular Licensed Area.</E>The geographic area within which the cellular licensee is permitted to transmit, or consent to allow other cellular licensees to transmit, electromagnetic energy and signals on the assigned channel block, in order to provide cellular service.</P>
            <P>
              <E T="03">Cellular Market Area (CMA).</E>A standard geographic area used by the FCC for administrative convenience in the licensing of cellular systems; a more recent term for “cellular market” (and includes Metropolitan Statistical Areas (MSAs) and Rural Service Areas (RSAs)).<E T="03">See</E>§ 22.909.<PRTPAGE P="15679"/>
            </P>
            <P>
              <E T="03">Cellular markets (obsolescent). See definition for “Cellular Market Area (CMA)”.</E>
            </P>
            <STARS/>
            <P>
              <E T="03">Cellular Overlay Authorization (COA).</E>A cellular area-based authorization in a CMA Block included in an auction under § 22.985, where the cellular licensed area is the geographic area within the CMA boundary (Channel Block A or B), subject to the requirement to protect incumbent licensees' operations from harmful interference under applicable rules.</P>
            <P>
              <E T="03">Cellular Overlay Licensee.</E>The holder of a Cellular Overlay Authorization.</P>
            <STARS/>
            <P>
              <E T="03">Cellular site-based authorization.</E>An authorization in the Cellular Radiotelephone Service where the Cellular Licensed Area is determined by the specified locations and technical parameters of base stations (cell sites), pursuant to the procedures set forth in § 22.911.</P>
            <STARS/>
            <P>
              <E T="03">CMA Block.</E>In the Cellular Radiotelephone Service, a CMA considered in regard to a specified channel block,<E T="03">i.e.,</E>either Channel Block A or Channel Block B (<E T="03">see</E>§ 22.905).</P>
            <STARS/>
            <P>
              <E T="03">Substantially Licensed CMA Block.</E>A CMA Block (A or B) where at least 95 percent of the total land area is Cellular Geographic Service Area or which contains no contiguous parcel of Unserved Area larger than 130 square kilometers (50 square miles).</P>
            <STARS/>
            <P>
              <E T="03">Unserved Area.</E>With regard to a channel block allocated for assignment in the Cellular Radiotelephone Service: Geographic area in the District of Columbia, or any State, Territory or Possession of the United States of America that is not within any Cellular Geographic Service Area of any cellular system authorized to transmit on that channel block. * * *</P>
            <P>7. Amend § 22.131 by revising paragraphs (c)(3)(iii) and (d)(2)(iv) to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 22.131</SECTNO>
            <SUBJECT>Procedures for mutually exclusive applications.</SUBJECT>
            <STARS/>
            <P>(c) * * *</P>
            <P>(3) * * *</P>
            <P>(iii) If all of the mutually exclusive applications filed on the earliest filing date are applications for initial authorization, a 30-day notice and cut-off filing group is used.</P>
            <STARS/>
            <P>(d) * * *</P>
            <P>(2) * * *</P>
            <P>(iv) Any application to expand the CGSA of a cellular system (as defined in § 22.911) in a CMA Block that has not been included in an auction under § 22.985.</P>
            <STARS/>
            <P>8. Amend § 22.165 by revising paragraph (e) to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 22.165</SECTNO>
            <SUBJECT>Additional transmitters for existing systems.</SUBJECT>
            <STARS/>
            <P>(e)<E T="03">Cellular Radiotelephone Service.</E>(1) In a CMA Block that has not been included in an auction under § 22.985, the service area boundaries of the additional transmitters, as calculated by the method set forth in § 22.911(a), must remain within the CGSA; the licensee must seek prior approval (using FCC Form 601) regarding any transmitters to be added under this section that would cause a change in the CGSA boundary.<E T="03">See</E>§ 22.953.</P>
            <P>(2) With regard to an incumbent's CGSA in a CMA Block that has been included in an auction under § 22.985, the service area boundaries of the additional transmitters, as calculated by the method set forth in § 22.911(a), must remain within the incumbent's CGSA.</P>
            <P>(3) A Cellular Overlay Licensee is permitted to expand into any Unserved Area within its licensed CMA Block so long as it protects existing cellular licensees from harmful interference.</P>
            <STARS/>
          </SECTION>
          <SECTION>
            <SECTNO>§ 22.228</SECTNO>
            <SUBJECT>[Removed]</SUBJECT>
            <P>9. Remove § 22.228.</P>
            <P>10. Revise § 22.901 to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 22.901</SECTNO>
            <SUBJECT>Cellular service requirements and limitations.</SUBJECT>
            <P>Each cellular system must provide either mobile service, fixed service, or a combination of mobile and fixed service, subject to the requirements, limitations and exceptions in this section. Mobile service provided may be of any type, including two-way radiotelephone, dispatch, one-way or two-way paging, and personal communications services (as defined in part 24 of this chapter). Fixed service is considered to be primary service, as is mobile service. When both mobile and fixed services are provided, they are considered to be co-primary services. In providing cellular service, each cellular system may incorporate any technology that meets all applicable technical requirements in this part.</P>
            <P>11. Revise § 22.909 to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 22.909</SECTNO>
            <SUBJECT>Cellular market areas (CMAs).</SUBJECT>

            <P>Cellular market areas (CMAs) are standard geographic areas used by the FCC for administrative convenience in the licensing of cellular systems. CMAs comprise Metropolitan Statistical Areas (MSAs) and Rural Service Areas (RSAs). All CMAs and the counties they comprise are listed in: “Common Carrier Public Mobile Services Information, Cellular MSA/RSA Markets and Counties,”<E T="03">Public Notice,</E>Report No. CL-92-40, 6 FCC Rcd 742 (1992).</P>
            <P>(a)<E T="03">MSAs.</E>Metropolitan Statistical Areas are 306 areas, including New England County Metropolitan Areas and the Gulf of Mexico Service Area (water area of the Gulf of Mexico, border is the coastline), defined by the Office of Management and Budget, as modified by the FCC.</P>
            <P>(b)<E T="03">RSAs.</E>Rural Service Areas are 428 areas, other than MSAs, established by the FCC.</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 22.912</SECTNO>
            <SUBJECT>[Removed]</SUBJECT>
            <P>12. Remove § 22.912.</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 22.929</SECTNO>
            <SUBJECT>[Removed]</SUBJECT>
            <P>13. Remove § 22.929.</P>
            <P>14. Revise § 22.946 to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 22.946</SECTNO>
            <SUBJECT>Construction period for cellular systems under site-based authorizations.</SUBJECT>

            <P>The construction period applicable to specific new or modified cellular facilities for which a site-based authorization is granted is one year, beginning on the date the authorization is granted. To satisfy this requirement, a cellular system must be providing service to mobile stations operated by subscribers and roamers. The licensee must notify the FCC (FCC Form 601) after the requirements of this section are met.<E T="03">See</E>§ 1.946 of this chapter. GMEZ cellular systems are not subject to construction period requirements.<E T="03">See</E>§ 22.950.</P>
            <P>15. Revise § 22.947 to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 22.947</SECTNO>
            <SUBJECT>Build-out period for CMA Block 672A (Chambers, TX).</SUBJECT>
            <P>This rule section applies only to cellular systems operating on Channel Block A in CMA 672 (Chambers, Texas).</P>

            <P>(a) A licensee that holds the Cellular Overlay Authorization for CMA Block 672A (Chambers, Texas) initially awarded via auction (<E T="03">i.e.,</E>the CMA Block for which cellular service was authorized solely under interim operating authority prior to the Stage I auction described in § 22.985) must be providing signal coverage and offering service over at least 35 percent of the geographic area of the CMA Block within four years of the grant of the authorization, and over at least 70 percent of the geographic area of its license authorization by the end of the license term. In applying this geographic benchmark, the licensee is to count total land area.<PRTPAGE P="15680"/>
            </P>

            <P>(b) The licensee must notify the FCC (FCC Form 601) after the requirements of this section are met and must include with its notification(s) GIS map files and other supporting documents showing compliance with the construction requirement.<E T="03">See</E>§ 1.946 of this chapter.<E T="03">See also</E>§ 22.953.</P>
            <P>(c) Failure to meet the requirements in this section by the deadline will result in automatic termination of the authorization and such licensee will be ineligible to regain it.</P>
            <P>16. Revise § 22.948 to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 22.948</SECTNO>
            <SUBJECT>Geographic partitioning and spectrum disaggregation.</SUBJECT>

            <P>Cellular licensees may apply to partition their cellular licensed area or to disaggregate their licensed spectrum at any time following the grant of their authorization(s). Parties seeking approval for partitioning and disaggregation shall request from the FCC an authorization for partial assignment of a license pursuant to § 1.948 of this chapter.<E T="03">See also</E>paragraph (f) of this section.</P>
            <P>(a)<E T="03">Partitioning.</E>Applicants must file FCC Form 603 pursuant to § 1.948 of this chapter. The filing must include the attachments required under § 22.953, including GIS map files and a reduced-size PDF map, for both the assignor and the assignee.</P>

            <P>(1) Within a CMA Block that has not yet been included in an auction under § 22.985, partitioning of a CGSA must be on a site-by-site basis;<E T="03">i.e.,</E>the partitioned area must comprise only the area resulting from one or more cell sites pursuant to § 22.911. At least one entire cell site must be partitioned. If all cell sites are assigned, it is not partitioning, but rather a full assignment of authorization.</P>

            <P>(2) Partitioning of the licensed area of a cellular area-based authorization (including,<E T="03">e.g.,</E>the licensed area of a Cellular Overlay Authorization) to a licensee in a CMA Block that has not yet been included in an auction under § 22.985 must be on a site-by-site basis;<E T="03">i.e.,</E>the partitioned area must comprise CGSA resulting from one or more cell sites pursuant to § 22.911.</P>

            <P>(3) Partitioning of the licensed area of a cellular area-based authorization within the same CMA Block that has been included in an auction under § 22.985, or to a licensee in another CMA Block that has also been included in such an auction (including,<E T="03">e.g.,</E>the partitioning of a Cellular Overlay Authorization area by one Cellular Overlay Licensee to another Cellular Overlay Licensee), may involve any proportion of division. If all of the licensed area is assigned, it is not partitioning, but rather a full assignment of authorization.</P>
            <P>(b)<E T="03">Disaggregation.</E>Spectrum may be disaggregated in any amount.</P>
            <P>(c)<E T="03">Combined partitioning and disaggregation.</E>The FCC will consider requests for partial assignment of licenses that propose combinations of partitioning and disaggregation.</P>
            <P>(d)<E T="03">Field strength limit.</E>For purposes of partitioning and disaggregation, cellular systems must be designed so as not to exceed a median field strength level of 40 dBμV/m at or beyond the boundary of the Cellular Licensed Area, unless all affected adjacent service area licensees agree to a different signal level.<E T="03">See</E>§ 22.983.</P>
            <P>(e)<E T="03">License term.</E>The license term for a partitioned license area and for disaggregated spectrum will be the remainder of the original license term.</P>
            <P>(f)<E T="03">Spectrum Leasing.</E>Cellular spectrum leasing is subject to the provisions of paragraphs (a)(1) through (a)(3), (b), and (c) of this section, except that applicants must file FCC Form 608 (not FCC Form 603), as well as all applicable provisions of subpart X of part 1 of this chapter.</P>
            <P>17. Revise § 22.949 to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 22.949</SECTNO>
            <SUBJECT>Unserved Area licensing process for site-based systems.</SUBJECT>
            <P>This section sets forth the process for licensing Unserved Area in CMA Blocks not yet included in an auction pursuant to § 22.985. The licensing process in this § 22.949 allows eligible parties to apply for any Unserved Area that remains in such CMA Blocks.</P>
            <P>(a) The Unserved Area licensing process described in this section is on-going and applications may be filed at any time, until the CMA Block is included in an auction pursuant to § 22.985.</P>

            <P>(b) There is no limit to the number of Unserved Area applications that may be granted on each CMA Channel Block that remains subject to the procedures of this section. Consequently, such Unserved Area applications are mutually exclusive only if the proposed CGSAs would overlap. Mutually exclusive applications are processed using the general procedures in § 22.131.<E T="03">See also</E>§ 22.961.</P>
            <P>(c) Unserved Area applications under this section may propose a CGSA covering more than one CMA. Each such Unserved Area application must request authorization for only one CGSA.</P>
            <P>(d) Settlements among some, but not all, applicants with mutually exclusive applications for Unserved Area (partial settlements) under this section are prohibited. Settlements among all applicants with mutually exclusive applications under this section (full settlements) are allowed and must be filed no later than the date that the FCC Form 175 (short-form) is filed.</P>
            <P>18. Amend § 22.950 by revising paragraphs (c) and (d) to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 22.950</SECTNO>
            <SUBJECT>Provision of service in the Gulf of Mexico Service Area (GMSA).</SUBJECT>
            <STARS/>
            <P>(c)<E T="03">Gulf of Mexico Exclusive Zone (GMEZ).</E>GMEZ licensees have an exclusive right to provide cellular service in the GMEZ, and may add, modify, or remove facilities anywhere within the GMEZ without prior FCC approval. There is no Unserved Area licensing procedure for the GMEZ.</P>
            <P>(d)<E T="03">Gulf of Mexico Coastal Zone (GMCZ).</E>The GMCZ is subject to the Unserved Area licensing procedure set forth in § 22.949.</P>
            <P>19. Revise § 22.953 to read as follows:</P>
          </SECTION>
          <SECTION>
            <SECTNO>§ 22.953</SECTNO>
            <SUBJECT>Content and form of applications for cellular authorizations.</SUBJECT>
            <P>Applications for authority to operate a new cellular system or to modify an existing cellular system must comply with the specifications in this section.</P>
            <P>(a)<E T="03">New Systems.</E>In addition to information required by subparts B and D of this part and by FCC Form 601, applications for a site-based authorization to operate a cellular system must comply with all applicable requirements set forth in part 1 of this chapter, including the requirements specified in §§ 1.913, 1.923, and 1.924, and must include the information listed below, in numbered exhibits. Geographical coordinates must be correct to ±1 second using the NAD 83 datum.</P>
            <P>(1)<E T="03">Exhibit I—Geographic Information System (GIS) map files.</E>The FCC will specify the file format required for the Geographic Information System (GIS) map files that are to be submitted electronically via the Universal Licensing System (ULS). In addition to GIS map files submitted electronically, the FCC reserves the right to request a full-size paper map from the applicant. The scale of the full-size paper map must be 1:500,000, regardless of whether any different scale is used for the reduced-size PDF map required in Exhibit II. In addition to the information required for the GIS map files, the paper map, if requested, must include all the information required for the reduced-size PDF map (<E T="03">see</E>paragraph (a)(2) of this section).</P>
            <P>(2)<E T="03">Exhibi