<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="fedregister.xsl"?>
<FEDREG xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FRMergedXML.xsd">
  <VOL>78</VOL>
  <NO>5</NO>
  <DATE>Tuesday, January 8, 2013</DATE>
  <UNITNAME>Contents</UNITNAME>
  <CNTNTS>
    <AGCY>
      <EAR>Agricultural Marketing</EAR>
      <PRTPAGE P="iii"/>
      <HD>Agricultural Marketing Service</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Apricots Grown in Designated Counties in Washington:</SJ>
        <SJDENT>
          <SJDOC>Temporary Suspension of Handling Regulations,</SJDOC>
          <PGS>1127-1130</PGS>
          <FRDOCBP D="3" T="08jar1.sgm">2013--00129</FRDOCBP>
        </SJDENT>
        <SJ>Decreased Assessment Rates:</SJ>
        <SJDENT>
          <SJDOC>Domestic Dates Produced or Packed in Riverside County, CA,</SJDOC>
          <PGS>1130-1133</PGS>
          <FRDOCBP D="3" T="08jar1.sgm">2013--00185</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Agriculture</EAR>
      <HD>Agriculture Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Agricultural Marketing Service</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Food Safety and Inspection Service</P>
      </SEE>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1522-1533</PGS>
          <FRDOCBP D="11" T="08JAP2.sgm">2012--31486</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Architectural</EAR>
      <HD>Architectural and Transportation Barriers Compliance Board</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Medical Diagnostic Equipment Accessibility Standards Advisory Committee; Meeting,</DOC>
          <PGS>1166</PGS>
          <FRDOCBP D="0" T="08jap1.sgm">2013--00071</FRDOCBP>
        </DOCENT>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1622</PGS>
          <FRDOCBP D="0" T="08JAP2.sgm">2012--31501</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Consumer Financial Protection</EAR>
      <HD>Bureau of Consumer Financial Protection</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1652-1655</PGS>
          <FRDOCBP D="3" T="08JAP2.sgm">2012--31512</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Centers Disease</EAR>
      <HD>Centers for Disease Control and Prevention</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Disease, Disability, and Injury Prevention and Control Special Emphasis Panel,</SJDOC>
          <PGS>1212</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00136</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Centers Medicare</EAR>
      <HD>Centers for Medicare &amp; Medicaid Services</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>1212-1213</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00065</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Children</EAR>
      <HD>Children and Families Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Descriptive Study of County versus State Administered Temporary Assistance for Needy Families Programs,</SJDOC>
          <PGS>1213-1214</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2012--31714</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Head Start Grant Application and Budget Instruments,</SJDOC>
          <PGS>1214</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00127</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Coast Guard</EAR>
      <HD>Coast Guard</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Regulated Navigation Areas:</SJ>
        <SJDENT>
          <SJDOC>Housatonic River, Bridge Replacement Operations; Stratford, CT,</SJDOC>
          <PGS>1145-1149</PGS>
          <FRDOCBP D="4" T="08jar1.sgm">2013--00211</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Merchant Marine Personnel Advisory Committee; Vacancies,</DOC>
          <PGS>1217-1218</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00090</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Commerce</EAR>
      <HD>Commerce Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Foreign-Trade Zones Board</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Industry and Security Bureau</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>International Trade Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Oceanic and Atmospheric Administration</P>
      </SEE>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1536-1560</PGS>
          <FRDOCBP D="24" T="08JAP2.sgm">2012--31489</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Commodity Futures</EAR>
      <HD>Commodity Futures Trading Commission</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Rules of Practice; Amendments to Delegations of Authority to the Office of General Counsel,</DOC>
          <PGS>1144-1145</PGS>
          <FRDOCBP D="1" T="08jar1.sgm">2012--31721</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Comptroller</EAR>
      <HD>Comptroller of the Currency</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>1305-1306</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00091</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Transition Period under Section 716 of the Dodd-Frank Wall Street Reform and Consumer Protection Act,</DOC>
          <PGS>1306-1307</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00093</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Defense Department</EAR>
      <HD>Defense Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Navy Department</P>
      </SEE>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <FRDOCBP D="3" T="08JAP2.sgm">2012--31491</FRDOCBP>
          <PGS>1646-1649, 1562-1565</PGS>
          <FRDOCBP D="3" T="08JAP2.sgm">2012--31510</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Defense Nuclear</EAR>
      <HD>Defense Nuclear Facilities Safety Board</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Second Extension of Hearing Record Closure Date,</DOC>
          <PGS>1206</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00096</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Education Department</EAR>
      <HD>Education Department</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1568</PGS>
          <FRDOCBP D="0" T="08JAP2.sgm">2012--31494</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Privacy Act; Systems of Records,</DOC>
          <PGS>1206-1209</PGS>
          <FRDOCBP D="3" T="08JAN1.sgm">2013--00163</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Employment and Training</EAR>
      <HD>Employment and Training Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Amended Certifications Regarding Eligibility to Apply for Worker Adjustment Assistance:</SJ>
        <SJDENT>
          <SJDOC>CalAmp Wireless Networks Corp., Oxnard, CA and Waseca, MN,</SJDOC>
          <PGS>1252</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00102</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Schneider Electric, U.S.A., et al., Lavergne, TN,</SJDOC>
          <PGS>1252-1253</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00104</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Schweizer Aircraft Corp., et al., Horseheads, NY,</SJDOC>
          <PGS>1253</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00103</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Determinations Regarding Eligibility to Apply for Worker Adjustment Assistance,</DOC>
          <PGS>1253-1256</PGS>
          <FRDOCBP D="3" T="08JAN1.sgm">2013--00100</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Guam Military Base Realignment Contractor Recruitment Standards,</DOC>
          <PGS>1256-1258</PGS>
          <FRDOCBP D="2" T="08JAN1.sgm">2013--00114</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Investigations Regarding Eligibility to Apply for Worker Adjustment Assistance,</DOC>
          <PGS>1258-1259</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00098</FRDOCBP>
        </DOCENT>
        <SJ>Labor Certification Process for the Temporary Employment of Aliens in Agriculture in the United States:</SJ>
        <SJDENT>
          <SJDOC>2013 Adverse Effect Wage Rates,</SJDOC>
          <PGS>1259-1260</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00117</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Prevailing Wage Rates for Certain Occupations Processed under H-2A Special Procedures,</SJDOC>
          <PGS>1260-1264</PGS>
          <FRDOCBP D="4" T="08JAN1.sgm">2013--00115</FRDOCBP>
        </SJDENT>
        <SJ>Negative Determinations Regarding Applications for Reconsideration:</SJ>
        <SJDENT>
          <SJDOC>CalAmp Wireless Networks Corp., Waseca, MN,</SJDOC>
          <PGS>1264</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00101</FRDOCBP>
        </SJDENT>
        <SJ>Revised Determinations on Reconsideration:</SJ>
        <SJDENT>
          <SJDOC>Dana Holding Corp., et al., Milwaukee, WI,</SJDOC>
          <PGS>1265</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00097</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Energy Department</EAR>
      <PRTPAGE P="iv"/>
      <HD>Energy Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Energy Efficiency and Renewable Energy Office</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Energy Regulatory Commission</P>
      </SEE>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1570-1571</PGS>
          <FRDOCBP D="1" T="08JAP2.sgm">2012--31497</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Energy Efficiency</EAR>
      <HD>Energy Efficiency and Renewable Energy Office</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>State Energy Advisory Board,</SJDOC>
          <PGS>1209-1210</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00106</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Environmental Protection</EAR>
      <HD>Environmental Protection Agency</HD>
      <CAT>
        <HD>RULES</HD>
        <SJ>Approvals and Promulgations of Implementation Plans; Designation of Areas for Air Quality Planning Purposes:</SJ>
        <SJDENT>
          <SJDOC>Nevada; Redesignation of Clark County to Attainment for the 1997 8-Hour Ozone Standard,</SJDOC>
          <PGS>1149-1153</PGS>
          <FRDOCBP D="4" T="08jar1.sgm">2013--00057</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1624-1629</PGS>
          <FRDOCBP D="5" T="08JAP2.sgm">2012--31502</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>Export Import</EAR>
      <HD>Export-Import Bank</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>1211</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00143</FRDOCBP>
        </DOCENT>
        <SJ>Applications for Final Commitment for Long-Term Loan or Financial Guarantee in Excess of $100 Million:</SJ>
        <SJDENT>
          <SJDOC>AP086856XX,</SJDOC>
          <PGS>1211-1212</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00142</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Aviation</EAR>
      <HD>Federal Aviation Administration</HD>
      <CAT>
        <HD>RULES</HD>
        <DOCENT>
          <DOC>Explosive Siting Requirements; Correction,</DOC>
          <PGS>1143-1144</PGS>
          <FRDOCBP D="1" T="08jar1.sgm">2013--00109</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Noise Certification Standards for Tiltrotors,</DOC>
          <PGS>1133-1143</PGS>
          <FRDOCBP D="10" T="08jar1.sgm">2013--00111</FRDOCBP>
        </DOCENT>
      </CAT>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Airworthiness Directives:</SJ>
        <SJDENT>
          <SJDOC>Cessna Aircraft Company Airplanes,</SJDOC>
          <PGS>1155-1158</PGS>
          <FRDOCBP D="3" T="08jap1.sgm">2013--00069</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Communications</EAR>
      <HD>Federal Communications Commission</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Commercial Operations in 3550-3650 MHz Band,</DOC>
          <PGS>1188-1193</PGS>
          <FRDOCBP D="5" T="08jap1.sgm">2013--00155</FRDOCBP>
        </DOCENT>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1658-1687</PGS>
          <FRDOCBP D="29" T="08JAP2.sgm">2012--31514</FRDOCBP>
        </SJDENT>
        <SJ>Service Rules for Advanced Wireless Services in H Block:</SJ>
        <SJDENT>
          <SJDOC>Implementing Section 6401 of Middle Class Tax Relief and Job Creation Act Related to 1915-1920 MHz and 1995-2000 MHz Bands,</SJDOC>
          <PGS>1166-1188</PGS>
          <FRDOCBP D="22" T="08jap1.sgm">2013--00157</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Deposit</EAR>
      <HD>Federal Deposit Insurance Corporation</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulaatory Agenda,</SJDOC>
          <PGS>1690-1695</PGS>
          <FRDOCBP D="5" T="08JAP2.sgm">2012--31515</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Energy</EAR>
      <HD>Federal Energy Regulatory Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Filings:</SJ>
        <SJDENT>
          <SJDOC>Anaheim, CA,</SJDOC>
          <PGS>1210</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00119</FRDOCBP>
        </SJDENT>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Grand River Dam Authority,</SJDOC>
          <PGS>1210</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00120</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Membership of Performance Review Board for Senior Executives,</DOC>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00118</FRDOCBP>
          <PGS>1210</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00121</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Reserve</EAR>
      <HD>Federal Reserve System</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1698-1701</PGS>
          <FRDOCBP D="3" T="08JAP2.sgm">2012--31517</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Formations of, Acquisitions by, and Mergers of Bank Holding Companies,</DOC>
          <PGS>1212</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00108</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Proposals to Engage in or to Acquire Companies Engaged in Permissible Nonbanking Activities,</DOC>
          <PGS>1212</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00107</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Federal Transit</EAR>
      <HD>Federal Transit Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Fiscal Year 2012 Public Transportation on Indian Reservations Program Project Selections,</DOC>
          <PGS>1301-1305</PGS>
          <FRDOCBP D="4" T="08JAN1.sgm">2013--00167</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Fish</EAR>
      <HD>Fish and Wildlife Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
        <SJDENT>
          <SJDOC>Otay River Estuary Restoration Project; South San Diego Bay Unit and Sweetwater Marsh Unit, San Diego Bay National Wildlife Refuge, CA,</SJDOC>
          <PGS>1246-1247</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00134</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Food and Drug</EAR>
      <HD>Food and Drug Administration</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Anesthesiology Devices:</SJ>
        <SJDENT>
          <SJDOC>Reclassification of Membrane Lung for Long-Term Pulmonary Support, etc.,</SJDOC>
          <PGS>1158-1162</PGS>
          <FRDOCBP D="4" T="08jap1.sgm">2013--00086</FRDOCBP>
        </SJDENT>
        <SJ>Cardiovascular Devices:</SJ>
        <SJDENT>
          <SJDOC>Reclassification of External Cardiac Compressor,</SJDOC>
          <PGS>1162-1166</PGS>
          <FRDOCBP D="4" T="08jap1.sgm">2013--00085</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Food Safety</EAR>
      <HD>Food Safety and Inspection Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Codex Alimentarius Commission Ad Hoc Codex Intergovernmental Task Force on Animal Feeding,</SJDOC>
          <PGS>1196-1197</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00169</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Foreign Trade</EAR>
      <HD>Foreign-Trade Zones Board</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Reorganizations and Expansions under Alternative Site Framework:</SJ>
        <SJDENT>
          <SJDOC>Foreign-Trade Zone 8, Toledo, OH,</SJDOC>
          <PGS>1197</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00156</FRDOCBP>
        </SJDENT>
        <SJ>Reorganizations under Alternative Site Framework:</SJ>
        <SJDENT>
          <SJDOC>Foreign-Trade Zone 32, Miami, FL,</SJDOC>
          <PGS>1197-1198</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00160</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>General Services</EAR>
      <HD>General Services Administration</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <FRDOCBP D="0" T="08JAP2.sgm">2012--31504</FRDOCBP>
          <PGS>1632, 1646-1649</PGS>
          <FRDOCBP D="3" T="08JAP2.sgm">2012--31510</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Health and Human</EAR>
      <HD>Health and Human Services Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Centers for Disease Control and Prevention</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Centers for Medicare &amp; Medicaid Services</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Children and Families Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Food and Drug Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Health Resources and Services Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>National Institutes of Health</P>
      </SEE>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1574-1583</PGS>
          <FRDOCBP D="9" T="08JAP2.sgm">2012--31671</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Health Resources</EAR>
      <HD>Health Resources and Services Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>1214-1216</PGS>
          <FRDOCBP D="2" T="08JAN1.sgm">2013--00031</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>
        <PRTPAGE P="v"/>
        <HD SOURCE="HED">See</HD>
        <P>U.S. Citizenship and Immigration Services</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>U.S. Customs and Border Protection</P>
      </SEE>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1586-1592</PGS>
          <FRDOCBP D="6" T="08JAP2.sgm">2012--31672</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Housing</EAR>
      <HD>Housing and Urban Development Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Supportive Housing for the Elderly:</SJ>
        <SJDENT>
          <SJDOC>Senior Preservation Rental Assistance Contracts Award Process,</SJDOC>
          <PGS>1224-1246</PGS>
          <FRDOCBP D="22" T="08JAN1.sgm">2013--00072</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Industry</EAR>
      <HD>Industry and Security Bureau</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Information Systems Technical Advisory Committee,</SJDOC>
          <PGS>1198</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00154</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Sensors and Instrumentation Technical Advisory Committee,</SJDOC>
          <PGS>1198</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00153</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>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1594-1595</PGS>
          <FRDOCBP D="1" T="08JAP2.sgm">2012--31498</FRDOCBP>
        </SJDENT>
      </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>Light-Walled Rectangular Pipe and Tube from Mexico,</SJDOC>
          <PGS>1199-1200</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00054</FRDOCBP>
        </SJDENT>
        <SJ>Antidumping Duty Changed Circumstances Review; Results, Extensions, Amendments, etc.:</SJ>
        <SJDENT>
          <SJDOC>Diamond Sawblades and Parts Thereof from the People's Republic of China,</SJDOC>
          <PGS>1200</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00158</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>International Trade Com</EAR>
      <HD>International Trade Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Investigations:</SJ>
        <SJDENT>
          <SJDOC>Certain Electronic Devices, Including Wireless Communication Devices, Tablet Computers, Media Players, and Televisions, and Components Thereof,</SJDOC>
          <PGS>1247-1248</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00149</FRDOCBP>
        </SJDENT>
        <SJ>Terminations of Investigations:</SJ>
        <SJDENT>
          <SJDOC>Certain Computing Devices with Associated Instruction Sets and Software,</SJDOC>
          <PGS>1248-1249</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00070</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Justice Department</EAR>
      <HD>Justice Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Equal Employment Opportunity Plan Certification and Short Form,</SJDOC>
          <PGS>1249-1250</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00147</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Stress Resiliency Study Questionnaires for Milwaukee Police Department,</SJDOC>
          <PGS>1250</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00148</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Lodging of Consent Decrees under Clean Air Act,</DOC>
          <PGS>1250-1251</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00092</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Lodging of Proposed Consent Decrees under Clean Air, Clean Water, and Resource Conservation and Recovery Acts,</DOC>
          <PGS>1251</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00060</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Lodging of Proposed Consent Decrees under Oil Pollution Act,</DOC>
          <PGS>1251-1252</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00062</FRDOCBP>
        </DOCENT>
      </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>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1598-1601</PGS>
          <FRDOCBP D="3" T="08JAP2.sgm">2012--31499</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Marine</EAR>
      <HD>Marine Mammal Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Meetings; Sunshine Act,</DOC>
          <PGS>1265</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00252</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>NASA</EAR>
      <HD>National Aeronautics and Space Administration</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <FRDOCBP D="0" T="08JAP2.sgm">2012--31505</FRDOCBP>
          <PGS>1634, 1646-1649</PGS>
          <FRDOCBP D="3" T="08JAP2.sgm">2012--31510</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Aerospace Safety Advisory Panel,</SJDOC>
          <PGS>1265-1266</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00064</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Credit</EAR>
      <HD>National Credit Union Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Meetings; Sunshine Act,</DOC>
          <PGS>1266</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00205</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Institute</EAR>
      <HD>National Institutes of Health</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Center for Scientific Review,</SJDOC>
          <PGS>1216</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00088</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Institute on Deafness and Other Communication Disorders,</SJDOC>
          <PGS>1217</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00087</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Office of the Director,</SJDOC>
          <PGS>1216-1217</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00089</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Oceanic</EAR>
      <HD>National Oceanic and Atmospheric Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Endangered and Threatened Species:</SJ>
        <SJDENT>
          <SJDOC>Take of Anadromous Fish,</SJDOC>
          <PGS>1200-1205</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00137</FRDOCBP>
          <FRDOCBP D="2" T="08JAN1.sgm">2013--00138</FRDOCBP>
          <FRDOCBP D="2" T="08JAN1.sgm">2013--00139</FRDOCBP>
        </SJDENT>
        <SJ>Taking and Importing Marine Mammals:</SJ>
        <SJDENT>
          <SJDOC>Takes Incidental to Hydrographic Surveys,</SJDOC>
          <PGS>1205-1206</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00135</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Science</EAR>
      <HD>National Science Foundation</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>1266-1267</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00188</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>National Transportation</EAR>
      <HD>National Transportation Safety Board</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <DOCENT>
          <DOC>Retrospective Analysis of Existing Rules; Notification,</DOC>
          <PGS>1193-1195</PGS>
          <FRDOCBP D="2" T="08jap1.sgm">2012--31623</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Navy</EAR>
      <HD>Navy Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Government-Owned Inventions; Available for Licensing,</DOC>
          <PGS>1206</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00066</FRDOCBP>
        </DOCENT>
        <SJ>Intent to Grant Exclusive Patent Licenses:</SJ>
        <SJDENT>
          <SJDOC>Allied Communications, LLC,</SJDOC>
          <PGS>1206</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00068</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Nuclear Regulatory</EAR>
      <HD>Nuclear Regulatory Commission</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>Low-Level Waste Disposal:</SJ>
        <SJDENT>
          <SJDOC>Correction,</SJDOC>
          <PGS>1155</PGS>
          <FRDOCBP D="0" T="08jap1.sgm">2012--31704</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Onsite Emergency Response Capabilities,</DOC>
          <PGS>1154-1155</PGS>
          <FRDOCBP D="1" T="08jap1.sgm">2012--31706</FRDOCBP>
        </DOCENT>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1704-1705</PGS>
          <FRDOCBP D="1" T="08JAP2.sgm">2012--31674</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Facility Operating and Combined Licenses:</SJ>
        <SJDENT>
          <SJDOC>Applications and Amendments Involving No Significant Hazards Considerations,</SJDOC>
          <PGS>1267-1274</PGS>
          <FRDOCBP D="7" T="08JAN1.sgm">2012--31710</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>Personnel</EAR>
      <HD>Personnel Management Office</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Privacy Act; Computer Matching Program,</DOC>
          <PGS>1275-1276</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00151</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Postal Regulatory</EAR>
      <HD>Postal Regulatory Commission</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>FY 2012 Annual Compliance Report,</DOC>
          <PGS>1276-1277</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00094</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Postal Service</EAR>
      <PRTPAGE P="vi"/>
      <HD>Postal Service</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>International Product Changes:</SJ>
        <SJDENT>
          <SJDOC>Global Expedited Package Services; Non-Published Rates,</SJDOC>
          <PGS>1277-1278</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00074</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Regulatory</EAR>
      <HD>Regulatory Information Service Center</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda; Regulatory Plan,</SJDOC>
          <PGS>1318-1519</PGS>
          <FRDOCBP D="201" T="08JAP2.sgm">2012--31480</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Securities</EAR>
      <HD>Securities and Exchange Commission</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1708-1711</PGS>
          <FRDOCBP D="3" T="08JAP2.sgm">2012--31518</FRDOCBP>
        </SJDENT>
      </CAT>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
        <SJDENT>
          <SJDOC>Chicago Board Options Exchange, Inc.,</SJDOC>
          <PGS>1296</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">C1--2012--30887</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Chicago Stock Exchange, Inc.,</SJDOC>
          <PGS>1290</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">C1--2012--30886</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Fixed Income Clearing Corp.,</SJDOC>
          <PGS>1278-1280</PGS>
          <FRDOCBP D="2" T="08JAN1.sgm">2013--00122</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>ICE Clear Europe Ltd.,</SJDOC>
          <PGS>1281-1284</PGS>
          <FRDOCBP D="3" T="08JAN1.sgm">2013--00084</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>NASDAQ OMX BX, Inc.,</SJDOC>
          <PGS>1293-1296</PGS>
          <FRDOCBP D="3" T="08JAN1.sgm">2013--00077</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>National Securities Clearing Corp.,</SJDOC>
          <PGS>1292-1293</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00083</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>New York Stock Exchange LLC,</SJDOC>
          <FRDOCBP D="2" T="08JAN1.sgm">2013--00079</FRDOCBP>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00081</FRDOCBP>
          <PGS>1278, 1280-1281, 1288-1290</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">C1--2012--31260</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>NYSE Arca, Inc.,</SJDOC>
          <PGS>1284</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">C1--2012--30888</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>NYSE MKT LLC,</SJDOC>
          <PGS>1284-1288, 1290-1292</PGS>
          <FRDOCBP D="2" T="08JAN1.sgm">2013--00078</FRDOCBP>
          <FRDOCBP D="2" T="08JAN1.sgm">2013--00080</FRDOCBP>
          <FRDOCBP D="2" T="08JAN1.sgm">2013--00082</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Small Business</EAR>
      <HD>Small Business Administration</HD>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1636-1643</PGS>
          <FRDOCBP D="7" T="08JAP2.sgm">2012--31507</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Social</EAR>
      <HD>Social Security Administration</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals,</DOC>
          <PGS>1296-1298</PGS>
          <FRDOCBP D="2" T="08JAN1.sgm">2013--00162</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>State Department</EAR>
      <HD>State Department</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Meetings:</SJ>
        <SJDENT>
          <SJDOC>Advisory Committee on Historical Diplomatic Documentation,</SJDOC>
          <PGS>1298-1299</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00165</FRDOCBP>
        </SJDENT>
        <SJ>Specially Designated Global Terrorists:</SJ>
        <SJDENT>
          <SJDOC>Abdelbasit Alhaj Alhassan Haj Hamad, also known as Abd Al-Basit, et al.,</SJDOC>
          <PGS>1299</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00164</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Mohamed Makawi Ibrahim Mohamed, aka Mohamed Makawi, et al.,</SJDOC>
          <PGS>1299</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00166</FRDOCBP>
        </SJDENT>
        <SJ>Waiver of Sections of Anti-Terrorism Act:</SJ>
        <SJDENT>
          <SJDOC>Palestine Liberation Organization Office,</SJDOC>
          <PGS>1299</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00168</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Trade Representative</EAR>
      <HD>Trade Representative, Office of United States</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Possible Withdrawal, Suspension, or Limitation of Generalized System of Preferences Benefits:</SJ>
        <SJDENT>
          <SJDOC>Bangladesh,</SJDOC>
          <PGS>1300-1301</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00067</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Transportation Department</EAR>
      <HD>Transportation Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Aviation Administration</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Federal Transit Administration</P>
      </SEE>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1604-1616</PGS>
          <FRDOCBP D="12" T="08JAP2.sgm">2012--31500</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Treasury</EAR>
      <HD>Treasury Department</HD>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>Comptroller of the Currency</P>
      </SEE>
      <SEE>
        <HD SOURCE="HED">See</HD>
        <P>United States Mint</P>
      </SEE>
      <CAT>
        <HD>PROPOSED RULES</HD>
        <SJ>REGULATORY AGENDA</SJ>
        <SJDENT>
          <SJDOC>Semiannual Regulatory Agenda,</SJDOC>
          <PGS>1618-1619</PGS>
          <FRDOCBP D="1" T="08JAP2.sgm">2012--31673</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>Nonimmigrant Petition Based on Blanket L Petition,</SJDOC>
          <PGS>1218-1219</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00161</FRDOCBP>
        </SJDENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>Customs</EAR>
      <HD>U.S. Customs and Border Protection</HD>
      <CAT>
        <HD>NOTICES</HD>
        <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
        <SJDENT>
          <SJDOC>Delivery Ticket,</SJDOC>
          <PGS>1219-1220</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00141</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Guarantee of Payment,</SJDOC>
          <PGS>1220</PGS>
          <FRDOCBP D="0" T="08JAN1.sgm">2013--00150</FRDOCBP>
        </SJDENT>
        <SJDENT>
          <SJDOC>Recordation and Enforcement of Trademarks and Copyrights,</SJDOC>
          <PGS>1220-1221</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00144</FRDOCBP>
        </SJDENT>
        <DOCENT>
          <DOC>Final Determination Concerning Ponstel Mefenamic Acid Capsules,</DOC>
          <PGS>1221-1222</PGS>
          <FRDOCBP D="1" T="08JAN1.sgm">2013--00140</FRDOCBP>
        </DOCENT>
        <DOCENT>
          <DOC>Quarterly IRS Interest Rates Used in Calculating Interest on Overdue Accounts and Refunds on Customs Duties,</DOC>
          <PGS>1222-1224</PGS>
          <FRDOCBP D="2" T="08JAN1.sgm">2013--00146</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <AGCY>
      <EAR>U.S. Mint</EAR>
      <HD>United States Mint</HD>
      <CAT>
        <HD>NOTICES</HD>
        <DOCENT>
          <DOC>Privacy Act; Systems of Records,</DOC>
          <PGS>1307-1316</PGS>
          <FRDOCBP D="9" T="08JAN1.sgm">2013--00191</FRDOCBP>
        </DOCENT>
      </CAT>
    </AGCY>
    <PTS>
      <HD SOURCE="HED">Separate Parts In This Issue</HD>
      <HD>Part II</HD>
      <DOCENT>
        <DOC>Regulatory Information Service Center,</DOC>
        <PGS>1318-1519</PGS>
        <FRDOCBP D="201" T="08JAP2.sgm">2012--31480</FRDOCBP>
      </DOCENT>
      <HD>Part III</HD>
      <DOCENT>
        <DOC>Agriculture Department,</DOC>
        <PGS>1522-1533</PGS>
        <FRDOCBP D="11" T="08JAP2.sgm">2012--31486</FRDOCBP>
      </DOCENT>
      <HD>Part IV</HD>
      <DOCENT>
        <DOC>Commerce Department,</DOC>
        <PGS>1536-1560</PGS>
        <FRDOCBP D="24" T="08JAP2.sgm">2012--31489</FRDOCBP>
      </DOCENT>
      <HD>Part V</HD>
      <DOCENT>
        <DOC>Defense Department,</DOC>
        <PGS>1562-1565</PGS>
        <FRDOCBP D="3" T="08JAP2.sgm">2012--31491</FRDOCBP>
      </DOCENT>
      <HD>Part VI</HD>
      <DOCENT>
        <DOC>Education Department,</DOC>
        <PGS>1568</PGS>
        <FRDOCBP D="0" T="08JAP2.sgm">2012--31494</FRDOCBP>
      </DOCENT>
      <HD>Part VII</HD>
      <DOCENT>
        <DOC>Energy Department,</DOC>
        <PGS>1570-1571</PGS>
        <FRDOCBP D="1" T="08JAP2.sgm">2012--31497</FRDOCBP>
      </DOCENT>
      <HD>Part VIII</HD>
      <DOCENT>
        <DOC>Health and Human Services Department,</DOC>
        <PGS>1574-1583</PGS>
        <FRDOCBP D="9" T="08JAP2.sgm">2012--31671</FRDOCBP>
      </DOCENT>
      <HD>Part IX</HD>
      <DOCENT>
        <DOC>Homeland Security Department,</DOC>
        <PGS>1586-1592</PGS>
        <FRDOCBP D="6" T="08JAP2.sgm">2012--31672</FRDOCBP>
      </DOCENT>
      <HD>Part X</HD>
      <DOCENT>
        <DOC>Interior Department,</DOC>
        <PGS>1594-1595</PGS>
        <FRDOCBP D="1" T="08JAP2.sgm">2012--31498</FRDOCBP>
      </DOCENT>
      <HD>Part XI</HD>
      <DOCENT>
        <DOC>Labor Department,</DOC>
        <PGS>1598-1601</PGS>
        <FRDOCBP D="3" T="08JAP2.sgm">2012--31499</FRDOCBP>
      </DOCENT>
      <HD>Part XII</HD>
      <DOCENT>
        <DOC>Transportation Department,</DOC>
        <PGS>1604-1616</PGS>
        <FRDOCBP D="12" T="08JAP2.sgm">2012--31500</FRDOCBP>
      </DOCENT>
      <HD>Part XIII</HD>
      <DOCENT>
        <DOC>Treasury Department,</DOC>
        <PGS>1618-1619</PGS>
        <FRDOCBP D="1" T="08JAP2.sgm">2012--31673</FRDOCBP>
      </DOCENT>
      <PRTPAGE P="vii"/>
      <HD>Part XIV</HD>
      <DOCENT>
        <DOC>Architectural and Transportation Barriers Compliance Board,</DOC>
        <PGS>1622</PGS>
        <FRDOCBP D="0" T="08JAP2.sgm">2012--31501</FRDOCBP>
      </DOCENT>
      <HD>Part XV</HD>
      <DOCENT>
        <DOC>Environmental Protection Agency,</DOC>
        <PGS>1624-1629</PGS>
        <FRDOCBP D="5" T="08JAP2.sgm">2012--31502</FRDOCBP>
      </DOCENT>
      <HD>Part XVI</HD>
      <DOCENT>
        <DOC>General Services Administration,</DOC>
        <PGS>1632</PGS>
        <FRDOCBP D="0" T="08JAP2.sgm">2012--31504</FRDOCBP>
      </DOCENT>
      <HD>Part XVII</HD>
      <DOCENT>
        <DOC>National Aeronautics and Space Administration,</DOC>
        <PGS>1634</PGS>
        <FRDOCBP D="0" T="08JAP2.sgm">2012--31505</FRDOCBP>
      </DOCENT>
      <HD>Part XVIII</HD>
      <DOCENT>
        <DOC>Small Business Administration,</DOC>
        <PGS>1636-1643</PGS>
        <FRDOCBP D="7" T="08JAP2.sgm">2012--31507</FRDOCBP>
      </DOCENT>
      <HD>Part XIX</HD>
      <DOCENT>
        <DOC>Defense Department,</DOC>
        <PGS>1646-1649</PGS>
        <FRDOCBP D="3" T="08JAP2.sgm">2012--31510</FRDOCBP>
      </DOCENT>
      <DOCENT>
        <DOC>General Services Administration,</DOC>
        <PGS>1646-1649</PGS>
        <FRDOCBP D="3" T="08JAP2.sgm">2012--31510</FRDOCBP>
      </DOCENT>
      <DOCENT>
        <DOC>National Aeronautics and Space Administration,</DOC>
        <PGS>1646-1649</PGS>
        <FRDOCBP D="3" T="08JAP2.sgm">2012--31510</FRDOCBP>
      </DOCENT>
      <HD>Part XX</HD>
      <DOCENT>
        <DOC>Bureau of Consumer Financial Protection,</DOC>
        <PGS>1652-1655</PGS>
        <FRDOCBP D="3" T="08JAP2.sgm">2012--31512</FRDOCBP>
      </DOCENT>
      <HD>Part XXI</HD>
      <DOCENT>
        <DOC>Federal Communications Commission,</DOC>
        <PGS>1658-1687</PGS>
        <FRDOCBP D="29" T="08JAP2.sgm">2012--31514</FRDOCBP>
      </DOCENT>
      <HD>Part XXII</HD>
      <DOCENT>
        <DOC>Federal Deposit Insurance Corporation,</DOC>
        <PGS>1690-1695</PGS>
        <FRDOCBP D="5" T="08JAP2.sgm">2012--31515</FRDOCBP>
      </DOCENT>
      <HD>Part XXIII</HD>
      <DOCENT>
        <DOC>Federal Reserve System,</DOC>
        <PGS>1698-1701</PGS>
        <FRDOCBP D="3" T="08JAP2.sgm">2012--31517</FRDOCBP>
      </DOCENT>
      <HD>Part XXIV</HD>
      <DOCENT>
        <DOC>Nuclear Regulatory Commission,</DOC>
        <PGS>1704-1705</PGS>
        <FRDOCBP D="1" T="08JAP2.sgm">2012--31674</FRDOCBP>
      </DOCENT>
      <HD>Part XXV</HD>
      <DOCENT>
        <DOC>Securities and Exchange Commission,</DOC>
        <PGS>1708-1711</PGS>
        <FRDOCBP D="3" T="08JAP2.sgm">2012--31518</FRDOCBP>
      </DOCENT>
    </PTS>
    <AIDS>
      <HD SOURCE="HED">Reader Aids</HD>
      <P>Consult the Reader Aids section at the end of this page for phone numbers, online resources, finding aids, reminders, and notice of recently enacted public laws.</P>
      
      <P>To subscribe to the Federal Register Table of Contents LISTSERV electronic mailing list, go to http://listserv.access.gpo.gov and select Online mailing list archives, FEDREGTOC-L, Join or leave the list (or change settings); then follow the instructions.</P>
    </AIDS>
  </CNTNTS>
  <VOL>78</VOL>
  <NO>5</NO>
  <DATE>Tuesday, January 8, 2013</DATE>
  <UNITNAME>Rules and Regulations</UNITNAME>
  <RULES>
    <RULE>
      <PREAMB>
        <PRTPAGE P="1127"/>
        <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Agricultural Marketing Service</SUBAGY>
        <CFR>7 CFR Part 922</CFR>
        <DEPDOC>[Docket No. AMS-FV-12-0028; FV12-922-2 IR]</DEPDOC>
        <SUBJECT>Apricots Grown in Designated Counties in Washington; Temporary Suspension of Handling Regulations</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Agricultural Marketing Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Interim rule with request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This rule suspends the minimum grade, size, quality, maturity, and inspection requirements prescribed under the Washington apricot marketing order for the 2012-13 fiscal period. The marketing order regulates the handling of apricots grown in designated Counties in Washington and is administered locally by the Washington Apricot Marketing Committee (Committee). In order for the Committee to continue collecting assessments and administer the marketing order, the Washington State Department of Agriculture will provide apricot handling data to the Committee during the suspension of the handling regulations. This rule is expected to reduce overall industry expenses and increase net returns to producers and handlers.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Effective January 9, 2013 through March 31, 2013; comments received by March 11, 2013 will be considered prior to the issuance of a final rule.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Interested persons are invited to submit written comments concerning this rule. Comments must be sent to the Docket Clerk, Marketing Order and Agreement Division, Fruit and Vegetable Program, AMS, USDA, 1400 Independence Avenue SW., STOP 0237, Washington, DC 20250-0237; Fax: (202) 720-8938; or Internet:<E T="03">www.regulations.gov.</E>All comments should reference the document number and the date and page number of this issue of the<E T="04">Federal Register</E>and will be made available for public inspection in the Office of the Docket Clerk during regular business hours, or can be viewed at:<E T="03">www.regulations.gov.</E>All comments submitted in response to this rule will be included in the record and will be made available to the public. Please be advised that the identity of the individuals or entities submitting the comments will be made public on the Internet at the address provided above.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Manuel Michel, Marketing Specialist, or Gary Olson, Regional Manager, Northwest Marketing Field Office, Marketing Order and Agreement Division, Fruit and Vegetable Program, AMS, USDA; Telephone: (503) 326-2724; Fax: (503) 326-7440; or Email:<E T="03">Manuel.Michel@ams.usda.gov</E>or<E T="03">GaryD.Olson@ams.usda.gov.</E>
          </P>

          <P>Small businesses may request information on complying with this regulation by contacting Laurel May, Marketing Order and Agreement Division, Fruit and Vegetable Program, AMS, USDA, 1400 Independence SW., STOP 0237, Washington, DC 20250-0237; Telephone: (202) 720-2491, Fax: (202) 720-8938, or Email:<E T="03">Laurel.May@ams.usda.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>This rule is issued under Marketing Agreement and Order No. 922, as amended (7 CFR 922), regulating the handling of apricots grown in designated counties in Washington, hereinafter referred to as the “order.” The order is effective under the Agricultural Marketing Agreement Act of 1937, as amended, (7 U.S.C. 601-674), hereinafter referred to as the “Act.”</P>
        <P>The Department of Agriculture (USDA) is issuing this rule in conformance with Executive Order 12866.</P>
        <P>This rule has been reviewed under Executive Order 12988, Civil Justice Reform. This rule is not intended to have retroactive effect.</P>
        <P>The Act provides that administrative proceedings must be exhausted before parties may file suit in court. Under section 608c(15)(A) of the Act, any handler subject to an order may file with USDA a petition stating that the order, any provision of the order, or any obligation imposed in connection with the order is not in accordance with law and request a modification of the order or to be exempted therefrom. A handler is then afforded the opportunity for a hearing on the petition. After the hearing USDA would rule on the petition. The Act provides that the district court of the United States in any district in which the handler is an inhabitant, or has his or her principal place of business, has jurisdiction to review USDA's ruling on the petition, provided an action is filed not later than 20 days after date of the entry of the ruling.</P>
        <P>This rule suspends the handling regulations prescribed under the order for the 2012-13 fiscal period. Specifically, this rule suspends the minimum grade, size, quality, maturity, and inspection requirements under the order. Notwithstanding the suspension of the order's handling regulations, apricots handled in Washington must still meet the state minimum grade requirement of Washington No. 2.</P>
        <P>As a direct result of the suspension of the order's handling regulations, information from the Inspection Service will no longer be available for the Committee to compile industry statistics and to assess handlers. However, collaboration with the Washington State Department of Agriculture will provide the Committee access to apricot handling data, similar to the handler information that has been previously collected and provided by the Inspection Service.</P>
        <P>Section 922.52 of the order authorizes the issuance of regulations for grade, size, quality, maturity, and pack for apricots grown in the production area. Section 922.53 authorizes the modification, suspension, or termination of regulations issued under § 922.52, whenever the Secretary finds that a regulation no longer effectuates the declared policy of the act.</P>
        <P>Section 922.55 provides that whenever the handling of any variety of apricots is regulated pursuant to § 922.52 or § 922.53, such apricots must be inspected by the Inspection Service, and certified as meeting the applicable requirements. The cost of this inspection and certification is borne by handlers.</P>

        <P>Section 922.60 authorizes the Committee, with the approval of USDA, to require reports and other information<PRTPAGE P="1128"/>from handlers that are necessary for the Committee to perform its duties.</P>
        <P>Minimum grade, size, quality, maturity, and inspection requirements for apricots regulated under the order are specified in § 922.321 (the section being suspended by this rule). When effective, § 922.321, with exemptions for certain varieties and types of shipments, provides that all apricots shall grade not less than Washington No. 1, and are at least reasonably uniform in color; provided, that such apricots of the Moorpark variety in open containers shall be generally well matured. The regulation also includes a minimum quantity exemption, as well as specific tolerances for apricots that fail to meet color, minimum diameter, and quality requirements.</P>
        <P>The Committee meets regularly to review and consider recommendations for the regulatory requirements of Washington apricots. Committee meetings are open to the public and interested persons may express their views at these meetings. The USDA reviews Committee recommendations, information submitted by the Committee, and other available information, and determines whether modification, suspension, or termination of the regulatory requirements would tend to effectuate the declared policy of the Act.</P>
        <P>At its May 24, 2012, meeting, the Committee unanimously recommended suspending the order's handling regulations for the 2012 season. The Committee requested that this rule be effective immediately for the 2012-13 fiscal period, which began on April 1, 2012.</P>
        <P>The objective of the handling regulation has been to ensure that only acceptable quality apricots enter fresh market channels, thereby ensuring consumer satisfaction, increasing sales, and improving returns to producers.</P>
        <P>The apricot industry recognizes the continued importance of quality as a significant factor in maintaining sales. Some Committee members expressed concern that the elimination of current handling and inspection requirements could potentially result in lower quality apricots being shipped to fresh markets, thereby affecting consumer demand. There is also concern that if overall quality declines, the Washington apricot industry could lose sales to other apricot producing regions.</P>
        <P>However, due to the evolving nature of fresh fruit marketing, many wholesale and retail apricot buyers now require their own specific criteria for product quality from all handlers. Therefore, the Committee believes the cost of inspection and certification, which is mandated when the handling regulations are in effect, may exceed the benefits derived.</P>
        <P>After much consideration, the Committee recommended the suspension of the handling regulations prescribed under the order for the 2012-13 fiscal period. This action will allow the Committee to evaluate the impact that suspended regulations will have on the quality of Washington apricots. Should the market situation so dictate, the Committee may take appropriate action to continue the suspension of the handling regulations or recommend termination of the order.</P>
        <P>This rule enables Washington apricot handlers to ship apricots without regard to the order's minimum grade, size, quality, maturity, and inspection requirements. This suspension action will also allow handlers to decrease their total costs by eliminating the expenses associated with mandatory inspection. However, this rule does not impede handlers from seeking product inspection on a voluntary basis if they find inspection desirable. Prior to the end of the fiscal period, the Committee will evaluate the effect that the suspension of the handling regulations has on the 2012 market conditions and on producer returns, and if necessary, make recommendations to USDA for changes.</P>
        <P>The suspension of the handling regulations will also result in the elimination of the inspection certificates being generated and forwarded to the Committee office by the Inspection Service. The Committee has used these certificates as the basis for the collection of handler assessments and for compiling apricot industry statistics. As a result of not having the information provided by the inspection certificates, the Committee will enter into a memorandum of understanding with the Washington State Department of Agriculture in order to obtain the information necessary to collect assessments and generate statistical information.</P>
        <P>Authorization to assess handlers enables the Committee to incur expenses that are reasonable and necessary to administer the program.</P>
        <P>Consistent with the suspension of § 922.321, this rule also suspends § 922.111 of the rules and regulations in effect under the order. Section 922.111 contains provisions for handlers to apply for waivers from mandatory inspection when such inspection is not readily available from the Inspection Service. With the suspension of regulation, such waivers are no longer necessary.</P>
        <HD SOURCE="HD1">Initial Regulatory Flexibility Analysis</HD>
        <P>Pursuant to requirements set forth in the Regulatory Flexibility Act (RFA) (5 U.S.C. 601-612), the Agricultural Marketing Service (AMS) has considered the economic impact of this action on small entities. Accordingly, AMS has prepared this initial regulatory flexibility analysis.</P>
        <P>The purpose of the RFA is to fit regulatory actions to the scale of business subject to such actions in order that small businesses will not be unduly or disproportionately burdened. Marketing orders issued pursuant to the Act, and the rules issued thereunder, are unique in that they are brought about through group action of essentially small entities acting on their own behalf.</P>
        <P>There are approximately 20 handlers of Washington apricots who are subject to regulation under the marketing order and approximately 94 apricot producers in the regulated area. Small agricultural service firms are defined by the Small Business Administration (SBA) (13 CFR 121.201) as those having annual receipts of less than $7,000,000, and small agricultural producers are defined as those having annual receipts of less than $750,000.</P>
        <P>Apricot production has been approximately 4,200 to 8,900 tons per year for the past several years. The National Agricultural Statistics Service (NASS) reports that all Washington apricot handlers combined ship approximately $7,132,000 worth of apricots during the 2011 season. In addition, based on acreage, production, and producer prices reported by NASS, and the total number of Washington apricot producers, average annual producer receipts are approximately $76,000, which is considerably less than the $750,000 threshold. In view of the foregoing, it can be concluded that a majority of the handlers and producers of Washington apricots may be classified as small entities.</P>
        <P>At its May 24, 2012, meeting, the Committee unanimously recommended suspending the handling regulations for the 2012-13 fiscal period.</P>
        <P>This rule suspends the handling regulations specified in §§ 922.111 and 922.321. The suspension of these handling regulations will allow the Washington apricot industry to market apricots without regard to minimum grade, size, quality, maturity, and inspection requirements prescribed under the federal marketing order. Authority for this action is provided in § 922.53.</P>

        <P>The handling regulations help ensure that only acceptable quality apricots<PRTPAGE P="1129"/>enter fresh market channels, thereby ensuring consumer satisfaction, increasing sales, and improving returns to producers. While the industry continues to believe that quality is an important factor in maintaining sales, the Committee believes the cost of inspection and certification may exceed the benefits derived. The Committee also believes that the demands of wholesale buyers and consumers will drive handlers and producers to maintain a high level of product quality without the necessity of minimum quality standards and mandatory inspections. The Committee will review the outcome of the handling regulation suspension prior to the end of the 2012-13 fiscal period and determine if continued suspension, or alternatively, termination of the marketing order is warranted. The handling regulations will be automatically reinstated on April 1, 2013.</P>
        <P>Apricot prices have fluctuated considerably in recent years, and at times some producers have faced difficulty covering their total costs. In response to the adverse economic conditions experienced by the industry, the Committee discussed the possibility of reducing expenses through the elimination of mandatory inspection. The Committee considered the potential consequences of suspending the handling and inspection requirements, and how this could result in lower quality apricots being shipped to fresh markets. Also, if fruit quality were to decline, there is some concern among Committee members that the Washington apricot industry could lose sales to other apricot producing regions.</P>
        <P>While acknowledging these concerns, the Committee also believes that the current marketing conditions make the program unnecessary, because the costs of regulation may be greater than the benefits gained. Therefore, the Committee recommended the suspension of the handling regulations for the 2012-13 fiscal period. The Committee will review the impacts of the suspension prior to the end of the fiscal period and consider appropriate actions for ensuing seasons.</P>
        <P>This rule enables handlers to ship apricots without regard to the order's minimum grade, size, quality, maturity, and inspection requirements during the 2012-13 fiscal period. This rule allows handlers to decrease their overall costs by eliminating the costs associated with mandatory inspection. This rule, however, does not impede handlers from seeking inspection on a voluntary basis if they find inspection desirable.</P>
        <P>The suspension of the handling regulations will result in the elimination of mandatory inspections and, in turn, the inspection certificates generated by the Inspection Service and provided to the Committee. The Committee has used such certificates for assessment billing purposes and for compiling industry statistics. As a result of needing the information that was previously provided by the inspection certificates, the Committee will enter into a memorandum of understanding with the Washington State Department of Agriculture in order to obtain information on which to collect assessments and generate statistical information.</P>
        <P>The Committee anticipates that this rule will not negatively impact small handlers and producers because it suspends minimum grade, size, quality, maturity, and inspection requirements prescribed under the order. The total cost of inspection and certification for fresh shipments of Washington apricots during the 2011 marketing season is estimated by the Committee to have been $0.23 per hundredweight, or approximately $12,700 total. This represents approximately $635 per handler. Since handlers may continue to have their apricots voluntarily inspected, the Committee expects that some handlers will continue to have at least a portion of their fresh apricots inspected and certified by the Inspection Service.</P>
        <P>Alternatives to the suspension of the handling regulations considered by the Committee included maintaining the status quo, suspending regulations indefinitely, and terminating the marketing order in its entirety. The Committee believes that the continuation of regulation would be an unnecessary burden on the industry, given the evolving marketing conditions and future outlook. Thus, continuing to regulate in the same manner was not a viable option to the Committee. The Committee also discussed suspending regulation indefinitely, but rejected this alternative at this time. The Committee believes that suspending the handling regulations for one season will provide sufficient information to evaluate the impact this has on the quality of Washington apricots. Last of all, the Committee considered terminating the order in its entirety, but similarly declined the option. The Committee will review the impacts of the suspension prior to the end of the fiscal period and consider appropriate actions for ensuing seasons.</P>
        <P>In accordance with the Paperwork Reduction Act of 1995, (44 U.S.C. Chapter 35), the order's information collection requirements have been previously approved by the Office of Management and Budget (OMB) and assigned OMB No. 0581-0189. No changes in those requirements as a result of this action are necessary. Should any changes become necessary, they would be submitted to OMB for approval.</P>
        <P>This rule will not impose any additional reporting or recordkeeping requirements on either small or large apricot handlers. As with all Federal marketing order programs, reports and forms are periodically reviewed to reduce information requirements and duplication by industry and public sector agencies.</P>
        <P>AMS is committed to complying with the E-Government Act, to promote the use of the Internet and other information technologies to provide increased opportunities for citizen access to Government information and services, and for other purposes.</P>
        <P>In addition, USDA has not identified any relevant Federal rules that duplicate, overlap or conflict with this rule.</P>
        <P>Further, the Committee's meeting was widely publicized throughout the Washington apricot industry and all interested persons were invited to attend the meeting and participate in Committee deliberations. Like all Committee meetings, the May 24, 2012, meeting was a public meeting and all entities, both large and small, were able to express their views on this issue. Finally, interested persons are invited to submit comments on this interim rule, including the regulatory and informational impacts of this action on small businesses.</P>

        <P>A small business guide on complying with fruit, vegetable, and specialty crop marketing agreements and orders may be viewed at:<E T="03">www.ams.usda.gov/MarketingOrdersSmallBusinessGuide.</E>Any questions about the compliance guide should be sent to Laurel May at the previously mentioned address in the<E T="02">FOR FURTHER INFORMATION CONTACT</E>section.</P>
        <P>This rule invites comments on the suspension of the handling regulations prescribed under the Washington apricot marketing order. Any comments timely received will be considered prior to finalization of this rule.</P>
        <P>After consideration of all relevant material presented, including the Committee's recommendation, and other information, it is found that the regulatory requirements no longer tend to effectuate the declared policy of the Act, and are therefore being suspended.</P>

        <P>Pursuant to 5 U.S.C. 553, it is also found and determined upon good cause that it is impracticable, unnecessary, and contrary to the public interest to<PRTPAGE P="1130"/>give preliminary notice prior to putting this rule into effect, and that good cause exists for not postponing the effective date of this rule until 30 days after publication in the<E T="04">Federal Register</E>because: (1) This interim rule is a relaxation in the apricot handling regulations and should be in place as soon as possible for the 2012-13 fiscal period; (2) handlers need to know as soon as possible that they are free to market their apricots without regard to the order's handling regulations; (3) this issue has been widely discussed at various industry and association meetings and the Committee has kept the industry well informed; (4) handlers are aware of this rule, which was recommended at a public meeting; and (5) this rule provides a 60-day comment period and any comments received will be considered prior to finalization of this rule.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 7 CFR Part 922</HD>
          <P>Apricots, Marketing agreements, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        
        <P>For the reasons set forth in the preamble, 7 CFR part 922 is amended as follows:</P>
        <REGTEXT PART="922" TITLE="7">
          <PART>
            <HD SOURCE="HED">PART 922—APRICOTS GROWN IN DESIGNATED COUNTIES IN WASHINGTON</HD>
          </PART>
          <AMDPAR>1. The authority citation for 7 CFR part 922 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>7 U.S.C. 601-674.</P>
          </AUTH>
        </REGTEXT>
        <REGTEXT PART="922" TITLE="7">
          <SECTION>
            <SECTNO>§§ 922.111 and 922.321</SECTNO>
            <SUBJECT>[Suspended]</SUBJECT>
          </SECTION>
          <AMDPAR>2. In Part 922, §§ 922.111 and 922.321 are suspended in their entirety from January 9, 2013 through March 31, 2013.</AMDPAR>
        </REGTEXT>
        <SIG>
          <DATED>Dated: January 2, 2013.</DATED>
          <NAME>David R. Shipman,</NAME>
          <TITLE>Administrator, Agricultural Marketing Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00129 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-02-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Agricultural Marketing Service</SUBAGY>
        <CFR>7 CFR Part 987</CFR>
        <DEPDOC>[Docket No. AMS-FV-12-0035; FV12-987-1 IR]</DEPDOC>
        <SUBJECT>Domestic Dates Produced or Packed in Riverside County, CA; Decreased Assessment Rate</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Agricultural Marketing Service, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Interim rule with request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This rule decreases the assessment rate established for the California Date Administrative Committee (Committee) for the 2012-13 and subsequent crop years from $1.00 to $0.90 per hundredweight of dates handled. The Committee locally administers the marketing order which regulates the handling of dates grown or packed in Riverside County, California. Assessments upon date handlers are used by the Committee to fund reasonable and necessary expenses of the program. The crop year begins October 1 and ends September 30. The assessment rate will remain in effect indefinitely unless modified, suspended, or terminated.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Effective January 9, 2013. Comments received by March 11, 2013, will be considered prior to issuance of a final rule.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Interested persons are invited to submit written comments concerning this rule. Comments must be sent to the Docket Clerk, Marketing Order Agreement Division, Fruit and Vegetable Programs, AMS, USDA, 1400 Independence Avenue SW., STOP 0237, Washington, DC 20250-0237; Fax: (202) 720-8938; or Internet:<E T="03">http://www.regulations.gov.</E>Comments should reference the docket number and the date and page number of this issue of the<E T="04">Federal Register</E>and will be available for public inspection in the Office of the Docket Clerk during regular business hours, or can be viewed at:<E T="03">http://www.regulations.gov.</E>All comments submitted in response to this rule will be included in the record and will be made available to the public. Please be advised that the identity of the individuals or entities submitting the comments will be made public on the Internet at the address provided above.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Jeff Smutny, Marketing Specialist, or Kurt J. Kimmel, Regional Director, California Marketing Field Office, Marketing Order and Agreement Division, Fruit and Vegetable Program, AMS, USDA; Telephone: (559) 487-5901, Fax: (559) 487-5906, or Email:<E T="03">Jeffrey.Smutny@ams.usda.gov</E>or<E T="03">Kurt.Kimmel@ams.usda.gov.</E>
          </P>

          <P>Small businesses may request information on complying with this regulation by contacting Laurel May, Marketing Order and Agreement Division, Fruit and Vegetable Program, AMS, USDA, 1400 Independence Avenue SW., STOP 0237, Washington, DC 20250-0237; Telephone: (202) 720-2491, Fax: (202) 720-8938, or Email:<E T="03">Laurel.May@ams.usda.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>This rule is issued under Marketing Agreement and Order No. 987, both as amended (7 CFR part 987), regulating the handling of dates produced or packed in Riverside County, California, hereinafter referred to as the “order.” The order is effective under the Agricultural Marketing Agreement Act of 1937, as amended (7 U.S.C. 601-674), hereinafter referred to as the “Act.”</P>
        <P>The Department of Agriculture (USDA) is issuing this rule in conformance with Executive Order 12866.</P>
        <P>This rule has been reviewed under Executive Order 12988, Civil Justice Reform. Under the marketing order now in effect, Riverside County, California date handlers are subject to assessments. Funds to administer the order are derived from such assessments. It is intended that the assessment rate as issued herein will be applicable to all assessable dates beginning October 1, 2012, and continue until amended, suspended, or terminated.</P>
        <P>The Act provides that administrative proceedings must be exhausted before parties may file suit in court. Under section 608c(15)(A) of the Act, any handler subject to an order may file with USDA a petition stating that the order, any provision of the order, or any obligation imposed in connection with the order is not in accordance with law and request a modification of the order or to be exempted therefrom. Such handler is afforded the opportunity for a hearing on the petition. After the hearing, USDA would rule on the petition. The Act provides that the district court of the United States in any district in which the handler is an inhabitant, or has his or her principal place of business, has jurisdiction to review USDA's ruling on the petition, provided an action is filed not later than 20 days after the date of the entry of the ruling.</P>
        <P>This rule decreases the assessment rate established for the Committee for the 2012-13 and subsequent crop years from $1.00 to $0.90 per hundredweight of dates.</P>

        <P>The California date marketing order provides authority for the Committee, with the approval of USDA, to formulate an annual budget of expenses and collect assessments from handlers to administer the program. The members of the Committee are producers and handlers of Riverside County, California dates. They are familiar with the Committee's needs and with the costs for goods and services in their local area and are thus in a position to formulate an appropriate budget and assessment rate. The assessment rate is formulated and discussed in a public meeting. Thus, all directly affected persons have<PRTPAGE P="1131"/>an opportunity to participate and provide input.</P>
        <P>For the 2010-11 and subsequent crop years, the Committee recommended, and USDA approved, an assessment rate that would continue in effect from crop year to crop year unless modified, suspended, or terminated by USDA upon recommendation and information submitted by the Committee or other information available to USDA.</P>
        <P>The Committee met on June 12, 2012, and unanimously recommended 2012-13 expenditures of $260,000 and an assessment rate of $0.90 per hundredweight of Riverside County, California dates. In comparison, last year's budgeted expenditures were $265,000. The assessment rate of $0.90 is $0.10 lower than the rate currently in effect. The Committee recommended a lower assessment rate because the 2012-13 crop is expected to be larger than the previous year. Income generated through the lower assessment rate combined with cull surplus contributions and funds contributed by the California Date Commission for shared marketing activities, should be sufficient to cover anticipated 2012-13 expenses.</P>
        <P>Proceeds from sales of cull dates are deposited into a surplus account for subsequent use by the Committee in covering the surplus pool share of the Committee's expenses. Handlers may also dispose of cull dates of their own production within their own livestock-feeding operation; otherwise, such cull dates must be shipped or delivered to the Committee for sale to non-human food product outlets. Pursuant to § 987.72(b), the Committee is authorized to temporarily use funds derived from assessments to defray expenses incurred in disposing of surplus dates. All such expenses are required to be deducted from proceeds obtained by the Committee from the disposal of surplus dates. For the 2012-13 crop year, the Committee estimated that $3,000 from the surplus account would be needed to temporarily defray expenses incurred in disposing of surplus dates.</P>
        <P>The major expenditures recommended by the Committee for the 2012-13 crop year include $110,000 for generic marketing promotions, $83,520 for general and administrative expenses, $43,800 for nutrition marketing programs, $12,680 for a contingency fund, and $5,000 for licensing renewal. Budgeted expenses for these items in 2011-12 were $96,300 for generic marketing promotions, $90,000 for general and administrative expenses, $73,600 for nutrition marketing programs, and $5,100 for marketing contingency.</P>
        <P>The assessment rate recommended by the Committee was derived based upon the anticipated size of the 2012-13 crop, the Committee's estimates of the incoming reserve, other income, and anticipated expenses. Date shipments for the year are estimated at 26,500,000 pounds which should provide $238,500 in assessment income. Income derived from handler assessments, along with a $3,000 reimbursement for the cost of disposing of surplus culls, and a $40,000 contribution from the California Date Commission for shared marketing expenses, should be adequate to cover budgeted expenses.</P>
        <P>Section 987.72(d) states that the Committee may maintain a monetary reserve not to exceed the average of one year's expenses incurred during the most recent five preceding crop years, except that an established reserve need not be reduced to conform to any recomputed average. Funds in the reserve are available for the Committee's use during the crop year to cover budgeted expenses as necessary or for other purposes deemed appropriate by USDA. The Committee expects to carry a $15,000 reserve into the 2012-13 crop year. They expect to add $21,500 to the reserve during the year, for a desired carryout of approximately $36,500, which is well below the limit specified in the order.</P>
        <P>The assessment rate established in this rule will continue in effect indefinitely unless modified, suspended, or terminated by USDA upon recommendation and information submitted by the Committee or other available information.</P>
        <P>Although this assessment rate is effective for an indefinite period, the Committee will continue to meet prior to or during each crop year to recommend a budget of expenses and consider recommendations for modification of the assessment rate. The dates and times of Committee meetings are available from the Committee or USDA. Committee meetings are open to the public and interested persons may express their views at these meetings. USDA will evaluate Committee recommendations and other available information to determine whether modification of the assessment rate is needed. Further rulemaking will be undertaken as necessary. The Committee's 2012-13 budget and those for subsequent crop years will be reviewed and, as appropriate, approved by USDA.</P>
        <HD SOURCE="HD1">Initial Regulatory Flexibility Analysis</HD>
        <P>Pursuant to requirements set forth in the Regulatory Flexibility Act (RFA) (5 U.S.C. 601-612), the Agricultural Marketing Service (AMS) has considered the economic impact of this rule on small entities. Accordingly, AMS has prepared this initial regulatory flexibility analysis.</P>
        <P>The purpose of the RFA is to fit regulatory actions to the scale of business subject to such actions in order that small businesses will not be unduly or disproportionately burdened. Marketing orders issued pursuant to the Act, and the rules issued thereunder, are unique in that they are brought about through group action of essentially small entities acting on their own behalf.</P>
        <P>There are approximately 79 producers of dates in the production area and 11 handlers subject to regulation under the marketing order. Small agricultural producers are defined by the Small Business Administration (13 CFR 121.201) as those having annual receipts less than $750,000, and small agricultural service firms are defined as those whose annual receipts are less than $7,000,000.</P>
        <P>According to the National Agricultural Statistics Service (NASS), data for the most recently completed crop year (2011) shows that about 3.68 tons, or 7,360 pounds, of dates were produced per acre. The 2011 grower price published by the NASS was $1,320 per ton, or $.66 per pound. Thus, the value of date production per acre in 2011 averaged about $4,858 (7,360 pounds times $.66 per pound). At that average price, a producer would have to farm over 154 acres to receive an annual income from dates of $750,000 ($750,000 divided by $4,858 per acre equals 154 acres). According to Committee staff, the majority of California date producers farm less than 154 acres. Thus, it can be concluded that the majority of date producers could be considered small entities. According to data from the Committee staff, the majority of handlers of California dates may also be considered small entities.</P>

        <P>This rule decreases the assessment rate established for the Committee and collected from handlers for the 2012-13 and subsequent crop years from $1.00 to $0.90 per hundredweight of dates handled. The Committee unanimously recommended 2012-13 expenditures of $260,000 and an assessment rate of $0.90 per hundredweight of dates, which is $0.10 lower than the 2011-12 rate, currently in effect. The quantity of assessable dates for the 2012-13 crop year is estimated at 26,500,000 pounds. Thus, the $0.90 rate should provide $238,500 in assessment income. Income derived from handler's assessments, along with the $3,000 contribution from<PRTPAGE P="1132"/>the surplus program, and the $40,000 contribution for shared marketing expenses should be adequate to meet the 2012-13 crop year expenses.</P>
        <P>The major expenditures recommended by the Committee for the 2012-13 crop year include $110,000 for generic marketing promotions, $83,520 for general and administrative expenses, $43,800 for nutrition marketing programs, $12,680 for a contingency fund, and $5,000 for licensing renewal. Budgeted expenses for these items in 2011-12 were $96,300 for generic marketing promotions, $90,000 for general and administrative expenses, $73,600 for nutrition marketing programs, and $5,100 for marketing contingency.</P>
        <P>The Committee recommended a lower assessment rate because the 2012-13 crop is expected to be larger than the previous year. As mentioned earlier, date shipments for the year are estimated at 26,500,000 pounds which should provide $238,500 in assessment income. Income derived from handler assessments, cull surplus contributions, and funds contributed by the California Date Commission for shared marketing activities, should be sufficient to cover anticipated 2012-13 expenses.</P>
        <P>Section 987.72(d) states that the Committee may maintain a monetary reserve not to exceed the average of one year's expenses incurred during the most recent five preceding crop years, except that an established reserve need not be reduced to conform to any recomputed average. Funds in the reserve are available for the Committee's use during the crop year to cover budgeted expenses as necessary or for other purposes deemed appropriate by USDA. The Committee expects to carry a $15,000 reserve into the 2012-13 crop year. They expect to add $21,500 to the reserve during the year, for a desired carryout of approximately $36,500, which is well below the limit specified in the order.</P>
        <P>The Committee reviewed and unanimously recommended 2012-13 crop year expenditures of $260,000. Prior to arriving at this budget, the Committee considered information from various sources, such as the Committee's Marketing Subcommittee, and Budget Committee. Alternative expenditure levels were discussed by these groups, based upon relative value of various marketing projects to the date industry. The assessment rate of $0.90 per hundredweight of dates was then derived, based upon the anticipated 2012-13 crop size, and the Committee's estimates of the incoming reserve, other income, and anticipated expenses. Assessing at the $0.90 per hundredweight of dates will generate approximately $21,500 less than the anticipated expenses, which the Committee determined to be acceptable, as other sources of income should provide adequate funds to cover expenses.</P>
        <P>A review of historical information and preliminary information pertaining to the upcoming crop year indicates that the grower price for the 2012-13 season could range between $1,180 and $1,320 per ton of dates. Therefore, the estimated assessment revenue for the 2012-13 crop year as a percentage of total grower revenue could range between 1.5 and 1.4 percent.</P>
        <P>This action decreases the assessment obligation imposed on handlers. Assessments are applied uniformly on all handlers, and some of the costs may be passed on to producers. However, decreasing the assessment rate reduces the burden on handlers, and may reduce the burden on producers. In addition, the Committee's meeting was widely publicized throughout the California date industry and all interested persons were invited to attend the meeting and participate in Committee deliberations on all issues. Like all Committee meetings, the June 12, 2012, meeting was a public meeting and all entities, both large and small, were able to express views on this issue. Finally, interested persons are invited to submit comments on this interim final rule, including the regulatory and informational impacts of this action on small businesses.</P>
        <P>In accordance with the Paperwork Reduction Act of 1995, (44 U.S.C. Chapter 35), the order's information collection requirements have been previously approved by the Office of Management and Budget (OMB) and assigned OMB No. 0581-0178. No changes in those requirements as a result of this action are necessary. Should any changes become necessary, they would be submitted to OMB for approval.</P>
        <P>This action imposes no additional reporting or recordkeeping requirements on either small or large Riverside County, California, date handlers. As with all Federal marketing order programs, reports and forms are periodically reviewed to reduce information requirements and duplication by industry and public sector agencies.</P>
        <P>AMS is committed to complying with the E-Government Act, to promote the use of the Internet and other information technologies to provide increased opportunities for citizen access to Government information and services, and for other purposes.</P>
        <P>USDA has not identified any relevant Federal rules that duplicate, overlap, or conflict with this rule.</P>

        <P>A small business guide on complying with fruit, vegetable, and specialty crop marketing agreements and orders may be viewed at:<E T="03">http://www.ams.usda.gov/MarketingOrdersSmallBusinessGuide.</E>Any questions about the compliance guide should be sent to Laurel May at the previously mentioned address in the<E T="02">FOR FURTHER INFORMATION CONTACT</E>section.</P>
        <P>After consideration of all relevant material presented, including the information and recommendation submitted by the Committee and other available information, it is hereby found that this rule, as hereinafter set forth, will tend to effectuate the declared policy of the Act.</P>

        <P>Pursuant to 5 U.S.C. 553, it is also found and determined upon good cause that it is impracticable, unnecessary, and contrary to the public interest to give preliminary notice prior to putting this rule into effect, and that good cause exists for not postponing the effective date of this rule until 30 days after publication in the<E T="04">Federal Register</E>because: (1) The 2012-13 crop year begins on October 1, 2012, and the marketing order requires that the rate of assessment for each crop year apply to all assessable dates handled during such crop year; (2) the action decreases the assessment rate for assessable dates beginning with the 2012-13 crop year; (3) handlers are aware of this action which was unanimously recommended by the Committee at a public meeting and is similar to other assessment rate actions issued in past years; and (4) this interim final rule provides a 60-day comment period, and all comments timely received will be considered prior to finalization of this rule.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 7 CFR Part 987</HD>
          <P>Dates, Marketing agreements, Reporting and recordkeeping requirements.</P>
        </LSTSUB>
        
        <P>For the reasons set forth in the preamble, 7 CFR part 987 is amended as follows:</P>
        <REGTEXT PART="987" TITLE="7">
          <PART>
            <HD SOURCE="HED">PART 987—DOMESTIC DATES PRODUCED OR PACKED IN RIVERSIDE COUNTY, CALIFORNIA</HD>
          </PART>
          <AMDPAR>1. The authority citation for 7 CFR part 987 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>7 U.S.C. 601-674.</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="987" TITLE="7">
          <AMDPAR>2. Section 987.339 is revised to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 987.339</SECTNO>
            <SUBJECT>Assessment rate.</SUBJECT>

            <P>On and after October 1, 2012, an assessment rate of  $0.90 per<PRTPAGE P="1133"/>hundredweight is established for Riverside County, California dates.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: January 2, 2013.</DATED>
          <NAME>David R. Shipman,</NAME>
          <TITLE>Administrator, Agricultural Marketing Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00185 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-02-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Federal Aviation Administration</SUBAGY>
        <CFR>14 CFR Parts 21 and 36</CFR>
        <DEPDOC>[Docket No. FAA-2011-0629; Amdt. Nos. 21-97; 36-29]</DEPDOC>
        <RIN>RIN 2120-AJ76</RIN>
        <SUBJECT>Noise Certification Standards for Tiltrotors</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 amends the regulations governing noise certification standards for issuing type and airworthiness certificates for a new civil, hybrid airplane-rotorcraft known as the tiltrotor. This noise standard establishes new noise limits and procedures as the basis to ensure consistent aviation noise reduction technology is incorporated in tiltrotors for environmental protection. It provides uniform noise certification standards for tiltrotors certificated in the United States and harmonizes the U.S. regulations with the standards of the International Civil Aviation Organization's (ICAO) Annex 16.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Effective March 11, 2013.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>For information on where to obtain copies of rulemaking documents and other information related to this final rule, see “How To Obtain Additional Information” in the<E T="02">SUPPLEMENTARY INFORMATION</E>section of this document.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>For technical questions concerning this final rule contact Sandy Liu, AEE-100, Office of Environment and Energy, Federal Aviation Administration, 800 Independence Avenue SW., Washington, DC 20591; telephone: (202) 493-4864; facsimile (202) 267-5594; email:<E T="03">sandy.liu@faa.gov.</E>
          </P>

          <P>For legal questions concerning this final rule contact Karen Petronis, AGC-200, Office of the Chief Counsel, International Law, Legislation, and Regulations Division, Federal Aviation Administration, 800 Independence Avenue SW., Washington, DC 20591; telephone: (202) 267-3073; email:<E T="03">karen.petronis@faa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Authority for This Rulemaking</HD>
        <P>The FAA's authority to issue rules on aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority.</P>
        <P>This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart III, Section 44715, Controlling aircraft noise and sonic boom. Under that section, the FAA is charged with prescribing regulations to measure and abate aircraft noise. This regulation is within the scope of that authority since it would establish new noise certification test procedures and noise limits for a new class of aircraft. Applicants for type certificates, changes in type design, and airworthiness certificates for tiltrotors are required to comply with these new regulations.</P>
        <HD SOURCE="HD1">Overview of Final Rule</HD>
        <P>The standards in this final rule apply to the issuance of an original type certificate, changes to a type certificate, and the issuance of a standard airworthiness certificate for tiltrotors. This final rule creates noise certification standards that are applicable to all tiltrotors, such as the AgustaWestland Model AW609 currently under development. These regulations incorporate the same standards as ICAO Annex 16, Volume 1, Chapter 13, Attachment F (Amendment 7) for tiltrotors, consistent with the FAA goal of harmonizing U.S. regulations with international standards.</P>
        <HD SOURCE="HD1">Background</HD>
        <P>A new aircraft type known as a tiltrotor is currently in production after more than six decades of research and development. The aircraft uses rotating nacelles, a hybrid of propellers and helicopter rotors, to provide both lift and propulsive force. The tiltrotor is designed to function as a helicopter for takeoff and landing and as an airplane during the en-route portion of flight operations.</P>
        <P>The most recognizable tiltrotor operating today is the V-22 Osprey used by the U.S. Marines and the U.S. Air Force. The V-22 Osprey was designed for the U.S. Department of Defense Special Operations Forces and can transport 24 fully equipped troops. The proposed civil version of the tiltrotor would carry up to nine passengers.</P>
        <P>The tiltrotor concept was first explored for the U.S. Army in the mid-1950s as a convertiplane concept that incorporated mixed vertical and forward flight capabilities. In 1958, Bell Helicopter Textron Inc. (Bell) of Fort Worth, Texas developed the XV-3 tiltrotor for a joint research program between the U.S. Army and the U.S. Air Force. The Bell XV-3 completed a successful full conversion from vertical flight to forward cruise and demonstrated the feasibility of tiltrotor technology. Following the successful full conversion of the Bell XV-3, the U.S. Army and National Aeronautics and Space Administration awarded Bell a prototype development contract in the mid 1970s to build two Bell XV-15 tiltrotor demonstrator aircraft. These tiltrotor aircraft served as predecessors to the V-22 Osprey to demonstrate mature tiltrotor technology and flight capabilities.</P>
        <HD SOURCE="HD2">ICAO Noise Certification Standards</HD>
        <P>ICAO is the international body with responsibility for the development of International Standards and Recommended Practices pursuant to the Convention on International Civil Aviation (the Chicago Convention). Consistent with their obligations under the Chicago Convention, Contracting States agree to implement ICAO standards in their national regulations to the extent practicable. The standards for aircraft noise are contained in Annex 16, Environmental Protection, Volume 1, Aircraft Noise.</P>
        <P>In anticipation of civil tiltrotor production, ICAO's Committee on Aviation Environmental Protection (CAEP) chartered the Tiltrotor Task Group (TRTG) in 1997 to develop noise certification guidelines for tiltrotors. The FAA participated in the TRTG and its development of the tiltrotor noise guidelines from 1997 to 2000. The ICAO tiltrotor guidelines used the same noise limits that the United States had incorporated into part 36, Appendix H for helicopter noise certification. The ICAO has included additional requirements that are unique to the design of tiltrotors.</P>
        <P>On June 29, 2001, the TRTG's guidelines were adopted by the ICAO Council for incorporation into Annex 16, Volume 1, Chapter 13, Attachment F (Amendment 7). The ICAO guidelines became effective on October 29, 2001, with an applicability date of March 21, 2002.</P>
        <HD SOURCE="HD2">Statement of the Problem</HD>

        <P>Current regulations in part 36 do not contain noise certification requirements specific to the tiltrotor and its unique<PRTPAGE P="1134"/>flight capabilities. Since no standards for the tiltrotor currently exist, the FAA is adding new standards to part 36, and amending part 21, § 21.93 (Classification of Changes in Type Design) to accommodate certification of the tiltrotor. In order to harmonize the U.S. regulations with the international standards, this rulemaking adopts the same noise certification standards as used in ICAO Annex 16, Volume 1, Chapter 13, Attachment F (Amendment 7) for tiltrotors.</P>
        <HD SOURCE="HD2">Type Certification Activity in the United States</HD>
        <P>As the tiltrotor concept and technology proved promising with the production of the V-22 Osprey, Bell and Agusta (now AgustaWestland) established a joint business venture in September 1998 to co-develop the Bell/Agusta model BA609 civil tiltrotor.</P>
        <P>In August 1996, Bell, the original and lead developer of the tiltrotor, applied for a U.S. type certificate for the model BA609 tiltrotor, prior to the establishment of the joint venture. The BA609 would be type certificated as a “special class” of aircraft under §§ 21.17 and 21.21, using the applicable airworthiness provisions of part 25 (Airworthiness Standards: Transport Category Airplanes) and part 29 (Airworthiness Standards: Transport Category Rotorcraft). This is the first application for this class of aircraft.</P>
        <P>In June 2011, the contract for the joint tiltrotor program between Bell and AgustaWestland was renegotiated, with AgustaWestland assuming full ownership. The change in ownership resulted in the BA609 designation being renamed to the AW609, and on February 15, 2012, AgustaWestland applied for a type certificate from the FAA. AgustaWestland is targeting existing helicopter operators as the primary civil market for the AW609, and has stated that the AW609 could operate from existing heliports without the need for new infrastructure to accommodate the aircraft.</P>
        <HD SOURCE="HD2">Summary of the NPRM</HD>
        <P>The FAA published a notice of proposed rulemaking (NPRM) on June 21, 2011 (76 FR 36001) that proposed the changes to parts 21 and 36 discussed above that would establish noise certification standards for issuing type and airworthiness certificates for the tiltrotor.</P>
        <HD SOURCE="HD1">Discussion of Public Comments</HD>
        <P>The comment period for the NPRM closed on October 19, 2011. The FAA received one comment, from AgustaWestland. AgustaWestland stated that the proposed rule did not specify the entity that would determine the flyover configuration in Appendix K to Part 36. AgustaWestland recommended that the regulation specify that the applicant be the entity that prescribes the constant flyover aircraft configuration.</P>
        <P>The FAA agrees the regulation needs to specify what entity prescribes the constant flyover configuration. The FAA agrees the applicant is the proper entity, and has modified the final rule to incorporate this change.</P>
        <HD SOURCE="HD2">Differences Between the NPRM and the Final Rule</HD>

        <P>We are adopting this final rule for the reasons stated in the NPRM, with the following changes. First, the NPRM incorrectly included V<E T="52">MCP</E>and V<E T="52">MO</E>as requirements for tiltrotors. Both V<E T="52">MCP</E>and V<E T="52">MO</E>are voluntary reporting parameters for airspeeds at maximum continuous power and maximum operating limit for airplane mode as noted in the ICAO standards. The FAA is not requiring them in Part 36. However, the voluntary reporting of V<E T="52">MCP</E>and V<E T="52">MO</E>will be recommended in an accompanying Advisory Circular as supplemental information. The FAA is removing V<E T="52">MCP</E>and V<E T="52">MO</E>representing airplane mode from § 36.1 and Appendix K in the final rule since airplane mode is only a voluntary and supplemental condition for noise. The harshest (maximum) noise levels are identified in helicopter mode.</P>

        <P>Second, the labels used in the proposed Figure K.2 of Appendix K to part 36 incorrectly describe the two sideline noise measurement points as S<E T="52">(starboard)</E>and S<E T="52">(port)</E>instead of S<E T="52">(sideline)</E>for both. Since the flyover condition has a symmetrical test set-up, the generic label assignment, S<E T="52">(sideline)</E>, is used to indicate that flight from either direction is allowable without a reference to right or left. The figure is adopted in this final rule with the corrected labels.</P>
        <P>Third, the NPRM included the term “power-on” in section K6.1(f) of Appendix K to part 36. That terminology is outdated and is replaced in this final rule by the term “reference”.</P>
        <P>Fourth, the final rule adds the phrase “throughout the 10 dB-down time interval.” in sections K7.5, K7.9 and K7.10 of Appendix K of part 36 to be consistent throughout the appendix.</P>
        <P>Fifth, based on AgustaWestland's comment discussed previously, section K6.3(b) of Appendix K to part 36 specifies that the flyover configuration is to be selected by the applicant.</P>
        <HD SOURCE="HD1">Regulatory Evaluation, Regulatory Flexibility Determination, International Trade Impact Assessment, and Unfunded Mandates Assessment</HD>
        <P>Changes to Federal regulations must undergo several economic analyses. First, Executive Order 12866 and 13563 direct each Federal agency to propose or adopt a regulation only upon a reasoned determination that the benefits of the intended regulation justify its costs. Second, the Regulatory Flexibility Act of 1980 (Pub. L. 96-354) requires agencies to analyze the economic impact of regulatory changes on small entities. Third, the Trade Agreements Act (Pub. L. 96-39) prohibits agencies from setting standards that create unnecessary obstacles to the foreign commerce of the United States. In developing U.S. standards, this Trade Act requires agencies to consider international standards and, where appropriate, that they be the basis of U.S. standards. Fourth, the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4) requires agencies to prepare a written assessment of the costs, benefits, and other effects of proposed or final rules that include a Federal mandate likely to result in the expenditure by State, local, or tribal governments, in the aggregate, or by the private sector, of $100 million or more annually (adjusted for inflation with base year of 1995). This portion of the preamble summarizes the FAA's analysis of the economic impacts of this final rule.</P>
        <P>Department of Transportation Order DOT 2100.5 prescribes policies and procedures for simplification, analysis, and review of regulations. If the expected cost impact is so minimal that a proposed or final rule does not warrant a full evaluation, this order permits that a statement to that effect and the basis for it be included in the preamble if a full regulatory evaluation of the cost and benefits is not prepared. Such a determination has been made for this final rule. The reasoning for this determination follows,</P>
        <P>This final rule:</P>
        <P>(1) Imposes minimal incremental costs and provides benefits;</P>
        <P>(2) Is not an economically “significant regulatory action” as defined in section 3(f) of Executive Order 12866;</P>
        <P>(3) Is not significant as defined in DOT's Regulatory Policies and Procedures;</P>
        <P>(4) Will not have a significant economic impact on a substantial number of smallentities;</P>
        <P>(5) Will not have a significant effect on international trade; and</P>

        <P>(6) Will not impose an unfunded mandate on state, local, or tribal<PRTPAGE P="1135"/>governments, or on the private sector by exceeding the monetary threshold identified.</P>
        
        <FP>These analyses are summarized below.</FP>
        
        <P>No comments were received on the regulatory evaluation of the proposed rule. However, after the NPRM was published on June 21, 2011, there was a change in the ownership of the known civil tiltrotor program.</P>
        <P>When the NPRM was published, the one known civil tiltrotor development program was jointly owned by the Bell and AgustaWestland helicopter companies; the project was designated the BA609. In November, 2011 AgustaWestland purchased Bell's share of the civil tiltrotor program and changed the designation of the aircraft in development to AW609. The former Bell Agusta Aerospace Company (BAAC) was renamed the AgustaWestland Tilt-Rotor Company, LLC and merged with Agusta US Incorporated to become AgustaWestland Tilt-Rotor Company Incorporated, an American company that is the applicant for a type certificate for the AW609. The new company is incorporated in Delaware and is a wholly owned subsidiary of AgustaWestland that is owned by Finmeccanica, an Italian firm.</P>
        <P>The AgustaWestland Tilt-Rotor Company, Inc. has rented a facility at the Arlington, Texas Municipal Airport. The facility consists of approximately 99,000 square feet including a hangar/office building. The company plans to construct an adjacent office building. The facilities may be used for aircraft sales, engineering and design, flight testing, and aircraft maintenance, and other activities when approved by the airport.</P>
        <P>Because of the change in ownership of the civil tiltrotor program that occurred after the publication of the NPRM, this regulatory evaluation has been revised to incorporate the changed circumstances.</P>
        <P>There are currently no part 36 noise certification standards for tiltrotors in U.S. regulations. This final rule provides part 36 noise certification requirements for tiltrotors by adopting existing ICAO standards. The initial regulatory evaluation estimated that these noise requirements would be minimal cost. We asked for comments and received none. Accordingly, we affirm our determination that these requirements will be minimal cost. Providing U.S. tiltrotor noise certification standards will facilitate the startup and development of a new commercial class of aircraft, the tiltrotor, and allow for certification in the United States as exists for other aircraft designs. The tiltrotor aircraft type can then be marketed domestically and internationally. The FAA believes that this could result in substantial benefits.</P>
        <P>The FAA used the same price/cost estimates for the NPRM and received no comments. The FAA maintained in the NPRM that this rule was minimal cost and we received no comments on that determination.</P>
        <P>The total value of the estimated market equals the aircraft purchase price multiplied by the estimated units sold. The potential size of the tiltrotor market has been estimated using the sales projections of the previous developer, Bell/Agusta. In the next 10 years, one model of a civil tiltrotor is expected to be available, the AW609 (previously the BA609). This aircraft is currently in development.</P>

        <P>The price of a BA609 (now the AW609) was estimated to be $10 to $14 million (aircraftcompare.com, “Bell Agusta BA609”,<E T="03">http://www.aircraftcompare.com/helicopter-airplane/Bell%20Agusta%20BA609%20/279</E>). This is an increase from the original estimate of $7 million in 2000. The price of $14 million for a BA609 was used to estimate the potential market size for tiltrotor aircraft because AgustaWestland has not announced a purchase price for the AW609.</P>
        <P>Bell estimated that the market would result in sales of approximately 100 BA609s over 10 years, making the potential near-term tiltrotor market worth a nominal $1 billion to $1.4 billion. Table 1 shows the nominal and present value estimates of the tiltrotor market. The present value is based on a 7 percent discount rate, and a ten year production period with 10 tiltrotors being delivered each year. The present value of the tiltrotor market is estimated to be between $702,000,000 and $983,000,000.</P>
        <GPH DEEP="232" SPAN="3">
          <GID>ER08JA13.005</GID>
        </GPH>
        <PRTPAGE P="1136"/>
        <P>Table 2 summarizes the incremental manufacturer costs for the noise certification of a civil tiltrotor as discussed in the initial regulatory evaluation. At that time we determined that these costs were minimal. We received no comments on that determination and it is not changed in the final rule.</P>
        <GPH DEEP="236" SPAN="3">
          <GID>ER08JA13.006</GID>
        </GPH>
        <P>Issuance of a type certificate requires compliance with the applicable noise certification requirements of part 36. Full noise certification testing is generally required for each new aircraft type and for certain voluntary changes to type design that are classified as acoustical change under § 21.93(b). The incremental costs recur only when a new type certificate is issued, or when a change to a type design results after an acoustical change is made.</P>
        <P>Noise certification costs consist of four major items: Acoustics; Flight Test; Aircraft; and Miscellaneous. For tiltrotors noise certification, as for any aircraft certification, the noise demonstration flight testing and reporting is the largest incremental cost of the noise certification.</P>
        <P>To meet the regulatory requirements for noise control, acoustical measurements are used to quantify the characteristic noise levels of the aircraft. Almost half the noise certification expense ($250,000) is invested in the acoustics group equipment and analysis. This cost includes overall noise test planning and coordination, noise test site preparation and measurement set-up.</P>
        <P>The second highest noise certification expense involves the flight test support ($220,000). These are the expenses for configuring and preparing the aircraft to execute the required noise flight test procedures.</P>
        <P>The last two noise certification expense groups are aircraft and miscellaneous expenses. The aircraft expense ($50,000) involves costs associated with aircraft flight time, fuel, and flight crew support. Most other general expenses of test support are miscellaneous costs ($68,000).</P>
        <P>The cost estimates for noise certification were provided by Bell Helicopter Textron, the original developer of the civil tiltrotor. The cost of noise certification for the tiltrotor is comparable to that for a large helicopter (over 7,000 pounds). As shown in Table 2, the estimated total incremental cost of a single noise certification is $588,000. As the $588,000 would be incurred in the first year, the nominal value equals the present value.</P>
        <P>The FAA may incur costs in this certification process. However, these costs are not expected to vary significantly from the agency's current costs to noise certificate any other new aircraft type.</P>
        <P>Based on the above analyses, and consistent with the determinations made in the NPRM, this final rule is considered to be a minimal cost rule.</P>
        <P>Since the tiltrotor industry is still developing, the costs and benefits discussed are based on the single existing civil tiltrotor program. This final rule establishes the noise certification requirements for a tiltrotor. While the estimated benefits and costs are based on a single tiltrotor type, we have also determined that any future designs will benefit from the established noise certification requirements.</P>
        <P>The present value cost of the final rule is $588,000 for the certification of one tiltrotor type, about the same as would be required for a traditional helicopter design. The FAA considered this cost to be minimal in the NPRM. The FAA received no comments on this minimal cost determination. Therefore, the FAA considers this cost to be minimal in this final regulatory evaluation.</P>
        <P>The FAA believes that this final rule will be cost beneficial because it is minimal cost, and because it facilitates the development of tiltrotor aircraft and the commercial market for them.</P>
        <HD SOURCE="HD2">Regulatory Flexibility Determination</HD>

        <P>The Regulatory Flexibility Act of 1980 (RFA) establishes “as a principle of regulatory issuance that agencies shall endeavor, consistent with the objective of the rule and of applicable statutes, to fit regulatory and informational requirements to the scale of the businesses, organizations, and governmental jurisdictions subject to regulation.” To achieve that principle, the RFA requires agencies to solicit and consider flexible regulatory proposals and to explain the rationale for their actions. The RFA covers a wide-range of small entities, including small businesses, not-for-profit organizations and small governmental jurisdictions.<PRTPAGE P="1137"/>
        </P>
        <P>Agencies must perform a review to determine whether a proposed or final rule will have a significant economic impact on a substantial number of small entities. If the agency determines that it will, the agency must prepare a regulatory flexibility analysis as described in the Act.</P>
        <P>However, if an agency determines that a proposed or final rule is not expected to have a significant economic impact on a substantial number of small entities, section 605(b) of the 1980 RFA provides that the head of the agency may so certify and a regulatory flexibility analysis is not required. The certification must include a statement providing the factual basis for this determination, and the reasoning should be clear.</P>
        <P>When the NPRM was published, the tiltrotor was being developed by a joint venture of Bell Helicopter, an American company and AgustaWestland, an Italian firm. Because an American firm was potentially affected by the proposed rule, a Regulatory Flexibility Analysis was prepared. No comments were received on the Regulatory Flexibility Analysis which concluded there was no significant economic impact on a substantial number of small entities.</P>
        <P>After the NPRM was published, AgustaWestland, an Italian company, bought the ownership interests of Bell Helicopter. As such, the original BAAC was renamed and merged to become AgustaWestland Tilt-Rotor Company Incorporated, a wholly owned subsidiary of AgustaWestland, an Italian company. AgustaWestland is owned by Finmeccanica, also an Italian company.</P>
        <P>Section 601 of the RFA defines the term “small business” as follows: “The term “small business” has the same meaning as the term “small business concern” under section 3 of the Small Business Act, * * *”</P>
        <P>Section 3(a)(1) of the Small Business Act defines a small business concern as follows: “For the purposes of this Act, a small business concern, including, but not limited to enterprises that are engaged in the business of the production of food and fiber, ranching and raising of livestock, aquaculture, and all other farming and agricultural related industries, shall be deemed to be one which is independently owned and operated and which is not dominant in its field of operation: ”</P>
        <P>Section 3(a)(2) of the Small Business Act discusses the establishment of size standards. The Small Business Administration (SBA) size standard for a small entity in aircraft manufacturing is 1,500 employees.</P>
        <P>The AgustaWestland Tilt-Rotor Company Incorporated currently employs 12 people. While the number of employees of the AgustaWestland Tilt Rotor Company meets the SBA employment size standard for a small entity, the company is not a small entity as defined by the SBA because it is not independently owned and operated. The owner of the AgustaWestland Tilt-Rotor Company, Inc. is Finmeccanica, which has 75,733 employees, far exceeding the aircraft manufacturing size standard of 1,500 employees.</P>
        <P>There are no other companies which are known to be developing or manufacturing a civil tiltrotor. Therefore, Finmeccanica (including its subsidiaries) is the dominant company involved in the development of a civilian tiltrotor. This final rule is expected to be minimal cost and there are no small entities affected. Therefore, as the acting FAA Administrator, I certify that this final rule will not have a significant economic impact on a substantial number of small tiltrotor manufacturers.</P>
        <HD SOURCE="HD2">International Trade Impact Assessment</HD>
        <P>The Trade Agreements Act of 1979 (Pub. L. 96-39), as amended by the Uruguay Round Agreements Act (Pub. L. 103-465), prohibits Federal agencies from establishing standards or engaging in related activities that create unnecessary obstacles to the foreign commerce of the United States. Pursuant to these Acts, the establishment of standards is not considered an unnecessary obstacle to the foreign commerce of the United States, so long as the standard has a legitimate domestic objective, such as the protection of safety, and does not operate in a manner that excludes imports that meet this objective. The statute also requires consideration of international standards and, where appropriate, that they be the basis for U.S. standards.</P>
        <P>The FAA has assessed the potential effect of this final rule and determined that it will encourage international trade by adopting the international standards of ICAO as the basis for a rule for the noise certification of tiltrotors.</P>
        <HD SOURCE="HD2">Unfunded Mandates Assessment</HD>
        <P>Title II of the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4) requires each Federal agency to prepare a written statement assessing the effects of any Federal mandate in a proposed or final agency rule that may result in an expenditure of $100 million or more (adjusted annually for inflation) in any one year by State, local, and tribal governments, in the aggregate, or by the private sector; such a mandate is deemed to be a “significant regulatory action”. The FAA currently uses an inflation-adjusted value of $143.1 million in lieu of $100 million. This final rule does not contain such a mandate; therefore, the requirements of Title II do not apply.</P>
        <HD SOURCE="HD2">Paperwork Reduction Act</HD>
        <P>The Paperwork Reduction Act of 1995 (44 U.S.C. 3507(d)) requires that the FAA consider the impact of paperwork and other information collection burdens imposed on the public. The FAA has determined that there is no new requirement for information collection associated with this final rule.</P>
        <HD SOURCE="HD2">International Compatibility</HD>
        <P>In keeping with U.S. obligations under the Convention on International Civil Aviation, it is FAA policy to conform to International Civil Aviation Organization (ICAO) Standards and Recommended Practices to the maximum extent practicable. In 2001, ICAO adopted tiltrotor noise guidelines. This regulation harmonizes U.S. noise standards with the international standards by adopting the same requirements, adapted for the U.S. regulatory format.</P>
        <HD SOURCE="HD2">Environmental Analysis</HD>
        <P>FAA Order 1050.1E identifies FAA actions that are categorically excluded from preparation of an environmental assessment or environmental impact statement under the National Environmental Policy Act in the absence of extraordinary circumstances. This rule adopts internationally established noise standards for a new civil, hybrid airplane-rotorcraft known as the tiltrotor. Based on the presence of both helicopter and propeller airplane characteristics inherit in the tiltrotor, the noise standards use preexisting helicopter noise certification limits and procedures. This final rule adopts these noise limits to control the harshest (maximum) noise levels when the tiltrotor operates in its noisiest configuration—helicopter mode. In airplane mode, the tiltrotor is significantly quieter because of its low RPM design in cruise mode. The FAA finds the applicability of the noise limits adopted here as technologically and environmentally consistent for this new class of aircraft.</P>

        <P>The FAA has determined this rulemaking action qualifies for the categorical exclusion identified in paragraph 312f of the Order and involves no extraordinary circumstances.<PRTPAGE P="1138"/>
        </P>
        <HD SOURCE="HD1">Executive Order Determinations</HD>
        <HD SOURCE="HD2">Executive Order 13132, Federalism</HD>
        <P>The FAA has analyzed this final rule under the principles and criteria of Executive Order 13132, Federalism. The agency determined that this action will not have a substantial direct effect on the States, or the relationship between the Federal Government and the States, or on the distribution of power and responsibilities among the various levels of government, and, therefore, does not have Federalism implications.</P>
        <HD SOURCE="HD2">Executive Order 13211, Regulations That Significantly Affect Energy Supply, Distribution, or Use</HD>
        <P>The FAA analyzed this final rule under Executive Order 13211, Actions Concerning Regulations that Significantly Affect Energy Supply, Distribution, or Use (May 18, 2001). The agency has determined that it is not a “significant energy action” under Executive Order 12866 and DOT's Regulatory Policies and Procedures, and it is not likely to have a significant adverse effect on the supply, distribution, or use of energy.</P>
        <HD SOURCE="HD1">How To Obtain Additional Information</HD>
        <HD SOURCE="HD2">Rulemaking Documents</HD>
        <P>An electronic copy of a rulemaking document my be obtained by using the Internet—</P>
        <P>1. Search the Federal eRulemaking Portal (<E T="03">http://www.regulations.gov</E>);</P>
        <P>2. Visit the FAA's Regulations and Policies Web page at<E T="03">http://www.faa.gov/regulations_policies/</E>or</P>
        <P>3. Access the Government Printing Office's Web page at<E T="03">http://www.gpo.gov/fdsys/.</E>
        </P>
        <P>Copies may also be obtained by sending a request (identified by notice, amendment, or docket number of this rulemaking) to the Federal Aviation Administration, Office of Rulemaking, ARM-1, 800 Independence Avenue SW., Washington, DC 20591, or by calling (202) 267-9680.</P>
        <HD SOURCE="HD2">Comments Submitted to the Docket</HD>
        <P>Comments received may be viewed by going to<E T="03">http://www.regulations.gov</E>and following the online instructions to search the docket number for this action. Anyone is able to search the electronic form of all comments received into any of the FAA's 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.).</P>
        <HD SOURCE="HD2">Small Business Regulatory Enforcement Fairness Act</HD>

        <P>The Small Business Regulatory Enforcement Fairness Act (SBREFA) of 1996 requires FAA to comply with small entity requests for information or advice about compliance with statutes and regulations within its jurisdiction. A small entity with questions regarding this document, may contact its local FAA official, or the person listed under the<E T="02">FOR FURTHER INFORMATION CONTACT</E>heading at the beginning of the preamble. To find out more about SBREFA on the Internet, visit<E T="03">http://www.faa.gov/regulations_policies/rulemaking/sbre_act/.</E>
        </P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <CFR>14 CFR Part 21</CFR>
          <P>Aircraft, Aviation safety, Reporting and recordkeeping requirements.</P>
          <CFR>14 CFR Part 36</CFR>
          <P>Aircraft, Noise control.</P>
        </LSTSUB>
        <HD SOURCE="HD1">The Amendment</HD>
        <P>In consideration of the foregoing, the Federal Aviation Administration amends chapter I of title 14, Code of Federal Regulations, as follows:</P>
        <REGTEXT PART="21" TITLE="14">
          <PART>
            <HD SOURCE="HED">PART 21—CERTIFICATION PROCEDURES FOR PRODUCTS AND PARTS</HD>
          </PART>
          <AMDPAR>1. The authority citation for part 21 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 7572; 49 U.S.C. 106(g), 40105, 40113, 44701-44702, 44704, 44707, 44709, 44711, 44713, 44715, 45303.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="21" TITLE="14">
          <AMDPAR>2. Amend § 21.93 by adding paragraph (b)(5) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 21.93</SECTNO>
            <SUBJECT>Classification of changes in type design.</SUBJECT>
            <STARS/>
            <P>(b) * * *</P>
            <P>(5) Tiltrotors.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="36" TITLE="14">
          <PART>
            <HD SOURCE="HED">PART 36—NOISE STANDARDS: AIRCRAFT TYPE AND AIRWORTHINESS CERTIFICATION</HD>
          </PART>
          <AMDPAR>3. The authority citation for part 36 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 4321<E T="03">et seq.;</E>49 U.S.C. 106(g), 40113, 44701-44702, 44704, 44715; sec. 305, Pub. L. 96-193, 94 Stat. 50, 57; E.O. 11514, 35 FR 4247, 3 CFR, 1966-1970 Comp., p. 902.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="36" TITLE="14">
          <AMDPAR>4. Amend § 36.1 as follows:</AMDPAR>
          <AMDPAR>A. Add paragraph (a)(5);</AMDPAR>
          <AMDPAR>B. Amend paragraph (c) by removing the phrase “or 36.11” and adding the phrase “36.11 or 36.13” in its place; and</AMDPAR>
          <AMDPAR>C. Add paragraph (i)</AMDPAR>
          <P>The additions and revisions read as follows:</P>
          <SECTION>
            <SECTNO>§ 36.1</SECTNO>
            <SUBJECT>Applicability and definitions.</SUBJECT>
            <STARS/>
            <P>(a) * * *</P>
            <P>(5) Type certificates, changes to those certificates, and standard airworthiness certificates, for tiltrotors.</P>
            <STARS/>
            <P>(i) For the purpose of showing compliance with this part for tiltrotors, the following terms have the specified meanings:</P>
            <P>
              <E T="03">Airplane mode</E>means a configuration with nacelles on the down stops (axis aligned horizontally) and rotor speed set to cruise revolutions per minute (RPM).</P>
            <P>
              <E T="03">Airplane mode RPM</E>means the lower range of rotor rotational speed in RPM defined for the airplane mode cruise flight condition.</P>
            <P>
              <E T="03">Fixed operation points</E>mean designated nacelle angle positions selected for airworthiness reference. These are default positions used to refer to normal nacelle positioning operation of the aircraft. The nacelle angle is controlled by a self-centering switch. When the nacelle angle is 0 degrees (airplane mode) and the pilot moves the nacelle switch upwards, the nacelles are programmed to automatically turn to the first default position (for example, 60 degrees) where they will stop. A second upward move of the switch will tilt the nacelle to the second default position (for example, 75 degrees). Above the last default position, the nacelle angle can be set to any angle up to approximately 95 degrees by moving the switch in the up or down direction. The number and position of the fixed operation points may vary on different tiltrotor configurations.</P>
            <P>
              <E T="03">Nacelle angle</E>is defined as the angle between the rotor shaft centerline and the longitudinal axis of the aircraft fuselage.</P>
            <P>
              <E T="03">Tiltrotor</E>means a class of aircraft capable of vertical take-off and landing, within the powered-lift category, with rotors mounted at or near the wing tips that vary in pitch from near vertical to near horizontal configuration relative to the wing and fuselage.</P>
            <P>
              <E T="03">Vertical takeoff and landing (VTOL) mode</E>means the aircraft state or configuration having the rotors orientated with the axis of rotation in a vertical manner (i.e., nacelle angle of approximately 90 degrees) for vertical takeoff and landing operations.</P>
            <P>V<E T="52">CON</E>is defined as the maximum authorized speed for any nacelle angle in VTOL/Conversion mode.</P>
            <P>
              <E T="03">VTOL/Conversion mode</E>is all approved nacelle positions where the<PRTPAGE P="1139"/>design operating rotor speed is used for hover operations.</P>
            <P>
              <E T="03">VTOL mode RPM</E>means highest range of RPM that occur for takeoff, approach, hover, and conversion conditions.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="36" TITLE="14">
          <AMDPAR>5. Add § 36.13 to subpart A to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 36.13</SECTNO>
            <SUBJECT>Acoustical change: Tiltrotor aircraft.</SUBJECT>
            <P>The following requirements apply to tiltrotors in any category for which an acoustical change approval is applied for under § 21.93(b) of this chapter on or after March 11, 2013:</P>
            <P>(a) In showing compliance with Appendix K of this part, noise levels must be measured, evaluated, and calculated in accordance with the applicable procedures and conditions prescribed in Appendix K of this part.</P>
            <P>(b) Compliance with the noise limits prescribed in section K4 (Noise Limits) of Appendix K of this part must be shown in accordance with the applicable provisions of sections K2 (Noise Evaluation Measure), K3 (Noise Measurement Reference Points), K6 (Noise Certification Reference Procedures), and K7 (Test Procedures) of Appendix K of this part.</P>
            <P>(c) After a change in type design, tiltrotor noise levels may not exceed the limits specified in § 36.1103.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="36" TITLE="14">
          <AMDPAR>6. Add Subpart K of part 36 to read as follows:</AMDPAR>
          <CONTENTS>
            <SUBPART>
              <HD SOURCE="HED">Subpart K—Tiltrotors</HD>
              <SECHD>Sec.</SECHD>
              <SECTNO>36.1101</SECTNO>
              <SUBJECT>Noise measurement and evaluation.</SUBJECT>
              <SECTNO>36.1103</SECTNO>
              <SUBJECT>Noise limits.</SUBJECT>
            </SUBPART>
          </CONTENTS>
          <SUBPART>
            <HD SOURCE="HED">Subpart K—Tiltrotors</HD>
            <SECTION>
              <SECTNO>§ 36.1101</SECTNO>
              <SUBJECT>Noise measurement and evaluation.</SUBJECT>
              <P>For tiltrotors, the noise generated must be measured and evaluated under Appendix K of this part, or under an approved equivalent procedure.</P>
            </SECTION>
            <SECTION>
              <SECTNO>§ 36.1103</SECTNO>
              <SUBJECT>Noise limits.</SUBJECT>
              <P>(a) Compliance with the maximum noise levels prescribed in Appendix K of this part must be shown for a tiltrotor for which the application for the issuance of a type certificate is made on or after March 11, 2013.</P>
              <P>(b) To demonstrate compliance with this part, noise levels may not exceed the noise limits listed in Appendix K, Section K4, Noise Limits of this part. Appendix K of this part (or an approved equivalent procedure) must also be used to evaluate and demonstrate compliance with the approved test procedures, and at the applicable noise measurement points.</P>
            </SECTION>
          </SUBPART>
        </REGTEXT>
        <REGTEXT PART="36" TITLE="14">
          <AMDPAR>7. Add Appendix K to part 36 to read as follows:</AMDPAR>
          <CONTENTS>
            <SUBPART>
              <HD SOURCE="HED">Appendix K to Part 36—Noise Requirements for Tiltrotors Under Subpart K</HD>
              <SECHD>Sec.</SECHD>
              <SECTNO>K1</SECTNO>
              <SUBJECT>General</SUBJECT>
              <SECTNO>K2</SECTNO>
              <SUBJECT>Noise Evaluation Measure</SUBJECT>
              <SECTNO>K3</SECTNO>
              <SUBJECT>Noise Measurement Reference Points</SUBJECT>
              <SECTNO>K4</SECTNO>
              <SUBJECT>Noise Limits</SUBJECT>
              <SECTNO>K5</SECTNO>
              <SUBJECT>Trade-offs</SUBJECT>
              <SECTNO>K6</SECTNO>
              <SUBJECT>Noise Certification Reference Procedures</SUBJECT>
              <SECTNO>K7</SECTNO>
              <SUBJECT>Test Procedures</SUBJECT>
            </SUBPART>
          </CONTENTS>
          <HD SOURCE="HD2">Section K1General</HD>
          <P>This appendix prescribes noise limits and procedures for measuring noise and adjusting the data to standard conditions for tiltrotors as specified in § 36.1 of this part.</P>
          <HD SOURCE="HD2">Section K2Noise Evaluation Measure</HD>
          <P>The noise evaluation measure is the effective perceived noise level in EPNdB, to be calculated in accordance with section A36.4 of Appendix A to this part, except corrections for spectral irregularities must be determined using the 50 Hz sound pressure level found in section H36.201 of Appendix H to this part.</P>
          <HD SOURCE="HD2">Section K3Noise Measurement Reference Points</HD>
          <P>The following noise reference points must be used when demonstrating tiltrotor compliance with section K6 (Noise Certification Reference Procedures) and section K7 (Test Procedures) of this appendix:</P>
          <P>(a)<E T="03">Takeoff reference noise measurement points—</E>
          </P>
          <P>As shown in Figure K1 below:</P>
          <P>(1) The centerline noise measurement flight path reference point, designated A, is located on the ground vertically below the reference takeoff flight path. The measurement point is located 1,640 feet (500 m) in the horizontal direction of flight from the point Cr where transition to climbing flight is initiated, as described in section K6.2 of this appendix;</P>
          <P>(2) Two sideline noise measurement points, designated as S(starboard) and S(port), are located on the ground perpendicular to and symmetrically stationed at 492 feet (150 m) on each side of the takeoff reference flight path. The measurement points bisect the centerline flight path reference point A.</P>
          <BILCOD>BILLING CODE 4910-13-P</BILCOD>
          <GPH DEEP="325" SPAN="3">
            <PRTPAGE P="1140"/>
            <GID>ER08JA13.007</GID>
          </GPH>
          <P>(b)<E T="03">Flyover reference noise measurement points</E>—</P>
          <P>As shown in Figure K2 below:</P>
          <P>(1) The centerline noise measurement flight path reference point, designated A, is located on the ground 492 feet (150 m) vertically below the reference flyover flight path. The measurement point is defined by the flyover reference procedure in section K6.3 of this appendix;</P>
          <GPH DEEP="272" SPAN="3">
            <GID>ER08JA13.008</GID>
          </GPH>
          <PRTPAGE P="1141"/>

          <P>(2) Two sideline noise measurement points, designated as S<E T="52">(sideline)</E>, are located on the ground perpendicular to and symmetrically stationed at 492 feet (150 m) on each side of the flyover reference flight path. The measurement points bisect the centerline flight path reference point A.</P>
          <P>(c)<E T="03">Approach reference noise measurement points</E>—</P>
          <P>As shown in Figure K3 below:</P>
          <P>(1) The centerline noise measurement flight path reference point, designated A, is located on the ground 394 feet (120 m) vertically below the reference approach flight path. The measurement point is defined by the approach reference procedure in section K6.4 of this appendix. On level ground, the measurement point corresponds to a position 3,740 feet (1,140 m) from the intersection of the 6.0 degree approach path with the ground plane;</P>
          <P>(2) Two sideline noise measurement points, designated as S(starboard) and S(port), are located on the ground perpendicular to and symmetrically stationed at 492 feet (150 m) on each side of the approach reference flight path. The measurement points bisect the centerline flight path reference point A.</P>
          <GPH DEEP="294" SPAN="3">
            <GID>ER08JA13.009</GID>
          </GPH>
          <HD SOURCE="HD2">Section K4Noise Limits</HD>
          <P>For a tiltrotor, the maximum noise levels, as determined in accordance with the noise evaluation in EPNdB and calculation method described in section H36.201 of Appendix H of this part, must not exceed the noise limits as follows:</P>
          <P>(a)<E T="03">At the takeoff flight path reference point:</E>For a tiltrotor having a maximum certificated takeoff weight (mass) of 176,370 pounds (80,000 kg) or more, in VTOL/Conversion mode, 109 EPNdB, decreasing linearly with the logarithm of the tiltrotor weight (mass) at a rate of 3.0 EPNdB per halving of weight (mass) down to 89 EPNdB, after which the limit is constant. Figure K4 illustrates the takeoff noise limit as a solid line.</P>
          <P>(b)<E T="03">At the Flyover path reference point:</E>For a tiltrotor having a maximum certificated takeoff weight (mass) of 176,370 pounds (80,000 kg) or more, in VTOL/Conversion mode, 108 EPNdB, decreasing linearly with the logarithm of the tiltrotor weight (mass) at a rate of 3.0 EPNdB per halving of weight (mass) down to 88 EPNdB, after which the limit is constant. Figure K4 illustrates the flyover noise limit as a dashed line.</P>
          <P>(c)<E T="03">At the approach flight path reference point:</E>For a tiltrotor having a maximum certificated takeoff weight (mass) of 176,370 pounds (80,000 kg) or more, in VTOL/Conversion mode, 110 EPNdB, decreasing linearly with the logarithm of the tiltrotors weight (mass) at a rate of 3.0 EPNdB per halving of weight (mass) down to 90 EPNdB, after which the limit is constant. Figure K4 illustrates the approach noise limit as a dash-dot line.</P>
          <GPH DEEP="432" SPAN="3">
            <PRTPAGE P="1142"/>
            <GID>ER08JA13.010</GID>
          </GPH>
          <BILCOD>BILLING CODE 4910-13-C</BILCOD>
          <HD SOURCE="HD2">Section K5Trade-Offs</HD>
          <P>If the noise evaluation measurement exceeds the noise limits described in K4 of this appendix at one or two measurement points:</P>
          <P>(a) The sum of excesses must not be greater than 4 EPNdB;</P>
          <P>(b) The excess at any single point must not be greater than 3 EPNdB; and</P>
          <P>(c) Any excess must be offset by the remaining noise margin at the other point or points.</P>
          <HD SOURCE="HD2">Section K6Noise Certification Reference Procedures</HD>
          <P>
            <E T="03">K6.1General Conditions</E>
          </P>
          <P>(a) [Reserved]</P>
          <P>(b) [Reserved]</P>
          <P>(c) The takeoff, flyover and approach reference procedures must be established in accordance with sections K6.2, K6.3 and K6.4 of this appendix, except as specified in section K6.1(d) of this appendix.</P>
          <P>(d) If the design characteristics of the tiltrotor prevent test flights from being conducted in accordance with section K6.2, K6.3 or K6.4 of this appendix, the applicant must revise the test procedures and resubmit the procedures for approval.</P>
          <P>(e) The following reference atmospheric conditions must be used to establish the reference procedures:</P>
          <P>(1) Sea level atmospheric pressure of 2,116 pounds per square foot (1,013.25 hPa);</P>
          <P>(2) Ambient air temperature of 77 °Fahrenheit (25 ° Celsius, i.e. ISA + 10 °C);</P>
          <P>(3) Relative humidity of 70 percent; and</P>
          <P>(4) Zero wind.</P>
          <P>(f) For tests conducted in accordance with sections K6.2, K6.3, and K6.4 of this appendix, use the maximum normal operating RPM corresponding to the airworthiness limit imposed by the manufacturer. For configurations for which the rotor speed automatically links with the flight condition, use the maximum normal operating rotor speed corresponding with the reference flight condition. For configurations for which the rotor speed can change by pilot action, use the highest normal rotor speed specified in the flight manual limitation section for the reference conditions.</P>
          <P>
            <E T="03">K6.2Takeoff Reference Procedure.</E>The takeoff reference flight procedure is as follows:</P>
          <P>(a) A constant takeoff configuration must be maintained, including the nacelle angle selected by the applicant;</P>

          <P>(b) The tiltrotor power must be stabilized at the maximum takeoff power corresponding to the minimum<PRTPAGE P="1143"/>installed engine(s) specification power available for the reference ambient conditions or gearbox torque limit, whichever is lower. The tiltrotor power must also be stabilized along a path starting from a point located 1,640 feet (500 m) before the flight path reference point, at 65 ft (20 m) above ground level;</P>
          <P>(c) The nacelle angle and the corresponding best rate of climb speed, or the lowest approved speed for the climb after takeoff, whichever is the greater, must be maintained throughout the takeoff reference procedure;</P>
          <P>(d) The rotor speed must be stabilized at the maximum normal operating RPM certificated for takeoff;</P>
          <P>(e) The weight (mass) of the tiltrotors must be the maximum takeoff weight (mass) as requested for noise certification; and</P>
          <P>(f) The reference takeoff flight profile is a straight line segment inclined from the starting point 1,640 feet (500 m) before to the center noise measurement point and 65 ft (20 m) above ground level at an angle defined by best rate of climb and the speed corresponding to the selected nacelle angle and for minimum specification engine performance.</P>
          <P>
            <E T="03">K6.3Flyover Reference Procedure.</E>The flyover reference flight procedure is as follows:</P>
          <P>(a) The tiltrotor must be stabilized for level flight along the centerline flyover flight path and over the noise measurement reference point at an altitude of 492 ft (150 m) above ground level;</P>
          <P>(b) A constant flyover configuration selected by the applicant must be maintained;</P>
          <P>(c) The weight (mass) of the tiltrotor must be the maximum takeoff weight (mass) as requested for noise certification;</P>
          <P>(d) In the VTOL/Conversion mode:</P>
          <P>(1) The nacelle angle must be at the authorized fixed operation point that is closest to the shallow nacelle angle certificated for zero airspeed;</P>
          <P>(2) The airspeed must be 0.9V<E T="52">CON</E>and</P>
          <P>(3) The rotor speed must be stabilized at the maximum normal operating RPM certificated for level flight.</P>
          <P>
            <E T="03">K6.4Approach Reference Procedure.</E>The approach reference procedure is as follows:</P>
          <P>(a) The tiltrotor must be stabilized to follow a 6.0 degree approach path;</P>
          <P>(b) An approved airworthiness configuration in which maximum noise occurs must be maintained;</P>
          <P>(1) An airspeed equal to the best rate of climb speed corresponding to the nacelle angle, or the lowest approved airspeed for the approach, whichever is greater, must be stabilized and maintained; and</P>
          <P>(2) The tiltrotor power during the approach must be stabilized over the flight path reference point, and continue as if landing;</P>
          <P>(c) The rotor speed must be stabilized at the maximum normal operating RPM certificated for approach;</P>
          <P>(d) The constant approach configuration used in airworthiness certification tests, with the landing gear extended, must be maintained; and</P>
          <P>(e) The weight (mass) of the tiltrotor at landing must be the maximum landing weight (mass) as requested for noise certification.</P>
          <HD SOURCE="HD2">Section K7Test Procedures</HD>
          <P>
            <E T="03">K7.1</E>[Reserved]</P>
          <P>
            <E T="03">K7.2</E>The test procedures and noise measurements must be conducted and processed to yield the noise evaluation measure designated in section K2 of this appendix.</P>
          <P>
            <E T="03">K7.3</E>If either the test conditions or test procedures do not comply to the applicable noise certification reference conditions or procedures prescribed by this part, the applicant must apply the correction methods described in section H36.205 of Appendix H of this part to the acoustic test data measured.</P>
          <P>
            <E T="03">K7.4</E>Adjustments for differences between test and reference flight procedures must not exceed:</P>
          <P>(a) For takeoff: 4.0 EPNdB, of which the arithmetic sum of delta 1 and the term −7.5 log (QK/QrKr) from delta 2 must not in total exceed 2.0 EPNdB;</P>
          <P>(b) For flyover or approach: 2.0 EPNdB.</P>
          <P>
            <E T="03">K7.5</E>The average rotor RPM must not vary from the normal maximum operating RPM by more than ±1.0 percent throughout the 10 dB-down time interval.</P>
          <P>
            <E T="03">K7.6</E>The tiltrotor airspeed must not vary from the reference airspeed appropriate to the flight demonstration by more than ±5 kts (±9 km/h) throughout the 10 dB-down time interval.</P>
          <P>
            <E T="03">K7.7</E>The number of level flyovers made with a head wind component must be equal to the number of level flyovers made with a tail wind component.</P>
          <P>
            <E T="03">K7.8</E>The tiltrotor must operate between ±10 degrees from the vertical or between ±65 feet (±20 m) lateral deviation tolerance, whichever is greater, above the reference track and throughout the 10 dB-down time interval.</P>
          <P>
            <E T="03">K7.9</E>The tiltrotor altitude must not vary during each flyover by more than ±30 ft (±9 m) from the reference altitude throughout the 10 dB-down time interval.</P>
          <P>
            <E T="03">K7.10</E>During the approach procedure, the tiltrotor must establish a stabilized constant speed approach and fly between approach angles of 5.5 degrees and 6.5 degrees throughout the 10 dB-down time interval.</P>
          <P>
            <E T="03">K7.11</E>During all test procedures, the tiltrotor weight (mass) must not be less than 90 percent and not more than 105 percent of the maximum certificated weight (mass). For each of the test procedures, complete at least one test at or above this maximum certificated weight (mass).</P>
          <P>
            <E T="03">K7.12</E>A tiltrotor capable of carrying external loads or external equipment must be noise certificated without such loads or equipment fitted</P>
          <P>
            <E T="03">K7.13</E>The value of V<E T="52">CON</E>used for noise certification must be included in the approved Flight Manual.</P>
        </REGTEXT>
        <SIG>
          <DATED>Issued in Washington, DC, on December 21, 2012.</DATED>
          <NAME>Michael P. Huerta,</NAME>
          <TITLE>Acting Administrator.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00111 Filed 1-7-13; 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 420</CFR>
        <DEPDOC>[Docket No. FAA-2011-0105; Amdt. No. 420-6A]</DEPDOC>
        <RIN>RIN 2120-AJ73</RIN>
        <SUBJECT>Explosive Siting Requirements; Correction</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Aviation Administration (FAA), DOT.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule; correction.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The FAA is correcting a final rule published on September 7, 2012<E T="03"/>(77 FR 55108). In that rule, the FAA amended its regulations to the requirements for siting explosives under a license to operate a launch site. The rule increases flexibility for launch site operators in site planning for the storage and handling of energetic liquids and explosives. The FAA inadvertently did not correctly identify the Department of Defense Explosives Safety Board.<E T="03"/>This document corrects the error.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Effective January 8, 2013.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>For technical questions concerning this final rule, contact Yvonne Tran, Commercial Space Transportation, Federal Aviation Administration, 800 Independence Avenue SW., Washington, DC 20591; telephone (202) 267-7908; facsimile (202) 267-5463, email<E T="03">yvonne.tran@faa.gov.</E>For legal questions concerning this final rule, contact Laura Montgomery, AGC 200,<PRTPAGE P="1144"/>Senior Attorney for Commercial Space Transportation, Office of the Chief Counsel, Federal Aviation Administration, 800 Independence Avenue SW., Washington, DC 20591; telephone (202) 267-3150; facsimile (202) 267-7971, email<E T="03">laura.montgomery@faa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Background</HD>
        <P>On September 7, 2012, the FAA published a final rule entitled, “Explosive Siting Requirements” (77 FR 55108).</P>
        <P>In that final rule, the FAA revised the requirements for siting explosives under a license to operate a launch site. The rule increased flexibility for launch site operators in site planning for the storage and handling of energetic liquids and explosives. In the discussion of the Overview of the Final Rule, the FAA explained that it was dispensing with the hazard groups of tables E-3 through E-6 of appendix E of Title 14, Code of Federal Regulations part 420 as a means of classification to be consistent with the Department of Defense (DOD) Explosives Safety Board (DDESB) and National Fire Protection Association (NFPA) practices. In the full title of DDESB, the FAA inadvertently used the word “siting” instead of “safety.” The FAA is now correcting the error to properly identify DDESB.</P>
        <HD SOURCE="HD2">Correction to Preamble</HD>
        <P>1. On page 55109, in the first column, in the first paragraph under Section I., correct “Department of Defense (DOD) Explosives Siting Board's (DDESB)” to read “Department of Defense (DOD) Explosives Safety Board (DDESB)”.</P>
        <SIG>
          <DATED>Issued in Washington, DC on January 2, 2013.</DATED>
          <NAME>Lirio Liu,</NAME>
          <TITLE>Director, Office of Rulemaking.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00109 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-13-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">COMMODITY FUTURES TRADING COMMISSION</AGENCY>
        <CFR>17 CFR Parts 9, 12, and 171</CFR>
        <SUBJECT>Rules of Practice; Amendments to Delegations of Authority to the Office of General Counsel</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Commodity Futures Trading Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Commodity Futures Trading Commission (“CFTC” or “Commission”) is amending its regulations delegating authority to the Commission's Office of General Counsel, so that all delegations thereto will be to the General Counsel, with authority to sub-delegate to any Commission employee under the supervision of the General Counsel.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>January 8, 2013.</P>
        </EFFDATE>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Lynn Bulan, Counsel, Office of General Counsel, 1155 21st Street NW., Washington, DC 20581,<E T="03">lbulan@cftc.gov</E>and (202) 418-5120.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The Commission is revising delegations of authority to the Office of General Counsel, replacing delegations to the Deputy General Counsel for Opinions and Review with delegations to the General Counsel. The reason for this change is due to the elimination of the position of Deputy General Counsel for Opinions and Review under a reorganization within the Office of General Counsel. The revisions will permit the General Counsel to sub-delegate authority to any Commission employee under his or her supervision.</P>
        <HD SOURCE="HD1">I. Rules Being Amended</HD>
        <P>The following CFTC rules are being amended.</P>
        <HD SOURCE="HD2">A. 17 CFR 9.9</HD>
        <P>CFTC rule 9.9 delegates certain authority to the Deputy General Counsel for Opinions and Review. Currently, the rule authorizes the Deputy General Counsel for Opinions and Review or his/her designee to handle certain procedural and technical matters and, in his/her discretion, to submit matters otherwise falling within this rule to the Commission for its consideration. The CFTC is changing the rule to grant this authority to the General Counsel. As a result, references to the Deputy General Counsel for Opinions and Review in rule 9.9 have been changed to the General Counsel, and to any employee under the General Counsel's supervision as he or she may designate.</P>
        <HD SOURCE="HD2">B. 17 CFR 12.10</HD>
        <P>CFTC rule 12.10(a)(3) sets forth all the persons upon whom the Proceedings Clerk must serve all notices, rulings, opinions, and orders. This list of persons includes the Deputy General Counsel for Opinions and Review. The rule is being revised such that all references to the Deputy General Counsel for Opinions and Review in rule 12.10 have been changed to the General Counsel, and permits the General Counsel to sub-delegate this authority to any Commission employee under his or her supervision.</P>
        <HD SOURCE="HD2">C. 17 CFR 12.408</HD>
        <P>CFTC rule 12.408 is titled “Delegation of Authority to the Deputy General Counsel for Opinions.” The text of the rule delegates certain functions to the General Counsel and not the Deputy General Counsel for Opinions. In order to conform the title of the section to the substance of the section, the reference in the title of the section has been changed to “Delegation of Authority to the General Counsel.”</P>
        <HD SOURCE="HD2">D. 17 CFR 171.1(c)</HD>
        <P>CFTC rule 171.1(c) provides the Deputy General Counsel for Opinions the authority to strike a notice of appeal in certain circumstances. All references to the Deputy General Counsel for Opinions in rule 171.1(c) have been changed to the General Counsel, or the General Counsel's delegate.</P>
        <HD SOURCE="HD2">E. 17 CFR 171.50</HD>
        <P>CFTC rule 171.50 delegates certain authority to the Deputy General Counsel for Opinions. The current rule authorizes the Deputy General Counsel for Opinions and Review or his/her designee to handle certain procedural and technical matters and, in his/her discretion, to submit matters otherwise falling within this rule to the Commission for its consideration. References in rule 171.50 have been changed to the General Counsel.</P>
        <HD SOURCE="HD1">II. Administrative Compliance</HD>
        <HD SOURCE="HD2">A. Administrative Procedure Act</HD>
        <P>The Administrative Procedure Act does not require notice of the proposed rulemaking and an opportunity for public participation in connection with these amendments, as they relate solely to agency organization, procedure and practice.<SU>1</SU>

          <FTREF/>For the same reason, these rules will become effective upon publication in the<E T="04">Federal Register</E>.<SU>2</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>1</SU>5 U.S.C. 553(b).</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>2</SU>5 U.S.C. 553(d).</P>
        </FTNT>
        <P>Pursuant to the authority contained in the Commodity Exchange Act, in particular section 2(a)(4), 7 U.S.C. 2(a)(4), the CFTC corrects part 9, 12 and 171 of Title 17 of the Code of Federal regulations as described below.</P>
        <HD SOURCE="HD2">B. Paperwork Reduction Act and Regulatory Flexibility Act</HD>
        <P>This rulemaking does not contain any collections of information for which the Commission must seek a control number under the Paperwork Reduction Act.<SU>3</SU>

          <FTREF/>Moreover, the Regulatory Flexibility Act requires the Commission to consider whether a rulemaking will<PRTPAGE P="1145"/>have a significant economic impact on a substantial number of small businesses only when the agency is obligated to publish a general notice of proposed rulemaking under section 553(b). As this rulemaking relates to agency organization and procedure, and therefore is not subject to notice and comment under section 553(b), a regulatory flexibility analysis is not required.<SU>4</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>3</SU>
            <E T="03">See</E>44 U.S.C. 3501<E T="03">et seq.</E>
          </P>
        </FTNT>
        <FTNT>
          <P>
            <SU>4</SU>
            <E T="03">See</E>5 U.S.C. 601(2).</P>
        </FTNT>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 17 CFR Parts 9, 12 and 171</HD>
          <P>Administrative practice and procedure, Commodity exchanges, Commodity futures, Rules of practice before administrative agency.</P>
        </LSTSUB>
        
        <P>For the reasons stated in the preamble, the Commodity Futures Trading Commission amends 17 CFR Parts 9, 12 and 171 as set forth below:</P>
        <REGTEXT PART="9" TITLE="17">
          <PART>
            <HD SOURCE="HED">PART 9—RULES RELATING TO REVIEW OF EXCHANGE DISCIPLINARY, ACCESS DENIAL OR OTHER ADVERSE ACTIONS</HD>
          </PART>
          <AMDPAR>1. The authority citation for Part 9 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>7 U.S.C. 4a, 6c, 7a, 12a, 12c, 16a, as amended by Title XIII of the Food, Conservation and Energy Act of 2008, Pub. L. 110-246, 122 Stat. 1624 (June 18, 2008), unless otherwise noted.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="9" TITLE="17">
          <AMDPAR>2. Section 9.9 is amended by revising paragraphs (b)(1) introductory text, (b)(3) and (b)(4), to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 9.9</SECTNO>
            <SUBJECT>Waiver of rules; delegation of authority.</SUBJECT>
            <STARS/>
            <P>(b) * * *</P>
            <P>(1) The Commission hereby delegates, until the Commission orders otherwise, to the General Counsel, or to any employee under the General Counsel's supervision as the General Counsel may designate, the authority:</P>
            <STARS/>
            <P>(3) The General Counsel, or his designee, may submit to the Commission for its consideration any matter which has been delegated pursuant to paragraph (b)(1) of this section.</P>
            <P>(4) Nothing in this section will be deemed to prohibit the Commission, at its election, from exercising the authority delegated to the General Counsel, or his designee, under this section.</P>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="12" TITLE="17">
          <PART>
            <HD SOURCE="HED">PART 12—RULES RELATING TO REPARATION PROCEEDINGS</HD>
          </PART>
          <AMDPAR>3. The authority citation for Part 12 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>7 U.S.C. 2(a)(12), 12a(5), and 18, as amended by Title XIII of the Food, Conservation and Energy Act of 2008, Pub. L. 110-246, 122 Stat. 1624 (June 18, 2008), unless otherwise noted.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="12" TITLE="17">
          <AMDPAR>4. Section 12.10 is amended by revising paragraph (a)(3) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 12.10</SECTNO>
            <SUBJECT>Service.</SUBJECT>
            <STARS/>
            <P>(a) * * *</P>
            <P>(3)<E T="03">Service of orders and decisions.</E>A copy of all notices, rulings, opinions and orders of the Proceedings Clerk, the Director of the Office of Proceedings, a Judgment Officer, Administrative Law Judge, the General Counsel or any employee under the General Counsel's supervision as the General Counsel may designate, or the Commission shall be served by the Proceedings Clerk on each of the parties.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="12" TITLE="17">
          <AMDPAR>5. Section 12.408 is amended by revising the section heading to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 12.408</SECTNO>
            <SUBJECT>Delegation of authority to the General Counsel.</SUBJECT>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="171" TITLE="17">
          <PART>
            <HD SOURCE="HED">PART 171—RULES RELATING TO REVIEW OF NATIONAL FUTURES ASSOCIATION DECISIONS IN DISCIPLINARY, MEMBERSHIP DENIAL, REGISTRATION AND MEMBERSHIP RESPONSIBILITY ACTIONS</HD>
            <HD SOURCE="HD1">Authority and Issuance</HD>
          </PART>
          <AMDPAR>6. The authority citation for Part 171 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>7 U.S.C. 4a, 12a, and 21, as amended by Title XIII of the Food, Conservation and Energy Act of 2008, Pub. L. 110-246, 122 Stat. 1624 (June 18, 2008), unless otherwise noted.</P>
          </AUTH>
        </REGTEXT>
        
        <REGTEXT PART="171" TITLE="17">
          <AMDPAR>7. Section 171.1 is amended by revising paragraph (c) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 171.1</SECTNO>
            <SUBJECT>Scope of rules.</SUBJECT>
            <STARS/>
            <P>(c)<E T="03">Appeals from excluded decisions.</E>If the General Counsel, or any employee under the General Counsel's supervision as the General Counsel may designate, determines that a notice of appeal submitted to the Commission is from a decision that is excluded from review under this part, the notice of appeal may be stricken and ordered to be returned to the aggrieved party who submitted it.</P>
            <STARS/>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="171" TITLE="17">
          <AMDPAR>8. Section 171.50 is amended by revising paragraphs (a) introductory text, (c), and (d) to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 171.50</SECTNO>
            <SUBJECT>Delegation to the General Counsel.</SUBJECT>
            <P>(a) The Commission hereby delegates, until it orders otherwise, to the General Counsel, or any employee under the General Counsel's supervision as the General Counsel may designate, the authority:</P>
            <STARS/>
            <P>(c) The General Counsel, or his designee, may submit to the Commission for its consideration any matter which has been delegated pursuant to paragraph (a) of this section.</P>
            <P>(d) Nothing in this section will be deemed to prohibit the Commission, at its election, from exercising the authority delegated to the General Counsel, or his designee, under this section.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Issued in Washington, DC on December 31, 2012, by the Commission.</DATED>
          <NAME>Sauntia S. Warfield,</NAME>
          <TITLE>Assistant Secretary of the Commission.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31721 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6351-01-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Coast Guard</SUBAGY>
        <CFR>33 CFR Part 165</CFR>
        <DEPDOC>[Docket Number USCG-2012-0824]</DEPDOC>
        <RIN>RIN 1625-AA11</RIN>
        <SUBJECT>Regulated Navigation Area; Housatonic River, Bridge Replacement Operations; Stratford, CT</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Coast Guard, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Temporary interim rule and request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Coast Guard is establishing a regulated navigation area (RNA) on the navigable waters of the Housatonic River surrounding the Interstate 95 (I-95) Bridge, between Stratford and Milford, CT. This RNA allows the Coast Guard to enforce speed and wake restrictions and prohibit all vessel traffic through the RNA during bridge replacement operations, both planned and unforeseen, that could pose an imminent hazard to persons and vessels operating in the area. This rule is necessary to provide for the safety of life on the navigable waters during the replacement of the bridge.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>This rule is effective and will be enforced from January, 7, 2013 through November 30, 2017.</P>

          <P>Comments and related material may be received by the Coast Guard through the effective period.<PRTPAGE P="1146"/>
          </P>
          <P>Requests for public meetings must be received by the Coast Guard on or before January 29, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Documents mentioned in this preamble are part of Docket Number USCG-2012-0824. To view documents mentioned in this preamble as being available in the docket, go to<E T="03">http://www.regulations.gov,</E>type the docket number in the “SEARCH” box and click “SEARCH.” Click on “Open Docket Folder” on the line associated with this rulemaking. You may also visit the Docket Management Facility in Room W12-140 on the ground floor of the Department of Transportation West Building, 1200 New Jersey Avenue SE., Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.</P>
          <P>You may submit comments, identified by docket number, using any one of the following methods:</P>
          <P>(1)<E T="03">Federal eRulemaking Portal:</E>
            <E T="03">http://www.regulations.gov.</E>
          </P>
          <P>(2)<E T="03">Fax:</E>(202) 493-2251.</P>
          <P>(3)<E T="03">Mail or Delivery:</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. Deliveries accepted between 9 a.m. and 5 p.m., Monday through Friday, except federal holidays. The telephone number is 202-366-9329.</P>

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

          <P>If you have questions on this rule, call or email Petty Officer Joseph Graun, Prevention Department, U.S. Coast Guard Sector Long Island Sound, (203) 468-4544,<E T="03">Joseph.L.Graun@uscg.mil;</E>or Lieutenant Isaac M. Slavitt, Waterways Management Division, U.S. Coast Guard First District, (617) 223-8385. If you have questions on viewing or submitting material to the docket, call Renee V. Wright, Program Manager, Docket Operations, telephone (202) 366-9826.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Table of Acronyms</HD>
        <EXTRACT>
          <P>COTPCaptain of the Port</P>
          <P>DHSDepartment of Homeland Security</P>
          <P>FR<E T="04">Federal Register</E>
          </P>
          <P>I-95Interstate 95</P>
          <P>LISLong Island Sound</P>
          <P>NPRMNotice of Proposed Rulemaking</P>
          <P>RNARegulated navigation area</P>
          <P>RRRailroad</P>
        </EXTRACT>
        <HD SOURCE="HD1">A. 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="HD2">1. Submitting Comments</HD>

        <P>If you submit a comment, please include the docket number for this rulemaking, 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 at<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, 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 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 self-addressed, stamped, 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="HD2">2. 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 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="HD2">3. Privacy Act</HD>

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

        <P>We currently do not plan to hold a public meeting. You may, however, submit a request for one, using one of the 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 in this rulemaking, we will hold one at a time and place announced by a later notice in the<E T="04">Federal Register</E>.</P>
        <HD SOURCE="HD1">B. Regulatory History and Information</HD>
        <P>Under 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a notice of proposed rulemaking (NPRM) with respect to this rule.</P>
        <P>A full waterway closure was not requested of the Coast Guard until November 21, 2012 when the Connecticut Department of Transportation (CT DOT) requested a complete waterway closure beginning January 7, 2013. This late submission did not give the Coast Guard enough time to publish an NPRM, take public comments, and issue a final rule before work begins in January.</P>
        <P>It would be impracticable and contrary to the public interest to delay promulgating this rule, as it is necessary to protect the safety of both the construction crew and the waterway users operating in the vicinity of the bridge construction zone. A delay or cancellation of the currently ongoing bridge rehabilitation project in order to accommodate a full notice and comment period would delay necessary operations, result in increased costs, and delay the date when the bridge is expected to reopen for normal operations. The Coast Guard believes it would be impracticable and contrary to the public interest to delay this regulation. At any time, the Coast Guard may publish an amended rule if necessary to address public concerns.</P>

        <P>For the same reasons, under 5 U.S.C. 553(d)(3), the Coast Guard finds that<PRTPAGE P="1147"/>good cause exists for making this rule effective less than 30 days after publication in the<E T="04">Federal Register</E>.</P>
        <HD SOURCE="HD1">C. Basis and Purpose</HD>
        <P>Under the Ports and Waterways Safety Act, 33 U.S.C. 1221-1236, and Department of Homeland Security Delegation No. 0170.1, the Coast Guard has the authority to establish RNAs in defined water areas that are determined to have hazardous conditions and in which vessel traffic can be regulated in the interest of safety.</P>
        <P>The purpose of this rulemaking is to provide for safety on the navigable waters in the regulated area during bridge reconstruction.</P>
        <HD SOURCE="HD1">D. Discussion of the Interim Rule</HD>
        <P>The Coast Guard is establishing an RNA on the navigable waters of the Housatonic River surrounding the Moses Wheeler Bridge which spans from Stratford to Milford, CT. This RNA allows the Captain of the Port Sector Long Island Sound (COTP) to establish speed and wake restrictions and to prohibit vessel traffic on this portion of the river for limited periods when necessary for the safety of vessels and workers during construction work in the channel. The Coast Guard will enforce a six knot speed limit as well as a “NO WAKE” zone and be able to close the designated area to all vessel traffic during any circumstance, planned or unforeseen, that poses an imminent threat to waterway users or construction operations in the area. Complete waterway closures will be minimized to that period absolutely necessary and made with as much advanced notice as possible. During closures, mariners may request permission from the COTP to transit through the RNA.</P>
        <P>This rule was prompted by the navigation safety situation created by reconstruction of the Moses Wheeler Bridge (sometimes referred to as the Interstate-95 (I-95) Bridge or the Housatonic River Bridge). This bridge carries I-95 (Connecticut Turnpike) over the Housatonic River between Stratford and Milford CT. The present bridge was built in the 1950s and designed with a 50 year life span. The bridge has surpassed its useable life span and the Connecticut Department of Transportation (CT DOT) has contracted to construct a replacement bridge. The contractor has begun bridge construction and is scheduled to complete the project in 2017.</P>
        <P>The Coast Guard has discussed this project with CT DOT to determine whether the project can be completed without channel closures and, if possible, what impact that would have on the project timeline. Through these discussions, it became clear that while the majority of construction activities during the span of this project would not require waterway closures, there are certain tasks that can only be completed in the channel and will require closing the waterway. Specifically, this includes the demolition of steel support beams. These large and extremely heavy steel support beams are suspended 55 feet above the water; to demolish them, they must be cut into sections and lowered on to a barge. This process will be extremely complex and presents many safety hazards including overhead crane operations, overhead cutting operations, potential falling debris, and barges positioned in the channel with a restricted ability to maneuver.</P>
        <P>In a letter to the U.S. Coast Guard dated November 21, 2012, CT DOT outlined two phases of operations that require in-channel work, two steps of which will require waterway closures. CT DOT will notify the Coast Guard as far in advance as possible if additional closures are needed. The Coast Guard has a copy of this letter in the docket.</P>
        <P>The first planned closure period will be three days during January of 2013. The purpose of this closure is to remove the steel support beams of the existing Moses Wheeler Bridge northbound span. Currently, the Coast Guard anticipates the three days will be weekdays and the closure will be in effect from 7 a.m. through 7 p.m.</P>
        <P>The second planned closure period is anticipated to be three days during January of 2014. The purpose of this closure is to remove the steel support beams of the existing Moses Wheeler Bridge southbound span. The three days will be weekdays and the closure will be in effect from 7 a.m. through 7 p.m.</P>
        <P>Entry into, anchoring, or movement within this RNA during a closure is prohibited unless authorized by the COTP or a designated representative.</P>
        <P>If the project is completed before November 30, 2017, the COTP will suspend enforcement of the RNA. The COTP will ensure that any notice of the suspension of enforcement reaches affected segments of the public by all appropriate means. Such means of notification could include, but would not be limited to, Broadcast Notice to Mariners and Local Notice to Mariners.</P>
        <HD SOURCE="HD1">E. Regulatory Analyses</HD>
        <P>We developed this rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on these statutes and executive orders.</P>
        <HD SOURCE="HD2">1. Regulatory Planning and Review</HD>
        <P>This rule is not a significant regulatory action under section 3(f) of Executive Order 12866, Regulatory Planning and Review, as supplemented by Executive Order 13563, Improving Regulation and Regulatory Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of Executive Order 12866 or under section 1 of Executive Order 13563. The Office of Management and Budget has not reviewed it under those Orders.</P>
        <P>The Coast Guard determined that this rulemaking will not be a significant regulatory action for the following reasons: Vessel traffic will only be restricted from the RNA for limited durations and the RNA covers only a small portion of the navigable waterways and all closures currently planned are scheduled during winter months when vessel traffic is low. Advanced public notifications will also be made to local mariners through appropriate means, which could include, but would not be limited to, Local Notice to Mariners and Broadcast Notice to Mariners.</P>
        <HD SOURCE="HD2">2. Impact on Small Entities</HD>
        <P>The Regulatory Flexibility Act of 1980 (RFA), 5 U.S.C. 601-612, as amended, requires federal agencies to consider the potential impact of regulations on small entities during rulemaking. The 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 enter or transit within the RNA during a vessel restriction period.</P>
        <P>The RNA would not have a significant economic impact on a substantial number of small entities for the following reasons: The RNA would be of limited size and any waterway closure of short duration. Additionally, all closures currently planned are scheduled during winter months when vessel traffic is low, before the effective period of a waterway closure, advanced public notifications will be made to local mariners through appropriate means, which could include, but would not be limited to, Local Notice to Mariners and Broadcast Notice to Mariners.</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<PRTPAGE P="1148"/>
          <E T="02">ADDRESSES</E>) explaining why you think it qualifies and how and to what degree this rule would economically affect it.</P>
        <HD SOURCE="HD2">3. Assistance for Small Entities</HD>

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

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

        <P>We have analyzed this rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA)(42 U.S.C. 4321-4370f), and have determined that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment. This rule involves restricting vessel movement within a regulated navigation area. This rule is categorically excluded from further review under paragraph 34(g) of Figure 2-1 of the Commandant Instruction. An environmental analysis checklist supporting this determination and a Categorical Exclusion Determination are available in the docket where indicated under<E T="02">ADDRESSES</E>. We seek any comments or information that may lead to the discovery of a significant environmental impact from this rule.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 33 CFR Part 165</HD>
          <P>Harbors, Marine safety, Navigation (water), Reporting and recordkeeping requirements, Security measures, Waterways.</P>
        </LSTSUB>
        
        <P>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR Part 165 as follows:</P>
        <REGTEXT PART="165" TITLE="33">
          <PART>
            <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
          </PART>
          <AMDPAR>1. The authority citation for Part 165 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>33 U.S.C. 1231; 46 U.S.C. Chapter 701, 3306, 3703; 50 U.S.C. 191, 195; 33 CFR 1.05-1, 6.04-1, 6.04-6, and 160.5; Pub. L. 107-295, 116 Stat. 2064; Department of Homeland Security Delegation No. 0170.1.</P>
          </AUTH>
          
        </REGTEXT>
        <REGTEXT PART="165" TITLE="33">
          <AMDPAR>2. Add § 165.T01-0824 to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 165.T01-0824</SECTNO>
            <SUBJECT>Regulated Navigation Area; Housatonic River Bridge Replacement Operations; Stratford, CT</SUBJECT>
            <P>(a)<E T="03">Location.</E>The following area is a regulated navigation area (RNA): All navigable waters of the Housatonic River between Stratford and Milford, CT, from bank to bank, surface to bottom; bounded to the north by the Metro North Railroad (RR) Bridge marked by a line connecting the following points: Point “A”, 41°12′17.19″ N, 073°06′40.29″ W western edge of the RR bridge in Stratford, CT, east to point “B”, 41°12′20.13″ N, 073°6′29.05″ W eastern edge of the RR bridge in Milford CT; bounded to the south by a line connecting the following points: Point “C” 41°12′14.36″ N, 073°06′41.06″ W western edge of construction trestle in Stratford, CT, east to point “D” 41°12′15.86″ N, 073°06′27.57″ W eastern bank of Housatonic River, Milford, CT.<PRTPAGE P="1149"/>All coordinates are North American Datum 1983.</P>
            <P>(b)<E T="03">Regulations.</E>(1) The general regulations contained in 33 CFR 165.10, 165.11, and 165.13 apply.</P>
            <P>(2) In accordance with the general regulations, entry into, anchoring, or movement within the RNA, during periods of enforcement, is prohibited unless authorized by the Captain of the Port Long Island Sound (COTP) or the COTP's designated representative.</P>
            <P>(3) During periods of enforcement, entry and movement within the RNA is subject to a “Slow-No Wake” speed limit. Vessels may not produce more than a minimum wake and may not attain speeds greater than six knots unless a higher minimum speed is necessary to maintain steerageway when traveling with a strong current. In no case may the wake produced by the vessel be such that it creates a danger of injury to persons, or damage to vessels or structures of any kind.</P>
            <P>(4) During periods of enforcement, all persons and vessels must comply with all orders and directions from the COTP or the COTP's designated representative.</P>
            <P>(5) During periods of enforcement, upon being hailed by a Coast Guard vessel by siren, radio, flashing light or other means, the operator of the vessel must proceed as directed.</P>
            <P>(6) Persons and vessels may request permission to enter the RNA during periods of closure on VHF-16 or via phone at 203-468-4401.</P>
            <P>(7) Notwithstanding anything contained in this rule, the Rules of the Road (33 CFR part 84—Subchapter E, inland navigational rules) are still in effect and must be strictly adhered to at all times.</P>
            <P>(c)<E T="03">Effective period.</E>This rule is effective from January 7, 2013 through November 30, 2017.</P>
            <P>(d)<E T="03">Enforcement period.</E>Except when suspended in accordance with paragraph (e) of this section, this RNA is enforceable 24 hours a day during the effective period.</P>
            <P>(e)<E T="03">Suspension of enforcement.</E>The COTP may suspend enforcement of the RNA. If enforcement is suspended, the COTP will cause a notice of the suspension of enforcement by all appropriate means to promote the widest publicity among the affected segments of the public. Such means of notification may include, but are not limited to, Broadcast Notice to Mariners and Local Notice to Mariners. Such notifications will include the date and time that enforcement is suspended as well as the date and time that enforcement will resume.</P>
            <P>(f)<E T="03">Waterway closure.</E>The COTP may temporarily suspend all traffic through the RNA for any situation that would pose imminent hazard to life on the navigable waters. In the event of a complete waterway closure, the COTP will make advance notice of the closure by all means available to promote the widest public distribution including, but not limited to, Broadcast Notice to Mariners and Local Notice to Mariners. Such notification will include the date and time of the closure as well as the date and time that normal vessel traffic can resume.</P>
            <P>(g) Violations of this RNA may be reported to the COTP, at 203-468-4401 or on VHF-Channel 16. Persons in violation of this RNA may be subject to civil or criminal penalties.</P>
          </SECTION>
        </REGTEXT>
        <SIG>
          <DATED>Dated: December 20, 2012.</DATED>
          <NAME>T.J. Vitullo,</NAME>
          <TITLE>Captain, U.S. Coast Guard,Acting Commander,First Coast Guard District.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00211 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-04-P</BILCOD>
    </RULE>
    <RULE>
      <PREAMB>
        <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
        <CFR>40 CFR Parts 52 and 81</CFR>
        <DEPDOC>[EPA-R09-OAR-2012-0792; FRL-9766-9]</DEPDOC>
        <SUBJECT>Approval and Promulgation of Implementation Plans and Designation of Areas for Air Quality Planning Purposes; State of Nevada; Redesignation of Clark County to Attainment for the 1997 8-Hour Ozone Standard</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Environmental Protection Agency (EPA).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Final rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>EPA is taking final action to approve, as a revision of the Nevada state implementation plan, the State's plan for maintaining the 1997 8-hour ozone standard in Clark County for ten years beyond redesignation, and the related motor vehicle emissions budgets, because they meet the applicable requirements for such plans and budgets. EPA is also taking final action to approve a request from the Nevada Division of Environmental Protection to redesignate the Clark County ozone nonattainment area to attainment for the 1997 8-hour ozone National Ambient Air Quality Standard because the area meets the statutory requirements for redesignation under the Clean Air Act.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>This rule is effective on February 7, 2013.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>EPA has established a docket for this action under Docket ID Number EPA-R09-OAR-2012-0792. Generally, documents in the docket for this action are available electronically at<E T="03">www.regulations.gov</E>and in hard copy at EPA Region IX, 75 Hawthorne Street, San Francisco, California. While all documents in the docket are listed at<E T="03">www.regulations.gov,</E>some information may be publicly available only at the hard copy location (e.g., copyrighted material, large maps), and some may not be publicly available in either location (e.g., confidential business information or “CBI”). To inspect the hard copy materials, please schedule an appointment during normal business hours with the contact listed in the<E T="02">FOR FURTHER INFORMATION CONTACT</E>section.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Ginger Vagenas, Air Planning Office (AIR-2), U.S. Environmental Protection Agency, Region IX, (415) 972-3964,<E T="03">vagenas.ginger@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. This supplementary information section is arranged as follows:</P>
        <HD SOURCE="HD1">Table of Contents</HD>
        <EXTRACT>
          <FP SOURCE="FP-2">I. Summary of Proposed Action</FP>
          <FP SOURCE="FP1-2">A. Determination That the Area Has Attained the Applicable NAAQS</FP>
          <FP SOURCE="FP1-2">B. The Area Must Have a Fully Approved SIP Meeting Requirements Applicable for Purposes of Redesignation Under Section 110 and Part D</FP>
          <FP SOURCE="FP1-2">C. The Area Must Show the Improvement in Air Quality Is Due to Permanent and Enforceable Emissions Reductions</FP>
          <FP SOURCE="FP1-2">D. The Area Must Have a Fully Approved Maintenance Plan Under CAA Section 175A</FP>
          <FP SOURCE="FP-2">II. Public Comments</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. Summary of Proposed Action</HD>

        <P>On November 13, 2012 (77 FR 67600), we proposed to take several related actions. First, under Clean Air Act (CAA or “Act”) section 110(k)(3), EPA proposed to approve a submittal from the Nevada Division of Environmental Protection (NDEP) dated April 11, 2011 of Clark County's<E T="03">Ozone Redesignation Request and Maintenance Plan</E>(March 2011) (“Clark County Ozone Maintenance Plan” or “Ozone Maintenance Plan”) as a revision to the Nevada state implementation plan (SIP).</P>

        <P>In connection with the Clark County Ozone Maintenance Plan, EPA proposed to find that the maintenance demonstration showing that the area will continue to attain the 1997 8-hour ozone national ambient air quality<PRTPAGE P="1150"/>standard (NAAQS or “standard”)<SU>1</SU>
          <FTREF/>for 10 years beyond redesignation (i.e., through 2022), and the contingency provisions describing the actions that Clark County will take in the event of a future monitored violation, meet all applicable requirements for maintenance plans and related contingency provisions in CAA section 175A. EPA also proposed to approve the motor vehicle emissions budgets (MVEBs) in the Clark County Ozone Maintenance Plan because we found they met the applicable transportation conformity requirements under 40 CFR 93.118(e).</P>
        <FTNT>
          <P>
            <SU>1</SU>The 1997 8-hour ozone standard is 0.08 parts per million (ppm) averaged over an 8-hour time frame.</P>
        </FTNT>
        <P>Second, under CAA section 107(d)(3)(D), EPA proposed to approve NDEP's request that accompanied the submittal of the maintenance plan to redesignate the Clark County 8-hour ozone nonattainment area<SU>2</SU>
          <FTREF/>to attainment for the 1997 8-hour ozone NAAQS. We did so based on our conclusion that the area has met the five criteria for redesignation under CAA section 107(d)(3)(E). Our conclusion in this regard was based on our determination that the area has attained the 1997 8-hour ozone NAAQS, that relevant portions of the Nevada SIP are fully approved, that the improvement in air quality is due to permanent and enforceable reductions in emissions, that Nevada has met all requirements applicable to the Clark County 8-hour ozone nonattainment area with respect to section 110 and part D of the CAA, and based on our approval as part of this action of the Clark County Ozone Maintenance Plan.</P>
        <FTNT>
          <P>
            <SU>2</SU>The boundaries of the Clark County ozone nonattainment area are defined in 40 CFR 81.329. Specifically, the area is defined as: “That portion of Clark County that lies in hydrographic areas 164A, 164B, 165, 166, 167, 212, 213, 214, 216, 217, and 218 but excluding the Moapa River Indian Reservation and the Fort Mojave Indian Reservation.” The area includes a significant portion of the unincorporated portions of central and southern Clark County, as well as the cities of Las Vegas, Henderson, North Las Vegas, and Boulder City.</P>
        </FTNT>
        <P>For the purposes of this final rule, we have summarized the basis for our findings in connection with the proposed approvals of the Ozone Maintenance Plan and redesignation request. For a more detailed explanation as well as background information concerning the 1997 8-hour ozone NAAQS, the CAA requirements for redesignation, and the ozone planning history of Clark County, please see our November 13, 2012 proposed rule.</P>
        <HD SOURCE="HD2">A. Determination That the Area Has Attained the Applicable NAAQS</HD>
        <P>Prior to redesignating an area to attainment, CAA section 107(d)(3)(E)(i) requires that we determine that the area has attained the NAAQS. For our proposed rule, consistent with the requirements contained in 40 CFR part 50, EPA reviewed the ozone ambient air monitoring data for the monitoring period from 2009 through 2011, as recorded in the EPA Air Quality System (AQS) database, and determined, based on the complete, quality-assured data for 2009-2011, that the Clark County 8-hour ozone nonattainment area has attained the 1997 8-hour ozone standard because the design value<SU>3</SU>
          <FTREF/>is less than 0.084 ppm. We also reviewed preliminary data from 2012 and found that it was consistent with continued attainment of the standard in the Clark County 8-hour ozone nonattainment area. See pages 67602-67604 of our November 13, 2012 proposed rule.</P>
        <FTNT>
          <P>
            <SU>3</SU>The design value for the 8-hour standard is the three-year average of the annual fourth-highest daily maximum 8-hour ozone concentration at the worst-case monitoring site in the area.</P>
        </FTNT>
        <HD SOURCE="HD2">B. The Area Must Have a Fully Approved SIP Meeting Requirements Applicable for Purposes of Redesignation Under Section 110 and Part D</HD>
        <P>Sections 107(d)(3)(E)(ii) and (v) of the CAA require EPA to determine that the area has a fully approved applicable SIP under section 110(k) that meets all applicable requirements under section 110 and part D for the purposes of redesignation. For the reasons summarized below, we found that the Clark County 8-hour ozone nonattainment area has a fully approved applicable SIP under section 110(k) that meets all applicable requirements under section 110 and part D for the purposes of redesignation. See pages 67604-67607 of our November 13, 2012 proposed rule.</P>
        <P>With respect to section 110 of the CAA (General SIP Requirements), we concluded that NDEP and Clark County have met all SIP requirements for Clark County applicable for purposes of redesignation. Our conclusion in this regard was based on our review of the Clark County portion of the Nevada SIP.</P>
        <P>With respect to part D (of title I of the CAA), we reviewed the Clark County portion of the Nevada SIP for compliance with applicable requirements under both subparts 1 and 2.<SU>4</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>4</SU>Subpart 1 contains general, less prescriptive requirements for all nonattainment areas of any pollutant, including ozone, governed by a NAAQS. Subpart 2 contains additional, more specific requirements for ozone nonattainment areas classified under subpart 2.</P>
        </FTNT>
        <P>First, we noted that EPA previously determined that the Clark County 8-hour ozone nonattainment area attained the 1997 8-hour ozone NAAQS based on 2007-2009 ozone data (76 FR 17343, March 29, 2011), and thereby suspended, under 40 CFR 51.918, the obligation on the State of Nevada to submit an attainment demonstration and associated reasonably available control measures (RACM), a reasonable further progress (RFP) plan, contingency measures and other planning requirements related to attainment of the 1997 8-hour ozone NAAQS. As such, we explained that the State's compliance status with the attainment-related SIP requirements under subpart 1 was not relevant for the purposes of evaluating the State's redesignation request.</P>
        <P>As to the other applicable subpart 1 requirements, we found that:</P>

        <P>• The emissions inventory requirements of CAA section 172(c)(3) would be met by our approval of the Clark County Ozone Maintenance Plan and related emissions inventories for volatile organic compounds (VOC) and oxides of nitrogen (NO<E T="52">X</E>);</P>
        <P>• A fully-approved nonattainment New Source Review (NSR) program was not a prerequisite to redesignation in this instance because the Clark County Ozone Maintenance Plan demonstrates maintenance of the standard without implementation of nonattainment NSR; moreover, after redesignation, sources under NDEP jurisdiction would be subject to the federal PSD program and sources under Clark County jurisdiction would be subject to an EPA-approved PSD program that is deficient in certain respects but not in ways that would interfere with maintenance of the ozone standard; and</P>
        <P>• Clark County and the State previously met the requirements for transportation conformity SIPs under section 176(c) (see EPA's approval of Clark County's transportation conformity SIP at 73 FR 66182, November 7, 2008).<SU>5</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>

            <SU>5</SU>In any event, EPA believes it is reasonable to interpret the conformity requirements as not applicable for purposes of evaluating a redesignation request under section 107(d)(3)(E). See<E T="03">Wall</E>v.<E T="03">EPA,</E>265 F.3d 426, 439 (6th Cir. 2001) upholding this interpretation.</P>
        </FTNT>

        <P>With respect to the requirements associated with subpart 2, we noted that the Clark County 8-hour ozone nonattainment area was initially designated nonattainment under subpart 1 of the CAA, but was subsequently classified as marginal nonattainment for the 1997 8-hour ozone standard under<PRTPAGE P="1151"/>subpart 2 of part D of the CAA in May 2012, i.e., after NDEP's submittal of the redesignation request. Under EPA's longstanding policy of evaluating requirements in accordance with the requirements due at the time a redesignation request is submitted and in consideration of the inequity of applying retroactively any requirements that might in the future be applied, we determined that the requirements under subpart 2 need not be addressed as a condition of redesignation.</P>
        <HD SOURCE="HD2">C. The Area Must Show the Improvement in Air Quality Is Due to Permanent and Enforceable Emissions Reductions</HD>
        <P>Section 107(d)(3)(E)(iii) precludes redesignation of a nonattainment area to attainment unless EPA determines that the improvement in air quality is due to permanent and enforceable reductions in emissions resulting from implementation of the applicable SIP and applicable Federal air pollution control regulations and other permanent and enforceable regulations. Based on our review of the control measures credited in the Clark County Ozone Maintenance Plan as providing the emissions reductions sufficient to attain the 1997 8-hour ozone NAAQS in the Clark County 8-hour ozone nonattainment area through the year 2022, and based on our consideration of other factors such as weather patterns and economic activity, we found that the improvement in air quality in the Clark County 8-hour ozone nonattainment area is the result of permanent and enforceable emissions reductions from a combination of Federal vehicle and fuel measures and EPA-approved State and local control measures. See pages 670607-67608 of our November 13, 2012 proposed rule.</P>
        <HD SOURCE="HD2">D. The Area Must Have a Fully Approved Maintenance Plan Under CAA Section 175A</HD>
        <P>Section 175A of the CAA sets forth the elements of a maintenance plan for areas seeking redesignation from nonattainment to attainment. As explained in the proposed rule, we interpret this section of the Act to require, in general, the following core elements: Attainment inventory, maintenance demonstration, monitoring network, verification of continued attainment, and contingency plan. Based on our review and evaluation of the Ozone Maintenance Plan, we concluded that it contained the core elements and met the requirements of CAA section 175A. See pages 67608-67613. Our conclusion was based on the following findings:</P>
        <P>• The base year emissions inventories for 2008 are comprehensive, that the methods and assumptions used by Clark County Department of Air Quality (DAQ) to develop the 2008 emission inventory are reasonable, and that the inventories reasonably estimate actual ozone season emissions in an attainment year. Moreover, we found that the 2008 emissions inventories in the Ozone Maintenance Plan reflect the latest planning assumptions and emissions models available at the time the plan was developed, and provide a comprehensive and reasonably accurate basis upon which to forecast ozone precursor emissions for years 2015 and 2022;</P>
        <P>• The projected VOC and NO<E T="52">X</E>emissions estimates adequately account for projected area-wide growth, specific projects (including, among others, the Nellis Air Force Base F-35 beddown project), and emissions reduction credits (ERCs), and show that VOC and NO<E T="52">X</E>emissions would remain well below the attainment levels throughout the 10-year maintenance period and thereby adequately demonstrate maintenance through that period;</P>
        <P>• Clark County DAQ has committed to continue to operate the air quality monitoring network to verify the continued attainment of the 1997 8-hour ozone NAAQS ambient ozone monitoring;<SU>6</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>6</SU>Although the Ozone Maintenance Plan is not explicit in this regard, we presume that Clark County DAQ's intention to continue operation of a monitoring network means that the agency intends to do so consistent with EPA's monitoring requirements in 40 CFR part 58 (“Ambient Air Quality Surveillance”).</P>
        </FTNT>
        <P>• Clark County DAQ's commitment in the Ozone Maintenance Plan to the continued operation of an ozone monitoring network and the requirement that NDEP and Clark County DAQ must inventory emissions sources and report to EPA on a periodic basis<SU>7</SU>
          <FTREF/>would be sufficient for the purpose of verifying continued attainment; and</P>
        <FTNT>
          <P>
            <SU>7</SU>See 40 CFR part 51, subpart A (“Air Emissions Reporting Requirements”).</P>
        </FTNT>
        <P>• The contingency provisions of the Ozone Maintenance Plan clearly identify specific contingency measures, contain adequate tracking and triggering mechanisms to determine when contingency measures are needed, contain a sufficient description of the process of recommending and implementing contingency measures, and contain specific timelines for action, and would, therefore, be adequate to ensure prompt correction of a violation and comply with the contingency-related requirements under CAA section 175A(d).</P>
        <P>Lastly, we proposed to approve the motor vehicle emissions budgets (MVEBs) contained in the Ozone Maintenance Plan because we found that they meet the transportation conformity adequacy requirements under 40 CFR 93.118(e)(4) and (5). In so proposing, we found that, among other things, the MVEBs, when considered with emissions from all other sources, would be consistent with maintenance of the 1997 8-hour ozone NAAQS in the Clark County 8-hour ozone nonattainment area.</P>
        <HD SOURCE="HD1">II. Public Comments</HD>
        <P>Our November 13, 2012 proposed rule provided for a 30-day comment period. We received comment letters in support of our proposed action from NDEP and the Washoe County Health District. In its comment letter, NDEP also noted that approval of the redesignation request for the Clark County 8-hour ozone nonattainment area will negate the need, that had been identified in EPA's proposed limited approval and limited disapproval of Clark County's revised NSR rules at 77 FR 43206, for a revision to NDEP's nonattainment NSR provisions at this time. We received no adverse comments in response to our November 13, 2012 proposed rule.</P>
        <HD SOURCE="HD1">III. Final Action</HD>

        <P>Under CAA sections 110(k)(3) and 107(d)(3)(D), and for the reasons set forth in our proposed rule and summarized above, EPA is taking final action to approve NDEP's submittal dated April 11, 2011 of Clark County's<E T="03">Ozone Redesignation Request and Maintenance Plan</E>(March 2011) (“Clark County Ozone Maintenance Plan”) as a revision to the Nevada SIP and to approve NDEP's request to redesignate the Clark County 8-hour ozone nonattainment area to attainment for the 1997 8-hour ozone NAAQS. In connection with the Clark County Ozone Maintenance Plan, EPA finds that the maintenance demonstration showing that the area will continue to attain the 1997 8-hour ozone NAAQS for 10 years beyond redesignation (i.e., through 2022) and the contingency provisions describing the actions that Clark County will take in the event of a future monitored violation meet all applicable requirements for maintenance plans and related contingency provisions in CAA section 175A. EPA is also approving the following motor vehicle emissions budgets (MVEBs) from the Clark County Ozone Maintenance Plan for transportation conformity purposes<PRTPAGE P="1152"/>because we find that they meet the applicable transportation conformity requirements under 40 CFR 93.118(e):</P>
        <GPOTABLE CDEF="s20,14,14" COLS="3" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Budget year</CHED>
            <CHED H="1">VOC (tpd,<LI>average summer</LI>
              <LI>weekday)</LI>
            </CHED>
            <CHED H="1">NO<E T="52">X</E>(tpd,<LI>average summer</LI>
              <LI>weekday)</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01" O="xl">2008</ENT>
            <ENT>65.08</ENT>
            <ENT>68.46</ENT>
          </ROW>
          <ROW>
            <ENT I="01" O="xl">2015</ENT>
            <ENT>45.32</ENT>
            <ENT>34.69</ENT>
          </ROW>
          <ROW>
            <ENT I="01" O="xl">2022</ENT>
            <ENT>36.71</ENT>
            <ENT>23.15</ENT>
          </ROW>
        </GPOTABLE>

        <P>These new MVEBs become effective on the date of publication of this final rule in the<E T="04">Federal Register</E>(see 40 CFR 93.118(f)(2)) and must be used by U.S. Department of Transportation (DOT) and the Regional Transportation Commission of Southern Nevada (RTC) for future transportation conformity determinations for Clark County. The existing 2008 VOC and NO<E T="52">X</E>MVEBs from the Clark County Early Progress Plan,<SU>8</SU>
          <FTREF/>which EPA found adequate in 2009, are replaced by these budgets.</P>
        <FTNT>
          <P>
            <SU>8</SU>On July 28, 2008, NDEP submitted the<E T="03">8-Hour Early Progress Plan for Clark County, Nevada</E>(June 2008) to EPA as a revision to the Nevada SIP.</P>
        </FTNT>
        <P>In connection with the redesignation request, EPA is taking final action to approve the request because we find that the area has met the five criteria for redesignation under CAA section 107(d)(3)(E). Specifically, we find that the area has attained the 1997 8-hour ozone NAAQS, that relevant portions of the Nevada SIP are fully approved, that the improvement in air quality is due to permanent and enforceable reductions in emissions, that Nevada has met all requirements applicable to the Clark County 8-hour ozone nonattainment area with respect to section 110 and part D of the CAA, and that the area has a fully approved maintenance plan meeting the requirements of section 175A (i.e., the Clark County Ozone Maintenance Plan approved herein).</P>
        <HD SOURCE="HD1">IV. Statutory and Executive Order Reviews</HD>
        <P>Under the CAA, redesignation of an area to attainment under section 107(d)(3)(E) and the accompanying approval of a maintenance plan under section 175A are actions that affect the status of a geographical area and do not impose any additional regulatory requirements on sources beyond those imposed by State law. Redesignation to attainment does not in and of itself create any new requirements, but rather results in the applicability of requirements contained in the CAA for areas that have been redesignated to attainment. Moreover, the Administrator is required to approve a SIP submission that complies with the provisions of the Act and applicable Federal regulations. 42 U.S.C. 7410(k); 40 CFR 52.02(a). Thus, in reviewing SIP submissions, EPA's role is to approve State choices, provided that they meet the criteria of the Clean Air Act. Accordingly, these actions merely approve a State plan and redesignation request as meeting Federal requirements and do not impose additional requirements beyond those by State law. For these reasons, these actions:</P>
        <P>• Are not a “significant regulatory action” subject to review by the Office of Management and Budget under Executive Order 12866 (58 FR 51735, October 4, 1993);</P>

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

        <P>• Are certified as not having a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601<E T="03">et seq.</E>);</P>
        <P>• Do not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4);</P>
        <P>• Do not have Federalism implications as specified in Executive Order 13132 (64 FR 43255, August 10, 1999);</P>
        <P>• Are not an economically significant regulatory action based on health or safety risks subject to Executive Order 13045 (62 FR 19885, April 23, 1997);</P>
        <P>• Are not a significant regulatory action subject to Executive Order 13211 (66 FR 28355, May 22, 2001);</P>
        <P>• Are not subject to requirements of Section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) because application of those requirements would be inconsistent with the CAA; and</P>
        <P>• Do not provide EPA with the discretionary authority to address disproportionate human health or environmental effects with practical, appropriate, and legally permissible methods under Executive Order 12898 (59 FR 7629, February 16, 1994).</P>
        <P>In addition, this rule does not have Tribal implications as specified by Executive Order 13175 (65 FR 67249, November 9, 2000), because the SIP is not approved to apply in Indian country located in the State, and EPA notes that it will not impose substantial direct costs on Tribal governments or preempt Tribal law. Nonetheless, EPA discussed the proposed action with the one Tribe, the Las Vegas Paiute Tribe, located within the Clark County 8-hour ozone nonattainment area. The Tribe has indicated that it concurs with the redesignation request.</P>

        <P>The Congressional Review Act, 5 U.S.C. 801 et seq., as added by the Small Business Regulatory Enforcement Fairness Act of 1996, generally provides that before a rule may take effect, the agency promulgating the rule must submit a rule report, which includes a copy of the rule, to each House of the Congress and to the Comptroller General of the United States. EPA will submit a report containing this action and other required information to the U.S. Senate, the U.S. House of Representatives, and the Comptroller General of the United States prior to publication of the rule in the<E T="04">Federal Register.</E>A major rule cannot take effect until 60 days after it is published in the<E T="04">Federal Register.</E>This action is not a “major rule” as defined by 5 U.S.C. 804(2).</P>
        <P>Under section 307(b)(1) of the CAA, petitions for judicial review of this action must be filed in the United States Court of Appeals for the appropriate circuit by March 11, 2013. Filing a petition for reconsideration by the Administrator of this final rule does not affect the finality of this action for the purposes of judicial review nor does it extend the time within which a petition for judicial review may be filed, and shall not postpone the effectiveness of such rule or action. This action may not be challenged later in proceedings to enforce its requirements. (See section 307(b)(2)).</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects</HD>
          <CFR>40 CFR Part 52</CFR>
          <P>Environmental protection, Air pollution control, Incorporation by reference, Intergovernmental relations, Nitrogen dioxide, Ozone, Reporting and recordkeeping requirements, Volatile organic compounds.</P>
          <CFR>40 CFR Part 81</CFR>
          <P>Environmental protection, Air pollution control, National parks, Wilderness areas.</P>
        </LSTSUB>
        <SIG>
          <DATED>Dated: December 20, 2012.</DATED>
          <NAME>Jared Blumenfeld,</NAME>
          <TITLE>Regional Administrator, Region IX.</TITLE>
        </SIG>
        
        <P>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<E T="03">et seq.</E>
            </P>
          </AUTH>
          <SUBPART>
            <HD SOURCE="HED">Subpart DD—Nevada</HD>
          </SUBPART>
        </REGTEXT>
        <REGTEXT PART="52" TITLE="40">

          <AMDPAR>2. Section 52.1470 in paragraph (e), the table is amended by adding an entry for “Ozone Redesignation Request and<PRTPAGE P="1153"/>Maintenance Plan, Clark County, Nevada (March 2011)” after the entry for “Emissions Inventory for 1995” to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 52.1470</SECTNO>
            <SUBJECT>Identification of plan.</SUBJECT>
            <STARS/>
            <P>(e) * * *</P>
            <GPOTABLE CDEF="s50,r50,12,r50,r50" COLS="5" OPTS="L1,i1">
              <TTITLE>EPA-Approved Nevada Nonregulatory and Quasi-Regulatory Measures</TTITLE>
              <BOXHD>
                <CHED H="1">Name of SIP provision</CHED>
                <CHED H="1">Applicable geographic or nonattainment area</CHED>
                <CHED H="1">State submittal date</CHED>
                <CHED H="1">EPA approval date</CHED>
                <CHED H="1">Explanation</CHED>
              </BOXHD>
              <ROW EXPSTB="04" RUL="s">
                <ENT I="21">
                  <E T="02">Air Quality Implementation Plan for the State of Nevada</E>
                </ENT>
              </ROW>
              <ROW EXPSTB="00">
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*******</ENT>
              </ROW>
              <ROW>
                <ENT I="01">Ozone Redesignation Request and Maintenance Plan, Clark County, Nevada (March 2011)</ENT>
                <ENT>Clark County, Nevada: that portion of Clark County that lies in hydrographic areas 164A, 164B, 165, 166, 167, 212, 213, 214, 216, 217, and 218, but excluding the Moapa River Indian Reservation and the Fort Mohave Indian Reservation</ENT>
                <ENT>4/11/11</ENT>
                <ENT>[Insert<E T="02">Federal Register</E>page number where the document begins] 1/8/13</ENT>
                <ENT>Approval includes appendices A, B, and C. Relates to the 1997 8-hour ozone standard.</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*******</ENT>
              </ROW>
            </GPOTABLE>
          </SECTION>
        </REGTEXT>
        <REGTEXT PART="81" TITLE="40">
          <PART>
            <HD SOURCE="HED">PART 81—[AMENDED]</HD>
          </PART>
          <AMDPAR>3. The authority citation for part 81 continues to read as follows:</AMDPAR>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>42 U.S.C. 7401<E T="03">et seq.</E>
            </P>
          </AUTH>
          <SUBPART>
            <HD SOURCE="HED">Subpart C—[AMENDED]</HD>
          </SUBPART>
        </REGTEXT>
        <REGTEXT PART="81" TITLE="40">
          <AMDPAR>4. Section 81.329 is amended in the table for “Nevada—1997 8-Hour Ozone NAAQS (Primary and Secondary)” by revising the entry for “Las Vegas, NV” to read as follows:</AMDPAR>
          <SECTION>
            <SECTNO>§ 81.329</SECTNO>
            <SUBJECT>Nevada.</SUBJECT>
            <STARS/>
            <GPOTABLE CDEF="s100,14,xs60,14,14" COLS="5" OPTS="L1,i1">
              <TTITLE>Nevada—1997 8-Hour Ozone NAAQS</TTITLE>
              <TDESC>[Primary and secondary]</TDESC>
              <BOXHD>
                <CHED H="1">Designated area</CHED>
                <CHED H="1">Designation<E T="51">a</E>
                </CHED>
                <CHED H="2">Date<E T="51">1</E>
                </CHED>
                <CHED H="2">Type</CHED>
                <CHED H="1">Classification</CHED>
                <CHED H="2">Date<E T="51">1</E>
                </CHED>
                <CHED H="2">Type</CHED>
              </BOXHD>
              <ROW>
                <ENT I="01">Las Vegas, NV: Clark County (part) That portion of Clark County that lies in hydrographic areas 164A, 164B, 165, 166, 167, 212, 213, 214, 216, 217, and 218, but excluding the Moapa River Indian Reservation and the Fort Mohave Indian Reservation<SU>b</SU>
                </ENT>
                <ENT>2/7/13</ENT>
                <ENT>Attainment</ENT>
              </ROW>
              <ROW>
                <ENT I="22"/>
              </ROW>
              <ROW>
                <ENT I="28">*******</ENT>
              </ROW>
              <TNOTE>
                <SU>a</SU>Includes Indian Country located in each county or area, except as otherwise specified.</TNOTE>
              <TNOTE>
                <SU>b</SU>The use of reservation boundaries for this designation is for purposes of CAA planning only and is not intended to be a federal determination of the exact boundaries of the reservations. Nor does the specific listing of the Tribes in this table confer, deny, or withdraw Federal recognition of any of the Tribes listed or not listed.</TNOTE>
              <TNOTE>
                <SU>1</SU>This date is June 15, 2004 unless otherwise noted.</TNOTE>
            </GPOTABLE>
          </SECTION>
        </REGTEXT>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00057 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6560-50-P</BILCOD>
    </RULE>
  </RULES>
  <VOL>78</VOL>
  <NO>5</NO>
  <DATE>Tuesday, January 8, 2013</DATE>
  <UNITNAME>Proposed Rules</UNITNAME>
  <PRORULES>
    <PRORULE>
      <PREAMB>
        <PRTPAGE P="1154"/>
        <AGENCY TYPE="F">NUCLEAR REGULATORY COMMISSION</AGENCY>
        <CFR>10 CFR Parts 50 &amp; 52</CFR>
        <DEPDOC>[NRC-2012-0031]</DEPDOC>
        <RIN>RIN 3150-AJ11</RIN>
        <SUBJECT>Onsite Emergency Response Capabilities</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Nuclear Regulatory Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Draft regulatory basis.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The U.S. Nuclear Regulatory Commission (NRC or the Commission) is issuing a draft regulatory basis document to support the potential amendment of its regulations concerning nuclear power plant licensees' onsite emergency response capabilities. The NRC is seeking public comments on this document. The issuance of this draft regulatory basis document is one of the actions stemming from the NRC's lessons-learned efforts associated with the March 2011 Fukushima Dai-ichi Nuclear Power Plant accident in Japan.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Submit comments by February 22, 2013. Comments received after this date will be considered if it is practical to do so, but the NRC is only able to ensure consideration of comments received on or before this date.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>You may access information and comment submissions related to these documents, which the NRC possesses and are publicly available, by searching on<E T="03">http://www.regulations.gov</E>under Docket ID NRC-2012-0031. You may submit comments by any of the following methods:</P>
          <P>•<E T="03">Federal Rulemaking Web Site:</E>Go to<E T="03">http://www.regulations.gov</E>and search for Docket ID NRC-2012-0031. Address questions about NRC dockets to Carol Gallagher; telephone: 301-492-3668; email:<E T="03">Carol.Gallagher@nrc.gov.</E>
          </P>
          <P>•<E T="03">Email comments to: Rulemaking.Comments@nrc.gov.</E>If you do not receive an automatic email reply confirming receipt, contact us directly at 301-415-1677.</P>
          <P>•<E T="03">Fax comments to:</E>Secretary, U.S. Nuclear Regulatory Commission at 301-415-1101.</P>
          <P>•<E T="03">Mail comments to:</E>Secretary, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, ATTN: Rulemakings and Adjudications Staff.</P>
          <P>•<E T="03">Hand deliver comments to:</E>11555 Rockville Pike, Rockville, Maryland 20852, between 7:30 a.m. and 4:15 p.m. (Eastern time) Federal workdays; telephone: 301-415-1677.</P>

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

          <P>Robert H. Beall, Office of Nuclear Reactor Regulation, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001; telephone: 301-415-3874; email:<E T="03">Robert.Beall@nrc.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Accessing Information and Submitting Comments</HD>
        <HD SOURCE="HD2">A. Accessing Information</HD>
        <P>Please refer to Docket ID NRC-2012-0031 when contacting the NRC about the availability of information for this notice. You may access information related to this draft regulatory basis, which the NRC possesses and is publicly available, by the following methods:</P>
        <P>•<E T="03">Federal Rulemaking Web Site:</E>Go to<E T="03">http://www.regulations.gov</E>and search for Docket ID NRC-2012-0031.</P>
        <P>•<E T="03">NRC's Agencywide Documents Access and Management System (ADAMS):</E>You may access publicly available documents online in the NRC Library at<E T="03">http://www.nrc.gov/reading-rm/adams.html.</E>To begin the search, select “<E T="03">ADAMS Public Documents</E>” and then select “<E T="03">Begin Web-based ADAMS Search.”</E>For problems with ADAMS, please contact the NRC's Public Document Room (PDR) reference staff at 1-800-397-4209, 301-415-4737, or by email to<E T="03">PDR.Resource@nrc.gov.</E>The ADAMS Accession No. for each document referenced in this notice (if that document is available in ADAMS) is provided the first time that a document is referenced. A table listing documents that provide additional background and supporting information is in Appendix F of the draft regulatory basis.</P>
        <P>•<E T="03">NRC's PDR:</E>You may examine and purchase copies of public documents at the NRC's PDR, Room O1-F21, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852.</P>
        <HD SOURCE="HD2">B. Submitting Comments</HD>
        <P>Please include Docket ID NRC-2012-0031 in the subject line of your comment submission to ensure that the NRC is able to make your comment submission available to the public in this docket.</P>

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

        <P>As the NRC continues its ongoing proposed rulemaking effort to amend portions of Parts 50 and 52 of Title 10 of the<E T="03">Code of Federal Regulations</E>(10 CFR) to strengthen and integrate onsite emergency response capabilities, the NRC is making preliminary documents publicly available on the Federal rulemaking Web site,<E T="03">www.regulations.gov,</E>under Docket ID NRC-2012-0031. By making these documents publicly available, the NRC seeks to inform stakeholders of the current status of the NRC's rulemaking development activities and to provide preparatory material for future public meetings. The NRC is instituting a 45-day public comment period on these materials, and the public is encouraged to participate in any related public meetings.<PRTPAGE P="1155"/>
        </P>
        <HD SOURCE="HD1">III. Publicly Available Documents</HD>
        <P>The NRC has posted on<E T="03">www.regulations.gov</E>for public availability the draft regulatory basis to strengthen and integrate onsite emergency response capabilities. This regulatory basis documents the reasons why the NRC determined rulemaking was the appropriate course of action to remedy a regulatory shortcoming.</P>
        <P>In addition, the NRC has posted preliminary proposed rule language related to this rulemaking as Appendix C of the draft regulatory basis. This preliminary proposed rule language contains one portion of the NRC's proposed changes. This language does not represent a final NRC staff position nor has it been reviewed by the Commission. Therefore, the preliminary proposed rule language may undergo significant revision during the rulemaking process.</P>

        <P>The NRC is requesting formal public comments on the draft regulatory basis and the preliminary proposed rule language. The NRC may post additional materials, including other preliminary proposed rule language, to the Federal rulemaking Web site at<E T="03">www.regulations.gov,</E>under Docket ID NRC-2012-0031. The Federal rulemaking Web site allows you to receive alerts when changes or additions occur in a docket folder. To subscribe: (1) Navigate to the docket folder (NRC-2012-0031); (2) click the “Email Alert” link; and (3) enter your email address and select how frequently you would like to receive emails (daily, weekly, or monthly).</P>
        <HD SOURCE="HD1">IV. Plain Writing</HD>
        <P>The Plain Writing Act of 2010 (Pub. L. 111-274) requires Federal agencies to write documents in a clear, concise, well-organized manner that also follows other best practices appropriate to the subject or field and the intended audience. Although regulations are exempt under the Act, the NRC is applying the same principles to its rulemaking documents. Therefore, the NRC has written this document, including the preliminary proposed rule language, to be consistent with the Plain Writing Act.</P>
        <SIG>
          <DATED>Dated at Rockville, Maryland, this 26th day of December, 2012.</DATED>
          
          <P>For the Nuclear Regulatory Commission.</P>
          
          <NAME>Sher Bahadur,</NAME>
          <TITLE>Deputy Director, Division of Policy and Rulemaking,  Office of Nuclear Reactor Regulation.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31706 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 7590-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION</AGENCY>
        <CFR>10 CFR Part 61</CFR>
        <DEPDOC>[NRC-2011-0012]</DEPDOC>
        <RIN>RIN 3150-AI92</RIN>
        <SUBJECT>Low-Level Waste Disposal</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Nuclear Regulatory Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Regulatory basis and preliminary rule language; second request for comment; correction.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The U.S. Nuclear Regulatory Commission (NRC) is correcting a document appearing in the<E T="04">Federal Register</E>on December 7, 2012 entitled, “Low-Level Waste Disposal” that announced the availability of a regulatory basis document and requested comment on preliminary rule language. This action is necessary to correct the title and number used to access the regulatory basis document in the NRC's Agencywide Documents Access and Management System (ADAMS).</P>
        </SUM>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Please refer to Docket ID NRC-2011-0012 when contacting the NRC about the availability of information for this document. You may access information and comment submittals related to this document, which the NRC possesses and are publicly available, by any of the following methods:</P>
          <P>•<E T="03">Federal Rulemaking Web site:</E>Go to<E T="03">http://www.regulations.gov</E>and search for Docket ID NRC-2011-0012.</P>
          <P>•<E T="03">ADAMS:</E>You may access publicly available documents online in the NRC Library at<E T="03">http://www.nrc.gov/reading-rm/adams.html.</E>To begin the search, select “ADAMS Public Documents” and then select “<E T="03">Begin Web-based ADAMS Search.”</E>For problems with ADAMS, please contact the NRC's Public Document Room (PDR) reference staff at 1-800-397-4209, 301-415-4737, or by email to<E T="03">pdr.resource@nrc.gov.</E>The ADAMS accession number for each document referenced in this document (if that document is available in ADAMS) is provided the first time that a document is referenced.</P>
          <P>•<E T="03">NRC's PDR:</E>You may examine and purchase copies of public documents at the NRC's PDR, Room O1-F21, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Andrew Carrera, Office of Federal and State Materials and Environmental Management Programs, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, telephone 301-415-1078, email<E T="03">Andrew.Carrera@nrc.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>The NRC is correcting the accession number and title of the regulatory basis document that was referenced in a document the NRC published on December 7, 2012 (77 FR 72997). The regulatory basis document has been further corrected to remove a reference to an unavailable document.</P>
        <P>On page 72997 of<E T="04">Federal Register</E>document 2012-29527, published December 07, 2012 (77 FR 72997), in the third column, under the caption titled<E T="02">SUPPLEMENTARY INFORMATION,</E>in the last paragraph of Section A,<E T="03">Accessing Information,</E>under Section I,<E T="03">Accessing Information and Submitting Comments,</E>“Regulatory Analysis forProposed Revisions to Low-Level Waste Disposal Requirement (10 CFR part 61)” is corrected to read “Regulatory Basis;” and “ML12306A480” is corrected to read “ML12356A242.”</P>
        <SIG>
          <DATED>Dated at Rockville, Maryland, this 28th day of December, 2012.</DATED>
          
          <P>For the Nuclear Regulatory Commission.</P>
          
          <NAME>Kevin O'Sullivan,</NAME>
          <TITLE>Acting Director,Division of Intergovernmental Liaisonand Rulemaking,Office of Federal and State Materialsand Environmental Management Programs.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31704 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 7590-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
        <SUBAGY>Federal Aviation Administration</SUBAGY>
        <CFR>14 CFR Part 39</CFR>
        <DEPDOC>[Docket No. FAA-2012-18033; Directorate Identifier 2004-CE-16-AD]</DEPDOC>
        <RIN>RIN 2120-AA64</RIN>
        <SUBJECT>Airworthiness Directives; Cessna Aircraft Company Airplanes</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Aviation Administration (FAA), DOT.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of proposed rulemaking (NPRM).</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>We propose to revise an existing airworthiness directive (AD) that applies to all Cessna Aircraft Company (Cessna) Models 190, 195 (L-126A,B,C), 195A, and 195B airplanes that are equipped with certain inboard aileron hinge brackets. The existing AD currently requires you to repetitively inspect the affected inboard aileron hinge brackets for cracks or corrosion and replace them if cracks or corrosion is found. Replacement with aluminum brackets would terminate the need for<PRTPAGE P="1156"/>the repetitive inspections. Since we issued AD 2004-21-08, the FAA, in recent months, has received reports of confusion between the casting number on the aileron hinge bracket and the part number (P/N) called out in the AD. This proposed AD would retain the actions of AD 2004-21-08 while requiring future compliance following a revised service bulletin that clarifies the casting numbers and part numbers to be inspected. We are proposing this AD to correct the unsafe condition on these products.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>We must receive comments on this proposed AD by February 22, 2013.</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>Deliver to Mail address above between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.</P>

          <P>For service information identified in this AD, contact Cessna Aircraft Company, Customer service, P.O. Box 7706, Wichita, KS 67277; telephone: (316) 517-5800; fax: (316) 517-7271; email:<E T="03">customercare@cessna.textron.com</E>; Internet:<E T="03">http://www.cessnasupport.com.</E>You may review copies of the referenced service information at the FAA, Small Airplane Directorate, 901 Locust, Kansas City, MO 64106. For information on the availability of this material at the FAA, call (816) 329-4148.</P>
        </ADD>
        <HD SOURCE="HD1">Examining the AD Docket</HD>
        <P>You may examine the AD docket on the Internet at<E T="03">http://www.regulations.gov</E>; or in person at the Docket Management Facility between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this proposed AD, the regulatory evaluation, any comments received, and other information. The street address for the Docket Office (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>Gary Park, Aerospace Engineer, Wichita ACO, FAA, 1801 Airport Road, Wichita, KS 67209; phone: (316) 946-4123; fax: (316) 946-4107; email:<E T="03">gary.park@faa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Comments Invited</HD>

        <P>We invite you to send any written relevant data, views, or arguments about this proposed AD. Send your comments to an address listed under the<E T="02">ADDRESSES</E>section. Include “Docket No. FAA-2012-18033; Directorate Identifier 2004-CE-16-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>On October 13, 2004, we issued AD 2004-21-08, amendment 39-13828 (69 FR 62396, October 26, 2004), for all Cessna Models 190, 195 (L-126A,B,C), 195A, and 195B airplanes that are equipped with certain inboard aileron hinge brackets. That AD requires you to repetitively inspect the affected inboard aileron hinge brackets for cracks or corrosion and replace them if cracks or corrosion is found. Replacement with aluminum brackets would terminate the need for the repetitive inspections.</P>
        <P>AD 2004-21-08 (69 FR 62396, October 26, 2004) resulted from several reports of cracks and corrosion found on the magnesium aileron hinge brackets. Magnesium is known to be susceptible to corrosion. We issued AD 2004-21-08 (69 FR 62396, October 26, 2004) to detect and correct corrosion damage to the inboard aileron hinge brackets. Such damage could result in the brackets cracking across the bearing boss and could lead to the aileron separating from the airplane with consequent reduced or loss of control.</P>
        <HD SOURCE="HD1">Actions Since Existing AD Was Issued</HD>
        <P>Since we issued AD 2004-21-08 (69 FR 62396, October 26, 2004), the FAA, in recent months, has received reports of confusion between the casting number on the aileron hinge bracket and the P/N called out in the AD. Due to this misunderstanding, proper inspections and/or replacement of the aileron hinge bracket may not be occurring following the AD. In one report, a service center provided an airworthiness compliance record stating “aileron hinge brackets are of a different part # than those specified in the note.” However, during a later inspection of the bracket, a crack was found through the bearing boss.</P>
        <HD SOURCE="HD1">Relevant Service Information</HD>
        <P>We reviewed Cessna Aircraft Company Single Engine Service Bulletin SEB04-1, dated April 26, 2004, and Single Engine Service Bulletin SEB04-01, Revision 1, dated October 3, 2012. The service information describes procedures for:</P>
        
        <FP SOURCE="FP-1">—Inspecting P/N 0322709 and P/N 0322709-1 inboard aileron hinge brackets for cracks or corrosion; and</FP>
        <FP SOURCE="FP-1">—Replacing any bracket found cracked or corroded with a bracket that is FAA-approved and made from aluminum.</FP>
        
        <P>Revision 1 of the service information adds casting numbers for the parts to be inspected and clarifies the inspection.</P>
        <HD SOURCE="HD1">FAA's Determination</HD>
        <P>We are proposing this AD because we evaluated all the relevant information and determined the unsafe condition described previously is likely to exist or develop in other products of the same type design.</P>
        <HD SOURCE="HD1">Proposed AD Requirements</HD>
        <P>This proposed AD would retain all requirements of AD 2004-21-08 (69 FR 62396, October 26, 2004) while requiring future compliance following a revised service bulletin that clarifies the casting numbers and part numbers to be inspected.</P>
        <HD SOURCE="HD1">Change to Existing AD</HD>
        <P>This proposed AD would retain all requirements of AD 2004-21-08 (69 FR 62396, October 26, 2004). Since AD 2004-21-08 was issued, the AD format has been revised, and certain paragraphs have been rearranged. As a result, the corresponding paragraph identifiers have changed in this proposed AD, as listed in the following table:</P>
        <GPOTABLE CDEF="15C,15C" COLS="2" OPTS="L2,i1">
          <TTITLE>Revised Paragraph Identifiers</TTITLE>
          <BOXHD>
            <CHED H="1">Requirement in AD 2004-21-08</CHED>
            <CHED H="1">Corresponding<LI>requirement in this proposed AD</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">paragraph (e)(1)</ENT>
            <ENT>paragraph (h)</ENT>
          </ROW>
          <ROW>
            <ENT I="01">paragraph (e)(2)</ENT>
            <ENT>paragraph (i)</ENT>
          </ROW>
          <ROW>
            <ENT I="01">paragraph (e)(3)</ENT>
            <ENT>paragraph (j)</ENT>
          </ROW>
        </GPOTABLE>
        <HD SOURCE="HD1">Costs of Compliance</HD>
        <P>We estimate that this proposed AD affects 643 airplanes of U.S. registry.</P>

        <P>We estimate the following costs to comply with this proposed AD:<PRTPAGE P="1157"/>
        </P>
        <GPOTABLE CDEF="s50,r100,r50,12C,r100" 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">Inspection of the affected inboard aileron hinge brackets for cracks or corrosion</ENT>
            <ENT>1 work-hour × $85 per hour = $85</ENT>
            <ENT>Not Applicable</ENT>
            <ENT>$85</ENT>
            <ENT>1,180 airplanes × $85 = $54,655.</ENT>
          </ROW>
        </GPOTABLE>
        <P>The new requirements of this proposed AD add no additional economic burden.</P>
        <P>We estimate the following costs to do any necessary replacements that would be required based on the results of the proposed inspection. We have no way of determining the number of aircraft that might need these replacements:</P>
        <GPOTABLE CDEF="s75,r75,12,12" COLS="4" OPTS="L2,i1">
          <TTITLE>On-Condition Costs</TTITLE>
          <BOXHD>
            <CHED H="1">Action</CHED>
            <CHED H="1">Labor cost</CHED>
            <CHED H="1">Parts cost</CHED>
            <CHED H="1">Cost per<LI>product</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Replacement of left-hand (LH) brackets</ENT>
            <ENT>3 work-hours × $85 per hour = $255</ENT>
            <ENT>$1,999</ENT>
            <ENT>$2,254</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Replacement of right-hand (RH) brackets</ENT>
            <ENT>3 work-hours × $85 per hour = $255</ENT>
            <ENT>1,592</ENT>
            <ENT>1,847</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Replacement of LH and RH brackets</ENT>
            <ENT>6 work-hours × $85 per hour = $510</ENT>
            <ENT>4,101</ENT>
            <ENT>4,611</ENT>
          </ROW>
        </GPOTABLE>
        <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 have 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 that the proposed regulation:</E>
        </P>
        <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
        <P>(2) Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979),</P>
        <P>(3) Will not affect intrastate aviation in Alaska, and</P>
        <P>(4) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
          <P>Air transportation, Aircraft, Aviation safety,  Incorporation by reference, Safety.</P>
        </LSTSUB>
        <HD SOURCE="HD1">The Proposed Amendment</HD>
        <P>Accordingly, under the authority delegated to me by the Administrator, the FAA proposes to amend 14 CFR part 39 as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
        </PART>
        <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>49 U.S.C. 106(g), 40113, 44701.</P>
        </AUTH>
        <SECTION>
          <SECTNO>§ 39.13</SECTNO>
          <SUBJECT>[Amended]</SUBJECT>
        </SECTION>
        <AMDPAR>2. The FAA amends § 39.13 by removing airworthiness directive (AD) 2004-21-08, Amendment 39-13828 (69 FR 62396, October 26, 2004), and adding the following new AD:</AMDPAR>
        
        <EXTRACT>
          <FP SOURCE="FP-2">
            <E T="04">Cessna Aircraft Company:</E>Docket No. FAA-2012-18033; Directorate Identifier 2004-CE-16-AD.</FP>
          <HD SOURCE="HD1">(a) Comments Due Date</HD>
          <P>The FAA must receive comments on this AD action by February 22, 2013.</P>
          <HD SOURCE="HD1">(b) Affected ADs</HD>
          <P>This AD revises AD 2004-21-08, Amendment 39-13828.</P>
          <HD SOURCE="HD1">(c) Applicability</HD>
          <P>This AD affects Models 190, 195 (L-126A,B,C), 195A, and 195B airplanes, all serial numbers, that are:</P>
          <P>(1) Certificated in any category; and</P>
          <P>(2) Equipped with at least one part number (P/N) 0322709 or P/N 0322709-1 inboard aileron hinge bracket.</P>
          <HD SOURCE="HD1">(d) Subject</HD>
          <P>Joint Aircraft System Component (JASC)/Air Transport Association (ATA) of America Code 2710, Aileron Control System.</P>
          <HD SOURCE="HD1">(e) Unsafe Condition</HD>
          <P>This AD was prompted by reports of confusion between the casting number on the aileron hinge bracket and the part number called out in the AD. We are issuing this AD to correct the unsafe condition on these products.</P>
          <HD SOURCE="HD1">(f) Compliance</HD>
          <P>Comply with this AD at the times specified following the procedures in Cessna Aircraft Company Single Engine Service Bulletin SEB04-01, Revision 1, dated October 3, 2012, unless already done.</P>
          <HD SOURCE="HD1">(g) Credit for Actions Accomplished in Accordance With Previous Service Information</HD>

          <P>This paragraph provides credit for the actions required by paragraphs (h), (i), and (j) of this AD, if the actions were performed before the effective date of this AD using Cessna Aircraft Company Single Engine Service Bulletin SEB04-1, dated April 26, 2004. All actions performed after the effective date of this AD will be required following Cessna Aircraft Company Single Engine Service Bulletin SEB04-01, Revision 1, dated October 3, 2012.<PRTPAGE P="1158"/>
          </P>
          <HD SOURCE="HD1">(h) Inspect Each P/N 0322709 and P/N 0322709-1 Inboard Aileron Hinge Bracket or Any Other Bracket Made From Magnesium for Cracks or Corrosion</HD>
          <P>Within the next 100 hours time-in-service (TIS) after November 30, 2004 (the effective date retained from AD 2004-21-08, Amendment 39-13828 (69 FR 62396, October 26, 2004)), and repetitively thereafter at intervals not to exceed 100 hours TIS until each bracket is replaced with aluminum, inspect each P/N 0322709 and P/N 0322709-1 inboard aileron hinge bracket or any other bracket made from magnesium for cracks or corrosion.</P>
          <HD SOURCE="HD1">(i) Replace Any Cracked or Corroded Inboard Aileron Hinge Bracket</HD>
          <P>Before further flight after any inspection where any cracked or corroded bracket is found, replace any cracked or corroded inboard aileron hinge.</P>
          <P>(1) If replacement is with an FAA-approved bracket made from magnesium, do the 100-hour TIS interval repetitive inspections as required in paragraph (h) of this AD.</P>
          <P>(2) If replacement is with an FAA-approved bracket that is made from aluminum, then no further inspections are necessary. These can be Cessna parts or non-Cessna parts.</P>
          <HD SOURCE="HD1">(j) Terminating Action for the Repetitive Inspections</HD>
          <P>(1) As terminating action for the repetitive inspections, you may replace all inboard aileron hinge brackets with FAA-approved brackets that are made from aluminum (as specified in paragraph (i)(2) of this AD) regardless if any corrosion or crack is found.</P>
          <P>(2) You may do this replacement at any time, but you must replace any corroded or cracked bracket before further flight after the applicable inspection where any corrosion or crack is found.</P>
          <HD SOURCE="HD1">(k) Alternative Methods of Compliance (AMOCs)</HD>
          <P>(1) The Manager, Wichita 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.</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>
          <P>(3) All AMOCs approved for AD 2004-21-08 (69 FR 62396, October 26, 2004) are approved for this AD.</P>
          <HD SOURCE="HD1">(l) Related Information</HD>

          <P>(1) For more information about this AD, contact Gary Park, Aerospace Engineer, Wichita ACO, FAA, 1801 Airport Road, Wichita, KS 67209; phone: (316) 946-4123; fax: (316) 946-4107; email:<E T="03">gary.park@faa.gov.</E>
          </P>

          <P>(2) For service information identified in this AD, contact Cessna Aircraft Company, Customer Service, P.O. Box 7706, Wichita, KS 67277; telephone: (316) 517-5800; fax: (316) 517-7271; email:<E T="03">customercare@cessna.textron.com</E>; Internet:<E T="03">http://www.cessnasupport.com.</E>You may review copies of the referenced service information at the FAA, Small Airplane Directorate, 901 Locust, Kansas City, MO 64106. For information on the availability of this material at the FAA, call (816) 329-4148.</P>
        </EXTRACT>
        
        <SIG>
          <DATED>Issued in Kansas City, Missouri, on December 31, 2012.</DATED>
          <NAME>Earl Lawrence,</NAME>
          <TITLE>Manager, Small Airplane Directorate, Aircraft Certification Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00069 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4910-13-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Food and Drug Administration</SUBAGY>
        <CFR>21 CFR Parts 868 and 870</CFR>
        <DEPDOC>[Docket No. FDA-2012-N-1174]</DEPDOC>
        <SUBJECT>Anesthesiology Devices; Reclassification of Membrane Lung for Long-Term Pulmonary Support; Redesignation as Extracorporeal Circuit and Accessories for Long-Term Pulmonary/Cardiac Support</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Food and Drug Administration, HHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed order.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>On its own initiative, based on new information, the Food and Drug Administration (FDA) is proposing to reclassify membrane lung devices for long-term pulmonary support, a preamendments class III device, into class II (special controls) for conditions where imminent death is threatened by cardiopulmonary failure in neonates and infants or where cardiopulmonary failure results in the inability to separate from cardiopulmonary bypass following cardiac surgery. A membrane lung for long-term pulmonary support refers to the oxygenator component of an extracorporeal circuit used during long-term procedures, commonly referred to as extracorporeal membrane oxygenation (ECMO). Because circuit components used with the oxygenator are to be subject to the same regulatory controls, all of the device components used in an ECMO procedure are being considered in the scope of this proposed order, and the title and identification of the regulation will be revised accordingly to include extracorporeal circuit and accessories for long-term pulmonary/cardiac support.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Submit either electronic or written comments on this proposed order by April 8, 2013. See section XI of this document for the proposed effective date of a final order based on this proposed order.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by Docket No. FDA-2012-N-1174, by any of the following methods:</P>
        </ADD>
        <HD SOURCE="HD1">Electronic Submissions</HD>
        <P>Submit electronic comments in the following way:</P>
        <P>•<E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
        <HD SOURCE="HD1">Written Submissions</HD>
        <P>Submit written submissions in the following way:</P>
        <P>•<E T="03">Mail/Hand delivery/Courier (for paper or CD-ROM submissions):</E>Division of Dockets Management (HFA-305), Food and Drug Administration, 5630 Fishers Lane, rm. 1061, Rockville, MD 20852.</P>
        <P>
          <E T="03">Instructions:</E>All submissions received must include the Agency name and Docket No. FDA-2012-N-1174 for this order. All comments received may be posted without change to<E T="03">http://www.regulations.gov</E>, including any personal information provided. For additional information on submitting comments, see the “Comments” heading of the<E T="02">SUPPLEMENTARY INFORMATION</E>section of this document.</P>
        <P>
          <E T="03">Docket:</E>For access to the docket to read background documents or comments received, go to<E T="03">http://www.regulations.gov</E>and insert the docket number, found in brackets in the heading of this document, into the “Search” box and follow the prompts and/or go to the Division of Dockets Management, 5630 Fishers Lane, rm. 1061, Rockville, MD 20852.</P>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Angela Krueger, Center for Devices and Radiological Health, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 66, rm. 1666, Silver Spring, MD 20993, 301-796-6380,<E T="03">angela.krueger@fda.hhs.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background—Regulatory Authorities</HD>

        <P>The FD&amp;C Act, as amended by the Medical Device Amendments of 1976 (the 1976 amendments) (Pub. L. 94-295), the Safe Medical Devices Act of 1990 (Pub. L. 101-629), the Food and Drug Administration Modernization Act of 1997 (FDAMA) (Pub. L. 105-115), the Medical Device User Fee and Modernization Act of 2002 (Pub. L. 107-250), the Medical Devices Technical Corrections Act of 2004 (Pub. L. 108-<PRTPAGE P="1159"/>214), the Food and Drug Administration Amendments Act of 2007 (Pub. L. 110-85), and Food and Drug Administration Safety and Innovation Act (FDASIA) (Pub. L. 112-144) established a comprehensive system for the regulation of medical devices intended for human use. Section 513 of the FD&amp;C Act (21 U.S.C. 360c) established three categories (classes) of devices, reflecting the regulatory controls needed to provide reasonable assurance of their safety and effectiveness. The three categories of devices are class I (general controls), class II (special controls), and class III (premarket approval).</P>
        <P>Under section 513 of the FD&amp;C Act, devices that were in commercial distribution before the enactment of the 1976 amendments, May 28, 1976 (generally referred to as preamendments devices), are classified after FDA has: (1) Received a recommendation from a device classification panel (an FDA advisory committee); (2) published the panel's recommendation for comment, along with a proposed regulation classifying the device; and (3) published a final regulation classifying the device. FDA has classified most preamendments devices under these procedures.</P>
        <P>Devices that were not in commercial distribution prior to May 28, 1976 (generally referred to as postamendments devices), are automatically classified by section 513(f) of the FD&amp;C Act into class III without any FDA process. Those devices remain in class III and require premarket approval unless, and until, the device is reclassified into class I or II or FDA issues an order finding the device to be substantially equivalent, in accordance with section 513(i) of the FD&amp;C Act, to a predicate device that does not require premarket approval. The Agency determines whether new devices are substantially equivalent to predicate devices by means of premarket notification procedures in section 510(k) of the FD&amp;C Act (21 U.S.C. 360(k)) and part 807 (21 CFR part 807).</P>
        <P>On July 9, 2012, FDASIA was enacted. Section 608(a) of FDASIA (126 Stat. 1056) amended section 513(e) of the FD&amp;C Act, changing the process for reclassifying a device from rulemaking to an administrative order.</P>

        <P>Section 513(e) of the FD&amp;C Act governs reclassification of preamendments devices. This section provides that FDA may, by administrative order, reclassify a device (in a proceeding that parallels the initial classification proceeding) based upon “new information.” FDA can initiate a reclassification under section 513(e) of the FD&amp;C Act or an interested person may petition FDA to reclassify a preamendments device. The term “new information,” as used in section 513(e) of the FD&amp;C Act, includes information developed as a result of a reevaluation of the data before the Agency when the device was originally classified, as well as information not presented, not available, or not developed at that time. (See, e.g.,<E T="03">Holland Rantos</E>v.<E T="03">United States Department of Health, Education, and Welfare,</E>587 F.2d 1173, 1174 n.1 (D.C. Cir. 1978);<E T="03">Upjohn</E>v.<E T="03">Finch,</E>422 F.2d 944 (6th Cir. 1970);<E T="03">Bell</E>v.<E T="03">Goddard,</E>366 F.2d 177 (7th Cir. 1966).)</P>

        <P>Reevaluation of the data previously before the Agency is an appropriate basis for subsequent regulatory action where the reevaluation is made in light of newly available regulatory authority (see<E T="03">Bell</E>v.<E T="03">Goddard,</E>supra, 366 F.2d at 181;<E T="03">Ethicon, Inc.</E>v.<E T="03">FDA,</E>762 F.Supp. 382, 389-391 (D.D.C. 1991)) or in light of changes in “medical science.” (See<E T="03">Upjohn</E>v.<E T="03">Finch,</E>supra, 422 F.2d at 951.) Whether data before the Agency are past or new data, the “new information” to support reclassification under section 513(e) must be “valid scientific evidence,” as defined in section 513(a)(3) of the FD&amp;C Act and 21 CFR 860.7(c)(2). (See, e.g.,<E T="03">General Medical Co.</E>v.<E T="03">FDA,</E>770 F.2d 214 (D.C. Cir. 1985);<E T="03">Contact Lens Assoc.</E>v.<E T="03">FDA,</E>766 F.2d 592 (D.C. Cir.), cert. denied, 474 U.S. 1062 (1985).)</P>
        <P>FDA relies upon “valid scientific evidence” in the classification process to determine the level of order for devices. To be considered in the reclassification process, the valid scientific evidence upon which the Agency relies must be publicly available. Publicly available information excludes trade secret and/or confidential commercial information, e.g., the contents of a pending premarket approval application (PMA). (See section 520(c) of the FD&amp;C Act (21 U.S.C. 360j(c)).) Section 520(h)(4) of the FD&amp;C Act, added by FDAMA, provides that FDA may use, for reclassification of a device, certain information in a PMA 6 years after the application has been approved. This includes information from clinical and preclinical tests or studies that demonstrate the safety or effectiveness of the device but does not include descriptions of methods of manufacture or product composition and other trade secrets.</P>

        <P>Section 513(e)(1) of the FD&amp;C Act sets forth the process for issuing a final order. Specifically, prior to the issuance of a final order reclassifying a device, the following must occur: (1) Publication of a proposed order in the<E T="04">Federal Register</E>; (2) a meeting of a device classification panel described in section 513(b) of the FD&amp;C Act; and (3) consideration of comments from all affected stakeholders, including patients, payors, and providers.</P>
        <P>FDAMA added section 510(m) to the FD&amp;C Act. Section 510(m) of the FD&amp;C Act provides that a class II device may be exempted from the premarket notification requirements under section 510(k) of the FD&amp;C Act, if the Agency determines that premarket notification is not necessary to assure the safety and effectiveness of the device.</P>
        <HD SOURCE="HD1">II. Regulatory History of the Device</HD>
        <P>On November 2, 1979 (44 FR 63387), FDA published a proposed rule for classification of membrane lungs for long-term pulmonary support as class III requiring premarket approval. The Anesthesiology Device Classification Panel recommended class III because the device is life sustaining and life supporting and sufficient information did not exist to determine the adequacy of general controls or to establish standards to provide a reasonable assurance of the safety and effectiveness of the device.</P>
        <P>No comments were received on the proposed rule and on July 16, 1982 (47 FR 31130), a final rule was published for membrane lungs for long-term pulmonary support, classifying these devices as class III. In 1987, FDA published a final rule amending the codified language for this device to clarify that no effective date had been established for the requirement for premarket approval for membrane lungs for long-term pulmonary support devices (52 FR 17732 at 17735; May 11, 1987). In 2009, FDA published an order under sections 515(i) and 519 of the FD&amp;C Act (21 U.S.C. 360e and 360i) for the submission of safety and effectiveness information on a membrane lung for long-term pulmonary support (74 FR 16214; April 9, 2009). In response to that order, FDA received information from one device manufacturer.</P>
        <HD SOURCE="HD1">III. Device Description</HD>

        <P>A membrane lung for long-term pulmonary support refers to the oxygenator component of an extracorporeal circuit used during long-term procedures, commonly referred to as an ECMO. An ECMO procedure provides assisted extracorporeal circulation and physiologic gas exchange of a patient's blood when an acute (reversible) condition prevents the patient's own body from providing the physiologic gas exchange needed to sustain life. The circuit is comprised of multiple device types, including, but<PRTPAGE P="1160"/>not limited to, an oxygenator, blood pump, cannulae, heat exchanger, tubing, filters, monitors/detectors, and other accessories; the circuit components and configuration (e.g., arteriovenous, veno-venous) may differ based on the needs of the individual patient or the condition being treated. ECMO is intended for patients with acute reversible respiratory or cardiac failure, unresponsive to optimal ventilation and/or pharmacologic management.</P>
        <P>Because circuit components used with the oxygenator can be appropriately regulated using the same set of regulatory controls, all of the device components used in an ECMO procedure are being considered in the scope of this proposed order as an extracorporeal circuit and accessories for long-term pulmonary/cardiac support.</P>
        <HD SOURCE="HD1">IV. Proposed Reclassification</HD>
        <P>FDA is proposing that the device subject to this proposed order be reclassified from class III to class II. FDA is further proposing to revise the title and identification of the regulation to reflect all device components used in ECMO. In addition, FDA is proposing to remove this regulation from 21 CFR part 868, Anesthesiology Devices, and add the revised version to 21 CFR part 870, Cardiovascular Devices, to better align this device type with other similar types of cardiovascular devices and align the review responsibilities for this device type. FDA believes that these devices can be utilized to provide assisted extracorporeal circulation and physiologic gas exchange of a patient's blood when an acute (reversible) condition prevents the patient's own body from providing the physiologic gas exchange needed to sustain life in conditions where imminent death is threatened by cardiopulmonary failure in neonates and infants or where cardiopulmonary failure results in the inability to separate from cardiopulmonary bypass following cardiac surgery.</P>

        <P>FDA believes that the identified special controls, in addition to general controls, are necessary to provide reasonable assurance of safety and effectiveness. Therefore, in accordance with sections 513(e) and 515(i) of the FD&amp;C Act and 21 CFR 860.130, based on new information with respect to the devices, FDA, on its own initiative, is proposing to reclassify this preamendments class III device into class II. The Agency has identified special controls under section 513(a) of the FD&amp;C Act that would provide reasonable assurance of their safety and effectiveness. The new information includes the history of use of the circuit components, publicly available safety and effectiveness information (as described in Section VII of this document) and the relatively low incidence of adverse events, as discussed in the recommendations for reclassification from the device industry (available in docket FDA-2009-M-0101 at<E T="03">http://www.regulations.gov</E>). FDA believes that this information is sufficient to demonstrate that the proposed special controls can effectively mitigate the risks to health identified in section V of this document and that these special controls, in addition to the general controls, will provide a reasonable assurance of safety and effectiveness for ECMO devices.</P>
        <P>FDA has considered membrane lung devices for long-term pulmonary support in accordance with the reserved criteria and decided that the device does require premarket notification. The Agency does not intend to exempt this proposed class II device from premarket notification (510(k)) submission as provided for under section 510(m) of the FD&amp;C Act.</P>
        <HD SOURCE="HD1">V. Risks to Health</HD>
        <P>After considering available information, including the recommendations of the advisory committee (panel) for the classification of these devices along with information submitted in response to the 515(i) order and any additional information that FDA has encountered, FDA has evaluated the risks to health associated with the use of extracorporeal circuits and accessories for long-term pulmonary/cardiac support and determined that the following risks to health are associated with its use:</P>
        <P>•<E T="03">Thrombocytopenia.</E>Blood platelets important to the clotting cascade may be damaged by use of the device, resulting in a tendency toward increased bleeding.</P>
        <P>•<E T="03">Hemolysis.</E>Red blood cells may be damaged by mechanical, material, or surface features of the extracorporeal circuit.</P>
        <P>•<E T="03">Thrombosis/thromboembolism.</E>Blood clots may form within the extracorporeal circuit due to inadequate blood flow.</P>
        <P>•<E T="03">Hemorrhage.</E>To keep blood from clotting in the extracorporeal circuit, anticoagulants are generally used and may cause increased bleeding during the procedure.</P>
        <P>•<E T="03">Hemodilution.</E>Dilution of the patient's blood may be caused by the priming of the ECMO circuit.</P>
        <P>•<E T="03">Inadequate gas exchange.</E>Mechanical failure of the circuit components may result in inadequate gas exchange.</P>
        <P>•<E T="03">Loss of mechanical integrity.</E>Weakness in the connections or construction of the circuit components could lead to leaks in the extracorporeal circuit.</P>
        <P>•<E T="03">Gas embolism.</E>Air may be introduced into the extracorporeal circuit and result in a gas embolism.</P>
        <P>•<E T="03">Adverse tissue reaction.</E>The patient-contacting materials of the device may cause an adverse immunological or allergic reaction in a patient if the materials are not biocompatible.</P>
        <P>•<E T="03">Infection.</E>Defects in the design or construction of the device preventing adequate cleaning and/or sterilization may allow pathogenic organisms to be introduced and may result in infection.</P>
        <P>•<E T="03">Mechanical injury to access vessels.</E>Mechanical injury to vessels may be caused acutely during access, or over time due to the long-term duration of use.</P>
        <HD SOURCE="HD1">VI. Summary of Reasons for Reclassification</HD>
        <P>FDA believes that extracorporeal circuits and accessories for long-term pulmonary/cardiac support should be reclassified into class II because special controls, in addition to general controls, can be established to provide reasonable assurance of the safety and effectiveness of the device. In addition, there is now adequate effectiveness information sufficient to establish special controls to provide such assurance for conditions where imminent death is threatened by cardiopulmonary failure in neonates and infants or where cardiopulmonary failure results in the inability to separate from cardiopulmonary bypass following cardiac surgery.</P>
        <P>FDA is proposing to rename this device to “Extracorporeal circuit and accessories for long-term pulmonary/cardiac support”; the current classification regulation for this device is referred to as “membrane lung for long-term pulmonary support.” For clarity, the new title for this proposed order will be removed from 21 CFR part 868 and redesignated to 21 CFR part 870. Section 870.4100 will be added to reflect all device components used in ECMO.</P>
        <HD SOURCE="HD1">VII. Summary of Data Upon Which the Reclassification Is Based</HD>

        <P>Since the time of the Panel recommendation, sufficient evidence has been developed to support a reclassification of extracorporeal circuits and accessories for long-term pulmonary/cardiac support to class II with special controls for conditions<PRTPAGE P="1161"/>where imminent death is threatened by cardiopulmonary failure in neonates and infants or where cardiopulmonary failure results in the inability to separate from cardiopulmonary bypass following cardiac surgery. FDA is familiar with the risks associated with the use of the components of the extracorporeal circuit because the same components are used for short-term use (durations less than 6 hours) for cardiopulmonary bypass. In addition, the Extracorporeal Life Support Organization registry data (Ref. 1), which provides information on over 28,000 ECMO procedures performed since 1987, and reviews of institutional experience (Ref. 2) demonstrate a favorable benefit-risk profile for extracorporeal circuits and accessories when used for conditions where imminent death is threatened by cardiopulmonary failure in neonates and infants or where cardiopulmonary failure results in the inability to separate from cardiopulmonary bypass following cardiac surgery.</P>
        <HD SOURCE="HD1">VIII. Proposed Special Controls</HD>
        <P>FDA believes that the following special controls, in addition to general controls, are sufficient to mitigate the risks to health described in section V of this document:</P>
        <P>• The design characteristics of the device must ensure that the geometry and design parameters are consistent with the intended use;</P>
        <P>• The device must be demonstrated to be biocompatible;</P>
        <P>• Sterility and shelf life testing must demonstrate the sterility of patient-contacting components and the shelf-life of these components;</P>
        <P>• Nonclinical performance evaluation of the device must demonstrate a reasonable assurance of safety and effectiveness for mechanical integrity, durability, and reliability;</P>
        <P>• In-vivo evaluation of the device must demonstrate device performance; and</P>
        <P>• Labeling must include a detailed summary of the nonclinical and clinical evaluations pertinent to use of the device and adequate instructions with respect to anticoagulation, circuit set up, and maintenance during a procedure.</P>
        <P>In addition, under 21 CFR 801.109, the sale, distribution, and use of this device are restricted to prescription use.</P>
        <HD SOURCE="HD1">IX. Environmental Impact</HD>
        <P>The Agency has determined under 21 CFR 25.34(b) that this action is of a type that does not individually or cumulatively have a significant effect on the human environment. Therefore, neither an environmental assessment nor an environmental impact statement is required.</P>
        <HD SOURCE="HD1">X. Paperwork Reduction Act of 1995</HD>
        <P>This proposed order refers to previously approved collections of information found in FDA regulations. These collections of information are subject to review by the Office of Management and Budget (OMB) under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520). The collections of information in 21 CFR part 812 are approved under OMB control number 0910-0078; the collections of information in part 807, subpart E, are approved under OMB control number 0910-0120; the collections of information in 21 CFR part 814, subpart B, are approved under OMB control number 0910-0231; and the collections of information under 21 CFR part 801 have are under OMB control number 0910-0485.</P>
        <HD SOURCE="HD1">XI. Proposed Effective Date</HD>

        <P>FDA is proposing that any final order based on this proposal become effective 30 days after date of publication of the final order in the<E T="04">Federal Register</E>.</P>
        <HD SOURCE="HD1">XII. Comments</HD>
        <P>Interested persons may submit either electronic comments to<E T="03">http://www.regulations.gov</E>or written comments regarding this document to the Division of Dockets Management (see<E T="02">ADDRESSES</E>). It is only necessary to send one set of comments. Identify comments with the docket number found in brackets in the heading of this document. Received comments may be seen in the Division of Dockets Management between 9 a.m. and 4 p.m., Monday through Friday, and will be posted to the docket at<E T="03">http://www.regulations.gov.</E>
        </P>
        <HD SOURCE="HD1">XIII. References</HD>

        <P>The following references have been placed on display in the Division of Dockets Management (see<E T="02">ADDRESSES</E>) and may be seen by interested persons between 9 a.m. and 4 p.m., Monday through Friday, and are available electronically at<E T="03">http://www.regulations.gov.</E>
        </P>
        
        <EXTRACT>

          <P>1. Fleming, G. M., J. G. Gurney, J. E. Donahue, et al., “Mechanical Component Failures in 28,171 Neonatal and Pediatric Extracorporeal Membrane Oxygenation Courses From 1987 to 2006,”<E T="03">Pediatric Critical Care Medicine Journal,</E>vol. 10, pp. 439-444, July 2009.</P>

          <P>2. Cook, L. N., “Update on Extracorporeal Membrane Oxygenation,”<E T="03">Paediatric Respiratory Reviews,</E>vol. 5, suppl. A, pp. S329-S337, 2004.</P>
        </EXTRACT>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 21 CFR Parts 868 and 870</HD>
          <P>Medical devices.</P>
        </LSTSUB>
        
        <P>Therefore, under the Federal Food, Drug, and Cosmetic Act and under authority delegated to the Commissioner of Food and Drugs, it is proposed that 21 CFR parts 868 and 870 be amended as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 868—ANESTHESIOLOGY DEVICES</HD>
        </PART>
        <AMDPAR>1. The authority citation for 21 CFR part 868 continues to read as follows:</AMDPAR>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>21 U.S.C. 351, 360, 360c, 360e, 360j, 371.</P>
        </AUTH>
        <SECTION>
          <SECTNO>§ 868.5610</SECTNO>
          <SUBJECT>[Removed]</SUBJECT>
        </SECTION>
        <AMDPAR>2. Remove § 868.5610.</AMDPAR>
        <PART>
          <HD SOURCE="HED">PART 870—CARDIOVASCULAR DEVICES</HD>
        </PART>
        <AMDPAR>3. The authority citation for 21 CFR part 870 continues to read as follows:</AMDPAR>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>21 U.S.C. 351, 360, 360c, 360e, 360j, 371.</P>
        </AUTH>
        
        <AMDPAR>4. Add § 870.4100 to subpart E to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 870.4100</SECTNO>
          <SUBJECT>Extracorporeal circuit and accessories for long-term pulmonary/cardiac support.</SUBJECT>
          <P>(a)<E T="03">Identification.</E>An extracorporeal circuit and accessories for long-term pulmonary/cardiac support (&gt;6 hours) is a system of devices that provides assisted extracorporeal circulation and physiologic gas exchange of the patient's blood in conditions where imminent death is threatened by cardiopulmonary failure in neonates and infants or where cardiopulmonary failure results in the inability to separate from cardiopulmonary bypass following cardiac surgery. An acute reversible or treatable cause of respiratory and/or cardiac failure should be evident, and the subject should demonstrate unresponsiveness to maximum medical or ventilation therapy. The main components of the system include the console (hardware), software, and disposables, including but not limited to, an oxygenator, blood pump, heat exchanger, cannulae, tubing, filters, and other accessories (e.g., monitors, detectors, sensors, connectors).</P>
          <P>(b)<E T="03">Class II (special controls).</E>The special controls for this device are:</P>
          <P>(1) The design characteristics of the device must ensure that the geometry and design parameters are consistent with the intended use;</P>
          <P>(2) The device must be demonstrated to be biocompatible;</P>

          <P>(3) Sterility and shelf life testing must demonstrate the sterility of patient-<PRTPAGE P="1162"/>contacting components and the shelf-life of these components;</P>
          <P>(4) Non-clinical performance evaluation of the device must provide a reasonable assurance of safety and effectiveness for mechanical integrity, durability, and reliability;</P>
          <P>(5) In-vivo evaluation of the device must demonstrate device performance; and</P>
          <P>(6) Labeling must include a detailed summary of the nonclinical and clinical evaluations pertinent to use of the device and adequate instructions with respect to anticoagulation, circuit set up, and maintenance during a procedure.</P>
        </SECTION>
        <SIG>
          <DATED>Dated: January 2, 2013.</DATED>
          <NAME>Leslie Kux,</NAME>
          <TITLE>Assistant Commissioner for Policy.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00086 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4160-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Food and Drug Administration</SUBAGY>
        <CFR>21 CFR Part 870</CFR>
        <DEPDOC>[Docket No. FDA-2012-N-1173]</DEPDOC>
        <SUBJECT>Cardiovascular Devices; Reclassification of External Cardiac Compressor</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Food and Drug Administration, HHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed order.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Food and Drug Administration (FDA) is proposing to reclassify the external cardiac compressor, including cardiopulmonary resuscitation (CPR) aids, from class III devices into class II (special controls). FDA is proposing this reclassification on its own initiative based on new information. FDA is taking this action under the Federal Food, Drug, and Cosmetic Act (the FD&amp;C Act), as amended.</P>
        </SUM>
        <EFFDATE>
          <HD SOURCE="HED">DATES:</HD>
          <P>Submit either electronic or written comments on this proposed order by April 8, 2013. See section XII of this document for the proposed effective date of a final order based on this proposed order.</P>
        </EFFDATE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by Docket No. FDA-2012-N-1173, by any of the following methods:</P>
        </ADD>
        <HD SOURCE="HD1">Electronic Submissions</HD>
        <P>Submit electronic comments in the following way:</P>
        <P>•<E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
        <HD SOURCE="HD1">Written Submissions</HD>
        <P>Submit written submissions in the following way:</P>
        <P>•<E T="03">Mail/Hand delivery/Courier (for paper or CD-ROM submissions):</E>Division of Dockets Management (HFA-305), Food and Drug Administration, 5630 Fishers Lane, rm. 1061, Rockville, MD 20852.</P>
        <P>
          <E T="03">Instructions:</E>All submissions received must include the Agency name and Docket No. FDA-2012-N-1173 for this order. All comments received may be posted without change to<E T="03">http://www.regulations.gov</E>, including any personal information provided. For additional information on submitting comments, see the “Comments” heading of the<E T="02">SUPPLEMENTARY INFORMATION</E>section of this document.</P>
        <P>
          <E T="03">Docket:</E>For access to the docket to read background documents or comments received, go to<E T="03">http://www.regulations.gov</E>and insert the docket number, found in brackets in the heading of this document, into the “Search” box and follow the prompts and/or go to the Division of Dockets Management, 5630 Fishers Lane, rm. 1061, Rockville, MD 20852.</P>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Melissa Burns, Center for Devices and Radiological Health, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 66, rm. 1646, Silver Spring, MD 20993, 301-796-5616,<E T="03">melissa.burns@fda.hhs.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Background—Regulatory Authorities</HD>
        <P>The FD&amp;C Act, as amended by the Medical Device Amendments of 1976 (the 1976 amendments) (Pub. L. 94-295), the Safe Medical Devices Act of 1990 (Pub. L. 101-629), the Food and Drug Administration Modernization Act of 1997 (FDAMA) (Pub. L. 105-115), the Medical Device User Fee and Modernization Act of 2002 (Pub. L. 107-250), the Medical Devices Technical Corrections Act of 2004 (Pub. L. 108-214), the Food and Drug Administration Amendments Act of 2007 (Pub. L. 110-85), and the Food and Drug Administration Safety and Innovation Act (FDASIA) (Pub. L. 112-144), established a comprehensive system for the regulation of medical devices intended for human use. Section 513 of the FD&amp;C Act (21 U.S.C. 360c) established three categories (classes) of devices, reflecting the regulatory controls needed to provide reasonable assurance of their safety and effectiveness. The three categories of devices are class I (general controls), class II (special controls), and class III (premarket approval).</P>
        <P>Under section 513 of the FD&amp;C Act, devices that were in commercial distribution before the enactment of the 1976 amendments, May 28, 1976 (generally referred to as preamendments devices), are classified after FDA has: (1) Received a recommendation from a device classification panel (an FDA advisory committee); (2) published the panel's recommendation for comment, along with a proposed regulation classifying the device; and (3) published a final regulation classifying the device. FDA has classified most preamendments devices under these procedures.</P>
        <P>Devices that were not in commercial distribution prior to May 28, 1976 (generally referred to as postamendments devices), are automatically classified by section 513(f) of the FD&amp;C Act into class III without any FDA process. Those devices remain in class III and require premarket approval unless, and until, the device is reclassified into class I or II or FDA issues an order finding the device to be substantially equivalent, in accordance with section 513(i) of the FD&amp;C Act, to a predicate device that does not require premarket approval. The Agency determines whether new devices are substantially equivalent to predicate devices by means of premarket notification procedures in section 510(k) of the FD&amp;C Act (21 U.S.C. 360(k)) and part 807 (21 CFR part 807).</P>
        <P>On July 9, 2012, FDASIA was enacted. Section 608(a) of FDASIA (126 Stat. 1056) amended section 513(e) of the FD&amp;C Act, changing the process for reclassifying a device from rulemaking to an administrative order.</P>

        <P>Section 513(e) of the FD&amp;C Act governs reclassification of preamendments devices. This section provides that FDA may, by administrative order, reclassify a device (in a proceeding that parallels the initial classification proceeding) based upon “new information.” FDA can initiate a reclassification under section 513(e) of the FD&amp;C Act or an interested person may petition FDA to reclassify a preamendments device. The term “new information,” as used in section 513(e) of the FD&amp;C Act, includes information developed as a result of a reevaluation of the data before the Agency when the device was originally classified, as well as information not presented, not available, or not developed at that time. (See, e.g.,<E T="03">Holland Rantos</E>v.<E T="03">United States Department of Health, Education, and Welfare,</E>587 F.2d 1173, 1174 n.1 (DC Cir. 1978);<E T="03">Upjohn</E>v.<E T="03">Finch,</E>422 F.2d 944 (6th Cir. 1970);<E T="03">Bell</E>v.<E T="03">Goddard,</E>366 F.2d 177 (7th Cir. 1966).)<PRTPAGE P="1163"/>
        </P>

        <P>Reevaluation of the data previously before the Agency is an appropriate basis for subsequent regulatory action where the reevaluation is made in light of newly available regulatory authority (see<E T="03">Bell</E>v.<E T="03">Goddard,</E>supra, 366 F.2d at 181;<E T="03">Ethicon, Inc.</E>v.<E T="03">FDA,</E>762 F.Supp. 382, 389-391 (D.D.C. 1991)) or in light of changes in “medical science.” (See<E T="03">Upjohn</E>v.<E T="03">Finch,</E>supra, 422 F.2d at 951.) Whether data before the Agency are past or new data, the “new information” to support reclassification under section 513(e) must be “valid scientific evidence,” as defined in section 513(a)(3) of the FD&amp;C Act and 21 CFR 860.7(c)(2). (See, e.g.,<E T="03">General Medical Co.</E>v.<E T="03">FDA,</E>770 F.2d 214 (DC Cir. 1985);<E T="03">Contact Lens Assoc.</E>v.<E T="03">FDA,</E>766 F.2d 592 (DC Cir.), cert. denied, 474 U.S. 1062 (1985).)</P>
        <P>FDA relies upon “valid scientific evidence” in the classification process to determine the level of regulation for devices. To be considered in the reclassification process, the valid scientific evidence upon which the Agency relies must be publicly available. Publicly available information excludes trade secret and/or confidential commercial information, e.g., the contents of a pending premarket approval application (PMA). (See section 520(c) of the FD&amp;C Act (21 U.S.C. 360j(c)).) Section 520(h)(4) of the FD&amp;C Act, added by FDAMA, provides that FDA may use, for reclassification of a device, certain information in a PMA 6 years after the application has been approved. This includes information from clinical and preclinical tests or studies that demonstrate the safety or effectiveness of the device, but does not include descriptions of methods of manufacture or product composition and other trade secrets.</P>

        <P>Section 513(e)(1) of the FD&amp;C Act sets forth the process for issuing a final order. Specifically, prior to the issuance of a final order reclassifying a device, the following must occur: (1) Publication of a proposed order in the<E T="04">Federal Register</E>; (2) a meeting of a device classification panel described in section 513(b) of the FD&amp;C Act; and (3) consideration of comments from all affected stakeholders, including patients, payors, and providers.</P>
        <P>FDAMA added section 510(m) to the FD&amp;C Act. Section 510(m) of the FD&amp;C Act provides that a class II device may be exempted from the premarket notification requirements under section 510(k) of the FD&amp;C Act, if the Agency determines that premarket notification is not necessary to assure the safety and effectiveness of the device.</P>
        <HD SOURCE="HD1">II. Regulatory History of the Device</HD>
        <P>On March 9, 1979 (44 FR 13424), FDA published a proposed rule for classification of external cardiac compressors as class III requiring premarket approval. The Cardiovascular Device Classification Panel and the Anesthesiology Device Classification Panel recommended class III because the device is life supporting and is potentially hazardous to life or health even when properly used, and the Panel believed that there was not sufficient information to develop a performance standard to provide a reasonable assurance of safety and effectiveness. No comments were received on the proposed rule and on February 5, 1980 (45 FR 7966), a final rule was published for external cardiac compressors, classifying these devices as class III. In 1987, FDA published a final rule amending the codified language for this device to clarify that no effective date had been established for the requirement for premarket approval for external cardiac compressor devices (52 FR 17732 at 17737; May 11, 1987). In 2009, FDA published an order under sections 515(i) and 519 of the FD&amp;C Act (21 U.S.C. 360e and 360i) for the submission of safety and effectivness information on external cardiac compressors (74 FR 16214; April 9, 2009). In response to that order, FDA received information from four manufacturers of external cardiac compressor devices.</P>
        <HD SOURCE="HD1">III. Device Description</HD>
        <P>External cardiac compressors (ECCs), also known as chest compressors, assist in the act of CPR. The devices in this classification are divided into two types: (1) Devices that provide automatic chest compressions at a fixed compression rate and depth (automated external cardiac compressors), which are placed directly on the patient's chest and are powered manually, pneumatically, or electrically and (2) devices that aid the emergency medical professional in delivering manual compressions at a compression depth and rate that are consistent with current guidelines (CPR Aids). These devices are placed beneath the hands of the emergency medical professional or in the vicinity of the cardiac arrest victim and provide audio and/or visual feedback to assist emergency personnel in following the recommended steps for CPR and maintaining the recommended rate and depth of compressions for the duration of CPR.</P>
        <HD SOURCE="HD1">IV. Proposed Reclassification</HD>
        <P>FDA is proposing that the device subject to this proposed order be reclassified from class III to class II. FDA believes CPR Aid devices and automated external cardiac compressor devices when used as indicated can supplement the effective delivery of CPR.</P>
        <P>FDA believes that the identified special controls, in addition to general controls, would provide reasonable assurance of safety and effectiveness. Therefore, in accordance with sections 513(e) and 515(i) of the FD&amp;C Act and 21 CFR 860.130, based on new information with respect to the devices, FDA, on its own initiative, is proposing to reclassify this preamendments class III device into class II. FDA believes that this information is sufficient to demonstrate that the proposed special controls can effectively mitigate the risks to health identified in section V of this document, and that these special controls in addition to the general controls will provide a reasonable assurance of safety and effectiveness for ECCs.</P>
        <P>FDA has considered automated external cardiac compressor devices in accordance with the reserved criteria and has determined that the device should be subject to the premarket notification (510(k) of the FD&amp;C Act) requirements as provided for under section 510(m) of the FD&amp;C Act. However, the Agency does intend to exempt a CPR Aid device when it is a prescription use device and when the feedback provided to the rescuer is consistent with the current version of the American Heart Association (AHA) guidelines for CPR (Ref. 1) from premarket notification (section 510(k) of the FD&amp;C Act) submission as provided for under section 510(m) of the FD&amp;C Act. The AHA guidelines recommend that chest compressions be the highest priority and the initial action when starting CPR in the adult victim of sudden cardiac arrest. Chest compressions are an especially critical component of CPR because perfusion during CPR depends on these compressions.</P>
        <HD SOURCE="HD1">V. Risks to Health</HD>

        <P>After considering available information, including the recommendations of the advisory committees (panels) for the classification of these devices, FDA has evaluated the risks to health associated with the use of external cardiac compressor devices and determined that the following risks to health are<PRTPAGE P="1164"/>associated with use of the automated external cardiac compressor devices:</P>
        <P>•<E T="03">Tissue damage or bone breakage, or inadequate blood flow.</E>Damage to the heart, other organs or tissues, can result from poor mechanical design, improper surface area of the plunger, improper vertical excursion of the plunger, improper force applied by the plunger, or improper energy transmission by the device.</P>
        <P>•<E T="03">Cardiac arrhythmias or electrical shock.</E>Excessive electrical leakage current can disturb the normal electrophysiology of the heart, leading to the onset of cardiac arrhythmias.</P>
        <P>•<E T="03">Adverse skin reactions.</E>Lack of biocompatibility in materials contacting skin may cause an adverse immunological or allergic reaction in a patient.</P>
        <P>FDA has evaluated the risks to health associated with the use of CPR Aid devices and determined that the following risks to health are associated with use of CPR Aid devices:</P>
        <P>•<E T="03">Suboptimal CPR delivery.</E>Inaccurate rate or depth feedback from the device or inadequate labeling may result in suboptimal delivery of CPR.</P>
        <P>•<E T="03">Adverse skin reactions.</E>Lack of biocompatibility in materials contacting skin may cause an adverse immunological or allergic reaction in a patient.</P>
        <HD SOURCE="HD1">VI. Summary of Reasons for Reclassification</HD>
        <P>FDA believes that automated external cardiac compressor devices indicated for adjunctive use with manual CPR (e.g., during transport—to assure more consistent and continuous therapy; or prolonged CPR—to avoid/replace rescuer fatigue) and CPR Aid devices should be reclassified into class II because special controls, in addition to general controls, can be established to provide reasonable assurance of the safety and effectiveness of the device. In addition, there is now adequate effectiveness information sufficient to establish special controls to provide such assurance.</P>
        <HD SOURCE="HD1">VII. Summary of Data Upon Which the Reclassification Is Based</HD>
        <P>Since the time of the Panel recommendation, sufficient evidence has been developed to support a reclassification of automated external cardiac compressors indicated for adjunctive use with manual CPR and CPR Aid devices into class II with special controls.</P>
        <P>Automated external cardiac compressors are tools used by emergency medical personnel to automate chest compressions during CPR. These devices are typically used in situations where extended CPR is required, such as during patient transport or when there are an inadequate number of trained personnel during extended CPR. The review of the available literature on mechanical versus manual chest compressions both by AHA (Ref. 1) and in a recent systematic literature review (Ref. 2) provided mixed results on whether mechanical compressions are as effective as manual chest compressions. However, it is well established that chest compressions are crucial to maintaining perfusion and that compressions of adequate rate and depth are necessary to increase the probability of survival in victims of sudden cardiac arrest (Ref. 1). As such, FDA believes that these devices, when indicated for use as an adjunct to manual CPR during patient transport or for use in situations where fatigue of or inaccessibility to emergency medical personnel may otherwise prevent adequate chest compressions, can be regulated as class II devices. These devices should not be used as a replacement for manual CPR. FDA believes that the special controls, including adequate labeling of the device for the appropriate use population, use conditions, and use by appropriately trained personnel, and performance testing of the device to ensure adequate chest compression rate and depth, adequately mitigate the risks.</P>
        <P>CPR Aid devices are used to remind emergency medical personnel of appropriate CPR steps and technique and to provide feedback on the rate and depth of compressions. AHA guidelines on CPR and emergency cardiovascular care (Ref. 1) conclude that “real-time CPR prompting and feedback technology such as visual and auditory prompting devices can improve the quality of CPR.” In addition, these devices have been reviewed by FDA for many years, and their risks are well-known. Between January 2000 and June 2012, FDA has not received any adverse event reports (medical device reports) associated with CPR Aid devices. FDA believes that the identified special controls, in addition to the general controls, provide reasonable assurance of safety and effectiveness.</P>
        <HD SOURCE="HD1">VIII. Proposed Special Controls</HD>
        <P>FDA believes that the following special controls, in addition to general controls, are sufficient to mitigate the risks to health described in section V of this document for automated external cardiac compressor devices:</P>
        <P>• Performance testing under simulated physiological conditions must demonstrate the reliability of the delivery of specific compression depth and rate over the intended duration and environment of use;</P>
        <P>• Labeling must include the clinical training for the safe use of this device and information on the patient population for which the device has been demonstrated to be effective;</P>
        <P>• For devices that incorporate electrical components, appropriate analysis and testing must validate electrical safety and electromagnetic compatibility;</P>
        <P>• For devices containing software, software verification, validation, and hazard analysis must be performed; and</P>
        <P>• Any elements of the device that may contact the patient must be demonstrated to be biocompatible;</P>
        <P>In addition, under 21 CFR 801.109, the sale, distribution, and use of the automated external cardiac compressor device are restricted to prescription use.</P>
        <P>FDA believes that the following special controls, in addition to general controls, are sufficient to mitigate the risks to health described in section V of this document for CPR Aid devices:</P>
        <P>• Performance testing under simulated physiological or use conditions must demonstrate the accuracy and reliability of the feedback to the user on specific compression rate and/or depth over the intended duration of use;</P>
        <P>• Labeling must include the clinical training, if needed, for the safe use of this device and information on the patient population for which the device has been demonstrated to be effective;</P>
        <P>• For devices that incorporate electrical components, appropriate analysis and testing must validate electrical safety and electromagnetic compatibility;</P>
        <P>• For devices containing software, software verification, validation, and hazard analysis must be performed;</P>
        <P>• Any elements of the device that may contact the patient must be demonstrated to be biocompatible; and</P>
        <P>• For over-the counter-devices, human factors testing and analysis must validate that the device design and labeling are sufficient for lay use.</P>
        <HD SOURCE="HD1">IX. Exemption From Premarket Notification Requirements</HD>

        <P>FDA, on its own initiative, is also proposing to exempt CPR Aid devices that provide feedback consistent with the current AHA guidelines for CPR from premarket notification, subject to limitations. The AHA guidelines are intended to support emergency medical personnel with a series of sequential assessments and actions for resuscitation of the victim. The intent of<PRTPAGE P="1165"/>the AHA guideline is to provide recommendations on the most effective CPR practices, rather than specific instructions for using CPR Aid or other devices on a victim of sudden cardiac arrest.</P>
        <P>FDA may consider a number of factors in determining whether premarket notification is necessary to provide reasonable assurance of the safety and effectiveness of a class II device. These factors are discussed in the guidance the Agency issued on February 19, 1998, entitled “Procedures for Class II Device Exemptions From Premarket Notification, Guidance for Industry and CDRH Staff ” (Ref. 3).</P>
        <P>FDA believes that a CPR Aid, when it is a prescription use device that provides feedback compliant with the current AHA guidelines for CPR, is appropriate for exemption from premarket notification, subject to the limitations of exemptions identified in 21 CFR 870.9, because the applicable special controls and general controls provide reasonable assurance of safety and effectiveness if device manufacturers follow the special controls requirements.</P>
        <P>FDA advises that exemption from the requirement of premarket notification for prescription CPR Aids does not mean that these devices would be exempt from any other statutory or regulatory requirements, unless such exemption is explicitly provided by order or regulation. Indeed, FDA's proposal to exempt these devices from the requirement of premarket notification is based, in part, on the assurance of safety and effectiveness that other regulatory controls, such as current good manufacturing practice requirements (21 CFR part 820) and the identified special controls, provide.</P>
        <HD SOURCE="HD1">X. Environmental Impact</HD>
        <P>The Agency has determined under 21 CFR 25.34(b) that this action is of a type that does not individually or cumulatively have a significant effect on the human environment. Therefore, neither an environmental assessment nor an environmental impact statement is required.</P>
        <HD SOURCE="HD1">XI. Paperwork Reduction Act of 1995</HD>
        <P>This proposed order refers to previously approved collections of information found in FDA regulations. These collections of information are subject to review by the Office of Management and Budget (OMB) under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520). The collections of information in 21 CFR part 812 are approved under OMB control number 0910-0078; the collections of information in part 807, subpart E, are approved under OMB control number 0910-0120; the collections of information in 21 CFR part 814, subpart B, are approved under OMB control number 0910-0231; and the collections of information under 21 CFR part 801 are approved under OMB control number 0910-0485.</P>
        <HD SOURCE="HD1">XII. Proposed Effective Date</HD>

        <P>FDA is proposing that any final order based on this proposal become effective 30 days after date of publication of the final order in the<E T="04">Federal Register</E>.</P>
        <HD SOURCE="HD1">XIII. Comments</HD>

        <P>Interested persons may submit either electronic comments regarding this document to<E T="03">http://www.regulations.gov</E>or written comments to the Division of Dockets Management (see<E T="02">ADDRESSES</E>). It is only necessary to send one set of comments. Identify comments with the docket number found in brackets in the heading of this document. Received comments may be seen in the Division of Dockets Management between 9 a.m. and 4 p.m., Monday through Friday, and will be posted to the docket at<E T="03">http://www.regulations.gov.</E>
        </P>
        <HD SOURCE="HD1">XIV. References</HD>

        <P>The following references have been placed on display in the Division of Dockets Management (see<E T="02">ADDRESSES</E>), and may be seen by interested persons between 9 a.m. and 4 p.m., Monday through Friday, and are available electronically at<E T="03">http://www.regulations.gov.</E>(FDA has verified all the Web site addresses in this reference section, but we are not responsible for any subsequent changes to the Web sites after this document publishes in the<E T="04">Federal Register</E>.)</P>
        
        <EXTRACT>
          <P>1. Berg R. A., R. Hemphill, B. S. Abella,<E T="03">et al.</E>, “2010 American Heart Association Guidelines for Cardiopulmonary Resuscitation and Emergency Cardiovascular Care Circulation,” vol. 122, issue 18, suppl. 3, 2010, available at<E T="03">http://circ.ahajournals.org/content/122/18_suppl_3/S685.full.pdf+html.</E>
          </P>

          <P>2. Brooks S. C., B. L. Bigham, and L. J. Morrison, “Mechanical Versus Manual Chest Compressions for Cardiac Arrest (Review),”<E T="03">The Cochrane Library,</E>issue 1, 2011, available at<E T="03">http://onlinelibrary.wiley.com/doi/10.1002/14651858.CD007260.pub2/pdf.</E>
          </P>

          <P>3. FDA guidance, “Procedures for Class II Device Exemptions From Premarket Notification, Guidance for Industry and CDRH Staff,” 1998, available at<E T="03">http://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/GuidanceDocuments/ucm080198.htm.</E>
          </P>
        </EXTRACT>
        
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 21 CFR Part 870</HD>
          <P>Medical devices.</P>
        </LSTSUB>
        
        <P>Therefore, under the Federal Food, Drug, and Cosmetic Act and under authority delegated to the Commissioner of Food and Drugs, it is proposed that 21 CFR part 870 be amended as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 870—CARDIOVASCULAR DEVICES</HD>
        </PART>
        <AMDPAR>1. The authority citation for 21 CFR part 870 continues to read as follows:</AMDPAR>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>21 U.S.C. 351, 360, 360c, 360e, 360j, 371.</P>
        </AUTH>
        
        <AMDPAR>2. Section 870.5200 is revised to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 870.5200</SECTNO>
          <SUBJECT>External cardiac compressor.</SUBJECT>
          <P>(a)<E T="03">Identification.</E>An automated external cardiac compressor is an external device that is electrically, pneumatically, or manually powered and is used to compress the chest periodically in the region of the heart to provide blood flow during cardiac arrest. Automated external cardiac compressor devices are used as an adjunct to manual cardiopulmonary resuscitation (CPR) during patient transport or extended CPR. This also includes CPR Aid devices, which are external devices intended to provide audio and/or visual feedback to the rescuer regarding compression rate and/or depth, to aid in the consistent application of manual CPR.</P>
          <P>(b)<E T="03">Classification.</E>(1) Class II (special controls) for the automated external cardiac compressor device. The special controls for this device are:</P>
          <P>(i) Performance testing under simulated physiological conditions must demonstrate the reliability of the delivery of specific compression depth and rate over the intended duration of use;</P>
          <P>(ii) Labeling must include the clinical training for the safe use of this device and information on the patient population for which the device has been demonstrated to be effective;</P>
          <P>(iii) For devices that incorporate electrical components, appropriate analysis and testing must validate electrical safety and electromagnetic compatibility;</P>
          <P>(iv) For devices containing software, software verification, validation, and hazard analysis must be performed; and</P>
          <P>(v) Any elements of the device that may contact the patient must be demonstrated to be biocompatible.</P>
          <P>(2) Class II (special controls) for the CPR Aid device. The special controls for this device are:</P>

          <P>(i) Performance testing under simulated physiological conditions must demonstrate the accuracy and reliability of the feedback to the user on specific compression rate and/or depth<PRTPAGE P="1166"/>over the intended duration and environment of use;</P>
          <P>(ii) Labeling must include the clinical training, if needed, for the safe use of this device and information on the patient population for which the device has been demonstrated to be effective;</P>
          <P>(iii) For devices that incorporate electrical components, appropriate analysis and testing must validate electrical safety and electromagnetic compatibility;</P>
          <P>(iv) For devices containing software, software verification, validation, and hazard analysis must be performed;</P>
          <P>(v) Any elements of the device that may contact the patient device must be demonstrated to be biocompatible; and</P>
          <P>(vi) For over-the-counter devices, human factors testing and analysis must validate that the device design and labeling are sufficient for lay use.</P>
          <P>(c)<E T="03">Premarket notification.</E>The CPR aid device is exempt from the premarket notification procedures in subpart E of part 807 of this chapter if it is a prescription use device that provides feedback to the rescuer consistent with the current American Heart Association guidelines for CPR and in compliance with the special controls under paragraph (b)(2) of this section, subject to the limitations of exemptions in § 870.9.</P>
        </SECTION>
        <SIG>
          <DATED>Dated: January 2, 2013.</DATED>
          <NAME>Leslie Kux,</NAME>
          <TITLE>Assistant Commissioner for Policy.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00085 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4160-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">ARCHITECTURAL AND TRANSPORTATION BARRIERS COMPLIANCE BOARD</AGENCY>
        <CFR>36 CFR Part 1195</CFR>
        <DEPDOC>[Docket No. ATBCB-2012-0003]</DEPDOC>
        <RIN>RIN 3014-AA40</RIN>
        <SUBJECT>Medical Diagnostic Equipment Accessibility Standards Advisory Committee</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Architectural and Transportation Barriers Compliance Board.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of advisory committee meeting.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Medical Diagnostic Equipment Accessibility Standards Advisory Committee will hold its third meeting. On July 5, 2012, the Architectural and Transportation Barriers Compliance Board (Access Board) established the advisory committee to make recommendations to the Board on matters associated with comments received and responses to questions included in a previously published Notice of Proposed Rulemaking (NPRM) on Medical Diagnostic Equipment Accessibility Standards.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The Committee will meet on January 22, 2013, from 10:00 a.m. to 5:00 p.m. and on January 23, 2012, from 9:00 a.m. to 2:30 p.m.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>The meeting will be held at the Access Board's Conference Room, 1331 F Street NW., Suite 800, Washington, DC 20004-1111.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Rex Pace, Office of Technical and Information Services, Architectural and Transportation Barriers Compliance Board, 1331 F Street NW., Suite 1000, Washington, DC 20004-1111. Telephone number (202) 272-0023 (Voice); (202) 272-0052 (TTY). Electronic mail address:<E T="03">pace@access-board.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>On July 5, 2012, the Architectural and Transportation Barriers Compliance Board (Access Board) established an advisory committee to make recommendations to the Board on matters associated with comments received and responses to questions included in a previously published NPRM on Medical Diagnostic Equipment Accessibility Standards. See 77 FR 6916 (February 9, 2012). The NPRM and information related to the proposed standards are available on the Access Board's Web site at:<E T="03">http://www.access-board.gov/medical-equipment.htm.</E>
        </P>
        <P>The advisory committee will hold its third meeting on January 22 and 23, 2013. The agenda includes the following:</P>
        <P>• Review of previous committee work;</P>
        <P>•  Presentations by medical practitioners and clinicians on the use of medical diagnostic equipment in relation to transfer surfaces;</P>
        <P>• Continued discussion on subcommittees based on medical diagnostic equipment type;</P>
        <P>• Continued discussion on transfer surface height and size;</P>
        <P>• Review and discussion on transfer support location and configuration;</P>
        <P>• Consideration of issues proposed by committee members; and</P>
        <P>• Discussion of administrative issues.</P>

        <P>The preliminary meeting agenda, along with information about the committee, is available at the Access Board's Web site (<E T="03">http://www.access-board.gov/medical-equipment.htm</E>).</P>
        <P>Committee meetings are open to the public and interested persons can attend the meetings and communicate their views. Members of the public will have opportunities to address the committee on issues of interest to them during public comment periods scheduled on each day of the meeting.</P>

        <P>The meetings will be accessible to persons with disabilities. An assistive listening system, computer assisted real-time transcription (CART), and sign language interpreters will be provided. Persons attending the meetings are requested to refrain from using perfume, cologne, and other fragrances for the comfort of other participants (<E T="03">see www.access-board.gov/about/policies/fragrance.htm</E>for more information). Also, persons wishing to provide handouts or other written information to the committee are requested to provide electronic formats to Rex Pace via email prior to the meetings so that alternate formats can be distributed to committee members.</P>
        <SIG>
          <NAME>David M. Capozzi,</NAME>
          <TITLE>Executive Director.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00071 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 8150-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
        <CFR>47 CFR Parts 1 and 27</CFR>
        <DEPDOC>[WT Docket No. 12-357; FCC 12-152]</DEPDOC>
        <SUBJECT>Service Rules for the Advanced Wireless Services in the H Block—Implementing Section 6401 of the Middle Class Tax Relief and Job Creation Act of 2012 Related to the 1915-1920 MHz and 1995-2000 MHz Bands</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Communications Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of proposed rulemaking.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In this document, the Commission proposes rules for the Advanced Wireless Services (AWS) H Block that would make available ten megahertz of spectrum for flexible use. The proposal would extend the widely-deployed Personal Communications Services (PCS) band, which is used by the four national providers as well as regional and rural providers to offer mobile service across the nation. The additional spectrum for mobile use will help ensure that the speed, capacity, and ubiquity of the nation's wireless networks keeps pace with the skyrocketing demand for mobile service.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>

          <P>Submit comments on or before February 6, 2013. Submit reply<PRTPAGE P="1167"/>comments on or before March 6, 2013. Written comments on the proposed information collection requirements, subject to the Paperwork Reduction Act (PRA) of 1995, Public Law 104-13, should be submitted on or before March 11, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Federal Communications Commission, 445 12th Street SW., Washington, DC 20554. 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, Office of Management and Budget, via email to<E T="03">Nicholas_A._Fraser@omb.eop.gov</E>or via fax at 202-395-5167. You may submit comments, identified by FCC 12-152, or by WT Docket No. 12-357, by any of the following methods:<E T="03">Federal eRulemaking Portal: http://www.regulations.gov.</E>Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Federal Communications Commission's Web Site: http://www.fcc.gov/cgb/ecfs/.</E>Follow the instructions for submitting comments.</P>
          <P>•<E T="03">People with Disabilities:</E>Contact the FCC to request reasonable accommodations (accessible format documents, sign language interpreters, CART, etc.) by email:<E T="03">FCC504@fcc.gov</E>or phone: (202) 418-0530 or TTY: (202) 418-0432.</P>
          <P>•<E T="03">Availability of Documents.</E>Comments, reply comments, and<E T="03">ex parte</E>submissions will be available for public inspection during regular business hours in the FCC Reference Center, Federal Communications Commission, 445 12th Street, SW., CY-A257, Washington, DC 20554. These documents will also be available via ECFS. Documents will be available electronically in ASCII, Microsoft Word, and/or Adobe Acrobat.</P>

          <P>For detailed instructions for submitting comments and additional information on the rulemaking process, see the<E T="02">SUPPLEMENTARY INFORMATION</E>section of this document.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Peter Daronco of the Broadband Division, Wireless Telecommunications Bureau, at (202) 418-BITS. For additional information concerning the Paperwork Reduction Act information collection requirements contained in this document, contact Judith B. Herman at (202) 418-0214, or via the Internet at<E T="03">PRA@fcc.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>This is a summary of the Commission's<E T="03">Notice of Proposed Rulemaking,</E>FCC 12-152, adopted on December 11, 2012, and released on December 17, 2012. The full text of this document is available for inspection and copying during normal business hours in the FCC Reference Information Center, Room CY-A257, 445 12th Street, SW., Washington, DC 20554. The complete text may be purchased from the Commission's duplicating contractor, Best Copy and Printing, Inc. (BCPI), Portals II, 445 12th Street, SW., Room CY-B402, Washington, DC 20554, (202) 488-5300, facsimile (202) 488-5563, or via email at<E T="03">fcc@bcpiweb.com.</E>The complete text is also available on the Commission's Web site at<E T="03">http://hraunfoss.fcc.gov/edocs_public/attachment/FCC-12-152A1doc.</E>Alternative formats (computer diskette, large print, audio cassette, and Braille) are available by contacting Brian Millin at (202) 418-7426, TTY (202) 418-7365, or via email to<E T="03">bmillin@fcc.gov.</E>
        </P>

        <P>Pursuant to §§ 1.415 and 1.419 of the Commission's rules, 47 CFR 1.415, 1.419, interested parties may file comments and reply comments on or before the dates indicated on the first page of this document. Comments may be filed using the Commission's Electronic Comment Filing System (ECFS).<E T="03">See Electronic Filing of Documents in Rulemaking Proceedings,</E>63 FR 24121 (1998). All filings should reference the docket numbers in this proceeding, FCC 12-152, or by WT Docket No. 12-357.</P>
        <P>
          <E T="03">Electronic Filers:</E>Comments may be filed electronically using the Internet by accessing the ECFS:<E T="03">http://fjallfoss.fcc.gov/ecfs2/.</E>
        </P>
        <P>
          <E T="03">Paper Filers:</E>Parties who choose to file by paper must file an original and one copy of each filing. If more than one docket or rulemaking number appears in the caption of this proceeding, filers must submit two additional copies for each additional docket or rulemaking number.</P>
        <P>Filings can be sent by hand or messenger delivery, by commercial overnight courier, or by first-class or overnight U.S. Postal Service mail. All filings must be addressed to the Commission's Secretary, Office of the Secretary, Federal Communications Commission.</P>

        <P>All hand-delivered or messenger-delivered paper filings for the Commission's Secretary must be delivered to FCC Headquarters at 445 12th St., SW., Room TW-A325, Washington, DC 20554. The filing hours are 8:00 a.m. to 7:00 p.m. All hand deliveries must be held together with rubber bands or fasteners. Any envelopes and boxes must be disposed of<E T="03">before</E>entering the building.</P>
        <P>Commercial overnight mail (other than U.S. Postal Service Express Mail and Priority Mail) must be sent to 9300 East Hampton Drive, Capitol Heights, MD 20743.</P>
        <P>U.S. Postal Service first-class, Express, and Priority mail must be addressed to 445 12th Street SW., Washington DC 20554.</P>
        <P>
          <E T="03">People with Disabilities:</E>To request materials in accessible formats for people with disabilities (braille, large print, electronic files, audio format), send an 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>
        <P>Document<E T="03">FCC 12-152</E>contains proposed information collection requirements subject to the PRA. It will be submitted to the Office of Management and Budget (OMB) for review under section 3507 of the PRA. OMB, the general public, and other Federal agencies are invited to comment on the proposed information collection requirements contained in this document. PRA comments should be submitted to Judith B. Herman at (202) 418-0214, or via the Internet at<E T="03">PRA@fcc.gov</E>and to Nicholas A. Fraser, Office of Management and Budget, via email to<E T="03">Nicholas_A._Fraser@omb.eop.gov</E>or via fax at 202-395-5167.</P>

        <P>To view a copy of this information collection request (ICR) submitted to OMB: (1) Go to the Web page<E T="03">http://www.reginfo.gov/public/do/PRAMain</E>, (2) look for the section of the Web page called “Currently Under Review,” (3) click on the downward-pointing arrow in the “Select Agency” box below the “Currently Under Review” heading, (4) select “Federal Communications Commission” from the list of agencies presented in the “Select Agency” box, (5) click the “Submit” button to the right of the “Select Agency” box, (6) when the list of FCC ICRs currently under review appears, look for the title of this ICR and then click on the ICR Reference Number. A copy of the FCC submission to OMB will be displayed.</P>
        <P>
          <E T="03">Initial Paperwork Reduction Act Analysis</E>
        </P>

        <P>This document contains proposed new or modified information collection requirements. The Commission, as part of its continuing effort to reduce paperwork burdens, invites the general public and the Office of Management and Budget (OMB) to comment on the 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<PRTPAGE P="1168"/>might further reduce the information collection burden for small business concerns with fewer than 25 employees.</P>
        <P>
          <E T="03">OMB Control Number:</E>3060-[XXXX].</P>
        <P>
          <E T="03">Title:</E>Sections 1.946, 1.949, 1.2105(a), etc.—Service Rules for Advanced Wireless Services (AWS) H Block.</P>
        <P>
          <E T="03">Form Number:</E>N/A.</P>
        <P>
          <E T="03">Type of Review:</E>New collection.</P>
        <P>
          <E T="03">Respondents:</E>Business or other for-profit entities, not-for-profit institutions, and state, local, or tribal government.</P>
        <P>
          <E T="03">Number of Respondents:</E>50 respondents; 50 responses.</P>
        <P>
          <E T="03">Estimated Time per Response:</E>.25 hours to .5 hours.</P>
        <P>
          <E T="03">Frequency of Response:</E>Annual, one time, and on occasion reporting requirements; recordkeeping requirement; and third party disclosure requirement.</P>
        <P>
          <E T="03">Obligation to Respond:</E>Required to obtain or retain benefits. Statutory authority for the information collection is contained in 15 U.S.C. 79<E T="03">et seq.;</E>47 U.S.C. sections 151, 154(i), 154(j), 155, 157, 225, 227, 303(r), 309, 1404, and 1451.</P>
        <P>
          <E T="03">Total Annual Burden:</E>14 hours.</P>
        <P>
          <E T="03">Total Annual Cost:</E>N/A.</P>
        <P>
          <E T="03">Privacy Impact Assessment:</E>N/A.</P>
        <P>
          <E T="03">Nature and Extent of Confidentiality:</E>There is no need for confidentiality.</P>
        <P>
          <E T="03">Needs and Uses:</E>The Commission is submitting this information collection to the Office of Management and Budget as a new collection. The<E T="03">Notice of Proposed Rulemaking (NPRM)</E>proposes rules for the Advanced Wireless Services (AWS) H Block to make available ten megahertz of spectrum for flexible use, extending the current Personal Communications Services (PCS) band, which is used by the four national providers as well as regional and rural providers to offer mobile service across the Nation. The<E T="03">NPRM</E>begins the Commission's implementation of the Congressional directive in the Middle Class Tax Relief and Job Creation Act of 2012 (Spectrum Act) to grant new initial licenses for the 1915-1920 MHz (Lower H Block) and 1995-2000 MHz (Upper H Block) bands through a system of competitive bidding—unless doing so would cause harmful interference to commercial mobile service licensees in the 1930-1995 MHz (PCS downlink) band.</P>
        <HD SOURCE="HD1">Summary</HD>
        <HD SOURCE="HD1">I. Introduction</HD>
        <P>1. We propose rules for the Advanced Wireless Services (AWS) H Block that would make available ten megahertz of spectrum for flexible use. The proposal would extend the widely-deployed Personal Communications Services (PCS) band, which is used by the four national providers as well as regional and rural providers to offer mobile service across the nation. The additional spectrum for mobile use will help ensure that the speed, capacity, and ubiquity of the nation's wireless networks keeps pace with the skyrocketing demand for mobile service.</P>
        <P>2. The Commission's action is a first step in implementing the Congressional directive in the Middle Class Tax Relief and Job Creation Act of 2012 (Spectrum Act) that we grant new initial licenses for the 1915-1920 MHz and 1995-2000 MHz bands (the Lower H Block and Upper H Block, respectively) through a system of competitive bidding—unless doing so would cause harmful interference to commercial mobile service licensees in the 1930-1995 MHz (PCS downlink) band (collectively, the Lower H Block and Upper H Block are referred to as the “H Block”).</P>
        <HD SOURCE="HD1">II. Discussion</HD>

        <P>3. To implement the Spectrum Act provisions pertaining to the H Block, and in keeping with our goal of expanding the amount of spectrum available for wireless broadband services, we propose terrestrial service rules for the H Block that would generally follow the Commission's part 27 rules. In some instances, we propose rules that are modified from part 27 to account for issues unique to the H Block, particularly to protect PCS licensees from harmful interference. With this<E T="03">NPRM,</E>we seek comment on a number of proposals regarding the licensing, use, and assignment of the spectrum, including the costs and benefits of the proposals.</P>

        <P>4. Although the Commission previously sought comment on many of these issues in the<E T="03">AWS-2 NPRM,</E>Service Rules for Advanced Wireless Services in the 1915-1920 MHz, 1995-2000 MHz, 2020-2025 MHz and 2175-2180 MHz Bands, 69 FR 63489 (Nov. 2, 2004) (<E T="03">AWS-2 NPRM</E>), and the<E T="03">2008 FNPRM,</E>Service Rules for Advanced Wireless Services in the 2155-2175 MHz Band; Service Rules for Advanced Wireless Services in the 1915-1920 MHz, 1995-2000 MHz, 2020-2025 MHz and 2175-2180 MHz Bands, 73 FR 35995 (June 25, 2008) (<E T="03">2008 FNPRM),</E>wireless broadband technologies and the wireless industry have evolved since the Commission last sought comment on these issues such that, in our assessment, the development of a fresh record is warranted. As a result, we will adopt H Block rules based on the record developed in response to this<E T="03">NPRM</E>(WT Docket No. 12-357). Parties may re-file in this docket earlier comments with any necessary updates.</P>
        <P>5. For each of the issues identified below, we seek comment on the most efficient manner to address the issue. Commenters should also identify the various costs and benefits associated with a particular proposal. We ask that commenters take into account only those costs and benefits that directly result from the implementation of the particular rules that could be adopted, including any proposed requirement or potential alternative requirement. Further, to the extent possible, commenters should provide specific data and information, such as actual or estimated dollar figures for each specific cost or benefit addressed, along with a description of how the data or information was calculated or obtained, and any supporting documentation or other evidentiary support.</P>
        <HD SOURCE="HD2">A. Spectrum Act Provisions for 1915-1920 MHz and 1995-2000 MHz</HD>
        <P>6. We discuss the Spectrum Act's four main statutory elements related to the H Block—allocation for commercial use, flexible use, assignment of licenses, and a determination regarding interference—in greater detail below.</P>
        <HD SOURCE="HD3">1. Allocation for Commercial Use</HD>

        <P>7. Section 6401 of the Spectrum Act requires the Commission to allocate the 1915-1920 MHz and 1995-2000 MHz bands for commercial use. The Spectrum Act does not define the phrase “allocate [the H Block] for commercial use.” When this phrase is read in the context of the Spectrum Act as a whole, we conclude it requires the Commission to make any changes necessary to, or otherwise ensure that, the Non-Federal Table of Allocations reflects that the spectrum identified in section 6401 can be used commercially and licensed to non-federal entities under flexible use service rules through a system of competitive bidding. All of the H Block spectrum is within the 1850-2000 MHz band, which is allocated exclusively for non-federal, fixed and mobile use on a primary basis and designated for use in the commercial PCS/AWS bands. We believe the Commission's prior allocation of the H Block is fully consistent with section 6401's allocation language because the existing allocation is the broadest allocation possible consistent with international allocations. We further read section 6401 as directing the Commission to maintain this existing allocation. Given the requirement to license under flexible use service rules, we do not read the requirement to allocate the H<PRTPAGE P="1169"/>Block for commercial use to specifically limit eligible uses to commercial uses.</P>
        <P>8. Therefore, we tentatively conclude that the existing allocation of the H Block for non-federal fixed and mobile use on a primary basis meets the allocation requirement of section 6401(b)(1)(A) for the H Block, and seek comment on this tentative conclusion. We seek comment on whether there are any additional actions the Commission should take to comply with the requirement to allocate the H Block for commercial use. We ask commenters that believe further action is needed to comply with Congress's mandate to detail what other action is necessary, including the costs and benefits of such action.</P>
        <HD SOURCE="HD3">2. Flexible Use</HD>
        <P>9. Consistent with the Spectrum Act's mandate that we license the H Block under flexible use service rules, we propose service rules for the H Block that permit a licensee to employ the spectrum for any non-Federal use permitted by the United States Table of Frequency Allocations, subject to the Commission's part 27 flexible use and other applicable rules (including service rules to avoid harmful interference). Congress recognized the potential benefits of flexible spectrum allocations and amended the Communications Act in 1997 to add section 303(y), which grants the Commission the authority to adopt flexible allocations if certain factors are met. Thus, we propose that the H Block may be used for any fixed or mobile service that is consistent with the allocations for the band. If commenters think any restrictions are warranted, they should describe why such restrictions are needed, quantify the costs and benefits of any such restrictions, and describe how such restrictions would comport with the statutory mandates of section 303(y) of the Communications Act and section 6401 of the Spectrum Act.</P>
        <HD SOURCE="HD3">3. Assignment of Licenses</HD>
        <P>10. Section 6401(b) of the Spectrum Act requires the Commission to assign initial licenses for the 1915-1920 and 1995-2000 MHz bands through a system of competitive bidding pursuant to section 309(j) of the Communications Act. Accordingly, below, we seek comment on proposals regarding competitive bidding rules that would apply to resolve any mutually exclusive applications accepted for H Block licenses.</P>
        <HD SOURCE="HD3">4. Determination of No Harmful Interference to the 1930-1995 MHz Band</HD>
        <P>11. The Commission is prohibited from granting initial licenses under the Spectrum Act for the H Block if the Commission determines that the H Block “cannot be used without causing harmful interference” to commercial mobile licensees in the 1930-1995 MHz band (PCS downlink band). We note that the Spectrum Act does not define the term “harmful interference,” and we propose to use the existing definition of “harmful interference” in the Commission's rules. Under the Commission's rules harmful interference is “[i]nterference which endangers the functioning of a radionavigation service or of other safety services or seriously degrades, obstructs, or repeatedly interrupts a radiocommunication service operating in accordance with [the International Telecommunications Union] Radio Regulations.”</P>
        <P>12.<E T="03">Upper H Block.</E>As detailed in the Band Plan section below, the Commission allocated this spectrum for fixed and mobile use in 2003, and it designated it for PCS/AWS base station operations and proposed service rules to that effect in 2004. During the eight years that WT Docket No. 04-356 has been pending, no party has filed technical data and/or analysis indicating that base station operations in the Upper H Block would cause harmful interference to licensees in the PCS downlink band. Accordingly, we tentatively conclude that licensing the Upper H Block under flexible use service rules will not cause harmful interference to commercial mobile licensees in the 1930-1995 MHz band. We seek comment on this tentative conclusion.</P>
        <P>13.<E T="03">Lower H Block.</E>In 2004 the Commission designated this spectrum for PCS/AWS mobile operations; paired with Upper H Block, after concluding that harmful interference from Lower H Block to the PCS downlink band could be addressed through appropriate service rules. In WT Docket No. 04-356, commenters vigorously debated the power and out-of-band emission limits necessary to avoid interference to mobiles receiving in the PCS downlink band. Four PCS licensees proposed technical rules for Lower H Block to avoid interference to PCS and at least one PCS licensee continues to advocate for one of the earlier proposals. As discussed in detail below, we propose a band plan and are seeking comment on technical rules to avoid interference, including the earlier proposals by PCS licensees. Accordingly, we tentatively conclude that it will be possible to auction and license the Lower H Block under flexible use service rules without causing harmful interference to commercial mobile licensees in the PCS downlink (1930-1995 MHz) band. We seek comment on this tentative conclusion. Regarding the proposed band plan and technical issues discussed in the sections below, we ask that commenters proposing alternative band plans and/or technical rules—including any alternative proposals that have been previously submitted to the Commission—provide detailed analyses of how their proposal will avoid harmful interference to licensees in the PCS downlink band.</P>
        <P>14.<E T="03">Alternatives, if Harmful Interference to PCS.</E>If, contrary to our expectation, the record results in a determination that licensing the Upper H Block, the Lower H Block, or both, would cause harmful interference to licensees in the PCS downlink band, section 6401(b)(4) of the Spectrum Act nullifies the initial requirement in section 6401(b)(1)(a) that the Commission to allocate the interfering spectrum for commercial use. We do not, however, believe that Congress intended section 6401(b)(4)(a) to disturb allocations adopted prior to the Spectrum Act. Rather, Congress intended section 6401(b)(4) to avoid harmful interference to the millions of existing customers of PCS licensees that might otherwise result from Commission actions implementing the requirements in section 6401(b)(1) related to H Block. Therefore, if we determine that the Lower H Block, the Upper H Block, or both, cannot be used without causing harmful interference to PCS licensees, we tentatively conclude that we may not under the Spectrum Act auction and grant initial licenses, subject to flexible use service rules, for the interfering spectrum. If we determine that half of the H Block cannot be auctioned and licensed, we tentatively conclude that the statute requires us to auction and license the half of the H Block that would not cause harmful interference to PCS downlinks (<E T="03">i.e.,</E>either the Upper or Lower H Block). Accordingly, we ask commenters to address what should be done in the alternative with the H Block or any portion of the H Block that we determine cannot be licensed under the Spectrum Act due to harmful interference to licensees in the PCS downlink band. In particular, should any such spectrum be designated for Unlicensed PCS (UPCS)?<PRTPAGE P="1170"/>
        </P>
        <HD SOURCE="HD2">B. Band Plan</HD>
        <P>15. In the following sections, we propose to license the H Block as paired 5 megahertz blocks, with the Upper H Block used for high-power base stations and the Lower H Block used for mobile and low power fixed operations. We further propose to license the H Block by Economic Areas. We invite commenters to propose other licensing areas including for the Gulf of Mexico.</P>
        <HD SOURCE="HD3">1. Block Configuration</HD>
        <P>16. In 2004, the Commission adopted the<E T="03">AWS Sixth Report and Order,</E>Amendment of Part 2 of the Commission's Rules to Allocate Spectrum Below 3 GHz for Mobile and Fixed Services to Support the Introduction of New Advanced Wireless Services, Including Third Generation Wireless Systems, 69 FR 62615 (Oct. 27, 2004), designating the H Block for licensed fixed and mobile services, including advanced wireless services, and pairing the 1915-1920 MHz band with the 1995-2000 MHz band. The Commission decided to pair the 1915-1920 MHz and 1995-2000 MHz bands because it found that pairing this spectrum would promote efficient use of the spectrum, would allow for the introduction of high-value services, and was otherwise preferable to the other options that had been put forth.</P>
        <P>17. In addition, the Commission contemplated that mobile operations would be conducted in the Lower H Block. The Commission reasoned that using the Lower H Block for low power operations would be advantageous because the adjacent 1910-1915 MHz PCS band is used for mobile operations and using the Lower H Block for high power base station operations could result in harmful interference to the PCS band.</P>
        <P>18. We see no reason to diverge from the reasoning in the<E T="03">AWS Sixth Report and Order.</E>Accordingly, we tentatively conclude that the 1915-1920 MHz and 1995-2000 MHz bands should be paired as a single band. In addition, we propose that high power base station operations will be prohibited in the Lower H Block. We seek comments on the costs and benefits of licensing the 1915-1920 MHz and 1995-2000 MHz bands in this manner. We also seek comment on alternate configurations of the H Block. Commenters should address any technical issues implicated in an alternate band plan, and should discuss the costs and benefits of any alternative proposal.</P>
        <HD SOURCE="HD3">2. Service Area</HD>
        <P>19.<E T="03">Geographic Area Licensing:</E>We propose to adopt a geographic area licensing scheme for the H Block because it is well-suited for the types of fixed and mobile services that would likely be deployed in these bands. Additionally, geographic-area licensing is consistent with the Commission's licensing approach for the AWS-1, Broadband PCS, Commercial 700 MHz bands, and AWS-4 bands. Based on the Commission's experience administering these services, geographic area licensing: (1) Provides licensees with substantial flexibility to respond to market demand, which results in significant improvements in spectrum utilization; (2) permits economies of scale because licensees can coordinate usage across an entire geographic area to maximize spectrum use; and, (3) reduces the regulatory burdens and transaction costs because wide-area licensing does not require site-by-site approval so a licensee can aggregate its service territories without incurring the administrative costs and delays associated with site-by-site licensing. We seek comment on this approach, including the costs and benefits of adopting a geographic area licensing scheme.</P>
        <P>20. In the event that commenters do not support geographic-area licensing for the H Block, commenters should explain their position and identify any alternative licensing proposals that they support, including the costs and benefits associated with such alternative proposals. Commenters should also address how an alternative licensing approach would be consistent with the statutory requirement to assign licenses in the H Block through competitive bidding and the statutory objectives that the Commission is required to promote in establishing methodologies for competitive bidding.</P>
        <P>21.<E T="03">Service Area Size.</E>We seek to adopt a service area size for the H Block that meets several statutory goals. These include facilitating access to spectrum by both small and large providers, providing for the efficient use of the spectrum, encouraging deployment of wireless broadband services to consumers, especially those in rural areas, and promoting investment in and rapid deployment of new technologies and services consistent with our obligations under section 309(j) of the Communications Act.</P>
        <P>22. To accomplish these goals, we propose to license the H Block on an Economic Area (EA) basis. The adjacent bands, both PCS and AWS-4, are licensed on an EA basis. EAs are small enough to provide spectrum access opportunities for smaller carriers but also may be aggregated up to larger license areas to achieve economies of scale. We seek comment on this approach and ask commenters to discuss and quantify the economic, technical, and other public interest considerations of any particular geographic scheme for this band, as well as the impact that any such scheme would have on rural service and competition.</P>
        <P>23. We also seek comment on whether we should license the H Block on a nationwide basis. We seek comment on the extent to which nationwide licenses maximize or limit the opportunity for licensees to provide the widest array of services, and whether nationwide licenses provide the necessary incentives to foster the growth of existing technologies and the development of new technologies. We also ask commenters to compare the advantages and disadvantages of nationwide licensing to those of licensing by EAs, including economic and financial considerations.</P>
        <P>24. In response to the<E T="03">AWS-2 NPRM,</E>some commenters argued that licensing the H Block using smaller geographic areas than EAs would accommodate its possible use as complementary spectrum to existing PCS offerings. Other commenters agreed and also noted that small and rural wireless providers would benefit if the Commission licensed the H Block using smaller geographic areas than EAs. Would licensing the H Block by areas smaller than EAs (<E T="03">e.g.,</E>Cellular Market Areas comprising Metropolitan Statistical Areas (MSAs) and Rural Service Areas (RSAs)) facilitate its use by smaller and rural operators? Would the benefits of smaller licenses outweigh any potential diseconomies of scale? We also seek comment on whether we should license the H Block by BTAs and the associated costs and benefits of this approach. Are there other geographic licensing methods that would better meet the stated goals for this band?</P>
        <HD SOURCE="HD3">3. Licensing the Gulf of Mexico</HD>

        <P>25. In addition, we seek comment on how to license the Gulf of Mexico. Should the Gulf of Mexico be part of another service area(s) or should we separately license a service area(s) to cover the Gulf of Mexico? Are there any public interest benefits that would be served by creating a Gulf of Mexico licensing area? Further, would the interests of the land based licensees be protected if we proceeded to license the Gulf of Mexico? Commenters that advocate a separate service area(s) to cover the Gulf of Mexico should discuss what boundaries should be used, and whether special interference protection criteria or performance requirements are<PRTPAGE P="1171"/>necessary due to the unique radio propagation characteristics and antenna siting challenges that exist for Gulf licensees.</P>
        <HD SOURCE="HD2">C. Technical Issues</HD>

        <P>26. As discussed above, we are proposing that the Upper H Block be used for base station (<E T="03">i.e.,</E>high power) operations, and the Lower H Block for mobile and other low-power operations. In this section we consider whether technical standards generally applicable to AWS and PCS stations are appropriate for these bands, or whether different standards are necessary to provide interference protection to services operating in adjacent spectrum bands. In light of the Spectrum Act, and our assessment of the relevant public interest benefits, a key goal in this proceeding is to develop technical rules that will permit optimal use of the H Block without causing harmful interference to commercial mobile service licensees in the 1930-1995 MHz PCS band. In responding to our inquiries, we ask commenting parties to provide test data and specific technical analysis to support their positions.</P>
        <HD SOURCE="HD3">1. Upper H Block: 1995-2000 MHz</HD>

        <P>27. Immediately below the Upper H Block is the 1930-1995 MHz PCS band, which is used for base station transmit/mobile receive (<E T="03">i.e.,</E>downlink). The Commission has tentatively concluded that base stations operating in the Upper H Block would be compatible with similar use of the spectrum below 1995 MHz, and there would be no need to apply technical standards more restrictive than those established for other AWS stations. The record developed in WT Docket No. 04-356 does not demonstrate any disagreement with this approach.</P>

        <P>28. Immediately above the Upper H Block is the 2000-2020 MHz band, which is allocated on a co-primary basis for Fixed, Mobile, and Mobile Satellite (Earth-to-space,<E T="03">i.e.,</E>for uplink mobile transmit/satellite receive). In the<E T="03">AWS-4 Report and Order,</E>we adopted service rules under which 2000-2020 MHz will be licensed terrestrially for mobile transmit/base station receive. Service Rules for Advanced Wireless Services in the 2000-2020 MHz and 2180-2200 MHz Bands, FCC 12-151. The Commission has previously concluded that there is potential for mutual interference between these two bands, and in WT Docket No. 04-356 MSS commenters raised concerns. In the<E T="03">AWS-4 Report and Order,</E>we concluded that the public interest is best served by requiring AWS-4 uplinks to operate at lower power levels in 2000-2005 MHz and emit lower emissions below 2000 MHz. We further concluded that 2 GHz MSS operators and AWS-4 licensees must accept any harmful interference from future, lawful operations in the Upper H Block due to out of band emissions in the 2000-2005 MHz band or receiver overload from transmitters operating within the 1995-2000 MHz band.</P>
        <HD SOURCE="HD3">a. Upper H Block Power Limits</HD>
        <P>29. We also propose to adopt the standard base station power limits that apply to AWS and PCS stations: 1640 watts peak equivalent isotropically radiated power (EIRP) in non-rural areas and 3280 watts peak EIRP in rural areas. We seek comment on this proposal.</P>
        <HD SOURCE="HD3">b. Upper H Block Out of Band Emissions Limits</HD>

        <P>30. Given the considerations addressed above, we propose an out-of band-emission (OOBE) limit for base stations of 43 + 10 log<E T="52">10</E>(P) dB, where P is the transmit power in watts, outside of the 1995-2000 MHz band. To provide some interference mitigation to AWS-4 uplink operations above 2000 MHz while ensuring that all of the Upper H Block spectrum can be used for more valuable downlink operations, we propose a further OOBE limit of 70 + 10 log<E T="52">10</E>(P) dB above 2005 MHz. We seek comment on our proposals and any alternative proposals, including comments on the associated costs and benefits of each proposal.</P>
        <HD SOURCE="HD3">c. Co-Channel Interference Between Licensees Operating in Adjacent Regions</HD>

        <P>31. If we ultimately decide to license this band on the basis of geographic service areas that are less than nationwide (<E T="03">e.g.,</E>EAs), we will have to ensure that such licensees do not cause interference to co-channel systems operating along their common geographic borders. In other services, the Commission has offered either a “boundary limit” or a “coordination” approach to provide interference protection between co-channel licensees operating in these bands. Both approaches have certain advantages and disadvantages. For example, coordination would likely minimize the potential for interference to coordinated stations, but could also impose unnecessary costs in coordinating facilities that have a low potential for interference. A boundary limit approach would establish an accepted standard, which would enable licensees to deploy facilities in boundary areas without the need for coordination; but could require some additional planning between licensees to ensure that potential interference does not occur.</P>
        <P>32. In other bands where spectrum has been allocated for fixed and mobile services, we have uniformly adopted the boundary limit method to minimize co-channel interference. For example, for the PCS and AWS-1 bands, which are closest in frequency to the H Block, there is a field strength limit of 47 dBμV/m at the boundary of licensed geographic areas. We propose that the boundary limit approach should be adopted for the H Block as the means for protecting licensees from co-channel interference at their borders, and propose to specify a boundary field strength limit of 47 dBμV/m. We seek comment on these proposals. We also ask whether, if the boundary limit method is adopted, we should permit licensees operating in adjoining areas to employ alternative, agreed-upon signal limits at their common borders.</P>
        <HD SOURCE="HD3">2. Lower H Block: 1915-1920 MHz</HD>
        <P>33. Immediately below the Lower H Block is the 1850-1915 MHz PCS band, which is used for mobile transmit/base receive. Use of the Lower H Block for mobile transmit/base receive, as we have proposed, would be compatible with this adjacent PCS band. Thus there would be no need to apply technical standards more restrictive than those established for AWS and PCS stations to protect PCS operations below 1915 MHz.</P>

        <P>34. Above the Lower H Block is the 1920-1930 MHz unlicensed PCS (UPCS) band, which does not require protection, and the 1930-1995 PCS base transmit/mobile receive band. The latter presents protection challenges for use of the Lower H Block. The Commission has previously concluded that there is potential for mobile transmitters in the 1915-1920 MHz band to cause out-of-band and overload interference to mobile receivers in the 1930-1995 MHz band, but only when certain worst-case conditions are all present. Specifically, “[t]he worst case occurs when the mobile transmitter is operating at maximum power (near the edge of its service area) at the upper edge of the band (near 1920 MHz) and the mobile receiver is trying to receive a weak signal (near the edge of its service area) at the lower edge of the band (near 1930 MHz) and only free space loss is considered.” Additionally, both mobiles must be in close proximity to each other, less than a few meters, and in line-of-sight conditions. The Commission found that the confluence of these worst-case circumstances is very infrequent and the risk of actual interference is further mitigated by<PRTPAGE P="1172"/>normal network management practices such as handoff and power management. Nevertheless, the Commission concluded that technical standards more restrictive for Lower H Block than those established for PCS may be appropriate to avoid impairing incumbent PCS operations above 1930 MHz.</P>
        <P>35. The Spectrum Act sharply focuses these concerns by requiring us to auction the H Block spectrum unless we determine that the frequencies cannot be used without causing harmful interference to commercial mobile service licensees in the frequencies between 1930 MHz and 1995 MHz (PCS downlink). We therefore wish to review previous proposals for Lower H Block power and emissions limits, evaluate how the interference environment may have changed since those earlier discussions, and determine what limits are appropriate for the current environment, and whether they may be increased in the future.</P>
        <HD SOURCE="HD3">a. Lower H Block Power Limits</HD>

        <P>36. Several parties have expressed concern about the potential for intermodulation interference, which can result from receiver overload, impacting PCS user equipment (UEs) receiving in the PCS B Block (1950-1965 MHz). In the<E T="03">2008 FNPRM,</E>the Commission proposed a limit on the EIRP from H Block mobile transmitters of +23 dBm/MHz. In response, Sprint and Verizon Wireless (both licensees of significant portions of PCS including B Block) and Nextel reiterated their 2005 proposal for gradated power limits to avoid interference to PCS as follows: A limit on mobile EIRP of +6 dBm/MHz in the 1917-1920 MHz band, and a limit of +30 dBm/MHz in the 1915-1917 MHz band. This proposal was supported by testing of a variety of mobiles commissioned by CTIA in 2004. Sprint has repeatedly and recently stated that the H Block can be auctioned and licensed without interfering with PCS operations by using these earlier-proposed, gradated power limits. AT&amp;T, also a licensee of a significant portion of PCS spectrum, including the B Block, did not concur with the plan put forth by Sprint, Verizon and Nextel and submitted an alternative solution. AT&amp;T proposed a uniform, “technologically neutral,” −13 dBm/MHz power limit on the Lower H Block to protect PCS, arguing that the split-band approach favored CDMA over GSM and wideband technologies, such as W-CDMA and UMTS/HSPA. In response to the<E T="03">AWS-4 NPRM</E>AT&amp;T favored leaving the H Block idle to serve as a guard band to protect AWS-4 and PCS. More recently, AT&amp;T argues in the alternative that if the Commission proceeds with an auction of the entire H Block despite AT&amp;T's concerns, we should adopt technical rules to protect PCS devices from harmful interference including appropriate power limits on H Block mobiles.</P>
        <P>37. We seek to establish technical requirements that will support flexible use of this spectrum in accordance with the Spectrum Act without causing harmful interference to PCS licensees. The record in WT Docket No. 04-356 was largely developed between four and eight years ago. Since then, the mobile broadband industry, including the wireless network equipment sector, has undergone a rapid evolution. The marketplace has seen greater adoption of wideband technologies such as UMTS and LTE, as well as the authorization and launch of PCS services in the G Block. Advances in mobile device development have unleashed new designs and ushered in the advent of the smartphone. We seek comment on how changes in the industry may have affected the assumptions underlying previous analyses. How have filtering techniques and duplex design improved? Given that the Commission's intentions to authorize mobile service in the H Block have been known in the industry since at least 2004, have better duplexer filters been employed in user equipment? How has the population of mobile devices changed, what is the mix of technologies in use in the marketplace, and what is the performance of this new generation of devices?</P>
        <P>38. We seek comment on the appropriate power limit for 1915-1920 MHz mobile devices in order to prevent interference to PCS operations. Commenters are asked to submit detailed technical analyses or studies in support of their recommendations and are encouraged to provide test data wherever possible. The assumptions that underpin the analyses should identify how harmful interference is defined. What probability of interference is deemed acceptable (what percentage of mobiles, what percentage of locations)? For example, the Commission's earlier proposal, 23 dBm/MHz, was based on a mobile separation of two meters between users, while others argued for a one-meter separation. Likewise, is defining harmful interference based on degradation to a receiver's noise floor appropriate for a system which is inherently interference-limited? If stricter limitations on mobile transmit power are deemed necessary to protect current legacy devices, should the power limits sunset after a period of time, allowing time for new, more resilient mobiles to comprise the bulk of the mobile population? How much time will licensees need to obtain and deploy UEs with the better filters, if better filters are still needed? How long will consumers' legacy UEs need to be protected? We also seek comment on the costs and benefits of alternative power limits.</P>
        <P>39. The 1915-1920 MHz band is also allocated for fixed services, so fixed stations will be allowed to operate in the band. However, because fixed station antennas are generally located some distance above ground level, the possibility of interference from fixed stations to PCS mobiles will likely be less than the anticipated interference from 1915-1920 MHz mobiles to PCS mobiles. We therefore believe that 1915-1920 MHz fixed stations should be permitted to employ a higher power level than mobiles operating in that band. We seek comment as to what that power level should be.</P>
        <HD SOURCE="HD3">b. Lower H Block Out of Band Emissions Limits</HD>

        <P>40. The Commission has previously concluded that, in certain circumstances, attenuating transmitter OOBEs by 43 + 10 log<E T="52">10</E>(P) dB is appropriate to minimize harmful electromagnetic interference between operators. This limit is generally applied in cases where adjacent services have similar characteristics, such as base-to-base or mobile-to-mobile and adhere to similar power limits. This limit has served well as a basis for development of industry standards which may impose tighter limits in some cases. An OOBE limit of 43 + 10 log<E T="52">10</E>(P) dB applies to most of the services authorized under parts 24 and 27. In particular, this is the limit imposed on transmitters operating in both the 1930-1995 MHz PCS band and the 1920-1930 MHz UPCS band adjacent to the Lower H Block. As both of these services in adjacent bands provide for mobiles with similar power, the same OOBE limit appears appropriate for the Lower H Block. The Commission therefore proposes to require attenuation of 43 + 10 log<E T="52">10</E>(P) to emissions from transmitters in the 1915-1920 MHz band.</P>

        <P>41. The risk of mobile-to-mobile interference discussed below may require a further OOBE limitation to protect against the potential for interference from the out-of band emissions of Lower H Block transmitters into PCS mobiles receiving in the 1930-1995 MHz band. Currently, the Commission's rules require licensees<PRTPAGE P="1173"/>operating in the 1850-1915 MHz PCS band to comply with the 43 + 10 log<E T="52">10</E>P dB OOBE limit at the edge of their authorized spectrum block. This level of required attenuation of emissions with respect to the transmitter power can be translated into a power spectral density of −13 dBm/MHz for out-of-band emissions. We are aware that PCS-industry standards require equipment manufacturers to incorporate a stronger OOBE suppression capability in PCS mobiles. In the<E T="03">2008 FNPRM,</E>the Commission proposed a stricter limit on out of band emissions from Lower H Block transmitters of −60 dBm/MHz in the frequency range of 1930-1990 MHz (PCS downlink band), equivalent to an attenuation of 90 + 10 log<E T="52">10</E>(P) dB. The joint proposal of Sprint, Verizon and Nextel requested a limit of −76 dBm/MHz. Their analysis assumed a one-meter separation and mobile receivers operating in noise-limited faded signal conditions, and included test data commissioned by CTIA. Most of the mobiles tested met this limit. The −76 dBm/MHz specification is also the industry standard for CDMA devices under TIA-98F. Ericsson and Motorola submitted comments supporting the use of industry standards as the basis for OOBE limits and cited −61 dBm/MHz for the GSM Standard, with Motorola citing −76 dBm/MHz for the CDMA standard. Ericsson provided a later submission specifically supporting a limit of −66 dBm/MHz. Motorola, responding to CTIA's measurements, noted the failure of two GSM devices to meet the tighter CDMA-based OOBE limits of −76 dBm/MHz and thus advocated a limit of −71 dBm/100 kHz, which is equivalent to −61 dBm/MHz.</P>

        <P>42. As discussed earlier, there has been considerable technological advancement in devices and technologies deployed in the mobile broadband industry since this issue was last under review. We note that many of the arguments for proposed OOBE limits were linked to industry standards at the time. The 3GPP standard for emerging 4G technology allows for a higher level of OOBE, generally −50 dBm/MHz in most bands, but has implemented a limit of −40 dBm/MHz in several bands. The current LTE standards for the use in PCS requires mobiles in 1850-1915 MHz to meet a limit of −50 dBm/MHz in 1930-1995 MHz. In this and the concurrent AWS-4 proceeding, Sprint has expressed support for an OOBE limit of −40 dBm/MHz from AWS-4 transmitters into the PCS downlink band at 1930-1995 MHz. In the<E T="03">AWS-4 Report and Order</E>we apply the limit of 70 + 10 log<E T="52">10</E>(P) dB, which is equivalent to −40 dBm/MHz, to all emissions below 2000 MHz. We believe that the current capabilities for mobile device manufacturers will support this level of tolerance for interference. Given that other operations may already be imposing out-of-band emissions at the −40 dBm/MHz level, should the Commission adopt this limit specifically for Lower H Block emissions in the 1930-1995 MHz range?</P>
        <P>43. The consensus from the record developed in WT Docket No. 04-356 supports the creation of a specific OOBE limit for emissions from Lower H Block transmitters into the 1930-1995 MHz band, even though no other PCS mobiles are subject to such tighter limits in this band. We seek comment on the appropriate OOBE limit for the Lower H Block necessary to prevent interference to PCS operations. Commenters are asked to submit detailed technical analyses or studies in support of their recommendations and are encouraged to provide test data wherever possible. As with comments regarding power limits, the assumptions that underpin the analyses should identify how harmful interference is defined. What probability of interference is deemed acceptable (what percentage of mobiles, what percentage of locations)? For example, the Commission's earlier proposal was based on a mobile separation of two meters between users, while others argued for a one-meter separation. Commenters should also discuss if certain limits favor or prohibit certain technologies, and are therefore not technologically neutral. For example, would imposing a limit of −76 dBm/MHz favor CDMA2000 over LTE, because CDMA2000 specifies −76 dBm/MHz for this band, while LTE specifies only −50 dBm/MHz? If stricter limitations on OOBE are deemed necessary to protect current legacy devices, should these limits sunset after a period of time, allowing time for new, more resilient mobiles to comprise the bulk of the mobile population? How much time will licensees need to obtain and deploy UEs with the better filters? How long will consumers' legacy UEs need to be protected? We also seek comment on the costs and benefits of alternative OOBE limits.</P>
        <P>44. To fully define an emissions limit, the Commission's rules generally specify details on how to measure the power of the emissions, such as the measurement bandwidth. For the Broadband PCS band, the measurement bandwidth used to determine compliance with this limit for mobile stations is one MHz or greater, with some modification in the one-MHz bands immediately outside and adjacent to the frequency block where a resolution bandwidth of at least one percent of the emission bandwidth of the fundamental emission of the transmitter may be employed. We believe that it is reasonable to apply this same procedure to transmissions in the 1915-1920 MHz band.</P>
        <HD SOURCE="HD3">3. Canadian and Mexican Coordination</HD>
        <P>45. Section 27.57(c) of our rules provides that AWS-1 operations are subject to international agreements with Mexico and Canada. We propose to use this approach for the H Block. Until such time as any adjusted agreements between the United States, Mexico and/or Canada can be agreed to, operations must not cause harmful interference across the border, consistent with the terms of the agreements currently in force. We note that our proposed rules, and any rules that may ultimately become effective pursuant to the above-captioned proceeding, may need to be modified to comply with any future agreements with Canada and Mexico regarding the use of the H Block. We seek comment on this issue, including the costs and benefits, and on any alternative approaches to this issue.</P>
        <HD SOURCE="HD3">4. Other Technical Issues</HD>
        <P>46. Part 27 contains several additional technical rules applicable to all part 27 services, including § 27.51 (Equipment authorization), § 27.52 (RF safety), § 27.54 (Frequency stability), § 27.56 (Antennas structures; air navigation safety), and § 27.63 (Disturbance of AM broadcast station antenna patterns). As we are proposing to license the H Block as Advanced Wireless Services under part 27, we propose that all of these part 27 technical rules should apply to all H Block licenses and licensees, including licensees who acquire their licenses through partitioning or disaggregation. We seek comment on this approach including comments on the associated costs and benefits.</P>

        <P>47. We recognize that H Block, governed under part 27 rules, is adjacent to Broadband PCS spectrum administered under part 24. The adjacent blocks are harmonized with the same uplink/downlink configuration. It is possible that the licensee of a PCS G Block geographic area may also acquire the authorization for the adjoining H Block through the competitive bidding process. In that event, the licensee may wish to deploy a wider channel bandwidth operating across both bands, and we believe that such flexibility is appropriate. For one thing, wider channel bandwidths may provide higher data rates and potentially more efficient use of the spectrum. The potential for<PRTPAGE P="1174"/>this situation raises questions about the possible effects of the combined blocks operating under different rule parts. Under the technical rules proposed herein, the limits on OOBE and power are similar, but not precisely the same. We anticipate that the licensee's combined operations should satisfy the more restrictive limit if a conflict arises. For example, an OOBE limit of 43 + 10 log<E T="52">10</E>(P) dB applies to both the Upper G Block and the Upper H block. However, the Upper H Block has an additional requirement to meet an OOBE limit of 70 + 10 log<E T="52">10</E>(P) dB above 2005 MHz. The combined operations of both blocks would still need to meet this tighter restriction above 2005 MHz. We further propose that to the extent a service provider establishes unified operations across the adjacent blocks, the operator may choose not to observe emission limits strictly between its adjacent block licenses in a geographic area, so long as it complies with other Commission rules and is not adversely affecting the operations of other parties by virtue of exceeding the emission limit. We seek comment on this observation. We also seek comment to identify potential conflicts between the two rule parts under this scenario and proposals on how they could be reconciled. Commenters should discuss and quantify any costs and benefits associated with such combined operations and any effects on competition, innovation and investment.</P>
        <HD SOURCE="HD2">D. Cost Sharing</HD>
        <HD SOURCE="HD3">1. 1915-1920 MHz Band</HD>

        <P>48. The 1915-1920 MHz band is a subset of a larger band at 1910-1930 MHz that is allocated for Fixed and Mobile services on a primary basis. In 1993, the Commission designated the 1910-1930 MHz band for use by Unlicensed Personal Communications Service (UPCS) devices. Prior to 1993, the 1910-1930 MHz band was allocated for Fixed services and used for fixed point to point microwave links. To facilitate the introduction of UPCS systems, the Commission designated the Unlicensed PCS Ad Hoc Committee for 2 GHz Microwave Transition and Management (now known as “UTAM, Inc.”) as the sole entity to coordinate and manage the transition. In accordance with the Commission's policies established in the<E T="03">Emerging Technologies</E>proceeding, UTAM subsequently relocated virtually all of the incumbent microwave links, thereby clearing the 1910-1930 MHz band for use by UPCS systems.</P>

        <P>49. In 2003, the Commission sought comment on re-designating all or a portion of the 1910-1920 MHz segment for AWS use. In 2004, the Commission re-designated the 1910-1915 MHz band from the UPCS to Fixed and Mobile services and assigned that spectrum to Sprint Nextel, Inc. (“Sprint”) as replacement spectrum for Sprint's operations being relocated from the 800 MHz band. Shortly thereafter, the Commission re-designated the 1915-1920 MHz band from UPCS for use by licensed AWS operations. In so doing, the Commission acknowledged that “UTAM must be fully and fairly reimbursed for relocating incumbent microwave users in this band” and agreed “that UTAM should be made whole for the investments it has made in clearing the UPCS bands.” Relative to the Lower H Block, the Commission specifically concluded that “UTAM is entitled to reimbursement of twenty-five percent—on a<E T="03">pro-rata</E>basis—of the total costs it has incurred, including its future payment obligations for links it has relocated, as of the date that a new entrant gains access to the 1915-1920 MHz spectrum band.” The Commission also determined that AWS licensees would be required to pay their portion of the 25 percent of costs prior to commencement of their operations.</P>
        <P>50. In the<E T="03">AWS-2 NPRM,</E>the Commission requested comments on methods for apportioning the relocation costs among H Block licensees, including what method of allocating relocation costs would be most advantageous to reimbursing UTAM and for providing certainty for bidders. The<E T="03">AWS-2 NPRM</E>also sought comment on what rules should govern the allocation of relocation costs among multiple AWS licensees in the 1915-1920 MHz band. Because UTAM requested that reimbursement payments from AWS licensees be due as a precondition to the granting of a license, the Commission sought comment on whether it would be advantageous to require AWS licensees to reimburse UTAM for its band clearing costs “earlier than the commencement of actual service.” To the extent that the Commission opted not to do so, the Commission also sought comment on whether it should specify when AWS entrants will be considered to have commenced operations.</P>

        <P>51. In deciding how to apportion UTAM's reimbursement among H Block licensees in the 1915-1920 MHz band, we believe it is important to provide auction bidders with reasonable certainty as to the range of the reimbursement obligation associated with each license under various auction outcomes. We also believe it is important for UTAM to be fully reimbursed as soon as possible given that UTAM cleared the band over ten years ago. Accordingly, we propose to require H Block licensees to pay a<E T="03">pro rata</E>amount of the 25 percent owed to UTAM based on the gross winning bids of the initial H Block auction. Specifically, we propose that the reimbursement amount owed (“RN”) be determined by dividing the gross winning bid (“GWB”) for an H Block license (<E T="03">i.e.,</E>an individual EA) by the sum of the gross winning bids for all H Block licenses won in the initial auction and then multiplying by $12,629,857. In other words, the cost-sharing formula would read as follows:</P>
        <GPH DEEP="41" SPAN="3">
          <GID>EP08JA13.011</GID>
        </GPH>

        <P>52. This formula would ensure that UTAM receives full reimbursement after the first auction by effectively apportioning the reimbursement costs associated with any unsold H Block licenses among the winning bidders of H Block licenses in the first auction—with an exception in the event a successful bidder's long-form application is not filed or granted, and a contingency to cover an unlikely scenario. We further propose that winning bidders of H Block licenses in the first auction of this spectrum would not have a right to seek reimbursement from other H Block licensees including for licenses awarded in subsequent auctions. We believe this approach would avoid recordkeeping burdens and potential disputes and that it is appropriate given that—in the event that most licenses are awarded—the reimbursement obligation for an individual license will represent but a fraction of overall reimbursement to UTAM. We seek comment on our proposals including the following<PRTPAGE P="1175"/>contingency: in the unlikely event that licenses covering less than 40 percent of the population of the United States are awarded in the first auction, we propose that winning bidders—in the first auction of this spectrum as well as in subsequent auctions—will be required to timely pay UTAM their<E T="03">pro rata</E>share calculated by dividing the population of the individual EA awarded at auction by the total U.S. population and then multiplying by $12,629,857. This contingent proposal would ensure that UTAM is reimbursed as soon as possible while also protecting winning bidders of H Block licenses from bearing an undue burden of the reimbursement obligation due to UTAM. We seek comment on our proposal.</P>
        <P>53. Alternatively, we specifically seek comment on the relative costs and benefits of adopting a population based cost-sharing formula as the general rule for the H Block. We acknowledge that using a population based approach in all events would offer bidders certainty as to the obligation attached to each license but this approach could also defer UTAM's full reimbursement indefinitely if less than all of the licenses are awarded during the initial auction.</P>
        <P>54. We further propose that winning bidders promptly pay UTAM the amount owed, as calculated pursuant to the formula that we adopt, within 30 days of grant of their long form applications for the licenses. For PCS and AWS-1, and AWS-4, cost sharing obligations are triggered when a licensee proposes to operate a base station in an area cleared of incumbents by another licensee. In this case, however, UTAM's members received no benefit for clearing the Lower H Block nationwide over ten years ago, and the Commission determined in 2003 that the new PCS/AWS licensees entering the band would reap the benefits of UTAM's efforts and that UTAM should be fully reimbursed. Moreover, as noted above, given the relative fraction of overall reimbursement to UTAM that will be owed by each winning bidder, we believe that it will not disincentivize parties from filing applications or impose a burden on winning bidders to reimburse UTAM within 30 days of the grant of their long-form applications. We seek comment on the above proposals, including the costs and benefits.</P>
        <HD SOURCE="HD3">2. 1995-2000 MHz Band</HD>
        <P>55. The 1995-2000 MHz band is part of the 1990-2025 MHz band that the Commission reallocated from the Broadcast Auxiliary Service (BAS) to emerging technologies such as PCS, AWS, and MSS. Consistent with the relocation principles established by the Commission, each new entrant had an independent responsibility to relocate incumbent BAS licensees. In addition, as a general rule, the Commission's traditional cost-sharing principles are applicable to the 1990-2025 MHz band. Sprint, which is the PCS licensee at 1990-1995 MHz, completed the BAS transition for the entire 35 megahertz in 2010. In 2011, Sprint notified the Commission that it entered in a private settlement with DISH to resolve the dispute with MSS licensees with respect to MSS licensees' obligation to reimburse Sprint for their share of the BAS relocation costs. Accordingly, the only remaining cost-sharing obligations in the 1990-2025 MHz band are attributable to the remaining, unassigned ten megahertz of spectrum in the 1990-2025 MHz band: 1995-2000 MHz and 2020-2025 MHz.</P>
        <P>56. In the<E T="03">AWS Sixth Report and Order,</E>the Commission determined that all new entrants to the 1990-2025 MHz band may be required to bear a proportional share of the costs incurred in the BAS clearance, on a<E T="03">pro rata</E>basis according to the amount of spectrum each licensee is assigned. However, the Commission did not decide specifically how to allocate that share. In the<E T="03">AWS-2 NPRM,</E>the Commission sought comment on how the reimbursement rights and obligations of each AWS licensee could be most efficiently and equitably allocated if the H Block were licensed on a geographic area basis other than as a nationwide license. To the extent that not all spectrum in the 1990-2025 MHz band would have been licensed, the Commission sought comment on whether to require those entrants who are licensed at that time to bear a<E T="03">pro rata</E>share of the relocation costs based on the amount of spectrum they have been assigned relative to the amount of 1990-2025 MHz spectrum that has been licensed. In addition, the Commission also sought comment on whether to impose reimbursement obligations on later arriving new entrants, on the appropriate length of such an obligation, and on the mechanism for applying those obligations.</P>

        <P>57. Consistent with the Commission's intent that all entrants to the 1990-2025 MHz band bear a proportional share of the costs incurred in the BAS clearance on a<E T="03">pro rata</E>basis according to the amount of spectrum each entrant is assigned, H Block licensees will be responsible for reimbursing Sprint for one-seventh of the BAS relocation costs (<E T="03">i.e.,</E>the proportional share of the costs associated with Sprint relocating 5 megahertz of BAS spectrum that will be used by H Block entrants). We believe it is important to provide auction bidders with reasonable certainty as to the range of the reimbursement obligation associated with each license under various auction outcomes. We also believe it is important for Sprint to be fully reimbursed as soon as possible given that Sprint cleared the H Block so H Block licensees will receive unencumbered spectrum. Accordingly, we propose to require H Block licensees to reimburse Sprint based on the gross winning bids of the initial H Block auction. Specifically, we propose that the reimbursement amount owed (“RN”) be determined by dividing the gross winning bid (“GWB”) for an H Block license (<E T="03">i.e.,</E>an individual EA) by the sum of the gross winning bids for all H Block licenses won in the initial auction and then multiplying by $94,875,516. In other words, the cost-sharing formula would read as follows:</P>
        <GPH DEEP="41" SPAN="3">
          <GID>EP08JA13.012</GID>
        </GPH>
        <FP>Because certain EAs, such as for the Gulf of Mexico, have a relative value that is not directly tied to population, our proposal seeks to allow the market to determine the value of each EA license and the associated amount of the reimbursement obligation. However, parties can comment on alternative cost-sharing formulas, including one based on population as described below. We seek comment on our proposals.</FP>

        <P>58. This formula would ensure that Sprint receives full reimbursement after the first auction by effectively apportioning the reimbursement costs associated with any unsold H Block licenses among the winning bidders of<PRTPAGE P="1176"/>H Block licenses in the first auction—with an exception in the event a successful bidder's long-form application is not filed or granted, and a contingency to cover an unlikely scenario. We further propose that winning bidders of H Block licenses in the first auction of this spectrum would not have a right to seek reimbursement from other H Block licensees including for licenses awarded in subsequent auctions. We believe this approach would avoid recordkeeping burdens and potential disputes and that it is appropriate given that—in the event that most licenses are awarded—the reimbursement obligation for an individual license will represent but a fraction of overall reimbursement to Sprint. We seek comment on our proposals including the following contingency: In the unlikely event that licenses covering less than 40 percent of the population of the United States are awarded in the first auction, we propose that winning bidders—in the first auction of this spectrum as well as in subsequent auctions—will be required to timely pay Sprint their<E T="03">pro rata</E>share calculated by dividing the population of the individual EA awarded at auction by the total U.S. population and then multiplying by $94,875,516. This contingent proposal would ensure that Sprint is reimbursed as soon as possible while also protecting winning bidders of H Block licenses from bearing an undue burden of the reimbursement obligation due to Sprint. We seek comment on our proposal.</P>
        <P>59. Alternatively, we specifically seek comment on the relative costs and benefits of adopting a population based cost-sharing formula as the general rule for the H Block. We acknowledge that using a population based approach in all events would offer bidders certainty as to the obligation attached to each license but this approach could also defer Sprint's full reimbursement indefinitely if less than all of the licenses are awarded during the initial auction.</P>
        <P>60. We further propose that winning bidders promptly pay Sprint the amount owed, as calculated pursuant to the formula that we adopt, within 30 days of grant of their long form applications for the licenses. For PCS and AWS-1, and AWS-4, cost sharing obligations are triggered when a licensee proposes to operate a base station in an area cleared of incumbents by another licensee. In this case, rather than Sprint itself benefiting from its band clearing efforts, other entrants in the band will reap the benefits of Sprint's efforts. Accordingly, we find no significant reason to treat Sprint any differently than UTAM and propose that Sprint be fully reimbursed by AWS licensees that will benefit from Sprint's clearing of the H Block. Moreover, as noted above, given the relative fraction of overall reimbursement to Sprint that will be owed by each winning bidder, we believe that it will not disincentivize parties from filing applications or impose a burden on winning bidders to reimburse Sprint within 30 days of the grant of their long-form applications. We seek comment on the above proposals, including the costs and benefits.</P>
        <P>61. Consistent with precedent, we propose a specific date on which the reimbursement obligation adopted above will terminate. In recent instances, the relocation and cost-sharing obligations sunset ten years after the first ET license is issued in the respective band. To the extent that Sprint had not completed the relocation of BAS from the 1990-2025 MHz band, BAS operations in the band would have become secondary after December 9, 2013. However, in this instance, we do not believe that the public interest would be served by adopting December 9, 2013 as the sunset date for terminating the requirement that H Block licensees collectively reimburse Sprint for one-seventh of the BAS relocation costs. Rather, we propose a sunset date for the cost-sharing obligations of H Block licensees to Sprint that is ten years after the first H Block license is issued in the band. We find that a number of factors support our proposal. As discussed above, Sprint relocated BAS incumbents from the 1995-2000 MHz band, even though H Block licensees and not Sprint itself will reap the benefits of Sprint's relocation of BAS. In addition, the integrated nature of BAS operations required relocations on a market-by-market basis, and such a requirement would have imposed significant costs on individual H Block entrants because isolated, link-by-link relocation was infeasible. It therefore served the public interest for Sprint to undertake the relocation on an integrated, nationwide basis. Because H Block licenses have yet to be auctioned and because interested applicants will be able to calculate their reimbursement obligation to Sprint in bidding on licenses, we do not believe that our proposal imposes a burden on the winning bidders of H Block licenses. We seek comment on our proposed sunset date, including the costs and benefits.</P>
        <HD SOURCE="HD2">E. Regulatory Issues; Licensing and Operating Rules</HD>
        <P>62. We are proposing licensing and operating rules that will provide H Block licensees with the flexibility to provide any fixed or mobile service that is consistent with the allocations for this spectrum. Specifically, we are seeking comment on the appropriate license term, criteria for renewal, and other licensing and operating rules pertaining to the H Block. In addition, we seek comment on the potential impact of all of our proposals on competition. In addressing these issues, commenters should discuss the costs and benefits associated with these proposals and any alternative that commenters propose.</P>
        <HD SOURCE="HD3">1. Regulatory Status</HD>
        <P>63. We propose to apply the regulatory status provisions of § 27.10 of the Commission's rules to licensees in the H Block. The Commission's current mobile service license application requires an applicant for mobile services to identify the regulatory status of the service(s) it intends to provide because service offerings may bear on eligibility and other statutory and regulatory requirements. Under part 27, the Commission permits applicants who may wish to provide both common carrier and non-common carrier services (or to switch between them) under a single license to request status as both a common carrier and a non-common carrier. Thus, a part 27 applicant is not required to choose between providing common carrier and non-common carrier services. We propose to adopt this same approach here. Licensees in the H Block would be able to provide all allowable services anywhere within their licensed area at any time, consistent with their regulatory status. We believe that this approach is likely to achieve efficiencies in the licensing and administrative process, and provide flexibility to the marketplace. We seek comment on the appropriate licensing approach and ask that commenters discuss the costs and benefits of their proposed licensing approach.</P>

        <P>64. We further propose that applicants and licensees in the H Block be required to indicate a regulatory status for any services they choose to provide. Apart from this designation of regulatory status, we do not propose to require applicants to describe the services they seek to provide. We caution potential applicants that an election to provide service on a common carrier basis typically requires that the elements of common carriage be present; otherwise the applicant must choose non-common carrier status. If potential applicants are<PRTPAGE P="1177"/>unsure of the nature of their services and their classification as common carrier services, they may submit a petition with their applications, or at any time, requesting clarification and including service descriptions for that purpose. We propose to apply this framework to H Block licensees and seek comment on this proposal, including the costs and benefits of this proposal.</P>
        <P>65. We also propose that if a licensee were to change the service or services it offers such that it would be inconsistent with its regulatory status, the licensee must notify the Commission. A change in a licensee's regulatory status would not require prior Commission authorization, provided the licensee was in compliance with the foreign ownership requirements of section 310(b) of the Communications Act that would apply as a result of the change, consistent with the Commission's rules for AWS-1 spectrum. Consistent with our part 27 rules, we propose to require licensees to file the notification within 30 days of a change made without the need for prior Commission approval, except that a different time period may apply where the change results in the discontinuance, reduction, or impairment of the existing service. We seek comment on this proposal, including the costs and benefits.</P>
        <HD SOURCE="HD3">2. Ownership Restrictions</HD>
        <HD SOURCE="HD3">a. Foreign Ownership Reporting</HD>
        <P>66. We propose to apply the provisions of § 27.12 of the Commission's rules to applicants for licenses in the H Block. Section 27.12 implements section 310 of the Communications Act, including foreign ownership and citizenship requirements that restrict the issuance of licenses to certain applicants. An applicant requesting authorization to provide services in this band other than broadcast, common carrier, aeronautical en route, and aeronautical fixed services would be subject to the restrictions in section 310(a), but not to the additional restrictions in section 310(b). An applicant requesting authorization for broadcast, common carrier, aeronautical en route, or aeronautical fixed services would be subject to both sections 310(a) and 310(b). We do not believe that applicants for this band should be subject to different obligations in reporting their foreign ownership based on the type of service authorization requested in the application. Consequently, we propose to require all applicants to provide the same foreign ownership information, which covers both sections 310(a) and 310(b), regardless of which service they propose to provide in the band. We note, however, that we would be unlikely to deny a license to an applicant requesting to provide exclusively services that are not subject to section 310(b), solely because its foreign ownership would disqualify it from receiving a license if the applicant had applied for authority to provide such services. However, if any such licensee later desires to provide any services that are subject to the restrictions in section 310(b) we would require the licensee to apply to the Commission for an amended license, and we would consider issues related to foreign ownership at that time. We request comment on this proposal, including any costs and benefits.</P>
        <HD SOURCE="HD3">b. Eligibility and Mobile Spectrum Holding Policies</HD>
        <P>67. We propose to adopt an open eligibility standard for the H Block. We believe that adopting such a standard should encourage efforts to develop new technologies, products and services, while helping to ensure efficient use of this spectrum. An open eligibility standard is consistent with the Commission's past practice for mobile wireless spectrum allocations, as well as with section 6404 of the Spectrum Act. We seek comment on our open eligibility approach.</P>

        <P>68. We note that an open eligibility approach would not affect citizenship, character, or other generally applicable qualifications that may apply under our rules. Additionally, section 6004 of the Spectrum Act restricts participation in auctions required under the Spectrum Act, which includes the H Block, by “person[s] who [have] been, for reasons of national security, barred by any agency of the Federal Government from bidding on a contract, participating in an auction, or receiving a grant.” We seek comment on our proposal to address this issue in the competitive bidding procedures section below. Further, as the Commission observed in the<E T="03">Incentive Auction NPRM,</E>Expanding the Economic and Innovation Opportunities of Spectrum Through Incentive Auctions, 77 FR 69934 (Nov. 21, 2012) (<E T="03">Incentive Auction NPRM</E>), section 6004 does not address eligibility to acquire licenses on the secondary market from the initial or subsequent licensee. We seek comment on whether section 6004 permits or requires the Commission to restrict eligibility of the persons described therein to acquire licenses in the secondary market, and whether and to what extent such restriction is consistent with other provisions of the Communications Act. If such restrictions should be implemented, should we do so by requiring certifications in applications similar to those required under our rules for enforcement of the Anti-Drug Abuse Act of 1988? Would it be permissible and appropriate to address such situations on a case-by-case basis in light of the specific facts and circumstances? Should we apply the same attribution rules in doing so, where the relevant person is not the sole owner of the proposed licensee?</P>
        <P>69. We seek comment generally on whether and how to address any mobile spectrum holdings issues involving H Block spectrum in order to meet our statutory requirements and our goals for the H Block. Section 309(j)(3)(B) of the Communications Act provides that in designing systems of competitive bidding, the Commission shall “promot[e] economic opportunity and competition and ensur[e] that new and innovative technologies are readily accessible to the American people by avoiding excessive concentration of licenses.” More recently, section 6404 of the Spectrum Act recognizes the Commission's authority “to adopt and enforce rules of general applicability, including rules concerning spectrum aggregation that promote competition.” We note that we recently initiated a proceeding to revisit the mobile spectrum holdings policies that apply to both transactions and auctions. In the past, the Commission has sought comment on these issues with respect to particular spectrum bands prior to auctioning spectrum licenses.</P>
        <P>70. We seek comment on whether the acquisition of H Block spectrum should be subject to the same general mobile spectrum holding policies applicable to frequency bands that the Commission has determined to be available and suitable for wireless services. Alternatively, depending on the specific rules and requirements that apply to H Block spectrum, should we distinguish H Block spectrum for purposes of evaluating mobile spectrum holdings? Commenters should discuss and quantify any costs and benefits associated with any proposals on the applicability of spectrum holdings policies to H Block spectrum.</P>
        <HD SOURCE="HD3">3. License Term, Performance Requirements, Renewal Criteria, Permanent Discontinuance of Operations</HD>
        <HD SOURCE="HD3">a. License Term</HD>

        <P>71. We propose to establish a 10-year term for licenses for the H Block. The Communications Act does not specify a term limit for AWS band licenses. The<PRTPAGE P="1178"/>Commission has adopted 10-year license terms for most wireless radio services licenses. To maintain this consistency among wireless services, in the<E T="03">AWS-2 NPRM,</E>the Commission proposed that H Block licenses have a term of 10 years. We continue to believe that a 10-year license term is appropriate, and consequently propose, a 10 year license term for the H Block spectrum. We seek comment on this proposal, including any costs and benefits of the proposal. In addition, we invite commenters to submit alternate proposals for the appropriate license term, which should similarly include a discussion on the costs and benefits.</P>
        <P>72. Under our license term proposal, if a license in these bands is partitioned or disaggregated, any partitionee or disaggregatee would be authorized to hold its license for the remainder of the partitioner's or disaggregator's original license term. This approach is similar to the partitioning provisions the Commission adopted for BRS, for broadband PCS licensees, for the 700 MHz band licensees, and for AWS-1 licenses at 1710-1755 MHz and 2110-2155 MHz, and AWS-4. We emphasize that nothing in our proposal is intended to enable a licensee, by partitioning or disaggregating the license, to confer greater rights than it was awarded under the terms of its license grant. Similarly, nothing in our proposal is intended to enable any partitionee or disaggregatee to obtain rights in excess of those previously possessed by the underlying licensee. We seek comment on these proposals, including the cost and benefits thereof.</P>
        <HD SOURCE="HD3">b. Performance Requirements</HD>

        <P>73. The Commission establishes performance requirements to promote the efficient deployment of wireless services, including to rural areas, and ensure that spectrum is used. Over the years, the Commission has applied different performance and construction requirements to different spectrum bands. For example, within four (4) years, an AWS-4 licensee must provide reliable terrestrial signal coverage and offer terrestrial service to at least forty (40) percent of its total AWS-4 population. Within seven (7) years, an AWS-4 licensee must provide reliable terrestrial signal coverage and offer terrestrial service to at least seventy (70) percent of the population in each of its license areas. Similarly, for licensees operating in the 2.3 GHz Wireless Communications Services (WCS) band, the Commission adopted performance requirements that included a population-based construction requirements (40 percent of the license area's population within four (4) years and 75 percent within six-and-a-half (6.5) years) and reporting requirements. In the<E T="03">AWS-2 NPRM,</E>the Commission broadly sought comment on whether it should establish any specific performance requirements in the H Block, including interim performance requirements.</P>
        <P>74. Today, we continue to believe that performance requirements play a critical role in ensuring that licensed spectrum does not lie fallow, and now propose to establish the following performance requirements. We seek comment on the following buildout requirements for the H Block:</P>
        <P>• H Block Interim Buildout Requirement: Within four (4) years, an H Block licensee shall provide signal coverage and offer service to at least forty (40) percent of the population in each of its license areas.</P>

        <P>• H Block Final Buildout Requirement: By the end of the license term,<E T="03">i.e.,</E>within ten (10) years, an H Block licensee shall provide signal coverage and offer service to at least seventy (70) percent of the population in each of its license areas.</P>
        <P>75. We propose these performance requirements in an effort to foster deployment expeditiously in the H Block for the provision of wireless, terrestrial broadband service, and to enable the Commission to take appropriate corrective action should such deployment fail to occur. Specifically, the interim benchmark at four years would ensure that a licensee begins deploying facilities quickly, thereby evidencing meaningful utilization of the spectrum. At the same time, by proposing a relatively low population threshold in the interim benchmark, we acknowledge that large-scale network deployment may ramp up over time as equipment becomes available and a customer base is established. In addition, by proposing a final buildout requirement timeline of ten years, we believe we allow a reasonable amount of time for any H Block licensee to attain nationwide scale.</P>
        <P>76. We seek comment on these proposed buildout requirements. We encourage comment on whether our proposals represent the appropriate balance between requirements that are too low as to not result in meaningful buildout and those that would be so high as to be unattainable. We also seek comment on whether other benchmarks represent more appropriate requirements? Commenters should discuss and quantify how any supported buildout requirements will affect investment and innovation as well as discuss and quantify other costs and benefits associated with the proposal.</P>
        <P>77.<E T="03">Agreements between H Block and AWS-4 licensees.</E>In the<E T="03">AWS-4 Report and Order,</E>we permit AWS-4 licensees to enter into private operator-to-operator agreements with all 1995-2000 MHz licensees to so that AWS-4 operations above 2000 MHz may have an OOBE level in excess of 70 + 10 log<E T="52">10</E>(P) dB into the 1995-2000 MHz band. In the event that an AWS-4 licensee reaches such an agreement with all 1995-2000 MHz licensees, should the H Block licensees' performance requirements be reduced or eliminated because accepting a higher OOBE level increases the use of the 2000-2005 MHz band? Implementing such an approach would enable a market-based solution for AWS-4 licensees who seek to remove technical rules designed to protect the H Block, by allowing them to acquire H Block licenses at auction (or, later, on the secondary market) and prioritize deployment of AWS-4 over H Block.</P>
        <P>78.<E T="03">Penalties for Failure to Meet Construction Requirements.</E>Along with construction benchmarks, we seek to adopt meaningful and enforceable consequences, or penalties, for failing to meet the benchmarks. Building on what we have learned from other bands and considering the unique characteristics of the H Block, we propose and seek comment, including on the costs and benefits, of the following penalties in the event an H Block licensee fails to satisfy its buildout requirements:</P>
        <P>• In the event an H Block licensee fails to meet the H Block Interim Buildout Requirement in its license area, the term of the license shall be reduced by two years.</P>
        <P>• In the event an H Block licensee fails to meet the H Block Final Buildout Requirement in its license area, the H Block license for each license area in which it fails to meet the buildout requirement shall terminate automatically without Commission action.</P>
        <P>79. We further propose that, in the event a licensee's authority to operate terminates, the licensee's spectrum rights would become available for reassignment pursuant to the competitive bidding provisions of section 309(j). Further, consistent with the Commission's rules for other spectrum bands, including AWS-1 and the Broadband Radio Service, we propose that any H Block licensee who forfeits its license for failure to meet its performance requirements would be precluded from regaining the license.</P>
        <P>80.<E T="03">Compliance Procedures.</E>Consistent with § 1.946(d) of the Commission's rules, we propose to<PRTPAGE P="1179"/>require H Block licensees to demonstrate compliance with the performance requirements by filing a construction notification within 15 days of the relevant milestone certifying that they have met the applicable performance benchmark. Further, we propose that each construction notification include electronic coverage maps and supporting documentation, which must be truthful and accurate and must not omit material information that is necessary for the Commission to determine compliance with its performance requirements.</P>
        <P>81. Electronic coverage maps must accurately depict the boundaries of each license area in the licensee's service territory. If a licensee does not provide reliable signal coverage to an entire license area, we propose that its map must accurately depict the boundaries of the area or areas within each license area not being served. Further, we propose that each licensee also must file supporting documentation certifying the type of service it is providing for each licensed area within its service territory and the type of technology used to provide such service. Supporting documentation must include the assumptions used to create the coverage maps, including the propagation model and the signal strength necessary to provide reliable service with the licensee's technology.</P>
        <HD SOURCE="HD3">c. Renewal Criteria</HD>

        <P>82. Pursuant to section 308(b) of the Communications Act, the Commission may require renewal applicants to “set forth such facts as the Commission by regulation may prescribe as to the citizenship, character, and financial, technical, and other qualifications of the applicant to operate the station” as well as “such other information as it may require.” We propose to adopt H Block license renewal requirements consistent with those adopted in the<E T="03">700 MHz First Report and Order</E>and<E T="03">the AWS-4 Report and Order,</E>which form the basis of the renewal paradigm proposed in our<E T="03">Wireless Radio Services Renewal NPRM. See Service Rules for the 698-746, 747-762 and 777-792 MHz Bands,</E>72 FR 24238 (May 2, 2007) (<E T="03">700 MHz First Report and Order</E>);<E T="03">AWS-4 Report and Order; Amendment of parts 1, 22, 24, 27, 74, 80, 90, 95, and 101 To Establish Uniform License Renewal, Discontinuance of Operation, and Geographic Partitioning and Spectrum Disaggregation Rules and Policies for Certain Wireless Radio Services,</E>75 FR 38959 (July 7, 2010) (<E T="03">WRS Renewal NPRM and Order</E>). We emphasize that, as the Commission made clear in these proceedings, a licensee's performance showing and its renewal showing are two distinct showings. A performance showing provides a snapshot in time of the level of a licensee's service, while a renewal showing provides information regarding the level and types of service provided over the entire license term.</P>

        <P>83. We propose that applicants for renewal of H Block licenses file a “renewal showing,” in which they demonstrate that they have provided, and are continuing to provide, service to the public, and that they are compliant with the Communications Act and the Commission's rules and policies. In the<E T="03">700 MHz First Report and Order,</E>the Commission explained that in the renewal context, the Commission considers “a variety of factors including the level and quality of service, whether service was ever interrupted or discontinued, whether service has been provided to rural areas, and any other factors associated with a licensee's level of service to the public.” As we adopted in the<E T="03">AWS-4 Report and Order,</E>we also propose to consider the extent to which service is provided to qualifying tribal lands. We propose that these same factors should be considered when evaluating renewal showings for the H Block and seek comment on this approach. Commenters should discuss and quantify the costs and benefits of this approach.</P>
        <P>84. As explained above, today we are proposing that H Block licensees meet four and ten-year performance obligations. We therefore seek comment on whether the public interest would be served by awarding H Block licensees renewal expectancies where they maintain the level of service demonstrated at the ten year performance benchmark through the end of their license term, provided that they have otherwise complied with the Communications Act and the Commission's rules and policies during their license term. We also seek comment on whether H Block licensees should obtain a renewal expectancy for subsequent license terms, if they continue to provide at least the level of service demonstrated at the ten year performance benchmark through the end of any subsequent license terms. Commenters should discuss and quantify the costs and benefits of this approach.</P>
        <P>85. Finally, consistent with the<E T="03">AWS-4 Report and Order,</E>the<E T="03">700 MHz First Report and Order</E>and the<E T="03">WRS Renewals NPRM and Order,</E>we propose to prohibit the filing of mutually exclusive renewal applications, and that if a license is not renewed, the associated spectrum would be returned to the Commission for reassignment. We seek comment on these proposals, including on the associated costs and benefits.</P>
        <HD SOURCE="HD3">d. Permanent Discontinuance of Operations</HD>
        <P>86. We also request comment on the Commission's rules governing the permanent discontinuance of operations, which are intended to afford licensees operational flexibility to use their spectrum efficiently while ensuring that spectrum does not lay idle for extended periods. Under § 1.955(a)(3) of the Commission's rules, an authorization will automatically terminate, without specific Commission action, if service is “permanently discontinued.” For the H Block, we propose to define “permanently discontinued” as a period of 180 consecutive days during which a licensee does not operate and does not serve at least one subscriber that is not affiliated with, controlled by, or related to the provider. We believe this definition strikes an appropriate balance between our twin goals of providing licensees operational flexibility while ensuring that spectrum does not lie fallow. Licensees would not be subject to this requirement until the date of the first performance requirement benchmark, which is proposed as 4 years from the license grant, so they will have adequate time to construct their network. In addition, consistent with § 1.955(a)(3) of the Commission's rules, we propose that, if an H Block licensee permanently discontinues service, the licensee must notify the Commission of the discontinuance within 10 days by filing FCC Form 601 or 605 and requesting license cancellation. An authorization will automatically terminate without specific Commission action if service is permanently discontinued even if a licensee fails to file the required form. We seek comment on these proposals, including the associated costs and benefits.</P>
        <HD SOURCE="HD3">4. Secondary Markets</HD>
        <HD SOURCE="HD3">a. Partitioning and Disaggregation</HD>

        <P>87. The Commission's part 27 rules generally allow for geographic partitioning and spectrum disaggregation. Geographic partitioning refers to the assignment of geographic portions of a license to another licensee along geopolitical or other boundaries. Spectrum disaggregation refers to the assignment of discrete amounts of spectrum under the license to another entity. Disaggregation allows for multiple transmitters in the same geographic area operated by different companies on adjacent frequencies in<PRTPAGE P="1180"/>the same band. As the Commission noted when first establishing partitioning and disaggregation rules, allowing such flexibility could facilitate the efficient use of spectrum by enabling licensees to make offerings directly responsive to market demands for particular types of services, increasing competition by allowing market entry by new entrants, and expediting provision of services that might not otherwise be provided in the near term.</P>
        <P>88. We propose to permit partitioning and disaggregation by licensees in the H Block. To ensure that the public interest would be served if partitioning or disaggregation is allowed, we propose requiring each H Block licensee that is a party to a partitioning, disaggregation or combination of both to independently meet the applicable performance and renewal requirements. We believe this approach would facilitate efficient spectrum use, while enabling service providers to configure geographic area licenses and spectrum blocks to meet their operational needs. We seek comment on these proposals. Commenters should discuss and quantify the costs and benefits of these proposals with respect to competition, innovation, and investment.</P>
        <P>89. We also seek comment on whether the Commission should adopt additional or different mechanisms to encourage partitioning and/or disaggregation of H Block spectrum and the extent to which such policies ultimately may promote more service, especially in rural areas. Commenters should discuss and quantify the costs and benefits of promoting more service using mechanisms to encourage partitioning and disaggregation of H Block spectrum, including the effects of the proposal.</P>
        <HD SOURCE="HD3">b. Spectrum Leasing</HD>
        <P>90. In 2003, in order to promote more efficient use of terrestrial wireless spectrum through secondary market transactions, while also eliminating regulatory uncertainty, the Commission adopted a comprehensive set of policies and rules to govern spectrum-leasing arrangements between terrestrial licensees and spectrum lessees. These policies and rules enable terrestrially-based Wireless Radio Service licensees holding “exclusive use” spectrum rights to lease some or all of the spectrum usage rights associated with their licenses to third party spectrum lessees, which then are permitted to provide wireless services consistent with the underlying license authorization. Through these actions, the Commission sought to promote more efficient, innovative, and dynamic use of the terrestrial spectrum, expand the scope of available wireless services and devices, enhance economic opportunities for accessing spectrum, and promote competition among terrestrial wireless service providers. In 2004, the Commission built upon this spectrum leasing framework by establishing immediate approval procedures for certain categories of terrestrial spectrum leasing arrangements and extending the spectrum leasing policies to additional Wireless Radio Services.</P>
        <P>91. We propose that the spectrum leasing policies and rules established in those proceedings be applied to the H Block in the same manner that those policies apply to other part 27 services. We seek comment on this proposal. Commenters should discuss the effects on competition, innovation and investment, and on extending our secondary spectrum leasing policies and rules to the H Block.</P>
        <HD SOURCE="HD3">5. Other Operating Requirements</HD>
        <P>92. Even though licenses in the H Block may be issued pursuant to one rule part, licensees in this band may be required to comply with rules contained in other parts of the Commission's rules by virtue of the particular services they provide. For example:</P>
        <P>• Applicants and licensees would be subject to the application filing procedures for the Universal Licensing System, set forth in part 1 of our rules.</P>
        <P>• Licensees would be required to comply with the practices and procedures listed in part 1 of our rules for license applications, adjudicatory proceedings, etc.</P>
        <P>• Licensees would be required to comply with the Commission's environmental provisions, including § 1.1307.</P>
        <P>• Licensees would be required to comply with the antenna structure provisions of part 17 of our rules.</P>
        <P>• To the extent a licensee provides a Commercial Mobile Radio Service, such service would be subject to the provisions of part 20 of the Commission's rules, including 911/E911 and hearing aid-compatibility requirements, along with the provisions in the rule part under which the license was issued. Part 20 applies to all CMRS providers, even though the stations may be licensed under other parts of our rules.</P>
        <P>• To the extent a licensee provides interconnected VoIP services, the licensee would be subject to the E911 service requirements set forth in part 9 of our rules.</P>

        <P>• The application of general provisions of parts 22, 24, 27, or 101 would include rules related to equal employment opportunity,<E T="03">etc.</E>
        </P>
        <P>93. We seek comment on whether we need to modify any of these rules to ensure that H Block licensees are covered under the necessary provisions. We seek comment on applying these rules to the H Block spectrum and specifically on any rules that would be affected by our proposal to apply elements of the framework of these parts, whether separately or in conjunction with other requirements. What are the potential problems that may be associated with the Commission's adoption of any of these potential requirements, and how do they compare to the potential benefits?</P>
        <HD SOURCE="HD3">6. Facilitating Access to Spectrum and the Provision of Service to Tribal Lands</HD>
        <P>94. The Commission currently has under consideration various provisions and policies intended to promote greater use of spectrum over Tribal lands. We propose to extend any rules and policies adopted in that proceeding to any licenses that may be issued through competitive bidding in this proceeding. We seek comment on this proposal, including any costs and benefits.</P>
        <HD SOURCE="HD2">F. Procedures for Any H Block Licenses Subject to Assignment by Competitive Bidding</HD>
        <P>95. As discussed above, if we adopt a geographic area licensing scheme for the 1915-1920 MHz and 1995-2000 MHz bands, we will resolve mutually exclusive applications through competitive bidding, consistent with our statutory mandate.</P>
        <HD SOURCE="HD3">1. Application of Part 1 Competitive Bidding Rules</HD>

        <P>96. We propose that the Commission would conduct any auction for H Block licenses in conformity with the general competitive bidding rules set forth in part 1, subpart Q, of the Commission's rules, and substantially consistent with the competitive 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 for its part 1 general competitive bidding rules 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<PRTPAGE P="1181"/>minimum opening bids and/or reserve prices, would be determined by the Wireless Telecommunications Bureau pursuant to its delegated authority. We seek comment on this approach, including the costs and benefits of this approach. We also seek comment on whether any of our part 1 rules would be inappropriate or should be modified for an auction of licenses in the H Block.</P>
        <HD SOURCE="HD3">2. Revision to Part 1 Certification Procedures</HD>
        <P>97. Section 6004 of the Spectrum Act prohibits “a person who has been, for reasons of national security, barred by any agency of the Federal Government from bidding on a contract, participating in an auction, or receiving a grant” from participating in a system of competitive bidding under section 309(j) required to be conducted under Title VI of the Spectrum Act. Accordingly, we propose to require that an auction applicant certify, under penalty of perjury, that it and all of the related individuals and entities required to be disclosed on the short-form application are not such persons. For purposes of this certification, we propose to define “person” as an individual, partnership, association, joint-stock company, trust, or corporation. We also propose to define “reasons of national security” to mean matters relating to the national defense and foreign relations of the United States. Our existing rules also include various certifications that a party must make in any application to participate in competitive bidding. As with other required certifications, failure to include the required certification by the applicable filing deadline would render the application unacceptable for filing, and the application would be dismissed with prejudice. We seek comment on this proposal.</P>
        <HD SOURCE="HD3">3. Small Business Provisions for Geographic Area Licenses</HD>
        <P>98. 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 Communications 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 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 this mandate is through the award of bidding credits to small businesses.</P>
        <P>99. The Commission has previously 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. Further, the Commission, while standardizing many auction rules, has determined that it would continue a service-by-service approach to defining small businesses.</P>

        <P>100. In the event that the Commission assigns exclusive geographic area licenses for the H Block, we believe that this spectrum would be employed for purposes similar to those for which the AWS-1 band is used. We therefore propose to establish the same small business size standards and associated bidding credits for the H Block as the Commission adopted for the AWS-1 band. We note that these small business size standards and associated bidding credits were proposed for the AWS-1 band because of the similarities between the AWS-1 service and the broadband PCS service and the Commission followed this approach when proposing small business size standards and associated bidding credits in the<E T="03">AWS 2 NPRM.</E>Thus, we propose to define a small business as an entity with average gross revenues for the preceding three years not exceeding $40 million, and a very small business as an entity with average gross revenues for the preceding three years not exceeding $15 million. We seek comment on this proposal, including the costs and benefits of the proposal.</P>
        <P>101. We propose to provide small businesses with a bidding credit of 15 percent and very small businesses with a bidding credit of 25 percent, as set forth in the standardized schedule in part 1 of our rules. We seek comment on the use of these standards and associated bidding credits, with particular focus on the appropriate definitions of small businesses and very small businesses as they may relate to the size of the geographic area to be served and the spectrum allocated to each license. Commenters should discuss and quantify any costs or benefits associated with these standards and associated bidding credits as they relate to the proposed geographic areas. In discussing these issues, commenters are requested to address and quantify the expected capital requirements for services in these bands and other characteristics of the service. Commenters are also invited to use comparisons with other services for which the Commission has already established auction procedures as a basis for their comments and any quantification of costs and benefits regarding the appropriate small business size standards.</P>
        <P>102. In establishing the criteria for small business bidding credits, we acknowledge the difficulty in accurately predicting the market forces that will exist at the time these frequencies are licensed. Thus, our forecasts of types of services that will be offered over these bands may require adjustment depending upon ongoing technological developments and changes in market conditions.</P>
        <P>103. We seek comment on whether the small business provisions we propose today are sufficient to promote participation by businesses owned by minorities and women, as well as rural telephone companies. To the extent that commenters propose additional provisions to ensure participation by minority-owned or women-owned businesses, they should address how such provisions should be crafted to meet the relevant standards of judicial review.</P>
        <P>104. In addition, we note that under our part 1 rules, a winning bidder for a market will be eligible to receive a bidding credit for serving a qualifying tribal land within that market, provided that it complies with the applicable competitive bidding rules. The Commission currently has under consideration various provisions and policies intended to promote greater use of spectrum over tribal lands. We propose to extend any rules and policies adopted in that proceeding to any H Block licenses that may be assigned through competitive bidding. We seek comment on this proposal.</P>
        <HD SOURCE="HD1">III. Procedural Matters</HD>
        <HD SOURCE="HD2">A. Ex Parte Presentations</HD>
        <P>105. The proceedings this<E T="03">Notice of Proposed Rulemaking</E>initiate 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<PRTPAGE P="1182"/>the meeting at which the<E T="03">ex parte</E>presentation was made, and (2) summarize all data presented and arguments made during the presentation. If the presentation consisted in whole or in part of the presentation of data or arguments already reflected in the presenter's written comments, memoranda or other filings in the proceeding, the presenter may provide citations to such data or arguments in his or her prior comments, memoranda, or other filings (specifying the relevant page and/or paragraph numbers where such data or arguments can be found) in lieu of summarizing them in the memorandum. Documents shown or given to Commission staff during<E T="03">ex parte</E>meetings are deemed to be written<E T="03">ex parte</E>presentations and must be filed consistent with rule § 1.1206(b). In proceedings governed by rule § 1.49(f) or for which the Commission has made available a method of electronic filing, written<E T="03">ex parte</E>presentations and memoranda summarizing oral<E T="03">ex parte</E>presentations, and all attachments thereto, must be filed through the electronic comment filing system available for that proceeding, and must be filed in their native format (<E T="03">e.g.,</E>.doc, .xml, .ppt, searchable .pdf). Participants in this proceeding should familiarize themselves with the Commission's<E T="03">ex parte</E>rules.</P>
        <HD SOURCE="HD2">B. Initial Regulatory Flexibility Analysis</HD>

        <P>106. As required by the Regulatory Flexibility Act of 1980, as amended (RFA), the Commission has prepared this present 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 this<E T="03">Notice of Proposed Rulemaking (NPRM).</E>Written public comments are requested on this IRFA. Comments must be identified as responses to the IRFA and must be filed by the deadlines specified in the<E T="03">NPRM</E>for comments. The Commission will send a copy of the<E T="03">NPRM,</E>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="HD2">C. Need for, and Objectives of, the Proposed Rules</HD>

        <P>107. Wireless broadband is a key component of economic growth, job creation and global competitiveness because consumers are increasingly using wireless broadband services to assist them in their everyday lives. The explosive growth of wireless broadband services has created increased demand for wireless spectrum, which is expected to continue increasing, despite technological developments that allow for more efficient spectrum use. Unleashing more spectrum for broadband is essential to meeting this demand In this<E T="03">NPRM,</E>we seek to increase the nation's supply of spectrum for mobile broadband by proposing rules for licensed fixed and mobile services, including advanced wireless services (AWS), in the H Block. These service rules would make available 10 MHz of spectrum for flexible use in accordance with the Spectrum Act, without causing harmful interference to PCS licensees. In proposing terrestrial service rules for the band, which include technical rules to protect against harmful interference, licensing rules to establish geographic license areas and spectrum block sizes, and performance requirements to promote robust buildout, we advance toward enabling rapid and efficient deployment in the band. We do so by proposing service, technical, assignment, and licensing rules for this spectrum that generally follow the Commission's part 27 rules that generally govern flexible use terrestrial wireless service—except that in order to protect PCS licenses, our proposed rules are more stringent in certain respects. Overall, these proposals are designed to provide for flexible use of this spectrum by allowing licensees to choose their type of service offerings, to encourage innovation and investment in mobile broadband use in this spectrum, and to provide a stable regulatory environment in which broadband deployment would be able to develop through the application of standard terrestrial wireless rules. The market-oriented licensing framework for these bands would ensure that this spectrum is efficiently utilized and will foster the development of new and innovative technologies and services, as well as encourage the growth and development of broadband services, ultimately leading to greater benefits to consumers.</P>
        <HD SOURCE="HD2">D. Legal Basis</HD>
        <P>108. The proposed action is authorized pursuant to sections 1, 2, 4(i), 201, 301, 302, 303, 307, 308, 309, 310, 316, 319, 324, 332, 333, 1404, and 1451 of the Communications Act of 1934, as amended, 47 U.S.C. 151, 152, 154(i), 201, 301, 302, 303, 307, 308, 309, 310, 316, 319, 324, 332, 333, 1404, and 1451.</P>
        <HD SOURCE="HD2">E. Description and Estimate of the Number of Small Entities to Which the Proposed Rules Will Apply</HD>
        <P>109. 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 and policies, 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>110.<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 that encompass entities that could be directly affected by the proposals under consideration. As of 2009, small businesses represented 99.9% of the 27.5 million businesses in the United States, according to the SBA. Additionally, 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, counties, towns, townships, villages, school districts, or special districts, with a population of less than fifty thousand.” Census Bureau data for 2007 indicate that there were 89,527 governmental jurisdictions in the United States. We estimate that, of this total, as many as 88,761 entities may qualify as “small governmental jurisdictions.” Thus, we estimate that most governmental jurisdictions are small.</P>
        <P>111.<E T="03">Wireless Telecommunications Carriers (except satellite).</E>The<E T="03">NPRM</E>proposes to apply various Commission policies and rules to terrestrial service in the MSS bands. We cannot predict who may in the future become a licensee or lease spectrum for terrestrial use in these bands. In general, any wireless telecommunications provider would be eligible to become an Advanced Wireless Service licensee or lease spectrum from the MSS or AWS<PRTPAGE P="1183"/>licensees. This industry comprises establishments engaged in operating and maintaining switching and transmission facilities to provide communications via the airwaves. Establishments in this industry have spectrum licenses and provide services using that spectrum, such as cellular phone services, paging services, wireless Internet access, and wireless video services. 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. Under the present and prior categories, the SBA has deemed a wireless business to be small if it has 1,500 or fewer employees. For this category, census data for 2007 show that there were 1,383 firms that operated for the entire year. Of this total, 1,368 firms had employment of 999 or fewer employees and 15 had employment of 1000 employees or more. Similarly, according to Commission data, 413 carriers reported that they were engaged in the provision of wireless telephony, including cellular service, Personal Communications Service (PCS), and Specialized Mobile Radio (SMR) Telephony services. Of these, an estimated 261 have 1,500 or fewer employees and 152 have more than 1,500 employees. Consequently, the Commission estimates that approximately half or more of these firms can be considered small. Thus, using available data, we estimate that the majority of wireless firms can be considered small.</P>
        <HD SOURCE="HD2">F. Description of Projected Reporting, Recordkeeping, and Other Compliance Requirements</HD>
        <P>112. This<E T="03">NPRM</E>contains new information collection requirements subject to the Paperwork Reduction Act of 1995 (PRA), Public Law 104-13. It will be submitted to the Office of Management and Budget (OMB) for review under section 3507(d) of the PRA. The projected reporting, recordkeeping, and other compliance requirements resulting from the<E T="03">NPRM</E>will apply to all entities in the same manner. The Commission believes that applying the same rules equally to all entities in this context promotes fairness. The Commission does not believe that the costs and/or administrative burdens associated with the rules will unduly burden small entities. The revisions the Commission adopts should benefit small entities by giving them more information, more flexibility, and more options for gaining access to valuable wireless spectrum.</P>

        <P>113. OMB, the general public, and other Federal agencies are invited to comment on the new or modified information collection requirements contained in this proceeding. In addition, we note that 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 the Commission might further reduce the information collection burden for small business concerns with fewer than 25 employees.</P>
        <HD SOURCE="HD2">G. Steps Taken To Minimize Significant Economic Impact on Small Entities, and Significant Alternatives Considered</HD>
        <P>114. 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 such 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 such small entities.”</P>
        <P>115. The proposal to license the H Block under Economic Areas (EA) geographic size licenses will provide regulatory parity with other AWS bands that are licensed on an EA basis, such as AWS-1 licenses. Additionally, assigning H Block in EA geographic areas would allow H Block licensees to make adjustments to suit their individual needs. EA license areas are small enough to provide spectrum access opportunities for smaller carriers. EA license areas also nest within and may be aggregated up to larger license areas. Depending on the licensing mechanism we adopt, licensees may adjust their geographic coverage through auction or through secondary markets. This proposal should enable H Block providers, or any entities, whether large or small, providing service in other AWS bands to more easily adjust their spectrum to build their networks pursuant to individual business plans.</P>
        <P>116. The technical rules of the<E T="03">NPRM</E>will protect entities operating in nearby spectrum bands from harmful interference, which may include small entities. These technical rules are based on the rules for AWS-1 spectrum, with specific additions or modifications designed to protect broadband PCS services operating in the 1930-1995 MHz band, as well as future services operating in the 2020-2025 MHz band.</P>
        <P>117. The<E T="03">NPRM</E>proposal pertaining to how the H Block licenses will be assigned includes proposals to assist small entities in competitive bidding. Specifically, small entities will benefit from the proposal to provide small businesses with a bidding credit of 15 percent and very small businesses with a bidding credit of 25 percent. Providing small businesses and very small businesses with bidding credits will provide an economic benefit to small entities by making it easier for small entities to acquire spectrum or access to spectrum in these bands.</P>
        <P>118. The<E T="03">NPRM</E>also proposes to provide H Block licensees with the flexibility to provide any fixed or mobile service that is consistent with the allocations for this spectrum, which is consistent with other spectrum allocated or designated for licensed fixed and mobile services,<E T="03">e.g.,</E>AWS-1. The<E T="03">NPRM</E>further proposes to generally license this spectrum under the Commission's market-oriented part 27 rules, except that certain restrictions would apply. These proposals include applying the Commission's secondary market policies and rules to all transactions involving the use of H Block bands for terrestrial services, which will provide greater predictability and regulatory parity with bands licensed for terrestrial mobile broadband service. This proposal should make it easier for H Block providers to enter secondary market arrangements involving terrestrial use of their spectrum. The secondary market rules apply equally to all entities, whether small or large. As a result, we believe that this proposal will provide an economic benefit to small entities by making it easier for entities, whether large or small, to enter into secondary market arrangements for H Block spectrum.</P>
        <HD SOURCE="HD2">H. Federal Rules That May Duplicate, Overlap, or Conflict With the Proposed Rules</HD>
        <P>119. None.</P>
        <HD SOURCE="HD1">IV. Ordering Clauses</HD>

        <P>120. Accordingly, it is ordered, pursuant to sections 1, 2, 4(i), 201, 301, 302, 303, 307, 308, 309, 310, 316, 319, 324, 332, 333, 1404, and 1451 of the Communications Act of 1934, as amended, 47 U.S.C. 151, 152, 154(i), 201, 301, 302, 303, 307, 308, 309, 310, 316, 319, 324, 332, 333, 1404, and 1451, that this<E T="03">Notice of Proposed Rulemaking</E>is hereby adopted.</P>

        <P>121. It is further ordered that notice is hereby given of the proposed<PRTPAGE P="1184"/>regulatory changes described in this notice and that comment is sought on these proposals.</P>
        <P>122. It is further ordered that the Initial Regulatory Flexibility Analysis is adopted.</P>
        <P>123. It is further ordered that the Commission's Consumer and Governmental Affairs Bureau, Reference Information Center, shall send a copy of this Notice, including the Initial Regulatory Flexibility Analysis, to the Chief Counsel for Advocacy of the Small Business Administration.</P>
        <LSTSUB>
          <HD SOURCE="HED">List of Subjects in 47 CFR Parts 1 and 27</HD>
          <P>Communications common carriers, Radio.</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 27 as follows:</P>
        <PART>
          <HD SOURCE="HED">PART 1—PRACTICE AND PROCEDURE</HD>
        </PART>
        <AMDPAR>1. The authority citation for part 1 is revised to read as follows:</AMDPAR>
        <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), 309 and 1404.</P>
        </AUTH>
        
        <AMDPAR>2. Section 1.949 is amended by adding paragraph (c) to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 1.949</SECTNO>
          <SUBJECT>Application for renewal of license.</SUBJECT>
          <STARS/>
          <P>(c)<E T="03">Renewal Showing.</E>An applicant for renewal of a geographic-area authorization in the 1915-1920 MHz and 1995-2000 service bands must make a renewal showing, independent of its performance requirements, as a condition of renewal. The showing must include a detailed description of the applicant's provision of service during the entire license period and address:</P>

          <P>(1) The level and quality of service provided by the applicant (<E T="03">e.g.,</E>the population served, the area served, the number of subscribers, the services offered);</P>
          <P>(2) The date service commenced, whether service was ever interrupted, and the duration of any interruption or outage;</P>
          <P>(3) The extent to which service is provided to rural areas;</P>
          <P>(4) The extent to which service is provided to qualifying tribal land as defined in § 1.2110(f)(3)(i); and</P>
          <P>(5) Any other factors associated with the level of service to the public.</P>
        </SECTION>
        <AMDPAR>3. Section 1.2105 is amended by adding paragraph (a)(2)(xii) to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 1.2105</SECTNO>
          <SUBJECT>Bidding application and certification procedures; prohibition of certain communications.</SUBJECT>
          <P>(a) * * *</P>
          <P>(2) * * *</P>
          <P>(xii) For auctions required to be conducted under Title VI of the Middle Class Tax Relief and Job Creation Act of 2012 (Pub. L. 112-96) the Commission may require certification under penalty of perjury that the applicant and all of the person(s) disclosed under paragraph (a)(2)(ii) of this section are not person(s) who have been, for reasons of national security, barred by any agency of the Federal Government from bidding on a contract, participating in an auction, or receiving a grant. For the purposes of this certification, the term “person” means an individual, partnership, association, joint-stock company, trust, or corporation, and the term “reasons of national security” means matters relating to the national defense and foreign relations of the United States.</P>
          <STARS/>
        </SECTION>
        <PART>
          <HD SOURCE="HED">PART 27—MISCELLANEOUS WIRELESS COMMUNICATIONS SERVICES</HD>
        </PART>
        <AMDPAR>4. The authority citation for part 27 is revised to read as follows:</AMDPAR>
        <AUTH>
          <HD SOURCE="HED">Authority:</HD>
          <P>47 U.S.C. 154, 301, 302, 303, 307, 309, 332, 336, 337, and 1451 unless otherwise noted.</P>
        </AUTH>
        
        <AMDPAR>5. Section 27.1 is amended by adding paragraph (b)(10) to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 27.1</SECTNO>
          <SUBJECT>Basis and purpose.</SUBJECT>
          <STARS/>
          <P>(b) * * *</P>
          <P>(10) 1915-1920 MHz and 1995-2000 MHz.</P>
          <STARS/>
        </SECTION>

        <AMDPAR>6. Section 27.4 is amended by revising the definition of “<E T="03">Advanced wireless service (AWS)”</E>to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 27.4</SECTNO>
          <SUBJECT>Terms and definitions.</SUBJECT>
          <P>
            <E T="03">Advanced wireless service (AWS).</E>A radiocommunication service licensed pursuant to this part for the frequency bands specified in § 27.5(h) or § 27.5(j).</P>
          <STARS/>
        </SECTION>
        <AMDPAR>7. Section 27.5 is amended by adding paragraph (j) to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 27.5</SECTNO>
          <SUBJECT>Frequencies.</SUBJECT>
          <STARS/>
          <P>(j)<E T="03">1915-1920 MHz and 1995-2000 MHz bands.</E>The paired 1915-1920 MHz and 1995-2000 MHz bands are available for assignment on an Economic Area basis.</P>
        </SECTION>
        <AMDPAR>8. Section 27.6 is amended by adding paragraph (i) to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 27.6</SECTNO>
          <SUBJECT>Service areas.</SUBJECT>
          <STARS/>
          <P>(i)<E T="03">1915-1920 MHz and 1995-2000 MHz bands.</E>AWS service areas for the 1915-1920 MHz and 1995-2000 MHz bands are based on Economic Areas (EAs) as defined in paragraph (a) of this section.</P>
        </SECTION>
        <AMDPAR>9. Section 27.13 is amended by adding paragraph (i) to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 27.13</SECTNO>
          <SUBJECT>License period.</SUBJECT>
          <STARS/>
          <P>(i)<E T="03">1915-1920 MHz and 1995-2000 MHz bands.</E>Authorizations for 1915-1920 MHz and 1995-2000 MHz bands will have a term not to exceed ten years from the date of issuance or renewal.</P>
        </SECTION>
        <AMDPAR>10. Section 27. 14 is amended by revising the first sentence of paragraphs (a), (f), and (k), and adding paragraph (q) to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 27.14</SECTNO>
          <SUBJECT>Construction requirements; criteria for renewal.</SUBJECT>
          <P>(a) AWS and WCS licensees, with the exception of WCS licensees holding authorizations for Block A in the 698-704 MHz and 728-734 MHz bands, Block B in the 704-710 MHz and 734-740 MHz bands, Block E in the 722-728 MHz band, Block C, C1, or C2 in the 746-757 MHz and 776-787 MHz bands, Block D in the 758-763 MHz and 788-793 MHz bands, Block A in the 2305-2310 MHz and 2350-2355 MHz bands, Block B in the 2310-2315 MHz and 2355-2360 MHz bands, Block C in the 2315-2320 MHz band, and Block D in the 2345-2350 MHz band, and with the exception of licensees holding AWS authorizations in the 1915-1920 MHz and 1995-2000 MHz bands, must, as a performance requirement, make a showing of “substantial service” in their license area within the prescribed license term set forth in § 27.13. * * *</P>
          <STARS/>
          <P>(f) Comparative renewal proceedings do not apply to WCS licensees holding authorizations for the 698-746 MHz, 747-762 MHz, and 777-792 MHz bands and licensees holding AWS authorizations for the 1915-1920 MHz and 1995-2000 MHz bands. * * *</P>
          <STARS/>
          <P>(k) Licensees holding WCS or AWS authorizations in the spectrum blocks enumerated in paragraphs (g), (h), (i), or (q) of this section, including any licensee that obtained its license pursuant to the procedures set forth in paragraph (j) of this section, shall demonstrate compliance with performance requirements by filing a construction notification with the Commission, within 15 days of the expiration of the applicable benchmark, in accordance with the provisions set forth in § 1.946(d) of this chapter. * * *</P>
          <STARS/>
          <PRTPAGE P="1185"/>
          <P>(q) The following provisions apply to any licensee holding an AWS authorization in the 1915-1920 MHz and 1995-2000 MHz bands (an “H Block licensee”):</P>
          <P>(1) An H Block licensee shall provide signal coverage and offer service within four (4) years from the date of the initial license to at least forty (40) percent of the total population in each service area that it has licensed in the 1915-1920 MHz and 1995-2000 MHz bands (“H Block Interim Buildout Requirement”).</P>
          <P>(2) An H Block licensee shall provide signal coverage and offer service within ten (10) years from the date of the initial license to at least seventy (70) percent of the population in each of its licensed areas in the 1915-1920 MHz and 1995-2000 MHz bands (“H Block Final Buildout Requirement”).</P>
          <P>(3) If an H Block licensee fails to establish that it meets the H Block Interim Buildout Requirement for a particular licensed area, then the H Block Final Buildout Requirement (in this paragraph (q)) and the H Block license term (as set forth in § 27.13) for each license area in which it fails to meet the H Block Interim Buildout Requirement shall be accelerated by two years (from ten to eight years).</P>
          <P>(4) If an H Block licensee fails to establish that it meets the H Block Final Buildout Requirement for a particular licensed areas in the 1915-1920 MHz and 1995-2000 MHz bands, its authorization for each license area in which it fails to meet the H Block Final Buildout Requirement shall terminate automatically without Commission action. The H Block licensee that has its license automatically terminate under paragraph (q) of this subsection will be ineligible to regain it if the Commission makes the license available at a later date.</P>
          <P>(5) To demonstrate compliance with these performance requirements, licensees shall use the most recently available U.S. Census Data at the time of measurement and shall base their measurements of population served on areas no larger than the Census Tract level. The population within a specific Census Tract (or other acceptable identifier) will only be deemed served by the licensee if it provides signal coverage to and offers service within the specific Census Tract (or other acceptable identifier). To the extent the Census Tract (or other acceptable identifier) extends beyond the boundaries of a license area, a licensee with authorizations for such areas may only include the population within the Census Tract (or other acceptable identifier) towards meeting the performance requirement of a single, individual license.</P>
        </SECTION>
        <AMDPAR>11. Section 27.15 is amended by revising the first sentence in paragraph (d)(1)(i); adding paragraph (d)(1)(iii); revising the first sentence in paragraph (d)(2)(i), and adding paragraph (d)(2)(iii) to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 27.15</SECTNO>
          <SUBJECT>Geographic partitioning and spectrum disaggregation.</SUBJECT>
          <STARS/>
          <P>(d) * * *</P>
          <P>(1) * * *</P>
          <P>(i) Except for WCS licensees holding authorizations for Block A in the 698-704 MHz and 728-734 MHz bands, Block B in the 704-710 MHz and 734-740 MHz bands, Block E in the 722-728 MHz band, Blocks C, C1, or C2 in the 746-757 MHz and 776-787 MHz bands, or Block D in the 758-763 MHz and 788-793 MHz bands; and for licensees holding AWS authorizations in the 1915-1920 MHz and 1995-2000 MHz bands; the following rules apply to WCS and AWS licensees holding authorizations for purposes of implementing the construction requirements set forth in § 27.14. * * *</P>
          <STARS/>

          <P>(iii) For licensees holding AWS authorizations in the 1915-1920 MHz and 1995-2000 MHz bands, the following rules apply for purposes of implementing the construction requirements set forth in § 27.14. Each party to a geographic partitioning must individually meet any service-specific performance requirements (<E T="03">i.e.,</E>construction and operation requirements). If a partitioner or partitionee fails to meet any service-specific performance requirements on or before the required date, then the consequences for this failure shall be those enumerated in § 27.14(q).</P>
          <P>(2) * * *</P>
          <P>(i) Except for WCS licensees holding authorizations for Block A in the 698-704 MHz and 728-734 MHz bands, Block B in the 704-710 MHz and 734-740 MHz bands, Block E in the 722-728 MHz band, Blocks C, C1, or C2 in the 746-757 MHz and 776-787 MHz bands, or Block D in the 758-763 MHz and 788-793 MHz bands; and for licensees holding AWS authorizations in 1915-1920 MHz and 1995-2000 MHz bands; the following rules apply to WCS and AWS licensees holding authorizations for purposes of implementing the construction requirements set forth in § 27.14. * * *</P>
          <STARS/>

          <P>(iii) For licensees holding AWS authorizations in the 1915-1920 MHz and 1995-2000 MHz bands, the following rules apply for purposes of implementing the construction requirements set forth in § 27.14. Each party to a spectrum disaggregation must individually meet any service-specific performance requirements (<E T="03">i.e.,</E>construction and operation requirements). If a disaggregator or a disagregatee fails to meet any service-specific performance requirements on or before the required date, then the consequences for this failure shall be those enumerated in § 27.14(q).</P>
        </SECTION>
        <AMDPAR>12. Section 27.17 is added to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 27.17</SECTNO>
          <SUBJECT>Discontinuance of service in the 1915-1920 MHz and 1995-2000 MHz bands.</SUBJECT>
          <P>(a)<E T="03">Termination of Authorization.</E>A licensee's AWS authorization in the 1915-1920 MHz and 1995-2000 MHz bands will automatically terminate, without specific Commission action, without specific Commission action, if it permanently discontinues service after meeting the H Block Interim Buildout Requirement specified in § 27.14.</P>
          <P>(b) Permanent discontinuance of service is defined as 180 consecutive days during which a licensee holding AWS authority in the 1915-1920 MHz and 1995-2000 MHz bands does not operate or, in the case of a commercial mobile radio service provider, does not provide service to at least one subscriber that is not affiliated with, controlled by, or related to the providing carrier.</P>
          <P>(c)<E T="03">Filing Requirements.</E>A licensee of the 1915-1920 MHz and 1995-2000 MHz bands that permanently discontinues service as defined in this section must notify the Commission of the discontinuance within 10 days by filing FCC Form 601 or 605 requesting license cancellation. An authorization will automatically terminate, without specific Commission action, if service is permanently discontinued as defined in this section, even if a licensee fails to file the required form requesting license cancellation.</P>
        </SECTION>
        <AMDPAR>13. Section 27.50 is amended by revising paragraph (d) introductory text, paragraphs (d)(1) and (2) introductory text, and adding paragraph (d)(7), to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 27.50</SECTNO>
          <SUBJECT>Power limits and duty cycle.</SUBJECT>
          <STARS/>
          <P>(d) The following power and antenna height requirements apply to stations transmitting in the 1710-1755 MHz, 2110-2155 MHz, 1915-1920 MHz and 1995-2000 MHz bands:</P>

          <P>(1) The power of each fixed or base station transmitting in the 1995-2000 MHz or the 2110-2155 MHz band and located in any county with population density of 100 or fewer persons per<PRTPAGE P="1186"/>square mile, based upon the most recently available population statistics from the Bureau of the Census, is limited to:</P>
          <STARS/>
          <P>(2) The power of each fixed or base station transmitting in the 1995-2000 MHz or the 2110-2155 MHz band and situated in any geographic location other than that described in paragraph (d)(1) is limited to:</P>
          <STARS/>
          <P>(7) Fixed, mobile and portable (hand-held) stations operating in the 1915-1920 MHz band are limited to 1 Watt EIRP, except that the total power of any portion of an emission that falls within the 1917-1920 MHz band may not exceed 4 milliwatts (6 dBm).</P>
          <STARS/>
        </SECTION>
        <AMDPAR>14. Section 27.53 is amended by revising paragraph (h) to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 27.53</SECTNO>
          <SUBJECT>Emission limits.</SUBJECT>
          <STARS/>
          <P>(h)<E T="03">AWS Emission Limits.</E>(1)<E T="03">General Protection Levels.</E>Except as otherwise specified below, for operations in the 1710-1755 MHz, 2110-2155 MHz, 1915-1920 MHz, and 1995-2000 MHz bands, the power of any emission outside a licensee's frequency block shall be attenuated below the transmitter power (P) by at least 43 + 10 log<E T="52">10</E>(P) dB.</P>
          <P>(2)<E T="03">Additional Protection Levels.</E>Notwithstanding the foregoing paragraph (h)(1) of this section:</P>

          <P>(i) For operations in the 1915-1920 MHz band, the power of any emission above 1930 MHz shall be attenuated below the transmitter power (P) in watts by at least 70 + 10 log<E T="52">10</E>(P) dB.</P>

          <P>(ii) For operations in the 1995-2000 MHz band, the power of any emission above 2005 MHz shall be attenuated below the transmitter power (P) in watts by at least 70 + 10 log<E T="52">10</E>(P) dB.</P>
          <P>(3)<E T="03">Measurement Procedure.</E>
          </P>
          <P>(i) Compliance with this provision is based on the use of measurement instrumentation employing a resolution bandwidth of 1 megahertz or greater. However, in the 1 megahertz bands immediately outside and adjacent to the licensee's frequency block, a resolution bandwidth of at least one percent of the emission bandwidth of the fundamental emission of the transmitter may be employed. The emission bandwidth is defined as the width of the signal between two points, one below the carrier center frequency and one above the carrier center frequency, outside of which all emissions are attenuated at least 26 dB below the transmitter power.</P>
          <P>(ii) When measuring the emission limits, the nominal carrier frequency shall be adjusted as close to the licensee's frequency block edges, both upper and lower, as the design permits.</P>
          <P>(iii) The measurements of emission power can be expressed in peak or average values, provided they are expressed in the same parameters as the transmitter power.</P>
          <STARS/>
        </SECTION>
        <AMDPAR>15. Section 27.55 is amended by revising paragraphs (a)(1) to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 27.55</SECTNO>
          <SUBJECT>Power strength limits.</SUBJECT>
          <P>(a) * * *</P>
          <P>(1) 1995-2000, 2110-2155, 2305-2320, 2345-2360 MHz bands: 47 dBµV/m.</P>
          <STARS/>
        </SECTION>
        <AMDPAR>16. Section 27.57 is amended by revising paragraph (c) to read as follows:</AMDPAR>
        <SECTION>
          <SECTNO>§ 27.57</SECTNO>
          <SUBJECT>International coordination.</SUBJECT>
          <STARS/>
          <P>(c) Operation in the 1710-1755 MHz, 1915-1920 MHz, 1995-2000 MHz and 2110-2155 MHz bands is subject to international agreements with Mexico and Canada.</P>
        </SECTION>
        <AMDPAR>17. Add subpart K to part 27 to read as follows:</AMDPAR>
        <CONTENTS>
          <SUBPART>
            <HD SOURCE="HED">Subpart K—1915-1920 MHz and 1995-2000 MHz</HD>
            <HD SOURCE="HD3">Licensing and Competitive Bidding Provisions</HD>
            <SECHD>Sec.</SECHD>
            <SECTNO>27.1001</SECTNO>
            <SUBJECT>1915-1920 MHz and 1995-2000 MHz bands subject to competitive bidding.</SUBJECT>
            <SECTNO>27.1002</SECTNO>
            <SUBJECT>Reimbursement obligation of AWS licensees at 1915-1920 MHz.</SUBJECT>
            <HD SOURCE="HD3">Reimbursement Obligations of AWS Licensees at 1915-1920 and 1995-2000 MHz</HD>
            <SECHD>Sec.</SECHD>
            <SECTNO>27.1021</SECTNO>
            <SUBJECT>Reimbursement obligation of AWS licensees at 1915-1920 MHz.</SUBJECT>
            <SECTNO>27.1031</SECTNO>
            <SUBJECT>Reimbursement obligation of AWS licensees at 1995-2000 MHz.</SUBJECT>
            <SECTNO>27.1041</SECTNO>
            <SUBJECT>Termination of Cost-Sharing Obligations.</SUBJECT>
          </SUBPART>
        </CONTENTS>
        <HD SOURCE="HD3">Licensing and Competitive Bidding Provisions</HD>
        <SECTION>
          <SECTNO>§ 27.1001</SECTNO>
          <SUBJECT>1915-1920 MHz and 1995-2000 MHz bands subject to competitive bidding.</SUBJECT>
          <P>Mutually exclusive initial applications for 1915-1920 MHz and 1995-2000 MHz band licenses are subject to competitive bidding. The general competitive bidding procedures set forth in 47 CFR part 1, subpart Q will apply unless otherwise provided in this subpart.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 27.1002</SECTNO>
          <SUBJECT>Designated entities in the 1915-1920 MHz and 1995-2000 MHz bands.</SUBJECT>
          <P>Eligibility for small business provisions:</P>
          <P>(a)(1) A small business is an entity that, together with its affiliates, its controlling interests, the affiliates of its controlling interests, and the entities with which it has an attributable material relationship, has average gross revenues not exceeding $40 million for the preceding three years.</P>
          <P>(2) A very small business is an entity that, together with its affiliates, its controlling interests, the affiliates of its controlling interests, and the entities with which it has an attributable material relationship, has average gross revenues not exceeding $15 million for the preceding three years.</P>
          <P>(b)<E T="03">Bidding credits.</E>A winning bidder that qualifies as a small business as defined in this section or a consortium of small businesses may use the bidding credit specified in § 1.2110(f)(2)(iii) of this chapter. A winning bidder that qualifies as a very small business as defined in this section or a consortium of very small businesses may use the bidding credit specified in § 1.2110(f)(2)(ii) of this chapter.</P>
          <HD SOURCE="HD3">Reimbursement Obligations of AWS Licensees at 1915-1920 and 1995-2000 MHz</HD>
        </SECTION>
        <SECTION>
          <SECTNO>§ 27.1021</SECTNO>
          <SUBJECT>Reimbursement obligation of AWS licensees at 1915-1920 MHz.</SUBJECT>

          <P>AWS licensees of the H Block (1915-1920 MHz paired with 1995-2000 MHz) are collectively responsible for reimbursing UTAM, Inc. a<E T="03">pro rata</E>share of the expenses that UTAM, Inc. has incurred from relocating and clearing incumbent Fixed Microwave Service (FS) licensees from the 1910-1930 MHz band. Specifically, within 30 days of grant of its long-form application, AWS licensees in the 1915-1920 MHz band, which constitutes 25 percent of the 1910-1930 MHz band, shall, on a<E T="03">pro rata</E>shared basis as set forth in paragraph (a) in this section reimburse 25 percent of the total relocation costs incurred by UTAM, Inc.</P>

          <P>(a) To the extent that H Block licenses awarded in the first auction for this spectrum cover, collectively, at least forty (40) percent of the nation's population, the amount owed to UTAM, Inc. by the winning bidder of each individual H Block license awarded in the first auction will be determined by dividing the gross winning bid (“GWB”) for each individual H Block license (<E T="03">i.e.,</E>an Economic Area (EA)) by the sum of the gross winning bids for all H Block licenses awarded in the first auction, and then multiplying by $12,629,857.</P>
          <GPH DEEP="41" SPAN="3">
            <PRTPAGE P="1187"/>
            <GID>EP08JA13.013</GID>
          </GPH>
          <P>Except as provided in paragraphs (b) and (c) of this section, an AWS licensee that obtains a license for a market not awarded in the first H Block auction will not have a reimbursement obligation to UTAM, Inc.</P>

          <P>(b) The Commission imposes payment obligations on bidders that withdraw provisionally winning bids during the course of an auction, on those that default on payments due after an auction closes, and on those that are disqualified.<E T="03">See</E>47 CFR 1.2110(f)(2)(i). In the initial auction, a winning bidder of an EA license that is not awarded a license for any reason will be deemed to have triggered a reimbursement obligation to UTAM, Inc. that will be paid to UTAM, Inc. by the licensee acquiring the EA license at reauction. The amount owed to UTAM, Inc. by the licensee acquiring the EA license at reauction will be based on the gross winning bid for the EA license in the initial auction. Accordingly, an applicant at reauction will know with certainty the reimbursement obligation it will owe for each EA license subject to this paragraph (b).</P>
          <P>(c) To the extent that H Block licenses awarded in the first auction for this spectrum cover, collectively, less than forty (40) percent of the nation's population, then the amount owed to UTAM, Inc. shall be more equitably dispersed across all EA licenses based on the relative population of the EA to the population of the United States. Specifically, the amount that the licensee of an individual H Block license must reimburse UTAM, Inc. shall be calculated by dividing the population of the individual BTA by the total U.S. population, and then multiplying by $12,629,857.</P>
          <GPH DEEP="41" SPAN="3">
            <GID>EP08JA13.014</GID>
          </GPH>
          <P>(d) For purposes of compliance with this section, licensees should determine population based on 2000 U.S. Census Data or such other data or measurements that the Wireless Telecommunications Bureau proposes and adopts under the notice and comment process for the auction procedures.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 27.1031</SECTNO>
          <SUBJECT>Reimbursement obligation of AWS licensees at 1995-2000 MHz.</SUBJECT>

          <P>AWS licensees of the H Block (1915-1920 MHz paired with 1995-2000 MHz) are collectively responsible for reimbursing Sprint Nextel, Inc. or a successor in interest to Sprint Nextel, Inc. (Sprint), a<E T="03">pro rata</E>share of the eligible expenses that Sprint has incurred from relocating and clearing Broadcast Auxiliary Service (BAS), Cable Television Relay Service (CARS), and Local Television Transmission Service (LTTS) incumbents from the 1990-2025 MHz band. Specifically, within 30 days of grant of its long-form application, AWS licensees in the 1995-2000 MHz band, which constitutes one-seventh of the 35 megahertz of spectrum at 1990-2025 MHz, shall, on a<E T="03">pro rata</E>shared basis as set forth below in this section reimburse one-seventh of the eligible expenses incurred by Sprint.</P>

          <P>(a) To the extent that H Block licenses awarded in the first auction for this spectrum cover, collectively, at least forty (40) percent of the nation's population, the amount owed to Sprint by the winning bidder of each individual H Block license awarded in the first auction will be determined by dividing the gross winning bid (“GWB”) for each individual H Block license (<E T="03">i.e.,</E>an Economic Area (EA)) by the sum of the gross winning bids for all H Block licenses awarded in the first auction, and then multiplying by $94,875,516.</P>
          <GPH DEEP="41" SPAN="3">
            <GID>EP08JA13.015</GID>
          </GPH>
          <P>Except as provided in paragraphs (b) and (c), an AWS licensee that obtains a license for a market not awarded in the first H Block auction will not have a reimbursement obligation to Sprint.</P>

          <P>(b) The Commission imposes payment obligations on bidders that withdraw provisionally winning bids during the course of an auction, on those that default on payments due after an auction closes, and on those that are disqualified.<E T="03">See</E>47 CFR 1.2110(f)(2)(i). In the first auction, a winning bidder of an EA license that is not awarded a license for any reason will be deemed to have triggered a reimbursement obligation to Sprint that will be paid to Sprint by the licensee acquiring the EA license at reauction. The amount owed to Sprint by the licensee acquiring the EA license at reauction will be based on the gross winning bid for the EA license in the first auction. Accordingly, an applicant at reauction will know with certainty the reimbursement obligation it will owe for each EA license subject to this paragraph (b).</P>
          <P>(c) To the extent that H Block licenses awarded in the first auction for this spectrum cover, collectively, less than forty (40) percent of the nation's population, then the amount owed to Sprint shall be more equitably dispersed across all EA licenses based on the relative population of the EA to the population of the United States. Specifically, the amount that the licensee of an individual H Block license must reimburse Sprint shall be calculated by dividing the population of the individual EA by the total U.S. population, and then multiplying by $94,875,516.</P>
          <GPH DEEP="56" SPAN="3">
            <PRTPAGE P="1188"/>
            <GID>EP08JA13.016</GID>
          </GPH>
          <P>(d) For purposes of compliance with this section, licensees should determine population based on 2000 U.S. Census Data or such other data or measurements that the Wireless Telecommunications Bureau proposes and adopts under the notice and comment process for the auction procedures.</P>
        </SECTION>
        <SECTION>
          <SECTNO>§ 27.1041</SECTNO>
          <SUBJECT>Termination of Cost-Sharing Obligations.</SUBJECT>
          <P>(a) The cost-sharing obligation adopted in this subpart will sunset ten years after the first H Block license is issued in the band.</P>
          <P>(b) An H Block licensee must satisfy in full its payment obligations under this subpart K within thirty days of the grant of its long-form application. The failure to timely satisfy a payment obligation in full prior to the applicable sunset date will not terminate the debt owed or a party's right to collect the debt.</P>
          
        </SECTION>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00157 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6712-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
        <CFR>47 CFR Part 95</CFR>
        <DEPDOC>[GN Docket No. 12-354; FCC 12-148]</DEPDOC>
        <SUBJECT>Commercial Operations in the 3550-3650 MHz Band</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Federal Communications Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Proposed rule.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In this document, the Commission proposes to create a new Citizens Broadband Radio Service under part 95 of its rules for shared small cell use in the 3550-3650 MHz band (3.5 GHz Band). The Commission seeks comment on other techniques that could be used to manage access within the 3.5 GHz band as well as protections for incumbent Department of Defense (DoD) and Fixed Satellite Service (FSS) users. The Commission also seeks comment on how the unique characteristics of small cells may help reduce the need for geographic protections and enable shared access of the 3.5 GHz Band across the widest possible geographic footprint. In addition, the Commission offers a supplemental proposal to integrate the 3650-3700 MHz band within the proposed Citizens Broadband Service, thereby encompassing an additional 50 megahertz of contiguous spectrum. This approach would leverage the benefits of small cell technology to enable widespread broadband access to the 3.5 GHz Band while minimizing the possibility of harmful interference to incumbent DoD and FSS users.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Submit comments on or before February 20, 2013 and reply comments on or before March 22, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>You may submit comments, identified by GN Docket No. 12-354, by any of the following methods:</P>
          <P>•<E T="03">Federal Communications Commission's Web Site: http://fjallfoss.fcc.gov/ecfs2/.</E>Follow the instructions for submitting comments.</P>
          <P>•<E T="03">Mail:</E>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:00 a.m. to 7:00 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. Commercial overnight mail (other than U.S. Postal Service Express Mail and Priority Mail) must be sent to 9300 East Hampton Drive, Capitol Heights, MD 20743. U.S. Postal Service first-class, Express, and Priority mail must be addressed to 445 12th Street SW., Washington DC 20554.</P>
          <P>•<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>

          <P>For detailed instructions for submitting comments and additional information on the rulemaking process, see the<E T="02">SUPPLEMENTARY INFORMATION</E>section of this document.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Paul Powell, Attorney Advisor, Wireless Bureau's Mobility Division, at (202) 744-3597 or<E T="03">Paul.Powell@fcc.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>This is a summary of the Commission's<E T="03">Notice of Proposed Rulemaking and Order</E>(NPRM), in GN Docket No. 12-354, FCC 12-148, adopted and released December 12, 2012. The full text of this document 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, (202)488-5300, facsimile (202) 488-5563, or via email at<E T="03">Fcc@bcpiweb.com.</E>The full text may also be downloaded at: www.fcc.gov. 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">
          <E T="0742">Synopsis of the  NPRM</E>
        </HD>
        <HD SOURCE="HD1">I. Introduction</HD>
        <P>1. With this<E T="03">NPRM,</E>the Federal Communications Commission (Commission) propose to create a new Citizens Broadband Service in the 3550-3650 MHz band (3.5 GHz Band) currently utilized for military and satellite operations, which will promote two major advances that enable more efficient use of radio spectrum: small cells and spectrum sharing. The 3.5 GHz Band was identified by the National Telecommunications and Information Administration (NTIA) for shared federal and non-federal use in the 2010 Fast Track Report.<E T="03">See NTIA, An Assessment of the Near-Term Viability of Accommodating Wireless Broadband Systems et al,</E>at<E T="03">http://www.ntia.doc.gov/files/ntia/publications/fasttrackevaluation_11152010.pdf.</E>Our proposal builds on our experience with spectrum sharing in the television white spaces (TVWS), proposes ideas teed up in our recent Notice of Inquiry on Dynamic Spectrum Access technologies, and broadly reflects recommendations made in a recent report by the President's Council of Advisors on Science and Technology (PCAST).<E T="03">See PCAST, Report to the President: Realizing the Full Potential of Government-Held Spectrum to Spur Economic Growth</E>at<E T="03">http://www.whitehouse.gov/sites/default/files/microsites/ostp/pcast_spectrum_report_final_july_20_2012.pdf.</E>We also seek comment on whether to include under these proposed new, flexible rules the neighboring 3650-3700 MHz band,<PRTPAGE P="1189"/>which is already used for commercial broadband services. Together, these proposals would make up to 150 megahertz of contiguous spectrum available for innovative mobile and fixed wireless broadband services without displacing mission-critical incumbent systems.</P>
        <P>2. Demand for wireless broadband capacity is growing much faster than the availability of new spectrum. While the Commission and the President have outlined a path for nearly doubling the amount of available spectrum for fixed and wireless broadband uses, some experts forecast a need for a thousand-fold increase in wireless capacity by 2020. To meet this demand, future generations of wireless technology and services must continue to increase their yield of bits per hertz per second. Future wireless traffic demands also require new wireless network architectures and new approaches to spectrum management.</P>

        <P>3. The PCAST Report identifies two technological advances as holding great promise for increasing our nation's wireless broadband capabilities. First, increased use of small cell network deployments can multiply wireless capacity within existing spectrum resources.<E T="03">See PCAST Report at vi, 17-20.</E>Second, increased spectrum sharing can make large swaths of otherwise “stovepiped” spectrum—nationwide bands set aside for important, but localized, government and non-government uses—newly available for broadband use. The proposed Citizens Broadband Service would foster the widespread utilization of both of these technological advances and promote the efficient use of the 3.5 GHz Band.</P>
        <P>4. Small cells are low-powered wireless base stations intended to cover targeted indoor or localized outdoor areas ranging in size from homes and offices to stadiums, shopping malls, hospitals, and metropolitan outdoor spaces. Typically, they provide wireless connectivity in areas that present capacity and coverage challenges to traditional wide-area macrocell networks. Small cells can be deployed relatively easily and inexpensively by consumers, enterprise users, and service providers. Networks that incorporate small cell technology can take advantage of greater “reuse” of scarce wireless frequencies, greatly increasing data capacity within the network footprint. For example, deploying ten small cells in a location in place of a single macro cell could result in a tenfold increase in capacity, using the same quantity of spectrum. Small cells can also be used to help fill in coverage gaps created by buildings, tower siting difficulties, and/or challenging terrain.</P>
        <P>5. Spectrum sharing in this context refers to the use of automated techniques to facilitate the coexistence of disparate unaffiliated spectrum dependent systems that would conventionally require separate bands to avoid interference. Such coexistence may happen, for example, by authorizing targeted use of new commercial systems in specific geographical areas where interference into incumbent systems is not a problem. The need to minimize interference risks has caused, over time, much spectrum to be reserved for “high value” systems that protect national security, safety of life, etc. For example, the military may need spectrum for advanced radar systems or hospitals may deploy networks to enable real-time monitoring of patient vital signs. However, many of these uses are highly localized in nature. Therefore, more agile technologies and sharing mechanisms could potentially allow large quantities of special-purpose federal and non-federal spectrum to be used for more general purposes, such as commercial broadband services, on a shared basis.</P>
        <P>6. The 3.5 GHz Band appears to be an ideal band in which to propose small cell deployments and shared spectrum use. The NTIA Fast Track Report identified the 3.5 GHz Band for potential shared federal and non-federal broadband use. Incumbent uses in the band include high powered Department of Defense (DoD) radars as well as non-federal Fixed Satellite Service (FSS) earth stations for receive-only, space-to-earth operations and feeder links. In the adjacent band below 3550 MHz there are high-powered ground and airborne military radars. The Fast Track Report recommended, based on the commercial wireless broadband technology that was assessed, that new commercial uses of the band occur outside of large “exclusion zones.” For this reason, and because of limited signal propagation at 3.5 GHz, the commercial wireless industry has expressed a viewpoint that the 3.5 GHz Band would not be particularly well-suited for macrocell deployment, with some suggesting that it might be more appropriate for fixed wireless or unlicensed use. We agree with the PCAST Report that the perceived disadvantages of the 3.5 GHz Band might be turned into advantages from the standpoint of promoting spectrum sharing and small cell innovation. Such a paradigm could vastly increase the usability of the band for wireless broadband.</P>
        <P>7. We propose to structure the Citizens Broadband Service according to a multi-tiered shared access model that reflects the PCAST recommendation. We propose that the Citizens Broadband Service be managed by a spectrum access system (SAS) incorporating a dynamic database and, potentially, other interference mitigation techniques. The SAS would ensure that Citizens Broadband Service users operate only in areas where they would not cause harmful interference to incumbent users and could also help manage interference protection among different tiers of Citizens Broadband Service users. The three tiers of service would be: (1) Incumbent Access; (2) Priority Access; and (3) General Authorized Access (GAA). We seek comment on this approach. In addition, consistent with the Fast Track Report, we propose to protect existing federal systems operating in the 3.5 GHz Band and seek comment on appropriate allocation models to accomplish the goals set forth in this Notice.</P>
        <P>8. We propose that the Incumbent Access tier would consist solely of authorized federal and grandfathered licensed FSS 3.5 GHz Band users. These Incumbent Access users would be protected from harmful interference from Citizens Broadband Service users through appropriate regulatory and technical means. Citizens Broadband Service users would not be permitted to operate within geographically designated Incumbent Use Zones, which would encompass the geographic area where low-powered small cells could cause harmful interference to incumbent operations. We seek comment on whether the use of small cell technology incorporating lower power levels and other distinguishing technical characteristics compared to higher power cellular architecture systems could significantly reduce the exclusion zones proposed in NTIA's Fast Track Report. Outside of these zones, the SAS would manage Citizens Broadband Service access and would ensure that lower tiered users would not operate in a manner that would cause harmful interference to federal and FSS users in the 3.5 GHz Band.</P>

        <P>9. The Priority Access tier would consist of a portion of the 3.5 GHz Band designated for small cell use by certain critical, quality-of-service dependent users at specific, targeted locations. We seek comment on who these eligible users should be and suggest that they could include hospitals, utilities, state and local governments, and/or other users with a distinct need for reliable, prioritized access to broadband spectrum at specific, localized facilities.<PRTPAGE P="1190"/>We expect that the availability of the Priority Access tier could bring the benefits of mass-market commercial scale to specialized uses and provide a new alternative to dedicated spectrum, which is in short supply. In order to prevent an expectation of quality of service in areas where such an expectation might not be warranted, Priority Access operations would only be permitted in geographic zones with no likelihood of harmful interference from Incumbent Access users and no expectation of harmful interference from Citizens Broadband Service users to Incumbent Access users. Priority Access users would be required to register in the SAS and accorded protection from interference from lower tier users and other Priority Access users within their local facilities.</P>
        <P>10. The General Authorized Access (GAA) tier would be assigned for use by the general public on an opportunistic, non-interfering basis within designated geographic areas. GAA users could include a wide range of residential, business, and others, including wireless telephone and Internet service providers. We propose to authorize GAA use in zones where small cell use would not interfere with incumbent operations. Unlike the Priority Access tier, we propose to allow GAA use in areas where some interference from incumbent operations might be expected. We also propose that GAA users be required to register in the SAS and comply with all applicable technical, regulatory, and enforcement rules to ensure that GAA users avoid causing harmful interference to Incumbent Access and Priority Access users and always accept harmful interference from such users. We also seek comment on whether federal entities could be authorized GAA users. We seek comment on what technologies could be used to enable effective GAA use of the 3.5 GHz Band.</P>
        <P>11. Under our main proposal, users in the Priority Access and GAA tiers would be licensed by rule as Citizens Broadband Service users under part 95 of the Commission's rules. A license-by-rule approach would provide individuals, organizations, and service providers with “automatic” authorization to deploy small cell systems, in much the same way that our Part 15 unlicensed rules have allowed widespread deployment of Wi-Fi access points. In the present context, we believe licensing by rule provides two advantages compared to unlicensed authorization. First, as a licensed service, 3.5 GHz Band operations would enjoy greater interference protection status in the Table of Frequency Allocations consistent with the proposed multi-tiered approach. Second, licensing by rule might allow for a more unified authorization framework for multiple tiers of users that otherwise might fall into different parts of the Commission's rules. We seek comment on whether the proposed framework could be implemented through other regulatory approaches, including through the part 15 unlicensed rules or through geographic area licensing. We also seek comment on the benefits that could accrue to federal users through use of the Citizens Broadband Service.</P>
        <P>12. We also offer a supplemental proposal to integrate the 3650-3700 MHz band within the proposed Citizens Broadband Service, thereby encompassing an additional 50 megahertz of contiguous spectrum. The Commission currently licenses the 3650-3700 MHz band on a non-exclusive basis, with protections for incumbent FSS operations. The 3650-3700 MHz band is used extensively by wireless Internet service providers, among others, to provide commercial broadband service. Expanding the Citizens Broadband Service to include this band could bring benefits of greater spectrum availability and equipment scale economies to current 3650-3700 MHz licensees. Under our proposal, the SAS would authorize existing licensees as GAA users in the larger, combined band, and would authorize higher power levels in less congested areas, provided there is no risk of harmful interference to Incumbent Access or Priority Access operations. This proposal contemplates conversion of the existing non-exclusive licensing framework to the license-by-rule framework proposed herein. We also note that the 3650-3700 MHz band is currently allocated on a primary basis to the federal radiolocation service in three locations. We seek comment on the potential impact of these proposed changes in the use of the 3650-3700 MHz band on these and other incumbent operations.</P>
        <P>13. If implemented, the new Citizens Broadband Service could help address the ongoing capacity shortage and promote new innovations in broadband technology, deployment, and spectrum management while protecting incumbent authorized federal and grandfathered FSS users. In order to develop a comprehensive record on this proposal, we seek comment on a wide range of technical, licensing, and other related issues. To that end, we seek comment on: (1) Appropriate licensing schemes; (2) specific flexible and resilient interference mitigation technologies and techniques that could be implemented by Citizens Broadband Service users; (3) appropriate deployment strategies for Citizens Broadband Service devices; and (4) the SAS dynamic database that is envisioned to manage access to and use of the 3.5 GHz Band. To ensure the development of a comprehensive record, we may release additional notices, analyses, or white papers for comment during the course of this proceeding. Moreover, because this proceeding raises significant novel technical issues with respect to sharing with federal users, we expect to work closely with NTIA and relevant federal agencies to perform necessary further analysis, and we encourage commenters to provide relevant technical input to inform this analysis, where appropriate.</P>
        <P>14.<E T="03">Freeze on New Earth Stations.</E>To preserve the stability of the spectral environment in the 3.5 GHz Band and ensure that opportunities continue to exist for wireless broadband services as proposed in the foregoing Notice, we direct the International Bureau to stop accepting applications in the 3600-3650 MHz band for new earth stations in the fixed-satellite service that are more than 10 statute miles from a licensed earth station's coordinates for the duration of this proceeding. This application freeze is narrowly tailored to ensure a stable spectral ecosystem for the proposed Citizens Broadband Service, while providing reasonable opportunities to obtain suitable real estate for the placement of new FSS earth station facilities near grandfathered earth stations. In light of the limited number of such grandfathered stations, such a freeze is expected to meet the immediate needs of earth station operators without significantly reducing the availability of spectrum for wireless broadband services by prohibiting expansion of new FSS earth stations in the 3600-3650 MHz band segment.</P>

        <P>15. The decision to impose this freeze is procedural in nature, and therefore the freeze is not subject to the notice and comment requirements of the Administrative Procedure Act. Moreover, for the reasons set forth above, in these circumstances there is good cause to find that notice and comment are impractical, unnecessary, and contrary to the public interest because it would undercut the purposes of the freeze. For the same reasons, and in order to avoid undercutting the purposes of the freeze, we find that there is good cause for making the freeze effective as of the release date of this<E T="03">NPRM.</E>
          <PRTPAGE P="1191"/>
        </P>
        <HD SOURCE="HD1">II. Procedural Matters</HD>
        <HD SOURCE="HD2">A. Ex Parte Rules</HD>
        <P>16. The proceeding this<E T="03">NPRM</E>initiates shall be treated as a “permit-but-disclose” proceeding in accordance with the Commission's ex parte rules. Persons making ex parte 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 ex parte presentations are reminded that memoranda summarizing the presentation must (1) list all persons attending or otherwise participating in the meeting at which the ex parte 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 ex parte meetings are deemed to be written ex parte 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 ex parte presentations and memoranda summarizing oral ex parte 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 ex parte rules.</P>

        <P>17. We exempt from the disclosure requirement under our ex parte rules all ex parte presentations made by NTIA or Department of Defense representatives. This<E T="03">NPRM</E>raises significant technical issues implicating federal and non-federal spectrum allocations and users. Staff from NTIA, DoD, and the FCC have engaged in technical discussions in the development of this Notice, and we anticipate these discussions will continue after this<E T="03">NPRM</E>is released. We believe that these discussions will benefit from an open exchange of information between agencies, and may involve sensitive information regarding the strategic federal use of the 3.5 GHz Band. Recognizing the value of federal agency collaboration on the technical issues raised in this Notice, NTIA's shared jurisdiction over the 3.5 GHz Band, the importance of protecting federal users in the 3.5 GHz Band from interference, and the goal of enabling spectrum sharing to help address the ongoing spectrum capacity crunch, we find that this exemption serves the public interest.</P>
        <HD SOURCE="HD2">B. Filing Requirements</HD>
        <P>18. 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. Comments may be filed using: (1) The Commission's Electronic Comment Filing System (ECFS), (2) the Federal Government's eRulemaking Portal, or (3) by filing paper copies.</P>
        <P>•<E T="03">Electronic Filers:</E>Comments may be filed electronically using the Internet by accessing the ECFS:<E T="03">http://www.fcc.gov/cgb/ecfs/</E>or the Federal eRulemaking Portal:<E T="03">http://www.regulations.gov</E>.</P>
        <P>•<E T="03">Paper Filers:</E>Parties who choose to file by paper must file an original and one copy of each filing. If more than one docket or rulemaking number appears in the caption of this proceeding, filers must submit two additional copies for each additional docket or rulemaking number.</P>
        <P>Filings can be sent by hand or messenger delivery, by commercial overnight courier, or by first-class or overnight U.S. Postal Service mail. All filings must be addressed to the Commission's Secretary, Office of the Secretary, Federal Communications Commission.</P>
        <P>• All hand-delivered or messenger-delivered paper filings for the Commission's Secretary must be delivered to FCC Headquarters at 445 12th St. SW., Room TW-A325, Washington, DC 20554. All hand deliveries must be held together with rubber bands or fasteners. Any envelopes must be disposed of before entering the building. The filing hours are 8:00 a.m. to 7:00 p.m.</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>19. Comments, reply comments, and ex parte submissions will be available for public inspection during regular business hours in the FCC Reference Center, Federal Communications Commission, 445 12th Street SW., CY-A257, Washington, DC 20554. These documents will also be available via ECFS. Documents will be available electronically in ASCII, Microsoft Word, and/or Adobe Acrobat.</P>

        <P>20. To request information in accessible formats (Braille, large print, electronic files, audio format), send an email to<E T="03">fcc504@fcc.gov</E>or call the FCC's Consumer and Governmental Affairs Bureau at (202) 418-0530 (voice), (202) 418-0432 (TTY). This document can also be downloaded in Word and Portable Document Format (PDF) at:<E T="03">http://www.fcc.gov.</E>
        </P>

        <P>21. For additional information on this proceeding, please contact Paul Powell of the Wireless Telecommunications Bureau at (202) 418-1613 or<E T="03">Paul.Powell@fcc.gov</E>.</P>
        <HD SOURCE="HD2">C. Paperwork Reduction Act of 1995 Analysis</HD>

        <P>22. This document contains proposed information collection requirements. The Commission, as part of its continuing effort to reduce paperwork burdens, invites the general public and the Office of Management and Budget (OMB) to comment on the information collection requirements contained in this document, as required by the Paperwork Reduction Act of 1995, Public Law 104-13. Public and agency comments are due March 11, 2013. Comments should address: (a) Whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; (b) the accuracy of the Commission's burden estimates; (c) ways to enhance the quality, utility, and clarity of the information collected; (d) ways to minimize the burden of the collection of information on the respondents, including the use of automated collection techniques or other forms of information technology; and (e) way to further reduce the information collection burden on small business concerns with fewer than 25 employees. 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>

        <P>23. 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<PRTPAGE P="1192"/>the Federal Communications Commission via email to<E T="03">PRA@fcc.gov</E>and to Nicholas A. Fraser, Office of Management and Budget, via email to<E T="03">Nicholas_A._Fraser@omb.eop.gov</E>or via fax at 202-395-5167.</P>
        <HD SOURCE="HD2">D. Initial Regulatory Flexibility Analysis</HD>

        <P>24. As required by the Regulatory Flexibility Act of 1980 (RFA), the Commission has prepared an Initial Regulatory Flexibility Analysis (IRFA) relating to the foregoing Notice. Written public comments are requested on the IRFA. These comments must be filed in accordance with the same filing deadlines as comments filed in response to this<E T="03">NPRM</E>as set forth on the first page of this document and have a separate and distinct heading designating them as responses to the IRFA.</P>
        <HD SOURCE="HD3">1. Description and Estimate of the Number of Small Entities to Which the Proposed Rules Will Apply</HD>

        <P>25. 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.<E T="03">See</E>5 U.S.C. 603(b)(3). The RFA generally defines the term “small entity” as having the same meaning as the terms “small business,” “small organization,” and “small governmental jurisdiction.”<E T="03">See</E>5 U.S.C. 601(6). In addition, the term “small business” has the same meaning as the term “small-business concern” under the Small Business Act.<E T="03">See</E>5 U.S.C. 601(3). 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.<E T="03">See</E>15 U.S.C. 632.</P>
        <P>26. In the following paragraphs, the Commission further describes and estimates the number and type of small entities that may be affected by the proposals set forth in the Notice. However, since the 3.5 GHz Band is not currently used by small businesses for terrestrial broadband, the proposed new service is unlikely to impose significant new burdens on small businesses. However, if our proposals were adopted, small businesses that choose to use the Citizens Broadband Service on a Priority Access or GAA basis would most likely be required to comply with new registration and compliance requirements, including registration in the SAS. In addition, any device manufacturers that choose to manufacture devices for use in the 3.5 GHz Band will have to ensure that such devices comply with any rules adopted in this proceeding. Finally, if our supplemental proposal to incorporate the 3650-3700 MHz band into the proposed Citizens Broadband Service is adopted, these new rules will apply to any small businesses currently licensed to operate in the 3650-3700 MHz band.</P>
        <P>27.<E T="03">Small Businesses, Small Organizations, and Small Governmental Jurisdictions.</E>The proposals set forth in the Notice, 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 that encompass entities that could be directly affected by the proposals under consideration. As of 2009, small businesses represented 99.9% of the 27.5 million businesses in the United States, according to the SBA. Additionally, 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, counties, towns, townships, villages, school districts, or special districts, with a population of less than fifty thousand.” Census Bureau data for 2007 indicate that there were 89,527 governmental jurisdictions in the United States. We estimate that, of this total, as many as 88,761 entities may qualify as “small governmental jurisdictions.” Thus, we estimate that most governmental jurisdictions are small.</P>
        <P>28.<E T="03">Wireless Telecommunications Carriers (except Satellite).</E>This industry comprises establishments engaged in operating and maintaining switching and transmission facilities to provide communications via the airwaves. Establishments in this industry have spectrum licenses and provide services using that spectrum, such as cellular phone services, paging services, wireless Internet access, and wireless video services. The appropriate size standard under SBA rules is for the category Wireless Telecommunications Carriers (except satellite). The size standard for that category is that a business is small if it has 1,500 or fewer employees. For this category, census data for 2007 show that there were 1,383 firms that operated for the entire year. Of this total, 1,368 firms had 999 or fewer employees and 15 had 1000 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.</P>
        <P>29.<E T="03">Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing.</E>The Census Bureau defines this category as follows: “This industry comprises establishments primarily engaged in manufacturing radio and television broadcast and wireless communications equipment. Examples of products made by these establishments are: transmitting and receiving antennas, cable television equipment, GPS equipment, pagers, cellular phones, mobile communications equipment, and radio and television studio and broadcasting equipment.” The SBA has developed a small business size standard for firms in this category, which is: all such firms having 750 or fewer employees. According to Census Bureau data for 2002, there were a total of 1,041 establishments in this category that operated for the entire year. Of this total, 1,010 had employment of under 500, and an additional 13 had employment of 500 to 999. Thus, under this size standard, the majority of firms can be considered small.</P>
        <P>30.<E T="03">3650-3700 MHz Band Licensees.</E>In March 2005, the Commission released an order providing for the nationwide, non-exclusive licensing of terrestrial operations, utilizing contention-based technologies, in the 3650 MHz band (i.e., 3650-3700 MHz). As of April 2010, more than 1270 licenses have been granted and more than 7433 sites have been registered. The Commission has not developed a definition of small entities applicable to 3650-3700 MHz band nationwide, non-exclusive licensees. However, we estimate that the majority of these licensees are Internet Access Service Providers (ISPs) and that most of those licensees are small businesses.</P>
        <HD SOURCE="HD3">2. Description of Projected Reporting, Recordkeeping, and Other Compliance Requirements for Small Entities</HD>

        <P>31. Under the Commission's proposal, all Citizens Broadband Service devices must comply with technical and operational requirements aimed at preventing interference to Incumbent Access and Priority Access users, including: complying with technical parameters (<E T="03">e.g.,</E>power and unwanted emission limits) as well as RF exposure requirements for the type of device; and incorporation of geo-location capabilities. Citizens Broadband Service users would be required to register such devices in the SAS.</P>

        <P>32. In addition, if our supplemental proposal to incorporate the 3650-3700<PRTPAGE P="1193"/>MHz band into the proposed Citizens Broadband Service is adopted, small businesses operating in this band will be required to transition from the current non-exclusive nationwide licensing approach to the Citizens Broadband Service license-by-rule approach. This will likely entail additional costs and administrative burdens. In the<E T="03">NPRM,</E>we seek comment on the extent of any such potential burdens.</P>
        <P>33. While our proposals would require small businesses to register in the SAS and comply with the rules established for the Citizens Broadband Service, they would receive the ability to access spectrum that is currently unavailable to them. On balance, this would constitute a significant benefit for small business.</P>
        <HD SOURCE="HD3">3. Steps Taken To Minimize the Significant Economic Impact on Small Entities, and Significant Alternatives Considered</HD>

        <P>34. 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 such 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.”<E T="03">See</E>5 U.S.C. 603(c)(1)-(c)(4).</P>
        <P>35. In the<E T="03">NPRM,</E>the Commission proposes that all Citizens Broadband Service users register in the SAS which will manage interference between different tiers of users. The<E T="03">NPRM</E>specifically invites comments on a range of potential technical, legal, and policy aspects of its proposal, including equipment authorization requirements and the specific mechanics of the SAS. At this time, the Commission has not excluded any alternative proposal concerning the operation of the Citizens Broadband Service 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. The Commission also solicits alternative licensing proposals, especially those that would not incur significant and unjustifiable adverse impacts on small entities.</P>
        <P>36. With regard to the supplemental proposal to include the 3650-3700 MHz band, we seek comment on the costs and benefits of extending the Citizens Broadband Service to this band. We also specifically seek comment on the projected cost to existing 3650-3700 MHz licensees and the amount of time it would take such licensees to transition to the new proposed licensing regime.</P>
        <HD SOURCE="HD3">4. Federal Rules That May Duplicate, Overlap, or Conflict With the Proposed Rules</HD>
        <P>37. None.</P>
        <HD SOURCE="HD2">E. Congressional Review Act</HD>

        <P>38. The Commission will not send a copy of the foregoing Order pursuant to the Congressional Review Act, see 5 U.S.C. 801(a)(1)(A), because the application freeze implemented in such<E T="03">Order</E>is a rule of agency organization, procedure, or practice that does not substantially affect the rights or obligations of non-agency parties.<E T="03">Id.</E>at 804(3)(C).</P>
        <HD SOURCE="HD1">III. Ordering Clauses</HD>

        <P>39. Pursuant to sections 1, 2, 4(i), 4(j), 7, 301, 302(a), 303, 307(e), and 316 of the Communications Act of 1934, as amended, 47 U.S.C. 151, 152, 154(i), 154(j), 157, 301, 302(a), 303, 307(e), and 316, this<E T="03">NPRM and Order</E>in GN Docket No. 12-148 is adopted.</P>
        <P>40. License applications for new earth stations in the fixed satellite service, which would receive on frequencies in the 3600-3650 MHz band on a primary basis, filed on or after December 12, 2012, shall not be accepted unless frequencies in this same band are currently licensed to an earth station within 10 miles of the requested coordinates.</P>
        <SIG>
          <FP>Federal Communications Commission.</FP>
          <NAME>Marlene H. Dortch,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00155 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6712-01-P</BILCOD>
    </PRORULE>
    <PRORULE>
      <PREAMB>
        <AGENCY TYPE="N">NATIONAL TRANSPORTATION SAFETY BOARD</AGENCY>
        <CFR>49 CFR Chapter VIII</CFR>
        <DEPDOC>[Docket No. NTSB-GC-2012-0002]</DEPDOC>
        <SUBJECT>Retrospective Analysis of Existing Rules; Notification</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>National Transportation Safety Board (NTSB or Board).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notification.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>On June 25, 2012, the NTSB published a request for information stating it was undertaking a review of all its regulations. 77 FR 37865. The NTSB indicated this review would occur as a result of Executive Order 13579, “Regulation and Independent Regulatory Agencies,” issued July 11, 2011, (76 FR 41587, July 14, 2011), which directs agencies to review all regulations to ensure they are up-to-date and comply with the principles articulated in Executive Order 13579. The NTSB stated it would specifically analyze all regulations within 49 CFR part 831, concerning accident investigation procedures, and publish a document setting forth its plan for proceeding with updates to its regulations. The NTSB collected comments from the public concerning its regulations, and herein notifies the public of its plan to update all NTSB regulations.</P>
        </SUM>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Copies of this notification, published in the<E T="04">Federal Register</E>(FR), are available for inspection and copying in the NTSB's public reading room, located at 490 L'Enfant Plaza SW., Washington, DC 20594-2003. Alternatively, documents related to this comprehensive review of NTSB regulations are available on the government-wide Web site on regulations at<E T="03">http://www.regulations.gov</E>(Docket ID Number NTSB-GC-2012-0002).</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>David Tochen, General Counsel, (202) 314-6080.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">I. Requirement To Review Regulations</HD>

        <P>In accordance with Executive Order 13579, the NTSB published a request for information stating it would undertake a comprehensive review of its regulations. Executive Order 13579 requests independent agencies issue public plans for periodic retrospective analysis of their existing “significant regulations.” The executive order states such analyses should identify any significant regulations that may be outmoded, ineffective, insufficient, or excessively burdensome. Then, the agency's plan should describe how it will modify, streamline, expand, or repeal those regulations in order to achieve the agency's regulatory objective. The President ordered agencies to allow for public participation in retrospective reviews; prioritize their reviews by first addressing the regulations that will provide the most significant monetary savings or in reductions in paperwork burdens; and regularly report the status of retrospective reviews to OIRA. The NTSB is committed to fulfilling the<PRTPAGE P="1194"/>requirements set forth in this follow-up order.</P>
        <P>As described in the NTSB's June 25, 2012 request for information, Executive Order 13579 encourages independent agencies to review “significant regulations”; however, the executive order does not define what agencies should consider to be “significant regulations.” The NTSB decided to utilize the definition of a “significant regulatory action” provided in Executive Order 12866, “Regulatory Planning and Review,” which is the executive order that established the modern regulatory review structure.<SU>1</SU>
          <FTREF/>The NTSB then determined that a very limited number of its regulatory actions are “major rules,” because they do not have a “significant economic impact upon a substantial number of small entities.” The NTSB's request for information, therefore, described only the NTSB regulations that could, when viewed in the broadest sense, have a significant economic impact upon a substantial number of small entities.</P>
        <FTNT>
          <P>
            <SU>1</SU>Section 3(f) of Executive Order 12866 defines “significant regulatory action” as one that is likely to result in a rule that may:</P>
          <P>(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;</P>
          <P>(2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another agency;</P>
          <P>(3) Materially alter the budgetary impact of entitlements, grants, user fees, or loan programs or the rights and obligations of recipients thereof; or</P>
          <P>(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>
        </FTNT>
        <P>The NTSB's request for information set forth a 6-month timeframe in which the NTSB indicated it would specifically review all provisions within part 831. In particular, the request for information states the NTSB would:</P>
        
        <EXTRACT>
          <P>[R]eview 49 CFR part 831 within the next 6 months to determine if any sections within part 831 could be modified, streamlined, expanded, or repealed, pursuant to the direction of Executive Order 13579. The NTSB's findings will form the basis for the NTSB's decision concerning whether the NTSB should make any changes to part 831. The NTSB is committed to issuing a Notice of Proposed Rulemaking within 6 months of the published findings, should the findings counsel in favor of changing any sections of part 831.</P>
        </EXTRACT>
        
        <FP>77 FR at 37867.</FP>
        <P>As explained more fully below, the NTSB has reviewed part 831 and anticipates publishing a notice of proposed rulemaking (NPRM) to suggest various changes to part 831.</P>
        <HD SOURCE="HD1">II. The NTSB's Review and Upcoming Changes</HD>
        <P>Since publishing its June 25, 2012 request for information, the NTSB has reviewed all parts of its regulations: 49 CFR Parts 800-850. The NTSB has determined to update certain parts in the near future, in accordance with the standard informal rulemaking procedure of soliciting comments from the public (Phase I). The NTSB then plans to publish a document indicating its changes to rules applicable only to internal agency matters (Phase II). Finally, the NTSB also plans to update other parts at a later date, as these parts require coordination with other agencies, and therefore should appear on a different timeline (Phase III).</P>
        <HD SOURCE="HD2">Phase I: Review of Parts Requiring Comment</HD>
        <P>The NTSB has carefully reviewed the following regulatory parts, and plans to publish a notice of proposed rulemaking updating these parts within three months of the date of this notification: Parts 801, 802, 803, 804, 806, 807, 825, 830, 831, 835, 837, 840, and 845. The NTSB has also drafted an additional part, to set forth requirements of notification applicable to certain highway accidents.</P>
        <P>As discussed in the June 25, 2012 request for information, the NTSB identified one part of its regulations that may contain “significant regulations” pursuant to the definition contemplated above: 49 CFR part 831. This part, entitled “Accident/Incident Investigation Procedures,” contains a set of 14 sections describing the NTSB's “party process,” which involves the NTSB's invitation to outside entities to assist with an investigation as a “party.” The NTSB typically extends party status to those organizations that can provide the necessary technical assistance to the investigation. The role of party representatives is to support the NTSB's investigation at the direction of the NTSB, all with the ultimate goal of improving transportation safety. These parties could be small entities, which the NTSB may request be available for the on-scene portion of an investigation, as well as follow-up meetings and/or tasks. The NTSB does not reimburse investigation participants for the amount of time expended for an NTSB investigation, nor does the NTSB pay for any travel costs that arise out of such participation. As a result, it is remotely possible that a combination of NTSB investigations could result in costs that exceed $100 million.</P>

        <P>The NTSB has undertaken a comprehensive review of part 831, and carefully considered the five comments the NTSB received as a result of its June 25, 2012 announcement indicating the plan to update NTSB regulations. The NTSB posted these comments in the public rulemaking docket, available at<E T="03">www.regulations.gov,</E>Docket No. NTSB-GC-2012-0002. The NTSB plans to publish an NPRM that responds to all comments and sets forth proposed changes to part 831.</P>
        <P>In addition, the NTSB has undertaken a review of its other regulatory parts, and also plans to issue an NPRM proposing changes to the other parts listed above. Within this NPRM, the NTSB will most likely propose a new part to address notification of certain highway accidents.</P>
        <P>The NTSB may publish its proposed changes to part 831 in the same NPRM as its changes to the other parts. In this regard, Phase I of the NTSB's comprehensive review of its regulations may consist of two tiers.</P>
        <HD SOURCE="HD2">Phase II: Changes Not Requiring Public Comment</HD>
        <P>In Phase II, the NTSB will issue changes to 49 CFR part 800. The NTSB has identified several sections of part 800 that are outdated. In addition, the NTSB recognizes several additional duties should be included in certain sections within part 800. Part 800 solely consists of internal agency procedures that are not relevant to the NTSB's work with the public, its parties, or any other agency. As a result, the NTSB does not plan to seek comments from the public concerning changes to part 800. 5 U.S.C. 553(b)(3)(A) (exempting from the public comment requirement “rules of agency organization, procedure, or practice”). The NTSB plans to publish its changes to part 800 in conjunction with, or shortly after, its publication of the final NPRM described in the plan for Phase I.</P>
        <HD SOURCE="HD2">Phase III: Changes Requiring Consultation With Other Agencies</HD>

        <P>The NTSB, at this time, is not prepared to alter part 850 of its regulations, which set forth procedures applicable to marine accident investigations. The NTSB maintains a close working relationship with the United States Coast Guard in accordance with 49 U.S.C. 1131, part 850 and a Memorandum of Understanding. The NTSB plans to address with the Coast Guard any changes to part 850, and prepare such changes on a distinct timeline, rather than contemporaneously with all other updates from Phases I and II of this project.<PRTPAGE P="1195"/>
        </P>
        <P>In the event the NTSB identifies the need for additional regulatory changes or additions it believes would benefit the agency, but require collaborating with other Federal agencies, the NTSB will also attempt to include such changes in Phase III of this project.</P>
        <HD SOURCE="HD1">III. Biennial Review</HD>
        <P>As stated in its June 25, 2012 request for information, the NTSB has not overseen any investigations that come within the definition of “significant regulatory actions.” Nevertheless, the NTSB indicated it is committed to reviewing its regulations within 49 CFR part 831, in the interest of ensuring none are “outmoded, ineffective, insufficient, or excessively burdensome” under Executive Orders 13563,”Regulation and Independent Regulatory Agencies,” issued January 18, 2011 (76 FR 3821, January 21, 2011) and 13579. As a result, following the comprehensive review and publication of the NPRM and final rule documents discussed in this notification, the NTSB will undertake a biennial review of part 831 to ensure no regulations are outmoded, ineffective, insufficient, or excessively burdensome. Following each biennial review, the NTSB will make its findings available for public comment.</P>
        <HD SOURCE="HD1">IV. Cultural Change</HD>
        <P>The NTSB's June 25, 2012 request for information also stated it was committed to encouraging and fostering a culture at the NTSB that ensures agency employees are aware NTSB regulations must remain up-to-date. The NTSB believes it has begun to achieve this goal, as almost all offices at the NTSB have been involved in the comprehensive review of regulations the NTSB recently concluded. Offices are aware of the importance of ensuring regulations are not outdated or difficult to comprehend.</P>
        <SIG>
          <NAME>Deborah A.P. Hersman,</NAME>
          <TITLE>Chairman.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2012-31623 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </PRORULE>
  </PRORULES>
  <VOL>78</VOL>
  <NO>5</NO>
  <DATE>Tuesday, January 8, 2013</DATE>
  <UNITNAME>Notices</UNITNAME>
  <NOTICES>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="1196"/>
        <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
        <SUBAGY>Food Safety and Inspection Service</SUBAGY>
        <DEPDOC>[Docket No. FSIS-2012-0052]</DEPDOC>
        <SUBJECT>Codex Alimentarius Commission: Meeting of the Ad Hoc Codex Intergovernmental Task Force on Animal Feeding</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of the Under Secretary for Food Safety, USDA.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of public meeting and request for comments.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Office of the Under Secretary for Food Safety, U.S. Department of Agriculture (USDA), and the Center for Veterinary Medicine (CVM), Food and Drug Administration (FDA), are sponsoring a public meeting on January 17, 2013. The objective of the public meeting is to provide information and receive public comments on agenda items and draft United States (U.S.) positions that will be discussed at the 7th Session of the Ad Hoc Codex Intergovernmental Task Force on Animal Feeding (AFTF) of the Codex Alimentarius Commission (Codex), which will be held in Berne, Switzerland, February 4-8, 2013. The Under Secretary for Food Safety and the Center for Veterinary Medicine, Food and Drug Administration, recognize the importance of providing interested parties the opportunity to obtain background information on the 7th Session of the AFTF and to address items on the agenda.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The public meeting is scheduled for Thursday January 17, 2013, from 1:00 p.m.-3:00 p.m.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>The public meeting will be held in the Jamie L. Whitten Building, United States Department of Agriculture (USDA), 1400 Independence Avenue SW., Room 107-A, Washington, DC 20250. Documents related to the 7th Session of the AFTF will be accessible via the World Wide Web at the following address:<E T="03">http://www.codexalimentarius.org/meetings-reports/en/</E>
          </P>

          <P>Dr. Daniel McChesney, U.S. Delegate to the 7th Session of the AFTF, invites U.S. interested parties to submit their comments electronically to the following email address<E T="03">Daniel.McChesney@fda.hhs.gov</E>and<E T="03">uscodex@fsis.usda.gov.</E>
          </P>
        </ADD>
        <HD SOURCE="HD1">Call-In Number</HD>
        <P>If you wish to participate in the public meeting for the 7th session of the AFTF by conference call, please use the call-in number and participant code listed below.</P>
        <P>
          <E T="03">Call-in Number:</E>1 (888) 858-2144.</P>
        <P>
          <E T="03">Participant Code:</E>6208658.</P>
        <P>
          <E T="03">For Further Information About the 7th Session of the</E>AFTF<E T="03">Contact:</E>Dr. Daniel G. McChesney, Director, Office of Surveillance and Compliance, Center for Veterinary Medicine, FDA, 7529 Standish Place, Rockville, MD 20855 Phone: (240) 453-6830, Fax: (240) 453-6880, Email:<E T="03">Daniel.McChesney@fda.hhs.gov.</E>
        </P>
        <P>
          <E T="03">For Further Information About the Public Meeting Contact:</E>Doreen Chen-Moulec, U.S. Codex Office, 1400 Independence Avenue SW., Room 4861, Washington, DC 20250, Phone: (202) 205-7760, Fax: (202) 720-3157, E-mail:<E T="03">uscodex@fsis.usda.gov.</E>
        </P>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Background</HD>
        <P>Codex was established in 1963 by two United Nations organizations, the Food and Agriculture Organization (FAO) and the World Health Organization (WHO). Through adoption of food standards, codes of practice, and other guidelines developed by its committees, and by promoting their adoption and implementation by governments, Codex seeks to protect the health of consumers and ensure that fair practices are used in trade.</P>
        <P>The AFTF is responsible for:</P>
        <P>(a) The development of guidelines, intended for governments on how to apply the existing Codex risk assessment methodologies to the various types of hazards related to contaminants/residues in feed ingredients, including feed additives used in feeding stuffs for food producing animals. The guidelines should include specific science-based risk assessment criteria to apply to feed contaminants/residues. These criteria should be consistent with existing Codex methodologies.</P>
        <P>The guidelines should also consider the need to address the establishment of rates of transfer and accumulation from feed to edible tissues in animal-derived products according to the characteristics of the hazard.</P>
        <P>The guidelines should be drawn up in such a way as to enable countries to prioritize and assess risks based upon local conditions, use, exposure of animals and the impact, if any, on human health.</P>
        <P>(b) Develop a prioritized list of hazards in feed ingredients and feed additives for governmental use. The list should contain hazards of international relevance that are reasonably likely to occur, and are thus likely to warrant future attention.</P>
        <P>In doing so, due consideration should be given to the prioritized list of hazards as recommended by the FAO/WHO Expert Meeting on Animal Feed Impact on Food Safety. Clear criteria should be used to prioritize the list of hazards and take account of the potential transfer of contaminants/residues in feed to edible animal products (e.g. meat, fish meat, milk and eggs).</P>
        <P>The Committee is hosted by Switzerland.</P>
        <HD SOURCE="HD1">Issues to be Discussed at the Public Meeting</HD>
        <P>The following items on the agenda for the 7th Session of the AFTF will be discussed during the public meeting:</P>
        <P>• Matters referred to the AFTF by Codex and other Codex committees and task forces</P>
        <P>• Report on activities of FAO, WHO and other international intergovernmental organizations</P>
        <P>• Draft guidelines on application of risk assessment for feed</P>
        <P>• Proposed draft guidance for use by governments in prioritizing the national feed hazards</P>

        <P>Each issue listed will be fully described in documents distributed, or to be distributed, by the Secretariat prior to the meeting. Members of the public may access copies of these documents (see<E T="02">ADDRESSES</E>).</P>
        <HD SOURCE="HD1">Public Meeting</HD>

        <P>At the January 17, 2013, public meeting, draft U.S. positions on the agenda items will be described and discussed, and attendees will have the<PRTPAGE P="1197"/>opportunity to pose questions and offer comments. Written comments may be offered at the meeting or sent to Daniel McChesney, U.S. Delegate for the 7th Session of the AFTF (see<E T="02">ADDRESSES</E>). Written comments should state that they relate to activities of the 7th Session of the AFTF.</P>
        <HD SOURCE="HD1">Additional Public Notification</HD>

        <P>FSIS will announce this notice online through the FSIS Web page located at<E T="03">http://www.fsis.usda.gov/regulations_&amp;_policies/Federal_Register_Notices/index.asp.</E>
        </P>
        <P>FSIS will also make copies of this<E T="04">Federal Register</E>publication available through the FSIS Constituent Update, which is used to provide information regarding FSIS policies, procedures, regulations,<E T="04">Federal Register</E>notices, FSIS public meetings, and other types of information that could affect or would be of interest to constituents and stakeholders. The Update is communicated via Listserv, a free electronic mail subscription service for industry, trade groups, consumer interest groups, health professionals, and other individuals who have asked to be included. The Update is also available on the FSIS Web page. In addition, FSIS offers an electronic mail subscription service which provides automatic and customized access to selected food safety news and information. This service is available at<E T="03">http://www.fsis.usda.gov/News_&amp;_Events/Email_Subscription/.</E>Options range from recalls to export information to regulations, directives, and notices. Customers can add or delete subscriptions themselves, and have the option to password protect their accounts.</P>
        <HD SOURCE="HD1">USDA Nondiscrimination Statement</HD>
        <P>USDA prohibits discrimination in all its programs and activities on the basis of race, color, national origin, gender, religion, age, disability, political beliefs, sexual orientation, and marital or family status. (Not all prohibited bases apply to all programs.) Persons with disabilities who require alternative means for communication of program information (Braille, large print, or audiotape.) should contact USDA's Target Center at 202-720-2600 (voice and TTY).</P>
        <P>To file a written complaint of discrimination, write USDA, Office of the Assistant Secretary for Civil Rights, 1400 Independence Avenue SW., Washington, DC 20250-9410 or call 202-720-5964 (voice and TTY). USDA is an equal opportunity provider and employer.</P>
        <SIG>
          <DATED>Done at Washington, DC on: December 21, 2012.</DATED>
          <NAME>MaryFrances Lowe,</NAME>
          <TITLE>U.S. Manager for Codex Alimentarius.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00169 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3410-DM-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>Foreign-Trade Zones Board</SUBAGY>
        <DEPDOC>[Order No. 1875]</DEPDOC>
        <SUBJECT>Reorganization/Expansion of Foreign-Trade Zone 8Under Alternative Site Framework;Toledo, OH</SUBJECT>
        <EXTRACT>
          <P>Pursuant to its authority under the Foreign-Trade Zones Act of June 18, 1934, as amended (19 U.S.C. 81a-81u), the Foreign-Trade Zones Board (the Board) adopts the following Order:</P>
        </EXTRACT>
        
        <P>
          <E T="03">Whereas,</E>the Board adopted the alternative site framework (ASF) (15 CFR Sec. 400.2(c)) as an option for the establishment or reorganization of zones;</P>
        <P>
          <E T="03">Whereas,</E>the Toledo-Lucas County Port Authority, grantee of Foreign-Trade Zone 8, submitted an application to the Board (FTZ Docket B-49-2012, docketed 7/12/2012) for authority to reorganize and expand the zone under the ASF with a service area of Sandusky, Henry, Wood, Lucas and Defiance Counties, Ohio, in and adjacent to the Toledo-Sandusky Customs and Border Protection port of entry, FTZ 8's existing Sites 1, 2, 4 and 5 would be categorized as magnet sites and Sites 7 and 8 as usage-driven sites, Site 3 would be removed from the zone and the grantee proposes an additional subzone (Subzone 8I) under the ASF;</P>
        <P>
          <E T="03">Whereas,</E>notice inviting public comment was given in the<E T="04">Federal Register</E>(77 FR 43048, 7/23/2012) and the application has been processed pursuant to the FTZ Act and the Board's regulations; and,</P>
        <P>
          <E T="03">Whereas,</E>the Board adopts the findings and recommendations of the examiner's report, and finds that the requirements of the FTZ Act and the Board's regulations are satisfied, and that the proposal is in the public interest;</P>
        <P>
          <E T="03">Now, therefore,</E>the Board hereby orders:</P>

        <P>The application to reorganize and expand FTZ 8 under the alternative site framework is approved, subject to the FTZ Act and the Board's regulations, including Section 400.13, to the Board's standard 2,000-acre activation limit for the zone, to a five-year ASF sunset provision for magnet sites that would terminate authority for Sites 2, 4 and 5 if not activated by December 31, 2017, and to three-year ASF sunset provisions for subzone/usage-driven sites that would terminate authority for Sites 7 and 8 as well as each site of Subzone 8I if no foreign-status merchandise is admitted for a<E T="03">bona fide</E>customs purpose by December 31, 2015.</P>
        <SIG>
          <DATED>Signed at Washington, DC, this 20th day of December 2012.</DATED>
          <NAME>Paul Piquado,</NAME>
          <TITLE>Assistant Secretary of Commercefor Import Administration,Alternate Chairman,Foreign-Trade Zones Board.</TITLE>
        </SIG>
        
        <FP SOURCE="FP-DASH">ATTEST:</FP>
        <SIG>
          <NAME>Andrew McGilvray,</NAME>
          <TITLE>Executive Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00156 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>Foreign-Trade Zones Board</SUBAGY>
        <DEPDOC>[Order No. 1876]</DEPDOC>
        <SUBJECT>Reorganization of Foreign-Trade Zone 32Under Alternative Site Framework;Miami, FL</SUBJECT>
        <EXTRACT>
          <P>Pursuant to its authority under the Foreign-Trade Zones Act of June 18, 1934, as amended (19 U.S.C. 81a-81u), the Foreign-Trade Zones Board (the Board) adopts the following Order:</P>
        </EXTRACT>
        
        <P>
          <E T="03">Whereas,</E>the Board adopted the alternative site framework (ASF) (15 CFR Sec. 400.2(c)) as an option for the establishment or reorganization of zones;</P>
        <P>
          <E T="03">Whereas,</E>the Greater Miami Foreign-Trade Zone, Inc., grantee of Foreign-Trade Zone 32, submitted an application to the Board (FTZ Docket B-51-2012, docketed July 13, 2012; amended October 9, 2012) for authority to reorganize under the ASF with a service area that includes a portion of Miami-Dade County, Florida, within the Miami Customs and Border Protection port of entry, FTZ 32's existing Site 1 would be categorized as a magnet site, Site 2 would be removed from the zone, and Sites 3 and 4 would be categorized as usage-driven sites;</P>
        <P>
          <E T="03">Whereas,</E>notice inviting public comment was given in the<E T="04">Federal Register</E>(77 FR 43048-43049, 7/23/2012) and the application, as amended, has been processed pursuant to the FTZ Act and the Board's regulations; and,</P>
        <P>
          <E T="03">Whereas,</E>the Board adopts the findings and recommendation of the examiner's report, and finds that the requirements of the FTZ Act and the Board's regulations are satisfied, and that the proposal, as amended, is in the public interest;<PRTPAGE P="1198"/>
        </P>
        <P>
          <E T="03">Now, therefore,</E>the Board hereby orders:</P>

        <P>The application, as amended, to reorganize FTZ 32 under the alternative site framework is approved, subject to the FTZ Act and the Board's regulations, including Section 400.13, to the Board's standard 2,000-acre activation limit for the zone, and to a three-year ASF sunset provision for usage-driven sites that would terminate authority for Sites 3 and 4 if no foreign-status merchandise is admitted for a<E T="03">bona fide</E>customs purpose by December 31, 2015.</P>
        <SIG>
          <DATED>Signed at Washington, DC, this 20th day of December 2012.</DATED>
          <NAME>Paul Piquado,</NAME>
          <TITLE>Assistant Secretary of Commercefor Import Administration,Alternate Chairman,Foreign-Trade Zones Board.</TITLE>
        </SIG>
        
        <FP SOURCE="FP-DASH">ATTEST:</FP>
        <SIG>
          <NAME>Andrew McGilvray,</NAME>
          <TITLE>Executive Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00160 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>Bureau of Industry and Security</SUBAGY>
        <SUBJECT>Sensors and Instrumentation Technical Advisory Committee; Notice of Partially Closed Meeting</SUBJECT>
        <P>The Sensors and Instrumentation Technical Advisory Committee (SITAC) will meet on January 29, 2013, 9:30 a.m., in the Herbert C. Hoover Building, Room 6087B, 14th Street between Constitution and Pennsylvania Avenues NW., Washington, DC. The Committee advises the Office of the Assistant Secretary for Export Administration on technical questions that affect the level of export controls applicable to sensors and instrumentation equipment and technology.</P>
        <HD SOURCE="HD1">Agenda</HD>
        <HD SOURCE="HD2">Public Session</HD>
        <FP SOURCE="FP-1">1. Welcome and Introductions.</FP>
        <FP SOURCE="FP-1">2. Remarks from the Bureau of Industry and Security Management.</FP>
        <FP SOURCE="FP-1">3. Industry Presentations.</FP>
        <FP SOURCE="FP-1">4. New Business.</FP>
        <HD SOURCE="HD2">Closed Session</HD>
        <FP SOURCE="FP-1">5. Discussion of matters determined to be exempt from the provisions relating to public meetings found in 5 U.S.C. app. 2 §§ 10(a)(1) and 10(a)(3).</FP>
        

        <P>The open session will be accessible via teleconference to 20 participants on a first come, first serve basis. To join the conference, submit inquiries to Ms. Yvette Springer at<E T="03">Yspringer@bis.doc.gov</E>no later than January 22, 2013.</P>
        <P>A limited number of seats will be available during the public session of the meeting. Reservations are not accepted. To the extent that time permits, members of the public may present oral statements to the Committee. The public may submit written statements at any time before or after the meeting. However, to facilitate distribution of public presentation materials to the Committee members, the Committee suggests that the materials be forwarded before the meeting to Ms. Springer.</P>
        <P>The Assistant Secretary for Administration, with the concurrence of the General Counsel, formally determined on December 11, 2012 pursuant to Section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. app. 2 § 10(d), that the portion of this meeting dealing with pre-decisional changes to the Commerce Control List and U.S. export control policies shall be exempt from the provisions relating to public meetings found in 5 U.S.C. app. 2 §§ 10(a)(1) and 10(a)(3). The remaining portions of the meeting will be open to the public.</P>
        <P>For more information contact Yvette Springer on (202) 482-2813.</P>
        <SIG>
          <DATED>Dated: January 2, 2013.</DATED>
          <NAME>Yvette Springer,</NAME>
          <TITLE>Committee Liaison.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00153 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>Bureau of Industry and Security</SUBAGY>
        <SUBJECT>Information SystemsTechnical Advisory Committee;Notice of Partially Closed Meeting</SUBJECT>
        <P>The Information Systems Technical Advisory Committee (ISTAC) will meet on January 23 and 24, 2013, 9:00 a.m., at Qualcomm Incorporated, 5775 Morehouse Drive, Building QRC, Room 119B, San Diego, California. The Committee advises the Office of the Assistant Secretary for Export Administration on technical questions that affect the level of export controls applicable to information systems equipment and technology.</P>
        <HD SOURCE="HD1">Wednesday, January 23</HD>
        <HD SOURCE="HD2">Open Session</HD>
        <FP SOURCE="FP-1">1. Welcome and Introductions</FP>
        <FP SOURCE="FP-1">2. Working Group Reports</FP>
        <FP SOURCE="FP-1">3. Industry presentation: Space Qualification</FP>
        <FP SOURCE="FP-1">4. Industry presentation: FPGAs</FP>
        <FP SOURCE="FP-1">5. Industry presentation: Rad-hard semiconductors</FP>
        <FP SOURCE="FP-1">6. Industry presentation: Trends in Cellular/Mobile Telecomm</FP>
        <FP SOURCE="FP-1">7. New business</FP>
        <HD SOURCE="HD1">Thursday, January 24</HD>
        <HD SOURCE="HD2">Closed Session</HD>
        <FP SOURCE="FP-1">8. Discussion of matters determined to be exempt from the provisions relating to public meetings found in 5 U.S.C. app. 2 §§ 10(a)(1) and 10(a)(3).</FP>
        

        <P>The open session will be accessible via teleconference to 20 participants on a first come, first serve basis. To join the conference, submit inquiries to Ms. Yvette Springer at<E T="03">Yvette.Springer(@bis.doc.gov</E>, no later than January 16, 2013.</P>
        <P>A limited number of seats will be available for the public session. Reservations are not accepted. If attending in person, forward your name, Name (to appear on badge), Title, Citizenship, Organization name, Organization address, Email, and Phone to Ms. Springer. To the extent time permits, members of the public may present oral statements to the Committee. The public may submit written statements at any time before or after the meeting. However, to facilitate distribution of public presentation materials to Committee members, the Committee suggests that public presentation materials or comments be forwarded before the meeting to Ms. Springer.</P>
        <P>The Assistant Secretary for Administration, with the concurrence of the delegate of the GeneralCounsel, formally determined on November 21, 2012, pursuant to Section 10(d) of the FederalAdvisory Committee Act, as amended (5 U.S.C. app. 2 § (l0)(d))), that the portion of the meeting concerning trade secrets and commercial or financial information deemed privileged or confidential as described in 5 U.S.C. 552b(c)(4) and the portion of the meeting concerning matters the disclosure of which would be likely to frustrate significantly implementation of an agency action as described in 5 U.S.C. 552b(c)(9)(B) shall be exempt from the provisions relating to public meetings found in 5 U.S.C. app. 2 §§ 10(a)(1) and l0(a)(3). The remaining portions of the meeting will be open to the public.</P>
        <P>For more information, call Yvette Springer at (202) 482-2813.</P>
        <SIG>
          <DATED>Dated: January 2, 2013.</DATED>
          
          <NAME>Yvette Springer,</NAME>
          <TITLE>Committee Liaison Officer.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00154 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4310-JT-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="1199"/>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>International Trade Administration</SUBAGY>
        <DEPDOC>[A-201-836]</DEPDOC>
        <SUBJECT>Light-Walled Rectangular Pipe and Tube From Mexico: Final Results of Antidumping Duty Administrative Review</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Import Administration, International Trade Administration, Department of Commerce.</P>
        </AGY>
        
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>On September 7, 2012, the Department of Commerce published the preliminary results of the administrative review of the antidumping duty order on light-walled rectangular pipe and tube (LWR pipe and tube) from Mexico. This review covers two respondent companies and the period of review is from August 1, 2010, through July 31, 2011. We invited interested parties to comment on the preliminary results but we received no such comments. Therefore, our final results remain unchanged from the preliminary results of review.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>January 8, 2013.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Edythe Artman or Angelica Mendoza, AD/CVD Operations, Office 7, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue NW., Washington, DC 20230; telephone: (202) 482-3931 or (202) 482-3019, respectively.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Background</HD>

        <P>On September 7, 2012, the Department published the preliminary results of the administrative review on LWR pipe and tube from Mexico in the<E T="04">Federal Register.</E>
          <SU>1</SU>
          <FTREF/>In these results, we preliminarily determined that the respondents, Maquilacero S.A. de C.V. (Maquilacero) and Regiomontana de Perfiles y Tubos S.A. de C.V. (Regiopytsa) did not sell subject merchandise at less than normal value during the period of review. We invited interested parties to comment on the preliminary results but received no such comments. We also did not receive a request for a hearing.</P>
        <FTNT>
          <P>
            <SU>1</SU>
            <E T="03">See Light-Walled Rectangular Pipe and Tube From Mexico: Preliminary Results and Partial Rescission of Antidumping Duty Administrative Review,</E>77 FR 55186 (September 7, 2012) (<E T="03">Preliminary Results</E>). Please note that reference to a partial rescission in this notice was erroneous, as no companies were rescinded from the review.</P>
        </FTNT>
        <HD SOURCE="HD1">Period of Review</HD>
        <P>The period of review is August 1, 2010, through July 31, 2011.</P>
        <HD SOURCE="HD1">Scope of the Order</HD>
        <P>The merchandise that is the subject of the order is certain welded carbon-quality light-walled steel pipe and tube, of rectangular (including square) cross section, having a wall thickness of less than 4 mm.</P>
        <P>The term carbon-quality steel includes both carbon steel and alloy steel which contains only small amounts of alloying elements. Specifically, the term carbon-quality includes products in which none of the elements listed below exceeds the quantity by weight respectively indicated: 1.80 percent of manganese, or 2.25 percent of silicon, or 1.00 percent of copper, or 0.50 percent of aluminum, or 1.25 percent of chromium, or 0.30 percent of cobalt, or 0.40 percent of lead, or 1.25 percent of nickel, or 0.30 percent of tungsten, or 0.10 percent of molybdenum, or 0.10 percent of niobium, or 0.15 percent vanadium, or 0.15 percent of zirconium. The description of carbon-quality is intended to identify carbon-quality products within the scope. The welded carbon-quality rectangular pipe and tube subject to the order is currently classified under the Harmonized Tariff Schedule of the United States (HTSUS) subheadings 7306.61.50.00 and 7306.61.70.60. While HTSUS subheadings are provided for convenience and customs purposes, our written description of the scope of the order is dispositive.</P>
        <HD SOURCE="HD1">Final Results of Review</HD>
        <P>We determine that the following weighted-average dumping margins exist for the period August 1, 2010, through July 31, 2011:</P>
        <GPOTABLE CDEF="s100,20" COLS="2" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">
              <E T="03">Manufacturer/Exporter</E>
            </CHED>
            <CHED H="1">
              <E T="03">Weighted-average dumping margins</E>
              <LI>
                <E T="03">(percent)</E>
              </LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Maquilacero S.A. de C.V.</ENT>
            <ENT>0.00</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Regiomontana de Perfiles y Tubos S.A. de C.V.</ENT>
            <ENT>0.00</ENT>
          </ROW>
        </GPOTABLE>
        <HD SOURCE="HD1">Assessment Rates</HD>
        <P>We will instruct U.S. Customs and Border Protection (CBP) to apply an assessment rate of zero percent to all entries of subject merchandise during the period of review that were produced and exported by Maquilacero and Regiopytsa.</P>

        <P>The Department clarified its “automatic assessment” regulation on May 6, 2003.<E T="03">See Assessment of Antidumping Duties.</E>This clarification will apply to entries of subject merchandise during the period of review produced by Maquilacero and Regiopytsa for which they did not know that their merchandise was destined for the United States. In such instances, we will instruct CBP to liquidate unreviewed entries at the all-others rate of 3.76 percent, as established in the less-than-fair-value investigation of this proceeding<SU>2</SU>
          <FTREF/>, if there is no rate for the intermediate company(ies) involved in the transaction.</P>
        <FTNT>
          <P>
            <SU>2</SU>
            <E T="03">See Light-Walled Rectangular Pipe and Tube from Mexico, the People's Republic of China, and the Republic of Korea: Antidumping Duty Orders; Light-Walled Rectangular Pipe and Tube from the Republic of Korea: Notice of Amended Final Determination of Sales at Less Than Fair Value,</E>73 FR 45403, 45405 (August 5, 2008).</P>
        </FTNT>
        <P>In accordance with 19 CFR 356.8(a), the Department intends to issue assessment instructions to CBP on or after 41 days following the publication of the final results of this review.</P>
        <HD SOURCE="HD1">Cash-Deposit Requirements</HD>

        <P>The following cash deposit requirements will be effective upon publication of the final results of this administrative review for all shipments of the subject merchandise entered or withdrawn from warehouse for consumption on or after the publication date of these final results, consistent with section 751(a)(2)(C) of the Act: (1) For subject merchandise manufactured and exported by the Maquilacero and Regiopytsa, the cash deposit rate will be zero; (2) for previously reviewed or investigated companies, the cash deposit rate will continue to be the company-specific rate published for the most recent period; (3) if the exporter is not a firm covered in this review, the prior review, or the investigation but the manufacturer is, then the cash-deposit rate will be the rate established for the most recent period for the manufacturer of the merchandise; and (4) if neither the exporter nor the manufacturer is a firm covered in this review, a previous<PRTPAGE P="1200"/>review or the less-than-fair-value investigation conducted by the Department, then the cash deposit rate will be the all-others rate of 3.76 percent. These deposit requirements, when imposed, shall remain in effect until further notice.</P>
        <HD SOURCE="HD1">Notifications to Interested Parties</HD>
        <P>This notice also serves as a final reminder to importers of their responsibility under 19 CFR 351.402(f)(2) to file a certificate regarding the reimbursement of antidumping duties prior to liquidation of the relevant entries during this review period. Failure to comply with this requirement could result in the Secretary's presumption that reimbursement of antidumping duties occurred and the subsequent assessment of doubled antidumping duties.</P>
        <P>This notice also serves as a reminder to parties subject to administrative protective orders (APO) of their responsibility concerning the return or destruction of proprietary information disclosed under APO in accordance with 19 CFR 351.305(a)(3), which continues to govern business proprietary information in this segment of the proceeding. Timely written notification of the return/destruction of APO materials or conversion to judicial protective order is hereby requested. Failure to comply with the regulations and terms of an APO is a violation, which is subject to sanction.</P>
        <P>We are issuing and publishing this notice in accordance with sections 751(a)(1) and 777(i)(1) of the Tariff Act of 1930, as amended.</P>
        <SIG>
          <DATED>Dated: December 26, 2012.</DATED>
          <NAME>Lynn Fischer Fox,</NAME>
          <TITLE>Deputy Assistant Secretary for Policy and Negotiations.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00054 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>International Trade Administration</SUBAGY>
        <DEPDOC>[A-570-900]</DEPDOC>
        <SUBJECT>Diamond Sawblades and Parts Thereof From the People's Republic of China: Initiation of Antidumping Duty Changed Circumstances Review</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Import Administration, International Trade Administration, Department of Commerce.</P>
        </AGY>
        
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Pursuant to section 751(b) of the Tariff Act of 1930, as amended, and 19 CFR 351.216 and 351.221(c)(3), the Department of Commerce is initiating a changed circumstances review of the antidumping duty order on diamond sawblades and parts thereof from the People's Republic of China with respect to Husqvarna (Hebei) Co., Ltd.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>January 8, 2013.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION:</HD>
          <P>Yang Jin Chun AD/CVD Operations, Office 1, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue NW., Washington, DC 20230; telephone: (202) 482-5760.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Background</HD>

        <P>The Department of Commerce (the Department) published the antidumping duty order on diamond sawblades and parts thereof from the People's Republic of China on November 4, 2009.<E T="03">See Diamond Sawblades and Parts Thereof From the People's Republic of China and the Republic of Korea: Antidumping Duty Orders,</E>74 FR 57145 (November 4, 2009).</P>
        <P>On October 1, 2012, Husqvarna (Hebei) Co., Ltd. (“Hebei Husqvarna”), an interested party in the ongoing, 2010-2011 administrative review, filed a request for a changed circumstances review. In its letter, Hebei Husqvarna informed the Department that Hebei Husqvarna Jikai Diamond Tools Co., Ltd. changed its name to Husqvarna (Hebei) Co., Ltd. on April 27, 2012, and it requested that the Department find Hebei Husqvarna to be the successor-in-interest to Hebei Husqvarna Jikai Diamond Tools Co., Ltd..</P>
        <HD SOURCE="HD1">Scope of the Order</HD>

        <P>The products covered by the order are all finished circular sawblades, whether slotted or not, with a working part that is comprised of a diamond segment or segments, and parts thereof. Merchandise subject to the order is typically imported under heading 8202.39.00.00 of the Harmonized Tariff Schedule of the United States (“HTSUS”). When packaged together as a set for retail sale with an item that is separately classified under headings 8202 to 8205 of the HTSUS, diamond sawblades or parts thereof may be imported under heading 8206.00.00.00 of the HTSUS. On October 11, 2011, the Department added HTSUS 6804.21.00.00 to the scope description pursuant to a request by U.S. Customs and Border Protection. The tariff classification is provided for convenience and customs purposes; however, the written description, available in<E T="03">Diamond Sawblades and Parts Thereof From the People's Republic of China: Preliminary Results of Antidumping Duty Administrative Review:</E>
          <E T="03">2010-2011,</E>77 FR 73417 (December 10, 2012), is dispositive.</P>
        <HD SOURCE="HD1">Initiation of Changed Circumstances Review</HD>
        <P>Based on Hebei Husqvarna's request and in accordance with section 751(b)(1) of the Tariff Act of 1930, as amended (the Act), and 19 CFR 351.216(b), the Department is initiating a changed circumstances review to determine whether Hebei Husqvarna is the successor-in-interest to Hebei Husqvarna Jikai Diamond Tools Co., Ltd. In accordance with 19 CFR 351.221(b)(2), we will send to interested parties questionnaires requesting factual information for review.</P>

        <P>In accordance with 19 CFR 351.221(c)(3), the Department will publish in the<E T="04">Federal Register</E>a notice of preliminary results of this changed circumstances review, which will set forth the factual and legal conclusions upon which our preliminary results are based and a description of any action proposed based on those results.</P>
        <P>This notice of initiation is in accordance with section 751(b)(1) of the Act, 19 CFR 351.216(b) and (d), and 19 CFR 351.221(b)(1).</P>
        <SIG>
          <DATED>Dated: December 31, 2012.</DATED>
          <NAME>Gary Taverman,</NAME>
          <TITLE>Senior Advisor for Antidumping and Countervailing Duty Operations.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00158 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <RIN>RIN 0648-XC424</RIN>
        <SUBJECT>Endangered and Threatened Species; Take of Anadromous Fish</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of receipt of a scientific purposes and Enhancement of survival permit application and Hatchery and Genetic Management Plan (HGMP); notice of availability of draft environmental assessment (EA).</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>Notice is hereby given that NMFS has received an application for a permit for scientific purposes and to enhance the propagation and survival of a listed species under the Endangered Species Act of 1973, as amended (ESA), from the California Department of Fish and Game (CDFG) and PacifiCorp for a 10 year period. As part of this permit application, the CDFG has submitted a<PRTPAGE P="1201"/>draft HGMP. The HGMP specifies methods for the operation of the Iron Gate hatchery coho salmon program, located along the Klamath River, within the State of California. This document serves to notify the public of the availability of the permit application and HGMP for public review and comment prior to a decision by NMFS whether to issue the permit.</P>
          <P>This notice also announces the availability for public review and comment of a Draft Environmental Assessment (EA) regarding issuance of the permit, which involves take of coho salmon listed as threatened under the ESA.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>

          <P>Written comments on the permit application, draft HGMP, and draft EA must be received at the appropriate address or fax number (see<E T="02">ADDRESSES</E>) no later than 5 p.m. Pacific standard time on February 7, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Written comments on the application, draft HGMP or draft EA should be submitted to Jim Simondet, Klamath Branch Supervisor, NMFS Northern California Office, 1655 Heindon Rd, Arcata, California 95521. Comments may also be submitted via fax (707) 825-4840, or you may transmit your comment as an attachment to the following email address:<E T="03">IronGateHGMP.SWR@noaa.gov.</E>
          </P>

          <P>Copies of the draft EA and HGMP are available for public review during regular business hours from 9:00 a.m. to 5 p.m. at the NMFS Arcata office, 1655 Heindon Road, Arcata, CA 95521, (707) 825-5171. The permit application may be viewed online at:<E T="03">https://apps.nmfs.noaa.gov/preview/preview_open_for_comment.cfm.</E>
          </P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Jim Simondet, Klamath Branch Supervisor, NMFS, telephone (707) 825-5171, email:<E T="03">jim.simondet@noaa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Background</HD>
        <P>Section 9 of the ESA (16 U.S.C. 1538) and Federal regulations prohibit the take of fish or wildlife species listed as endangered or threatened. The term “take” is defined under the ESA to mean to harass, harm, pursue, hunt, shoot, wound, kill, trap, capture, or collect, or to attempt to engage in any such conduct (16 U.S.C. 1532(19)). NMFS may issue permits to take listed species for scientific purposes or to enhance the propagation or survival of the affected species under section 10(a)(1)(A) of the ESA (16 U.S.C. 1539(a)(1)(A)). NMFS regulations governing such permits are found at 50 CFR 222.308.</P>
        <P>The CDFG and PacifiCorp have applied for a permit under section 10(a)(1)(A) of the ESA for a period of 10 years that would allow CDFG to take adult and juvenile coho salmon in the threatened Southern Oregon/Northern California Coast Evolutionarily Significant Unit pursuant to a HGMP, which was developed with technical assistance from NMFS. The HGMP will be implemented as part of the existing coho salmon artificial propagation program at Iron Gate Hatchery. Actions taken pursuant to the permit are designed to enhance the survival of coho salmon residing in the Upper Klamath River below Iron Gate Dam.</P>
        <P>The HGMP incorporates two main components: Artificial propagation and monitoring and evaluation (M&amp;E). Artificial propagation activities that could lead to the take of listed coho salmon include: Adult broodstock collection, spawning, rearing, handling, evaluation, tagging and release of progeny. The HGMP includes measures to increase the fertilization of eggs and survival rate for each life stage and to minimize the likelihood of genetic or ecological effects to listed natural fish resulting from the hatchery operations and propagation of hatchery fish.</P>
        <P>Monitoring and evaluation will occur by conducting coho spawning ground and carcass surveys in the mainstem Klamath River and tributaries that comprise habitat for the Upper Klamath River coho salmon population unit. These data will be used to estimate adult natural and hatchery escapement levels and spawn timing to each stream for the Upper Klamath population unit as a whole. M&amp;E activities will also collect necessary data to document achievement of performance indicators specified in the HGMP. For a more detailed discussion of the project please see the permit application package.</P>
        <HD SOURCE="HD1">National Environmental Policy Act Compliance</HD>
        <P>Proposed permit issuance triggers the need for compliance with the National Environmental Policy Act (NEPA). NMFS has prepared a draft EA which evaluates the impacts of the proposed issuance of the permit and implementation of the HGMP, as well as the No Action Alternative in which the permit would not be issued and the HGMP may not be fully implemented.</P>
        <HD SOURCE="HD1">Public Comments Solicited</HD>
        <P>NMFS invites the public to comment on the permit application, draft HGMP, and draft EA during a 30 day public comment period beginning on the date of this notice. All comments and materials received, including names and addresses, will become part of the administrative record and may be released to the public. This notice is provided pursuant to section 10(c) of the ESA (16 U.S.C. 1529(c)) and regulations for implementing NEPA (40 CFR 1506.6). We provide this notice in order to allow the public, agencies, or other organizations to review and comment on these documents.</P>
        <HD SOURCE="HD1">Next Steps</HD>

        <P>NMFS will evaluate the application, associated documents, and comments submitted to determine whether the application meets the requirements of section 10(a)(1)(A) of the ESA and Federal regulations. The final permit decisions will not be made until after the end of the 30-day comment period and after NMFS has fully considered all relevant comments received during the comment period. NMFS will publish notice of its final action in the<E T="04">Federal Register</E>.</P>
        <SIG>
          <NAME>Angela Somma,</NAME>
          <TITLE>Chief, Endangered Species Division, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00137 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <RIN>RIN 0648-XC425</RIN>
        <SUBJECT>Endangered and Threatened Species; Take of Anadromous Fish</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Applications for two new scientific research permits and four research permit renewals.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>Notice is hereby given that NMFS has received six scientific research permit application requests relating to Pacific salmon. The proposed research is intended to increase knowledge of species listed under the Endangered Species Act (ESA) and to help guide management and conservation efforts. The applications may be viewed online at:<E T="03">https://apps.nmfs.noaa.gov/preview/preview_open_for_comment.cfm.</E>
          </P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>

          <P>Comments or requests for a public hearing on the applications must be received at the appropriate address or fax number (see<E T="02">ADDRESSES</E>) no later than 5 p.m. Pacific standard time on February 7, 2013.</P>
        </DATES>
        <ADD>
          <PRTPAGE P="1202"/>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Written comments on the applications should be sent to the Protected Resources Division, NMFS, 1201 NE Lloyd Blvd., Suite 1100, Portland, OR 97232-1274. Comments may also be sent via fax to 503-230-5441 or by email to<E T="03">nmfs.nwr.apps@noaa.gov.</E>
          </P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Rob Clapp, Portland, OR (ph.: 503-231-2314), Fax: 503-230-5441, email:<E T="03">Robert.Clapp@noaa.gov</E>). Permit application instructions are available from the address above, or online at<E T="03">https://apps.nmfs.noaa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Species Covered in This Notice</HD>
        <P>The following listed species are covered in this notice:</P>
        
        <FP SOURCE="FP-1">Chinook salmon (<E T="03">Oncorhynchus tshawytscha</E>): endangered upper Columbia River (UCR); threatened Snake River (SR) spring/sum (spr/sum); threatened SR fall;</FP>
        <FP SOURCE="FP-1">Steelhead (<E T="03">O. mykiss</E>): threatened UCR; threatened SR; threatened middle Columbia River (MCR).</FP>
        <FP SOURCE="FP-1">Sockeye salmon (<E T="03">O. nerka</E>): endangered SR.</FP>
        <HD SOURCE="HD1">Authority</HD>

        <P>Scientific research permits are issued in accordance with section 10(a)(1)(A) of the ESA (16 U.S.C. 1531<E T="03">et. seq</E>) and regulations governing listed fish and wildlife permits (50 CFR 222-226). NMFS issues permits based on findings that such permits: (1) Are applied for in good faith; (2) if granted and exercised, would not operate to the disadvantage of the listed species that are the subject of the permit; and (3) are consistent with the purposes and policy of section 2 of the ESA. The authority to take listed species is subject to conditions set forth in the permits.</P>

        <P>Anyone requesting a hearing on an application listed in this notice should set out the specific reasons why a hearing on that application would be appropriate (see<E T="02">ADDRESSES</E>). Such hearings are held at the discretion of the Assistant Administrator for Fisheries, NMFS.</P>
        <HD SOURCE="HD1">Applications Received</HD>
        <HD SOURCE="HD2">Permit 1124—5R</HD>
        <P>The Idaho Department of Fish and Game (IDFG) is seeking to renew for five years a permit under which they have been conducting six research projects in the Snake River basin for more than 10 years. The permit would continue to cover the following actions: One general fish population inventory; one project designed to monitor fish health throughout the state; two projects looking at natural and hatchery Chinook salmon production (in which sockeye may rarely be captured); one project monitoring natural steelhead; and one project centering on recovering sockeye salmon in Idaho. Much of the work being conducted under these projects is covered by other ESA authorizations; the work contemplated here is only the work that may affect sockeye salmon. The purposes of the research are therefore to monitor listed salmonid health, help guide sockeye salmon recovery operations, and out rightly rescue sockeye salmon in need of help due to circumstances such as being trapped by low flows. The benefits to the salmon will come in the form of information to help guide resource managers in restoring the listed fish and, as stated, in directly rescuing them from peril. The fish would be captured by various methods-screw traps, electrofishing, hook-and-line-angling, mid-water trawl-and most would immediately be released. A few of the captured fish may die as a result of the research.</P>
        <HD SOURCE="HD2">Permit 1134—6R</HD>
        <P>The Columbia River Inter-Tribal Fish Commission (CRITFC) is seeking to renew for five years a permit under which they have been conducting research for nearly 15 years. The permit would continue covering five study projects that, among them, would annually take adult and juvenile threatened SR fall Chinook salmon, adult and juvenile threatened SR spring/summer Chinook salmon, and adult and juvenile threatened SR steelhead in the Snake River basin. There have been some changes in the research over the last ten years; nonetheless, the projects proposed are largely continuations of ongoing research. They are: Project 1—Adult Spring/summer and Fall Chinook Salmon and Summer Steelhead Ground and Aerial Spawning Ground Surveys; Project 2—Cryopreservation of Spring/summer Chinook Salmon and Summer Steelhead Gametes; Project 3—Adult Chinook Salmon Abundance Monitoring Using Video Weirs, Acoustic Imaging, and PIT tag Detectors in the South Fork Salmon River; Project 4—Snorkel, Seine, fyke net, Minnow Trap, and Electrofishing Surveys and Collection of Juvenile Chinook Salmon and Steelhead; and Project 5—Juvenile Anadromous Salmonid Emigration Studies Using Rotary Screw Traps. Under these tasks, listed adult and juvenile salmon would be variously (1) observed/harassed during fish population and production monitoring surveys; (2) captured (using seines, trawls, traps, hook-and-line angling equipment, and electrofishing equipment) and anesthetized; (3) sampled for biological information and tissue samples, (4) PIT-tagged or tagged with other identifiers, (5) and released.</P>
        <P>The research has many purposes and would benefit listed salmon and steelhead in different ways. However, in general, the studies are part of ongoing efforts to monitor the status of listed species in the Snake River basin and to use those data to inform decisions about land- and fisheries management actions and to help prioritize and plan recovery measures for the listed species. Under the proposal, the studies would continue to benefit listed species by generating population abundance estimates, allowing comparisons to be made between naturally reproducing populations and those being supplemented with hatchery fish, and helping preserve listed salmon and steelhead genetic diversity. The CRITFC does not intend to kill any of the fish being captured, but a small percentage may die as a result of the research activities.</P>
        <HD SOURCE="HD2">Permit 1480—3R</HD>

        <P>The United States Geological Survey (USGS) is seeking to renew for five years a permit under which they have been conducting research for more than a decade. The renewed permit would continue to allow the USGS to annually take adult and juvenile endangered UCR Chinook and threatened UCR steelhead in nine tributaries to the Methow River (and its mainstem) in Washington State. The purpose of the research is to monitor the contribution these streams make to Chinook and steelhead production in the Methow subbasin—both before and after human-made passage barriers in the streams have been removed. The research would benefit the fish by generating information on the effectiveness of such restoration actions in the area and that information, in turn, would be used to guide other such efforts throughout the region. The USGS proposes to capture the fish—using weirs/traps, nets, and electrofishing equipment—anesthetize them, PIT-tag them (if they are large enough), allow them to recover, and release them. Several instream PIT-tag interrogation sites would be put into place to monitor the fish in the tributaries. In addition, tissue samples would be taken from some of the fish. The USGS does not intend to kill any of the fish being captured, but a small percentage may die as an unintended result of the research activities.<PRTPAGE P="1203"/>
        </P>
        <HD SOURCE="HD2">Permit 13380—2R</HD>
        <P>The NWFSC is seeking to renew for five years a permit that currently allows them to annually take natural juvenile SR spring/summer Chinook salmon and SR steelhead in the Salmon River subbasin in Idaho. This research has been in progress for over ten years and is designed to assess three alternative methods of nutrient enhancement (Salmon carcasses, carcass analogues, and nutrient pellets) on biological communities in Columbia River tributaries. In general, the purpose of the research is to learn how salmonids acquire nutrients from the carcasses of dead spawners and test three methods of using those nutrients to increase growth and survival among naturally produced salmonids. The research would benefit the fish by helping managers use nutrient enhancement techniques to recover listed salmonid populations. Moreover, managers would gain a broader understanding of the role marine-derived nutrients play in ecosystem health as a whole. This, in turn, would help inform management decisions and actions intended to help salmon recovery in the future.</P>
        <P>Under the proposed research, the fish would variously be (a) captured (using seines, nets, traps, and possibly, electrofishing equipment) and anesthetized; (b) measured, weighed and fin-clipped; (c) held for a time in enclosures in the stream from which they are captured; and (d) released. A number of the captured fish would also be intentionally killed so the researchers may conduct stable isotope, otolith, and diet analyses with the purpose of linking growth and survival to habitat conditions. It is also likely that a small percentage of the fish being captured would unintentionally be killed during the process; in such instances, any unintentional mortalities would be used in place of any fish that would otherwise be lethally taken. In addition, tissue samples would be taken from adult carcasses.</P>
        <HD SOURCE="HD2">Permit 16979</HD>
        <P>The Washington Department of Fish and Wildlife (WDFW) is seeking a five-year permit to collect data on UCR Chinook and steelhead abundance, status, distribution, diversity, species/ecological interactions, and behavior in the Columbia River from its confluence with the Yakima River upstream to Chief Joseph Dam. The research will benefit fish by helping managers (a) understand the distribution and proportion of hatchery and natural origin steelhead, and Chinook in UCR tributaries, (b) understand the influences of other biotic and abiotic factors with respect to recovering listed species, (c) understand the potential effects of proposed land use practices, (d) determine appropriate regulatory and habitat protection measures in the areas where land use actions are planned, (e) project the impacts of potential hydraulic projects, and (f) evaluate the effectiveness of local forest practices and instream habitat improvement projects in terms of their ability to protect and enhance listed salmonid populations.</P>
        <P>The researchers would capture fish via a wide variety of means (snorkeling, dip netting, seining, using electrofishing equipment, traps and weirs, and barbless hook-and-line sampling). The captured fish would be variously tissue sampled, measured, tagged, allowed to recover, and released. The researchers do not intend to kill any of the fish being captured, but a small percentage of them may inadvertently be killed as a result of the proposed activities.</P>
        <HD SOURCE="HD2">Permit 17306</HD>
        <P>The Oregon Department of Fish and Wildlife (ODFW) is seeking a five-year permit to capture threatened MCR steelhead (adults and juveniles) in the upper Deschutes River, Oregon. The various proposed activities would include adult and juvenile snorkel surveys throughout the basin, screw trapping, backpack and boat electrofishing and mark/recapture studies, hook and line surveys, telemetry, seining, spawning ground surveys using weirs and redd counts, monitoring habitat restoration projects, and setting traps and nets in reservoirs for population monitoring. Data collected from this work would be used to inform management decisions. Biologists from the ODFW have been conducting this work in the area for decades without the need for a permit, but since threatened MCR steelhead have recently been reintroduced to the area, they are seeking a permit that would allow them to continue it. The researchers do not intend to kill any of the fish being captured, but a small percentage may be killed as an inadvertent result of the activities.</P>

        <P>This notice is provided pursuant to section 10(c) of the ESA. NMFS will evaluate the applications, associated documents, and comments submitted to determine whether the applications meet the requirements of section 10(a) of the ESA and Federal regulations. The final permit decisions will not be made until after the end of the 30-day comment period. NMFS will publish notice of its final action in the<E T="04">Federal Register</E>.</P>
        <SIG>
          <NAME>Angela Somma,</NAME>
          <TITLE>Chief, Endangered Species Division, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00138 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <RIN>RIN 0648-XC426</RIN>
        <SUBJECT>Endangered and Threatened Species; Take of Anadromous Fish</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Issuance of five scientific research permits.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Notice is hereby given that NMFS has issued Permit 14808 to the California Department of Fish and Game (CDFG), Permit 15573 to the Glenn-Colusa Irrigation District (GCID), Permit 16543 to the California Department of Water Resources (CDWR), Permit 13791 to the United States Fish and Wildlife Service (USFWS), and Permit 17077 to Dr. Peter Moyle with the University of California, Davis (UCD).</P>
        </SUM>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>The approved application for each permit is available on the Applications and Permits for Protected Species (APPS),<E T="03">https://apps.nmfs.noaa.gov</E>Web site by searching the permit number within the Search Database page. The applications, issued permits and supporting documents are also available upon written request or by appointment: Protected Resources Division, NMFS, 650 Capitol Mall, Room 5-100, Sacramento, CA 95814 (phone: (916) 930-3600, fax: (916) 930-3629).</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Amanda Cranford at 916-930-3706, or email:<E T="03">Amanda.Cranford@noaa.gov.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Authority</HD>

        <P>The issuance of permits and permit modifications, as required by the Endangered Species Act of 1973 (16 U.S.C. 1531-1543) (ESA), is based on a finding that such permits/modifications: (1) Are applied for in good faith; (2) would not operate to the disadvantage of the listed species which are the subject of the permits; and (3) are consistent with the purposes and policies set forth in section 2 of the<PRTPAGE P="1204"/>ESA. Authority to take listed species is subject to conditions set forth in the permits. Permits and modifications are issued in accordance with and are subject to the ESA and NMFS regulations (50 CFR parts 222-226) governing listed fish and wildlife permits.</P>
        <HD SOURCE="HD1">Species Covered in This Notice</HD>

        <P>This notice is relevant to federally endangered Sacramento River (SR) winter-run Chinook salmon (<E T="03">Oncorhyncus tshawytscha</E>), threatened Central Valley (CV) spring-run Chinook salmon (<E T="03">O. tshawytscha</E>), threatened California Central Valley (CCV) steelhead (<E T="03">O. mykiss</E>), and threatened southern distinct population segment (SDPS) of North American green sturgeon (<E T="03">Acipenser medirostris</E>), henceforth referred to as ESA-listed salmonids and SDPS green sturgeon.</P>
        <HD SOURCE="HD1">Permits Issued</HD>
        <HD SOURCE="HD2">Permit 14808</HD>

        <P>A notice of the receipt of an application for a scientific research permit (14808) was published in the<E T="04">Federal Register</E>on April 24, 2012 (77 FR 24469). Permit 14808 was issued to CDFG on September 26, 2012 and expires on December 31, 2017.</P>
        <P>Permit 14808 is for research to be conducted at two different sites within the upper Sacramento River, California. The main purpose of the research conducted by CDFG is to monitor the outmigration of juvenile salmonids on a real-time basis and provide daily summaries of timing, abundance and size distribution of salmonids in the Sacramento River at two different sites before they enter the Delta. Data can then be forwarded to various water agencies for better management decisions and to reduce frequency of ESA-listed fish entrainment. Permit 14808 authorizes capture (by rotary screw trap), anesthetizing, handling (fork length measurements and wet weights), and release of smolt and juvenile SR winter-run and CV spring-run Chinook salmon, adult and juvenile CCV steelhead and juvenile SDPS green sturgeon downstream of the trapping location.</P>
        <P>Permit 14808 authorizes non-lethal take and low levels (not to exceed two percent) of unintentional lethal take. Permit 14808 also authorizes intentional, directed lethal take of smolt and juvenile adipose fin-clipped, hatchery produced, SR winter-run Chinook salmon for coded wire tag retrieval and processing.</P>
        <HD SOURCE="HD2">Permit 15573</HD>

        <P>A notice of the receipt of an application for a scientific research and enhancement permit renewal (15573) was published in the<E T="04">Federal Register</E>on December 15, 2010 (75 FR 78226). Permit 15573 was issued to GCID on October 5, 2012 and expires on December 31, 2017.</P>
        <P>Permit 15573 is for research to be conducted in an oxbow of the Sacramento River, immediately downstream of the Hamilton City Pumping Plant, Glenn County, California. The primary objectives to which ESA-listed salmonids and SDPS green sturgeon may be taken are to collect emigration data as a reference and research tool to provide short-term monitoring specifically related to restoration actions and long-term monitoring to detect annular and cyclic population changes. Take activities associated with research on smolt and juvenile ESA-listed salmonids and juvenile SDPS green sturgeon include the following: capture (by rotary screw trap), anesthetizing, and release of fish downstream of the trapping location.</P>
        <P>Permit 15573 authorizes non-lethal and low levels (not to exceed two percent) of unintentional lethal take of smolt and juvenile ESA-listed salmonids and juvenile SDPS green sturgeon. Permit 15573 does not authorize any intentional lethal take of ESA-listed salmonids and SDPS green sturgeon.</P>
        <HD SOURCE="HD2">Permit 16543</HD>

        <P>A notice of the receipt of an application for a scientific research and enhancement permit (16543) was published in the<E T="04">Federal Register</E>on July 18, 2012 (77 FR 42278). Permit 16543 was issued to CDWR on October 22, 2012 and expires on December 31, 2014.</P>
        <P>Permit 16543 is for research to be conducted in the Sacramento-San Joaquin Delta, California. The primary objectives to which ESA-listed salmonids and SDPS green sturgeon may be taken are to provide information on spatial and environmental patterns of predation; critical information for guiding future restoration projects on conditions likely to support or discourage higher predation rates on ESA-listed and native fishes. Take activities associated with research on adult ESA-listed salmonids and both juvenile and adult SDPS green sturgeon include the following: capture (by trammel net), handling (species identification and enumeration), and release of fish downstream of the capture location.</P>
        <P>Permit 16543 authorizes CDWR non-lethal take of adult ESA-listed salmonids and both juvenile and adult SDPS green sturgeon. Permit 16543 does not authorize any unintentional or intentional lethal take of ESA-listed salmonids and SDPS green sturgeon.</P>
        <HD SOURCE="HD2">Permit 13791</HD>

        <P>A notice of the receipt of an application for a scientific research and enhancement permit (13791) was published in the<E T="04">Federal Register</E>on April 24, 2012 (77 FR 24469). Permit 13791 was issued to USFWS on October 23, 2012 and expires on December 31, 2015.</P>
        <P>Permit 13791 is for research to be conducted in the Sacramento River basin and the Sacramento-San Joaquin Delta, California. The primary objectives to which ESA-listed salmonids and SDPS green sturgeon may be taken by the USFWS' Delta Juvenile Fish Monitoring Program and the Breach III Project are to provide basic biological and population information on fishes of management concern. Additionally, data collected can be used by natural resource managers to evaluate the effectiveness of water operations, aquatic habitat restoration, and fish management practices within the San Francisco Estuary (SFE) and its watershed. Take activities associated with research on juvenile ESA-listed salmonids and SDPS green sturgeon include the following: capture (by fyke nets, multi-mesh gill nets, larval fish trawls, midwater trawls, Kodiak trawls, electrofishing and beach seines), handling (species and race identification and enumeration, fork-length measurements, tissue/scale samples if applicable), and release of fish downstream of the capture location.</P>
        <P>Permit 13791 authorizes non-lethal take and low levels (not to exceed 12.5 percent) of unintentional lethal take. Permit 13791 also authorizes intentional, directed lethal take of smolt and juvenile adipose fin-clipped, hatchery produced, SR winter-run and CV spring-run Chinook salmon for coded wire tag retrieval and processing.</P>
        <HD SOURCE="HD2">Permit 17077</HD>

        <P>A notice of the receipt of an application for a scientific research and enhancement permit (17077) was published in the<E T="04">Federal Register</E>on August 24, 2012 (77 FR 51520). Permit 17077 was issued to Dr. Peter Moyle on November 26, 2012 and expires on December 31, 2015.</P>

        <P>Permit 17077 is for research to be conducted in three distinct regions across the SFE: the Cache-Lindsay Slough complex, the Sherman Lake<PRTPAGE P="1205"/>complex, and Suisun Marsh. The primary objectives to which ESA-listed salmonids and SDPS green sturgeon may be taken by Dr. Moyle are to determine the extent that native fishes use intertidal and subtidal shallow water and marsh (SWM) habitats in the northern arc of the SFE and to understand how fishes commonly inhabiting Suisun Marsh use the Sacramento River corridor to access SWM habitats that are not currently surveyed in Sherman Lake, Cache Slough and Lindsey Slough. Further, Dr. Moyle will model fish abundance and assembly using biophysical habitat data (including slough geomorphology, hydrology, and water quality) to guide restoration projects that will successfully support native fishes and discourage aliens.</P>
        <P>Permit 17077 authorizes non-lethal take and low levels (not to exceed 20 percent, equivalent to one fish) of unintentional lethal take of adult and juvenile ESA-listed salmonids and both adult and juvenile SDPS green sturgeon. Permit 17077 does not authorize any intentional lethal take of ESA-listed salmonids or SDPS green sturgeon.</P>
        <SIG>
          <NAME>Angela Somma,</NAME>
          <TITLE>Chief, Endangered Species Division, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00139 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
        <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
        <RIN>RIN 0648-XC359</RIN>
        <SUBJECT>Taking and Importing Marine Mammals; Taking Marine Mammals Incidental to Hydrographic Surveys</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice; receipt of application for letter of authorization; request for comments and information.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>NMFS' Office of Protected Resources has received a request from the NOAA Office of Coast Survey (OCS) for authorization to take small numbers of marine mammals incidental to conducting hydrographic surveys, over the course of 5 years from the date of issuance. Pursuant to regulations implementing the Marine Mammal Protection Act (MMPA), NMFS is announcing receipt of OCS's request under the MMPA for the development and implementation of regulations governing the incidental taking of marine mammals. We invite information, suggestions, and comments on OCS's application and request.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments and information must be received no later than February 7, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Comments on the application should be addressed to P. Michael Payne, Chief, Permits and Conservation Division, Office of Protected Resources, National Marine Fisheries Service, 1315 East-West Highway, Silver Spring, MD 20910-3225. The mailbox address for providing email comments is<E T="03">ITP.Laws@noaa.gov.</E>We are not responsible for email comments sent to addresses other than the one provided here. Comments sent via email, including all attachments, must not exceed a 10-megabyte file size.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ben Laws, Office of Protected Resources, NMFS, (301) 427-8401.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Availability</HD>

        <P>An electronic copy of OCS's application may be obtained by visiting theInternet at:<E T="03">http://www.nmfs.noaa.gov/pr/permits/incidental.htm#applications.</E>
        </P>
        

        <P>The OCS released a draft Environmental Assessment, prepared pursuant to requirements of the National Environmental Policy Act, for the conduct of their hydrographic surveys on June 20, 2012. A copy of the draft EA which would also support our proposed rulemaking under the MMPA, is also available at<E T="03">http://www.nauticalcharts.noaa.gov/Legal/.</E>
        </P>
        <HD SOURCE="HD1">Background</HD>
        <P>Section 101(a)(5)(A) of the MMPA (16 U.S.C. 1361<E T="03">et seq.</E>) directs the Secretary of Commerce (Secretary) to allow, upon request, the incidental, but not intentional, taking of small numbers of marine mammals by U.S. citizens who engage in a specified activity (other than commercial fishing) if certain findings are made and regulations are issued.</P>
        <P>Incidental taking shall be allowed if NMFS finds that the taking will have a negligible impact on the species or stock(s) affected and will not have an unmitigable adverse impact on the availability of the species or stock(s) for taking for subsistence uses, and if the permissible methods of taking and requirements pertaining to the mitigation, monitoring and reporting of such taking are set forth.</P>
        <P>NMFS has defined “negligible impact” in 50 CFR 216.103 as “an impact resulting from the specified activity that cannot be reasonably expected to, and is not reasonably likely to, adversely affect the species or stock through effects on annual rates of recruitment or survival.” Except with respect to certain activities not pertinent here, the MMPA defines “harassment” as: “any act of pursuit, torment, or annoyance which (i) has the potential to injure a marine mammal or marine mammal stock in the wild [Level A harassment]; or (ii) has the potential to disturb a marine mammal or marine mammal stock in the wild by causing disruption of behavioral patterns, including, but not limited to, migration, breathing, nursing, breeding, feeding, or sheltering [Level B harassment].”</P>
        <HD SOURCE="HD1">Summary of Request</HD>
        <P>On December 27, 2012, we received a complete and adequate application from OCS requesting authorization for take of marine mammals incidental to hydrographic surveys conducted by OCS. The requested governing regulations would be valid for 5 years from the date of issuance. OCS operates active acoustic devices that have the potential to disturb marine mammals, and operates throughout coastal waters of the U.S. Exclusive Economic Zone. During 2013-18, OCS plans to conduct surveys in all coastal waters of the U.S. except for those in the Caribbean and in Hawaii and other Pacific islands. Because the specified activities have the potential to take marine mammals present within the action areas, OCS requests authorization to take small numbers of multiple species or stocks of marine mammal.</P>
        <HD SOURCE="HD1">Specified Activities</HD>
        <P>Hydrographic survey projects support OCS's mandated mission to provide reliable nautical charts and other products necessary for safe navigation, economic security, and environmental sustainability in U.S. coastal waters. OCS surveys approximately 3,000 square nautical miles of coastal waters each year, and proposes to continue the same level of activity. In order to conduct these surveys, OCS uses active acoustic devices, including some that may result in behavioral harassment of marine mammals. These include high-frequency single-beam and multibeam echosounders and side-scan sonars mounted on or towed behind vessels traveling at a slow speed.</P>

        <P>A more detailed description of the hydrographic surveys conducted by OCS may be found in their application, which is available at:<E T="03">http://www.nmfs.noaa.gov/pr/permits/incidental.htm.</E>
          <PRTPAGE P="1206"/>
        </P>
        <HD SOURCE="HD1">Information Solicited</HD>

        <P>Interested persons may submit information, suggestions, and comments concerning OCS's request (see<E T="02">ADDRESSES</E>). We will consider all information, suggestions, and comments related to the request during the development of proposed regulations governing the incidental taking of marine mammals by OCS, if appropriate.</P>
        <SIG>
          <NAME>Helen M. Golde,</NAME>
          <TITLE>Acting Director, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00135 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3510-22-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Department of the Navy</SUBAGY>
        <SUBJECT>Notice of Availability of Government-Owned Inventions; Available for Licensing</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Department of the Navy, DoD.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The inventions listed below are assigned to the United States Government as represented by the Secretary of the Navy and are available for licensing by the Department of the Navy.</P>
          <P>The following patents are available for licensing: Patent application 12/650,413: Finite State Machine Architecture for Software Development (a system for developing an application program having functionality that corresponds to a finite state machine model)//U.S. Patent No. 8,238,924: Real-Time Optimization of Allocation of Resources//U.S. Patent No. 7,685,207: Adaptive Web-Based Asset Control System.</P>
        </SUM>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Requests for copies of the patents cited should be directed to Office of Counsel, Naval Surface Warfare Center, Crane Div, Code OOL, Bldg 2, 300 Highway 361, Crane, IN 47522-5001.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Mr. Christopher Monsey, Naval Surface Warfare Center, Crane Div, Code OOL, Bldg 2, 300 Highway 361, Crane, IN 47522-5001, telephone (812) 854-4100.</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>35 U.S.C. 207, 37 CFR part 404.</P>
          </AUTH>
          <SIG>
            <DATED>Dated: December 31, 2012.</DATED>
            <NAME>C. K. Chiappetta,</NAME>
            <TITLE>Lieutenant Commander, Office of the Judge Advocate General, U.S. Navy, Federal Register Liaison Officer.</TITLE>
          </SIG>
        </FURINF>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00066 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3810-FF-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF DEFENSE</AGENCY>
        <SUBAGY>Department of the Navy</SUBAGY>
        <SUBJECT>Notice of Intent To Grant Exclusive Patent License; Allied Communications, LLC</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Department of the Navy, DoD.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Department of the Navy hereby gives notice of its intent to grant to Allied Communications, LLC., a revocable, nonassignable, exclusive license to practice in the United States, the Government-owned inventions described in U.S. Patent No. 7,685,207: Adaptive Web-Based Asset Control System, Navy Case No. 83634, issued March 23, 2010.//U.S. Patent application No. 12/650,413: Finite State Machine Architecture For Software Development, Navy Case No. 99,766, filed December 30, 2009.//U.S. Patent No. 8,238,924: Real-Time Optimization of Allocation of Resources, Navy Case No. 99956, issued August 7, 2012.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Anyone wishing to object to the grant of this license must file written objections along with supporting evidence, if any, not later than January 23, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Written objections are to be filed with Naval Surface Warfare Center, Crane Div, Code OOL, Bldg 2, 300 Highway 361, Crane, IN 47522-5001.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Mr. Christopher Monsey, Naval Surface Warfare Center, Crane Div, Code OOL, Bldg 2, 300 Highway 361, Crane, IN 47522-5001, telephone 812-854-4100.</P>
          <AUTH>
            <HD SOURCE="HED">Authority:</HD>
            <P>35 U.S.C. 207, 37 CFR part 404.</P>
          </AUTH>
          <SIG>
            <DATED>Dated: December 31, 2012.</DATED>
            <NAME>C. K. Chiappetta,</NAME>
            <TITLE>Lieutenant Commander, Office of the Judge Advocate General, U.S. Navy, Federal Register Liaison Officer.</TITLE>
          </SIG>
        </FURINF>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00068 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3810-FF-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEFENSE NUCLEAR FACILITIES SAFETY BOARD</AGENCY>
        <SUBJECT>Second Extension of Hearing Record Closure Date</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Defense Nuclear Facilities Safety Board.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Second extension of hearing record closure date.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The Defense Nuclear Facilities Safety Board (Board) published a document in the<E T="04">Federal Register</E>on August 15, 2012, (77 FR 48970), as amended, September 7, 2012, (77 FR 55196). The publication concerned notice of a hearing and meeting on October 2, 2012, regarding safety-related aspects of the design and factors that could affect the timely execution of the Uranium Processing Facility (UPF) project at the Y-12 National Security Complex. The Board stated in the August 15, 2012, hearing notice that the hearing record would remain open until November 2, 2012, for the receipt of additional materials. The Board subsequently extended the hearing record closure date to January 2, 2013 (77 FR 65871).</P>
          <P>
            <E T="03">Extension of Time:</E>The Board now extends the period of time for which the hearing record will remain open to January 16, 2013, to further accommodate submission of answers to questions taken for the record during the course of the public hearing.</P>
          <P>
            <E T="03">Contact Person for Further Information:</E>Debra H. Richardson, Deputy General Manager, Defense Nuclear Facilities Safety Board, 625 Indiana Avenue NW., Suite 700, Washington, DC 20004-2901, (800) 788-4016. This is a toll-free number.</P>
        </SUM>
        <SIG>
          <DATED>Dated: January 2, 2013.</DATED>
          <NAME>Peter S. Winokur,</NAME>
          <TITLE>Chairman.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00096 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 3670-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF EDUCATION</AGENCY>
        <SUBJECT>Privacy Act of 1974; System of Records—Evaluation of the Pell Grant Experiments Under the Experimental Sites Initiative—2012</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Institute of Education Sciences, Department of Education.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of a new system of records.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>In accordance with the Privacy Act of 1974, as amended (Privacy Act), the Department of Education (Department) publishes this notice of a new system of records entitled “Evaluation of the Pell Grant Experiments Under the Experimental Sites Initiative—2012” (18-13-31).</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Submit your comments on this proposed new system of records on or before February 7, 2013.</P>

          <P>The Department filed a report describing the new system of records covered by this notice with the Chair of the Senate Committee on Homeland Security and Governmental Affairs, the Chair of the House Committee on Oversight and Government Reform, and the Administrator of the Office of Information and Regulatory Affairs,<PRTPAGE P="1207"/>Office of Management and Budget (OMB) on January 3, 2013. This system of records will become effective at the later date of: (1) The expiration of the 40-day period for OMB review on February 12, 2013, unless OMB waives 10 days of the 40-day review period for compelling reasons shown by the Department, or (2) February 7, 2013, unless the system of records needs to be changed as a result of public comment or OMB review.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Address all comments about this new system of records to Dr. Audrey Pendleton, Associate Commissioner, Evaluation Division, National Center for Education Evaluation and Regional Assistance, Institute of Education Sciences, U.S. Department of Education, 555 New Jersey Avenue NW., room 502D, Washington, DC 20208-0001. Telephone: (202) 208-7078. If you prefer to send comments through the Internet, use the following address:<E T="03">comments@ed.gov</E>.</P>
          <P>You must include the term “Pell Grant Experiments Under the Experimental Sites Initiative—2012” in the subject line of the electronic message.</P>
          <P>During and after the comment period, you may inspect all comments about this notice at the U.S. Department of Education in room 502D, 555 New Jersey Avenue NW., Washington, DC, between the hours of 8:00 a.m. and 4:30 p.m., Eastern time, Monday through Friday of each week except Federal holidays.</P>
        </ADD>
        <HD SOURCE="HD2">Assistance to Individuals With Disabilities in Reviewing the Rulemaking Record</HD>

        <P>On request we will provide an appropriate accommodation or auxiliary aid to an individual with a disability who needs assistance to review the comments or other documents in the public rulemaking record for this notice. If you want to schedule an appointment for this type of accommodation or auxiliary aid, please contact the person listed under<E T="02">FOR FURTHER INFORMATION CONTACT</E>.</P>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Dr. Marsha Silverberg. Telephone: (202)208-7178. If you use a telecommunications device for the deaf (TDD) or text telephone (TTY), call the Federal Relay Service (FRS), toll free, at 1-800-877-8339.</P>
          <P>Individuals with disabilities can obtain this document in an accessible format (e.g., braille, large print, audiotape, or compact disc) on request to the contact person listed in this section.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Introduction</HD>

        <P>The Privacy Act (5 U.S.C. 552a) requires the Department to publish in the<E T="04">Federal Register</E>this notice of a new system of records maintained by the Department. The Department's regulations implementing the Privacy Act are contained in part 5b of Title 34 of the Code of Federal Regulations (CFR).</P>
        <P>The Privacy Act applies to any record about an individual that is maintained in a system of records from which individually identifying information is retrieved by a unique identifier associated with each individual, such as a name or Social Security Number. The information about each individual is called a “record,” and the system, whether manual or computer-based, is called a “system of records.”</P>

        <P>The Privacy Act requires each agency to publish a notice of a system of records in the<E T="04">Federal Register</E>and to prepare and send a report to OMB whenever the agency publishes a new system of records or makes a significant change to an established system of records. Each agency is also required to send copies of the report to the Chair of the Senate Committee on Homeland Security and Governmental Affairs and the Chair of the House Committee on Oversight and Government Reform. These reports are inc1uded to permit an evaluation of the probable effect of the proposal on the privacy rights of individuals.</P>
        <P>The National Center for Education Evaluation and Regional Assistance at the Department's Institute of Education Sciences (IES) commissioned a study to conduct an evaluation of the impacts of two different experiments involving the Pell Grant eligibility criteria. The first experiment expands eligibility for Pell Grants to income-eligible students who already possess a bachelor's degree and who enroll in occupational training. The second experiment expands eligibility for Pell Grants to students who enroll in occupational programs that have a shorter duration than allowable under current rules. Both experiments are being implemented under the Experimental Sites Initiative (ESI), authorized by section 487A(b) of the Higher Education Act of 1965 (HEA) (20 U.S.C. 1094a(b)), which allows the Secretary to grant waivers from specific title IV HEA statutory or regulatory requirements to allow institutions to test alternative methods for administering those Federal student aid programs. The study will compare students with expanded access to Pell Grants to similar students who will not have access, in order to assess the effects of expanded Pell Grant access on educational attainment, employment, and earnings. It will be conducted under a contract that IES awarded in September 2012.</P>
        <P>The study will provide credible and reliable information to help guide future policy decisions in the area of Federal financial aid. The central research questions that the study will address are: What is the impact of expanding Pell Grant eligibility on employment and earnings? Does it improve access to occupational training? How does it affect financial aid receipt and student debt?</P>
        <P>The system will contain records on approximately 10,800 students from approximately 51 participating institutions of higher education.</P>
        <P>
          <E T="03">Electronic Access to This Document:</E>The official version of this document is the document published in the<E T="04">Federal Register</E>. Free Internet access to the official edition of the<E T="04">Federal Register</E>and the Code of Federal Regulations is available via the Federal Digital System at:<E T="03">www.gpo.gov/fdsys.</E>At this site you can view this document, as well as all other documents of this Department published in the<E T="04">Federal Register</E>, in text or Adobe Portable Document Format (PDF). To use PDF you must have Adobe Acrobat Reader, which is available free at the site.</P>

        <P>You may also access documents of the Department published in the<E T="04">Federal Register</E>by using the articlesearch feature at:<E T="03">www.federalregister.gov.</E>Specifically, through the advanced search feature at this site, you can limit your search to documents published by the Department.</P>
        <SIG>
          <DATED>Dated: January 3, 2013.</DATED>
          <NAME>John Q. Easton,</NAME>
          <TITLE>Director, Institute of Education Sciences.</TITLE>
        </SIG>
        <P>For the reasons discussed in the preamble, the Director of the Institute of Education Sciences, U.S. Department of Education, publishes a notice of a new system of records to read as follows:</P>
        <PRIACT>
          <HD SOURCE="HD1">SYSTEM NUMBER:</HD>
          <P>18-13-31.</P>
          <HD SOURCE="HD2">SYSTEM NAME:</HD>
          <P>Evaluation of the Pell Grants Experiments Under the Experimental Sites Initiative—2012.</P>
          <HD SOURCE="HD2">SECURITY CLASSIFICATION:</HD>
          <P>None.</P>
          <HD SOURCE="HD2">SYSTEM LOCATIONS:</HD>

          <P>(1) Evaluation Division, National Center for Education Evaluation and Regional Assistance, Institute of Education Sciences (IES), U.S.<PRTPAGE P="1208"/>Department of Education, 555 New Jersey Avenue NW., room 502D, Washington, DC 20208-0001.</P>
          <P>(2) Social Policy Research Associates, 1330 Broadway, Suite 1426, Oakland, CA 94612-2513 (contractor).</P>
          <P>(3) Mathematica Policy Research, Inc., 600 Alexander Park, Princeton, NJ 08540-6346 (subcontractor).</P>
          <HD SOURCE="HD2">CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:</HD>
          <P>The system will contain records on approximately 10,800 students from approximately 51 institutions of higher education.</P>
          <HD SOURCE="HD2">CATEGORIES OF RECORDS IN THE SYSTEM:</HD>
          <P>The system of records includes individually identifying information about the students who agree to participate in the study. This information includes name, birth date, and contact information; demographic information such as race, ethnicity, gender, age, and educational background; the type of program in which the student is enrolled, the student's progress through the program (credits earned) including completion; methods used to pay for the education and training, including financial aid received and amount of student debt incurred; receipt of support services; and information on employment and earnings.</P>
          <P>It is also our intention to include students' Social Security Numbers (SSNs) to obtain information on their financial aid and their employment and earnings; we expect to obtain the students' employment and earnings data from the administrative records of another Federal agency. Other methods for obtaining the information (i.e., self-reporting) have proven to be infeasible and unreliable. SSNs are necessary to obtain the needed employment and earnings data, and this method will place a low burden on students and will not be costly to the Federal government.</P>
          <HD SOURCE="HD2">AUTHORITY FOR MAINTENANCE OF THE SYSTEM:</HD>
          <P>The study is authorized by section 487A(b)(2) of the Higher Education Act of 1965 (HEA), 20 U.S.C. 1094a(b)(2), which requires the Secretary of Education to review and evaluate the experiences of institutions that participate as experimental sites and to submit a biennial report based on the review and evaluation to the Committee on Health, Education, Labor, and Pensions of the Senate and the Committee on Education and Labor of the House of Representatives. The study is also authorized by section 173(a)(1)(A) of the Education Sciences Reform Act of 2002 (ESRA) (20 U.S.C. 9563(a)(1)(A)), which authorizes the National Center for Education Evaluation and Regional Assistance to conduct evaluations of Federal education programs administered by the Secretary and to determine the impact of such programs.</P>
          <HD SOURCE="HD2">PURPOSE(S):</HD>
          <P>The information contained in the records maintained in this system will support an evaluation of the impacts of two different experimental expansions to the Pell Grant eligibility criteria. The first experiment expands eligibility for Pell Grants to income-eligible students who already possess a bachelor's degree and who enroll in occupational training, while the second experiment expands eligibility for Pell Grants to students who enroll in occupational programs that have a shorter duration than allowable under current rules. Both experiments are being implemented under the Experimental Sites Initiative (ESI), authorized by section 487A(b) of the HEA. The study will compare students with expanded access to Pell Grants to similar students who will not have access in order to assess the effects of expanded Pell Grant access on educational attainment, employment, and earnings. The study will address the following research questions:</P>
          <P>
            <E T="03">1. What is the impact of expanding Pell Grant eligibility on employment and earnings?</E>The ultimate goal of the study is to determine if providing Pell Grants for those with a bachelor's degree and for relatively short-term job training affects participants' job prospects and income levels.</P>
          <P>
            <E T="03">2. Does it improve access to occupational training?</E>Understanding whether the experiments made a difference in training enrollments will help in interpreting the presence or lack of earnings impacts.</P>
          <P>
            <E T="03">3. How does it affect financial aid receipt and student debt?</E>With student debt loads being an increasing public policy concern, expansions in Pell Grant eligibility are intended to reduce reliance on loans that may carry high interest levels. The study will examine the impacts of the experiments on the types and amounts of financial aid students receive and on their expenditures for education and training.</P>
          <HD SOURCE="HD2">ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND THE PURPOSES OF SUCH USES:</HD>
          <P>The Department of Education (Department) may disclose information contained in a record in this system of records under the routine uses listed in this system of records without the consent of the individual if the disclosure is compatible with the purposes for which the record was collected. These disclosures may be made on a case-by-case basis or, if the Department has complied with the computer matching requirements of the Privacy Act of 1974, as amended (Privacy Act), under a computer matching agreement. Any disclosure of individually identifiable information from a record in this system must also comply with the requirements of section 183 of the ESRA (20 U.S.C. 9573) providing for confidentiality standards that apply to all collections, reporting, and publication of data by IES.</P>
          <P>(1)<E T="03">Contract Disclosure.</E>If the Department contracts with an entity for the purposes of performing any function that requires disclosure of records in this system to employees of the contractor, the Department may disclose the records to those employees. Before entering into such a contract, the Department shall require the contractor to maintain Privacy Act safeguards as required under 5 U.S.C. 552a(m) with respect to the records in the system.</P>
          <P>(2)<E T="03">Federal Agency Disclosure.</E>The Department may disclose records from this system of records to another Federal agency for the purposes of allowing that agency to provide assistance to the Department with the evaluation of a federally supported education program. Under the requirements of the Family Educational Rights and Privacy Act (FERPA), 20 U.S.C. 1232g and 34 CFR part 99, the Department will enter into an interagency agreement with the other Federal agency designating that agency as the Department's authorized representative before disclosing any personally identifiable information from any students' education records to that Federal agency. Under the terms of such an interagency agreement, the Federal agency will not be permitted to redisclose any personally identifiable information obtained from students' education records, and will be required to destroy any personally identifiable information from students' education records when no longer needed for the purposes of the evaluation as well as to maintain safeguards to protect the confidentiality of any personally identifiable information disclosed.</P>
          <P>(3)<E T="03">Research Disclosure.</E>The Director of the Institute of Education Sciences may disclose information from this system of records to qualified researchers solely for the purpose of carrying out specific research that is compatible with the purpose(s) of this system of records. The researcher shall be required to maintain safeguards under the Privacy Act of 1974 and section 183 of the ESRA (20 U.S.C.<PRTPAGE P="1209"/>9573(c)) with respect to such records. When personally identifiable information from a student's education record will be disclosed to the researcher under FERPA, the researcher also shall be required to comply with the requirements in the applicable FERPA exception to consent.</P>
          <HD SOURCE="HD2">DISCLOSURE TO CONSUMER REPORTING AGENCIES:</HD>
          <P>Not applicable to this system of records.</P>
          <HD SOURCE="HD2">POLICIES AND PRACTICES FOR STORING, RETRIEVING, ACCESSING, RETAINING, AND DISPOSING OF RECORDS IN THE SYSTEM:</HD>
          <HD SOURCE="HD2">STORAGE:</HD>
          <P>The Department maintains records on CD-ROM, and the contractor (Social Policy Research Associates) and sub-contractor (Mathematica Policy Research, Inc.) maintain data for this system on computers and in hard copy.</P>
          <HD SOURCE="HD2">RETRIEVABILITY:</HD>
          <P>Records in this system are indexed and retrieved by a number assigned to each individual that is cross-referenced by the individual's name on a separate list.</P>
          <HD SOURCE="HD2">SAFEGUARDS:</HD>
          <P>All physical access to the Department's site and to the site of the Department's contractor and subcontractor, where this system of records is maintained, is controlled and monitored by security personnel. The computer system employed by the Department offers a high degree of resistance to tampering and circumvention. This security system limits data access to Department and contract staff on a need-to-know basis, and controls individual users' ability to access and alter records within the system. The contractor and subcontractor will establish a similar set of procedures at its site to ensure confidentiality of data. The contractor's and subcontractor's systems are required to ensure that information identifying individuals is in files physically separated from other research data. The contractor and subcontractor will maintain security of the complete set of all master data files and documentation. Access to individually identifying data will be strictly controlled. All data will be kept in locked file cabinets during nonworking hours, and work on hardcopy data will take place in a single room, except for data entry. Physical security of electronic data will also be maintained. Security features that protect project data include: Password-protected accounts that authorize users to use the contractor's system but to access only specific network directories and network software; user rights and directory and file attributes that limit those who can use particular directories and files and determine how they can use them; and additional security features that the network administrators will establish for projects as needed. The contractor's and subcontractor's employees who “maintain” (collect, maintain, use, or disseminate) data in this system shall comply with the requirements of the confidentiality standards in section 183 of the ESRA (20 U.S.C. 9573).</P>
          <HD SOURCE="HD2">RETENTION AND DISPOSAL:</HD>
          <P>Records are maintained and disposed of in accordance with the Department's Records Disposition Schedule 068 (NARA Disposition Authority N1-441-08-18).</P>
          <HD SOURCE="HD2">SYSTEM MANAGER AND ADDRESS:</HD>
          <P>Associate Commissioner, Evaluation Division, National Center for Education Evaluation and Regional Assistance, Institute of Education Sciences, U.S. Department of Education, 555 New Jersey Avenue NW., room 502D, Washington, DC 20208-0001.</P>
          <HD SOURCE="HD2">NOTIFICATION PROCEDURE:</HD>
          <P>If you wish to determine whether a record exists regarding you in the system of records, contact the systems manager. Your request must meet the requirements of regulations at 34 CFR 5b.5, including proof of identity.</P>
          <HD SOURCE="HD2">RECORD ACCESS PROCEDURE:</HD>
          <P>If you wish to gain access to your record in the system of records, contact the system manager. Your request must meet the requirements of regulations at 34 CFR 5b.5, including proof of identity.</P>
          <HD SOURCE="HD2">CONTESTING RECORD PROCEDURE:</HD>
          <P>If you wish to contest the content of a record regarding you in the system of records, contact the system manager. Your request must meet the requirements of the regulations at 34 CFR 5b.7, including proof of identity.</P>
          <HD SOURCE="HD2">RECORD SOURCE CATEGORIES:</HD>
          <P>This system contains records on students participating in the Evaluation of the Pell Grant Experiments Under the Experimental Sites Initiative. Data will be obtained through student records maintained by participating institutions, a survey of students, data extracts from Free Applications for Federal Student Aid, and from the administrative records of another Federal agency with data on the students' earnings and employment outcomes.</P>
          <HD SOURCE="HD2">EXEMPTIONS CLAIMED FOR THE SYSTEM:</HD>
          <P>None.</P>
        </PRIACT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00163 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Energy Efficiency and Renewable Energy</SUBAGY>
        <SUBJECT>State Energy Advisory Board (STEAB)</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Energy Efficiency and Renewable Energy, Department of Energy.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of Open Teleconference.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>This notice announces a teleconference call of the State Energy Advisory Board (STEAB). The Federal Advisory Committee Act (Pub. L. 92-463; 86 Stat. 770) requires that public notice of these meetings be announced in the<E T="04">Federal Register</E>.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Thursday, January 24, 2013 from 3:30 p.m. to 4:00 p.m. (EST). To receive the call-in number and passcode, please contact the Board's Designated Federal Officer (DFO) at the address or phone number listed below.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Gil Sperling, STEAB Designated Federal Officer, U.S. Department of Energy, Office of Energy Efficiency and Renewable Energy, 1000 Independence Ave. SW., Washington, DC 20585. Phone number is (202) 287-1644.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>
          <E T="03">Purpose of the Board:</E>To make recommendations to the Assistant Secretary for the Office of Energy Efficiency and Renewable Energy regarding goals and objectives, programmatic and administrative policies, and to otherwise carry out the Board's responsibilities as designated in the State Energy Efficiency Programs Improvement Act of 1990 (Pub. L. 101-440).</P>
        <P>
          <E T="03">Tentative Agenda:</E>Receive an update on the activities of the STEAB's Taskforces, review the activities of the newly formed STEAB Strategic Planning Subcommittee, and provide an update to the Board on routine business matters and other topics of interest, and begin discussion planning for a spring 2013 meeting.</P>
        <P>
          <E T="03">Public Participation:</E>The meeting is open to the public. Written statements may be filed with the Board either before or after the meeting. Members of the public who wish to make oral statements pertaining to agenda items should contact Gil Sperling at the address or telephone number listed above. Requests to make oral comments must be received five days prior to the<PRTPAGE P="1210"/>meeting; reasonable provision will be made to include requested topic(s) on the agenda. The Chair of the Board is empowered to conduct the meeting in a fashion that will facilitate the orderly conduct of business.</P>
        <P>
          <E T="03">Minutes:</E>The minutes of the meeting will be available for public review and copying within 60 days on the STEAB Web site at:<E T="03">www.steab.org.</E>
        </P>
        <SIG>
          <DATED/>
          <P>Issued at Washington, DC, on January 2, 2013.</P>
          <NAME>LaTanya R. Butler,</NAME>
          <TITLE>Deputy Committee Management Officer.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00106 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6450-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <DEPDOC>[Docket No. NJ13-8-000]</DEPDOC>
        <SUBJECT>City of Anaheim, California; Notice of Filing</SUBJECT>
        <P>Take notice that on December 21, 2012, City of Anaheim, California submitted its tariff filing per 35.28(e): Anaheim 2013 TRBAA Update to be effective 1/1/2013.</P>
        <P>Any person desiring to intervene or to protest this filing must file in accordance with Rules 211 and 214 of the Commission's Rules of Practice and Procedure (18 CFR 385.211, 385.214). Protests will be considered by the Commission in determining the appropriate action to be taken, but will not serve to make protestants parties to the proceeding. Any person wishing to become a party must file a notice of intervention or motion to intervene, as appropriate. Such notices, motions, or protests must be filed on or before the comment date. On or before the comment date, it is not necessary to serve motions to intervene or protests on persons other than the Applicant.</P>

        <P>The Commission encourages electronic submission of protests and interventions in lieu of paper using the “eFiling” link at<E T="03">http://www.ferc.gov</E>. Persons unable to file electronically should submit an original and 14 copies of the protest or intervention to the Federal Energy Regulatory Commission, 888 First Street NE., Washington, DC 20426.</P>
        <P>This filing is accessible on-line at<E T="03">http://www.ferc.gov</E>, using the “eLibrary” link and is available for review in the Commission's Public Reference Room in Washington, DC. There is an “eSubscription” link on the web site that enables subscribers to receive email notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please email<E T="03">FERCOnlineSupport@ferc.gov</E>, or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.</P>
        <P>
          <E T="03">Comment Date:</E>5:00 p.m. Eastern Time on January 11, 2013.</P>
        <SIG>
          <DATED>Dated: January 2, 2013.</DATED>
          <NAME>Kimberly D. Bose,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00119 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <DEPDOC>[Project No. 2524-018]</DEPDOC>
        <SUBJECT>Grand River Dam Authority; Notice of Telephone Meeting To Discuss the Salina Pumped Storage Project Water Quality Study Results</SUBJECT>
        <P>a.<E T="03">Date and Time of Meeting:</E>Wednesday, January 16, 2013, 2 p.m. Central Standard Time, (3 p.m. Eastern Standard Time).</P>
        <P>b.<E T="03">Place:</E>Teleconference hosted by Grand River Dam Authority. (An RSVP is required. See paragraph f below.)</P>
        <P>c.<E T="03">FERC Contact:</E>Stephen Bowler at (202) 505-6861 or<E T="03">stephen.bowler@ferc.gov</E>; or Jeanne Edwards at (202) 502-6181 or<E T="03">jeanne.edwards@ferc.gov</E>.</P>
        <P>d.<E T="03">Purpose of Meeting:</E>As a follow-up to its study report meeting of October 11, 2012, the Grand River Dam Authority (GRDA) is holding a technical meeting to discuss the results of the Water Quality Study as they stand at the conclusion of fieldwork.</P>
        <P>e.<E T="03">Proposed Agenda:</E>
        </P>
        <FP SOURCE="FP-1">(1) GRDA: Introduction</FP>
        <FP SOURCE="FP-1">(2) Oklahoma Water Resources Control Board (OWRB): Water quality study results at the conclusion of fieldwork</FP>
        <FP SOURCE="FP-1">(3) GRDA, OWRB, and other participants: Discussion</FP>

        <P>f. All local, state, and federal agencies, Indian tribes, and other interested parties are invited to participate by phone. Please email Jacklyn Jaggars by close of business on Monday, January 14, 2013, at<E T="03">jjaggars@grda.com</E>to RSVP and to receive specific instructions on how to participate.</P>
        <SIG>
          <DATED>Dated: January 2, 2013.</DATED>
          <NAME>Kimberly D. Bose,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00120 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <SUBJECT>Notice of Membership of Performance Review Board for Senior Executives (PRB)</SUBJECT>
        <P>The Federal Energy Regulatory Commission hereby provides notice of the membership of its Performance Review Board (PRB) for the Commission's Senior Executive Service (SES) members. The function of this board is to make recommendations relating to the performance of senior executives in the Commission. This action is undertaken in accordance with Title 5, U.S.C., Section 4314(c)(4).</P>
        <P>The Commission's PRB will remove the following member:</P>
        
        <FP SOURCE="FP-1">Joseph H. McClelland</FP>
        <SIG>
          <DATED>Dated: January 2, 2013.</DATED>
          <NAME>Kimberly D. Bose,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00121 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
        <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
        <SUBJECT>Notice of Membership of Performance Review Board for Senior Executives (PRB)</SUBJECT>
        <P>The Federal Energy Regulatory Commission hereby provides notice of the membership of its Performance Review Board (PRB) for the Commission's Senior Executive Service (SES) members. The function of this board is to make recommendations relating to the performance of senior executives in the Commission. This action is undertaken in accordance with Title 5, U.S.C., Section 4314(c)(4).</P>
        <P>The Commission's PRB will remove the following member:</P>
        
        <FP SOURCE="FP-1">Charles H. Schneider</FP>
        
        <P>The Commission's PRB will add the following member:</P>
        
        <FP SOURCE="FP-1">Anton C. Porter, PRB Chairman</FP>
        <SIG>
          <DATED>Dated: January 2, 2013.</DATED>
          <NAME>Kimberly D. Bose,</NAME>
          <TITLE>Secretary.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00118 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6717-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <PRTPAGE P="1211"/>
        <AGENCY TYPE="N">EXPORT-IMPORT BANK OF THE UNITED STATES</AGENCY>
        <DEPDOC>[Public Notice 2012-0561]</DEPDOC>
        <SUBJECT>Agency Information Collection Activities: Comment Request</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Export-Import Bank of the U.S.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Submission for OMB Review and Comments Request.</P>
        </ACT>
        <P>
          <E T="03">Form Title:</E>Application for Approved Finance Provider EIB 10-06.</P>
        
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Export-Import Bank of the United States (Ex-Im Bank), as a part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal Agencies to comment on the proposed information collection, as required by the Paperwork Reduction Act of 1995.</P>
          <P>Ex-Im Bank has made the following changes to this form:</P>
          <P>Under Approved Finance Provided added the following programs:</P>
          
          <FP SOURCE="FP-1">Master Guarantee Agreement</FP>
          <FP SOURCE="FP-1">Working Capital Guarantee</FP>
          <FP SOURCE="FP-1">Global Credit Express—Originating Lender</FP>
          <FP SOURCE="FP-1">Other (please specify)</FP>
          
          <P>Under Required Supplemental Information paragraph d—change to read:</P>
          <P>d. Description of Applicant's trace finance and or commercial lending or asset based lending experience and a description of said experience of each member of senior management and each person who will be responsible for the Ex-Im Bank relationship, including each person who will sign the MGA (if one is being requested) or other documents to be submitted to Ex-Im Bank.</P>
          <P>Updated all Certifications and Notices as needed.</P>
          <P>The Application for Approved Finance Provider will be used to determine if the finance provider has the financial strength and administrative staff to originate, administer, collect, and if needed, restructure international loans. This application will also improve Ex-Im Bank's compliance with the Open Government initiative by providingtransparency into specific information used to determine if an applicant is qualified to use our loan guarantee programs. Export-Import Bank potential finance providers will be able to submit this form on paper. In the future, we will consider allowing the submissionof this information electronically.</P>
          <P>The survey form can be viewed at<E T="03">www.exim.gov/pub/EIB10.06.pdf</E>.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments should be received on or before February 7, 2013 to be assured of consideration.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Comments may be submitted through<E T="03">www.Regulations.Gov</E>or mailed to Jeffrey Abramson, Export-Import Bank of the United States, 811 Vermont Ave. NW., Washington, DC 20571.</P>
        </ADD>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P SOURCE="NPAR">
          <E T="03">Titles and Form Number:</E>EIB 10-06 Application for Approved Finance Provider.</P>
        <P>
          <E T="03">OMB Number:</E>3048-0032.</P>
        <P>
          <E T="03">Type of Review:</E>Renewal.</P>
        <P>
          <E T="03">Need and Use:</E>The Application for Approved Finance Provider will be used to determine if the finance provider has the financial strength and administrative staff to originate, administer, collect, and if needed, restructure international loans. This application will also improve Ex-Im Bank's compliance with the Open Government initiative by providing transparency into specific information used to determine if an applicant is qualified to use our loan guarantee programs. Export-Import Bank potential finance providers will be able to submit this form on paper.</P>
        <P>
          <E T="03">Affected Public:</E>This form affects entities involved in the export of U.S. goods and  services.</P>
        <P>
          <E T="03">Annual Number of Respondents:</E>50.</P>
        <P>
          <E T="03">Estimated Time per Respondent:</E>3.0 hours.</P>
        <P>
          <E T="03">Government Burden Hours:</E>100 hours.</P>
        <P>
          <E T="03">Estimated Government Burden Cost:</E>$6,000.00.</P>
        <P>
          <E T="03">Frequency of Reporting or Use:</E>Yearly.</P>
        <SIG>
          <NAME>Sharon A. Whitt,</NAME>
          <TITLE>Agency Clearance Officer.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00143 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6690-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">EXPORT-IMPORT BANK OF THE UNITED STATES</AGENCY>
        <DEPDOC>[Public Notice 2012-0558]</DEPDOC>
        <SUBJECT>Application for Final Commitment for a Long-Term Loan or Financial Guarantee in Excess of $100 million: AP086856XX</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Export-Import Bank of the United States.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This Notice is to inform the public, in accordance with Section 3(c)(10) of the Charter of the Export-Import Bank of the United States (“Ex-Im Bank”), that Ex-Im Bank has received an application for final commitment for a long-term loan or financial guarantee in excess of $100 million (as calculated in accordance with Section 3(c)(10) of the Charter).Comments received within the comment period specified below will be presented to the Ex-Im Bank Board of Directors prior to final action on this Transaction.</P>
          <P>
            <E T="03">Reference:</E>AP086856XX.</P>
          <HD SOURCE="HD1">Purpose and Use</HD>
          <P>Brief description of the purpose of the transaction:</P>
          
          <FP SOURCE="FP-1">To support the export of U.S.-manufactured commercial aircraft to Luxembourg.</FP>
          
          <P>Brief non-proprietary description of the anticipated use of the items being exported:</P>
          
          <FP SOURCE="FP-1">To provide cargo services globally.</FP>
          
          <P>To the extent that Ex-Im Bank is reasonably aware, the item(s) being exported are not expected to be used to produce exports or provide services in competition with the exportation of goods or provision of services by a United States industry.</P>
          <HD SOURCE="HD1">Parties</HD>
          <P>
            <E T="03">Principal Supplier:</E>The Boeing Company.</P>
          <P>
            <E T="03">Obligor:</E>Cargolux Airlines International S.A.</P>
          <P>
            <E T="03">Guarantor(s):</E>N/A.</P>
          <HD SOURCE="HD1">Description of Items Being Exported</HD>
          <P>The items being exported are Boeing 747 aircraft.</P>
          <P>
            <E T="03">Information On Decision:</E>Information on the final decision for this transaction will be available in the “Summary Minutes of Meetings of Board of Directors” on<E T="03">http://www.exim.gov/articles.cfm/board%20minute.</E>
          </P>
          <P>
            <E T="03">Confidential Information:</E>Please note that this notice does not include confidential or proprietary business information; information which, if disclosed, would violate the Trade Secrets Act; or information which would jeopardize jobs in the United States by supplying information that competitors could use to compete with companies in the United States.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments must be received on or before February 4, 2013 to be assured of consideration before final consideration of the transaction by the Board of Directors of Ex-Im Bank.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Comments may be submitted through Regulations.gov at<E T="03">www.regulations.gov</E>. To submit a comment, enter EIB-2012-0053 under the heading “Enter Keyword or ID” and select Search. Follow the instructions provided at the Submit a Comment screen. Please include your name,<PRTPAGE P="1212"/>company name (if any) and EIB-2012-0053 on any attached document.</P>
        </ADD>
        <SIG>
          <NAME>Sharon A. Whitt,</NAME>
          <TITLE>Records Clearance Officer.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00142 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6690-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">FEDERAL RESERVE SYSTEM</AGENCY>
        <SUBJECT>Formations of, Acquisitions by, and Mergers of Bank Holding Companies</SUBJECT>

        <P>The companies listed in this notice have applied to the Board for approval, pursuant to the Bank Holding Company Act of 1956 (12 U.S.C. 1841<E T="03">et seq.</E>) (BHC Act), Regulation Y (12 CFR part 225), and all other applicable statutes and regulations to become a bank holding company and/or to acquire the assets or the ownership of, control of, or the power to vote shares of a bank or bank holding company and all of the banks and nonbanking companies owned by the bank holding company, including the companies listed below.</P>
        <P>The applications listed below, as well as other related filings required by the Board, are available for immediate inspection at the Federal Reserve Bank indicated. The applications will also be available for inspection at the offices of the Board of Governors. Interested persons may express their views in writing on the standards enumerated in the BHC Act (12 U.S.C. 1842(c)). If the proposal also involves the acquisition of a nonbanking company, the review also includes whether the acquisition of the nonbanking company complies with the standards in section 4 of the BHC Act (12 U.S.C. 1843). Unless otherwise noted, nonbanking activities will be conducted throughout the United States.</P>
        <P>Unless otherwise noted, comments regarding each of these applications must be received at the Reserve Bank indicated or the offices of the Board of Governors not later than February 1, 2013.</P>
        <P>A. Federal Reserve Bank of Chicago (Colette A. Fried, Assistant Vice President) 230 South LaSalle Street, Chicago, Illinois 60690-1414:</P>
        <P>1.<E T="03">Van Buren Bancorporation, Inc.,</E>Keosauqua, Iowa; to acquire 100 percent of First Iowa State Bank, Albia, Iowa.</P>
        <SIG>
          <DATED>Board of Governors of the Federal Reserve System, January 3, 2013.</DATED>
          <NAME>Margaret McCloskey Shanks,</NAME>
          <TITLE>Deputy Secretary of the Board.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00108 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6210-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
        <SUBJECT>Notice of Proposals To Engage in or To Acquire Companies Engaged in Permissible Nonbanking Activities</SUBJECT>

        <P>The companies listed in this notice have given notice under section 4 of the Bank Holding Company Act (12 U.S.C. 1843) (BHC Act) and Regulation Y, (12 CFR Part 225) to engage<E T="03">de novo,</E>or to acquire or control voting securities or assets of a company, including the companies listed below, that engages either directly or through a subsidiary or other company, in a nonbanking activity that is listed in § 225.28 of Regulation Y (12 CFR 225.28) or that the Board has determined by Order to be closely related to banking and permissible for bank holding companies. Unless otherwise noted, these activities will be conducted throughout the United States.</P>
        <P>Each notice is available for inspection at the Federal Reserve Bank indicated. The notice also will be available for inspection at the offices of the Board of Governors. Interested persons may express their views in writing on the question whether the proposal complies with the standards of section 4 of the BHC Act.</P>
        <P>Unless otherwise noted, comments regarding the applications must be received at the Reserve Bank indicated or the offices of the Board of Governors not later than January 23, 2013.</P>
        <P>A. Federal Reserve Bank of Chicago (Colette A. Fried, Assistant Vice President) 230 South LaSalle Street, Chicago, Illinois 60690-1414:</P>
        <P>
          <E T="03">1. Baylake Corporation,</E>Sturgeon Bay, Wisconsin; to acquire 100 percent of the voting shares of Admiral Asset Management, LLC, Green Bay, Wisconsin and thereby indirectly engage in providing financial advice and agency transactional services for customers, pursuant to sections 225.28(b)(6) and (b)(7) all of Regulation Y.</P>
        <SIG>
          <DATED>Board of Governors of the Federal Reserve System, January 3, 2013.</DATED>
          <NAME>Margaret McCloskey Shanks,</NAME>
          <TITLE>Deputy Secretary of the Board.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00107 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 6210-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Centers for Disease Control and Prevention</SUBAGY>
        <SUBJECT>Disease, Disability, and Injury Prevention and Control Special Emphasis Panel (SEP): Initial Review</SUBJECT>
        <P>The meeting announced below concerns Natural History and Prevention of Viral Hepatitis Among Alaska Natives, Funding Opportunity Announcement (FOA) PS13-001, initial review.</P>
        <P>In accordance with Section 10(a)(2) of the Federal Advisory Committee Act (Pub. L. 92-463), the Centers for Disease Control and Prevention (CDC) announces the aforementioned meeting:</P>
        
        <EXTRACT>
          <P>
            <E T="03">Time and Date:</E>1:00 p.m.-3:00 p.m., February 11, 2013 (Closed).</P>
          <P>
            <E T="03">Place:</E>Teleconference.</P>
          <P>
            <E T="03">Status:</E>The meeting will be closed to the public in accordance with provisions set forth in Section 552b(c)(4) and (6), Title 5 U.S.C., and the Determination of the Director, Management Analysis and Services Office, CDC, pursuant to Public Law 92-463.</P>
          <P>
            <E T="03">Matters To Be Discussed:</E>The meeting will include the initial review, discussion, and evaluation of applications received in response to “Natural History and Prevention of Viral Hepatitis Among Alaska Natives, FOA PS13-001.”</P>
          <P>
            <E T="03">Contact Person for More Information:</E>Gregory Anderson, M.S., M.P.H., Scientific Review Officer, CDC, 1600 Clifton Road, NE., Mailstop E60, Atlanta, Georgia 30333, Telephone: (404) 718-8833.</P>

          <P>The Director, Management Analysis and Services Office, has been delegated the authority to sign<E T="04">Federal Register</E>notices pertaining to announcements of meetings and other committee management activities, for both the Centers for Disease Control and Prevention and the Agency for Toxic Substances and Disease Registry.</P>
        </EXTRACT>
        <SIG>
          <DATED>Dated: January 2, 2013.</DATED>
          <NAME>Dana Redford,</NAME>
          <TITLE>Acting Director, Management Analysis and Services Office, Centers for Disease Control and Prevention.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00136 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4163-18-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
        <DEPDOC>[Document Identifier CMS-10457]</DEPDOC>
        <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Centers for Medicare &amp; Medicaid Services, HHS.<PRTPAGE P="1213"/>
          </P>
          <P>In compliance with the requirement of section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995, the Centers for Medicare &amp; Medicaid Services (CMS) is publishing the following summary of proposed collections for public comment. Interested persons are invited to send comments regarding this burden estimate or any other aspect of this collection of information, including any of the following subjects: (1) The necessity and utility of the proposed information collection for the proper performance of the agency's functions; (2) the accuracy of the estimated burden; (3) ways to enhance the quality, utility, and clarity of the information to be collected; and (4) the use of automated collection techniques or other forms of information technology to minimize the information collection burden.</P>
          <P>1.<E T="03">Type of Information Collection Request:</E>New collection (request for a new OMB control number).<E T="03">Title of Information Collection:</E>MAC Satisfaction Indicator (MSI) Participant Information Registration Form.<E T="03">Use:</E>Section 1874(A)(b)(3)(B) of the Social Security Act requires that provider satisfaction be a performance standard for the work of Medicare Administrative Contractors (MACs). In order to gain provider feedback regarding their satisfaction with their MACs, we need to be able to contact the providers. Therefore, we need accurate contact information to: select from a random sample, forward the survey to the appropriate respondent, and increase response rates. The survey will not be added to this package. Instead, it will be processed under a different control number via an Interagency Agreement.<E T="03">Form Number:</E>CMS-10457 (OCN 0938-New).<E T="03">Frequency:</E>Yearly.<E T="03">Affected Public:</E>Private Sector (business or other for-profit and not-for-profit institutions).<E T="03">Number of Respondents:</E>150,000.<E T="03">Total Annual Responses:</E>150,000.<E T="03">Total Annual Hours:</E>2,500. (For policy questions regarding this collection contact Teresa Mundell at 410-786-9176. For all other issues call 410-786-1326.)</P>

          <P>To obtain copies of the supporting statement and any related forms for the proposed paperwork collections referenced above, access CMS' Web site address at<E T="03">http://www.cms.hhs.gov/PaperworkReductionActof1995,</E>or Email your request, including your address, phone number, OMB number, and CMS document identifier, to<E T="03">Paperwork@cms.hhs.gov,</E>or call the Reports Clearance Office on (410) 786-1326.</P>

          <P>In commenting on the proposed information collections please reference the document identifier or OMB control number. To be assured consideration, comments and recommendations must be submitted in one of the following ways by<E T="03">March 11, 2013</E>:</P>
          <P>1.<E T="03">Electronically.</E>You may submit your comments electronically to<E T="03">http://www.regulations.gov.</E>Follow the instructions for “Comment or Submission” or “More Search Options” to find the information collection document(s) accepting comments.</P>
          <P>2.<E T="03">By regular mail.</E>You may mail written comments to the following address: CMS, Office of Strategic Operations and Regulatory Affairs, Division of Regulations Development, Attention: Document Identifier/OMB Control Number _____, Room C4-26-05, 7500 Security Boulevard, Baltimore, Maryland 21244-1850.</P>
        </AGY>
        <SIG>
          <DATED>Dated: January 2, 2013.</DATED>
          <NAME>Martique Jones,</NAME>
          <TITLE>Deputy Director, Regulations Development Group, Office of Strategic Operations and Regulatory Affairs.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00065 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4120-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Administration for Children and Families</SUBAGY>
        <SUBJECT>Proposed Information Collection Activity; Comment Request</SUBJECT>
        <P>
          <E T="03">Title:</E>Descriptive Study of County versus State Administered Temporary Assistance for Needy Families (TANF) Programs.</P>
        <P>
          <E T="03">OMB No.:</E>New Collection.</P>
        <P>
          <E T="03">Description:</E>The Administration for Children and Families (ACF) is proposing an information collection activity as part of the Descriptive Study of County and State Administered TANF Programs. The proposed information collection consists of semi-structured interviews with key County and State staff on questions of county TANF administration, policies, service delivery, and program context. Through this information collection, ACF seeks to gain an in-depth, systematic understanding of the differences in program implementation, operations, outputs and outcomes between state and county administered TANF programs, and identify special technical assistance needs of state supervised, county administered programs.</P>
        <P>
          <E T="03">Respondents:</E>Semi-structured interviews will be held with state and county TANF administrators and staff.</P>
        <GPOTABLE CDEF="s50,12,12,12,12" COLS="5" OPTS="L2,i1">
          <TTITLE>Annual Burden Estimates</TTITLE>
          <BOXHD>
            <CHED H="1">Instrument</CHED>
            <CHED H="1">Annual<LI>number of</LI>
              <LI>respondents</LI>
            </CHED>
            <CHED H="1">Number of<LI>responses per respondent</LI>
            </CHED>
            <CHED H="1">Average<LI>burden hours</LI>
              <LI>per response</LI>
            </CHED>
            <CHED H="1">Annual burden hours</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Discussion Guide for use with countyTANF Administrators</ENT>
            <ENT>12</ENT>
            <ENT>1</ENT>
            <ENT>1.5</ENT>
            <ENT>18</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Discussion Guide for use with state TANFAdministrators or program managers</ENT>
            <ENT>6</ENT>
            <ENT>1</ENT>
            <ENT>1</ENT>
            <ENT>6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Discussion Guide for use with state human service department director or cabinet-level official</ENT>
            <ENT>6</ENT>
            <ENT>1</ENT>
            <ENT>1</ENT>
            <ENT>6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Discussion Guide for use with county executives or county board members</ENT>
            <ENT>12</ENT>
            <ENT>1</ENT>
            <ENT>1</ENT>
            <ENT>12</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">Discussion Guide for use with County TANF directors' associations, or similar organizations</ENT>
            <ENT>6</ENT>
            <ENT>1</ENT>
            <ENT>1.5</ENT>
            <ENT>9</ENT>
          </ROW>
          <ROW>
            <ENT I="03">Estimated Total Annual Burden Hours:</ENT>
            <ENT/>
            <ENT/>
            <ENT/>
            <ENT>51</ENT>
          </ROW>
        </GPOTABLE>

        <P>In compliance with the requirements of Section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995, the Administration for Children and Families is soliciting public comment on the specific aspects of the information collection described above. Copies of the proposed collection of information can be obtained and comments may be forwarded by writing to the Administration for Children and Families, Office of Planning, Research and Evaluation, 370 L'Enfant Promenade SW., Washington, DC 20447, Attn: OPRE Reports Clearance Officer.<PRTPAGE P="1214"/>Email address:<E T="03">OPREinfocollection@acf.hhs.gov.</E>All requests should be identified by the title of the information collection.</P>
        <P>The Department specifically requests comments on (a) Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information shall have practical utility; (b) the accuracy of the agency's estimate of the burden of the proposed collection of information; (c) the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or other forms of information technology. Consideration will be given to comments and suggestions submitted within 60 days of this publication.</P>
        <SIG>
          <NAME>Steven M. Hammer,</NAME>
          <TITLE>Reports Clearance Officer; Office of Planning, Research and Evaluation</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2012-31714 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4184-09-M</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Administration for Children and Families</SUBAGY>
        <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
        <P>
          <E T="03">Title:</E>Head Start Grant Application and Budget Instruments.</P>
        <P>
          <E T="03">OMB No.:</E>0970-0207.</P>
        <P>
          <E T="03">Description:</E>The Office of Head Start is proposing to renew, without changes, the Head Start Grant Application and Budget Instrument, which standardizes the grant application information that is requested from all Head Start and Early Head Start grantees applying for continuation grants. The application and budget forms are available in a password-protected, web-based system. Completed applications can be transmitted electronically to Regional and Central Offices. The Administration for Children and Families believes that this application form makes the process of applying for Head Start program grants more efficient for applicants.</P>
        <P>
          <E T="03">Respondents:</E>Head Start and Early Head Start grantees.</P>
        <HD SOURCE="HD1">Respondents</HD>
        <GPOTABLE CDEF="s75,12C,12C,12C,12C" COLS="5" OPTS="L2,i1">
          <TTITLE>Annual Burden Estimates</TTITLE>
          <BOXHD>
            <CHED H="1">Instrument</CHED>
            <CHED H="1">Number of<LI>respondents</LI>
            </CHED>
            <CHED H="1">Number of<LI>responses per</LI>
              <LI>respondent</LI>
            </CHED>
            <CHED H="1">Average<LI>burden hours</LI>
              <LI>per response</LI>
            </CHED>
            <CHED H="1">Total burden hours</CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">HS grant and budget instrument</ENT>
            <ENT>1,600</ENT>
            <ENT>1</ENT>
            <ENT>33</ENT>
            <ENT>52,800</ENT>
          </ROW>
        </GPOTABLE>
        <P>
          <E T="03">Estimated Total Annual Burden Hours:</E>52,800.</P>
        <HD SOURCE="HD1">Additional Information</HD>

        <P>Copies of the proposed collection may be obtained by writing to the Administration for Children and Families, Office of Planning, Research and Evaluation, 370 L'Enfant Promenade, SW., Washington, DC 20447, Attn: ACF Reports Clearance Officer. All requests should be identified by the title of the information collection. Email address:<E T="03">infocollection@acf.hhs.gov.</E>
        </P>
        <HD SOURCE="HD1">OMB Comment</HD>

        <P>OMB is required to make a decision concerning the collection of information between 30 and 60 days after publication of this document in the<E T="04">Federal Register</E>. Therefore, a comment is best assured of having its full effect if OMB receives it within 30 days of publication. Written comments and recommendations for the proposed information collection should be sent directly to the following: Office of Management and Budget, Paperwork Reduction Project, Fax: 202-395-7285, Email:<E T="03">OIRA_SUBMISSION@OMB.EOP.GOV,</E>Attn: Desk Officer for the Administration for Children and Families.</P>
        <SIG>
          <NAME>Robert Sargis,</NAME>
          <TITLE>Reports Clearance Officer.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00127 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4184-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>Health Resources and Services Administration</SUBAGY>
        <SUBJECT>Agency Information Collection Activities: Proposed Collection: Comment Request</SUBJECT>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>In compliance with the requirement for opportunity for public comment on proposed data collection projects (section 3506(c)(2)(A) of Title 44, United States Code, as amended by the Paperwork Reduction Act of 1995, Pub. L. 104-13), the Health Resources and Services Administration (HRSA) publishes periodic summaries of proposed projects being developed for submission to the Office of Management and Budget (OMB) under the Paperwork Reduction Act of 1995. To request more information on the proposed project or to obtain a copy of the data collection plans and draft instruments, email<E T="03">paperwork@hrsa.gov</E>or call the HRSA Reports Clearance Officer at (301) 443-1984.</P>
          <P>HRSA especially requests comments on: (1) The necessity and utility of the proposed information collection for the proper performance of the agency's functions, (2) the accuracy of the estimated burden, (3) ways to enhance the quality, utility, and clarity of the information to be collected, and (4) the use of automated collection techniques or other forms of information technology to minimize the information collection burden.</P>
          <HD SOURCE="HD1">Information Collection Request Title: National Practitioner Data Bank for Adverse Information on Physicians and Other Health Care Practitioners—45 CFR Part 60 Regulations and Forms OMB No. 0915-0126—Revision</HD>
          <P>
            <E T="03">Abstract:</E>This is a request for a revision of OMB approval of the information collections contained in regulations found at 45 CFR Part 60 governing the National Practitioner Data Bank (NPDB) and the forms to be used in registering with, reporting information to, and requesting information from the NPDB. Section 6403 of the Patient Protection and Affordable Care Act of 2010 (Affordable Care Act) Public Law 111-148 requires the transfer of all data in the Healthcare Integrity and Protection Data Bank (HIPDB) to the NPDB. Data collection will not change; however, the merger will consolidate forms from OMB No. 0915-0239 for HIPDB under OMB No. 0915-0126 for NPDB. Responsibility for NPDB implementation and operation resides in the Bureau of Health Professions, Health Resources and Services Administration (HRSA), Department of Health and Human Services (HHS). Operation of the HIPDB was delegated by the HHS Office of the Inspector General to HRSA. This rule<PRTPAGE P="1215"/>eliminates duplicative data reporting and access requirements between the HIPDB [established through the Health Insurance Portability and Accountability Act of 1996 (HIPPA) under Section 1128(b)(5) of the Social Security Act (42 U.S.C. 1320a-7e)] and the NPDB [established through the Health Care Quality Improvement Act of 1986 under Title IV (42 U.S.C. 11101<E T="03">et seq.</E>) and expanded by Section 1921 of the Social Security Act (42 U.S.C. 1396r-2)]. Information previously collected and disclosed through the HIPDB will be collected and disclosed through the NPDB. Section 6403 of the Affordable Care Act consolidates the collection and disclosure of information from both data banks under Title 45 part 60 of the Code of Federal Regulations (CFR). The Department of Health and Human Services (HHS) will subsequently remove Title 45 part 61, which implemented the HIPDB.</P>
          <P>The intent of NPDB is to improve the quality of health care by encouraging hospitals, state licensing boards, professional societies, and other entities providing health care services, to identify and discipline those who engage in unprofessional behavior; and to restrict the ability of incompetent health care practitioners, providers, or suppliers to move from state to state without disclosure of previous damaging or incompetent performance. It also serves as a fraud and abuse clearinghouse for the reporting and disclosing of certain final adverse actions (excluding settlements in which no findings of liability have been made) taken against health care practitioners, providers, or suppliers by health plans, federal agencies, and state agencies.</P>
          <P>The NPDB acts primarily as a flagging system; its principal purpose is to facilitate comprehensive review of practitioners' professional credentials and background. Information is collected from, and disseminated to, eligible entities (entities that are entitled to query and/or report to the NPDB under the three aforementioned statutory authorities) on the following: (1) Medical malpractice payments, (2) licensure actions taken by Boards of Medical Examiners, (3) state licensure and certification actions, (4) federal licensure and certification actions, (5) negative actions or findings taken by peer review organizations or private accreditation entities, (6) adverse actions taken against clinical privileges, (7) federal or state criminal convictions related to the delivery of a health care item or service, (8) civil judgments related to the delivery of a health care item or service, (9) exclusions from participation in federal or state health care programs, and (10) other adjudicated actions or decisions. It is intended that NPDB information should be considered with other relevant information in evaluating credentials of health care practitioners, providers, and suppliers.</P>

          <P>The reporting forms and the request for information forms (query forms) are accessed, completed, and submitted to the NPDB electronically through the NPDB Web site at<E T="03">http://www.npdb-hipdb.hrsa.gov/.</E>All reporting and querying is performed through this secure Web site.</P>
          <P>
            <E T="03">Burden Statement:</E>Burden in this context means the time expended by persons to generate, maintain, retain, disclose, or provide the information requested. This includes the time needed to review instructions, to develop, acquire, install and utilize technology and systems for the purpose of collecting, validating and verifying information, processing and maintaining information, and disclosing and providing information, to train personnel and to be able to respond to a collection of information, to search data sources, to complete and review the collection of information, and to transmit or otherwise disclose the information. The total annual burden hours estimated for this Information Collection Request are summarized in the table below.</P>
          <P>The annual estimate of burden is as follows:</P>
        </SUM>
        <GPOTABLE CDEF="s100,12,12,12,12,12" COLS="6" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Form name</CHED>
            <CHED H="1">Number of<LI>respondents</LI>
            </CHED>
            <CHED H="1">Number of<LI>responses per</LI>
              <LI>respondent</LI>
            </CHED>
            <CHED H="1">Total<LI>responses</LI>
            </CHED>
            <CHED H="1">Average<LI>burden per</LI>
              <LI>response</LI>
              <LI>(in hours)</LI>
            </CHED>
            <CHED H="1">Total<LI>burden</LI>
              <LI>hours</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">Entity Registration (initial)</ENT>
            <ENT>856</ENT>
            <ENT>1</ENT>
            <ENT>856</ENT>
            <ENT>1</ENT>
            <ENT>856</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Entity Registration (renewal)</ENT>
            <ENT>12,748</ENT>
            <ENT>1</ENT>
            <ENT>12,748</ENT>
            <ENT>1</ENT>
            <ENT>12,748</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Individual Subject Query</ENT>
            <ENT>4,460,926</ENT>
            <ENT>1</ENT>
            <ENT>4,460,926</ENT>
            <ENT>0.1</ENT>
            <ENT>446,093</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Individual Self Query</ENT>
            <ENT>64,187</ENT>
            <ENT>1</ENT>
            <ENT>64,187</ENT>
            <ENT>0.4</ENT>
            <ENT>25,675</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Title IV Clinical Privileges Action</ENT>
            <ENT>862</ENT>
            <ENT>1</ENT>
            <ENT>862</ENT>
            <ENT>0.75</ENT>
            <ENT>647</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Professional Society Membership Action</ENT>
            <ENT>67</ENT>
            <ENT>1</ENT>
            <ENT>67</ENT>
            <ENT>0.75</ENT>
            <ENT>50</ENT>
          </ROW>
          <ROW>
            <ENT I="01">State Licensure Action</ENT>
            <ENT>62,178</ENT>
            <ENT>1</ENT>
            <ENT>62,178</ENT>
            <ENT>0.75</ENT>
            <ENT>46,634</ENT>
          </ROW>
          <ROW>
            <ENT I="01">DEA/Federal Licensure Action</ENT>
            <ENT>497</ENT>
            <ENT>1</ENT>
            <ENT>497</ENT>
            <ENT>0.75</ENT>
            <ENT>373</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Exclusion/Debarment</ENT>
            <ENT>16,243</ENT>
            <ENT>1</ENT>
            <ENT>16,243</ENT>
            <ENT>0.75</ENT>
            <ENT>12,182</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Government and Administrative Action</ENT>
            <ENT>2,592</ENT>
            <ENT>1</ENT>
            <ENT>2,592</ENT>
            <ENT>0.75</ENT>
            <ENT>1,944</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Health Plan Action</ENT>
            <ENT>515</ENT>
            <ENT>1</ENT>
            <ENT>515</ENT>
            <ENT>0.75</ENT>
            <ENT>386</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Civil Judgment</ENT>
            <ENT>10</ENT>
            <ENT>1</ENT>
            <ENT>10</ENT>
            <ENT>0.75</ENT>
            <ENT>8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Criminal Conviction</ENT>
            <ENT>1,253</ENT>
            <ENT>1</ENT>
            <ENT>1,253</ENT>
            <ENT>0.75</ENT>
            <ENT>940</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Medical Malpractice Payment</ENT>
            <ENT>13,326</ENT>
            <ENT>1</ENT>
            <ENT>13,326</ENT>
            <ENT>0.75</ENT>
            <ENT>9,995</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Private Accreditation Entity and Peer Review Organization</ENT>
            <ENT>10</ENT>
            <ENT>1</ENT>
            <ENT>10</ENT>
            <ENT>0.75</ENT>
            <ENT>8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Authorized Agent Designation Form (Add &amp; Edit)</ENT>
            <ENT>2055</ENT>
            <ENT>1</ENT>
            <ENT>2055</ENT>
            <ENT>0.25</ENT>
            <ENT>514</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Account Discrepancy Report</ENT>
            <ENT>20</ENT>
            <ENT>1</ENT>
            <ENT>20</ENT>
            <ENT>0.25</ENT>
            <ENT>5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Report Review Request Form</ENT>
            <ENT>83</ENT>
            <ENT>1</ENT>
            <ENT>83</ENT>
            <ENT>.25</ENT>
            <ENT>21</ENT>
          </ROW>
          <ROW>
            <ENT I="01">Electronic Transfer Funds Authorization</ENT>
            <ENT>276</ENT>
            <ENT>1</ENT>
            <ENT>276</ENT>
            <ENT>0.25</ENT>
            <ENT>69</ENT>
          </ROW>
          <ROW RUL="n,s">
            <ENT I="01">Subject Statement and Dispute Initiation Form (Individual &amp; Organization)</ENT>
            <ENT>100</ENT>
            <ENT>1</ENT>
            <ENT>100</ENT>
            <ENT>1</ENT>
            <ENT>100</ENT>
          </ROW>
          <ROW>
            <ENT I="03">TOTAL</ENT>
            <ENT>4,641,704</ENT>
            <ENT/>
            <ENT>4,641,704</ENT>
            <ENT/>
            <ENT>561,395</ENT>
          </ROW>
        </GPOTABLE>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Submit your comments to<E T="03">paperwork@hrsa.gov</E>or mail the HRSA Reports Clearance Officer, Room 10-29, Parklawn Building, 5600 Fishers Lane, Rockville, MD 20857.</P>
          <P>
            <E T="03">Deadline:</E>Comments on this Information Collection Request must be received within 60 days of this notice.</P>
        </ADD>
        <SIG>
          <PRTPAGE P="1216"/>
          <DATED>Dated: December 21, 2012.</DATED>
          <NAME>Bahar Niakan,</NAME>
          <TITLE>Director, Division of Policy and Information Coordination.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00031 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4165-15-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>National Institutes of Health</SUBAGY>
        <SUBJECT>Center for Scientific Review; Notice of Closed Meetings</SUBJECT>
        <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meetings.</P>
        <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
        
        <EXTRACT>
          <P>
            <E T="03">Name of Committee:</E>Emerging Technologies and Training Neurosciences Integrated Review Group Bioengineering of Neuroscience, Vision and Low Vision Technologies Study Section.</P>
          <P>
            <E T="03">Date:</E>February 7, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 6:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Westin St. Francis Hotel, 335 Powell Street, San Francisco, CA 94102.</P>
          <P>
            <E T="03">Contact Person:</E>Robert C Elliott, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 5190, MSC 7846, Bethesda, MD 20892, 301-435-3009,<E T="03">elliotro@csr.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>Surgical Sciences, Biomedical Imaging and Bioengineering Integrated Review Group, Biomedical Imaging Technology A Study Section.</P>
          <P>
            <E T="03">Date:</E>February 7-8, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 5:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Serrano Hotel, 405 Taylor Street, San Francisco, CA 94102.</P>
          <P>
            <E T="03">Contact Person:</E>Behrouz Shabestari, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 5126, MSC 7854, Bethesda, MD 20892, (301) 435-2409,<E T="03">shabestb@csr.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>Endocrinology, Metabolism, Nutrition and Reproductive Sciences Integrated Review Group, Cellular Aspects of Diabetes and Obesity Study Section.</P>
          <P>
            <E T="03">Date:</E>February 7, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 6:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Hyatt Regency Bethesda, One Bethesda Metro Center, 7400 Wisconsin Avenue, Bethesda, MD 20814.</P>
          <P>
            <E T="03">Contact Person:</E>Robert Garofalo, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institute of Health, 6701 Rockledge Drive, Room 6156, MSC 7892, Bethesda, MD 20892, 301-435-1043,<E T="03">garofalors@csr.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>Emerging Technologies and Training Neurosciences Integrated Review Group Neuroscience and Ophthalmic Imaging Technologies Study Section.</P>
          <P>
            <E T="03">Date:</E>February 7, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 6:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Renaissance Washington DC, Dupont Circle, 1143 New Hampshire Avenue NW., Washington, DC 20037.</P>
          <P>
            <E T="03">Contact Person:</E>Yvonne Bennett, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 5199, MSC 7846, Bethesda, MD 20892, 301-379-3793,<E T="03">bennetty@csr.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>Oncology 2—Translational Clinical Integrated Review Group Chemo/Dietary Prevention Study Section.</P>
          <P>
            <E T="03">Date:</E>February 7-8, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 5:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Sheraton Silver Spring, 8777 Georgia Avenue, Silver Spring, MD 20910.</P>
          <P>
            <E T="03">Contact Person:</E>Sally A Mulhern, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 6198, MSC 7804, Bethesda, MD 20892, (301) 408-9724,<E T="03">mulherns@csr.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>Interdisciplinary Molecular Sciences and Training Integrated Review Group Enabling Bioanalytical and Imaging Technologies Study Section.</P>
          <P>
            <E T="03">Date:</E>February 7-8, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 6:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>Renaissance Mayflower Hotel, 1127 Connecticut Avenue NW., Washington, DC 20036.</P>
          <P>
            <E T="03">Contact Person:</E>Dennis Hlasta, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 6185, MSC, Bethesda, MD 20892, 301-435-1047,<E T="03">dennis.hlasta@nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>Endocrinology, Metabolism, Nutrition and Reproductive Sciences Integrated Review Group, Clinical and Integrative Diabetes and Obesity Study Section.</P>
          <P>
            <E T="03">Date:</E>February 7, 2013.</P>
          <P>
            <E T="03">Time:</E>8:00 a.m. to 6:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications</P>
          <P>
            <E T="03">Place:</E>Residence Inn Bethesda, 7335 Wisconsin Avenue, Bethesda, MD 20814.</P>
          <P>
            <E T="03">Contact Person:</E>Nancy Sheard, SCD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 6046-E, MSC 7892, Bethesda, MD 20892, 301-408-9901,<E T="03">sheardn@csr.nih.gov.</E>
          </P>
          
          <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.306, Comparative Medicine; 93.333, Clinical Research, 93.306, 93.333, 93.337, 93.393-93.396, 93.837-93.844, 93.846-93.878, 93.892, 93.893, National Institutes of Health, HHS)</FP>
        </EXTRACT>
        <SIG>
          <DATED>Dated: January 2, 2013.</DATED>
          <NAME>Anna Snouffer,</NAME>
          <TITLE>Deputy Director, Office of Federal Advisory Committee Policy.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00088 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4140-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>National Institutes of Health</SUBAGY>
        <SUBJECT>Office of the Director, National Institutes of Health; Notice of Meeting</SUBJECT>
        <P>Pursuant to section 10(a) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of a meeting of the Recombinant DNA Advisory Committee.</P>
        <P>The meeting will be open to the public, with attendance limited to space available. Individuals who plan to attend and need special assistance, such as sign language interpretation or other reasonable accommodations, should notify the Contact Person listed below in advance of the meeting.</P>
        
        <EXTRACT>
          <P>
            <E T="03">Name of Committee:</E>Recombinant DNA Advisory Committee.</P>
          <P>
            <E T="03">Date:</E>January 24, 2013.</P>
          <P>
            <E T="03">Time:</E>9:00 a.m. to 4:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>The NIH Recombinant DNA Advisory Committee (RAC) will discuss Biosafety measures for research with highly pathogenic avian influenza H5N1 strains that have the potential to be transmissible through respiratory droplets and related data management activities. Please check the meeting agenda at OBA Meetings Page (available at the following URL:<E T="03">http://oba.od.nih.gov/rdna_rac/rac_meetings.html</E>) for more information.</P>
          <P>
            <E T="03">Place:</E>National Institutes of Health, Building 45, Lower Level, Conference Room C1-C2, 45 Center Drive, Rockville, MD 20892.</P>
          <P>
            <E T="03">Contact Person:</E>Chezelle George, Office of Biotechnology Activities, Office of Science Policy/OD, National Institutes of Health, 6705 Rockledge Drive, Room 750, Bethesda, MD 20892, 301-496-9838,<E T="03">georgec@od.nih.gov.</E>
          </P>
          

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

          <P>OMB's “Mandatory Information Requirements for Federal Assistance Program Announcements” (45 FR 39592, June 11,<PRTPAGE P="1217"/>1980) requires a statement concerning the official government programs contained in the Catalog of Federal Domestic Assistance. Normally NIH lists in its announcements the number and title of affected individual programs for the guidance of the public. Because the guidance in this notice covers virtually every NIH and Federal research program in which DNA recombinant molecule techniques could be used, it has been determined not to be cost effective or in the public interest to attempt to list these programs. Such a list would likely require several additional pages. In addition, NIH could not be certain that every Federal program would be included as many Federal agencies, as well as private organizations, both national and international, have elected to follow the NIH Guidelines. In lieu of the individual program listing, NIH invites readers to direct questions to the information address above about whether individual programs listed in the Catalog of Federal Domestic Assistance are affected.</P>
          
          <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.14, Intramural Research Training Award; 93.22, Clinical Research Loan Repayment Program for Individuals from Disadvantaged Backgrounds; 93.232, Loan Repayment Program for Research Generally; 93.39, Academic Research Enhancement Award; 93.936, NIH Acquired Immunodeficiency Syndrome Research Loan Repayment Program; 93.187, Undergraduate Scholarship Program for Individuals from Disadvantaged Backgrounds, National Institutes of Health, HHS)</FP>
        </EXTRACT>
        
        <P>In the interest of security, NIH has instituted stringent procedures for entrance onto the NIH campus. All visitor vehicles, including taxicabs, hotel, and airport shuttles will be inspected before being allowed on campus. Visitors will be asked to show one form of identification (for example, a government-issued photo ID, driver's license, or passport) and to state the purpose of their visit.</P>

        <P>OBA will offer those members of the public viewing the meeting via webcast (see link on<E T="03">OBA Meetings Page</E>) the opportunity to submit comments to be read during the scheduled public comment periods. Individuals wishing to submit comments should use the comment form, which will accommodate comments up to 1500 characters, and will be available on the<E T="03">OBA Meetings Page</E>during the meeting. Please submit your comment prior to the start of the public comment period. Please limit your comment to a statement that can be read in one to two minutes. Please include your name and affiliation with your comment.</P>
        <P>OBA will read comments into the record during the public comment periods that are specified on the agenda. Please note, while every effort is made to keep the meeting discussions to the times stated on the agenda, it is not unusual for the meeting to run ahead or behind schedule due to changes in the time needed to review a protocol. It is advisable to monitor the webcast to determine when public comments will be read. Comments submitted electronically will follow any comments by individuals attending the meeting in person. Comments will be read in the order received and your name and affiliation will be read with the comment. Please note OBA may not be able to read every comment received in the time allotted for public comment. Comments not read will become part of the public record.</P>
        <P>Any interested person may file written comments with the committee by forwarding the statement to the Contact Person listed on this notice. The statement should include the name, address, telephone number and when applicable, the business or professional affiliation of the interested person.</P>
        <SIG>
          <DATED>Dated: January 3, 2012.</DATED>
          <NAME>Carolyn A. Baum,</NAME>
          <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00089 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4140-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
        <SUBAGY>National Institutes of Health</SUBAGY>
        <SUBJECT>National Institute on Deafness and Other Communication Disorders; Notice of Closed Meetings</SUBJECT>
        <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meetings.</P>
        <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
        
        <EXTRACT>
          <P>
            <E T="03">Name of Committee:</E>National Institute on Deafness and Other Communication Disorders Special Emphasis Panel Chemosensory P50 Review.</P>
          <P>
            <E T="03">Date:</E>January 31, 2013.</P>
          <P>
            <E T="03">Time:</E>12:00 p.m. to 3:30 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>National Institutes of Health, 6120 Executive Blvd.,  Rockville, MD 20852, (Telephone Conference Call).</P>
          <P>
            <E T="03">Contact Person:</E>Sheo Singh, Ph.D., Scientific Review Officer, Scientific Review Branch,  Division of Extramural Activities, Executive Plaza South, Room 400C, 6120 Executive Blvd.,  Bethesda, MD 20892, 301-496-8683,<E T="03">singhs@nidcd.nih.gov.</E>
          </P>
          
          <P>
            <E T="03">Name of Committee:</E>National Institute on Deafness and Other Communication Disorders Special Emphasis Panel, SBIR Review Meeting.</P>
          <P>
            <E T="03">Date:</E>February 5, 2013.</P>
          <P>
            <E T="03">Time:</E>12:00 p.m. to 2:00 p.m.</P>
          <P>
            <E T="03">Agenda:</E>To review and evaluate grant applications.</P>
          <P>
            <E T="03">Place:</E>National Institutes of Health, 6120 Executive Blvd.,  Rockville, MD 20852.</P>
          <P>
            <E T="03">Contact Person:</E>Sheo Singh, Ph.D., Scientific Review Officer, Scientific Review Branch,  Division of Extramural Activities, Executive Plaza South, Room 400C, 6120 Executive Blvd., Bethesda, MD 20892, 301-496-8683,<E T="03">singhs@nidcd.nih.gov.</E>
          </P>
          <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.173, Biological Research Related to Deafness and Communicative Disorders, National Institutes of Health, HHS)</FP>
        </EXTRACT>
        <SIG>
          <DATED>Dated: December 31, 2012.</DATED>
          <NAME>Melanie J. Gray,</NAME>
          <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00087 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4140-01-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>Coast Guard</SUBAGY>
        <DEPDOC>[Docket No. USCG-2012-1080]</DEPDOC>
        <SUBJECT>Merchant Marine Personnel Advisory Committee; Vacancies</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Coast Guard, DHS.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Request for applications.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Coast Guard seeks applications for membership on the Merchant Marine Personnel Advisory Committee (MERPAC). This Committee advises the Secretary of the Department of Homeland Security on matters related to personnel in the U.S. merchant marine, including but not limited to training, qualifications, certification, documentation, and fitness standards.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Applicants should submit a cover letter and resume in time to reach the Alternate Designated Federal Officer (ADFO) on or before March 11, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Applicants should send their cover letter and resume to the following address: Commandant (CG-OES-1),  ATTN MERPAC, US Coast Guard, 2100 2ND ST SW STOP 7126, WASHINGTON DC 20593-7126; or by faxing (202) 372-1926; or by emailing to<E T="03">davis.j.breyer@uscg.mil.</E>This notice is available in our online docket, USCG-2012-1080, at<E T="03">http://www.regulations.gov.</E>
          </P>
        </ADD>
        <FURINF>
          <PRTPAGE P="1218"/>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>Davis J. Breyer, ADFO of MERPAC; telephone 202-372-1445 or email at<E T="03">davis.j.breyer@uscg.mil.</E>
          </P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>

        <P>MERPAC is a Federal advisory committee established under the authority of section 871 of The Homeland Security Act of 2002, (Title 6, United States Code, section 451). This committee is established in accordance with and operates under the provisions of the<E T="03">Federal Advisory Committee Act</E>(FACA) (Title 5, United States Code, Appendix). MERPAC advises the Secretary of the Department of Homeland Security on matters relating to personnel in the U.S. merchant marine, including but not limited to training, qualifications, certification, documentation, and fitness standards. The Committee will advise, consult with, and make recommendations reflecting its independent judgment to the Secretary.</P>
        <P>MERPAC is expected to meet approximately twice a year as called for by its charter, once at or near Coast Guard Headquarters, Washington, DC, and once at a location outside of Washington. It may also meet for extraordinary purposes. Its subcommittees and working groups may also meet to consider specific tasks as required.</P>
        <P>We will consider applications for six positions that expire or become vacant on June 1, 2013. To be eligible, you should have experience in one or more of the following areas of expertise: One position for a marine educator representing the viewpoint of State Maritime Academies; one position for a licensed engineering officer who is licensed as either a limited chief engineer or a designated duty engineer; one position for a licensed deck officer with an unlimited tonnage master's license with experience on tank vessels; one position for a member who represents the viewpoint of shipping companies employed in ship operation management; one position for an unlicensed seaman who represents the viewpoint of Qualified Members of the Engine Department; and one position for a member who will be drawn from the general public.</P>

        <P>If you are selected as a member from the general public, you will be appointed and serve as a Special Government Employee (SGE) as defined in section 202(a) of title 18, United States Code. As a candidate for appointment as a SGE, applicants are required to complete a Confidential Financial Disclosure Report (OGE Form 450). A completed OGE Form 450 is not releasable to the public except under an order issued by a Federal court or as otherwise provided under the<E T="03">Privacy Act</E>(5 U.S.C. 552a). Only the Designated Agency Ethics Official (DAEO) or his or her designee may release a Confidential Financial Disclosure Report. Applicants can obtain this form by going to the Web site of the Office of Government Ethics (<E T="03">www.oge.gov</E>) or by contacting the individual listed above in the<E T="02">FOR FURTHER INFORMATION CONTACT</E>section of this notice. Applications not accompanied by a completed OGE-Form 450 will not be considered.</P>

        <P>Registered lobbyists are not eligible to serve on federal advisory committees. Registered lobbyists are lobbyists required to comply with provisions contained in the<E T="03">Lobbying Disclosure Act of 1995</E>(Pub. L. 104-65 as amended).</P>
        <P>Each MERPAC committee member serves a term of office of up to three years. Members may be considered to serve consecutive terms. All members serve without compensation from the Federal Government; however, upon request, they do receive travel reimbursement and per diem.</P>
        <P>The Department of Homeland Security (DHS) does not discriminate in employment on the basis of race, color, religion, sex, national origin, political affiliation, sexual orientation, gender identity, marital status, disability and genetic information, age, membership in an employee organization, or any other non-merit factor.</P>

        <P>If you are interested in applying to become a member of the Committee, send your cover letter and resume to Davis J. Breyer, ADFO of MERPAC by mail, fax, or email according to the instructions in the<E T="02">ADDRESSES</E>section of this notice. Send your cover letter and resume in time for it to be received by the ADFO on or before March 11, 2013.</P>
        <P>To visit our online docket, go to<E T="03">http://www.regulations.gov,</E>enter the docket number for this notice (USCG-2012-1080) in the Search box, and click “Search”. Please do not post your resume on this site. During the vetting process, applicants may be asked to provide date of birth and social security number.</P>
        <SIG>
          <DATED>Dated: December 31, 2012.</DATED>
          <NAME>J. G. Lantz,</NAME>
          <TITLE>Director of Commercial Regulations and Standards.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00090 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9110-04-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>U.S. Citizenship and Immigration Services</SUBAGY>
        <DEPDOC>[OMB Control Number 1615-0010]</DEPDOC>
        <SUBJECT>Agency Information Collection Activities: Nonimmigrant Petition Based on Blanket L Petition; Form I-129S; Revision of a Currently Approved Collection</SUBJECT>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>60-Day Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>The Department of Homeland Security (DHS), U.S. Citizenship and Immigration Services (USCIS) invites the general public and other Federal agencies to comment upon this proposed revision of a currently approved collection of information. In accordance with the Paperwork Reduction Act (PRA) of 1995, the information collection notice is published in the<E T="04">Federal Register</E>to obtain comments regarding the nature of the information collection, the categories of respondents, the estimated burden (i.e. the time, effort, and resources used by the respondents to respond), the estimated cost to the respondent, and the actual information collection instruments.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Comments are encouraged and will be accepted for 60 days until March 11, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>All submissions received must include the OMB Control Number 1615-0010 in the subject box, the agency name and Docket ID USCIS-2006-0050. To avoid duplicate submissions, please use only one of the following methods to submit comments:</P>
          <P>(1)<E T="03">Online.</E>Submit comments via the Federal eRulemaking Portal Web site at<E T="03">www.Regulations.gov</E>under e-Docket ID number USCIS-2006-0050;</P>
          <P>(2)<E T="03">Email.</E>Submit comments to<E T="03">USCISFRComment@uscis.dhs.gov</E>;</P>
          <P>(3)<E T="03">Mail.</E>Submit written comments to DHS, USCIS, Office of Policy and Strategy, Chief, Regulatory Coordination Division, 20 Massachusetts Avenue NW., Washington, DC 20529-2140.</P>
        </ADD>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">Comments</HD>

        <P>Regardless of the method used for submitting comments or material, all submissions will be posted, without change, to the Federal eRulemaking Portal at<E T="03">http://www.regulations.gov</E>, and will include any personal information you provide. Therefore, submitting this information makes it public. You may wish to consider limiting the amount of personal<PRTPAGE P="1219"/>information that you provide in any voluntary submission you make to DHS. DHS may withhold information provided in comments from public viewing that it determines may impact the privacy of an individual or is offensive. For additional information, please read the Privacy Act notice that is available via the link in the footer of<E T="03">http://www.regulations.gov</E>.</P>
        <NOTE>
          <HD SOURCE="HED">Note:</HD>

          <P>The address listed in this notice should only be used to submit comments concerning this information collection. Please do not submit requests for individual case status inquiries to this address. If you are seeking information about the status of your individual case, please check “My Case Status” online at:<E T="03">https://egov.uscis.gov/cris/Dashboard.do</E>, or call the USCIS National Customer Service Center at 1-800-375-5283.</P>
        </NOTE>
        <P>Written comments and suggestions from the public and affected agencies should address one or more of the following four points:</P>
        <P>(1) Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
        <P>(2) Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
        <P>(3) Enhance the quality, utility, and clarity of the information to be collected; and</P>
        <P>(4) Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, e.g., permitting electronic submission of responses.</P>
        <HD SOURCE="HD1">Overview of This Information Collection</HD>
        <P>(1)<E T="03">Type of Information Collection:</E>Revision of a Currently Approved Collection.</P>
        <P>(2)<E T="03">Title of the Form/Collection:</E>Nonimmigrant Petition Based on Blanket L Petition.</P>
        <P>(3)<E T="03">Agency form number, if any, and the applicable component of the DHS sponsoring the collection:</E>I-129S; USCIS.</P>
        <P>(4)<E T="03">Affected public who will be asked or required to respond, as well as a brief abstract: Primary:</E>Business or others for profit. This form is used by an employer to classify employees as L-1 nonimmigrant intracompany transferees under a blanket L petition approval. USCIS will use the data on this form to determine eligibility for the requested immigration benefit.</P>
        <P>(5)<E T="03">An estimate of the total number of respondents and the amount of time estimated for an average respondent to respond:</E>75,000 responses at 1.5 hours (1 hour and 30 minutes) per response.</P>
        <P>(6)<E T="03">An estimate of the total public burden (in hours) associated with the collection:</E>112,500 annual burden hours.</P>

        <P>If you need a copy of the information collection instrument with instructions, or additional information, please visit the Federal eRulemaking Portal site at:<E T="03">http://www.regulations.gov</E>. We may also be contacted at: USCIS, Office of Policy and Strategy, Regulatory Coordination Division, 20 Massachusetts Avenue NW., Washington, DC 20529-2140, Telephone number 202-272-8377.</P>
        <SIG>
          <DATED>Dated: January 3, 2013.</DATED>
          <NAME>Laura Dawkins,</NAME>
          <TITLE>Chief,Regulatory Coordination Division,Office of Policy and Strategy,U.S. Citizenship and Immigration Services,Department of Homeland Security.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00161 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9111-97-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>U.S. Customs and Border Protection</SUBAGY>
        <SUBJECT>Agency Information Collection Activities:Delivery Ticket</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>U.S. Customs and Border Protection, Department of Homeland Security.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>30-Day notice and request for comments; Extension of an existing information collection.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>U.S. Customs and Border Protection (CBP) of the Department of Homeland Security will be submitting the following information collection request to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act: Delivery Ticket (CBP 6043). This is a proposed extension of an information collection that was previously approved. CBP is proposing that this information collection be extended with no change to the burden hours. This document is published to obtain comments from the public and affected agencies. This information collection was previously published in the<E T="04">Federal Register</E>(77 FR 65900) on October 31, 2012, allowing for a 60-day comment period. This notice allows for an additional 30 days for public comments. This process is conducted in accordance with 5 CFR 1320.10.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Written comments should be received on or before February 7, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Interested persons are invited to submit written comments onthis information collection to the Office of Information and Regulatory Affairs, Office of Management and Budget. Comments should be addressed to the OMB Desk Officer for U.S. Customs and Border Protection, Department of Homeland Security, and sent via electronic mail to<E T="03">oira_submission@omb.eop.gov</E>or faxed to (202) 395-5806.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Requests for additional information should be directed to Tracey Denning, U.S. Customs and Border Protection, Regulationsand Rulings, Office of International Trade, 799 9th Street, NW., 5th Floor, Washington, DC. 20229-1177, at 202-325-0265.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>CBP invites the general public and affected Federal agencies to submit written comments and suggestions on proposed and/or continuing information collection requests pursuant to the Paperwork Reduction Act (Pub. L.104-13). Your comments should address one of the following four points:</P>
        <P>(1) Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency/component, including whether the information will have practical utility;</P>
        <P>(2) Evaluate the accuracy of the agencies/components estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
        <P>(3) Enhance the quality, utility, and clarity of the information to be collected; and</P>
        <P>(4) Minimize the burden of the collections of information on those who are to respond, including the use of appropriate automated, electronic, mechanical, or other technological techniques or other forms of information.</P>
        <P>
          <E T="03">Title:</E>Delivery Ticket.</P>
        <P>
          <E T="03">OMB Number:</E>1651-0081.</P>
        <P>
          <E T="03">Form Number:</E>CBP Form 6043.</P>
        <P>
          <E T="03">Abstract:</E>CBP Form 6043,<E T="03">Delivery Ticket,</E>is used to document transfers of imported merchandise between parties. This form collects information such as the name and address of the consignee; the name of the importing carrier; lien information; the location of where the goods originated and where they were delivered; and information about the imported merchandise. CBP Form 6043 is filled out by warehouse proprietors,<PRTPAGE P="1220"/>carriers, Foreign Trade Zone operators and others involved in transfers of imported merchandise. This form is authorized by 19 U.S.C .1551a and 1565, and provided for by 19 CFR 4.34, 4.37 and 19.9. It is accessible at:<E T="03">http://forms.cbp.gov/pdf/CBP_Form_6043.pdf</E>
        </P>
        <P>
          <E T="03">Action:</E>CBP proposes to extend the expiration date of this information collection with no change to the estimated burden hours.</P>
        <P>
          <E T="03">Type of Review:</E>Extension (without change).</P>
        <P>
          <E T="03">Affected Public:</E>Businesses.</P>
        <P>
          <E T="03">Estimated Number of Respondents:</E>1000.</P>
        <P>
          <E T="03">Estimated Number of Annual Responses per Respondent:</E>200.</P>
        <P>
          <E T="03">Estimated Number of Total Annual Responses:</E>200,000.</P>
        <P>
          <E T="03">Estimated Time per Response:</E>20 minutes.</P>
        <P>
          <E T="03">Estimated Total Annual Burden Hours:</E>66,000.</P>
        <SIG>
          <DATED>Dated: January 3, 2013.</DATED>
          <NAME>Tracey Denning,</NAME>
          <TITLE>Agency Clearance Officer,U.S. Customs and Border Protection.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00141 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9111-14-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>U.S. Customs and Border Protection</SUBAGY>
        <SUBJECT>Agency Information Collection Activities: Guarantee of Payment</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>U.S. Customs and Border Protection, Department of Homeland Security.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>30-Day notice and request for comments; Extension of an existing information collection.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>U.S. Customs and Border Protection (CBP) of the Department of Homeland Security will be submitting the following information collection request to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act: Guarantee of Payment (CBP Form I-510). This is a proposed extension of an information collection that was previously approved. CBP is proposing that this information collection be extended with no change to the burden hours. This document is published to obtain comments from the public and affected agencies. This information collection was previously published in the<E T="04">Federal Register</E>(77 FR 65899) on October 31, 2012, allowing for a 60-day comment period. This notice allows for an additional 30 days for public comments. This process is conducted in accordance with 5 CFR 1320.10.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Written comments should be received on or before February 7, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Interested persons are invited to submit written comments on this information collection to the Office of Information and Regulatory Affairs, Office of Management and Budget. Comments should be addressed to the OMB Desk Officer for U.S. Customs and Border Protection, Department of Homeland Security, and sent via electronic mail to<E T="03">oira_submission@omb.eop.gov</E>or faxed to (202) 395-5806.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Requests for additional information should be directed to Tracey Denning, U.S. Customs and Border Protection, Regulations and Rulings, Office of International Trade, 799 9th Street NW., 5th Floor, Washington, DC 20229-1177, at 202-325-0265.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>CBP invites the general public and affected Federal agencies to submit written comments and suggestions on proposed and/or continuing information collection requests pursuant to the Paperwork Reduction Act (Pub. L. 104-13). Your comments should address one of the following four points:</P>
        <P>(1) Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency/component, including whether the information will have practical utility;</P>
        <P>(2) Evaluate the accuracy of the agencies/components estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
        <P>(3) Enhance the quality, utility, and clarity of the information to be collected; and</P>
        <P>(4) Minimize the burden of the collections of information on those who are to respond, including the use of appropriate automated, electronic, mechanical, or other technological techniques or other forms of information.</P>
        <P>
          <E T="03">Title:</E>Guarantee of Payment.</P>
        <P>
          <E T="03">OMB Number:</E>1651-0127.</P>
        <P>
          <E T="03">Form Number:</E>CBP Form I-510.</P>
        <P>
          <E T="03">Abstract:</E>Section 253 of the Immigration and Nationality Act (INA) requires that an alien crewman found to be or suspected of being afflicted with any of the diseases named in section 255 of the INA shall be placed in a hospital for treatment and/or observation with the expense of such observation and/or treatment being borne by the carrier. The guarantee of payment for medical and other related expenses required by section 253 of the Act shall be executed by the owner, agent, consignee, commanding officer or master of the vessel or aircraft on CBP Form I-510,<E T="03">Guarantee of Payment.</E>No vessel or aircraft can be granted clearance until such expenses are paid or the payment is appropriately guaranteed.</P>

        <P>CBP Form I-510 collects information such as the name of the owner, agent, commander officer or master of the vessel or aircraft; the name of the crewman; the port of arrival; and signature of the guarantor. This form is provided for by 8 CFR 253.1 and is accessible at:<E T="03">http://forms.cbp.gov/pdf/CBP_Form_i510.pdf.</E>
        </P>
        <P>
          <E T="03">Action:</E>CBP proposes to extend the expiration date of this information collection with no change to the estimated burden hours or to CBP Form I-510.</P>
        <P>
          <E T="03">Type of Review:</E>Extension (without change).</P>
        <P>
          <E T="03">Affected Public:</E>Businesses.</P>
        <P>
          <E T="03">Estimated Number of Respondents:</E>100.</P>
        <P>
          <E T="03">Estimated Number of Total Annual Responses:</E>100.</P>
        <P>
          <E T="03">Estimated Time per Response:</E>5<E T="03"/>minutes.</P>
        <P>
          <E T="03">Estimated Total Annual Burden Hours:</E>8.</P>
        <SIG>
          <DATED>Dated: January 3, 2013.</DATED>
          <NAME>Tracey Denning,</NAME>
          <TITLE>Agency Clearance Officer, U.S. Customs and Border Protection.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00150 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9111-14-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>U.S. Customs and Border Protection</SUBAGY>
        <SUBJECT>Agency Information Collection Activities: Regulations Relating to Recordation and Enforcement of Trademarks and Copyrights</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>U.S. Customs and Border Protection, Department of Homeland Security.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>30-Day notice and request for comments; Extension of an existing information collection.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>U.S. Customs and Border Protection (CBP) of the Department of Homeland Security will be submitting the following information collection request to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act: Regulations Relating to Recordation and Enforcement of Trademarks and Copyrights (Part 133 of<PRTPAGE P="1221"/>the CBP Regulations). This is a proposed extension of an information collection that was previously approved. CBP is proposing that this information collection be extended with no change to the burden hours. This document is published to obtain comments from the public and affected agencies. This information collection was previously published in the<E T="04">Federal Register</E>(77 FR 64533) on October 22, 2012, allowing for a 60-day comment period. Two comments were received. This notice allows for an additional 30 days for public comments. This process is conducted in accordance with 5 CFR 1320.10.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>Written comments should be received on or before February 7, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>Interested persons are invited to submit written comments on this information collection to the Office of Information and Regulatory Affairs, Office of Management and Budget. Comments should be addressed to the OMB Desk Officer for U.S. Customs and Border Protection, Department of Homeland Security, and sent via electronic mail to<E T="03">oira_submission@omb.eop.gov</E>or faxed to (202) 395-5806.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Requests for additional information should be directed to Tracey Denning, U.S. Customs and Border Protection, Regulations and Rulings, Office of International Trade, 799 9th Street NW., 5th Floor, Washington, DC 20229-1177, at 202-325-0265.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>CBP invites the general public and affected Federal agencies to submit written comments and suggestions on proposed and/or continuing information collection requests pursuant to the Paperwork Reduction Act (Pub. L. 104-13). Your comments should address one of the following four points:</P>
        <P>(1) Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency/component, including whether the information will have practical utility;</P>
        <P>(2) Evaluate the accuracy of the agency/component estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
        <P>(3) Enhance the quality, utility, and clarity of the information to be collected; and</P>
        <P>(4) Minimize the burden of the collections of information on those who are to respond, including the use of appropriate automated, electronic, mechanical, or other technological techniques or other forms of information.</P>
        <P>
          <E T="03">Title:</E>Regulations Relating to Recordation and Enforcement of Trademark and Copyrights (Part 133 of the CBP Regulations).</P>
        <P>
          <E T="03">OMB Number:</E>1651-0123.</P>
        <P>
          <E T="03">Form Number:</E>None.</P>
        <P>
          <E T="03">Abstract:</E>In accordance with 19 CFR part 133, trademark and trade name owners and those claiming copyright protection may submit information to CBP to enable CBP officers to identify violating articles at the borders. Parties seeking to have merchandise excluded from entry must provide proof to CBP of the validity of the rights they seek to protect. The information collected by CBP is used to identify infringing goods at the borders and determine if such goods infringe on intellectual property rights for which federal law provides import protection. Respondents may submit their information to CBP electronically at<E T="03">https://apps.cbp.gov/e-recordations/,</E>or they may submit their information on paper in accordance with 19 CFR 133.2 and 133.3 for trademarks, or 19 CFR 133.32 and 133.33 for copyrights.</P>
        <P>
          <E T="03">Current Actions:</E>This submission is being made to extend the expiration date.</P>
        <P>
          <E T="03">Type of Review:</E>Extension (without change).</P>
        <P>
          <E T="03">Affected Public:</E>Businesses and Individuals.</P>
        <P>
          <E T="03">Estimated Number of Respondents:</E>2,000.</P>
        <P>
          <E T="03">Estimated Time per Respondent:</E>2 hours.</P>
        <P>
          <E T="03">Estimated Total Annual Burden Hours:</E>4,000.</P>
        <SIG>
          <DATED>Dated: January 3, 2013.</DATED>
          <NAME>Tracey Denning,</NAME>
          <TITLE>Agency Clearance Officer,  U.S. Customs and Border Protection.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00144 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9111-14-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>U.S. Customs and Border Protection</SUBAGY>
        <SUBJECT>Notice of Issuance of Final Determination Concerning Ponstel® (Mefenamic Acid) Capsules</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>U.S. Customs and Border Protection, Department of Homeland Security.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of final determination.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>This document provides notice that U.S. Customs and Border Protection (“CBP”) has issued a final determination concerning the country of origin of Ponstel® (mefenamic acid) capsules. Based upon the facts presented, CBP has concluded in the final determination that India is the country of origin of the Ponstel (mefenamic acid) capsules for purposes of U.S. Government procurement.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>The final determination was issued on December 26, 2012. A copy of the final determination is attached. Any party-at-interest, as defined in 19 CFR 177.22(d), may seek judicial review of this final determination on or before February 7, 2013.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Heather K. Pinnock, Valuation and Special Programs Branch: (202) 325-0034.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>Notice is hereby given that on December 26, 2012, pursuant to subpart B of part 177, Customs and Border Protection Regulations (19 CFR part 177, subpart B), CBP issued a final determination concerning the country of origin of Ponstel (mefenamic acid) capsules, which may be offered to the U.S. Government under an undesignated government procurement contract. This final determination, in HQ H233356, was issued at the request of West-Ward Pharmaceutical Corp., under procedures set forth at 19 CFR part 177, subpart B, which implements Title III of the Trade Agreements Act of 1979, as amended (19 U.S.C. 2511-18). In the final determination CBP concluded that, based upon the facts presented, mefenamic acid from India, blended with excipients and packaged into dosage form in the United States, was not substantially transformed in the United States, such that India is the country of origin of the finished Ponstel (mefenamic acid) capsules for purposes of U.S. Government procurement.</P>

        <P>Section 177.29, CBP Regulations (19 CFR 177.29), provides that a notice of final determination shall be published in the<E T="04">Federal Register</E>within 60 days of the date the final determination is issued. Section 177.30, CBP Regulations (19 CFR 177.30), provides that any party-at-interest, as defined in 19 CFR 177.22(d), may seek judicial review of a final determination within 30 days of publication of such determination in the<E T="04">Federal Register</E>.</P>
        <SIG>
          <DATED>Dated: January 3, 2013.</DATED>
          <NAME>Jeremy Baskin,</NAME>
          <TITLE>Acting Executive Director, Regulations and Rulings, Office of International Trade.</TITLE>
        </SIG>
        <EXTRACT>
          <HD SOURCE="HD1">Attachment</HD>
          <HD SOURCE="HD1">HQ H233356</HD>
          <HD SOURCE="HD2">December 26, 2012</HD>
          <FP SOURCE="FP-1">MAR-2 OT:RR:CTF:VS H233356HkP<PRTPAGE P="1222"/>
          </FP>
          <FP SOURCE="FP-1">CATEGORY: Origin</FP>
          
          <FP SOURCE="FP-1">Ms. Susan Todd</FP>
          <FP SOURCE="FP-1">Senior Manager, Regulatory Affairs</FP>
          <FP SOURCE="FP-1">West-Ward Pharmaceutical Corp.</FP>
          <FP SOURCE="FP-1">435 Industrial Way West</FP>
          <FP SOURCE="FP-1">Eatontown, NJ 07724</FP>
          
          <FP SOURCE="FP-2">RE: Government Procurement; Trade Agreements Act; Country of Origin of Ponstel® (mefenamic acid) Capsules; Substantial Transformation</FP>
          
          <FP>Dear Ms. Todd:</FP>
          <P>This is in response to your letter, dated August 21, 2012, requesting a final determination on behalf of West-Ward Pharmaceutical Corp. (“West-Ward”) pursuant to subpart B of part 177 of the U.S. Customs and Border Protection (“CBP”) Regulations (19 C.F.R. Part 177). Under these regulations, which implement Title III of the Trade Agreements Act of 1979 (“TAA”), as amended (19 U.S.C. § 2511 et seq.), CBP issues country of origin advisory rulings and final determinations as to whether an article is or would be a product of a designated country or instrumentality for the purposes of granting waivers of certain “Buy American” restrictions in U.S. law or practice for products offered for sale to the U.S. Government.</P>
          <P>This final determination concerns the country of origin of Ponstel (mefenamic acid) capsules. As a U.S. importer, West-Ward is a party-at-interest within the meaning of 19 C.F.R. § 177.22(d)(1) and is entitled to request this final determination.</P>
          <HD SOURCE="HD3">FACTS:</HD>
          <P>West-Ward imports mefenamic acid powder in bulk form from India, where it is manufactured. Mefenamic acid is the active pharmaceutical ingredient (“API”) in the pharmaceutical product Ponstel. Ponstel is indicated for the relief of mild to moderate pain caused by primary dysmenorrhea and is approved by the U.S. Food and Drug Administration, NDA no. 015034.</P>
          <P>After importation, West-Ward combines the API, mefenamic acid, with inactive ingredients and processes it into dosage form. The inactive ingredients are lactose monohydrate, D&amp;C Yellow No. 10, FD&amp;C Yellow No. 6, gelatin, titanium dioxide, and food-grade inks. The mefenamic acid is added to a tumbler and blended. Lactose monohydrate, a diluent, is then added to the tumbler and blended with the API. The blend is transferred to an encapsulating machine and used to fill capsules purchased from a U.S. supplier. The capsules are packed into bottles of 30 capsules each, which are packaged and shipped to the U.S.-holder of the New Drug Application for Ponstel.</P>
          <HD SOURCE="HD3">ISSUE:</HD>
          <P>What is the country of origin of Ponstel (mefenamic acid) capsules for purposes of U.S. Government procurement?</P>
          <HD SOURCE="HD3">LAW AND ANALYSIS:</HD>
          <P>Pursuant to Subpart B of Part 177, 19 CFR § 177.21 et seq., which implements Title III of the Trade Agreements Act of 1979, as amended (19 U.S.C. § 2511 et seq.), CBP issues country of origin advisory rulings and final determinations as to whether an article is or would be a product of a designated country or instrumentality for the purposes of granting waivers of certain “Buy American” restrictions in U.S. law or practice for products offered for sale to the U.S. Government.</P>
          <P>Under the rule of origin set forth under 19 U.S.C. § 2518(4)(B):</P>
          
          <P>An article is a product of a country or instrumentality only if (i) it is wholly the growth, product, or manufacture of that country or instrumentality, or (ii) in the case of an article which consists in whole or in part of materials from another country or instrumentality, it has been substantially transformed into a new and different article of commerce with a name, character, or use distinct from that of the article or articles from which it was so transformed.</P>
          
          <FP>
            <E T="03">See also</E>19 C.F.R. § 177.22(a).</FP>

          <P>A substantial transformation occurs when an article emerges from a process with a new name, character and use different from that possessed by the article prior to processing. A substantial transformation will not result from a minor manufacturing or combining process that leaves the identity of the article intact.<E T="03">See United States v. Gibson-Thomsen Co.,</E>27 C.C.P.A. 267 (1940); and,<E T="03">National Juice Products Association v. United States,</E>628 F. Supp. 978 (Ct. Int'l Trade 1986).</P>

          <P>In determining whether a substantial transformation occurs in the manufacture of chemical products such as pharmaceuticals, CBP has consistently examined the complexity of the processing and whether the final article retains the essential identity and character of the raw material. To that end, CBP has generally held that the processing of pharmaceutical products from bulk form into measured doses does not result in a substantial transformation of the product.<E T="03">See e.g.,</E>Headquarters Ruling Letter (“HQ”) 561975, dated April 3, 2002; HQ 561544, dated May 1, 2000; and, HQ 735146, dated November 15, 1993.</P>
          <P>For instance, in HQ 561975, the anesthetic drug sevoflurane imported into the U.S. in bulk form and processed into dosage form by extensive testing operations, followed by filtering and packaging into bottles, was found not to have undergone a substantial transformation in the U.S. There was no change in name (the product was identified as sevoflurane in both its bulk and processed form). The sevoflurane retained its chemical and physical properties after the U.S. processing. Lastly, because the imported bulk sevoflurane had a predetermined medicinal use as an inhalable anesthetic drug, the processing in the United States resulted in no change in the product's use.</P>
          <P>Likewise, in HQ 561544, the testing, filtering and sterile packaging of Geneticin Sulfate bulk powder, to create Geneticin Selective Antibiotic, was not found to have substantially transformed the antibiotic substance because the processing only involved the removal of impurities from the bulk chemical and the placement of the chemical into smaller packaging.</P>
          <P>In HQ 735146, 100 percent pure acetaminophen imported from China was blended with excipients in the United States, granulated and sold to pharmaceutical companies to process into tablets for retail sale under private labels. U.S. Customs (now CBP) found that the process in the United States did not substantially transform the imported product because the product was referred to as acetaminophen both before importation and after U.S. processing, as imported the acetaminophen was used for medicinal purposes and continued to be so used after U.S. processing, and the granulating process minimally affected the chemical and physical properties of the acetaminophen.</P>
          <P>In this case, the mefenamic acid imported from India is blended with excipients and packaged into dosage form in the United States. Based on the rulings above, we find that this process does not substantially transform the mefenamic acid because its chemical character remains the same. As such, we find that the country of origin of the Ponstel (mefenamic acid) capsules is India, where the mefanamic acid was manufactured.</P>
          <HD SOURCE="HD3">HOLDING:</HD>
          <P>Based on the facts in this case, the blending and packaging operations performed in the United States do not substantially transform the mefenamic acid imported from India. Therefore, the country of origin of the Ponstel® (mefenamic acid) capsules is India for purposes of U.S. Government procurement.</P>
          <P>Notice of this final determination will be given in the<E T="04">Federal Register</E>, as required by 19 C.F.R. § 177.29. Any party-at-interest other than the party which requested this final determination may request, pursuant to 19 C.F.R. § 177.31, that CBP reexamine the matter anew and issue a new final determination. Pursuant to 19 C.F.R. § 177.30, any party-at-interest may, within 30 days of publication of the<E T="04">Federal Register</E>Notice referenced above, seek judicial review of this final determination before the Court of International Trade.</P>
          <P>Sincerely,</P>
          <FP>Jeremy Baskin,</FP>
          <FP SOURCE="FP-1">
            <E T="03">Acting Executive Director, Regulations and Rulings, Office of International Trade.</E>
          </FP>
        </EXTRACT>
        
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00140 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE;P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
        <SUBAGY>U.S. Customs and Border Protection</SUBAGY>
        <SUBJECT>Quarterly IRS Interest Rates Used in Calculating Interest on Overdue Accounts and Refunds on Customs Duties</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>U.S. Customs and Border Protection, Department of Homeland Security.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>General notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>

          <P>This notice advises the public of the quarterly Internal Revenue Service interest rates used to calculate interest on overdue accounts (underpayments) and refunds (overpayments) of customs duties. For the calendar quarter beginning January 1, 2013, the interest rates for<PRTPAGE P="1223"/>overpayments will be 2 percent for corporations and 3 percent for non-corporations, and the interest rate for underpayments will be 3 percent for both corporations and non-corporations. This notice is published for the convenience of the importing public and U.S. Customs and Border Protection personnel.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Effective Date:</E>January 1, 2013.</P>
        </DATES>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Ron Wyman, Revenue Division, Collection and Refunds Branch, 6650 Telecom Drive, Suite #100, Indianapolis, Indiana 46278; telephone (317) 614-4516.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Background</HD>

        <P>Pursuant to 19 U.S.C. 1505 and Treasury Decision 85-93, published in the<E T="04">Federal Register</E>on May 29, 1985 (50 FR 21832), the interest rate paid on applicable overpayments or underpayments of customs duties must be in accordance with the Internal Revenue Code rate established under 26 U.S.C. 6621 and 6622. Section 6621 was amended (at paragraph (a)(1)(B) by the Internal Revenue Service Restructuring and Reform Act of 1998, Public Law 105-206, 112 Stat. 685) to provide different interest rates applicable to overpayments: one for corporations and one for non-corporations.</P>
        <P>The interest rates are based on the Federal short-term rate and determined by the Internal Revenue Service (IRS) on behalf of the Secretary of the Treasury on a quarterly basis. The rates effective for a quarter are determined during the first-month period of the previous quarter.</P>
        <P>In Revenue Ruling 2012-32, the IRS determined the rates of interest for the calendar quarter beginning January 1, 2013, and ending on March 31, 2013. The interest rate paid to the Treasury for underpayments will be the Federal short-term rate (1%) plus two percentage points (2%) for a total of three percent (3%) for both corporations and non-corporations. For corporate overpayments, the rate is the Federal short-term rate (1%) plus one percentage point (1%) for a total of two percent (2%). For overpayments made by non-corporations, the rate is the Federal short-term rate (1%) plus two percentage points (2%) for a total of three percent (3%). These interest rates are subject to change for the calendar quarter beginning April 1, 2013, and ending June 30, 2013.</P>
        <P>For the convenience of the importing public and U.S. Customs and Border Protection personnel the following list of IRS interest rates used, covering the period from before July of 1974 to date, to calculate interest on overdue accounts and refunds of customs duties, is published in summary format.</P>
        <GPOTABLE CDEF="10,10,10,10,10" COLS="5" OPTS="L2,tp0,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1">Beginning date</CHED>
            <CHED H="1">Ending date</CHED>
            <CHED H="1">
              <E T="03">Under-payments</E>
              <LI>
                <E T="03">(percent)</E>
              </LI>
            </CHED>
            <CHED H="1">Over-payments<LI>(percent)</LI>
            </CHED>
            <CHED H="1">Corporate overpayments<LI>(Eff. 1-1-99)</LI>
              <LI>(percent)</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">070174</ENT>
            <ENT>063075</ENT>
            <ENT>6</ENT>
            <ENT>6</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">070175</ENT>
            <ENT>013176</ENT>
            <ENT>9</ENT>
            <ENT>9</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">020176</ENT>
            <ENT>013178</ENT>
            <ENT>7</ENT>
            <ENT>7</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">020178</ENT>
            <ENT>013180</ENT>
            <ENT>6</ENT>
            <ENT>6</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">020180</ENT>
            <ENT>013182</ENT>
            <ENT>12</ENT>
            <ENT>12</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">020182</ENT>
            <ENT>123182</ENT>
            <ENT>20</ENT>
            <ENT>20</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">010183</ENT>
            <ENT>063083</ENT>
            <ENT>16</ENT>
            <ENT>16</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">070183</ENT>
            <ENT>123184</ENT>
            <ENT>11</ENT>
            <ENT>11</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">010185</ENT>
            <ENT>063085</ENT>
            <ENT>13</ENT>
            <ENT>13</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">070185</ENT>
            <ENT>123185</ENT>
            <ENT>11</ENT>
            <ENT>11</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">010186</ENT>
            <ENT>063086</ENT>
            <ENT>10</ENT>
            <ENT>10</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">070186</ENT>
            <ENT>123186</ENT>
            <ENT>9</ENT>
            <ENT>9</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">010187</ENT>
            <ENT>093087</ENT>
            <ENT>9</ENT>
            <ENT>8</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">100187</ENT>
            <ENT>123187</ENT>
            <ENT>10</ENT>
            <ENT>9</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">010188</ENT>
            <ENT>033188</ENT>
            <ENT>11</ENT>
            <ENT>10</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">040188</ENT>
            <ENT>093088</ENT>
            <ENT>10</ENT>
            <ENT>9</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">100188</ENT>
            <ENT>033189</ENT>
            <ENT>11</ENT>
            <ENT>10</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">040189</ENT>
            <ENT>093089</ENT>
            <ENT>12</ENT>
            <ENT>11</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">100189</ENT>
            <ENT>033191</ENT>
            <ENT>11</ENT>
            <ENT>10</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">040191</ENT>
            <ENT>123191</ENT>
            <ENT>10</ENT>
            <ENT>9</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">010192</ENT>
            <ENT>033192</ENT>
            <ENT>9</ENT>
            <ENT>8</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">040192</ENT>
            <ENT>093092</ENT>
            <ENT>8</ENT>
            <ENT>7</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">100192</ENT>
            <ENT>063094</ENT>
            <ENT>7</ENT>
            <ENT>6</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">070194</ENT>
            <ENT>093094</ENT>
            <ENT>8</ENT>
            <ENT>7</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">100194</ENT>
            <ENT>033195</ENT>
            <ENT>9</ENT>
            <ENT>8</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">040195</ENT>
            <ENT>063095</ENT>
            <ENT>10</ENT>
            <ENT>9</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">070195</ENT>
            <ENT>033196</ENT>
            <ENT>9</ENT>
            <ENT>8</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">040196</ENT>
            <ENT>063096</ENT>
            <ENT>8</ENT>
            <ENT>7</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">070196</ENT>
            <ENT>033198</ENT>
            <ENT>9</ENT>
            <ENT>8</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">040198</ENT>
            <ENT>123198</ENT>
            <ENT>8</ENT>
            <ENT>7</ENT>
            <ENT/>
          </ROW>
          <ROW>
            <ENT I="01">010199</ENT>
            <ENT>033199</ENT>
            <ENT>7</ENT>
            <ENT>7</ENT>
            <ENT>6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">040199</ENT>
            <ENT>033100</ENT>
            <ENT>8</ENT>
            <ENT>8</ENT>
            <ENT>7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">040100</ENT>
            <ENT>033101</ENT>
            <ENT>9</ENT>
            <ENT>9</ENT>
            <ENT>8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">040101</ENT>
            <ENT>063001</ENT>
            <ENT>8</ENT>
            <ENT>8</ENT>
            <ENT>7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">070101</ENT>
            <ENT>123101</ENT>
            <ENT>7</ENT>
            <ENT>7</ENT>
            <ENT>6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">010102</ENT>
            <ENT>123102</ENT>
            <ENT>6</ENT>
            <ENT>6</ENT>
            <ENT>5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">010103</ENT>
            <ENT>093003</ENT>
            <ENT>5</ENT>
            <ENT>5</ENT>
            <ENT>4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">100103</ENT>
            <ENT>033104</ENT>
            <ENT>4</ENT>
            <ENT>4</ENT>
            <ENT>3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">040104</ENT>
            <ENT>063004</ENT>
            <ENT>5</ENT>
            <ENT>5</ENT>
            <ENT>4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">070104</ENT>
            <ENT>093004</ENT>
            <ENT>4</ENT>
            <ENT>4</ENT>
            <ENT>3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">100104</ENT>
            <ENT>033105</ENT>
            <ENT>5</ENT>
            <ENT>5</ENT>
            <ENT>4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">040105</ENT>
            <ENT>093005</ENT>
            <ENT>6</ENT>
            <ENT>6</ENT>
            <ENT>5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">100105</ENT>
            <ENT>063006</ENT>
            <ENT>7</ENT>
            <ENT>7</ENT>
            <ENT>6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">070106</ENT>
            <ENT>123107</ENT>
            <ENT>8</ENT>
            <ENT>8</ENT>
            <ENT>7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">010108</ENT>
            <ENT>033108</ENT>
            <ENT>7</ENT>
            <ENT>7</ENT>
            <ENT>6</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="1224"/>
            <ENT I="01">040108</ENT>
            <ENT>063008</ENT>
            <ENT>6</ENT>
            <ENT>6</ENT>
            <ENT>5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">070108</ENT>
            <ENT>093008</ENT>
            <ENT>5</ENT>
            <ENT>5</ENT>
            <ENT>4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">100108</ENT>
            <ENT>123108</ENT>
            <ENT>6</ENT>
            <ENT>6</ENT>
            <ENT>5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">010109</ENT>
            <ENT>033109</ENT>
            <ENT>5</ENT>
            <ENT>5</ENT>
            <ENT>4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">040109</ENT>
            <ENT>123110</ENT>
            <ENT>4</ENT>
            <ENT>4</ENT>
            <ENT>3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">010111</ENT>
            <ENT>033111</ENT>
            <ENT>3</ENT>
            <ENT>3</ENT>
            <ENT>2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">040111</ENT>
            <ENT>093011</ENT>
            <ENT>4</ENT>
            <ENT>4</ENT>
            <ENT>3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">100111</ENT>
            <ENT>033113</ENT>
            <ENT>3</ENT>
            <ENT>3</ENT>
            <ENT>2</ENT>
          </ROW>
        </GPOTABLE>
        <SIG>
          <DATED>Dated: January 2, 2013.</DATED>
          <NAME>Thomas S. Winkowski,</NAME>
          <TITLE>Acting Deputy Commissioner, U.S. Customs and Border Protection.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00146 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 9111-14-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
        <DEPDOC>[Docket No. FR-5667-N-01]</DEPDOC>
        <SUBJECT>Supportive Housing for the Elderly; Advance Notice of Senior Preservation Rental Assistance Contracts Award Process</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Office of the Assistant Secretary for Housing—Federal Housing Commissioner, (HUD).</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>The Section 202 Supportive Housing for the Elderly Act of 2010, signed into law in January 2011, authorizes HUD to provide Senior Preservation Rental Assistance Contracts (SPRACs) with 20-year terms to prevent displacement of elderly residents of certain projects assisted under HUD's Section 202 Supportive Housing for the Elderly program in the case of refinancing or recapitalization and to further preserve and maintain affordability of Section 202 Direct Loan projects. In Fiscal Year (FY) 2012, $16 million was made available for SPRAC funding. This notice advises of HUD's intent to award SPRACs through the proposed application process described in this notice. HUD is soliciting comments on the proposed process for awarding SPRACs and the associated criteria for establishing eligibility to apply for a SPRAC.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>
            <E T="03">Comment Due Date: March 11, 2013.</E>
          </P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Interested persons are invited to submit comments regarding this notice to the Regulations Division, Office of General Counsel, Department of Housing and Urban Development, 451 7th Street SW., Room 10276, Washington, DC 20410-0500. Communications must refer to the above docket number and title. There are two methods for submitting public comments. All submissions must refer to the above docket number and title.</P>
          <P>
            <E T="03">1. Submission of Comments by Mail.</E>Comments may be submitted by mail to the Regulations Division, Office of General Counsel, Department of Housing and Urban Development, 451 7th Street SW., Room 10276, Washington, DC 20410-0500.</P>
          <P>
            <E T="03">2. Electronic Submission of Comments.</E>Interested persons may submit comments electronically through the Federal eRulemaking Portal at<E T="03">www.regulations.gov.</E>HUD strongly encourages commenters to submit comments electronically. Electronic submission of comments allows the commenter maximum time to prepare and submit a comment, ensures timely receipt by HUD, and enables HUD to make them immediately available to the public. Comments submitted electronically through the<E T="03">www.regulations.gov</E>Web site can be viewed by other commenters and interested members of the public. Commenters should follow the instructions provided on that site to submit comments electronically.</P>
        </ADD>
        <NOTE>
          <HD SOURCE="HED">Note:</HD>
          <P>To receive consideration as public comments, comments must be submitted through one of the two methods specified above. Again, all submissions must refer to the docket number and title of the notice.</P>
        </NOTE>
        <P>
          <E T="03">No Facsimile Comments.</E>Facsimile (FAX) comments are not acceptable.</P>
        <P>
          <E T="03">Public Inspection of Public Comments.</E>All properly submitted comments and communications submitted to HUD will be available for public inspection and copying between 8 a.m. and 5 p.m. weekdays at the above address. Due to security measures at the HUD Headquarters building, an appointment to review the public comments must be scheduled in advance by calling the Regulations Division at 202-708-3055 (this is not a toll-free number). Individuals with speech or hearing impairments may access this number via TTY by calling the Federal Relay Service at 800-877-8339. Copies of all comments submitted are available for inspection and downloading at<E T="03">www.regulations.gov.</E>
        </P>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Margaret Salazar, Deputy Director of the Office of Affordable Housing Development, Office of Multifamily Housing Programs, Office of Housing, Department of Housing and Urban Development, 451 7th Street SW., Room 6112, Washington, DC 20410; telephone number 202-708-2495 (this is not a toll-free number). Persons with hearing or speech impairments may access this number through TTY by calling the toll-free Federal Relay Service at 800-877-8339.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <HD SOURCE="HD1">I. Background</HD>
        <P>The Section 202 Supportive Housing for the Elderly Act of 2010 (Pub. L. 111-372, approved January 4, 2011) (Section 202 of 2010 Act) authorizes HUD to provide SPRACs with 20-year terms to prevent displacement of elderly residents of certain projects assisted under HUD's Section 202 Supportive Housing for the Elderly program (Section 202 program) in the case of refinancing or recapitalization and to further preserve and maintain affordability of Section 202 Direct Loan projects. General authority for a Section 202 Direct Loan is provided by Section 811 of the American Homeownership and Economic Opportunity (AHEO) Act of 2000, as amended by the Section 202 of 2010 Act (12 U.S.C. 1701q note). Pursuant to this authority, SPRAC assistance may be provided to Section 202 properties with original interest rates of 6 percent or less (financed prior to 1974), when the property is refinanced to make capital repairs and the owner does not anticipate debt service savings from the refinance. In FY 2012, $16 million was made available for SPRAC funding.</P>
        <HD SOURCE="HD1">II. This Notice—Solicitation of Comment</HD>

        <P>This notice advises of HUD's intent to award SPRACs through the proposed application process described in this notice. HUD is soliciting comments on<PRTPAGE P="1225"/>the proposed process for awarding SPRACs and the associated criteria for establishing eligibility to apply for a SPRAC. Specifically, HUD requests comment on the following sections of this notice:</P>
        <HD SOURCE="HD2">Eligibility Criteria</HD>
        <P>1. Are any additional eligibility criteria necessary to ensure those elderly residents most at risk of displacement receive SPRAC assistance?</P>
        <P>2. Should any of the eligibility criteria be removed or modified?</P>
        <P>3. Is eligibility criterion six—a seven percent or below vacancy rate—realistic for Section 202 properties with interest rates of 6 percent or less financed prior to 1974? If not, why not (please provide any data you have supporting your comments)?</P>
        <HD SOURCE="HD2">Award Process</HD>
        <P>1. Is the SPRAC award process an effective and efficient means of providing rental assistance to elderly residents at risk of displacement? Should HUD modify the award process? If so, how?</P>
        <P>2. Is separating qualified Owner-applicants into two pools based on willingness to target very low income elderly tenants an effective means of serving the population most in need? If so, how? If not, why (please provide any data or information you have supporting your comments)?</P>
        <P>HUD will take all comments into consideration and issue a final notice that will provide threshold criteria for Owner-applicant eligibility and final details of the FY 2012 SPRAC award process.</P>
        <HD SOURCE="HD1">III. Proposed SPRAC Application and Award Process</HD>
        <HD SOURCE="HD2">Purpose of the Program</HD>
        <P>The Section 202 Supportive Housing for the Elderly Act of 2010 (Pub. L. 111-372, approved January 4, 2011) (Section 202 of 2010 Act) authorizes HUD to provide SPRACs to unassisted Section 202 units. The SPRAC contracts will have 20-year terms, with funding subject to annual appropriations. The purpose of SPRACs is to prevent displacement of income-eligible elderly residents of Section 202 Direct Loan properties with original interest rates of 6 percent or less, when the property is refinanced and the Owner does not anticipate debt service savings from the refinance. General authority for a Section 202 Direct Loan is provided by Section 811 of the American Homeownership and Economic Opportunity (AHEO) Act of 2000, as amended by the Section 202 of 2010 Act (12 U.S.C. 1701q note). In order to be income-eligible to receive SPRAC assistance, household income must be 80 percent or below area median income (AMI).</P>
        <P>In addition to protecting elderly residents from displacement, SPRAC assistance is also intended to further preservation and affordability of these pre-1974 Section 202 Direct Loan projects. The mortgages on these properties, originally for 40 or 50-year terms, are reaching their maturity dates. When mortgages mature, the use and affordability restrictions of these properties expire, putting the long term affordability of this senior housing at risk. Very low-income elderly tenants of maturing mortgage properties are at the most immediate risk of displacement. The award process described in this notice will target these maturing mortgage properties by ranking qualified applications received by mortgage maturity date. Properties with mortgage maturity dates that predate the SPRAC application deadline, and properties with maturity dates sooner than 60 days following the SPRAC application deadline will not be eligible for SPRAC awards.</P>
        <P>HUD oversees a portfolio of 209 Section 202 properties with original interest rates of six percent or less. All were financed prior to 1974. Many pre-1974 Section 202 Direct Loan properties have never completed a rehabilitation effort and are in need of significant capital repairs. Owners may wish to prepay the existing Section 202 Direct Loan in order to obtain new financing to address the physical needs of the project. Even in a time of historically low interest rates, however, it is unlikely that the refinancing of an eligible Section 202 Direct Loan would result in a reduction in debt service.</P>
        <P>The anticipated increase in debt service from the Section 202 refinance places unassisted elderly residents in danger of displacement. Tenants may be at risk as Owners seek additional income to pay the increased debt service. The majority of pre-1974 Direct Loan projects are “partially assisted,” meaning that some, but not all units receive Section 8 Project Based Rental assistance. Under AHEO, as amended, the Owner may qualify to receive a Section 8 rent adjustment on the Section 8 units, which could bring additional income to cover the increased debt service requirement. However, it is unlikely that this income will be sufficient to pay the increased debt service. The Owner may look to the unassisted households of the project to pay a rent increase to cover the costs of the new loan. The imposition of a rent increase places unassisted elderly residents at risk of possible displacement. SPRAC assistance will provide rental assistance on previously unassisted units. In addition, this assistance may provide revenue that could offset the cost of a service coordinator or other operating costs. This assistance eliminates the need for Owners to impose rent increases on these vulnerable households.</P>

        <P>The provision of SPRACs is contingent on HUD approval of the Section 202 Direct Loan prepayment. As a matter of policy, HUD has determined that the amount of proposed repairs must rise to the level of substantial rehabilitation as defined in the HUD<E T="03">Multifamily Accelerated Processing (MAP) Guide, 4430-G, Rev-1.</E>Otherwise, the transaction could have the effect of merely trading low interest debt for higher interest debt.<SU>1</SU>
          <FTREF/>The substantial rehabilitation must be in compliance with the Section 504 accessibility requirements described in 24 CFR part 8. HUD applies the Uniform Federal Accessibility Standards (UFAS) through its regulations under part 8. The prepayment, in conjunction with the substantial rehabilitation of the project and the provision of SPRAC, will facilitate the improvement of the project and the long-term preservation of the project as housing affordable to current and future elderly households.</P>
        <FTNT>
          <P>
            <SU>1</SU>The MAP Guide may be accessed at<E T="03">http://portal.hud.gov/hudportal/HUD?src=/program_offices/administration/hudclips/guidebooks/hsg-GB4430.</E>
          </P>
        </FTNT>
        <P>The HUD Section 202 Direct Loan portfolio includes 18,600 unassisted units. To receive SPRAC assistance for these unassisted units, the project Owner must meet all SPRAC Notice requirements, and all prepayment requirements of AHEO. Over the next decade, an average of 2,000 unassisted units per year risk losing affordability due to maturing Section 202 loans.</P>
        <P>The Consolidated and Further Continuing Appropriations Act, 2012 (Public Law 112-55, approved November 18, 2011) makes funds available to fund the first year of assistance for 20-year project-based rental assistance contracts for unassisted units in qualifying Section 202 projects. The precise number of units/households to receive assistance will be determined based on the availability of funds.</P>

        <P>SPRACs are not Section 8 project based rental assistance Housing Assistance Payment (HAP) contracts. However, pursuant to the Section 202 of 2010 Act, HUD will administer SPRACs under the same requirements governing project-based rental assistance made<PRTPAGE P="1226"/>available under section 8 of the United States Housing Act of 1937 (42 U.S.C. 1473f), and implemented through the regulations at 24 CFR part 883. To be eligible for SPRAC assistance, residents must be income-eligible (at-or-below 80 percent of AMI). SPRAC assistance will only be provided to units occupied by income-eligible households at the time the SPRAC is executed. Initial SPRAC rents will be established based on market comparables. Over the 20-year term of the SPRAC, contracts will be administered using the processes described in the HUD<E T="03">Section 8 Renewal Policy Guidebook,</E>under Option 1: Mark up to Market. Rents will be adjusted annually using the Operating Cost Adjustment Factor (OCAF) described in the<E T="03">Section 8 Renewal Policy Guidebook.</E>An updated Rent Comparability Study (RCS) will be required every five (5) years. At the end of the 20-year term, subject to the availability of appropriations, HUD may renew the SPRAC for an additional 20-year term. Please note that though SPRACs will be administered under Section 8 guidance, this does not mean that SPRACs are a form of Section 8 rental assistance. SPRACs will be administered in accordance with the current Section 8 regulations until HUD publishes regulations to govern SPRACs in the near future.</P>
        <HD SOURCE="HD1">I. Available Funds</HD>
        <P>HUD is making $16 million in FY 2012 funds available to fund the initial year of SPRAC units for selected properties. HUD anticipates this could fund up to 2,000 unassisted units. Funding for future contract years are subject to appropriations. HUD may make new SPRAC contract awards in future funding rounds if and when appropriations are available for this purpose.</P>
        <HD SOURCE="HD2">Award Process</HD>
        <P>The proposal is to award SPRAC requests through an application process, open to those projects electing to prepay and refinance the Section 202 Direct Loan under the terms of AHEO and HUD guidance provided in Housing Notice 12-08 for Section 202 Direct Loan prepayment requirements.<SU>2</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>2</SU>See<E T="03">http://portal.hud.gov/hudportal/HUD?src=/program_offices/administration/hudclips/notices/hsg.</E>
          </P>
        </FTNT>
        <P>Section 202 projects that apply and meet eligibility criteria will be separated into two pools:</P>
        <P>(1) Pool One—those Owner-applicants that commit to use SPRAC assistance for existing low income and very low income tenants residing at the property at the time of the 202 Direct Loan prepayment, and for new very low income tenants (50 percent of AMI) upon unit turnover; and</P>
        <P>(2) Pool Two—those Owner-applicants that do not commit to use SPRAC assistance exclusively for low income and very low income tenants residing at the property at the time of the 202 Direct Loan prepayment, and for new very low income tenants (50 percent of AMI) upon unit turnover, but rather for tenants at or below 80 percent of AMI.</P>
        <P>All qualified Owner-applicants and the respective properties in both Pool One and Pool Two will be ranked by mortgage maturity date. Beginning with those in Pool One, SPRAC awards will be made based on the mortgage maturity date of each property. HUD will select the property with the earliest chronological maturity date first, the property with the second earliest maturity date second, and so forth, until funding is exhausted. If there are not enough qualified Owner-applicants in Pool One to exhaust available SPRAC funding, those qualified Owner-applicants in Pool Two will become eligible for SPRAC awards. The process for award will be identical to that for Pool Two and will be based on mortgage maturity date. Properties with mortgage maturity dates that predate the SPRAC application deadline will not be eligible for SPRAC awards.<SU>3</SU>
          <FTREF/>There is no maximum award ceiling per project.</P>
        <FTNT>
          <P>
            <SU>3</SU>Pursuant to AHEO, SPRAC awards must be linked to a qualifying mortgage prepayment, not a mortgage maturity. Therefore a property will not receive SPRAC if the mortgage matures before the Direct Loan prepayment is completed.</P>
        </FTNT>
        <P>HUD will not make partial awards. HUD will only select projects that can be fully funded with available SPRAC funds. For example, if the next eligible project on the list (ranked by mortgage maturity date) includes 100 unassisted income-eligible units, HUD will only select this project for funding if there are sufficient SPRAC resources to fund all 100 income-eligible units. If resources are not sufficient, HUD will select the next eligible project that can be fully funded or will close the award process until further notice. (Following public comment on this notice and incorporation of these comments, a SPRAC Housing Notice will establish minimum basic eligibility criteria for Owner-applicants to apply by a certain deadline, which will be provided in the final notice that follows and takes into consideration public comment on this notice.)</P>
        <HD SOURCE="HD2">Eligibility Criteria</HD>
        <P>Eligible Owner-applicants will own properties that meet the following criteria:</P>
        <P>1. Their property must be a Section 202 property with an original interest rate of six percent or less (funded prior to 1974) and with unassisted units.</P>
        <P>2. Their most recent Real Estate Assessment Center (REAC) score at the property must be 60 or above, and the property must have no open Exigent Health and Safety findings.</P>
        <P>3. Their most recent Management and Occupancy Review score at the property must be satisfactory or higher.</P>
        <P>4. Their property must have no open referrals to the Departmental Enforcement Center.</P>
        <P>5. The Owner-applicant must intend to refinance under the terms and conditions of AHEO, as amended, with no anticipated debt service savings from the refinance. A purchase/acquisition transaction is also eligible if the project will not experience debt service savings as a result of the transaction. (In the case of an acquisition, the current Owner must submit the SPRAC request but may provide evidence in the form of a purchase/sale agreement that the prepayment will include an acquisition.) The Owner-applicant must demonstrate that without SPRAC the rents for unassisted elderly tenants will be raised to compensate for the increased debt service costs resulting from prepayment at a higher interest rate. Rent increases will place unassisted elderly tenants at high risk of displacement.</P>
        <P>6. Their property vacancy rate must be seven percent or lower for the 24 month period prior to application or the Owner-applicant must intend to convert efficiency units to one-bedroom units in accordance with Housing Notice 2011-03.<SU>4</SU>
          <FTREF/>In order to convert efficiency units to one-bedroom units, the Owner-applicant must demonstrate an average vacancy rate in the efficiency units of at least 25 percent for at least 24 months or documentation must be shown that supports that the proposed conversion units are functionally obsolete.</P>
        <FTNT>
          <P>
            <SU>4</SU>See<E T="03">http://portal.hud.gov/hudportal/documents/huddoc?id=11-03hsgn.pdf.</E>
          </P>
        </FTNT>
        <P>7. Their property is proximate to the amenities and services needed by elderly residents.</P>
        <P>8. The Owner-applicant is not eligible to request assistance if such owner:</P>

        <P>i. Has been charged with a systemic violation of the Fair Housing Act or received a cause determination from a substantially equivalent state or local fair housing agency concerning a systemic violation of a substantially<PRTPAGE P="1227"/>equivalent state or local fair housing law proscribing discrimination because of race, color, religion, sex, national origin, disability or familial status;</P>
        <P>ii. Is a defendant in a Fair Housing Act lawsuit filed by the Department of Justice alleging a pattern or practice of discrimination or denial of rights to a group of persons raising an issue of general public interest pursuant to 42 U.S.C. 3614(a);</P>
        <P>iii. Has received a letter of findings identifying systemic noncompliance under Title VI of the Civil Rights Act of 1964, Section 504 of the Rehabilitation Act of 1973, or Section 109 of the Housing and Community Development Act of 1974;</P>
        <P>iv. Has received a cause determination from a substantially equivalent state or local fair housing agency concerning a systemic violation of provisions of a state or local law proscribing discrimination in housing based on sexual orientation or gender identity; or</P>
        <P>v. Has received a cause determination from a substantially equivalent state or local fair housing agency concerning a systemic violation of a state or local law proscribing discrimination in housing based on lawful source of income; and</P>
        <P>vi. If applicable, has not resolved to HUD's satisfaction, the charge, lawsuit, letter of findings or cause determination referenced in subparagraphs (i), (ii), (iii), (iv) or (v) and/or is not in current compliance with any agreement or consent order resolving the matter.</P>
        <HD SOURCE="HD2">Award Process</HD>
        <P>Funding for SPRAC awards is extremely limited and a significant number of equally worthy projects are expected to compete for SPRAC funding. To allocate these scarce resources effectively, HUD proposes to make SPRAC awards using an application process where applications are separated into two pools:</P>
        <P>(1) Pool One—those Owner-applicants that commit to use SPRAC assistance for existing low income and very low income tenants residing at the property at the time of the 202 Direct Loan prepayment, and for new very low income tenants (50 percent of Area Media Income) upon unit turnover; and</P>
        <P>(2) Pool Two—those Owner-applicants that do not commit to use SPRAC assistance exclusively for low income and very low income tenants residing at the property at the time of the 202 Direct Loan prepayment, and for new very low income tenants (50 percent of AMI) upon unit turnover, but rather for tenants at or below 80 percent of AMI.</P>
        <P>Both Pools will be ranked by mortgage maturity date, and beginning with Pool One, projects will be awarded SPRAC in chronological order until funding is exhausted. If funding is not exhausted from Pool One, awards will be made in chronological order of mortgage maturity date for Pool Two. HUD believes all pre-1974 Section 202 properties that meet the eligibility requirements are in need of preservation, and all unassisted residents of these properties are potentially vulnerable to rent increases or displacement. Elderly tenants of properties with imminent mortgage maturity dates are at greatest risk of displacement because those properties are closer to terminating their relationship with HUD. As the mortgage matures, the property is no longer obligated to operate as housing affordable to very low, low, and/or moderate-income elderly households.</P>
        <P>HUD's top priority is protecting very low income unassisted elderly tenants from displacement and providing assistance to this population in the future. Therefore, HUD will give priority to those qualified Owner-applicants that commit to target 100 percent of SPRAC assistance to very low-income and low income elderly residents residing in the project at the time of the Direct Loan prepayment, and exclusively to very low income tenants at unit turnover. These projects will go into Pool One for SPRAC awards. Households that currently reside in unassisted units at the Section 202 Direct Loan project, and that meet the low income eligibility criteria (at or below 80 percent of AMI) will be eligible to receive SPRAC assistance. However, upon unit turnover, the Owner-applicants will commit to make the vacant units available exclusively to very low income households.</P>

        <P>To determine very low income thresholds, the Owner-applicant should determine annual income by following the income verification process described in HUD Handbook 4350.3,<E T="03">Occupancy Requirements of Subsidized Multifamily Housing Programs.</E>
          <SU>5</SU>

          <FTREF/>The Owner-applicant must compare the household's annual income with HUD's current FY low income limits. For this comparison, Owner-applicants must know the size of the household (e.g., 1 person household). Owner-applicants may find HUD's low income limits by visiting<E T="03">http://www.huduser.org/portal/datasets/il/il12/index_il2012.html.</E>At this site, Owner-applicants click “Click Here for FY 2012 IL Documentation.” The Owner-applicant then selects the state and county in which the property is located, and clicks “Next Screen.” The relevant information is located in the row labeled “Very Low (50%) Income Limits.” If the household's annual income is greater than the very low-income limit found in this row, the household does not qualify as a very low income household for the purposes of SPRAC eligibility.</P>
        <FTNT>
          <P>
            <SU>5</SU>See<E T="03">http://portal.hud.gov/hudportal/HUD?src=/program_offices/administration/hudclips/handbooks/hsgh/4350.3.</E>
          </P>
        </FTNT>
        <P>Qualified Owner-applicants in Pool One will be ranked by project mortgage maturity date, and those projects will be funded based on chronological maturity date, with the earliest maturity date selected first, until all SPRAC funds are exhausted. Properties with mortgage maturity dates that predate the SPRAC application deadline will not be eligible for SPRAC awards. This approach allows HUD to target those properties with imminent maturing mortgages to meet the statutory intent to protect unassisted elderly residents from displacement.</P>
        <P>If two properties have the same mortgage maturity date, projects in low-vacancy areas<SU>6</SU>
          <FTREF/>will be given priority, because residents in these areas would have the most difficulty securing affordable housing if they did not have access to rental assistance. To determine if a project is in a low-vacancy area, please see Attachment 1. If none of the projects with the same mortgage maturity date are in a low-vacancy area, the project with the greatest number of unassisted units will be funded within the limitation of available funds, in order to reach the greatest number of impacted elderly residents.</P>
        <FTNT>
          <P>
            <SU>6</SU>“Low-vacancy area” was defined for the purposes of this assistance as a county that currently and historically demonstrates a moderate to tight rental housing market for low-income renters. HUD determined this definition with two thresholds. First, the county must be below the national vacancy rate for units affordable to low-income household in 2000, which is 7.3 percent. Second, the county must be below the 80th percentile vacancy rate for low-income renters as estimated by the 2005-2009 American Community Survey 5 year estimates, which is 8.7 percent. A list of low-vacancy areas is included in Attachment 1.</P>
        </FTNT>

        <P>If there are not enough qualified Owner-applicants in Pool One to utilize all available SPRAC funding, qualified Owner-applicants that meet the threshold criteria but do not commit to use SPRAC assistance for existing low income and very low income tenants residing at the property at the time of the 202 Direct Loan prepayment, and for new very low income tenants (50 percent of AMI) upon unit turnover, but rather tenants at or below 80 percent of AMI (Pool Two) will become eligible. The award process for Pool Two Owner-<PRTPAGE P="1228"/>applicants will be identical to that for Pool One.</P>
        <P>Properties selected via the outlined application process will receive a preliminary notification of SPRAC award. Final SPRAC awards will be contingent on the property successfully receiving HUD approval to prepay the Section 202 Direct Loan under the requirements of AHEO and any standing or subsequent HUD guidance related to Section 202 Direct Loan prepayments.</P>
        <P>HUD is proposing a six-stage process for the award of SPRACs:</P>

        <P>(1) Submission by the Owner-applicant of an Expression of Interest Letter (<E T="03">an Expression of Interest is not being solicited at this time</E>);</P>
        <P>(2) Separation of qualified Owner-Applicants into Pool One and Pool Two based on Owner-applicant commitment to target very low income elderly residents;</P>
        <P>(3) Ranking of Applications by Mortgage Maturity Date;</P>
        <P>(4) Notification to Proceed;</P>
        <P>(5) Completion of Prepayment Request and Approval; and</P>
        <P>(6) Fund Reservation and Obligation.</P>
        <HD SOURCE="HD3">Stage 1: Owner Submits an Expression of Interest Letter</HD>
        <P>An Owner-applicant must first determine that the 202 Direct Loan property meets the above basic eligibility criteria for SPRAC award. An interested and eligible Owner-applicant will then submit an Expression of Interest Letter for SPRAC award to HUD. HUD proposes the following information should be included in or with the Expression of Interest Letter:</P>
        <P>1. Project name and FHA number.</P>
        <P>2. Statement that the Owner-applicant plans to refinance and does not anticipate debt service savings from the refinance, and must plan repairs that rise to the level of substantial rehabilitation.</P>
        <P>3. Statement that the Owner-applicant will commit to target SPRAC assistance exclusively for existing low income and very low income tenants residing at the property at the time of the 202 Direct Loan prepayment, and for new very low income tenants (50 percent of Area Media Income) upon unit turnover (if applicable).</P>
        <P>4. Rent rolls from the 3 months preceding the Letter of Intent, verifying that the property has a vacancy rate of seven percent or lower.</P>
        
        <FP>or</FP>
        
        <P>The Owner-applicant must include a statement of intent to convert efficiency units to one-bedroom units in accordance with Housing Notice 2011-03. In order to convert efficiency units to one-bedroom units, the property rent roll must demonstrate that average vacancy rate in the efficiency units is at least 25 percent for at least 24 months or the Owner-applicant must provide a letter from a licensed appraiser or a licensed architect indicating that the efficiency units proposed for conversion are functionally obsolete.</P>

        <P>5. Rent Comparability Study (RCS), commissioned by the Owner, to estimate the approximate amount of SPRAC funding needed to provide assistance at market rent levels for the unassisted units. The RCS must be completed in accordance with Chapter 9 of the<E T="03">Section 8 Renewal Policy Guidebook</E>(<E T="03">http://portal.hud.gov/hudportal/documents/huddoc?id=DOC_14528.pdf</E>). If the property has a Section 8 HAP contract and the Owner has commissioned an RCS within the last five years, the RCS may be used per the guidelines of Chapter 9 of the<E T="03">Section 8 Renewal Policy Guidebook.</E>HUD will use the RCS to approximate the SPRAC contract rents based on comparable market rents.<SU>7</SU>
          <FTREF/>
        </P>
        <FTNT>
          <P>
            <SU>7</SU>At this stage, HUD will use the RCS to forecast the potential SPRAC rent levels and cost of providing assistance to the unassisted units at the property. The RCS will not be interpreted as the final rent or assistance level, which will be determined at a later stage of the process. The Owner is not required to provide an assessment or calculation of assistance at this stage.</P>
        </FTNT>
        <P>6. The Owner-Applicant must submit one of the following to demonstrate the property is proximate to amenities and services needed by the elderly residents:</P>
        <P>A. Submit a letter, signed by the Housing, Planning, or Community Development office of the local municipality verifying that:</P>
        <P>(i) This Section 202 property is proximate to social, recreational, educational, commercial, and health facilities and services, and other municipal facilities and services; or</P>
        <P>(ii) If the Section 202 property is not currently proximate to social, recreational, educational, commercial, and health facilities or services, the preservation of this Section 202 property is an integral part of a concerted community revitalization plan.</P>
        
        <FP>or</FP>
        

        <P>B. Provide a certification from the Designated Point of Contact for the designated Preferred Sustainability Status Community where the property is located, using form HUD2995. A list of Preferred Sustainability Status Communities and the corresponding points of contact can be found here:<E T="03">http://portal.hud.gov/hudportal/HUD?src=/program_offices/administration/grants/nofa11/psscontacts.</E>The form will certify the nexus between the proposed preservation of the Section 202 property by the owner applicant and the Livability Principles as they are being advanced in the Preferred Sustainability Status Community. This certification must be signed and dated anytime from the date of the publication of the SPRAC Final Notice to the deadline date of the SPRAC funding opportunity. Any certifications signed before or after those dates will not be acceptable.</P>
        <P>8. Statement certifying that the Owner-applicant is in compliance with the civil rights threshold requirements set forth under “Eligibility Criteria” in this Notice.</P>
        <NOTE>
          <HD SOURCE="HED">Note:</HD>
          <P>HUD will remove the application from the pool and notify those Owner-applicants who do not meet the qualifications for a SPRAC award.</P>
        </NOTE>
        <HD SOURCE="HD3">Stage 2: Separation of Applications by Very low Income Targeting into Pool One and Pool Two</HD>
        <P>Those qualified Owner-Applicants that include a statement of commitment to use SPRAC assistance for existing low income and very low income tenants residing at the property at the time of the 202 Direct Loan prepayment, and for new very low income tenants (50 percent of AMI) upon unit turnover will be placed in Pool One and those qualified Owner-applicants that do not include a statement of commitment will be placed in Pool Two. Once all qualified Owner-applicants in Pool One have received SPRAC assistance, awards will begin for Pool Two.</P>
        <HD SOURCE="HD3">Stage 3: Ranking of Applications by Mortgage Maturity Date</HD>
        <P>Upon the submission deadline for the Expression of Interest Letter and the separation of qualified Owner-applicants into Pool One and Pool Two, HUD will rank the qualified Owner-applicants and corresponding projects by mortgage maturity date. If two or more qualified applicants have the same mortgage maturity date, the project(s) in low-vacancy areas listed in the appendix to this Notice will be given priority. If none of the projects with the same mortgage maturity date are in low-vacancy areas, the project with the most unassisted units will be selected within limitations of funding.</P>

        <P>Beginning with Pool One, HUD will allocate SPRAC funding in chronological order of mortgage maturity date, using the RCS, the number of unassisted units, and contract cost information in comparable properties to estimate needed funding,<PRTPAGE P="1229"/>until all SPRAC funds are exhausted. HUD will not make partial awards. HUD will only select projects that can be fully funded with available SPRAC funds. For example, if the next project on the list includes 100 unassisted units HUD will only select this project for funding if there are sufficient SPRAC resources to fund all 100 units under the contract. If resources are not sufficient, HUD will select the next eligible project that can be fully funded or will close the award process until further notice.</P>
        <P>Once all qualified Owner-applicants in Pool One have been funded, HUD will award SPRAC to those qualified Owner-applicants in Pool Two chronologically by mortgage maturity date. Awards made to Pool Two Owner-applicants will follow the same procedures outlined above for Pool One.</P>
        <HD SOURCE="HD3">Stage 4: Notification to Proceed</HD>
        <P>Upon selection, the Owner-applicant will receive a Notification to Proceed letter confirming the project was selected to receive a SPRAC award. This Notification will specify that SPRAC assistance will only be provided for unassisted units occupied by income-eligible residents (at or below 80 percent of AMI) at the time of execution of the SPRAC. The Notification to Proceed letter will not guarantee funding, as the Owner-applicant will need to meet all criteria and complete the Section 202 prepayment process successfully before receiving funds. The Notification to Proceed letter will include an estimated dollar amount for potential SPRAC assistance, determined by the required RCS submitted by the Owner-applicant. This amount is subject to change based on the determination of the number of income-eligible unassisted units at the property and market comparable rents using the RCS. The Owner-applicant will be required to verify tenant incomes to determine the number of income-eligible households (at 80 percent AMI or below) residing in unassisted units at the time the SPRAC is executed.</P>

        <P>The Notification to Proceed letter will be conditioned on HUD approval of a prepayment request and the closing of the proposed refinance. The Owner-applicant must submit a<E T="03">complete</E>prepayment request to the Multifamily Hub/PC office within 60 days of the date of receipt of the Notification to Proceed letter. The prepayment request must include all information required by Housing Notice 12-08. Failure to submit the prepayment request within 60 days of the date of receipt of the Notification to Proceed letter will nullify the Notification to Proceed and the Owner-applicant's eligibility for SPRAC for this round of funding. The Notification to Proceed letter will be valid for no more than 180 days (six months). During this 180 day period, the Owner-applicant will finalize and submit the prepayment request and secure the refinance loan. If the prepayment approval is not granted in that time, and/or if the Owner-applicant does not close the refinancing in this time period, the project's selection in the lottery will be cancelled and the corresponding funds released.</P>
        <P>If the Owner-applicant is planning to use FHA financing, HUD will extend the Notification to Proceed to accommodate the timeline for FHA application reviews, provided that the Owner-applicant submits evidence of submission of an FHA insured loan application. HUD may also consider extending the Notification to Proceed if the Owner-applicants pursues Low Income Housing Tax Credits (LIHTCs), either in the form of 9 percent or 4 percent LIHTCs. The Owner-applicant must submit evidence of tax credit application in order to receive an extension. If the project is selected and issued a Notification to Proceed and the Owner-applicant proposes to use 9 percent tax credits, the Owner-Applicant will have one opportunity to apply for the 9 percent tax credits in the next scheduled application round administered by the state or local issuing agency. If 9 percent tax credits cannot be secured during that first application cycle, the Notification to Proceed will be cancelled unless the Owner can demonstrate feasibility to meet Section 202 prepayment requirements without tax credits.</P>
        <HD SOURCE="HD3">Stage 5: Prepayment Request and Approval</HD>
        <P>
          <E T="03">1. Submission of Prepayment request to Hub/PC within 60 days of receipt of the Notification to Proceed letter.</E>The Owner-applicant will submit a Section 202 Direct Loan prepayment request to the Hub/PC. The Hub/PC will screen, review and process the application to ensure it meets the requirements of Housing Notice 12-08 and any subsequent guidance on Section 202 Direct Loan prepayments.<SU>8</SU>

          <FTREF/>The review will ensure compliance with all applicable statutes, regulations and policies. The review will include an environmental review by HUD Multifamily Development staff pursuant to the requirements at 24 CFR Part 50. Guidance for completion of this review may be found in Chapter 9 of the<E T="03">Multifamily Accelerated Processing</E>(MAP) Guide. The review will include an assessment to verify the proposed repairs rise to the level of substantial rehabilitation and the proposed refinance will result in an increase in debt service, placing unassisted elderly residents at risk of increased rents and concomitantly displacement. If there is no anticipated increase in debt service, the project will not be eligible for SPRAC and the Notification to Proceed will be revoked. The Hub/PC Director will forward recommendations for Direct Loan prepayment approval to HUD Headquarters Office of Asset Management. Upon receipt of the Hub/PC recommendation, the Office of Asset Management will review the prepayment request and, within 30 days of the date of receipt of the Hub/PC recommendation, will make a determination of prepayment approval and notify the Hub/PC and the Owner-applicant.</P>
        <FTNT>
          <P>
            <SU>8</SU>
            <E T="04">Note:</E>HUD intends to issue an update to Housing Notice 12-08 in the near future to clarify prepayment processing and requirements, including environmental review requirements.</P>
        </FTNT>
        <P>
          <E T="03">2. Rent Comparability Study and Contract Request.</E>
          <SU>9</SU>

          <FTREF/>After receiving the Notification to Proceed letter, and while the prepayment application is completed, the Owner-applicant will be required to submit a copy of the Rent Comparability Study submitted with their Letter of Intent, that meets the requirements of the<E T="03">Section 8 Renewal Policy Guidebook.</E>The Owner-applicant should also submit income verification information and a Contract Renewal Request Form (HUD Form 9264)<SU>10</SU>
          <FTREF/>requesting a 20-year contract under Option 1: Mark up to Market. The Hub/PC will determine the rents for the project for the units occupied by income-eligible residents (those at or below 80 percent of AMI), and prepare the SPRAC for execution.</P>
        <FTNT>
          <P>
            <SU>9</SU>The SPRAC Notification to Proceed will provide the maximum number of units that may be assisted under the SPRAC. The lender should be advised of the possibility that the number of SPRAC-assisted units on the contract could decrease if residents are found to be over-income. The lender would rely on the RCS for “market” rents on which to underwrite the loan.</P>
        </FTNT>
        <FTNT>
          <P>
            <SU>10</SU>(<E T="03">http://portal.hud.gov/hudportal/documents/huddoc?id=DOC_14523.pdf</E>)</P>
        </FTNT>
        <HD SOURCE="HD3">Stage 6: Fund Reservation and Obligation</HD>
        <P>Upon approval of the prepayment request by HUD headquarters Office of Asset Management, HUD will issue an official fund reservation for the final SPRAC funding amount for that project. Once the fund reservation is complete, HUD will execute the SPRAC.</P>

        <P>On the date of closing, the owner will execute the required Use Agreement and other loan documents as well as the SPRAC. Upon closing, HUD will obligate the SPRAC funds. Following<PRTPAGE P="1230"/>the closing, the SPRAC will be administered under the rules and terms of the<E T="03">Section 8 Renewal Policy Guidebook</E>by the PBCA and the HUD field office staff.</P>
        <HD SOURCE="HD2">Environmental Impact</HD>
        <P>An Environmental Assessment (EA) and Finding of No Significant Impact (FONSI) with respect to the environment has been made for this Advance Notice in accordance with HUD regulations at 24 CFR part 50 that implement section 102(2)(C) of the National Environmental Policy Act of 1969 (42 U.S.C. 4332(2)(C)). The EA and FONSI is available for public inspection between 8 a.m. and 5 p.m. weekdays in the Regulations Division, Office of General Counsel, Department of Housing and Urban Development, 451 Seventh Street SW., Room 10276, Washington DC 20410-0500. Due to security measures at this HUD Headquarters Building, an advance appointment to review the EA and FONSI must be scheduled by calling the Regulations Division at 202-708-3055 (not a toll free number).</P>
        <SIG>
          <DATED>Dated: January 2, 2013.</DATED>
          <NAME>Carol J. Galante,</NAME>
          <TITLE>Acting Assistant Secretary for Housing-Federal Housing Commissioner.</TITLE>
        </SIG>
        <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        <GPH DEEP="629" SPAN="3">
          <PRTPAGE P="1231"/>
          <GID>EN08JA13.000</GID>
        </GPH>
        <BILCOD>BILLING CODE 4210-67-C</BILCOD>
        <PRTPAGE P="1232"/>
        <GPOTABLE CDEF="xs60,r50,14,14" COLS="4" OPTS="L2,i1">
          <TTITLE>Attachment 1—Low Vacancy Areas</TTITLE>
          <BOXHD>
            <CHED H="1">County FIPS code</CHED>
            <CHED H="1">County name</CHED>
            <CHED H="1">Vacancy Rate for Units Affordable to 80% of AMI</CHED>
            <CHED H="2">2009 ACS 5 Year average<LI>(percent)</LI>
            </CHED>
            <CHED H="2">2000 Census<LI>(percent)</LI>
            </CHED>
          </BOXHD>
          <ROW>
            <ENT I="01">01007</ENT>
            <ENT>Bibb County; Birmingham-Hoover, AL Metro Area; Alabama</ENT>
            <ENT>0.6</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">01063</ENT>
            <ENT>Greene County; Tuscaloosa, AL Metro Area; Alabama</ENT>
            <ENT>0.4</ENT>
            <ENT>3.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">01065</ENT>
            <ENT>Hale County; Tuscaloosa, AL Metro Area; Alabama</ENT>
            <ENT>0.9</ENT>
            <ENT>2.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">01085</ENT>
            <ENT>Lowndes County; Montgomery, AL Metro Area; Alabama</ENT>
            <ENT>3.9</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">01091</ENT>
            <ENT>Marengo County, Alabama</ENT>
            <ENT>3.3</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">01107</ENT>
            <ENT>Pickens County, Alabama</ENT>
            <ENT>5.7</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">01131</ENT>
            <ENT>Wilcox County, Alabama</ENT>
            <ENT>3.6</ENT>
            <ENT>5.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">02020</ENT>
            <ENT>Anchorage Municipality; Anchorage, AK Metro Area; Alaska</ENT>
            <ENT>4.8</ENT>
            <ENT>5.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">02050</ENT>
            <ENT>Bethel Census Area, Alaska</ENT>
            <ENT>2.6</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">02110</ENT>
            <ENT>Juneau City and Borough; Juneau, AK Micro Area; Alaska</ENT>
            <ENT>1.8</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">02188</ENT>
            <ENT>Northwest Arctic Borough, Alaska</ENT>
            <ENT>2.6</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">02195</ENT>
            <ENT>Petersburg Census Area, Alaska</ENT>
            <ENT>6.8</ENT>
            <ENT>N/A</ENT>
          </ROW>
          <ROW>
            <ENT I="01">02220</ENT>
            <ENT>Sitka City and Borough, Alaska</ENT>
            <ENT>1.3</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">02270</ENT>
            <ENT>Wade Hampton Census Area, Alaska</ENT>
            <ENT>1.0</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">04005</ENT>
            <ENT>Coconino County; Flagstaff, AZ Metro Area; Arizona</ENT>
            <ENT>6.8</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">05041</ENT>
            <ENT>Desha County, Arkansas</ENT>
            <ENT>6.2</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">05057</ENT>
            <ENT>Hempstead County; Hope, AR Micro Area; Arkansas</ENT>
            <ENT>3.2</ENT>
            <ENT>5.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">05079</ENT>
            <ENT>Lincoln County; Pine Bluff, AR Metro Area; Arkansas</ENT>
            <ENT>6.8</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">05085</ENT>
            <ENT>Lonoke County; Little Rock-North Little Rock-Conway, AR Metro Area; Arkansas</ENT>
            <ENT>3.0</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">05099</ENT>
            <ENT>Nevada County; Hope, AR Micro Area; Arkansas</ENT>
            <ENT>2.4</ENT>
            <ENT>4.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06001</ENT>
            <ENT>Alameda County; San Francisco-Oakland-Fremont, CA Metro Area; California</ENT>
            <ENT>6.7</ENT>
            <ENT>2.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06007</ENT>
            <ENT>Butte County; Chico, CA Metro Area; California</ENT>
            <ENT>4.7</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06009</ENT>
            <ENT>Calaveras County, California</ENT>
            <ENT>6.2</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06011</ENT>
            <ENT>Colusa County, California</ENT>
            <ENT>2.8</ENT>
            <ENT>2.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06013</ENT>
            <ENT>Contra Costa County; San Francisco-Oakland-Fremont, CA Metro Area; California</ENT>
            <ENT>7.6</ENT>
            <ENT>3.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06019</ENT>
            <ENT>Fresno County; Fresno, CA Metro Area; California</ENT>
            <ENT>4.9</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06023</ENT>
            <ENT>Humboldt County; Eureka-Arcata-Fortuna, CA Micro Area; California</ENT>
            <ENT>6.3</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06025</ENT>
            <ENT>Imperial County; El Centro, CA Metro Area; California</ENT>
            <ENT>5.6</ENT>
            <ENT>5.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06027</ENT>
            <ENT>Inyo County; Bishop, CA Micro Area; California</ENT>
            <ENT>3.4</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06031</ENT>
            <ENT>Kings County; Hanford-Corcoran, CA Metro Area; California</ENT>
            <ENT>3.7</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06037</ENT>
            <ENT>Los Angeles County; Los Angeles-Long Beach-Santa Ana, CA Metro Area; California</ENT>
            <ENT>2.4</ENT>
            <ENT>4.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06039</ENT>
            <ENT>Madera County; Madera-Chowchilla, CA Metro Area; California</ENT>
            <ENT>3.8</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06041</ENT>
            <ENT>Marin County; San Francisco-Oakland-Fremont, CA Metro Area; California</ENT>
            <ENT>2.6</ENT>
            <ENT>1.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06045</ENT>
            <ENT>Mendocino County; Ukiah, CA Micro Area; California</ENT>
            <ENT>5.0</ENT>
            <ENT>3.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06047</ENT>
            <ENT>Merced County; Merced, CA Metro Area; California</ENT>
            <ENT>6.3</ENT>
            <ENT>4.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06053</ENT>
            <ENT>Monterey County; Salinas, CA Metro Area; California</ENT>
            <ENT>5.7</ENT>
            <ENT>2.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06055</ENT>
            <ENT>Napa County; Napa, CA Metro Area; California</ENT>
            <ENT>5.1</ENT>
            <ENT>2.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06057</ENT>
            <ENT>Nevada County; Truckee-Grass Valley, CA Micro Area; California</ENT>
            <ENT>6.7</ENT>
            <ENT>3.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06059</ENT>
            <ENT>Orange County; Los Angeles-Long Beach-Santa Ana, CA Metro Area; California</ENT>
            <ENT>2.7</ENT>
            <ENT>2.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06061</ENT>
            <ENT>Placer County; Sacramento—Arden-Arcade—Roseville, CA Metro Area; California</ENT>
            <ENT>7.5</ENT>
            <ENT>4.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06067</ENT>
            <ENT>Sacramento County; Sacramento—Arden-Arcade—Roseville, CA Metro Area; California</ENT>
            <ENT>7.6</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06069</ENT>
            <ENT>San Benito County; San Jose-Sunnyvale-Santa Clara, CA Metro Area; California</ENT>
            <ENT>3.4</ENT>
            <ENT>2.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06073</ENT>
            <ENT>San Diego County; San Diego-Carlsbad-San Marcos, CA Metro Area; California</ENT>
            <ENT>4.7</ENT>
            <ENT>3.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06075</ENT>
            <ENT>San Francisco County; San Francisco-Oakland-Fremont, CA Metro Area; California</ENT>
            <ENT>4.2</ENT>
            <ENT>2.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06077</ENT>
            <ENT>San Joaquin County; Stockton, CA Metro Area; California</ENT>
            <ENT>6.3</ENT>
            <ENT>4.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06079</ENT>
            <ENT>San Luis Obispo County; San Luis Obispo-Paso Robles, CA Metro Area; California</ENT>
            <ENT>3.4</ENT>
            <ENT>3.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06081</ENT>
            <ENT>San Mateo County; San Francisco-Oakland-Fremont, CA Metro Area; California</ENT>
            <ENT>4.0</ENT>
            <ENT>1.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06083</ENT>
            <ENT>Santa Barbara County; Santa Barbara-Santa Maria-Goleta, CA Metro Area; California</ENT>
            <ENT>3.7</ENT>
            <ENT>2.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06085</ENT>
            <ENT>Santa Clara County; San Jose-Sunnyvale-Santa Clara, CA Metro Area; California</ENT>
            <ENT>3.3</ENT>
            <ENT>1.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06087</ENT>
            <ENT>Santa Cruz County; Santa Cruz-Watsonville, CA Metro Area; California</ENT>
            <ENT>3.4</ENT>
            <ENT>2.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06089</ENT>
            <ENT>Shasta County; Redding, CA Metro Area; California</ENT>
            <ENT>6.5</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06091</ENT>
            <ENT>Sierra County, California</ENT>
            <ENT>1.4</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06095</ENT>
            <ENT>Solano County; Vallejo-Fairfield, CA Metro Area; California</ENT>
            <ENT>7.1</ENT>
            <ENT>4.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06097</ENT>
            <ENT>Sonoma County; Santa Rosa-Petaluma, CA Metro Area; California</ENT>
            <ENT>5.3</ENT>
            <ENT>1.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06099</ENT>
            <ENT>Stanislaus County; Modesto, CA Metro Area; California</ENT>
            <ENT>6.6</ENT>
            <ENT>4.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06101</ENT>
            <ENT>Sutter County; Yuba City, CA Metro Area; California</ENT>
            <ENT>7.1</ENT>
            <ENT>5.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06107</ENT>
            <ENT>Tulare County; Visalia-Porterville, CA Metro Area; California</ENT>
            <ENT>3.3</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06109</ENT>
            <ENT>Tuolumne County; Phoenix Lake-Cedar Ridge, CA Micro Area; California</ENT>
            <ENT>5.5</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06111</ENT>
            <ENT>Ventura County; Oxnard-Thousand Oaks-Ventura, CA Metro Area; California</ENT>
            <ENT>3.2</ENT>
            <ENT>2.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">06113</ENT>
            <ENT>Yolo County; Sacramento—Arden-Arcade—Roseville, CA Metro Area; California</ENT>
            <ENT>3.9</ENT>
            <ENT>3.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">08005</ENT>
            <ENT>Arapahoe County; Denver-Aurora-Broomfield, CO Metro Area; Colorado</ENT>
            <ENT>8.5</ENT>
            <ENT>4.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">08013</ENT>
            <ENT>Boulder County; Boulder, CO Metro Area; Colorado</ENT>
            <ENT>4.8</ENT>
            <ENT>3.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">08014</ENT>
            <ENT>Broomfield County; Denver-Aurora-Broomfield, CO Metro Area; Colorado</ENT>
            <ENT>6.5</ENT>
            <ENT>N/A</ENT>
          </ROW>
          <ROW>
            <ENT I="01">08021</ENT>
            <ENT>Conejos County, Colorado</ENT>
            <ENT>7.5</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">08045</ENT>
            <ENT>Garfield County, Colorado</ENT>
            <ENT>2.6</ENT>
            <ENT>3.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">08059</ENT>
            <ENT>Jefferson County; Denver-Aurora-Broomfield, CO Metro Area; Colorado</ENT>
            <ENT>5.6</ENT>
            <ENT>4.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">08069</ENT>
            <ENT>Larimer County; Fort Collins-Loveland, CO Metro Area; Colorado</ENT>
            <ENT>5.3</ENT>
            <ENT>4.3</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="1233"/>
            <ENT I="01">08071</ENT>
            <ENT>Las Animas County, Colorado</ENT>
            <ENT>8.3</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">08077</ENT>
            <ENT>Mesa County; Grand Junction, CO Metro Area; Colorado</ENT>
            <ENT>2.7</ENT>
            <ENT>6.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">08079</ENT>
            <ENT>Mineral County, Colorado</ENT>
            <ENT>N/A</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">08087</ENT>
            <ENT>Morgan County; Fort Morgan, CO Micro Area; Colorado</ENT>
            <ENT>8.4</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">08097</ENT>
            <ENT>Pitkin County, Colorado</ENT>
            <ENT>4.7</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">09001</ENT>
            <ENT>Fairfield County; Bridgeport-Stamford-Norwalk, CT Metro Area; Connecticut</ENT>
            <ENT>7.5</ENT>
            <ENT>4.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">09003</ENT>
            <ENT>Hartford County; Hartford-West Hartford-East Hartford, CT Metro Area; Connecticut</ENT>
            <ENT>7.5</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">09005</ENT>
            <ENT>Litchfield County; Torrington, CT Micro Area; Connecticut</ENT>
            <ENT>7.5</ENT>
            <ENT>4.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">09007</ENT>
            <ENT>Middlesex County; Hartford-West Hartford-East Hartford, CT Metro Area; Connecticut</ENT>
            <ENT>5.9</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">09009</ENT>
            <ENT>New Haven County; New Haven-Milford, CT Metro Area; Connecticut</ENT>
            <ENT>7.3</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">09011</ENT>
            <ENT>New London County; Norwich-New London, CT Metro Area; Connecticut</ENT>
            <ENT>5.6</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">09013</ENT>
            <ENT>Tolland County; Hartford-West Hartford-East Hartford, CT Metro Area; Connecticut</ENT>
            <ENT>6.2</ENT>
            <ENT>3.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">09015</ENT>
            <ENT>Windham County; Willimantic, CT Micro Area; Connecticut</ENT>
            <ENT>4.3</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">11001</ENT>
            <ENT>District of Columbia; Washington-Arlington-Alexandria, DC-VA-MD-WV Metro Area; District of Columbia</ENT>
            <ENT>5.8</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">12003</ENT>
            <ENT>Baker County; Jacksonville, FL Metro Area; Florida</ENT>
            <ENT>1.5</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">12086</ENT>
            <ENT>Miami-Dade County; Miami-Fort Lauderdale-Pompano Beach, FL Metro Area; Florida</ENT>
            <ENT>7.8</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13007</ENT>
            <ENT>Baker County; Albany, GA Metro Area; Georgia</ENT>
            <ENT>7.2</ENT>
            <ENT>1.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13013</ENT>
            <ENT>Barrow County; Atlanta-Sandy Springs-Marietta, GA Metro Area; Georgia</ENT>
            <ENT>8.6</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13035</ENT>
            <ENT>Butts County; Atlanta-Sandy Springs-Marietta, GA Metro Area; Georgia</ENT>
            <ENT>4.0</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13043</ENT>
            <ENT>Candler County, Georgia</ENT>
            <ENT>2.6</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13079</ENT>
            <ENT>Crawford County; Macon, GA Metro Area; Georgia</ENT>
            <ENT>7.0</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13083</ENT>
            <ENT>Dade County; Chattanooga, TN-GA Metro Area; Georgia</ENT>
            <ENT>8.6</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13085</ENT>
            <ENT>Dawson County; Atlanta-Sandy Springs-Marietta, GA Metro Area; Georgia</ENT>
            <ENT>3.5</ENT>
            <ENT>3.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13105</ENT>
            <ENT>Elbert County, Georgia</ENT>
            <ENT>7.5</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13117</ENT>
            <ENT>Forsyth County; Atlanta-Sandy Springs-Marietta, GA Metro Area; Georgia</ENT>
            <ENT>6.5</ENT>
            <ENT>4.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13129</ENT>
            <ENT>Gordon County; Calhoun, GA Micro Area; Georgia</ENT>
            <ENT>8.4</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13133</ENT>
            <ENT>Greene County, Georgia</ENT>
            <ENT>7.3</ENT>
            <ENT>3.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13139</ENT>
            <ENT>Hall County; Gainesville, GA Metro Area; Georgia</ENT>
            <ENT>7.3</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13159</ENT>
            <ENT>Jasper County; Atlanta-Sandy Springs-Marietta, GA Metro Area; Georgia</ENT>
            <ENT>3.7</ENT>
            <ENT>3.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13171</ENT>
            <ENT>Lamar County; Atlanta-Sandy Springs-Marietta, GA Metro Area; Georgia</ENT>
            <ENT>4.6</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13181</ENT>
            <ENT>Lincoln County, Georgia</ENT>
            <ENT>2.2</ENT>
            <ENT>4.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13197</ENT>
            <ENT>Marion County; Columbus, GA-AL Metro Area; Georgia</ENT>
            <ENT>8.3</ENT>
            <ENT>3.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13199</ENT>
            <ENT>Meriwether County; Atlanta-Sandy Springs-Marietta, GA Metro Area; Georgia</ENT>
            <ENT>4.9</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13205</ENT>
            <ENT>Mitchell County, Georgia</ENT>
            <ENT>2.2</ENT>
            <ENT>3.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13211</ENT>
            <ENT>Morgan County, Georgia</ENT>
            <ENT>3.1</ENT>
            <ENT>3.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13217</ENT>
            <ENT>Newton County; Atlanta-Sandy Springs-Marietta, GA Metro Area; Georgia</ENT>
            <ENT>7.7</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13231</ENT>
            <ENT>Pike County; Atlanta-Sandy Springs-Marietta, GA Metro Area; Georgia</ENT>
            <ENT>8.1</ENT>
            <ENT>4.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13237</ENT>
            <ENT>Putnam County, Georgia</ENT>
            <ENT>1.0</ENT>
            <ENT>4.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13249</ENT>
            <ENT>Schley County; Americus, GA Micro Area; Georgia</ENT>
            <ENT>3.2</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13293</ENT>
            <ENT>Upson County; Thomaston, GA Micro Area; Georgia</ENT>
            <ENT>2.7</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13297</ENT>
            <ENT>Walton County; Atlanta-Sandy Springs-Marietta, GA Metro Area; Georgia</ENT>
            <ENT>4.0</ENT>
            <ENT>5.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13301</ENT>
            <ENT>Warren County, Georgia</ENT>
            <ENT>1.2</ENT>
            <ENT>4.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">13307</ENT>
            <ENT>Webster County, Georgia</ENT>
            <ENT>N/A</ENT>
            <ENT>N/A</ENT>
          </ROW>
          <ROW>
            <ENT I="01">15005</ENT>
            <ENT>Kalawao County, Hawaii</ENT>
            <ENT>N/A</ENT>
            <ENT>N/A</ENT>
          </ROW>
          <ROW>
            <ENT I="01">16001</ENT>
            <ENT>Ada County; Boise City-Nampa, ID Metro Area; Idaho</ENT>
            <ENT>6.6</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">16017</ENT>
            <ENT>Bonner County, Idaho</ENT>
            <ENT>5.0</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">16027</ENT>
            <ENT>Canyon County; Boise City-Nampa, ID Metro Area; Idaho</ENT>
            <ENT>7.8</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">16041</ENT>
            <ENT>Franklin County; Logan, UT-ID Metro Area; Idaho</ENT>
            <ENT>1.1</ENT>
            <ENT>3.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">16045</ENT>
            <ENT>Gem County; Boise City-Nampa, ID Metro Area; Idaho</ENT>
            <ENT>N/A</ENT>
            <ENT>6.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">16047</ENT>
            <ENT>Gooding County, Idaho</ENT>
            <ENT>4.7</ENT>
            <ENT>4.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">16053</ENT>
            <ENT>Jerome County; Twin Falls, ID Micro Area; Idaho</ENT>
            <ENT>4.1</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">16057</ENT>
            <ENT>Latah County; Moscow, ID Micro Area; Idaho</ENT>
            <ENT>5.8</ENT>
            <ENT>5.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">16065</ENT>
            <ENT>Madison County; Rexburg, ID Micro Area; Idaho</ENT>
            <ENT>3.0</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">16069</ENT>
            <ENT>Nez Perce County; Lewiston, ID-WA Metro Area; Idaho</ENT>
            <ENT>3.3</ENT>
            <ENT>4.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">16071</ENT>
            <ENT>Oneida County, Idaho</ENT>
            <ENT>5.3</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">16077</ENT>
            <ENT>Power County; Pocatello, ID Metro Area; Idaho</ENT>
            <ENT>3.8</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">16087</ENT>
            <ENT>Washington County, Idaho</ENT>
            <ENT>3.8</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17007</ENT>
            <ENT>Boone County; Rockford, IL Metro Area; Illinois</ENT>
            <ENT>6.8</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17009</ENT>
            <ENT>Brown County, Illinois</ENT>
            <ENT>2.4</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17013</ENT>
            <ENT>Calhoun County; St. Louis, MO-IL Metro Area; Illinois</ENT>
            <ENT>4.1</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17019</ENT>
            <ENT>Champaign County; Champaign-Urbana, IL Metro Area; Illinois</ENT>
            <ENT>8.5</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17027</ENT>
            <ENT>Clinton County; St. Louis, MO-IL Metro Area; Illinois</ENT>
            <ENT>3.5</ENT>
            <ENT>4.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17031</ENT>
            <ENT>Cook County; Chicago-Naperville-Joliet, IL-IN-WI Metro Area; Illinois</ENT>
            <ENT>8.0</ENT>
            <ENT>6.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17037</ENT>
            <ENT>DeKalb County; Chicago-Naperville-Joliet, IL-IN-WI Metro Area; Illinois</ENT>
            <ENT>4.5</ENT>
            <ENT>3.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17043</ENT>
            <ENT>DuPage County; Chicago-Naperville-Joliet, IL-IN-WI Metro Area; Illinois</ENT>
            <ENT>8.3</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17053</ENT>
            <ENT>Ford County; Champaign-Urbana, IL Metro Area; Illinois</ENT>
            <ENT>2.5</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17055</ENT>
            <ENT>Franklin County, Illinois</ENT>
            <ENT>6.8</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="1234"/>
            <ENT I="01">17057</ENT>
            <ENT>Fulton County; Canton, IL Micro Area; Illinois</ENT>
            <ENT>5.2</ENT>
            <ENT>4.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17061</ENT>
            <ENT>Greene County, Illinois</ENT>
            <ENT>5.0</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17071</ENT>
            <ENT>Henderson County; Burlington, IA-IL Micro Area; Illinois</ENT>
            <ENT>1.0</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17073</ENT>
            <ENT>Henry County; Davenport-Moline-Rock Island, IA-IL Metro Area; Illinois</ENT>
            <ENT>8.0</ENT>
            <ENT>5.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17075</ENT>
            <ENT>Iroquois County, Illinois</ENT>
            <ENT>6.7</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17083</ENT>
            <ENT>Jersey County; St. Louis, MO-IL Metro Area; Illinois</ENT>
            <ENT>4.8</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17087</ENT>
            <ENT>Johnson County, Illinois</ENT>
            <ENT>1.3</ENT>
            <ENT>3.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17089</ENT>
            <ENT>Kane County; Chicago-Naperville-Joliet, IL-IN-WI Metro Area; Illinois</ENT>
            <ENT>7.2</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17091</ENT>
            <ENT>Kankakee County; Kankakee-Bradley, IL Metro Area; Illinois</ENT>
            <ENT>7.2</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17097</ENT>
            <ENT>Lake County; Chicago-Naperville-Joliet, IL-IN-WI Metro Area; Illinois</ENT>
            <ENT>8.2</ENT>
            <ENT>5.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17109</ENT>
            <ENT>McDonough County; Macomb, IL Micro Area; Illinois</ENT>
            <ENT>3.4</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17111</ENT>
            <ENT>McHenry County; Chicago-Naperville-Joliet, IL-IN-WI Metro Area; Illinois</ENT>
            <ENT>7.1</ENT>
            <ENT>4.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17125</ENT>
            <ENT>Mason County, Illinois</ENT>
            <ENT>3.6</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17131</ENT>
            <ENT>Mercer County; Davenport-Moline-Rock Island, IA-IL Metro Area; Illinois</ENT>
            <ENT>4.9</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17139</ENT>
            <ENT>Moultrie County, Illinois</ENT>
            <ENT>8.0</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17141</ENT>
            <ENT>Ogle County; Rochelle, IL Micro Area; Illinois</ENT>
            <ENT>5.8</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17147</ENT>
            <ENT>Piatt County; Champaign-Urbana, IL Metro Area; Illinois</ENT>
            <ENT>5.7</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17149</ENT>
            <ENT>Pike County, Illinois</ENT>
            <ENT>4.6</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17153</ENT>
            <ENT>Pulaski County, Illinois</ENT>
            <ENT>5.2</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17161</ENT>
            <ENT>Rock Island County; Davenport-Moline-Rock Island, IA-IL Metro Area; Illinois</ENT>
            <ENT>7.0</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17169</ENT>
            <ENT>Schuyler County, Illinois</ENT>
            <ENT>N/A</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17171</ENT>
            <ENT>Scott County; Jacksonville, IL Micro Area; Illinois</ENT>
            <ENT>4.1</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17173</ENT>
            <ENT>Shelby County, Illinois</ENT>
            <ENT>3.9</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17181</ENT>
            <ENT>Union County, Illinois</ENT>
            <ENT>1.8</ENT>
            <ENT>4.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17195</ENT>
            <ENT>Whiteside County; Sterling, IL Micro Area; Illinois</ENT>
            <ENT>3.6</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17197</ENT>
            <ENT>Will County; Chicago-Naperville-Joliet, IL-IN-WI Metro Area; Illinois</ENT>
            <ENT>8.0</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">17203</ENT>
            <ENT>Woodford County; Peoria, IL Metro Area; Illinois</ENT>
            <ENT>4.4</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18001</ENT>
            <ENT>Adams County; Decatur, IN Micro Area; Indiana</ENT>
            <ENT>8.0</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18007</ENT>
            <ENT>Benton County; Lafayette, IN Metro Area; Indiana</ENT>
            <ENT>4.3</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18015</ENT>
            <ENT>Carroll County; Lafayette, IN Metro Area; Indiana</ENT>
            <ENT>4.2</ENT>
            <ENT>4.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18029</ENT>
            <ENT>Dearborn County; Cincinnati-Middletown, OH-KY-IN Metro Area; Indiana</ENT>
            <ENT>8.6</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18031</ENT>
            <ENT>Decatur County; Greensburg, IN Micro Area; Indiana</ENT>
            <ENT>1.7</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18037</ENT>
            <ENT>Dubois County; Jasper, IN Micro Area; Indiana</ENT>
            <ENT>6.1</ENT>
            <ENT>3.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18073</ENT>
            <ENT>Jasper County; Chicago-Naperville-Joliet, IL-IN-WI Metro Area; Indiana</ENT>
            <ENT>5.1</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18085</ENT>
            <ENT>Kosciusko County; Warsaw, IN Micro Area; Indiana</ENT>
            <ENT>3.0</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18087</ENT>
            <ENT>LaGrange County, Indiana</ENT>
            <ENT>5.7</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18089</ENT>
            <ENT>Lake County; Chicago-Naperville-Joliet, IL-IN-WI Metro Area; Indiana</ENT>
            <ENT>7.8</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18105</ENT>
            <ENT>Monroe County; Bloomington, IN Metro Area; Indiana</ENT>
            <ENT>8.5</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18111</ENT>
            <ENT>Newton County; Chicago-Naperville-Joliet, IL-IN-WI Metro Area; Indiana</ENT>
            <ENT>5.9</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18119</ENT>
            <ENT>Owen County; Bloomington, IN Metro Area; Indiana</ENT>
            <ENT>4.6</ENT>
            <ENT>5.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18121</ENT>
            <ENT>Parke County, Indiana</ENT>
            <ENT>7.5</ENT>
            <ENT>5.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18127</ENT>
            <ENT>Porter County; Chicago-Naperville-Joliet, IL-IN-WI Metro Area; Indiana</ENT>
            <ENT>7.1</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18137</ENT>
            <ENT>Ripley County, Indiana</ENT>
            <ENT>6.0</ENT>
            <ENT>4.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18149</ENT>
            <ENT>Starke County, Indiana</ENT>
            <ENT>3.9</ENT>
            <ENT>4.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18157</ENT>
            <ENT>Tippecanoe County; Lafayette, IN Metro Area; Indiana</ENT>
            <ENT>6.6</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18159</ENT>
            <ENT>Tipton County; Kokomo, IN Metro Area; Indiana</ENT>
            <ENT>1.8</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18161</ENT>
            <ENT>Union County, Indiana</ENT>
            <ENT>5.7</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18165</ENT>
            <ENT>Vermillion County; Terre Haute, IN Metro Area; Indiana</ENT>
            <ENT>7.5</ENT>
            <ENT>5.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18171</ENT>
            <ENT>Warren County, Indiana</ENT>
            <ENT>6.4</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18175</ENT>
            <ENT>Washington County; Louisville-Jefferson County, KY-IN Metro Area; Indiana</ENT>
            <ENT>6.3</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18181</ENT>
            <ENT>White County, Indiana</ENT>
            <ENT>8.5</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">18183</ENT>
            <ENT>Whitley County; Fort Wayne, IN Metro Area; Indiana</ENT>
            <ENT>6.7</ENT>
            <ENT>7.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19003</ENT>
            <ENT>Adams County, Iowa</ENT>
            <ENT>4.5</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19005</ENT>
            <ENT>Allamakee County, Iowa</ENT>
            <ENT>7.4</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19009</ENT>
            <ENT>Audubon County, Iowa</ENT>
            <ENT>4.3</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19011</ENT>
            <ENT>Benton County; Cedar Rapids, IA Metro Area; Iowa</ENT>
            <ENT>3.8</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19013</ENT>
            <ENT>Black Hawk County; Waterloo-Cedar Falls, IA Metro Area; Iowa</ENT>
            <ENT>4.8</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19015</ENT>
            <ENT>Boone County; Boone, IA Micro Area; Iowa</ENT>
            <ENT>2.9</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19017</ENT>
            <ENT>Bremer County; Waterloo-Cedar Falls, IA Metro Area; Iowa</ENT>
            <ENT>3.0</ENT>
            <ENT>5.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19021</ENT>
            <ENT>Buena Vista County; Storm Lake, IA Micro Area; Iowa</ENT>
            <ENT>1.8</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19023</ENT>
            <ENT>Butler County, Iowa</ENT>
            <ENT>2.5</ENT>
            <ENT>4.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19031</ENT>
            <ENT>Cedar County, Iowa</ENT>
            <ENT>0.9</ENT>
            <ENT>5.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19033</ENT>
            <ENT>Cerro Gordo County; Mason City, IA Micro Area; Iowa</ENT>
            <ENT>8.0</ENT>
            <ENT>5.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19037</ENT>
            <ENT>Chickasaw County, Iowa</ENT>
            <ENT>3.4</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19041</ENT>
            <ENT>Clay County; Spencer, IA Micro Area; Iowa</ENT>
            <ENT>7.3</ENT>
            <ENT>4.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19049</ENT>
            <ENT>Dallas County; Des Moines-West Des Moines, IA Metro Area; Iowa</ENT>
            <ENT>4.5</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19073</ENT>
            <ENT>Greene County, Iowa</ENT>
            <ENT>4.7</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19075</ENT>
            <ENT>Grundy County; Waterloo-Cedar Falls, IA Metro Area; Iowa</ENT>
            <ENT>5.0</ENT>
            <ENT>4.7</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="1235"/>
            <ENT I="01">19079</ENT>
            <ENT>Hamilton County, Iowa</ENT>
            <ENT>6.4</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19081</ENT>
            <ENT>Hancock County, Iowa</ENT>
            <ENT>5.3</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19085</ENT>
            <ENT>Harrison County; Omaha-Council Bluffs, NE-IA Metro Area; Iowa</ENT>
            <ENT>5.5</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19091</ENT>
            <ENT>Humboldt County, Iowa</ENT>
            <ENT>5.3</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19097</ENT>
            <ENT>Jackson County, Iowa</ENT>
            <ENT>6.0</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19103</ENT>
            <ENT>Johnson County; Iowa City, IA Metro Area; Iowa</ENT>
            <ENT>5.3</ENT>
            <ENT>3.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19105</ENT>
            <ENT>Jones County; Cedar Rapids, IA Metro Area; Iowa</ENT>
            <ENT>6.5</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19113</ENT>
            <ENT>Linn County; Cedar Rapids, IA Metro Area; Iowa</ENT>
            <ENT>6.9</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19121</ENT>
            <ENT>Madison County; Des Moines-West Des Moines, IA Metro Area; Iowa</ENT>
            <ENT>4.4</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19131</ENT>
            <ENT>Mitchell County, Iowa</ENT>
            <ENT>N/A</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19135</ENT>
            <ENT>Monroe County, Iowa</ENT>
            <ENT>N/A</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19139</ENT>
            <ENT>Muscatine County; Muscatine, IA Micro Area; Iowa</ENT>
            <ENT>5.1</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19153</ENT>
            <ENT>Polk County; Des Moines-West Des Moines, IA Metro Area; Iowa</ENT>
            <ENT>5.7</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19159</ENT>
            <ENT>Ringgold County, Iowa</ENT>
            <ENT>1.0</ENT>
            <ENT>5.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19163</ENT>
            <ENT>Scott County; Davenport-Moline-Rock Island, IA-IL Metro Area; Iowa</ENT>
            <ENT>8.0</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19169</ENT>
            <ENT>Story County; Ames, IA Metro Area; Iowa</ENT>
            <ENT>4.2</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19177</ENT>
            <ENT>Van Buren County, Iowa</ENT>
            <ENT>7.0</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19179</ENT>
            <ENT>Wapello County; Ottumwa, IA Micro Area; Iowa</ENT>
            <ENT>7.4</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19181</ENT>
            <ENT>Warren County; Des Moines-West Des Moines, IA Metro Area; Iowa</ENT>
            <ENT>2.8</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19185</ENT>
            <ENT>Wayne County, Iowa</ENT>
            <ENT>2.2</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19187</ENT>
            <ENT>Webster County; Fort Dodge, IA Micro Area; Iowa</ENT>
            <ENT>4.6</ENT>
            <ENT>7.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19191</ENT>
            <ENT>Winneshiek County, Iowa</ENT>
            <ENT>7.0</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">19197</ENT>
            <ENT>Wright County, Iowa</ENT>
            <ENT>6.7</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">20017</ENT>
            <ENT>Chase County; Emporia, KS Micro Area; Kansas</ENT>
            <ENT>N/A</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">20023</ENT>
            <ENT>Cheyenne County, Kansas</ENT>
            <ENT>5.8</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">20045</ENT>
            <ENT>Douglas County; Lawrence, KS Metro Area; Kansas</ENT>
            <ENT>6.3</ENT>
            <ENT>3.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">20049</ENT>
            <ENT>Elk County, Kansas</ENT>
            <ENT>N/A</ENT>
            <ENT>7.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">20059</ENT>
            <ENT>Franklin County; Kansas City, MO-KS Metro Area; Kansas</ENT>
            <ENT>6.5</ENT>
            <ENT>5.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">20073</ENT>
            <ENT>Greenwood County, Kansas</ENT>
            <ENT>3.7</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">20079</ENT>
            <ENT>Harvey County; Wichita, KS Metro Area; Kansas</ENT>
            <ENT>8.7</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">20087</ENT>
            <ENT>Jefferson County; Topeka, KS Metro Area; Kansas</ENT>
            <ENT>4.9</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">20091</ENT>
            <ENT>Johnson County; Kansas City, MO-KS Metro Area; Kansas</ENT>
            <ENT>7.6</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">20107</ENT>
            <ENT>Linn County; Kansas City, MO-KS Metro Area; Kansas</ENT>
            <ENT>4.7</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">20121</ENT>
            <ENT>Miami County; Kansas City, MO-KS Metro Area; Kansas</ENT>
            <ENT>2.9</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">20131</ENT>
            <ENT>Nemaha County, Kansas</ENT>
            <ENT>4.7</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">20133</ENT>
            <ENT>Neosho County, Kansas</ENT>
            <ENT>3.3</ENT>
            <ENT>7.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">20161</ENT>
            <ENT>Riley County; Manhattan, KS Metro Area; Kansas</ENT>
            <ENT>4.3</ENT>
            <ENT>3.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">20183</ENT>
            <ENT>Smith County, Kansas</ENT>
            <ENT>6.3</ENT>
            <ENT>4.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">20199</ENT>
            <ENT>Wallace County, Kansas</ENT>
            <ENT>4.8</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21017</ENT>
            <ENT>Bourbon County; Lexington-Fayette, KY Metro Area; Kentucky</ENT>
            <ENT>4.7</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21023</ENT>
            <ENT>Bracken County; Cincinnati-Middletown, OH-KY-IN Metro Area; Kentucky</ENT>
            <ENT>6.1</ENT>
            <ENT>3.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21025</ENT>
            <ENT>Breathitt County, Kentucky</ENT>
            <ENT>2.4</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21029</ENT>
            <ENT>Bullitt County; Louisville-Jefferson County, KY-IN Metro Area; Kentucky</ENT>
            <ENT>6.1</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21031</ENT>
            <ENT>Butler County, Kentucky</ENT>
            <ENT>7.3</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21045</ENT>
            <ENT>Casey County, Kentucky</ENT>
            <ENT>2.1</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21051</ENT>
            <ENT>Clay County, Kentucky</ENT>
            <ENT>4.0</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21069</ENT>
            <ENT>Fleming County, Kentucky</ENT>
            <ENT>4.5</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21097</ENT>
            <ENT>Harrison County, Kentucky</ENT>
            <ENT>7.3</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21101</ENT>
            <ENT>Henderson County; Evansville, IN-KY Metro Area; Kentucky</ENT>
            <ENT>6.7</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21103</ENT>
            <ENT>Henry County; Louisville-Jefferson County, KY-IN Metro Area; Kentucky</ENT>
            <ENT>1.8</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21105</ENT>
            <ENT>Hickman County, Kentucky</ENT>
            <ENT>N/A</ENT>
            <ENT>4.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21109</ENT>
            <ENT>Jackson County, Kentucky</ENT>
            <ENT>4.7</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21113</ENT>
            <ENT>Jessamine County; Lexington-Fayette, KY Metro Area; Kentucky</ENT>
            <ENT>5.6</ENT>
            <ENT>5.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21129</ENT>
            <ENT>Lee County, Kentucky</ENT>
            <ENT>5.9</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21153</ENT>
            <ENT>Magoffin County, Kentucky</ENT>
            <ENT>8.3</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21185</ENT>
            <ENT>Oldham County; Louisville-Jefferson County, KY-IN Metro Area; Kentucky</ENT>
            <ENT>5.7</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21189</ENT>
            <ENT>Owsley County, Kentucky</ENT>
            <ENT>1.1</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21197</ENT>
            <ENT>Powell County, Kentucky</ENT>
            <ENT>3.1</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21211</ENT>
            <ENT>Shelby County; Louisville-Jefferson County, KY-IN Metro Area; Kentucky</ENT>
            <ENT>7.1</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21221</ENT>
            <ENT>Trigg County; Clarksville, TN-KY Metro Area; Kentucky</ENT>
            <ENT>7.6</ENT>
            <ENT>4.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21229</ENT>
            <ENT>Washington County, Kentucky</ENT>
            <ENT>6.3</ENT>
            <ENT>1.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">21239</ENT>
            <ENT>Woodford County; Lexington-Fayette, KY Metro Area; Kentucky</ENT>
            <ENT>3.2</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">22007</ENT>
            <ENT>Assumption Parish; Pierre Part, LA Micro Area; Louisiana</ENT>
            <ENT>6.0</ENT>
            <ENT>4.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">22009</ENT>
            <ENT>Avoyelles Parish, Louisiana</ENT>
            <ENT>6.1</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">22025</ENT>
            <ENT>Catahoula Parish, Louisiana</ENT>
            <ENT>2.9</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">22029</ENT>
            <ENT>Concordia Parish; Natchez, MS-LA Micro Area; Louisiana</ENT>
            <ENT>5.6</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">22037</ENT>
            <ENT>East Feliciana Parish; Baton Rouge, LA Metro Area; Louisiana</ENT>
            <ENT>1.2</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">22039</ENT>
            <ENT>Evangeline Parish, Louisiana</ENT>
            <ENT>8.5</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="1236"/>
            <ENT I="01">22041</ENT>
            <ENT>Franklin Parish, Louisiana</ENT>
            <ENT>1.8</ENT>
            <ENT>5.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">22045</ENT>
            <ENT>Iberia Parish; New Iberia, LA Micro Area; Louisiana</ENT>
            <ENT>4.0</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">22065</ENT>
            <ENT>Madison Parish; Tallulah, LA Micro Area; Louisiana</ENT>
            <ENT>3.7</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">22075</ENT>
            <ENT>Plaquemines Parish; New Orleans-Metairie-Kenner, LA Metro Area; Louisiana</ENT>
            <ENT>2.6</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">22081</ENT>
            <ENT>Red River Parish, Louisiana</ENT>
            <ENT>2.9</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">22083</ENT>
            <ENT>Richland Parish, Louisiana</ENT>
            <ENT>5.4</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">22087</ENT>
            <ENT>St. Bernard Parish; New Orleans-Metairie-Kenner, LA Metro Area; Louisiana</ENT>
            <ENT>4.4</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">22091</ENT>
            <ENT>St. Helena Parish; Baton Rouge, LA Metro Area; Louisiana</ENT>
            <ENT>N/A</ENT>
            <ENT>4.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">22125</ENT>
            <ENT>West Feliciana Parish; Baton Rouge, LA Metro Area; Louisiana</ENT>
            <ENT>2.5</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">23005</ENT>
            <ENT>Cumberland County; Portland-South Portland-Biddeford, ME Metro Area; Maine</ENT>
            <ENT>5.7</ENT>
            <ENT>3.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">23009</ENT>
            <ENT>Hancock County, Maine</ENT>
            <ENT>8.1</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">23013</ENT>
            <ENT>Knox County; Rockland, ME Micro Area; Maine</ENT>
            <ENT>7.3</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">23019</ENT>
            <ENT>Penobscot County; Bangor, ME Metro Area; Maine</ENT>
            <ENT>5.9</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">23023</ENT>
            <ENT>Sagadahoc County; Portland-South Portland-Biddeford, ME Metro Area; Maine</ENT>
            <ENT>7.5</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">24003</ENT>
            <ENT>Anne Arundel County; Baltimore-Towson, MD Metro Area; Maryland</ENT>
            <ENT>6.3</ENT>
            <ENT>4.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">24005</ENT>
            <ENT>Baltimore County; Baltimore-Towson, MD Metro Area; Maryland</ENT>
            <ENT>6.2</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">24009</ENT>
            <ENT>Calvert County; Washington-Arlington-Alexandria, DC-VA-MD-WV Metro Area; Maryland</ENT>
            <ENT>3.9</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">24011</ENT>
            <ENT>Caroline County, Maryland</ENT>
            <ENT>4.5</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">24013</ENT>
            <ENT>Carroll County; Baltimore-Towson, MD Metro Area; Maryland</ENT>
            <ENT>6.0</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">24017</ENT>
            <ENT>Charles County; Washington-Arlington-Alexandria, DC-VA-MD-WV Metro Area; Maryland</ENT>
            <ENT>5.4</ENT>
            <ENT>4.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">24019</ENT>
            <ENT>Dorchester County; Cambridge, MD Micro Area; Maryland</ENT>
            <ENT>4.7</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">24021</ENT>
            <ENT>Frederick County; Washington-Arlington-Alexandria, DC-VA-MD-WV Metro Area; Maryland</ENT>
            <ENT>5.5</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">24025</ENT>
            <ENT>Harford County; Baltimore-Towson, MD Metro Area; Maryland</ENT>
            <ENT>6.0</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">24031</ENT>
            <ENT>Montgomery County; Washington-Arlington-Alexandria, DC-VA-MD-WV Metro Area; Maryland</ENT>
            <ENT>5.3</ENT>
            <ENT>3.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">24033</ENT>
            <ENT>Prince George's County; Washington-Arlington-Alexandria, DC-VA-MD-WV Metro Area; Maryland</ENT>
            <ENT>8.1</ENT>
            <ENT>5.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">24035</ENT>
            <ENT>Queen Anne's County; Baltimore-Towson, MD Metro Area; Maryland</ENT>
            <ENT>4.9</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">24041</ENT>
            <ENT>Talbot County; Easton, MD Micro Area; Maryland</ENT>
            <ENT>3.1</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">24043</ENT>
            <ENT>Washington County; Hagerstown-Martinsburg, MD-WV Metro Area; Maryland</ENT>
            <ENT>7.4</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">24045</ENT>
            <ENT>Wicomico County; Salisbury, MD Metro Area; Maryland</ENT>
            <ENT>5.6</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">25001</ENT>
            <ENT>Barnstable County; Barnstable Town, MA Metro Area; Massachusetts</ENT>
            <ENT>6.5</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">25005</ENT>
            <ENT>Bristol County; Providence-New Bedford-Fall River, RI-MA Metro Area; Massachusetts</ENT>
            <ENT>5.1</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">25007</ENT>
            <ENT>Dukes County, Massachusetts</ENT>
            <ENT>6.6</ENT>
            <ENT>4.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">25009</ENT>
            <ENT>Essex County; Boston-Cambridge-Quincy, MA-NH Metro Area; Massachusetts</ENT>
            <ENT>6.3</ENT>
            <ENT>3.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">25011</ENT>
            <ENT>Franklin County; Springfield, MA Metro Area; Massachusetts</ENT>
            <ENT>2.3</ENT>
            <ENT>2.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">25013</ENT>
            <ENT>Hampden County; Springfield, MA Metro Area; Massachusetts</ENT>
            <ENT>5.0</ENT>
            <ENT>5.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">25015</ENT>
            <ENT>Hampshire County; Springfield, MA Metro Area; Massachusetts</ENT>
            <ENT>4.8</ENT>
            <ENT>2.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">25017</ENT>
            <ENT>Middlesex County; Boston-Cambridge-Quincy, MA-NH Metro Area; Massachusetts</ENT>
            <ENT>5.8</ENT>
            <ENT>2.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">25021</ENT>
            <ENT>Norfolk County; Boston-Cambridge-Quincy, MA-NH Metro Area; Massachusetts</ENT>
            <ENT>3.8</ENT>
            <ENT>2.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">25023</ENT>
            <ENT>Plymouth County; Boston-Cambridge-Quincy, MA-NH Metro Area; Massachusetts</ENT>
            <ENT>4.4</ENT>
            <ENT>3.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">25025</ENT>
            <ENT>Suffolk County; Boston-Cambridge-Quincy, MA-NH Metro Area; Massachusetts</ENT>
            <ENT>5.5</ENT>
            <ENT>3.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">25027</ENT>
            <ENT>Worcester County; Worcester, MA Metro Area; Massachusetts</ENT>
            <ENT>7.8</ENT>
            <ENT>4.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26005</ENT>
            <ENT>Allegan County; Allegan, MI Micro Area; Michigan</ENT>
            <ENT>6.5</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26007</ENT>
            <ENT>Alpena County; Alpena, MI Micro Area; Michigan</ENT>
            <ENT>6.8</ENT>
            <ENT>5.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26015</ENT>
            <ENT>Barry County; Grand Rapids-Wyoming, MI Metro Area; Michigan</ENT>
            <ENT>7.6</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26027</ENT>
            <ENT>Cass County; South Bend-Mishawaka, IN-MI Metro Area; Michigan</ENT>
            <ENT>8.5</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26029</ENT>
            <ENT>Charlevoix County, Michigan</ENT>
            <ENT>5.9</ENT>
            <ENT>5.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26031</ENT>
            <ENT>Cheboygan County, Michigan</ENT>
            <ENT>8.0</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26045</ENT>
            <ENT>Eaton County; Lansing-East Lansing, MI Metro Area; Michigan</ENT>
            <ENT>8.0</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26051</ENT>
            <ENT>Gladwin County, Michigan</ENT>
            <ENT>6.8</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26055</ENT>
            <ENT>Grand Traverse County; Traverse City, MI Micro Area; Michigan</ENT>
            <ENT>8.3</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26061</ENT>
            <ENT>Houghton County; Houghton, MI Micro Area; Michigan</ENT>
            <ENT>4.4</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26063</ENT>
            <ENT>Huron County, Michigan</ENT>
            <ENT>8.2</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26067</ENT>
            <ENT>Ionia County; Grand Rapids-Wyoming, MI Metro Area; Michigan</ENT>
            <ENT>6.3</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26077</ENT>
            <ENT>Kalamazoo County; Kalamazoo-Portage, MI Metro Area; Michigan</ENT>
            <ENT>8.6</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26081</ENT>
            <ENT>Kent County; Grand Rapids-Wyoming, MI Metro Area; Michigan</ENT>
            <ENT>7.8</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26087</ENT>
            <ENT>Lapeer County; Detroit-Warren-Livonia, MI Metro Area; Michigan</ENT>
            <ENT>7.2</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26091</ENT>
            <ENT>Lenawee County; Adrian, MI Micro Area; Michigan</ENT>
            <ENT>6.8</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26099</ENT>
            <ENT>Macomb County; Detroit-Warren-Livonia, MI Metro Area; Michigan</ENT>
            <ENT>7.2</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26111</ENT>
            <ENT>Midland County; Midland, MI Micro Area; Michigan</ENT>
            <ENT>6.0</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26115</ENT>
            <ENT>Monroe County; Monroe, MI Metro Area; Michigan</ENT>
            <ENT>8.0</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26119</ENT>
            <ENT>Montmorency County, Michigan</ENT>
            <ENT>4.2</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26123</ENT>
            <ENT>Newaygo County; Grand Rapids-Wyoming, MI Metro Area; Michigan</ENT>
            <ENT>6.2</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26129</ENT>
            <ENT>Ogemaw County, Michigan</ENT>
            <ENT>4.8</ENT>
            <ENT>4.5</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="1237"/>
            <ENT I="01">26145</ENT>
            <ENT>Saginaw County; Saginaw-Saginaw Township North, MI Metro Area; Michigan</ENT>
            <ENT>8.7</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">26165</ENT>
            <ENT>Wexford County; Cadillac, MI Micro Area; Michigan</ENT>
            <ENT>5.4</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27003</ENT>
            <ENT>Anoka County; Minneapolis-St. Paul-Bloomington, MN-WI Metro Area; Minnesota</ENT>
            <ENT>7.6</ENT>
            <ENT>2.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27005</ENT>
            <ENT>Becker County, Minnesota</ENT>
            <ENT>1.7</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27007</ENT>
            <ENT>Beltrami County; Bemidji, MN Micro Area; Minnesota</ENT>
            <ENT>6.2</ENT>
            <ENT>4.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27013</ENT>
            <ENT>Blue Earth County; Mankato-North Mankato, MN Metro Area; Minnesota</ENT>
            <ENT>5.6</ENT>
            <ENT>3.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27017</ENT>
            <ENT>Carlton County; Duluth, MN-WI Metro Area; Minnesota</ENT>
            <ENT>2.5</ENT>
            <ENT>4.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27019</ENT>
            <ENT>Carver County; Minneapolis-St. Paul-Bloomington, MN-WI Metro Area; Minnesota</ENT>
            <ENT>4.3</ENT>
            <ENT>2.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27021</ENT>
            <ENT>Cass County; Brainerd, MN Micro Area; Minnesota</ENT>
            <ENT>4.6</ENT>
            <ENT>4.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27025</ENT>
            <ENT>Chisago County; Minneapolis-St. Paul-Bloomington, MN-WI Metro Area; Minnesota</ENT>
            <ENT>5.3</ENT>
            <ENT>2.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27029</ENT>
            <ENT>Clearwater County, Minnesota</ENT>
            <ENT>5.5</ENT>
            <ENT>5.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27031</ENT>
            <ENT>Cook County, Minnesota</ENT>
            <ENT>4.9</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27035</ENT>
            <ENT>Crow Wing County; Brainerd, MN Micro Area; Minnesota</ENT>
            <ENT>4.6</ENT>
            <ENT>2.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27037</ENT>
            <ENT>Dakota County; Minneapolis-St. Paul-Bloomington, MN-WI Metro Area; Minnesota</ENT>
            <ENT>8.2</ENT>
            <ENT>2.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27041</ENT>
            <ENT>Douglas County; Alexandria, MN Micro Area; Minnesota</ENT>
            <ENT>2.3</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27049</ENT>
            <ENT>Goodhue County; Red Wing, MN Micro Area; Minnesota</ENT>
            <ENT>6.0</ENT>
            <ENT>4.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27053</ENT>
            <ENT>Hennepin County; Minneapolis-St. Paul-Bloomington, MN-WI Metro Area; Minnesota</ENT>
            <ENT>6.5</ENT>
            <ENT>2.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27059</ENT>
            <ENT>Isanti County; Minneapolis-St. Paul-Bloomington, MN-WI Metro Area; Minnesota</ENT>
            <ENT>8.7</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27061</ENT>
            <ENT>Itasca County, Minnesota</ENT>
            <ENT>4.5</ENT>
            <ENT>4.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27065</ENT>
            <ENT>Kanabec County, Minnesota</ENT>
            <ENT>3.1</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27087</ENT>
            <ENT>Mahnomen County, Minnesota</ENT>
            <ENT>5.9</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27093</ENT>
            <ENT>Meeker County, Minnesota</ENT>
            <ENT>7.4</ENT>
            <ENT>4.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27095</ENT>
            <ENT>Mille Lacs County, Minnesota</ENT>
            <ENT>3.4</ENT>
            <ENT>3.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27097</ENT>
            <ENT>Morrison County, Minnesota</ENT>
            <ENT>3.0</ENT>
            <ENT>4.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27099</ENT>
            <ENT>Mower County; Austin, MN Micro Area; Minnesota</ENT>
            <ENT>5.1</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27103</ENT>
            <ENT>Nicollet County; Mankato-North Mankato, MN Metro Area; Minnesota</ENT>
            <ENT>2.3</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27105</ENT>
            <ENT>Nobles County; Worthington, MN Micro Area; Minnesota</ENT>
            <ENT>2.4</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27111</ENT>
            <ENT>Otter Tail County; Fergus Falls, MN Micro Area; Minnesota</ENT>
            <ENT>6.1</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27115</ENT>
            <ENT>Pine County, Minnesota</ENT>
            <ENT>3.9</ENT>
            <ENT>4.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27121</ENT>
            <ENT>Pope County, Minnesota</ENT>
            <ENT>4.2</ENT>
            <ENT>4.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27123</ENT>
            <ENT>Ramsey County; Minneapolis-St. Paul-Bloomington, MN-WI Metro Area; Minnesota</ENT>
            <ENT>6.6</ENT>
            <ENT>2.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27137</ENT>
            <ENT>St. Louis County; Duluth, MN-WI Metro Area; Minnesota</ENT>
            <ENT>5.2</ENT>
            <ENT>6.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27139</ENT>
            <ENT>Scott County; Minneapolis-St. Paul-Bloomington, MN-WI Metro Area; Minnesota</ENT>
            <ENT>6.7</ENT>
            <ENT>4.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27143</ENT>
            <ENT>Sibley County, Minnesota</ENT>
            <ENT>7.9</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27145</ENT>
            <ENT>Stearns County; St. Cloud, MN Metro Area; Minnesota</ENT>
            <ENT>6.8</ENT>
            <ENT>3.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27149</ENT>
            <ENT>Stevens County, Minnesota</ENT>
            <ENT>7.2</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27157</ENT>
            <ENT>Wabasha County; Rochester, MN Metro Area; Minnesota</ENT>
            <ENT>7.4</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27159</ENT>
            <ENT>Wadena County, Minnesota</ENT>
            <ENT>7.0</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27163</ENT>
            <ENT>Washington County; Minneapolis-St. Paul-Bloomington, MN-WI Metro Area; Minnesota</ENT>
            <ENT>6.7</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27169</ENT>
            <ENT>Winona County; Winona, MN Micro Area; Minnesota</ENT>
            <ENT>4.8</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">27171</ENT>
            <ENT>Wright County; Minneapolis-St. Paul-Bloomington, MN-WI Metro Area; Minnesota</ENT>
            <ENT>3.9</ENT>
            <ENT>2.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28005</ENT>
            <ENT>Amite County; McComb, MS Micro Area; Mississippi</ENT>
            <ENT>4.7</ENT>
            <ENT>4.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28011</ENT>
            <ENT>Bolivar County; Cleveland, MS Micro Area; Mississippi</ENT>
            <ENT>6.2</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28013</ENT>
            <ENT>Calhoun County, Mississippi</ENT>
            <ENT>2.7</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28021</ENT>
            <ENT>Claiborne County, Mississippi</ENT>
            <ENT>8.7</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28027</ENT>
            <ENT>Coahoma County; Clarksdale, MS Micro Area; Mississippi</ENT>
            <ENT>5.9</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28051</ENT>
            <ENT>Holmes County, Mississippi</ENT>
            <ENT>2.6</ENT>
            <ENT>4.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28053</ENT>
            <ENT>Humphreys County, Mississippi</ENT>
            <ENT>N/A</ENT>
            <ENT>3.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28061</ENT>
            <ENT>Jasper County; Laurel, MS Micro Area; Mississippi</ENT>
            <ENT>3.2</ENT>
            <ENT>4.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28069</ENT>
            <ENT>Kemper County; Meridian, MS Micro Area; Mississippi</ENT>
            <ENT>1.2</ENT>
            <ENT>2.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28089</ENT>
            <ENT>Madison County; Jackson, MS Metro Area; Mississippi</ENT>
            <ENT>6.8</ENT>
            <ENT>5.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28093</ENT>
            <ENT>Marshall County; Memphis, TN-MS-AR Metro Area; Mississippi</ENT>
            <ENT>5.6</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28103</ENT>
            <ENT>Noxubee County, Mississippi</ENT>
            <ENT>2.3</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28119</ENT>
            <ENT>Quitman County, Mississippi</ENT>
            <ENT>8.2</ENT>
            <ENT>3.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28123</ENT>
            <ENT>Scott County, Mississippi</ENT>
            <ENT>6.8</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28125</ENT>
            <ENT>Sharkey County, Mississippi</ENT>
            <ENT>6.5</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28133</ENT>
            <ENT>Sunflower County; Indianola, MS Micro Area; Mississippi</ENT>
            <ENT>3.4</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28135</ENT>
            <ENT>Tallahatchie County, Mississippi</ENT>
            <ENT>7.8</ENT>
            <ENT>4.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28137</ENT>
            <ENT>Tate County; Memphis, TN-MS-AR Metro Area; Mississippi</ENT>
            <ENT>7.1</ENT>
            <ENT>4.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28145</ENT>
            <ENT>Union County, Mississippi</ENT>
            <ENT>7.6</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28147</ENT>
            <ENT>Walthall County, Mississippi</ENT>
            <ENT>3.5</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28155</ENT>
            <ENT>Webster County, Mississippi</ENT>
            <ENT>2.3</ENT>
            <ENT>4.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">28157</ENT>
            <ENT>Wilkinson County, Mississippi</ENT>
            <ENT>2.2</ENT>
            <ENT>1.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">29003</ENT>
            <ENT>Andrew County; St. Joseph, MO-KS Metro Area; Missouri</ENT>
            <ENT>N/A</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">29013</ENT>
            <ENT>Bates County; Kansas City, MO-KS Metro Area; Missouri</ENT>
            <ENT>4.9</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">29017</ENT>
            <ENT>Bollinger County; Cape Girardeau-Jackson, MO-IL Metro Area; Missouri</ENT>
            <ENT>5.9</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">29019</ENT>
            <ENT>Boone County; Columbia, MO Metro Area; Missouri</ENT>
            <ENT>6.6</ENT>
            <ENT>7.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">29037</ENT>
            <ENT>Cass County; Kansas City, MO-KS Metro Area; Missouri</ENT>
            <ENT>6.5</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="1238"/>
            <ENT I="01">29045</ENT>
            <ENT>Clark County; Fort Madison-Keokuk, IA-MO Micro Area; Missouri</ENT>
            <ENT>6.3</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">29049</ENT>
            <ENT>Clinton County; Kansas City, MO-KS Metro Area; Missouri</ENT>
            <ENT>6.2</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">29051</ENT>
            <ENT>Cole County; Jefferson City, MO Metro Area; Missouri</ENT>
            <ENT>6.0</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">29093</ENT>
            <ENT>Iron County, Missouri</ENT>
            <ENT>3.9</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">29183</ENT>
            <ENT>St. Charles County; St. Louis, MO-IL Metro Area; Missouri</ENT>
            <ENT>6.8</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">29186</ENT>
            <ENT>Ste. Genevieve County, Missouri</ENT>
            <ENT>6.6</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">29189</ENT>
            <ENT>St. Louis County; St. Louis, MO-IL Metro Area; Missouri</ENT>
            <ENT>6.7</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">29219</ENT>
            <ENT>Warren County; St. Louis, MO-IL Metro Area; Missouri</ENT>
            <ENT>1.9</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">29227</ENT>
            <ENT>Worth County, Missouri</ENT>
            <ENT>8.6</ENT>
            <ENT>6.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">30005</ENT>
            <ENT>Blaine County, Montana</ENT>
            <ENT>5.5</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">30013</ENT>
            <ENT>Cascade County; Great Falls, MT Metro Area; Montana</ENT>
            <ENT>5.3</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">30029</ENT>
            <ENT>Flathead County; Kalispell, MT Micro Area; Montana</ENT>
            <ENT>7.0</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">30031</ENT>
            <ENT>Gallatin County; Bozeman, MT Micro Area; Montana</ENT>
            <ENT>4.5</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">30049</ENT>
            <ENT>Lewis and Clark County; Helena, MT Micro Area; Montana</ENT>
            <ENT>5.3</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">30063</ENT>
            <ENT>Missoula County; Missoula, MT Metro Area; Montana</ENT>
            <ENT>6.0</ENT>
            <ENT>4.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">30081</ENT>
            <ENT>Ravalli County, Montana</ENT>
            <ENT>8.1</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">30095</ENT>
            <ENT>Stillwater County, Montana</ENT>
            <ENT>3.4</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">30099</ENT>
            <ENT>Teton County, Montana</ENT>
            <ENT>1.5</ENT>
            <ENT>6.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">30103</ENT>
            <ENT>Treasure County, Montana</ENT>
            <ENT>3.8</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">30105</ENT>
            <ENT>Valley County, Montana</ENT>
            <ENT>7.8</ENT>
            <ENT>7.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">30111</ENT>
            <ENT>Yellowstone County; Billings, MT Metro Area; Montana</ENT>
            <ENT>4.0</ENT>
            <ENT>5.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31005</ENT>
            <ENT>Arthur County, Nebraska</ENT>
            <ENT>N/A</ENT>
            <ENT>5.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31007</ENT>
            <ENT>Banner County; Scottsbluff, NE Micro Area; Nebraska</ENT>
            <ENT>2.7</ENT>
            <ENT>N/A</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31019</ENT>
            <ENT>Buffalo County; Kearney, NE Micro Area; Nebraska</ENT>
            <ENT>7.2</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31021</ENT>
            <ENT>Burt County, Nebraska</ENT>
            <ENT>5.0</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31039</ENT>
            <ENT>Cuming County, Nebraska</ENT>
            <ENT>0.8</ENT>
            <ENT>5.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31051</ENT>
            <ENT>Dixon County; Sioux City, IA-NE-SD Metro Area; Nebraska</ENT>
            <ENT>5.6</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31059</ENT>
            <ENT>Fillmore County, Nebraska</ENT>
            <ENT>1.4</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31061</ENT>
            <ENT>Franklin County, Nebraska</ENT>
            <ENT>8.2</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31109</ENT>
            <ENT>Lancaster County; Lincoln, NE Metro Area; Nebraska</ENT>
            <ENT>7.5</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31117</ENT>
            <ENT>McPherson County; North Platte, NE Micro Area; Nebraska</ENT>
            <ENT>4.5</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31121</ENT>
            <ENT>Merrick County; Grand Island, NE Micro Area; Nebraska</ENT>
            <ENT>4.6</ENT>
            <ENT>6.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31149</ENT>
            <ENT>Rock County, Nebraska</ENT>
            <ENT>6.7</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31153</ENT>
            <ENT>Sarpy County; Omaha-Council Bluffs, NE-IA Metro Area; Nebraska</ENT>
            <ENT>6.9</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31159</ENT>
            <ENT>Seward County; Lincoln, NE Metro Area; Nebraska</ENT>
            <ENT>5.3</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31165</ENT>
            <ENT>Sioux County, Nebraska</ENT>
            <ENT>6.9</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31167</ENT>
            <ENT>Stanton County; Norfolk, NE Micro Area; Nebraska</ENT>
            <ENT>N/A</ENT>
            <ENT>6.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31173</ENT>
            <ENT>Thurston County, Nebraska</ENT>
            <ENT>7.0</ENT>
            <ENT>4.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31177</ENT>
            <ENT>Washington County; Omaha-Council Bluffs, NE-IA Metro Area; Nebraska</ENT>
            <ENT>5.8</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">31179</ENT>
            <ENT>Wayne County, Nebraska</ENT>
            <ENT>7.1</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">33001</ENT>
            <ENT>Belknap County; Laconia, NH Micro Area; New Hampshire</ENT>
            <ENT>4.7</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">33005</ENT>
            <ENT>Cheshire County; Keene, NH Micro Area; New Hampshire</ENT>
            <ENT>4.9</ENT>
            <ENT>3.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">33009</ENT>
            <ENT>Grafton County; Lebanon, NH-VT Micro Area; New Hampshire</ENT>
            <ENT>7.6</ENT>
            <ENT>3.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">33011</ENT>
            <ENT>Hillsborough County; Manchester-Nashua, NH Metro Area; New Hampshire</ENT>
            <ENT>6.9</ENT>
            <ENT>2.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">33013</ENT>
            <ENT>Merrimack County; Concord, NH Micro Area; New Hampshire</ENT>
            <ENT>4.5</ENT>
            <ENT>3.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">33015</ENT>
            <ENT>Rockingham County; Boston-Cambridge-Quincy, MA-NH Metro Area; New Hampshire</ENT>
            <ENT>7.4</ENT>
            <ENT>3.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">33017</ENT>
            <ENT>Strafford County; Boston-Cambridge-Quincy, MA-NH Metro Area; New Hampshire</ENT>
            <ENT>4.7</ENT>
            <ENT>2.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">33019</ENT>
            <ENT>Sullivan County; Claremont, NH Micro Area; New Hampshire</ENT>
            <ENT>3.9</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">34003</ENT>
            <ENT>Bergen County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New Jersey</ENT>
            <ENT>3.8</ENT>
            <ENT>2.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">34005</ENT>
            <ENT>Burlington County; Philadelphia-Camden-Wilmington, PA-NJ-DE-MD Metro Area; New Jersey</ENT>
            <ENT>6.1</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">34007</ENT>
            <ENT>Camden County; Philadelphia-Camden-Wilmington, PA-NJ-DE-MD Metro Area; New Jersey</ENT>
            <ENT>5.5</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">34011</ENT>
            <ENT>Cumberland County; Vineland-Millville-Bridgeton, NJ Metro Area; New Jersey</ENT>
            <ENT>8.1</ENT>
            <ENT>6.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">34013</ENT>
            <ENT>Essex County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New Jersey</ENT>
            <ENT>7.1</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">34015</ENT>
            <ENT>Gloucester County; Philadelphia-Camden-Wilmington, PA-NJ-DE-MD Metro Area; New Jersey</ENT>
            <ENT>7.7</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">34017</ENT>
            <ENT>Hudson County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New Jersey</ENT>
            <ENT>6.2</ENT>
            <ENT>3.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">34019</ENT>
            <ENT>Hunterdon County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New Jersey</ENT>
            <ENT>2.2</ENT>
            <ENT>4.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">34021</ENT>
            <ENT>Mercer County; Trenton-Ewing, NJ Metro Area; New Jersey</ENT>
            <ENT>7.7</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">34023</ENT>
            <ENT>Middlesex County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New Jersey</ENT>
            <ENT>5.3</ENT>
            <ENT>3.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">34025</ENT>
            <ENT>Monmouth County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New Jersey</ENT>
            <ENT>5.6</ENT>
            <ENT>4.5</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="1239"/>
            <ENT I="01">34027</ENT>
            <ENT>Morris County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New Jersey</ENT>
            <ENT>6.0</ENT>
            <ENT>2.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">34031</ENT>
            <ENT>Passaic County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New Jersey</ENT>
            <ENT>6.5</ENT>
            <ENT>3.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">34037</ENT>
            <ENT>Sussex County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New Jersey</ENT>
            <ENT>3.5</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">34039</ENT>
            <ENT>Union County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New Jersey</ENT>
            <ENT>6.5</ENT>
            <ENT>3.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">34041</ENT>
            <ENT>Warren County; Allentown-Bethlehem-Easton, PA-NJ Metro Area; New Jersey</ENT>
            <ENT>7.0</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">35033</ENT>
            <ENT>Mora County, New Mexico</ENT>
            <ENT>7.1</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36001</ENT>
            <ENT>Albany County; Albany-Schenectady-Troy, NY Metro Area; New York</ENT>
            <ENT>4.8</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36005</ENT>
            <ENT>Bronx County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New York</ENT>
            <ENT>3.7</ENT>
            <ENT>4.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36019</ENT>
            <ENT>Clinton County; Plattsburgh, NY Micro Area; New York</ENT>
            <ENT>5.3</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36021</ENT>
            <ENT>Columbia County; Hudson, NY Micro Area; New York</ENT>
            <ENT>5.9</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36027</ENT>
            <ENT>Dutchess County; Poughkeepsie-Newburgh-Middletown, NY Metro Area; New York</ENT>
            <ENT>6.0</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36047</ENT>
            <ENT>Kings County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New York</ENT>
            <ENT>3.7</ENT>
            <ENT>3.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36059</ENT>
            <ENT>Nassau County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New York</ENT>
            <ENT>6.3</ENT>
            <ENT>2.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36061</ENT>
            <ENT>New York County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New York</ENT>
            <ENT>2.5</ENT>
            <ENT>3.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36071</ENT>
            <ENT>Orange County; Poughkeepsie-Newburgh-Middletown, NY Metro Area; New York</ENT>
            <ENT>4.2</ENT>
            <ENT>4.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36079</ENT>
            <ENT>Putnam County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New York</ENT>
            <ENT>5.0</ENT>
            <ENT>2.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36081</ENT>
            <ENT>Queens County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New York</ENT>
            <ENT>3.3</ENT>
            <ENT>2.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36085</ENT>
            <ENT>Richmond County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New York</ENT>
            <ENT>8.2</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36087</ENT>
            <ENT>Rockland County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New York</ENT>
            <ENT>4.2</ENT>
            <ENT>3.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36091</ENT>
            <ENT>Saratoga County; Albany-Schenectady-Troy, NY Metro Area; New York</ENT>
            <ENT>6.0</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36103</ENT>
            <ENT>Suffolk County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New York</ENT>
            <ENT>6.5</ENT>
            <ENT>3.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36109</ENT>
            <ENT>Tompkins County; Ithaca, NY Metro Area; New York</ENT>
            <ENT>3.3</ENT>
            <ENT>4.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36111</ENT>
            <ENT>Ulster County; Kingston, NY Metro Area; New York</ENT>
            <ENT>4.2</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36119</ENT>
            <ENT>Westchester County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; New York</ENT>
            <ENT>5.2</ENT>
            <ENT>3.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">36121</ENT>
            <ENT>Wyoming County, New York</ENT>
            <ENT>5.2</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37005</ENT>
            <ENT>Alleghany County, North Carolina</ENT>
            <ENT>2.1</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37015</ENT>
            <ENT>Bertie County, North Carolina</ENT>
            <ENT>4.4</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37023</ENT>
            <ENT>Burke County; Hickory-Lenoir-Morganton, NC Metro Area; North Carolina</ENT>
            <ENT>8.5</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37029</ENT>
            <ENT>Camden County; Elizabeth City, NC Micro Area; North Carolina</ENT>
            <ENT>N/A</ENT>
            <ENT>3.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37041</ENT>
            <ENT>Chowan County, North Carolina</ENT>
            <ENT>1.6</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37043</ENT>
            <ENT>Clay County, North Carolina</ENT>
            <ENT>7.6</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37057</ENT>
            <ENT>Davidson County; Thomasville-Lexington, NC Micro Area; North Carolina</ENT>
            <ENT>6.1</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37073</ENT>
            <ENT>Gates County, North Carolina</ENT>
            <ENT>2.0</ENT>
            <ENT>3.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37077</ENT>
            <ENT>Granville County, North Carolina</ENT>
            <ENT>3.6</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37079</ENT>
            <ENT>Greene County; Greenville, NC Metro Area; North Carolina</ENT>
            <ENT>4.5</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37083</ENT>
            <ENT>Halifax County; Roanoke Rapids, NC Micro Area; North Carolina</ENT>
            <ENT>6.0</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37091</ENT>
            <ENT>Hertford County, North Carolina</ENT>
            <ENT>7.2</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37109</ENT>
            <ENT>Lincoln County; Lincolnton, NC Micro Area; North Carolina</ENT>
            <ENT>4.5</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37111</ENT>
            <ENT>McDowell County, North Carolina</ENT>
            <ENT>7.5</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37117</ENT>
            <ENT>Martin County, North Carolina</ENT>
            <ENT>5.6</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37121</ENT>
            <ENT>Mitchell County, North Carolina</ENT>
            <ENT>1.2</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37123</ENT>
            <ENT>Montgomery County, North Carolina</ENT>
            <ENT>5.9</ENT>
            <ENT>5.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37131</ENT>
            <ENT>Northampton County; Roanoke Rapids, NC Micro Area; North Carolina</ENT>
            <ENT>1.7</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37143</ENT>
            <ENT>Perquimans County; Elizabeth City, NC Micro Area; North Carolina</ENT>
            <ENT>2.6</ENT>
            <ENT>5.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37145</ENT>
            <ENT>Person County; Durham-Chapel Hill, NC Metro Area; North Carolina</ENT>
            <ENT>5.5</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37169</ENT>
            <ENT>Stokes County; Winston-Salem, NC Metro Area; North Carolina</ENT>
            <ENT>7.0</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37175</ENT>
            <ENT>Transylvania County; Brevard, NC Micro Area; North Carolina</ENT>
            <ENT>4.6</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37177</ENT>
            <ENT>Tyrrell County, North Carolina</ENT>
            <ENT>3.7</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37179</ENT>
            <ENT>Union County; Charlotte-Gastonia-Concord, NC-SC Metro Area; North Carolina</ENT>
            <ENT>5.5</ENT>
            <ENT>3.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37181</ENT>
            <ENT>Vance County; Henderson, NC Micro Area; North Carolina</ENT>
            <ENT>6.4</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37187</ENT>
            <ENT>Washington County, North Carolina</ENT>
            <ENT>4.4</ENT>
            <ENT>6.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37189</ENT>
            <ENT>Watauga County; Boone, NC Micro Area; North Carolina</ENT>
            <ENT>6.6</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">37195</ENT>
            <ENT>Wilson County; Wilson, NC Micro Area; North Carolina</ENT>
            <ENT>6.5</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">38015</ENT>
            <ENT>Burleigh County; Bismarck, ND Metro Area; North Dakota</ENT>
            <ENT>5.5</ENT>
            <ENT>5.3</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="1240"/>
            <ENT I="01">38017</ENT>
            <ENT>Cass County; Fargo, ND-MN Metro Area; North Dakota</ENT>
            <ENT>4.5</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">38035</ENT>
            <ENT>Grand Forks County; Grand Forks, ND-MN Metro Area; North Dakota</ENT>
            <ENT>6.9</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">38079</ENT>
            <ENT>Rolette County, North Dakota</ENT>
            <ENT>7.8</ENT>
            <ENT>7.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">38085</ENT>
            <ENT>Sioux County, North Dakota</ENT>
            <ENT>3.5</ENT>
            <ENT>3.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">38091</ENT>
            <ENT>Steele County, North Dakota</ENT>
            <ENT>5.0</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">38101</ENT>
            <ENT>Ward County; Minot, ND Micro Area; North Dakota</ENT>
            <ENT>3.7</ENT>
            <ENT>5.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39001</ENT>
            <ENT>Adams County, Ohio</ENT>
            <ENT>8.6</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39005</ENT>
            <ENT>Ashland County; Ashland, OH Micro Area; Ohio</ENT>
            <ENT>5.1</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39015</ENT>
            <ENT>Brown County; Cincinnati-Middletown, OH-KY-IN Metro Area; Ohio</ENT>
            <ENT>6.3</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39019</ENT>
            <ENT>Carroll County; Canton-Massillon, OH Metro Area; Ohio</ENT>
            <ENT>2.9</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39029</ENT>
            <ENT>Columbiana County; East Liverpool-Salem, OH Micro Area; Ohio</ENT>
            <ENT>6.2</ENT>
            <ENT>6.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39037</ENT>
            <ENT>Darke County; Greenville, OH Micro Area; Ohio</ENT>
            <ENT>3.9</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39045</ENT>
            <ENT>Fairfield County; Columbus, OH Metro Area; Ohio</ENT>
            <ENT>5.8</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39055</ENT>
            <ENT>Geauga County; Cleveland-Elyria-Mentor, OH Metro Area; Ohio</ENT>
            <ENT>7.3</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39057</ENT>
            <ENT>Greene County; Dayton, OH Metro Area; Ohio</ENT>
            <ENT>6.1</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39067</ENT>
            <ENT>Harrison County, Ohio</ENT>
            <ENT>2.0</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39069</ENT>
            <ENT>Henry County, Ohio</ENT>
            <ENT>5.9</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39071</ENT>
            <ENT>Highland County, Ohio</ENT>
            <ENT>5.0</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39073</ENT>
            <ENT>Hocking County, Ohio</ENT>
            <ENT>6.1</ENT>
            <ENT>4.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39075</ENT>
            <ENT>Holmes County, Ohio</ENT>
            <ENT>5.0</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39077</ENT>
            <ENT>Huron County; Norwalk, OH Micro Area; Ohio</ENT>
            <ENT>7.9</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39083</ENT>
            <ENT>Knox County; Mount Vernon, OH Micro Area; Ohio</ENT>
            <ENT>5.5</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39085</ENT>
            <ENT>Lake County; Cleveland-Elyria-Mentor, OH Metro Area; Ohio</ENT>
            <ENT>7.4</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39089</ENT>
            <ENT>Licking County; Columbus, OH Metro Area; Ohio</ENT>
            <ENT>5.3</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39091</ENT>
            <ENT>Logan County; Bellefontaine, OH Micro Area; Ohio</ENT>
            <ENT>2.5</ENT>
            <ENT>7.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39097</ENT>
            <ENT>Madison County; Columbus, OH Metro Area; Ohio</ENT>
            <ENT>4.3</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39107</ENT>
            <ENT>Mercer County; Celina, OH Micro Area; Ohio</ENT>
            <ENT>5.4</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39109</ENT>
            <ENT>Miami County; Dayton, OH Metro Area; Ohio</ENT>
            <ENT>8.1</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39117</ENT>
            <ENT>Morrow County; Columbus, OH Metro Area; Ohio</ENT>
            <ENT>1.0</ENT>
            <ENT>4.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39121</ENT>
            <ENT>Noble County, Ohio</ENT>
            <ENT>5.5</ENT>
            <ENT>3.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39125</ENT>
            <ENT>Paulding County, Ohio</ENT>
            <ENT>8.6</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39129</ENT>
            <ENT>Pickaway County; Columbus, OH Metro Area; Ohio</ENT>
            <ENT>6.9</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39135</ENT>
            <ENT>Preble County; Dayton, OH Metro Area; Ohio</ENT>
            <ENT>1.7</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39137</ENT>
            <ENT>Putnam County, Ohio</ENT>
            <ENT>8.1</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39163</ENT>
            <ENT>Vinton County, Ohio</ENT>
            <ENT>4.8</ENT>
            <ENT>3.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39169</ENT>
            <ENT>Wayne County; Wooster, OH Micro Area; Ohio</ENT>
            <ENT>6.3</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39171</ENT>
            <ENT>Williams County, Ohio</ENT>
            <ENT>6.5</ENT>
            <ENT>5.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">39173</ENT>
            <ENT>Wood County; Toledo, OH Metro Area; Ohio</ENT>
            <ENT>7.5</ENT>
            <ENT>5.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">41027</ENT>
            <ENT>Hood River County; Hood River, OR Micro Area; Oregon</ENT>
            <ENT>7.4</ENT>
            <ENT>2.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">41029</ENT>
            <ENT>Jackson County; Medford, OR Metro Area; Oregon</ENT>
            <ENT>3.8</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">41033</ENT>
            <ENT>Josephine County; Grants Pass, OR Micro Area; Oregon</ENT>
            <ENT>4.0</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">41039</ENT>
            <ENT>Lane County; Eugene-Springfield, OR Metro Area; Oregon</ENT>
            <ENT>4.4</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">41051</ENT>
            <ENT>Multnomah County; Portland-Vancouver-Beaverton, OR-WA Metro Area; Oregon</ENT>
            <ENT>5.1</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">41053</ENT>
            <ENT>Polk County; Salem, OR Metro Area; Oregon</ENT>
            <ENT>7.6</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">41067</ENT>
            <ENT>Washington County; Portland-Vancouver-Beaverton, OR-WA Metro Area; Oregon</ENT>
            <ENT>5.7</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">41071</ENT>
            <ENT>Yamhill County; Portland-Vancouver-Beaverton, OR-WA Metro Area; Oregon</ENT>
            <ENT>5.0</ENT>
            <ENT>5.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42001</ENT>
            <ENT>Adams County; Gettysburg, PA Micro Area; Pennsylvania</ENT>
            <ENT>1.7</ENT>
            <ENT>3.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42005</ENT>
            <ENT>Armstrong County; Pittsburgh, PA Metro Area; Pennsylvania</ENT>
            <ENT>4.0</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42009</ENT>
            <ENT>Bedford County, Pennsylvania</ENT>
            <ENT>3.8</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42011</ENT>
            <ENT>Berks County; Reading, PA Metro Area; Pennsylvania</ENT>
            <ENT>6.1</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42013</ENT>
            <ENT>Blair County; Altoona, PA Metro Area; Pennsylvania</ENT>
            <ENT>5.8</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42017</ENT>
            <ENT>Bucks County; Philadelphia-Camden-Wilmington, PA-NJ-DE-MD Metro Area; Pennsylvania</ENT>
            <ENT>8.2</ENT>
            <ENT>4.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42019</ENT>
            <ENT>Butler County; Pittsburgh, PA Metro Area; Pennsylvania</ENT>
            <ENT>5.6</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42027</ENT>
            <ENT>Centre County; State College, PA Metro Area; Pennsylvania</ENT>
            <ENT>2.4</ENT>
            <ENT>3.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42029</ENT>
            <ENT>Chester County; Philadelphia-Camden-Wilmington, PA-NJ-DE-MD Metro Area; Pennsylvania</ENT>
            <ENT>5.4</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42031</ENT>
            <ENT>Clarion County, Pennsylvania</ENT>
            <ENT>8.2</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42033</ENT>
            <ENT>Clearfield County; DuBois, PA Micro Area; Pennsylvania</ENT>
            <ENT>5.5</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42035</ENT>
            <ENT>Clinton County; Lock Haven, PA Micro Area; Pennsylvania</ENT>
            <ENT>2.4</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42037</ENT>
            <ENT>Columbia County; Bloomsburg-Berwick, PA Micro Area; Pennsylvania</ENT>
            <ENT>5.5</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42041</ENT>
            <ENT>Cumberland County; Harrisburg-Carlisle, PA Metro Area; Pennsylvania</ENT>
            <ENT>3.0</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42045</ENT>
            <ENT>Delaware County; Philadelphia-Camden-Wilmington, PA-NJ-DE-MD Metro Area; Pennsylvania</ENT>
            <ENT>7.3</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42053</ENT>
            <ENT>Forest County, Pennsylvania</ENT>
            <ENT>3.3</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42055</ENT>
            <ENT>Franklin County; Chambersburg, PA Micro Area; Pennsylvania</ENT>
            <ENT>4.5</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42057</ENT>
            <ENT>Fulton County, Pennsylvania</ENT>
            <ENT>2.0</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42061</ENT>
            <ENT>Huntingdon County; Huntingdon, PA Micro Area; Pennsylvania</ENT>
            <ENT>8.1</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="1241"/>
            <ENT I="01">42065</ENT>
            <ENT>Jefferson County, Pennsylvania</ENT>
            <ENT>4.2</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42067</ENT>
            <ENT>Juniata County, Pennsylvania</ENT>
            <ENT>2.4</ENT>
            <ENT>5.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42071</ENT>
            <ENT>Lancaster County; Lancaster, PA Metro Area; Pennsylvania</ENT>
            <ENT>4.2</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42075</ENT>
            <ENT>Lebanon County; Lebanon, PA Metro Area; Pennsylvania</ENT>
            <ENT>3.6</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42077</ENT>
            <ENT>Lehigh County; Allentown-Bethlehem-Easton, PA-NJ Metro Area; Pennsylvania</ENT>
            <ENT>4.9</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42085</ENT>
            <ENT>Mercer County; Youngstown-Warren-Boardman, OH-PA Metro Area; Pennsylvania</ENT>
            <ENT>7.9</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42089</ENT>
            <ENT>Monroe County; East Stroudsburg, PA Micro Area; Pennsylvania</ENT>
            <ENT>4.9</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42091</ENT>
            <ENT>Montgomery County; Philadelphia-Camden-Wilmington, PA-NJ-DE-MD Metro Area; Pennsylvania</ENT>
            <ENT>6.4</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42095</ENT>
            <ENT>Northampton County; Allentown-Bethlehem-Easton, PA-NJ Metro Area; Pennsylvania</ENT>
            <ENT>5.2</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42103</ENT>
            <ENT>Pike County; New York-Northern New Jersey-Long Island, NY-NJ-PA Metro Area; Pennsylvania</ENT>
            <ENT>5.8</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42105</ENT>
            <ENT>Potter County, Pennsylvania</ENT>
            <ENT>5.7</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42109</ENT>
            <ENT>Snyder County; Selinsgrove, PA Micro Area; Pennsylvania</ENT>
            <ENT>2.0</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42111</ENT>
            <ENT>Somerset County; Somerset, PA Micro Area; Pennsylvania</ENT>
            <ENT>5.7</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42115</ENT>
            <ENT>Susquehanna County, Pennsylvania</ENT>
            <ENT>2.7</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42117</ENT>
            <ENT>Tioga County, Pennsylvania</ENT>
            <ENT>3.6</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42119</ENT>
            <ENT>Union County; Lewisburg, PA Micro Area; Pennsylvania</ENT>
            <ENT>3.6</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42121</ENT>
            <ENT>Venango County; Oil City, PA Micro Area; Pennsylvania</ENT>
            <ENT>3.7</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42127</ENT>
            <ENT>Wayne County, Pennsylvania</ENT>
            <ENT>3.7</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">42131</ENT>
            <ENT>Wyoming County; Scranton-Wilkes-Barre, PA Metro Area; Pennsylvania</ENT>
            <ENT>1.0</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">44001</ENT>
            <ENT>Bristol County; Providence-New Bedford-Fall River, RI-MA Metro Area; Rhode Island</ENT>
            <ENT>2.8</ENT>
            <ENT>4.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">44003</ENT>
            <ENT>Kent County; Providence-New Bedford-Fall River, RI-MA Metro Area; Rhode Island</ENT>
            <ENT>5.1</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">44005</ENT>
            <ENT>Newport County; Providence-New Bedford-Fall River, RI-MA Metro Area; Rhode Island</ENT>
            <ENT>6.4</ENT>
            <ENT>5.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">44007</ENT>
            <ENT>Providence County; Providence-New Bedford-Fall River, RI-MA Metro Area; Rhode Island</ENT>
            <ENT>7.7</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">45005</ENT>
            <ENT>Allendale County, South Carolina</ENT>
            <ENT>7.4</ENT>
            <ENT>4.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">45017</ENT>
            <ENT>Calhoun County; Columbia, SC Metro Area; South Carolina</ENT>
            <ENT>1.8</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">45039</ENT>
            <ENT>Fairfield County; Columbia, SC Metro Area; South Carolina</ENT>
            <ENT>7.5</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">45065</ENT>
            <ENT>McCormick County, South Carolina</ENT>
            <ENT>6.5</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">45081</ENT>
            <ENT>Saluda County; Columbia, SC Metro Area; South Carolina</ENT>
            <ENT>6.8</ENT>
            <ENT>5.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">45089</ENT>
            <ENT>Williamsburg County, South Carolina</ENT>
            <ENT>2.9</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">46011</ENT>
            <ENT>Brookings County; Brookings, SD Micro Area; South Dakota</ENT>
            <ENT>4.8</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">46015</ENT>
            <ENT>Brule County, South Dakota</ENT>
            <ENT>2.7</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">46017</ENT>
            <ENT>Buffalo County, South Dakota</ENT>
            <ENT>N/A</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">46031</ENT>
            <ENT>Corson County, South Dakota</ENT>
            <ENT>3.5</ENT>
            <ENT>4.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">46033</ENT>
            <ENT>Custer County, South Dakota</ENT>
            <ENT>8.2</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">46049</ENT>
            <ENT>Faulk County, South Dakota</ENT>
            <ENT>4.1</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">46059</ENT>
            <ENT>Hand County, South Dakota</ENT>
            <ENT>3.7</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">46067</ENT>
            <ENT>Hutchinson County, South Dakota</ENT>
            <ENT>6.0</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">46079</ENT>
            <ENT>Lake County, South Dakota</ENT>
            <ENT>5.8</ENT>
            <ENT>3.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">46099</ENT>
            <ENT>Minnehaha County; Sioux Falls, SD Metro Area; South Dakota</ENT>
            <ENT>7.7</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">46103</ENT>
            <ENT>Pennington County; Rapid City, SD Metro Area; South Dakota</ENT>
            <ENT>6.7</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">46109</ENT>
            <ENT>Roberts County, South Dakota</ENT>
            <ENT>5.2</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">46111</ENT>
            <ENT>Sanborn County, South Dakota</ENT>
            <ENT>3.2</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">46113</ENT>
            <ENT>Shannon County, South Dakota</ENT>
            <ENT>1.1</ENT>
            <ENT>0.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">46121</ENT>
            <ENT>Todd County, South Dakota</ENT>
            <ENT>8.1</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">47003</ENT>
            <ENT>Bedford County; Shelbyville, TN Micro Area; Tennessee</ENT>
            <ENT>4.7</ENT>
            <ENT>6.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">47021</ENT>
            <ENT>Cheatham County; Nashville-Davidson—Murfreesboro—Franklin, TN Metro Area; Tennessee</ENT>
            <ENT>3.9</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">47047</ENT>
            <ENT>Fayette County; Memphis, TN-MS-AR Metro Area; Tennessee</ENT>
            <ENT>6.4</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">47127</ENT>
            <ENT>Moore County; Tullahoma, TN Micro Area; Tennessee</ENT>
            <ENT>4.4</ENT>
            <ENT>3.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">47147</ENT>
            <ENT>Robertson County; Nashville-Davidson—Murfreesboro—Franklin, TN Metro Area; Tennessee</ENT>
            <ENT>7.4</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">47171</ENT>
            <ENT>Unicoi County; Johnson City, TN Metro Area; Tennessee</ENT>
            <ENT>8.1</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">47175</ENT>
            <ENT>Van Buren County, Tennessee</ENT>
            <ENT>5.9</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48013</ENT>
            <ENT>Atascosa County; San Antonio, TX Metro Area; Texas</ENT>
            <ENT>5.7</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48015</ENT>
            <ENT>Austin County; Houston-Sugar Land-Baytown, TX Metro Area; Texas</ENT>
            <ENT>8.5</ENT>
            <ENT>3.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48033</ENT>
            <ENT>Borden County, Texas</ENT>
            <ENT>N/A</ENT>
            <ENT>N/A</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48035</ENT>
            <ENT>Bosque County, Texas</ENT>
            <ENT>7.0</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48041</ENT>
            <ENT>Brazos County; College Station-Bryan, TX Metro Area; Texas</ENT>
            <ENT>7.7</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48053</ENT>
            <ENT>Burnet County, Texas</ENT>
            <ENT>4.9</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48055</ENT>
            <ENT>Caldwell County; Austin-Round Rock, TX Metro Area; Texas</ENT>
            <ENT>3.8</ENT>
            <ENT>4.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48095</ENT>
            <ENT>Concho County, Texas</ENT>
            <ENT>1.7</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48097</ENT>
            <ENT>Cooke County; Gainesville, TX Micro Area; Texas</ENT>
            <ENT>5.8</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48119</ENT>
            <ENT>Delta County; Dallas-Fort Worth-Arlington, TX Metro Area; Texas</ENT>
            <ENT>1.0</ENT>
            <ENT>6.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48123</ENT>
            <ENT>DeWitt County, Texas</ENT>
            <ENT>7.1</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="1242"/>
            <ENT I="01">48137</ENT>
            <ENT>Edwards County, Texas</ENT>
            <ENT>2.7</ENT>
            <ENT>4.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48139</ENT>
            <ENT>Ellis County; Dallas-Fort Worth-Arlington, TX Metro Area; Texas</ENT>
            <ENT>6.9</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48157</ENT>
            <ENT>Fort Bend County; Houston-Sugar Land-Baytown, TX Metro Area; Texas</ENT>
            <ENT>7.3</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48171</ENT>
            <ENT>Gillespie County; Fredericksburg, TX Micro Area; Texas</ENT>
            <ENT>1.5</ENT>
            <ENT>3.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48173</ENT>
            <ENT>Glasscock County, Texas</ENT>
            <ENT>N/A</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48205</ENT>
            <ENT>Hartley County, Texas</ENT>
            <ENT>1.1</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48209</ENT>
            <ENT>Hays County; Austin-Round Rock, TX Metro Area; Texas</ENT>
            <ENT>6.1</ENT>
            <ENT>4.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48225</ENT>
            <ENT>Houston County, Texas</ENT>
            <ENT>7.3</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48247</ENT>
            <ENT>Jim Hogg County, Texas</ENT>
            <ENT>5.9</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48251</ENT>
            <ENT>Johnson County; Dallas-Fort Worth-Arlington, TX Metro Area; Texas</ENT>
            <ENT>5.8</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48257</ENT>
            <ENT>Kaufman County; Dallas-Fort Worth-Arlington, TX Metro Area; Texas</ENT>
            <ENT>6.7</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48261</ENT>
            <ENT>Kenedy County; Kingsville, TX Micro Area; Texas</ENT>
            <ENT>N/A</ENT>
            <ENT>N/A</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48267</ENT>
            <ENT>Kimble County, Texas</ENT>
            <ENT>5.1</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48269</ENT>
            <ENT>King County, Texas</ENT>
            <ENT>N/A</ENT>
            <ENT>N/A</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48293</ENT>
            <ENT>Limestone County, Texas</ENT>
            <ENT>6.0</ENT>
            <ENT>6.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48301</ENT>
            <ENT>Loving County, Texas</ENT>
            <ENT>N/A</ENT>
            <ENT>N/A</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48305</ENT>
            <ENT>Lynn County, Texas</ENT>
            <ENT>N/A</ENT>
            <ENT>7.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48307</ENT>
            <ENT>McCulloch County, Texas</ENT>
            <ENT>0.5</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48327</ENT>
            <ENT>Menard County, Texas</ENT>
            <ENT>3.7</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48397</ENT>
            <ENT>Rockwall County; Dallas-Fort Worth-Arlington, TX Metro Area; Texas</ENT>
            <ENT>3.0</ENT>
            <ENT>6.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48421</ENT>
            <ENT>Sherman County, Texas</ENT>
            <ENT>5.5</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48425</ENT>
            <ENT>Somervell County; Granbury, TX Micro Area; Texas</ENT>
            <ENT>N/A</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48453</ENT>
            <ENT>Travis County; Austin-Round Rock, TX Metro Area; Texas</ENT>
            <ENT>8.1</ENT>
            <ENT>3.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48467</ENT>
            <ENT>Van Zandt County, Texas</ENT>
            <ENT>4.2</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48477</ENT>
            <ENT>Washington County; Brenham, TX Micro Area; Texas</ENT>
            <ENT>4.0</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48479</ENT>
            <ENT>Webb County; Laredo, TX Metro Area; Texas</ENT>
            <ENT>6.4</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48491</ENT>
            <ENT>Williamson County; Austin-Round Rock, TX Metro Area; Texas</ENT>
            <ENT>6.3</ENT>
            <ENT>3.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">48495</ENT>
            <ENT>Winkler County, Texas</ENT>
            <ENT>0.8</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">49005</ENT>
            <ENT>Cache County; Logan, UT-ID Metro Area; Utah</ENT>
            <ENT>4.8</ENT>
            <ENT>4.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">49009</ENT>
            <ENT>Daggett County, Utah</ENT>
            <ENT>3.7</ENT>
            <ENT>3.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">49011</ENT>
            <ENT>Davis County; Ogden-Clearfield, UT Metro Area; Utah</ENT>
            <ENT>6.5</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">49021</ENT>
            <ENT>Iron County; Cedar City, UT Micro Area; Utah</ENT>
            <ENT>6.8</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">49023</ENT>
            <ENT>Juab County; Provo-Orem, UT Metro Area; Utah</ENT>
            <ENT>3.4</ENT>
            <ENT>2.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">49027</ENT>
            <ENT>Millard County, Utah</ENT>
            <ENT>4.3</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">49031</ENT>
            <ENT>Piute County, Utah</ENT>
            <ENT>N/A</ENT>
            <ENT>4.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">49035</ENT>
            <ENT>Salt Lake County; Salt Lake City, UT Metro Area; Utah</ENT>
            <ENT>5.9</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">49047</ENT>
            <ENT>Uintah County; Vernal, UT Micro Area; Utah</ENT>
            <ENT>5.3</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">49049</ENT>
            <ENT>Utah County; Provo-Orem, UT Metro Area; Utah</ENT>
            <ENT>5.3</ENT>
            <ENT>3.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">50001</ENT>
            <ENT>Addison County, Vermont</ENT>
            <ENT>8.1</ENT>
            <ENT>3.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">50003</ENT>
            <ENT>Bennington County; Bennington, VT Micro Area; Vermont</ENT>
            <ENT>2.2</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">50005</ENT>
            <ENT>Caledonia County, Vermont</ENT>
            <ENT>6.9</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">50007</ENT>
            <ENT>Chittenden County; Burlington-South Burlington, VT Metro Area; Vermont</ENT>
            <ENT>3.8</ENT>
            <ENT>1.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">50011</ENT>
            <ENT>Franklin County; Burlington-South Burlington, VT Metro Area; Vermont</ENT>
            <ENT>5.4</ENT>
            <ENT>2.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">50013</ENT>
            <ENT>Grand Isle County; Burlington-South Burlington, VT Metro Area; Vermont</ENT>
            <ENT>4.6</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">50015</ENT>
            <ENT>Lamoille County, Vermont</ENT>
            <ENT>4.5</ENT>
            <ENT>2.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">50021</ENT>
            <ENT>Rutland County; Rutland, VT Micro Area; Vermont</ENT>
            <ENT>7.2</ENT>
            <ENT>4.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">50023</ENT>
            <ENT>Washington County; Barre, VT Micro Area; Vermont</ENT>
            <ENT>6.1</ENT>
            <ENT>3.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">50025</ENT>
            <ENT>Windham County, Vermont</ENT>
            <ENT>8.2</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">50027</ENT>
            <ENT>Windsor County; Lebanon, NH-VT Micro Area; Vermont</ENT>
            <ENT>6.7</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51003</ENT>
            <ENT>Albemarle County; Charlottesville, VA Metro Area; Virginia</ENT>
            <ENT>5.5</ENT>
            <ENT>3.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51005</ENT>
            <ENT>Alleghany County, Virginia</ENT>
            <ENT>3.1</ENT>
            <ENT>5.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51007</ENT>
            <ENT>Amelia County; Richmond, VA Metro Area; Virginia</ENT>
            <ENT>N/A</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51009</ENT>
            <ENT>Amherst County; Lynchburg, VA Metro Area; Virginia</ENT>
            <ENT>2.3</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51013</ENT>
            <ENT>Arlington County; Washington-Arlington-Alexandria, DC-VA-MD-WV Metro Area; Virginia</ENT>
            <ENT>6.6</ENT>
            <ENT>2.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51015</ENT>
            <ENT>Augusta County; Staunton-Waynesboro, VA Micro Area; Virginia</ENT>
            <ENT>6.0</ENT>
            <ENT>5.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51017</ENT>
            <ENT>Bath County, Virginia</ENT>
            <ENT>5.6</ENT>
            <ENT>2.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51019</ENT>
            <ENT>Bedford County; Lynchburg, VA Metro Area; Virginia</ENT>
            <ENT>6.9</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51021</ENT>
            <ENT>Bland County, Virginia</ENT>
            <ENT>3.8</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51025</ENT>
            <ENT>Brunswick County, Virginia</ENT>
            <ENT>1.7</ENT>
            <ENT>1.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51029</ENT>
            <ENT>Buckingham County, Virginia</ENT>
            <ENT>3.5</ENT>
            <ENT>3.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51031</ENT>
            <ENT>Campbell County; Lynchburg, VA Metro Area; Virginia</ENT>
            <ENT>4.6</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51033</ENT>
            <ENT>Caroline County; Richmond, VA Metro Area; Virginia</ENT>
            <ENT>8.1</ENT>
            <ENT>3.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51043</ENT>
            <ENT>Clarke County; Washington-Arlington-Alexandria, DC-VA-MD-WV Metro Area; Virginia</ENT>
            <ENT>7.1</ENT>
            <ENT>3.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51045</ENT>
            <ENT>Craig County; Roanoke, VA Metro Area; Virginia</ENT>
            <ENT>1.1</ENT>
            <ENT>3.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51047</ENT>
            <ENT>Culpeper County; Culpeper, VA Micro Area; Virginia</ENT>
            <ENT>7.4</ENT>
            <ENT>2.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51049</ENT>
            <ENT>Cumberland County; Richmond, VA Metro Area; Virginia</ENT>
            <ENT>N/A</ENT>
            <ENT>3.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51057</ENT>
            <ENT>Essex County, Virginia</ENT>
            <ENT>2.7</ENT>
            <ENT>3.0</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="1243"/>
            <ENT I="01">51059</ENT>
            <ENT>Fairfax County; Washington-Arlington-Alexandria, DC-VA-MD-WV Metro Area; Virginia</ENT>
            <ENT>5.0</ENT>
            <ENT>2.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51063</ENT>
            <ENT>Floyd County, Virginia</ENT>
            <ENT>7.8</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51065</ENT>
            <ENT>Fluvanna County; Charlottesville, VA Metro Area; Virginia</ENT>
            <ENT>3.8</ENT>
            <ENT>4.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51067</ENT>
            <ENT>Franklin County; Roanoke, VA Metro Area; Virginia</ENT>
            <ENT>6.4</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51069</ENT>
            <ENT>Frederick County; Winchester, VA-WV Metro Area; Virginia</ENT>
            <ENT>6.6</ENT>
            <ENT>5.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51073</ENT>
            <ENT>Gloucester County; Virginia Beach-Norfolk-Newport News, VA-NC Metro Area; Virginia</ENT>
            <ENT>2.5</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51075</ENT>
            <ENT>Goochland County; Richmond, VA Metro Area; Virginia</ENT>
            <ENT>6.0</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51079</ENT>
            <ENT>Greene County; Charlottesville, VA Metro Area; Virginia</ENT>
            <ENT>1.4</ENT>
            <ENT>3.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51081</ENT>
            <ENT>Greensville County, Virginia</ENT>
            <ENT>5.7</ENT>
            <ENT>3.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51083</ENT>
            <ENT>Halifax County, Virginia</ENT>
            <ENT>8.4</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51085</ENT>
            <ENT>Hanover County; Richmond, VA Metro Area; Virginia</ENT>
            <ENT>5.2</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51087</ENT>
            <ENT>Henrico County; Richmond, VA Metro Area; Virginia</ENT>
            <ENT>6.8</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51093</ENT>
            <ENT>Isle of Wight County; Virginia Beach-Norfolk-Newport News, VA-NC Metro Area; Virginia</ENT>
            <ENT>3.0</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51097</ENT>
            <ENT>King and Queen County; Richmond, VA Metro Area; Virginia</ENT>
            <ENT>2.7</ENT>
            <ENT>2.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51101</ENT>
            <ENT>King William County; Richmond, VA Metro Area; Virginia</ENT>
            <ENT>3.2</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51103</ENT>
            <ENT>Lancaster County, Virginia</ENT>
            <ENT>1.8</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51109</ENT>
            <ENT>Louisa County; Richmond, VA Metro Area; Virginia</ENT>
            <ENT>3.9</ENT>
            <ENT>3.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51111</ENT>
            <ENT>Lunenburg County, Virginia</ENT>
            <ENT>7.4</ENT>
            <ENT>4.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51113</ENT>
            <ENT>Madison County, Virginia</ENT>
            <ENT>4.7</ENT>
            <ENT>3.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51115</ENT>
            <ENT>Mathews County; Virginia Beach-Norfolk-Newport News, VA-NC Metro Area; Virginia</ENT>
            <ENT>N/A</ENT>
            <ENT>4.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51119</ENT>
            <ENT>Middlesex County, Virginia</ENT>
            <ENT>7.8</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51121</ENT>
            <ENT>Montgomery County; Blacksburg-Christiansburg-Radford, VA Metro Area; Virginia</ENT>
            <ENT>4.9</ENT>
            <ENT>3.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51125</ENT>
            <ENT>Nelson County; Charlottesville, VA Metro Area; Virginia</ENT>
            <ENT>7.6</ENT>
            <ENT>3.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51127</ENT>
            <ENT>New Kent County; Richmond, VA Metro Area; Virginia</ENT>
            <ENT>N/A</ENT>
            <ENT>2.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51131</ENT>
            <ENT>Northampton County, Virginia</ENT>
            <ENT>3.8</ENT>
            <ENT>4.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51133</ENT>
            <ENT>Northumberland County, Virginia</ENT>
            <ENT>N/A</ENT>
            <ENT>3.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51135</ENT>
            <ENT>Nottoway County, Virginia</ENT>
            <ENT>3.0</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51139</ENT>
            <ENT>Page County, Virginia</ENT>
            <ENT>3.6</ENT>
            <ENT>4.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51149</ENT>
            <ENT>Prince George County; Richmond, VA Metro Area; Virginia</ENT>
            <ENT>4.8</ENT>
            <ENT>4.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51153</ENT>
            <ENT>Prince William County; Washington-Arlington-Alexandria, DC-VA-MD-WV Metro Area; Virginia</ENT>
            <ENT>8.3</ENT>
            <ENT>3.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51155</ENT>
            <ENT>Pulaski County; Blacksburg-Christiansburg-Radford, VA Metro Area; Virginia</ENT>
            <ENT>6.3</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51157</ENT>
            <ENT>Rappahannock County, Virginia</ENT>
            <ENT>N/A</ENT>
            <ENT>3.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51159</ENT>
            <ENT>Richmond County, Virginia</ENT>
            <ENT>2.1</ENT>
            <ENT>3.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51161</ENT>
            <ENT>Roanoke County; Roanoke, VA Metro Area; Virginia</ENT>
            <ENT>6.4</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51165</ENT>
            <ENT>Rockingham County; Harrisonburg, VA Metro Area; Virginia</ENT>
            <ENT>2.3</ENT>
            <ENT>4.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51171</ENT>
            <ENT>Shenandoah County, Virginia</ENT>
            <ENT>6.3</ENT>
            <ENT>4.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51183</ENT>
            <ENT>Sussex County; Richmond, VA Metro Area; Virginia</ENT>
            <ENT>1.5</ENT>
            <ENT>4.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51187</ENT>
            <ENT>Warren County; Washington-Arlington-Alexandria, DC-VA-MD-WV Metro Area; Virginia</ENT>
            <ENT>7.9</ENT>
            <ENT>3.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51191</ENT>
            <ENT>Washington County; Kingsport-Bristol-Bristol, TN-VA Metro Area; Virginia</ENT>
            <ENT>6.1</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51193</ENT>
            <ENT>Westmoreland County, Virginia</ENT>
            <ENT>1.2</ENT>
            <ENT>4.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51199</ENT>
            <ENT>York County; Virginia Beach-Norfolk-Newport News, VA-NC Metro Area; Virginia</ENT>
            <ENT>4.8</ENT>
            <ENT>3.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51510</ENT>
            <ENT>Alexandria city; Washington-Arlington-Alexandria, DC-VA-MD-WV Metro Area; Virginia</ENT>
            <ENT>5.6</ENT>
            <ENT>2.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51515</ENT>
            <ENT>Bedford city; Lynchburg, VA Metro Area; Virginia</ENT>
            <ENT>N/A</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51530</ENT>
            <ENT>Buena Vista city, Virginia</ENT>
            <ENT>2.1</ENT>
            <ENT>3.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51540</ENT>
            <ENT>Charlottesville city; Charlottesville, VA Metro Area; Virginia</ENT>
            <ENT>6.1</ENT>
            <ENT>2.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51550</ENT>
            <ENT>Chesapeake city; Virginia Beach-Norfolk-Newport News, VA-NC Metro Area; Virginia</ENT>
            <ENT>1.6</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51595</ENT>
            <ENT>Emporia city, Virginia</ENT>
            <ENT>5.4</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51600</ENT>
            <ENT>Fairfax city; Washington-Arlington-Alexandria, DC-VA-MD-WV Metro Area; Virginia</ENT>
            <ENT>N/A</ENT>
            <ENT>1.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51610</ENT>
            <ENT>Falls Church city; Washington-Arlington-Alexandria, DC-VA-MD-WV Metro Area; Virginia</ENT>
            <ENT>4.6</ENT>
            <ENT>3.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51650</ENT>
            <ENT>Hampton city; Virginia Beach-Norfolk-Newport News, VA-NC Metro Area; Virginia</ENT>
            <ENT>7.7</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51660</ENT>
            <ENT>Harrisonburg city; Harrisonburg, VA Metro Area; Virginia</ENT>
            <ENT>4.0</ENT>
            <ENT>3.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51678</ENT>
            <ENT>Lexington city, Virginia</ENT>
            <ENT>N/A</ENT>
            <ENT>3.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51700</ENT>
            <ENT>Newport News city; Virginia Beach-Norfolk-Newport News, VA-NC Metro Area; Virginia</ENT>
            <ENT>6.6</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51735</ENT>
            <ENT>Poquoson city; Virginia Beach-Norfolk-Newport News, VA-NC Metro Area; Virginia</ENT>
            <ENT>5.2</ENT>
            <ENT>0.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51740</ENT>
            <ENT>Portsmouth city; Virginia Beach-Norfolk-Newport News, VA-NC Metro Area; Virginia</ENT>
            <ENT>4.6</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51750</ENT>
            <ENT>Radford city; Blacksburg-Christiansburg-Radford, VA Metro Area; Virginia</ENT>
            <ENT>2.5</ENT>
            <ENT>6.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51760</ENT>
            <ENT>Richmond city; Richmond, VA Metro Area; Virginia</ENT>
            <ENT>7.2</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51770</ENT>
            <ENT>Roanoke city; Roanoke, VA Metro Area; Virginia</ENT>
            <ENT>5.4</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51800</ENT>
            <ENT>Suffolk city; Virginia Beach-Norfolk-Newport News, VA-NC Metro Area; Virginia</ENT>
            <ENT>5.0</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51810</ENT>
            <ENT>Virginia Beach city; Virginia Beach-Norfolk-Newport News, VA-NC Metro Area; Virginia</ENT>
            <ENT>5.2</ENT>
            <ENT>4.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">51820</ENT>
            <ENT>Waynesboro city; Staunton-Waynesboro, VA Micro Area; Virginia</ENT>
            <ENT>6.5</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="1244"/>
            <ENT I="01">51830</ENT>
            <ENT>Williamsburg city; Virginia Beach-Norfolk-Newport News, VA-NC Metro Area; Virginia</ENT>
            <ENT>8.6</ENT>
            <ENT>2.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53007</ENT>
            <ENT>Chelan County; Wenatchee-East Wenatchee, WA Metro Area; Washington</ENT>
            <ENT>7.3</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53011</ENT>
            <ENT>Clark County; Portland-Vancouver-Beaverton, OR-WA Metro Area; Washington</ENT>
            <ENT>5.3</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53029</ENT>
            <ENT>Island County; Oak Harbor, WA Micro Area; Washington</ENT>
            <ENT>6.1</ENT>
            <ENT>4.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53031</ENT>
            <ENT>Jefferson County, Washington</ENT>
            <ENT>3.0</ENT>
            <ENT>5.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53033</ENT>
            <ENT>King County; Seattle-Tacoma-Bellevue, WA Metro Area; Washington</ENT>
            <ENT>4.8</ENT>
            <ENT>4.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53035</ENT>
            <ENT>Kitsap County; Bremerton-Silverdale, WA Metro Area; Washington</ENT>
            <ENT>6.2</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53037</ENT>
            <ENT>Kittitas County; Ellensburg, WA Micro Area; Washington</ENT>
            <ENT>3.7</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53043</ENT>
            <ENT>Lincoln County, Washington</ENT>
            <ENT>1.5</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53045</ENT>
            <ENT>Mason County; Shelton, WA Micro Area; Washington</ENT>
            <ENT>5.0</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53053</ENT>
            <ENT>Pierce County; Seattle-Tacoma-Bellevue, WA Metro Area; Washington</ENT>
            <ENT>6.4</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53055</ENT>
            <ENT>San Juan County, Washington</ENT>
            <ENT>5.8</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53057</ENT>
            <ENT>Skagit County; Mount Vernon-Anacortes, WA Metro Area; Washington</ENT>
            <ENT>4.2</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53059</ENT>
            <ENT>Skamania County; Portland-Vancouver-Beaverton, OR-WA Metro Area; Washington</ENT>
            <ENT>0.4</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53061</ENT>
            <ENT>Snohomish County; Seattle-Tacoma-Bellevue, WA Metro Area; Washington</ENT>
            <ENT>4.7</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53065</ENT>
            <ENT>Stevens County, Washington</ENT>
            <ENT>6.9</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53067</ENT>
            <ENT>Thurston County; Olympia, WA Metro Area; Washington</ENT>
            <ENT>4.1</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53069</ENT>
            <ENT>Wahkiakum County, Washington</ENT>
            <ENT>N/A</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">53073</ENT>
            <ENT>Whatcom County; Bellingham, WA Metro Area; Washington</ENT>
            <ENT>2.7</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">54001</ENT>
            <ENT>Barbour County, West Virginia</ENT>
            <ENT>5.1</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">54003</ENT>
            <ENT>Berkeley County; Hagerstown-Martinsburg, MD-WV Metro Area; West Virginia</ENT>
            <ENT>5.8</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">54013</ENT>
            <ENT>Calhoun County, West Virginia</ENT>
            <ENT>6.5</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">54017</ENT>
            <ENT>Doddridge County; Clarksburg, WV Micro Area; West Virginia</ENT>
            <ENT>0.9</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">54027</ENT>
            <ENT>Hampshire County; Winchester, VA-WV Metro Area; West Virginia</ENT>
            <ENT>3.9</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">54037</ENT>
            <ENT>Jefferson County; Washington-Arlington-Alexandria, DC-VA-MD-WV Metro Area; West Virginia</ENT>
            <ENT>7.1</ENT>
            <ENT>4.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">54041</ENT>
            <ENT>Lewis County, West Virginia</ENT>
            <ENT>3.1</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">54043</ENT>
            <ENT>Lincoln County; Charleston, WV Metro Area; West Virginia</ENT>
            <ENT>1.9</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">54051</ENT>
            <ENT>Marshall County; Wheeling, WV-OH Metro Area; West Virginia</ENT>
            <ENT>3.2</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">54071</ENT>
            <ENT>Pendleton County, West Virginia</ENT>
            <ENT>2.7</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">54083</ENT>
            <ENT>Randolph County, West Virginia</ENT>
            <ENT>6.4</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">54085</ENT>
            <ENT>Ritchie County, West Virginia</ENT>
            <ENT>6.0</ENT>
            <ENT>5.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">54087</ENT>
            <ENT>Roane County, West Virginia</ENT>
            <ENT>2.1</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">54095</ENT>
            <ENT>Tyler County, West Virginia</ENT>
            <ENT>3.9</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">54101</ENT>
            <ENT>Webster County, West Virginia</ENT>
            <ENT>8.3</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">54109</ENT>
            <ENT>Wyoming County, West Virginia</ENT>
            <ENT>1.1</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55001</ENT>
            <ENT>Adams County, Wisconsin</ENT>
            <ENT>5.7</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55003</ENT>
            <ENT>Ashland County, Wisconsin</ENT>
            <ENT>8.0</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55005</ENT>
            <ENT>Barron County, Wisconsin</ENT>
            <ENT>4.5</ENT>
            <ENT>4.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55007</ENT>
            <ENT>Bayfield County, Wisconsin</ENT>
            <ENT>5.0</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55009</ENT>
            <ENT>Brown County; Green Bay, WI Metro Area; Wisconsin</ENT>
            <ENT>6.5</ENT>
            <ENT>4.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55013</ENT>
            <ENT>Burnett County, Wisconsin</ENT>
            <ENT>4.5</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55017</ENT>
            <ENT>Chippewa County; Eau Claire, WI Metro Area; Wisconsin</ENT>
            <ENT>4.5</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55019</ENT>
            <ENT>Clark County, Wisconsin</ENT>
            <ENT>7.1</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55021</ENT>
            <ENT>Columbia County; Madison, WI Metro Area; Wisconsin</ENT>
            <ENT>8.2</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55025</ENT>
            <ENT>Dane County; Madison, WI Metro Area; Wisconsin</ENT>
            <ENT>7.0</ENT>
            <ENT>4.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55031</ENT>
            <ENT>Douglas County; Duluth, MN-WI Metro Area; Wisconsin</ENT>
            <ENT>7.5</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55035</ENT>
            <ENT>Eau Claire County; Eau Claire, WI Metro Area; Wisconsin</ENT>
            <ENT>4.0</ENT>
            <ENT>3.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55037</ENT>
            <ENT>Florence County; Iron Mountain, MI-WI Micro Area; Wisconsin</ENT>
            <ENT>7.7</ENT>
            <ENT>5.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55055</ENT>
            <ENT>Jefferson County; Watertown-Fort Atkinson, WI Micro Area; Wisconsin</ENT>
            <ENT>6.6</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55061</ENT>
            <ENT>Kewaunee County; Green Bay, WI Metro Area; Wisconsin</ENT>
            <ENT>2.6</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55063</ENT>
            <ENT>La Crosse County; La Crosse, WI-MN Metro Area; Wisconsin</ENT>
            <ENT>3.1</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55077</ENT>
            <ENT>Marquette County, Wisconsin</ENT>
            <ENT>3.1</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55079</ENT>
            <ENT>Milwaukee County; Milwaukee-Waukesha-West Allis, WI Metro Area; Wisconsin</ENT>
            <ENT>4.8</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55081</ENT>
            <ENT>Monroe County, Wisconsin</ENT>
            <ENT>5.2</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55083</ENT>
            <ENT>Oconto County; Green Bay, WI Metro Area; Wisconsin</ENT>
            <ENT>4.9</ENT>
            <ENT>5.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55087</ENT>
            <ENT>Outagamie County; Appleton, WI Metro Area; Wisconsin</ENT>
            <ENT>5.1</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55089</ENT>
            <ENT>Ozaukee County; Milwaukee-Waukesha-West Allis, WI Metro Area; Wisconsin</ENT>
            <ENT>8.3</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55093</ENT>
            <ENT>Pierce County; Minneapolis-St. Paul-Bloomington, MN-WI Metro Area; Wisconsin</ENT>
            <ENT>3.5</ENT>
            <ENT>3.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55097</ENT>
            <ENT>Portage County; Stevens Point, WI Micro Area; Wisconsin</ENT>
            <ENT>4.3</ENT>
            <ENT>4.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55101</ENT>
            <ENT>Racine County; Racine, WI Metro Area; Wisconsin</ENT>
            <ENT>6.0</ENT>
            <ENT>7.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55107</ENT>
            <ENT>Rusk County, Wisconsin</ENT>
            <ENT>3.3</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55109</ENT>
            <ENT>St. Croix County; Minneapolis-St. Paul-Bloomington, MN-WI Metro Area; Wisconsin</ENT>
            <ENT>4.2</ENT>
            <ENT>3.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55113</ENT>
            <ENT>Sawyer County, Wisconsin</ENT>
            <ENT>1.6</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55115</ENT>
            <ENT>Shawano County, Wisconsin</ENT>
            <ENT>5.9</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55117</ENT>
            <ENT>Sheboygan County; Sheboygan, WI Metro Area; Wisconsin</ENT>
            <ENT>6.8</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55119</ENT>
            <ENT>Taylor County, Wisconsin</ENT>
            <ENT>6.7</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55123</ENT>
            <ENT>Vernon County, Wisconsin</ENT>
            <ENT>6.8</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <PRTPAGE P="1245"/>
            <ENT I="01">55127</ENT>
            <ENT>Walworth County; Whitewater, WI Micro Area; Wisconsin</ENT>
            <ENT>7.9</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55131</ENT>
            <ENT>Washington County; Milwaukee-Waukesha-West Allis, WI Metro Area; Wisconsin</ENT>
            <ENT>3.8</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55133</ENT>
            <ENT>Waukesha County; Milwaukee-Waukesha-West Allis, WI Metro Area; Wisconsin</ENT>
            <ENT>4.6</ENT>
            <ENT>5.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55137</ENT>
            <ENT>Waushara County, Wisconsin</ENT>
            <ENT>3.3</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55139</ENT>
            <ENT>Winnebago County; Oshkosh-Neenah, WI Metro Area; Wisconsin</ENT>
            <ENT>7.5</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">55141</ENT>
            <ENT>Wood County; Marshfield-Wisconsin Rapids, WI Micro Area; Wisconsin</ENT>
            <ENT>6.6</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">56001</ENT>
            <ENT>Albany County; Laramie, WY Micro Area; Wyoming</ENT>
            <ENT>7.4</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">56005</ENT>
            <ENT>Campbell County; Gillette, WY Micro Area; Wyoming</ENT>
            <ENT>5.3</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">56019</ENT>
            <ENT>Johnson County, Wyoming</ENT>
            <ENT>1.4</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">56033</ENT>
            <ENT>Sheridan County; Sheridan, WY Micro Area; Wyoming</ENT>
            <ENT>3.6</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72003</ENT>
            <ENT>Aguada Municipio; Aguadilla-Isabela-San Sebastián, PR Metro Area; Puerto Rico</ENT>
            <ENT>N/A</ENT>
            <ENT>6.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72005</ENT>
            <ENT>Aguadilla Municipio; Aguadilla-Isabela-San Sebastián, PR Metro Area; Puerto Rico</ENT>
            <ENT>4.3</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72007</ENT>
            <ENT>Aguas Buenas Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>2.2</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72015</ENT>
            <ENT>Arroyo Municipio; Guayama, PR Metro Area; Puerto Rico</ENT>
            <ENT>2.5</ENT>
            <ENT>3.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72017</ENT>
            <ENT>Barceloneta Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>4.7</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72019</ENT>
            <ENT>Barranquitas Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>1.0</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72025</ENT>
            <ENT>Caguas Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>2.5</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72029</ENT>
            <ENT>Canovanas Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>2.1</ENT>
            <ENT>6.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72031</ENT>
            <ENT>Carolina Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>4.4</ENT>
            <ENT>7.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72033</ENT>
            <ENT>Cataño Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>3.6</ENT>
            <ENT>5.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72035</ENT>
            <ENT>Cayey Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>4.1</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72037</ENT>
            <ENT>Ceiba Municipio; Fajardo, PR Metro Area; Puerto Rico</ENT>
            <ENT>1.6</ENT>
            <ENT>6.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72039</ENT>
            <ENT>Ciales Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>N/A</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72041</ENT>
            <ENT>Cidra Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>N/A</ENT>
            <ENT>5.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72043</ENT>
            <ENT>Coamo Municipio; Coamo, PR Micro Area; Puerto Rico</ENT>
            <ENT>N/A</ENT>
            <ENT>5.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72047</ENT>
            <ENT>Corozal Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>1.2</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72057</ENT>
            <ENT>Guayama Municipio; Guayama, PR Metro Area; Puerto Rico</ENT>
            <ENT>3.9</ENT>
            <ENT>5.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72059</ENT>
            <ENT>Guayanilla Municipio; Yauco, PR Metro Area; Puerto Rico</ENT>
            <ENT>2.2</ENT>
            <ENT>5.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72061</ENT>
            <ENT>Guaynabo Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>2.0</ENT>
            <ENT>6.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72063</ENT>
            <ENT>Gurabo Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>6.7</ENT>
            <ENT>3.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72065</ENT>
            <ENT>Hatillo Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>6.0</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72071</ENT>
            <ENT>Isabela Municipio; Aguadilla-Isabela-San Sebastián, PR Metro Area; Puerto Rico</ENT>
            <ENT>2.2</ENT>
            <ENT>6.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72073</ENT>
            <ENT>Jayuya Municipio; Jayuya, PR Micro Area; Puerto Rico</ENT>
            <ENT>N/A</ENT>
            <ENT>2.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72075</ENT>
            <ENT>Juana Díaz Municipio; Ponce, PR Metro Area; Puerto Rico</ENT>
            <ENT>1.9</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72077</ENT>
            <ENT>Juncos Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>4.6</ENT>
            <ENT>4.9</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72087</ENT>
            <ENT>Lofza Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>1.3</ENT>
            <ENT>4.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72093</ENT>
            <ENT>Maricao Municipio, Puerto Rico</ENT>
            <ENT>N/A</ENT>
            <ENT>4.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72095</ENT>
            <ENT>Maunabo Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>N/A</ENT>
            <ENT>1.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72101</ENT>
            <ENT>Morovis Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>2.3</ENT>
            <ENT>4.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72103</ENT>
            <ENT>Naguabo Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>6.4</ENT>
            <ENT>6.3</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72107</ENT>
            <ENT>Orocovis Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>0.6</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72111</ENT>
            <ENT>Peñuelas Municipio; Yauco, PR Metro Area; Puerto Rico</ENT>
            <ENT>1.9</ENT>
            <ENT>5.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72113</ENT>
            <ENT>Ponce Municipio; Ponce, PR Metro Area; Puerto Rico</ENT>
            <ENT>2.6</ENT>
            <ENT>4.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72115</ENT>
            <ENT>Quebradillas Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>2.4</ENT>
            <ENT>4.7</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72119</ENT>
            <ENT>Río Grande Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>4.0</ENT>
            <ENT>6.5</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72121</ENT>
            <ENT>Sabana Grande Municipio; San Germán-Cabo Rojo, PR Metro Area; Puerto Rico</ENT>
            <ENT>1.0</ENT>
            <ENT>5.1</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72123</ENT>
            <ENT>Salinas Municipio; Coamo, PR Micro Area; Puerto Rico</ENT>
            <ENT>1.8</ENT>
            <ENT>2.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72125</ENT>
            <ENT>San Germán Municipio; San Germán-Cabo Rojo, PR Metro Area; Puerto Rico</ENT>
            <ENT>1.9</ENT>
            <ENT>6.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72127</ENT>
            <ENT>San Juan Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>4.5</ENT>
            <ENT>6.2</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72133</ENT>
            <ENT>Santa Isabel Municipio; Santa Isabel, PR Micro Area; Puerto Rico</ENT>
            <ENT>N/A</ENT>
            <ENT>1.6</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72143</ENT>
            <ENT>Vega Alta Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>5.0</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72147</ENT>
            <ENT>Vieques Municipio, Puerto Rico</ENT>
            <ENT>8.4</ENT>
            <ENT>7.0</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72149</ENT>
            <ENT>Villalba Municipio; Ponce, PR Metro Area; Puerto Rico</ENT>
            <ENT>1.8</ENT>
            <ENT>4.4</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72151</ENT>
            <ENT>Yabucoa Municipio; San Juan-Caguas-Guaynabo, PR Metro Area; Puerto Rico</ENT>
            <ENT>3.8</ENT>
            <ENT>4.8</ENT>
          </ROW>
          <ROW>
            <ENT I="01">72153</ENT>
            <ENT>Yauco Municipio; Yauco, PR Metro Area; Puerto Rico</ENT>
            <ENT>2.0</ENT>
            <ENT>6.1</ENT>
          </ROW>
        </GPOTABLE>
        <NOTE>
          <PRTPAGE P="1246"/>
          <HD SOURCE="HED">Note:</HD>
          <P>A property meets the low-vacancy threshold if it is located in a county that was below the national rental vacancy rate for units affordable to low-income households in 2000 (7.3 percent) and was within the 80th percentile of low-income rental vacancy rates (8.7 percent) as measured by the 2009 5 year ACS (meaning that 80 percent of counties had a vacancy rate below 8.7 percent in the 2009 5 year ACS).</P>
        </NOTE>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00072 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4210-67-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
        <SUBAGY>Fish and Wildlife Service</SUBAGY>
        <DEPDOC>[FWS-R8-R-2012-N270; FXRS12610800000-134-FF08RSDC00]</DEPDOC>
        <SUBJECT>Otay River Estuary Restoration Project; South San Diego Bay Unit and Sweetwater Marsh Unit of the San Diego Bay National Wildlife Refuge, California; Intent To Prepare an Environmental Impact Statement</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>Fish and Wildlife Service, Interior.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice of intent; reinitiation of scoping and request for public comment.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>We, the U.S. Fish and Wildlife Service (Service), are reinitiating scoping with regard to the environmental impact statement (EIS) for the proposed Otay River Estuary Restoration Project. As originally proposed, the project involved the restoration of estuarine and salt marsh (subtidal and intertidal wetlands) habitats within the western terminus of the Otay River and a portion of the salt ponds in the San Diego Bay National Wildlife Refuge-South San Diego Bay Unit. Based on information developed since the original scoping period, the proposed project may now also include the restoration of a portion of the D Street Fill, located within the San Diego Bay National Wildlife Refuge-Sweetwater Marsh Unit. We originally published a notice of intent on November 14, 2011 (76 FR 70480), and scoping comments were accepted through January 12, 2012. Since then, we have expanded the Area of Potential Effect of the restoration project to include the salt ponds and D Street Fill within the San Diego Bay National Wildlife Refuge. This second notice advises the public that we intend to gather additional information through scoping regarding an EIS for the expanded project. We encourage the public and other agencies to participate in the NEPA scoping process by sending written suggestions and information on the issues and concerns that should be addressed in the draft EIS, including the range of alternatives, appropriate mitigation measures, and the nature and extent of potential environmental impacts. Comments submitted during the earlier scoping period do not need to be resubmitted.</P>
        </SUM>
        <DATES>
          <HD SOURCE="HED">DATES:</HD>
          <P>To ensure that we have adequate time to evaluate and incorporate suggestions and other input, we must receive your comments on or before February 8, 2013.</P>
        </DATES>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>
          <P>Send your comments or requests for more information by one of the following methods.</P>
          <P>
            <E T="03">Email: Otay_NOI@fws.gov.</E>Please include “Otay Estuary NOI” in the subject line of the message</P>
          <P>
            <E T="03">Fax:</E>Attn: Brian Collins, (619) 476-9149</P>
          <P>
            <E T="03">U.S. Mail:</E>Brian Collins, U.S. Fish and Wildlife Service, San Diego National Wildlife Refuge Complex, P.O. Box 2358, Chula Vista, CA 91912</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>Brian Collins, Refuge Manager (619-575-2704, extension 302), or Andrew Yuen, Project Leader (619-476-9150, extension 100).</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P/>
        <HD SOURCE="HD1">Background</HD>
        <P>In 2006, we completed a Comprehensive Conservation Plan (CCP) and EIS/Record of Decision (ROD) to guide the management of the San Diego Bay National Wildlife Refuge over a 15-year period (71 FR 64552, November 2, 2006). The wildlife and habitat management goal of the selected management alternative in the CCP for the South San Diego Bay Unit is to “Protect, manage, enhance, and restore * * * coastal wetlands * * * to benefit the native fish, wildlife, and plant species supported within the South San Diego Bay Unit.” One of the strategies identified to meet this goal is to restore native habitats in the Otay River floodplain and the salt ponds. The wildlife and habitat management goal of the selected alternative for the Sweetwater Marsh Unit is to “Protect, manage, enhance, and restore coastal wetland and upland habitats to benefit native fish, wildlife, and plant species within the Sweetwater Marsh Unit.” The proposed restoration project represents step-down restoration planning for the western portion of the Otay River floodplain, salt ponds, and D Street Fill. The site-specific EIS for this project will tier from the programmatic EIS and ROD prepared for the CCP. Funding for the proposed restoration is being provided by the Poseidon Resources Carlsbad Desalination Project to fulfill part of their mitigation requirement for the desalination project. On November 15, 2007, the California Coastal Commission (Commission) approved a Coastal Development Permit (CDP No. E-06-013) for the Poseidon desalination facility in Carlsbad, San Diego County. As part of that approval, the Commission required Poseidon to implement a Marine Life Mitigation Plan (MLMP).</P>
        <P>In early 2010, Poseidon submitted an initial proposal to the Commission identifying possible mitigation sites. The submittal compared about a dozen potential sites in the Southern California Bight and concluded that the Otay River floodplain portion of the San Diego Bay NWR was most suited to provide the type and amount of mitigation the MLMP required. Commission staff and members of the Commission's Scientific Advisory Panel reviewed Poseidon's analysis and concurred that the Otay River floodplain site was most likely to meet the MLMP requirements and objectives. Final site selection required approval by both the Commission and the San Diego Regional Water Quality Control Board (SDRWQCB). On February 9, 2011, the Commission unanimously approved the Otay River floodplain site, and the site was approved by the SDRWQCB on March 9, 2011. On October 15, 2012, the Commission's Executive Director approved an 18-month extension to Poseidon Resources to submit a Coastal Development Permit application based on the potential additional benefits of restoration or partial restoration of salt ponds as part of the Otay River Estuary Restoration Project. The MLMP requirements and objectives are consistent with the goals and objectives set forth in our CCP for the Otay River floodplain, salt ponds, and D Street Fill.</P>
        <P>Prior to implementation of the restoration project, the California Coastal Commission must approve a Coastal Development Permit (CDP) for the proposed restoration. In accordance with the California Environmental Quality Act, the CDP process is exempt from the requirement of preparing an environmental impact report. The Commission's staff report and findings related to the CDP application for the project will be the environmental analysis document prepared under the Commission's certified regulatory program. The Commission will allow sufficient opportunity during the CDP process for public review and comment.</P>
        <HD SOURCE="HD1">Proposed Project</HD>

        <P>We propose to convert disturbed uplands within the western portion of the Otay River floodplain and salt ponds<PRTPAGE P="1247"/>to functional estuarine and salt marsh habitats. We may also restore a portion of the D Street Fill to salt marsh habitat. Upland buffers to be provided around portions of the restored wetlands would be planted with native upland and wetland/upland transitional vegetation. The major goals of the project are to protect, manage, enhance, and restore open water coastal wetlands and native upland to benefit native fish, wildlife, and plant species supported within the South San Diego Bay Unit and Sweetwater Marsh Unit of the San Diego Bay NWR and to provide habitat for migratory shorebirds and other salt-marsh-dependent species.</P>
        <P>The uplands portion of the project site, which is located within the City of San Diego to the west of Interstate 5 between Main Street to the north and Palm Avenue to the south, is included entirely within an area managed by the Service as a National Wildlife Refuge. The eastern portion of the uplands site is owned by the Service in fee title, while the western portion is leased to the Service by the State Lands Commission. D Street Fill is located west of Interstate 5 and south of the Sweetwater River. The Salt Ponds are located west of Interstate 5 and south of the Chula Vista Marina.</P>
        <P>In order to restore estuarine habitat in the Otay River floodplain, we have initially estimated that approximately 75 acres would need to be graded to provide both the wetland and upland components of the proposed restoration. To achieve elevations appropriate for supporting the desired estuarine habitat types, excavation of 3 to 11 feet of soil over an area of approximately 65 acres would be required, generating an estimated 750,000 to 1 million cubic yards of material. The excavated soil may be used to create estuarine and salt marsh habitats in the salt ponds, with the remainder being transported off site to an approved disposal site. The proposed wetlands would be tidally connected to San Diego Bay, directly and through the existing Otay River channel. Additional grading to potentially deepen and widen the Otay River channel from the western edge of the project site out to the mouth of the river, and potentially dredging channels in the mudflats to increase tidal circulation to the adjacent restored salt ponds, may be needed pending hydraulic modeling. At the D Street Fill, material would be excavated and removed to restore historic salt marsh.</P>
        <HD SOURCE="HD1">Public Comment</HD>
        <P>We are furnishing this second notice in accordance with section 1501.7 of the NEPA implementing regulations, to obtain suggestions and information from other agencies and the public on the scope of issues to be addressed in the EIS. The Service is currently developing a range of restoration alternatives to be analyzed in the draft EIS, and we invite written comments from interested parties to ensure identification of the full range of alternatives, issues, and concerns. Information gathered through this scoping process will assist us in developing a range of alternatives. A detailed description of the proposed action and alternatives will be included in the EIS. The EIS will also address the direct, indirect, and cumulative impacts of the alternatives on environmental resources and identify appropriate mitigation measures for adverse environmental effects.</P>
        <P>Written comments we receive become part of the public record associated with this action. Before including your address, phone number, email address, or other personal identifying information in your comment, you should be aware that your entire comment, including your personal identifying information, may be made publicly available at any time. While you can ask us in your comment to withhold your personal identifying information from public review, we cannot guarantee that we will be able to do so.</P>

        <P>In addition to providing written comments, the public is encouraged to attend a public scoping meeting to provide us with suggestions and information on the scope of issues and alternatives to consider when drafting the EIS. A public scoping meeting will be held in San Diego County, California, in early 2013. We will mail a separate announcement to the public with the exact date, time, and location of the public scoping meeting. Requests to be contacted about the scoping meeting should be directed to the contact provided under<E T="02">ADDRESSES</E>above. We will accept both oral and written comments at the scoping meeting. Written comments previously provided in response to the November 2011 notice of intent and during the December 2011 scoping meeting are part of the public record and will be considered during our NEPA review. Comments submitted previously do not need to be resubmitted.</P>
        <HD SOURCE="HD1">NEPA Compliance</HD>

        <P>We will conduct environmental review in accordance with the requirements of NEPA, as amended (42 U.S.C. 4321<E T="03">et seq.</E>), its implementing regulations (40 CFR parts 1500-1508), other applicable regulations, and our procedures for compliance with those regulations. We anticipate that a draft EIS will be available for public review in the winter of 2014.</P>
        <SIG>
          <NAME>Alexandra Pitts,</NAME>
          <TITLE>Acting Regional Director, Pacific Southwest Region.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00134 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4310-55-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">INTERNATIONAL TRADE COMMISSION</AGENCY>
        <DEPDOC>[Inv. No. 337-TA-862]</DEPDOC>
        <SUBJECT>Certain Electronic Devices, Including Wireless Communication Devices, Tablet Computers, Media Players, and Televisions, and Components Thereof;Institution of Investigation Pursuant to United States Code</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>U.S. International Trade Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Notice is hereby given that a complaint was filed with the U.S. International Trade Commission on November 30, 2012, under section 337 of the Tariff Act of 1930, as amended, 19 U.S.C. 1337, on behalf of Ericsson Inc. of Plano, Texas and Telefonaktiebolaget LM Ericsson of Stockholm, Sweden. Letters supplementing the complaint were filed on December 3, December 12, and December 19, 2012. The complaint alleges violations of section 337 based upon the importation into the United States, the sale for importation, and the sale within the United States after importation of certain electronic devices, including wireless communication devices, tablet computers, media players, and televisions, and components thereof by reason of infringement of certain claims of U.S. Patent No. 6,029,052 (“the `052 patent”); U.S. Patent No. 6,058,359 (“the `359 patent”); U.S. Patent No. 6,278,888 (“the `888 patent”); U.S. Patent No. 6,301,556 (“the `556 patent”); U.S. Patent No. 6,418,310 (“the `310 patent”); U.S. Patent No. 6,445,917 (“the `917 patent”); U.S. Patent No. 6,473,506 (“the `506 patent”); U.S. Patent No. 6,519,223 (“the `223 patent”); U.S. Patent No. 6,624,832 (“the `832 patent”); U.S. Patent No. 6,772,215 (“the `215 patent”); and U.S. Patent No. 8,169,992 (“the `992 patent”). The complaint further alleges that an industry in the United States exists or is in the process of being established as required by subsection (a)(2) of section 337.</P>

          <P>The complainants request that the Commission institute an investigation and, after the investigation, issue an<PRTPAGE P="1248"/>exclusion order and a cease and desist order.</P>
        </SUM>
        <ADD>
          <HD SOURCE="HED">ADDRESSES:</HD>

          <P>The complaint, except for any confidential information contained therein, is available for inspection during official business hours (8:45 a.m. to 5:15 p.m.) in the Office of the Secretary, U.S. International Trade Commission, 500 E Street, SW., Room 112, Washington, DC 20436, telephone (202) 205-2000. Hearing impaired individuals are advised that information on this matter can be obtained by contacting the Commission's TDD terminal on (202) 205-1810. Persons with mobility impairments who will need special assistance in gaining access to the Commission should contact the Office of the Secretary at (202) 205-2000. General information concerning the Commission may also be obtained by accessing its internet server at<E T="03">http://www.usitc.gov</E>. The public record for this investigation may be viewed on the Commission's electronic docket (EDIS) at<E T="03">http://edis.usitc.gov</E>.</P>
        </ADD>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
          <P>The Office of Unfair Import Investigations, U.S. International Trade Commission, telephone (202) 205-2560.</P>
          <P>
            <E T="03">Authority:</E>The authority for institution of this investigation is contained in section 337 of the Tariff Act of 1930, as amended, and in section 210.10 of the Commission's Rules of Practice and Procedure, 19 CFR 210.10 (2012).</P>
          <P>
            <E T="03">Scope of Investigation:</E>Having considered the complaint, the U.S. International Trade Commission, on January 2, 2013, ORDERED THAT—</P>
          <P>(1) Pursuant to subsection (b) of section 337 of the Tariff Act of 1930, as amended, an investigation be instituted to determine whether there is a violation of subsection (a)(1)(B) of section 337 in the importation into the United States, the sale for importation, or the sale within the United States after importation of certain electronic devices, including wireless communication devices, tablet computers, media players, and televisions, and components thereof that infringe one or more of claims 1-3, 5, 8, 11, 13, 14, and 18 of the `052 patent; claims 28-33, 36, 37, 39-43, 46, 47, 50, 51, and 54 of the `359 patent; claim 30 of the `888 patent; claims 1-3, 8, 10, 19, 20, 23, 24, 26-33, 38, 40, 50, 53-55, 57, and 62-68 of the `556 patent; 1, 4, 6, 9-13, and 16-20 of the `310 patent; claims 1, 24-26, 28, 30, and 54 of the `917 patent; claims 1, 4, 6, 7, 17, 20, 22, and 23 of the `506 patent; claims 1-3, 11-14, 19, 21, 22, and 30-32 of the `223 patent, claims 1, 4, 9, 10, and 12 of the `832 patent; claims 1, 2, 4, 6, 8, 15, 22, 25, 26, 29, 32, 34, 45, 46, 49, 52, and 54 of the `215 patent; claims 1, 3, 5-8, and 10-15 of the `992 patent, and whether an industry in the United States exists or is in the process of being established as required by subsection (a)(2) of section 337;</P>
          <P>(2) Pursuant to Commission Rule 210.50(b)(1), 19 CFR 210.50(b)(1), the presiding administrative law judge shall take evidence or other information and hear arguments from the parties and other interested persons with respect to the public interest in this investigation, as appropriate, and provide the Commission with findings of fact and a recommended determination on this issue, which shall be limited to the statutory public interest factors, 19 U.S.C. 1337(d)(1), (f)(1), (g)(1);</P>
          <P>(3) For the purpose of the investigation so instituted, the following are hereby named as parties upon which this notice of investigation shall be served:</P>
          <P>(a) The complainants are:</P>
          
          <FP SOURCE="FP-1">Ericsson Inc.,6300 Legacy Drive,Plano, TX 75024;</FP>
          <FP SOURCE="FP-1">Telefonaktiebolaget LM Ericcson,Torshamsgatan 23, Kista,164 83 Stockholm,Sweden.</FP>
          
          <P>(b) The respondents are the following entities alleged to be in violation of section 337, and are the parties upon which the complaint is to be served:</P>
          
          <FP SOURCE="FP-1">Samsung Electronics America, Inc.,85 Challenger Road,Ridgefield Park, NJ 07660.</FP>
          <FP SOURCE="FP-1">Samsung Telecommunications America LLC,1301 East Lookout Drive,Richardson, TX 75082.</FP>
          <FP SOURCE="FP-1">Samsung Electronics Co., Ltd.,Samsung Electronics Building,1320-10, Seocho 2-dong,Seocho-gu, Seoul 137-857,Republic of Korea.</FP>
          
          <P>(c) The Office of Unfair Import Investigations, U.S. International Trade Commission, 500 E Street SW., Suite 401, Washington, DC 20436; and</P>
          <P>(4) For the investigation so instituted, the Chief Administrative Law Judge, U.S. International Trade Commission, shall designate the presiding Administrative Law Judge.</P>
          <P>Responses to the complaint and the notice of investigation must be submitted by the named respondents in accordance with section 210.13 of the Commission's Rules of Practice and Procedure, 19 CFR 210.13. Pursuant to 19 CFR201.16(d)-(e) and 210.13(a), such responses will be considered by the Commission if received not later than 20 days after the date of service by the Commission of the complaint and the notice of investigation. Extensions of time for submitting responses to the complaint and the notice of investigation will not be granted unless good cause therefor is shown.</P>
          <P>Failure of a respondent to file a timely response to each allegation in the complaint and in this notice may be deemed to constitute a waiver of the right to appear and contest the allegations of the complaint and this notice, and to authorize the administrative law judge and the Commission, without further notice to the respondent, to find the facts to be as alleged in the complaint and this notice and to enter an initial determination and a final determination containing such findings, and may result in the issuance of an exclusion order or a cease and desist order or both directed against the respondent.</P>
          <SIG>
            <DATED>Issued: January 3, 2013.</DATED>
            
            <P>By order of the Commission.</P>
            <NAME>William R. Bishop,</NAME>
            <TITLE>Supervisory Hearings and Information Officer.</TITLE>
          </SIG>
        </FURINF>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00149 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 7020-02-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">INTERNATIONAL TRADE COMMISSION</AGENCY>
        <DEPDOC>[Investigation No. 337-TA-812]</DEPDOC>
        <SUBJECT>Certain Computing Devices With Associated Instruction Sets and Software; Notice of Commission Determination Not To Review an Initial Determination Granting a Joint Motion To Terminate This Investigation Based on a Settlement; Termination of Investigation</SUBJECT>
        <AGY>
          <HD SOURCE="HED">AGENCY:</HD>
          <P>U.S. International Trade Commission.</P>
        </AGY>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>Notice.</P>
        </ACT>
        <SUM>
          <HD SOURCE="HED">SUMMARY:</HD>
          <P>Notice is hereby given that the U.S. International Trade Commission has determined not to review an initial determination (“ID”) (Order No. 18) granting a joint motion to terminate this investigation based on a settlement. The investigation is hereby terminated.</P>
        </SUM>
        <FURINF>
          <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>

          <P>James A. Worth, Office of the General Counsel, U.S. International Trade Commission, 500 E Street SW., Washington, DC 20436, telephone (202) 205-3065. Copies of non-confidential documents filed in connection with this investigation are or will be available for inspection during official business hours (8:45 a.m. to 5:15 p.m.) in the Office of the Secretary, U.S. International Trade Commission, 500 E Street SW., Washington, DC 20436, telephone (202) 205-2000. General information concerning the Commission<PRTPAGE P="1249"/>may also be obtained by accessing its Internet server (<E T="03">http://www.usitc.gov</E>). The public record for this investigation may be viewed on the Commission's electronic docket (EDIS) at<E T="03">http://edis.usitc.gov.</E>Hearing-impaired persons are advised that information on this matter can be obtained by contacting the Commission's TDD terminal on (202) 205-1810.</P>
        </FURINF>
      </PREAMB>
      <SUPLINF>
        <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
        <P>This investigation was instituted on February 27, 2012, based upon a complaint filed on behalf of VIA Technologies, Inc. of New Taipei City, Taiwan; IP-First, LLC of Fremont, California; and Centaur Technology, Inc. of Austin, Texas (collectively, “VIA”) on September 22, 2011, as amended on October 13, 2011, and as further amended on October 31, 2011. 76 FR 70490 (November 14, 2011). The complaint alleged violations of section 337 of the Tariff Act of 1930 (19 U.S.C. 1337) in the sale for importation, importation, or sale after importation in the United States of certain computing devices with associated instruction sets and software by reason of infringement of claims 1-4, 7-10, and 26-29 of U.S. Patent No. 6,253,312; claims 1, 14, and 21 of U.S. Patent No. 6,253,311; claims 20, 27, and 30 of U.S. Patent No. 6,754,810; claims 1-3 and 10-14 of U.S. Patent No. 7,185,180; and claims 23, 24 and 28-30 of U.S. Patent No. 7,155,598. The notice of institution named as respondent Apple Inc., a/k/a Apple Computer, Inc. of Cupertino, California (“Apple”).</P>
        <P>On November 19, 2012, VIA and Apple filed a joint motion seeking to terminate the investigation based upon a settlement agreement. On November 29, 2012, the Commission investigative attorney filed a response in support of the motion. On November 30, 2012, the administrative law judge granted the motion, finding that termination of the investigation based on a settlement between VIA and Apple does not impose any undue burdens on the public health and welfare, competitive conditions in the United States economy, the production of like or directly competitive articles in the United States, or United States consumers. No petitions for review were filed.</P>
        <P>Having considered the record in the investigation, the Commission has determined not to review the subject ID and to terminate the investigation.</P>
        <P>This action is taken under the authority of section 337 of the Tariff Act of 1930, as amended (19 U.S.C. 1337), and Part 210 of the Commission's Rules of Practice and Procedure (19 CFR part 210).</P>
        <SIG>
          <P>By order of the Commission.</P>
          <DATED>Issued: January 2, 2013.</DATED>
          <NAME>William R. Bishop,</NAME>
          <TITLE>Supervisory Hearing and Information Officer.</TITLE>
        </SIG>
      </SUPLINF>
      <FRDOC>[FR Doc. 2013-00070 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 7020-02-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="N">DEPARTMENT OF JUSTICE</AGENCY>
        <DEPDOC>[OMB Number 1121-NEW]</DEPDOC>
        <SUBJECT>Agency Information Collection Activities; Extension of a Currently Approved Collection; Comment Request:Equal Employment Opportunity Plan Certification and Short Form</SUBJECT>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>30-Day Notice.</P>
        </ACT>

        <P>The U.S. Department of Justice (DOJ), Office of Justice Programs (OJP) will be submitting the following information collection request to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act of 1995. The proposed information collection is published to obtain comments from the public and affected agencies. This proposed information collection was previously published in the<E T="04">Federal Register</E>, Volume 77, Number 207, page 65204, on October 25, 2012, allowing for a 60-day comment period.</P>
        <P>The purpose of this notice is to allow for an additional 30 days for public comment until February 7, 2013. This process is conducted in accordance with 5 CFR 1320.10.</P>
        <P>Written comments and/or suggestions regarding the items contained in this notice, especially the estimated public burden and associated response time, should be directed to the Office of Management and Budget, Office of Information and Regulatory Affairs, Attention: Department of Justice Desk Officer, Washington, DC 20503. Additionally, comments may be submitted to OMB via facsimile to (202) 395-7285. Written comments and suggestions from the public and affected agencies concerning the proposed collection of information are encouraged. Your comments should address one or more of the following four points:</P>
        
        <FP SOURCE="FP-1">—Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</FP>
        <FP SOURCE="FP-1">—Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</FP>
        <FP SOURCE="FP-1">—Enhance the quality, utility, and clarity of the information to be collected; and</FP>
        <FP SOURCE="FP-1">—Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology; e.g., permitting electronic submission of responses.</FP>
        <HD SOURCE="HD1">Overview of This Information Collection</HD>
        <P>(1)<E T="03">Type of Information Collection:</E>Revision of a currently approved collection.</P>
        <P>(2)<E T="03">Title of the Form/Collection:</E>Equal Employment Opportunity Plan Certification and Short Form.</P>
        <P>(3)<E T="03">Agency form number, if any, and the applicable component of the Department sponsoring the collection:</E>The Office for Civil Rights, Office of Justice Programs, United States Department of Justice, is sponsoring the collection.</P>
        <P>(4)<E T="03">Affected public who will be asked or required to respond, as well as a brief abstract:</E>Primary: State, and local, government instrumentalities. Other: For-profit Institutions. 28 CFR 42.301 et seq. authorizes the Department of Justice to collect information regarding employment practices from State or Local units of government, agencies of State and Local governments, and Private entities, institutions or organizations to which OJP, COPS or OVW extend Federal financial assistance.</P>
        <P>(5)<E T="03">An estimate of the total number of respondents and the amount of time estimated for an average respondent to respond/reply:</E>There are a total of 6371 respondents. It is estimated that it will take 1,290 respondents receiving a grant of $500,000 or more one hour to complete an Equal Employment Opportunity Plan Short Form and submit it to the Office of Justice Programs. In addition, an estimated 5,081 of respondents seeking grants ranging from $25,000 up to $500,000 will be required to complete Certification stating that they are maintaining a current Equal Employment Opportunity Plan on file and submit the certification to OJP. Completion and submission of the Certification will take<FR>1/4</FR>hour.</P>
        <P>(6)<E T="03">An estimate of the total public burden (in hours) associated with the collection:</E>For the 6371 respondents, the total estimated burden hours on respondents would be 2,560 to complete the EEOP Short Form or Certification.<PRTPAGE P="1250"/>
        </P>
        <P>If additional information is required, contact Jerri Murray, Department Clearance Officer, United States Department of Justice, Justice Management Division, Policy and Planning Staff, Two Constitution Square, 145 N Street NE., Room 3W-1407B, Washington, DC 20530.</P>
        <SIG>
          <DATED>Dated: January 3, 2013.</DATED>
          <NAME>Jerri Murray,</NAME>
          <TITLE>Department Clearance Officer for PRA,U.S. Department of Justice.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00147 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4410-18-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
        <DEPDOC>[OMB Number 1103-NEW]</DEPDOC>
        <SUBJECT>Agency Information Collection Activities:Proposed New Collection; Comments Requested; Stress Resiliency Study Questionnaires for Milwaukee Police Department</SUBJECT>
        <ACT>
          <HD SOURCE="HED">ACTION:</HD>
          <P>60-Day notice.</P>
        </ACT>
        <P>The Department of Justice (DOJ) Office of Community Oriented Policing Services (COPS) will be submitting the following information collection request to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act of 1995. The revision of a previously approved information collection is published to obtain comments from the public and affected agencies.</P>
        <P>The purpose of this notice is to allow for 60 days for public comment until March 11, 2013. This process is conducted in accordance with 5 CFR 1320.10.</P>
        <P>If you have comments, especially on the estimated public burden or associated response time, suggestions, or need a copy of the proposed information collection instrument with instructions or additional information, please contact Danielle Ouellette, Department of Justice, Office of Community Oriented Policing Services, 145 N Street NE., Washington, DC 20530.Written comments and suggestions from the public and affected agencies concerning the proposed collection of information are encouraged. Your comments should address one or more of the following four points:</P>
        
        <FP SOURCE="FP-1">—Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</FP>
        <FP SOURCE="FP-1">—Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</FP>
        <FP SOURCE="FP-1">—Enhance the quality, utility, and clarity of the information to be collected; and</FP>
        <FP SOURCE="FP-1">—Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, e.g., permitting electronic submission of responses.</FP>
        <HD SOURCE="HD1">Overview of This Information Collection</HD>
        <P>(1)<E T="03">Type of Information Collection:</E>Proposed new collection; comments requested.</P>
        <P>(2)<E T="03">Title of the Form/Collection:</E>Stress Resiliency Study Questionnaires for Milwaukee Police Department.</P>
        <P>(3)<E T="03">Agency form number, if any, and the applicable component of the Department sponsoring the collection:</E>None. U.S. Department of Justice Office of Community Oriented Policing Services.</P>
        <P>(4)<E T="03">Affected public who will be asked or required to respond, as well as a brief abstract:</E>The Milwaukee Police Department (MPD) will be the affected public who is subject to this survey through a COPS cooperative agreement with the MPD. These surveys will be used to collect data on MPD officers' perceived stress, responses to stressful experiences, stress and its relationship to biometrics and related questionnaires.</P>
        <P>(5)<E T="03">An estimate of the total number of respondents and the amount of time estimated for an average respondent to respond/reply:</E>It is estimated that 120 respondents annually will complete the form within .57 hours (34 minutes).</P>
        <P>(6)<E T="03">An estimate of the total public burden (in hours) associated with the collection:</E>There are an estimated 68 total annual burden hours associated with this collection.</P>
        <P>If additional information is required contact: Jerri Murray, Department Clearance Officer, United States Department of Justice, Justice Management Division, Policy and Planning Staff, Two Constitution Square, 145 N Street NE., Room 3W-1407B, Washington, DC 20530.</P>
        <SIG>
          <DATED>Dated: January 3, 2013.</DATED>
          <NAME>Jerri Murray,</NAME>
          <TITLE>Department Clearance Officer for PRA,U.S. Department of Justice.</TITLE>
        </SIG>
      </PREAMB>
      <FRDOC>[FR Doc. 2013-00148 Filed 1-7-13; 8:45 am]</FRDOC>
      <BILCOD>BILLING CODE 4410-AT-P</BILCOD>
    </NOTICE>
    <NOTICE>
      <PREAMB>
        <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
        <SUBJECT>Notice of Lodging of Proposed Consent Decree Under the Clean Air Act</SUBJECT>

        <P>On December 20, 2012, the Department of Justice lodged a proposed Consent Decree with the United States District Court for the District of Massachusetts in the lawsuit entitled,<E T="03">United States of America</E>v.<E T="03">Solutia, Inc. and INEOS Melamines, LLC,</E>Civil Action No. 3:12-cv-12377-KPN.</P>
        <P>In its Complaint, the United States alleged that the Defendant's actions at their chemical manufacturing plant violated the Clean Air Act, and regulations promulgated pursuant to the Clean Air Act. The alleged violations occurred at the Defendants' Indian Orchard Plant in Springfield, Massachusetts. The United States alleges in its Complaint that Defendants violated: (A) Sections 112 and 502 of the Clean Air Act, 42 U.S.C. 7412 and 7661a, and implementing regulations; (B) the Final Reasonably Available Control Technology Compliance Plan Conditional Approval issued by the Massachusetts Department of Environmental Protection (“Massachusetts DEP”) on June 20, 1989 which contains requirements on the operation of the Plant; and (C) the Air Quality Operating Permit issued to Solutia Inc. on June 26, 2005 by the Massachusetts DEP pursuant to Title V of the Clean Air Act and 310 C.M.R. 7.00: Appendix C which also contains requirements on the operation of the Plant.</P>
        <P>Upon entry of Consent Decree, the Defendants will pay a civil penalty in the amount of $970,000 to the United States. In addition, under the terms of the Consent Decree, the Defendants will implement an enhanced leak detection and repair system to control and manage the air pollutants emitted at the facility. As part of this leak detection and repair system, the Defendants will undertake efforts above and beyond what is currently required by the Clean Air Act and the regulations that the United States alleged were violated at the Plant. Pursuant to the proposed Consent Decree, the Defendants will conduct more frequent monitoring for possible equipment leaks, use lower thresholds for the repairs of leaks, replace leaking equipment more quickly with improved equipment, and conduct third-party audits of its leak detection and repair program.</P>

        <P>The proposed Consent Decree resolves both Solutia Inc.'s liability, and INEOS Melamines, LLC's liability for all of the violations of the Clean Air Act<PRTPAGE P="1251"/>that the United States alleges in its Complaint.</P>

        <P>The publication of this notice initiates a 30-day period for public comment on the proposed Consent Decree. Comments should be addressed to the Assistant Attorney General, Environment and Natural Resources Division, and should refer to<E T="03">United States of America</E>v.<E T="03">Solutia, Inc. and INEOS Melamines, LLC,</E>D.J. Ref. No. 90-5-2-1-09980. All comments must be submitted no later than thirty (30) days after the publication date of this notice. Comments may be submitted either by email or by mail:</P>
        <GPOTABLE CDEF="xs100,r100" COLS="2" OPTS="L0,tp0,p0,8/9,g1,t1,i1">
          <TTITLE/>
          <BOXHD>
            <CHED H="1"/>
            <CHED H="1"/>
          </BOXHD>
          <ROW>
            <ENT I="01">
              <E T="03">To submit comments:</E>
            </ENT>
            <ENT>
              <E T="03">Send them to:</E>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="01">By e-mail</ENT>
            <ENT>
              <E T="03">pubcomment-ees.enrd@usdoj.gov.</E>
            </ENT>
          </ROW>
          <ROW>
            <ENT I="01">By mail</ENT>
            <ENT>Assistant Attorney General, U.S. DOJ-ENRD, P.O. Box 7611, Washington, DC 20044-7611.</ENT>
          </ROW>
        </GPOTABLE>

        <P>During the public comment period, the Consent Decree may be examined and downloaded at this Justice Department Web site:<E T="03">http://www.usdoj.gov/enrd/Consent_Decrees.html.</E>We will provide a paper copy of the Consent Decree